Database Develop

Random boots and sudden steep battery drops

Guys, I have a serious problem. First, look at the pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what happened (and keeps happening):
Phone randomly boots whether I am on 3G or WiFi. Also, it boots when the phone is challenged to open a webpage, load an image or an app wants a bit more processing power. When it boots after the crash the battery hits 0! So it gets stuck in a boot loop because it thinks there is no battery juice left. The only way to successfully boot is to plug in the charger. So, I am royally screwed if when this happens outside.
I am currently running Slimkat 8.12.1 and I tried Maclaw's Carbon (20141119 release)...same problem! Is the battery dying one me? (My S3 Mini is 1 year old) If so, I will immediately buy one if this is gonna solve the problem. Because my phone right now is pretty much useless and super unstable.
PS: I also have super steep battery drain issue. I wake the phone to check an email and browse for a bit...and BLAM! it hits the bottom! see:

also people with an s3 mini older than a year, how is your battery health?
anyone else having the same problem?

wtx1033 said:
also people with an s3 mini older than a year, how is your battery health?
anyone else having the same problem?
Click to expand...
Click to collapse
I have this phone for about 15 months and i'm on Slimkat (by Android-Andi) for 6 months with no problem with the battery until now. I suggest to replace your battery to fix the random reboots. After that a new clean install of the Slimkat (or the rom of your choice) can help. Now if you want to see what drains your battery install the BetterBatteryStats or the Wakelock Detector. The Greenify helps also after. I hope that all these can help you.

jstath1972 said:
I have this phone for about 15 months and i'm on Slimkat (by Android-Andi) for 6 months with no problem with the battery until now. I suggest to replace your battery to fix the random reboots. After that a new clean install of the Slimkat (or the rom of your choice) can help. Now if you want to see what drains your battery install the BetterBatteryStats or the Wakelock Detector. The Greenify helps also after. I hope that all these can help you.
Click to expand...
Click to collapse
ok i ordered a new battery. btw, by clean install do you mean i should avoid restoring my helium backup of apps?

wtx1033 said:
ok i ordered a new battery. btw, by clean install do you mean i should avoid restoring my helium backup of apps?
Click to expand...
Click to collapse
TWRP Recovery clean install:
Reboot to TWRP recovery
Choose wipe/advanced wipe
Choose Dalvik Cache/System/Cache/Data/Internal Storage
Swipe to wipe
Flash new rom/gapps
Wipe Dalvik Cache and Cache
Reboot.
And finaly avoid restoring your helium backup of app.

jstath1972 said:
TWRP Recovery clean install:
Reboot to TWRP recovery
Choose wipe/advanced wipe
Choose Dalvik Cache/System/Cache/Data/Internal Storage
Swipe to wipe
Flash new rom/gapps
Wipe Dalvik Cache and Cache
Reboot.
And finaly avoid restoring your helium backup of app.
Click to expand...
Click to collapse
I'll do that (my new battery just arrived ) should I also avoid Google automatic restore?

wtx1033 said:
I'll do that (my new battery just arrived ) should I also avoid Google automatic restore?
Click to expand...
Click to collapse
No... allow the Google automatic restore. Btw i recommend you to install this http://forum.xda-developers.com/showthread.php?t=2758098 rom or this http://forum.xda-developers.com/showthread.php?t=2666235 because in my opinion they are the most stable. Good flashing.:fingers-crossed:

okay
jstath1972 said:
No... allow the Google automatic restore. Btw i recommend you to install this http://forum.xda-developers.com/showthread.php?t=2758098 rom or this http://forum.xda-developers.com/showthread.php?t=2666235 because in my opinion they are the most stable. Good flashing.:fingers-crossed:
Click to expand...
Click to collapse
i was gonna flash slimkat 8.14
already using 8.12 and i am happy with this ROM

wtx1033 said:
i was gonna flash slimkat 8.14
already using 8.12 and i am happy with this ROM
Click to expand...
Click to collapse
Good choice :good:

HTC issued fix for voice calling Bug!!!

Hey Guys,
Finally HTC issue fix today for the ridiculous voice calling bug. For those with stock rom, kindly run software update in Setting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Better late than never...

Ok how widespread was this bug? How did it occur because I've not had any problems at all. Sorry if I sound like a fusspot but I'm actually curious.

ss4adib said:
Ok how widespread was this bug? How did it occur because I've not had any problems at all. Sorry if I sound like a fusspot but I'm actually curious.
Click to expand...
Click to collapse
I had it with Viper 7.01.
I reverted temp. back to 5.8 Venom and didnt have it.
I read a lot of posts on it over on the Nexus 4 boards, they had it too..

Well in that case wouldn't it be classed as a Google problem? Oh well it's great that HTC have sorted it out for us at least.

tintin814 said:
Hey Guys,
Finally HTC issue fix today for the ridiculous voice calling bug. For those with stock rom, kindly run software update in Setting.
Click to expand...
Click to collapse
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?

skeleton1911 said:
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?
Click to expand...
Click to collapse
I'm waiting for this too.[emoji4]

