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!
Related
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..
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.
About 2 months ago, my g4 plus started to power off on its own whenever on a battery percentage lower than 50%. This has been very bothersome to me. It powers off usually when playing a video or playing music through the speakers. Can anybody pls offer a solution?
noobplayer551 said:
About 2 months ago, my g4 plus started to power off on its own whenever on a battery percentage lower than 50%. This has been very bothersome to me. It powers off usually when playing a video or playing music through the speakers. Can anybody pls offer a solution?
Click to expand...
Click to collapse
1) Try a factory reset
2) Send the phone to a service center
noobplayer551 said:
About 2 months ago, my g4 plus started to power off on its own whenever on a battery percentage lower than 50%. This has been very bothersome to me. It powers off usually when playing a video or playing music through the speakers. Can anybody pls offer a solution?
Click to expand...
Click to collapse
rooted, unlocked bootloader?
Sent from my XT1254 using Tapatalk
Same problem here. About 2 or 3 months with this problem.
What i got?
This doesn't happen when the phone is connected to charger.
It is almost always related with speaker, (notifications, music, youtube)
Also with camera (snapchat, stock camera)
The problem happens hardly ever when you are using a ROM (7 days with RRemix, only 1 restart - instead of- 5 power offs with stock rom every day)
I dont remember if it also happened in Marshmallow BEFORE installing any nougat firmware.
I have never read or heard about this bug in an European or USA's Moto G4 or G4 plus.
Everybody with this problem has had been using turbo charger every day.
Happens with locked or unlocked bootloader
If you're not agree with something of that, tell me, so i can delete it. (with proofs of course)
Solutions
Some users reported:
Disconnecting the battery for 30 minutes solved de problem, (i will try this, you have to open the device to do it)
Other users affirmed that changing the battery will solve the problem, i will do it if the the other solution doesn't work.
Calibrating the battery didn't work for me (3 days of full charges and discharges with 6 hours of wait to charge when the battery is 0%)
I'm really decided to fix this problem, for me and for everybody, because it is very annoying
ivan290 said:
Same problem here. About 2 or 3 months with this problem.
What i got?
This doesn't happen when the phone is connected to charger.
It is almost always related with speaker, (notifications, music, youtube)
Also with camera (snapchat, stock camera)
The problem happens hardly ever when you are using a ROM (7 days with RRemix, only 1 restart - instead of- 5 power offs with stock rom every day)
I dont remember if it also happened in Marshmallow BEFORE installing any nougat firmware.
I have never read or heard about this bug in an European or USA's Moto G4 or G4 plus.
Everybody with this problem has had been using turbo charger every day.
Happens with locked or unlocked bootloader
If you're not agree with something of that, tell me, so i can delete it. (with proofs of course)
Solutions
Some users reported:
Disconnecting the battery for 30 minutes solved de problem, (i will try this, you have to open the device to do it)
Other users affirmed that changing the battery will solve the problem, i will do it if the the other solution doesn't work.
Calibrating the battery didn't work for me (3 days of full charges and discharges with 6 hours of wait to charge when the battery is 0%)
I'm really decided to fix this problem, for me and for everybody, because it is very annoying
Click to expand...
Click to collapse
This thread is one of the first I've heard of this issue. I've had my G4 for about 3 months so far and discharging works fine- regardless, this definitely reeks of a hardware problem though.
Motorola Service Centers WILL take your phone even if it's out of warranty and the battery is failing (just make sure to reflash stock ROM). Or, you can purchase a battery from WitRigs for $20 USD (several weeks shipping however) and replace it yourself.
ivan290 said:
Same problem here. About 2 or 3 months with this problem.
What i got?
This doesn't happen when the phone is connected to charger.
It is almost always related with speaker, (notifications, music, youtube)
Also with camera (snapchat, stock camera)
The problem happens hardly ever when you are using a ROM (7 days with RRemix, only 1 restart - instead of- 5 power offs with stock rom every day)
I dont remember if it also happened in Marshmallow BEFORE installing any nougat firmware.
I have never read or heard about this bug in an European or USA's Moto G4 or G4 plus.
Everybody with this problem has had been using turbo charger every day.
Happens with locked or unlocked bootloader
If you're not agree with something of that, tell me, so i can delete it. (with proofs of course)
Solutions
Some users reported:
Disconnecting the battery for 30 minutes solved de problem, (i will try this, you have to open the device to do it)
Other users affirmed that changing the battery will solve the problem, i will do it if the the other solution doesn't work.
Calibrating the battery didn't work for me (3 days of full charges and discharges with 6 hours of wait to charge when the battery is 0%)
I'm really decided to fix this problem, for me and for everybody, because it is very annoying
Click to expand...
Click to collapse
Thanks man!
Appreciate the help. But can you please disconnect your battery ASAP and share the result? Because after my phone's battery goes below 50, it is hardly usable at all, powering off at least 3 times continuously.
Yes exactly the same happens to me, also with more than 50%.
I will try that battery disconnecting and i'll report!
ivan290 said:
Yes exactly the same happens to me, also with more than 50%.
I will try that battery disconnecting and i'll report!
Click to expand...
Click to collapse
Any developments?
OK, i couldn't open my device because of a problem with the screws, so i gave up and i sent my device to a particular cell phone repair house, they replaced my battery, until now (8 hours) i can see the bug is fixed. My phone doesnt power off doing the same that before replacing the battery would had ended up in a power off... Also i noticed the bug with camera is fixed too, the problem of dark photos with flash.....
Xt1643(indian version)
I thought I am the only person having this issue. Replacing battery helped?or any other method if worked for you??
Also battery's cost?
saurabh8263 said:
Xt1643(indian version)
I thought I am the only person having this issue. Replacing battery helped?or any other method if worked for you??
Also battery's cost?
Click to expand...
Click to collapse
Please read the thread and find your answers first.
strongst said:
Please read the thread and find your answers first.
Click to expand...
Click to collapse
I did before posting. I mentioned xt1643 at first to know if any Indian guy faced this(or in future will read this) so he would let me know the price if he had his battery replaced. And also to know if changing battery solved their prob temporary at that time or permanently.
Same problem here, I decide buy a new battery. Sadly in my country I only find generic batteries . It's the only thing left for me to prove. I had been having lots of problems with that phone (ghost touch, yellow screen and now the battery).
I bought it in the US so I don't have warranty here.
No more Motorola-Lenovo for me, I'm going to change it as soon as I can.
I bought my Moto G4 Plus (XT1641 [Canada & Mexico variant]) 1 month ago. It came with Android 6.0.1, but i installed the Nougat OTA automaticly (so i did not test marshmallow). Well i get some spontaneous shutdowns too, when i was on stock rom.
This issue is similar to the one that has the Nexus 6p (zRam conflicts). What i did to stop the shutdowns is disable zRam and KSM, you can install ElementalX kernel and with a kernel managging app like EXManager (recommended) or kernel adiutor just disable the mentioned features.
If you want to remain with the stock kernel just follow these steps: https://forum.xda-developers.com/moto-g4/development/mod-disable-zram-t3435613
I recommend you to read the posted comment by EarlyMon in the page 2 of the thread, so you will know exactly what are you doing by disabling the zRam (basicly, boosting your SD617).
If this helps you, let me know.
This happens only when I install any custom rom...the phone works fine with x720 5.8.018s version...anything apart from that device will shut down every 2-3 minutes ...very strange behaviour ...any one has any idea ?
any custom rom , android 6 or 7 , AOSP or stock based, it will boot fine and after initial setup , it will work for 3-4 minutes and then suddenly device shuts down. .. when i boot it up again , same thing happens, in one minute shuts down.
if i flash 5.8.018s stock rom , everything works fine....and it doesnt shut down...
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
marik1 said:
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
Click to expand...
Click to collapse
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Manan79 said:
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Click to expand...
Click to collapse
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Manan79 said:
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Click to expand...
Click to collapse
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
Click to expand...
Click to collapse
On my equipment too !!
Andresdsr said:
On my equipment too !!
Click to expand...
Click to collapse
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
mchlbenner said:
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Andresdsr said:
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Click to expand...
Click to collapse
Does anyone completely solved the shutting down issue on x720? I remember the same issue with the stock rom when i was getting the phone (5.8.018). but this rom could have been a shop rom, cant remember.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Click to expand...
Click to collapse
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
sk8223 said:
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
Click to expand...
Click to collapse
Thanks for the information.
Could be possible... If I'm shaking the phone like a cocktail-mixer, it feels something loose inside it and this could be the battery of course which could be not fixed correctly. But I am sure, that this issue has also something to do what is happening on the phone currently. Sometimes I am going to bed and the phone does not move for 8hrs, it simply lays on the table. In the morning, it is shutted down. Need to hold the power button for about 10sec to restart the phone (usually hold 2sec to power on). Sometimes (not really often) it warm-starts automatically.
I think this could be also a memory issue or internal storage. Yesterday I was playing a game (Bowling by Jason Belmonte) and after 3min, the phone hung up, display remains on, no reaction on pressing the hardware buttons, waiting 5min... nothing happens. So I pressed the power button 10sec, phone seems to reboot normally, but it take a bit more time in my oppinion. Now after entering the pin, some phone configurations were resetted to default, but not all. Playing this came, it sometimes happened, that the phone switches off (with one vibration). Rebooting with a 10sec press and it runs again normally. This time phone hung up and some configurations were resetted to default. WTF?
Today I have played Hmmsim 2. Phone hung up again, pressing the power button 10sec, phone begins to reboot, but rebooting never finished (waiting for about 1-2hrs). Long Press power button (10sec) to try to reboot again - same behaviour, never ending ROM loading screen. Wiped to factory via TWRP and the phone reboots again, but all configurations lost, like freshly installed rom. OK, whatever, using the google backup for apps and so on... when installing the apps in the background, the phone reboots about 3-4 times, app installations not finished. Cancelled and shutting the phone down to TWRP, where I am now...
What I will try to say is, that whenever the storage or memory is used to much or something like that, the phone begins with that behaviour.
And now I am thining about what to try next. I think I will try to flash the stock recovery via TOOL ALL IN ONE then flashing a stock rom like 5.9.023S.
I am still not sure of a hardware issue...
peed_neslo said:
I am still not sure of a hardware issue...
Click to expand...
Click to collapse
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
sk8223 said:
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
Click to expand...
Click to collapse
Thank you very much!
I am sure that the phone was doing the same on stock rom, but maybe fewer times. I have flashed a stock based rom now (Turbos mini 5.9.023s) and the issue still exists, but now the phone reboots normally more often than going into edl mode (emergency mode). I have found an old thread here on XDA and the issues described there sounds nearly the same. Finally the user in this thread also had hardware issue.
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
peed_neslo said:
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
Click to expand...
Click to collapse
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
Click to expand...
Click to collapse
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Admittedly I'm not sure at all if this issue was already present after starting the phone for the first time. One of the first things I have done during the initial setup wizard was using the integrated data transfer app by LeEco (scanning a QR code with the old Xperia Z, downloading app to transfer data to the x720). This app establishes a Wifi direct connection between both phones to transfer the data like apps and other stuff. This transfer process takes at least 6-7 hours and during that process I am sure that the phone was not rebooting a single time. Maybe a specific app or background process of an app causes this irregular rebootings. I have not testet this. I have installed the most common of my apps also using different custom ROMs later.
On the current ROM (Turbos mini 5.19.023s) I have now looked into the last_kmsg.log file severel times after the phone was hard-rebooting (not to emergency mode - the phone is switching down to emergence mode really rarely since I have flashed the stock based ROM) to debug for a kernel problem and the power off reason seems to be ""Triggered from PS_HOLD (PS_HOLD/MSM controlled shutdown)". In the log file I could also find some "kernel panic" entries. So I have a little gleam of hope that the issue is not a hardware problem. I have to test a bit more with the stock recovery/ROMto gain a better knowledge of the issue. I think I will post this into the ROM topic to ask a developer.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Finally - I got it working without any problems now!
Happily it seems to be not a hardware issue. I have flashed the Grossoshop ROM and Recovery via a provided .bat file. This .bat file has flashed the recovery first via fastboot, then the ROM via fastboot. This Grossoshop ROM was based on 5.8.018s I think. Then I have updated TWRP Recovery to the latest version via TWRP itself (flashed the new image). Then I have flashed Mauro's 2.2 (which is based on 5.9.023s) and it is running great! Super performance, no extrem battery drain, no reboots, all is working (except the chinese design downloads as I cannot create a Leeco account from Germany). But now I'm satisfied. :good::laugh:
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
Thanks!
Click to expand...
Click to collapse
My x720 has done the same to me a couple of times now, Vibrates once and turns off and I have to hold the power button for a few seconds longer to turn it back on again which is odd.
The battery was charged over 50% % 70% at the times it happened and I wasn't even using the phone, It was just sat on the table in front of me.
I didn't have any problems at all until a few days ago when it first shut down.
I'm using Oreo - AICP 13.1 from here - https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
The problem now is I don't know where to start troubleshooting When I get time I am planning on a clean wipe and fresh install of AICP again to see if that solves the problem
When using this ROM does your phone heat up a lot.
Sent from my LEX727 using xda premium
Did you manage to fix the problem somehow?
What I flash for fingerprint back to work ...?
linage till latest...
RR
Aex
Stock 15s/19s/23s/26s
28s(customised)
even modem ...
All gone wrong....
The fingerprint scanner has never worked good on this phone. I would forget about it
Sent from my Le X820 using Tapatalk
reefmonger said:
The fingerprint scanner has never worked good on this phone. I would forget about it
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
I cant say that. For me fingerprint works fast and good.
A friend with a S7 has got no better fingerprint detection
I would suggest to install the latest modem
I've tried everything and mine doesn't work. It worked for two days, then died, and two days later it revived for two hours, after trying the battery drain trick that seemed to work on other phones. It then died again, and hasn't worked ever since. Now I don't expect it to work, and I live happier without worrying about it. Unless someone comes up with a "magical" solution, which I highly doubt. The phone can work without it and the fingerprint scanner is not even among the main 5 reasons why I bought this phone (those being RAM size, screen size, screen resolution, storage capacity, camera quality)
Did you try to update the modem firmware?
IF not, download 23S version and flash in recovery.
https://yadi.sk/d/5v2p3F7o3GJBxn/China
Beackman said:
Did you try to update the modem firmware?
IF not, download 23S version and flash in recovery.
https://yadi.sk/d/5v2p3F7o3GJBxn/China
Click to expand...
Click to collapse
Tired but nothing worked flashed modem 26s/23s both
jman0 said:
I've tried everything and mine doesn't work. It worked for two days, then died, and two days later it revived for two hours, after trying the battery drain trick that seemed to work on other phones. It then died again, and hasn't worked ever since. Now I don't expect it to work, and I live happier without worrying about it. Unless someone comes up with a "magical" solution, which I highly doubt. The phone can work without it and the fingerprint scanner is not even among the main 5 reasons why I bought this phone (those being RAM size, screen size, screen resolution, storage capacity, camera quality)
Click to expand...
Click to collapse
I bought because of the specification.
meetgajjar31 said:
Tired but nothing worked flashed modem 26s/23s both
Click to expand...
Click to collapse
But you cleared cache and dalvik cache? if yes, the fingerprint has a hardware problem.
You can find all the firmwares here. 419D or 26s have been reported to fix the fingerprint scanner.
fingerprint authentication
In my case, fingerprint authentication now works after burning slim7.
https://forum.xda-developers.com/le-max-2/development/7-1-2-slim7-lemax-2-t3636674
[email protected] said:
In my case, fingerprint authentication now works after burning slim7.
https://forum.xda-developers.com/le-max-2/development/7-1-2-slim7-lemax-2-t3636674
Click to expand...
Click to collapse
I also tried that (and the rest of the Android 7 ROM's) and got the same result: nothing. I guess mine has a hardware problem
try calibrating the fingerprint sensor. Seems to work fine after that.
anmolkakkar said:
try calibrating the fingerprint sensor. Seems to work fine after that.
Click to expand...
Click to collapse
My fingerprint sensor died right after using calibration. The sensor accuracy seemed bad (it would unlock just 1 out of every 3 times, even after having registered the same finger twice, as recommended by many people) so I decided to try calibration. I calibrated the sensor and it died.
jman0 said:
My fingerprint sensor died right after using calibration. The sensor accuracy seemed bad (it would unlock just 1 out of every 3 times, even after having registered the same finger twice, as recommended by many people) so I decided to try calibration. I calibrated the sensor and it died.
Click to expand...
Click to collapse
That's sad. This trick has always seemed to work for me.
my fingerprint sensor started to vibrate after update just the modem firmware to 23s chinese
and i'm still on the indian stock firmware 19s
But I am still unable to complete the registration process, it vibrates 3 or 4 times and stoped
i guess i will try again after my phone cool down
sorry for my english
Mo908 said:
my fingerprint sensor started to vibrate after update just the modem firmware to 23s chinese
and i'm still on the indian stock firmware 19s
But I am still unable to complete the registration process, it vibrates 3 or 4 times and stoped
i guess i will try again after my phone cool down
sorry for my english
Click to expand...
Click to collapse
That's what happened to me when my sensor came back to life temporarily. It started vibrating but did not register the fingers, just kept telling me to try again. Next morning it registered the fingers, but the sensor died again two hours later
jman0 said:
That's what happened to me when my sensor came back to life temporarily. It started vibrating but did not register the fingers, just kept telling me to try again. Next morning it registered the fingers, but the sensor died again two hours later
Click to expand...
Click to collapse
I have succeeded to register my finger twice !
and it works fine for now
Mo908 said:
I have succeeded to register my finger twice !
and it works fine for now
Click to expand...
Click to collapse
Lucky you. I hope it lasts for you
As a last resort, I just tried flashing the latest Cuoco92 ROM via flashboot, and that didn't help, either, so I think I'm definitely giving up on this. I've been enjoying the rest of the phone features with no problems, but this fingerprint issue, although it lets you keep using the phone, is quite annoying, and proof (again) of how disastrous (if not nonexistent) Chinese QC is. Sometimes I even think about filing a dispute through Paypal and getting a refund.
My FP dead after less than one week I got Lex829 now I got the phone almost 6 months. I was running Tora33 23S stock rom for long time with the dead Fingerprint. Recently I installed (flash by TWRP) official stock Eui rom 26S and tried test Fingerprint just for fun, miracle does happen it came back alive and still working until now with stock 26S rom. FP speed kinda slow but its ok for me just glad its working again