yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] firefly6240:
I had both this issue and extreme battery drain.( I got about 1 - 2 hours per full battery charge)

to fix it I did a full wipe and installed the 12/14 rom and the Cyan gapps but still had both issues.

then I flashed Gear kernel (this fixed the battery drain I now get about 7 hours with moderate use)

I switched the governer to Lulzactive which I've had pretty good luck with before but it was pretty noticeably laggy,

I then tried the Lionheart governer with SIOplus (the default scheduler) and it was like night and day.

its smooth and snappy and does not lag on calls anymore.

hopefully this helps.
[Vibrant Android Development] bryantthesmith:
I too had a huge battery drain issue that was fixed by moving to another kernel (Fluid Kernel). There must be something funky in the standard Kernel. On my phone I noticed that the main battery culprit was the radio (svnet in BBS) until I moved kernels. I'll give the Gear Kernel another go to see if it helps my lag. Last time I tried it I couldn't boot after flashing.
[Vibrant Android Development] sauron82:
I was getting good battery life with Fluid kernel. No such thing as great battery on this phone lol. I'd usually get 7-8 hours with decent use.
[Vibrant Android Development] sada23:
New build 12/20/2013 uploaded

New build 12/20/2013 uploaded.

Enjoy!!!
[Vibrant Android Development] moldyghosty:
So, I guess I am the only one who gets 12 to 24 hours, depending on usage?
[Vibrant Android Development] cricketz66:
battery

I have got a day and a half ....but it was with little use but hey kitkat/vibrant no complaint here!
[Vibrant Android Development] cashmundy:
Getting no Wifi with the 12/20 build, won't turn on at all. Restoring back to 12/09 build which works well for me.

As for battery issues: when my battery runs down while the phone is just sitting, I find it is the Google bloat/spyware which is doing it, based on looking at running apps and battery usage info. Google Play Services is the worst offender. Don't know what it does, probably nothing good, but I removed it and had only one app fail: Realtor.com. My solution was to delete the Realtor.com app, and I'm planning on purging all the Google stuff from my phone.

Thanks for the builds. Not one brick or boot-loop yet, which is as good as it gets at the bleeding edge.:good: :cowboy:
[Vibrant Android Development] sada23:
I have replaced the build with WiFi fixed. Re download and flash. I find the new build more fast and smooth.
[Vibrant Android Development] bigtom624:
I just d/l and flashed the 12/20 build again and wifi is still not turning on.
[Vibrant Android Development] selmandeli:
I have no problem with WiFi on first version of 12/20.

Edit: With the second version of 12/20 I lost my Baseband. Nothing helps to get it back.
[Vibrant Android Development] bigtom624:
I tried to flash it 3 different times and all 3 had no wifi. I just keep my Vibrant around as a backup and to mess around with it. I don't have a sim card in it, so without wifi I can't do much. No problem though. I still appreciate Sada23 updating it and keeping this dinosaur relevant. Thanks again.
[Vibrant Android Development] Martezgarki:
Were you using gear kernel before flashing?
[Vibrant Android Development] binniebin:
Go to download mode and Flash last froyo with odin

Turn off device

Hold vol up and connect usb to PC, device should show download mode

Flash last Official froyo with odin

I lost my baseband too then Cleaned all device with no recovery and problem to get in download mode, after that what I write got my baseband back, and starter over again to put 4.4.2 with fluid kernel

Dont use Gear kernel and backup your efs and Hold it in safe place like bed ;)
[Vibrant Android Development] smokey155193:
hi binneibin. what's wrong with gear kernel. I also lose my baseband up on installing it to restore it have to go back to cm7 and start again.

---------- Post added at 06:55 AM ---------- Previous post was at 06:46 AM ----------

