yashsingh1/xdaforums huggingface dataset:
[LG Nitro HD] tdm:
Right... vendor/ota roms come with baseband firmware. Forgot about that, I've only ever installed one vendor rom.
[LG Nitro HD] notzippy:
Just had a partial crash, screen froze while I was playing a game "Dragon Egg". I plugged it into the pc and as soon as I did that the screen turned off (maybe BSOD ?), but adb was working so I saved a bit of the logcat as it was going on (doa_logcat.log) I also copied off the last_kmsg.0 (it is in the zip as last_kmsg.1). I then did an adb reboot and copied off all the files listed above. After reboot phone is running fine.

Hope this helps...

Nz
[LG Nitro HD] notzippy:
Forgot to add this file

I/Process ( 550): Sending signal. PID: 550 SIG: 3

I/dalvikvm( 550): threadid=3: reacting to signal 3

E/Sensors ( 550): poll() failed (Interrupted system call)

I/dalvikvm( 550): Wrote stack traces to '/data/anr/traces.txt'
[LG Nitro HD] altvolt74:
Unable to find the post with aosp 4.1 built I. This thread can some one help

:confused:

---------- Post added at 05:49 PM ---------- Previous post was at 05:36 PM ----------

And which of this ROMs has WiFi direc
[LG Nitro HD] lordcheeto03:
http://xdaforums.com/showthread.php?p=36289450&highlight=aosp#post36289450

Page 23, 1st post.

Delivered.
[LG Nitro HD] tdm:
More news on the crashing issues...

Got the crap scared out of me this morning investigating a bsod. My kids were playing games on the spectrum yesterday and when I came home, it had a black screen and the button backlights were lit up. I didn't have time to do anything with it, so I plugged it into the computer to keep the battery charged. Got up this morning and started tinkering with it. I found that killing surfaceflinger made the screen come back. Wow, that's cool. But for some reason, the screen was washed out from the center to about 1/8" from the edge in a rounded rectangle pattern. Like screen burn-in on an old CRT while the screen was completely black. I rebooted and the same pattern appeared even on the LG logo. Oh sh!t, I'm thinking my screen is busted somehow. I panicked and went into recovery, reinstalled the vendor GB ROM, same deal. Back into recovery, wipe, reistall RC2, and finally I noticed the washed out rectangle fading. Whew! I'm so relieved. No idea what happened ... anyone familiar with display hardware who can explain this?

And then this afternoon, I'm letting my 7yo play some games. Nothing that eats too much horespower, just Jewels or something like that. And the next thing I know, he shows me the boot animation. That kid seriously has a future in software testing, I swear. ;) Anyway, I look and the phone didn't actually reboot, it was just a UI restart. And it was the same Adreno/GSL running out of memory issue which caused surfaceflinger to restart.

Seems suspicious that surfaceflinger is involved in both of these issues. But as far as I know, CM10 does not have this issue across all hardware (or even all MSM devices) so the problem can't be in the generic code. I wonder if the Adreno libs are faulty. Does anyone know which other devices have CM10 ROMs and use these same Adreno binaries?
[LG Nitro HD] tdm:
Not sure what to make of that one. In doa_logcat.log I see several of these:

W/Watchdog( 550): *** WATCHDOG KILLING SYSTEM PROCESS: null

Followed by what seems to be a complete UI restart.
[LG Nitro HD] aldo90:
I couldn't find the log cats just the kmsg file, dont remember if was a random reboot or a BSOD

View attachment last_kmsg.4.zip

EDIT: got another one View attachment last_kmsg.9.rar
[LG Nitro HD] notzippy:
I wasnt sure what to make of it either, thats why I passed it on :)

Weird what happened with your phones display - so it was just time that fixed it ? I let my 2yo proof my layout design - if he can navigate it, it must be good :D

interesting work done by slg1119, the HTC sensation does have the same gpu, it would be nice if they shared there work..

Nz
[LG Nitro HD] tdm:
Yeah just time fixed it. Others at AF said they have had the same issue and its caused by over heating the display.

I'll definitely look at for HTC sensation roms later this week....
[LG Nitro HD] Flyview:
This is why I run at 1.29GHz until we get some undervolting. Phone just gets too hot if charging, being used and/or talking on the phone.
[LG Nitro HD] lyfkevin:
Sony Xperia S, it's CM10 by Free Xperia Project

EDIT:

