yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ShermCraig:
Proposing a change

Instead of calling them nightly's, we need to come up with a new name. I'll start!

Occasionally's

Sporadically's

Anyone have any other ideas? Winner get's a free Nightly!

:rolleyes:
[Vibrant Android Development] mulcahyd:
Cyanoversion
[Vibrant Android Development] cashyftw:
Ohh ohh I have an idea, how about nightlies.
[Vibrant Android Development] mulcahyd:
11hrs 27min @ 45% . So far I've been running since in the morning.

On #26.
[Vibrant Android Development] Stevenjcarney:
Everyotherdailys?
[Vibrant Android Development] d_phekt:
Once in a while-eez
[Vibrant Android Development] T.C.P:
how about, everynight roms to flash?
[Vibrant Android Development] Henchmin:
Calm down people, its not like this is their job to make these roms for us. They do it on their own free will.

With that said, I'm so excited for a good, working GPS, CM7 rom that I'm pinching my **** to hold of the cum.
[Vibrant Android Development] defconoi:
ya know if you guys are impatient to try the new features/gps, why not compile it from source?
[Vibrant Android Development] Kaik541:
telling end users to be calm on xda, ha! you must be new here. expecting patience is like asking people not to post questions in the development section.
[Vibrant Android Development] dasunsrule32:
Lol
[Vibrant Android Development] ZeroIsntTheHero:
Or stop complaining and go back to froyo since it is so important. It is interesting to see how much some of you depend on having something to flash though. If you're that obsessed, flash back to one of the original builds and then go through 26 flashes to get back to present. If you can't wait without moaning and complaining, get out of your parents' basement for a few minutes, go outside and find something to do so that we don't have to listen to you. Or go post in General since obviously you have nothing to contribute to development.
[Vibrant Android Development] xriderx66:
Haha haven't had a good laugh on xda in a while!
[Vibrant Android Development] masr1979:
And this is what we call an overshare kids... can you say O-V-E-R-S-H-A-R-E?
[Vibrant Android Development] beren28:
When-you-least-expectedlies
[Vibrant Android Development] oblib__:
Ooooh, I think this is what I was looking for the first time I tried CM7. Would this be system wide volume normalization? I thought I saw some where that CM7 enabled this, but then I couldn't find it when I loaded Kang a week or two ago. If the "compression feature" is normalization, then that + GPS make CM7 a no-brainer.

Edit:

Hmm, does that mean things will only be normalized if the developer of the app tells the app to use this effect? That doesn't seem as nice as I was hoping...
[Vibrant Android Development] playonline53tms:
ETALESS's
[Vibrant Android Development] imitebewrong:
[YOUTUBE]h-LbvFckptY[/YOUTUBE]

10char
[Vibrant Android Development] bearsfan85:
I did this not that amusing lol, but seriously gps isnt that big of a deal its not like we are waiting for the phone to work, most of the people on xda who flash are men anyways and thus we dont need gps to get where we are going

btw dont expect to have gps working with this build http://review.cyanogenmod.com/#change,6205 they abandoned the change
[Vibrant Android Development] lightninbug:
Agreed! From one Chicago guy to another, Da Bears!!
[Vibrant Android Development] Cesarp 24:
I'm still checking every two houries.

Sent from My CM7 Monster
[Vibrant Android Development] rogerchew:
that's odd, just checked now it says it's "merged"

http://review.cyanogenmod.com/#change,6156
[Vibrant Android Development] bearsfan85:
i wish people could read dates and numbers

merged on the 16th abandoned on the 18th also 6205 > 6156
[Vibrant Android Development] hd2life:
Get #29 while it's hot, gps mystery soon to be solved.
[Vibrant Android Development] treyvaporizer:
Yayyyyy

Sent from SGH-T959 (CM7)
[Vibrant Android Development] awolbrin:
#29 is up!!!

#29 is up!!! downloading now

