yashsingh1/xdaforums huggingface dataset:
[LG Nitro HD] salimbaba:
i have su640, (i_skt) .. and it is confirmed not to work with this Rom.. if i flash a p930 Cwm, it chooses to install atnt version which boots fine but has orientation issues, auto rotate fails.

i_skt simply fails to boot.
[LG Nitro HD] tdm:
Been looking into GPS issues with my VS920 (i_vzw) ... that's the last step until I can get official CM support. In my tests, I found that an incorrect gps module can cause the boot animation loop indefinitely.

su640 users, does that sound like your issue? Can you try to replace /system/lib/hw/gps.msm8660.so with the official CM10 version to see if that fixes boot? Also try just removing /system/lib/hw/gps.msm8660.so.
[LG Nitro HD] lyfkevin:
great found :] there is no gps.msm8660.so file in official su640 cm10. gonna try now

--------------------------------------------------------------------------------------------

edit : doesnt work, also tried to replace gps.msm8660 by gps.iprj.so
[LG Nitro HD] tdm:
GPS is fixed in i_vzw so it should get official cm support soon. :D That frees me up to take a look at i_skt and I_lgu, and also get aokp42 fixed.
[LG Nitro HD] notzippy:
Anyone notice that when the phone reboots the wifi settings get reset to be always on ? Not good for battery life..

Nz
[LG Nitro HD] notzippy:
Random restart, my phone was not plugged in so I do not know how the charger invoked a reboot - aokp41, last_kmsg.0

[ 4805.145263] charger: power supply ac (Mains) online (action=change num_online=1 num_supplies=3)
[ 4865.145263] charger: power supply ac (Mains) online (action=change num_online=1 num_supplies=3)
[ 4925.145263] charger: power supply ac (Mains) online (action=change num_online=1 num_supplies=3)
[ 4981.256011] charger: [4981231] rebooting
[ 4982.179138] SysRq : Emergency Remount R/O
[ 4982.180358] SysRq invoked by charger
[ 4982.202026] EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)
[ 4982.226501] EXT4-fs (mmcblk0p28): re-mounted. Opts: (null)
[ 4982.243988] EXT4-fs (mmcblk0p31): re-mounted. Opts: (null)
[ 4982.258514] EXT4-fs (mmcblk0p22): re-mounted. Opts: (null)
[ 4982.259765] Emergency Remount complete
[ 4982.285858] sys_reboot: sys_reboot is called from android
[ 4982.286651] sys_reboot: reboot cmd is 19088743
[ 4982.287078] kernel_restart: invoked by charger
[ 4982.291198] sdio_alInitiating msm_sdio_al_shutdown...
[ 4982.292083] sdio_al: sdio_al_modem_reset_operations
[ 4982.292907] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 1
[ 4982.294097] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 1
[ 4982.296417] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 1
[ 4982.297302] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 1
[ 4982.298553] sdio_al: sdio_al_modem_reset_operations
[ 4982.299774] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 4
[ 4982.300628] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 4
[ 4982.302032] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 4
[ 4982.303222] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 4
[ 4982.304443] sdio_al: msm_sdio_al_shutdown: msm_sdio_al_shutdown complete.
[ 4982.415985] Restarting system.
[ 4982.418212] set_dload_mode : 0
[ 4982.420867] restart time : 2013-02-12 15:58:27.566511390 UTC
[ 4982.422302] Going down for restart now
[LG Nitro HD] tdm:
Yeah that is really weird. "charger" should not be running at all during normal operation.

I don't suppose you can check now and see if it's running? It's not running here on my Nitro (also aokp41).

If I get any more reports of charger misbehaving, I will either instrument it heavily or rip it out entirely. I think there's a LG proprietary charger app that can be used instead.
[LG Nitro HD] notzippy:
No, its not running right now but I will check regularly

Nz
[LG Nitro HD] notzippy:
Has anyone used the app CSipSimple ? When it attempts to dial out it immediatley segfaults

https://play.google.com/store/apps/details?id=com.csipsimple