I tried all versions of gear kernel on all versions of android got vibrant. and never get baseband to work. previously got MBR checksum error when partitioned internal SD card using subzero kernel. can't get rid of MBR checksum error till now. tried all ways from xda to some but no success. do it have some relation to gear kernel. help please.
[Vibrant Android Development] waihung0626:
I have wifi is still not turning on too.Have a fix?
[Vibrant Android Development] testomat:
How to downgrade via recovery to older cm version like 10.2 ? i use actually cm11 and if i use recovery to flash 10.2 i got assert failed: getprop ("ro.product.device...." status 7 failure.
[Vibrant Android Development] smokey155193:
to downgrade use semaphore kernel and then format data cache datadata system etc. flash new rom.
[Vibrant Android Development] sada23:
New Build 12/23/2013

New build 12/23/2013 uploaded.
[Vibrant Android Development] cashmundy:
So far so good. Wifi is working. I should note that I am putting Openpdroid on top of these builds (using [MENTION=4342828]mateorod[/MENTION]'s amazing AutoPatcher) which is really asking for trouble.

It's fun to turn off permissions for apps, even system apps, while enabling "notify", and see just how much information apps harvest that they apparently want but don't need, judging by how much one can turn off and still have things work just fine. Doing this must really annoy Google/NSA. Hopefully, anyway.

For example, why does sending an SMS cause "Phone" to want "network information" and "subscriber ID"? The SMS goes out just fine with those disabled. Someday I should set my netbook up as a Wifi access point, connect the phone and run iptraf, see who it's talking to other than me.
[Vibrant Android Development] Shinotheweevil:
Does anyone got hotword detection working? The Mackay port has it working but I want to keep this one.
[Vibrant Android Development] smokey155193:
camera force closed after trying to select video for video capture
[Vibrant Android Development] Martezgarki:
Same here.
[Vibrant Android Development] N00B_IN_N33D:
Try flashing this: http://xdaforums.com/attachment.php?attachmentid=2015334&d=1370300508

No promises, but that should fix the problem you're having.
[Vibrant Android Development] ddb707:
no baseband

baseband unknown n no gsm connection.... plssssss help asap..
[Vibrant Android Development] flapane:
Did you even bother reading the first post?
[Vibrant Android Development] flapane:
Installed latest build coming from JB4.1 (CM10). Factory reset and then double install.

I got an endless bootloop.

edit: Solved by formatting and reinstalling it two times.
[Vibrant Android Development] ddb707:
the instructions in the op is not working for the baseband issue... pls help... i tried most of the posts, but nothing works.. wat am i to do...??
[Vibrant Android Development] cricketz66:
I had same issue... had to Odin back to stock rom to get back both baseband and imei number back
[Vibrant Android Development] waihung0626:
you can try Installe fluid kenrel v1.0
[Vibrant Android Development] flapane:
Camera JB+ doesn't crash, so it's something related to camera.apk itself.
[Vibrant Android Development] sada23:
New build 12/27/2013

New build 12/27/2013

I dont have any Camera or video recording issues with this build. Even Panaroma works.
[Vibrant Android Development] flapane:
A couple of issues coming from JB4.1 and using stock kernel (12/23 build).

- Higer standby battery drain (more than double), even though the phone seems to go into deep sleep.

- No H264 video can be played. I tried with Gallery JB, Gallery JB+, Quickpic, Diceplayer, Playerpro. It seems that the build completely lacks support for SW and HW video decoding which was shipped with JB4.1 or 4.2 ROMs.
[Vibrant Android Development] elfabio00:
(Status 7)

Installation aborted...

Help :/
[Vibrant Android Development] firefly6240:
flash fluid kernel: http://xdaforums.com/showthread.php?t=2535879

then reboot recovery and try flashing again.

also note that occasionally you will have to flash fluid kernel twice if your already getting errors.

---------- Post added at 09:38 PM ---------- Previous post was at 09:25 PM ----------

1. if you have a backup of your EFS folder then you can copy the files from the backup into your current efs folder.

2. if you have a recent nandroid backup you can revert to that and re-flash this ROM

3. if you have no backups as a last ditch effort you can try deleting everything in your efs folder and rebooting.

a. some people report that the files will regenerate on their own. (note this method never worked for me)

4. you can try flashing a CM 10.2 ROM

a. this seems to have a 50% success rate

5. you'll need to Odin back to stock and start over

if you don't have backups, moving forward I would advise that you have the following backups (unless you are always willing to Odin back to stock) as flashing roms always has some risk.

1. at least 1 nandroid backup

2. a backup of your EFS folder

a. you can manually do this using a root enabled file browser or if you use gear kernel it will do it for you.

3. (optional) a backup of your critical apps (I use titanium backup but there are other options out there.

---------- Post added at 09:49 PM ---------- Previous post was at 09:38 PM ----------

for battery drain:

I use Gear Kernel

I use the "Lionheart" CPU governor with the default "SIOPlus" scheduler.

this killed the battery drain which oddly seemed to come from apps requesting GPS location constantly even when location is disabled.

I also overclock to 1.1ghz which causes no noticeable impact on battery life over stock speed.

For h264 videos the newly updated MX Player on the market works perfectly.

note that it was not compatible with android 4.4 until a few days ago, but now that they updated it it works great.

(note that I have only tried it while using gear kernel so there is a chance the issue is with the stock kernel)
[Vibrant Android Development] flapane:
Thanks a lot, MX Player works great (I guess they rewrote 4.4 API from scratch, hence some players still have issues, JB gallery player included).

I'll try Gear Kernel and will keep you guys updated (tonight the battery dropped by almost 30% in (supposedly) deep sleep state and in airplane mode!)
[Vibrant Android Development] Galaxy3HELL:
Do not install GearKernel, you will lose Data and Network Signal.

Fluid kernel is best CM11 kernel for our vibrant, even if it doesnt have any special feature :)
[Vibrant Android Development] flapane:
I didn't lose my baseband nor IMEI.
[Vibrant Android Development] firefly6240:
you wont lose data and network signal by initially flashing it, but thanks for reminding me.

just as a warning to everyone who does use it, note that you will want to flash fluid kernel before flashing ROMs (even updating this one)

otherwise you'll likely get the status 7 error.

(even if you forget and get the status 7 error just flash fluid kernel twice and then flash your rom)

in the off chance that your efs folder gets corrupted (that's what causes the no data error) just do the following:

1. Gear Kernel automatically backs up your efs folder to the sd card under sdcard > backup > efs

2. copy the files in that folder using a root file browser (I use root explorer, but even the pre-packaged CM file browser works)

3. browse to the efs folder located under your root folder: / > efs

4. paste the files you copied and confirm overwrite (you may need to mount the folder as read/write depending on your file browser)

5. reboot
[Vibrant Android Development] flapane:
Thanks, how weird. So, the workflow for upgrading CM11 is:

- Flash Fluid Kernel from recovery

- Flash new CM11 build

- Re-Flash Gear Kernel
[Vibrant Android Development] flapane:
Here's the difference in deep sleep with stock CM kernel (left) and Gear Kernel (right), which is more similar to the deep sleep battery drain I had on JB4.1

I still don't know why the battery details still don't show when the phone is awake, though.
[Vibrant Android Development] firefly6240:
Yeah that's what I do.

Alternatively if you dont need the options you could just use fluid kernel.

but in my opinion the benefits of Gear kernel are well worth the extra steps.
[Vibrant Android Development] flapane:
Absolutely. I used to use Glitch on GB and Semaphore on JB4.1, I undervolt, finetune scheduler and cpu governor, set up BLN, so the more features the better.
[Vibrant Android Development] sada23:
Final build for the year 2013

Build Date 12/31/2013 uploaded

HAPPY NEW YEAR!!!
[Vibrant Android Development] flapane:
Happy new year to developers, ROM cooks, newbies, advanced users!
[Vibrant Android Development] Martezgarki:
Happy New Year!!

May the Vibrant live forever!
[Vibrant Android Development] sada23:
First build of the year 2014

Build Date 01/02/2014 uploaded.
[Vibrant Android Development] sauron82:
Hey Sada, can I install this as an update (just wipe cache and flash), or do you recommend a clean flash?
[Vibrant Android Development] sada23:
If are already on one of the CM 4.4 builds, you could flash it over the previous ROM after wirping Cache and Dalvik Cache. No need to do clean installs everytime.
[Vibrant Android Development] flapane:
Did FaultException ever answer you about releasing the build as "official", thus including it into CM official repository?

ICS, JB4.2 and 4.3 were a true nightmare in terms of slowness, no matter what users said, but Google did a great job with KitKat on older devices. It runs almost as good as GB. I can't see why dropping support for Vibrant. :(
[Vibrant Android Development] smokey155193:
can anyone build a kernel or add support to the present one for otg. please.
[Vibrant Android Development] binniebin:
Someone tried to use ART on last version?

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Vibrant Android Development] Ace42:
Was it broken for you?

Sent from my LG Optimus G
[Vibrant Android Development] binniebin:
Im not sure but when its updating cant apply host file, ADS are annoying in some aps.

No problems on my vibrant with last BUILD from cm sources and never had so I asked is this of ART, but now I don't know where's prob.

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Vibrant Android Development] binniebin:
Sorry for last post, bad topic I have issue on my N7 with last Adaway, nevermind.

About ART...

Working on my grouper (N7), vibrant is too slow on ART, first few boots work's pretty nice, but it's lagging so quick when device is up longer.

So anybody is using ART for longer time? It's so nice that this phone work so well and got last version of green robot, but we want more and more, more performance without loosing battery life ;)

Regards
[Vibrant Android Development] flapane:
That's weird, because Dalvik requires the code to be compiled in real time, while ART uses pre compiled code, so in theory it should be lighter.
[Vibrant Android Development] sada23:
New Build uploaded

New build 01/10/2014 uploaded
[Vibrant Android Development] CTown:
It's just a guess but perhaps ART produces code optimized for Snapdragon.
[Vibrant Android Development] waihung0626:
nice,Thanks your rom and kernel for good work:silly:
[Vibrant Android Development] flapane:
Thanks. Has the "no wifi" bug been solved? Did it affect vibrantmtd only?
[Vibrant Android Development] sada23:
Yes its solved.
[Vibrant Android Development] flapane:
Also, with this build I finally see the awake/sleep graph in Battery stats.
[Vibrant Android Development] maelstromm:
Dug up my old vibrant and odin-ed back to stock (UVJFD), having issues with my SIII. Can anyone recommend what I need to do next? Do I need to be on ICS bootloader before I flash? Wow, it's been so long since I used this phone I really need some help getting it back to operational status. Any help is greatly appreciated.
[Vibrant Android Development] sada23:
New build 01/13/2014 uploaded
[Vibrant Android Development] sauron82:
From stock, root then install CWM (pm me and I can send you the two update.zips if you need them) Install latest CM10.1 official nightly (just d/l from CM website), which will update your recovery to CWM 6.x that can flash CM11. Then flash this rom and enjoy.

If there's a quicker, fewer-steps method, plz let me know.
[Vibrant Android Development] Martezgarki:
Stuck at boot animation for latest build
[Vibrant Android Development] bigtom624:
Mine did the same thing. Stuck at Vibrant logo.
[Vibrant Android Development] selmandeli:
Same here :(
[Vibrant Android Development] sada23:
New Build uploaded.

New build 01/14/2014 uploaded.

The previous build did have some boot issue. Its corrected in this build and this build boots without issues, Sorry about the previous build. I have removed the previous build.
[Vibrant Android Development] binniebin:
Well all good on my device running 130114

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Vibrant Android Development] Martezgarki:
A question here, for quiet hours settings, is there a way to mute ringing for incoming calls too? I basically want quiet hours to function like vibration mode where everything (calls, msgs) just notify me through vibration as it would be bad to have your phone ringing in a meeting.
[Vibrant Android Development] maelstromm:
Thank you for the detailed steps. I did have to add one step in between. I had to flash Fluid Kernel to bring CWM to 6.0.4.4 before I could flash CM11. Works well so far!!
[Vibrant Android Development] Stanislaus:
Hi, I'm currently on CM10.2 build 20140102 and it works great but I'm thinking of updating to cm11. I was wondering if the incoming call and the battery drain issues are still present. Thanks

Sent from my Samsung Galaxy Vibrant powered by CM10.2
[Vibrant Android Development] flapane:
Absolutely no battery drain issues as of 10jan build and Gear kernel.
[Vibrant Android Development] martabakeju:
Hello,

For some reason I don't have any GSM signal after flashing this rom. I followed the instruction in the op about copying the md5 files, but my mobile network is still not working.

Can anyone please help me?
[Vibrant Android Development] audifanatic518:
Are there any more complete installation instructions?

I'm coming from CM 10.1.3-RC2 (it's been a while since I last flashed a new ROM). Clockworkmod is giving me errors about the partitioning when I try to flash the zip file.

