Develop Bugs

[Q] Phone into pocket = standby?

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.

[Q] Charging Issue - No one seems to know

Alright this is a rough one so let me start elaborating my predicament.
The phone will charge fine that isn't a problem.
The problem is "Discharging"
from a rough estimate of 100% till about 80% nothing it will say it's "Still Charging" (well showing the lightning symbol, no big deal)
but as soon as it reaches a lower percent (79% Etc.) it will keep making the Screen turn on and off on and off all day until around 14% which makes the battery use more juice having the screen on.
the issue is it believes to be "Plugged" in and "unplugged" consistently to make the screen wake and sleep.
the wake timer is set to the minimum which is 15 seconds, every other action has been taken that I know of,
Settings-Apps-Notifications,
Settings-Developer-Stay Awake
Settings-Sounds-Notifications
and so on,
I just figured heck, i'll root my Nexus in hopes there are additional options to resolve my issue but no Rom I've found allows this unless maybe I missed one that has this feature to turn off the information if the phone is charging, or not.
Thank you for all your brilliant information in the past, this is a new account I've been with the XDA since 09
Last option would be to buy the Nexus 4 but I am to believe it's a 3G only device and I run through Verizon, the only other option would be to keep my unlimited data and buy their phone. any and all advice is appreciated thank you again,

i bet you have the "fingers" inside your usb port touching each other. one might be slightly bent, causing the issue. if they do touch, the device thinks its plugged in.

That makes sense I didn't take that into account. Would I be able to use needle nose pliers and fix it myself or is there a .Command I can program my phone or even an app that will make it so the only time my screen comes on is for the power button?
If I have to I can always just buy the Nexus 4 if that's a smart choice?
Thank you for your wisdom.

Dominic.Black said:
That makes sense I didn't take that into account. Would I be able to use needle nose pliers and fix it myself or is there a .Command I can program my phone or even an app that will make it so the only time my screen comes on is for the power button?
If I have to I can always just buy the Nexus 4 if that's a smart choice?
Thank you for your wisdom.
Click to expand...
Click to collapse
you can try a stiff wire, i dont think needle nose pliers will fit. also, you could try cleaning it with alcohol(not to much). the n4 is nice too

HTC One M8s power on and heat issues?

