yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] Electroman365:
This doesn't work. After I dial the number and hit the red "quick start" I get a warning telling me "fuel guage will be reset....", and the only options are "ok" or "cancel" but hitting either one will actually terminate the procedure and take me to my home screen.

I'm having a similar problem with the phone sometimes shutting off at 30%, 20% ... but I've noticed it only does that when it also shows the wrong charging percentage as sometimes the % stops at 70+% or 80+% or it moves up extremely slowly after that. What I do when it does that is I take out the battery and then put it back in and the phone will show the correct percentage and it will shut down at 0% or around there.

I'm still wondering if there's a fix for the this problem.
[Galaxy Note 4 General] dictum9:
I found out that none of the OEM batteries are any good, the thing that helps the most is a new, extended battery.

Even "new" OEM batteries are way past their expiration date, they age even if not used. A new battery a lot of times solves the reboot/ shutdown issue, unless it's that emmc hardware issue.
[X Play Q&A, Help & Troubleshooting] HuzefaChalla:
Hi i am using stock rom on moto x play indian edition dual sim.

From 2-3 days sensor is not working. No automatic brightness working. No auto rotate working. Please help me

I have also check by going in test mode with *#*#2486#*#*

And it showing proximity sensor is disabled :confused: :crying:
[X Play Q&A, Help & Troubleshooting] pijes:
Any chance that you have a screen protector installed and it's blocking the sensor?
[X Play Q&A, Help & Troubleshooting] HuzefaChalla:
Yes i have a screen protector. But it doesn't cover sensor

Before 2-3 days it was just working fine even with screen protector.

And now suddenly it's not working.
[X Play Q&A, Help & Troubleshooting] harykishan:
Same here guyz. WIth stock 6.0.1 latest update, i think mostly all sensors are behaving erroneously. Any one knows the solution for this irritating daily problem.
[X Play Q&A, Help & Troubleshooting] vampire36:
Any fixes guys ? My proximity, rotation sensor stopped working suddenly today. Tried factory reset as well. Not helping. No screen protector or case! Any fixes ?
[X Play Q&A, Help & Troubleshooting] harykishan:
Same thing happened with mine as well. It was 6 months ago. I tried almost everything possible like factory resets (multiple times), soft restarts, reboots, rooting, installing N, then again coming back to stock ROM MM 6.0.1. But nothing worked. Proximity and other sensors are dead. So be prepared....
[X Play Q&A, Help & Troubleshooting] vampire36:
Crap thats such a pain! Now moto display doesnt work and calls have become a pain! Guess time to move to next phone :P
[X Play Q&A, Help & Troubleshooting] harykishan:
Looks like your phone is infected with blood cancer which is flowing into all parts of it :D

For me it was just with the sensors...rest of all were absolutely fine. For a company like motorola, this kind of bugs in sw are pathetic and not to have.

Finally after a long 6 months pain, and wasting lot of hours on research, I went back to my old trusted Samsung Galaxy phone. Never will own again a Moto!!!
[X Play Q&A, Help & Troubleshooting] isene:
My light sensor stopped working last evening.... Tried going back to 5.1.1, 6.0.1 and 7.1* but no avail, guessing it's a hardware failure
[X Play Q&A, Help & Troubleshooting] harykishan:
I broke my head for almost 6 months figuring whether this behaviour was a hw failure or sw failure. I lost my peace and lot of hours (trying to fix and figure out) with these sensor deaths on moto x play. Had lot of respect for moto. Now you can understand how i treat it. Noting solved. So my kind and wise suggestion for you would be to try all your trials to restore it - but only once!!! If they don't work at first try, they will never come alive again!!!

Few days ago i fell back to my trusted Samsung Galaxy J7 (by exchanging my moto x play with J7). Peace restored.

I will for sure get scared to go for any Moto devices. Period.

