Yotaphone 2 warm/heat ??? - YotaPhone

Hello!
I've jut got my yotaphone YD206 with CN rom, i flashed to EU rom. I love this phone.
My problem is the top half of the phone is really warm/hot. Is it normal ? I though its the CPU or the WIFI.
Any opinion ?
Thanks (Sorry my english)

Lollipop is buggy, that does not help...
zolee166 said:
Hello!
I've jut got my yotaphone YD206 with CN rom, i flashed to EU rom. I love this phone.
My problem is the top half of the phone is really warm/hot. Is it normal ? I though its the CPU or the WIFI.
Any opinion ?
Thanks (Sorry my english)
Click to expand...
Click to collapse
Lollipop is indeed buggy, and one of the most serious bugs is that the radios is allways ON even if the WiFi is set to be disabled when screen off, that makes the Lollipop battery suck. Actually there's lots of bugs in Lollipop and that's to blame Google, lately has been really lame, since KitKat at least. KitKat is way superior but unfortunately the EPD implementation on KitKat is subpar. Yota as it seems has the intention of releasing the Marshmallow version, and it's now on Beta, so let's finger cross and wait for the best.
People here over XDA forums also come to check informations so they can install the latest Firmwares, and sometimes they don't know there's several models of YotaPhone 2 basically distinction being the radio frequencies they can work, so it's important that you use your device correct radio when using other firmwares, for example my Phone is from HongKong and I use the /radio files from the latest HongKong firmware, no matter if I am installing a Russian or European firmware. The wrong radio makes your phone use more battery and lost connection.

zolee166 said:
Hello!
I've jut got my yotaphone YD206 with CN rom, i flashed to EU rom. I love this phone.
My problem is the top half of the phone is really warm/hot. Is it normal ? I though its the CPU or the WIFI.
Any opinion ?
Thanks (Sorry my english)
Click to expand...
Click to collapse
Root and install No-frills CPU Control is your solution :good: More details here : https://youtu.be/vOiAMsxq578

I have had same problem with the phone heating up badly last weeks time, this is the Yotaphone 2 206 model kitkat 4.4.4 , not rooted or anything, just as out of the box, it would randomly heat up so bad that it would switch itself off and not turn on again until cooled down, it seemed to get better after turning off location service but that could be coincidene

Marshmallow ROM overall is working well, I advice anyone that is not happy with KitKat to run Marshmallow, Lollipop is a disaster. Just remember that if you have a YD206 you should use the China radio or a little better the Hybrid Baseband created by some users. About the battery time, KitKkat and Marshmallow are the best ones, Just keep in mind that location services and Wifi always scanning uses too much battery. If you know how to use Tasker, you can program it to use data services only each 20 minutes or so when screen is off, making it idle for each 20 minutes with no data connection will make you battery really last longer, then make a rule to auto turn data on when screen on, make a tasker to get wifi on when you are at home and to disable wifi when you are out, with tasker or similar app you can make pretty much everything possible!

I use this to stop wifi out of home.
Easy to use and no root required.

Related