waiting for this on developers edition.
i called HTC yesterday and they had me shut off google play framework services and ive been able to get calls since yesterday but i keep getting the google play store has stopped working msg.

Howie3045 said:
waiting for this on developers edition.
i called HTC yesterday and they had me shut off google play framework services and ive been able to get calls since yesterday but i keep getting the google play store has stopped working msg.
Click to expand...
Click to collapse
temp fix is:
look my screenshot . link
and enable the play framework services! first

skeleton1911 said:
temp fix is:
look my screenshot . link
and enable the play framework services! first
Click to expand...
Click to collapse
This fix works 100% but keeps the phone awake all the time.

smokin901 said:
This fix works 100% but keeps the phone awake all the time.
Click to expand...
Click to collapse
it shows play services yes. but it will not drain your battery.. (for me battery is fine with that fix)

skeleton1911 said:
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?
Click to expand...
Click to collapse
+1.
A nandroid backup (system partition) would be very much appreciated.

skeleton1911 said:
it shows play services yes. but it will not drain your battery.. (for me battery is fine with that fix)
Click to expand...
Click to collapse
WakeLock Detector detects that the CPU remains active and deep sleep is never achieved, so somethings up with that. I'm just going to wait it out with an older build.

Michiel0211 said:
WakeLock Detector detects that the CPU remains active and deep sleep is never achieved, so somethings up with that. I'm just going to wait it out with an older build.
Click to expand...
Click to collapse
I disabled the checkin service and Im also having a wake lock. Phone never goes into deep sleep. Is it possible to get the zip file for the OTA updates to see what is being updated from HTC? Then hopefully the ROM makers can integrate this.

That will work for root. I'm stock right now though.
Sent from my HTC One using XDA Free mobile app

Here I shared that mentioned OTA.zip. Calls work fine now. Yesterday issue appeared on my device but already today morning I got the update which fixed it.

Any XT1095 Pure Edition owners here?

I am in need of assistance to prove that I have a defective Moto X (XT1095) Pure Edition.
My last thread has gone unanswered... probably for good reason.... probably of bad luck.
But I think from my extensive testing, I have stumbled upon an issue with my specific phone that could be a defect and not just a software (or OS, or kernel) issue.
What I am asking XT1095 owners to do:
- tell me your Android ROM version (stock, stock-rooted, Liquid, etc...) and version number
- go to Play Store and install the free app called "CatLog" (used read logcat... logs of whats going on in the phone)
- and post a snap shot or the log itself in this thread
From my tests with several ROMs, GAPPS, recoveries, boot images, radios, and all the other possible IMGs out there, I come to the same errors shown in the logcat's:
- many many errors that say: WifiMachineState
- its showing up on the log every couple of secs (regardless of ROM or settings)
- like in this image (from stock 5.0) captured with CatLog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
look at the red E for errors
I would like to see if its just on my Moto X.... am I just unlucky to get a defective one.
... or does everyone else have the same errors.
Thanks for your efforts.

XT1095 rooted with TWRP installed (unlocked bootloader obv) stock ROM.
I have tons of those errors too.

diggitydogg said:
XT1095 rooted with TWRP installed (unlocked bootloader obv) stock ROM.
I have tons of those errors too.
Click to expand...
Click to collapse
Thanks for the prompt reply.
I guess it might be software based. I just downgraded to 4.4.4 stock. And it seems those errors are not there anymore. they just come up as debug messages rather than errors now.
We will see how stable it is.

I haven't noticed any instabilities when it comes to my WiFi connection or cell connection. What instabilities are you noticing?

diggitydogg said:
I haven't noticed any instabilities when it comes to my WiFi connection or cell connection. What instabilities are you noticing?
Click to expand...
Click to collapse
intermittent locking up (freezing), regardless if it was in a sleep state or awake state. and had to hold power button until it boots up again
- and that with stock (unrooted and bootloader still locked)
i detailed a thread about my Moto X (2014) adventure here with all the details and updates:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124

eyeoncomputers said:
intermittent locking up (freezing), regardless if it was in a sleep state or awake state. and had to hold power button until it boots up again
- and that with stock (unrooted and bootloader still locked)
i detailed a thread about my Moto X (2014) adventure here with all the details and updates:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
Click to expand...
Click to collapse
Ah. Well I can say that I have had no such thing and have the same WiFi errors in the log as you. Unfortunately it's something else with your phone...

I think so too. Just trying everything before I have to ask Motorola for a replacement.
Too early to say yet, but the stock 4.4.4 (with no errors showing up in the logcat) is looking good. (knock on wood)

Damn, spoke too soon.
Even without those WifiStateMachine errors, the stock 4.4.4 still did a random crash on me while in use. Lame.
I will do some further testing to see if I can pinpoint the exact issue, but its looking like I will need a replacement from Motorola.

