• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10, AOKP41)

death2all110 said:
1. This has been covered:
Incredible 2 Owners Receiving Text Messages from VZWNMN? Here is How to Stop Them – Droid Life

Basically has to do with Contact Management/Backup Assistant/BA Plus

2. Have you tried wiping caches/data? What rom are you coming from. More info is required

3. Have been a few reports? I thought this was reported in the tracker? Please confirm and post.

4. Probably setcpu. Try to replicate/see Number 2?
Click to expand...

1. Ah, ok. I'll look into that, thanks.

2.
Well, if you are talking about a wipe that's different from the CWM wipe that I did prior to installing the rom, then no. Although there was this one odd error during the factory reset, but it didn't seem to affect the wiping process, but what am I to know. Something about a volume being inaccessible or something. I don't remember.

I am coming from a rooted and bootloader unlocked ICS Rom.

I could see about getting a logcat on it if you want. My adb is a bit rusty though, so results may vary.

3.
Yes, I wasn't looking at the CM_AOKP issues, it's logged under "Gets stuck in charging animation when charged while phone is off", which is basically what happened in a nutshell. My apologies.

4. The issue was part of 3. After reading the reports given by users I concur with all of them, with the "zombie" charging without being charged and the stuck charging animation. The 2 are part of one issue on the Bug Tracker.
 
Cartoonman said:
So far I'm really liking the rom. I just have some minor issues to report (and I have checked the bug tracker beforehand)

LG Spectrum
CW 10.0


1.
http://i.imgur.com/MqYdKrz.jpg

I seem to be getting these odd text messages from Verizon, which never happened before. Something with the radio I guess?

2.
http://i.imgur.com/KCfZLVb.jpg

When I click on Mobile Networks, it just crashes. Not a serious crash, but nevertheless, it does not proceed.

http://i.imgur.com/xYxfTi5.jpg

3.
Some odd voodoo stuff was going on when I unplugged the phone (when it was off) from the charger. When I pressed the power button it seemed to be somehow stuck on "charging mode" even though it was disconnected from the charger. The LG screen would show up, then black, then LG again, then the charging battery icon would appear, and it would display as if it was charging the phone.

After removing the battery however it seemed to remedy the issue.

4.
Upon booting, apparently the CyanogenMod boot animation never got an "exit" signal upon the phone entering the lock screen, so I was getting haptic feedback from what was supposed to be the lock screen, but all I could see was the CyanogenMod boot animation, that was still going on. Pressing the power button once had the same effect as closing the screen/locking the phone, and pressing it again turned the screen back on, but the CyanogenMod animation was still on-going.
After a restart however the issue went away. This issue may have been related to my setCPU setting of I believe 4xxMhz minimum and on ondemand governour, but I would have to replicate it to be sure.
Click to expand...

As to 1. go to vzw.com/sync and delete the accounts.
 
only issues I have with CM10 RC1 has been that the phone likes to random reboot a couple times a day. so far only once has it restarted afterwards without assistance. It hangs on the CM logo while coming back up, did it twice yesterday and again this morning. Each time was while I was not using the phone for several hours and it was either sitting on a table (ie flat wood surface), or in my pocket (this morning, having not used the phone in 9+ hours, not even turning the screen on).

plugging the phone into my computer and sending a an adb reboot recovery command gets it to restart. pressing the power button (during the CM logo loop) just turns the screen off/on has no other effect. Wiping cache and dalvik cache gets the phone to boot (causing a "Android is upgrading" message while it counts my apps and does what ever it does at that time), but does not provide any DATA, mobile or wifi. Trying a reboot or shutdown command after that and the phone fails to restart, it just sits there with the "shutting down" or "restarting" message on the screen (waited 45 minutes one time).

last kmsg from this morning shows this at the end

