Related
Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Inginerul said:
Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Click to expand...
Click to collapse
Yes... noticed this with Sygic. It's a known app bug, and they still haven't fixed it yet. Haven't had this issue with Google maps though. Be warned however that any navigation app will chew up your battery very fast... Can't help it since it's accessing the Net, Compass, Accelerometer and GPS antenna - all at the same time at a high refresh rate...
Thank you fir your reply!
I know navigation is supposed to use a lot of battery but doing it even with processes closed?
It's good to know you confirm the Sygic bug. Honestly I've googled for 2 days and wasn't able to find any useful info about such a bug with Sygic. And for me, since Google Maps 6.6.0 acts the same way, it makes me think it's also a bug. For now I'm sticking to Maps 5.8.0 and I've reported the issue over to Google.
Thank you again!
Sony xperia Z3 Dual D6633 Android 5.0.2 Build 23.1.1.E.0.1
Hi there,
Upgraded my Z3 to lollipop last week and, despite the fact that the upgrade itself was flawless, I think I went from a device that used to work like a charm to one full of annoyances.
On day #1, noticed the batt drain skyrocket. 3h after disconnecting it, it was at 68%, half way through the morning. WTF? was my first thought. On a typical day on kitkat, I was able to end the day at 40% at least.
The second thing I´ve noticed was the phone app. It starts giving me errors, saying that the "network could not be reached" when I try to dial a number. If I insist for 4, 5 more times, it crashes. Dialing is only possible again if I reset the phone.
The third thing is the lock screen. It seems that lollipop has a drop down menu that makes it possible to enable/disable lots of things, like communications and even setting the phone in airplane mode. Imho that´s a huge liability / security risk and it appears that there is no way around that.
Still about the lock screen, it seems to have a bug: if you have any activesync account setup, not notifications will show up, no matter how you configure it (to show all or hide sensitive content).
So, I had only one thing to do, after reading forums etc... factory reseting it.
Surprise! All problems are still there.
Does any1 have any tips on those?
Thanks in advance.
There will be a widget on one of the screens which keeps refreshing itself and I found that to be the battery killer on my 6603.
Did you use any specific app to pinpoint the culprit?
1. It is possible that the battery levels are calibrating and will be imprecise for a while after the update, using the device normally for a couple of days will fix it, or at least this is what I observed in many phones I owned.
2. This is very weird and I can't help you with. If not even factory reset did help you may have some corrupted data on one of your contacts maybe? Try to make a thread about this issue on the Sony forum.
3. I noticed that as well, but even on pervious versions you could turn off the phone so I don't think it changes anything. Make sure to disable the multi user options that would allowanyone to add a new user from the lock screen.
4. Another weird thing, I use exchange accounts on my phone and I don't have any problem on mine. See point 2.
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
ozzy lion said:
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
Click to expand...
Click to collapse
That's not a smartphone anymore, with all functions shut down and brightness low.
This phone has the best screen, use it at least 50% brightness.
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
ozzy lion said:
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
Click to expand...
Click to collapse
You said stamina.
Stamina means already some functions off.
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Hi, if problems are persistant you can always downgrad software at KitKat by using FlashTool and wait Lollipop 5.1 (5.1 will probably solve many problems).
StealthNet said:
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Click to expand...
Click to collapse
A new firmware version has dropped for the Z3 which I think fixes your issues with notifications.
I received it OTA yesterday, I'm running the Balkans customisation.
Thank you for the tip! I hope it does! Will keep it posted here just for the reference. I am starting to feel other "symptoms" as well, like bluetooth instability (you pair a device and it stops working, have to pair again).
.
Just hit another weird thing.
I am not being able to create a new vpn connection. I am trying to use the PureVPN and IPVanish client software, but when I try to setup the conection, I receive a disclaimer, saying that my traffic might be monitored, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
My device is encrypted and I have also noticed that I am not able to decrypt it.
Also, If I go to Accessibility and try to enable a service, the same thing happens: a disclaimer appears, saying that the service might observe my actions, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
Any ideas?
Ok, just a quick fup: the ability to create VPNs from apps is disabled if you encrypt the phone. It seems that if you create if before encrypting, it won´t be disabled; but you wont be able to create a new vpn from an app downloaded, after encryption.
Regarding the Accessibility > Services, after a *lot* of research, I have found that Twilight was the culprit. For the reference:
https://code.google.com/p/android/issues/detail?id=79637
I'm having an issue where it takes fund minutes to lock location on the phone. The problem is most noticeable on Waze. I turn Waze on every time I get in the car (the speed traps alone are worth it), and sometimes it's half my trip before it locks on.
The location is set to high accuracy, and it does eventually lock on. My 6p would lock on in one second.
Anyone else? Thanks
lanternca said:
I'm having an issue where it takes fund minutes to lock location on the phone. The problem is most noticeable on Waze. I turn Waze on every time I get in the car (the speed traps alone are worth it), and sometimes it's half my trip before it locks on.
The location is set to high accuracy, and it does eventually lock on. My 6p would lock on in one second.
Anyone else? Thanks
Click to expand...
Click to collapse
I've seen issues in Waze as well, with both GPS lock and the Compas going screwy...
Have you guys tried running gps status or gps toolbox?
What settings do you have selected in location settings?
On my v10 if I enable the additional low power Qualcomm IZat location estimation option, gps runs all screwy.
Id like to know if gps is hit or miss, as its another of the main features I need and use on a daily basis, along with Ok Google..
My Pixel is now locking GPS in a few seconds after I open Waze. Probably even faster than my 6P.
For anyone else having these problems, here are all the steps I did (not sure which if any of these actually solved the problem)
1. Uninstalled Waze. Turned off Location. Rebooted into Safe Mode (Long Press "Power Off")
2. Once in Safe Mode, turn location back on, open Google Maps outside, let GPS lock (that time still took a while) and use navigation for a while
3. Rebooted the phone again into safe mode. reopened Google Maps and let GPS lock on
4. Rebooted the phone normally, open Goolge Maps first to make sure GPS was working. Then installed Waze
It's been working pretty well for the past few days.
I'm still seeing issues with the compass, I get a GPS lock quickly, but it always shows I'm pointing 100-160 degrees off from my actual heading. Tried using GPS status to calibrate, it now says I'm calibrated, but I still see the issue, even in GPS Status.The compass points in one direction, then once I start moving, the GPS corrects the heading to my actual direction...
I've never had this issue with any other phone, very frustrating.
Hi,
Since about 2 weeks ago, every time I reenable GPS I get popus asking for permission for High Accuracy.
Problem is, I want HA mode. This is the mode I use by default, by I always disable Location (via Tasker action) if I'm not using an app that needs it.
Initially I thought it's a problem with Tasker, but I tested that even if I just use top-menu shortcut (or any other way to turn off GPS), I will get the popup when reenabling.
Steps to reproduce:
1. Enable GPS, switch to High Accuracy mode.
2. Turn off GPS (just the top menu icon, or slider in Settings).
3. Turn on GPS -> popup on the screen.
Phone is SM-G930F running Oreo, R16NW.G930FXXS2ERH6 software (stock).
Does this happen to anyone else? Can someone test?
Happens here as well, GS9+, everytime I use high accuracy mode, no matter the app.
Thanks! I still don't know what I can do about this, but at least you confirm it's not any special case.
Same on my Note 10+ -_- Rather annoying
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 on LineageOS 19.1.
At first I want to thank @rINanDO, @ChronoMonochrome for all your work which was reused here and helped a lot.
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
GPS
Wifi
USB
Video playback (HW/SW)
OTA Updates
Tethering via USB, WIFI and Bluetooth
Sensors
RIL
Spoiler: Whats not working
NFC
Encryption
Maybe random reboots
SD card maybe can't formated as internal memory
Maybe more
I would recommend to use microG instead of gapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Spoiler: Changelog
26.01.2022
08.03.2022
17.03.2022
25.03.2022
04.04.2022
19.04.2022
03.05.2022
15.06.2022
08.07.2022
22.09.2022
25.01.2023
Spoiler: How to install it?
Instructions
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Telegramm group:
Samsung Galaxy Note II testing group
t.me
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
XDA:DevDB Information
[ROM][12.x][N7100][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Beta
Created 2021-12-30
Last Updated 2023-01-25
Alternative download link for the initial version:
File on MEGA
mega.nz
Originally posted in [ROM][UNOFFICIAL][11.0][N7100][Samsung Galaxy Note 2][LineageOS 18.1][ALPHA][TREBLELIZED]:
I just flashed the newly Android 12 LineageOS 19 build this morning.
It's currently a bit early to share my experience yet since I need some more time, but I already like to share my first impression.
First of all, I was surprised that I could just do a dirty flash over your current 18.1 dec build without any problems.
I did not perform a clean flash because I couldn't backup my Session messages, normally I always perform clean flashes.
I used TWPR 3.5.2 custom recovery to flash this ROM and only wiped Cache and Dalvik Cache/ART partition.
Everything went smooth. It didn't take too long for the first boot either.
Right after the first boot, just when it was booted, the phone rebooted.
After this reboot, I didn't encounter any random reboots yet.
Everything seems working smooth and snappy at the moment.
I can confirm that Magisk 23 is still working on this ROM. You just need to re-flash it after the first boot.
The only annoying thing I discovered is a blinking LED issue and the battery that last less longer, but that's maybe linked to the blinking LED issue.
Something I immediately noticed is that my notification LED is actually red now while charging and green when it hits 100%.
In previous 18.1 build, the LED always got a weird yellowish colour while charging.
Another thing that caught my eye was "Google Play System update" in settings.
I don't understands why it's there since it's supposed to be a degoogled ROM.
Google Play System updates is a part of the Google Play Services ecosystem.
I didn't install any GAPPS and this ROM didn't came with GAPPS pre installed.
Spoiler: What I can confirm is working
- It (re)boots correctly
- Able to receive and sending sms messages and phone calls (didn't try SIM unlock yet. I used the workaround that is mentioned in the main post)
- Camera's
- Wi-Fi (both, 2.4 GHz and 5GHz)
- Video's (YouTube in browser)
- Sensors, except compass (phone rotates correctly)
- Charge correctly to 100%
- S-pen (just as a regular styles, no button functionality)
Spoiler: What is not working + bugs
- An annoying blinking LED issue.
I never experience this before on any ROM.
Can be a coincidence, but after the battery drops below 75%, the notification LED is constantly blinking red, even when the screen is on.
I already tried to literary turn off all notifications options. I even disabled blinking LED option, but it still keeps blinking, even after a reboot. It only disappears after fully charging the phone but will come back in time.
I didn't find a way to fix this.
- Android 12 theme engine seems to be broken.
Some things like buttons (like emergency call button on lockscreen), text (search apps in launcher) and backgrounds in notifications icons in notification panel are still LineageOS teal.
Switching a wallpaper with different colours, but it doesn't change the theme colour of the device. Buttons, lockscreen clock etc. are still light blue. I try to add some screenshots to highlight this problem.
Also, the options to change the icon shape seems to be gone, even in developer settings.
Everything turned into circles after the update. Can't change it.
- USB (can't connect to pc (MTP))
- Extended screenshot beyond your screen
- There was a weird issue that my device is stuck at Samsung Galaxy II screen when turning on the device (not the LineageOS boot screen). I only had this once so can't describe how to reproduce it yet.
I just turned off my device in the power setting inside the ROM. The next time I turned on the device, it was stuck on that screen for 10 minutes. It was fixed by simply holding the power button for a while to turn off the phone.
After doing this, the phone rebooted normally again. I didn't got this issue again.
Besides the blinking LED issue, I had a very good first impression.
I really don't mind that some gimmick features are not working.
I only have this ROM for a few hours, so please keep in mind that I need more time for extensive and more in-depth testing.
Maybe there are some critical problems that I still need to discover.
I just wanted to give a quick update.
@html6405
If there are some specific things you like to try or things I need to keep an eye on, please let me know.
A big thank you to html6405 for this rom! Almost everything seems to work good.
The only thing i am missing is wake by proximity sensor. I use the app Waveup from F-droid for this. I know from trying other roms, that this is an unreliable feature. The sensor hardware is working, that much i know.
When using Lineageos 16, this is a built in feature in the rom, but it deactivates after every reboot. I have to manually turn it off and on every time to get it to work.
No big issue. Just glad to have latest Android on this device. I hope you get more appreciation from this than what you got from your Los 18.1 thread.
Let me know if you want feedback of any kind.
Happy new year!
It does work! I couldn't resist trying the future LOS19.
The overall impression is quite good, as the system seems to be more stable than the previous LOS18.1 for this phone. Still, the development options screen hanged a couple of times. At some point the system crashed and kept rebooting into recovery - fixed by erasing data partition. GPS works, although not well enough. The compass doesn't work in GPStest, but works in Compass app from Fdroid. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Two preinstalled applications are unsafe, contain trackers: camera and via. These had to be removed. Open Camera from Fdroid is installed - it works. The system web browser is preconfigured to ring Google; one may want to review its settings.
Installed Insular app (a sandbox made of the work profile) from Fdroid. The work profile works, but looses its filesystem after disabling and enabling it again. To bring the filesystem back reboot is required.
Phone encryption doesn't work, sadly. This is the same as with many previous custom ROMs for this phone.
A strange horizontal bar is seen at the bottom of the screen (nav bar home button??). Disable "Navigation hint" to get rid of it.
All together, it's an excellent result for the first attempt on LOS19. Looking forward to further releases!
Happy New Year everyone! Thank you html6405 for such an exciting present!
porcino said:
GPS works remarkably well, better than in the previous ROM, but compass doesn't work. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Click to expand...
Click to collapse
This are really great news, could some one else confirm that GPS is working?
I cant test it by my own...
If it's working fine, I will add it to the working list.
GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
----------------
Added later... Still, GPS is not working well enough in this first release. It finds satellites slower than my ancient HTC DHD (ace) running cm13. Then it locks and in a moment loses the lock. I'll look into this in more detail...
porcino said:
GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
Click to expand...
Click to collapse
Great, hopefully some one else can confirm this , you're the only person so far.
Yes indeed - working GPS very important, and needs to be confirmed by multiple sources.
But kudos to the developer for making progress on this.
hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!
alexfire_s said:
hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!
Click to expand...
Click to collapse
Just tried: flight mode, screen off, location off, BT and NFC off, no GApps, just sitting on the desk starting with fully charged. After half an hour the estimated battery life is 10h, 6m. Not great. The battery felt fine last night for a couple of hours of experimenting with secure messengers, then fully charged, then down to 2% by morning. I'll try uninstalling the messengers in case they are draining the battery - wait for an update.
I could not find a way of disabling the clock on the sleeping screen. It disappears after a while, but the screen power consumption is suspect.
Well, this is the first alpha release, the things with power consumption might improve soon.
----------------
Update: I found a way to disable the clock on the sleep screen and the battery life increased to 23 hours, mobile network 1% (still the flight mode is on), phone idle 1%.
The method to disable the display was to press the power button while the notification panel is open...- perhaps another bug.
porcino said:
Well, this is the first alpha release, the things with power consumption might improve soon.
Click to expand...
Click to collapse
The always on display will be turned off in the next build, this will improve the power consumption a lot.
You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .
html6405 said:
You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .
Click to expand...
Click to collapse
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.
porcino said:
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.
Click to expand...
Click to collapse
Theoretically it should be enabled by default (what I will change in the next build for sure), but anyway, it's good if you can turn it off yet.
Great news, another person confirmed with a video that GPS is working ,
so I will add it to the working list.
Nice to see, that this worked out nearly blindly, because I have no testing opportunities...
With AOD button on then off the battery life is estimated as "more than 2 days left" (flight mode, idle). Let's wait for a little longer...
-------------------
Update: after 11h it predicts "5 days left" and counting! Very good! The graph shows slightly increased power consumption in the first hour, and then it goes almost horizontal. I think it will be more than 5 days at idle, perhaps twice as many.
-------------------
Further update: after 1 day 5 hours it says 9 days left. The way the graph in Battery Usage page goes makes me think that it will last about 20 days if left idle. I don't know what caused the quick discharge in the first hour; after that the graph is a straight line pointing beyond 20 days mark...
-------------------
Yet another update: 28 days predicted after 23 hours of idling. Very good! This is with all wireless interfaces off, Always On Display off and NavBar off.
For reference - Note 4 with cdDroid 9 under similar conditions reports 45 days.
I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
-----------------
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
-----------------
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon
alexfire_s said:
I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
Click to expand...
Click to collapse
Simply remove the sdcard.
alexfire_s said:
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
Click to expand...
Click to collapse
You're right, this will come later from lineageos.
alexfire_s said:
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon
Click to expand...
Click to collapse
Ok, this will also be fixed from the linageos side.
html6405 said:
Simply remove the sdcard.
You're right, this will come later from lineageos.
Ok, this will also be fixed from the linageos side.
Click to expand...
Click to collapse
now I use the 7100 as the main device, I actively use it, I can quickly share bugs if I find them. is it possible to contact you directly without communicating on the formum? do you use a group of testers in telegram?