Hello fellow xders, I have a problem with my nexus 4, I've tried almost everything but nothing really works, let me tell you the previous build when it's working normally.
When working:
*Unlocked & rooted.
Rom: CM 13 Rom nightly build
Kernel: CM 13 stock Kernel
Recovery: TWRP 2.8
Everything works fine for some months until 2 days ago I tried my nexus for VR using Google Cardboard that I bought online.
After using it, my phone starts turning off by itself randomly, and now I can't even boot to my rom without my charger plugged in.
I've wipe everything, using my new TWRP 3, I mean everything, even my internal storage, but the phone still won't work without the charger plugged in.
So i thought, maybe it's the battery. Please note that my phone never had any problems before, I mean ever.
So i thought battery is the problem, but turns out I can boot to my recovery rom all the time without a problem, the phone turn off by itself only when I tried to install the new CM13 rom, the same thing happened when I tried install another rom.
Does anyone ever have this kind of problem before, i really need help, thanks.
With the phone powered off, does the LED come turn on after inserting the charging cable?
audit13 said:
With the phone powered off, does the LED come turn on after inserting the charging cable?
Click to expand...
Click to collapse
No, it's not turned on like usual. and when i tried to do "Data Format" in TWRP 3.0, it gives an Error, something like /dev error 255, i don't remember the whole line.
It's probably something to do with the memory card error perhaps? What do you think?
Now I downgraded back my phone to stock condition, i unrooted everything, even locked my bootloader back.
Now i'm using stock android 5.1.1, with factory settings, here's some condition I noticed with stock factory settings:
1. I still can't boot properly to my stock rom without the charging cable plugged in. It only shows boot animations for a while and suddenly phone turned off by itself.
2. I can boot into the stock rom with my charger cable plugged in, and after I get inside the stock rom, I can unplugged the cable and everything seems to work normally. So I don't think it's battery problem.
3. I think the problem has something to do with the boot sequence / internal memory / internal memory partition / block, cmiiw
Please help me, I don't know why things go like this after using VR cardboard, I wonder if it's the cause.
Thanks a lot for your reply, sorry for my bad english
After booting into stock, how quickly does the battery drain?
audit13 said:
With the phone powered off, does the LED come turn on after inserting the charging cable?
Click to expand...
Click to collapse
and it's probably caused by the accelometer, it's just my hunch, but when I changed my ROM to CM13, my phone won't auto rotate automatically. probably the CM 13 kernel didn't handle the accelometer correctly. and when I use it for 360 video which use accelometer rigorously, it makes the accelometer worked too hard or something, or the cm 13 kernel didn't handle it correctly and it affect my whole hardware. it's just shooting in the dark, but i hope it helps you with more information a little bit.
audit13 said:
After booting into stock, how quickly does the battery drain?
Click to expand...
Click to collapse
i haven't tried using it for the whole day, but for the past 2 hours it works fine without charging. the drained percentage is also very small, because i don't have many apps installed yet, and i didn't even use cellular data connection. but for phone call or sms it's working perfectly without any problem
audit13 said:
After booting into stock, how quickly does the battery drain?
Click to expand...
Click to collapse
but despite everything, you're right about one thing, my LED doesn't turn on when charging, it's not usually like this. i didn't notice this before, what does it mean?
Wow, this is strange and it does appear that the battery is fine. I don't know what else to suggest as you did everything I would have done.
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
The lack of a led when charging is normal in a stock rom.
---------- Post added at 07:33 AM ---------- Previous post was at 07:29 AM ----------
Hmm, never tried to recalibrate an accelerometer.
I have the same problem, the device just works plugged in charger. I read some threads and the problem in all thread are solved with a battery replacement.
Yep, I'm afraid this is indeed a battery problem. Had the same issue with mine Nexus, it worked as usual, then it suddenly went off and didn't want to boot again without the charger plugged in. Worked perfectly in a recovery, though. Replacing the battery fixed the problem.
gutosilva said:
I have the same problem, the device just works plugged in charger. I read some threads and the problem in all thread are solved with a battery replacement.
Click to expand...
Click to collapse
Hey Gutosilva,
a little late to the party aren't ya?, Sorry you are experiencing this. did you just recently get the phone? try a new battery and this should fix it.
Covert_Death said:
Hey Gutosilva,
a little late to the party aren't ya?, Sorry you are experiencing this. did you just recently get the phone? try a new battery and this should fix it.
Click to expand...
Click to collapse
No, but my Nexus have this issue just recently. A service shop says this is a motherboard issue, I hope isn't. The devive has exactly the same problem in this thread, and I read others similar threads and all were solved changing the battery.
(Sorry for my imperfect English, I not speak english naturally)
I wouldn't trust a repair shop to properly diagnose the issue as it was really only discovered from trial and error.
Batteries should be cheap and fix the issue. either at a repair store if that's what you tell them to do or do it yourself
One question: Should my phone be with the stock rom when the battery is changed? Have any relation or possible problem if another rom is installed?
hastthou said:
Hello fellow xders, I have a problem with my nexus 4, I've tried almost everything but nothing really works, let me tell you the previous build when it's working normally.
When working:
*Unlocked & rooted.
Rom: CM 13 Rom nightly build
Kernel: CM 13 stock Kernel
Recovery: TWRP 2.8
Everything works fine for some months until 2 days ago I tried my nexus for VR using Google Cardboard that I bought online.
After using it, my phone starts turning off by itself randomly, and now I can't even boot to my rom without my charger plugged in.
I've wipe everything, using my new TWRP 3, I mean everything, even my internal storage, but the phone still won't work without the charger plugged in.
So i thought, maybe it's the battery. Please note that my phone never had any problems before, I mean ever.
So i thought battery is the problem, but turns out I can boot to my recovery rom all the time without a problem, the phone turn off by itself only when I tried to install the new CM13 rom, the same thing happened when I tried install another rom.
Does anyone ever have this kind of problem before, i really need help, thanks.
Click to expand...
Click to collapse
Hey man. When you chnange the battery was you nexus 4 with a custom rom already installed? I'm having the same issue and will buy a new battery.
Wagierek said:
Yep, I'm afraid this is indeed a battery problem. Had the same issue with mine Nexus, it worked as usual, then it suddenly went off and didn't want to boot again without the charger plugged in. Worked perfectly in a recovery, though. Replacing the battery fixed the problem.
Click to expand...
Click to collapse
If you can get anyhow the phone to turn on ... with charger...
then install an app called Ampere and chack if battery is charging or not ..
Also if battery is charging fine ..let it go to some 50 - 80 % charged then remove the charger and check at the rate at which battery is draining,,,
Also u can buy a battery and change it your ... but carefull while buying as our device is old and the market is flooded with cheap Chinese stuff..
---------- Post added at 10:07 PM ---------- Previous post was at 10:00 PM ----------
anirudh.88 said:
If you can get anyhow the phone to turn on ... with charger...
then install an app called Ampere and chack if battery is charging or not ..
Also if battery is charging fine ..let it go to some 50 - 80 % charged then remove the charger and check at the rate at which battery is draining,,,
Also u can buy a battery and change it your ... but carefull while buying as our device is old and the market is flooded with cheap Chinese stuff..
Click to expand...
Click to collapse
flashed 2 days back only ..
WIP AOSP 7.0
http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444
working smooth ..only flaw i find is inbuilt music app is not working.. but google music which came with gaaps is working.. and camera app is old...I have yet to root this device, after that will remove the music and camera app.. and get the google stock one..
Related
I dont understand i have tried everything! I must be missing something
I have booted before with no problems aside from the robo voice
I come home in hopes to fix it and now no matter what build i use no matter what zimage i use the phone boots like normal in to Android and then just shuts down.... What am i missing here?
Spent all Morning Flashing rom and radio combos and still the same thing, Reformatted my sd card Nothing.
NO HELP?
this happened to me when i started using my extanded battery, no matter what i did it boots vibrates then shuts, im back to my normal battery all the builds work now, i figured out that the extended battery might need a driver or something.
here the same! with original battery is working
With extanded battery is shutting down! in one line by booting with haret
Chragin off (temp overheat)
battery working with
desirebuild_v5
battery dosent work with
mattcfroyorc1.4
mattcfroyorc1.3a
Wow never even thought about changing back to a stock battery. Or even mentioning that i again
This happened to me when I had a multi-boot program installed on the winmo side. Uninstalled it- booted just fine.
there have been a couple of threads with the same issue.. the devs have been asked about it.. nothing heard back as yet.. but it definitely it is an extended battery that is causing it
Yes the extended battery is it. I read it somewhere in the forums that it is not supported yet as there are no drivers and due to which while booting haret reads the battery temp to be 90 while it actually being ~30 and hence cant boot.
Replace it with stock and you are good to go
Mine is still the stock battery and still does the same thing for all versions of ROM and android too..
kingfisher1111 Mine is still the stock battery and still does the same thing for all versions of ROM and android too..
Click to expand...
Click to collapse
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.
nardone24 said:
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.
Click to expand...
Click to collapse
yes mine is original battery that came out of box with Tmobile..
Any one help me on this issue?
so i've noticed multiple times today (just got it yesterday, rooted) that the charging indicator flashes on and off. this keeps bringing it out of standby. although sometimes the screen turns on without it saying charging but that seems to be a known issue.
but whats up with the charging flashing
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Strange
Never had this issue on my a500 - but have the exact same issue on my Samsung Intercept with a slightly damaged charging port - after unplugging the system will still show as charging and offer to mount as an external storage device - even though it's not plugged into anything.
Had the random screen on when I was still on a 3.0 based rom - have you registered your tablet with Acer and upgraded ota to 3.1? Can also manually flash 3.1 update.
best of luck!
i just updated my last post,
but yeah im on the latest ota 3.1 in the US and registered
lbhocky19 said:
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Click to expand...
Click to collapse
Yes! Easy as hell too.
Check this out, and good luck!
(How to root a500 3.1 stock)
http://forum.xda-developers.com/showthread.php?t=1138228
(Edit: the method you linked to looks like the same method described here at XDA. May not solve your problem)
well cancel my happiness. did a reboot and now it fully thinks its charging. no flickering.
even plugged it in and unplugged and still says charging.
this time i plugged it in and rebooted. at least the notification went away
edit: and its back.
really strange....
May want to just return it and snag a new one if that is easy/possible.
After your full reset did you do any Modding/install any apps? May be possible something you are running is causing the issue, but I am really stumped on this one.
Could always get cwm running and reset the battery cache, but I am pretty doubtful that is gonna do anything.
same problem for me here.though I did not root my device yet.it shows charging with no charger plugged in.also recognized that my battery indicator sometimes remains on a certain percentage and hangs.after a restart it shows the actual battery level.I am on stock rom 3.0.1...maybe I send it back tomorrow.because this is really enoying...
yup. mine just started doing the hanging at one percentage til reboot
don´t know if it´s software or even hardware related
the fact that we have identical problems makes me think software
Hi.
I have been having very strange issues with my battery, and I hope that there are some people here who know about the hardware more than I do and might be able to help me.
First of all, the battery indicator is unstable, it can show me 49% of battery and suddenly tell me there is only 10% left. I am attaching a screenshot of my battery stats where those spikes are visible.
Or worse, the battery indicator might suddenly jump to 0% and make the phone turn off, then when I turn it on it shows that it has at least 25% left.
Second problem, I very often can't charge the phone. I connect the charger, and the notification LED doesn't light yellow, instead, the whole battery menu just disappears from the settings so I can't access it... And after a few hours it might begin actually charging, then the menu is visible.
Battery temp always shows -30 degrees celsius, or some similarly impossible temperature.
After trying to switch to a different kernel (from unleashed to hells core) and to a different rom (from purity to android L and liquidsmooth) I decided this is an hardware problem and bought a new (hopefully original) battery on ebay.
I installed the new battery. Now it does work a little bit better, but still, the problems persist.
Is there anything I can do, before buying a new phone?
It doesn't have warranty anymore, it's one and a half years old.
Thanks
Definitely battery failure. Replace the battery or buy a new phone
Sent from my Nexus 4
This is most definitely due to a faulty battery, so time to get a new phone. At least Shamu's release is right around the corner.
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
romitkin said:
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
Click to expand...
Click to collapse
I'd try comletly stock rom, and see if the issue persists.
Yup, stock ROM always first step, then replace battery. If it still persists, than it is most likely some other hardware issue that might not be worth it to replace.
Sent from my Nexus 4 using XDA Free mobile app
romitkin said:
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
Click to expand...
Click to collapse
Exactly same situation with my Nexus 4. Battery being replaced and it's not better. Just ordered a Moto X 2014 and waiting for it.
I tried the stock ROM. And it didn't solve the problem. Is there anything else I can check about the hardware before replacing the whole phone?
romitkin said:
I tried the stock ROM. And it didn't solve the problem. Is there anything else I can check about the hardware before replacing the whole phone?
Click to expand...
Click to collapse
Have you just flashed a stock rom, or completley restored the phone to factory settings using google factory images?
Serris said:
Have you just flashed a stock rom, or completley restored the phone to factory settings using google factory images?
Click to expand...
Click to collapse
I used a factory image, it deleted everything including my sd-card etc
romitkin said:
I used a factory image, it deleted everything including my sd-card etc
Click to expand...
Click to collapse
Hmm unfortunately this leaves me without any ideas. May ask how old is your phone and did you drop it previously?
It's one and a half years old, and well, I did drop it a lot.However, I always used a good case (ringke fusion) and I don't recall any recent drops prior to the time the problems started.
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
burnoutslo said:
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
Click to expand...
Click to collapse
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
xzces said:
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
Click to expand...
Click to collapse
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
afarnedi said:
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
Click to expand...
Click to collapse
sushant6786 said:
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
Click to expand...
Click to collapse
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
I had once this issue on cm12.1 oneplus 2 . What I did to solve this problem successfully.
1. I removed case from my phone . This causes grounding issues sometimes.
2. Reflashed OxygenOS.
3. Then I flashed cm on top of it. Wiped data, cache, dalvik only. didn't wiped system partition.
4. That's it. I'm. I'm typing right now while charging. Totally perfect.
I noticed it more with my cheaper USB C cables.
I bought a half dozen and some are better than others.
the boxed cable that was stock is the best by far.
Yesterday i aux in my phone to a audio player and observed the same problem again with touchscreen. Feeling very annoyed because of this and other bugs.
My phone used to lock up completely for up to 30 seconds after plugging in the charger. After move to cyanogenmod 13 this does not happen anymore, so obviously a bug in OxygenOS.
Skickat från min ONE A2003 via Tapatalk
Hmm, this is generally not a problem with your phone or your software, but relates to the power supply. Noise in the power or grounding issues specifically cause the 'ghost touches' and erratic behaviour you describe. If you are lucky, your charger and cable are also fine and the issue is with the power socket, in which case you need an electrician to come and take a look. If its the charger/cable, then simply get a new one and you are good to go.
To figure out where the issue is, start by using the same charger + cable in a different location (completely different physical location). If the problem persists, then try changing the cable in that same location. If it still persists, try a different charger.
If the problem is NOT there at the alternate location, then chances are its your wiring and you need an electrician to sort this out for you.
Hi,
I know this has been discussed many times, but I have something more to share regarding this, and maybe it can help anyone find a solution.
My X820 arrived last Friday, bought from Geekbuying. It had Indian 19s ROM, although it might be slightly modified by the shop.
Fingerprint was working well, but I wanted a better and more optimized ROM, so I flashed TWRP and got Small EUI. The worst thing is that I forgot one important step (yes, backup) and flashed the ROM right away.
Fingerprint kept working, but got worse. On Indian 19s, it unlocked the screen or apps very quickly, but on Small EUI it took it 1 or 2 seconds, so on Sunday morning I tried the calibration option under settings. That's the moment the fingerprint scanner stopped working. I spent some time on Sunday, and most of Monday trying different ROMS, but nothing worked. The sensor would not react at all, and would not let me add fingers.
Yesterday, I found a thread, on a OnePlus 2 forum, where people described a similar issue on that phone, and the way they got the sensor to work again: they drained the battery down to 0%, to the point when the phone would shut down by itself. Then they charged the phone again, and the sensor came back to life.
I tried that (I'm now on Cuoco92's 93c ROM), and after turning the phone on again, the sensor seemed to keep failing, but there was a difference. Before that, it wouldn't react at all, but this time, a message instructed me to keep my finger on the sensor for a longer time and to try again. This message was not appearing before.
I left the phone alone for the night, as I use it as an alarm clock, and in the morning I tried again, and it worked. I was able to register fingers and the sensor began working as usual, and unlocked the screen almost instantly.
But now,. two hours later, it is dead again. I've noticed it doesn't unlock the screen. I've just tried to remove the fingers I had registered earlier and see if I can add them again, but it doesn't work. This time, there's no message that instructs me to keep my finger on the sensor for a longer time, or to try again.
Well, I definitely haven't solved the issue, but I may have found something. Maybe others with dead sensors can try this solution and report back.
To drain the battery, I used this app: Your Battery Drainer
P.S.: BTW, I decided to try draining the battery because I remembered that when first I got the phone, the battery was empty. I almost freaked out when I tried to turn it on for the first time, as it wouldn't turn on, but it turned out to be that the battery was empty. After I left the phone charging for a while, it turned on normally.
I also just got my phone today 6gb RAM, 64gb UFS2.0.
Fingerprint very fast with 19s ROM.
I think I will stick with this ROM forever.
kkcheong said:
I also just got my phone today 6gb RAM, 64gb UFS2.0.
Fingerprint very fast with 19s ROM.
I think I will stick with this ROM forever.
Click to expand...
Click to collapse
You should, that was my mistake (I think) besides the LeEco software, and maybe fp hardware, not being too good. I just flashed the stock Indian 19s ROM again and the sensor is not working. I'm now downloading the Chinese 16s version, which others reported helped them revive their sensors. If the Chinese ROM doesn't work, I'll flash the Indian ROM again and try draining the battery in the evening, as I did yesterday.
jman0 said:
You should, that was my mistake (I think) besides the LeEco software, and maybe fp hardware, not being too good. I just flashed the stock Indian 19s ROM again and the sensor is not working. I'm now downloading the Chinese 16s version, which others reported helped them revive their sensors. If the Chinese ROM doesn't work, I'll flash the Indian ROM again and try draining the battery in the evening, as I did yesterday.
Click to expand...
Click to collapse
Good investigative work. I wish you good luck and will be reading this thread until you get it working.
I am quite happy to get this for USD186 for current x820 version even though without headphone.
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
jman0 said:
My X820 arrived last Friday, bought from Geekbuying. It had Indian 19s ROM, although it might be slightly modified by the shop.
Click to expand...
Click to collapse
How do you know 19s is modified by the shop?
Actually I just got the phone. I will report back if it does in 7 days. Haha.
kkcheong said:
Good investigative work. I wish you good luck and will be reading this thread until you get it working.
I am quite happy to get this for USD186 for current x820 version even though without headphone.
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
How do you know 19s is modified by the shop?
Click to expand...
Click to collapse
I don't know, maybe not. Anyway, I'm on the Indian 19s again and the fingerprint sensor is not working. If I have the time, I'll try draining the battery again this evening, and will report back tomorrow
jman0 said:
I don't know, maybe not. Anyway, I'm on the Indian 19s again and the fingerprint sensor is not working. If I have the time, I'll try draining the battery again this evening, and will report back tomorrow
Click to expand...
Click to collapse
Will wait for your result . 19s is actually badly optimized. I got 99k in Antutu.
I try every method with roms with apps but fingerprint newer works.
today i read this thread, i try now to drain battery with this app and i cant believe fingerprint start work.
But how long fingerprint will work.
Is there a possibility quick charge 3.0 heat kill the fingerprint sensor? Did you enable quick charge in the menu? Mine one still disabled and I am now worry to turn it on.
sina5566 said:
I try every method with roms with apps but fingerprint newer works.
today i read this thread, i try now to drain battery with this app and i cant believe fingerprint start work.
But how long fingerprint will work.
Click to expand...
Click to collapse
Just try to flash the CN Firmware S16 not the whole Rom
kkcheong said:
Is there a possibility quick charge 3.0 heat kill the fingerprint sensor? Did you enable quick charge in the menu? Mine one still disabled and I am now worry to turn it on.
Click to expand...
Click to collapse
That might be it. Today my sensor is not working, after draining the battery, but last night, when I charged the phone again, I did it with the fast charger. When I have the time, I'll try again with a pc or just disabling fast charging. Maybe you have a point there. Nice one.
Blubber120 said:
Just try to flash the CN Firmware S16 not the whole Rom
Click to expand...
Click to collapse
You mean the modem files, don't you? That was also one of my next steps, but first I'll try draining the battery again and not using quick charge afterwards. When I first got the phone with an empty battery, fast charging was not enabled, so it took the phone ages to charge, but the fp sensor worked. I think we may be close to a solution for everyone, and something LeEco should know. Maybe they can implement an slower fast charge which doesn't interfere with the fp sensor.
Anyway, fp sensor was not my main reason for purchasing this phone, so it's not that high on my priority list.
sina5566 said:
I try every method with roms with apps but fingerprint newer works.
today i read this thread, i try now to drain battery with this app and i cant believe fingerprint start work.
But how long fingerprint will work.
Click to expand...
Click to collapse
As another user suggested, disable fast charging, if you have it enabled, and see if fp sensor keeps working afterwards. It's good to know this method worked for you, too
Well, after flashing the Indian 19s ROM and draining the battery, nothing changed, but it could still have something to do with fast charging. Although I had it disabled, when I plugged the phone in, using LeEco's original charger, it charged the phone fast, rather than slow, so I think that maybe it didn't work because of that. I'll repeat the process again, this time using an old regular slow charger.
Did anyone else tried? Did you succeed?
jman0 said:
Well, after flashing the Indian 19s ROM and draining the battery, nothing changed, but it could still have something to do with fast charging. Although I had it disabled, when I plugged the phone in, using LeEco's original charger, it charged the phone fast, rather than slow, so I think that maybe it didn't work because of that. I'll repeat the process again, this time using an old regular slow charger.
Did anyone else tried? Did you succeed?
Click to expand...
Click to collapse
I scared that quick charge heat already kill the finger print. I mean hardware is dead.
But I still support support experiment to fix the fingerprint.
I think the FP problem has to do with HEAT. The FP failed to work when I was on holiday in Florida a few weeks ago. When I returned to the cool Toronto ,Canada, it is back to normal - works most of the time.
[email protected] said:
I think the FP problem has to do with HEAT. The FP failed to work when I was on holiday in Florida a few weeks ago. When I returned to the cool Toronto ,Canada, it is back to normal - works most of the time.
Click to expand...
Click to collapse
Fast charge generates a lot of heat, that's why it's our main suspect right now
Did you flash 23s modem? not the rom, only the modem and after the update of modem clean install of the rom ?
I have tried.. draining all battery from 25% to 0% and smartphone Switch off and after i charged almost 50% without fast charge and tourn on but unfortunatly fp still dont work
Listen guys, I hate to burst your bubble, but I have to... For starters, there are MANY people in the forums flashing all sorts of ROMs and different things, and their fingerprint readers still work. I can say the same thing for Quick Charge 3.0, everybody uses it, so I highly doubt that either of these things are causing the hardware failure.
Also, remember that OnePlus uses Dash charge and all heat is relegated to the charger and not smartphone.
I own two X829's that I bought from Banggood for $196 each a few months ago, and the fingerprint readers still work after countless flashing and charging, and believe me the phone has gotten incredibly hot at times too.
Early on though, I thought that my fingerprint reader had died because it stopped working on when I moved to the Nougat ROMs and later I found out that I needed a more recent modem for the fingerprint reader to work (23S or 419D), but what I have done in a panic was contact Banggood and I told them that my fingerprint reader had died on both my phones. I told them that I had already troubleshooted and consulted the forums. I told them that it was a common defect. I made a YouTube video for them showing the problem. They told me that I could return it to them to China and that they would refund me, but I told them that it cost too much to ship to China and that the last time I returned something to them it got lost in the mail. They then said that I could take the phones to a local repair shop and that they would refund me the cost of the repair, they said that the most they could refund me was $116, so I made a fake invoice for $116 and send it to them because I had bought two fingerprint readers from AliExpress for $7 each and wanted to repair them myself.
In the end I never needed the fingerprint readers because I was wrong and sold them on eBay, and Banggood refunded me the $116 for the so called repair, so in the end I only paid $82 for my Le Max 2. Hope this helps!