Database Users

SGS2 Official firmware Bugs

Not everyone flashes their phone, but all of us suffer from bugs.
I thought of starting an exclusive thread just for discussing the bugs present on the official SGS2 Firmware.
With the experts here, hopefully they can be clarified, resolved and become history
So, i'll start with the bugs i found.
My firmware version is I9100GDDKL1
First issue
When i get a call and answer it, the screen times out, as the proximity sensor signals it to. But often AFTER the call, and after i take the phone away from my ear to hang up, the screen does not come back again, instead it goes blank black. The call is still on as i am not able to press the end call soft button.
Pressing the home key OR the power key have no affect, it last for 10-20 seconds maybe and then it comes back on its own AFTER the person on the other side hangs up.
Any ideas? This is a sensor, or a software glitch?
Second Issue
Sometimes the phone just loses connectivity. Alot of times its within the city. Its odd, because normally others using the same network do not face this issue.
I have to then manually re-connect to the network.
What issues can these be?
Third Issue
I have noticed this twice now. Phone starts acting funny, as in no signal and does not restore it. I restart it, but when i do, the entire home screen and app drawer is gone. Its blank. All other phone functions work just fine.
I restart again a couple of times, but no luck. So i finally open the back cover, take out the battery, sim and SD Card and put them back again. After that when i switch it on again, it works just fine.
Software or Hardware problem?

This thread is a great idea i think.
My firmware version is I9100XWLP4.
I have only one issue, the same as the first issue in the op, been using this firmware for about a week now, and thats the only problem i have come accross so far.
Any insight would be appreciated.
Thanks
Jesse

My PDA is i9100XWKI4 and GB on it.
First two issues are happening with my SGS2 also, but twice in a week or thrice in a week only. I think proximity sensor have some HW issue.
For calls, even phone shows good signal, but calls are dropped, before I thought it was the problem with other end party, but realized that it is SGS2 problem.

My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Sent from my GT-I9100 using xda premium

Azax said:
My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Click to expand...
Click to collapse
We can solve alot of issues by simply flashing it, but i wanted to know if there is some way that we can solve them with simpler adjustments/enhancements?
Also if we conclude that something is an hardware issue, then we should just go to a service center and get it corrected, shouldn't we?

There isn't a great deal you can do about most 'problems' if you stick to stock & don't root or run custom firmware.
Short of sending it back to Samsung. Who will probably only flash the latest firmware (if there is any) if the problem isn't hardware related. Which you could easily do yourself.
Rooting/running custom firmware gives you the ability to solve problems that otherwise wouldn't be fixable (and definitely produces problems that otherwise wouldn't happen as well sometimes obviously).

I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
I think all do update their firmware. I Infact changed to the latest one recently, but it didn't do any good.
I am not against flashing man .
Just keeping it as a last resort.

sk1989 said:
I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
ICS BUGS thread search please we dont need another one .
Hardware is relatively simple if you do not have a problem on GB firmware then it is not hardware .
jje
Click to expand...
Click to collapse

This is not for ICS alone.
You mean to say there can be NO hardware fault at all?

[Q] Should I return my yureka phone?

Hello Yureka Owners,
I got my Yureka from Amazon on 8th March. The below mentioned issues are forcing me to consider returning this device via the amazon return order service.
Battery not charging upto 100% even after continous charging for more than 9 hours
Random reboots
Reboots during on going phone calls (specifically when headphones are used for calls/also happened randomly for certain phone calls without headphones)
Burn smell at the headphone jack when using headphones
Device heating up in general
I have the latest cm11 proximity sensor bug fix update preinstalled in my phone. Please suggest whether to return this device or keep it? Your prompt response will help me in making a fast return decision.
Kind Regards,
Shreesh
Edit: Have charged with the phone switched off,still at 99%
And have done factory reset too.

Shreesh_the_beginner said:
Hello Yureka Owners,
I got my Yureka from Amazon on 8th March. The below mentioned issues are forcing me to consider returning this device via the amazon return order service.
Battery not charging upto 100% even after continous charging for more than 9 hours
Random reboots
Reboots during on going phone calls (specifically when headphones are used for calls/also happened randomly for certain phone calls without headphones)
Burn smell at the headphone jack when using headphones
Device heating up in general
I have the latest cm11 proximity sensor bug fix update preinstalled in my phone. Please suggest whether to return this device or keep it? Your prompt response will help me in making a fast return decision.
Kind Regards,
Shreesh
Click to expand...
Click to collapse
Hi Shreesh,
The problems you've mentioned above have solutions, For the battery, It will never charge to 100%, Simple reason for it is overcharge current. To Protect the phone from damage, the phone cuts the supply of current and stops at 99% but it'll be surely fixed in updates...
For random reboots, have you tried Factory resetting your phone? If not then try to or flash CWM Backup of Yureka.
The burning smell, Hmm... That is weird but It happens when some heavy work is processed. It's normal, just change your performance profile to Power Save.
Hope these will fix!

