4 core unlock for LG Watch Urbane 2. - LG Watch Urbane 2

Hey there. Would someone be willing to unlock all 4 cores for LG watch urbane 2. It has already been done for the LG watch urbane but it seems like it was never attempted for the urbane 2. Since it has more ram than the original urbane, i think unlocking all 4 cores would make this watch a viable daily driver even today. Much appreciated! Thanks!

Hey there. It seems like no one is interested in this watch anymore. I figured out a method that is less graceful but it works and it will breathe some new life into your device.
Please do this at your own risk. I am not responsible for any bricked devices.
Step 1:
- Follow the guide in this forum to install TWRP recovery.
https://forum.xda-developers.com/sm...ot-twrp-squashfs-3-1-1-lg-urbane-2nd-t3661569
- The SuperSU provided in that thread didn't work for me. Just an FYI. Your mileage may vary.
Step 2:
- Download the following:
1. Kernel Auditor for wear ( requires busy box )
2. A zip with both root and busy box.
Here is the link ( Contains both Kernel auditor. apk and zip that would root your device and install busy box at the same time - how nice!)
https://mega.nz/file/9UgmgZYI#1YEv4NnmNx3MCLAHDjt_5Lz-yEnhAX6MFWcDpga7TWw
Step 3.
- In TWRP - Flash mixedroot.zip. Wipe dalvik Cache. Reboot.
- Boot into Android Wear. Adb push KA.apk and install with adb. ( Nice guide here: https://www.techadvisor.co.uk/how-to/google-android/sideload-apps-android-wear-3673967/)
- Reboot your device again. Tada.
You'll have Kernel Auditor. The UI for KA on round watches is very awkward but it still works. LG Watch Urbane 2 has two core disabled by default and the other two run at powersave with a frequency of 800mhz. You can unlock the other two cores and change the CPU governor to ondemand. You can play around with other stuff too. But read up about it before u make any drastic changes.
That'd be all folks!
If any of the kernel gurus read this - ideally we need a custom kernel w/ more cpu governors and and an undervolt for the CPU for better battery life. It has been done for LG watch Urbane Gen 1. It's unfortunate it never happened for Urbane 2.
Thanks! This is by no means a definitive guide. I am no expert btw. Do everything at your own risk!

Save more battery life in screen turned off mode
Hey guys. So I have been playing around with the LG watch urbane 2 the past few days with the unlocked cores. The sweet spot seems to be three active cores at 1 Ghz on-demand governor. I easily get a day's worth of battery w/ that with always-on display on and wifi turned off.
I discovered another application called CPUPARK. It's great cuz you can assign how many cores stay active during screen on and screen off periods which can potentially save some battery when the watch is idling. I am not sure whether ambient mode has any bearing on this. Needs further testing but in theory, it should work for those of you who like to turn off AOD.
Here is the link:
https://www.phonearena.com/news/Spo...ol-over-your-devices-active-CPU-cores_id74194
Sideload with adb. Open the application - then press the middle button. it will give you a floating square window which looks nice on the watch with everything visible. You can change core frequencies from there. In the advanced mode you can change active cores w/ screen on and off and their individual frequencies and governors.
I am not sure whether this works without kernel auditor and busybox. I don't think this app has any dependencies except root. Anyway wanted to put out there. Will test the battery and report when able.

Update!
So I have been running this setup for a couple of days now:
I have: AOD on, Wifi on, all health stuff on, fairly regular notifications..
The battery lasted more than one a half days. And it's snappy. So i'd say it's worth doing.

supratentorial said:
Hey there. It seems like no one is interested in this watch anymore. I figured out a method that is less graceful but it works and it will breathe some new life into your device.
Please do this at your own risk. I am not responsible for any bricked devices.
Step 1:
Click to expand...
Click to collapse
Hi,
I ask for your help.
My urbane 2 is currently faulty, and it crashes
- Urban 2W200v
"target reported max download size of 268435456 bytes
sending 'recovery' (18658 KB)...
OKAY [ 0.742s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.834s."
and still in the Fastboot menu.
You help me save his life, thank you very much.
I am not good at using English, and am using translate google.

Related

Smartass CPU Governor on Droid 2

So I was investigating loadable kernel modules on the Droid 2 this weekend. One of the modules I tried loading was the smartass governor module and to my surprise it worked. From what I can tell it appears to be working with no problems.
The module itself is from a Milestone Cyanogen ROM. Given how close the Milestone is to the Droid 1 and how close the Droid 1 is to the Droid 2 it seemed like a safe try to see if it would load.
Requirements:
You must be rooted. This really should go without saying but I'm trying to cover all the bases here.
You must have busybox installed.
You must be able to boot into clockwork recovery.
I've tried this on Fission ROM but since we can't change the kernel on the Droid 2 this will probably work on any other Droid 2 ROM. D2G users, YMMV.
NOTICE: By installing this you assume any and all risk for what might happen to your phone. I am not responsible if this mod causes your phone to stop working, catch fire, steal your significant other, and/or hijack a plane. Basically I haven't had any issues but that is not a guarantee that you won't have any issues.
Attached is the update.zip. Boot into clockwork recovery and choose this zip to install. Once you reboot you'll be using the smartass governor.
So what has this done for your battery life?
Anecdotally I believe my battery life has improved. With the ondemand governor and data and wifi off I've seen my battery drop 10% in a night. With the smartass governor under the same conditions my battery appears to be the same. Now given that Motorola phones report the battery in just 10% increments my totally non-scientific analysis might end up being nothing.
Really you'd have to try it yourself and determine if things are better. From what I've read online the smartass governor is better at conserving battery than ondemand but it really depends on how you use your phone.
Download circle battery widget from the market. Its free and somehow it reports 1% increments. I have been using it for a while now and it seems to be spot on.
Sent from my DROID2 using Tapatalk
It just guesses
Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.
Looks interesting. I'll wait until a little more feedback is given before I try it. How is the performance after the install?
I'm guessing you have to sbf to go back?
tbaker077 said:
How is the performance after the install?
Click to expand...
Click to collapse
No different than using the ondemand governor. Smartass takes a clever approach to CPU scaling: instead of polling CPU usage like ondemand it detects when the phone comes out of sleep and sets a timer to go off in two ticks. Once that timer goes off it looks at CPU usage and scales if needed. What does all this mean? Well, if you turn on your phone to quickly check the time and then turn it back off the smartass governor will never ramp up the clockspeed. So far after a few days of light usage I've been quite pleased.
rtfield said:
I'm guessing you have to sbf to go back?
Click to expand...
Click to collapse
Nope. If you want to revert just chmod 644 /etc/startup/smartass.sh and reboot.
Sweet
Thanks
I wonder if they could modify this to work with the new gingerbread kernel.
I know when I had an HTC Eris, Conap used a smartass gov on his kernel and it was awesome.
So I took a shot and flashed the smartass governor a second ago on my GB d2, and seems to be working just fine. I'll report later with battery stats and anything else i notice.
Spitemare said:
Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.
Click to expand...
Click to collapse
I took a look at this and found some stuff that might be encouraging.
Here is the source for the battery driver. Line 397 reads as such:
Code:
val->intval = sply->batt_state.capacity;
If line 397 is changed to this
Code:
val->intval = sply->batt_state.batt_capacity_one;
then battery level should be reported in 1% increments. I've posted the updated driver code here.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...
Do we really need busybox to uses this?
tbaker077 said:
Do we really need busybox to uses this?
Click to expand...
Click to collapse
Busybox's insmod is a little more robust then the insmod that's on the Droid 2. You can try editing the file /etc/startup/smartass.sh to remove the references to busybox and see if it works; I just stuck with busybox since that was what worked for me when building this thing. I'd try it myself but I can't at the moment.
I'm running an experiment now to see how long this governor will take me. I charged my phone to 100% last night (really 100% and not just to when the charging light went off) and turned it off. I turned it on this morning and will let the phone run until 5% battery is left. At that time I'll take a screenshot showing how long the system has been up. A few guidelines:
ROM is Fission 2.6.1 which of course means Froyo. I've been thinking about switching to the leaked Gingerbread ROM but I've decided to wait a little longer
Data must remain on. I usually turn data off when I'm not using it but to get results closer to worst case I'll keep data on. The only time it will go off is when I turn on Wi-Fi at home.
No turning off the phone at any time nor plugging it in. I guess I'm going to be using Dropbox a lot during this to transfer files but I don't want to reset the time since plugged in at all.
No overclocking, underclocking, or undervolting. Clockspeed and voltage are stock.
Usage will be light to moderate. I tend to use my phones for calls, chats, and web browsing. I'll throw in some YouTube videos and maybe download Angry Birds.
No apps that try to maximize battery life. That means no SetCPU, Tasker, Superpower, etc. This is supposed to be about how well the smartass governor does for battery life.
Again, once I reach 5% I'll try to take a screenshot of how long the phone went without being recharged.
Spitemare said:
I took a look at this and found some stuff that might be encouraging.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...
Click to expand...
Click to collapse
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.
So unfortunately my phone rebooted halfway into the experiment so there is no screenshot for you all. I will say my phone made it just under 36 hours (6:30 Friday to 18:15 Saturday) on this governor. With some moderate internet browsing and way too many YouTube videos I'm quite happy with the outcome using this governor.
ZaneKaminski said:
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.
Click to expand...
Click to collapse
I've already compiled the modified module and tried to load it. The phone just prevents it from loading since the hardware interrupts are already bound to the compiled in driver.
eFuse doesn't prevent new kernel modules from being loaded. Since a kernel module can alter almost anything not being able to change the kernel isn't too much of a problem. What a kernel module can't really do, however, is change device drivers. There's not a really clean way to unload a device driver module since it binds to hardware interrupts and you can't really unbind that once the phone is up and running. If you want to replace a device driver with an alternate module you have to load the module before the original module is loaded sometime during the boot process. With compiled in device drivers though that's not really possible.
Basically we're in a situation where we need to load an alternate version of the device driver in module form before the compiled in device driver binds to the hardware interrupts. That would take some sort of ramdisk containing the altered driver module and we can't do that with eFuse.
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.
I installed this and didn't see any improvement in battery life until I ran
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
It said it was still ondemand. I checked scaling_available_governors and smartass was not in there, so I went ahead and installed the zip again... still doesn't work.
I went ahead and took a look at /etc/startup/smartass.sh. The permissions were right, so I ran /etc/startup/smartass.sh. I then checked /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and it was set to smartass.
Can anyone shed some light on why this script is not running on boot? I'm running the leaked Motorola Gingerbread ROM if that makes a difference.
Spitemare said:
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.
Click to expand...
Click to collapse
I see. I'm guessing the way to hijack said calls would be through directly modifying memory, right? That definitely is not something that sounds easy to do.
I tried running smartass.sh through an init.d script... still nothing. I actually had to make the /etc/init.d/ directory, so I figured that init.d scripts aren't supported on the Motorola Gingerbread rom... strange. I'll look for somewhere else where I can run stuff on startup.
Look for /etc/install_recovery.sh. That file is run by /init.rc if it exists. It's how the overclock stuff gets loaded on Fission. What the update.zip does is back up that file if it exists and then append /etc/startup/smartass.sh to the end. Just add the following to the end of /etc/install_recovery.sh if the update.zip doesn't add it:
Code:
/etc/startup/smartass.sh

[Q] S-OFF... what now?

Hey all
First time poster long time lurker
I finally took the plunge and rooted my phone (using Revolutionary)
Sadly, I'm stuck!
nb. On the boot screen (volume+Power), it says S-OFF
What do I do now, if I want to install a ROM (or revert back to my old build)?
Thanks in advance
ps. I've downloaded and tried to use fre3vo, etc. but can't get my head round it
pps. sorry for the long winded post
Zofu said:
HOn the boot screen (volume+Power), it says S-OFF
What do I do now, if I want to install a ROM (or revert back to my old build)?
Click to expand...
Click to collapse
Christ, that wasn't a long winded post....!
Next step is to install a custom recovery and root your STOCK ROM.
Although if you choose to download and install CWM as part of the revolutionary process you may already have the custom recovery installed. In which case simply download a custom ROM (which all come pre-rooted) to your SD and then flash it, although ensure that you read all the installation instructions first.
If you didn't install CWM as part of the S-OFF process then look at my signature where there are a couple of links
1) adb & fastboot
download this and extract contents onto PC
2) Flash CWM & su via fastboot
follow instructions in this thread to flash both the custom recovery (ensure that you get the version for your device SAGA)
Then I'd suggest you enter CWM and take whats known as a Nandroid backup of your device.
Then you should be able to download any custom ROM you like.
Any questions then ask, you should never do any steps that you are unsure or uncomfortable with as you can do damage to your device!
Cheers for the reply, ben_pyett!
I'll make a start now
I know it's not that complicated a prcoess, but I kinda jumped in assuming it'd take 5 minutes, I guess
I've flashed the Cyanogen 7.1.0 RC by NeoLogix onto both mine and my wife's handsets... and I have to say it's VERY impressive!
Initially it doubled the battery life, and with some clever settings tweaks (which I'm more than happy to post here, menu by menu, if you end up using the same ROM) I've more than quadrupled the effective battery runtime.
ben_pyett said:
1) adb & fastboot
download this and extract contents onto PC
Click to expand...
Click to collapse
Ok I did this
ben_pyett said:
2) Flash CWM & su via fastboot
follow instructions in this thread to flash both the custom recovery (ensure that you get the version for your device SAGA)
Click to expand...
Click to collapse
I followed the instructions ("fastboot flash recovery recovery.img" -- where "recovery.img" was the Desire S CWM recovery) via my USB with the phone in Fastboot mode (white screen)
ben_pyett said:
Then I'd suggest you enter CWM and take whats known as a Nandroid backup of your device.
Click to expand...
Click to collapse
How do I enter CWM?
Do you mean turn my phone on normally and CWM app will be installed?
Seems I seriously need walking through this!
Grr
Here's the way I find best.... switch your phone OFF, but leave it plugged in via USB.
From your command prompt, type "adb reboot recovery"
The phone will then boot to recovery
Zofu said:
How do I enter CWM?
Do you mean turn my phone on normally and CWM app will be installed?
Seems I seriously need walking through this!
Grr
Click to expand...
Click to collapse
Sounds like you've made huge progress...
I'm assuming that you've also push'd the SU file while in fastboot? if not do that as well.
At this point you should decide which custom ROM you wish to install and download that and all its add-ons and place them on you SD card so that you are able to use them once you're in RECOVERY. You should probably take the time while the ROM downloads to read the install instructions that come with the ROM, that often involve running additional WIPE scripts etc....but each ROM is different.
Anyway back to the question you asked, how to enter CWM (clock work mod) which is your custom recovery.
You should normally boot your phone and then go into Settings->Power->fast boot and ensure that its un-ticked.
Easy Way
Install ROM Manager from the market and then choose the Reboot into Recovery Option (second one down from top) and voila!
Manual Way
Power Off your phone.
Turn on your phone by pressing Power button + Volume Down button together.
You should now see the white HBOOT screen, using the volume up & down buttons to flick through options and Power button as enter you should be able to find the RECOVERY option. go into that.
Don't worry once you have a custom ROM things will be easier as most customs have an Advanced power Menu which has reboot into recovery as an option.
Quick update:
ben_pyett said:
I'm assuming that you've also push'd the SU file while in fastboot? if not do that as well.
Click to expand...
Click to collapse
I have no idea what the above^ means!
Ok, I got into Recovery manually (black Revolutionary screen with menu)
What do I choose in the menu to install a ROM?
- reboot system now
- apply update from sdcard
etc.
Does the ROM have to be at the root of the SD?
Can the ROM be named anything you wish, or does it have to be named "update.zip"?
Still a little confused!
Cheers guys for your super help so far
Zofu said:
Quick update:
What do I choose in the menu to install a ROM?
- reboot system now
- apply update from sdcard
etc.
Does the ROM have to be at the root of the SD?
Can the ROM be named anything you wish, or does it have to be named "update.zip"?
Click to expand...
Click to collapse
This is the option that you need install ZIP from sdcard
The ROM can be called anything you want, I never bother renaming the ROM files that the cooks call them, so that I can easily identify which is which and it can be position in any location on the SD not just the root directory. Although try to avoid directories with spaces in for now.
Update.zip is something else so don't use that option.
Once you've done this I'd also download and install the CUSTOM recovery EXT4 as its much easier to use....you can do that by simply installing the following APK which you'll find in this post and that will install the new recovery for you.
best of luck...back in two hours.....got to go and watch MANCHESTER UNITED NOW!
Cheers Ben
Have fun!
*edit: fixed issue with ROM install*
I decided to give Cyanogen 7.1.0 RC by NeoLogix's ROM a try and it seems to be working fine
Thanks for the helps, guys!
ps. if wanted to install another ROM, do I need to uninstall the previous one (wipe it again?), or can I just copy another ROM over and install like I did before?
Zofu i suggest you flash virtuus unity! its a great sense 3 rom. i love it! it has brought my desire s to life!!
You shouldn't be swayed by any of our opinions with regards which ROM to choose, I'd suggest that you install all of them one after each and decide for yourself which one suits you most
Although first question is sense or no sense.
The reason why there are so many roms is because we all have such differing tastes
Enjoy
PS
There is no UN install task, but each ROM will have its own install instructions in the first post of the thread which will have it's own wipe recommendations
Swyped from HTC Desire S using XDA Premium
LaKraven said:
I've flashed the Cyanogen 7.1.0 RC by NeoLogix onto both mine and my wife's handsets... and I have to say it's VERY impressive!
Initially it doubled the battery life, and with some clever settings tweaks (which I'm more than happy to post here, menu by menu, if you end up using the same ROM) I've more than quadrupled the effective battery runtime.
Click to expand...
Click to collapse
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
To add to ben_pyett's suggestion... I wouldn't exactly just "install each one, one after another" as there is actually a finite number of times the ROM can be flashed before you start to damage the internal memory (sure, it's a high number, but why cause more wear than you have to, right?)
I'd suggest you read up on the ROMs before you decide to try them out! Take a look at what features they have, what people have to say about them (particularly looking for bugs and potential problems).
Hell, if you're lucky, you may even find an introductory video to some ROMs on YouTube, which will give you a little more insight into what to expect.
As Ben said, the first question is "To Sense, or not to Sense?"
As a matter of personal opinion, I've chosen "not to Sense" in favor of better battery runtime and the "cleaner" GUI.
Bombastc said:
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
Click to expand...
Click to collapse
I spent days trying to tweak the stock Desire S ROM (and again after the update I applied ~ a week ago) with quite literally no success!
Even with the most riggorous (performance and feature restricting) power management setup, I still couldn't get the thing to pass the 18 hour mark (which I only achieved with the help of Tasker, used to toggle Airplane Mode during my sleeping hours etc.)
Having switched to the CM7 ROM linked previously, and using nothing but a combination of changing its default settings, and SetCPU (to scale the CPU clock for superior power saving with literally NO performance hit), it'll now run for almost 48 hours between charges (more than sufficient, wouldn't you agree?)
I'll post a separate thread in here with a complete battery optimization guide for the aforementioned ROM.
Just to clarify, after more than 4 hours running on the battery (at least half of which with the display on and the phone in use) it has gone from full to just 90%, which in itself averages to about 40 hours of runtime.
Coupled with my SetCPU scaling, this adds ~8 more hours!
This means that, with moderately heavy use (though I haven't yet had time to test absolute runtime with HD 720p video playback just yet) you can expect a screen & WiFi ON time of 24 hours, with a standby time (again, with WiFi on) of a further 24 hours!
La Kraven - can you teach me how to dougie lol? You really quadrupled your batt? :O
Bombastc said:
La Kraven - can you teach me how to dougie lol? You really quadrupled your batt? :O
Click to expand...
Click to collapse
Yes.... and just to give you some comparrative reference:
Battery Use:
Mobile Standby: 74% (that's the GSM radio)
Wi-Fi: 12%
Phone Idle: 9%
Display: 4%
Android System: 2%
EDIT: The GSM registers heavily on "Mobile Standby" because I cannot get any cell reception where I live (AT ALL), so the GSM is idling, constantly looking for a carrier. If you're in a GSM (or better) environment, you can expect the "Mobile Standby" value to be substancially lower, most likely with other feautres such as Wi-Fi, Bluetooth or GPS leading the consumption values (dependant on what you've got enabled)
LaKraven said:
I spent days trying to tweak the stock Desire S ROM (and again after the update I applied ~ a week ago) with quite literally no success!
Even with the most riggorous (performance and feature restricting) power management setup, I still couldn't get the thing to pass the 18 hour mark (which I only achieved with the help of Tasker, used to toggle Airplane Mode during my sleeping hours etc.)
Having switched to the CM7 ROM linked previously, and using nothing but a combination of changing its default settings, and SetCPU (to scale the CPU clock for superior power saving with literally NO performance hit), it'll now run for almost 48 hours between charges (more than sufficient, wouldn't you agree?)
I'll post a separate thread in here with a complete battery optimization guide for the aforementioned ROM.
Just to clarify, after more than 4 hours running on the battery (at least half of which with the display on and the phone in use) it has gone from full to just 90%, which in itself averages to about 40 hours of runtime.
Coupled with my SetCPU scaling, this adds ~8 more hours!
This means that, with moderately heavy use (though I haven't yet had time to test absolute runtime with HD 720p video playback just yet) you can expect a screen & WiFi ON time of 24 hours, with a standby time (again, with WiFi on) of a further 24 hours!
Click to expand...
Click to collapse
Thx so much, HALF of that would be fine with me lol!
Bombastc said:
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
Click to expand...
Click to collapse
We are new to Android at some point, this is my first Android device.......but I've had many HTC Sense Windows mobile devices beforehand and most of the same things tend to apply.
I'd suggest as a first port of call you read this thread which is a GUIDE, and sticky for a reason kindly written by wnp_79, I learnt loads from reading this alone.
Don't expect to learn everything in a days....it takes weeks or months.....
just enjoy....and remember that we're all different have differing expectations and uses for the same devices so what suits one of us doesn't always suit the other.
ps
you shouldn't really go off topic like this.....if you need specific help say so and create a new thread or read the sticky threads which contain GUIDES and links to many useful resources. Don't expect to become an expert over night and attempt to learn as much as possible by simply reading before you risk damaging your device!

TUT - Use Set CPU to overclock your Android Smartphone

Looking for some ways to Overclock your device? Well here is a short post, which can guide you to use SetCPU and overclock your android smartphone.
Why to OVerclock using SetCPU:
The speed of your Android device is solely dependent on the processor of the device. Now every processor is set at a certain speed at which it processes the data. The more the clock speed, the more faster the processor operates, and hence faster the device. Overclocking means that you increase the clock speed of the processor over the limit it is set to operate. Now when you do so, it is certain that your device will function faster.
But the overclocking should be done with great care, and tactic, as if you do not follow the procedure properly, you might ending up bricking or even permanently damaging your phone’s processor. Now if you overclock the device too much, it might give heating issues, and it might even damage the hardware of the phone, or the processor specifically. Or if you down clock the device too much, it might not even boot up. So overclocking must be proceeded with care. Also in this tutorial we will be overclocking your device using SetCPU app. Follow the procedure below, to Overclock your device using setcpu. Also if you are looking to do some more android tweaks, get them here.
Pre- Requisites :
Before we begin the process to overclock your android smartphone using setcpu, first of all let us go through some things that need to be done before we start with the procedure.
Make sure the device is at least 70% charged, as we do not want that the device to shut down in the middle of procedure.
To overclock and use SetCPU you need to have root access, i.e., your android device needs to be rooted. SO if you haven’t rooted it yet, first go root it, and then come back.
Also overclocking your device, can be harmful for the device, so make a complete backup of the device before proceeding.
How to Use Set CPU to Over clock Processor :
So follow these steps to over clock your phone using the Set CPU.
First of all, install SetCPU app on your device.
Now, that you have finished the installation procedure, you need to launch the app.
Click on “Auto Detect Speeds” option.
Then grant the phone will ask you to grant the root access to the Set CPU app, confirm the root access.
Now you need to set the maximum and the minimum limits of the clock speed for your processor
You have to note that these speed limits should be balanced, i.e., not too high or too low. As it may cause your phone to behave abruptly. If it is too low, the phone may stop response, and if it is too high it may overheat, and even the processor might get permanently damaged. So it should be done carefully.
Also do not select the option “Bott on SET”, till you think the speed limits are stable.
Now when you are satisfied with the speeds, you need to choose the times when you want the Set CPU to start and over clock your phone, like while on user space, or on demand.
his was a short guide, on how to use SET CPU to over clock your processor. Also if in case, the phone gets into trouble, you need to reboot into the recovery mode, and then flash the backup you made via the recovery. You would get the phone recovered to the period, backup was made. Also if you face any more issues, you can always contact us via the comment section below.
i have samsung j1 2016 j120h its a spreadtrum variant of j1 2016. i am rooted all cpu tuning apps wont work the cpus stay the same even after applying setttings. and i noticed that my cpu0 and cpu3 are the only ones active. my soc is sc772se
Set CPU or KernelAuditor is FAKE, it make your device have a lot of ads. It only can limit cpu clock, choose cpu clock and CaN't OVER-OVERCOCK. The max stock frequency not rise (my english so bad), must flash custom kernel overclocked.

*ROOT ONLY* Honor 5X Marsmallow battery tweak.

Im not responsible for any behavior like the Note 7, if its explodes while applying the tweak its not my fault!
This tweak will edit a simple file so that the minimum cores get decreased and we wont get unnecessary battery drain
ROOT ONLY!
Manual Guide:
1. Make sure your device has root acces,
2. Install Root Browser from the playstore.
3. Open the app and navigate to > sys/devices/system/cpu/cpu0/core_ctl
4. Search for the file min_cpus make sure the permissions are set to rw-r-r (it showsup under the file name).
5. Open min_cpus and change the number '4' to '0', This will say to the CPU that a minimal of 1 cpu core is needed to be active instead of 4 all the time.
6. Save the file and navigate back to > sys/devices/system/cpu/cpu0/core_ctl and change the permissions back to r-r-r.
7. Your device will still run 'smooth' and safe some battery! You have to apply this every single reboot or need to make a init.d script and make it run every single reboot..
You can also use the provided script in the "Attached Files" section. If you use a script runner you dont have to follow the Manual guide everytime you boot.
Share what you think, any feedback is appreciated!
Thanks, so i did the steps 1 to 6, and the contents of that folder disappear, is that normal? I restart the phone and the files appear and i did the same steps the files disappear again.
danino22000 said:
Thanks, so i did the steps 1 to 6, and the contents of that folder disappear, is that normal? I restart the phone and the files appear and i did the same steps the files disappear again.
Click to expand...
Click to collapse
What content? Im not sure what you mean..
Demian3112 said:
What content? Im not sure what you mean..
Click to expand...
Click to collapse
The files inside core_ctl folder disappear.
danino22000 said:
The files inside core_ctl folder disappear.
Click to expand...
Click to collapse
It shouldnt what device do you have Kiw l21? MM or LP? Open kernel adiutor or something else and see how the cores behave make sure battery settings is on Performance. Not much what i can do other wise..
Kiw l24 MM last update from honor UK support page. For example in kernel adiutor if i want to change the min frequency to 200mhz or any other, the settings won't apply, it return to the original frequency after few secs.
SOT ?? @Demian3112
danino22000 said:
Kiw l24 MM last update from honor UK support page. For example in kernel adiutor if i want to change the min frequency to 200mhz or any other, the settings won't apply, it return to the original frequency after few secs.
Click to expand...
Click to collapse
You cant set big cluster. For small cluster go to sys/devices/system/cpu/cpu4/cpufreq/ and look for min freq set permissions to rw-r-r open it change value 800000 to 200000 save it change permissions back to r-r-r
kartrikpal said:
SOT ?? @Demian3112
Click to expand...
Click to collapse
Havent measured. I safe about 3-8% in an hour doing the same stuff youtube, google, whatsapp and facebook etc. It really depends on what you are doing.
Little cluster runs idle 800mhz with the tweak 200mhz
Big cluster has 8 cores active all the time, with this tweak 0 in idle/simple tasks. It only enables when needed
Just try it out yourself. If you dont like it remove kernal adiutor restart device and tweaks are undone
doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min
halfacannoli said:
doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min
Click to expand...
Click to collapse
Make site battery manager is on performance.. i dont Have this issue and i Just upgrades to B330
Demian3112 said:
Make site battery manager is on performance.. i dont Have this issue and i Just upgrades to B330
Click to expand...
Click to collapse
Thanks for the fast response. However, that did not work for me initially. I was able to resolve the issue and it looks like I was able to set the frequency for the big cores as well. As a preface, I have the L24 and updated to MM EMUI 4 through the zip that was found on the hihonor UK website. After the update I did a factory reset. I am just letting you know because some of things you described didn't work while other things did.
What did work was setting the Mincpu to 0, so that when idle only 1 core is running. This worked great, so thanks for that! However, in Kernel Aduiter, I had to set the governor to Interactive for it to use the other Big cores when I am using the phone. If I set it to ondemand, the other 3 big cores does not activate, only core 1 is used along with the 4 little cores.
What did not work per your instructions were setting the min frequencies for the little cores. Yes, I changed the Power option to performance, but every time I exited the kernel auditer, it would revert back to a min frequency of 800mhz.
After tinkering with the phone for a couple of days, I was able to set the min frequency to 200mhz for BOTH big cores and little cores and it seems that both settings are sticking. Throughout the 2 days, I did many changes so I have yet to narrow it down to what changes I did that made both changes stick. When I have some time I will try to reproduce the results and post on how I got it to work. I would also like to give it a few days to make sure that the changes stick.
---------- Post added at 10:22 PM ---------- Previous post was at 10:13 PM ----------
danino22000 said:
The files inside core_ctl folder disappear.
Click to expand...
Click to collapse
it disappears because permission was changed to r-r-r which is read only. change permission to include w (write) and execute, and you'll see it again
halfacannoli said:
doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min
Click to expand...
Click to collapse
Got to battery manager and set it to performance.
Can someone make an script to keep this installed upon boot? Thanks.
Robertleehadley said:
Can someone make an script to keep this installed upon boot? Thanks.
Click to expand...
Click to collapse
If i have time i will do it!
Nice tweak on changing 4 to 0 at min_cpus but Root Browser (w/Root and Grant) refused to save it so i used X-plore by Michal Baclk Version: 3.86.02 Build Date: 7/16/16 and it took perfectly!
Thanks for the other kernel adjustments too.
anyone ever make that bat file?
And has anyone tried setting CPU4 the same way as suggested for CPU0? By default, it is set to 1.
I'm also a little concerned I may not have understood the directions properly...
From what I read, it looks like you are ignoring the large cores and only modifying the little ones? Am I understanding that correctly?
And why can't we just tick the 'use this on boot' in kernel aduitor? Why does it need to be reset upon every boot? I mean, we are doing these steps with ROOT access, are we not? Shouldn't the file stay modified? I am quite confused... but very eager to get more battery life out of this... was shocked to see that all 8 cores are always on... and my device NEVER hit deep sleep or any of the slower frequencies all day!
No wonder I can drop to 85% within an hour. Sheesh... this blows.
Ok, I played with it some more...
Looks like Root access has nothing to do with modifying that file. Yes, you need root to modify it... but it never stays changed after a reboot. This tells me that this area must be a hardware toggle area. Meaning, there's some place with the default value stored, and is loaded from there to this location during boot.
I did my best to follow all these steps.
upon reboot, every single thing I put in is lost. Kernel Aduitor seems to lose my settings even if I check 'apply on boot'.
furthermore, all 8 cores are still on.
True, I *do* now see that all the big cores aren't *always* on... but it isn't very different from before doing these steps (at least now I can see a core or 2 shutoff for all of about a tenth of a second)
The little cores... they looked like they took the settings the best... until I closed Kernel Aduitor and reopened it... all the settings reverted.
Yep, waiting with anticipation for some guru who is best at putting something together to set all those freq.'s and such that will apply all of them and keep settings.
Very useful battery mod if it can be made to apply and hold up after restarts.
Yes the hotplug drivers and govenors change it back this is something within the kernal thst you cant edit without needing to flash another rom.. Im on CM13 and batttery has improved quite a bit.. Just give it a try its my daily driver now and its smooth as hell..
Demian3112 said:
Yes the hotplug drivers and govenors change it back this is something within the kernal thst you cant edit without needing to flash another rom.. Im on CM13 and batttery has improved quite a bit.. Just give it a try its my daily driver now and its smooth as hell..
Click to expand...
Click to collapse
Without or before flashing a better ROM, did this item ever get worked out whether by another way to make settings stick or a Huawei small update? Thanks for any advice.
Sent from my MT2L03 using Tapatalk

[Guide] Post-Root Common Issues, Bugs, and Fixes

This guide is meant to help those who have rooted their phones and are now finding it slow, laggy, messy, etc.
I've been seeing a lot of posts repeating common problems that have been fixed by other members of the forums, so I'll compile a list of the most common bugs and fixes for them (the ones that can be fixed) in this guide so people can refer to it instead of swamping dev threads with the same questions over and over again. The quicker we can get through the common problems, the quicker we can get to fixing the ones we don't have solutions to so far.
Disclaimer: After installing the ENG bootloader, you are going to experience less battery life. There are things we can do to improve this, but nothing I have discovered so far will get you back to stock battery life... except re-installing stock ROM. Also standard disclaimer that all of the fixes here are done at your own risk. I am not responsible for any of these fixes breaking your phone.
Bug #1: Phone is laggy after rooting the phone/Battery is down the tank.
Fix: The phone is (partially) lagging because the ENG bootloader automatically sets the CPU governor to "Performance." While this is supposed to lock the CPU frequency at the maximum values, it does cause a lot of heat and possibly throttling. Additionally, the max core clocks are set to 1.593Ghz instead of their actual maximums. Not every CPU Tuner will allow you to set the big cores separately, so look around for one that does if you don't want to use Kernel Toolkit.
First, use Flashfire to flash one of two zips provided by psouza4 on our sister Verizon Galaxy S7 (Edge) threads.
1. Kernel fixes & tweaks V15
2. Kernel fixes, tweaks, & Debloater
You need only flash one of these two zips. One additionally debloats the system, one does not. Choose whichever suits your needs.
What the zips do:
Adds a rotate button to the native gallery app.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
Removes bloatware and/or apps that can be downloaded from the Play Store and don't need to live in /system (fix+debloat version):
Next, install a CPU Tuner utility like Kernel Toolkit, then change the governor from "Performance" to "Interactive." Also change the max CPU frequency of the little cores to 1.593Ghz and the big cores to 2.150Ghz while you're at it. Leave the cores at their default minimum frequency. This will go a long way to improving the speed of the phone. Also make sure you that have the new settings to apply on boot. Every kernel manager should have this option somewhere.
Note: Although the max frequency in the settings screen will drop to some number, as long as you can see the CPU ramp up to the new settings in the information screen, then everything is fine. You can test the max frequency by turning the screen off and then back on.
Then, install sEFix and set entropy to "Ultra."
Lastly, install L Speed and:
Code:
-Main Tweaks: Turn on
-Battery Improvement
-OOM Killer
-Kernel Tweaks - "Light"
-CPU Tuner: Turn on
-CPU Optimizer
-LNET Optimizer: Turn on
-Google DNS
-Faster Streaming
-Faster Dormancy
-IO Tweaks: Turn on
-IO Boost
-Partition Remount
-RAM Manager
-Balanced
-Seeder
-Moderate
Their individual effects can be read up on here.
Bug #2: Weird "hurricane" icon in the corner.
Fix: This is related to the imsservice.apk which controls the RCS icon and the VoLTE icon being displayed. Someone has a modified version of the Note 5 imsservice.apk with these removed. You can find the apk HERE in the OP's attachment. HOWEVER, you will push this to a different location than the location mentioned in the guide there. You have two choices, you can either push the apk via ADB from you computer or you can copy the file using a root file manager.
ADB Method (Assumes you know what you're doing. Don't copy the code verbatim if you don't know what the command is doing):
Code:
adb remount
adb push imsservice.apk /system/priv-app/imsservice/imsservice.apk
adb reboot
Root File Manager Method:
Transfer the imsservice.apk to your phone. Anywhere where you'll remember the location is fine. Open the file manager with root compatibility and copy the file to /system/priv-app/imsservice/ and overwrite the imsservice.apk already in the folder.
Set permissions of the file to 0644 or rw-r--r-- depending on your file manager. You can set permissions using most file managers.
Restart the phone.
I've included the stock PD8 imsservice.apk as an attachment below if anyone has issues with the modified one from the guide.
Bug #3: Notification warning that system has been modified.
Fix #1: Disable com.samsung.android.securitylogagent & com.tmobile.pr.adapt using your favorite package disabler. This will hide all notifications associated with this app as well as the root check that you might have encountered.
Fix #2: This fix requires Xposed. You can follow the instructions to install Xposed HERE.
Then install the Xposed module NotifyClean, activate the module, and reboot the phone. You will then use this app to block the notification under the package com.samsung.android.securitylogagent by clicking on the package so that it is highlighted red. The notification should disappear!
Note: This app can also be used to hide the icon for WiFi Calling if it's annoying you. You can still use the WiFi calling function while hiding the notification.
Bug #4: I keep losing root.
Fix #1: Secure boot/startup has caused the loss of root. So make sure you DO NOT SETUP the secure boot option when you're first setting up the phone or any time afterwards. This is the same option that forces users to type in/swipe in their password on a screen with a black background. This is not the normal type/swipe your password on your lockscreen after a boot.
Fix #2: Disable Security policy updates. I've also heard that people who leave this option on lose their root after a couple of reboots. You can find this setting under:
Settings > Lock screen and security > Other security settings > Security policy updates > Automatic updates (Turn this setting off).
Fix #3: Disable auto-updates for apps in Google Play Store. It's possible that SuperSU auto-updated, breaking root.
Fix #4: Disable automatic updates for the phone. I don't think these run anyways on modified software, but it can't hurt. You can disable the applications responsible for automatic updates using Titanium Backup, EZ Disabler, or any other package disabler you know of. The packages to disable are:
com.sec.android.soagent
com.wssyncmldm
com.samsung.firmware.nfc
com.samsung.android.firmware.tsp
Bug #5napchat: Unable to log into Snapchat.
Fix #1: This happens if you attempt to login to Snapchat after installing Xposed. Just make sure you login to Snapchat prior to installing Xposed. Done.
Fix #2: If you've already installed Xposed, you can:
-Do a clean install through ODIN, and re-root your phone, install and log into Snapchat, then install Xposed.
-Uninstall Xposed by flashing THIS through Flashfire, uninstalling the Xposed framework app, and clearing the data on your Snapchat app. Then login to Snapchat and re-install Xposed.
Bug #6: WiFi passwords aren't being saved
Fix: Use a root file manager like Solid Explorer and go to /system and open/edit build.prop. Scroll down or use the "find" function to search for ro.securestorage=true and change it from true to false (ro.securestorage=false). Save the file. Done!
If you guys have any more bugs that you run into, please feel free to post them here. Anyone who knows of any additional fixes to these bugs or solutions to any bugs that others post, also feel free to add them in the comments and I will compile them into this guide when I get a chance.
I've included the PD8 imsservice.apk below if you need it
Reserved
Reserved
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
thegameksk said:
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
Click to expand...
Click to collapse
Not every CPU Tuner utility will let you set the individual big.LITTLE cores separately. Try using the one recommended or look for another one that does allow it. Kernel Toolkit is the only one that I remember off the top of my head. I'll also make an edit in the post to avoid further confusion.
hey all, does anyone have or has experienced your incoming calls not being recieved? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Great post! Unfortunately I'm having problems with smart view after rooting. Every time I try to screen mirror it works but it is extremely laggy making it unusable. This has only been an issue since root and I've tried mirroring to three different devices and it's the same with all of them. I followed the instructions in this thread to see if these tweaks would help but they didn't change my screen mirroring issue at all. Is anyone else out there experiencing this?
little help please.
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
cris_epic said:
hey all, does anyone have or has experienced your incoming calls not being received? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Click to expand...
Click to collapse
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
JKLIMES1 said:
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
Click to expand...
Click to collapse
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
JKLIMES1 said:
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
Click to expand...
Click to collapse
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Is this what you mean about the cores?
thegameksk said:
Is this what you mean about the cores?
Click to expand...
Click to collapse
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
h.nocturna said:
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
Click to expand...
Click to collapse
AWESOME!! changing the permissions did the job for me. Thanks.
h.nocturna said:
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
Click to expand...
Click to collapse
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
cris_epic said:
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Trying changing the permissions as mentioned, that worked perfect for me.
thegameksk said:
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
Click to expand...
Click to collapse
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
h.nocturna said:
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
Click to expand...
Click to collapse
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
thegameksk said:
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
Click to expand...
Click to collapse
This is the expected behavior. This just means that they will clock up to the max when there is a high load, but then drop back down to the lowest frequency to save battery when there is nothing to be done. Everything is working as it should.
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
thegameksk said:
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
Click to expand...
Click to collapse
Mines was hot just with normal usage. I used every tip and fix that people suggested but it was still pretty slow and lagged if I had a game running and a couple of more apps running. Battery was OK though.

Categories

Resources