D/AudioHardwareMSM8660( 206): setMicMute_nosync calling voice mute with the mMicMute 0
E/AudioHardwareMSM8660( 206): unknown voice stream
I/AudioService( 454): Remote Control registerMediaButtonIntent() for PendingIntent{41f4de70: PendingIntentRecord{422e6b48 com.csipsimple broadcastIntent}}
I/AudioService( 454): AudioFocus requestAudioFocus() from android.media.AudioManager@41c60a30com.csipsimple.utils.audio.AudioFocus8$1@41c70c38
D/AudioTrack( 3387): Turn on Direct Output for VOIP RX
W/AudioPolicyManagerBase( 206): getInput() could not find profile for device 100000, samplingRate 16000, format 1,channelMask 0010
E/AudioRecord( 3387): Could not get audio input for record source 7
E/libOpenSLES( 3387): android_audioRecorder_realize(0x5b72e008) error creating AudioRecord object
W/libOpenSLES( 3387): Leaving Object::Realize (SL_RESULT_CONTENT_UNSUPPORTED)
I/AudioService( 454): Remote Control unregisterMediaButtonIntent() for PendingIntent{42070750: PendingIntentRecord{422e6b48 com.csipsimple broadcastIntent}}
I/AudioService( 454): AudioFocus abandonAudioFocus() from android.media.AudioManager@41c60a30com.csipsimple.utils.audio.AudioFocus8$1@41c70c38
F/libc ( 3387): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 3563 (ervice.Executor)
I/DEBUG ( 201): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 201): Build fingerprint: 'lge/aokp_i_atnt/i_atnt:4.1.2/JZO54K/eng.build.20130201.104034:userdebug/test-keys'
I/DEBUG ( 201): pid: 3387, tid: 3563, name: ervice.Executor >>> com.csipsimple:sipStack <<<
I/DEBUG ( 201): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 201): r0 00000000 r1 00000007 r2 00000000 r3 00000000
I/DEBUG ( 201): r4 5c882cec r5 5b7f8138 r6 5e180d5d r7 5b7c3a35
I/DEBUG ( 201): r8 5b7f80bc r9 10624dd3 sl fffffffe fp ffffffff
I/DEBUG ( 201): ip 00000007 sp 5e3b2520 lr 407abcbd pc 5e18e5ac cpsr 60070030
I/DEBUG ( 201): d0 5555555555555555 d1 5555555555555555
I/DEBUG ( 201): d2 5555555555555555 d3 5555555555555555
[LG Nitro HD] notzippy:
Havent tried it on a official CM10 build, but it also segfaults on AOKP 42

Nz
[LG Nitro HD] pcwizzy37:
That is what I get when I try to get cm10.1 to boot on my LG Lucid!
[LG Nitro HD] lionman229:
I never ever did an unbrick (knock on wood) and i get the camera reboot :(
[LG Nitro HD] drumist:
Very confusing...
[LG Nitro HD] tdm:
+1

I bought my device used and it had GB. No reason to suspect it has ever had a custom ROM let alone an unbrick. And I have the camera reboot issue.
[LG Nitro HD] aquariuz23:
A couple of bugs I've encountered tonight, and yes I've done a clean install tonight. Can anybody else please confirm these as widespread bugs or just my phone itself. Do note that these things were working in CM10.

1) Netflix has no video, just black screen, but audio works fine.

2) Google Now uses noise cancelling mic instead of proper mic

3) Audio is back to mono (tested in Poweramp, probably the reason why i said the audio quality seemed different in my last reply)

4) Youtube app could not play any video. the loading circular loop will continuously loop for about 10 seconds, blinking every 2 seconds, before giving an error " there was a problem while playing Touch to retry".

5) Playback of any video file using any video app (mx player, quickpic, even gallery) severely lags at a framerate of about 2-3fps. Audio part runs smoothly.

tdmcode, if these are bugs in the rom n not just my phone, issues 2 and 3 had also occured in CM10 a few months back but were remedied (after a really long time). Not sure what's going on with the others though. Nonetheless, I still love this ROM! And as long as we don't get any random BSODs or reboots, I can deal with all the other issues. Hopefully you can remedy them too :)
[LG Nitro HD] Maverick.Marq:
Cm10 or akop?
[LG Nitro HD] woodardbg:
I too can confirm YouTube and Google voice using noise cancelling mic.

