-
Content Count
5,951 -
Joined
-
Last visited
-
Days Won
412
Posts posted by EskeRahn
-
-
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.-
1
-
-
(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 👎 -
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.-
1
-
-
@TeZtdeviceInteresting idea with the Aeroplane mode, I will try that overnight WITH the sim physically mounted.
ADD: After 11 hours in Aeroplane mode it was down to 94%, so roughly 0.5% per hour. Certainly not impressive, but tolerable.
Will recharge, and see what the day brings, but has not got my hopes up high.....
ADD II: still bad out of Aeroplane mode-
1
-
-
(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...-
2
-
-
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. -
8 hours ago, CornholioGSM said:
Have you tested to play with network connection modes in 4636 menu?
No, I have not bothered to fiddle with that, nor have I tried with a sim from another carrier.
-
..Nice @hling, we got a very long thread mainly with DIY cases over here:
-
1
-
-
12 minutes ago, Hook said:
Well, and this will probably be my last comment on this unless something changes-
I'm very tempted to flash back to 22.1, and await and see if a 23.0 in a year or so will fix it...
-
(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-
2
-
-
This is a ping-post, as i updated the above post multiple times, and the conclussion this far is
The 22.2 bug seems to be related to the presence of a SIM card!! -
On 5/12/2025 at 12:19 PM, claude0001 said:
I think many (most?) of those who had ordered an OG (qx1000) Pro1 via the website and were "upgraded" to a qx1050 after the SoC thing happened. At some point all the focus was on IGG backers, and website customers were left in the rain ...
Sadly I think this is accurate. 😢
-
1
-
-
(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?
-
3
-
-
-
I have upgraded it (without factory reset) to 22.2 20250503, and will recharge and see what happens. If horrible, I will try with yet another factory reset (and no MTG, no and no apps whatsoever, all left default, and skip/disable to all questions)....
-
1
-
-
At 22.1 20250405 with same setup after two hours it has gone from 100% to.... 99%
So I still claim that 22.2 is borked... Sorry.
...After 5h: 97%, 8h: 94%-
1
-
-
At 03 I finished recharging after installing the 0503 with MTG, with only very few apps, and restricted all I can, and in just 4h11m it has eaten 31%, so there IS an issue - sorry.
I will flash back to 22.1 (dirty, and if needed with a Factory reset, and recreate)
I flashed back to 22.1 (0405) with a factory reset and will recreate.
-
1
-
-
I HOPE that I sometimes in the following week will have verified that all from the original Pro1 that can be transferred has been, so I can install LineageOS 22.2 on it freshly reset, and I will be sure to install the same 0503 version reported on above, to rule out that anything that had issues has been fixed. (But no promise I will find time for it)
-
1
-
-
USUALLY the problems people experiences with fastboot is related to the communication with the watch.
Either cable, port or driver.
Silly as it may sound on Windows11, a 'newer' USB3 port might cause problems. On my Lenovo X1 Yoga gen 6 (20XY), I can not get fastboot to work directly. But if I use an old usb2 hub, things works fine. It also works fine if I go via my thunderbolt 4 docking, and a USB3 port on that.
AFAIK, there are fewer issues if the machine is on LINUX.
You might also try from an old PC with USB2 ports only.Usually it is not super picky on the cable, but try swapping that also if a different port does not help. And then finally the more complex is that not all drivers works equally well, and that can be a hassle.
(Note that on my pc, a direct cable works fine with ADB or with file-transfer, it is fastboot that is quite picky) - my guess would be a handshaking issue in fastboot for Windows, where it fails if it gets the answer too fast)-
2
-
-
Hmm, not in my case. It worked fine on 22.1, and now works fine back on latest stock android.
Though I will not rule out if Lineage got the calibration wrong, and thought it was at 100% when it was not, and thus did not use the full span - I highly doubt it though.
Much more likely that 'something' in the system got confused on the dirty flashing from 22.1 to 22.2 (or maybe rudiments from earlier dirty flashing, that kicked in going to 22.2) I really ought to have made a factory reset while on 22.2, to test before going to stock, but well I did not....
But anyone else seeing the bug, I would strongly recommend to try a factory reset (after suitable backups obviously)-
2
-
-
-
5 hours ago, TeZtdevice said:
Updated / now closed ticket:
No such drain here - must be something you're doing mod or app wise.
Hmm the below seems to say otherwise. But It MIGHT be the lacking factory reset that triggered the bug.
-
Well I'm now off the LineageOS wagon for a while, at the least until I get all transferred, a lot is omitted by google on transfer. Several important apps .... 😠
Note that I did NOT do a factory reset going from 22.1 to 22.2, so that MIGHT be the issue, and obviously would be the first to try for a support ticket.....-
1
-
-
I just followed the guide at page 1, and took the liberty to adjust a few more details
- The line on userdata missed a destination
- Commented that you might want to skip flashing persist.img if from Android/LineageOS
- Added that you MUST do an extra factory reset from the settings, to use the full amount of memory.
Hope that's OK @Waxberry🙂
-
2

LineageOS 22.x Official Release for Pro1 (QX1000)
in General Discussion
Posted
Picked fairly at random... Need UMTS B1+B and LTE B3+7, https://www.frequencycheck.com/carriers/3-tre-denmark and or
https://www.frequencycheck.com/carriers/tdc-denmark (GSM 900, 1800, UMTS B1+B8, LTE B7+B20+B3)