I have been searching the forum but i cannot seem to get any answers to this.
I have installed null 23 on my GG V1 with excitement that i would be able to tether Bluetooth to my GG so i can use stock apps etc on my wrist.
I have it up and working but it becomes insanely hot after around 4 minutes or so,to the degree of feeling like it will explode any minute.
So having Bluetooth tethering using the wifi spoof is pointless then if the watch overheats and needs to be turned off.
Has anyone else experienced this or found a fix for it please,as all the hype to use google,apps etc seem pointless.
warrencoakley said:
I have been searching the forum but i cannot seem to get any answers to this.
I have installed null 23 on my GG V1 with excitement that i would be able to tether Bluetooth to my GG so i can use stock apps etc on my wrist.
I have it up and working but it becomes insanely hot after around 4 minutes or so,to the degree of feeling like it will explode any minute.
So having Bluetooth tethering using the wifi spoof is pointless then if the watch overheats and needs to be turned off.
Has anyone else experienced this or found a fix for it please,as all the hype to use google,apps etc seem pointless.
Click to expand...
Click to collapse
I installed null a couple of days back and don't have this problem. my phone however went into meltdown, and it was due to the phones lookout security not knowing what was going on.
delboydell said:
I installed null a couple of days back and don't have this problem. my phone however went into meltdown, and it was due to the phones lookout security not knowing what was going on.
Click to expand...
Click to collapse
Really i have had numerous people who have rooted their Galaxy Gear who have said when they tether on the null rom the watch heats up,so your saying that that does not happen with yours? So you can keep the tethering going for a long time on the watch with no issues?
warrencoakley said:
Really i have had numerous people who have rooted their Galaxy Gear who have said when they tether on the null rom the watch heats up,so your saying that that does not happen with yours? So you can keep the tethering going for a long time on the watch with no issues?
Click to expand...
Click to collapse
Yes mine is fine I used the video mix app and watched about 15 mins of the new robocop film without issues
warrencoakley said:
I have been searching the forum but i cannot seem to get any answers to this.
I have installed null 23 on my GG V1 with excitement that i would be able to tether Bluetooth to my GG so i can use stock apps etc on my wrist.
I have it up and working but it becomes insanely hot after around 4 minutes or so,to the degree of feeling like it will explode any minute.
So having Bluetooth tethering using the wifi spoof is pointless then if the watch overheats and needs to be turned off.
Has anyone else experienced this or found a fix for it please,as all the hype to use google,apps etc seem pointless.
Click to expand...
Click to collapse
i had this issue too, it heats up in 3 to 4 min. i can tell you why!
while you are tethering, go to voltage control and there you can notice that the cpu is fully loaded.
i solved that by putting the governor to "power save" and the minimal power to 600 MHZ. in this way, cpu will stick to the minimal power that you defined.
i will try to change the kernel to "triangulum" and give you feedback for that.
Issa Eid said:
i had this issue too, it heats up in 3 to 4 min. i can tell you why!
while you are tethering, go to voltage control and there you can notice that the cpu is fully loaded.
i solved that by putting the governor to "power save" and the minimal power to 600 MHZ. in this way, cpu will stick to the minimal power that you defined.
i will try to change the kernel to "triangulum" and give you feedback for that.
Click to expand...
Click to collapse
OK i will try that and see if it stops the over heating but i would love to hear some feedback on the triangulum. Thanks
delboydell said:
Yes mine is fine I used the video mix app and watched about 15 mins of the new robocop film without issues
Click to expand...
Click to collapse
Did you do anything within null 23 or settings? in order to reduce the heat completely? What way are you tethering?
Issa Eid said:
i had this issue too, it heats up in 3 to 4 min. i can tell you why!
while you are tethering, go to voltage control and there you can notice that the cpu is fully loaded.
i solved that by putting the governor to "power save" and the minimal power to 600 MHZ. in this way, cpu will stick to the minimal power that you defined.
i will try to change the kernel to "triangulum" and give you feedback for that.
Click to expand...
Click to collapse
OK i done that and it seems to be still heating up. DO i need to change the scheduler to anything?
Issa Eid said:
i had this issue too, it heats up in 3 to 4 min. i can tell you why!
while you are tethering, go to voltage control and there you can notice that the cpu is fully loaded.
i solved that by putting the governor to "power save" and the minimal power to 600 MHZ. in this way, cpu will stick to the minimal power that you defined.
i will try to change the kernel to "triangulum" and give you feedback for that.
Click to expand...
Click to collapse
OK tried it a few times,it doesn't hit up as much but there is some heat there. Am i doing anything wrong?
Can't really help other than to say I haven't had any heating issues
warrencoakley said:
OK tried it a few times,it doesn't hit up as much but there is some heat there. Am i doing anything wrong?
Click to expand...
Click to collapse
no there is nothing wrong, it's just heat bcz the cpu stick to 600 MHZ all the time while the tethering is on.
i tried triangulum for some time, i found the same thing! the cpu is fully loaded untill you limit his power by the same procedure.
the thing is you can apply power save with minimal power to 200 MHZ and it will never heat! but you will face a huge lag !!
i couldn't find any other way.
Issa Eid said:
no there is nothing wrong, it's just heat bcz the cpu stick to 600 MHZ all the time while the tethering is on.
i tried triangulum for some time, i found the same thing! the cpu is fully loaded untill you limit his power by the same procedure.
the thing is you can apply power save with minimal power to 200 MHZ and it will never heat! but you will face a huge lag !!
i couldn't find any other way.
Click to expand...
Click to collapse
I've been tethered with my Gear for about 9 hours and I haven't noticed heating. I'm mostly tethered, with some random sync going in the background, but it's never truly hot.
warrencoakley said:
Did you do anything within null 23 or settings? in order to reduce the heat completely? What way are you tethering?
Click to expand...
Click to collapse
when I 1st installed null, I didn't alter any settings (about processer and cores) as I don't mess with things I don't understand. I also am in the uk and have teathering as standard on my S4 so I didn't install the extra stuff for doing that? perhaps that's the problem.
Related
Im so happy Have run the battery down low & not experianced any problems locking up when waking up from battery (provided you dont set the mhz too low when you suspend!!! It doesnt "lock up" so much as takes an eternity to wake back up, haha)
No good settings for you (running automatic voltage), 528mhz for 10 seconds, 245.76 system idle, 122.88mhz on backlight off, 61.44mhz on suspend.
19mhz suspend takes too long to wake to be worth it.
Anywho... Unplugged from the charger around 10pm last night @ 100%. Still on 85% almost 12 hours later! (haven't really used the phone much until right now hah)
http://forum.xda-developers.com/showthread.php?t=507212
http://www.nuerom.com/BlogEngine/post/2009/05/09/nueDynamicClock-13.aspx
Works out overall to over > 2 more days of standby VS what I was getting yseterday. Killer!
Fast enough underclocked @ 61mhz to play mp3/aac/htc FM player audio no skipping or problems.
Gotta love that LoL!
Personally, got it set to 528mhz for 10 seconds, then 61mhz after for anything else.
Don't think it is working for me. Says....
Current processor speed and voltage:
0.00 MHz @1.1V
Confirmed! It worked but it didn't help to improve my battery even i ran at power saving mode.
I bricked my phone doing some stupid registry edit (it was stupid... should have known better... Had Hex selected instead of Dec) anyways hard reset my phone installed everything including this and now it works ... I love happy accidents lol
i try to install this and it says it is being blocked by something on the phone? it says it will try to fix but needs to restart and then nothing? any help
anybody else have a problem installing this?
DadamsJR said:
anybody else have a problem installing this?
Click to expand...
Click to collapse
Down this file below and install it before installing nueDynamicClock
thank you very much! Davey
leonarderman said:
Down this file below and install it before installing nueDynamicClock
Click to expand...
Click to collapse
That did the trick for me
Seems to lock up my phone coming out of suspension. I have tried the settings on the first post but seems to always lock up. Timmay!!!
Hi, I recently got a data plan for my vogue and signed in to thr Google account, as well as downloaded a few apps. What I find is that without even touching my phone my battery drains dramatically (about half way in four hours). I had data enabled before, it's just that I never used it. Anybody know why this is?
Data sync is off, and background data is off as well.
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
manifest3r said:
Hi, I recently got a data plan for my vogue and signed in to thr Google account, as well as downloaded a few apps. What I find is that without even touching my phone my battery drains dramatically (about half way in four hours). I had data enabled before, it's just that I never used it. Anybody know why this is?
Data sync is off, and background data is off as well.
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
how old is your battery?
almost 2 years old now, I know that takes a toll too...
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
Currently the phone runs at full clock speed all the time.
Back when the kernel had the clock speed and voltage reducing (late feb/early march), I used to get 48-56 hours out of the battery with data on.
Lately, over the past few weekends, I've been only able to get 36 hours. Sucks if I forget to charge my phone overnight.
These numbers are based on when the phone actually shut off due to no more power, not the battery gauge itself (it has been incorrect in the past and may still be).
Try the 2/22 kernel. See if it helps.
You'll lose features, but let me know if it improves anything. I intend to check this out in the future.
You can also open a terminal app in a current kernel and do:
Code:
su
echo 1 > /sys/module/board_htcvogue/parameters/slow_clock_when_lcd_off
echo 1 > /sys/module/pm/parameters/slow_clock_when_idle
Sleep and wake up to make it take effect. This will do the same as the 2/22 kernel.
Perhaps Myn can make this a RogueTools startup option?
NOTE:
1. This was disabled because it didn't work on some phones (caused them to freeze -- worked fine on mine).
2. Don't use this with overclocking! Bad things may result (I haven't checked the code).
jnadke said:
Currently the phone runs at full clock speed all the time.
Back when the kernel had the clock speed and voltage reducing (late feb/early march), I used to get 48-56 hours out of the battery with data on.
Lately, over the past few weekends, I've been only able to get 36 hours. Sucks if I forget to charge my phone overnight.
These numbers are based on when the phone actually shut off due to no more power, not the battery gauge itself (it has been incorrect in the past and may still be).
Try the 2/22 kernel. See if it helps.
You'll lose features, but let me know if it improves anything. I intend to check this out in the future.
You can also open a terminal app in a current kernel and do:
Code:
su
echo 1 > /sys/module/board_htcvogue/parameters/slow_clock_when_lcd_off
echo 1 > /sys/module/pm/parameters/slow_clock_when_idle
Sleep and wake up to make it take effect. This will do the same as the 2/22 kernel.
Perhaps Myn can make this a RogueTools startup option?
NOTE:
1. This was disabled because it didn't work on some phones (caused them to freeze -- worked fine on mine).
2. Don't use this with overclocking! Bad things may result (I haven't checked the code).
Click to expand...
Click to collapse
I'd love to add this to RogueTools but I am not sure if this is something that dzo will address in the kernel.
dzo: Please let me know. I don't want to step on your toes. I have no probs adding this to RogueTools but if you have plans for this I'll stay clear.
myn said:
I'd love to add this to RogueTools but I am not sure if this is something that dzo will address in the kernel.
dzo: Please let me know. I don't want to step on your toes. I have no probs adding this to RogueTools but if you have plans for this I'll stay clear.
Click to expand...
Click to collapse
Actually I have plans for this, however it won't be fixed in the near-term. You could probably add it to RogueTools for now.
I would like to get some form of cpufreq support working on the vogue. I've already talked with dzo in the past about adding cpufreq support, he didn't have much interest in implementing it.
I've never tested scientifically if these values actually make a difference. Technically, as dzo mentions, the clocks are all turned off when the device is idle (i.e. truly sleeping). However, there are cases where the clock-reducing would have an effect when linux is idling, but the processor hasn't slept yet. This would happen if an app is repeatedly waking up the device to sync.
My observations are entirely empirical. I used to get really good battery life across the board until I upgraded my kernel past 2/22 (I used that one up until late March).
I'll use the phone for a while with clock idling turned on and see if my battery life improves.
jnadke said:
Actually I have plans for this, however it won't be fixed in the near-term. You could probably add it to RogueTools for now.
I would like to get some form of cpufreq support working on the vogue. I've already talked with dzo in the past about adding cpufreq support, he didn't have much interest in implementing it.
I've never tested scientifically if these values actually make a difference. Technically, as dzo mentions, the clocks are all turned off when the device is idle (i.e. truly sleeping). However, there are cases where the clock-reducing would have an effect when linux is idling, but the processor hasn't slept yet. This would happen if an app is repeatedly waking up the device to sync.
My observations are entirely empirical. I used to get really good battery life across the board until I upgraded my kernel past 2/22 (I used that one up until late March).
I'll use the phone for a while with clock idling turned on and see if my battery life improves.
Click to expand...
Click to collapse
All the tests I have done suggest that changing the clock when the device is on has no effect on power consumption. We are lucky because the battery reports power consumption. On idle the cpu does a SWFI which stops the CPU clock (and some other clocks too). What would make a difference is implementing power collapse on idle (CPU is completely powered down just like when asleep) and I have thought about doing this. It's quite a bit of work and wince doesn't do this so perhaps it's not reliable. I might do some tests to see how much power it would save.
Well, here's an odd question.
I really want to drain my battery, preferably quite fast. At the moment I've got it on full brightness, no screen timeout, running a particle simulator, but it's dropping quite slowly. I want my battery to feel the burn! Are there any apps that people would suggest to absolutely kill my battery?
I'm actually considering writing an app that kills CPU, accesses the net, attempts to connect to GPS etc etc... Could make my life easier.
Soo simple just connect to ur wifi or 2g network i will drain automatically
Kamilabano said:
Soo simple just connect to ur wifi or 2g network i will drain automatically
Click to expand...
Click to collapse
Nope, I'm talking heavy duty, 20% per half hour drain.
load maps in the background..turn gps data wifi..livewallpaper..play music while playing games.. wala! battery drain so fast..
Just turn everything on and play with mmorpg like pocket legend with 3G connection. I think you Will drain from full to empty in about 2 hours
Sent from my GT-I9000 using XDA App
Hmm.... While most of these are good solutions, they all require active use of the phone. Anything that I can set and forget?
set the phone to 'never sleep' under settings.
the like said above, leave as many apps running, music, play a 720p video,
Leave camcorder running, gps on, wifi, everything you can imagine,
then leave it, If the phone wont sleep, the apps should stay running, unless RAM gets low
overclock to 1.6ghz and do other stuffs and it will go like a rocket
or if u r total nuts then connect + to the -
samiulislam16 said:
overclock to 1.6ghz and do other stuffs and it will go like a rocket
or if u r total nuts then connect + to the -
Click to expand...
Click to collapse
Ah yes, overclocking, thanks for that tip.
And perhaps I should find a nice resistor to do that...
montymintypie said:
Hmm.... While most of these are good solutions, they all require active use of the phone. Anything that I can set and forget?
Click to expand...
Click to collapse
Play a movie at full brightness
montymintypie said:
Well, here's an odd question.
I really want to drain my battery, preferably quite fast. At the moment I've got it on full brightness, no screen timeout, running a particle simulator, but it's dropping quite slowly. I want my battery to feel the burn! Are there any apps that people would suggest to absolutely kill my battery?
I'm actually considering writing an app that kills CPU, accesses the net, attempts to connect to GPS etc etc... Could make my life easier.
Click to expand...
Click to collapse
Download Stability test from Market.Fastest way to drain battery
malcho said:
Download Stability test from Market.Fastest way to drain battery
Click to expand...
Click to collapse
Hey, this is EXACTLY what I was looking for, thanks! In fact, I may also go ahead and overclock now I have this.
You could also try downloading something with 3G in the background when running Stability test.
Turn on wifi/bluetooth/gps and download a large file too
montymintypie said:
Hey, this is EXACTLY what I was looking for, thanks! In fact, I may also go ahead and overclock now I have this.
Click to expand...
Click to collapse
It's no problem.Enjoy
Stock JVR with Semaphore 1.6.0bm
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min( 652800) Max( 652800) Max.screen off(300mhz)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
Installed gsam for more meaningful data logging.
Unchecked Auto Sync Data in the Data Usage settings
Changed CPU clock min/max 652800
Installed Deep sleep battery saver Xposed module. (on slumber profile) buts phone into deep sleep when screen is off.
If i remember anything else i did on here, i'll post it.
(sorry its taking so long for replies/updates, "new user status" prevents my posts 5 minutes in between.) (hard to believe, been a member since 2011, just lurked alot.)
*May have found lower limit on the CPU, no instability as of yet, however phone is acting a bit erratic, looking into this currently. (booting takes FOREVER. this is a problem.)
*Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
*Changed CPU freq. to min max 652800 based on advice of the community.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
gh0stpirate said:
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min(960000) Max(stock) Max.screen off(157440)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
If i remember anything else i did on here, i'll post it.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
Click to expand...
Click to collapse
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
bblzd said:
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
Click to expand...
Click to collapse
Thanks for the tips! heres what i changed:
installed gsam for more meaningful data logging.
unchecked Auto Sync Data in the Data Usage settings
changed CPU clock min/max 300mhz
Zainiak said:
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
Click to expand...
Click to collapse
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
gh0stpirate said:
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
Click to expand...
Click to collapse
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
bblzd said:
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
Click to expand...
Click to collapse
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
gh0stpirate said:
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
Click to expand...
Click to collapse
Unfortunately I do not, just speculation based off what I've seen when monitoring current draw (using Current Widget) and the battery percentage before and after a reboot.
I do have shots demonstrating low idle drain with Auto Syncs and Locations disabled. On average I'd say my drop is about 1% over 5 hours of deep sleep, but it's always hard to tell because there's no way for me to know exactly when it drops without active logging which would interfere with the phone's deep sleep.
Generally speaking a reboot uses ~1% of your battery. If you're locking your CPU to run at only 300mhz I would just leave it on the entire time. Especially if mobile data is off and so is WiFi. Make sure you go into Settings > WiFi > *Touch the 3-dot menu* > Advanced > Disable "Scanning Always Available". I lose about 1-2% in airplane mode overnight over clocked with high quality sound driver from Viper4Android. Plus the Google now hotword activated everywhere but lock screen.
A while back I did a test with my N5 to purposely nerf its power to see how long of a SoT I could get with it. I did pretty much everything you mentioned in the OP. Locked max CPU frequency to match min. Lowest screen brightness, airplane mode, etc. I was able to get over 12 hours SoT. So if the N5 can get 12 hours with the screen on using the same setup you plan in using with the phone getting nice and warm... I don't think a week standby time is too farfetched as long as it's idle most of the time except for pictures. Depends on how much music you listen to I guess. Only problem is even with music saved on the device itself, running at 300mhz you're going to run into skips and pops. Especially when the screen is off. Music playback will be kinda iffy.
Good luck though and let us know how it goes.
Edit: Actually I was mistaken. I just disabled everything like location, sync, etc. Default kernel parameters except switching to ondemandplus governor. This was on an older release of Uber kernel. 12+ hours SoT with ~30% battery remaining!
Here's my post;
http://forum.xda-developers.com/showthread.php?p=52133394
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
KJ said:
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
Click to expand...
Click to collapse
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
Currently Using Apollo music player, can confirm Zero issues using music playback, confirmed CPU freq. using cpu frequency app. most of these things are using hardware decoders
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
But if the phone is sleeping soundly as it should.... The max CPU is irrelevant if not being used. The lag and strain to run processes may hurt a lot though.
You let the music play while the screen was off for a few minutes or did you just play it for a few seconds? I have music stutter on screen off with frequencies higher than 300mhz. I get it with 729mhz. If it doesn't happen to you, awesome. Not sure why though. Do you have time to purchase an OTG charger? Might be worth looking into and they aren't that expensive.
http://www.amazon.com/Best-Sellers-...-Phone-Battery-Packs/zgbs/wireless/7073960011
Currently listening with screen off/on full songs. No issues. no time to purchase an OTG charger however :/
Updated main post to reflect newest enhancements.
Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
It can be done
Sent from my Nexus 5 using XDA Free mobile app
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Flukzr said:
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Click to expand...
Click to collapse
I remembered a discussion along those lines, ill bump the freq. to 652800 min max, and update the main post. An external pack would be great, but i unfortunately just don't have the cash at the moment. between the trip and i just ordered a triple monitor stand and a new wifi usb to play with nethunter
gh0stpirate said:
Screen Brightness set to low as possibe.
Airplane Mode
Click to expand...
Click to collapse
This is basically all you need, the phone will idle for a week or so in airplane mode.
Hi.
I experiencing heavy battery drain Form avast on my non-rooted phone with stock ROM. Like 80% or so..
I am not able to provide a log yet but does anyone got a clue where it might come from?
anyone?
Well avast mostly eats cpu time.. so yeah it will eat battery life.
OmegaRED^ said:
Well avast mostly eats cpu time.. so yeah it will eat battery life.
Click to expand...
Click to collapse
Yeah ok but on my other phone GT-i9505 it's nothing near 80% like on my this one..
80% seems pretty much considering that the display usually drains most battery, right?
PePeMoke said:
Yeah ok but on my other phone GT-i9505 it's nothing near 80% like on my this one..
80% seems pretty much considering that the display usually drains most battery, right?
Click to expand...
Click to collapse
No actually combine network activity with cpu activity and the display can become the lesser evil.
You should look at the wake locks perhaps something you are not noticing.
OmegaRED^ said:
No actually combine network activity with cpu activity and the display can become the lesser evil.
You should look at the wake locks perhaps something you are not noticing.
Click to expand...
Click to collapse
I am checking the wakelocks now with greenify.
thanks for the info!
How do I combine network activity with cpu activity?
Is there a thread reagarding this?
Note: I am not quite sure whether this works.
I use Tasker to do the following:
Profile>Status>Display off
In-Task>Network>Mobile Data 2G/3G>only 2G
Out-Task>Network>Mobile Data 2G/3G>prefer 3G
But there is no option choosing LTE. (This is for my GT-I9505 which is capable of LTE)
I can only enable or disable LTE via secure settings plugin,
but if I enable LTE via Out-Task won't this interfere with the In-Task?
Or what do you mean by "combine network activity with cpu activity"?
Please help a noob out
I mean when you have the network and cpu working hard it quickly eats the battery.
There are many reasons why a phone would use the battery aggressively and it's sometimes a pure pain to track down what or why.
OmegaRED^ said:
I mean when you have the network and cpu working hard it quickly eats the battery.
There are many reasons why a phone would use the battery aggressively and it's sometimes a pure pain to track down what or why.
Click to expand...
Click to collapse
Ok got it.
Could you help me out with the Tasker set up?
would you do it like that too?
Plus I am not sure how to test whether it works well...because the
display is off
PePeMoke said:
Ok got it.
Could you help me out with the Tasker set up?
would you do it like that too?
Plus I am not sure how to test whether it works well...because the
display is off
Click to expand...
Click to collapse
suggestions anyone?