yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] xriderx66:
Hey guys, does it look like I should save anything on here? This is my internal SD

I saved all my ROMS/Music and I still can't find where my Pics are saved...

I'm mostly talking about the stuff in the third pic. It has all that technical ROM stuff.

http://i.imgur.com/QUfOe.png

http://i.imgur.com/Fwcal.png

http://i.imgur.com/38LzJ.png
[Vibrant Android Development] samsgun357:
@x can't read screenshots???..

Look for dcim folder for pics

drool on my chin from a mouth full of jellybeans....
[Vibrant Android Development] xriderx66:
https://docs.google.com/open?id=0B51WDCqb9qiFSURqMk9MOGowSHM

https://docs.google.com/open?id=0B51WDCqb9qiFYThha1VybWE0Vjg

https://docs.google.com/open?id=0B51WDCqb9qiFZUtEZ3FRS2JLVjg

See if that works.

Also my pics don't seem to be on DCIM I'm going to go look in external SD.
[Vibrant Android Development] samsgun357:
That worked. I believe most of those documents are created during flash/boot. They aren't really necessary for phone function. They will regenerate during flash/boot if needed.

I would only be concerned with personal data and zips you want.

Also back up efs. Mine wasn't affected but better safe than sorry.

drool on my chin from a mouth full of jellybeans....
[Vibrant Android Development] xriderx66:
My EFS is backed up but can't tell which folder its inside...
[Vibrant Android Development] samsgun357:
I am looking at it from phone not PC. Like I said non of that was messed with. I long pressed folder sdcard0 with es file explorer then delete and it did its thing, none of the important stuff deleted. I actually tried to delete it again and it wouldn't allow it.
[Vibrant Android Development] xriderx66:
Yeah, EFS is in the root file /

Anyways, thanks for all your help. I didn't actually go through and delete everything, but I did clear up about 3GB by deleting stuff from some of my apps.

If you have iFunny, delete its cache. Mine was eating up about 800MB by saying every picture i've ever seen.

P.S. 6,000 posts.. HELL YEAH
[Vibrant Android Development] fernkomoyo:
Woah! Super Nice Rom... Everything working fine for me... the only thing that i need to know it's how to activate BLN..! THX
[Vibrant Android Development] xriderx66:
Hmm makelegs, I was wondering if the browser with the cherry pickings could be used on another jb rom?
[Vibrant Android Development] makelegs:
All those picks were merged...give it a whirl. I don't use it, personally.
[Vibrant Android Development] imilleson:
If you are using Devil kernel you can use the devil kernel manager from the playstore, alternatively if you are using any BLN supporting kernel then you can use NStools from the playstore to toggle blink on or off. lastly some kernels allow this to be toggled on or off through recovery (I think devil is one of them)
[Vibrant Android Development] kwartey:
overclock

hi guys, is there anyway i can over clock my cpu ,and if so how? my room seems to be a bit slow. thanks
[Vibrant Android Development] imilleson:
Read the above post, NStools gives this functionality. Be careful and do not "set on boot" unless you have tested the clocked values first
[Vibrant Android Development] Toast6977:
Is there a current list of known issues or anything? Been looking around and haven't really found too much. Haven't flashed anything above gingerbread. Been too afraid of the EU bug.

Doesn't sound like anything like that has happened with JB yet. Pretty much I have to have this phone. If I ruin it I'm screwed. I am comfortable with flashing, that's not the problem, just nervous about things like EU..

So what do you think? Safely flash JB? If something goes wrong, then return to my current Bionix 1.3.1?

Thanks, didn't interns to hijack.... just figured y'all are comfy with this rom by now..
[Vibrant Android Development] skinzy98:
You might just want to try an aokp ics build. Those are stable
[Vibrant Android Development] Hung0702:
Phone Settings?

Am I the only one who isn't able to access the phone settings (Phone > Settings)? As a result, I can't set up Google Voice as my default voicemail provider. Trying to access the settings force closes the phone app for me ("process com.android.phone has stopped").

