Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

[CM7] Discussion of Nightlies

keyboard nightly build

  • Please log in to reply
1779 replies to this topic

#41 siraltus

siraltus
  • Members
  • 22 posts
  • Device Model:|1|
  • MOD Version:CM 5.0.8
  • Recovery Image:Amon_RA

Posted 24 February 2011 - 06:30 AM

View Postnickcv, on 24 February 2011 - 05:28 AM, said:

Installed nightly 6, and as soon as it finishes booting, I get a FC for the status bar. Trying to open any of the options under settings results in an FC as well.

Same here. Reverted back to #5.

#42 Beafy

Beafy
  • Members
  • 16 posts
  • Country:us
  • Device Model:Nook Color
  • MOD Version:CM7 nightly
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 07:27 AM

View PostMightytalldude, on 24 February 2011 - 06:23 AM, said:

I also confirm on nightly #6 the status bar force close error message. Flashed back to 5.

Same thing here.

I have a problem not being able to associate with one of my two wireless routers.  logcat says authentication is timing out.  There one major difference between my router that works and the one that doesn't.  The one that doesn't work is wireless N and the one that does is G.  All my other wireless devices work OK with both.

Also, for people with SoftKeys FC problem, if it gets into a FC cycle, go back to the home screen and launch it manually and the FC cycle will stop.  Dunno what triggers it.

Edited by Beafy, 24 February 2011 - 07:37 AM.


#43 newellj79

newellj79
  • Members
  • 130 posts
  • Country:us
  • Device Model:nook color
  • MOD Version:cm7 nightly 8
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 12:50 PM

I confirm status bar force close immediately with nightly 6. Reverted back to nightly 5 and everything is ok.

#44 newellj79

newellj79
  • Members
  • 130 posts
  • Country:us
  • Device Model:nook color
  • MOD Version:cm7 nightly 8
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 12:53 PM

View Postkage87z, on 24 February 2011 - 05:22 AM, said:

So, when we update, like 5 to 6, do we need to do a complete wipe? (System, data, cache?)


NO! Don't wipe anything. Just flash over.

#45 Mightytalldude

Mightytalldude
  • Members
  • 158 posts
  • Twitter:Mightytalldude
  • Country:us
  • Device Model:Nexus One & Nook Color
  • MOD Version:CM7 nightlies
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 02:04 PM

Looks like nightly 7 will require a wipe. Post #236. http://forum.xda-dev...960542&page=24.
Make a TB backup, and save your launcher settings and that'll get things back quickly after the wipe.

Edited by Mightytalldude, 24 February 2011 - 02:10 PM.


#46 Cypher2

Cypher2
  • Donators
  • 45 posts
  • Twitter:nathaneltitane
  • LocationMontreal, Canada
  • Country:ca
  • Device Model:SG Note I717 - ASUS TF700
  • MOD Version:CM10 (Nightlies)
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 02:28 PM

And that's why I don't want to play around flashing my nook around this time :)

#47 Aixelsyd

Aixelsyd
  • Members
  • 38 posts
  • Device Model:|3|
  • MOD Version:5.0.7.1
  • Recovery Image:Cyanogen

Posted 24 February 2011 - 02:59 PM

View PostPeterL, on 24 February 2011 - 04:07 AM, said:

Anyone have a method to get adb shell up and running of sdcard?  The old days, the recovery image had a shell builtin.  

I have a copy of root downloaded from link above.  Thanks.

Also, I followed instructions off http://briefmobile.c...nook-color.  He swears wiping /boot isn't an issue. UGH!
Wiping /boot is for sure and issue. I had the same thing happen the first time I loaded CM7 as I wiped /boot on accident. Luckily I was using a bootable CWM sdcard and made a backup of the stock Nook software that I had rooted before trying out CM7. SO it was a simple fix to toss teh sdcard in boot to CWR and then restore.

#48 Local Stain

Local Stain

    Yell Fire!

  • Donators
  • 82 posts
  • Twitter:LocalStain
  • LocationA very small island, Planet Earth
  • Country:us
  • Device Model:HTC Aria
  • MOD Version:cm 7 RC
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 04:35 PM

