Database Info

[Q]Galaxy Tab 2 7.0 frozen every morning after charging/sleeping, help?

Hi All,
First - I'm new - but I did plenty of searching and found some similar problems, but nothing quite the same. Most are really old and this is with a newer Tab with ICS stock on it so most I felt didn't apply.
I just got a Galaxy Tab 2 7.0 a week ago. I'm very happy with it except for one constant annoyance. Every morning after charging all night I have to hard reset the tablet. When I press the wake button I get the splash screen, but it's very sluggish and never responds. Sometimes I can swipe it away but the desktop never comes up.
I believe it to be something I've installed but I need some help to figure out what because of the troubleshooting steps I've taken. Here's what I've tried so far:
Factory Reset - after doing this and charging overnight this did *NOT* happen. *This leads me to believe that it's an installed app and not a hardware or OS issue*
After Factory Reset I tried restoring my apps manually instead of automatically via my Google account. No difference.
I was selective about what I restored - didn't just get EVERYTHING. Still no difference.
I am charging using the supplied cable and charger that came with the tablet
Wifi is on and there is a 16GB MicroSD card in the device every night.
I tried using a different launcher (both nova and apex) thinking it might be something conflicting with Samsung's SecLauncher but no improvement.
Since the issue I have rooted the device, but this same problem was happening both before and after. I believe I have a rogue process either memory leaking or eating CPU cycles that prevents me from even waking the device fully - and so far I can't figure out what it is. I have three questions for the group:
A) Any other new GTab 2 7.0 users with the same issue?
B) Is there an app I can run that polls my CPU/memory and running app usages to a text file every few minutes so that I can reboot and see what was going on right before I rebooted?
C) Any other info I can provide to help figure out WTF is going on?
Device info:
My Installed Android Apps
Adobe Flash Player 11.1 (v11.1.115.7)
​
Amazon (v1.4.0)
​
Angry Birds (v1.1.0)
​
Apex Launcher (v1.1.0)
​
App List Backup (v1.0)
​
baconreader (v1.36)
​
Bank of America (v3.2.181)
​
Cisco WebEx Meetings (v1.1.0.34)
​
Concur (v8.3.1)
​
Dolphin Browser HD (v8.0.0)
​
Draw Free (v1.5.21)
​
Dropsync (v2.0.4)
​
English for Smart Keyboard PRO (v1.0)
​
ES File Explorer (v1.6.1.3)
​
Evernote (v3.6.2)
​
Google Reader (v1.1.1)
​
ING DIRECT (v3.0)
​
KeePassDroid (v1.9.9)
​
Khan Academy (v2.5)
​
Mint.com (v2.1.0)
​
Mizuu Lite (v1.7.9.3)
​
Mobile Mouse (v2.0.6)
​
MX Player (v1.6d Rev.1)
​
MyAppsList (v1.6)
​
MyFitnessPal (v2.2.012)
​
NZBAir (v5.0.7)
​
Schwab (v2.1.0.1)
​
Screensaver (v1.1.3)
​
Skype (v2.8.0.920)
​
Smart Keyboard Pro (v4.6.1)
​
TED (v1.0.6)
​
Titanium Backup (v5.0.0)
​
Titanium Backup PRO (v1.2.1)
​
Twitter (v3.2.1)
​
UNO (v3.6.3)
​
Vanguard (v2.2)
​
Viewer for Khan Academy (v1.0.4)
​
Voodoo OTA RootKeeper (v1.2)
​
WDlxTV MediaPlayers Remote (v0.5.7)
​
Where's My Water? (v1.5.1)
​
Device Summary
Device: samsung GT-P3113
Android Version: 4.0.3
Build: IML74K.P3113UEALCB
Applications Installed: 40​

I just got my tablet today, so I can't really say if I will or won't experience this, but maybe you can try killing processes before you go to sleep, or selectively killing things to see if the problem is fixed. It will take time, but sometimes troubleshooting is simply a pain in the ass.

After the tab charges the charger needs to be removed....Or you would have to reset.....
On another note this tab is it resets when it gets a few degrees over running temp
p-3113 Puff, Puff, Puff,...... just sende'n smoke signals

hi, well there is something I can't understand, why didn't you return it after one week, you should have consider to take it to Samsung before rooting it.
there is plenty of applications who can provide a complete report about your processes, just type cpu diagnostic or process log in Google play.
and I think you can unroot it, then let the people who are already paid by your warranty do their job.
If I helped you, please press the thanks button ;-)

sos_sifou said:
hi, well there is something I can't understand, why didn't you return it after one week, you should have consider to take it to Samsung before rooting it.
there is plenty of applications who can provide a complete report about your processes, just type cpu diagnostic or process log in Google play.
and I think you can unroot it, then let the people who are already paid by your warranty do their job.
Click to expand...
Click to collapse
I don't believe it's an issue with the hardware or OS - I think it's something I've installed. I don't need to return something that's not defective because when I factory reset it it doesn't do this.
I'll try those searches you suggested.