I have flashed [ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s for someone and it is working really great. The only serious issue, which existed on stock years ago, is the main reason they stopped using the phone in the past - sometimes when the phone is off it could take between 5 and 30 minutes of pressing the power button to turn it back on. Sometimes it will turn back on very easily, other times like last night it took nearly 30 minutes, of holding the power button down for various lengths of time ranging from several seconds to more than 90 seconds, with and without volume down or volume up, and it finally normally booted after letting it charge for about 15 minutes to around 75%.
The user remembers in the past that if the battery went completely dead they would have to charge it to 100% or close to it before it would turn on again. They are now trying not to turn it off but if they could rest assured if it does end up off it will turn on again without issue, finding a way to manually apply a security patch if possible, would be all that is stopping this being a viable replacement, and save them having to spend on a new phone.
The back cover gets very hot (not just warm) but this only seems to be when booting.
Have any of you experienced any of this, and is there a fix?

well , do not own the m8s but isnt there a low battery warning built in? (also am not using that rom). or an app that would do the same thing? set warning at whatever batt. % they choose and never have to worry about a completely drained battery and phone turning off.
also , is there possibility of a faulty power button?
are they using a case that wont let heat dissipate?
just some thoughts. good luck with getring a fix.

mrrocketdog said:
well , do not own the m8s but isnt there a low battery warning built in? (also am not using that rom). or an app that would do the same thing? set warning at whatever batt. % they choose and never have to worry about a completely drained battery and phone turning off.
also , is there possibility of a faulty power button?
are they using a case that wont let heat dissipate?
just some thoughts. good luck with getring a fix.
Click to expand...
Click to collapse
Thanks for the input. I know I have low battery blinking light set up on my own device with Revenge OS Android 10 but I'm not sure it's on Oreo - I will check and see if there is an app. Even when the screen is on the power button is hit and miss but way less responsive on lower battery. Would eBay be the best place to find a replacement, and perhaps use a YouTube teardown for reference? I want to get them a case as a gift but they don't use one at the moment. Most of the phone (cover? chassis?) is metallic.

runswithascript said:
Thanks for the input. I know I have low battery blinking light set up on my own device with Revenge OS Android 10 but I'm not sure it's on Oreo - I will check and see if there is an app. Even when the screen is on the power button is hit and miss but way less responsive on lower battery. Would eBay be the best place to find a replacement, and perhaps use a YouTube teardown for reference? I want to get them a case as a gift but they don't use one at the moment. Most of the phone (cover? chassis?) is metallic.
Click to expand...
Click to collapse
for me yes & yes . amazon and youtube for a vid.
there is also a sight https://www.ifixit.com/# , i've never used myself but have seen it referenced alot. i believe they have teardown guides , a community for support , and possibly tools (if needed). not sure about parts.
but those 3 would be my go-tos if there was nothing here on xda.
not sure about cases. surely somewhere on the www is a review of cases if you dont already have one in mind.
stay safe & good luck.

Question Screen flicker issue

Anyone run into this yet. https://www.androidpolice.com/google-pixel-6-and-6-pro-screen-flicker/

"Some Redditors speculate that the flickering might be related to static discharge that's released when hitting the button."
Yeah, nothing like the rocket scientists at Reddit to come up with sound answers
Static electricity would destroy the display.
FET's are very sensitive to over voltage on their gates.
Maybe what they were trying to say was unintentional temporary surge on the gates of the matrix TFT's.
If that's the cause long as that surge doesn't exceed the max specs for the FET's in the matrix it's not damaging. If it does, outlook not so good.
If it's not happening during normal operation once on, it's probably a harmless quirk.
Who knows maybe intentional to give it some character I sort of think it looks cool... but Google isn't cool so yeah, it's a fk up.

I have it on my P6P. Turn phone completely off, quickly tap power button and it'll flicker. I'm guessing it's trying to power up but since you only quickly pressed the button, not full power is given.
I'm not worried about it.

I've seen no noticeable flicker at all. Perhaps I just lucked out on this phone?

By design there is an inbuilt delay so you have to press and hold the power button, this helps prevents accidental power ups and also allows time for the user to press other combination of buttons (i.e. to get the bootloader screen), so on a quick press things are still happening behind the scenes like a pre-flight check, and the screen electronics are probably immediately powered up as part of this pre-flight check.
When the button is released without reaching the timeout period to trigger a full power on, the phone just goes back to being off again, now you have a falling voltage which doesn't always drop immediately due to stored charges in capacitors, and that can cause odd glitches sometimes as components see lower voltages than they are designed to work with. With sensitive chips (like flash memory) there will be brownout detection, so they immediately stop cleanly when they see a low voltage, and before that voltage has dropped so low it starts causing oddities or malfunctions. The glitching might also just be the effect of other devices stopping and magnetic fields collapsing causing some spurious data to get to the screen before the screen itself has powered off.
It certainly isn't a fault or anything to worry about, just a quirk of the design.

is it really an issue? Or just phone geeks looking for something to complain about? What effect does it actually have on the usage of the phone?

skimminstones said:
is it really an issue? Or just phone geeks looking for something to complain about? What effect does it actually have on the usage of the phone?
Click to expand...
Click to collapse
Without knowing what's happening it's impossible to say it's harmless.
See my previous post.
At this price point I would send it back... or not and risk eating the repair latter. It could be mobo hardware related.

Google addressed this today saying to basically power your phone like you normally would, without pressing the power button in quick succession without powering the phone up, and that a fix will be out in the December patch/update.
It's not a hardware issue.
Link (Google community post): https://support.google.com/pixelphone/thread/133351387/pixel-6-pro-display-residual-light?hl=en

I had this happen once where the scrolling on the screen stuttered the entire time scrolling, then after closing the app and opening it again it was fine again, and haven't seen it since. My guess is that phone went into a deep sleep state, and took some time to wake

Ironically, I'm getting it using XDA website!

Question Pixel stand 2

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.