SOS for ROM no MIUI with programmed start - Xiaomi Mi 5 Questions & Answers

hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?

bettuccio said:
hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?
Click to expand...
Click to collapse
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.

dev>null said:
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.
Click to expand...
Click to collapse
dear friend I have already tried everything, I changed 4 different ROMs Aosp (clean installation) but I understood now that the problem is not the overheating of the processor but it is the touch screen that is blocked. As for the programmed switch-on I discovered that in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds. A great solution for me. I did not understand if it is a bug of Aosp as the phone does not charge the battery if it is on but if it is off or I have to plug in the power cord and then restart then charge. I have a feeling it's time to switch phones. Thanks anyway ; }

All cool !
bettuccio said:
... in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds....
Click to expand...
Click to collapse
which Aosp roms? I'm curious to test

dev>null said:
All cool !
which Aosp roms? I'm curious to test
Click to expand...
Click to collapse
I remember 2 of the latest updates. One is "CrDroid" and the other is "Syberia" the one I have right now.

Related

[Q] Most stable, bug free 4.2.2 rom?

As of right now there are many roms being worked on. I'm currently running AOSPizza which is fast and stable.
My question is, what 4.2.2. rom seems the to the most stable and bug free? (Working data, camera+camcorder, GPS, etc.)
It is very hard to keep track when the roms are constantly being updated.
Thanks in advance!
KayxGee1 said:
As of right now there are many roms being worked on. I'm currently running AOSPizza which is fast and stable.
My question is, what 4.2.2. rom seems the to the most stable and bug free? (Working data, camera+camcorder, GPS, etc.)
It is very hard to keep track when the roms are constantly being updated.
Thanks in advance!
Click to expand...
Click to collapse
They all run differently for different people. Not sure why. Might be Gapps, previous fastbooted stock rom, or *insert reason here*. You just have to try them all and see what you like. PAC, Carbon, and CM10.1 are updated daily, so they can differ from one release to the next....so my best advice is to pick one you like the features of and stay with it, find a stable-for-you version, and try the nightlies with a nandroid on hand if you need it.
I've tried a few, and I am back on stock now. All of the 4.2.2 roms have bugs that I can't live with (battery and bluetooth.)
I have heard there are some worth keeping, but for me it is too much work to keep flashing roms all the time.
adamr240 said:
I've tried a few, and I am back on stock now. All of the 4.2.2 roms have bugs that I can't live with (battery and bluetooth.)
I have heard there are some worth keeping, but for me it is too much work to keep flashing roms all the time.
Click to expand...
Click to collapse
Is there any reason besides bluetooth audio that you choose stock over one of the 4.1 roms?
Eruditass said:
Is there any reason besides bluetooth audio that you choose stock over one of the 4.1 roms?
Click to expand...
Click to collapse
4.2.2 battery life can be bad. I'm down to 79% with minimal use (checked 3 emails) flashed a rom, been off charger for 9 hours now. One of the biggest battery leeches is Maps -- Yesterday it had 779 wakelock interrupts in a 6 hour period -- means it took my phone out of deep sleep for a second over 100 times every hour. Greenify seems to be helping but I need to do more testing with it. Oh, and disabled Greenify for Maps and had 37 wakelock interrupts in 14 minutes....Sometimes I wonder if its not Maps but the Google Now weather panel making Maps do GPS calls for updated location info for weather. My battery wasn't near as bad till I started using the Now widget over cLock weather panel.
Eruditass said:
Is there any reason besides bluetooth audio that you choose stock over one of the 4.1 roms?
Click to expand...
Click to collapse
The pizza rom was great, but didn't allow me to use Google Voice as my voicemail.
The Mexico rom was okay, but it was missing something that i needed.
I quit flashing, it is too much hassle to set up everything.

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

[Q] Incoming call delay after updating to CarbonROM KitKat 4.4

Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
That is happening on every 4.4 I think. It was on CM10.1, CM10.2 too.
Lag on calling screen
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
krazzykuldeep said:
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
Click to expand...
Click to collapse
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Klaas68 said:
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Click to expand...
Click to collapse
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
krazzykuldeep said:
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
Click to expand...
Click to collapse
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Klaas68 said:
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Click to expand...
Click to collapse
I installed the AOSP rom and it seems stable and maybe the call delay issue is better, still have to test it more.
I do however miss some nice functions which were present of the Carbon ROM:
- separate lockscreen background
- disabling the annoying Google Now bar on the homepages
- some fine tuning in icon colors
- kliing an app by long-press the back button
- defining hotkeys e.g. for the camera
and some more..
Is there maybe some package to install to add functions like this to the AOSP ?
Klaas68 said:
...
Click to expand...
Click to collapse
Use Xposed module for all what you need. Gravity Box or others module..
R_a_z_v_a_n said:
Use Xposed module for all what you need. Gravity Box or others module..
Click to expand...
Click to collapse
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Klaas68 said:
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Click to expand...
Click to collapse
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
shut_down said:
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
Click to expand...
Click to collapse
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Klaas68 said:
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Click to expand...
Click to collapse
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
shut_down said:
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
Click to expand...
Click to collapse
OK I did those 3 steps before flashing the new ROM. Sometimes I even had to do it twoce because the ROM did not install and raised a error 7 or so...
I think it was more a problem with the APN configuration and never before needed to do this manually...
Updating from 4.4.2 to 4.4.4
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
harsh3793 said:
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
Click to expand...
Click to collapse
If you dirty flash (just wipe cache/dalvik and install) the new version, you want loose your apps etc.
But I would recommend to do a clean flash (factory reset and format system), but before backup your apps with Titanium. After installing the new version you can restore your apps and data.
But anyway, before wiping/installing anything do a nandroid backup. So if anything went wrong, you can go back in just a minute.
solution ?
Klaas68 said:
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
Has anyone solved this problem ? I have this problem with every rom that i've tried. I'm losing patience with android phone.
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Wysłane z Light-fonika 1-2 ....
...
MikiGry said:
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Click to expand...
Click to collapse
I am stressed when receiving an incoming call and caller don't hear me. I wait from mobile phone calling without problems.
I just wanted to know if there is a ROM without this problem or if anyone have solution.:cyclops:
@ian2189
This is our phones problem. 99% of the users (me too) were expiring this since gingerbread 2.3.6 . So i think there isnt a solution. I now why it is happening but it is unfixnable.
Wysłane z mojego nexusowego tablecika.....
Yeah... I even bought another phone because of this...