I am having some of the same issues mentioned here,status bar etc. Can someone tell me if I if I revert back to my 5 image can I flash this evenings nightly(7)over the top of the 5 with the proper wipes, etc. Just not sure if I should revert or hold out and deal with the minor issues I am having until tonight. Thanks in advance for any help.

#49 canyoufindben

canyoufindben
  • Members
  • 25 posts
  • Country:us
  • Device Model:Motorola Droid
  • MOD Version:CM7 Nightlies
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 04:43 PM

View PostPeterL, on 24 February 2011 - 04:07 AM, said:

Anyone have a method to get adb shell up and running of sdcard?  The old days, the recovery image had a shell builtin.  

I have a copy of root downloaded from link above.  Thanks.

Also, I followed instructions off http://briefmobile.c...nook-color.  He swears wiping /boot isn't an issue. UGH!


DO NOT FORMAT BOOT WITH CWM 3.0.0.6
Don't misconstrue, I'm not yelling at you, I'm making a point. You will need to flash 3.0.0.5 and format your /boot /system /data /cache You can use this one with just the cwm http://forum.xda-dev...ad.php?t=922870

Next burn a nookie froyo do the sdcard and boot from it the sdcard.
Drop these files to the sdcard, both system.img and boot.img from http://forum.xda-dev...ad.php?t=919353
You can follow those directions to with adb to flash your boot and system back to factory 1.0.1

It's my understanding that this happened because CM7 is still using the .29 kernel that comes with the stock /boot. So once you get your NC booting back to Factory 1.0.1 you can begin again from there.

I've also made this mistake. You can recover from this, but you have to have adb setup to do it. I've tried to use the flashable zip file that's on XDA for this, but it just doesn't seem to work after formating /boot with 3.0.0.6

Next time, do not format /boot, I know its a common practice with some other NookColor ROMS, but it is unnecessary with properly written scripts. With 3.0.0.6 only format /system /data and /cache.

Hope that helps you. It's the steps I took to restoring my NC to factory and then back to CM7 nightlies.

#50 kage87z

kage87z
  • Members
  • 18 posts
  • Country:us
  • Device Model:D1/NC
  • MOD Version:CM7 Nightlies
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 06:27 PM

View Postnewellj79, on 24 February 2011 - 12:53 PM, said:

NO! Don't wipe anything. Just flash over.

Coolio.  Fortunately, I didn't do anything.. still on 5... waiting for the dust to settle on 6, as I will on 7.

But thanks for the clarification.

View PostMightytalldude, on 24 February 2011 - 02:04 PM, said:

Looks like nightly 7 will require a wipe. Post #236. http://forum.xda-dev...960542&page=24.
Make a TB backup, and save your launcher settings and that'll get things back quickly after the wipe.

Will this be needed for everyone... or just those running 6?

Edited by kage87z, 24 February 2011 - 06:33 PM.


#51 newellj79

newellj79
  • Members
  • 130 posts
  • Country:us
  • Device Model:nook color
  • MOD Version:cm7 nightly 8
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 07:49 PM

I read the post. I'm wondering if he means a full wipe (format system, data and cache)? Please let me know so I'm ready to go first thing in the morning.

#52 Mightytalldude

Mightytalldude
  • Members
  • 158 posts
  • Twitter:Mightytalldude
  • Country:us
  • Device Model:Nexus One & Nook Color
  • MOD Version:CM7 nightlies
  • Recovery Image:ClockworkMod

Posted 24 February 2011 - 07:51 PM

I'm guessing it means a full wipe reading his description, i.e. system / data / cache but not boot.

Edited by Mightytalldude, 24 February 2011 - 09:33 PM.


#53 nullexe

nullexe
  • Members
  • 1 posts
  • Device Model:Nexus One
  • MOD Version:7
  • Recovery Image:ClockworkMod

Posted 25 February 2011 - 02:40 AM

View PostBeafy, on 24 February 2011 - 07:27 AM, said:


I have a problem not being able to associate with one of my two wireless routers.  logcat says authentication is timing out.  There one major difference between my router that works and the one that doesn't.  The one that doesn't work is wireless N and the one that does is G.  All my other wireless devices work OK with both.


I had the same issue.  Check if your N router is in mixed mode or if it is to low or high in the spectrum.

