Q&A for [KERNEL] FusterCluck Kernel (39a) CM/AOSP/Stock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL] FusterCluck Kernel (39a) CM/AOSP/Stock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery life update on 3.1 for stock
On default settings this kernel (r3b3) used more juice than the stock one.
I flashed 3.1, tweaked some things and now I have 3h 40min SOT with 50% battery left, which is pretty awesome imo and gets the job done for me. No heavy gaming, but I use camera and image editing apps and had no problems whatsoever. Today I was mostly browsing the web.
Settings I am using are :
cpu governor - ondemand with max frequency set to 1497 (but it keeps coming back to 1900, dunno what's up with that)
Cpu hotplug - inteliplug on conservative profile. Minimum cpu's online set to 4 (no difference in speed imo but very battery friendly combined with underclocking)
I/O scheduler - sio
Undervolted everything - 50mV
I had one reboot when I walked outside and tried to set brightness to the max (really weird and random). Didn't catch the log tho. The problem didn't reoccur, so I don't think it's a big of a deal. The phone acts nice and it's cool, no drops in signal, radios, gps and wifi work like a charm. BT works on my speakers and headphones.
Screen uses ~ 40% of battery, kernel ~ 28%, android system ~ 8%.
Using extreme 1.1 rom btw.
Great job on stock 3.1 @Yoinx I will update the status when I get to test it a bit more.
MilanStojkovic said:
On default settings this kernel (r3b3) used more juice than the stock one.
I flashed 3.1, tweaked some things and now I have 3h 40min SOT with 50% battery left, which is pretty awesome imo and gets the job done for me. No heavy gaming, but I use camera and image editing apps and had no problems whatsoever. Today I was mostly browsing the web.
Settings I am using are :
cpu governor - ondemand with max frequency set to 1497 (but it keeps coming back to 1900, dunno what's up with that)
Cpu hotplug - inteliplug on conservative profile. Minimum cpu's online set to 4 (no difference in speed imo but very battery friendly combined with underclocking)
I/O scheduler - sio
Undervolted everything - 50mV
I had one reboot when I walked outside and tried to set brightness to the max (really weird and random). Didn't catch the log tho. The problem didn't reoccur, so I don't think it's a big of a deal. The phone acts nice and it's cool, no drops in signal, radios, gps and wifi work like a charm. BT works on my speakers and headphones.
Screen uses ~ 40% of battery, kernel ~ 28%, android system ~ 8%.
Using extreme 1.1 rom btw.
Great job on stock 3.1 @Yoinx I will update the status when I get to test it a bit more.
Click to expand...
Click to collapse
Could be a bug with on-demand. Set the max cpu freq in the msm limiter... Should stop that.
3.1
Had a few random reboots yesterday under pretty mild usage. I am positive undervolting or underclocking was the cause since the 1400 wouldn't stick. I tried both trickster and adiutor. Not sure what was the problem but flashing bouchigo's int.d support zip and installing ukm and setting frequencies in synapse msm limiter solved the problem. It seems to be sticking now. Still undervolted, but working good for now. Thanks for the suggestion! I will keep monitoring the frequencies to see if that was a permanent fix.
Also noticed that underclocking the gpu while using msm-tz-adreno won't stick, not even in synapse. Same with msm_cpufreq. Choosing simple_ondemand is causing an instant system crash on extreme 1.1
That's all for now
UPDATE
Yup, freq sticking at 1574, undervolted - 45mV global, stable and smooth
3h20min SoT with 55% battery remaining. Sweet!
Where is the apk to change settings
richielasalsa said:
Where is the apk to change settings
Click to expand...
Click to collapse
look it up on Playstore. Synapse worked best for me, just make sure you have init.d set up if you are on extreme 1.1. There are other options too. Trickster, kernel auditor etc.
So I've gotten my standby time to be pretty good but under moderate use, the device is getting warm and chewing through battery. I.e 4hrs off charger, 40 minutes of screen and only 71% left. I'm stock rooted and removed bloat. Even had stuff greenified (just uninstalled to test now). Is there anything I can do without tripping Knox to slow down the CPU a little? The native power save mode is all or nothing now - they used to let you control which features were enabled on older devices
km8j said:
So I've gotten my standby time to be pretty good but under moderate use, the device is getting warm and chewing through battery. I.e 4hrs off charger, 40 minutes of screen and only 71% left. I'm stock rooted and removed bloat. Even had stuff greenified (just uninstalled to test now). Is there anything I can do without tripping Knox to slow down the CPU a little? The native power save mode is all or nothing now - they used to let you control which features were enabled on older devices
Click to expand...
Click to collapse
If your rooted, download a program called Trickster Mod. (All credit to the dev) It allows you to underclock the CPU. Stock value is set at 1.5Ghz. WIthout an overclocked kernel, that value cannot change. However, underclocking is available. And since this device is a true octa-core dropping it to 1.2 Ghz shouldn't be a problem. Also you can change your governor to a conservative one. Stock is ondemand. Conservative and Performance are able to be selected. Changing your TCP congestion to cubic instead of the stock bic, in my experience, gives you a bit better battery life as well. Hope this helps.
Thanks!
The app doesn't say it supports s6, does it definitely work?
You can try kernel tweaker which is also availble on the play store. By the way we do have a Q&A forum so your questions would be better suited over there.
I can't find anything called "kernel tweaker" exactly... Also my question was about apps and this is app subforum. Sorry if that isn't correct
Intro
Over the past while I've finally decided to fix all minor annoyances on my Nexus 4. Here is a guide where I'll share all my modifications to make Mashmallow on the Mako as good as can be.
Kernel
Kernel Proper
The actual kernel included in this guide is HellSpawn kernel by @spezi77 which is based on hells-Core for Marshmallow, with all up-to-date Linux patches (3.4.112) and Google security patches (June 1). (Although I use, advocate, and absolutely recommend HellSpawn, feel free to use another custom kernel in the installer. You'll have to replace zImage and make your own changes to kernel/sema-boot.sh if your kernel doesn't include the same governors, hotplugs, etc.)
Here are a few highlights of HellSpawn itself:
- Includes the elementalx governor from @flar2 and lightweight mako_hotplug driver from @franciscofranco, which are much better than the stock ondemand governor and mpdecision hotplugs.
- Includes franciscofranco's gamma control, which is a much better default gamma for your screen and can be changed with franco's Nexus Display Control app or other Kernel Tweaker Apps.
- Includes a GPU overclock (400 -> 487 MHz) for when really demanding graphics operations require it.
- Includes BFQ, an optimized version of the default kernel's CFQ i/o scheduler. It helps when Play Store updates occur or when apps perform a lot of disk activity.
- Includes double tap to wake feature, which uses minimal extra battery and is much more convenient than the power key.
- When the screen is off, and not sleeping, only one CPU is active and it's limited to 1 GHz, which helps standby battery life with running background services.
Custom Kernel Installer
(original post with r1 was made on reddit)
I've adjusted many default kernel settings, based on a few years experience of running custom kernels. It uses the optimized elementalx governor from ElementalX kernel and lightweight mako_hotplug from franco kernel, with some of flar2's N5 settings, some of @hellsgod's N6 settings, and some of mine. There are other governors and hotplugs available, but from my experience, these offer the best balance of speed and battery life.
It includes a small, safe, -50 mV undervolt for a bit less heat from the CPU. - a user on reddit reported a reboot with r1, so I've removed voltage settings. It's probably useless to include such a small undervolt anyway. Change voltage settings in an init.d script or Kernel Tweaker app if you wish.
It activates double tap to wake by default, and also turns on power key suspend. If you press the power key with the screen on, double tap to wake will be turned off. Those on custom ROMs or Xposed's GravityBox can activate features to turn the screen off (double tap status bar, lock screen, nav bar, etc.) and keep double tap to wake on. Those without custom ROMs can perhaps use something like Greenify which can remap the home button long-press to turn the screen off.
It includes a patch to sepolicy which allows Viper4Android to work in selinux enforcing mode. You need to have SuperSU installed to have this work.
I've adjusted the io scheduler and page cache for better performance, tuned towards random reads.
It includes stock thermald and a tweaked thermald configuration that scales CPU frequencies up and down a little smoother when your temps get high. It should be noted that most custom kernels disable thermald for their own in-kernel thermal driver. I never liked doing this, as thermald does more than just adjust CPU frequencies - it also throttles GPU, screen brightness, and most importantly, battery charging. When your device gets too hot while charging, the worst thing to do is keep up the current and let the battery go over 45 degrees.
It includes a service to do 'Shared Cpufreq Policy', which lets thermald throttle all cores properly, and also lets the Battery Saver feature work correctly, by limiting all cores. This hasn't worked since KitKat and was one of my biggest annoyances. Many, if not all custom kernels just deleted the Power HAL libraries so battery saver feature doesn't work at all!
Includes Semaphore's 'mpdfake', a service to eat the touch boost spam that the Power HAL generates when not using mpdecision. If a custom kernel does not delete the Power HAL libraries, then your logcat is being spammed and logd process uses a lot of background CPU!
Includes a service to attempt to fix once and for all the location/GPS issues. I'm not going to state it works 100% yet, as I've only had max 24 hr uptime while making changes from the r1 release, but so far so good. Fingers crossed...
Includes a service to give SystemUI and Phone/Dialer higher priority. I haven't had a chance to really test it, as my device is sans-SIM at the moment, but it hopefully will lead to better responsiveness when you receive a call. (Under testing: giving some background processes lower priority, so they don't interrupt app usage.)
Move dalvik-cache to /cache partition and free 300-500 MB:
On each boot, it will check to see if you have a /cache/dalvik-cache folder, and will use it as the dalvik-cache if so.
If you are clean flashing a ROM and want to use /cache for dalvik-cache, create an empty dir in TWRP: /cache/dalvik-cache
If you just want to switch from /data to /cache, copy the /data/dalvik-cache to /cache/dalvik-cache and reboot.
Remember to be careful not to wipe /cache when 'dirty' flashing if you do this!
How to reset the mediaserver process quickly to get videos playing:
While your screen has been on for a few seconds or longer, double press the power key. You'll have to try it a few times to get the timing right, because a quick double press activates the camera in some ROMs. Also you're waiting for the screen to go off, not just dark. Practice a few times in low light, and you'll get the hang of the timing: each press should be followed by about half a second. You'll feel a short vibration when the service resets mediaserver to give some feedback that it's working. If it doesn't run the first time, keep cycling the screen off and on again until you get that vibration.
Remember: you have to start with the screen on, this allows you to quickly check on notifications from screen off without resetting mediaserver.
How to reset the sensors if ambient brightness, auto rotation, GPS, or any other sensors stop working:
Same as above, but this time you do the action twice. That is, screen on - double press power - vibrate once - double press power. You must do the two double presses within a second or two, so a little more practice may be needed. You'll feel two short vibrations when the service resets the sensors.
*** As of mod-r4, the new method to reset both mediaserver and sensors is Hold Volume Up and Power.
How to reset the touch screen if it becomes unresponsive:
If you happen to double tap to wake, the screen comes up, but no touches are being registered, tap on the screen with five fingers. If this doesn't reset it, turn the screen off and on again with the power key, and tap on the screen with both hands, all ten fingers. This will reset the driver and get it going again without a reboot.
Download & Installation
The installer is attached to this post. It's for AOSP ROMs, and uses the UberTC 5.4 toolchain. I'll post up CM versions on request.
Flash the zip with TWRP 3.0.2. If you have made any changes to your Marshmallow ROM (other custom kernels, etc.) you must remember to always flash custom kernels after (dirty) flashing custom ROMs! This is especially important, as if you are missing thermald you're going to have a bad time. FLASH YOUR ROM BEFORE THIS KERNEL INSTALLER UNLESS YOU HAVEN'T MADE ANY CHANGES. You can kill your device without thermal throttling!
Wiping dalvik-cache, and /cache is never necessary when flashing a custom kernel only.
ROM
Graphics Drivers
Audio
SuperSU - System or systemless?
Changelog: r14-mod-r3 - r13-mod4 - r16-mod-r5 - r04-mod-r6 - r05-mod-r7
Sorry, ran out of time for now but I'll continue the post soon...
If I want to customise the features, do I only comment out the features which I don't need in sema-boot.sh? Thx!
Hi @xenyz,
Thank you for your new kernel, I have to say that I missed using your projects.
Until now I'm testing it and the only cons I found is that with mako_hotplug when (temp increases) 1026 frequency makes mako very unresponsive.
Is there a way to change this frequency through a init.t script?
Thanks for keeping mako alive!
jer_ying_fd said:
If I want to customise the features, do I only comment out the features which I don't need in sema-boot.sh? Thx!
Click to expand...
Click to collapse
Sure, or another option is to put your overrides in /system/etc/init.d
jolas said:
Until now I'm testing it and the only cons I found is that with mako_hotplug when (temp increases) 1026 frequency makes mako very unresponsive.
Is there a way to change this frequency through a init.t script?
Click to expand...
Click to collapse
Carefully edit /system/etc/thermald.conf either in the installer before flashing, or on your device after flashing, and make your changes near the end of the file.
Can anyone comment on whether their location services are working better? I'm still undecided.
Sent from my Nexus 4 using Tapatalk
With the introduction of the new features of hellspawn r14, will it still work as it is?
jer_ying_fd said:
With the introduction of the new features of hellspawn r14, will it still work as it is?
Click to expand...
Click to collapse
I'm testing it out to make sure it's stable first. At least one change has to be made, turning off the new msm_hotplug which is enabled by default in r14.
Sent from my Nexus 4 using Tapatalk
xenyz said:
I'm testing it out to make sure it's stable first. At least one change has to be made, turning off the new msm_hotplug which is enabled by default in r14.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Ahh of course, I forgot to edit that out....
I've gotten strange behavior after installing the kernel on my Chroma ROM Nexus 4.
The touchscreen began to have bouts of unresponsiveness, when it never had it prior to installation
Extremely slow on wakeup after a long time in sleep mode. Once again, never had that issue before
Overall lag and slowdown that wasn't present on the stock kernel
I've enabled only D2TW, the new I/O scheduler, 1 core active on sleep, Schedule workqueues on awake cores, and ThermalId
Just now, it did a random reboot. Any idea on what the issue could be?
ArtOfSnaila said:
I've enabled only D2TW, the new I/O scheduler, 1 core active on sleep, Schedule workqueues on awake cores, and ThermalId
Just now, it did a random reboot. Any idea on what the issue could be?
Click to expand...
Click to collapse
Could you try it without changing any settings? Force stop the kernel app and reboot.
Do you use any Doze modification apps? Greenify aggressive doze?
Was it a reboot or a SystemUI restart? Did you see the Google bootloader logo? If so, send me last_kmsg
Sent from my Nexus 4 using Tapatalk
xenyz said:
Could you try it without changing any settings? Force stop the kernel app and reboot.
Do you use any Doze modification apps? Greenify aggressive doze?
Was it a reboot or a SystemUI restart? Did you see the Google bootloader logo? If so, send me last_kmsg
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Alright, I'll try it without any settings modified.
I do use Aggressive Doze, could that be conflicting with the kernel? It never seemed to affect the stock kernel besides making the wake take a bit longer, but no lag afterwards.
It was a complete reboot, with the Google logo and everything. Here's the last_kmsg.
ArtOfSnaila said:
I do use Aggressive Doze, could that be conflicting with the kernel? It never seemed to affect the stock kernel besides making the wake take a bit longer, but no lag afterwards.
Click to expand...
Click to collapse
I have noticed some erratic behaviour when modifying doze settings. My best guess is that there are certain assumptions made in Marshmallow as to when the device will be in Doze mode, and changing them can have unintended consequences.
ArtOfSnaila said:
It was a complete reboot, with the Google logo and everything. Here's the last_kmsg.
Click to expand...
Click to collapse
That is strange, the reboot was caused by a restart to recovery request. If it happens again, grab another last_kmsg?
Sent from my Nexus 4 using Tapatalk
xenyz said:
I have noticed some erratic behaviour when modifying doze settings. My best guess is that there are certain assumptions made in Marshmallow as to when the device will be in Doze mode, and changing them can have unintended consequences.
That is strange, the reboot was caused by a restart to recovery request. If it happens again, grab another last_kmsg?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Ah crap, about the last.kmsg, I think I know what happened. To pull the .txt file I had to reboot into recovery and use terminal to mount /system and then pull it. It might've pulled data off of that restart.
Currently using the phone with no kernel app active, and it's doing fine. I'll keep you posted if weird stuff happens.
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
ArtOfSnaila said:
...
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
Click to expand...
Click to collapse
Maybe it had to do with hotplug settings (I used to have similar problems until I modified thermald.conf settings)
Sent from my Nexus 4 using Tapatalk
ArtOfSnaila said:
Another thing I noticed is that when I plugged in the charger, the phone would slow down a lot.
Click to expand...
Click to collapse
That's likely because of the thermal throttle when the battery gets warm. Keep in mind this is actually good for your battery, although annoying when it slows down.
I'm thinking about raising the threshold just a bit in the next release.
Sent from my Nexus 4 using Tapatalk
xenyz said:
That's likely because of the thermal throttle when the battery gets warm. Keep in mind this is actually good for your battery, although annoying when it slows down.
I'm thinking about raising the threshold just a bit in the next release.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I found the following changes to accomplish best my needs (snappier phone with average temp)
jolas said:
I found the following changes to accomplish best my needs (snappier phone with average temp)
Click to expand...
Click to collapse
Cool. Er, warm. Eh, whatever.
What's your battery temps whilst charging? This is my main concern and where throttle is necessary.
All batteries achieve optimum service life if used at 20°C (68°F) or slightly below. If, for example, a battery operates at 30°C (86°F) instead of a more moderate lower room temperature, the cycle life is reduced by 20 percent. At 40°C (104°F), the loss jumps to a whopping 40 percent, and if charged and discharged at 45°C (113°F), the cycle life is only half of what can be expected if used at 20°C (68°F).
Click to expand...
Click to collapse
source
I know it's likely not that useful for those of us with original batteries on older devices, but I try to treat it as best I can.
Sent from my Nexus 4 using Tapatalk
xenyz said:
Cool. Er, warm. Eh, whatever.
What's your battery temps whilst charging? This is my main concern and where throttle is necessary.
source
I know it's likely not that useful for those of us with original batteries on older devices, but I try to treat it as best I can.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Charging with screen on, battery temp around 40°C
Sent from my Nexus 4 using Tapatalk
After more than 24 hours of usage without kernel manager, it ran fine, until it started throttling for some reason. Turns out somehow, the max clock speed was locked to 1000 or so Mhz. I don't know if that was the kernel or the app misbehaving, but I ended up having to reactivate the kernel app to set the clock speed back to normal
There was another spontaneous reboot, here's the last.kmsg.
ArtOfSnaila said:
There was another spontaneous reboot, here's the last.kmsg.
Click to expand...
Click to collapse
Thanks for the log. I had a similar reboot but with r14, something in the wakeup_reasons code. I'll have a look through spezi77s commits in kernel/power and see if I can spot something.
I haven't had one reboot in a month or so of using r13, so it's quite strange that you had one so soon, after 24h.
As for the throttle, keep an eye on your battery temperature in Kernel Auditor or whatever and see if it's higher than 40 degrees when you get the 1 GHz max freq.
Edit: I discovered at least one bug in r2 wrt the PowerHal touch boost spam. I'm thinking of posting r14mod3 but I'm not certain r14 is stable yet (see main kernel thread)...
Sent from my Nexus 4 using Tapatalk
Hello everyone!
Usually I am not active on forums because usually most answers are somewhere in the vast internet. But this time I gave up.
I have a problem with my Note 5's (SM-N920L) fast battery drain. Now it even goes 20% per hour when I use it.
My phone is already about 1,5 year old and I use it a lot, so I read that might be a battery problem so I tried booting it into safe mode and it solved the problem so it seems there is a problem with some app or other functionality, not a battery. So I have factory reset my phone and it was working fine for maybe 3 days, then afternight it drained batterry ultra fast again.
I tried uninstalling any apps that I had installed the day before it broke again, but it didn't help
I have also rooted my phone previously to try to find the reason for fast drain with Gsam stats and WakeLock but I still couldn't find out what's the cause of the problem.
I've seen some posts about deep sleep issue, but my battery drain is qute ok when I'm not using it.
Did anyone have a similar problem? Do you have an idea what can I do to repair it?
Greetings,
Paweł (Paul) Sawicki
Recently I've been trying a different set of tweaks and have the best battery life I've ever had with this device.
DO NOT USE GREENIFY. As it drains the battery a lot these days.
-Rom: PixelRom v6 (Samsung based, all other roms suck for our device, this is odexed and the fastest)
-Kernel: Fuel kernel.
-Cpu governor:
Big: zzmove
Small: interactive
-Flash the lastest Magisk 13 beta.
-Download - then install the following magisk zip plugins through the magisk app:
-(Deleted crossbreeder, as it causes system hangs)
-DozeGMS
-https://forum.xda-developers.com/apps/magisk
Then install busybox (use one which installs successfully). Then hebf from the play store, don't apply any profiles. Disable the extra logging and kernel panics - set it to stay on boot.
-Battery tab - Enable improve battery, low ram device, instant doze.
And I do recommend making your wifi turn off when the screen goes off.
Welcome to three days of battery with frequent usage.
-
Thank you
Turbine1991 said:
Recently I've been trying a different set of tweaks and have the best battery life I've ever had with this device.
DO NOT USE GREENIFY. As it drains the battery a lot these days.
-Rom: PixelRom v6 (Samsung based, all other roms suck for our device, this is odexed and the fastest)
-Kernel: Fuel kernel.
-Cpu governor:
Big: zzmove
Small: interactive
-Flash the lastest Magisk 13 beta.
-Download - then install the following magisk zip plugins through the magisk app:
-CrossBreeder Lite Edition
-DozeGMS
-https://forum.xda-developers.com/apps/magisk
Then install busybox (use one which installs successfully). Then hebf from the play store, don't apply any profiles. Disable the extra logging and kernel panics - set it to stay on boot.
-Battery tab - Enable improve battery, low ram device, instant doze.
And I do recommend making your wifi turn off when the screen goes off.
Welcome to three days of battery with frequent usage.
-
Click to expand...
Click to collapse
Thank you for your detailed reply! :highfive:
I'll try to install the set you've mentioned and will get back soon with results. I hope this will be the solution.
Have a nice day!
Greetings,
Paweł (Paul) Sawicki
Also got the best battery life with Pixelrom 6
Turbine1991 said:
Recently I've been trying a different set of tweaks and have the best battery life I've ever had with this device.
DO NOT USE GREENIFY. As it drains the battery a lot these days.
-Rom: PixelRom v6 (Samsung based, all other roms suck for our device, this is odexed and the fastest)
-Kernel: Fuel kernel.
-Cpu governor:
Big: zzmove
Small: interactive
-Flash the lastest Magisk 13 beta.
-Download - then install the following magisk zip plugins through the magisk app:
-CrossBreeder Lite Edition
-DozeGMS
-https://forum.xda-developers.com/apps/magisk
Then install busybox (use one which installs successfully). Then hebf from the play store, don't apply any profiles. Disable the extra logging and kernel panics - set it to stay on boot.
-Battery tab - Enable improve battery, low ram device, instant doze.
And I do recommend making your wifi turn off when the screen goes off.
Welcome to three days of battery with frequent usage.
-
Click to expand...
Click to collapse
I can only find Crossbreeder Ultra Lite. The Crossbreeder Lite thread says it's for 5.1 and below. What one is right to use?
Check system processes. I found out recently that com.android.systemui uses 15% cpu even on empty home screen and heats up my device without any reason. It was definately the cause of my battery drain. I've been trying disabling apps and unnececery options, and suddenly ui stoped draining and went down to normal 0.5% cpu consuimption. But I don't know exactly what I changed. My latest action was to update all Galaxy Apps.
Actually - don't use that Crossbreeder plugin, it seems to cause system hangs. Everything else though is fine - it'll make the battery life sing!
I also accepted this device just had bad battery life. But now it's never been so good.
IMO Samsung should have used a single processor and use a bigger battery.
Turbine1991 said:
Recently I've been trying a different set of tweaks and have the best battery life I've ever had with this device.
DO NOT USE GREENIFY. As it drains the battery a lot these days.
-Rom: PixelRom v6 (Samsung based, all other roms suck for our device, this is odexed and the fastest)
-Kernel: Fuel kernel.
-Cpu governor:
Big: zzmove
Small: interactive
-Flash the lastest Magisk 13 beta.
-Download - then install the following magisk zip plugins through the magisk app:
-(Deleted crossbreeder, as it causes system hangs)
-DozeGMS
-https://forum.xda-developers.com/apps/magisk
Then install busybox (use one which installs successfully). Then hebf from the play store, don't apply any profiles. Disable the extra logging and kernel panics - set it to stay on boot.
-Battery tab - Enable improve battery, low ram device, instant doze.
And I do recommend making your wifi turn off when the screen goes off.
Welcome to three days of battery with frequent usage.
-
Click to expand...
Click to collapse
Ok I did most of these, except zzmoove thing which I dont know how to do... But my battery is still draining like crazy... almost more than 5% idle...
Can any body help?
Hello! (Sorry I could not create DevDB entry)
Its time for my first kernel.
I currently own the old but gold LG G Watch R.
It is so slow - taking out your phone is 5 times faster than using this thing.
With this kernel the experience is improved by changing the voltage, count and frequency of the CPU-Cores. (At least factor 4 in cpu performance?)
You need to have ext4 on your system partition to get this thing booting!
Ramdisk-Changes:
Enable all four cores
Change ondemand up_threshold from 90% to 85%
Set cpu core frequency for core0 and core1 to 1,4Ghz (Next version i will try even more)
Set cpu core frequency for core0 and core1 to 0,9Ghz
fstab: Change /system to ext4
Kernel modifications
Disable legacy components like squashfs and ext2, ext3..
Enable basic f2fs (sadly not booting - i will try to upstream it someday)
Customize PVS Voltage table: 20+ PVS will use voltage 900mV, 890mV and 980mV instead of 1050mV, 1050mV, 1140mV
Customize PVS Floor voltage to 900mV, 890mV, 970mV
Is my watch using the new voltage levels?
Execute (adb)
Code:
dmesg | grep voltage
And look if the values match with the values posted above
Is my watch clocking higher now?
Execute (adb)
Code:
cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
The correct output should be four times 1401600, the current init.rc sets the scaling limit to 2x1305600 and 2x900000 though
This kernel was only tested by me for about 30minutes now. It can crash at any time. Do not blame me - i just want to share something with this awesome community.
This kernel is based on android-msm-bass-3.10-nougat-mr1-wear-release
I will try to overclock and undervolt even more.
And find the next bottleneck (For sure its slow storage, so we need f2fs)
I do not recommend flashing this kernel, better just use fastboot boot.img since we can not be sure that it is stable yet
Hi can you share the source code with us please?
Nice Kernel.
Gonna try this as my new daily driver.
Set up a fresh System on my G Watch R with 512MB System and 125MB Cache.
It's working pretty fine for now, just gotta check for stability and battery life
petya230 said:
Hi can you share the source code with us please?
Click to expand...
Click to collapse
Sorry for the late answer
Yes i will soon release it (I can not tell a exact date yet)
Infact the current changes are just changing the voltage table and the fstab
Darthsternie said:
Nice Kernel.
Gonna try this as my new daily driver.
Set up a fresh System on my G Watch R with 512MB System and 125MB Cache.
It's working pretty fine for now, just gotta check for stability and battery life
Click to expand...
Click to collapse
Thats great
I'm having some booting issues and I'm not currently using or developing for this watch.
But i will try to get some information about which features could be useful for our device.
Maybe its worth the afford because the current new smartwatches around are not really better compared to our watch
I'm currently thinking about zstd compression for the system partition or for everything. But porting will be a massive afford and i can not tell for sure if i wanna do this
_Beni_ said:
Sorry for the late answer
Yes i will soon release it (I can not tell a exact date yet)
Infact the current changes are just changing the voltage table and the fstab
Thats great
I'm having some booting issues and I'm not currently using or developing for this watch.
But i will try to get some information about which features could be useful for our device.
Maybe its worth the afford because the current new smartwatches around are not really better compared to our watch
I'm currently thinking about zstd compression for the system partition or for everything. But porting will be a massive afford and i can not tell for sure if i wanna do this
Click to expand...
Click to collapse
The Kernel seems to be pretty stable. Since flashing I didn't have a single system crash or reboot.
It's a lso a lot snappier. Normally when I took it of the charging Pad in the morning and enter the Pin-Code it would lag quite a lot.
Switching between Apps also feels snappier
What kind of boot problems do you have? If it's the "Watch only boots while in the charging cradle" then it's a dead battery
Darthsternie said:
The Kernel seems to be pretty stable. Since flashing I didn't have a single system crash or reboot.
It's a lso a lot snappier. Normally when I took it of the charging Pad in the morning and enter the Pin-Code it would lag quite a lot.
Switching between Apps also feels snappier
What kind of boot problems do you have? If it's the "Watch only boots while in the charging cradle" then it's a dead battery
Click to expand...
Click to collapse
It just does not boot from the kernel - Its probably because i flashed the wrong kernel or a not working one.
I already fixed the dead battery problem with some little solder bridge
I'm sure we could gain some more performance by using f2fs - but I'm not that good at upstreaming (But someday i will )
_Beni_ said:
It just does not boot from the kernel - Its probably because i flashed the wrong kernel or a not working one.
I already fixed the dead battery problem with some little solder bridge
I'm sure we could gain some more performance by using f2fs - but I'm not that good at upstreaming (But someday i will )
Click to expand...
Click to collapse
Do you have a current EXT4 rom? All of the old roms no longer exist for download.
_Beni_ said:
Ramdisk-Changes:
Enable all four cores
Change ondemand up_threshold from 90% to 85%
Set cpu core frequency for core0 and core1 to 1,4Ghz (Next version i will try even more)
Set cpu core frequency for core0 and core1 to 0,9Ghz
fstab: Change /system to ext4
Kernel modifications
Disable legacy components like squashfs and ext2, ext3..
Enable basic f2fs (sadly not booting - i will try to upstream it someday)
Customize PVS Voltage table: 20+ PVS will use voltage 900mV, 890mV and 980mV instead of 1050mV, 1050mV, 1140mV
Customize PVS Floor voltage to 900mV, 890mV, 970mV
Is my watch clocking higher now?
Execute (adb)
Code:
cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
The correct output should be four times 1401600, the current init.rc sets the scaling limit to 2x1305600 and 2x900000 though
Click to expand...
Click to collapse
can you explain more and show me all how to do this. especial is modify ramdisk to apply new frequency on qualcomm device?
Is it possible to use this kernel based on NWS2.170620.003?