Code: 
[ 1860.102661] ================tcp_nuke_addr================
[ 1860.102996] ================tcp_nuke_addr================
[ 1860.103057]    family 10 
[ 1860.107666] tcp_nuke_addr : sk :  0xda42c5e0 
[ 1860.108428] tcp_nuke_addr : sk :  0xd6f5b5c0 
[ 1860.108551] tcp_nuke_addr : sk :  0xd6f5eb80 
[ 1860.108978] tcp_nuke_addr : sk :  0xda42db60 
[ 1860.109222] tcp_nuke_addr : sk :  0xd6f59ae0 
[ 1860.111053] tcp_nuke_addr : sk :  0xd6f5f0e0 
[ 1860.123840] tcp_nuke_addr : sk :  0xd6f5f640 
[ 1860.130859] tcp_nuke_addr : sk :  0xda42a040 
[ 1860.131408] tcp_nuke_addr : sk :  0xd6f58ac0 
[ 1860.133544] tcp_nuke_addr : sk :  0xd6f5d0a0 
[ 1860.140869] tcp_nuke_addr : sk :  0xd6f5c5e0 
[ 1860.141082] ================tcp_nuke_addr================
[ 1862.984130] msm8x60_multi_sdio_slot_status_irq: MDM2AP_SYNC Status = 0
[ 1862.984191] msm8x60_multi_sdio_slot_status_irq: calling sdc2_status_notify_cb
[ 1862.984344] msm8x60_multi_sdio_slot_status_irq: calling sdc5_status_notify_cb
[ 1863.004974] Restarting system with command ''.
[ 1863.005432] set_dload_mode : 0
[ 1863.005737] restart time : 2013-01-18 03:43:27.266848426 UTC
[ 1863.006225] Going down for restart now

previous last kmsg looked a little different
Code: 
[ 1218.946716] Trip point triggered by current temperature (50 degrees) measured by Temperature-Sensor 0
[ 1220.400390] SysRq : Emergency Remount R/O
[ 1220.435882] EXT4-fs (mmcblk0p28): re-mounted. Opts: (null)
[ 1220.481018] EXT4-fs (mmcblk0p20): re-mounted. Opts: (null)
[ 1220.498046] EXT4-fs (mmcblk0p27): re-mounted. Opts: (null)
[ 1220.513519] EXT4-fs (mmcblk0p29): re-mounted. Opts: (null)
[ 1220.525695] EXT4-fs (mmcblk0p23): re-mounted. Opts: (null)
[ 1220.537689] EXT4-fs (mmcblk0p22): re-mounted. Opts: (null)
[ 1220.537902] Emergency Remount complete
[ 1220.606628] sys_reboot: sys_reboot is called from android
[ 1220.606658] sys_reboot: reboot cmd is 19088743
[ 1220.607849] sdio_alInitiating msm_sdio_al_shutdown...
[ 1220.607879] sdio_al: sdio_al_close_all_channels
[ 1220.607879] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_RMNT
[ 1220.647430] sdio_al:channel_close: Ch SDIO_RMNT closed successfully
[ 1220.647430] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_ULS
[ 1220.647766] sdio_al:channel_close: Ch SDIO_ULS closed successfully
[ 1220.647766] sdio_al: sdio_al_modem_reset_operations
[ 1220.647796] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 1
[ 1220.647796] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 1
[ 1220.648010] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 1
[ 1220.650146] sdio_al: channel_close: Invalid device state 2
[ 1220.650970] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 1
[ 1220.651000] sdio_al: sdio_al_close_all_channels
[ 1220.651000] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_RPC
[ 1220.651428] sdio_al:channel_close: Ch SDIO_RPC closed successfully
[ 1220.651428] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_QMI
[ 1220.651763] sdio_al:channel_close: Ch SDIO_QMI closed successfully
[ 1220.651763] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_DIAG
[ 1220.652099] sdio_al:channel_close: Ch SDIO_DIAG closed successfully
[ 1220.652130] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_SMEM
[ 1220.652435] sdio_al:channel_close: Ch SDIO_SMEM closed successfully
[ 1220.652465] sdio_al: sdio_al_modem_reset_operations
[ 1220.652465] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 4
[ 1220.652496] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 4
[ 1220.657073] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 4
[ 1220.662719] rpcrouter_sdio_remote_remove Called
[ 1220.663513] rpcrouter_sdio_remote_remove Completed
[ 1220.673248] sdio_al: channel_close: Invalid device state 2
[ 1220.673339] sdio_smem_unregister_client: sdio_close error (-19)
[ 1220.706146] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 4
[ 1220.706176] sdio_al: msm_sdio_al_shutdown: msm_sdio_al_shutdown complete.
[ 1223.459594] msm8x60_multi_sdio_slot_status_irq: MDM2AP_SYNC Status = 0
[ 1223.459777] msm8x60_multi_sdio_slot_status_irq: calling sdc2_status_notify_cb
[ 1223.459869] msm8x60_multi_sdio_slot_status_irq: calling sdc5_status_notify_cb
[ 1223.480255] sdio_al:sdio_al_sdio_remove for card 1
[ 1223.480316] sdio_al:sdio_al_sdio_remove: ask_reading_mailbox for card 1
[ 1223.480468] sdio_al: sdio_al_sdio_remove: Notifying SDIO clients for card 1
[ 1223.480529] sdio_al: sdio_al_sdio_remove: Finished Notifying SDIO clients for card 1
[ 1223.480743] sdio_al:sdio_al_sdio_remove: vote for sleep for card 1
[ 1223.480926] sdio_al:sdio_al_sdio_remove: flush_workqueue for card 1
[ 1223.481170] sdio_al:sdio_al_sdio_remove: sdio card 1 removed.
[ 1223.482818] mmc1: card 0002 removed
[ 1223.624633] sdio_al:sdio_al_sdio_remove for card 4
[ 1223.624725] sdio_al:sdio_al_sdio_remove: ask_reading_mailbox for card 4
[ 1223.624816] sdio_al: sdio_al_sdio_remove: Notifying SDIO clients for card 4
[ 1223.624938] sdio_al: sdio_al_sdio_remove: Finished Notifying SDIO clients for card 4
[ 1223.625091] sdio_al:sdio_al_sdio_remove: vote for sleep for card 4
[ 1223.625274] sdio_al:sdio_al_sdio_remove: flush_workqueue for card 4
[ 1223.625518] sdio_al:sdio_al_sdio_remove: sdio card 4 removed.
[ 1223.627227] mmc4: card 0002 removed
[ 1223.636718] Restarting system.
[ 1223.637329] set_dload_mode : 0
[ 1223.637634] restart time : 2013-01-18 04:12:20.109396270 UTC
[ 1223.637908] Going down for restart now