Battery life is that good as of yet. Been running aokp since it was put up.

However I haven't had any BSODs or random reboots as of yet. Which is great.

Those other issues I can deal with. It was just the BSODs and reboots that kept me from using cm10 daily. Aokp seems a lot better IMO

nice job

Edit: just confirmed Netflix bug Also. No video. Audio works
[LG Nitro HD] aquariuz23:
buddy, u must be sleeping while reading my post :P n anyways if it was cm10 why would I post it on the aokp thread? Lol.
[LG Nitro HD] david.degraw54:
This isn't a cm10 thread lol u must've been sleeping while reading the title of the thread.
[LG Nitro HD] tdm:
This thread is not for the official CM10. But it is for both of my ROMs, CM10 and AOKP.

Note there is very little difference between my CM10 and the official one. At least for now.
[LG Nitro HD] Maverick.Marq:
= my post made sense :p
[LG Nitro HD] tdm:
Playing with the wifi-p2p stuff, it seems this is the source of the problem:

<3>[ 31.448730] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23

The wifi driver is not detecting p2p support from the hardware for some reason. Need to figure out why in order to fix wifi-p2p.

Of course, the driver should handle this situation and not panic the kernel. That's an easy fix.
[LG Nitro HD] aquariuz23:
Lol yeah I completely forgot that there r 2 rooms on this thread. My bad.
[LG Nitro HD] tdm:
Sent an email to rmcc about the wifi-direct issue, hopefully he'll respond.

The camera reboot issue is proving more difficult. I don't see anything that indicates a problem in the kernel logs, just an unceremonious hard reboot. :(
[LG Nitro HD] aquariuz23:
One more bug update guys sorry. This was also previously present at arcee's cm10.

Call volume via speaker phone is seriously low, to the point where I need to place the speaker close to my ear to hear. The volume via the earpiece is good enough, but a little low.
[LG Nitro HD] Maverick.Marq:
Posted this in the cm10 nightly discussion but I thought I'd post it here as well as this seems to be where the action is happening.

Got an email from someone working on camera reboot issue

” Comment #2 on issue 6550 by tdm.c...@gmail.com: Reboot when power button is pressed in camera app. p930

http://code.google.com/p/cyanogenmod/issues/detail?id=6550

I'm looking at this issue but not finding many clues.

What is the ion kernel change referenced? *Can you point me to a github commit?"

If anyone can find this commit it would be extremely helpful! Thanks :)
[LG Nitro HD] tdm:
Yeah guess who that was.... ;)
[LG Nitro HD] Maverick.Marq:
Derp xP

Should have known. Well I looked as hard as I could. Couldn't find the commit on any of the change log sites I don't think they go back dar enough
[LG Nitro HD] tdm:
Had another BSOD today. I noticed it when the phone rang with a voice call. I wonder if there's a correlation there?

Anyway, I saved off all the logs (the phone is accessible via adb during this time). Didn't see anything interesting in them, just normal activity. :confused:
[LG Nitro HD] aquariuz23:
Yeah, we basically have two kinds of black screen of death related with android 4.1.

The first one and the most annoying one since it drains the battery severely is when the phone randomly and quietly reboots itself but fails to load the rom. It will go to the LG logo, n when the logo disappears, the rom never loads, just sits there in a black screen n the phone is completely non responsive. However, the phone eventually gets hot for some reason. When you do a battery pull, the phone reboots n works fine, but u will find that the battery will lose about 10-20% of charge in the matter of seconds.

The 2nd bsod is less sinister but annoying nonetheless. Simply put, the screen will not wake up from a sleep or standby. The phone itself is fully active with calls or notifications working, sound too and hard keys as well. But the screen is off and non responsive to touch.

So yeah, I hope that gives you some kind of idea what we've been facing the past few months ever since using cm10. The worst part is, not everyone experiences both or either of the bsods. Some ppl won't ever see the issue for months and others, like me, will constantly get them.
[LG Nitro HD] tdm:
Was just on my way to bed and noticed another BSOD so I captured the dmesg and compared it to the one earlier today (well, technically yesterday). Two o-freakin-clock in the morning and I'm poring over kernel logs. Grrr...