Getting a not so random reboots. Any way to track the reason?

I've been using this outstanding phone for more than a year now. It's awesome.
since i have some feature that i would like to keep i am Not using the official miui (neither global, dev or chinese) but trying different roms in the last few weeks(MSM, Epic, Lineage etc..).
I just cant seem to figure out what makes the phone reboot when i'm climbing on my bike(v twin -F800st if it matters at all) and sometimes when charging it. Maybe the heat is the problem( i dont think so as i couldn't see any trouble with it on the last year at all).
Some Roms make me experience this more than others(MSM) and some less(Epic).
Is there any way to log for the reason of the reboots?
Tried a few different Kernels as well but didn't change anything.
Mi Max 2(oxygen), currently on Epic rom, nougat 7.1.1 miui 10.
Any help would be much appreciated.
eeebbr said:
I've been using this outstanding phone for more than a year now. It's awesome.
since i have some feature that i would like to keep i am Not using the official miui (neither global, dev or chinese) but trying different roms in the last few weeks(MSM, Epic, Lineage etc..).
I just cant seem to figure out what makes the phone reboot when i'm climbing on my bike(v twin -F800st if it matters at all) and sometimes when charging it. Maybe the heat is the problem( i dont think so as i couldn't see any trouble with it on the last year at all).
Some Roms make me experience this more than others(MSM) and some less(Epic).
Is there any way to log for the reason of the reboots?
Tried a few different Kernels as well but didn't change anything.
Mi Max 2(oxygen), currently on Epic rom, nougat 7.1.1 miui 10.
Any help would be much appreciated.
Click to expand...
Click to collapse
Sounds daft but when you're mounting your bike are you accidentally pressing the power button too long on the phone, use to happen to me on my car windscreen mount. As for the reboots during charging that is weird
definetly not the situation here.
The fact that this phone screen is rather big and the kavpower(https://www.amazon.com/Kapaver-Xiaomi-Cover-Premium-Rugged/dp/B0747RJ5RL) case shows the part above the vol up button which i can mount the phone pretty easily being far away from the power button...
Also, it doesn't always goes off instantly. sometimes i can ride for 10-15 mins and than a extensive reboot session starts.
As soon as i pull it of the bike, it usually just stops this frenzy.
Thats wh im so eager to find a way to find th reboot reason.
can you attach the logcats?
First assumption here would be the overclocking or under volting .. so stick with a stock kernel or near stock rom / ie miui global or xiaomi.eu or mi-globe.. and see if the reboots disappear .. if it goes away try introducing one thing at a time .. a kernel then a rom and so on

DT2W Not Working Sometimes on Every Rom

Double tap to wake future sometimes not working or i have to tap 6-7 times to phone awake. Its same on all roms. Miui, xiaomi.eu, LOS, PE etc... I think its vendor related thing and maybe because of that stock miui doesnt include this feature?
What do you think and are u have this issue?
This function works just fine on the EU weekly beta and its custom versions by Mi-Globe and ROS Miui
Still same problem. Sometimes it works sometimes i need to tap 4-5 times to wake. I disabled pocket mode but no lock...
arpharazonn said:
Still same problem. Sometimes it works sometimes i need to tap 4-5 times to wake. I disabled pocket mode but no lock...
Click to expand...
Click to collapse
You must have corruption or a hardware issue then, I am currently using the latest Mi-Globe build and definitely do not have issues with Doubletap to Wake. It will not wake on 1 tap, but will definitely wake on 2 taps.
This may sound strange, until you consider that corruptions, encryption/permissions issue are the likely culprits with your issue.
I recently resolved a couple of issues by performing a full wipe, and changing TWRP, to "TWRP-3.3.0-0423-XIAOMI8-EN-wzsx150" its from Xiaomi EU and it does not have the encryption issue that many other versions of custom TWRP have. Perhaps, your issue, is a firmware based permissions issue?
It would only take 5 minutes to test changing over to TWRP-3.3.0-0423-XIAOMI8-EN-wzsx150 and see if that alone brings any improvements.. Flash root again afterwards. If you still have the issue, after trying the TWRP that I suggested, back up your files and do a complete wipe including formatting storage ( Type yes, and reboot to recovery) These types of issues are often permissions based.
If you are using Miui, I have had great success with the Mi-Globe Miui custom rom, it has many additional features, great battery life, and it's very fluid, with zero ads. If you decide to try it, scroll down the page to choose with options you want, or want to omit.
BTW, it sucks that this community isn't very active,with helping people out with their issues. On other popular threads, I would have expected that a lot of other people would have chimed in to report whether or not they have experienced this issue, or how they overcame the issue.
Good Luck

Categories

Resources