Found some suspicious mutex code in the jb update that rmcc applied from CAF. Naturally, I enabled the mutex debugging options in the kernel to see what happens... and what happens is that the msm framebuffer code panics the kernel, for some reason that is not readily apparent. Apparently there's some really bad mojo in there that's going to be a huge pain in the backside to diagnose and fix. At this point, I don't even know who to blame... Qualcomm, LG, or CAF.
The Following 2 Users Say Thank You to tdm For This Useful Post:
I fixed two mutex issues in the MDP (display) code. If anyone is running into bsod issues, please try these. All I ask is to report back on whether the fix worked, and to check if either of the below messages shows up in the kernel log (dmesg) at least a couple times per day. Simply run "adb shell dmesg | grep mutex" from your computer, or open a shell and run "dmesg | grep mutex" directly on the phone.
Diagnostic messages:
mdp4_overlay_play: mutex double unlock avoided
mdp4_dtv_overlay: spurious mutex_unlock avoided
Instructions:
1. You should be running Quattrimus CM10 or AOKP41 rc1, rc2, or rc3.
2. Download the appropriate boot image for your device from below.
3. Name the image boot.img
4. Reboot into recovery.
5. Run these commands exactly as shown:
adb push boot.img /
adb shell dd if=/boot.img of=/dev/block/mmcblk0p8 bs=4096
adb reboot
Would it be worth it to change to this boot image even if we haven't noticed a bsod? I've been working in the yard an average of 4-5 hours most days playing music through double twist on my phone so if its sound related... I should see something fairly quick. I could flash this if your just data mining right now.
If of course any data from someone who isn't experiencing bsods would be helpful.
Sent from my VS920 4G using Tapatalk 2
__________________
Occasionally, I can be found on #androidforums on freenode.
Would it be worth it to change to this boot image even if we haven't noticed a bsod? I've been working in the yard an average of 4-5 hours most days playing music through double twist on my phone so if its sound related... I should see something fairly quick. I could flash this if your just data mining right now.
If of course any data from someone who isn't experiencing bsods would be helpful.
I think I just witnessed a bsod happening real-time this morning.
I unlocked my phone and went to pull up an app, and the screen froze. No response from anything except the power button. But pressing the power button did turn off the screen, and then turn it back on again. I even waited about 10 seconds to check if the lock screen would engage, but it didn't. So I had some other things to do for the next 20 minutes and left it alone.
Then I picked it up again and the screen won't come on when I press the power button. adb connects, and it's got that weird issue where "ps" hangs. But the app is different (it's Google+ this time). Any attempt to access anything under /proc/<pid> that deals with the VM hangs. This includes cmdline and maps. But surprisingly, stat, statm, and status are okay....
So next I killed surfaceflinger and the bootanim comes up, but won't go away. And that pesky 24462 process is still hanging around causing trouble.
Tried to run "sync". It hangs.
Tried to unmount filesystems. Seems like ext4 read/write filesystems hang (/mpt, /tombstones) but readonly fat filesystems don't (/firmware).
It seems like there is a lock that is held but never released. Possibly in the filesystem code. But I'm sure it won't be easy to find.
I think I had close to the same issue. My phone was on the charger while I took a nap. When I got up, I went to see if I had missed any calls or texts and the screen was black. I tried power a couple times no dice. I forced it off and still couldn't get it back. pulled battery. rebooted got the boot animation issue where I couldn't get into user space. Hard reboot via power and left the phone by itself and it booted. scary
So I flashed the new boot.img. This gave me the hanging boot animation (odd since I'd had it disabled unless the boot.img affected that somehow). I went ahead and ADB'd in and did a dmesg dump. Being that the only thing that changed was this new boot.img I then took the original boot.img (from the downloaded zip) and moved that back over then did another dmesg dump.
I'm unsure if these will help at all or if there's something else I should be looking at to provide you more information.
I'd mess with it more, but I use my phone as my alarm clock so I don't want to brick it for the night.
*edit*
Ok, maybe this isn't necessarily related to the new boot.img. I was playing with bootanimations by pushing them to /data/local/bootanimation.zip to get rid of the pink unicorn and everytime I put a new bootanimation in there it does the same bootanimation loop thing, even with the original boot.img. Not sure why, but figured it might be worth mentioning. Also, anytime it bootanimation loops, the screen will timeout and the power button brings it back to the bootanimation. Removing the /data/local/bootanimation.zip through adb and rebooting through adb makes it boot perfectly fine again.
Last edited by Yoinx; February 4th, 2013 at 09:26 PM.
So I flashed the new boot.img. This gave me the hanging boot animation (odd since I'd had it disabled unless the boot.img affected that somehow). I went ahead and ADB'd in and did a dmesg dump. Being that the only thing that changed was this new boot.img I then took the original boot.img (from the downloaded zip) and moved that back over then did another dmesg dump.
I'm unsure if these will help at all or if there's something else I should be looking at to provide you more information.
I'd mess with it more, but I use my phone as my alarm clock so I don't want to brick it for the night.
*edit*
Ok, maybe this isn't necessarily related to the new boot.img. I was playing with bootanimations by pushing them to /data/local/bootanimation.zip to get rid of the pink unicorn and everytime I put a new bootanimation in there it does the same bootanimation loop thing, even with the original boot.img. Not sure why, but figured it might be worth mentioning. Also, anytime it bootanimation loops, the screen will timeout and the power button brings it back to the bootanimation. Removing the /data/local/bootanimation.zip through adb and rebooting through adb makes it boot perfectly fine again.
So... are you able to run the test kernel now, or did you give up?
So... are you able to run the test kernel now, or did you give up?
And has anyone else used this successfully yet?
Give up? Nah. I don't know how much anything I can provide could really help. But, I did end up getting it to boot with the test kernel. Didn't do anything different, just re-copied it over. Kinda odd.
This line in my dmesg for boot changed, even with the last time I had flashed it when it looped on the animation, this line was the same as the original kernel (changed from 4 to 2 not 2 to 1). Only thing I've noticed so far.
<6>[ 72.812347] mdp4_overlay_mdp_perf_upd mdp bw is changed [1] from 2 to 1
However, I'm headed to bed. I'll look for the mutex dmesg entries throughout tomorrow and post anything I get. However, I hadn't been having any bsods. So I can't gurantee any useful info.
The Following User Says Thank You to Yoinx For This Useful Post:
Device(s): VS920, TF700T, Droid X, Droid Inc, T-bolt <-smashed into a million bits, Galaxy Note 2 :)
Carrier: Verizon
Thanks: 70
Thanked 38 Times in 26 Posts
Quote:
Originally Posted by tdm
I fixed two mutex issues in the MDP (display) code. If anyone is running into bsod issues, please try these. All I ask is to report back on whether the fix worked, and to check if either of the below messages shows up in the kernel log (dmesg) at least a couple times per day. Simply run "adb shell dmesg | grep mutex" from your computer, or open a shell and run "dmesg | grep mutex" directly on the phone.
Diagnostic messages:
mdp4_overlay_play: mutex double unlock avoided
mdp4_dtv_overlay: spurious mutex_unlock avoided
I put the new boot.img on the phone. The phone had CM10 rc3 and I had not seen the black screen failure. I did have the black screen issue right after I put CM10 rc1 on the phone. rc3 has been on the phone since the day you put the link and I've not had any problems. booted right up first time.
I am not seeing any mutex lines in dmesg. I will keep checking.
Thank you TDM for all you do!
Last edited by hayneskr; February 5th, 2013 at 12:45 AM.
The Following User Says Thank You to hayneskr For This Useful Post:
Device(s): Galaxy Nexus, LG Spectrum, Droid Charge
Carrier: Verizon
Thanks: 8
Thanked 3 Times in 3 Posts
Quote:
Originally Posted by Yoinx
It doesn't list vs920. Are you indicating that this should flash on the spectrum?
*TDM beat me to it*
I'm currently running a 4.2 rom on my Gnex and I think the 4.1 roms I used actually ran better, so I wouldn't be in any huge rush to get on 4.2 on the Spectrum, personally. 4.2 still seems to have some inherent bugs of its own.
Yeah. I've never really understood the cross device portability. Thought/hoped maybe since it had been posted here it might be cross flashable or something.
Glad i asked first
Also. Still no mutex entries in my dmesg yet since last night on Aokp41 rc3 with your test kernel.
Sent from my VS920 4G using Tapatalk 2
The Following User Says Thank You to Yoinx For This Useful Post:
Thanks for getting this together mr tdm. I look forward to trying it out.
Everything seems to be working, except GPS of course -- I can't test that because I want to keep my phone pristine for investigation:
* wifi works
* bluetooth seems to work but I didn't pair with anything yet
* radio seems to work, in that it says no sim, no service, roaming which is normal for me
* front and back cameras work
Here's the plan:
I'll do a rebuild in the morning and toss out CM10.1 in a new thread. I'm dropping i_skt and i_lgu for the moment until I can get some things ironed out with the users on xda, so the build will be only for i_atnt and i_vzw.
Next I'll move on to AOKP42 and see about setting up nightly builds.
I will plan on continuing to support CM10.0/AOKP41 and continuing to fix bugs in both. The BSOD and reboot issues and bluetooth mac are on top of my todo list.
Everything seems to be working, except GPS of course -- I can't test that because I want to keep my phone pristine for investigation:
* wifi works
* bluetooth seems to work but I didn't pair with anything yet
* radio seems to work, in that it says no sim, no service, roaming which is normal for me
* front and back cameras work
Here's the plan:
I'll do a rebuild in the morning and toss out CM10.1 in a new thread. I'm dropping i_skt and i_lgu for the moment until I can get some things ironed out with the users on xda, so the build will be only for i_atnt and i_vzw.
Next I'll move on to AOKP42 and see about setting up nightly builds.
I will plan on continuing to support CM10.0/AOKP41 and continuing to fix bugs in both. The BSOD and reboot issues and bluetooth mac are on top of my todo list.
Roger that.
Thanks for the feedback. I'm very much looking forward to trying it out.
Been thinking... I'd kinda like to get official cm support for the spectrum. I think the two things that will hold it back are the gps and Bluetooth mac. So after I get cm10.1 spun up, those will likely be my next targets.
Just an update. 2 days with the test kernel for that mutex thing SBD still not a single entry in dmesg for it. Been checking a few times a day and nothing at all has shown.
Sent from my VS920 4G using Tapatalk 2
The Following User Says Thank You to Yoinx For This Useful Post:
I had a random reboot today then the bootanimation hung rotating the phone to landscape would show half the homescreen and half the bootanimation, going back would just be the full bootanimation. I pulled everything in /data/local/tmp but wasn't sure what I should send/post as I assume that it would be the .1/.2/.3 of each file. However, I noticed that in logcat_radio at least it contained some personal info (phone number at least jumped out at me), I don't really care about people getting my phone number. I just always worry about phone cloning and such.
Which files are actually needed to help you diagnose this?
*edit*
Actually, just went ahead and PMd you a link to a zip with all the files.
Last edited by Yoinx; February 7th, 2013 at 04:23 PM.
Rebuilt AOSP41 today. Here are the issues that I found immediately:
* Camera apk didn't build for some reason (?)
* Front camera doesn't work (or at least it didn't in the last build)
* Don't want OpenWNN or PinyinIME
* Baseband version shows Unknown
Additionally reported by brianmaedche:
* Can't downloadsome apps from market (which ones?)
* Some setting missing in mobile network and phone testing menu (which?)
* No 4g
The Following 3 Users Say Thank You to tdm For This Useful Post:
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
Quote:
Originally Posted by tdm
Additionally reported by brianmaedche:
* Can't downloadsome apps from market (which ones?)
This has been an issue of the aokp for a while. I haven't been able to download BECU, wallbase, Truvia and many other apps. I get the 'incompatible' error.
However, if I have the app saved as a backup or the apk, I can still install it. The issue seems to be with the rom and the market.
The Following User Says Thank You to MrB206 For This Useful Post:
This has been an issue of the aokp for a while. I haven't been able to download BECU, wallbase, Truvia and many other apps. I get the 'incompatible' error.
However, if I have the app saved as a backup or the apk, I can still install it. The issue seems to be with the rom and the market.
Hmmm that's strange (and a nice coincidence). I use becu and wallbase myself, so I'll definitely check those next time I test a clean install.
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
Right? I've only encountered it with aokp... Clean flash, dirty, restore... Doesn't matter. The BECU error was the most frustrating, but I archive it, so I just installed from sd.
This has been an issue of the aokp for a while. I haven't been able to download BECU, wallbase, Truvia and many other apps. I get the 'incompatible' error.
However, if I have the app saved as a backup or the apk, I can still install it. The issue seems to be with the rom and the market.
I've never heard of those apps before. However I just went ahead and grabbed becu and wall base off the market with no issues running aokp41 rc3. Only mods to it are tdm's test kernel from a page or two back and I have an time 4.2 keyboard (plus whatever framework is included four that in the flashable zip).
Can't really explain it but it doesn't seem to be an incompatibility between aokp and those apps through the play store app... assuming I got the right two apps. A banking app and a wallpaper app.
A you trying to get them through the play store website and getting the "incompatible" message?
Yes. Try to get them and I get this message. Ironically, this app is currently installed when I see this:
Just checked, mine does not say that. I'm on a nitro, running aokp41 rc4 with dpi=280.
If you have changed your dpi, you might want to go through the dpi steps again. Otherwise, I guess I'll try to remember to check the spectrum tomorrow.
This has been an issue of the aokp for a while. I haven't been able to download BECU, wallbase, Truvia and many other apps. I get the 'incompatible' error.
However, if I have the app saved as a backup or the apk, I can still install it. The issue seems to be with the rom and the market.
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
Quote:
Originally Posted by tdm
Just checked, mine does not say that. I'm on a nitro, running aokp41 rc4 with dpi=280.
If you have changed your dpi, you might want to go through the dpi steps again. Otherwise, I guess I'll try to remember to check the spectrum tomorrow.
I changed my dpi, but I did the same on cm10 and cm10.1 but didn't encounter this.
Wiping data doesn't clear dpi changes if you did them to the default.prop on the /system partition. You'd need to revert the file or re-install the OS to fix that.
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
I don't know what default prop is. I used the aokp rom control to change the dpi. That might be the issue... I guess it depends on how that rom control app alters settings.
Last edited by MrB206; February 8th, 2013 at 09:48 AM.
I don't know what default prop is. I used the aokp rom control to change the dpi. That might be the issue... I guess it depends on how that rom control app alters settings.
Yes aokp rom control modifies build.prop. Go through the steps there that tell you how to fix app compatibility issues. Your default dpi is 320.
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
That did the trick.
But why is this issue only with aokp? I don't have this problem with any other jb rom on the spectrum. I even alter the build prop in cm10 and cm10.1 to change the lcd to 280.
Last edited by MrB206; February 8th, 2013 at 12:10 PM.
But why is this issue only with aokp? I don't have this problem with any other jb rom on the spectrum. I even alter the build prop in cm10 and cm10.1 to change the lcd to 280.
I'm not a dpi guru. I only recently started altering mine. But whatever the issue is, it's in Google's proprietary stuff, so we may never get a good explanation.
Device(s): LG Spectrum, ASUS Transformer 300T, Droid 2 Global, Droid X
Carrier: Not Provided
Thanks: 12
Thanked 252 Times in 224 Posts
Re: [ROM] Quattrimus JB (CM10, AOKP41)
If I had to guess, it has more to do with the cherry pick nature of aokp, than anything else. I bet something narses up a setting that doesn't happen with cm.
I am trying to convince my wife to let me put this ROM on her Spectrum. I have a problem that she needs to have her Facebook contacts show in her regular contact list. I told her it does and I put all of the settings on mine and they do not show up. I have been tracking this thread and I am currently on AOKP41 RC1. I know that her phone will work better on this ROM but that was a deal breaker for her. Has anyone else seen this issue or know how to resolve it?
I say it again this time. This ROM rocks and I keep telling my wife she needs me to put it on her phone.
I will be moving my phone to RC4 soon.
Any help with this would be GREATLY appreciated.
Thanks.
Side note:
TDM hope your son is recovered from the surgery. Thank you for all you have already done on the ROM.
The Following User Says Thank You to lildrmr93 For This Useful Post:
Device(s): LG Vortex CM7
Samsung Galaxy S CM7
Kindle Fire CM9 ICS
LG Spectrum rooted
Carrier: Not Provided
Thanks: 126
Thanked 119 Times in 58 Posts
Quote:
Originally Posted by lildrmr93
I am trying to convince my wife to let me put this ROM on her Spectrum. I have a problem that she needs to have her Facebook contacts show in her regular contact list. I told her it does and I put all of the settings on mine and they do not show up. I have been tracking this thread and I am currently on AOKP41 RC1. I know that her phone will work better on this ROM but that was a deal breaker for her. Has anyone else seen this issue or know how to resolve it?
I say it again this time. This ROM rocks and I keep telling my wife she needs me to put it on her phone.
I will be moving my phone to RC4 soon.
Any help with this would be GREATLY appreciated.
Thanks.
Side note:
TDM hope your son is recovered from the surgery. Thank you for all you have already done on the ROM.
For her facebook contacts to sync and be added to her regular contacts in your settings menu go to accounts and her facebook should show there. if not add her facebook account by clicking add account. once its added click on it and it should open another screen where you can check a box to sync its contacts to your phone.
I am trying to convince my wife to let me put this ROM on her Spectrum. I have a problem that she needs to have her Facebook contacts show in her regular contact list. I told her it does and I put all of the settings on mine and they do not show up. I have been tracking this thread and I am currently on AOKP41 RC1. I know that her phone will work better on this ROM but that was a deal breaker for her. Has anyone else seen this issue or know how to resolve it?
I say it again this time. This ROM rocks and I keep telling my wife she needs me to put it on her phone.
I will be moving my phone to RC4 soon.
Any help with this would be GREATLY appreciated.
Thanks.
Side note:
TDM hope your son is recovered from the surgery. Thank you for all you have already done on the ROM.
Could be an issue with the default contacts app. If your sync settings are all correct you could try a different contact app perhaps. Personally i always use go dialer which has its contacts app built in
545Likes