If I wait long enough on the CM logo (during start up) I get the same as mentioned above by cartoonman. I hear my notification sound go off as the alert for my new email (that I have not read nor acknowledged yet today) goes off, and touching the screen makes it vibrate as if It was going to the unlock screen (but only once), and pressing the volume buttons causes the volume up or down sounds to play, and the power button switches the screen on and off like it would if the phone were working. but the CM logo never goes away.
 
I did a wipedata/factory reset today and this is what the error said:

E: format_volume: make_extf4fs failed on /dev/block/mmcblklp2

but then it just goes on to format /sdcard/.android_secure. . .

Is that bad?
 
Cartoonman said:
4.
Upon booting, apparently the CyanogenMod boot animation never got an "exit" signal upon the phone entering the lock screen, so I was getting haptic feedback from what was supposed to be the lock screen, but all I could see was the CyanogenMod boot animation, that was still going on. Pressing the power button once had the same effect as closing the screen/locking the phone, and pressing it again turned the screen back on, but the CyanogenMod animation was still on-going.
After a restart however the issue went away. This issue may have been related to my setCPU setting of I believe 4xxMhz minimum and on ondemand governour, but I would have to replicate it to be sure.
Click to expand...

We've had the same thing happen on both our spectrums, I don't use setCPU, CPU is set at 1512/192, Interactive, Deadline, same as it has been for the last several CM10 versions, so it seems to be specific to RC1.
 
Cartoonman said:
4.
Upon booting, apparently the CyanogenMod boot animation never got an "exit" signal upon the phone entering the lock screen, so I was getting haptic feedback from what was supposed to be the lock screen, but all I could see was the CyanogenMod boot animation, that was still going on. Pressing the power button once had the same effect as closing the screen/locking the phone, and pressing it again turned the screen back on, but the CyanogenMod animation was still on-going.
After a restart however the issue went away. This issue may have been related to my setCPU setting of I believe 4xxMhz minimum and on ondemand governour, but I would have to replicate it to be sure.
Click to expand...

I just had this happen as well after testing to see if the camera reboot issue still happens (it does). After the reboot the CM boot animation never left, tho I was getting haptic and audio feedback from the phone... Only thing I have had happen on RC1.
 
IMUcarmen said:
I'm having some weird boot anomalies as well.
Click to expand...

Is it anyway similar to this?

Upon booting, apparently the CyanogenMod boot animation never got an "exit" signal upon the phone entering the lock screen, so I was getting haptic feedback from what was supposed to be the lock screen, but all I could see was the CyanogenMod boot animation, that was still going on. Pressing the power button once had the same effect as closing the screen/locking the phone, and pressing it again turned the screen back on, but the CyanogenMod animation was still on-going.
Click to expand...

