[ROM][GINGERBREAD] CyanogenMOD 7 Nightly Builds.

[ssethv]

Are you using the stock radio? I get much lower speeds, and if there was something easy to fix it, that'd be nice.

First off. I was running off wifi at my house secondly, even using 3g I get at least 2-4mbps DL speed and a little less upload speed. I am using 2.15.00.07.28 radio....

 

[rpz3.14]

First off. I was running off wifi at my house secondly, even using 3g I get at least 2-4mbps DL speed and a little less upload speed. I am using 2.15.00.07.28 radio....

That makes sense. I am using the same radio, but typically get closer to 1 Mbps down and .5 Mbps up. Maybe I should have waited for the TB

 

[kaefbaml]

If you killed a 3500 in 5 hrs with only music playing from your SD card... then something else is going on. Some other app is running and sucking the battery. I don't listen to music on my DInc but I have taken 6 hr GPS nav trips after using the phone all day and only had to plug in for the last hour.

Did you look at the battery stats in Spare Parts and see what process was running the longest?

yeah man, it said my display was eating it up... i did put the cyanogen mod nexus live paper today, rather last night, so maybe thats what did it, and im thinking thats what made my phone glitch out this morning too while trying to unlock.

 

[kaefbaml]

the most speed i get on my 3g is about 1-2mb average. feels like people are getting a lot faster speeds than me

 

