• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root MikG 3.1 Hot Reboots - My Problem/Findings - Your Thoughts??

mikem0269 said:
Im 4 days now with out a single problem. If you want i can post up screen shots on my hardware and software if you want to compare. Just ask. But like i said no reboots of any kind on my Evo.
Click to expand...

Interesting...thanks for the updates. As you might have seen from the posts before yours, I/we seemed to have been able to get a log of the problem leading up to the hot reboots.

One question for you...what hardware version do you have?? I have v0002...EVO from launch day, 6/4/10.

Also, if you can do me a favor and try out the scenario(s) in my previous post above:

http://androidforums.com/evo-4g-all...lem-findings-your-thoughts-2.html#post4086451

First..sorry, another question. When was the last time you rebooted your phone FULLY...shutdown and restart?? We've found that a reboot flushes and/or kills whatever process it is causing the hot reboots so that scenario indicates in the link above does NOT produce hot reboots. It is only after MANY hours of uptime without shutting the phone that the reboots occur.

Ok, try this...set your screen timeout for any interval of 30 sec, 1 min, 2 minutes in the Home
 
It's been shut down completely 1 time yesterday and I'm ver #0004.
I see no lag or anything before the screen goes off. When I turn it back on the clock just
Flips to the current time.
 
mikem0269 said:
It's been shut down completely 1 time yesterday and I'm ver #0004.
I see no lag or anything before the screen goes off. When I turn it back on the clock just
Flips to the current time.
Click to expand...

Ok...thanks...that helps. Between the fact that you shut down waaaaay back yesterday which, I ASSume, makes your "uptime" many hours AND the fact that you are v0004 hardware RESULTING in NO hot reboot might be good information. If I had the same history with my phone as you have with a shut down back yesterday, I could pretty much GUAR-AN-TEE a hot reboot...

Thanks again!
 
Updating again....8am EDT here and I swapped out my battery for a fully-charged one. I think I had only two hot reboots during this recent battery and one of them I did ON PURPOSE to see if I could still replicate the issue which I could. Battery lasted a pretty amazing nearly 33 hours under pretty normal use for me.

I think I can confidently make the following statements:


(1) the hot reboots are a real and replicable issue, not so random (for me and, and at least one other person at theMikMik forums) caused by some sort of "fatal exception" as indicated here: Random Hot Reboots - Page 21 ;
(2) I can avoid hot reboots if I set the screen timeout to a longer interval but, regardless what interval is chosen, I must manually turn off the screen before the phone automatically times out the screen;
(3) the hot reboots significantly affect my battery life and, if they are avoided like I have been able to do this past day, my battery life significantly improves and if very good

​
So, there is a way I have found to avoid the hot reboots and, hopefully, it not too much trouble for the ROM dev to fix the issue permanently!!:D
 
scudder said:
Just letting whoever is interested or following this hot reboot issue that a buddy Gamblor01 over at theMikMik forum was able to replicate what I found with my hot reboot issue where it was happening juuuust before the screen would timeout according to the Display settings.

My buddy thinks that he got a log file capture during a hot reboot!! Keeps ME from having to save a log with my port issue :D SOOOOO, he's gonna send over to the dev, aamikam, and we'll see what happens.

I'll keep you all posted...
Click to expand...

Shout out...oh yeah! :)

Mik is looking over my log so we will see if he knows what is going on.

Just FYI my phone is hardware version 3, which is sort of funny. Scudder said his is version 2 and he got it on launch day. I got my EVO on the 4th day it was available and mine is version 3. I seriously doubt that is enough time to even manufacture a new version. I wonder what the difference in hardware version even means...
 
antonio8 said:
hey scudder,

might have something for you.

i switched to express rom and 1 person had a reboot issue and here is the reply of the rom developer.

i included the link (hope i done it correcet and i hope it is allowed to do this).

scroll to response #408 on page 41 and read the next couple.