I have seen this happen to my Galaxy Tab 2 (7) every once in a while. What I have noticed using the app "Watchdog" is that there is a system process (I am at work so cannot access/remember it) that every once in a while chews up 40-60% of the processors juice(Could be a TouchWiz process... i wouldn't know) ... This thing should fly once we have it rooted and once we have our devs clean it up and get some cleaner roms out
Hang in there mate... Good times are about to come

Totally - waiting for some CM9 on this.
Yenupuri said:
I have seen this happen to my Galaxy Tab 2 (7) every once in a while. What I have noticed using the app "Watchdog" is that there is a system process (I am at work so cannot access/remember it) that every once in a while chews up 40-60% of the processors juice(Could be a TouchWiz process... i wouldn't know) ... This thing should fly once we have it rooted and once we have our devs clean it up and get some cleaner roms out
Hang in there mate... Good times are about to come
Click to expand...
Click to collapse

sickysticky said:
After the tab charges the charger needs to be removed....Or you would have to reset.....
On another note this tab is it resets when it gets a few degrees over running temp
p-3113 Puff, Puff, Puff,...... just sende'n smoke signals
Click to expand...
Click to collapse
This is bull. I'm supposed to babysit my tab and unplug it when it's full, or it will freeze and reboot? That's ridiculous.

jimmy0x52 said:
Totally - waiting for some CM9 on this.
Click to expand...
Click to collapse
And that will happen only after we get our own sub-forum [ If someone hasnt done it yet, this is where we ask for it http://forum.xda-developers.com/showthread.php?t=1416406 ]

jimmy0x52 said:
This is bull. I'm supposed to babysit my tab and unplug it when it's full, or it will freeze and reboot? That's ridiculous.
Click to expand...
Click to collapse
I had my tablet plugged in overnight and when I woke up, I didn't get the freezing issue, so I think its just the OP and not necessarily a wide spread problem.

I've been having seemingly random freezes and about once every two or so days. It's kind of annoying--at first I thought the battery was dead, but it seems it's a common thing. Might head back to Costco to swap for a different one.

xreflection said:
I had my tablet plugged in overnight and when I woke up, I didn't get the freezing issue, so I think its just the OP and not necessarily a wide spread problem.
Click to expand...
Click to collapse
I purchased this as my second tablet, first being a Kindle Fire that I did everything to. But I love this thing!! I have not rooted yet, waiting for CM9... I always have the SOD after charging or not using the Tab for a long period of time; this is my fault for not conserving battery and just turning it off. BUT! SOD's are a pretty much a grantee that I have noticed with ICS tablet platforms that I have experienced so far. WHY? I do not know. I have also noticed that after playing any games for a lengthy time, they suddenly go into a glitching mode, as if the processors are just worn out.
Those are just a couple of things that I have noticed. Let me know any suggestions.

Tweaks that might be helpful
JimmyO:
Why not go back to stock, with factory reset , and run your tab for a couple of days (and nights) to determine whether you have a base problem. If you do, take it back or contact manufacturer. If not, as you have already indicated. then the problem is, allmost without doubt, bad software. In that case you may need to just load no more than half a dozen "essential" apps, try them for several days; if problems then remove them one at a time until problem is solved. If no problem, repeat the process with another half dozen apps.
You have a wide diversity of apps, many of which may auto-refresh. I would suspect one of these is mis-behaving.
The following is a response from Michael S to a string of negative feedback comments on the SGT 2 7, recently published by an individual on Amazon.
Michael is obviously a very savy guy, as his comments provide numerous tweaks that every SGT 2 owner (and most ICS users) should be vividly aware of. This info may help you to solve your problem, and get the most out of your SGT 2 7".
Edited by the author on May 2, 2012 6:55:32 PM PDT
Michael S says:
Right now my Tab 2 stats show the device is going 2 days 14 hours on a battery charge with 43% left. I use the Tab a few hours a day web surfing, doing research, checking and responding to emails. There are a number of ways to save juice so I'll mention a few that I use; which some, all, or none, may be applicable to others' situations:
#1 - Go into "Settings", then "Wi-Fi". At the top right-hand side there is a icon of "3 bars and a small triangle" (basically an option button) click on it and and when the "Advance" box shows on the screen, click it. Then click on "Keep Wi-Fi on during sleep" then check "only when plugged in". This will turn off the Wi-Fi when in sleep mode & running on the batteries. I use a login pattern to unlock my Tab and every time I unlock the screen it states "establishing Wi-Fi connection" I'm using WEP2 encryption on my network and the Tab starts Wi-Fi within seconds of waking from sleep. If one wants their Tab running multiple apps and to always have the most up-to-date information "pushed" to the device even while sleeping and running in battery mode, then one has to trade battery life for always-on information. The Wi-Fi will be active in sleep mode when it is plugged in. If you Always want the Wi-Fi off when in sleep mode then select "Never" instead of "Only when plugged in".
#2 - I mostly use my Tab at home or at the office. I have both Wi-Fi network settings saved in the device, so I turned off "Network Notification" in the same area as # 1 above. This stops the Tab from periodically searching the Wi-Fi Network for "Open Networks". If I go out and want to connect to a Wi-fi hot spot, I simply turn this feature back on.
Note: When you are in "Settings" and "Wi-Fi" mode you will notice that periodically the device shows "Scanning". Because you are in Wi-Fi mode, it scans to refresh the wi-fi networks its found, to help you connect to them. It does not continue to scan the network after you leave Wi-Fi settings, unless "Network Notification" is turn on, although the scan intervals may be different between the two modes.
#3 - In "Settings" then " Location Services" make sure "Use GPS Satellites" is unchecked. This requires more battery and a clear view of the sky, and is really only useful outside.
Those 3 settings will make a difference in battery consumption, and will not affect most people's use of the Tablet, although others' actual mileage may vary
#4 - In addition, as I stated earlier, I mostly use my Tab 2 at work or home, so I always know where I am. Therefore, I also turn off "Use Wireless Networks" (Found in the "Location Service" section). This use Wi-Fi to help determine your location for Maps and such. If a App or Apps are running in the background and they have a location feature, this stop them from updating while the Tab is sitting idle, or your while your using other apps.
#5- Because I use my Tab mostly at work or home and I know where I am, I usually turn-off GPS. Click on the "Clock" icon at the lower right-hand side, and then uncheck "GPS". If I ever need it, I quickly turn it back on.
#6- In "Settings" "Account and Sync" I have "Auto Sync" turned off. I turn it on when it's plugged in and then have it Sync. Then I turn if off once its done charging and back on battery power. I usually sync only 1-2 per week, same as my Skyrocket.
#7- Next, in "Settings" then "Developer Options" (I don't run a bunch of Apps and don't use a lot of "Notifications") so I check the box "Do not Keep Activities" This means when I leave an App, ICS closes the app instead of letting it run in the background, possibly sucking more juice. I saved this one for last, as it impacts the tablet operation the most. If a person uses "Notifications" or likes to multitask with many apps running and want to quickly switch between them, then thus option is not useful. What it does do is free one up from going into "Task Manager" and closing down a bunch of Apps you thought you closed but were only minimized when you exit-ed the App.
#8- Lastly, Usually the biggest drain on the battery is the display. Currently under "Battery" in "Settings" the Display has consumed 65%, with the next closest item "Internet" at 19%, and "Android System" & "Android OS" at 5% each, with everything else at less than 5% combined. Unfortunately, I'm unable to recommend the "Auto-Display" mode, as for me, it makes the display too dark most of the time (click on the "Clock" icon and then check the "Auto" box to engage).
I keep the display setting at about 20-25% as I mostly use the tab 2 indoors. As mentioned above, others' actual mileage may vary with Auto-Display turned on. I use Auto-Display on my Skyrocket, as I use it equally indoors and outdoors. When indoors, I find Auto-Display too dark also, but I live with it because when using the Skyrocket outdoors I find the Auto-Display is a must to see the display in bright sunlight, and therefore watch the battery drain accordingly. To compensation for this, I replaced the stock battery (1,850 mAh) with an extended battery (2,250 mAh) for a 22% capacity increase. This is obviously not a option on the Tab 2.
Hope this is of help!! I know it was to me.
__________________
Cbill
Transformers (2), Xoom, Nook Color (MicroSD root), Galaxy 7+, Optimus V (root)

hi, i have had similar problems with my HTC One X, found the culprit was NZBAir, try uninstalling it.
jimmy0x52 said:
Hi All,
First - I'm new - but I did plenty of searching and found some similar problems, but nothing quite the same. Most are really old and this is with a newer Tab with ICS stock on it so most I felt didn't apply.
I just got a Galaxy Tab 2 7.0 a week ago. I'm very happy with it except for one constant annoyance. Every morning after charging all night I have to hard reset the tablet. When I press the wake button I get the splash screen, but it's very sluggish and never responds. Sometimes I can swipe it away but the desktop never comes up.
I believe it to be something I've installed but I need some help to figure out what because of the troubleshooting steps I've taken. Here's what I've tried so far:
Factory Reset - after doing this and charging overnight this did *NOT* happen. *This leads me to believe that it's an installed app and not a hardware or OS issue*
After Factory Reset I tried restoring my apps manually instead of automatically via my Google account. No difference.
I was selective about what I restored - didn't just get EVERYTHING. Still no difference.
I am charging using the supplied cable and charger that came with the tablet
Wifi is on and there is a 16GB MicroSD card in the device every night.
I tried using a different launcher (both nova and apex) thinking it might be something conflicting with Samsung's SecLauncher but no improvement.
Since the issue I have rooted the device, but this same problem was happening both before and after. I believe I have a rogue process either memory leaking or eating CPU cycles that prevents me from even waking the device fully - and so far I can't figure out what it is. I have three questions for the group:
A) Any other new GTab 2 7.0 users with the same issue?
B) Is there an app I can run that polls my CPU/memory and running app usages to a text file every few minutes so that I can reboot and see what was going on right before I rebooted?
C) Any other info I can provide to help figure out WTF is going on?
Device info:
My Installed Android Apps
Adobe Flash Player 11.1 (v11.1.115.7)
​
Amazon (v1.4.0)
​
Angry Birds (v1.1.0)
​
Apex Launcher (v1.1.0)
​
App List Backup (v1.0)
​
baconreader (v1.36)
​
Bank of America (v3.2.181)
​
Cisco WebEx Meetings (v1.1.0.34)
​
Concur (v8.3.1)
​
Dolphin Browser HD (v8.0.0)
​
Draw Free (v1.5.21)
​
Dropsync (v2.0.4)
​
English for Smart Keyboard PRO (v1.0)
​
ES File Explorer (v1.6.1.3)
​
Evernote (v3.6.2)
​
Google Reader (v1.1.1)
​
ING DIRECT (v3.0)
​
KeePassDroid (v1.9.9)
​
Khan Academy (v2.5)
​
Mint.com (v2.1.0)
​
Mizuu Lite (v1.7.9.3)
​
Mobile Mouse (v2.0.6)
​
MX Player (v1.6d Rev.1)
​
MyAppsList (v1.6)
​
MyFitnessPal (v2.2.012)
​
NZBAir (v5.0.7)
​
Schwab (v2.1.0.1)
​
Screensaver (v1.1.3)
​
Skype (v2.8.0.920)
​
Smart Keyboard Pro (v4.6.1)
​
TED (v1.0.6)
​
Titanium Backup (v5.0.0)
​
Titanium Backup PRO (v1.2.1)
​
Twitter (v3.2.1)
​
UNO (v3.6.3)
​
Vanguard (v2.2)
​
Viewer for Khan Academy (v1.0.4)
​
Voodoo OTA RootKeeper (v1.2)
​
WDlxTV MediaPlayers Remote (v0.5.7)
​
Where's My Water? (v1.5.1)
​
Device Summary
Device: samsung GT-P3113
Android Version: 4.0.3
Build: IML74K.P3113UEALCB
Applications Installed: 40​
Click to expand...
Click to collapse