Thanks!
[Vibrant Android Development] Martezgarki:
Perhaps try to flash to CM10.2 before CM11. From stock I usually do Eclair straight to CM9, then CM10.2 and CM11. This gave me no problems so I assume it will be the same for you too.
[Vibrant Android Development] flapane:
It's because of the new layout. Flash twice or even thrice, it will eventually work.

I went straight from 10.1 to 11.

You may try to flash 10.2 as well, it won't hurt.
[Vibrant Android Development] cashmundy:
This works, thanks for the info. Some way of doing it without having to do a system wipe would be nice, but flashing Semaphore (for android 4.3), rebooting into recovery and then formatting everything except boot (and then of course flashing the 10.2 rom) does get the job done.

I've switched back to [MENTION=3252166]sada23[/MENTION]'s 10.2 builds (thanks again for both build series). KitKat seems to be sort of dumbed down and yet have some Google creeepiness (always on microphone listening for voice commands?) built deeper into it. For me it is actually slower than 4.3, especially browser rendering, but that could be because I'm using OpenPdroid, which doesn't work with ART, only Dalvik.

A clean install of either 4.3 or 4.4 without gapps (check out Fdroid for things like K9mail, which didn't work well on 4.4 but is great on JB and much better than the AOSP email client) is cleaner and faster and with vastly better battery life than with the Google bloat/spyware. For me anyway.

And coming soon: Ubuntu Touch or KDE Plasma Active. Enjoy!
[Vibrant Android Development] Martezgarki:
I actually find 4.4 to be smoother, but that's if you don't use the laggy/incomplete ART. It's not enabled by default for a reason.
[Vibrant Android Development] sauron82:
Wouldn't it be easier just to manually put the phone on vibrate when you go into the meeting?

Click thanks if I helped you
[Vibrant Android Development] Martezgarki:
I'd prefer my phone to go automatically vibrate mode during work hours but not only meeting...
[Vibrant Android Development] sauron82:
Then I'd suggest using profiles or Tasker. You can set a work profile that puts everything on vibrate. Tasker can do that and more.

Click thanks if I helped you
[Vibrant Android Development] WinterPhoenix96:
To add onto his suggestion, I use Llama myself for stuff like that, which is free by the way.
[Vibrant Android Development] audifanatic518:
I've flashed like 5 or 6 times with no luck. Howeve, instead of partition errors, I'm getting other errors.

set_metadata_recursive: some changes failed
E: Error in /sdcard/cm-11-20140114-SADANAND-vibrantmtd
(Status 7)
Installation aborted
[Vibrant Android Development] sauron82:
Probably a corrupt zip. Try redownloading the rom.
[Vibrant Android Development] audifanatic518:
Did that too a few times
[Vibrant Android Development] sauron82:
Try flashing Fluid kernel before flashing the rom. Flash Fluid, reboot recovery then flash the rom.

Click thanks if I helped you

Current: Galaxy Note 3 SM-N900W8

Former (but still working): Galaxy S Vibrant SGH-T959, Galaxy Ace GT-S5830D
[Vibrant Android Development] audifanatic518:
Still nothing, same error message

Here's what I did (and did previously, except without the kernel flashing, step 4):

*Nandroid backup of course

1)factory reset

