Related
I have had a rooted epic for a few months now and have been experiencing a lot of software difficulties recently. I am using Epic Experience Froyo, but I have switched to other roms and still experience the problems (which I have researched but have yet to find a cure). I have times where the screen will turn black and unresponsive, yet the capacitive buttons at the bottom are still lit up, and it will either restart the phone at the lock screen and regain signal or I will have to manually take the battery out. Sometimes I get the same issue except the screen just freezes. Other times (even if the phone is idle in my pocket) it will randomly reboot and I can feel it vibrating in my pocket. I have done many full factory resets w/oden. Everytime I get the problem it seems to gradually get more severe.
I would love for any input to work towards a solution.
Thanks,
Dylan.
Sounds exactly like the problems I was experiencing with my Evo. Do you overclock your phone by any chance? Or have you ever installed lagfix applications?
I overclocked once for about 2 days @ 1.2ghz, but then reverted to regular. For a long time I had Juice Defender installed.
Slick.dylan said:
I overclocked once for about 2 days @ 1.2ghz, but then reverted to regular. For a long time I had Juice Defender installed.
Click to expand...
Click to collapse
Ok, so as far as juice defender is concerned, what are its performance characteristics? Did you ever use quadrant to see what it was putting up? I doubt the overclock for such a short period of time is what would've caused so many problems, but from my experiences, any of these add ons that take your quadrant and almost double it are usually ones that can cause some permanent damage on the phone. I used to run what was called Snap Turbo which was a performance tweaking apk attached to a linked kernal that used to go well with CM6. Well, turbo mode does exactly what ViperSpeed lag fix does. As soon as I started messing around with the Snap Turbo, that's when my screen used to become unresponsive, phone used to freeze, and I would get random reboots almost 10x per day. After I started experiencing these issues, I could never revert back to another Rom or even go back to stock without getting the same issues. I ended up getting rid of that Evo and getting another. As soon as I rooted my next one, random reboots started but not as frequently. Basically, I believe that rooting your phone is going to cause SOME issues. Constantly messing around with it will result in A LOT of issues. It's almost unavoidable and some folks are lucky enough to never experience any issues, but that's the risk you take if you want all the benefits that come with hacking the phone. I hope you find a setup on your phone that isn't so unreliable but I doubt there's anything you can do to completely fix it. I hope I'm wrong, though, because anything you do to fix those issues would be a great help to us all if we end up in the same boat in the future...God forbid!
Juice Defender mainly just altered settings with the wireless connectivity (Like stopping it from using wireless network when the phone is idle). I've also thought about this... I am using 3 different batteries, 1 is default battery, and the other 2 are of a cheap $10 ebay set.
hey guys...i was getting great battery life on di18 and dk28 but for the last week its sucked i loss on average 8-10% an hour (setCPU at 200-1000 ondemand and 200-200 sreen off) i have calibrated my battery twice and still no luck as soon as i take it off the charger it drops to 95% any thing else i can try? thanks for the help
For about 2 months since I have owned this phone it has given me nothing but crap. I always kept my G1 in my pocket and I always dropped it, even had it in water 3 times! (never had any problems) The G2 however if I kept it in my pocket, dropped it, or open/closed the keyboard repeatedly the phone would shutoff! Very Very disappointed at first. I missed many calls and text messages.
So How come NOW I can drop it, open/close the keyboard repeatedly, and keep it in my pocket without it shutting off?
I did a little investigating of the battery and contact points on this phone, it turns out that there is room for play with my battery. SO every so often the contacts would lose connection with the battery!
TO fix this I put a small piece of folded paper along the top edge of the battery opposite of the contact point to the phone, it made a more secure and snug fit to the contact points.
The battery does get Hot so I do not recommend this as a permanent fix as it is now a small fire hazard.
BUT, to this day I have had ZERO problems.
I am sooooo now with my G2 any questions or other comments please leave them below.
CYANOGENMOD 7 RC1
Class 10 4gb microSd
1500MAH battery
Hard rubberized black graphic case
Talk about going backward! I remember the old nokia 5160s that everyone and their brother had folded up paper in the batteries about 10 years ago! LOL
SySfS
Meh... I don't think anyone else has this problem. If they did then they probably exchanged it.
Sent from my T-Mobile G2 running Cyanogenmod.
I have this problem.
I can't exchange it because I bought the phone on ebay.
If you search through the threads and on google, quite a few people experience this random freeze / shutdown where you have to do a battery pull.
I've tried flashing different roms, using only basic apps etc...
I don't think it's software related anymore, and if it is, it's too hard to diagnose. Many suggestions have been made, micro sd card slot, battery connections, software, weird app, different rom... I haven't tried removing SD card yet and my battery connection seems ok, it's pretty tight in there...
Don't know what the problem is and I wish someone could figure it out as it's frustrating to drop too much $$$ on a phone and have it act this way.
Random Reboots
I have a similar problem with my G2. It randomly reboots when its siting stationary on my desk or in my car.
This problem is made stranger though because it NEVER does this while I'm using it!! If I have it playing Pandora or Youtube - no reboots. But, like clockwork, if turn off the screen and set it on my desk, reboot... never fails... it will reboot 2 or 3 times then seems to be ok for a little while. Very annoying because I can't make or receive calls while its doing this.
Like others I've read plenty of posts on this but no working fix I can find. Some people say they returned their phone 2 or 3 times and still have the same issue. Some people say its related to signal strength but it does this will full bars or no bars.
I've tried custom Roms: CM6.1.1, CM7-RC1, & Virtuous 1.0.1 and the problem remains.
Does anyone know how to fix this? This is the only negative about an otherwise HOT little phone.
At least yours reboots! A lot of others just freeze (like mine)! And then you don't even know it.
I'm trying out another theory... Installed CM6 a few days ago. Had the same problem.
But I just started OC using CPU Tuner and the stock CM6 Kernel., the lowest option I have for clock speed is 700 something for some reason, so I just used that. So far, 36h, hasn't done it. I THINK, it might be related to the phone not getting enough juice for some odd reason - even on stock, so when you OC it and set a higher clock speed for idle, it might help. NOT sure yet but testing. Will post up if it "fixes" the problem for me.
My G2 was randomly shutting off a lot, usually right after I stuck it in my pocket. The solution? I exchanged it. The new one never does that XD
Possible fix for random reboot
I think I may have found a working fix for my random reboots. Credit goes to the OP.
I installed the Pershoot kernel and since then I haven't had a reboot and up until now it has rebooted like clockwork.
I'll see how it goes.
I had this problem while using the Red ChiChi/EVO batteries, but I believe my problem to be with the back cover. I might have dropped it and the cover got slightly tweaked, or perhaps it was the chichi battery, as it wasn't exactly a perfect fit. If a certain spot on it gets touched or pushed in, the battery loses contact with the pins and kills the phone. I have to pull the battery and let it set for a minute b4 putting it back in and powering up.
I used the same method, with a piece of folded paper on top for a while.
Perhaps its a different problem than the OP, but this only happened with my ChiChi batteries. With stock battery, it always seemed to be a good enough fit, and the corners kept it in place.
I ended up buying an extra stock battery for around $20, and now I carry 2 Stock batteries at all times.
Solution finally?!
I think I found the solution for my phone:
set OC profiles so the phone doesn't go below a certain mhz threshold.
On CM6 stock with CPU Tuner, it defaults to 700mhz lowest. Did not notice any increase in battery drain.
Uptime - 70 hours. Finally fixed!
//UPDATE: I did experience a freeze around the 100 hour mark, but so far that's the only one in the last week or so. In any case, it's doing MUCH better than before...
//OK I lied it still does it but so far just once or twice a week. Better than once a day.
So far there are apparently three problems/solutions:
- Micro SD slot loose connection / improper close - Check micro SD card slot
- Idle voltage too low, freezes phone / use OC kernel and set screen off speed higher
- Bad battery connection / manually fix
After many tries and diagnosing I think one issue is that on stock settings, the idle / screen off profile is set too low, which can freeze the phone (although I did have it freeze once while I was actively texting... not sure why). But 99% of the time it happened with the screen off. Hopefully it doesn't happen again, will keep phone on to see, but I don't remember it going more than 48h without freezing lately.
I have tried the following which did NOT fix the issue for me:
Micro SD check
Uninstall programs (skype, launcher pro, various others)
Revert to "stock"
CM6 "stock"
Checked Battery
Used stock battery / China battery
All those solutions still led to the random freeze / battery pull situation, but could potentially work for you.
2 G2's did the same thing. T-Mobile states known problem. After 14-hour shut down pulled mSDHC card and Sim and replaced battery which was drained in the off-state.
Solved problem and bought a Nokia N8.
Customer Service at T-Mobile and HTC is totally unconnected and unresponsive. Their answer wait for the FOTA.
Hope they don't send it to my Symbian ^3 jewel!
Was Shutting down multiple times a day - FIXED!
Hey Guys,
I've purchased my G2 from ebay so was not able to return it. So I've been trying to fix this problem for ever.
I have not found anything that works until now (knock on wood).
I installed the Cyanogenmod (cm_vision_full-32.zip) and updated my older CM version. The phone has not shutdown once in 4 days, which is a first.
Note: my GPS does not work with this version. I'm about to try a clean wipe to see if it will activate. I'm guessing however that the shutdown issue is 100% tied to the GPS so if I'm successful the problem will return. If a wipe does not work I'll try new radios.
I'll update any progress.
-Pappi23
lost800 said:
I have this problem.
I can't exchange it because I bought the phone on ebay.
Click to expand...
Click to collapse
Caveat emptor.
I know. Live in Canada and only way to get the phone.
Me too, although my phone is at uptime: 211 hours right now
CM6 with cpu tuner with the settings posted above... basically make sure it never underclocks below 700 mhz.
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.
Never happened to me or even heard of it
Sent from my GT-I9100
have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it
thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).
Right, no matter what, I'm getting battery drain in stand by. No sync, Google now disabled, no mail, no location reporting/history etc. and yet I'm getting weird battery readings. In the pic below you can see, I'll let it idle for a couple of hours and the battery will drain. Then I'll use the n10 and the levels will spike. BBS shows that the n10 is awake for about 4 hours but the partial wakelock and kernel wakelock nothing untoward. I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
yets said:
I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
Click to expand...
Click to collapse
You can unroot and relock your device. Rooting should not be a warrenty issue.
See: " [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE"
http://forum.xda-developers.com/showthread.php?t=2001868&highlight=unroot
Features mentioned among many: "* Unlock/Re-Lock your Bootloader"
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
EniGmA1987 said:
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
Click to expand...
Click to collapse
Is it worth getting in touch with Google? I've had it since just after xmas? I'm about to factory reset it for the second time this week.
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
EniGmA1987 said:
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
Click to expand...
Click to collapse
I'd rather not factory restore it, this is my second time doing it. I'm starting from the beginning like it's a fresh install, just using the Google apps only to see if there are issues there and then adding more until I'm comfortable.
I want to root the tablet only as a last resort as I'm attempting to see if it is an app or it is the battery. I'd rather not brick it or void warranty only to find out it is the battery and then be unable to get a replacement.
There must be somebody that has similar problems?
So, factory reset, this is after 24 hours; This is not kosher. Stock apps. Only thing syncing if you can call it that was Google now. No syncing or anything. Purely from stock apps with updates. Stock battery graph says that it's not awake but stats say it's awake for 19 hours.This doesn't even come close to advertised idle/stand by time. Surely I should return it? I was adamant that I wouldn't complain but I didn't pay so much money for it to come out with this as stock performance.
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
EniGmA1987 said:
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
Click to expand...
Click to collapse
Thanks. To be fair I think if purchasing such an item, you shouldn't have to become a developer/hacker to study such an issue. Haha! I've used Google now when I first got the tablet and not understanding what it was had it enabled and get there was no battery drain to such an extent.
Fair play to Google, they've agreed to send me out a new one. It reached a point where I couldn't enjoy using the tablet and everything was a test to see what could be causing the issue.
I won't bad mouth Google, as I understand that things do become faulty and these items are complex enough. On another note I called up the RMA team in American (I googled the wrong number) and the two ladies were more than helpful. I don't know how anyone has problems with them. Maybe it was my British accent that did it!
So, I've got a replacement and so far it is not displaying the same issues. It got me thinking about when my original problem started and I think it started when it was updated to 4.2.2. This model comes stock 4.2.1 and it's prompting me to update. Should I bother? Was I just unlucky? Is there a specific way to ensure that the update is a clean update?
yets said:
... This model comes stock 4.2.1 and it's prompting me to update. Should I bother? ...
Click to expand...
Click to collapse
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
3DSammy said:
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
Click to expand...
Click to collapse
Yeah, I kind of did that when I factory reset it, I just loaded up the stock apps, desynced everything, logged out of everything that wouldn't be used, disabled Google Now and location settings, rebooted and it was still iffy. Before I sent it back I left it for a day and the battery stats were going up and down like a roller coaster. Could it of been a faulty battery? I would like to update but I'm so wary of the problem coming back.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
You may have been unlucky. I have had great battery on all 4.2.2 some ROMs/kernels make a difference.
Sent from my Nexus 10 using XDA Premium HD app
So, after a few days my new Nexus 10 started displaying exactly the same issues as before and I had just about ruled everything out. I used BBS again and looked at the stats, with PowerManagerService being the main culprit but the numbers in Partial wake locks just didn't match. There were very little wakelocks but something was still draining. I looked at the CPU and for most of the CPU was running at 200hz in deep sleep. I just couldn't figure it out and looked at the Running apps and there was only a few but one remained constant throughout all my tests and that was the Settings app. I took a punt and stopped it and cleared it from recent apps. Lo and Behold, the drain has disappeared and the battery doesn't drop at all in idle.
Excuse my noobiness, I didn't know that Android treated Settings as a separate app? On my Samsung S3, this isn't the case, once you leave settings it closes it and suspends it causing no drain.
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
EniGmA1987 said:
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
Click to expand...
Click to collapse
Sorry, didn't make myself clear. BBS was saying that tablet was running at 200mhz preventing it from deep sleep and that thing causing it was having the System Settings app not closing. Hope that makes sense and helps people in the future.
Well that is certainly an interesting find. If you restart the tablet and dont open settings does the tablet sleep fine?
Yes, if you restart it and avoid going into settings, it sleeps happily only waking sync if you have any. It has been idling for about 10 hours without dropping.
I've attached a picture and if you compare to the one I posted at the start of the thread you can see a clear difference. There was a point where I forgot to close Settings and you can see the drain (middle of the graph).
Somehow I don't think this is normal. It dropped almost 30% at home while I was at work. Google now is disabled but groove IP running. No apps that should be sucking battery, but its mostly the android OS. Any thoughts?
Sent from my Nexus 10 using xda app-developers app
Probably the exact same thing as the guy above me. Doesnt look like you are deep sleeping one bit.
I finally decided to go public with my issues after trying to figure this out by myself for months. this is about wifi issues with the modem (any app that is loading something online, can't do anything because the phone doesn't send any up or download commands) and performance problems when the battery gets low (i think its either bad BCL driver or hotplug driver)
Modem issues.
I will try to explain this as best as i can and also hope that im not alone on this one.
Let me first talk about nougat b08 as that was the first time i have encountered the issue (on 2.4ghz networks only). And NO this is not because of interferances in my area or bad wifi channles or anything. Also it's only happening on my axon 7 (All other devices like my laptop, console etc are fine.
i noticed that any app/game when saying "connecting" (or any other indicator) the wifi icon at the top stays blank (meaning there are no up and down arrows for a period of time). This doesn't happen always but way too frequently to be a minor issue.
Let's take a few examples:
-chrome: when i try to open sites sometimes the loading bar stays at the left. Wifi icon doesn't show any up or downloads (the previous mentioned arrows).
-Sync (reddit client): loading circle spins and spins without any indication of any real progress. Again the wifi icon doesn't show anything happening either)
-XDA Labs: same thing here as in Sync.
-any game with internet connection required: Same thing again.
This often results in a connection error or timeout.
Reminder that this was while i was on nougat b08. This issue never happend in 5ghz but as i mentioned previously, this is not because of any 2.4 ghz interferances etc. here is why:
i fixed the whole issue by flashing the nougat b10 modem. Now the issue was fixed and i never ran into it again until Oreo b02.
This time tho the issue persists on both wifi bands (5ghz and 2.4ghz). The issues are exactly the same as in nougat b08 apart from 5ghz being affected now as well. Flashing the oreo b03 modem doesn't do anything since its the exact same. I also tried flashing the nougat b10 up to b12 modems but the nougat modems seem to break Calls. when i had the nougat modems installed on oreo, i couldn't hear the other person and they couldn't hear me. But they did fix the wifi issue (just tested again with nougat b10 modem)
so yeah thats the issue i have currently with the modems wifi stuff. i hope my explanation was somewhat understandable.
Low Battery Performance issue (starting between 50 and 40% battery left
Now this one is weird as idk what the real culprit is. I think its either a bad BCL driver or a bad Hotplugging driver.
Here is some info on BCL by @Infy_AsiX : https://forum.xda-developers.com/axon-7/how-to/degraded-battery-bcl-device-lag-t3752545
Now if you have read the linked BCL post, you should know that the device throttles the cpu if the voltage hits a certain low threshold which decreases performance big time.
I gotta say that my battery isn't degraded. Like not at all (aside from very little which is natural with any battery that gets older and older).
But the Voltage never drops below the 3.2-3.3 Volt threshold. in fact my voltage is over 3.5+ Volt at 15% battery left. fully charged its over 4.
The time when the phone starts to lag is around 50 to 40% remaining battery. the voltage there is around 3.7+ Volt which should not trigger the BCL to throttle my device.
So maybe the BCL driver is buggy i thought, so i tried disabling it through the shell but it stays/resets to enabled. So perhaps its locked by the kernel. i also tried editing the thresholds but they reset right after to their original value as well. rebooting doesn't help this. AND YES my device is rooted with the system write protection disabled so thats not the issue as i can freely modify any system file.
So i can't say for sure if BCL is buggy. If it isnt than its definetly not the culprit because i never hit the thresholds for it to start throttling in the first place.
And about Hotplugging, im not really sure if this is the culprit either. I only know that it can disable a certain number of cores at various scenarios which depends on how ZTE configured it. And idk how i can disable it through shell commands. If thats possible at all.
I will edit this post multiple times probably tomorrow (and will post a reply when i updated the OP and what i added) as im really tired. So bare with me for now if i couldn't explain something as good (and any possible typos)
I have also weird issues,does this look normal?it can't be ,it sit on 6% for like 20minutes now
Predatorhaze said:
I have also weird issues,does this look normal?it can't be ,it sit on 6% for like 20minutes now
Click to expand...
Click to collapse
Idk. But this isn't the same issue i described in the op. In the op i was talking about low battery performance issues which cause the device to lag heavily. Not about inaccurate percentages
GodOfPsychos said:
I finally decided to go public with my issues after trying to figure this out by myself for months. this is about wifi issues with the modem (any app that is loading something online, can't do anything because the phone doesn't send any up or download commands) and performance problems when the battery gets low (i think its either bad BCL driver or hotplug driver)
Modem issues.
I will try to explain this as best as i can and also hope that im not alone on this one.
Let me first talk about nougat b08 as that was the first time i have encountered the issue (on 2.4ghz networks only). And NO this is not because of interferances in my area or bad wifi channles or anything. Also it's only happening on my axon 7 (All other devices like my laptop, console etc are fine.
i noticed that any app/game when saying "connecting" (or any other indicator) the wifi icon at the top stays blank (meaning there are no up and down arrows for a period of time). This doesn't happen always but way too frequently to be a minor issue.
Let's take a few examples:
-chrome: when i try to open sites sometimes the loading bar stays at the left. Wifi icon doesn't show any up or downloads (the previous mentioned arrows).
-Sync (reddit client): loading circle spins and spins without any indication of any real progress. Again the wifi icon doesn't show anything happening either)
-XDA Labs: same thing here as in Sync.
-any game with internet connection required: Same thing again.
This often results in a connection error or timeout.
Reminder that this was while i was on nougat b08. This issue never happend in 5ghz but as i mentioned previously, this is not because of any 2.4 ghz interferances etc. here is why:
i fixed the whole issue by flashing the nougat b10 modem. Now the issue was fixed and i never ran into it again until Oreo b02.
This time tho the issue persists on both wifi bands (5ghz and 2.4ghz). The issues are exactly the same as in nougat b08 apart from 5ghz being affected now as well. Flashing the oreo b03 modem doesn't do anything since its the exact same. I also tried flashing the nougat b10 up to b12 modems but the nougat modems seem to break Calls. when i had the nougat modems installed on oreo, i couldn't hear the other person and they couldn't hear me. But they did fix the wifi issue (just tested again with nougat b10 modem)
so yeah thats the issue i have currently with the modems wifi stuff. i hope my explanation was somewhat understandable.
Low Battery Performance issue (starting between 50 and 40% battery left
Now this one is weird as idk what the real culprit is. I think its either a bad BCL driver or a bad Hotplugging driver.
Here is some info on BCL by @Infy_AsiX : https://forum.xda-developers.com/axon-7/how-to/degraded-battery-bcl-device-lag-t3752545
Now if you have read the linked BCL post, you should know that the device throttles the cpu if the voltage hits a certain low threshold which decreases performance big time.
I gotta say that my battery isn't degraded. Like not at all (aside from very little which is natural with any battery that gets older and older).
But the Voltage never drops below the 3.2-3.3 Volt threshold. in fact my voltage is over 3.5+ Volt at 15% battery left. fully charged its over 4.
The time when the phone starts to lag is around 50 to 40% remaining battery. the voltage there is around 3.7+ Volt which should not trigger the BCL to throttle my device.
So maybe the BCL driver is buggy i thought, so i tried disabling it through the shell but it stays/resets to enabled. So perhaps its locked by the kernel. i also tried editing the thresholds but they reset right after to their original value as well. rebooting doesn't help this. AND YES my device is rooted with the system write protection disabled so thats not the issue as i can freely modify any system file.
So i can't say for sure if BCL is buggy. If it isnt than its definetly not the culprit because i never hit the thresholds for it to start throttling in the first place.
And about Hotplugging, im not really sure if this is the culprit either. I only know that it can disable a certain number of cores at various scenarios which depends on how ZTE configured it. And idk how i can disable it through shell commands. If thats possible at all.
I will edit this post multiple times probably tomorrow (and will post a reply when i updated the OP and what i added) as im really tired. So bare with me for now if i couldn't explain something as good (and any possible typos)
Click to expand...
Click to collapse
are you sure modem = wifi? I really don't know, but I think they are separate, i.e. the modem file is probably only for cell connectivity
The battery stuff is a mess, but it's probably BCL... It was very badly set on stock G firmware when I had my G. Does your phone turn off if you set a very high CPU load like Gcam pics?
Choose an username... said:
are you sure modem = wifi? I really don't know, but I think they are separate, i.e. the modem file is probably only for cell connectivity
The battery stuff is a mess, but it's probably BCL... It was very badly set on stock G firmware when I had my G. Does your phone turn off if you set a very high CPU load like Gcam pics?
Click to expand...
Click to collapse
I think so at least since in nougat b08 i fixed that issue by using the nougat b10 modem.
It could also be that its just for cell connectivity like u said. But then is the question why it still interferes with wifi somehow.
About bcl. My phone never turned off. Yeah i tried getting a high load on cpu through various apps (like gcam, games, benchmark). But they all lag like hell because of some throttle on cpu and gpu. Not thermal throttling though as this only happens on the mentioned percentages (40-50%). And the voltages are not hitting the thresholds either
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Predatorhaze said:
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Click to expand...
Click to collapse
This thread is about stock oreo though. Not pie.
And 3.7+ voltage is perfectly fine and healthy for your battery at 10%.
I suggest you make your own thread with all the issues you encounter on your setup (rom, kernel etc) and try to give an explanation as detailed as possible.
Predatorhaze said:
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Click to expand...
Click to collapse
you using any custom kernel like kran's EAS? Those have those exact problems you mentioned
Choose an username... said:
you using any custom kernel like kran's EAS? Those have those exact problems you mentioned
Click to expand...
Click to collapse
No,but i was planning to flash the EAS version right now lol.
I did a clean flash ion gsi with hellsgate reborn sinister eas and the problem looks gone,or maybe not.Happens random but less then on bootleggers.
Clean flashed again latest bootleggers with schwifty r5 kernel and speedy vendor 5.1.Wifi also just random disconnects.But one thing i notice now,i charged my battery to 100% and unplugged it,it stays at 100%.Rebooted to twrp for transfer some files to my phone and it still sits on 100%.Booted system and still at 100%.I think its odd because most of the time when i unplug at 100 it drops directly to 99%.
---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------
GodOfPsychos said:
This thread is about stock oreo though. Not pie.
And 3.7+ voltage is perfectly fine and healthy for your battery at 10%.
I suggest you make your own thread with all the issues you encounter on your setup (rom, kernel etc) and try to give an explanation as detailed as possible.
Click to expand...
Click to collapse
okay thanks,and sorry.We need a thread we can discuss everything
Finally found a command that works to disable bcl. Now gotta test for a few days if it solved the low battery performance issue.
I will update the OP once i confirmed it working
For anyone interested in trying it out (for stock oreo only!):
Requirements:
-you need to be rooted of course
-Selinux must be set to permissive. Otherwise terminal emulator doesn't work
-terminal emulator app (on playstore). Im using material terminal emulator
Type in:
su
echo -n disable > /sys/devices/soc/soc:qcom,bcl/mode
Don't reboot. This will revert the changes since those are kernel files (which are not real since they are temporary virtual files) and get loaded a new everytime at startup.
In short: bcl gets enabled again
Sidenote: most results after googling for disabling bcl all had false commands. Every one i found had the "-n" missing inside the command. At last an xda post for a sony xperia phone, had the right command. Funny how the only thing that was missing was entering "-n" after "echo"
Short update: Yes BCL was the culprit in my case and disabling it helped the low battery performance issue i was having. Also no sudden shutdowns for me (since my battery isn't degraded that much as previously stated). If you experience sudden shutdowns, don't worry. BCL gets re-enabled at every boot.
As for the wifi issues, i still haven't found a way to solve this problem.
Will edit the OP later.
Update on the bcl matter: right now it actually does seem my battery is degrading. The voltage readings jump up and down which shouldn't be happening. Perhaps this is the reason i thought my battery was fine since the voltage was fine when i checked it. But in reality it often jumps down and up randomly. This started to happen more often since yesterday
Disabling bcl worked without issues at first. But today i noticed that my battery has problems if i disable bcl. The percentage jumps down way too quick. It jumped from full charge to around 47% and stayed at that percentage for over an hour even tho i was actively using my phone (while the real percentage should have been higher since it hadn't used 53% in such a short time). So i guess the bcl lag i was experiencing was infact first symptoms of degradation of by battery.
I also had my first sudden shutdown at 9%
Its not certain tho yet. I ordered a new battery. Gonna replace it and then i will see if that really was the issue
GodOfPsychos said:
Its not certain tho yet.
Click to expand...
Click to collapse
Wow well i guess this answers that question (see screenshot)
1768mah at full charge. So yep, im so gonna change my battery
Battery health 56%...almost half.
Edit: i know accubattery is not THE most accurate way to show the actual degradation. But its a rough estimate. So the actual capacity could be slightly higher or lower. Nevertheless, it's still clear my battery is clearly degraded by now.
GodOfPsychos said:
Update on the bcl matter: right now it actually does seem my battery is degrading. The voltage readings jump up and down which shouldn't be happening. Perhaps this is the reason i thought my battery was fine since the voltage was fine when i checked it. But in reality it often jumps down and up randomly. This started to happen more often since yesterday
Disabling bcl worked without issues at first. But today i noticed that my battery has problems if i disable bcl. The percentage jumps down way too quick. It jumped from full charge to around 47% and stayed at that percentage for over an hour even tho i was actively using my phone (while the real percentage should have been higher since it hadn't used 53% in such a short time). So i guess the bcl lag i was experiencing was infact first symptoms of degradation of by battery.
I also had my first sudden shutdown at 9%
Its not certain tho yet. I ordered a new battery. Gonna replace it and then i will see if that really was the issue
Click to expand...
Click to collapse
I had these exacts same problems.Now with a new battery I have the idea the problem is still here