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

Root [BETA]Cyanogen!! Landed!!! :) Go get it![Updated 7/12/2011]

Can anyone confirm if this new "camera/youtube/netflix..." fix straightens up the annoying and random?:

Code:
"The process android.process.media has stopped unexpectedly. Please try again" [Force Close]
 
I am trying to figure out the database writes task. That used to be one of the longest parts of the Quadrant benchmark, and I have trouble with the fact that installing a new ROM cuts that task by an order of magnitude. I'm wondering if it is not executing correctly.

Looks like my new refurb overclocks better than my old phone; my old phone wouldn't run for very long at anything over 1.1ghz / stock voltage. I've run about 15 Quadrant benchmarks in a row on 1.3 and it hasn't locked up.
 
Can anyone confirm if this new "camera/youtube/netflix..." fix straightens up the annoying and random?:

Code:
"The process android.process.media has stopped unexpectedly. Please try again" [Force Close]

I have never had this issue, but I don't have the issue now either if that helps.
 
My quadrant hit 2000 without any over clocking, not that it means much when all is said and done especially with the ability to "cheat" quadrant.

Overall I think my phone is working much faster, which is good enough for me.
 
Camera fix works on number 6, yeah. I'm running it fine right now.

EDIT: The CRT and Cyanogen Mod text zip worked for me when I flashed them.

Yep I found a new Zip that worked for me as well.

Does anyone's actual camera button work?

My camera button doesn't work, but using the screen button works fine.

No mine does not work either, but like you said the screen button works fine.
 
I've been going back n forth trying this out but currently back on Apex. Would a simple method to going back to CM7 be, Sbf back to froyo then flash to the current nightly - would that work or do I have to start from scratch and update to the current nightly?
 
My quadrant hit 2000 without any over clocking, not that it means much when all is said and done especially with the ability to "cheat" quadrant.

Overall I think my phone is working much faster, which is good enough for me.

My results are 100% legit....I get between 2200 and 2300 without overclocking at all.
 
I've been going back n forth trying this out but currently back on Apex. Would a simple method to going back to CM7 be, Sbf back to froyo then flash to the current nightly - would that work or do I have to start from scratch and update to the current nightly?

You should be able to SBF back to FroYo and then just flash the new nightly and be just fine. I have personally not done this but seen many post from people who have with no issues.
 
So.............

I may have fixed the network location issue. But since it's a framework issue, you'll lose the CRT fix. I'm gonna try to recompile the CRT framework to try and have both.

Can someone point me to the current CRT zip file?

Thanks
 
I could use a little help. I attempted to use the camera fix files this morning on Nightly #6. Rebooted, and was only able to get to stock recovery. So I SBF'd, reinstalled nightly 6, and then re-copied over the camera fix files, this time making sure to set 744 permissions on the files. Rebooted, and its still not going back into CM4DX. Not sure if I need to wipe Davlik, but without access to ClockworkMod recovery, I don't know how to do that. Any tips before I SBF again???

Just to clarify, when I reboot, it automatically goes to the little green android with the white/yellow ! triangle.
 
I could use a little help. I attempted to use the camera fix files this morning on Nightly #6. Rebooted, and was only able to get to stock recovery. So I SBF'd, reinstalled nightly 6, and then re-copied over the camera fix files, this time making sure to set 744 permissions on the files. Rebooted, and its still not going back into CM4DX. Not sure if I need to wipe Davlik, but without access to ClockworkMod recovery, I don't know how to do that. Any tips before I SBF again???

Just to clarify, when I reboot, it automatically goes to the little green android with the white/yellow ! triangle.


Hit the search button, then the power button on top
 
Hit the search button, then the power button on top
Still seems to go to stock recovery... can't get it to go anywhere else...

I just don't understand how I'm getting stuck like this twice. Seems like people in the other thread are just copying the files without worrying about permissions, and it works just great for them. I'm not a moron, just cursed I guess.

I used the "Mount System" app to change system to R/W, then using Yaff's file explorer to rename the originals, then copy the new files, mounted system back as R/o, then rebooted... am I not supposed to leave the backup files in /system ?
 
Anyone know if someone is accepting bug submissions for these builds?

I get a kernel panic after listening to my music for a while. I've pulled two of the /data/dontpanic logs but frankly, I'm no guru at this.

I'm just not sure if the devs are in "we have enough bugs to work on" mode :D
 
Anyone know if someone is accepting bug submissions for these builds?

I get a kernel panic after listening to my music for a while. I've pulled two of the /data/dontpanic logs but frankly, I'm no guru at this.

I'm just not sure if the devs are in "we have enough bugs to work on" mode :D

Could you post the logs? I am on rooted stock .596 and get kernel panics using the stock GB app. I was going to flash CM to see if that fixed the kernel panics.

I don't know much about anything, but I would like to look at them.
 
I ran the camera fix in zip file form in cwr

Yeah, I'm grabbing that .zip file as well. There are 2 sets of files... one that is just designed to be extracted and manually copied, and the other that is designed to be flashed/updated within recovery. I'll try the update/recovery version and see how that works.
 
Could you post the logs? I am on rooted stock .596 and get kernel panics using the stock GB app. I was going to flash CM to see if that fixed the kernel panics.

I don't know much about anything, but I would like to look at them.

Sure. Here you go. They're named <date> <incremented number> <filename> - the incremented number is just 1 for both of these because I only got one yesterday and one this morning.
 

Attachments

Back
Top Bottom