yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] FaultException:
I usually heimdall or odin back to stock firmware -> flash overstock -> flash cm7.

Overstock will not boot for you but you let it try to boot for a minute or two to convert your partitions. After, you can pull the battery, button combo into recovery, and flash CM7. It may take a few seconds for it to go into recovery and may look like it's just stuck again, keep holding the combo. If you get into recovery but get errors, you didn't wait long enough in the first boot before rebooting.

Overstock Kernel:

http://cmw.22aaf3.com/aries/sgh-t959/root/Cmenard-overstock-vibrant.zip

Here are the stock .pit and .tar for Odin:

http://files.androidspin.com/downlo...in/samsung/vibrant/&file=s1_odin_20100512.rar (unzip this rar and take the .pit)

http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&file=T959UVJFD.tar (leave this tar zipped)

.pit goes in PIT field of Odin

.tar goes in PDA field of Odin
[Vibrant Android Development] PowSniffer0110:
Thanks! Didnt see all this but def helps. I thinnk Im good on JFD right now and bout to flash 16B and GAPPS hopefully all is well. NOW my real question is why did formatting boot (which is what I assume it was), make me not be able to boot into recovery? I had the GLITCH recovery btw
[Vibrant Android Development] FaultException:
How did you format?
[Vibrant Android Development] PowSniffer0110:
Wipe Data/Factory Reset then advanced and formatted from the bottom up
[Vibrant Android Development] Dougfresh:
It doesn't matter if you format boot but keep in mind that you must flash a kernel or a rom immediately afterwards
[Vibrant Android Development] mr_psycho:
First, use heimdall for this procedure. Grab a "boot.img" from any cwm flash able zip like glitch v14. In heimdall, add a kernel and then add a recovery. For the file, choose the "boot.img" you extracted for both. Flash, and you will now be able to access cwm recovery with the finger combo.

Btw, you will need a pit file to load first for heimdall 1.3.x before you can choose a kernel or a recovery to flash. I think from download mode, heimdall can extract your pit. Otherwise, use the pit you already have from other Odin packages.

MP

From Porta Hell.

Sung of Sam Vibrant, T-Mobile USA
[Vibrant Android Development] jrafael:
@FaultException

I have a regular 3g Vibrant and I did the FFC mod using a Vibrant 4G camera.

The rear cam work perfect in any rom (samsung froyo/gb, cm7, cm9), now the front camera works correctly only if I use a vibrant 4G based rom (bionix frost), if I use any other rom the front camera is always 180 of the actual orientation (rear cam works correctly).

Can you direct me to what values to change or play with ?

BTW: I don't know any programing but I know how to decompile an app and do some minor smali edit.

Thanks for reading.

PS: I have been looking around and found this

http://developer.android.com/reference/android/hardware/Camera.Parameters.html

http://stackoverflow.com/questions/9080911/android-camera-in-my-app-is-rotated

but I have no idea where those are located.
[Vibrant Android Development] Pielvrx:
I went from cm7, wiped everything, flashed 16 b. It auto booted, then flashed it again, then gapps, then fixer, rebooted and is great
[Vibrant Android Development] jnusz:
Just wanted to say that I'm running build 16B (using the Icy Glitch V14 B5 kernel) and this is the smoothest my phone has ever ran. I can't wait until everything else is implemented, i'm sure there are options that haven't been put in that will let me make it run even MORE smooth.

Thanks for your hard work guys.
[Vibrant Android Development] scrizz:
w00t lol

another Tampa person xD

I'll read 2morrow sorry :eek: :(

:D
[Vibrant Android Development] Dougfresh:
This place is full of them!!:D
[Vibrant Android Development] FaultException:
I don't know for sure.

The Camera.Parameters would only affect the app that uses those parameters. Any other app would still be flipped.

A start would be to examine an open source Vibrant 4G ROM.

Also, are you pushing the I9000 camera files or the Vibrant 4G camera files? I believe the wiki says to push I9K files, but if you're using a V4G camera, you might try that. (If you bootloop, flash the ROM over itself to restore the original ROM files)
[Vibrant Android Development] jrafael:
Thanks for responding.