Thanks for replying buddy.
Yes I have done factory reset,still no luck.Can you guide on how to flash CWM Backup of Yureka?
And what about the reboots? Its annoying during on going calls.
Should I return this device?
N'ayam Amarsh'e said:
Hi Shreesh,
The problems you've mentioned above have solutions, For the battery, It will never charge to 100%, Simple reason for it is overcharge current. To Protect the phone from damage, the phone cuts the supply of current and stops at 99% but it'll be surely fixed in updates...
For random reboots, have you tried Factory resetting your phone? If not then try to or flash CWM Backup of Yureka.
The burning smell, Hmm... That is weird but It happens when some heavy work is processed. It's normal, just change your performance profile to Power Save.
Hope these will fix!
Click to expand...
Click to collapse

Shreesh_the_beginner said:
Hello Yureka Owners,
I got my Yureka from Amazon on 8th March. The below mentioned issues are forcing me to consider returning this device via the amazon return order service.
[*]Burn smell at the headphone jack when using headphones
I have the latest cm11 proximity sensor bug fix update preinstalled in my phone. Please suggest whether to return this device or keep it? Your prompt response will help me in making a fast return decision.
Kind Regards,
Shreesh
Edit: Have charged with the phone switched off,still at 99%
And have done factory reset too.
Click to expand...
Click to collapse
Do not take any chances with the burning smell. return the phone.
schubeir

Change Battery status Style
Shreesh_the_beginner said:
Hello Yureka Owners,
I got my Yureka from Amazon on 8th March. The below mentioned issues are forcing me to consider returning this device via the amazon return order service.
Battery not charging upto 100% even after continous charging for more than 9 hours
Random reboots
Reboots during on going phone calls (specifically when headphones are used for calls/also happened randomly for certain phone calls without headphones)
Burn smell at the headphone jack when using headphones
Device heating up in general
I have the latest cm11 proximity sensor bug fix update preinstalled in my phone. Please suggest whether to return this device or keep it? Your prompt response will help me in making a fast return decision.
Kind Regards,
Shreesh
Edit: Have charged with the phone switched off,still at 99%
And have done factory reset too.
Click to expand...
Click to collapse
I am not sure what is wrong with your Yureka.But mine get charged in 3 hours i.e. 100% and last long till one complete day with heavy usage of Wi-Fi.From 99% to 100% it takes 10-15 mins but it doesnt show 100% in circle. Circle gets blank & on lock screen it shows Charged.So please check one more time as i dont think so it is bug or any problem.

for random reboots do you have changed processor frequency or governors? or maybe custom kernel?

Shreesh_the_beginner said:
Thanks for replying buddy.
Yes I have done factory reset,still no luck.Can you guide on how to flash CWM Backup of Yureka?
And what about the reboots? Its annoying during on going calls.
Should I return this device?
Click to expand...
Click to collapse
Of Course, Just flash CWM, search for Flashing CWM in Yureka and after that download the CWM Backup from the forum development section, there's a thread named System Dump or something , just download the ZIP file given in the link and put it in SD Card,
Go to Settings->Developer Options and set Advanced Reboot Checked Now Hold Power Button-Reboot-Recovery and you'll boot to recovery, Now select Apply update from SD Card and select the ZIP file you downloaded->Yes->(After That's done)Reboot System.
Hope it'll fix...

Return it immediately..
You can't expect much quality from a re-branded Chinese phone, please do not do anything which might make them reject warranty and return it ASAP.

Reboot issue
Shreesh_the_beginner said:
Hello Yureka Owners,
I got my Yureka from Amazon on 8th March. The below mentioned issues are forcing me to consider returning this device via the amazon return order service.
Battery not charging upto 100% even after continous charging for more than 9 hours
Random reboots
Reboots during on going phone calls (specifically when headphones are used for calls/also happened randomly for certain phone calls without headphones)
Burn smell at the headphone jack when using headphones
Device heating up in general
I have the latest cm11 proximity sensor bug fix update preinstalled in my phone. Please suggest whether to return this device or keep it? Your prompt response will help me in making a fast return decision.
Kind Regards,
Shreesh
Edit: Have charged with the phone switched off,still at 99%
And have done factory reset too.
Click to expand...
Click to collapse
Hi Even I am facing issue of reboot during calls or any application running.
I bought this phone this week and started using today only.
I had already updated the OS before start using.
Please advice if this issue can be resolved ?
Or shall I return it?
Thanks
Rajendra .