Anyway, I found this in both logs at a time when I could reasonably expect the screen might have went out to lunch:

[APDS9900] [apds9900_check_reliablility 932] ### apds9900_check_reliablility fail!! reinit device !! control reg(0),buf(20)

Please watch for this message. If you can, connect a USB cable during BSOD and at least once per day and run something like this:

adb shell dmesg | grep APDS

If you see it without the BSOD, it's a false alarm.

If you don't see it during the BSOD, it's a false alarm.

But... if it's always there for a BSOD but never any other time, that's a good indication it's pointing to the root cause.
[LG Nitro HD] tdm:
Oh btw, the apds9900 device driver says "apds9900.c - Linux kernel modules for ambient light + proximity sensor". Don't know why this would correlate to the BSOD but who knows....
[LG Nitro HD] tampaboy1984:
I am on CM10 build and YouTube will not play videos in HD, is this same issue in AOKP?
[LG Nitro HD] woodardbg:
aokp plays in HD. but its hit or miss. sometimes videos play sometimes loading the video get stuck and all you see is the "loading circle" moving then stops
[LG Nitro HD] tampaboy1984:
I went to the newest CM10 nightly and this issue is resolved.
[LG Nitro HD] Malnilion:
This would make a TON of sense. I was able to pretty much eliminate my BSOD's for a while by changing an auto-brightness setting, but I messed with my configurations and they came back.
[LG Nitro HD] tdm:
Hmmmmm ... I wonder if the issue is that the proximity sensor is stuck in always-on?
[LG Nitro HD] Swetnes:
Well if this turns out to be the culprit (which makes sense) I think they should give you a job at CM. :rolleyes:
[LG Nitro HD] tdm:
I did a very quick look and it looks like the apds9000 driver code is exactly the same between ics and jb. So something else might be somehow interfering or conflicting with it, perhaps.
[LG Nitro HD] Maverick.Marq:
I might be wrong because I never used ICS for more than a couple days but reboots occurred on ICS as well right guys?
[LG Nitro HD] tdm:
That would be good to know. Anyone?

Also I will start playing with oc/uv kernel and linaro soon.
[LG Nitro HD] rani9990:
Reboots happened on everything other than stock :P
[LG Nitro HD] tdm:
Stock meaning gb, ics, or both?
[LG Nitro HD] rani9990:
There were no gingerbread ROMs other than stock. So no random reboots on GB. Or stock ICS. But cm9 had it. HO!NO!'s full throttle based off of cm9 seemed to have the least, if not none amount of random reboots.
[LG Nitro HD] tdm:
Sorry I'm not that familiar with all the models and stock versions yet. I'm coming from the spectrum which vzw had just recently ota'd to ics. And afaik nobody has experienced the bsod or camera+power reboot on that (though random reboots are reported, and there are no working jb roms for it yet).

My att nitro came with gb (bought it used) and I assume most or all of the original run of devices did also.

I was under the impression that most or all of the carriers had ota'd to ics and the vzw spectrum was the last hold out. Is that accurate?

It's curious that stock ics does not have these issues but cm9 does. That means it's likely that either LG released bad kernel code, or one of rmcc's ics changes is to blame, or cm9 tickles a kernel bug that stock does not.

Interestingly, I made the spectrum ics kernel by using the cm9 iproj kernel. LG had about 98% of the i_vzw code done by the time they dropped i_atnt so it was relatively easy.

I'll do some more research on this...

Thanks!
[LG Nitro HD] rani9990:
No problem. Yes, most of the carriers have updated past gingerbread to ICS. But fwiw, this could be unsolvable, because by far EVERY phone I have had has experienced multiple random reboots and bsods on custom ROMs.
[LG Nitro HD] aquariuz23:
Tdmcode, somehow, your aokp rom is the stablest n most reliable so far. I've only had one bsod since I flashed your rom a few nights ago. N other than the bugs, performance is superb!
[LG Nitro HD] drumist:
A lot of people are still on Gingerbread because the ICS update required flashing from a computer.
[LG Nitro HD] tdm:
Did a diff between the V10f GB kernel sources and the CM iproj kernel sources. There are only a few changed lines between them, discounting whitespace and api changes. Not knowing the hardware, I can't say which changes are good and which are bad. I may try reverting all of them and see what happens.