I'm using the libs from i9000, I can't use the v4g camera because its tw based (gb 2.3.6), unfortunately there is not aosp for for the v4g atm :(
[Vibrant Android Development] FaultException:
Really, no AOSP-based ROMs for V4G, just not that popular, eh?

As for the camera files, I mean the proprietary files, for example, the GPSD blob from this ROM is one that was used in CM7 (Gingerbread) in the past apparently, and there is no official proprietary blobs for Vibrant for ICS being that we haven't even got official Gingerbread.

But I can imagine there being some differences in the way Android tries to interface with the blob or the blob tries to interface with Android versions.

But that could definitely be a problem, being that you're running phone A with B's camera blobs, with C's camera.
[Vibrant Android Development] jrafael:
I look at their gingerbread blobs and there are nothing like I9000 GB.

under system/lib:

libarccamera.so

libcamera.so

libcamera_client.so

libcamera_eclair.so

libcamera_froyo.

libcamera_gingerbread.so

libcameraservice.so

libcamerafirmwarejni.so

libseccamera.so

libseccameraadaptor.so

I you want I can take my ffc out and mailed to you, so you can test further ?
[Vibrant Android Development] Danstek:
When I'm on wifi, data connection keeps dropping for some reason. It cuts out on both wifi and cellular network and has to constantly reconnect. Cellular network works fine with wifi off though. Is anyone else experiencing this or is it just me?
[Vibrant Android Development] FaultException:
Nah.

If you can, could you find an old sixstringsg CM9 kang (before he started doing it from source...), one that is the I9K CM9 with Vibrant stuff added, can you try the FFC with that and see if that works?
[Vibrant Android Development] sixstringsg:
http://androtransfer.com/vibrant
[Vibrant Android Development] FaultException:
Thanks! :D

Try that out jrafael if you could please.
[Vibrant Android Development] charkey:
I was using sixstringsg's Hacksung builds prior to 16b and tested FFC does indeed work on my camera granted I have the first revision of the FFC if that matters.
[Vibrant Android Development] FaultException:
Are you using a Vibrant 4G camera, or an I9K one?
[Vibrant Android Development] charkey:
I'm using the first revision of the i9k one.
[Vibrant Android Development] FaultException:
Ah... yeah, the guy having the problem has a V4G camera, although I'm not sure if others with I9K have the same flipped problem, do you?
[Vibrant Android Development] FaultException:
For anyone with the mute/unmute bug, install this CM9 Phone APK that has ngiordano (Nelson) and neobuddy89's mute/unmute fix from ICS Passion.

http://xdaforums.com/showthread.php?t=1524744
[Vibrant Android Development] charkey:
I haven't tested out pushing the files yet from the CM9 i9k build. Do you know what files we need to push over? I've done it on the CM7 i9k build and it was only a single file called libcamera.so. FFC image was fine with CM7; yet to find out with CM9.
[Vibrant Android Development] jad3675:
FYI, the mediafire link isn't working.

John
[Vibrant Android Development] Richcar:
yes it's working couldn't get it to work on my phone but it working fine on the pc .are you trying to download on your pc or your phone ?
[Vibrant Android Development] jad3675:
Well, it's working now. Didn't work on phone, or two different computers.
[Vibrant Android Development] PowSniffer0110:
Is this your sorce for vibrant? Or..? Cuz I'm looking for the same thing as the other Guy. Need to implement the ffc fix from back in cm7 or whatever so my ffc is flipped and screwed. Thanks a bunch already
[Vibrant Android Development] sixstringsg:
Those are builds. Normal people out source on github, and even if it was a tarball, it would be a tar, not a zip.
[Vibrant Android Development] charkey:
I believe we had this bug in previous CM7's as well but was later fixed. I usually don't get voicemails but I received one earlier this week and the voicemail notification will not disappear even though I have gone through and deleted all my voicemails.

Anyone having similar problems and have a possible fix for this?
[Vibrant Android Development] FaultException:
The notification in your bar? Do you mean it keeps coming back each reboot or it doesn't go away in the first place?
[Vibrant Android Development] charkey:
Yes in the notification bar. It doesn't go away even after rebooting. I've made sure that I've deleted all my voicemails too.
[Vibrant Android Development] jrongi1:
Try this... Call your vibrant from another phone and leave new message, then check and delete it the icon should go away.

vibrant icz

360° Productions
[Vibrant Android Development] charkey:
Thanks for the suggestion but that still did not solve the problem. I have the TMobile Visual Voicemail app installed on my phone and was able to remove the notification from the notification bar for the visual voicemail but was unable to remove the actual voicemail icon by calling into the voicemail service and then listening and deleting the voicemail.

Is this working for you?
[Vibrant Android Development] jrongi1:
I quit using VM back on miui gb because of the same problem.

vibrant icz

360° Productions
[Vibrant Android Development] charkey:
This is a pretty solid release aside from the very minor issues. Will this ever go to the automatic nightly builds and be recognized on ROM manager for updates just like how CM7 is?
[Vibrant Android Development] FaultException:
Eventually, I imagine, yes.

Some CM9 devices are already being built it looks:

http://get.cm/?device=galaxys2
[Vibrant Android Development] Smartassassin:
Exited about build 17

Sent from my phone, not yours.
[Vibrant Android Development] jnusz:
yea, I can't wait to see all the stuff that's been implemented since this build. Really can't wait for an official CM9 nightly.

I know I know... and I do know, so I won't ask for an ETA ;)
[Vibrant Android Development] FaultException:
Lol. I didn't even know that 17 was out... will build today.
[Vibrant Android Development] Smartassassin:
perfect, thanks man

Sent from my phone, not yours.
[Vibrant Android Development] jnusz:
SWEET! Thanks FE, I look forward to seeing what's been implemented. I'll be checking back later this evening when I finally get home ;)
[Vibrant Android Development] FaultException:
Build 17 up, not tested.
[Vibrant Android Development] Linnel:
So, has it been addressed yet that Call blocking doesn't work? Selecting a contact and checking "send to voicemail" does nothing, and there is no option to block numbers who aren't in contacts.