If so, it's already logged under CM_AOKP in the bug tracker.




reeseboy said:
I just had this happen as well after testing to see if the camera reboot issue still happens (it does). After the reboot the CM boot animation never left, tho I was getting haptic and audio feedback from the phone... Only thing I have had happen on RC1.
Click to expand...

Hmm, did you happen to charge the phone during this incident or was it completely unplugged when this happened?
 
I'll have to look into what stops the boot animation and why it's not happening sometimes.

In other news...

I got the device repos updated and pushed the upcoming kernel fix for the Bluetooth crash also (the one I thought I had fixed in rc1 but didn't). I'll send a pull request to CM so official builds can have some of my fixes, but they will probably ignore it. I've never had much luck getting their attention.

My 7yo got the spectrum to reboot this morning playing bad piggies for about 20min. It was a user space reboot command, not a crash. I'll be adding more diagnostic code to try to find the root cause of this issue.
 
tdm said:
I'll have to look into what stops the boot animation and why it's not happening sometimes.

In other news...

I got the device repos updated and pushed the upcoming kernel fix for the Bluetooth crash also (the one I thought I had fixed in rc1 but didn't). I'll send a pull request to CM so official builds can have some of my fixes, but they will probably ignore it. I've never had much luck getting their attention.

My 7yo got the spectrum to reboot this morning playing bad piggies for about 20min. It was a user space reboot command, not a crash. I'll be adding more diagnostic code to try to find the root cause of this issue.
Click to expand...

got a temp solution for the boot animation loop for everyone, it sucks, but it works.

1. plug your phone into a computer with adb you know works with your phone (in my case, ONLY my linux OS on my external hdd for my laptop)
2. adb shell "ps |grep -i animation"
you should get something like this:

graphics 440 1 80612 36292 ffffffff 40067cd4 S /system/bin/bootanimation

3. adb shell "kill -9 440"
where "440" = the number in your line from the previous step (the first number after "graphics")

4. magically the boot animation will go away and your unlock screen will be there...


for troubleshooting for TDM, when the looping occurs, if you place your finger where the unlock should be and don't let up, your phone vibrates like the lock screen normally would, you can then slide your finger to what ever unlock position you want (default is up for google search/now, and right to just unlock) and it will do it. if you receive a phone call, email, or text you will hear the ringtone/notification sound while the boot animation runs.

still no data, wifi or 1x/3g/4g

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

interesting, the battery was running very low and did not seem to be charging while plugged into my computer (20 minutes and no change in the charge level), so shut the phone off and left it plugged into my laptop. for no reason I can figure out, I typed in adb devices on my laptop and the phone showed up. powered off and usb charging only I can access my phone via adb, a little odd in my mind, but hey, I'll take it.
 
finndo77 said:
got a temp solution for the boot animation loop for everyone, it sucks, but it works.

1. plug your phone into a computer with adb you know works with your phone (in my case, ONLY my linux OS on my external hdd for my laptop)
2. adb shell "ps |grep -i animation"
you should get something like this:

graphics 440 1 80612 36292 ffffffff 40067cd4 S /system/bin/bootanimation

3. adb shell "kill -9 440"
where "440" = the number in your line from the previous step (the first number after "graphics")

4. magically the boot animation will go away and your unlock screen will be there...


for troubleshooting for TDM, when the looping occurs, if you place your finger where the unlock should be and don't let up, your phone vibrates like the lock screen normally would, you can then slide your finger to what ever unlock position you want (default is up for google search/now, and right to just unlock) and it will do it. if you receive a phone call, email, or text you will hear the ringtone/notification sound while the boot animation runs.

still no data, wifi or 1x/3g/4g
Click to expand...

Is that for when the boot animation IS stuck, and to do the adb during the "stuckage", or is that a patch that keeps the issue from happening again?


interesting, the battery was running very low and did not seem to be charging while plugged into my computer (20 minutes and no change in the charge level), so shut the phone off and left it plugged into my laptop. for no reason I can figure out, I typed in adb devices on my laptop and the phone showed up. powered off and usb charging only I can access my phone via adb, a little odd in my mind, but hey, I'll take it.
Click to expand...

This is probablly related to the logged request "Request "fast charge" mode on LG Spectrum when attached to proper power source" but not sure.
 
I did that while the animation was looping, actually it had been looping for 3.5+ hours, as my "linux laptop" is my work win7 laptop and I had to wait until after work to reboot with the external HDD.

so while the looping is going on, strange enough though that adb stopped working as soon as I killed the boot animation loop. (the device was not reporting being in debug mode)

and I think it pretty darn cool that I can adb my phone while it is powered off and consider it an awesome bonus to the greatness of our devs. :)

in case anyone is wondering, I did provide logcats to TDM of bootup through the looping boot animation.
 
In the data/local/tmp folder, should I assume that last_ksmg.9 is the most recent and .0 is the oldest? Or is it the other way around? Also, sidenote, what's the significance of February 1970, or why are they dated from then?

Got a random freeze. Black screen. Not sure if the phone was on or off, had to do a battery pull to get it back on.

Here's last_ksmg.9 from right after I rebooted: http://pastebin.com/KJD3LrW1

And here's last_ksmg.0 from right after I rebooted in case I'm wrong about the file order: http://pastebin.com/GNLRA9DB
 
zacanger said:
In the data/local/tmp folder, should I assume that last_ksmg.9 is the most recent and .0 is the oldest? Or is it the other way around? Also, sidenote, what's the significance of February 1970, or why are they dated from then?

Got a random freeze. Black screen. Not sure if the phone was on or off, had to do a battery pull to get it back on.

Here's last_ksmg.9 from right after I rebooted: http://pastebin.com/KJD3LrW1

And here's last_ksmg.0 from right after I rebooted in case I'm wrong about the file order: http://pastebin.com/GNLRA9DB
Click to expand...

Zero is the newest. Looks like another user space reboot request.

I should have done better diagnostics for that later this week.
 
Cartoonman said:
I did a wipedata/factory reset today and this is what the error said:

E: format_volume: make_extf4fs failed on /dev/block/mmcblklp2

but then it just goes on to format /sdcard/.android_secure. . .

Is that bad?
Click to expand...
Which recovery are you using when you get that error?
 
Cartoonman said:
I did a wipedata/factory reset today and this is what the error said:

E: format_volume: make_extf4fs failed on /dev/block/mmcblklp2

but then it just goes on to format /sdcard/.android_secure. . .

Is that bad?
Click to expand...

I believe this is for sdext support. Nobody uses that with modern phones. So the error is really benign and not applicable.
 
Neph81 said:
Which recovery are you using when you get that error?
Click to expand...
CWM 6.0.1.1 standard. I just wanted to make sure it wasn't anything serious like a system partition or anything. I'm horrible when it comes to linux permissions. It does that error everytime I do a datawipe. My ICS backup isn't exactly the cleanest ROM, it's got some strange stuff going on, from a adware virus to frozen apps and such. I'm just happy to breathe some fresh air in this technically unofficial release.

Is it just me or is the logcat in CM 10.0 restricted to su? I wanted to get a logcat of the Systeminfo crash but I can't seem to access the logcat via app, and can only seem to get it through terminal emulator and running as #su.
 
For the boot anim not stopping, I found going into cwm and clearing cache and dalvik is a quick fix also. I had to get my phone back up while at work and tried it and it worked. Don't know if it was a fluke, or if it is something stored in either cache or dalvik making the boot anim not go off.
 
tdm said:
I was hoping to have that done this week but I had some issues getting out rc1 and I'm getting busy at my real job and I have a 3yo son who just had surgery. So it might be another week or two. Enjoy 4.1 it's the best Rom I've made to date. :)
Click to expand...


TDM hope your son is recovering well.

I just put AOKP RC1 on. I am soo loving this phone now. I am about to swipe the wife's phone to put her on it cause she is still 100% stock.

I am very thankful for ALL of the devs who worked on this. I was happy to see other devs pick up and go when TDM was 'afk' if you will.

Keep up the great work!!!
 
  • Like
Reactions: tdm
eclipsed039 said:
hey TDM, off topic, how's your son?
Click to expand...

Thanks for asking, he's doing as well as can be expected.

He had surgery for strabismus. The recovery is going well -- his pain is receding and he's been pretty much back to his normal self for a couple days.

The doctor told us up front that the success rate was 80% so we were rather nervous about it, but there doesn't seem to be any good alternative. We won't know for sure whether the surgery was a complete success until the follow-up visit in 3 weeks, but it looks very promising.

On the other hand, me and my wife have had the flu for the last couple days. The boys have already had it and recovered. Chasing four boys running around full-tilt while you have the flu is quite exhausting. I came to work today to get some rest... :p
 
You must log in or register to reply here.
Back
Top Bottom