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

Root condemned cm7

paleodust said:
http://pastebin.com/embed_js.php?i=4TzhHPVt
Click to expand...
It does show a kernel panic near the end of that log(shown below) but I'm not really sure why it's happening. I might try flashing Condemned tomorrow to see if I can get bluetooth to crash.

Code: 
<4>[ 3091.149688] ------------[ cut here ]------------
<4>[ 3091.150451] WARNING: at kernel/workqueue.c:364 flush_cpu_workqueue+0x40/0xc4()
<4>[ 3091.151672] Modules linked in: wlan
<4>[ 3091.153411] [<c036d88c>] (dump_stack+0x0/0x14) from [<c0063d3c>] (warn_slowpath+0x70/0x8c)
<4>[ 3091.156372] [<c0063ccc>] (warn_slowpath+0x0/0x8c) from [<c007514c>] (flush_cpu_workqueue+0x40/0xc4)
<4>[ 3091.158721]  r3:d44c1800 r2:00000000
<4>[ 3091.161865]  r7:d44c36c8 r6:c0359218 r5:d44cc000 r4:d44c36c0
<4>[ 3091.164703] [<c007510c>] (flush_cpu_workqueue+0x0/0xc4) from [<c0075b14>] (flush_workqueue+0x24/0x30)
<4>[ 3091.167633]  r4:d44c36e0
<4>[ 3091.168762] [<c0075af0>] (flush_workqueue+0x0/0x30) from [<c0359234>] (add_conn+0x1c/0x48)
<4>[ 3091.173980]  r5:d44cc000 r4:c430f6a8
<4>[ 3091.176818] [<c0359218>] (add_conn+0x0/0x48) from [<c0075598>] (worker_thread+0x194/0x238)
<4>[ 3091.203582]  r5:d44cc000 r4:d44c36c0
<4>[ 3091.209442] [<c0075404>] (worker_thread+0x0/0x238) from [<c007956c>] (kthread+0x58/0x94)
<4>[ 3091.211029] [<c0079514>] (kthread+0x0/0x94) from [<c0067318>] (do_exit+0x0/0x7f8)
<4>[ 3091.212646]  r7:00000000 r6:00000000 r5:00000000 r4:00000000
<4>[ 3091.216064] ---[ end trace c1770ed3ad733118 ]---
 
aphlatoon said:
I accidently deleted browser.apk while in the terminal window, now the browser won't come up. I tried copying the browser.apk file from the original build, moved it back to /system/app/ directory but it still won't work, any ideas how to bring it back up?
Click to expand...
You might just need to set the permissions. So place the Browser.apk in /system/app/ then in terminal emulator run these commands:
Code: 
#get root
su

#set permissions to rw-r--r-- (644)
chmod 644 /system/app/Browser.apk

#set owner:group to root:root (0:0)
chown 0:0 /system/app/Browser.apk
See if that works and if not, try rebooting to recovery, wiping cache + dalvik-cache, and fix permissions(fix uid mismatches under other for Amon_RA recovery), then reboot.
 
doogald said:
Is that settings->call settings->vibrate on answer?

Even if it's not, this is something I would turn on anyway. This always lets me know that the call is going through and I can now put the phone to my head, rather than dial, hold to my head, get nothing but silence and finally look at the display, only to discover that it never dialed because I have a poor signal or something.
Click to expand...

No it's when you place the call. It's the feature you want that I can't stand
 
I had a reboot as well just after pairing my bluetooth headset for the first time after flashing V18.1 S2H this morning.
 
I don't use BT much, but I paired my headset and drove for a half hour with no trouble at all. V18.1, S2H. (Where I think I am staying for good, actually.)
 
doogald said:
(Where I think I am staying for good, actually.)
Click to expand...

+1

So far I'm very impressed with this ROM, it's snappy and smooth.
Everything works so far. Even did a short drive with navigation (updated to 5.9) and no reboots.


Had a few initial troubles after flashing this morning (after a full wipe) with restoring apps (not from TB, just letting Google do its thing).

Got a the dreaded "insufficient space" error on about 10 of them which resolved themselves when I manually re-downloaded them later.
I also flashed Cache2Cache, but that should be ok, correct?

Yahoo email also gave me a hiccup trying to set it up through the standard app, but that went away after a few tries.
Shazam and FastWeb Installer (AppBrain) didn't want to download due to a "package file is invalid" error and when I finally got them to download they just would FC immediately, but again after a few tries and reboots they now work flawlessly.
I don't think my Eris could run any better than it is now.

Thanks so much for all your work CS! :)
 
paleodust said:
Any luck finding anything yet?
Click to expand...

No.. so far I haven't found anything that looks like it would cause BT issues and I tested the Eris with my BT piece this weekend and had no problems either... I'll keep trying to reproduce it though. Are you oc'ing at all or anything?
 