Also there is no longer a charging state when phone off, inserting a cable just boots into phone, but I'm sure that's been noted already.

EDIT:This was in 16B, I'll try 17 tonight.
[Vibrant Android Development] Smartassassin:
Has the framework changed or will 16 themes still work on this!?

Sent from my phone, not yours.
[Vibrant Android Development] FaultException:
I don't know, you can always try.
[Vibrant Android Development] FaultException:
Didn't even know about that, I just compiled it from synced source after learning that 17 was out :p

If it still does it in 17, let me know and I'll add it to known issues, and tell pawitp.
[Vibrant Android Development] jnusz:
Just flashed build 17... So far so good. Just got done charging to 100% and resetting battery stats so I can get a good read on the base kernel before doing any modding except my screen brightness.

Thanks for the build FE.
[Vibrant Android Development] manjish:
thanks FE......17 is super smooth and bugless.....great job THS
[Vibrant Android Development] traicer:
gps working?
[Vibrant Android Development] jnusz:
My GPS locked just fine, even after deep sleep on the kernel that came packaged... Now that I've given it a full day's use I'll be switching to the Icy Glitch kernel. ;)
[Vibrant Android Development] Linnel:
Flashed. Build 17, send contact to voicemail still doesn't work. I believe this would actually be considered a bug.

Nevermind I dislike the lack of a blacklist of numbers not in contacts, nevermind the fact when the phone is plugged in from off, it no longer has a charging state, nevermind my GPS still refuses to activate, and even my mobile network location seems less accurate (likely unrelated)...

Also the generic boot animation is obscenely bright and colorful. But none of these are really "bugs" with the firmware cept the issue on top. I'd love to flash other builds, but this is actually my daily use phone, so I try to keep flashing to a minimum.

Side note, when I flashed from 16B to 17, some, but not all of my gapps disappeared, as did some apps that aren't gapps, untill I flashed the latest gapps package, when they all came back. Odd behavior, not a bug.
[Vibrant Android Development] FaultException:
Thank you for letting me know, I'll add the contact issue to the known issues list and I've notified pawitp.

I've also asked pawitp to confirm whether the charging state missing is present in the Galaxy S build.
[Vibrant Android Development] FaultException:
Confirmed. Off-mode charging is broken on Vibrant specifically.

Linnel, or anyone else, can you confirm whether it still charges while the phone is off and just won't display? Or if the charging is completely broken while off?

Also, Linnel, what kernel are you using?

