yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] maelstromm:
Only thing I did different to you was to Factory Reset before Flashing Initial package. I got the Status 7 when installing the device specific zip.
[Vibrant Android Development] nht48823:
I been using 06 for about couple of days now. everything seem to be running very fast and smooth. defiantly battery does seem to drain fast. last couple of days I been averaging around 10-12 hours compare to I was using ICS Passion for couple of months my average was pretty close to 18-20 hours
[Vibrant Android Development] joe98200:
I haven't been getting any sort of significant lag and I have 36 apps installed. With my personal use I squeeze 24+ hours out of this ROM.
[Vibrant Android Development] nht48823:
oh wow that gives me hope... that's great news! maybe i should upgrade to whatever the latest out there. let me understand this coming from 06 all I need to do is flash the "base" file correct, without wipe data?
[Vibrant Android Development] dddtc2005:
How about flash a devil kernel(tar file) in odin when you got stuck?
[Vibrant Android Development] joe98200:
If you're coming from a previous Helly Bean version, flash base then the file for Vibrant then addon. All the instructions you'll need are in the OP.

And I'm not sure if version had anything to do with my battery life. I've been using this ROM since its first public release and my battery life has been consistently long (deadline ondemand).
[Vibrant Android Development] hkfan:
Which tar file from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/112/ ?

This will only give me kernel right ? and then I have to follow all the steps from OP including initial package flash ? or start from base rom
[Vibrant Android Development] dddtc2005:
Yeah, if you use vibrant, choose vibrant edition, CMC or VC both OK.

And yes it only gives you kernel. I'm not sure this will work or not. But i have ever face this problem before, and this method works.

You follow all the steps until the last time got stuck, right? So i think it may be a kernel problem, and it is only a suggestion that you can have a try. But it may still not work.

Good luck~
[Vibrant Android Development] WingCero:
So how is the latest version faring? I am on the version of Hellybean that debuted on XDA. At first it was love,

now its just a buggy messy that flips out A LOT. Can someone give their take on the August 7th build?
[Vibrant Android Development] Drjjones426:
0807 seems to work well I haven't had any issues yet
[Vibrant Android Development] ddanc1984:
You'll need to install GB bootloaders too I believe in addition to following the OP.
[Vibrant Android Development] nht48823:
I still cant get the GPS to lock in my location (i never use navigation anyways) but other then that I am using it as my daily drive...love it!!
[Vibrant Android Development] TFordham:
No issues here. Very smooth. What bugs are you referring to? How does it "flip out?"
[Vibrant Android Development] Annex1:
My phone has been very smooth since ver 803

The flipping out part, are you talking about where it's trying to wake up?
[Vibrant Android Development] imilleson:
The first version of hellybean developed sporadic camera crashes, soft rebooting, xda app crashing, launcher FCing yada yada.. I am well aware of the necessity to do a clean install which I did, it was just an initial release and needed work.

I tried 803 and it was much better, but now I am on FEs cm10 And it is actually smoother than when I was in hellybean , I am running the devil 112 kernel though so that explains the extra butter
[Vibrant Android Development] kristibaee:
oh ok sorry. im trying flashing it again and the initial.zip doesnt install and gives me an error, the base.zip installs &then the vibrant.zip goes into bootloop. how can i fix this ?
[Vibrant Android Development] shiftymccool:
/datadata

Holy crap... /datadata makes so much difference! I decided to go from SlimICS to CM10 to give Jelly Bean a try and it was LAGGY. Decided to give Helly Bean a shot since it makes use of the /datadata partition and it makes all the difference.

The only issue I'm having (with this and CM10) is choppy video recording/playback. Is there any way to fix this? I'd like to stay on this ROM for a while but choppy video recording is a deal-breaker for me. Is anybody else noticing this? It seems to happen when the frame for the gallery thumbnail is being captured. Without spending my day troubleshooting, it seems to happen a few times before 30 seconds into the video with a large "chop" at about 15-18 seconds.

Thanks for the killer ROM guys, I never imagined the vibe going this many OS revs and still be able to handle it... You guys work magic!
[Vibrant Android Development] Annex1:
Try MX player. removes choppiness... in some roms....