Edit: well, I was able to use *004*xxxxxxxxxx# in order to default to Google Voice, but I would still like to be able to access my phone settings.
[Vibrant Android Development] skinzy98:
Its possibly just a bad flash
[Vibrant Android Development] ShaPrince:
I need help. I'm having wifi issues as well. I went into cwm recovery, but I don't see devil settings or anything of the sort. I also don't see an option to change wifi to strong. Please help.:confused:
[Vibrant Android Development] imilleson:
First off this only will work if you are using devil kernel. Download devil kernel config app from market and grant root access. Then find the WiFi setting I think they are under misc. Then change to strong
[Vibrant Android Development] ShaPrince:
Thanx again. Last question, any suggestions on which devil kernel I should use and if at all possible, could you provide:D the link. It would be greatly appreciated.
[Vibrant Android Development] imilleson:
Main repository http://rootaxbox.no-ip.org/derteufel/

This is the one I am using with CM10 and it rocks Devil3_1.1.2_JellyBean_vibrant_CFS_BLN_CMC_20120806.zip
[Vibrant Android Development] lloydb9382:
I survived that bug thankfully.. I used Eugene froyo to odin to with a new 8gb SD .. then I used lidroid to partition my SD .. after l lidroid about twice I had access to my SD. Then flash ICS
[Vibrant Android Development] dE.fUsEd:
Running the latest SKANG. Reboot to Recovery doesn't seem to work.

Just reboots normal.