My Vibrant is out for USB-port repair right now so I can't test it.
[Vibrant Android Development] Richcar:
Hey FE, where can i get the stock kernel that came with this rom,sorry if it has been posted already but i could'nt find it .thanks.....
[Vibrant Android Development] FaultException:
Stock kernel is specific to CyanogenMod Aries ROMs and is not provided on it's own that I know of. To go back to stock kernel, you can always flash the ROM back over itself, you might have to reinitialize Google though.
[Vibrant Android Development] Richcar:
ok thanks.......
[Vibrant Android Development] Pielvrx:
Fault, your a cool Dev. You seem to be very prompt with the replies and you seem to handle the sarcasm with professionalism. Anyways thank you.
[Vibrant Android Development] Smartassassin:
I am getting some insane battery with this rom. Great work guys

Sent from my phone, not yours.
[Vibrant Android Development] Linnel:
Everything I'm using is from your kang of CM9 BUILD17.

What happens is that when its off, rather than boot into charging, it boots into the phone. Which I suppose means its not broken, why I waited so long to report it, I mean obviously in the phone state it charges fine.
[Vibrant Android Development] FaultException:
I've added it to the known issue list.
[Vibrant Android Development] Linnel:
Its not that its broken, its that it doesn't exist, when in the off state, you plug the device in, it boots as normal, there is no off mode charging state anymore.
[Vibrant Android Development] FaultException:
Corrected.
[Vibrant Android Development] Pielvrx:
But damn it the pig mode is gone FaultE. It's gone...lol ;)
[Vibrant Android Development] FaultException:
The pig mode?
[Vibrant Android Development] core123:
Love this rom so far no problems. GPS even working better than it usually does thanks for all your work!
[Vibrant Android Development] ginzberg:
I just saw that the Epic 4G's CM9 build went beta... a lot of their work would be found in our future builds as well, right (both aries?)? Noticed two interesting things on their blog (http://epiccm.blogspot.com/). 1) Dock Audio support is in beta0, I had read that this was not brought in to CM7 purposefully, so it's a welcomed surprise in CM9 and 2) Mention about battery drain potentially being related to phone's camera process not terminating... wonder if that affects us too in some cases.
[Vibrant Android Development] sixstringsg:
The Epic 4G is so different from the Vibrant, it's ridiculous. I'm pretty sure they're not even part of THS, but I'm not positive on that.
[Vibrant Android Development] FaultException:
If they submit their common CM9 work (disappearing media, etc) into THS and CM repo's, then it will make it's way into this build.
[Vibrant Android Development] Pielvrx:
Lol, sorry I was "sarcastisizing" linnel. It was suppose to be "off mode"
[Vibrant Android Development] Sincitybronze:
Damn this rom is legit.13 hours of heavy use without calibrating and 35% battery left. Glitch kernel works great with this. Only issue I see is auto brightness changes too often.
[Vibrant Android Development] jzero88:
Hell ya. Batter life is insane. And this Rom is butter!!
[Vibrant Android Development] jnusz:
On the battery life issue. I seem to be getting less battery life out of build 17 than I was getting with Build 16... It seems that the Android OS process is showing even more usage than it was with build 16.

I know that this reading is showing incorrectly, but with build 17 it's showing even greater usage and it appears that at least the increase is correct as I lost like 20% overnight last night. CPU Spy shows that I was going into deep sleep, but the battery stats showed that it was coming awake periodically. (not sure why, have Advanced Task Killer killing ever 1/2 hour and Juice Defender (free) doing it's basic stuff. Might be heading back to build 16 just to try to confirm, but that will have to happen later in the day.
[Vibrant Android Development] nuwanmw1988:
this rom is pretty solid.Thanx FE
[Vibrant Android Development] charkey:
Android OS is showing high battery usage between builds 16 and 17. I know this also varies across phones as it depends on what applications are installed but what's a good way to debug what exactly is consuming battery power? Can this information be debugged from the LogCat?
[Vibrant Android Development] FaultException:
Hmm... About Phone > Battery Usage? I guess there's a known issue about Android reporting higher, but that was in 16 too.
[Vibrant Android Development] charkey:
I guess my question was to find out the breakdown of what exactly the processes in Android OS is that's causing anywhere between 10% and 70% of battery usage.
[Vibrant Android Development] mohamobo:
Anyone try this on CM9?

http://xdaforums.com/showpost.php?p=23275045&postcount=1
[Vibrant Android Development] Sincitybronze:
Baseband in settings indicates ka7. Does this mean the modem is also ka7?
[Vibrant Android Development] chrisjs81:
Awesome ROM, definitely the snappiest so far.

