hi guys recently updated to EUI5.8 14s
was working flawlessly with root and xposed n all gapps loaded up for last few days
just tonight pulled phone out of pocket to find black screen and the led light in BLUE, couldnt turn on screen whatsoever had to hard restart by holding the power button down
luckily i had a backup of EUI5.6 14s in my twrp to revert back to
anyone else had this problem? 5.8 really fixed alot of issues with the max 2 including faster fingerprint n faster overall performance its a shame that this has happened
I blame the exposed framework. I really can not understand all of these Problems you guys come across
use xposed on all my devices from KK to MM with zero problems, only have gravitybox, youtube adaway and keyboard modder modules only
this is not an xposed problem
im thinking its just possible that its because the EUI5.8 was a dev release but very strange problem
I am using Resurrection Remix v5.8 official and I face this Blue LED of death every 2-3 days per week... its really killing me.
Initially when I flashed the ROM everything was fine and from the last three - four months I have been having this issue.
Have been really busy and unable to re-flash and check.
Related
Hello.
Im getting some random crashes, like one per 3 or 4 days. I hace cyanogen mod last stable version.
The cellphone just freeze at any moment doing different things, sometimes ir freeze and automatically reboot, and sometimes i hace to force reboot. Once also screen gets black, but i could see the task bar, and then it automatically reboot.
How could i see a logfile to check whats going on ?
Any idea of what could be crashing my phone?
Thanks
The reason is the kernel. We need ATT or one of the other carriers that are compatible to release either a leak or official JB version and then we will get a lot more stability on our notes. Until then we are going to see some random reboots. I have been on a 10.1 kang since it came out and have not had any random reboots or freezes yet
But im In 10.0 its supoused to be a stable version
The ROM is stable. The KERNEL is not.
Glad I found this thread. Answered alot of questions
I'm not sure if this is normal or not, however I also experienced occasional reboots with some roms but after a week of using the same rom they seem to occur less and less... maybe I'm just being more cautious with the things that caused it in some way but they do seem to subside a little after a few days on a rom... I do dirty flash to newer versions of the same rom sometimes with maybe a crash or two for a day then fine... anyone else experience this?
My situation was similar. First days i have more crashes than now.
Please see the screenshot of the screen flicker.
This problem tho resolved through a reboot but Is it normal behavior or should I be worried and buy some other phone?
I have been using this phone over a year now. These screen flickers come time to time on my device almost once in a month. Is it a known issue with this device?
Any opinions
Zack208 said:
Please see the screenshot of the screen flicker.
This problem tho resolved through a reboot but Is it normal behavior or should I be worried and buy some other phone?
I have been using this phone over a year now. These screen flickers come time to time on my device almost once in a month. Is it a known issue with this device?
Any opinions
Click to expand...
Click to collapse
I would look at these options first
(1) Rom ( Change roms if it happens it with other roms then rom ok)
(2) Kernel (Change kernel if it does it with other kernels then kernel ok)
(3) Battery (Change battery if does it with other battery then that is not the problem)
(4) Hardware ( Service issue return to repair)
I have seen quite a few post's suggesting a new battery could solve it perhaps that is worth a try
It happened for me, but i solved it with reinstalling with stock ND5 rom with full wipe and then installing boeffla 5.3, no issues till then, i am now on latest beta and still no issues.
Hello,
I got XPERIA Mini Pro a couple weeks ago. It was on stock firmware with android 4.0.4. It's warranty ended a long time ago but the phone was still in a very good shape. I really like trying custom ROMs from different developers as I did on my previous XPERIA X10i. So I chose Unofficial CM11 from LegacyXperia with KitKat for start. I unlocked bootloader without any problems. Flashed kernel with flashtool, then flashed ROM with kernel's build-in recovery. It worked fine although sometimes It hung when I wanted to wake my phone and I had to pull battery out. It happend occasionaly and I though I can live with that. But after a couple days proximity sensor as well as front camera gone. I tried whiping cache, factory reset, pulling battery out for about 20 seconds, flashing ROM again, even flashing stock firmware again. Nothing helped. I did research and it appeared that this is common problem with mango after android 4.2. I think. OK, I thought I can live with that. I returned to CM11 but after a while problem with hungs on wake up started to annoy me. I decided to try the highest cyanogenmod for mango on stable stage of development, not nightly like CM11. It was CM9.1. Again, it worked fine and in fact, it was stable. But after a while I noticed that not only front camera and proximity sensor are gone but ALL OF MY SENSORS died. I tried a couple of things like before (whipe, reset, flash etc.). Tried going back on stock. Tried apps from market which test and reset sensors. Every one I tried said my phone does not support sensors. Accelerometer is crucial for me as I use SleepAsDroid app every day. I flashed CRDROID (based on CM11 but much much more stable) which I use till now. Tried doing research on Internet but I found nothing. Tried hitting my phone and dropping It (that helped a lot of people), tried heating battery by overloading processor (that helped a lot of people too). Nothing helped. Tried repleacing files responsible for sensors with the ones from stock firmware. Now test programs show that I have working light sensor but it does not change it's values at all. I accepted the fact that I won't restore my sensors but I must ask:
Is there anything more I can do? Did I missed something?
Is the only way to fix my problem buying a new motherboard? It appears strict hardware problem, right?
Please help, any suggestion will be much appreciated.
Best regards
Hi! I've been reading this forum on and off for few years, but never actually posted. Hope someone here can help me sort out my issue, thanks in advance!
Basically, I've flashed a cm13 via custom recovery on my second phone - Xiaomi Mi4, and I'm having all sorts of issues with it. I bought the phone in China, and for a while
used the stock MIUI interface, but I hated all the bloated apps and weird pop-up advertising, so decided to flash. it was the first time i've attempted it, so it took some
time to figure it out
My two main issues with cm13:
1. It crashes and restarts two/three times daily for me. I mean, I've cleared cache, I basically have no apps on the phone (apart from few messaging apps and facebook).
Is it just because it's an early cm13 build, or it's a nature of custom roms? I'm wondering if switching to a snapshot cm12 build would be better? I don't really care for
android 6 features on this phone that much, I just want a stable experience.
2. The charging became uber slow, painfully so. On MIUI it'd charge to 100% in about 3 hours or so. On cm13 it takes 3-4 hours to get to 30-40%! Never seen anything like
this. Also, if the battery depletes to 0%, the phone wouldn't turn on, even plugged in for charging. It'd turn on after an hour or two into the charging process. Seems weird,
as every other android phone I've owned previously would turn on even with 0% battery if I'm plugged in.
Anyone else experience any of the listed issues? Is it just an early build, or I've done something wrong in the flashing process? I really just want a stable simple os, no advanced
features or whatever, just need it to work
Thanks!
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
mmrx said:
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
Click to expand...
Click to collapse
Thanks for reply! Would you mind telling me which gaps you've used for your build? I remember I had some sort of an issue with few gaps
I tried, I think only the smallest package worked for me. Maybe that's the issue and something in the gaps i've installed freezing/rebooting my os?
Thanks
Hello !
For many issues i left Android 10 , issues like battery drain , camera, proximity sensor issue , network issue, restart issue.
Big question will there be a stable Android 10 ultimately??? ?
If then when?
I have two EU Mi A3 phones on Android 10 (one fully stock, second one rooted). There is no battery drain, no network issue, no random restarts. The latest June update (not available for global yet) fixed also camera and "generic" memory leak issue (or at least it's not that visible anymore). The only remaining issue is that Chrome sometimes freezes during browsing, but that could be due to the app itself.
Long story short, A10 is already as stable as A9 was.
Yes, same here, full stock global unrooted, no big issues.
You can use brave browser, no ads and no freezes
Here the situation is totally different.
I have owned 2 Mi A3 phones.
Both were upgraded to A10 (Evolution X with root). While one was stable, the other suffered from automatic reboots when the screen is locked (usually when I'm asleep) or while unlocking the screen.
Both were originally European versions of the phone, but the custom A10 ROM may have installed a global firmware/vendor.
The stable one I gave to my sister and she's still using and upgrading it without problems.
I kept the unstable one for myself and I've tried to repair or at least find out why it reboots by installing different ROMs (crDroid and Evolution X) and different kernels (Bit and Fenix) but so far I've not been able to solve the issue. I've looked at the logcat and even send the logcat to the developer of some custom ROMs.
I suspect that the reboot happened because of the phone activating itself to look for new messages in the background (while the screen is locked). Maybe the phone was switching between different sleep/active states. The reason I suspect this is because I've seen at least once that the reboot happened around the same time that I see in the logfile of my WiFi access point that this phone is having some internet traffic.
Sadly I don't have the right skills to develop my own custom ROM, but if someone with these skills is reading: If you have time, please make a custom ROM based on A9 with signature spoofing and root. I was still using Kitkat a half year ago, so I'm not in a hurry to use A10 or 11.
Update:
I've just read some one suspect that the reboot is caused by the phone trying to adjust the brightness because he was walking out of a building when the reboot happened... so maybe in my case it was the phone (while the screen is off and locked) is receiving a new message and trying to turn on the screen to show the notification.
Well guys there is new disgusting problem faced by me also by many ..
Screen goes off after call , it doesn't alive untill the other person hangs.
We r here mostly use global version.
Facing many bugs!!
Like restart problem!!
Sensor problem..
Battery not stable..!
MI A3 still they didn't declared STABLE 10.
SO I AM WAITING WITH MY GLOBAL VERSION..
_mysiak_ said:
I have two EU Mi A3 phones on Android 10 (one fully stock, second one rooted). There is no battery drain, no network issue, no random restarts. The latest June update (not available for global yet) fixed also camera and "generic" memory leak issue (or at least it's not that visible anymore). The only remaining issue is that Chrome sometimes freezes during browsing, but that could be due to the app itself.
Long story short, A10 is already as stable as A9 was.
Click to expand...
Click to collapse
Yes EU iz most stable ?but still not stable A10
eric2 said:
Here the situation is totally different.
I have owned 2 Mi A3 phones.
Both were upgraded to A10 (Evolution X with root). While one was stable, the other suffered from automatic reboots when the screen is locked (usually when I'm asleep) or while unlocking the screen.
Both were originally European versions of the phone, but the custom A10 ROM may have installed a global firmware/vendor.
The stable one I gave to my sister and she's still using and upgrading it without problems.
I kept the unstable one for myself and I've tried to repair or at least find out why it reboots by installing different ROMs (crDroid and Evolution X) and different kernels (Bit and Fenix) but so far I've not been able to solve the issue. I've looked at the logcat and even send the logcat to the developer of some custom ROMs.
I suspect that the reboot happened because of the phone activating itself to look for new messages in the background (while the screen is locked). Maybe the phone was switching between different sleep/active states. The reason I suspect this is because I've seen at least once that the reboot happened around the same time that I see in the logfile of my WiFi access point that this phone is having some internet traffic.
Sadly I don't have the right skills to develop my own custom ROM, but if someone with these skills is reading: If you have time, please make a custom ROM based on A9 with signature spoofing and root. I was still using Kitkat a half year ago, so I'm not in a hurry to use A10 or 11.
Update:
I've just read some one suspect that the reboot is caused by the phone trying to adjust the brightness because he was walking out of a building when the reboot happened... so maybe in my case it was the phone (while the screen is off and locked) is receiving a new message and trying to turn on the screen to show the notification.
Click to expand...
Click to collapse
Well thats definitely big concerns.. however.. a10 is just out for this device in may update! So waiting for more fixes !
I think dev. Should concern about the feedbacks and bugs..
Not worth to use like this..
I am not ROM developer i have seen only miui11 Working for a9 but i dont like miui at all..
I dont think anyone will make rom for a9. Coz its very irritating work to rollback !
I only like stock rom!
Am just waiting for PIXEL EXPERIENCE..
The rom u use Evolution X has not good camera. Like stock..
I want 99%✓✓ ok custom like stock..