:(
[Vibrant Android Development] imilleson:
That is odd. What kernel? Try Devil for JB
[Vibrant Android Development] dE.fUsEd:
Not sure what is going on. Maybe it's a software issue. Was using stock kernel with rom, but I can't even boot to Recovery using adb.

It just reboots as normal.

Tried with Rom Manager too. Can't get in at all. I want to flash Devils Kernel but I can't get in to do it. :o

---------- Post added at 01:08 AM ---------- Previous post was at 12:16 AM ----------

Finally got in. Every time I load the newest Devil Kernel, the phone boot loops and has to be restored to odin. :(
[Vibrant Android Development] Exel:
Working great, thanks.
[Vibrant Android Development] zxevik:
most recent version just randomly shuts the phone off after a few minutes of screen being off.

at first i thought it was the holo locker I had installed. came from a fresh odin and worked my way back up to jb, tried 3 other roms and have used other versions of this rom in the past and they were not having this problem. :/
[Vibrant Android Development] omnifarious:
I haven't heard much of this rom since I initially tested it. I was wondering what issues other testers had/have faced on newer nightlies. Anyone care to share?
[Vibrant Android Development] Exel:
I flash these sometimes because they get releases faster than cm10 nightlies. (Sometimes.)

Runs great and has nice cherry picks!
[Vibrant Android Development] trippmcnealy:
Running 09/07 with Devil kernel and this thing is fast and smooth!

Great work!
[Vibrant Android Development] gunks:
Tried to wipe battery stats via recovery and it screwed up my IMEI somehow and would reboot a min or two after booting over and over. Tried flashing another kernel and lots of others things, nothing worked. Running a full wipe now.
[Vibrant Android Development] makelegs:
Newest build = datadata
[Vibrant Android Development] hurtz777:
Hellz yeah datadata is back. Should be able to use the latest Devil HB kernel from HB0923 rom zip since it runs on datadata also.
[Vibrant Android Development] makelegs:
Anyone having screen rotation issues on latest build(s)?
[Vibrant Android Development] hurtz777:
Devil HB 1.5.3 HB datadata kernels

Makelegs I have no issues with screen rotation on the latest build. I am currently running the Devil HB 1.5.3 datadata kernel on cm-10-20120925.0004-vibrantmtd and it works perfect as well as no Play Store issues. I just extracted the boot.img from HB 0925 and injected it into the the Jelly Bro 0925 rom zip. I have also made some Devil HB 1.5.3 cwm flashable zip files that shoudl flash fine on top of Jelly Bro cm-10-20120925.0004-vibrantmtd if that is your flavor and I have attached them to this post. Great job makelegs! This CM based rom is definitely every bit as fast as Slim Bean 2.5v if not possibly smoother with the Devil HB 1.5.3. Thanks again makelegs for a nice smooth release and bringing the much needed full datadata back for maximum performance! No bugs to report so far, but I will let you know if any arise.

EDIT:

I just updated the two Devil 1.5.3 HB datadata kernels because for some reason I had the wrong boot.img in them so just redownload and flash th new one. ;-(
[Vibrant Android Development] makelegs:
Thanks man....had a "screen rotation ssue" report on twitter. I figured I'd bounce it off the A-Team in here. It had to have been an anomoly. Thanks for the confirmation! :)
[Vibrant Android Development] cancrippler:
Just tried this ROM again after months of cm10 nightlies. Wow, no new kernel needed! This thing is dripping with butter.

Thanks for really delivering!
[Vibrant Android Development] samsgun357:
Thinking about jumping over to this from hellybean. HB has been great, just looking to change the flavor. How is jellybro in comparison to HB? Not trying to hijack the thread, just looking for a little info. Thanks
[Vibrant Android Development] corpsetomb:
I'm in the same boat. Just flashed this tonight, coming from HB. So far my initial reaction is that it feels smoother and faster. I am going to keep it for a few days and test it out.
[Vibrant Android Development] samsgun357:
Keep me posted over the next few days! As I said before I'm really dialed in on HB. This is the only other JB ROM that I'm truly interested in testing. Thanks corpse!

sent from the depths of helly bean
[Vibrant Android Development] hurtz777:
Both JellyBro an HB 0927 run identically smooth for me now that they are both on datadata and that is running the same Devil 1.6.1 VC kernel. The main reason I choose HD 0927 is because if the center clock on notification bad and the aroma installer is sexual. I would also say that HB 0927 should be a little more stable because it doesn't have as many untested cherry picks. All in all you can't go wrong with either FE's CM10 Nightly 0928, HB 0927, or the latest Jelly Bro with Devil 1.6.1 JB/HB datadata kernel. I am glad to see that all the roms have gone back to the faster datadata and vsync enabled which definitely speeds everything across the board, Now if we could find a way to get some ics 4.0.4 battery and GPS and we would be all set! Mad props to makelegs for including the cherry picks and giving us a different choice for JB rom.
[Vibrant Android Development] Sugartibbs:
+1 been bouncin back and forth too close to call, Probly need to be off line for a week, seems Im flashin a new build every nite.
[Vibrant Android Development] corpsetomb:
Sams,

I don't know if it's just specific to my phone, but Skank has been A LOT better on battery life for me (without calibration and moderate to almost heavy use, about 24 hours), also (up until now, fingers crossed) I haven't had the Android OS issue that seems to eat up battery. I am using it with stock kernel and Justunbeans inverted gapps as of right now. GPS locks after reboot, haven't tried it yet after deep sleep. It also seems to keep a good amount of RAM free. It is consistently smooth, whereas HB felt a little bit (very little, but noticeable to me) sluggish. I'll keep at it and let you know if anything changes.

Sugar, I know what you mean, I think I flashed pretty much all the JB roms within a 3 day period! lol.
[Vibrant Android Development] samsgun357:
Thanks corpse. I flashed acid audio mod tonight but it wouldn't boot past animation. I reflashed helly without a wipe and now I'm getting some errors. So I will probably be flashing this sooner than later. Thanks again for the update!

sent from the depths of helly bean
[Vibrant Android Development] corpsetomb:
So I have read through and searched past issues through cyanogenmod, but haven't really found a solution to a small issue I've been having.

I can only play mp3 files through any music player of choice, however if I try to play wav files, it is all static and distorted. Does anyone have a fix for this? Being a musician I get a lot of our band music in wav format before it becomes mp3. Any help is appreciated!

---------- Post added at 06:37 PM ---------- Previous post was at 05:56 PM ----------

Anytime!
[Vibrant Android Development] gunks:
Looking forward to the next release! Thanks makelegs.
[Vibrant Android Development] Moped_Ryder:
Anyone try the latest?
[Vibrant Android Development] gunks:
I'm on the latest... Been using the nightlies for the last 2 weeks... Great rom. Works good with Semaphore.

edit: One feature that I wish was included is the option to mute the camera capture sound. Other than that its awesome.
[Vibrant Android Development] makelegs:
Coulda sworn that feature was in there already.... /shrug

I'll look into it. If there is a commit, I'll grab it. I start to lose track, honestly. :)
[Vibrant Android Development] josh2020glacier:
BIG THANKS! This Rom is one of the smoothest tons for gaming. Good looks again.
[Vibrant Android Development] makelegs:
Glad some of you still enjoy it!
[Vibrant Android Development] josh2020glacier:
Yes I rock this as daily. This Rom and cm10 only ones that run MOST WANTED game the best.
[Vibrant Android Development] mohamobo:
Keep up your good work for the community :good:
[Vibrant Android Development] josh2020glacier:
This is why I use this ROM. Pretty stable and smooth plus I like some features not all the features the other ROMs have. I don't need all that extra stuff just need my clear all button and theming stuff. Thanks skank!
[Vibrant Android Development] explorer-10:
On this rom, is there a way to enable led flashlight? I see an option, but it is greyed out. I installed this rom on my bro's phone along with the latest GApps, but with stock kernel, whatever kernel came with the jellybro rom(probably not stock though, but you know what I mean)
[Vibrant Android Development] explorer-10:
Also, how do I install an app from explorer-like apps if I can't press the "install" button? Every other action works like "cancel" and "show/hide info" but install won't work. What can I do???
[Vibrant Android Development] samsgun357:
Led flashlight is pointless on the vibe, there is no led flash on it. I'm not quite sure what you mean you can't press install. If you are referring to installing apk's make sure you have unknown sources √ in settings>security. Some apk's are system apps and won't install that way. You must move the apk to

/system/app and fix permission 644, rw-r--r--.

As far as kernel's, semaphore 2.latest.v or devil3 jelly helly kernel should work fine as long as this ROM has same partitions as CM10.

I bought this from Sky Mall.
[Vibrant Android Development] explorer-10:
By "can't press install", I meant that after attempting to install a non-system apk, I see a cancel button and an install button. Pressing the cancel button indicates that I can press it, showing the highlighted blue color while pressing the install button does not. No matter which direction I rotate the screen, I cannot for the life of me press that install button no matter what. It's there, but I can't press it with the blue showing up, therefore it's not letting me press it. At first, I thought that maybe his screen had too many fingerprints, so I cleaned it. No do. I rebooted into recovery, wiped both cache and dalvik and fixed permissions, no do either. Here's what I mean from my phone where the blue on the "install" shows up, as on my brother's, it does not.
[Vibrant Android Development] Dougfresh:
What's that circle image between the N and the ST in install.... also remove the antivirus
[Vibrant Android Development] explorer-10:
It's the show touches input thing, not really sure why I enabled that for and my bro's phone is a vibrant, I'm just showing the example from my nexus s. I think I prefer to keep the AV.
[Vibrant Android Development] Dougfresh:
Man, redo everything again. Recovery, factory wipe, format system, reflash the rom and gapps if applicable and start Fresh!!!! When in doubt fully wipe :cool:
[Vibrant Android Development] mohamobo:
Waiting Jellybro CM10.1 love
[Vibrant Android Development] Moped_Ryder:
Uploading: update-cm-7.2.0-RC0-Vibrant-KANG-signed.12112011-1323

Now - will post when completed.
[Vibrant Android Development] atinm:
Just to make sure - you're not using our kernel images are you? If you didn't build the kernel, you are - otherwise the kernel file in device/samsung/vibrant would be created by you. We would appreciate it if you would build your own from source if you are - the kernel images have one of the CyanogenMod team member's names on them (I don't know if it is mine or pawitp's), and it would be better that Kangs used their own (your's ideally) instead because we don't want to be associated with the Vibrant while there are issues with E911. Thanks.
[Vibrant Android Development] Moped_Ryder:
Honestly I haven't edited it one bit. Its was in the same folder from he OP's original link. I just was lucky enough to download it before it was deleted.

Since it has your kernel I wont post it. I'm just now starting to learn how to compile kernels.
[Vibrant Android Development] makelegs:
That pretty much explains the Euroskank decision to simply delete the folder. The primary issue is fairly serious and I don't blame any Dev for wanting to disassociate himself, under the circumstances. I don't own a vibrant, either, and I haven't learned how to compile kennels. I'm just a kangbanger, so until the situation is resolved or circumvented by cm9, my efforts will remain focused on captivate and fascinate....unfortunately.

In case anyone did not clearly understand.....I interpreted Atinm's post as a request to NO LONGER POST links to the previous kang. Your compliance with his request would be greatly appreciated.

I suppose you could PM each other though ;-)
[Vibrant Android Development] betam4x:
Ok hold up a second. I've heard rumors of there being a 911 issue with the vibrant...would someone please explain to me what this issue is (in technical terms, hint: I'm a programmer) and WHY that the CM team would decide to abandon the platform rather than fixing the bug? While i've not been involved in android development at this point, I've done plenty of kernel mods/hacks in my lifetime, and if needed i will get my hands dirty.
[Vibrant Android Development] jrafael:
you might want to start reading from here