+ HTC Sensation, HP Touchpad etc
[LG Nitro HD] miroslav_mm:
My opinion, we have 3 difference kinds of reboot/problem.

First one - Vold reboot - I already fixed it.

Second - "black screen and the button backlights" - problems with backlights driver in kernel.

Third - problem with hwcomposer it working not right because Andreno libs/kernel drivers KGSL have mistake.

Currently in CM10 using JB Andreno libs from 8960 - it working but think bad idea. I am tried use libs from official JB ROM HTC One S (S3) - inside libs for 8660_SURF. ROM booting but system not starting because have problem with KGSL, need update drivers in kernel. Kernel sources of HTC One S (S3) not available so need port from CAF.
[LG Nitro HD] aquariuz23:
TDM, that burnt out ring around the display existed since the beginning of time on cm10 preview 1 from arcee. I had encountered that once or twice randomly, and the only way for it to disappear, in my case, was just to let it sit for a few minutes and it'll just vanish on its own. I don't think it was an overheating issue because I experienced it not during a charge but from a random black screen. When I pulled the battery and rebooted, the ring appeared.
[LG Nitro HD] lyfkevin:
hi tdm, su640 version does'nt boot.

stucked at LG logo.

I replaced cm10 boot.img and then boots

wifi cannot turn on

---------- Post added at 11:13 PM ---------- Previous post was at 10:23 PM ----------

just flashed official cm10, found that kernel compile date was Sun Jan27.

but in github, CyanogenMod/lge-kernel-iproj last update was 3months ago?

It means sth added recently but we cant see?
[LG Nitro HD] aquariuz23:
TDM, I'm having a serious issue that came out of nowhere. This is gonna be long so please bear with me, I want you to get an idea of what happened, maybe you can figure out what's wrong.

This past friday, I woke up to my phone stuck at the bootanimation. Sorry but I didn't have the chance to do a logcat or anything. I just had to reboot it by pulling out the battery. However, even after rebooting, the phone continued being stuck in the bootanimation. I went to cwm, and cleared both caches, and still nothing. No matter what I did, it will not budge from the bootanimation. I ended up making a nandroid backup of the phone, and proceeded to wiping the data off the phone. Rebooted it, and it loaded the rom just fine (of course missing all my data). At this point, I was still on Beta 6, and decided maybe I should just update to RC1. Flashed RC1 and Gapps, rebooted, and I'm still fine. Good. So I thought let me try to restore back my /data from the backup. Did so, and now I'm stuck on the bootanimation again. So something is really wrong with my data partition. Frustrated at the thought of losing all my not backed up files (text messages primarily) I went back to CWM and gave a last try to wipe caches and reboot. Lo Behold, it booted up into the ROM with all my data intact! I immediately made a TiBu backup of everything!

