Would you say that the LG G6 is "fast" in day-to-day use? A higher rating indicates that you think the LG G6 exhibits fantastic performance. Like, is it as fast as your tears when you watch The Titanic?
Then, drop a comment if you have anything to add!
Top notch...but still it could have SD835....
Mines fast, 2 things that really make people feel they have a slow phone.. 1. Always closing background apps. This truly shows the phone down cause the phone has to reopen every app every time they use it if they "close all" like most do to conserve battery life. In reality leaving them open speeds up the phone and saves battery life since phone doesn't have to speed the extra power to relaunch the app it just pulls it back up from being "minimised" 2. People that use stock launchers and don't change the animation scale in dev options. I'd like to actually add a 3rd. Connection speed truly does slow the phone down too. Lot of people confuse ann app not fully loading or a browser being slow. With that being the phones fault when I turn 1/2 the time it's from slow connection speeds.
It's fast but not all that smooth...
Is fast like my old oneplus 3t
After Android Pie update the mobile lags a bit.
Try these commands, after these commands my phone became too smooth
Code:
adb shell settings delete global device_idle_constants
Code:
adb shell dumpsys deviceidle enable
Code:
adb shell dumpsys deviceidle force-idle
Code:
adb shell settings put global device_idle_constants inactive_to=30000,sensing_to=0,locating_to=0,location_accuracy=20.0,motion_inactive_to=0,idle_after_inactive_to=0,idle_pending_to=300000,max_idle_pending_to=600000,idle_pending_factor=2.0,idle_to=3600000,max_idle_to=21600000,idle_factor=2.0,min_time_to_alarm=3600000,max_temp_app_whitelist_duration=300000,mms_temp_app_whitelist_duration=60000,sms_temp_app_whitelist_duration=20000
Related
Hey guys,
I need help. My battery life is absolutely shocking. And yes, I have adequately calibrated my battery (which IMO shouldn't make that much of a difference).
Please share your tips for maximizing battery here!
Basically, when I call someone, I lose like 10% in about 10 minutes. Not good. And I like to be on the phone for hours on end.
Please help, and thus also help others!
P.S: I am using Wolfbreaks 2.3.3 ROM.
P.P.S: I have tried:
CPU Profiles
Setting Max Clock Speed to 576MHz.
Governor is interactive.
2G only (never 3G) on a 900MHz network.
Manually killed some tasks which may consume battery (rarely though, makes no observable difference).
I never connect wireless, and (background) data is disabled.
Brightness always at an all-time low.
Added some build.prop modifications (setting the WiFi scan interval to 5 minutes [300 seconds], just in case I enable WiFi).
No Bravia Engine/xLoud enabled (not even included in the ROM).
Undervolt kernel module (my phone never crashes).
NOTE: Aeroplane mode is not an option unfortunately I need my phone on an connected 24/7.
Other things to note about my use:
I don't ever listen to music.
I never browse the internet whilst connected to 3G.
I rarely connect to my WAP.
I rarely use the camera.
I rarely watch videos.
I occasionally (sometimes) browse the Gallery ( <100 pictures ).
Cheers guys!
Even I have recently installed wolf's rom and I find that the battery is performing lesser than before...
Did your battery encounter overheating issue before? I'm not an expert therefore I'm just capable to give advice As for me battery draining quite fast too when on call but on other time its just fine
I have a Star A3 running 2.3.4
The question is more of a general question to the android platform, I don't suspect the hardware matters.
I am running Ttorrent Pro on the phone, and the speeds are less than impressive (everyone else says the same thing) I am on a very fast connection, using speed guide I literally max out the speedtest servers in my local area (20Mb up/down which is the max they let you go to, I would get 100/100 if my speedtest server would allow it) and I have a port forwarded correctly.
but anyways, what I have noticed is, when wake the phone, and open the torrent application the speeds are down to around 3Kbps if I leave it open the speeds immediately start ramping up to 200-300Kbps if I keep it awake.
So this makes me think, when the phone is sleeping a lot of the connections are being closed, or when the phone is asleep it won't try and open new connections to new peers (and the current peer list may go stale while its asleep)
this is with all torrents, now the exact same torrent on another PC with a DSL connection (3Mb down 300Kb up) is downloading faster than the phone.
Are there any developers out there than can explain what processes are going to sleep that may be useful to keep awake for downloading, and also what are the tcp limits on the phone, ie. max open connections, max half open etc?
When the phone clocks down its CPU, of course it'll make your apps run slower. Is that so strange? Leaving it connected to the power seems to keep the CPU at high speed on my devices at least, but I guess that may vary from phone to phone.
A torrent client have a quite intelligent algorithm choosing the numbers of peers it connects to depending on several parameter such as effective bandwidth and so, and if your device lower its CPU frequency, the bandwidth will suffer.
There's also another possibility. Running the task in the background, i.e. without its main window visible, and Android may kill the app. More than 15 hidden apps (e.g. background running), and Android begin to kill the oldest. This is quite invisible to you, because Android must restart them as well. The problem with a torrent app, is that setting up the torrent, connecting to pears etc takes a while, and if the app gets killed and restarted once up running, you'll never achieve great speed. If this is the case, leaving the main activity visible prevents Android killing/restarting it.
I brought my old LG-G3 back to life to use strictly as a media player with a prop edit to disable the cellular radio (I was using my old Samsung GS3, but it finally died after all these years!). Running LOS 09/01 nightly w/xdabbeb's 35b bootstack and everything is buttery smooth. Performance is really top notch for this device running LOS 14.1 - no complaints here. If anyone wants to use their device as a mini tablet (wifi only/disable radio) this is what you do via a root adb shell on a pc:
Code:
adb shell
Code:
su
Code:
setprop persist.radio.noril 1
That command removes the cellular radio portion from the OS. There will no longer be a signal bar in the status bar. Wifi will still work so the device is basically now a mini tablet. You will gain a major increase in battery life. A couple of things to note:
-Root required. Flash Lineage's SU addon (I couldn't get Magisk to work, and I no longer use SuperSU so I can't comment on that). Enable root for apps & adb in Developer Options.
-The radio is disabled, but the OS is still built as a phone. In the Battery section it'll still show "phone idle" as draining battery. Ignore it, it's a false reading.
-On this device there is an odd side effect where the GPS becomes disabled too. Apparently LG ties some GPS hardware to the device's RIL. This doesn't happen on other phones for future reference. It doesn't bother me, I would have turned location off anyways - after all, I'm just listening to music from my 128gb microSD. The GPS will still be available in the system, but it simply will not find any satellites. Just turn off the GPS so it's not searching and draining your battery.
-You can also do it from a terminal app or Lineage's built in terminal (you have to enable the terminal in Developer Options).
-To revert and restore the radio, do the same thing, but replace the "1" with a "0" in the command.
-The radio disable will remain when dirty flashing an update (no need to run the command again).
-If you play any Kanye West, your phone will make a vomit sound and immediately self destruct....you've been warned!
-Revert Command:
Code:
setprop persist.radio.noril 0
Just curious - how is this better than disabling mobile networks and leaving the phone in airplane mode?
syborg said:
Just curious - how is this better than disabling mobile networks and leaving the phone in airplane mode?
Click to expand...
Click to collapse
Disabling mobile networks still causes the system to ping and look for telephony related services (aka battery consumption). Airplane mode would be a better comparison, though the data signal is still "alive" on the system. Doing this removes your RIL completely. So services that would normally ping won't because there is no RIL/data and those services will only begin pinging when on Wifi (like a data only tablet). This method is the more battery friendly than airplane mode.
annoyingduck said:
I brought my old LG-G3 back to life to use strictly as a media player with a prop edit to disable the cellular radio (I was using my old Samsung GS3, but it finally died after all these years!). Running LOS 09/01 nightly w/xdabbeb's 35b bootstack and everything is buttery smooth. Performance is really top notch for this device running LOS 14.1 - no complaints here. If anyone wants to use their device as a mini tablet (wifi only/disable radio) this is what you do via a root adb shell on a pc:
Code:
adb shell
Code:
su
Code:
setprop persist.radio.noril 1
That command removes the cellular radio portion from the OS. There will no longer be a signal bar in the status bar. Wifi will still work so the device is basically now a mini tablet. You will gain a major increase in battery life. A couple of things to note:
-Root required. Flash Lineage's SU addon (I couldn't get Magisk to work, and I no longer use SuperSU so I can't comment on that). Enable root for apps & adb in Developer Options.
-The radio is disabled, but the OS is still built as a phone. In the Battery section it'll still show "phone idle" as draining battery. Ignore it, it's a false reading.
-On this device there is an odd side effect where the GPS becomes disabled too. Apparently LG ties some GPS hardware to the device's RIL. This doesn't happen on other phones for future reference. It doesn't bother me, I would have turned location off anyways - after all, I'm just listening to music from my 128gb microSD. The GPS will still be available in the system, but it simply will not find any satellites. Just turn off the GPS so it's not searching and draining your battery.
-You can also do it from a terminal app or Lineage's built in terminal (you have to enable the terminal in Developer Options).
-To revert and restore the radio, do the same thing, but replace the "1" with a "0" in the command.
-The radio disable will remain when dirty flashing an update (no need to run the command again).
-If you play any Kanye West, your phone will make a vomit sound and immediately self destruct....you've been warned!
-Revert Command:
Code:
setprop persist.radio.noril 0
Click to expand...
Click to collapse
Even if this is an old thread, it was exactly what I searched for. It works perfect and pushes my "S6 Edge-iPod" to new battery levels. Holds days and drops only a few percent. (Running Android 11 custom Rom)
Thank you for giving that information, I googled a long time to finally find this.
Hello all,
I read that is better to disable Wifi to get more battery life on that smartwatch. On the net there is some tutorial about that, using ADB drivers and Minimal ADB and Fastboot: tapping the foolowing commands:
adb devices
adb kill-server
adb root
adb shell mount -o rw,remount,rw /system
adb shell mv /system/lib/firmware/wifi /system/lib/firmware/wifi_off
adb reboot
I execute commands ok, until command four; I have a failure in the command "adb shell mount -o rw,remount,rw /system": mount: Operation not permitted.
I read that in chinese rom it works, but my watch is international ROM I think. My question are:
1- How can I execute this command without failure?
2- Do I have to unlock the bootloader first?
My rom is readonly mode and I cannot disable wifi I think.
3- Anyone achieved to disable wifi?
Thanks a lot!!
Yes, you need to unlock your bootloader and also root (as you can see by the commands). Personally I wouldn't recommend this, it's like using a cannon ball to kill a fly. WiFi isn't the common cause of excessive battery drain, in most cases the cause is corrupted or bad data stored on watch and because it tries to use WiFi it drains battery, so you are not fixing the cause either. You could also simple factory reset the watch and do not connect to WiFi, this way probably it won't use it later. There are other things you can do to find what's the culprit, and you don't need adb, root or unlocking the bootloader.
Can you not just use
adb shell svc wifi disable
?
You could try PaceOn, it gives WiFi control and has a service that alerts you to BT and WiFi connections.
I'm not sure how much battery cost is incurred by running PaceOn, but it could be worth trying as it give control direct from the watch, eschewing the need for a computer, cable and ADB.
@Quinny899
no, whenever something needs wifi, it just turning back on and getting back to work again.
Agree with lfom & shadowcaster666 on some of the points made here.
Just share my personal configuration.
One-time settings on the watch:
- Set Auto Upload off
- Set Auto Airplane on (00:00-23:59)
- Install PaceOn
Then, use PaceOn to control wifi/bluetooth connections when needed.
Also turn on PaceOn CXN service to see exactly when the watch makes wifi/bluetooth connections.
I have used PaceOn for many months and I can say its battery consumption is negligible.
lfom said:
Yes, you need to unlock your bootloader and also root (as you can see by the commands). Personally I wouldn't recommend this, it's like using a cannon ball to kill a fly. WiFi isn't the common cause of excessive battery drain, in most cases the cause is corrupted or bad data stored on watch and because it tries to use WiFi it drains battery, so you are not fixing the cause either. You could also simple factory reset the watch and do not connect to WiFi, this way probably it won't use it later. There are other things you can do to find what's the culprit, and you don't need adb, root or unlocking the bootloader.
Click to expand...
Click to collapse
I'm almost sure wifi is the culprit of my stratos battery drainage issue. What would be the best way to identify corrupted or bad data stored on my watch? My watch is only one week old I've just set up wifi at home to update to the latest firmware.
gustavosoares said:
I'm almost sure wifi is the culprit of my stratos battery drainage issue. What would be the best way to identify corrupted or bad data stored on my watch? My watch is only one week old I've just set up wifi at home to update to the latest firmware.
Click to expand...
Click to collapse
Battery guide/tips: https://forum.xda-developers.com/smartwatch/amazfit/ultimatre-guide-battery-drain-issues-t3791829
Or you can just use "Amazfit PACE Tuner" - it has control for both WiFi and Bluetooth. No need for root or unlocked bootloader.
Android 10 (Havoc OS), have root access.
And, maybe u know how set fake battery level?
I try change file "capacity" at /sys/devices/platform/battery/power_supply/Battery, but OS don't allow me do it.
Hi,
please try:
(adb shell) dumpsys battery set level 5
(to set battery level to 5 until reboot or reset)
or
(adb shell) dumpsys battery set ac 1
(adb shell) dumpsys battery set status 2
(to set battery status to charging until reboot/reset)
No root access needed.
Skip „adb shell” if running from on-device terminal.
Reset (restore to actual values) by using:
(adb shell) dumpsys battery reset
Your device will shutdown anyway, but much later, depending on kernel values I think.
Mine Oneplus One shuts down at ~2.7V, while Nexus 5 only goes to 3.1V.
Thank you, @bugmento !
All this may seem silly, but it is life or death on a device with a "battery-ectomy" where you have removed the battery and wired in 4V in as a power supply.
The system keeps on thinking that you're discharged because no electrons ever go into the "battery", i.e. the fixed power supply.
If you actually have a battery, you can fudge the numbers at your own peril.
I've seen that level numbers over 10,000,000 cause the percentage level to get reported as zero percent.
If you have a wired device (head unit, battery-ectomied device), do this.
Code:
$ dumpsys battery set present 0 -f
# dumpsys battery unplug -f
$ dumpsys battery set level 99 -f
$ dumpsys battery
"unplug" means to never update the number. It will say " (UPDATES STOPPED -- use 'reset' to restart)".
99 is a nice number and you can see if it has changed somehow.
Edit: I'm still beating my head against this...
In short what I'm doing here and what is the purpose of this. I was able to mod Samsung Galaxy J3 in a way to be used as a 3D printer klipper firmware server by removing the battery and 3D printed a custom one, in which I placed a DC to DC step down module to use the 24v from the 3D printer and step it down to 4v to power on the phone and it all works great! If interested in doing this can share more details, stl for the custom battery and links to the step down module I used. The phone boots and runs perfectly! I run debian linux in container in linux deploy app in which I installed all the needed software to run klipper (klipper, moonraker and mainsail), installed custom driver to connect the printer serial to the micro usb on the phone and all works great!
My problem is that the phone battery level indicator slowly shows like the phone is discharging but it isn't in reallity because it is hardwired to stable voltage from the dc step down module I used. Currently installed android 6 (cyanogen mod 13.0-j3xnite) because the newer versions of android are pain in the a*s to run linux without android to cut it's services and hibernate it, so I'm looking a way to force or trick android think it's battery level stays the same or fake the numbers on it because I'm worried if the level goes down to 0 maybe android will try to shut it down.... I haven't experienced it because it "discharges" at very slow rate but I'm also worried to run a long print on the printer because of this. As you my assume I have root and bla bla... Searched the interned how to force android to set custom battery level but there are only fake apps how to trick friends or your bos that your phone doesn't have battery. Maybe I will need help from a developer how to trick android kernel to show custom or static battery level, or to use some magisk / xposed module for this. Please help me, highly appreciated! When I try "dumpsys battery set level 99" android says batter service not found... Please help and thank you for your time!
Renate said:
Thank you, @bugmento !
All this may seem silly, but it is life or death on a device with a "battery-ectomy" where you have removed the battery and wired in 4V in as a power supply.
The system keeps on thinking that you're discharged because no electrons ever go into the "battery", i.e. the fixed power supply.
If you actually have a battery, you can fudge the numbers at your own peril.
I've seen that level numbers over 10,000,000 cause the percentage level to get reported as zero percent.
If you have a wired device (head unit, battery-ectomied device), do this.
Code:
$ dumpsys battery set present 0 -f
# dumpsys battery unplug -f
$ dumpsys battery set level 99 -f
$ dumpsys battery
"unplug" means to never update the number. It will say " (UPDATES STOPPED -- use 'reset' to restart)".
99 is a nice number and you can see if it has changed somehow.
Edit: I'm still beating my head against this...
Click to expand...
Click to collapse
Did you found a solution? I really need this! Thank you!
thewhisper said:
Did you found a solution?
Click to expand...
Click to collapse
Yes, I found the perfect solution, but I'm not sure how universal it is:
Code:
cp /data/local/tmp/one /sys/devices/platform/battery/FG_daemon_disable
The one file is just the "1" character because echo / tee was being difficult.
"FG" is "fuel gauge", not "foreground".
This sets the battery level at 50% and never annoys you.