Related
Randomly the home button and some apps decide to not work or show that its available. I have DRC83 build with the latest cyan ROM. any ideas as to what happened and how to fix it?
Thanks
wipe and relfash
Are you talking about long-pressing the home button? The list that shows there is made up of the six most recently used programs. It constantly changes based on what programs you have run.
I have seen this happen as well, it is not related to the long press but when just trying to go to the home screen nothing happens.
This same issue happened to my G1
I was running stock 1.6 Android on my G1 (Build DMD 64 or something) fairly happily for about a year. I returned my original G1 a year ago on stock 1.6 (different build number that I can't remember) because the speakers were blown, and got this one from T-Mobile as a replacement.
Anyway, after a Market update crashed last month, my Home button and call buttons would not work at all. They would light up, but the system just seemed to ignore them. A reboot to factory default fixed the problem, so it is almost definitely a software issue of some kind.
On the plus side, a reset to factory defaults emboldened me to finally try rooting my phone since I had lost all my custom settings anyway. I've since flashed about 12 different ROMs and plan on trying to build my own custom ROM in the near future. Since you're running Cyanogenmod anyway, you've obviously already rooted, but I just thought I'd offer a sympathetic story with a seemingly happy ending. Good luck.
Within the last couple days I noticed that my power/standby button doesn't always work. From time to time I will try pressing it and I will try holding it, and randomly I will hear the camera shutter sound and it will take a screenshot! Weird... I just flashed SC 2.8 today and the problem was still there. Anybody have this happen/have suggestions on how to fix it?
I know when you take a screen shot with 2.8 you hold the back button and hit the power button.
Just try to flash 2.8 again.
The screen shot thing is part of Android 2.2 I believe, but I've been having the same issue and I'm on stock/deodexed/debloated EB01. I can never tell if I just don't press the button enough or if the button truly isn't working. I agree with k rock though, clear cache, wipe dalvik and try to reflash it.
This is good news....I was looking for the answer to this....I knew it was possible but wasn't sure how to accomplish.
Happens to me too.
i haven't updated to 2.8 yet, but i know making the power button take pics in camera mode was added as a feature in one of the earlier sc versions. i'm on 2.4, and i haven't had any issues with the button not working, though.
i want to disable it ...its annoying...can someone pls tell us how?
xlinth said:
i want to disable it ...its annoying...can someone pls tell us how?
Click to expand...
Click to collapse
It might be possible for you to use root explorer to just kill the app, ScreenCaptureService.apk, I don't think this will break anything else since its just a system app. Worst case you have to reflash 2.8. Maybe just try moving it first so you can put it back if you want.
wideopn11 said:
It might be possible for you to use root explorer to just kill the app, ScreenCaptureService.apk, I don't think this will break anything else since its just a system app. Worst case you have to reflash 2.8. Maybe just try moving it first so you can put it back if you want.
Click to expand...
Click to collapse
I believe this to be true. I read somewhere you could do that but never tried because I imagined somewhere, sometime I'd want to use it. The screen capture has been available since DL30 (you're supposed to hold down the Back button while then pressing power, this always works for me as long as you wait just a bit before pressing power button), but based on what has been posted here and my own experience, it seems to be buggy (i.e., taking screenshots when you don't want it to/have not even pressed the back button - for me, I couldn't get the power button to do anything after having taken a picture accidentally until I tapped the Back button once)
I haven't had the bug since moving to SC2.8 though (a couple days ago, I'd normally get a couple unintended screenshots a day).
Its been my experience that sometimes the soft keys at the bottom of the device have a mind of their own sometimes. On many an occasion my back button specifically will activate two or three times all on its own
Samsung Fascinate
Super Frankenclean 2.8
EB16 Voodoo Kernel
tyler1234567's TransblueHC theme
Sent from XDa App Premium
Yes, this has happened to me. I am guilty of not wiping between SC2.6 and SC2.8, though. There has been just enough goofy behavior that I think I will do a wipe later today and re-Odin the SC2.8 tar file on to my phone.
Sent from my SCH-I500 using XDA App
Question:
What locking feature are you using? pin, pattern, password, glass slide?
Voodoo or non
I have a theory.
I think they got my phone worse, I'm planning on take it back to Samsung but first I want the opinion of you guys since I've learned so much in XDA and they are so much "pros" in here.
I would like to know if there is something I can do? Is there something I should say to them? and mostly ... Should I ask for a full refund for the new $330 main board that DID NOT fixed the problem or they did well?
The beginning :
- I bought a N900W8 in september 2013, since the very beginning it had a multitouch problem, when XY from a finger aligned with the XY from another finger, one of them would disappear, it wasn't such a problem for me since the odds to trigger the bug wasn't that much and I had warranty.
- Kitkat was out and I couldn't help myself and updated it to the mexican leak, since it was "Knox-trigger free" and "downgreadable" I was still planning to take it to warranty if the problem with the touchscreen persists.
- Everything was fine and it didn't had the problem anymore, kitkat was amazing, rooted it, installed X-Note, my phone was great. Months passed, I updated it with the canadian Kitkat NB7 and more months passed.
- So, it's september 2014, I was reading reddit on my phone and it started to lag bad, like unusable bad.
Diagnostic :
- Later I notice it's not lag, it's a delay with the touchscreen. If I used any voice assistant app It would work perfectly but if I touched anything on any spot, it would take like 30 sec to recognize or it would act like I was long pressing it or double tapping, same thing with the pen and the physical buttons (volume, home, power). I spend nearly 20min tapping everywhere on TWRP recovery mode and there was no delay, the physical buttons worked perfectly too. EDIT: every time I installed or re-installed a ROM every tap/physical worked perfectly when selecting (next, next, choose apps, etc). the delays started after booting the OS.
What I did :
- Clean up the phone, check RAM (max was 10% still had 15~45sec delay), Format, Hard Reset, Reinstalled Kernel, Reinstalled ROM, Downgrade ROM, tried another Kernel, another ROM, 3 more ROMs, 2 more Kernels, flashed everything stock, tried stock with custom kernel.. NOTHING. The only thing I couldn't do was to flash Jellybean back because I updated to NB7.
- Took it directly to Samsung (Knox was still 0x0 but there is NO 4.4 update in my country yet so warranty wouldn't cover it) the guy said it was too weird, I took care of my phone so much, he though I bought it 1 week ago not 1 year lol.
What SAMSUNG did :
- After a week they told me it was the main board / motherboard, charged almost $330 for a new one.
- Went to pick it up, the guy turn it on and handle it to me, I even couldn't choose the language because the delay was there. He immediately called someone on the phone, and told me he has to take a video when the problem occurs, but when he inserted the battery back my phone started to work perfectly, almost 45min later was still good so he told me to go back if something happens again. My Scover didn't work, they told me it's "normal" for the Scovers to broke (it did worked before taking it to repair).
- 3 days later I decided to install 4.4 again, but this time I was not going to update it so I could downgrade to 4.3, long story short, I flashed 15 times and downgrade it 16 times because everytime I was on Kitkat the incredibly annoying delay cames back and it fixes when I flash JB back.
New problems :
- The problem persists on kitkat dissapears on jellybean, I haven't tried the updated firmwares, just the leaked mexican one since I needed to downgrade android.
- Scover makes my phone flashes like I'm open it and closing it.
- Every re-boot the half botton of the screen and the volume/home buttons, back and menu, won't work, the power button shows a black screen with the options on the top. I have to pull the battery or shutdown- turn it on in order to solve the problem.
Thank you for reading !
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?
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Side loaded any apps?
I've experienced this issue lately. Yes I am using Nova as my daily driver. I just restarted the phone and issue went away. Hopefully it stays away. If it pops up again I'll report back.
I've had my phone for about a month now. I have had Nova loaded since day one but just recently have experienced the freezing and reboots. It is very random for sure. I may try a run without Nova if it happens much more.
Charkatak said:
Side loaded any apps?
Click to expand...
Click to collapse
Nope, nothing sideloaded...
I am using Pixel 2 launcher for over a month and I like it.
I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s
Still on nought and have noticed bout the past week or so have had 2 freez ups. I'm using nova also. Rooted with magisk and viper and a batt mod.
twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Wow... I've had my Ph1 for over a month, running Nova.(not rooted, don't feel the need to) .. and I've had no issues at all... I'll admit I can recall a few hiccups (nothing major) when I first received it, but after all the updates, mine is running top notch... I understand that this phone had a rough launch... and a butt load of updates... But I honestly can't complain about my experience....
Well I made it almost 8 days this time before it restarted on its own while sitting on my desk. I usually like to reboot my phones every so often but I wanted to see how long it would go this time. DARN lol!!!
qwahchees said:
I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s
Click to expand...
Click to collapse
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.
rootnooby said:
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.
Click to expand...
Click to collapse
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?
rootnooby said:
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?
Click to expand...
Click to collapse
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.
Warlord721 said:
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.
Click to expand...
Click to collapse
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?
Jank4AU said:
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?
Click to expand...
Click to collapse
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.
rootnooby said:
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.
Click to expand...
Click to collapse
But what kind of freezes are you getting? Is it more like brief lag or a complete freeze? If so, what's the duration?
Jank4AU said:
But what kind of freezes are you getting? Is it more like brief lag our a complete freeze? If so, what's the duration?
Click to expand...
Click to collapse
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.
rootnooby said:
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.
Click to expand...
Click to collapse
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.
Jank4AU said:
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.
Click to expand...
Click to collapse
Thanks. Good points. I'll take your advice and clean flash.
The phone is less than 6 months old, getting hard freezes. requires restart by holding power and vol down.
Happens almost everyday while watching youtube and trying to switch to any other application.