#54 canyoufindben

canyoufindben
  • Members
  • 25 posts
  • Country:us
  • Device Model:Motorola Droid
  • MOD Version:CM7 Nightlies
  • Recovery Image:ClockworkMod

Posted 25 February 2011 - 04:03 AM

Is anyone else having an issue with Pandora on nightly #5? It just force closes on me.

#55 Krazypoloc

Krazypoloc
  • Members
  • 31 posts
  • Device Model:Droid2, NOOK Color
  • MOD Version:Nightly V<>
  • Recovery Image:ClockworkMod

Posted 25 February 2011 - 04:24 AM

Just got a NC today.  Lots of issues with V6...trying V5 now. FC when launching WIFI settings. Unlock slider only half screen size. I haven't read full change logs yet but I'm sure these issues are documented.

**Update**

Went to V5 and its running flawlessly. None of the issues I was having with V6 are occurring.

Edited by Krazypoloc, 25 February 2011 - 05:17 AM.


#56 siraltus

siraltus
  • Members
  • 22 posts
  • Device Model:|1|
  • MOD Version:CM 5.0.8
  • Recovery Image:Amon_RA

Posted 25 February 2011 - 04:32 AM

View Postcanyoufindben, on 25 February 2011 - 04:03 AM, said:

Is anyone else having an issue with Pandora on nightly #5? It just force closes on me.

Pandora's been FCing since daily #1. All we can do is wait until CM devs address this problem.

#57 Shadowswittness

Shadowswittness
  • Members
  • 6 posts
  • Device Model:Nook Color
  • MOD Version:CM7 nightlie 5
  • Recovery Image:Cyanogen

Posted 25 February 2011 - 06:16 AM

Any news on when 7 will post ?

#58 jimmy87lee

jimmy87lee
  • Members
  • 4 posts
  • Device Model:Verizon Droid
  • MOD Version:6.1.2
  • Recovery Image:Cyanogen

Posted 25 February 2011 - 08:13 AM

View PostShadowswittness, on 25 February 2011 - 06:16 AM, said:

Any news on when 7 will post ?

like.. now?

Edited by jimmy87lee, 25 February 2011 - 08:13 AM.


#59 Beafy

Beafy
  • Members
  • 16 posts
  • Country:us
  • Device Model:Nook Color
  • MOD Version:CM7 nightly
  • Recovery Image:ClockworkMod

Posted 25 February 2011 - 09:56 AM

Nightly 7 was a complete non-starter for me.  Wireless settings under Settings FC with a NullPointerException every time.  Yes, I did a complete wipe of system/data/cache.  Twice.  Only if you are lucky enough to set up a wireless connection during setup do you ever get one at all.

Also, I remembered from another thread that someone was going to be changing encore from mdpi to hdpi.  However, Android System Info was reporting a density of 1.25, which is really wacky!  It's supposed to be something like 1 (mdpi), 1.5 (hdpi), or .75 (ldpi).  From an app developer's perspective, this is highly exceptional and unexpected.  Perhaps related, some things show up fuzzy on-screen.

Reverting to nightly 5.

#60 jimmy87lee

jimmy87lee
  • Members
  • 4 posts
  • Device Model:Verizon Droid
  • MOD Version:6.1.2
  • Recovery Image:Cyanogen

Posted 25 February 2011 - 10:44 AM

View PostBeafy, on 25 February 2011 - 09:56 AM, said:

Nightly 7 was a complete non-starter for me.  Wireless settings under Settings FC with a NullPointerException every time.  Yes, I did a complete wipe of system/data/cache.  Twice.  Only if you are lucky enough to set up a wireless connection during setup do you ever get one at all.

Also, I remembered from another thread that someone was going to be changing encore from mdpi to hdpi.  However, Android System Info was reporting a density of 1.25, which is really wacky!  It's supposed to be something like 1 (mdpi), 1.5 (hdpi), or .75 (ldpi).  From an app developer's perspective, this is highly exceptional and unexpected.  Perhaps related, some things show up fuzzy on-screen.

Reverting to nightly 5.

Here's a workaround for the wifi: http://forum.xda-dev...3&postcount=268