After that is completed, I tried rebooting the phone, and just what I had thought, it failed to boot up again, getting stuck again. So I wiped the phone, started fresh, and put in all my info from scratch. Tried rebooting again, and all is fine so far. Now I restored all my backup from TiBu, and after over an hour, it told me to reboot, so I did. And BAM, the phone is now stuck again on the bootanimation! I am like GAAHHH!!! BLEEP BLEEP BLEEP!! Went back to cwm, again tried to wipe caches, and thankfully it booted back up. From there on, I did not reboot the phone at all and had no force reboot so I was good. But this morning, I woke up to my alarm ringing, and when I tried to disable it, the phone locked up! :( And sure enough, rebooting it left me stuck again, and this time, nothing that I do (except wiping /data) fixes it. So now I'm screwed, sorta.

Can you think of anything I can do to prevent this from occuring again? I'm about to try wiping partitions to do a completely fresh install of RC2, and then just install the apps from fresh and maybe restore my text messages :( Any suggestions guys?
[LG Nitro HD] miroslav_mm:
no. date in kernel version it just date of build. night build all time sync with tree after building, and all time rebuilding all components, not matter was changes or no.
[LG Nitro HD] tdm:
Hmm okay I'll look into the SU640 boot image.

CM10 compiles the kernel with each build. So the kernel build date will always match the ROM build date, regardless of whether there have been any kernel changes.
[LG Nitro HD] tdm:
The Spectrum users have encountered this issue also. I haven't figured out what causes it. Based on your input it seems that something in the data partition is a contributing factor, which is new information.

Really the only thing that would help at this point is if you can narrow down what in the data partition is causing this, or if I can reproduce it myself.
[LG Nitro HD] aquariuz23:
TDM, so I'm back and operational now. Followed the following steps that kernelpan1c and I used to try to fix our BSODs and it got me back up and running.

---------- Post added at 07:57 PM ---------- Previous post was at 07:49 PM ----------

TDM, the only thing I can think off that I did the night before I experienced the persistent bootanimation lock was that I decided to give the tablet interface a try in the settings. Tbh, I think when I set up the tablet interface, it said that I should reboot for the changes to take affect, so I did, and I fell asleep, and maybe it has been stuck in bootanimation since then. That's all I can think of. Now if that is the case, does that settings get saved in the data partition or some other partition? I'm on AOKP btw.
[LG Nitro HD] tdm:
Okay cool. That narrows things down. What exact version were you using?

I have a resource pruning/optimization script that removes "unused" resources. I had been removing the sw600dp resources in the beta builds because I didn't think they were used. But it turns out these are used for tablet mode. When booting into tablet mode (either by forcing it in AOKP or by setting the density sufficiently low in CM10) and those resources are not present, the system cannot start up and you see the boot animation indefinitely.

For AOKP, the "force tablet ui" setting is stored in this file:

/data/data/com.aokp.romcontrol/shared_prefs/com.aokp.romcontrol_preferences.xml
[LG Nitro HD] xordos:
mic issues

Hi tdmcode,

I know the mic issue has been raise a few times in this thread, but not sure if you have any plan/time take a look this.

The issue is the voice recording in many app is too low, even I directly speak to the upper part (the noise cancellation mic) it is better than regular mic, but still very low. For example, "Smart Voice Recorder" from google play store.

And looks like the phone call doesn't affected by this issue. but some voice chat app barely useable because this problem.

Thanks.
[LG Nitro HD] tdm:
I downloaded the app and I see the issue.

Does official CM10 work, or is it the same?
[LG Nitro HD] michaelbmx29:
I'm having a problem with instagram.. when i try to edit a picture, the picture disappears and i can't edit it the picture will pop back up after 10 secs or so but it will flicker.
[LG Nitro HD] Flyview:
This has to do with the general problem of flickering in CM10. Go to developer options and check disable hardware overlays. You have to do this after every reboot.
[LG Nitro HD] xordos:
I am not sure about this one right now...I can see my record history has good recording levels, that is a few month back...that maybe CM9 or CM10. I will refresh to CM9 and CM10 tonight to test it again.

Or if anyone have similar issue, pls share.

Thanks again for the quick response.

************************

Edit: following are some result when searching the "CM10 nightly discussion" Thread:

Sep 14:

http://xdaforums.com/showpost.php?p=31524515&postcount=450

Has the issue.

Sep 18:

http://xdaforums.com/showpost.php?p=31696553&postcount=488

this post says "Primary mic is back to bottom"

Oct 3:

http://xdaforums.com/showpost.php?p=32308924&postcount=730

.."not utilize noise cancel mic"

Still, I am going to test it latest nightly CM10 build tonight and report back.
[LG Nitro HD] tdm:
Thanks for digging those up. I see some interesting commits:

commit 48df37d18417ffd7dcc1dd20126f6cea607a2b93

Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org>

Date: Sun Sep 16 23:27:00 2012 +0100

iprj: Use P2P-capable firmware for STA mode

Change-Id: I7692439a2a02c81d05e52341e81c7134db8158be

commit da92b5426c8a837cefc0461f4a76784f3cad347d

Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org>

Date: Sun Sep 16 02:41:01 2012 +0100

iprj: Build the right audio HAL

Change-Id: I0525910f606b2b5558775a64b2dbce7d3233e59b

commit a4180e76ac945666b6c6a57e86e15ee612f566e4

Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org>

Date: Fri Sep 14 22:38:02 2012 +0100

iprj: Add a variation of the audio HAL

The acdb map in the iprj would create an ifdef mess in the common HAL,

so let's just fork it

Change-Id: Ibc8564c1f9fff31610ea5b133f7a7041487aa96f

I don't have the change da92b5426c8a837cefc0461f4a76784f3cad347d in my build tree so I'll look at fixing that.

Also don't have the correct wifi fimware in change 48df37d18417ffd7dcc1dd20126f6cea607a2b93 so maybe that's why wifi-p2p is not working.
[LG Nitro HD] xordos:
Just want to report back, (and as you already figured out some CM commit), the latest CM10 (20130128) doesn't have this issue, the primary mic is at the bottom, and the record level is clear and loud.
[LG Nitro HD] tdm:
Got voice search and wifi direct working on the nitro. I'm getting a kernel crash on the spectrum when accepting a wifi direct request so I'll need to fix that.
[LG Nitro HD] Flyview:
Does that mean it'll be using the correct mic? I think it's also using the noise cancelling mic when talking on speaker, no one can understand what I'm saying too well.
[LG Nitro HD] tdm:
Yes, same as cm10. Assuming that's correct.
[LG Nitro HD] aldo90:
last kmsg log, it was a random reboot I guess, two days ago. no BSOD or reboot since then and battery is good i suppose..
[LG Nitro HD] Flyview:
Just tested RC2. Called myself from another phone, put the Nitro on speaker and blew air into each mic. It's using the noise cancelling mic 100% on speaker :(
[LG Nitro HD] tdm:
The fix will be in rc3.
[LG Nitro HD] tdm:
Oh and rc3 is a bit delayed due to issues with the spectrum. I may have it tomorrow, or maybe the day after, depending on how long it takes me to find a kernel panic.
[LG Nitro HD] aquariuz23:
No worries sir, what u have done this far is amazing, considering how stable this rom is. Nobody here is rushing u for anything, well, maybe except for jb 4.2 Haha!

BTW, I probably should inform u that I am still experiencing the stuck on bootanimation issue. My phone ran out of juice and died. When I powered it n turned it back on, the phone remained in bootanimation. Fortunately, this time, I was able to recover by clearing both caches. Is there anything u might need from me if this continues to happen? Also, speaking of wiping caches, is formatting the caches partition the same as clearing the two caches?
[LG Nitro HD] tdm:
Thanks! That's a new one I haven't seen before. I'll definitely look into it. But it sounds like this is a pretty rare issue. If the issue is not obvious in the code, it may be difficult to reproduce and fix.
[LG Nitro HD] tdm:
Next time this happens, connect up to a computer and get me a logcat (adb logcat -d) and a dmesg (adb shell dmesg).
[LG Nitro HD] tdm:
Well, after digging a bit, I believe I found the exact line of code that caused the issue. It is deep in the bowels of the scheduler. The issue seems to be a bad pointer when walking up one of the scheduler data structures.

It's very difficult to diagnose issues with data structures if they cannot be reproduced at will, and doubly so for bad non-null pointers. Additionally, I can't seem to find any other reports of the same issue or any fixes for the issue using google. This is in generic code (eg. used by all architectures) and certainly very highly exercised. So if it happened often at all, google should have turned up more results.

Unfortunately the best we can do right now is hope this issue doesn't happen again. :(
[LG Nitro HD] RealyPssd:
Heya,

Been usuing your ROM/s for a few weeks now, and they've been great, very rarely are there any black screens/reboots, Maybe 2 or 3 total.

But I'm having problems with my Volume Keys/Rocker. I'm not sure if it's related to the ROMs or the phone it self, but lately they're very seldom working.

I tried wiping everything and installing CM10 rc2 and they still didn't work. I've been on your AOKP ROM before I tried your CM10 to see if that fixed the problem.

The phone is less than a year old and I've taken pretty good care of it..
[LG Nitro HD] tdm:
I was looking at yet another crash report, and the user indicated the phone was getting pretty warm. The reboot was called by userspace, just like most of the others we've been seeing. I decided to look through all the proprietary LG binaries to see which ones might call reboot. Guess what? thermald has the string "__reboot" in it. Hmmmm.... this is very interesting. I will need to investigate more. I don't see any obvious strings that would be logged .. which makes sense, because we haven't seen any so far.
[LG Nitro HD] tdm:
Try official CM10. If the issue is fixed there but not in my CM10, I'll take a look. Otherwise perhaps it's a hardware issue?
[LG Nitro HD] xordos:
cool, this explains some of my GUI restart as well. Usually, when I play some games for about 10-20 minutes, it may GUI restart.

Not sure if following is useful or not, probably you already know it:

http://xdaforums.com/showthread.php?t=1474736

Maybe we can find some threashold value? or even adjust it?

========

Edit, maybe I will try to find some app to stress testing / over loading the CPU? and monitor the temperature at the same time. to see if I can reproduce the GUI restart?

anyone has any suggestion about such app?
[LG Nitro HD] aldo90:
Actually, the phone was warm when I had the reboot, even in GB happened, usually starts when the phone get to 41C or 42C, I know this because I have a widget that shows the temperature, mostly when I'm using wi-fi. Yesterday I was playing minecraft and the temperature reached 42C and nothing happened, but I wasn't using wi-fi, so, I don't know if wi-fi is mainly the problem.

The idea of the app is fanstastic, if you find one please share it with us :)
[LG Nitro HD] xordos:
Thanks for the link, that will stress the GPU, but what I was thinking a simple app just stress CPU, with a interface show the current temperature, and (better if) you can control start/stop the stress. like Prime95 or orthos in PC.