I haven't had any choppiness but I don't really watch videos on my phone
[Vibrant Android Development] mfndoom:
ok, i've been reading this thread for days now and i'm trying to make sure to follow directions and avoid looking like the noob i am.

so here goes...i'm running zenwich right now, do i just do a factory reset then follow instructions pulled from this thread?(the reason i'm asking is a tutorial video i watched the guy went from stock-->passion(i know i know)-->icsslim then-->jelly bean)

Flash in this order 1. HB initial (there is a link in op) then reboot recovery

2. HB base (its in the download folder)

3. HB vibrant (also in DL folder)

4. Add ons (also in DL folder in op)

Reboot

thanks for any help.
[Vibrant Android Development] AgentFour20:
You only need to flash ICS or CM9 if your coming from stock . Just follow OP "coming from another ROM"
[Vibrant Android Development] mfndoom:
awesome, thanks!
[Vibrant Android Development] samsgun357:
If you are already on helly, you don't need initial. If you are coming from any other ROM you do. If the initial doesn't work (and you need it) I don't think its a good idea to try the other zips. What you could do is go back to a previous version of helly then flash the base, vibrant and add on zip (wipe cache etc). If you get a boot loop, stuck on boot animation screen> pull battery, and 3 button back to recovery, reboot.....if boot loop continues reflash. I hope this helps

drool on my chin from a mouth full of jellybeans
[Vibrant Android Development] DerTeufel1980:
To really fix is, I need you to help me. The first zip never should fail.

Please try flashing it again, and after it fails, connect your phone to pc and do the following:

adb shell

cat tmp/recovery.log

then copy the output please into a txt file and attach it here. Many thanks.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] shiftymccool:
Thanks for the reply. It's not so much the video playback that's choppy. I just tried MX Player and a couple others but the chop is still there. It must be happening during the recording because it's always in the same place during playback and many of my videos have messed up thumbnails (rainbow colors and heavy pixelation). I was on a different ROM some time back (I switch too much to remember which) but I had installed SubZero kernel with an optional 720p playback flashable. I had this same issue on that ROM with that kernel until I flashed that package. So far that's the only evidence I have that this issue can actually be fixed.

I hope I'm not the only one with this issue so it can get some attention (I know y'all have bigger fish to fry than one dude's small issue). If there's anything I can provide that will help with this just let me know.

Keep it up y'all!
[Vibrant Android Development] Annex1:
It sucks but wait 30 sec before recording... then try to record something and then play and see what happens.
[Vibrant Android Development] tsiah:
I've been using Helly Bean for a few days now (804 with the 1.1.2 kernel) and haven't had any problems (aside from no GPS...) until today.

I sent a text message, hit the home key and the phone froze. Backlights wouldn't turn off, no response to any buttons. I held power to shut the phone down. The battery was dead so it wouldn't turn on again. After installing backup battery and booting the phone, all my text messages were gone.

Any idea what would cause that?

It's not a huge deal but I don't want it happening again.

About to flash 807 :) Love this jelly bean action!
[Vibrant Android Development] GTOJim:
I had a bad battery that acted like that, it had a good charge. Swapped the battery problem went away, put the bad battery back with a full charge and after awhile phone froze. Tossed that battery and haven't had a problem since. Hope you have another battery you can try or hopefully it's just an abnormally and won't happen again.
[Vibrant Android Development] imilleson:
Check kernel settings and make sure your not using BIGmem as that breaks video, I think XL mem works best for video . Use either devil kernel all from market or check in recovery
[Vibrant Android Development] treleung:
By far and away the best on battery, fastest, smoothest ROM available for Vibrant. I get better battery life here than on KB5 ROMs. Freakin' awesome. Thanks devs.
[Vibrant Android Development] nguyns:
Vote for you! Your work is so good! Try your best!
[Vibrant Android Development] DerTeufel1980:
I think i am going to make a all in one file next release. It seems to be too complicated for many users to flash more than one file.

The file probably is about 250 mb, but no one would have to take care of the device or previous rom. Hope that's okay for all of you

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] ou814us2:
The problem is people think they know what they are doing when they really dont. If everyone followed directions put in front of them this would be a boring world;)

BTW, great rom..love your work and thanks!
[Vibrant Android Development] Annex1:
I agree with you... On the many users not knowing what they are doing... I personally don't care how you do it :)