Polish Rom has killed my phone !!!! :(

Hello guys, a long time ago now before the official 4.4.2 KK was available for my SM-N9005 I flashed a leaked Polish one. Before the flash my phone was working perfectly, no problems at all. After flashing the firmware I noticed my battery was draining at more than 1 percent a minute and it was pretty unhelpful to say the least, after looking at my battery info in settings says that NFC was using 63% of my battery !!! Now we all know this cannot be right ?! So I tried to disable it but couldn't as it was greyed out. It was stuck on and did not work at all. I waited quite a while and when the official KK firmware was released i flashed it but still no NFC. Now I have updated my phone to Lollipop and my NFC still does not work. Have you guys got any suggestions on how to get this working again ? It's definitely not a hardware fault as it has happened to my note and one of my family members notes after installing this firmware.
Many thanks
I have attached a screenshot that quite clearly says NFC is off although it is actually 'on' and not working. It is greyed out and cannot move it
Maybe something wrong with the nfc chip in your battery? Buy new battery (ebay) and see if that helps?
Sendt fra min SM-N915FY
Already thought of that, thanks anyway though
I've seen this happen on the S5, too. Very annoying problem, nobody seems to know if it's a software or hardware problem.
Have you tried doing a 30 seconds battery pull, and then wiping the cache in recovery? (Dalvik too, if you can.) Also clear out the cache under Settings > Storage. Let it sit for a while and see if it's off. If not, try another battery pull and see if it's off when you turn it back on. That process worked for my S5. (Which has never had any other firmware than PHN.)

Samsung Galaxy A3 (300FU) Battery Stats Problem Bluetooth

Hey guys
recently i bought a Bluetooth speaker and connected it to my A3 (300FU), but now when i check the battery stats to see what is eating my battery it only shows Bluetooth (not even screen, wifi etc) [ see screenshots]
i deleted dumpstat/logcat and also wiped cache partition but it didn't help.... is there an obvious solution or am i missing something here?
*running stock Marshmellow ROM
Any help would be appreciated
i think a few users have it confirmed, Bluetooth seems to be a major drain in MM for A3FU.
i can only advise to update to a newer build. what build are you btw? do a screenshot of About in Settings
i didn't have a problem until recently, when i paired my device with the bluetooth speaker.
should i reset network settings?
I've attached the screenshot.
all users who reported BT issues came from first BT pairing, just like you. and they were all on PH3.
It's a rom bug that you can only hope they notice and fix, and then it's up to you to try the new builds and see if there is any change.
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
Quite sure bluetooth is being the idiot here.
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
conanDO98 said:
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
Click to expand...
Click to collapse
Nearby device scanning is turned to off, should i reset network settings? maybe that way it will correct the readings
For the Battery stats --> Settings -->at the System section search for Battery--> Battery usage, or maybe just use S finder
I've got the same issue. Untill I switch Bluetooth on, normal battery stats, as soon as I do, everything is reported as Bluetooth - no screen use, now Android System use. "Nearby Device scanning " option seems to have no effect.
I also had this issue when I upgraded to MM (build CPI1)... even tried factory reset, but problem persisted.
I think it's a bug in the Samsung ROM, no way to get rid of it without a software upgrade.
Same "bug" with my A300FU.
Tried everything...
Installed earlier firmware (rom) with odin (in which I did not have the exaggerated Bluetooth usage)
Installed latest firmware again
Full wipe
Install latest firmware
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
According to the battery gauge Bluetooth is using approx 4mAh PER SECOND
Also explored the option to modify the power profile.xml in the framework-res.apk but to no avail (keep getting bootloop)
*frustrated*
Anyone an idea?
Flashing cm12 or cm13 and then reverting to stock 6.0.1 is also not a solution to this issue......
My Wife's Galaxy A5 (2015) also has this bug. All 6.0 firmwares - even latest from January. So stupid - I can't belive that they can't see this bug. There is no battery drain - only bad statistics. But its very anoying because You cant check how long screen was used etc. Scaning of near devices is disabled too - didnt help. Dammed.
Have You find any solution?
I never looked at that screen before, but I recently noticed this too and it freaked me out at first. After testing it tho, I was gonna post and ask other peoples' experience, but then I found this thread.
What I get is that initially my batterystats are recorded normally, but then when i turn on bluetooth, even if it's for 1 second, all stats disappear and bluetooth appears in that list with what appears to be a huge (and impossible) drain.
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
PlutoDelic said:
Quite sure bluetooth is being the idiot here.
Click to expand...
Click to collapse
I normally have bluetooth on, and I don't actually notice my battery draining any faster than when it's off. Also, if the computed battery usage on this was accurate on my phone, I would run out of power in a matter of seconds. So it's definately a bug in the battery stats.
aerogenes said:
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
Click to expand...
Click to collapse
I beg to differ! I flashed lollypop and the problem disappears then, but it's there on both marshmallow builds for our country, even when starting fresh after a data wipe.
Which roms have you tried? And what rom is your colleague on after the OTA that fixed it? Buildnumbers would really help
For me: U1CPH3 and S1CPL1 both have this issue
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Bffn45 said:
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Click to expand...
Click to collapse
Al right, thanks! Latest rom/update for my country is from december too, but i still have it.
So i'll try downloading a jan 2017 rom for a different country and see what happens
Update:
Installed the S1CQA2 firmware, which should be the latest, and the bug is still there. Just with less unbelievable numbers and it takes a little while longer for it to make all other stats disappear.
Update2:
Looked into the powerprofiles.xml too, but the marshmallow one (which has this issue) is identical to the lollipop one (that doesn't have this issue). Also all there is to edit in there is the amperage usage for actual A2DP, but according to this https://source.android.com/devices/tech/power/values.html a lot of battery usage is just pushed to the batterystats service by the controller.
Now wondering what files are associated to the bluetooth controller. Simply replacing the bluetooth.apk from a different rom where this is working does not solve it either.
After some more digging, and succesfully porting the S5 bluetooth files to my phone, i found out that the samsung S5 suffers from this issue as well andthus the issue was still not fixed
Also, judging from other posts in other forums it appears the Note 4 has it too.
Therefore I think it is a touchwiz bug, and I am clueless on what to try anymore.
This is my third post in this thread in a row but editing my previous posts here might make the new info go unnoticed...
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
great effort mate, really love it when people monitor the release stream .
Carpe-Dimi said:
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
Click to expand...
Click to collapse
Thanks for the heads up... I've just flashed the update, and I can confirm that also for me this new firmware solves the BT issue. :good:

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?

Random shutdowns with every rom

Hi all,
I have an N910G in Australia. I have tried many different roms and different OS versions but always have the same problem of random shutdowns on low cell signal.
I'm currently running the Andycar rom because it's just a customised stock MM room and even uses the original CSC.
My phone has never been better but the random shutdowns are happening even on this room.
It can't be an EMMC issue because the phone is perfectly reliable on a stock factory rom.
My wife also has an N910G. I have the exact same issue on both device.
I just installed wakelock to see if it helps but it's too soon to know yet.
What am i missing?
Thanks in advance for any comments
Battery. There is a topic about it out there somewhere.
Only with non standard roms? Multiple phones and batteries, all working properly with stock roms, all will work for days with a reliable cell signal. All will reboot or turn off with a low or changing cell signal.
I'm not ruling battery out but it doesn't sound right to me.
My gut feeling is that it's CSC or BL related but I've tried original stock versions with the custom ROMs - same problems.
The last rom I tried was a customised debloated stock rom - same problem.
I'm lost ...
Rabbit308 said:
Hi all,
I have an N910G in Australia. I have tried many different roms and different OS versions but always have the same problem of random shutdowns on low cell signal.
I'm currently running the Andycar rom because it's just a customised stock MM room and even uses the original CSC.
My phone has never been better but the random shutdowns are happening even on this room.
It can't be an EMMC issue because the phone is perfectly reliable on a stock factory rom.
My wife also has an N910G. I have the exact same issue on both device.
I just installed wakelock to see if it helps but it's too soon to know yet.
What am i missing?
Thanks in advance for any comments
Click to expand...
Click to collapse
Hi all,
I have stared from scratch with another fresh install of Andycar customised stock MM 6.0.1 rom. I can use it around the house perfectly for days on end. Battery life and performance is awesome but when I go to work the phone will randomly shutdown every 10 minutes or so.
It's definitely not battery.
It's not EMC.
It's not the sim.
I've flashed modem.bin and NON-HLOS.bin from the stock rom (that works 100% reliably) but still I have the same problem that I've had with every single rom I've ever run apart from the stock Samsung rom.
Any time I go somewhere where signal is low the phone will soon shutdown instantly.
Is there anyone else in Australia running an SM-N910G on Telstra with a non standard rom?
Hi, I am not in australia, but can say this.... for what its worth, I have an n910v galaxy note 4 on a custom rom myself. I have set up 3 others exactly like mine. I have not used the rom you mentioned but am using the modestrom instead. none of the phones I set up have ever had random shutdowns. It may be a random problem with the rom itself. I know it isn't really helpful, but wanted to state it anyway.
tattmann said:
Hi, I am not in australia, but can say this.... for what its worth, I have an n910v galaxy note 4 on a custom rom myself. I have set up 3 others exactly like mine. I have not used the rom you mentioned but am using the modestrom instead. none of the phones I set up have ever had random shutdowns. It may be a random problem with the rom itself. I know it isn't really helpful, but wanted to state it anyway.
Click to expand...
Click to collapse
Hey tattmann,
It doesn't specifically help me but I do appreciate the reply :good:
It's strange that i can produce the same problem on multiple (3) devices with so many different roms. I can't believe that no one else has had the same problems.
In every case I can restore a stock rom and the device will perform reliably - despite having horrible battery life, masses of bloatware and crappy performance...
Thanks again for the reply
With custom roms my phone is shutting down completely when i either open gallery or do two or multiple things at once. Weird thing is once its shut down i cant power it on immediately. I have to connect to charger or remove battery. Then its turning on when i press the button. Sometimes it happens irritatingly fast.

With every ROM i try i have the same issue: Bluetooth makes wifi to go soooo slow, any help ?

Hello guys, i'm getting crazy about this because, after trying a lot of custom and some official roms i keep having this problem: when bluetooth is active wifi is slow and become useless many times, not every times tho, which makes me even more confused but i'm pretty sure i've made a right diagnose of the problem and it's BT and Wifi interfering...
It's logical to think this must be a hardware issue, specially if you havent experienced it, and i might even try it in another p8 i have (i havent tried yet because it needs a new screen)
As a user i just can't live without bluetooth, maybe some of you didnt noticed it but you also have this issue... i'm just almost all day using bluetooth audio.
In case you experienced this problem, can you suggest any solution ? i'm sure this has to be a repeated problem in many devices due to the similar frequency range BT and Wifi operates (congratulations to the ones who decided to make this standards this way)
In the moment i think every custom rom i tried had some little imperfection or issue and, right now my choice is EMUi 4.1, for me the most valuable thing is the feeling of the OS, the stability, fluidity, consistence, elegance of the interface, and i can have all that with this firmware despite this f***** problem which is a total red line for me. Of course i'd root and customize EMUI a little bit...
BTW... i seem to worried for a 7 years old phone that i just love to have in my hand but its supposed to be just a spare phone while my main one waits for a fix... well yes, i got excited, and frustrated, and excited again... but i guess i will have to accept this dramatic situation and fix my new phone asap.
Suggestion of any custom rom or general solution for this ? thank you guys

Categories

Resources