Originally Posted by PowSniffer0110

Wipe Data/Factory Reset then advanced and formatted from the bottom up

I went from cm7, wiped everything, flashed 16 b. It auto booted, then flashed it again, then gapps, then fixer, rebooted and is great

Sent from my vibe cm9 16b using xda premium

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.

Originally Posted by jrafael

but I have no idea where those are located.

w00t lol
another Tampa person xD

I'll read 2morrow sorry

Originally Posted by scrizz

w00t lol
another Tampa person xD

I'll read 2morrow sorry

This place is full of them!!

Originally Posted by 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/referen...arameters.html

http://stackoverflow.com/questions/9...app-is-rotated

but I have no idea where those are located.

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)

Originally Posted by 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)

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

Sent from my GT-I9000 using xda premium

Originally Posted by 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

Sent from my GT-I9000 using xda premium

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.

Originally Posted by 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.

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 ?

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?

Originally Posted by 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 ?

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?