@@ -252,7 +252,7 @@
/* FAR-to-NEAR */
data->ps_detection = 1;

- input_report_abs(data->input_dev_proxi, ABS_DISTANCE, 3); // fix to 3cm when near
+ input_report_abs(data->input_dev_proxi, ABS_DISTANCE, 0); // fix to 0cm when near
input_sync(data->input_dev_proxi);

ret = i2c_smbus_write_word_data(client, CMD_WORD|APDS9900_PILTL_REG, data->ps_hyster
esis_threshold);

@@ -959,7 +960,7 @@
else
break;
}
- if(((data->enable &0x20)==0)&&((enable &0x20)==1))
+ if(((data->enable &0x20)==0)&&((enable &0x20)==0x20))
{
apds9900_set_pilt(client, 1023); // to force first Near-to-Far interrupt
apds9900_set_piht(client, 0);

@@ -967,6 +968,7 @@
papds9900_data->ps_threshold = APDS990x_PS_DETECTION_THRESHOLD;
papds9900_data->ps_hysteresis_threshold = APDS990x_PS_HSYTERESIS_THRESHOLD;

+ apds9900_change_ps_threshold(client);
if(apds9900_debug_mask & APDS9900_DEBUG_GEN_INFO)
DEBUG_MSG("### apds9900_set_enable initialize ps_threshold\n");
}

@@ -1609,7 +1611,7 @@
apds9900_set_config(client, 0x00); /* unless they need to use wait time more than > 700ms */

/* ALS tuning */
- apds9900_set_atime(client, 0xCA); /* ALS = 100ms , MAX count = 37888 */
+ apds9900_set_atime(client, pdata->atime); /* ALS = 100ms , MAX count = 37888 */

/* proximity tuning */
apds9900_set_ptime(client, 0xFF); /* recommended value. don't change it unless there's proper reason PTIME = 2.72ms, MAX count = 1023 */

@@ -1715,7 +1717,7 @@
dev_info(&client->dev, "enable = %s\n", papds9900_data->enable ? "1" : "0");

pdata->power(1);
- mdelay(10);
+ mdelay(20);

err = sysfs_create_group(&client->dev.kobj, &apds9900_attr_group);

@@ -1932,7 +1934,7 @@
if(papds9900_data->enable != 0x2F)
{
pdata->power(1);
- mdelay(10);
+ mdelay(20);
}

//if(papds9900_data->enable != apds9900_enable_backup)
[LG Nitro HD] tdm:
Playing around with over clock, my nitro seems stable at 1674. It wouldn't boot when I added in the higher frequencies 1728..1944.

Using a linaro compiled kernel also.
[LG Nitro HD] BigSexySCJCD:
Nice would love to see an overclock kernel , and thanks for all your work so far its been great
[LG Nitro HD] hereric:
Just installed AOKP41. Looks good so far, I performed the unbricking guide with the P936 KDZ, so hopefully I will have less random reboots than I did previously!

My random reboots happen VERY RARELY on official ICS, and NEVER in GB.

CM10 and 9 have them pretty frequently though.

Currently have the p936 baseband, will try different basebands to see if the frequency of reboots changes based on that too.

Just noticed there is no mobile data toggle. Is there any way that can be added in a coming release?
[LG Nitro HD] tdm:
I don't think aokp has a data toggle. I can look into adding it though.

It's there on my cm10 build, yes?
[LG Nitro HD] david.degraw54:
I would assume so since its there in the official CM10 build.
[LG Nitro HD] lionman229:
Have you been able to contact RC about these issues? Ill be able to test any fixes in about 2 weeks when im home from college. Ill be happy to help in any way possible.
[LG Nitro HD] tdm:
He didn't respond to my email, I'll have to try again. Or maybe find a forum that he frequents.
[LG Nitro HD] lordcheeto03:
I'm using AOKP and have experienced not one single random reboot. The camera bug that exists in cm10 is most assuredly present, but that's it as far as reboots go. I have the charging glitch mentioned earlier, but it's more of an annoyance than anything. From what I've noticed so far is that this thing is full of swag, but not too many bugs.