Thank me if these words of experience are helpful to you.
[X Play Q&A, Help & Troubleshooting] isene:
The sensors are solderd to the motherboard which means to restore a faulty sensor you will have to replace the whole board.... or have the patience and skill to desolder/deflow and solder/reflow the sensors which is a prety delicate practice
[X Play Q&A, Help & Troubleshooting] harykishan:
Agreed. I have even got that done with experts here. But the board of Moto x play is so thin like a paper!!! This makes it much more worse. So, avoid getting any hw soldering jobs on moto boards. They are not like samsung boards. I even had multiple visits to Moto service here in Bengaluru, but everytime they only suggest me to replace the complete board. Moto service is pathetic!!!

I now do have enough experience and wisdom on these matters. Please keep posted here if you still try meddling with your board and the results.
[X Play Q&A, Help & Troubleshooting] GuestX00520:
sensors off

I just buy this phone, from a woman, 70 bucks, and i noticed just now my 2 sensor r off - light and proximity - on andorid 6.0.1 .... so this is seriously ****, sensor r f..ed up after update to andorid marshamloow only? they will dont work when i downgrade to andorid 5?
[X Play Q&A, Help & Troubleshooting] isene:
I just dropped it off at my reseller within warranty.

Flashed everything back to stock, with no unlocked bootloader warnings.

So hopefully they will repair it within warranty (Netherlands) because it's a hardware failure for sure
[X Play Q&A, Help & Troubleshooting] harykishan:
Sorry to hear that buddy. Ya, Moto X has this tendency and it is very much inline with moto upgrades faulty sensors with Marshmallow. I even went back and reflashed to stock lollipop (and even locked back bootloader and removed the bootloader unlocked warnings), but nothing worked.

Try your luck and post it here.

For me it was sure a hardware damage!!! but not sure how software can damage hardware. I will stay away from Motos for the rest of my life. I am very happy with my Samsung Galaxy.

---------- Post added at 04:23 PM ---------- Previous post was at 04:17 PM ----------

That sounds good and bad as well. Good part is they took your mobile to fix it.

Bad part is, here in India before even touching my mobile they asked for IMEI numbers of my mobile. They key-in these in their testing software and boom there they go. They found that my device's bootloader was unlocked and rooted. With this info they rejected to even touch my mobile.

Not sure, if you lock it back after unlocking once, will the status really be locked even in their software??? If yes, its good news again.

If no, they simply hold your device for a week or so, and return it back with the same reason.

So my suggestion is you double-check whether they replace the entire board or not. Also, keep periodically finding out the current status of the replacement.
[X Play Q&A, Help & Troubleshooting] isene:
In The Netherlands and the rest of Europe there is a law about warranty.

The manufacturer must be 100% sure the flaw is caused by unlocking and flashing custom firmware, if they can't prove this 100% they must fix the issue under waranty. <== TL;DR of the law :)

Source (31999L0044)

I know for sure this problem isn't caused by a unlocked bootloader ;) because it's unlocked from the start without problems.
[X Play Q&A, Help & Troubleshooting] abhi191:
Oh wow.. are the sensors of all moto x play failing now ?? because mine light and proximity sensors are also not working since last few days..!!

Wonder if this is a strategy by Motorola to disable sensors after certain period of owning :confused:

LOL Jk..:p
[X Play Q&A, Help & Troubleshooting] harykishan:
Moto hardware and software both are crap. Now we all practically know why google sold it off to chinese.
[X Play Q&A, Help & Troubleshooting] pijes:
by your logic, Volvo are crap too.
[X Play Q&A, Help & Troubleshooting] noel_105:
Just wanted to report that my sensors are also dying/dead. A week ago my vibration motor died, and a few days ago my proximity sensor and brightness sensor died, so now my screen is stuck at maximum brightness.

Even disabling auto brightness, the screen is stuck at max brightness, so it's likely more than just the sensor that died, but also some circuiting. I can tolerate no vibration, but once I was left using my phone with max brightness all the time, I said screw it. Hurts my eyes too much, especially at night.