random reboots
Shreesh_the_beginner said:
Thanks for replying buddy.
Yes I have done factory reset,still no luck.Can you guide on how to flash CWM Backup of Yureka?
And what about the reboots? Its annoying during on going calls.
Should I return this device?
Click to expand...
Click to collapse
Hey Shreesh!!!
i also have same problem, it goes random reboot,
is there any solution ??
please let me know,
otherwise i will return it.?

Hello !!
I returned the phone. I will wait to see whether the cm12 update (that is supposedly releasing on the 26th of this month) resolves the problems or not.
Regards,
Shreesh

mrashidt said:
You can't expect much quality from a re-branded Chinese phone, please do not do anything which might make them reject warranty and return it ASAP.
Click to expand...
Click to collapse
You can't ignore Yureka (The Zeus) for just being a rebranded Chinese Mobile.
MMX is an Indian Company.
To all the Haters->
I AM AN INDIAN AND I'M PROUD OF IT, AND TALKING ABOUT THE CHINESE CRAP!! I DON'T CARE, I D O N ' T C A R E!!!!

Facing problem of proximity sensor
Hieee Yureka Owners
I hav purchased yureka in January and since then, facing problem of blank screen while calling and one side of earpiece is not working.. Besides many calls and emails to customer care, my problem is still unsolved.
Please suggest me the way to get it solved or should I return my cell?
Megha Mehta

N'ayam Amarsh'e said:
You can't ignore Yureka (The Zeus) for just being a rebranded Chinese Mobile.
MMX is an Indian Company.
To all the Haters->
I AM AN INDIAN AND I'M PROUD OF IT, AND TALKING ABOUT THE CHINESE CRAP!! I DON'T CARE, I D O N ' T C A R E!!!!
Click to expand...
Click to collapse
No body said anything about any country, the discussion is about a phone!. This is a tech forum so stop over reacting!

Note 4 freezes and restarts issue! Ultimate thread

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.

leeco pro 3 x727 shuts down after few minutes

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?

can anyone please explain this weird battery behavior?

it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)

SnoopDoge said:
it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)
Click to expand...
Click to collapse
There are several threads about a battery issue like this one in Q&A section https://forum.xda-developers.com/moto-g4-plus/help/sudden-shutdown-t3842810
Maybe you have a similar issue, but not with complete shutdown or random reboot

SnoopDoge said:
it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)
Click to expand...
Click to collapse
Maybe a reset would help or you can try flashing Stock ROM/Custom ROM whatever you are using again.

Heeth21 said:
Maybe a reset would help or you can try flashing Stock ROM/Custom ROM whatever you are using again.
Click to expand...
Click to collapse
i'm not risking a reset or flashing a rom (i'm using stock rom) and have my phone damaged, because yea i've seen people doing that they lose features and issue is not solved

SnoopDoge said:
i'm not risking a reset or flashing a rom (i'm using stock rom) and have my phone damaged, because yea i've seen people doing that they lose features and issue is not solved
Click to expand...
Click to collapse
What features have you seen people losing which have not been solved yet?
A reset can always help to determine whether its a software issue or hardware issue.

Heeth21 said:
What features have you seen people losing which have not been solved yet?
A reset can always help to determine whether its a software issue or hardware issue.
Click to expand...
Click to collapse
well... they lose fingeprint option, they lost IMEI numbers, the phone becomes "uncertified" on play store, not receiving future updates, going to back to a way old security patch (just yesterday i saw someone reset their G5s device and the security patch went back to Nov 2017), and i've seen many people done factory reset to fix battery issues but it's not solved

SnoopDoge said:
well... they lose fingeprint option, they lost IMEI numbers, the phone becomes "uncertified" on play store, not receiving future updates, going to back to a way old security patch (just yesterday i saw someone reset their G5s device and the security patch went back to Nov 2017), and i've seen many people done factory reset to fix battery issues but it's not solved
Click to expand...
Click to collapse
Fingerprint problem is seen after using blankflash (idk about any other fingerprint related issue) and is fixed for most of the users. Blankflash needs to be used after getting device hardbricked i.e while trying downgrading bootloader of Stock ROM and then using OTA.
Downgrade is never ever recommended.
IMEI problem can be fixed for every device (unless they do something stupid like restore some other device's "persist" in their device without a copy of their own "persist" which is unique to every device)
Backing up efs via TWRP (which in turns backs up persist too) is a notice that every dev has given to follow, its just a consequence of not following instructions.
Play Store uncertified is while using Custom ROMs and if its while using Stock ROM (have been for a very few cases) a Stock ROM flash via fastboot resolves it.
I do not know about the last two problems which you mentioned, but Security patch changes by flashing a ROM (Stock or Custom)
People who have done factory reset but it didn't resolve battery problem, well a Stock ROM flash via fastboot can always help and if still the problem continues, then its a most probably a hardware issue.
Thank you for letting me know about these, I didn't knew about security patch change on factory reseting, and also sorry if I sounded rude earlier, it was intended