Nope. I haven't changed anything that would affect it (that I can think of). It doesn't cause problems with my wife's Eris on V17.
 
paleodust said:
Nope. I haven't changed anything that would affect it (that I can think of). It doesn't cause problems with my wife's Eris on V17.
Click to expand...

Just a friendly suggestion: have you considered going back to V17 in order to potentially isolate this to the ROM? In other words, if installing V17 from scratch induces the same problem, then perhaps V18 is not the issue.

And, if it does fix the problem, since you say that you are miserable without working BT, wouldn't that be better, rather than struggling with V18?
 
doogald said:
Just a friendly suggestion: have you considered going back to V17 in order to potentially isolate this to the ROM? In other words, if installing V17 from scratch induces the same problem, then perhaps V18 is not the issue.

And, if it does fix the problem, since you say that you are miserable without working BT, wouldn't that be better, rather than struggling with V18?
Click to expand...

I may have to do something like that but I was hoping for a fix from CS or something since V18.1 is otherwise great and the new ROM dance is a big pain.

It wouldn't have anything to do with running low on SD space, would it?
 
I have v17 running on mine. There's no problem when turning on the bluetooth but when I try to pair it, it reboots.
Also, I used to connect the usb as an mp3 player in the car, now it gives me "usb error". I have tried it with both debugging enabled and disabled.
 
paleodust said:
I may have to do something like that but I was hoping for a fix from CS or something since V18.1 is otherwise great and the new ROM dance is a big pain.
Click to expand...

This is one reason why I keep a Nandroid around for at least a week after upgrading a ROM until I am absolutely sure that I will not need it. In fact, I still have a few for xtrSENSE and GSB that I am pretty sure I will not go back to. You never know.

Still, with Titanium Backup, it takes me about a half hour to load a new ROM these days. I always start up without signing in to my Google account, so the ROM will not waste time reinstalling my apps, then go into the market, install Titanium, restart to Recovery to flash xtrcache2cache, restart and use Titanium to restore my apps (which is the part that takes the longest). I do a separate restore of my WiFi access points, go into the settings app to reset my settings, go into a few apps to make sure that they are all set (and I also restore my last 100 texts from SMS Backup+), and I'm ready to go.
 
doogald said:
I do a separate restore of my WiFi access points, go into the settings app to reset my settings, go into a few apps to make sure that they are all set.
Click to expand...

How do you do a separate restore of WiFi?

What settings app are you referring to for resetting your settings?
 
paleodust said:
How do you do a separate restore of WiFi?
Click to expand...

Titanium. It's the one system app that I restore, but only for CM7 ROMs. So, going from V17 to V18, I just restore the WiFi settings. I wouldn't restore it to xtrSENSE, however.

Rather than a batch restore, where it won't show up, I go into the normal backup/restore. I have WiFi settings set to backup every night, so they are always refreshed.

(I just checked - it's called "WiFi Access Points".)

So, after I batch restore the missing apps, I then manually restore WiFi Access Points.

What settings app are you referring to for resetting your settings?
Click to expand...

From home, manu->settings. Just the normal settings app. I go into all of the things manually that I change from stock - turn off animations, change display time out to 30 seconds, change VM to Google Voice, change the CM settings to the ones that I want - this all takes a few minutes tops.
 
Ok, hadn't used Bluetooth since I flashed last week and paired my headset (reboot after pairing), but today when I tried to use BT, the phone connected fine to the headset (got the short confirmation beep), but 1 or 2 seconds after the phone promptly rebooted.
I tried that about 3 times with the same results. :(

All my settings are how they came with the ROM, did a clean install after a full wipe.

Everything else is running beautiful so far, even nagivation (5.9) has been stable for a few trips without any reboots at all.
 
So a couple are having by problems and some aren't. You guys using 18 or 18.1 and stripped or vanilla... Trying to narrow things down. I have 18.1 vanilla on this Eris.
 
CondemnedSoul said:
So a couple are having by problems and some aren't. You guys using 18 or 18.1 and stripped or vanilla... Trying to narrow things down. I have 18.1 vanilla on this Eris.
Click to expand...

I just did a clean wipe and re-installed V18.1, with the same problem. That was even before installing any apps. :(

I've had the same bluetooth reset issue on both V18 and V18.1. V17 worked just fine and my wife's phone still runs just fine with the same exact bluetooth device on 17.

I've only been using S2H since V17.

Could you please drop V17 S2H in the box for me just in case?
 
paleodust said:
I just did a clean wipe and re-installed V18.1, with the same problem. That was even before installing any apps. :(

I've had the same bluetooth reset issue on both V18 and V18.1. V17 worked just fine and my wife's phone still runs just fine with the same exact bluetooth device on 17.

I've only been using S2H since V17.

Could you please drop V17 S2H in the box for me just in case?
Click to expand...

Both versions of 17 are there
 
You must log in or register to reply here.
Back
Top Bottom