Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
arrrghhh said:
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
Click to expand...
Click to collapse
Thanks arrrghhh, i'll go back to 1276, it seemed to far away in the past compared to 131x or 1320 and my idea was to take latest.
I've never tried older than 1295 as far as i remember. I'll give a try with 1276.
I created a new thread b/c i was not sure it was related to GB and i didn't to mispost in the build topic ... Admin can close or move
diegolvobanania said:
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Click to expand...
Click to collapse
Same issue, it was running great, fast UI, data was fine, I rebooted then the same issues appeared on my next boot>
I just wanted to let it be known, he's not the only one with these issues
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
I decided to go back to FRX06 with stock kernel (1276) and without overclocking because i'd like to use it daily instead of WinMo.
Gingerbread is a bot nicer, ans a couple of extr&a fetures, but is alpha - not stable enough to operate daily.
prexzone said:
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
Click to expand...
Click to collapse
That one's weird - I've had spontaneous autoreboots to WinMo, but I've never had WinMo itself bootloop.
You might have failing hardware?
Sounds like that battery issue people were experiencing.
Remove battery for a few hours put it in and charge it, then turn it on only AFTER charging.
There's a chip in the battery that needs resetting, this should do so.
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
prexzone said:
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
Click to expand...
Click to collapse
Well, hopefully this bug doesn't hit you that often. You can avoid it by shutting down before battery hits 0 (though most of the time battery hitting 0 doesn't trigger this).
You can also avoid this by:
*Getting a second battery. When this bug hits your first battery, just boot Android with the second, and then while plugged in, swap in your first battery. I believe it should start charging normally.
*Getting an external battery charger.
Last time I checked, you could pick up 3 third-party spare batteries with an external charger for like 10 bucks of eBay.
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
prexzone said:
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
Click to expand...
Click to collapse
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
arrrghhh said:
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
Click to expand...
Click to collapse
The only black spot i faced with 1276 is hte screen not lighting up when unlocking the device.
That happened randomly, and of course, this is alayhs when yhou need it the most.
I steped up to wilstilt2's 1300 to get rid of this.
Thanks dvs for your work and support.
It's arela pleasure to use the portage everyday.
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
If you go to ryannathans' "Intro to Android - SD card" sticky, the link to the kernels is up near the top of the first post - along with many other useful links.
prexzone said:
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
Click to expand...
Click to collapse
Here you can find tons of kernels :
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Wilstilt2 ones available from there maybe
http://forum.xda-developers.com/showthread.php?t=885550&highlight=Wistilt
but link in 1st post leads ot v1321.
i don't remeber where i founf v1300... sorry
Related
Turns out this is obviously an issue with my phone, and not the new kernels I have been using. All though it has only happened with Fserve's franco.Kernel.v19.3-gbs.v15 and franco.Kernel |.v19.4| 2.6.32.46. But the problem is the same between both of them, happens less often with v19.4. But rather than bother the kernel developers I will put a general post here. I'm sure that they already have their hands full, and I don't think it's a kernel issue anymore.
The issue:
My lockscreen keeps burning the image into my LCD when I put the screen to sleep. Always is the last image it was at when I shut it off, and it takes around 3-4 hours after flashing a kernel to start with the issue.
It's basically the same type of thing that happens if you leave a computer monitor on at the same screen for day or so, the image stays on the screen for a while because it has burned itself into the monitor.
I cannot take a Logcat as it is disabled in the franco kernel I am currently running. Current specs are in my signature.
Essentially I am trying to track down the cause of this issue, as it seems to happen across different setups, no matter the LCD sleep settings I set, and doesn't go away with lower overclock settings. But when I flash my phone back to OEM specs with KDZ updater it does not produce the problem at all.
It has to be software related because if it was my hardware, It would produce the same result when KDZ updated.
Anyone have this issue at any point? Any suggestions on how to fix it?
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
bigsupersquid said:
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
Click to expand...
Click to collapse
No luck, not supported in this kernel. I return the message
Code:
dmesg > /sdcard/dmesg.txt
klogctl: Function not implemented
Just returns an empty dmesg.txt file.
gahhh, i'm sorry. thought that'd work for sure.
maybe adb bugreport?
FOUND IT!!
Turns out the screen off animation in CM7 was the cause of my issues. For whatever reason, with the screen off animation disabled my screen no longer burns any images into the LCD. I have been burn free for 2 days now.
Weird. Oh well
EDIT: **** me it's back again, what the hell? This is truly a noggin scratcher of a problem here...
I have the bugreport:
Download the bugreport(report.txt)
Compiled through Terminal Emulator v1.0.29 and taken 5 min after screen burn was noticed.
Currently running franco.Kernel v19.3 CFS to see if the problem goes away, as I ran this kernel for a week with absolutely no issues.
Update: Logcat is working on v19.3 CFS version so I was able to take a look at what the phone was doing. Turns out the screen state is set to 0 when I turn it off, and it runs all the screen state off commands properly. But, with logcat not working on v19.4 CFS I am not able to compare notes. Going to look through the bugreports I have and see if there are any differences.
Aha! I have found something that might be of some help. In the battery history section of the bugreport, v19.3 does a Kernel wake_lock when turning the screen on and off, while v19.4 is doing just a wake_lock. They may be versions of the same thing, but maybe the difference in the process is what's causing my problems? I ran v19.3 for around 6 hours today and I had no issues with screen burning.
Well, after 8 hours of 19.3 CFS I still am facing the same screen burning problem. Nothing seems to be making the problem go away. My next step is going to KDZ flash my phone back to stock and run it like that for a day. If the problem persists I am taking it in to be serviced because it is definetly a hardware problem.
Update:
Day One of running stock V10V firmware, and no screen burning occurring at all. Going to keep it running like this for the rest of the week to see if anything will pop up. Maybe CM7 went on a fritz? I dunno, I'm no closer to finding the source, but it's looking like software right now.
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Okay, approximately 4 hours into CM7 with francokernel v19.4 BFS, I am experiencing the same LCD Screen burning issue. Nothing is making it go away in any settings. Going to try void forever and see if anything changes.
Download Bugreport HERE(log1.txt)
Shofire91 said:
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Click to expand...
Click to collapse
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
dancom96 said:
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
Click to expand...
Click to collapse
Not too sure, it's almost like the backlight LED turns off, leaving the lockscreen image there to burn into the LCD. Or maybe just a programming anomoly?
Either way, 2 hours into void forever's rom I am getting the problem once again (argh!!).
It only seems to do this with a custom ROM, the v10v firmware ran without any LCD issues whatsoever. Now why would it do that? I ran V10V rooted and clockworkmod recovery and no LCD issues. Only with a custom ROM.
Download the bugreport here(log2.txt)
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Shofire91 said:
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Click to expand...
Click to collapse
i dont know it it is cm7 6.5.7 issue cuz i never experienced ur problem with this rom or rom based on 6.5.7
I'm working on the assumption that my problem is just an anomoly that I have come across. Searches returned nothing, and I was able to run 6.5.7 without a single issue for weeks, across different kernels. It just came out of nowhere, maybe it will still turn up in 6.6.1, but at this point only time will tell.
This thread is essentially a record of my findings over time to help anyone who has had this issue(there are a few, but not many) figure out where to turn on fixing the problem.
Took a bugreport in 6.6.1 MIUI just for anyone to look through and see if any differences turn up. I have yet to find something that points to the cause.
Download the bugreport(log3.txt)
UPDATE:
3 days in and nothing so far, seems to have been a problem in CM7 6.5.7. Haven't had a single bug since.
Im also experiencing the lcd burn issue on cm7 6.5.7 with goldleaf kernel... doesnt happen on other kernels tho. Ive had this issue before with stock froyo when i got my phone. Since goldenleaf or whatever is based on stock kernel then i think it must be the kernels fault...
Wierd, I had the same trouble as soon as I tried fserve's kernel as well. Mind you it was 19.3 gbs v15 where it all began for me. But yet it went away when I flashed the phone back to stock with KDZ updater, but still came back after reflashing CM7 6.5.7 with franco's 19.4 kernel, and any other kernel after that, even the stock CM7 one. Even any ROM I used that is 6.5.7 based caused the problem to come back. CM7 6.6.1 seems to be the only answer for me at this point. Not sure what is causing the problem but it seems to be based from fserve's modded kernels, but yet it only manifests itself on a few number of devices. Is your O1 a P500 or a P500h?
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
ert69 said:
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Let me know how it turns out.
Shofire91 said:
Let me know how it turns out.
Click to expand...
Click to collapse
Nope. Still can see my lockscreen. I think it might be the roms fault as some have stated before. Plus, that kernel drained my batt like crazy so I went back to goldenleaf.
Sent from my LG-P500 using xda premium
Were you not having the same trouble with goldleaf as well? It has to be the ROM because I am running the setup in my signature since Sunday. No issues at all. Something about 6.5.7 and fserve's kernel don't seem to mix for certain phones. I wonder what the difference is that causes it? I wish I knew more about Unix and Java so I could figure it out. Any developers out there with a little free time?
Sent from my LG-P500h using XDA App
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.
I have searched our Forum for anything on this phone overheating and there is one thread that I came across, but most people did not really have this issue at all. I mean in normal usage doing pretty much nothing my phone holds at 45-50C, given that is with all four cores operating, and if I play a game the cores have reached 70C and up, I am almost certain that is simply too high for this phone to be operating at. Also, even when I use eco mode the phone still idles around 40C and will reach temps as high as 64C. I am just wondering if I am alone or people have actually tested this also and have results similar to mine. I was hoping maybe there might be potential fixes for this or would I need to get a replacement device?
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Pony Express said:
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Click to expand...
Click to collapse
Yeah, I live in Arlington, TX. Yeah, I noticed the self-dim feature, but that happens way too much, and too often, I mean I rarely get to use the phone at 100% brightness and no phone should be like that in my opinion. I am just curious if other people are dealing with similar issues, but I am checking eco mode now and my temps on idle are 36C-38C, its when I actually use my phone as a quad core phone, shocking, that it gets waaay hotter. I mean its hot on the back of the phone when I touch there and when I check the temp with an app. I feel I should be able to use my quad core as a quad core when need be, not have it get so hot its unbearable to hold, plus I don't want to do any damage with it reaching 70C temps.
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
All og's get hot like that when playing games, etc. It is just how it is designed - like it or not / love it or leave it, lol.
I would have preferred they make the phone a little thicker with more heat sink so it could run full speed all the time when needed.
But they didn't. So, oh well. Maybe my next phone will fix that someday.
Jason
Sent from my LG-E970 using Tapatalk 2
Pony Express said:
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
Click to expand...
Click to collapse
Darn, I was hoping for something else, ha. Oh well, guess I will be dealing with that then, meh.. By any chance could you tell me your temps you are getting? So, I know what is normal for the device?
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Pony Express said:
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Click to expand...
Click to collapse
Yes, but this happen on wifi only with data and no sim card installed, I am waiting to get an at&t sim card, lol. Shouldn't have done it online, but it cost 99 cents, instead of $15 bucks in the store.
Good call... hope it helps !!
Pony Express said:
Good call... hope it helps !!
Click to expand...
Click to collapse
Well, the strange thing is that I reverted back to stock everything, no root, or unlocked boot loader, and my overheating issue has been solved.. Weird. I only get around 35C even doing a benchmark with all four cores running at the same time. I think the Base rom and kernels still have some bugs that need to be worked out. I idle at 22C now, woot!
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Pony Express said:
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Click to expand...
Click to collapse
Oh wow, I did not even know that was an issue, ha, well, thanks for the heads up on that and I think I have to send my phone off to LG sadly, according to AT&T, but when I get it back I will be looking into their new base rom, I did skim the thread a little, and I am glad to hear there is no overheating. I am not sure if it was a kernel issue or the base rom itself, which is puzzling.
You may have selected Sk8's kernel during The Base's installation. I can't speak for it myself, but it's different than the stock kernel and may have been causing the problem?
Speculation at best.
No worries, Its what I am doing right now, just speculating, I mean I actually selected both kernels in the base rom, and tested them out. I was trying to figure out what the issue was. I think it might not have left me do a clean install, as I did select Sk8's Kernel first. So, I am thinking that the kernel stuck, even when I did a full wipe, before reinstalling and using the other kernel. I also was getting Kernel crashes, and it kept showing up a kernel crash screen, and asked me to go into download mode to store the dump file on my computer. I am new to android/Linux things, I am far more familiar with Windows based things, but android is the freedom OS of mobile devices. I like the customizations and things you can do with it, lol. Its sweet, and I am learning everyday, so that I can possible become a Dev later on. I have ported some things before and I know other forms of coding, just not the required programming languages for Linux.
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
bleached45 said:
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
Click to expand...
Click to collapse
v1:
- initial release
v2:
- added GPU OC and UV settings
v2.1
- revert GPU settings until i get them more stable
- add voltage control via sysfs (use system tuner to select your custom UV settings)
- fix the black screen issue for alot of users
v2.2
- fast_charge on usb (icon will still show as slow charge but it will actually charge faster)
- cpu tweak to enable use of all freqs in high stress times like games and benchmarks
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Zekk98 said:
v1:
...
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Click to expand...
Click to collapse
Shows what I know, lol.
I was going by what I read for the Base ROM Aroma installer description, maybe the Base is still using an old version, but if you installed it on your own, then you should have been the latest.
Sorry, lol.
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
MaxPresi said:
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
Click to expand...
Click to collapse
Same problem here,
Try wiping dalvik Cache about 10 times ..it worked for me ...
I also had this problem ...but it got solved becaz I had a backup of good runing rom without SOD
Can you turn the phone on if it shuts down or do you have to remove battery? I had the problem only on Neutrino rom, but I didn't do a clean install so I thought it was that
I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix, with some of them the phone not started.
But I do not have this problem with the new kernel (3.1.10) .. or with CM9 nor the CM 10.1 Epinter. The problem with this kernel is when it heats up very much, the screen tearing.
And no, I do not need to remove the battery ... if I hit once as if I turn on the screen, he turn on himself.
I've tried to save the logcat with the application Catlog and put him to save every 1 line, but not the right ... he save the log a few minutes before turning off.
As the 3.1.10 kernel works, I believe that is not a hardware defect.
My memory is: 0x00EF (0xBEEF)
TegraTevision: A03 prime
Tegraparts: mbr: 1100:100:800
thanks ...
Hi may I ask if you resolved this problem as I have it to. Thanks
lisaamybeth said:
Hi may I ask if you resolved this problem as I have it to. Thanks
Click to expand...
Click to collapse
The post just above yours has a solution... read it.
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
lisaamybeth said:
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
Click to expand...
Click to collapse
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
lisaamybeth said:
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
Click to expand...
Click to collapse
In the post that I replied to, you only stated that you had issues with CM10.1/3.1.10 kernel, which is why my post was worded the way it was. you didn't specify that it was also with GB based ROMs as well. The only thing that makes sense at this point is a board/hardware related issue. As I briefly said in my last post, we all have different board revisions. We all won't see the same results. Thats why you see people talking about having screen tearing issues when others have no issue. I suspect its the same in regards to this issue.
Hello everybody,
about two months ago, I had an issue with my installed ROM on my Redmi Note 2 Prime (I think it was this one: http://forum.xda-developers.com/redmi-note-2/orig-development/rom-cyanogenmod-12-1-t3288916 ). I decided to try out another ROM so I installled Bule's Mokee ROM ( http://forum.xda-developers.com/red...nt/rom-cm-12-1-mokee-bule-mokee-blue-t3328382 ). After a few days with this ROM I recognized a big battery drain while screen off so I installed BetterBatteryStats to get some more informations. It told me that about 50-75% of the time my CPU was running at 800mhz instead of deepsleep (at a normal day with about 1-2h of Screen-On-Time). It didn't look to me like something is creating a wakelock though (but maybe I am just unable to see this). I tried the next ROM: Daniel Pinto's CM12.1 (http://forum.xda-developers.com/redmi-note-2/development/rom-unofficial-t3310551) and again the same issue! I tried a full wipe of my internal storage, did not install xposed and did not install any titanium backup. The battery drain didn't go away. So i flashed another ROM: SlimMIUI V7.1.3.0 ( http://forum.xda-developers.com/redmi-note-2/development/rom-slimmiui-dev-stable-t3296594 ) and suddenly there was no more screen off battery drain! This went well for about three weeks and now I am facing the old problem again! Please tell me what I am doing wrong since I don't believe it's a ROM-related issue.
I installed these apps (according to MIUI):
9gag
AdAway
Android System WebView
Antutu 3DBench
Antutu Benchmark
AquaMail
BetterBatteryStats
BikeComputer
Burning Series
Chrome
DB Navigator
Dropbox
ES Datei Explorer
Google Play Store
Google Play-Dienste
Google-Tastatur
Greenify (wasn't installed before SlimMIUI)
GuitarTuna
Hacker's Keyboard
Hearthstone
irplus
Maps
Messenger
MX Player
mydealz
No-Frills CPU Control
Nova Launcher
Open Camera
PaderSprinter
QuickPic
scondoo
SleepTimer
Spotify
SuperSU
Telegram
TeslaUnread
Titanium Backup
Twitch
Unified Remote Control
Wakelock Detector Free
WhatsApp
Youtube
What I have tried so far:
- changing ROM (clean flash)
- not installing xposed
- not using old backups
- changing the battery
- using airplane mode
Also, I wonder why there are these gaps in the battery history since I didn't reboot yesterday...but these gaps don't appear every day.
Please help me to fix this really annoying problem and make my RN2 great again!
Thanks,
Kooneybert
The biggest drain comes from all the Xiaomi bloat. Read this thread for details on how to reduce the bloat. In my experience, the second main culprit is WhatsApp. I've had to stop it from giving sound notifications (or even vibrating) when messages come in. Now, I have between 90%-95% deep sleep on idle. Basically, anything that turns on audio could be a problem, because sometimes audio doesn't go off afterwards.
You might want to try GSAM Battery Monitor for more information about what is eating up your battery.
DarthJabba9 said:
The biggest drain comes from all the Xiaomi bloat. Read this thread for details on how to reduce the bloat. In my experience, the second main culprit is WhatsApp. I've had to stop it from giving sound notifications (or even vibrating) when messages come in. Now, I have between 90%-95% deep sleep on idle. Basically, anything that turns on audio could be a problem, because sometimes audio doesn't go off afterwards.
You might want to try GSAM Battery Monitor for more information about what is eating up your battery.
Click to expand...
Click to collapse
Thx for your reply! The problem is not MIUI-exclusive. CM 12.1 from Daniel Pinto is pretty slim but gave the same result (from the first day on).
Whatsapp can't be the only problem since all my friends use it and nobody have this problem (some of them also even have a RN2). Also, my phone is in silent mode almost all the time so no app is allowed to make noise or vibrate.
I just installed GSAM Battery Monitor but I don't know how to use the app/read the provided data. I could use some help there, too.
Kooneybert said:
Thx for your reply! The problem is not MIUI-exclusive. CM 12.1 from Daniel Pinto is pretty slim but gave the same result (from the first day on).
Whatsapp can't be the only problem since all my friends use it and nobody have this problem (some of them also even have a RN2). Also, my phone is in silent mode almost all the time so no app is allowed to make noise or vibrate.
I just installed GSAM Battery Monitor but I don't know how to use the app/read the provided data. I could use some help there, too.
Click to expand...
Click to collapse
You can only be sure if you have a really skinny ROM whereby all the unnecessary Xiaomi stuff has been removed. There are all sorts of things going on in the background - including things embedded in the boot image.
There are also possibly optimisation issues with the kernel. All the ROMs seem to depend on the same binary kernels, since there is no GPL release of the kernel source code. You might want to try one of the skinny boot images by @jajk
As for GSAM, the best to learn is by trial and error (tip: tap on everything visible to see where it leads to, and what information it gives you).
DarthJabba9 said:
You can only be sure if you have a really skinny ROM whereby all the unnecessary Xiaomi stuff has been removed. There are all sorts of things going on in the background - including things embedded in the boot image.
Click to expand...
Click to collapse
...on all three ROMs? Only for me? With this effect? On some days, it reduces my battery by 50-80%! Hard to believe it is not a bug. Also, SlimMIUI has reduced Xiaomi-Stuff, Daniel Pinto's CM 12.1 looked even more clean to me.
DarthJabba9 said:
There are also possibly optimisation issues with the kernel. All the ROMs seem to depend on the same binary kernels, since there is no GPL release of the kernel source code. You might want to try one of the skinny boot images by @jajk
Click to expand...
Click to collapse
Aren't there different kernels out there for the RN2? Bule's Mokee-ROM uses a modified kernel e.g. Does every ROM come with a certain kernel or may it be applied from the ROM before? So maybe I am still using the kernel from Bule's Rom with my MIUI?
DarthJabba9 said:
As for GSAM, the best to learn is by trial and error (tip: tap on everything visible to see where it leads to, and what information it gives you).
Click to expand...
Click to collapse
This will help me to read the information but it won't help to understand them, too. What do you think about this:
Kernels: You can't compile a custom kernel without the Xiaomi kernel source code. All you are left with is tinkering with ramdisk in the boot image
Screenshots: the one on the right shows what is sucking your battery; the biggest culprits are the Xiaomi kernel and Google ...
DarthJabba9 said:
Screenshots: the one on the right shows what is sucking your battery; the biggest culprits are the Xiaomi kernel and Google ...
Click to expand...
Click to collapse
...is this normal? The Kernel is the biggest battery sucker on my tablet aswell (which still has great battery). What do you think about the 8,5h of wakelock time produced by the kernel? If this is the problem, what can I do to solve it?
Kooneybert said:
...is this normal? The Kernel is the biggest battery sucker on my tablet aswell (which still has great battery). What do you think about the 8,5h of wakelock time produced by the kernel? If this is the problem, what can I do to solve it?
Click to expand...
Click to collapse
A "screen awake" of approximately 50% seems to me to be highly excessive (at least, if the phone was mostly idle). In nearly 12 hours, I have a screen awake of 55 minutes - so 8 hours in 15 hours seems strange. How exactly were you using your phone during this 15 hour period?
Perhaps the custom boot images by @jajk might help (see the first link in http://forum.xda-developers.com/redmi-note-2/general/roll-skinny-miui-t3309873). I am currently on v714-15 of the custom boot image.
Sounds like you may be having issues similar to what I was dealing with not too long ago, but my 'solution' was to install Bule's Mokee (still don't know why this ROM worked where so many others failed). Daniel's CM 12.1 and Xiaomi.eu were both giving me significant drain with and without the screen on to the point where I was sometimes finishing the day with an hour and a half of screen on time and ~20% battery. Now I'm getting up to double that.
One thing I can recommend is using MiFlash/Fastboot to do a total reset from scratch. Didn't really work for me, but you may be different.
Other than that, although it's tedious, you may have to install 1-3 apps per day after a fresh install to see if your battery holds at first and then dies sometime after installing certain culprits. It takes forever, but at least this helped me when I moved to Mokee to make sure that it wasn't any of my 'vital' apps that were causing me issues.
Best of luck!
Funny thing that the Mokee-Rom did SOLVE your problem. In my eyes this Rom was the beginning of my problems.
beokabatukaba said:
One thing I can recommend is using MiFlash/Fastboot to do a total reset from scratch. Didn't really work for me, but you may be different.
Click to expand...
Click to collapse
What is the difference to using TWRP?
I will try the Mokee-Rom tomorrow. Since I never used MiFlash/Fastboot before I won't use it until you tell me that there is a difference compared to doing a full wipe with TWRP.
I tried flashing the Mokee-Rom again but the problems go on. I installed very few apps and the battery is still very bad. Today I had 18 minutes of SOT and though I lost 14% in a few hours. This time it was caused by Whatsapp:
It always seems that some apps just don't like to stop doing something but it's random which app is the problem.
I am totally running out of ideas so please help me guys!
I'm on Mokee and satisfied with battery, this rom have less problems than other (for me). First of all i have installed MobileRadioActiveFix with xposed, then SmartNetwork to turn off wifi while my screen is off. I've got few other things but right now i've got over 4h SOT so it is not bad score.
i have the same problem! it happens with flashing severals ROMs (mokee by bule?) and starts battery drain with all ROM, it never goes... is not the battery, the cable or the rom..... i dont know im disperate... the sot changed from 4-4.5 h to 2-2.5 h... with all ROM, please help us and sorry for my bad english
Well i had situation that my SOT suddenly got down but i was still on march rom. After update to latest version without wipe it is ok right now.
Have you tried with wiping all with internal memory? Maybe something is there still and that is making a problem.
Another thing that came to my mind: have you changed build.prop and have copy of it? If so, delete it. I had some problems becuase of that.
Mauelith said:
Well i had situation that my SOT suddenly got down but i was still on march rom. After update to latest version without wipe it is ok right now.
Have you tried with wiping all with internal memory? Maybe something is there still and that is making a problem.
Another thing that came to my mind: have you changed build.prop and have copy of it? If so, delete it. I had some problems becuase of that.
Click to expand...
Click to collapse
every rom i have flashed was a clean install (full wipe of internal) after latest miui update, when the phone shut down at 0%, i put off the battery for 10 min, after i put back and the phone was at 19%!! now is on charge... maybe the problem is solved.. i will post if it is solved (sorry for my bad english)
I had that problem with earlier phone and it drived me crazy. I was not able to find what was the cause unfortunatelly. Phone was given to service point to install branded rom (it was not available for public). Right now i do not have problems like that, if i have some i'm able to find solution somehow. Although what i wrote helped me when i saw SOT problem.
problem persists... is there a method/app to calibrate battery that works?
AngelHxH said:
problem persists... is there a method/app to calibrate battery that works?
Click to expand...
Click to collapse
Not that I know of. I`m facing the same issues like you here.
You can try:
-discharging until the phone shuts off
-charge it in OFF mode until its full
-disconnect charger, put battery out and in again
-connect charger, charge it to 100% again...
repeat until it shows 100% when connecting the charger.
For some ppl this seems to work.
Please let me know if you find out something!
There are lots of ppl out there with exact the same issue!
BR
EDIT: Installed PSYROM V3 for testing purpose right now. Lets see how it does with skynet and a freshly calibrated Battery with the internal calibration tool of the rom. I`ll give feedback on monday.
Update to my issue:
-I did a full wipe (including internal memory)
-Installed PSY ROM V3.0 and Skynet
-Wiped cache/dalvic
-Startet the phone, installed my apps etc
-Charged it to 100%, waited 20 more minutes
-Did the Battery calibration with the internal calibration tool (everything is described in psy mans thread)
-Did a reboot
So far there is no Battery Drain, after the (long) reboot, wich took around 5-10min because miui is optimizing apps etc the phone came up with 97% and stayed there for almost an hour now.
I´ll give you guys feedback next week. Hopefully we get this sorted out.
You can try Angels & demons ROM v8.0 it is providing me with great battery life, so much better than stock or stable version of MIUI. I use Gsam battery monitor, and I have not faced that issue so far.