it has boot-loop :(
[Vibrant Android Development] kinzkarazy:
yesh build 29 is up about to flash it
[Vibrant Android Development] krazie1:
Whoa Nightly 29 is up can't wait to check it out. I'm curious about the GPS, or maybe the mute/unmute could be fixed.
[Vibrant Android Development] jimmynguyen91:
Dang... #29 gave me bootloop. Flashed from #24.
[Vibrant Android Development] Nabeel10:
GPS working? !!
[Vibrant Android Development] treyvaporizer:
My GPS doesn't seem to work, I'm gonna reboot and post answers.

Edit: no gps yet, but hey it's the first shot, it'll work eventually. Its turning on so that's a good sign! On a good note, this build is blazin' fast! Boots fast, no lag. Install on the GPS test app was instantaneous. Like 2 seconds from when I hit "ok". Too bad the test was negative :P. Oh well!

Sent from SGH-T959 (CM7)
[Vibrant Android Development] Cesarp 24:
Guys you don't have to do a data wipe. But wipe dalvik. And u can flash withought boot loop. I'm on 29 and threw Neo 7 on it right away smooth as always.

Btw **** GPS.

Sent from My CM7 Monster
[Vibrant Android Development] cashyftw:
GPS DOES NOT WORK, as mention earlier, the GPS issue has been abandon, read back 1 page.
[Vibrant Android Development] amwilliams9:
Booted just fine for me. However it did take much longer to fire up.
[Vibrant Android Development] zadk1el:
So far no issue... gps test doesnt show any satellite right now... flashed straight from 26 no bootloop.
[Vibrant Android Development] j.youngberg:
Wiped dalvik and cache. After flashing I got a boot loop after coming from 25.

Also, the guys at cm mentioned they're working on GPS so its not abandoned.
[Vibrant Android Development] bearsfan85:
I'm in a recovery loop (boots up into recovery, tries to flash a zip, fails and repeats), oh good fun at 3 am will post a link to the initial kernel via odin once I find it for anyone else who gets unlucky

http://download.microdoof.net/cmsgs/cm7-vibrant-initial-package.zip

might take a few times to get into recovery mode, so gl
[Vibrant Android Development] hd2life:
Yes bootlops ahead, wiped data and chase and it worked. GPS does show its working!! It shows the icon on top in maps, need to test outside for a fix.
[Vibrant Android Development] cal4877:
Well I hope is a major improvement on this one since it took so long
[Vibrant Android Development] kinzkarazy:
build 29 works good for me no bootloop problem flashed from 25 just remember to nandroid before flashing guys
[Vibrant Android Development] treyvaporizer:
Also the orientation is broken. But other than that, great build. Few kinks need to be worked out in GPS but it should be fine.

Sent from SGH-T959 (CM7)
[Vibrant Android Development] cashyftw:
Bootloop for me also, came from a nandroid (was currently on miui) just went to wipe cache, lets see what this does..
[Vibrant Android Development] d_phekt:
#29 flashed okay for me too. Only problem I'm having so far is Metamorph isn't working? Applying themes, but doesn't take after reboot.

Edit: Got it working... formatted system & cache, reflashed #29 & wiped dalvik cache... once again booted fine w/ no loops, but had to reinstall gapps.
[Vibrant Android Development] apollo15rover:
Go to settings, cyanogenmod, display...and under orientation make sure all boxes are checked.same happened to me and this fixed it.

GPS doesn't work for me..
[Vibrant Android Development] cashyftw:
Yep keep getting bootloops..
[Vibrant Android Development] iBustCh3rries:
no George St. Pierre on my phone either

Beamed fresh from Planet Awesome
[Vibrant Android Development] iBustCh3rries:
Edit: but I booted fine no bootloops I had trouble with getting it to connect to the network but it connected after a few minutes

Edit again: so didn't mean to quote myself

Beamed fresh from Planet Awesome
[Vibrant Android Development] ironlood:
Flashed over no problem ... I feel sorry for those who got a boot loop

GPS not quite fixed but its getting there ... I turned on GPS and waited while watching Google maps it pinpoint the street I was on but was about 3 blocks off ... and NOT... I REPEAT NOT 100% ACCURATE ONLY LOCKED WITH 1700 METERS (I only put that because there are people who will skim what I wrote and probably pick out GPS, LOCKED, and PINPOINT then call me a liar lol)

The within 1700 meters of accuracy is a decent improvement because prior to this I was getting within 3500-2800 meters tops.

So hopefully within the next few builds there will be a decent gps.
[Vibrant Android Development] bearsfan85:
got the same recovery loop issue 2 times in a row coming from 24, i guess format system data cache boot and try again
[Vibrant Android Development] richan90:
And this is with "Use Wifi Networks" set to off right?
[Vibrant Android Development] Binary100100:
Me either... but each day we're getting closer.
[Vibrant Android Development] iBustCh3rries:
I just got it down to 20 meters

Beamed fresh from Planet Awesome
[Vibrant Android Development] apollo15rover:
Haven't tried on maps yet, GPS Test picked up zero satellites
[Vibrant Android Development] treyvaporizer:
Thanks!!

Sent from SGH-T959 (CM7)
[Vibrant Android Development] bearsfan85:
you have wifi on so its using that to determine ur location, has nothing to do with gps
[Vibrant Android Development] ironlood:
Yeah I don't use WiFi networks since I don't have any networks in range ...
[Vibrant Android Development] ferhanmm:
i think he meant wireless networks. It must be turned off in your location settings to do a true test.
[Vibrant Android Development] jaikat:
honestly i don't need GPS in my area, yet i don't want to use cm7 until the mute/unmute bug is gone, thats why i keep watching this thread hoping it will be solved sometime soon...
[Vibrant Android Development] :
confirmed coming from 24 will get u into a boot loop. odin back and flash 29, u'll be as good as new.
[Vibrant Android Development] wyvernwaddell:
Got a bootloop on first flash of 29,reflashed and all is fine. GPS turns on, but doesn't get a fix...or at least not one I can see in gps test..not showing any sats.
[Vibrant Android Development] oblib__:
Can anyone that's flashed this comment on sound compression?

BTW read the thread: gps was abandoned for this nightly

http://review.cyanogenmod.com/#change,6205
[Vibrant Android Development] movieaddict:
i just flashed 29# from rom manager prem and went fine with no bootloops, how are u guys getting bootloops? R u flashing from Rom manager premium and wiping dalvik etc or downloading from the cm site and going through recovery? because everytime people say they get bootloops i dont and now im curious as to why? I know each individual phone is finicky but im really curious to why!
[Vibrant Android Development] archie53:
I have not had the bootloop issue. What I have always done is download on computer, move to sd, boot in cwm, run a backup and then flash the update. For giggles I just used Rom Manager to download, wipe davlik, and install 29 and everything worked. Either some phones just don't to be flashedor maybe some downloads are bad or incomplete.
[Vibrant Android Development] cellneuron:
good, find a good reason skipping this build.
[Vibrant Android Development] numberoneoppa:
Got myself a the bootloop, too, on 29. First time I've ever experienced a problem like this on CM7. Not using ROMmanager. Doing it via CWM.

edit: Fix: battery pull allows you to three button into recovery.

edit2: Reflashed, working. Yay!
[Vibrant Android Development] blahbommer:
got a bootloop flashed through recovery coming from nightly 15

i wiped cache and dalvick cache

went back into recovery and reflashed

now its booting up fine
[Vibrant Android Development] numberoneoppa:
I seem to have a bug. When telling the phone to reboot (terminal, recovery, power-down menu), it will not follow through properly. It will shut down and just sit there until I press some buttons.

:-|

edit: It seems to have something to do with the USB being plugged in.

edit: So it seems it DOES reboot... it just takes a very long time. Will post back when I find more out.
[Vibrant Android Development] movieaddict:
weird rare bug
[Vibrant Android Development] compuguy1088:
Same here... though wouldn't it be easier to flash a earlier nightly using Odin/heimdall than to flash this?
[Vibrant Android Development] numberoneoppa:
^Are earlier nightlies odin-able? :P

See my post above, though. I could three-finger into recovery after doing a battery pull.
[Vibrant Android Development] krntehknik303:
Weird how I'm the only one where when restoring the nandroid back up the back up seems to force close constantly. And then when I try to flash #29 on it it starts to boot loop my phone constantly and it does not change anything. I have tried wiping dalvik and cache partition and fix permissions and it still boot loops the phone... does that mean I need to odin back and reflash?
[Vibrant Android Development] masr1979:
Sometimes that's the fastest most surefire way of fixing things, good luck :D

About the FC, I was having those at some point and I formatted "System" from the "Mounts and Storage" menu, reflashed whatever version I was having problems with and didn't experience any further problems on that side of things.
[Vibrant Android Development] krntehknik303:
I tried this formatting the system and reflashed but their seems to be the same force close issues.. I'm going to try one more time and see what happens and will report back. Sucks that I'm one of those who get the boot loops...

Edit; yea that method does not work.. I think the way my rom was backed up probably ended up getting corrupted because the back up from before is working properly..
[Vibrant Android Development] scrizz:
u sure ur data partition is not the problem?

:confused:
[Vibrant Android Development] gamikzone:
i dont think they are, an odin-able file would usally be a .tar
[Vibrant Android Development] chuck24:
Don't know if it's a bug or what but I can't mount my external SD card.... really don't know if it's a bug or a quick fix but if anybody had some help my ears are open....
[Vibrant Android Development] xriderx66:
wait so....... 29 is not safe right now?
[Vibrant Android Development] krntehknik303:
What do you mean data partition?
[Vibrant Android Development] bigtom624:
Everything went fine for me. No problems at all.
[Vibrant Android Development] xriderx66:
How did you flash? Did you use PREMIUM Rom Manager to flash it, or download on PC put on SDCARD and then CWR and flash?
[Vibrant Android Development] mulcahyd:
I'm also on #29. First time install had rare boot loop. Second time it went through. Did wipe delvic cache.
[Vibrant Android Development] MStrawder:
Your data partition is where most of your settings and user data are stored. Could easily be a corruption in there causing your issue.
[Vibrant Android Development] krntehknik303:
Weird. Everything is running fine after restoring a different nandroid back up.
[Vibrant Android Development] xriderx66:
So im on #25 right now

what i should do is

go to CWR

Wipe dalvik cache

Flash #29

? is that it?
[Vibrant Android Development] movieaddict:
It's safe for most people but some are reporting bootloops
[Vibrant Android Development] movieaddict:
Best bet for non bootloops is rom manager method, make sure u wipe dalvik
[Vibrant Android Development] xriderx66:
I don't have premium rom manager right now, so can i just go to CWR, wipe dalvik cache, and flash, because thats exactly what rom manager would do right?
[Vibrant Android Development] scrizz:
yup.

that's what it does

:D
[Vibrant Android Development] xriderx66:
ok.

flashing now, if this doesn't work... imma get you scrizz.

thanks but i ran out of thanks so i said thanks.

EDIT: YAYYYYYYYYYYYY A BOOTLOOP.
[Vibrant Android Development] ewidtfeldt:
No problems coming from 24 to 29. Downloaded directly to phone and flashed through rom manager wiping dalvik.
[Vibrant Android Development] movieaddict:
Lets hope u don't get another bootloop after u followed me like last time xrider.lol
[Vibrant Android Development] krntehknik303:
Well I guess thats where my problems are with the data partition because everything is working up to par when I flashed over a older nandroid back up.
[Vibrant Android Development] xriderx66:
yeah i got bootloop.

and since this is a new computer apparently it doesn't have drivers......... >.<

sooooooooooooo

im downloading and updating samsung mini kies rightnow.
[Vibrant Android Development] numberoneoppa:
Dude. Battery pull then three-finger into recovery. Have you tried it?
[Vibrant Android Development] xriderx66:
Thanks, but im not a newfag haha.

I just didn't have the drivers i got it don't worry its odin'ing half way right now.

god odin's starting to piss me off.

Can i just flash to #29 with dalvik cache wiped now? lol
[Vibrant Android Development] numberoneoppa:
Alright, my bad. Just seemed that you were going to odin a little bit early. :P

Also, many people might want to try wiping dalvik after flashing a new ROM, not before. It shouldn't make a difference, but then again, it's not really necessary to wipe it at all...... from my experience.
[Vibrant Android Development] AgentFour20:
I came from #15 to #29 all is fine. I wipe dalvik cache and cache partition then flashed. No loops. Recovery works fine too.
[Vibrant Android Development] movieaddict:
With my exp from cm7 it's always better to wipe dalvik then not too
[Vibrant Android Development] jereader:
So, it seems that the bootloops happen when flashing from an older CM to a newer CM, but not from stock to CM. It also seems that they can be solved by formatting /system from recovery (forget your username, but thanks!)
[Vibrant Android Development] xriderx66:
OKAY! it's working for me after ODIN.

Guess i missed a step, for people like me who dont like odin.

Heres how

You can do the ROM Manager way, but i found CWR easier.

Boot into CWR

wipe dalvik cache

wipe cache partition

flash rom

have fun.
[Vibrant Android Development] muleyman:
The fix for this its posted a couple of times in the thread. Search for my username. I pointed someone to the post number a couple of days ago.
[Vibrant Android Development] muleyman:
Came from 26 via ROM manager. No reboot issues.
[Vibrant Android Development] bigtom624:
ROM Manager Premium. Wipe Davlik and flash. I also check Gapps. I never get bootloops doing it this way.
[Vibrant Android Development] Phateless:
Will be picking up a vibrant today and looking forward to joining in the fray. Lack of cyanogenmod is the reason I sold the vibrant 4g.
[Vibrant Android Development] movieaddict:
Welcome!
[Vibrant Android Development] m2zomb1e:
ran into bootloop, reflashed and it works fine.
[Vibrant Android Development] cashyftw:
Still getting bootloops, re read everything since 29 came out, Last option is odin.. I don't want to lose everything lol
[Vibrant Android Development] compuguy1088:
For the people playing at home...this is the thread he is referring to:

Which goes to these posts:

Hard way (Didn't work for me either...):

The Easy Way (Did not work for me...):
[Vibrant Android Development] joe.kerwin:
These bootloops don't require odin. Pull battery, reboot holding power, volume up and down until phone restarts TWICE, then let go of just the power button keeping both volume keys down, you'll be back in recovery, flash the same nightly you already did, wipe dalvik again just for fun, this should work.

Had to do this on 26 and 29.
[Vibrant Android Development] xriderx66:
yeye i understand your pain.

I forgot to backup about 20 of new apps that i downloaded.... im trying to find them right now lol.

I odin'd and wiped dalvik, then cache partition, and flashed 29 and its been working pretty smooth. just flashed KB5 on it though.

Just wondering...

is anyone's GPS actually working? lol
[Vibrant Android Development] cashyftw:
Wow, this is impossible, going back to miui until 30 comes out.
[Vibrant Android Development] cashyftw:
Thanks for trying to help dude, I am indeed VERY frustrated lol, I've never been this bad off, I'm just going back to miui for now.

EDIT: Nope, just kidding, Miui is now giving me bootloops also.. perfect.
[Vibrant Android Development] scrizz:
next person that asks about GPS is getting banned!

lol jk jk
[Vibrant Android Development] xriderx66:
why is miui givin u bootloops lol bad luck?

i see that white text scrizz dun try to outsmart me!

but srsly wtf happened to all the fags goin "GPS IS GONNA WOERK ON 29 GUISE I PROMISE!"
[Vibrant Android Development] richan90:
Everyone should get in the habit of doing a nandroid before flashing anything. Waiting an extra minutes is worth it over losing your data.

Sent from my SGH-T959
[Vibrant Android Development] xriderx66:
whats a nandroid.

jk i know what a nandroid is its like a backup, but i dunno how to do it. i never needed it ha
[Vibrant Android Development] krntehknik303:
Unless you're one of those that has his data partition get corrupted in the process of backing up the rom.
[Vibrant Android Development] defconoi:
no bootloops here flashing from #25, wiped dalvik, data, cache, factory reset, no problems, if you are new to this you should be using nandroid to back up your phone, Odin is a thing of the past, especially if you know what your doing

#29 is working great, just wipe all AND BACKUP BACKUP BACKUP, ALWAYS BACKUP! then you wont need odin unless u pull battery while its flashing the kernel or the kernel is F*^&'d
[Vibrant Android Development] cashyftw:
Wiped everything, now 29 is working, go figure.
[Vibrant Android Development] Virtuososteve:
I got #29 to work

1. Odin

2. root (obviously)

3. Go to recovery

4. wipe data/factory reset

5. install zip

6. wipe cache

7. wipe dalvik cache

8. fix permissions

9. reboot
[Vibrant Android Development] jzero88:
Using system panel but can't tell why this build is a juice whore. Came from a fresh install too.
[Vibrant Android Development] archie53:
For those of you that are worried about losing apps, and since these nightlies have been pretty consistent why don't you have titanium run every night, in the middle of the night. That way your apps are always backed up and no worries. And you can wake up download the new nightly, make a backup and flash away.

Sent from my CM7 Powered Vibrant
[Vibrant Android Development] compuguy1088:
I religously do this every time I flash a nightly, or ANY rom for that matter. Even comming from stock, the recovery does not seem to want to restore or backup the system or data partitions. Any suggestions?

What I've seen is either a recovery boot loop, or the inability to restore/backup from nandroid.

Edit: It seems nightly 26 has this same issue...I recommend going back to 25....
[Vibrant Android Development] funeralthirst:
i got a bootloop when i flashed through recovery the first time. i pulled the battery and booted into recovery, factory reset/wipe data, wipe cache partition, reflashed and it worked.
[Vibrant Android Development] compuguy1088:
Sadly I've resolved that issue, but I'm unable to restore or backup using nandroid with 26 or 29.....
[Vibrant Android Development] Phateless:
That's actually a really good idea.
[Vibrant Android Development] bigfkncee:
I just got the bootloops on 29 also. Like others have already stated, reflashing from recovery fixed it up quick-fast.....no Odin necessary. Thank you all for having the answer before I even asked the question.

Edit: I'm having forcecloses all over the place. Gonna try to flash a backup. :/

Edit2:Flashed back to 23,still got forcecloses.......restored a backup of 15 and flashed 23 over it and everything seems peachy again. :)
[Vibrant Android Development] adampdx:
Wiping Problem

I also experienced the boot loop after 29 flashing from 24. This same thing happened to me trying to go to 26 from 24. Wiping and wiping and wiping did the trick, but...really? I'm not complaining, of course, but I do wonder if this is something that I should get used to when trying out the nightlies? This is the third Android device I've had CM on and this is the first time I've experienced this type of thing. In the long run I suppose it only means that I'll flash the new nightly less frequently, but my God how that idea pains me.

And I'm not going to mention the GPS. :)