I apologize if this has been asked and/or answered, but I could not find the answer on XDA or in this thread. Not even in a Google search. If I missed it, could someone direct me to it? I really did look. LOL
I was wondering if it would be possible for me to increase the brightness of the capacitive buttons on my Rezound permanently. I've installed NilsP ICS Business Sense ROM (I absolutely love it), but the buttons are too dim for my usage. I can go in and change the file "currents" in the /sys/devices/platform/leds-pm8058/leds/button-backlight directory, but it reverts back to a value of "2" after a reboot. Also, if I change the file "01tweaks" in the /system/etc/init.d directory, after a reboot, it also reverts back to a value if "2". Where in the system could I change that value so that it would become permanent? Or is it possible? Or would it be possible, even though I would prefer the above solution, to remove it completely so that it's back to stock values that the system controls?
Sent from my ADR6425LVW using xda premium
Personally, I would be careful how high you bump it. HTC sets that level for a reason.
You might burn them out over time with more current, and also your battery life will take a hit.
But if you can figure it out, go experiment. I haven't heard of anybody doing this before.
I'm not sure that that file is referring to the current in amperage. It's in with other files like "brightness" (value of 60) and "maximum" (value of 255). Also, if you look at the file "01tweaks", there is a section called "#dim-leds" that has an echo value of "2" that appears to be written to the file "currents".
I could be all wrong about this. And if someone knows, please let me know.
Other than that, I'm still looking for a fix for this issue.
Sent from my ADR6425LVW using xda premium
Anyone else have any ideas? I'm running out. LOL!
Sent from my ADR6425LVW using xda premium
I saw this app the other day, and by looking at the screen shots of it, you can do some tweaking of the Capacitive button brightness
http://forum.xda-developers.com/showthread.php?t=1719934
GrayTheWolf said:
Personally, I would be careful how high you bump it. HTC sets that level for a reason.
You might burn them out over time with more current, and also your battery life will take a hit.
But if you can figure it out, go experiment. I haven't heard of anybody doing this before.
Click to expand...
Click to collapse
They're just LEDs. They don't really burn out unless you physically damage them or give them way too much voltage.
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
mclass55 said:
I saw this app the other day, and by looking at the screen shots of it, you can do some tweaking of the Capacitive button brightness
http://forum.xda-developers.com/showthread.php?t=1719934
Click to expand...
Click to collapse
Doesn't work on mine on CM9.
scy1192 said:
They're just LEDs. They don't really burn out unless you physically damage them or give them way too much voltage.
Click to expand...
Click to collapse
That's what I said, is it not?
You could try this. This file, when placed in the /system/etc/init.d folder will change the leds to a dimmer value than stock. Maybe if you play with changing the shecho number you can achieve what you are after. I believe that a value of "0" is off, but not sure and I haven't played with it to find out.
Just unzip and let us know how it works out for you.
View attachment dimleds.zip
GrayTheWolf said:
That's what I said, is it not?
Click to expand...
Click to collapse
No, you said that HTC set the normal level for a reason. Running it at 100% all the time would not damage the LEDs though.
Related
Just something to try if you're using the perma-temp root. Grab Autokiller and set it to ultimate (and just for ****s and gigggles, I did the UI optimization that increases homescreen events to 60), and you'll immediately notice less RAM usage and further battery life.
It's pretty awesome
And no, Autokiller is not a task manager (although it can be used as one).
Findings:
250,275,300 Seems to be the most stable if you multitask a lot.
300,325,350 is for those of you who are like me and don't need to multitask (single app at a single time kind of user).
You can go higher, but be careful. For a test, I like to set it higher, turn off the screen, wait a bit for the minfree settings to close off apps, and then text yourself from another phone or from GVoice. If you recieve it, those values are good (depending on your phone usage). For me, as long as the messaging app can stay open and not get killed off, I'm perfectly happy.
Also, at the second set of values (the higher ones), I'm noticing a distinct speed and smoothenss increase in the Rosie carousel as well as the notifications pulldown.
Oh snap! When did you get here?
oohaylima said:
Oh snap! When did you get here?
Click to expand...
Click to collapse
Aha! A familiar face, always welcome to see you here
I decided screw it, got a good deal on a 3D with my early upgrade (wasn't due till June of next year) and honestly, I'm pretty damn happy with this out of the box.
Thanks, will give it a try.
I'm experimenting now with higher settings. I'm currently trying out 250,275,300.
LiquidSolstice said:
Aha! A familiar face, always welcome to see you here
I decided screw it, got a good deal on a 3D with my early upgrade (wasn't due till June of next year) and honestly, I'm pretty damn happy with this out of the box.
Click to expand...
Click to collapse
Welcome aboard brother! I can't wait to ticker with this device too. This weekend I'll be able to get away from work and try this out.
How much decrease in RAM usage did you notice with your finding?
Bumped it up to 275,300,325, still not stability issues yet.
oohaylima said:
Welcome aboard brother! I can't wait to ticker with this device too. This weekend I'll be able to get away from work and try this out.
How much decrease in RAM usage did you notice with your finding?
Click to expand...
Click to collapse
Well, right now, I have about 320 MB of free RAM. I get that "free RAM" is a performance myth, and that unused RAM is useless. But the benefit for me is less battery is being used.
this is good info, thanks
Keep in mind that the higher you go, the less stable multitasking will be. I'm kind of a "single app at a single time" kind of user, so I can afford to go quite high. For instance, if you set it really high, and start listening to music, and then go into your Gmail app, there's a chance that the music app might automatically be killed off.
Homescreen Optimization setting? That's not in this all is it? So how does that go. I'd like to try that one too.
Sent from my PG86100 using Tapatalk
felacio said:
Homescreen Optimization setting? That's not in this all is it? So how does that go. I'd like to try that one too.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
That's in the "Adanced Settings" section of Autokiller. TO find out what they all do, go here: http://andrs.w3pla.net/autokiller/kernel. Keep in mind, not all of them may make a difference on your phone.
The specific one I'm talking about is this:
UI
Increases "maximum-events-per-sec" to 60 for smoother Homescreen scrolling and transitions.
Click to expand...
Click to collapse
I haven't looked at the build.prop at all, so I don't know if this was already set or not.
LiquidSolstice said:
That's in the "Adanced Settings" section of Autokiller. TO find out what they all do, go here: http://andrs.w3pla.net/autokiller/kernel. Keep in mind, not all of them may make a difference on your phone.
The specific one I'm talking about is this:
I haven't looked at the build.prop at all, so I don't know if this was already set or not.
Click to expand...
Click to collapse
Oh duh. Didn't even notice the advanced spot in settings? Thanks. And I'll press thanks as soon as I get on my computer lol
Sent from my PG86100 using Tapatalk
I can't believe I forgot this app this was this was a must on my hero....
Sent from my PG86100 using XDA Premium App
Just a heads up, sometimes the perma-temp root doesn't always hold after a reboot. If it doesn't, your autokiller settings won't work until you re-root.
Can't wait till this temp-root dance is over
LiquidSolstice said:
Just a heads up, sometimes the perma-temp root doesn't always hold after a reboot. If it doesn't, your autokiller settings won't work until you re-root.
Can't wait till this temp-root dance is over
Click to expand...
Click to collapse
That's why in the advanced section, you make it apply the tweaks after 2 minutes, which should be enough time to get it all temp-rooted again
Good call on this liquid! Thanks for the heads up. Phone is running great!
Sent from my PG86100 using Tapatalk
Had to push mine from Ultimate to the next step down. Sense was having to reload into memory sometimes.
we'll see how that works. it was nice seeing 250mb free though. lol not sure how much battery it actually saved. have to test that tomorrow.
Idea for App:
Basically what I am looking for the app to do is incrementally raise the min and max settings for the CPU, change CPU governor to performance, and run stress test for 30 seconds to 1 minute. It would then repeat until all speeds are verified as good or the phone freezes or reboots. If either occurs then the app would tell the user the last speed that was stable. See here for what I posted in the Vipermod thread for more info of what I am talking about.
Is this possible? Has it already been made and I just can't find it?
qwerty017 said:
Idea for App:
Basically what I am looking for the app to do is incrementally raise the min and max settings for the CPU, change CPU governor to performance, and run stress test for 30 seconds to 1 minute. It would then repeat until all speeds are verified as good or the phone freezes or reboots. If either occurs then the app would tell the user the last speed that was stable. See here for what I posted in the Vipermod thread for more info of what I am talking about.
Is this possible? Has it already been made and I just can't find it?
Click to expand...
Click to collapse
stop being a cheapo and buy SetCPU... it has all that plus more. >.>
onl difference is you gotta step up... just do a native test per step... just because your phone can hit the frequency and survive doesnt mean that the CPU can have a load off with that step and then poof... . but yea... buy SetCPU, no more thread response.
Ok...?
Tilde88 said:
stop being a cheapo and buy SetCPU... it has all that plus more. >.>
onl difference is you gotta step up... just do a native test per step... just because your phone can hit the frequency and survive doesnt mean that the CPU can have a load off with that step and then poof... . but yea... buy SetCPU, no more thread response.
Click to expand...
Click to collapse
Ok. Not helpful at all but thanks, I guess. Already own SetCPU. Looking for something that will do it automatically like I initially said.
qwerty017 said:
Ok. Not helpful at all but thanks, I guess. Already own SetCPU. Looking for something that will do it automatically like I initially said.
Click to expand...
Click to collapse
really? you cant tell if your phone can run on a certain frequency by moving a slider while on performance governor? Good luck with finding any help.
Sigh...
Tilde88 said:
really? you cant tell if your phone can run on a certain frequency by moving a slider while on performance governor? Good luck with finding any help.
Click to expand...
Click to collapse
I was hoping you would at least do what you said and not reply to this thread anymore since you offer nothing. But since you can't I will explain. If you still don't understand then please follow your own advice.
I am requesting an app. Whether I can or cannot do the same thing with SetCPU is irrelevant. Not just me but a bunch of people are using the flashable overclock daemon for whatever the reason may be. I know I can manually change the settings to find out. I do not want to and I expect it is the same for others. Just as I use Battery Calibrator to remove the batterystats.bin file because it is easier to push a button and have it do the work, I want a program that will do what I am asking by just pushing a button rather than having to go through the terminal or install SetCPU.
qwerty017 said:
I was hoping you would at least do what you said and not reply to this thread anymore since you offer nothing. But since you can't I will explain. If you still don't understand then please follow your own advice.
I am requesting an app. Whether I can or cannot do the same thing with SetCPU is irrelevant. Not just me but a bunch of people are using the flashable overclock daemon for whatever the reason may be. I know I can manually change the settings to find out. I do not want to and I expect it is the same for others. Just as I use Battery Calibrator to remove the batterystats.bin file because it is easier to push a button and have it do the work, I want a program that will do what I am asking by just pushing a button rather than having to go through the terminal or install SetCPU.
Click to expand...
Click to collapse
yea i know what you mean... sorry, i really was being a bit of an ass now that i reread it. what you want is something to go to next step, benchmark, go to next step benchmark, and continue to do so until the phone cant handle it.
the problem is, [now this im not 100% but its an assumption], that the daemon is specifying a max value. So I can come up with two scenarios.
1.Though it isn't INSMOD (like the LoadableKernelModule) , it is defaulted on boot through init.d script. The only way to reload those scripts, would be to reboot. Perhaps a hot boot may work. So you would need the app to rewrite wake_max_freq, then reboot... then somehow test it (just a cpu load test app). the script would then need to change the default value to a higher one from a list [the one it just stepped up to], and then tell it if AndroidBoot=Fail to revert to last step (which it probably wont be able to do since the phone would lock on boot since you can default a frequency that is too high). Seems like alot of time to me...
2.I took too long to type this and forgot #2
i know it will eventually be done through a real OC'ing script ... but seriously... whats so bad about testing your device?i can test every step (starting at 192) in less than two minutes. Idk i may just be being a hardass since I find that a user should always test his labors. a computer can only say or show so much, your eyes and intuition cannot be processed.
Ok. Didn't realize it requires a reboot. From what it looked like to me it just read the 6 text files and ran it in real time. If it does require a reboot then I can see the problem you are talking about with having it boot loop every time it starts up after the bad setting is ran. Going to have to look some more into how the init.d is set up. Looks like I may just need to learn some shell scripting.
Sent from my PG86100 using Tapatalk
qwerty017 said:
Ok. Didn't realize it requires a reboot. From what it looked like to me it just read the 6 text files and ran it in real time. If it does require a reboot then I can see the problem you are talking about with having it boot loop every time it starts up after the bad setting is ran. Going to have to look some more into how the init.d is set up. Looks like I may just need to learn some shell scripting.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
im just assuming not 100% so dont get your hopes down
You want your capacitive buttons more dim, but don't want to go through the trouble of flashing a kernel? Fear not! Team Xposed has you covered.
It's a very simple process actually. (Thank you to joe85 and mwalt2 for their sources!)
There are three ways to achieve this.
-One of them requires init.d (the script will change the value upon boot)
-Second of them can be inserted into the kernel ramdisk
-Third of them can be done manually.
Let's start with the easiest, which is manually. With your phone connected to ADB, OR in a terminal emulator, simply type this in:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
I've taken the steps to insert it into my kernel ramdisk, and you can too. Just insert that line in bootcomplete.rc or where ever you feel comfortable in ramdisk.
Now, for those who want to use it as an init.d script, I've attached a flashable zip at the bottom, or you can do it yourself by using root explorer to edit any current scripts in your /system/etc/init.d folder and placing the same line in there.
I'd tinker with values in ADB first to find a value that fits you best. The flashable zip I'm attaching has the value set at 2.
NOTE: Make sure your kernel supports init.d if you choose to flash the zip. (Most of them do, it's just a disclaimer to cover my ass for the "it doesn't work" replies)
This was exactly what I was looking for, thanks for all the awesome tutorials Freeza!
Thanks man! Worked perfect.
Sent from my PG86100 using Tapatalk
Is there anyway, using the first method, to have it persist through reboots?
faugnom1 said:
Is there anyway, using the first method, to have it persist through reboots?
Click to expand...
Click to collapse
If the rom supports init.d, it will persist past reboots. It gets loaded each time the phone boots.
the flashable zip worked great thank u!!! i did try adb and i wouldnt work is there something im missing?i am normally pretty good with adb
This would be great to bake into a rom. Thanks for this script
I actually did the opposite. Since a few kernels or ROMS have the led dimmed already. I use this and change the value to 20 to keep it bright. Haha
I modded my leds green. So that makes them dimmer already.
Anyways, thanks for this!
freeza said:
You want your capacitive buttons more dim, but don't want to go through the trouble of flashing a kernel? Fear not! Team Xposed has you covered.
It's a very simple process actually. (Thank you to joe85 and mwalt2 for their sources!)
There are three ways to achieve this.
-One of them requires init.d (the script will change the value upon boot)
-Second of them can be inserted into the kernel ramdisk
-Third of them can be done manually.
Let's start with the easiest, which is manually. With your phone connected to ADB, OR in a terminal emulator, simply type this in:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
I've taken the steps to insert it into my kernel ramdisk, and you can too. Just insert that line in bootcomplete.rc or where ever you feel comfortable in ramdisk.
Now, for those who want to use it as an init.d script, I've attached a flashable zip at the bottom, or you can do it yourself by using root explorer to edit any current scripts in your /system/etc/init.d folder and placing the same line in there.
I'd tinker with values in ADB first to find a value that fits you best. The flashable zip I'm attaching has the value set at 2.
NOTE: Make sure your kernel supports init.d if you choose to flash the zip. (Most of them do, it's just a disclaimer to cover my ass for the "it doesn't work" replies)
Click to expand...
Click to collapse
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
It Works like a charm
Thanks !
It works like a charm.
At first, i've tested with adb to find the correct value for my needs.
And now with starting script my default value is now set to 6.
Sheers
cobraboy85 said:
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
Click to expand...
Click to collapse
That's just plain erroneous. Period. SteelROM has been running with the lights set at 2 for weeks, and battery life is fantastic. Simple logic will tell you less amps to a light results in less battery drain. So, if anything, dimming those LEDs will INCREASE your battery life!
freeza said:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
Click to expand...
Click to collapse
0 = off, 2 = dim. Same results I found a while back. However, 20 is the highest you could/should go. (it actually does matter!) This setting is for mA (AKA milliamps for those less electrically knowledgable). SO setting to over 20 could result in excess current going to the LEDs meaning unecessary heat and shortened battery life.
SteelH said:
That's just plain erroneous. Period. SteelROM has been running with the lights set at 2 for weeks, and battery life is fantastic. Simple logic will tell you less amps to a light results in less battery drain. So, if anything, dimming those LEDs will INCREASE your battery life!
Click to expand...
Click to collapse
you didn't think i was being serious did you....
hahaha
cobraboy85 said:
you didn't think i was being serious did you....
hahaha
Click to expand...
Click to collapse
I noticed after the lulz part haha
cobraboy85 said:
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
Click to expand...
Click to collapse
wipe data/system/boot/wimax/sd/sd-ext/a window or two
Then flash a kernel from the EVO 4G section. You'll be as good as new!
freeza said:
wipe data/system/boot/wimax/sd/sd-ext/a window or two
Then flash a kernel from the EVO 4G section. You'll be as good as new!
Click to expand...
Click to collapse
Bro... I was kidding lol. The sarcasm was because people always do that right after flashing a rom..... because they are retarded
cobraboy85 said:
Bro... I was kidding lol. The sarcasm was because people always do that right after flashing a rom..... because they are retarded
Click to expand...
Click to collapse
I know, as was I
Are these values supposed to stick after a reboot if done manually? I was just wondering because I tried the manual way and reset my phone and the leds went back to the normal brightness.
jstn76rs said:
Are these values supposed to stick after a reboot if done manually? I was just wondering because I tried the manual way and reset my phone and the leds went back to the normal brightness.
Click to expand...
Click to collapse
They stick if you add a script to init.d or init.post_boot.sh or kernel ramdisk
freeza said:
They stick if you add a script to init.d or init.post_boot.sh or kernel ramdisk
Click to expand...
Click to collapse
thanks for the response. I have one little request would you be able to make a flashable zip for me with it set to 4.
I know that you can change the governor speed in the settings, and its set at minimum 216 and maximum at 1000. What is the risk of increasing the minimum to say over three or four hundred? At what point will it become unstable or crash? I know it is different for every kernel, I'm just looking for a good, safe setting. Thanks for any input.
Sent from my MB870 using Tapatalk
It won't crash from increasing the minimum speed, because there is no overclocking occurring. Increasing the minimum speed is safe; however, you will notice a decrease in battery life from increasing the minimum speed.
I tried to increase it, but it won't come off of 216. Do I have to change another setting to make it take?
Sent from my MB870 using Tapatalk
Lord Nykon said:
I tried to increase it, but it won't come off of 216. Do I have to change another setting to make it take?
Sent from my MB870 using Tapatalk
Click to expand...
Click to collapse
Yeah doesn't work.
Sent from my MB870 using xda premium
I seem to have noticed that even though the setting appears yo have not changed, the phone had dramatically increased in speed.
Sent from my MB870 using Tapatalk
You can't overclock it because our kernel doesn't support it. Nothing you can do will change it. The only way we'll ever be able to make use of those settings is if we get an unlocked bootloader. Then a custom kernel.
Lord Nykon said:
I seem to have noticed that even though the setting appears yo have not changed, the phone had dramatically increased in speed.
Sent from my MB870 using Tapatalk
Click to expand...
Click to collapse
You must have done what 7 billion i7 3960x's would take 103,227,037,000,000,000,000,000,000,000,000,000,00 0,000,000,000,000,000,000,000,000,000 years to do, and accidentally cracked your bootloader and accidentally wrote and flashed a custom kernel, all without realizing it.
I don't appreciate the sarcasm. I never said I cracked anything, nor did I EVER say I unlocked a kernel that devs with a million times more ability than me could bot do. If I was able to accomplish such things, why would I even be on here asking for help? My phone does perform better with minimum set up, but I NEVER said it was like a new phone. I am a relative noob to this, and I know my limitations. So, if all you have is a smarta** comment, keep it your self.
Lord Nykon said:
I don't appreciate the sarcasm. I never said I cracked anything, nor did I EVER say I unlocked a kernel that devs with a million times more ability than me could bot do. If I was able to accomplish such things, why would I even be on here asking for help? My phone does perform better with minimum set up, but I NEVER said it was like a new phone. I am a relative noob to this, and I know my limitations. So, if all you have is a smarta** comment, keep it your self.
Click to expand...
Click to collapse
Oh come on, get the stick out of your butt. I was just teasing because you said the phone was much faster after trying to change it. Can we still be besties?
LOL, you got it.
Hoping to get a stable zip up for people that wish to try to maximize battery life
This is my phone. Tried with another and it didn't like it so much. Work in progress. Lola
https://youtu.be/Bj8uPgGd6uw
Hoping to get 20 hours screen on time. Around 3 days worth.. Will see
Found your thread. We can talk here now. Hit me up if you need assistance.
Sent from my C525c using Tapatalk
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Moody66 said:
Hardware wise. Other phone didn't like lower voltage. Lol
Click to expand...
Click to collapse
Is the other phone on CM, or more simply put, using a custom kernel?
Sent from my C525c using Tapatalk
SHM said:
Found your thread. We can talk here now. Hit me up if you need assistance.
Sent from my C525c using Tapatalk
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Is the other phone on CM, or more simply put, using a custom kernel?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Same as mine. Had to put it back though. Its the wife's. I know no CPUs are exact on capabilities. Hers wasn't as forgiving. Still have tweaking to do. Lol. Less voltage drop. Won't be as huge on savings though. I figured as long as these have been made they would be more refined. Sigh. Running toms original release. Just playing with governors and voltage.
Dropped max down just a little. One of the guys that does beanstalk taught me a little. Wish they would do a bean build. I started but the old laptop is having issues. Bad ram i think. Will replace it tomorrow and try again. If I have to i will throw everything on my newer laptop. Hate tearing windows out of it. Lol. Got to much to do today with wife and kid both sick
Here is what I have do far on this charge.
Moody66 said:
Here is what I have do far on this charge.
Click to expand...
Click to collapse
You had 7 hours of screen time and only dropped 27% What are you using to achieve this?
MikeyLee said:
You had 7 hours of screen time and only dropped 27% What are you using to achieve this?
Click to expand...
Click to collapse
Modifications. Over 10 hours now and am at 62%. Lol
How long before you're ready to reveal these mods to us?
Moody66 said:
Modifications. Over 10 hours now and am at 62%. Lol
Click to expand...
Click to collapse
When can we test this out?
MikeyLee said:
When can we test this out?
Click to expand...
Click to collapse
Still working on it. All phones are different. Some CPUs handle voltage changes better than others.
https://drive.google.com/file/d/0B97V_YadJs2baVJZSlVJMUJPZjg/view?usp=docslist_api
Over 12 hours and I am at 55% battery. This thing may make 24 hours screen on. Lol
Looking forward to this when it's available
MikeyLee said:
Looking forward to this when it's available
Click to expand...
Click to collapse
OK. 50% battery and I have 13 hours 43 minutes screen on. 42 hours off charge. For three mates total to tinker with. Guess I will see what the lowest I can make that all three will run properly on.
Moody66 said:
OK. 50% battery and I have 13 hours 43 minutes screen on. 42 hours off charge. For three mates total to tinker with. Guess I will see what the lowest I can make that all three will run properly on.
Click to expand...
Click to collapse
Dang man let me test this lol
Done a lot of digging to find a flashable that allows the user to make adjustments to voltages and such for a device of similar hardware. Starting to think there isn't one. Lol all phones being different it really needs to be tweakable by the user. What works fine on my mate 2 doesnt for another mate 2 here. Ideas?
Moody66 said:
Done a lot of digging to find a flashable that allows the user to make adjustments to voltages and such for a device of similar hardware. Starting to think there isn't one. Lol all phones being different it really needs to be tweakable by the user. What works fine on my mate 2 doesnt for another mate 2 here. Ideas?
Click to expand...
Click to collapse
This sounds promising. I hope someone can some up with something soon!
---------- Post added at 11:57 AM ---------- Previous post was at 11:07 AM ----------
Out of curiosity, what sort of issues did you see with one device that you didn't see with the other?
MikeyLee said:
This sounds promising. I hope someone can some up with something soon!
---------- Post added at 11:57 AM ---------- Previous post was at 11:07 AM ----------
Out of curiosity, what sort of issues did you see with one device that you didn't see with the other?
Click to expand...
Click to collapse
And what changes were made to the first MT2?
Maybe a flashable wouldn't be ideal given the issues found amongst different devices. Possibly a guide using your tweaks as a maximum base line would be doable along with mentioned recommendations for medium and minimum modifications. Maximum being the best battery life but could result in crashes from some and not other, medium being the ideal inbetween that should suffice for everyone (theoretically speaking), and minimum meaning it will certainly work for everyone but battery life will have a slight improvement. Just brainstorming though.
However, if a flashable zip is what you seek for which would allow users to choose some options then may I suggest making an Aroma Flashable Zip?
Sent from my C525c using Tapatalk
SHM said:
Maybe a flashable wouldn't be ideal given the issues found amongst different devices. Possibly a guide using your tweaks as a maximum base line would be doable along with mentioned recommendations for medium and minimum modifications. Maximum being the best battery life but could result in crashes from some and not other, medium being the ideal inbetween that should suffice for everyone (theoretically speaking), and minimum meaning it will certainly work for everyone but battery life will have a slight improvement. Just brainstorming though.
However, if a flashable zip is what you seek for which would allow users to choose some options then may I suggest making an Aroma Flashable Zip?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
+1
SHM said:
Maybe a flashable wouldn't be ideal given the issues found amongst different devices. Possibly a guide using your tweaks as a maximum base line would be doable along with mentioned recommendations for medium and minimum modifications. Maximum being the best battery life but could result in crashes from some and not other, medium being the ideal inbetween that should suffice for everyone (theoretically speaking), and minimum meaning it will certainly work for everyone but battery life will have a slight improvement. Just brainstorming though.
However, if a flashable zip is what you seek for which would allow users to choose some options then may I suggest making an Aroma Flashable Zip?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Excellent idea. Set back to defaults and it sureeee made a difference. Screenshots supplied.
Lol. You can clearly see it in the pics.
Moody66 said:
Excellent idea. Set back to defaults and it sureeee made a difference. Screenshots supplied.
Lol. You can clearly see it in the pics.
Click to expand...
Click to collapse
Impressive. Like I said I'm willing to test it out if you want to send me some settings recommendations and whatever else I would need.