One thing about the charging glitch; has anyone else noticed that once it happens in AOKP it tends to be present in other ROMs as well? I performed a clean install of full throttle and paranoid only to find that they have a hard time charging also. Never saw the problem before flashing this ROM.
[LG Nitro HD] tdm:
Warming up the build box, CM 10.1 branch created.

AOKP seems to be on branch jb-mr1. Don't know if that's their final branch name or not, they tend to be less public about their development (or maybe I just don't know the right places to look).
[LG Nitro HD] david.degraw54:
I don't think there is a cm10.1 branch for the nitro yet as the post says that the branch will have to be created by the devices maintainer and when that happens they usually post it on the CM Google+ page and I haven't seen anything for our device yet. I could be wrong though...
[LG Nitro HD] tdm:
That's what makes it fun! :D
[LG Nitro HD] Maverick.Marq:
I wish I could thank this post a million billion times.
[LG Nitro HD] tdm:
It compiles and I got it up far enough that adb is accessible.

Currently working through library linkage issues that are preventing surfaceflinger (the GUI) from coming up.
[LG Nitro HD] tdm:
The cutting edge is making me bleed, so I think it's going to be a few days before I can get CM 10.1 going. They redid the qcom hardware stuff again and it'll take a while to sort it out.
[LG Nitro HD] Maverick.Marq:
Your perseverance is truly a testament to the wonderful ability of the human mind (go home maverick.marq you're drunk)
[LG Nitro HD] tdm:
Looks like I am finally getting the radio issues figured out on the spectrum. I expect that Monday or Tuesday I'll release updated ROMs with full i_vzw support and an OC kernel compiled with linaro.

There's little to no changes going into 4.1 anymore so there will probably be a delay of a couple weeks while 4.2 gets broader device support, then we'll see 4.2 ROMs start popping up.
[LG Nitro HD] tdm:
Anyone getting 4g with at&t? I'm in Seattle and at&t has 4g ads all over. But I've not seen 4g yet, only "h+". I'm using straight talk and my own aokp41 build on an at&t nitro.

The spectrum that I have (a loaner for dev work) gets a 4g signal no problem, on vzw if course. So I know the 4g indicator is in there somewhere lol.
[LG Nitro HD] lordcheeto03:
I am currently using JellyBam ROM and getting AT&T 4G in Pensacola, FL, so I know I am in a 4G area for sure... Just for the sake of taking one for the team I will flash AOKP again and make sure my settings are set for 4G and report back as to whether or not I get it with that ROM. I will do it with your CM10 as well if you wish, just let me know.
[LG Nitro HD] arda99:
Straight talk has access to HSPA+ only, no LTE, even you're on ATT network.
[LG Nitro HD] lordcheeto03:
AOKP41 on clean install + gapps... nothing extra, no google accounts added, nothing; shows 4G connectivity.

I'm flashing your CM10 for good measure and about to post screenshots for visual proof, but 4G connectivity IS present in your CM10 as well.
[LG Nitro HD] lordcheeto03:
CM10.
[LG Nitro HD] Maverick.Marq:
I currently have a bsod. but I'm trying to run adb shell dmesg | grep APDS

the command goes through and I don't see anything. I'm not formilliar with dmesg

does this mean the line you looked for was not there?

So I did a logcat and dmesg to txt files.

I did a search for apds on both and nothing showed up.

hope this provides some insight into the bsod.

btw this is on cm10 nightlies but the reboot issue should be the same.

summary

cm10 Nightly

BSOD

no adps in log cat or dmesg
[LG Nitro HD] tdm:
Yeah no output means no match. I downloaded the dmesg. There is about 90 minutes of log but nothing about APDS.

How long was it prior to taking this dmesg capture that you (1) first noticed the BSOD, and (2) last used the screen successfully?