jmgraham / cbill thanks for all the help I will try it out!
also - yay for our own forum!

[APP][ROOT][4.0+]Battery Charge Limit v1.1.1

Please read the following before installing the app:
This app requires a rooted mobile (Android 4.0 or later)
Before uninstalling the app, disable limit in the app (if forgotten, reboot after uninstalling)
Usage instructions and app details:
Enable limit in the app
Change the limit up to which it should charge (default: 80)
Check which control file suits best for your device, see Q/A section below for hints. In most cases, the pre-selected choice should be the best that's available for your device.
The app only gets kicked in while you connect a charger (or USB), and automatically closes shortly after unplugging charger (or USB) i.e it only runs in the background as long as it is plugged in, and won't affect your battery life.
If your device is not charging even after disabling the limit (which shouldn't happen, just in case), uninstall the app and reboot the device (The changes made by the app don't survive a reboot). Your device should charge normally then.
If the app says "your device is not yet supported"
There are various control files in different devices (due to OEMs), and toggling the values in them (0 and 1) makes it possible to enable and disable charging via software (might not be possible for every device), though the charging cable is still physically connected.
Since we cannot own every device, it is impossible for us to find every file. We can support a lot more devices with information provided by testing possible files on different devices by you, the people in the community.
Hence, for support to be provided to other devices, you need to do some detective work to find the files on the respective devices. Please refer to this file for control files of currently supported devices, so you can know where they are generally present: https://github.com/sriharshaarangi/BatteryChargeLimit/blob/master/app/src/main/res/raw/control_files.json
You can send us a pull request or open an issue on GitHub. If necessary, you can also post the name of the device and the file here.
FAQ
Q) Can you please add support for... (insert arbitrary device name here)?
A) Maybe, but we need your help. Bottom line, this app does nothing but modifying the content of a certain "control file", some more details are given above. If you find such a control file for your device, please let us know (ideally, open a GitHub issue here: https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and we will add support for your device.
Q) I think I observed a bug. Can you fix it?
A) We'll do our best, but we need your help: Please open an issue on GitHub (https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and provide as much information as possible about the problem.
In most cases, we need the "logcat" logs of your device to find out about the exact issue. In order to provide those, you could use aLogcat (https://play.google.com/store/apps/details?id=rs.pedjaapps.alogcatroot.app).
FOR CHARGING-RELATED ISSUES: Select the "Time" format in the preferences of aLogcat, so we can see precise timings, and filter for "(Charging|Power) State" with "Apply as regular expression" ticked.
FOR CRASHES: Please also select the "Time" format and provide unfiltered logcat data that includes the stack trace of the crash.
Q) Why do you want to limit charge to a lower capacity?
A) In short, to prolong battery life in long term usage. For more information, refer this : http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Q) How does this app work? Does it modify something in the ROM/Kernel to stop charging?
A) It writes "0" or "1" to a control file that represents some state of the power supply hardware, as simple as that. The file is normally read-only, so you need root to overwrite it.
The change might be automatically reversed by the OS if the power supply situation changes. Anyway, it should never survive a reboot of the device.
Q) I can select multiple more than one control file in the radio group. Which one should I use?
A) For most devices, battery_charging_enabled or store_mode are preferable. Try those first and see if it works. If you observe any bugs, try another file.
Q) I have a OnePlus device, and the app doesn't work correctly for me. What to do?
A) Check that the control file you selected is NOT battery_charging_enabled! Although it should be preferred in general, there are known issues for this file with OnePlus devices.
Q) I use the store_mode on a Samsung device. My device always stops charging at 70 % (or other specific percentage), no matter what limit I have set.
A) The store_mode implementation differs among the supported (Samsung) devices.
Normally, it freezes the level at the current percentage when store_mode is triggered until the cable is unplugged for some seconds. This is a normal condition due to Samsung's kernel implementation, it's not a bug of this app.
If this is a problem for you, try to switch to another control file (e.g. batt_slate_mode), if supported.
Q) How does the "automatic stats reset" work?
A) The automatic reset should perform a stats reset when your power supply is removed while the battery level is within the desired range. Everything else is wrong behavior.
Q) No matter if I the "automatic stats reset" is enabled or not, my phone is always resetting my battery statistics. Why?
A) Are you using a threshold above 90%? If yes, your ROM will most likely clear the stats when the power is removed. There is nothing we can do about that.
Downloads:
The app is available on Google Play Store
Alternate APK download links:
v1.1.1: https://www.androidfilehost.com/?fid=674106145207486851
v1.1.0: https://www.androidfilehost.com/?fid=817906626617956614
v1.0.4: https://www.androidfilehost.com/?fid=889764386195927297
v1.0.3: https://www.androidfilehost.com/?fid=745425885120755941
v1.0.2: https://www.androidfilehost.com/?fid=889764386195923345
v1.0.1: https://www.androidfilehost.com/?fid=889764386195919111
v1.0.0: https://www.androidfilehost.com/?fid=817550096634789023
v0.11.0: https://www.androidfilehost.com/?fid=961840155545580765
v0.10.0: https://www.androidfilehost.com/?fid=961840155545576298
v0.9.2: https://www.androidfilehost.com/?fid=457095661767160082
v0.8.2: https://www.androidfilehost.com/?fid=673368273298951679
Please uninstall versions < 0.8 before installing this!
Changelog:
1.1.1:
Fix charging status layout issues and misc UI fixes @xdnax
Added switch to disable toasts on service changes @xdnax
Added switch to show temperature in notification @xdnax
Ensuring write permissions on the charging control file @real_milux
Fixed notification sound on limit reach @sriharshaarangi
Fixed a bug causing crash
Added Russian translation
Updated Bengali, German and Brazilian Portuguese translations
Added control file for Amazon Tate (LineageOS 14.1)
1.1.0:
UI & icon redesign @xdnax
Custom control file data support @xdnax
Improved control file lists @real_milux
ICS (Android 4.0, API 14) compatibility @real_milux
Pixel/Pixel 2 support fixes @xdnax
Added control files for Pixel/Pixel 2, Xiaomi Redmi Note 2, Sony XPERIA Mini, Le 1s, Huawei P10 lite, HTC One, Motorola Defy+, Xiaomi Mi A1
Bengali translation @AdroitAdorKhan
Spanish translation @Joseahfer
Lots of bugfixes and minor improvements
1.0.4:
New "always write" setting for devices that modify their control files in a problematic way
Experimental support for Xiaomi MiPad 2, Nexus 5, Nexus 9, Galaxy Nexus (maguro) and Xiaomi Mi6
1.0.3:
Fixed service starting after boot when disabled
1.0.2:
Fixed ignoring "ACTION_POWER_CONNECTED" when service was disabled
Experimental support for Nexus 10, Nvidia Shield and Xiaomi Mi6
1.0.1:
Added preference to disable limit enforcement aka "state fixing"
Added expert preference to enable immediate reaction to power state events (be careful!)
1.0.0:
Tested Magisk 13.x support
Improved UI
Even higher service priority (against being killed by Android)
Online limit change support (limit changeable while service is active)
Settings with control file selection and temperature scale
Fahrenheit temperature info support
Greatly improved "state fixing" with exponentially increasing delay (hopefully fixing GitHub issue #15 aka "rapid cycling")
Greatly improved SU shell speed/performance
German translation
0.11.0:
Improved UI (Using NumberPickers, GitHub issue #13)
Show voltage and temperature in app and notification (GitHub issue #14)
0.10.0:
The recharge threshold can now be customized between 0 and the chosen charging limit
Sending a charging limit of 100 via (broadcast) intent will disable the service.
Sending values between 40 and 99 will enable and start the service if it was previously disabled.
0.9.2:
Fixed crash on some devices that are unrooted or unsupported
0.9.1:
Fixed widget not showing in some devices
0.9:
Added Widget to toggle service
Added scrollable view
0.8.2:
experimental Amazon Fire support
0.8.1:
Bugfixes
0.8:
State check after boot (starting monitoring service as necessary)
Bugfixes
0.7:
Experimental support for Huawei and Nexus 4 devices
Support for external control over charging limit
Bug fixes
0.5
Ability to select recharge limit (Range: 10%)
Automatic file selection
Added store_mode for Samsung devices
Added option to auto reset stats
(Huge code refactoring)
0.3
Updated to support 7.1.1
Auto-select the battery charging file for Samsung, Pixel and Nexus devices
Added clear battery stats button
Auto-whitelisting from Doze mode
XDA:DevDB Information
Battery Charge Limit, App for all devices (see above for details)
Contributors
harsha1397, real_milux
Source Code: https://github.com/sriharshaarangi/BatteryChargeLimit
Version Information
Status: Stable
Current Stable Version: 1.1.1
Stable Release Date: 2018-10-17
Current Beta Version: 1.0.4
Beta Release Date: 2017-09-04
Created 2017-02-15
Last Updated 2020-08-05

Todo:
- Check for charging on device boot
- Widget for quick toggle
- Widget to reset batterystats
- Limit reached alert
- Low battery alert - Needs a service running in the background
- UI overhaul
- on/off switch to enable/disable charging

I can't believe it. You can't imagine how long I was looking for such an app .
Will try it!

I remember this was a feature that some kernels had years ago, and I would limit the charge to 85%. On my laptop I can cap it to 60%, which is great because I leave the charger in often.
Anyway, thank you for making this app!

Freezy202 said:
I can't believe it. You can't imagine how long I was looking for such an app .
Will try it!
Click to expand...
Click to collapse
Ace42 said:
I remember this was a feature that some kernels had years ago, and I would limit the charge to 85%. On my laptop I can cap it to 60%, which is great because I leave the charger in often.
Anyway, thank you for making this app!
Click to expand...
Click to collapse
Did you get a chance to test it? Is it working as expected?

harsha1397 said:
Did you get a chance to test it? Is it working as expected?
Click to expand...
Click to collapse
Unfortunately it does not work as it should :/. It doesn't really limit. Even when I unplug the notification doesn't go away as you mentioned.
I have a HTC One M8, android 6.

Freezy202 said:
Unfortunately it does not work as it should :/. It doesn't really limit. Even when I unplug the notification doesn't go away as you mentioned.
I have a HTC One M8, android 6.
Click to expand...
Click to collapse
Does the battery percentage continue to rise beyond the limit? Regarding notification, it doesn't immediately go away after unplugging. It goes away after the percentage drops 3% below the limit. It is to ensure that the phone again charges to the limit if the phone is still plugged in. If it is not plugged in, then notification closes.

very good idea, thanks for app, was looking for app like this for a long time will report in half hour if app works

thanks!I always was searching such an app cause:
1)I read if u charge your battery till 80% it will last more time..
2)At the end of the day,I always have 40% battery left and I cant trust my phone for the next day without charge.
Thanks again It works on my moto x play!It stopped at 79% but its ok not such a big deal!

ok, so it worked, but first time, when i unpluged and pluged app didn't noticed pluging and continued charging. after that i tried several times and it worked again. so there should be somewhere bug in monitoring pluging charger sometimes is left unnoticed.
Sent from my ONE A2005 using Tapatalk

harsha1397 said:
Did you get a chance to test it? Is it working as expected?
Click to expand...
Click to collapse
Seems to work on my LeEco Pro 3. Charging icon switched to normal battery at 80%.

This is what I have been looking for!
Thank you for the app!
I tried it and its stop charging after 95% ?
Im on xperia z5 Nougat.
But the notification doesnt go away when I unplug the charger's cable from the phone.
Turning off the app but did make the notification disappear.
Another question.
Does it really stop the charger from giving electricity to our phone?
Or does it only change the charging status?
Im scared that the app tells that it stopped charging, but the electricity is still going on.
Gesendet von meinem E6653 mit Tapatalk

Can somebody explain to me, why someone would want to limit the charging current?

chitose_ndy said:
This is what I have been looking for!
Thank you for the app!
I tried it and its stop charging after 95%
Im on xperia z5 Nougat.
But the notification doesnt go away when I unplug the charger's cable from the phone.
Turning off the app but did make the notification disappear.
Another question.
Does it really stop the charger from giving electricity to our phone?
Or does it only change the charging status?
Im scared that the app tells that it stopped charging, but the electricity is still going on.
Gesendet von meinem E6653 mit Tapatalk
Click to expand...
Click to collapse
1. Regarding notification, (I have updated the OP as well):
The app only gets kicked in while you connect a charger (or USB), and automatically closes shortly after unplugging (not immediate, it closes after percentage drops more than 3% below the limit because the app doesn't know whether the cable is physically connected or not, since we disable charging at the limit. So, after it drops below 3% and (a)the charger is still connected, it charges again to the limit, and (b)if it is disconnected, then the notification closes) .
So, it is not a bug.
2. Does it really stop the charger from giving electricity to our phone?
It actually stops charging at the limit. It is in the same way any phone automatically stops charging when the battery reaches 100% capacity.

Freddy1X said:
Can somebody explain to me, why someone would want to limit the charging current?
Click to expand...
Click to collapse
tl;dr : To prolong battery life in long term
For more information: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

harsha1397 said:
Does the battery percentage continue to rise beyond the limit? Regarding notification, it doesn't immediately go away after unplugging. It goes away after the percentage drops 3% below the limit. It is to ensure that the phone again charges to the limit if the phone is still plugged in. If it is not plugged in, then notification closes.
Click to expand...
Click to collapse
Exactly. It continues to charge.

Freezy202 said:
Exactly. It continues to charge.
Click to expand...
Click to collapse
Weird. Seems to work on other devices.

harsha1397 said:
Weird. Seems to work on other devices.
Click to expand...
Click to collapse
Is it possible that some kernels aren't compatible with this, or even certain SoCs? I have a Kindle Fire with a mediatek, so I'll test the app on there later.

harsha1397 said:
Weird. Seems to work on other devices.
Click to expand...
Click to collapse
Maybe I'll try another kernel. Anyway I wanted to change my rom . Actually it's always the other way around. Other people have Bugs except me, this time I have no luck haha.

Ace42 said:
Is it possible that some kernels aren't compatible with this, or even certain SoCs? I have a Kindle Fire with a mediatek, so I'll test the app on there later.
Click to expand...
Click to collapse
I don't know the reason(I don't think this is kernel dependent), but this file is the key: /sys/class/power_supply/battery/charging_enabled
It should be 1 by default. And when it reaches the limit, the value is made 0 by the app.

Android 10 v11.0.7 Bugs, Enhancements, Battery Life etc.

Android 10
Release date: Tuesday, Jun 23th, 2020
Build Version: QKQ1.191002.002.V11.0.7.0.QDLMIXM
Kernel Version: 3.18.124-perf-g6d04eb4a
#1 Wed Jun 17 09:54:01 WIB 2020
Bootloader Version: N/A
Baseband Version: 953_GEN_PACK-1.202044.1.240106.1,953_GEN_PACK-1.202044.1.240106.1
Android Security Patch Version: June 2020
Please report bugs via Xiaomi's Feedback app.
How to Generate Bug Reports
Bugs:
1- N/A
2- 4G Speeds seems low. Source
3- Camera JPEG quality is lowered, file size of photos is lowered, and the overall quality of the pictures is lower than previous update (old update picture file size 8MB, now 3MB) Source
4- Video recording has a bug while focusing and sometimes misses the subject (not actually blurry, but soft focussed and not sharp), and while tapping to focus, it still misses (test it on your own computer screen).Source
5- Customize your pixel message is still present and cannot be dismissed. Source
6- Sim card menu is still not adapted to the dark mode, it persists to be white while global theme is dark. Source 1 - Source 2
7- Direct Share is still broken. Source
8- Some users device starts and after 2 min it restart automatically! Source
Missing features:
N/A
Enhancements:
1- Third Stable Android 10 release.
2- It comes with June 2020 Android Security patch.
3- New! MiCommunity app now being forced as system. Source
4- Fixed! Microphone bug is now fixed. Tested in Facebook Messenger, Facebook, Instagram, Whatsapp. Source
5- Fixed! 5Ghz band in Wi-Fi tether is now working. Source
6- This update cleared about 2GB of storage space for some users. Source
7- New! General audio quality was improved, by lowering the overall volume of media (Xiaomi's side) while keeping it louder for ringtones. Good job! Audio lacks bass a litte, but it's crispier now. Source
8- Lock and unlock sounds work as intended. Source
Battery Life:
N/A
Notes:
- This is the third stable Android 10 update for Xiaomi Mi A2 Lite.
- There was May 2020 Security patch in the second stable Android 10 update.
- Arrived 28 days later after v11.0.5
- It weights 22.9 MB for OTA.
- Xiaomi didnt updated the modem in this build so dont expect something new.
3DMark Test Results: (v2.0.4661)
Slingshot Extreme OpenGL ES 3.1 - Overall score N/A
Slingshot Extreme Vulkan - Overall score N/A
It will be beneficial to restart your phone after the first installation.
Older builds:
1 - Android 10 v11.0.4
2- Android 10 v11.0.5
I will constantly update this thread.

Aadil Gillani said:
Successfully Updated to June Patch.
SS attached below
Click to expand...
Click to collapse
Update OP for bugreports from last version to check what's fixed, what's new, what's still broken. Will update my review as soon as I dig deeper into the new update.
Let's begin:
Update was about 22MB going from .05 to .7 and it took just a few minutes to install. (wasn't this supposed to be 06 or 6?)
On a first look there is a new MiCommunity app now being forced as system, it's like an app for their forum and being promoted as "must have", I don't think so, but that's that.
Testing download speed on a 150mbps uplink b/g/n router goes up to 30mbps but there is a QOS system managing the wi-fi, with QOS disabled we got a speed of 60mbps.
Testing download speed on moderate 4G signal is simply horrendous clocking at 2mbps and with full signal clocking at 4mbps (this is simply a joke) so the 4G bug still persists.
Microphone bug is now fixed, tested in Facebook Messenger, Facebook, Instagram, Whatsapp. But while in facebook messenger volume seems to be loud, in Facebook, Instagram, Whatsapp volume is lower, but audio is ok.
Video recording has a bug while focusing and sometimes misses the subject (not actually blurry, but soft focussed and not sharp), and while tapping to focus, it still misses (test it on your own computer screen). Camera seems to work ok as functionality, but JPEG quality is lowered, file size of photos is lowered, and the overall quality of the pictures is lower than previous update (old update picture file size 8MB, now 3MB). Picture attached, you can see some artifacting in the natural blur area (this is not portrait photo) and it only gets worse in low light.
Customize your pixel message is still present and cannot be dismissed.
5Ghz band in Wi-Fi tether is now working.
Sim card menu is still not adapted to the dark mode, it persists to be white while global theme is dark.
This update cleared about 2GB of storage space (at least for me).
Google Play security is still 1 May 2020.
Nothing new to report setting wise, no new features, nothing broken.
Overall performance testing each setting in the menu was very good, no slowdowns.
Moving to general system and 3rd party experience:
3rd party audio effects now work without process crash (Noozxoide EIZO-Rewire E).
Playback of SACD DSF, FLAC, and MP3 is flawless.
OK Google now works ok.
General audio quality was improved, by lowering the overall volume of media (Xiaomi's side) while keeping it louder for ringtones. Good job! Audio lacks bass a litte, but it's crispier now.
Gaming experience with resource heavy games is fine and has no problems: tested with Asphalt 9, Black Desert Mobile, Honkai Impact and PPSSPP emulation (framedrop to 24 from 30 - PSP games are locked at 30fps - is because the screenshot animation).
Multitasking while resource heavy gaming was done without system reloading any of those games, could switch to any of those games on the fly without problems.
Youtube playback for 1080p60fps didn't drop any frames (1 frames dropped when switching to 1080p60).
No other 3rd party, play store app encountered any problems.
During heavy testing CPU temperature didn't go over 42C and no thermal throttling slowed down the device.
With 96 applications loaded into the memory device started to work a little slower, but keeping in mind that 96 apps were loaded I believe that's just fine.
Now locking/unlocking, reboot and USB MTP testing:
Unlocking the device via fingerprint is smooth and fast with no apps started.
Unlocking the device via fingerprint with a lot of apps in the memory is still fast and smooth.
Unlocking the device via swipe is still weird but works better than the last update, so lockscreen unlock was not fully fixed, still fails sometimes to pop up pin code.
Lock and unlock sounds work as intended.
Notifications can ring over playing music without stuttering.
Charging sound work as intended, but it's a little quiet.
MTP is still inconsistent in transferring file batches. Files do not appear in Google or 3rd party apps after being copied to the card. Reboot makes the files appear, bug is still present.
Reboot time is ok.
Rapid charging is working even faster.
That's it, the phone is usable.
For the battery test, I need at least 2 cycles to test the actual battery life.
Cycle one - stand-by time, only 23minutes of SOT and only using the phone to auto-update apps (4g, wi-fi b/g/n, bluetooth always online) gives a stand-by time of ~5 days which is as expected.
Cycle two - I got about aprox 6 hours of battery time with screen on and heavy use with (wi-fi on, 4f and bluetooth). What was heavy use? I made sure the screen won't turn off for more than 10 minutes, gaming on resource heavy games, maybe 1-2hrs of screen casting Youtube and overall maybe 15 minutes of phone calls.
Conclusion: while stand-by times stayed the same over the updates, since A10 was released the SOT decreased. Also the phone was almost at thermal throttle limit after ~1hour. That's not quite optimized yet and while in normal day to day use I won't use my phone for 6 hours straight, that's not a good SOT for 4kmAh battery.
-----------------Later edit
It seems like glance notification screen is gone, notifications now wake up the phone in lock screen. The old feature was better because you couldn't interact with the screen when notified, so it wouldn't pose a threat in the pocket. Now you can interact with the screen.
Glance screen is back after reboot, bug didn't appear in >1 week of use.

A full charge takes 8 hours with original adapter. So charging speed is ****ed.. If anyone finds a solution,do share.

Sinister Sakib said:
A full charge takes 8 hours with original adapter. So charging speed is ****ed.. If anyone finds a solution,do share.
Click to expand...
Click to collapse
Never had this problem, but I would try a complete wipe and then reinstall the stock rom.

I can't see this update

How can they force a buggy app like Mi Community on every phone ??? The app sometimes crashes if I navigate too fast through it. Also, it asks for call logs in order to log in. I just don't trust xiaomi with these moves.
Edit: Also, Mi Community app notifications can't be disabled anymore from the notification channels.

Customize your pixel message is still present and cannot be dismissed.
OMG. Xiaomi please fix this!

sulczan said:
I can't see this update
Click to expand...
Click to collapse
me too.
Anyone have the 11.0.7 default recovery flashable zip?

Sinister Sakib said:
A full charge takes 8 hours with original adapter. So charging speed is ****ed.. If anyone finds a solution,do share.
Click to expand...
Click to collapse
Do double check cable and port support fast charging.

A data wipe solved the case.

In my experience battery life is worse.
+10% overnight decrease without doing nothing.

The first thing I noticed with 11.0.7 is that now when the phone is restarted, it doesn't pass the lock screen automatically.
In the last 11.0.x updates, when I restarted my phone, it started with the home screen instead of the lock screen while I had fingerprint activated.
+1 for 11.0.7

Still usable...
I've paused this update for several days because I did not want to ruin my Pie 9 phone, but one morning when I was using the phone as hotspot and the update was downloaded without my consent, so I rebooted and installed it.
Verdict after factory reset:
Android 10 gestures are a bit to much for my 3gb ram version. Pie 9 gestures work smooth like before. Forcing dark mode when in battery saving mode is hilarious when you have an IPS panel, because it uses MORE battery. Charging, battery drain and connection are about the same like on pie. Best thing is that the steps to adapt the volume on Bluetooth speakers are now far smaller the on pie 9, where it was either to loud or to silent.

ardanai said:
The first thing I noticed with 11.0.7 is that now when the phone is restarted, it doesn't pass the lock screen automatically.
In the last 11.0.x updates, when I restarted my phone, it started with the home screen instead of the lock screen while I had fingerprint activated.
+1 for 11.0.7
Click to expand...
Click to collapse
Direct share is now working and brings the list of your recent contacts.
+1 for 11.0.7

Afet some days the lag reappear so Xiaomi didn't fix this and you need to restart the phone to work properly and after 4-5 days do the same is not very big deal but is annoying.

Bluetooth only hast SBC Codec. You can View curent Codec in Developer settings while playing. And after Bluetooth Connect to my Car the Bluetooth Volume ist verry Low.

ardanai said:
Direct share is now working and brings the list of your recent contacts.
+1 for 11.0.7
Click to expand...
Click to collapse
Can you share ss as for me direct Share insnt working

Eistee82 said:
Bluetooth only hast SBC Codec. You can View curent Codec in Developer settings while playing. And after Bluetooth Connect to my Car the Bluetooth Volume ist verry Low.
Click to expand...
Click to collapse
bluetooth with my Uconnect Jeep Compass doesn't works!!!

Good news is that WiFi hotspot works for me now. It never worked on pie. I have no idea if it was working on older Q releases.
Bad news is that with WiFi or Bluetooth hotspot I cannot connect to adb. I'm fairly sure it worked in pie. Looks like I gotta take a wifi router or USB cable for dev on the road now.

Background apps don't stay in memory
I've already done a factory reset, disabled Adaptive Battery to no avail.
I've seen this problem posted in different places, even after the latest update v11.0.7
The following where posted after 2020-06-23
ahmed elmansy said:
Please last question pleas...My phone has a problem after updating Android 10....The problem is،،memory leak in android 10....My phone type is..xiaomi mi a2 lite....It is part of the Android one project...It becomes difficult to open applications and it becomes irritating
Click to expand...
Click to collapse
a1291762 said:
That's not a question.
Apps not staying in memory is a known issue with android 10. I reboot weekly as a workaround.
Click to expand...
Click to collapse
And in the Mi Community forum:
In this post: thread-3179276-1-0.html (I can't put the full link since I'm new)
[Discussion] mi a2 lite android 10 bug
2020-07-01 02:44:35
Background apps refresh very often. Same here?
Click to expand...
Click to collapse
And in this post by barysekk418 thread-3171282-1-0.html (I can't put the full link since I'm new)
[Other] Xiaomi Mi A2 Lite - Device After Update
2020-06-27 10:09:00
"... I also feel a big problem when switching from the facebook application to the Messenger application. In FACEBOOK application, look at user profile and then click on the icon message, and switch from FACEBOOK application to MESSENGER application. The transition from one application to another is time consuming. The device freezes for a while (sometimes I have to restart the application, sometimes I don't have to and the application is alone manages to load), then restores and the contents of the the second application is loaded, which again takes a long time and then everything is displayed. ..."
Click to expand...
Click to collapse

Customize background process limit

My phone is running lineageos 16.0. Sometimes the touch screen will freeze randomly for a few seconds and it can become extremely annoying. I have found that limiting background processes to 4 in developer options or having the phone being charged removes the issue entirely. Would there be any way I could create a custom background process limit to automatically turn on or off when the phone is disconnected/connected to power?

Set option Limit background process to "No background process" and your phone will work fine, with no hanging problems or no slowness.
Doing so forces Android to stop each process ( read: app ) as soon as it is empty ( that is
when you’re not using the app or any of its services ).
Note that this will also help in saving your battery life, in most cases.

jwoegerbauer said:
Set option Limit background process to "No background process" and your phone will work fine, with no hanging problems or no slowness.
Doing so forces Android to stop each process ( read: app ) as soon as it is empty ( that is
when you’re not using the app or any of its services ).
Note that this will also help in saving your battery life, in most cases.
Click to expand...
Click to collapse
Yes, I am aware of this, though I only want it enabled when my phone is not being charged. Would there be a way to automate this?

All can get automated.
If phone's Android is rooted then you for example can use Tasker app ( or an init.d if Android supports init.d ) to reach your goal.
Road map:
1. Get phone's battery status
2. Depending on this configure Android's LMK
3. Reboot so new LMK's settings get activated

Hello, i know about this command
Code:
service call activity 51 i32 x
Where x is the number of background processes you want.
If the API changes in the future, it's easy to look it up again. http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.4.4_r1/android/app/IActivityManager.java?av=f
Look for the line with SET_PROCESS_LIMIT_TRANSACTION
Then just extrapolate that info to http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/DESIRED_ANDROID_VERSION/android/app/IActivityManager.java?av=f
Replacing DESIRED_ANDROID_VERSION with the version you're interested in.
But now these links broken, Where can i found "x" number in newer android?
Thanks

[ROM][UNOFFICIAL][12L][N7100][Samsung Galaxy Note 2][LineageOS 19.1][BETA]

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?