1690 replies to this topic

[TheGreenJester]

ccooluke, on 06 May 2011 - 10:34 PM, said:

so i flashed 7.0.3 then nightly 65... .phone force closing like a mofo. Trying to go back to 7.0.3 right now. How will I be able to transition back to the nightlies safely?

7.0.3 is based on 2.3.3 while the nightlies are based on 2.3.4. You will probably have to wipe the cache at the very least if you are switching back and forth.

[Elroy944]

ccooluke, on 06 May 2011 - 10:34 PM, said:

so i flashed 7.0.3 then nightly 65... .phone force closing like a mofo. Trying to go back to 7.0.3 right now. How will I be able to transition back to the nightlies safely?

best thing is make backup with titanium backup (apps, settings whatever you like)after that do a full wipe and install the 65 nightly.

it works great on my desire z with latest pershoot kernel (2.6.32.39) and latest radio rom (12.52. 60.25_26.08.04.30)

[trickinit]

Elroy944, on 07 May 2011 - 12:10 AM, said:

best thing is make backup with titanium backup (apps, settings whatever you like)after that do a full wipe and install the 65 nightly.

it works great on my desire z with latest pershoot kernel (2.6.32.39) and latest radio rom (12.52. 60.25_26.08.04.30)

I'm having the same issue. I was on nightly 64, then flashed 7.0.3 (before Cyanogen warned not to) and started getting incessant force closes (com.android.media). Unfortunately, I didn't make a nandroid before flashing it. So I tried flashing nightly 65 and started getting a worse one: "com.android.phone" kept force closing, and my phone wouldn't connect to the cell network at all. So I backed up all of my apps through Titanium Backup and did a full wipe (/data, /cache, /system, /dalvik-cache) and tried flashing nightly 65 again, but with the same result. So I ended up flashing my most recent nandroid backup from a few weeks ago. It worked for a few hours, but now the "com.android.media" force close has started again. I can reboot my phone, which makes it stop for a little while, but then it eventually starts up again.

I don't understand why this would still be lingering after a full wipe, and restoring back to a good backup. The only thing I can think of is that I restored my apps through Titanium Backup, but I don't see how they could have anything to do with it. Does anyone have any ideas? I know I can't be the only one running into this.

[yokonunz]

How is 66?

[Sangruria]

trickinit, on 07 May 2011 - 07:21 AM, said:

I'm having the same issue. I was on nightly 64, then flashed 7.0.3 (before Cyanogen warned not to) and started getting incessant force closes (com.android.media). Unfortunately, I didn't make a nandroid before flashing it. So I tried flashing nightly 65 and started getting a worse one: "com.android.phone" kept force closing, and my phone wouldn't connect to the cell network at all. So I backed up all of my apps through Titanium Backup and did a full wipe (/data, /cache, /system, /dalvik-cache) and tried flashing nightly 65 again, but with the same result. So I ended up flashing my most recent nandroid backup from a few weeks ago. It worked for a few hours, but now the "com.android.media" force close has started again. I can reboot my phone, which makes it stop for a little while, but then it eventually starts up again.

I don't understand why this would still be lingering after a full wipe, and restoring back to a good backup. The only thing I can think of is that I restored my apps through Titanium Backup, but I don't see how they could have anything to do with it. Does anyone have any ideas? I know I can't be the only one running into this.

I was having same issue. Here is what i did. Formatted cache, data , system using clockworkmod and flashed nightly 66. Looks good so far. even my GPS is working perfectly now.

[jdnh]

I posted about this earlier, yes flashing 7.0.3 over an existing rom breaks things.  fix permissions did nothing, i tried clearing dalvik cache and it did nothing.  I wound up doing a full wipe, including cache, everything except the sd card then flashed 7.0.3 and have no issues.   Of course come to find out the new nightlies use 2.3.4 android and i wanted to flash those, so i might hold off a little bit but if not i will report back if it breaks things or not.

trickinit, on 07 May 2011 - 07:21 AM, said:

I'm having the same issue. I was on nightly 64, then flashed 7.0.3 (before Cyanogen warned not to) and started getting incessant force closes (com.android.media). Unfortunately, I didn't make a nandroid before flashing it. So I tried flashing nightly 65 and started getting a worse one: "com.android.phone" kept force closing, and my phone wouldn't connect to the cell network at all. So I backed up all of my apps through Titanium Backup and did a full wipe (/data, /cache, /system, /dalvik-cache) and tried flashing nightly 65 again, but with the same result. So I ended up flashing my most recent nandroid backup from a few weeks ago. It worked for a few hours, but now the "com.android.media" force close has started again. I can reboot my phone, which makes it stop for a little while, but then it eventually starts up again.

I don't understand why this would still be lingering after a full wipe, and restoring back to a good backup. The only thing I can think of is that I restored my apps through Titanium Backup, but I don't see how they could have anything to do with it. Does anyone have any ideas? I know I can't be the only one running into this.

[chris2busy]

Hello..I am having horrific wifi drain issues..I suspect that it is because of N mode being enabled in the rom..How can i disable it/find out if it is?

[-Stevo-]

Restoring all of your system app data (not to be focused with your normal app data) with titanium will cause issues. If there is an option to not restore system app settings, use it and restore the rest of your non-system apps.

[jdnh]

Update,  I flashed nightly 66 over 7.0.3 and all went ok... latest radio, all seems to work...  battery life is good, however, keep in mind battery calibration can be an issue.   You should charge it overnight (or an extra hour or two after it reads 100%) , then clear battery stats and let it drain until it shuts itself off (dont charge it or connect it to usb during this time), then plug it in and charge it up (you can power it on and use the phone while it's charging)...   this routine added a lot of battery life for me.

so i guess it's downgrading 2.3.4 to 2.3.3 that breaks things.

[jdnh]

heres a new one, flash videos dont display, flash works, i see the ad popups and video controls in flash apps, i hear the audio, but i cant see the video at all, its like that layer is not displaying?

[GinoA]

Nightly #66 seemed to break the theme chooser again.  Looks just like when it broke a couple weeks ago.

Went back to #65.  Will try #67 later today.

[GinoA]

GinoA, on 09 May 2011 - 03:19 PM, said:

Nightly #66 seemed to break the theme chooser again.  Looks just like when it broke a couple weeks ago.

Went back to #65.  Will try #67 later today.

#67 also had a borked theme-chooser.  Will try the brand-new #70 later.

[merdely]

GinoA, on 09 May 2011 - 08:19 PM, said:

#67 also had a borked theme-chooser.  Will try the brand-new #70 later.

Given that 66, 67, and 70 are all about 10 MB less than previous nightlies, 70 is borked too.

[biscuitownz]

Nightly 71 seemed to have fixed my 720p video playback, now it doesn't skip ( FINALLY ). Will test more tomorrow

[nemiro]

Is anyone else having strange problems with the touchscreen in the last few nightlies? Sometimes it will allow me to turn on/off the speaker in the lockscreen, but not allow me to unlock the screen.  Then it will do random weird things if I do get in.  Pushing the power button, and then waking it up again usually frees it up, but it still may have other random strange problems.  I can reboot, and it may be gone, or it may still be there.  Any suggestions?

[GinoA]

biscuitownz, on 10 May 2011 - 06:42 AM, said:

Nightly 71 seemed to have fixed my 720p video playback, now it doesn't skip ( FINALLY ). Will test more tomorrow

#71 still has the theme chooser borked.  Can't stand that green default theme.  May downgrade to #65 again later.

[warbird87]

Im still running #42... having a hard time not flashing a new nightly but it doesnt seem like everything is working to well and i have had no issues with the one i am using now...

[93sleeper]

Anybody get the gtalk video or voice chat to work on 2.3.4 yet

[TheGreenJester]

warbird87, on 10 May 2011 - 06:52 PM, said:

Im still running #42... having a hard time not flashing a new nightly but it doesnt seem like everything is working to well and i have had no issues with the one i am using now...

#42 is based on Android 2.3.3 and is a few nightlies before CM 7.0.2, the latest stable release. The later nighlies are based on 2.3.4 which is still getting some bugfixes. I understand the "if it ain't broke don't fix it" mentality, but I would recommend updating to 7.0.2. The fixes in between #42 and stable were fixes after all.

[TroyAG1]

#72 notifications sounds play until the notification bar is touched/moved won't play the one I select either just some wood block sounding noise.