I bought a Moto G5 Plus to replace this one. Hopefully it survives longer.
[X Play Q&A, Help & Troubleshooting] harykishan:
Really sorry to hear that your sensors and even vibration motor is dead!!! Looks like a pretty common problem with Moto x plays. Suffering this and reading all the complaints one after one here, why again Moto G5???

Are these sensor deaths happening only with Moto X play? Or did somebody notice them with Moto models as well?
[X Play Q&A, Help & Troubleshooting] noel_105:
I haven't experienced significant hardware issues with Moto phones in the past. I mainly just wanted a budget phone that is bloat-free (for when I use the stock ROM), has active 3rd party support, and lasts through the day. I was also considering the Redmi Note 4 but decided against it because of the limited 3rd party support.

Moto's stock software is very good, the G5+ has plenty of active development, and it has a good battery (not as good as the Redmi Note 4, but good enough) so I decided to go with Moto again. Assuming there are no similar premature hardware failures like this, the phone should last a while. If the phone doesn't make it through minimum 2 years, I'll likely not consider Moto again for a while.
[X Play Q&A, Help & Troubleshooting] harykishan:
hi noel, any updates on 6 months usage of your moto G5+? any premature deaths noticed? Just let us know here... just to gauge motos.
[X Play Q&A, Help & Troubleshooting] noel_105:
Everything good so far. I've been running Resurrection Remix v5.8.3-20170702 since then with the stock kernel. It has been 100% stable, no crashes or bugs.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
i have started experiencing problems with my hima in that it shuts down now at around 20% battery automatically. didnt have this problem before. it started happening one day after i flashed a new rom. im using the same programs i used before. the only things that have changed are its gotten really cold now(could that affect the battery performance?) and i flashed the rom from a different pc than i usually use. any1 make anything out of this? :confused:
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
This has been a problem since WM6..its common..try using different Radio roms and search around the forum for more info
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
i was using wm6 before this started happening... there were no problems then. and i didnt flash the radio rom when i upgraded either. its the same radio. its like one day the phone decided it would stop working at 20% :S
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
i once saw the battery @ 3% on wm6... and it was still working...
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
That's the ideal situation and it fortunately still works this way for me.

Which ROM and which radio version are you currently running and which ROM did work till 3%?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
i was using c_shekhars 7.0b rom at the time n i flashed 7.0c after that. this problem didnt start immediately after installing 7.0c but after quite a long time(many recharge cycles later). I have never upgraded radio rom ever since i got the device n its 1.10.00. Just flashed one of sonblacks roms from pdaviet.net and its going fine till yet. I hope the problems gone although havent had a chance to let the battery drain yet.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
Thanks, this is the most detailed report of what actually happened in this subject that I've seen so far. And it looks ike proof of what I already expected: that it's not part of the logic in any given ROM but more likely a symptom of a slowly dying battery. If it would have anything to do with the ROM, it should happen to all with identical devices and all directly after burning the ROM.

It is however true that WM5 and WM6 are more battery hungry than WM2003 and it's likely that these operating systems respond more critical to battery problems. Together that would indeed mean that you'd notice battery problems much earlier. So if battery life is your primary concern it's likely that going back to WM2003 would lengthen both your battery life and the time you can use it per charge.

I can't find exact reports on the production period of the Himalaya, some say the first ones were spotted as early as 1999 (probably mistaken device identity) and I'm sure that I haven't seen them in the shops from late 2004.

This type of LiIon battery probably has an average lifespan of 300 full cycles so indeed the first unlucky ones should drop out by now. If that happens to you right after flashing a ROM it comes natural to blame the ROM.

Beware! I've seen at least one report of someone who bought a "new" battery that performed even worse than the one that came with his Hima. LiIon batteries have a long, but still limited shelf life when not charged regularly. And I personally noticed when buying camera batteries that quality does have a price tag, buy from reliable sources, read return policy.

I'm currently studying if there is a way to bring down WM6 battery drain but can't make any promises if I'll ever succeed.