2)wipe cache

3) wipe dalvik

4)flash Fluid Kernel

5) flash ROM
[Vibrant Android Development] sauron82:
Then I say go back to stock and start from scratch.

Click thanks if I helped you

Current: Galaxy Note 3 SM-N900W8

Former (but still working): Galaxy S Vibrant SGH-T959, Galaxy Ace GT-S5830D
[Vibrant Android Development] audifanatic518:
-___- I hate my life lol, just tried that too
[Vibrant Android Development] sauron82:
Wow that sucks. I'm out or ideas. Maybe the chips just don't want to be flashed anymore. I've never heard of that, but they have a lifespan don't they? I don't wanna say you might be screwed, but...

Click thanks if I helped you

Current: Galaxy Note 3 SM-N900W8

Former (but still working): Galaxy S Vibrant SGH-T959, Galaxy Ace GT-S5830D
[Vibrant Android Development] audifanatic518:
Well I can re-flash 10.1 again just fine, so I'm not sure if that's the issue (I don't flash too many ROMS anyway, this is my first one in over a year).

Here's what I did:

odin to stock eclair

install CWM via this: http://xdaforums.com/showthread.php?t=849028

flash directly to 10.1

attempt to flash to 11.0 anf fail miserably :(
[Vibrant Android Development] sauron82:
That's the same method I used lol.

One question though: Did you root first and then flash CWM or did you just flash CWM and then flash a rom? I always rooted first, then flashed CWM, then flashed the latest CM10.1.3 nightly directly from Cyanogen's website. The first time I flash it, it updates CWM and reboots recovery, then I flash it again and it installs the rom. Then I flash Fluid kernel to update CWM again to 6.0.4.4, then I flash CM11 (this rom), which leaves you with CWM 6.0.4.5. Whether you flash Fluid kernel again at the end is up to you, but I did.

If you're coming from freshly-Odined stock, and it doesn't work, then I have no idea what could be going wrong. I'm not a dev though, just an experienced flasher. I also haven't updated my Vibrant since Christmas now that I'm using my Note 3, but I will this weekend as I'm giving it to my cousin soon. So I'll let you know if I have any issues. If you get it working in the meantime though let me know what you do to get it back up.

Click thanks if I helped you

Current: Galaxy Note 3 SM-N900W8

Former (but still working): Galaxy S Vibrant SGH-T959, Galaxy Ace GT-S5830D