I don't like test with heavy game right now, because I remember when I look through the logcat once I have a GUI restart, I think saw somewhere has OutOfMemory error, really not sure. So just want to use a simple App first to avoid the bug/defect from the testing program itself.
[LG Nitro HD] Flyview:
I use an app called "stability test". Should do exactly what you need.
[LG Nitro HD] tdm:
Here is a test for the thermald reboot issue. Anyone with even a little bit of batch or shell scripting experience should be able to do this.

1. Remount /system read-write.

2. Rename /system/bin/thermald to /system/bin/thermald.real

3. Paste the following script into a file named thermald:

#!/system/bin/sh

if [ -f /data/local/tmp/thermald.strace ]; then
mv /data/local/tmp/thermald.strace /data/local/tmp/thermald.strace.old
fi

exec /system/xbin/strace -f -s 256 -o /data/local/tmp/thermald.strace /system/bin/thermald.real "$@"

4. Push this to /system/bin/thermald and make it mode 755.

5. Reboot.

6. Push the heck out of the phone until it reboots: play games, do benchmarks, whatever.

7. After thermal reboot, send me a copy of /data/local/tmp/thermald.strace.old.
[LG Nitro HD] tdm:
That's a great CPU test app. thermald limited to 1026mhz after a few minutes and It looks like it stabilized there.