http://xdaforums.com/showthread.php?t=1387314&page=2
[Vibrant Android Development] Jasonhunterx:
We should just start a thread to get this thing fixed so it can be one spot where everyone can contribute!
[Vibrant Android Development] atinm:
The E911 calls are a special type of call that have to circumvent SIM card validation and Samsung modified the code path for emergency calls to handle this by adding a special command to their RIL, but only for Vibrant. After we figured this out, we were able to make 911 calls, but that wasn't enough. It turns out that on connection callback, the Samsung RIL then goes all over the framework enabling audio routing, turning on GPS etc - none of which is done in a standard way and we don't have the code that actually does it as it is framework code that is not released by Samsung. The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail and no one on the team actually having a Vibrant made it that much harder to figure out what is going on.

As it was, I was the only one still working on it, but then another Vibrant developer got involved and then he decided to start throwing F bombs at me and threatening me when I got tired of his snide comments about CyanogenMod not releasing Hercules repositories that I don't control and I decided to stop supporting Vibrant. As no one on the CyanogenMod team is working on the Vibrant (nor likely to start), and as not having E911 is a very big deal that we really don't want to deal with, CyanogenMod decided to stop supporting Vibrant and it has been taken off the nightly build queue and the updates have been deleted.

The code is still in the repositories, but it requires someone who knows what s/he is doing to build it as none of us on the CyanogenMod/teamhacksung teams intend to do it again (and it is unlikely any one of us will actually work on it). The Galaxy S and Captivate code base is moving on, so any Vibrant developer will also need to keep track of changes that are happening there and pull them if they are applicable to the Vibrant because we aren't doing any testing on Vibrant and therefore may break things inadvertently.
[Vibrant Android Development] awolbrin:
**** t-mobile