[ROM] 3.13.12 the Express RC 1.0 Updated!!! Sense 3.0 Fully Working Landscape!!! - Page 41 - xda-developers

i do not know android much so i am going off of his response.
Click to expand...

Thanks for looking out...your link worked fine...just scrolled down to #408 like you mentioned.

I can't say that that issue is ever partially related to what I have been experiencing. I DO NOT PRETEND to know what I'm talking about when I'm about to say what I'm going to say now so ANYONE please confirm or correct me....first, that ROM is different that MikG and don't think it is based upon MikG architecture at all. Secondly, from the title indicating "Sense 3.0 Fully Working" that seems to indicate a FULL SENSE 3.0 ROM with MikG a Sense 2.1 + elements of other stuff ported over...I think...?? So, as such, there might be inherent and totally separate FC and reboot issues with the Sense 3.0 ROM you're referring to.

Lastly, the reboot issues that are explained when "exiting out of certain programs" are NOT AT ALL what I'm experiencing. While the memory issues discussed can cause FCs and reboot issues that does NOT seem to be the concern with the MikG ROM. The hot reboots I have CAN be replicated and ONLY HAPPEN (for me) seconds before my screen timeout setting is about to turn the screen off automatically. If I shut the screen off manually I have NO REBOOTS WHATSOEVER.

Thanks though....appreciated!!:D
 
gamblor01 said:
I finally figured out the exact cause and how to avoid it!!!
If you're curious the link is here:


Random Hot Reboots - Page 25
Click to expand...

Good info. Keep brightness above 5%. I've always kept my brightness around 10-20% so that would explain me never having the issue. I'm on MIUI right now and I don't get reboots if I set it all the way to the min, but that could very well be because of the ROM.
 
Rxpert83 said:
Good info. Keep brightness above 5%. I've always kept my brightness around 10-20% so that would explain me never having the issue. I'm on MIUI right now and I don't get reboots if I set it all the way to the min, but that could very well be because of the ROM.
Click to expand...

It shouldn't be ROM specific because I was looking at the Android source code. I updated my post over at the mikmik forums -- it's actually caused by brightness profiles. The default brightness setting doesn't actually allow you to set a level lower than 8% brightness. Even though it looks like you're setting it to 0%, you're not. But using brightness profiles allows you to set something lower than 8% and then triggers the problem. I'm still not sure why 5, 6, and 7% are safe (they should cause the error as well), but none of these values are even reachable when using the default setting in menu > settings > display > brightness. At least not on MikG (and I suspect not on any other ROM as well).
 
I tried to duplicate this on my phone.

I am running Mikg3.11, anthrax kernel, smurfed out.

I set my screen timeout to 15 seconds and took the brightness off of auto and slid it all the way down to nothing. I don't see it telling me any numeric percentages though.

Well, my phone just turns off. does that old tv set thing, the electron strobe bar.

I went looking for a different way to set my brightness, looking for the numeric percentages spelt out like you guys mentioned, can't find it like that.

Looked under tweaks, under extras there are different animations. I looked at the shutdown animations, there is one that is the light bar and one that is the white htc screen thing. I opted to try htc one, says it is loading files and gets through. was wondering if you have it set to this and it is 'shutting down' when screen times out and you are thinking you are getting phone reboots.

Well, it does exactly zip. doesn't show up with screen time out or with phone shutdown.

Tried turning the crt animations off too and it still doesn't show up.

so, I proved exactly nothing and had a good time doing it. :)
 
Did you read my previous post? It looks like you cannot set anything lower than 8% using menu > settings > display > brightness. In order to see the percentage you have to use an app like brightness profiles.

Could you please download that from the play store and try again? It would be very useful to know if it happens for you as well. Thanks!
 
Rxpert83 said:
I downloaded the app and set it to 0% and cannot duplicate the reboot

Miui.us 2.3.2
Click to expand...

