Related
I have noticed that when I am using my EVO in the car for GPS + bluetooth + charging, it can get quite warm. Especially when its sitting in direct sun. Several times now while it's sitting in my cup holder it has started blinking the LED rapidly. I checked the battery temp in the battery app I run and it was approaching 50 degrees Celsius. What is a reasonable cut off temp that I can set an audible warning with so I notice next time it starts getting really hot? 49C ? What is considered the point where an EVO is "too hot"?
Also, on a potentially related note, the EVO will often crash and restart when I'm using GPS + voice communication (on a call) + BT + charging. This seems to be the required combination of multi-tasking to replicate the restart. I do this a LOT in my car with work so I have easily replicated it several times. I called Sprint and talked with advanced tech support. Once I described the specific problem he essentially offered to send a replacement phone with almost no resistance. This led me to believe its potentially a common/known issue internally at Sprint. Once I said a few magic words (voice and GPS simultaneously), he seemed to acknowledge it was a valid issue he had some experience seeing. They replaced a 0003 unit with a hardware version 0004 unit. Unfortunately, the issue still occurs. However, it doesn't seem to necessarily be heat related as the phone isn't always hot when it happens and I don't get rapid LED lights like when it has gotten really hot. All battery use has been the normal stock battery in both hardware versions.
Background info:
For testing purposes I am using stock Sprint rom fully updated, rooted. All standard radio/kernal, etc. No overclocking or anything like that.
I do all those Multitasking things all the time. It has never crashed/rebooted, in fact I don't recall ever having a random reboot.
I rarely have it in direct sunlight, I use a ProClip most of the time (which does allow a lot of air all around it).
It does get warm doing GPS, Charging and BT Voice Call. And it barely keeps up charging while GPS Navigation is going.
It might be your charger is allowing it to charge faster than it can handle.
I run MikGinger now and ran NonSense ROM for while.
My BT is always a little flakey though. If I make a call, hang up and wait and make another voice dial call it will all work fine. If I hang up and immediately make another call the phone will disconnect headset and leave Voice Prompt on Screen. If I clear screen and click headset again it reconnects fine and all is good. Every ROM has done this including CM7, Stock and Leaked based ones.
I had this same issue on my original phone. Doing anything in the car while it charged caused it to reboot. Even after being off and cooling down, I could get it to reboot by quickly scrolling up and down in the browser. My phone would just get warmer and warmer, then reboot.
I got them to give me a replacement, and all has been fine after that. It's a white Evo, HW rev 0004. I'd recommend getting another replacement. You shouldn't have to sacrifice doing what you want in order to keep your phone running. I can now have my phone charging on a hot day while getting GPS instructions and listening to Pandora. I don't have any bluetooth stuff, but I imagine I could do that as well.
I would like to have the screen power down, but leave the touchscreen active. Then I can tap/swipe the screen to return the display, instead of hitting the power button. [Note: This is only for a "docked" state.]
Also, since "Display" is always the battery killer, this could prove useful for battery savings. With the screen dimmed to 20, I'm drawing about ~500mA. With the display is off, the power draw is ~100mA. Pandora is playing away the whole time. [Note: I'm not checking the power draw often, so take these numbers with a grain of salt.]
I would really like the nitty gritty details on how the power is routed to all the components (i.e. what can be independently powered up/down, and what is on the same power bus).
Any kernel gurus out there?
To be honest, this just sounds like a not-so-good idea.
Why not just flash something that gives your optical button joystick thing an unlock function?
And if you are just using this for when it is docked, why not just leave the screen on?
So, flashing an unofficial rom is a good idea, but tweaking one is not? If people didn't try the "not-so-good" ideas, this site wouldn't exist.
I have CM7, so I have the feature... disabled. The OJ button pushes the phone "dock" across my desk, and unlocks my phone if I pull it out of my pocket the wrong way. Besides, this is only substituting one button for another.
At a minimum, it would be nice to get the backlight to <5 (out of 255, not %), but I assume a full power down is where the real power savings will come from. I just want to tap the screen to bring back the UI.
sealdog said:
And if you are just using this for when it is docked, why not just leave the screen on?
Click to expand...
Click to collapse
Charging + screen on + CPU active = overheating battery. (i.e. It's not good for the battery.)
No need to get defensive but I see your point.
I think he just meant not optimal or efficient but it is your phone and actually sounded like an idea I thought of a while back. I'll be watching the thread.
06stang said:
No need to get defensive but I see your point.
I think he just meant not optimal or efficient but it is your phone and actually sounded like an idea I thought of a while back. I'll be watching the thread.
Click to expand...
Click to collapse
That was more after-work-commute mood than anything he said. I thought I caught the pissy bits (that isn't the original text), but apparently not.
So, sorry, SealDog. I didn't mean to be such an _____.
Anyways, here's another way to think about it, or just more info....
I just plugged in to AC, and the battery is at 23%. This means the charge current is at ~950mA.
With the screen off, it's putting ~800-850mA towards charging the battery (fast charge rate). With the screen on, it's only putting ~500mA towards charging (trickle charge rate), and burning up ~450mA.
Somewhere around 40-42 degrees C, the charge controller drops to ~500mA, because the battery is getting too hot. Yet, I'm still drawing ~450mA, leaving almost no current towards charging.
When it gets hotter (42-44 degrees C), the charger shuts off completely. Now, I'm just discharging the battery.
I have run into this too many times. 6+ hours on the charger, and the battery has only charged up 10-15%. Not cool. (In fact, the phone is freaking hot.)
BTW, I'm trying find every on/off setting I can (e.g. 1x/3G toggle). Mainly, I want to know what each unit's idle power is. I read about lots of battery saving things, but do they really help? Does 1x truly draw less idle current than 3G? Does shutting off wifi, gps, etc. actually save power when idle? Byrong did a nice backlight + CPU frequency examination. I'd just like to go further. I have an incomplete test built in Tasker (I have to fix the stinking task priorities, and remove all "sleeps").
My ultimate goal is to have a set of Tasker profiles that optimize power consumption for my purposes, without sacrificing functionality. For example, my mobile data choice is on or off, but off means C2DM can't reach the phone. I have plans for C2DM, so this isn't something I wish to sacrifice. But, if the screen is off and the network load is near zero, 1x is sufficient.
Try screen stand by root
『Moved by touch™』 ?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
This is available on my S3 i9300 with Siyah kernel, but I don't use it for two reasons:
- Accidentally activating the screen and waking the phone
- The digitizer normally turns off, and leaving it on drains your battery.
Just got the GN for Sprint 2 days ago and have so far enjoyed my selection. I have run across an issue with the onboard barometer though. It seems to always read way lower that the pressure actually is. With every app I use it on it reads 1.2 mercuries low inHg and about 35 hPa low depending on which app I use. Is there any way to calibrate the sensor to compensate since not all apps have a calibration option?
Zero responses? There has to be some way to calibrate it since it uses a piezo system and not actual mercury.
Depends on where you are. It's not corrected for height, so if you are 1000ft above MSL, you'll read 1 inHg low because that's the actual pressure. Your local weather station/airport altimeter setting have corrected for altitude, so places like Denver, CO don't scare people by telling them the local pressure is lower than at the center of hurricanes.
Various apps have a built-in correction factor that you have to manually enter. Barometer HD and Barograph are two that I've found so far that have a correction setting. You have to play with it until it reads the same as the weather man says. Barograph seems cool because it periodically takes the reading, instead of telling you what it is every half a second. You only see the power of a barometer by observing the pressure changes over several hours. Another graph over time app I just found is Barometer Monitor. There's no correction factor, but it does allow you to specify how often it measures the pressure.
A friend of mine has a Motorola Razr which automatically switches to standby (screen off) when it's put into his pocket.
Does anyone know if there's a way for us HOX users to accomplish this?
WiplashNL said:
A friend of mine has a Motorola Razr which automatically switches to standby (screen off) when it's put into his pocket.
Does anyone know if there's a way for us HOX users to accomplish this?
Click to expand...
Click to collapse
Man, I feel like an advertisement recently, but I feel like this would be something not too hard to accomplish with Tasker. If light levels drop to near nothing and the proximity sensor detects a very short distance, like the phone is in your pocket, it turns the screen off. I'd also put in an if for disabling this function when you're on a call, just because it already does it and I don't know if it'd interfere. You could test it though.
Battery use might be a concern if it polls the sensors too much. Would have to look into it.
Edit: I set up a simple test for this on my Infuse, and I got it to work, but it doesn't work instantaneously. The sensors are only polled every x number of seconds, but I don't know what that number is exactly. I suspect it shouldn't take more battery than it would if you had auto brightness on, and with auto brightness on, it's probably already updating the value, if it isn't always anyway (I want to say it does regardless), so I guess battery shouldn't be a concern. I guess it turning off with a couple of seconds of delay is still better than it staying on for 30+ seconds.
My pixel stand 2 has a fan built in. The software has limited options for it's functionality. I use the phone nearly continuously as a hotspot on the stand. It gets quite hot, and I am using acca to keep charging between 40 to 80%. I suspect the pixel stand's fan isn't really responding to the phone's temperature, but doing it's own weird Google ****. If Google would give the option of 100% fan speed continuously my problem would be solved. My intention is to rule this device to MY specifications. I plan to open the device and direct wire it's fan to run at full speed continuously. My question to the community is: how to wire the fan to the existing internal circuitry to make this happen? My usual, non elegant solution would be to just power the fan from an external adapter. But this results in multiple power strips with multi plug adapters, an electricians nightmare. YouTube shows some teardowns, but no voltage pinout points.
I'm sorry to say that I don't have any advice on this. I don't even own a wireless charger, but I especially understand using one in your circumstance.
I just wanted to comment because what you want to do reminds me of things that I do all the time with other (usually, computer) hardware that I don't like how it works, and figuring out ways to keep things as simple as possible, but yeah, no idea about the Stand 2.
Good luck!
GivIn2It said:
My pixel stand 2 has a fan built in. The software has limited options for it's functionality. I use the phone nearly continuously as a hotspot on the stand. It gets quite hot, and I am using acca to keep charging between 40 to 80%. I suspect the pixel stand's fan isn't really responding to the phone's temperature, but doing it's own weird Google ****. If Google would give the option of 100% fan speed continuously my problem would be solved. My intention is to rule this device to MY specifications. I plan to open the device and direct wire it's fan to run at full speed continuously. My question to the community is: how to wire the fan to the existing internal circuitry to make this happen? My usual, non elegant solution would be to just power the fan from an external adapter. But this results in multiple power strips with multi plug adapters, an electricians nightmare. YouTube shows some teardowns, but no voltage pinout points.
Click to expand...
Click to collapse
Mine is working just fine, I have acc set to stop at 70% and the stand set to max charge and the fan is running fast nonstop. Only issue I have is sometimes the stand doesn't communicate to the phone but that's apparently a widespread issue.
Thanks, I have been gleaning some information on this, will post when I get it sorted.
Namelesswonder said:
Mine is working just fine, I have acc set to stop at 70% and the stand set to max charge and the fan is running fast nonstop. Only issue I have is sometimes the stand doesn't communicate to the phone but that's apparently a widespread issue.
Click to expand...
Click to collapse
When the stand fails communication with the phone does your fan continue to run, or does it quit? Are you running heat generating apps while on the stand? Like Hotspot or AnyDesk?
GivIn2It said:
Thanks, I have been gleaning some information on this, will post when I get it sorted.
When the stand fails communication with the phone does your fan continue to run, or does it quit? Are you running heat generating apps while on the stand? Like Hotspot or AnyDesk?
Click to expand...
Click to collapse
With no connection the fan runs extremely slowly, it's following a temperature readout on the coil and I don't think it ever will run as fast as when the phone tells the stand to ramp up the fan.
I used to have an issue at the beginning of the year where the phone would just not connect to the stand at all, and I would have to unpair and pair the stand back to the phone. This happened a few times in a month but then just stopped and I haven't had that issue since.
I do know that what case you use does make it harder for the phone to make a connection. I previously was using the Google case but it is thick enough that it would not connect every so often and also wasn't good because it increased the efficiency loses and also trapped heat in the phone. Ended up switching to a thin case and it's better, but probably would be best caseless.
I don't run anything on my phone when it is charging, it's always idle.
Namelesswonder said:
With no connection the fan runs extremely slowly, it's following a temperature readout on the coil and I don't think it ever will run as fast as when the phone tells the stand to ramp up the fan.
I used to have an issue at the beginning of the year where the phone would just not connect to the stand at all, and I would have to unpair and pair the stand back to the phone. This happened a few times in a month but then just stopped and I haven't had that issue since.
I do know that what case you use does make it harder for the phone to make a connection. I previously was using the Google case but it is thick enough that it would not connect every so often and also wasn't good because it increased the efficiency loses and also trapped heat in the phone. Ended up switching to a thin case and it's better, but probably would be best caseless.
I don't run anything on my phone when it is charging, it's always idle.
Click to expand...
Click to collapse
I take the phone out of the case when charging on the stand. I rma'd one stand due to the fan would not start up unless I shook the stand. Now this new stand lets the phone get smokin hot sometimes. What are your ACCA settings? Mine are /sys/devices/platform/google,charger/charge_stop_level 100 5 shutdown (if not charging) at 5 Resume charging at 40 stop charging at 80. The reason I have the resume at 40 is I will often have the phone discharge to 50% or lower in use, and when I had resume set to 70% ACCA would fail, (when I sat the phone on the stand discharged to anything below the set resume point) the phone would discharge to 5, then shutdown, and proceed to charge itself to 100. I still have some trouble with ACCA and the phone charged to 100 in the morning even if I place on the stand before the resume point.
I think our main difference is that I spank my phone harder when its on it's stand than when I'm carrying it. Hotspot, mostly. But sometimes, other stuff, as well. Maybe the stand just isn't capable of keeping up with the heat generated.
GivIn2It said:
I take the phone out of the case when charging on the stand. I rma'd one stand due to the fan would not start up unless I shook the stand. Now this new stand lets the phone get smokin hot sometimes. What are your ACCA settings? Mine are /sys/devices/platform/google,charger/charge_stop_level 100 5 shutdown (if not charging) at 5 Resume charging at 40 stop charging at 80. The reason I have the resume at 40 is I will often have the phone discharge to 50% or lower in use, and when I had resume set to 70% ACCA would fail, (when I sat the phone on the stand discharged to anything below the set resume point) the phone would discharge to 5, then shutdown, and proceed to charge itself to 100. I still have some trouble with ACCA and the phone charged to 100 in the morning even if I place on the stand before the resume point.
Click to expand...
Click to collapse
Code:
configVerCode=202206010
capacity=(2 50 65 70 false false)
temperature=(40 45 120 51)
cooldownRatio=(50 10)
cooldownCurrent=
cooldownCustom=()
resetBattStats=(false false false)
chargingSwitch=(gcpm/constant_charge_current_max 600000 0 --)
applyOnBoot=()
applyOnPlug=()
maxChargingCurrent=(600)
maxChargingVoltage=()
language=
runCmdOnPause=''
ampFactor=
voltFactor=
loopCmd=''
prioritizeBattIdleMode=true
currentWorkaround=false
battStatusWorkaround=true
schedule=''
battStatusOverride=''
rebootResume=false
: one-line script sample; echo nothing >/dev/null
Battery kept between 65% and 70%, charging switch supports battery idle mode and setting maximum charge current 600mA, prioritizing battery idle mode is enabled so the battery is essentially not used and phone instead is using external power when active.
Thank you. If your phone goes below 65% and you place it on the stand, will it pick up charging?
Did you enter your settings under the ACCA interface, or ACC?
GivIn2It said:
Thank you. If your phone goes below 65% and you place it on the stand, will it pick up charging?
Did you enter your settings under the ACCA interface, or ACC?
Click to expand...
Click to collapse
Yes, if it drops below 65% it will charge at 600mA back up to 70% and then the battery will idle, it won't begin charging until below 65% which would take probably over a week for the battery to selfdischarge down to 65%.
Overwrite the contents of /data/adb/vr25/acc-data/config.txt and restart acc.
Overwrite the contents of /data/adb/vr25/acc-data/config.txt and restart acc.
OK I will paste the exact code you sent into that location and see how it goes. I assume this will automatically change the ACCA interface as well. I will probably disable it in Magisk first, then re enable the module after reboot.
I did follow that exactly did copy the changed file in root explorer, saw it change the file size to confirm it really happened. But the changes do not show up in ACCA. It shows automatic charging s witch and prioritize battery idle disabled, charging power control disabled. Do the changes made to config.txt not show in ACCA or did something else fail?
I figured it out. Had to remove all the blank spaces between lines. Removed the word code: at the top. Removed the line : one-line script sample; echo nothing >/dev/null at the end. And probably most importantly, changed the configVerCode=202206010 to my existing code number, as the program checks this on boot and rewrites the original file if the numbers don't match. According to the documentation, this is a nono, but I couldn't figure how else to make it work. It is working as you said it would with these changes.
GivIn2It said:
I figured it out. Had to remove all the blank spaces between lines. Removed the word code: at the top. Removed the line : one-line script sample; echo nothing >/dev/null at the end. And probably most importantly, changed the configVerCode=202206010 to my existing code number, as the program checks this on boot and rewrites the original file if the numbers don't match. According to the documentation, this is a nono, but I couldn't figure how else to make it work. It is working as you said it would with these changes.
Click to expand...
Click to collapse
That means you are using a different version of acc, so your mileage may vary. I'm still using the last stable release which is 2022.6.4.
Might also be worthwhile to install Kirisakura kernel as it puts more thermal constraints on to mitigate heat better than stock.