One last point: I once thought that the sudden burst of energy consumption that flashing a ROM is could be the culprit, but abandoned that thought. So far none of the developers and ROM cooks in these forums, who all regularly flash, reported battery problems that I'm aware of. Now I tend to believe that most of them charge so regularly and hardly ever discharge to the limit that this behaviour actually increases battery life.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
I agree it must have something to do with the battery dying. Ive just set my device to stay on with bluetooth enabled and audio files playing. battery is at 28% right now. i hope it doesn't die at 20%.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
nope it didnt keep on going. died at 20% :mad: so i guess no turning back for the battery now. will have to try and keep it fully charged all the time :S anyone know how much a new battery costs?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
it wouldn't hurt to try radio 1.17 and you still can see how long it lasts in its current condition. These batteries are widely available on Ebay, from very cheap up to very expensive triple sized with extra extended back cover. See for yourself if you trust an ebay seller or if you prefer to shop locally with ebay prices in the back of your mind.

Beware, original HTC batteries are relatively rare on Ebay, if the offer doesn't say "original" be sure it's a clone.

I once bought bad clone batteries for a camera, they came with "3 year guarantee" but the seller disappeared in less than a year.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
ok can i upgrade the radio without changing or affecting the rom n all my saved files etc? would it change anything in the OS? i most probably wont be buying stuff off ebay coz might be too expensive.. wat with all the shipping costs etc amounting to almost the same as the batteries cost. you said once a guy bought a new battery with worse performance. is there any way to check battery performance at the time of buying(ie any softwares)?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] HonkBB:
..

Hi,

I'm using Tofclock WM6 and radio 1.17 - works well and the PDA shuts down somewhere around 3 % !

So long

HonkBB
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
most of the regular people on this forum use radio 1.17 and none of them has so far reported battery problems.

It doesn't prove anything, I've never seen a red car with a flat tyre (true) but I still can't conclude that red cars for some mysterious reason never have flat tyres. There even might be some causal explanation:

-psychology of ppl buying red cars

-I see a lot less red cars than blue, black, white, metalic

-more women than men drive red cars, women are perhaps more careful about buying fresh tyres in time.

Conclusion, it never hurts to try
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] xPreSiDenT:
do i have to hard reset my device after flashing the radio?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] mantd:
From my experience its the battery.

With my previous battery, my hima was shutting down at 20-30% and i couldnt switch on the machine until i charge it.

I bought a new battery , I've experience using my himalaya to 1%, and it can still turn on. :)

-Erman
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] mantd:
no you dont need to do a hard reset. A reset would suffice.

-Erman
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] HonkBB:
...

Hi,

what you discovered is called in science:

ILLUSORY CORRELATION

Maybe, you're right - but we don't have enough statistics to prove if there is really no correlation between radio rom and the battery problem. So lets carry out a poll with users using WM6 and the different radio roms ... then we get exact values ;)

so long

HonkBB
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
I'm not a noob in science but I intentionally try to avoid terms like illusory correlation.

A poll doesn't make much sense in this forum, look at n (=number of replies) in other polls.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] dark_wing:
It does not make sense that battery life in WM6 is much weaker than the 2003 since it is on Flash (persistant storage) and hence the ROM is not functioning most of the time which per my understanding is the cause of battery draining. Hence with the WM6 the battery life should be the same as 2003 if not better right?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
That sounds very logical. You should also expect that WM6 would be much smarter in power management than WM2003, based on the 3 years of extra development time. But it's just not what WM5 and WM6 users experience. Nobody so far reported in these forums to have experienced better battery life than with WM2003. Several people reported drain problems. It quacks like a duck, it walks, swims, flies like a duck, it looks like a duck but logic tells us that we should call it a dog?

No, there is a "logical" explanation, from MS developers point of view. You can read all about it on

http://blogs.msdn.com/windowsmobile/archive/2005/08/01/446240.aspx

http://blogs.msdn.com/windowsmobile/archive/2005/08/03/447404.aspx

http://blogs.msdn.com/windowsmobile/archive/2005/08/10/450186.aspx

http://blogs.msdn.com/windowsmobile/archive/2005/08/11/450591.aspx