Well thanks for trying. Not sure what else I'm missing...must be something. But Scudder also confirmed that his phone exhibits the same behavior at the 4/5% threshold. So it was definitely the cause of *my* reboots. Weird.
 
gamblor01 said:
Did you read my previous post? It looks like you cannot set anything lower than 8% using menu > settings > display > brightness. In order to see the percentage you have to use an app like brightness profiles.

Could you please download that from the play store and try again? It would be very useful to know if it happens for you as well. Thanks!
Click to expand...

Actually, I didn't till after I had posted mine cause I was writing at same time. :)

I will give it a shot though and see. I'll let you know. I hope you have got it figured out. I thought I was on to something too. :)

edit: Yep, dl'd the app, put at 4%, let it time out, and got a reboot, showing the boot animation . Ok, I don't like that. that app is going in the trash... :)

Did Scudder have that app and have it set that low too?
 
dustwun77 said:
Actually, I didn't till after I had posted mine cause I was writing at same time. :)

I will give it a shot though and see. I'll let you know. I hope you have got it figured out. I thought I was on to something too. :)

edit: Yep, dl'd the app, put at 4%, let it time out, and got a reboot, showing the boot animation . Ok, I don't like that. that app is going in the trash... :)

Did Scudder have that app and have it set that low too?
Click to expand...

gamblor01 said:
Well thanks for trying. Not sure what else I'm missing...must be something. But Scudder also confirmed that his phone exhibits the same behavior at the 4/5% threshold. So it was definitely the cause of *my* reboots. Weird.
Click to expand...

Hi guys....

Read. Tried. Tested. Confirmed for me! Brightness setting at 5% or more, I'm fine; 4% or under, hot reboots.

And, yes I had that app and had it set most of the time at 0%. HOWEVER, I also tested the phone with the app Quick Settings that has a sliding scale for brightness (vs. Brightness Profiles where you can define specific brightness percentages). Sliding the Quick Settings as far down as possible sets the brightness to 3% and, sure enough, reboot...

So it does not seem to be isolated to only Brightness Profiles but perhaps ANY app that lowers the brightness below the 5% minimum "hot reboot threshold."

ALSO, I haven't tested the MikTweaks option to change the Display "autobrightness" settings from "Default" to "Lower" or "Lowest"...
 
dustwun77 said:
Actually, I didn't till after I had posted mine cause I was writing at same time. :)

I will give it a shot though and see. I'll let you know. I hope you have got it figured out. I thought I was on to something too. :)

edit: Yep, dl'd the app, put at 4%, let it time out, and got a reboot, showing the boot animation . Ok, I don't like that. that app is going in the trash... :)

Did Scudder have that app and have it set that low too?
Click to expand...

Awesome thanks for verifying! I figured you might not have seen my post so that's why I asked. I'm not really sure who is at fault here...Google or the app developers. I'm really curious why Android defines 8% (or actually 20 on the scale of 0-255) as the minimum brightness setting. It reminds me of the whole "our amps go to 11" bit in Spinal Tap. If the scale 20-255, why not just make 20 be 0 and 255 be 100? There is a some simple math to convert from the 20-255 scale to be a 100 point scale. I'm wondering if maybe 20-255 stands for something that isn't a linear function? I don't know...there are unfortunately very few comments in the Java code that I was looking at. I have no idea what they were thinking most of the time.
 
So sounds like you figured out the issue.

You guys are tenacious. I would have given up and used a Rom where it didn't happen.

Great work!



Naters
 
Rxpert83 said:
I restored a nandroid of Mikg and installed the app, set it to 0% and indeed had a reboot (with bootani) right before screen was set to go out.

So for MikG=reboot MIUI=no reboot

Great work inspector.
Click to expand...

Thanks...that likely implies that there is a smali change mik made that is causing this. Both Scudder and I have seemed to think that the problem began with version 3.0. Out or curiosity, what version of MikG do you have?
 
You must log in or register to reply here.
Back
Top Bottom