I upgraded directly from Bionix-v, without much issue. First flash installed an updated CWM and then started the Vibrant boot loop, pulled the battery and 3-buttoned into the new CWM, flashed again and it was all updated.

GPS not working very well though. I'm having the same problem others have run into where the GPS just disappears after the phone has been up for a while.

The Glitch kernel made no difference, the borked yagf2 made no difference. The full yagf2 made GPS lock speed *much* faster but it still only works after a reboot.

Adding in the Froyo libgps.so and gps.bravoc.so also does not seem to help.

Disabling the notifications for the built-in messaging app doesn't seem to stick after a reboot, but I haven't tried to clear data or fix permissions yet.

Still, I've experienced no lag and no force-closes so far. Much better than with my previous rom.
[Vibrant Android Development] FaultException:
CM9 off mode charging seems to work for me. Although I'm not sure how old the CM9 update in my sd-card is...

Can anyone else try this for me please?
[Vibrant Android Development] xriderx66:
Fault, Just curious I just checked out the Known Issues list, and well.. Most of the ICS roms already here such as AOKP, AOSP(passion,slim etc) have most of the issues that CM9 has fixed? Why do you guys not ask implement their fixes onto CM9?
[Vibrant Android Development] FaultException:
I'm just the Vibrant maintainer :p I haven't been contributing much or at all to common bug fixes. In fact, the known issues list was pulled from the Captivate's article.

For all I know, it could be something we're doing wrong, and they might not have even had the issue in the first place.
[Vibrant Android Development] CTown:
I can confirm that off mode charging works. Also I can access both /mnt/sdcard and /mnt/emmc through OI File Manager!
[Vibrant Android Development] jnusz:
FE, Build 15 shows that the mute/unmute issue was hopefully fixed, I just had a call last night and another this morning that I had to mute/unmute. The funny thing is that my wife (which is who was calling) knew nothing about the issue specifically said, 'it sounds like you're in a tunnel'. LOL

But mute/unmute took care of it. This is on build 17 with Icy Glitch v14 b5.
[Vibrant Android Development] FaultException:
Thanks.

I guess the "hopefully" wasn't true then. :p -- I'll add it to known issues, thanks.
[Vibrant Android Development] jrongi1:
I know that it's annoying but lets not beat this bug to death, remember that the last fix caused the 911 problem that caused CM to drop the vibrant.

@fault thanks again for your time and effort as official maintainer.

vibrant icz

360° Productions
[Vibrant Android Development] Pielvrx:
Hell ya. Thanks again Fault for your support. U da sh*t
[Vibrant Android Development] charkey:
What's the method that everyone is doing to enable FFC? What files are you pushing from the i9K build to the Vibrant?
[Vibrant Android Development] Richcar:
Go here and copy the ffc files from post 234 and flash it . http://xdaforums.com/showthread.php?t=1512518&page=24
[Vibrant Android Development] jvpde:
Once CM7.2 Final lands, will we be getting formal nightlies for the Vibrant?
[Vibrant Android Development] sixstringsg:
None of the Galaxy Devices are officially added to the CM repo for ICS yet, and we don't really know when that will happen. It doesn't have to do with CM7.2 though.
[Vibrant Android Development] charkey:
Thanks for that Richcar. It looks like there's only 2 files that's needed to ADB Push over to the phone: 1) camera.aries.so and 2) camera.goldfish.so

Tested it out and so far so good.
[Vibrant Android Development] Sincitybronze:
Is anyone using the Aries phone.apk to deal with mute/unmute problems?
[Vibrant Android Development] a2296455:
Hey Fault it sounds like you are on top of it, but there is already a ROM with an excellent Kernel...and they want to contribute back to CyanogenMod and help you out with CM9. They have already done most of the work, now it just needs to be incorporated into CM's repo..

http://xdaforums.com/showthread.php?t=1362961
[Vibrant Android Development] FaultException:
Where did they say that?

Also, one thing to consider is, how did they get those things to work?

Quote from CM Development Q&A:

ICS Passion uses a hacked phone apk to try and solve mute/unmute, while I'm trying to solve it in libaudio, even if I don't know the reason that a certain statement is causing it, it's still better than hacking it to mute/unmute at the apk level.