However, I think the CPU+GPU test alternates between CPU and GPU. Using the strace script, I see CPU1 flipping back and forth from online to offline while the scene on the screen flips between rotating and stopped. This probably gives the phone just enough breathing room to keep it stable. I've been running for 5 minutes so far and the system seems pretty stable. I'll keep it running for a while and see what happens.
[LG Nitro HD] Flyview:
Why not just use the CPU only test? That keeps both cores online. Actually, that's why I use it. If I ever need to apply my init.d CPU frequency script manually, I need to force both cores online or else it doesn't apply the settings for the second core. Also, watch as the temp goes back down the phone will be set to 1.67GHz as we found before. As a temporary hack, i increased the thresholds in my thermald so that they aren't reached under normal use, for this reason.
[LG Nitro HD] tdm:
My goal is to force thermald to reboot. The CPU only test doesn't seem capable of provoking this. thermald limits the CPUs to 1026mhz and the system seems to stabilize there.

Most all of the times I've seen my phone restart, my kids have been playing games, and most of the other users' crashes have had traces of GPU involvement in the logs. So that leads me to the conclusion that the GPU is the component at fault -- or at least the component that pushes the thermal limit past the critical threshold.
[LG Nitro HD] Flyview:
If you want to create as much heat as possible, drain the phone a bit so it doesn't have full battery, plug it in so it is charging AC, make a phone call on speaker so the screen is on, and run the CPU+GPU test all at the same time. That should do it! lol. Charging and being on a call makes the phone hottest, I've found.

EDIT: I have some logs for you. I've put them in a rar. All are from CM10 RC2. You'll find "crash 1", "crash 2" and "tombstones". I found the tombstones confusing because the highest number isn't the newest by date so I just took them all.

Crash 1 is from a few days ago (jan 27). I believe it was a screen freeze where it stopped being responsive, followed by the screen eventually turning off and not turning back on. No reboot. Similar to what I was seeing with the conservative governor but I've been using ondemand...

Crash 2 just happened (jan 30). Screen goes black a second after I turned it on, LG logo shows once, and then nothing. I had to power down by holding the power button, and then power on. So the phone did again, not reboot. I wasn't doing much on the phone, I had a pdf open I was reading and the screen had timed out earlier or maybe I turned it off.
[LG Nitro HD] aldo90:
I just had two BSOD, one after the instalation of the stability test app and the other one while running the app, after five or six minutes at 41C, here are the logs