Jump to content

EskeRahn

Keymaster
  • Content Count

    5,937
  • Joined

  • Last visited

  • Days Won

    406

Posts posted by EskeRahn

  1. 17 hours ago, hling said:

    EskeRahn, I quickly glanced at the post about screen replacement and saw that CornholioGSM is located in the EU. I'm in NYC. So probably not feasible.   When I press the on button today there was a flash of the wall paper intact and then black again.

    Hmm this might actually be good news, as this sounds more like a software bug than a hardware bug. Can it boot into bootloader-mode showing the menu?
    If so a factory reset is most likely the way to go, and if that does not do the trick a full reflash to factory mode. (follow the first post on the forum)

  2. If you are 'lucky' it is 'just' the display, though that it not something you just go and buy a new around the corner, it is possible to replace for many with a little tech knowledge. If I recall correctly @CornholioGSM has offered the service of swapping for some price. so if that still holds and depending on your location, that might be an interesting option. 

  3. 3 hours ago, puppymang said:

    nothing constructive to add but i just wanted to say thanks

    i use my pro1 as my daily driver with VZW and would've hated to have to go through downgrading to a version that doesn't have battery problems.

    It does not seem to be everyone that gets this bug, but the risk is clearly there.

    • Like 2
  4. 10 hours ago, claude0001 said:

    Imho, distributing an unofficial ROM really makes sense only if you daily-drive it yourself.

    Totally agree, and I really only use it for testing the usability of LOS, and have it idle as a workphone, that does not ring each month anyway... So would easily overlook al kind of bugs myself, I just check that it installs smoothly, check if the keyboard works (and it has not really worked for me for quite a while) - and else keep it on stand by. So if I suddenly could not make or receive a call there could go half a year before I found out....On the other hand a drop in idle stand by was quickly spotted.....

    • Like 1
  5. 3 hours ago, claude0001 said:

    Not that I have anything constructive to add, but in LineageOS's defence: They are stuck forever with the Linux kernel version and drivers that shipped with the original Android 9 OS. As the divide between increasingly modern Lineage/Android userland and the base Linux OS amplifies, bugs like this become more and more likely, unfortunately. 

    Oh I know it is good people doing their best - I'm just frustrated, sorry for whining.
    But as you keep the 16.0 alive, we can hope that  you, or someone else with the suitable knowledge, can keep the 22.1 alive, if the 22.2 stay broken.... Let us see what the coming months or the 23.0 next year will bring.

    But as this is a bug not all seem to see, I guess the chance for it ever being fixed is slim. As with any bug the first step to a fix very often goes trough being able to reproduce it.

    • Like 1
  6. Next step 22.1 and factory reset here, wasted enough time on useless 22.2 - I wonder if it is like AICP a nice project that was just made horrible by some crucial bugs.... 😣:classic_sad:

    (PS the factory reset, sets the band selection back to the default LTE/TDSCCDMA/CDMA/EvDo/GSM/WCDMA)

    ADD: And back to a more reasonable consumption 4% in roughly three hour
    Will try "LTE/CDMA/EvDO/GSM/WCDMA (PRL)" on 22.1 just for the fun of it.....
    And it is down 4% in another 3½ hours

    • Thanks 1
    • Haha 1
  7. 11 hours ago, CornholioGSM said:

    ....again question...have you tested to switch to another network mode in *#*#4636#*#* ?

     

    ...I got it at default
    LTE/TDSCCDMA/CDMA/EvDo/GSM/WCDMA
    just tried to change to
    LTE/TDSCCDMA/GSM

    ADD I:
    ...The "LTE/TDSCCDMA/GSM" ate 50% in slightly short of eight hours while I slept - so still utterly useless.

    ADD II:
    Tried "LTE only" (after some recharging) And this seems even worse. 5% in half an hour!!!

    ADD III:
    Now trying "LTE/CDMA/EvDO/GSM/WCDMA (PRL)" , as suggested by @CornholioGSM 
    Absolutely horrible 9% in an hour, if it improved anything compared to "LTE only" it was by a tiny tiny margin.

    • Like 1
  8. (lineage-22.2-20250531-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511)

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
    The draining bug with a sim inserted is still there... 5% in the first hour, completely idle, with almost all apps removed 👎

  9. 17 hours ago, TeZtdevice said:

    7-8% in 7 hours with flightmode on and mounted SIM.

    Well we could live with that... I got a bit better, but mine is currently a REALLY minimalistic setup, and was with zero screen interaction, so that was to be expected.
    But in the order of 1% / hour would be what I'm used to see WITH the sim mounted and online on e.g. 22.1.

    • Like 1
  10. (lineage-22.2-20250524-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511)

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
    I have no idea whether the draining issue has been improved/fixed.
    The bug is still there...

    • Like 2
  11. There are SO many things that could be tested and adjusted, that just might affect this, so really a complex job to pin-point.

    Just like FxTec never really pin-pointed the conditions in which the Pro1X has network issues....
    But it sure could be interesting to dig into the differences. A bit sad it came with a semi-major update, making it much harder to give a qualified guess on where the bug was introduced.

  12. (lineage-22.2-20250517-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511)

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
    I have no idea whether the draining issue has been improved/fixed.
    The bug is still there, from 100% to 24% in roughly 11 hours idle over night

    • Like 2
  13. (BTW it seems so greedy that the reduced current at 98% makes it hard to reach 99%, it has been at "98% - charging" for over half an hour 🙈... display off, checks about every five minute...)

    UPDATE: Got it charged to 100% and after 3h it is down to 96% and that is OK.
    So now I will try to reenable the stuff I disabled, and recharge. But still No sim, no WiFi, no apps

    UPDATE: After 75m it is down to 99% and that is OK.
    So now I tried to add sim and WiFi, no account, no apps, and recharged.

    UPDATE: After 4h it is down from 100 to 82% and that is not good, 4½ %/h...
    I will now remove WiFi, and recharge...

    UPDATE: After less than 1h like that it is down from 100 to 93% and that is really bad.
    I will try to add WiFi and remove the sim. And recharge...

    UPDATE: After 6h it is down to 96% and that is OK.
    SO the 22.2 bug seems to be related to the presence of a SIM card!!
    The next interesting question is if it is a specific sim card, or some specific bands the 22.2 can not handle properly???
    Note that it is left at the default state of mobile data being disabled.

    Next I just reinserted the sim to verify, that it is here the culprit is.
    UPDATE: After slightly under 1h it is down from 100 to 95% and that is not good, ~5 %/h...

    ...I have turned it OFF.

    I use "3" in Denmark, and AFAIK they use B1(2100MHz) and B8(900MHz) for UMTS as well as B3(1800MHz).

    Those of you that tested 22.2 without the issue, do you have a sim inserted, and if so, what bands are you using?

    • Thanks 3
×
×
  • Create New...

Important Information

Terms