So the main culprit seems to be the unattended mode. Fits like a glove to my personal experience:

-testing my device, navigation software on, all connections (BT, IR, GPRS, GSM) on, backlight 100%, constantly recalculating routes, it almost takes me 4 hours to go from 100% battery to totally flat.

-accidentally leaving some animated tasks open in the background, unattended mode while I thought it was suspended (asleep, standby, what's in a name) drained my battery once in about one hour!

But there somehow is another culprit as well. I have no idea what it is but even after a clean reboot my device stays alive almost 4 days on 2003 and "only" 3 days on WM6. I don't care, after draining in WM2003 I need to restore a backup while WM6 allows me to leave it on backup battery in a drawer for a couple of weeks without dropping a single bit.

I wish I knew a way to tell WM6 to use as much power while sustained on battery pack as it uses on backup battery.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] c_shekhar:
Ha Ha Ha !LOL!

I must buy a red car next time..May be it comes with a women in it;) ;) .

Seriously:

It is purely the age factor whick takes the device OFF phenomenon at higher %ge. I am debating on this issue since last 1 1/2 yrs for now. back then my device was shutting down at 10-11% now lately it is shutting down at 22% and other battery at 28% (I have two of the same age).
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
My device shuts at 2% Main Battery and 0% Backup....I cant u se my Phone feture of the PDA due to sum f****** Liqued Damage...maybe thats ONE of the reasons
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] c_shekhar:
lucky indeed. how old is your battery?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
very old....if i PM u its picture u wont beleive that its still running...I accidently even shortted it..the covering on it is melted a little due to the Shock.but it still works
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
my battery

Here how it looks
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] help123:
phone off 39%

ather90 i have same battry like your and also i bought i new battry but my phone stop geting network 39% close on 29% so i am realy confuse where is somthing wrong old and new battry giving same result dmnnn i waste 750 rupes
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
0% backup??? Your device should keep backup to 100% till it shuts off. This sounds like you need to replace your backup battery. When you check it out, you can also see if you can clean up the PCB, it might help you restore the phone function. IMHO the best way to clean PCB's is:

-remove backup battery

-put a deep dish full of demineralised water

-soak the pcb for some minutes

-shake off the water

-rub it with clean demineralised water and a clean tooth brush

-soak again in clean demineralised water

-repeat several times

-take off the water with paper towels, leave it to dry in open air for at least a day

reassemble

test

hopefully cheer
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
no the backup battery is only 0% when i take out the main battery..i took it out yesterday for scanning the battery and posting its image..and regarding the hone function..u wnt believe how happy i am..btw can u tell me whats a PCB

but i will change the battery
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] HonkBB:
I'm not sure about that. My PDA is around 4-5 years old and still using the same battery. And the mda is the whole day in "action" ... as I guess there is no memory effect with li-ion batteries ... maybe old batteries discharge faster but it makes no sense that the pda shuts down at 20% battery capacity ?!?!

So long

HonkBB
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] paulpax:
yes this is true, my PDA is around 5 years old and the battery shuts down at less than 39% using WM6 AND previously using WM2003, the shutdown % for both ROMS is the same. The PDA will just shutdown, and if you leave it for a few minutes, its RESTARTS then you can use it for a few minute, then SHUTS DOWN again.

bought a higher maH Battery and kept the old one as backup, seldom used, now when i use it, it shuts down the XDA2 at 70%.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
PCB stands for printed circuit board. The entire device=

PCB

LCD

antenna

batteries

housing
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
LiIon indeed has no significant memory effect. But they do die, sometimes abrupt, sometimes in steps. WM only reports the amount of energy that theoretically should be left (if the cell would still be healthy).

There is a battery utility that actually records how often you charge your battery and how you use your device, allowing it to calculate how much standby and use time is actually left in the battery. I'm sorry, I can't remember the name of this software. It even has the feature to give every battery you use a number. You should tell it which battery is in use after switching batteries.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
@Maggy

Thank u very much...Now its clear..very clear