Database Develop

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

Freezing all the Time...

I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?

I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/

Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!

deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm

If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.

Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.

jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse

eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse

[Q] Doc's Master ICS V5

I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..

cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
It might have been a bad flash. Try redownloading the rom and flash again. Also, make sure that you do not have too many apps installed. How much free space do you have on system?

The only apps that I had were the ones that came with the ROM itself, didn't download anything before or after flashing it.

may i know does this rom support audience cancelling noise?
thx

I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one

scrypt said:
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
Click to expand...
Click to collapse
ICS ones, but the Dev thread tells that & more.
I don't miss Nandroid when I'm backing up with Super Manager, Super Backup for data, apks, call logs and SMS.

cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
When my screen first appears after a reboot it does that, too, shows half the screen, then the other half, but only for a couple of seconds, I figured it's because it's still reading media, loading widgets, screen, etc. Doesn't last more than 2 seconds, fortunately.

cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
Were you still running the Glitch kernel that installs with the ROM?
It's odd that it went from working to not working. It sounds like something changed something which caused a conflict or corruption... it wouldn't have boot looped otherwise.
If not had any issues like this...

It was a fresh install of the ROM itself, was running for ~ 5 minutes. I didn't install anything via the Market or anything like that....

Un-invert Calendar?
I like Doc's V5 ROM a lot. Best I've used so far. However, I don't care for the inverted apps and am using the "Revert Inverted Apps to Stock" tweak mentioned here. It works just as expected except for the Calendar app - it remains inverted.
Can anyone else confirm so I'll know it's not just me?
Does anyone have a solution?
Thanks!
Bob

Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.

Anyone have vibration issues when receiving texts?

battery life
Battery saving settings - LiveOC 126%, MaxCPU=800*1.26=1008MHz. Nexus KB3 Modem. No deep idle sleep, no screen state settings, no internal voltage settings, ARM voltages are OC/UV. Power saver in ROMSettings enabled.
Boraltis said:
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Click to expand...
Click to collapse

has any one experienced having a feedback loop in either your end or their end when using either the speaker phone or a headset?
Sent from my SGH-I897 using XDA

I am having an issue with the system time. It won't update automatically. Just gets stuck at a particular instance like 3:45 and won't update until I manually change the clock from 24 hours to 12 or vice versa. The happens after long sleep periods like two hours. After this the problem is persistent until I flash a new kernel.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
xThe Enforcer said:
Anyone have vibration issues when receiving texts?
Click to expand...
Click to collapse
Yes I am having this same problem no vibration with texts

no vibration with texts
Yeah. Same here. No separate vibration for SMS. But if you turn "Vibration only" system wide - it works for SMS.
Awkward.
scrypt said:
Yes I am having this same problem no vibration with texts
Click to expand...
Click to collapse

For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration

Well anybody having an issue with time???please read my previous post^^ and tell me if it's sounds familiar , thanks

It happens when you switch a kernel as well? Try switching ROMs and see if it does it then go back to this, I haven't used this ROM since this incident ( OP ), using DK3 atm =p

b-eock said:
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Click to expand...
Click to collapse
I love you.
Sent from my SGH-I897 using xda premium

Invisiblek's 4.4 12-30-13 Nightly Impression

I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night

The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.

Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.

My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.

Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.

Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.

goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.

EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.

Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?

Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.

Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!

sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.

I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4

Phone goes crazy when (I guess) overheated

Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!

flashroyal said:
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
Click to expand...
Click to collapse
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)

Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?

stefan2012 said:
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
Click to expand...
Click to collapse
Logs?

JoinTheRealms said:
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Click to expand...
Click to collapse
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs

flashroyal said:
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
Click to expand...
Click to collapse
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good

JoinTheRealms said:
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
Click to expand...
Click to collapse
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???

flashroyal said:
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
Click to expand...
Click to collapse
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay

JoinTheRealms said:
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
Click to expand...
Click to collapse
I don't know why, but every time I tried to record screen, phone just reboots. I tried with various apps, every time same thing. I cant find built in app in beanstalk 4.4. I'll try stock again but cant before tomorow. Thank you for your time

Use beanstalk with grouper blobs, and press vol up and power simultaneously to record
Sent from my LG-P880 using Tapatalk 4