[phillydog#CB]

Repeated FC issue

Seems like I go through this pattern with FC issues and CM7. If I'm lucky, I may go 2 days without a FC but when they start to happen it's a rapidly snowballing effect. It may start with FC in browser, but then appears in K9, Google framework, Handcent, etc within a couple minutes depending on my activity. If I even try to reninstall a backup from ROM manager I get an error message, although I can always manually reboot into recovery and restore.

I did a complete wipe and clean install of RC2 on 3/18 which last a 4 day record until 3/22. I made a 3/20 backup which I restored on 3/22. This lasted until 3/24 when I started the rapid FC domino effect and had to restore. I made a backup on 3/24 before the crash but found that this only lasted about 12 hours. I just loaded my CM backup I made on 3/20. I have tried to fix permissions but it seems like this has little effect other than severely slowing down the OS. Did I miss something?

 

[kaefbaml]

Seems like I go through this pattern with FC issues and CM7. If I'm lucky, I may go 2 days without a FC but when they start to happen it's a rapidly snowballing effect. It may start with FC in browser, but then appears in K9, Google framework, Handcent, etc within a couple minutes depending on my activity. If I even try to reninstall a backup from ROM manager I get an error message, although I can always manually reboot into recovery and restore.

I did a complete wipe and clean install of RC2 on 3/18 which last a 4 day record until 3/22. I made a 3/20 backup which I restored on 3/22. This lasted until 3/24 when I started the rapid FC domino effect and had to restore. I made a backup on 3/24 before the crash but found that this only lasted about 12 hours. I just loaded my CM backup I made on 3/20. I have tried to fix permissions but it seems like this has little effect other than severely slowing down the OS. Did I miss something?

im referring to the part i put in bold.


and yes you did, the fact that the real GB isnt realeasd for our Dincs yet.

I do love cyanogen and it feels really open, like i can change anything i want. but having that advantage in the morning waking up, is more of a hassle then knowing i have a stock rom thats isnt going to force close me or lose something like 720p just cuz we want this version NOW. lol its a toss up. but im about 55% / 45% on going back to stock sence. One more malfunction which i know is going to happen. I think i can wait untill the OTA

this was a fun run, and im sure ill load cyanogen7 once it is stable and have my wonderful camera in full affect!

ill always be rooted and awaiting..

 

[rpz3.14]

this was a fun run, and im sure ill load cyanogen7 once it is stable and have my wonderful camera in full affect!

ill always be rooted and awaiting..

I haven't had too much bad luck with CM7, and have settled on 27 until the rest of the community finds the next big thing for me, but it would be interesting to take a look at CM6 to see what a "stable" rom is for the CM team and how different it is from the nightlies.

 

[ssethv]

Seems like I go through this pattern with FC issues and CM7. If I'm lucky, I may go 2 days without a FC but when they start to happen it's a rapidly snowballing effect. It may start with FC in browser, but then appears in K9, Google framework, Handcent, etc within a couple minutes depending on my activity. If I even try to reninstall a backup from ROM manager I get an error message, although I can always manually reboot into recovery and restore.

I did a complete wipe and clean install of RC2 on 3/18 which last a 4 day record until 3/22. I made a 3/20 backup which I restored on 3/22. This lasted until 3/24 when I started the rapid FC domino effect and had to restore. I made a backup on 3/24 before the crash but found that this only lasted about 12 hours. I just loaded my CM backup I made on 3/20. I have tried to fix permissions but it seems like this has little effect other than severely slowing down the OS. Did I miss something?

are you using any kernels? if so, are you overclocking or underclocking? I have never had any type of issues like that except with build 30 so I went back to 28, and they were still not that bad... I don't use any task killers either... and I NEVER use ClockWorkMod (except to make a nandroid once in a while) ....
I always DL the CM7 releases from the mirror site on my PC, Not ClockWorkMod

1. I make nandroid (clockwork or manually)
2. go into manual recovery
3. Wipe cache -> then wipe dalvik cache
4. install zip (nightly) from sd
5. install zip (Kernel) from sd.
6. Reboot phone.
I see you already tried fixing permissions from manual recovery right?

 

[PvilleComp]

Edited for not posting after 3rd drink rule

 

[ssethv]

Edited for not posting after 3rd drink rule

Nice... so I take it your night is going well?

 

[ssethv]

SO glad tapatalk is back up and working now... I almost went to rehab

 

[kaefbaml]

Wait a sec.... when I dl a new nightly i have to the flash the kernel again? If so fail on my part
.. crap

Android, the best community. Sent using tapatalk!

 

[PvilleComp]

Depends on your definition of well!

The night's not over yet and the rules can change on drink 6 LOL

 

[BSG75]

I had those cascading FCs today. DLed #28 and did a full wipe and install. Everything seems to be working reasonably well so far.

I also have thought about going back to Sense (Skyraider) for good cameras. I think I need to be able to touch-to-focus and shoot quality video. Flashing roms is the beauty of Android, right?

 

[ssethv]

Wait a sec.... when I dl a new nightly i have to the flash the kernel again? If so fail on my part
.. crap

Android, the best community. Sent using tapatalk!

Yes (Im 99% sure, I always do and have been told to do it)... just follow my instructions exactly and youll be good to go or re-read the OP (first page of this thread)... well.. here it is WORD FOR WORD on page 1.

FLASH INSTRUCTIONS
THIS IS NOT THE PLACE TO ASK HOW TO FLASH A ROM OR KERNEL. IF YOU DO NOT KNOW HOW TO DO THIS, PLEASE GO READ SOME MORE BEFORE FLASHING.

If this is your first time flashing a CM7 Nightly, or you are returning from another ROM, you must absolutely do a full wipe before flashing. That means wiping your user data, cache, and Dalvik cache from recovery,
After wiping, go ahead and flash the most recent nightly. Once the installation is finished, you will need to flash the Google Apps(gapps). These consist of the Android Market, Gmail, Maps, etc.
If you choose to flash a custom kernel, it is advised to boot into the ROM once, and then wipe cache and Dalvik cache from recovery before flashing the kernel.

 

[ssethv]

Depends on your definition of well!

The night's not over yet and the rules can change on drink 6 LOL

ohhhh... so very true. Be safe bro!

 

[ssethv]

I had those cascading FCs today. DLed #28 and did a full wipe and install. Everything seems to be working reasonably well so far.

I also have thought about going back to Sense (Skyraider) for good cameras. I think I need to be able to touch-to-focus and shoot quality video. Flashing roms is the beauty of Android, right?

Same here, 28 seems to be the last stable nightly out there so far. anyway... My camera doesn't take the most clear shots like it used too on stock sense BUT it is still auto-focusing for me. overall the quality of video and camera isn't enough to push me out of CM7 yet.... but it is nice to know there is basic sense ROMs. and yes your right, Flashing ROM's is the beauty of android

 

[ssethv]

Hittin the sack yall... I work 9-5 at the funeral home doing NOTHING ALL DAY, so ill be online all day works for me, gettin paid to do this and pretty much what ever I want... Have a good night, be safe, don't be sorry

 

[kaefbaml]

Thanks seth

Android, the best community. Sent using tapatalk!

 

[phillydog#CB]

are you using any kernels? if so, are you overclocking or underclocking? I have never had any type of issues like that except with build 30 so I went back to 28, and they were still not that bad... I don't use any task killers either... and I NEVER use ClockWorkMod (except to make a nandroid once in a while) ....
I always DL the CM7 releases from the mirror site on my PC, Not ClockWorkMod

1. I make nandroid (clockwork or manually)
2. go into manual recovery
3. Wipe cache -> then wipe dalvik cache
4. install zip (nightly) from sd
5. install zip (Kernel) from sd.
6. Reboot phone.
I see you already tried fixing permissions from manual recovery right?

Thanks for your help.
I always wipe DCache. Doesn't seem like it makes a difference if I manually install or install from ROM Manager.....generally my experience is that if I have a bad install, it never boots correctly in the first place and that has only happened once. I tried fixing permissions and it seemed like it made no difference or slowed everything down to a crawl. However that was after the snowballing began. Lastly, I only use stock kernels.