Just do it how you want.
[Vibrant Android Development] gunks:
I think the problem came about where people were thinking that the initial file was the same as the base file, or vice versa. And having the base not being in the primary DL location was most likely the cause. I say just do it the way that easiest for you man. If they cant figure it out that's too damn bad... you guys make it easy enough as it is.
[Vibrant Android Development] Br1cK'd:
+1, do it how its easiest for you DT, the reasons I left XDA are splattered throughout this thread, peeps not reading, not listening, and jumping in head first before they read and heed the directions you post.

Do it how you want though man, its your build, and your idea of how you want it to work. If people would slow down and understand what they are supposed to do, there wouldn't be near as many false reports that are user induced. Unfortunately many in the Vibrant forum don't do that, and ask the same questions time and time again in many threads.

Sent from the ICZen Experience
[Vibrant Android Development] ddanc1984:
Agreed. The Devs make it easy enough, if people would just RTFOP (Read The F*#*ing OP). Also before one takes off flashing they should read at least the last 5-6 pages of the thread or do a search looking for specific answers to questions they may have BEFORE flashing. Just bad juju to flash then worry about how to do it....that's a Ready, Fire, Aim approach and it generates a needless clutter of questions that have already been answered multiple times. One suggestion for the OP would be be something about the Status 7 issue and how to address it (does the Initial flash fix it?). Most people who have been flashing for awhile know how to work around that but unless you want the thread cluttered with inane and repetitive questions it might merit consideration. But then again like I heard it said before (paraphrasing): If you want someone not to read something, put it in the OP!. I think Jimmy Hoffa is in an OP somewhere.

Another thing, when flashing a new ROM from different Dev than your current ROM...always do a full wipe. Don't be lazy and DON'T use Google Restore. Also use a kernel cleaner and/or Darkside. That alone will save you a lot of FC and other issues. If you don't practice good wiping and flashing protocol, quit whining about FCs like it's a ROM problem.

Good ROM by the way!
[Vibrant Android Development] samsgun357:
My battery life on 807 has not been good. I was getting 16-20hrs per charge, now 9hrs overnight. It appears that my phone is not sleeping. Android system used 55% and screen 15%. I flashed annex cid tweak, I don't know if that is what's effecting my battery?

sent from my magic box to yours
[Vibrant Android Development] nht48823:
Yes I notice similar issue with battery.
[Vibrant Android Development] xriderx66:
I don't understand how and why you developers are SO KIND to these noobs..

If I was a dev. I would get pissed off at every other post.

I say keep it how it is, it may be useful as a noob-repellent.

If they don't get something, and don't READ the OP/other posts then its their damn fault they bootlooped.

The thing causing this is also the OP not being Der. I agree it may cause ease on Der himself, but the OP is not how it should be (no offence TF)

There are no clear instructions how to get away from status 7, direct links to all the downloads and mostly there is TOO MUCH ****.

There is NO organization in the OP at all.

My suggestion: Der needs his own thread/ TF needs to remove all the crap from the OP and be direct.

Edit: sorry for my language, this thread is giving me headaches.
[Vibrant Android Development] ragedz:
My battery life has been as I stated before. Similar to remics. I used to disable data to get extra. Now I just don't worry about it. I can do full charge at 12am, unplug and wake up next morning with about 84 percent at almost 12 hours. After talking for a few hours it usually drops to around 30. By the time I goto work at 330pm, I'm around 14. If I don't use my phone in the morning for talking I end up with around 50 when I'm going to work. I can get almost 24 hours with only data use like Facebook or browser. Talk time seems to eat it up. But we all know how these batteries go out. Also, fast charge will not keep my phone going as long as regular for some reason. I keep that disabled.
[Vibrant Android Development] shiftymccool:
I think that did it, I was on CM9 mem to begin with. I'm not sure how it's possible, but the camera seems to open faster and be more responsive now as well. There used to be quite a bit of lag between pressing the record button and the recording actually beginning.... now gone.

Anyway, thanks a load guys. I'll be sticking with this ROM for a while.
[Vibrant Android Development] samsgun357:
I guess I'll wait for next update and do a squeaky clean install.

sent from my magic box to yours
[Vibrant Android Development] taurus193:
+1
[Vibrant Android Development] Tophall32:
New to JB not to flashing.

As someone who would love to try this rom I think this is the problem.

I read ALL the OP info and the reports of problems before I try out a ROM.

However, if the Download location does NOT have all the files necessary or at least links to where to find files then ANYONE will have problems and will say so.

I fully appreciate the hard UNPAID work developers do. I want to support you and help others to make your time easier.

Please UPDATE the OP or the Download site to allow 1st time users of this ROM to find all of the fines including the base one.
[Vibrant Android Development] Toast6977:
Is there a script to run for a squeeky clean install. Was reading where you might need to run a kernel cleaning script. Is that for even a new install coming from froyo? Or is that just if you've used different kernels on this rom?
[Vibrant Android Development] samsgun357:
You can run the ultimate kernel cleaning script, I usually only run that when flashing new kernels. Since this ROM comes with, IMO, the best kernel available its not necessary. If you go to www.team-passion.com, there are steps for SCI.

I usually just do a full wipe/factory data, cache, dalvik cache and format system then flash ROM.

sent from my magic box to yours
[Vibrant Android Development] TFordham:
No offense taken. I think the OP is organized enough, as long as people read it, which clearly doesn't happen. I will add on status 7. I've never had it, and I don't feel like reading 20 pages to get the details, so xriderx66, if you wouldn't mind, PM exactly what is going on and the solution (no one else....I don't want dozens of PMs coming in) and I will add it in.

I suppose I was rather naive with this thread. I only put it up since the early stage of the ROM was being mentioned in an entirely different thread. Seemed like it needed a home, and I didn't see anyone posting one. The time involved may be more than I wanted to invest.
[Vibrant Android Development] Annex1:
The way people are getting the error is by flashing in a different recovery, CMW works and DEVIL works, flashing in any other you will most likely have an error. I heard Glitch works, but I don't test these.... Since mine has always worked fine
[Vibrant Android Development] samsgun357:
+1 status 7 error=never
[Vibrant Android Development] Zephiroth2007:
807 version works perfect :laugh:

La version 807 funciona perfecto :laugh:
[Vibrant Android Development] DerTeufel1980:
well, i am uploading the new "allinone" package now. it can be flashed on i9000, captivate, vibrant and fascinate (of course i only could test i9000 myself).

the needed version is detected automatically, but it is important, that you are running a kernel with correct default.prop (this is similar to build.prop, but for recovery).

if you are using my kernel already, you don't need to worry about this.

if you are running a different kernel, and want be sure that all goes well, just create the file "device" at /sdcard/devil, so the full path would be:

/sdcard/devil/device. write your device into this file (i9000, cappy, vibrant, fascinate)

you still need to flash the addons, because they don't change very often, and including them would be useless traffic for me and you.

the file can be found at http://rootaxbox.no-ip.org/derteufel/test/

md5sum already is there, too. upload is taking about 30 min from now.

other changes:

- compiled from latest sources

- added nstools to settings menu (for testing, going to be replaced by devil kernel apps)

attention: this is still a test. don't flash it, if you don't know what you are doing/how to get back
[Vibrant Android Development] GTOJim:
Flashed, phone just finished booting normally. Worked great.
[Vibrant Android Development] ddanc1984:
+1
[Vibrant Android Development] taurus193:
Flashed allinone,,no wipe everything running great.....
[Vibrant Android Development] jpgilman:
I made the mistake of trying to follow the Guide I found on the Helly Bean site. I assumed those would be the most likely to be correct. Based upon my reading of the guide, I skipped flashing Initial and Base and flashed helly_bean_vibrant directly over GB, then flashed the AddOn. I literally had no clue that Initial or Base were relevant. The rom mostly, kind of worked, which made be believe that I had flashed correctly and I assumed JB for Vibrant was far more alpha than ready to go, which wasn't inconsistent with some of the stuff I read.

Ultimately I found other instructions, followed those and life has been grand ever since.
[Vibrant Android Development] hurtz777:
Der I wiped and flashed the AIO0809 and have found no issues so far! I placed NS Tools in system\app and your NSTools shortcut in Settings opens NSTools flawlessly. I can't wait until the next build when you change the shortcut to Devil Kernel Config app for full rom control. Has anyone noticed that if you scroll NSTools down quickly that the menu gets all jarbled up and you have to kill it and reopen to fix it? Der will you use Devil Kernel Config app or Devil Kernel Manager app? I prefer Devil Kernel Config app because v0.9.1 20120808 is working flawlessly and is saving all kernel settings properly with HB 1.13 kernel. AIO0809 is pure butter even without using SmartassV2 governor and this is definitely the snappiest JB build to date and is comparable or maybe a little faster then CM9 4.04. I find that ONDEMAND governor with VR or DEADLINE scheduler give about 30% more battery vs SmartassV2 governor with SIO when running at 1.2ghz. Using the smooth profile makes ONDEMAND feel just as snappy as SmartassV2 to me. Der thanks for the new build for us crackflashers!

---------- Post added at 08:43 PM ---------- Previous post was at 08:00 PM ----------

Has anyone noticed that the background process limit setting won't save after reboot? I noticed this with FE's CM10 0807 build also so I assume it is a CM10 bug.
[Vibrant Android Development] samsgun357:
@hurtz haven't noticed the background process limit not saving as I usually have mine at standard. When trying to launch nstools from settings it crashes. I saw your post about pushing to /system/app, where did you get .apk?

I also noticed

In settings>launcher, only home and general launch but I am glad to see trebuchet launcher!

Kill app back function is finally working properly!

Edit: just read that process limit isn't saving in slim as well

sent from my magic box to yours
[Vibrant Android Development] kristibaee:
This rom is finally smooth for me after re-flashing it a couple times, but im having a problem. My friends receive my sms waaay after i send them, sometimes over 30 minutes late. Is there any way i could fix that because id really like to keep using this beautiful rom.
[Vibrant Android Development] hurtz777:
Samsgun357 I have attached NSTools.apk. Just push it to system\app with a root file explorer, set permissions, and reboot and the NSTools in Settings will work. I would still recommend using Devil Kernel Config for full kernel options.
[Vibrant Android Development] xriderx66:
I flashed ROM- nowipe- and then GAPPS, and currently my Play Store does not work. It gives me a FC everytime I try to download an app.

I wiped cache/data and fixed permissions.

I saw this question being asked earlier, but saw no solutions to it.
[Vibrant Android Development] gunks:
Try uninstall updates option in manage apps.
[Vibrant Android Development] xriderx66:
Worked - thank you.
[Vibrant Android Development] kristibaee:
So i guess no one else is having problems with not being able to send sms then ?
[Vibrant Android Development] dddtc2005:
works for me. Thanks
[Vibrant Android Development] samsgun357:
Its working for me. You did flash the helly bean add ons right?

sent from my magic box to yours

---------- Post added at 12:24 AM ---------- Previous post was at 12:14 AM ----------

Edit

sent from my magic box to yours
[Vibrant Android Development] kristibaee:
Yes, the add-on from 7/29

---------- Post added at 11:40 PM ---------- Previous post was at 11:26 PM ----------

I dont think its the addons because everyone else would have the issue too
[Vibrant Android Development] samsgun357:
@kristi, what exactly happens when you try and send SMS?

sent from my magic box to yours
[Vibrant Android Development] kristibaee:
Nothing happens, everything is normal, its just like it sent. But multiple people have told me they get my texts late or dont get them at all. I also tested it with a texting app &texted the app from my phone... my sms took 40 min to arrive &the other one did not arrive at all. No problem with receiving sms though.
[Vibrant Android Development] samsgun357:
@kristi, pm coming.

sent from my magic box to yours
[Vibrant Android Development] here.david:
Everythings seems to be perfect even got GPS now...

Not sure why, yet GPS is now working...as well as everything except Fasterfix which has never worked, however, not needed as I said GPS working GREAT!:good:
[Vibrant Android Development] ward360:
I an having problems with this too.

I can send myself a text and it comes through instantly, if I send my wife a text (she is on ATT) it comes through 1 to 2 hours late.

If she texts me it comes through instantly.

I was thinking this was a problem with ATT - T-Mobile not the phone itself. All texts were SMS. And everything act's normal.

I am running 807 and flashed from 804 with no wipe just base, ROM and then addon