eyeoncomputers said:
Damn, spoke too soon.
Even without those WifiStatMachine errors, the stock 4.4.4 still did a random crash on me while in use. Lame.
I will do some further testing to see if I can pinpoint the exact issue, but its looking like I will need a replacement from Motorola.
Click to expand...
Click to collapse
Just installed that logcat reader, I have ZERO errors. My WiFi has been bulletproof. Still on kitkat. Your crash, was it a reboot? I'd wipe everything, reflash 4.4.4 and use it for a couple days without anything installed. If you still have issues, then an RMA is in order, methinks.

I forgot to turn on WiFi.

This is the right picture... I turned on WiFi and no errors

_MetalHead_ said:
Just installed that logcat reader, I have ZERO errors. My WiFi has been bulletproof. Still on kitkat. Your crash, was it a reboot? I'd wipe everything, reflash 4.4.4 and use it for a couple days without anything installed. If you still have issues, then an RMA is in order, methinks.
Click to expand...
Click to collapse
It just crashed (froze) on me twice in the last 12 hours. On stock 4.4.4 now. Logcat's are showing no errors, but the random freezing (crashing) continues.
I am about to wipe and do a full factory restore to 4.4.4 again and install nothing (as well as not even sign into a Google account). Then I will do the same with a 5.0 stock after that. I have a feeling its still going do to the random crashes.
Motorola is giving me a hard time about the return RMA. So I am trying to build up as much evidence as possible.
dia_naji said:
This is the right picture... I turned on WiFi and no errors
Click to expand...
Click to collapse
Thank you for your efforts dia_naji.
The CatLog will do best if your Android was rooted, but its not a big deal. I am guessing your system is not randomly crashing like mine.

Battery percentage showing 3800% after flashing 6.0.1/Root/LK

I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu

I'm having the same problem here, confused

its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899

It's a bug of 6.0.1... Wait for small OTA or 6.0.2

Is it a bug or just an issue with custom kernels? I expect the latter.

simms22 said:
its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899
Click to expand...
Click to collapse
How long do I have to ignore it? What's causing the problem?

Amos91 said:
Is it a bug or just an issue with custom kernels? I expect the latter.
Click to expand...
Click to collapse
It's not a custom kernel - its a fresh factory image install, so stock kernel.
I'd say wait for Google to push an OTA out or another factory image.

Shadester9 said:
How long do I have to ignore it? What's causing the problem?
Click to expand...
Click to collapse
cause, no idea. but i remember the M dev preview had the same issue. some were affected, some werent. id just give it a few run throughs, maybe itll fix itself?

Well, it's not the kernel, since I have the same issue with the stock kernel with 6.0.1 and LeanKernel.

This is just bad.. I can't see how long my battery will actually last
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/24jDFHQ

Yeah, I think I'm going back to 6.0. This isn't worth it.

Not only battery status messed up, the Battery tab in setting is missing as well ...

antiquezip said:
Not only battery status messed up, the Battery tab in setting is missing as well ...
Click to expand...
Click to collapse
Yeah, I accessed mine by tapping the battery icon in quick settings.
Really odd for a bug like this to go unnoticed by Google.

No issues here on a clean install (including partition trims in TWRP) of 6.0.1.

Face_Plant said:
No issues here on a clean install (including partition trims in TWRP) of 6.0.1.
Click to expand...
Click to collapse
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..

MarkPH123 said:
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..
Click to expand...
Click to collapse
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?

Face_Plant said:
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?
Click to expand...
Click to collapse
Ah I see, I was rooted beforehand but wiped everything for a clean slate.
So still stock recovery, stock kernel and no root.
Might have a go at TWRP partition trimming tomorrow when I've got some time to do it.

My battery indication shows 100%, did a clean install and no issues whatsover.

gee2012 said:
My battery indication shows 100%, did a clean install and no issues whatsover.
Click to expand...
Click to collapse
This is odd.
I did use NRT's 'Stock & Unroot' option.
It may have missed the kernel so I'll extract that and try flashing different parts of Android to see if I get any sense out of it or some sort of fix, or Google may figure it out before me (hopefully )

Shadester9 said:
I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu
Click to expand...
Click to collapse
Congratulations man! You're battery should last a whole month without charging!!! Suh-weeeet!

Question Help : "-1:misconfigured IRQ 470 glink-native"

Hello!
My phone doent go deep sleep randomly
BBS and kernel logs show:
-1:misconfigured IRQ 43 smp2p
-1:misconfigured IRQ 470 glink-native (!!!!!!!!! this is a main mistake)
Spoiler: previous time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: new time after fastboot
On any firmware / rom / kernel, stock or non-stock
I tried fastboot official rom - but problem still
It fixes only with reboot.
Pls, help me!

Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.

Bonoboo said:
Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.
Click to expand...
Click to collapse
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too

bodyajoy said:
still active mode randomly
Click to expand...
Click to collapse
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.

Bonoboo said:
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.
Click to expand...
Click to collapse
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it

bodyajoy said:
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it
Click to expand...
Click to collapse
Did you ever figure this out? - Having a similar problem with my Poco X3 Pro

bodyajoy said:
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too
Click to expand...
Click to collapse
Hmmmm, Are you sure about this problem?