I'm so sad to read what your saying atinm...

you did so many great thing from vibrant users.

what can we do? how can we make t-mobile/Samsung release the necessary code?
[Vibrant Android Development] CM Wave:
So, basically, if Samsung releases code or someone comes up with a working fix, the CM team will still abandon Vibrant owners. Nice. Thanks.
[Vibrant Android Development] bobshute:
The epic had the same problem. Cm wanted to fix it and did 3 days ago. The fix won't work on the vibrant (cdma vs GSM) but the same methods to find a fix would. As far as I can tell cm just doesn't want to support the vibrant anymore.
[Vibrant Android Development] atinm:
You're welcome to take it up yourself. There is no reason for me or coolya (the only other developer who did any Vibrant specific work on this, and he left developing for the Vibrant before I did) to want to work on it - and no one else on the CM team has ever worked on it.
[Vibrant Android Development] atinm:
Actually no - we already tried all the same things and the issue is quite different because CDMA doesn't use SIM cards - therefore they needed to *avoid* calling the code that GSM uses and that works on Galaxy S and Captivate (and the bug fix for the Epic4g was to not continue with dial processing the way GSM does for Emergency Calls because it doesn't need all the SIM validation etc). The issue on Vibrant is that it *uses* GSM and needs to have the same code work, and it doesn't due to Vibrant specific things in the framework that we haven't solved.

Again, if others want to work on the Vibrant, the code is available on our repositories - have at it and recruit as many developers are you want to work on it. We do not discourage anyone else from working on this, and neither will we ignore any fixes to this issue if someone else makes the fixes. However, I am not going to spend any time working on it, and no one besides me has worked on it in months anyway.

This is my last post on this thread - I don't want to keep harping on the fact that others can continue development if they so desire, it is just CyanogenMod (and specifically me, but since I'm the only developer that was doing any work on the Vibrant, it effectively means no one is now) that will not continue supporting the device due to the E911 issue.
[Vibrant Android Development] CM Wave:
One week it was no Vibrant support because the hardware was weird. The next week it was no Vibrant support because you don't have one. The week after that it was no Vibrant support because someone on the internet hurt your feelings. As a Vibrant owner that's been told 1001 different stories, I'm just glad you finally settled on an excuse.