yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] sixstringsg:
Once device trees and such are pushed, how many would be interested in nightlies? As of now, build 14 only has 53 downloads. At that point, it probably wouldn't be worth the bandwidth costs to upload nightlies, but we'll see.

Edit: I'll also have to look and see at the end of the month how much bandwidth I'm using. I might have enough to be fine without paying extra, we'll see.
[Vibrant Android Development] mohamobo:
I am interested.
[Vibrant Android Development] Dougfresh:
Six the thread is under sam 9000 themes and apps attached is v3.0 but I traditionally use v5.0 which I also DL'd.

http://db.tt/BC8lAmlo

Thanks my man!

Edit this is v5.0 alternate batt mod

http://db.tt/U9fKwOSr

V3 is a ring no #'s and v5 is big #'s

---------- Post added at 10:44 PM ---------- Previous post was at 10:07 PM ----------

I just extracted the systemUI.apk from one of those links I provided and renamed the originally one .bak and pushed it onto system and set permissions,cleared cache and dalvik and I'm golden....
[Vibrant Android Development] sixstringsg:
Yeah, that's fine. Basically his script checks to see of you're an i9000, and you're not. If you get tired of doing it that way, bug him to add Vibrant, or I can make a zip for you.
[Vibrant Android Development] TR88:
I would be interested.

EDIT: My mistake, seems to be working now. Perhaps it was my computer.
[Vibrant Android Development] roffee:
i can't save status of usb debug, updated from cm9 build13
[Vibrant Android Development] trailblazerz11:
Its known bug for build 14

"Regression in BUILD 14: adb turns off every reboot"

View i9000 thread OP for changelog
[Vibrant Android Development] notverycreative:
Why is color tuning greyed out in Device Settings?
[Vibrant Android Development] sixstringsg:
Because the Glitch kernel does not support that yet.
[Vibrant Android Development] btyork:
Am I missing an update log from 14? What's different?
[Vibrant Android Development] digitaltoddy:
Any idea when OP will be updated to include list of changes with 14?
[Vibrant Android Development] jrafael:
http://xdaforums.com/showthread.php?t=1363593
[Vibrant Android Development] sixstringsg:
So here's how this works: I do not own a Vibrant. I have a friend that does, so i maintain this for him and a few other guys. I am helping maintain and test kernels for four devices, I have work, and I have school, so i am quite limited on time. I do not make money from this ROM, in fact I lose money due to bandwidth costs. The more people bug me about it, the more likely I am to stop maintaining this ROM, or just stop posting it on XDA. The OP will get updated, I figured people would rather have a new build and no OP than the other way around. I also link to the i9000 OP in my OP, you can find the info yourself.
[Vibrant Android Development] btyork:
I meant no disrespect, and it didn't click that the other change log applied here. I don't own a vibrant either, my roommate does however. So we both appreciate what you do, cause it allows me to play on his phone as well. Thanks! :)

I wish I hadn't posted, cause someone else did at the exact same time... ;/
[Vibrant Android Development] jrafael:
I know you mean well my friend. Thanks for your hardwork.

Have you consider using sourceforge for hosting your project ?
[Vibrant Android Development] sixstringsg:
I own a dedicated server, and hosting on source forge doesn't provide near the flexibility I need. I should be fine bandwidth wise. I have other projects that need the server anyway.
[Vibrant Android Development] anomalous3:
Note for anyone upgrading to this from a previous version: If you forgot to wipe and now it's lagging terribly, try a kernel cleaning script and flashing Eugene's streamline kernel. I got to keep all my data and lag is gone. Edit: I suppose you could also probably format /boot and /system and flash build 14 again, or maybe even run a kernel cleaning script and flash it again, but I'm all for the minimum amount of flashing/wiping necessary.
[Vibrant Android Development] JettyLife:
Hey guys do the cm7 themes work on this? Maybe an obvious stupid question...

Vibrant + ICS
[Vibrant Android Development] sixstringsg:
No.

10char
[Vibrant Android Development] sneakysnake16:
Hey you don't know me im new here but I'm a flashaholic and I don't mind testing Roms for anyone if you need a tester just pm me with a link to the rom/kernel whatever you need and ill help out :) goodluck
[Vibrant Android Development] :
has anyone tested between CM9 and Passion? if so i was just wondering which is better?
[Vibrant Android Development] trailblazerz11:
Passion is based on CM9. So pretty similar. Glitch kernel pushes Cm9 on top for me though. So many features.
[Vibrant Android Development] sixstringsg:
Passion claims to be AOSP last I checked, which is different from CM9.
[Vibrant Android Development] :
are there any accurate battery mods for CM9?
[Vibrant Android Development] trailblazerz11:
i9000 theming forum has several by perka and others.

Their scripts do check for i9000 though so you might have to change build.prop or edit scripts if you are on t959
[Vibrant Android Development] :
so just change i9000 to t959 and everything should work?
[Vibrant Android Development] trailblazerz11:
their kernel dev said it was heavily based on cm9 but i dunno for sure.

---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------

ehh other way around.. to flash i9000 mods

EDIT: Now that i checked perkamods install scripts, i think he only checks ro.build.version.incremental which *might* not have been changed in this kang so try and flash
[Vibrant Android Development] charkey:
Battery life on #14 is amazing. It's the best ROM yet with great battery life. I'm not going to state the daily life span of the battery as it depends on usage but it's the best I've ever seen on any ROM.
[Vibrant Android Development] hkfan:
Does this ROM has mute unmute and deep sleep GPS bug like passion ?
[Vibrant Android Development] djf8:
All ICS builds have mute/unmute bug iirc.
[Vibrant Android Development] granduke:
Will we get USB Hosting with Icy Glitch on this version or do we need to wait for the next ROM?
[Vibrant Android Development] sixstringsg:
If you flash the new kernel it will work just fine until I update the ROM. I probably won't update the ROM until THS build 15 though, and add the new kernel then.
[Vibrant Android Development] :
just wondering is everyones Google Services taking ~50% of battery? or did i do something wrong?

----

nvm looks like my phone wasn't sleeping because of google maps
[Vibrant Android Development] roogerrisboredd:
I followed the instructions on installing but always boot loop even after flashing it again after mtd mismatch. Can anyone tell me if I'm missing something here?
[Vibrant Android Development] trailblazerz11:
1st flash should flash kernl ?and recovery I think so to match you can flash rom.

Though if it still says mismatch maybe try flashing glitch beta1
[Vibrant Android Development] Tarv:
I had the same issue. Caused by mismatch of old version of CWM.

Just battery pull, then boot back in to CWM using HOME+VOL UP+PWR (let go when screen turns on).

Re-flash the ROM with the new CWM that comes up, all should be good.
[Vibrant Android Development] meamgood:
This is a weird one and not that important, but I cannot install the CM9 music app that was released a little while ago. I removed the default one with Titanium backup and then placed the apk in data/app, but when I rebooted I got stuck in a boot loop. I got into recovery and tried fixing permissions, but that didn't work. I ended up reflashing and everything is fine now.
[Vibrant Android Development] trailblazerz11:
Don't think you need to place in /app just install like normal apk. Treat it like Google music app.
[Vibrant Android Development] :
is it possible to flash the alpha cmsettings.zip on v14?
[Vibrant Android Development] sixstringsg:
Should be fine, yes.
[Vibrant Android Development] Ventus_zx:
IM about to give this a try haha. First ill back up the ol CM7
[Vibrant Android Development] :
hey six one more quick question. I'm not able to mount via usb or use adb even with android debugging checked and was wondering if that was an issue that is unique to me or if its a rom issue? i tried reading through the bugs but wasn't sure.

----------

nvm i finally looked in the glitch settings. it didn't cross my mind that it would be in there!
[Vibrant Android Development] Ventus_zx:
Crap i forgot to wipe before coming to this rom. Now i apear to be stuck in the glitch kernel screen.... is that normal?

and i cant get into recovery. MAn.. I dont wanna odin back to stock....
[Vibrant Android Development] :
i know this is gonna suck but try a battery pull. then depending on your boot loader do the three button or two button to recovery and try it that way
[Vibrant Android Development] Dougfresh:
Take out the battery and reinstall it press power and down vol and you should boot to recovery. On froyo bootloader its both vol buttons and power. Then do a full wipe and reinstall
[Vibrant Android Development] Ventus_zx:
That didnt work so i odined back to stock. Im gonna re root and recover my cm& backup and try this again

---------- Post added at 09:22 PM ---------- Previous post was at 09:18 PM ----------

Urgh i hate glitch kernel... Always colors my screen wierd. In this case its purple...
[Vibrant Android Development] :
may i suggest when you are on cm7 flash a gingerbread boot loader instead of froyo. I believe that may fix your screen issue
[Vibrant Android Development] bearsfan85:
I recommend flashing another rom if you are not happy with the way this one works. Also you can always change that in settings as well
[Vibrant Android Development] sixstringsg:
People like you are the reason that developers quit XDA.
[Vibrant Android Development] Ventus_zx:
Sorry... I didnt mean it offensivly! I still used and tested the rom! I like it! Im just waiting for the final release. Ive been watching this rom for a while. That was just my opinion and i guess my bad luck. For some reason everytime i use a rom with glitch kernel the color gets wierd.
[Vibrant Android Development] sixstringsg:
There isn't a way to make the word hate not offensive. Also, in case you didn't know, the glitch kernel colors are fully user controllable. Therefore if you don't like the colors, it is purely your fault and nobody elses.
[Vibrant Android Development] Ventus_zx:
OK well i didnt know. when ever i asked for help the answer was - Maybe your screen is broken or check voodoo (usually voodoo wasnt there)
[Vibrant Android Development] :
install voodoo and fix settings. There is also the color tuning in settings that may be off
[Vibrant Android Development] Ventus_zx:
yeah mine was off.
[Vibrant Android Development] sixstringsg:
Well there's your issue. We aren't using voodoo color. Edit the colors through your device settings. And next time, read the kernel OP before bashing a kernel.
[Vibrant Android Development] josepr0218:
Is there a battery mod percent for this rom I really want battery mod
[Vibrant Android Development] Ventus_zx:
The device setting color edit IS OFF. I already said that.
[Vibrant Android Development] jad3675:
I've never had any issues with any glitch kernel either on CM7 or CM9. They are some of the smoothest kernels out there.

I've only had issues when I've OC'ed and not been careful with the UV/OV settings.

Six is doing us a big favor by redoing/porting the Team Hacksung ROM for the Vibrant.

John
[Vibrant Android Development] roogerrisboredd:
I tried everything. Nothing seems to work. On gingerbread bl I would have boot loop on glitch screen and then the 2 combo button didn't work to get me back into recovery. On froyo bl it bootlopped on the vibrant screen and I couldn't get back into recovery. I guess I have a rrare vibrant that refuses to work with icy glitch kernel. Any other ideas anyone
[Vibrant Android Development] tinyaznboi:
When you are in gb boot loader to get into recovery the method of getting into recovery changes the combo then becomes hold volume down and power.

Here's something you can try ,

Download a fresh cop of cm9 and flash it. COMPLETELY WIPE, do the method you would use when coming from a new rom. Boot up and make sure it boots all the way. Then get back into recovery andy run a kernel cleaner than flash the kernel. Remember this kernel only works with cm9 not passion not doc. Good luck
[Vibrant Android Development] roogerrisboredd:
Thanks man but im quite aware that the button combo changes when using the gb bl. It just seems no matter how many times I wipe it, I get the same results. I downloaded copies of the rom twice already but no luck. My phone simply isn't compatable with icy glitch. It really is true when they say all vibrants are different.
[Vibrant Android Development] tinyaznboi:
does the rom work just fine and not the kernel? if that's the case then try posing in the kernel thread. Maybe someone can help you there :D
[Vibrant Android Development] roogerrisboredd:
LOL no the farthest I got was the kernel screen. Its was the stock kernel too so I have no idea what's going on
[Vibrant Android Development] tinyaznboi:
Try this... might work but it works for me, just give it a shot. unless you already tried it.

1.Reboot into Recovery

2.WIPE (wipe data/factory reset + wipe cache partition)

3.Format system

4.Flash CM9

5.Flash AGAIN

6.Fix Permissions

7.Bootup and give it some time, initial boot generally takes some time

lemme know if that works good luck! :D
[Vibrant Android Development] test.im.09:
Hi,

I am able to install this ROM on my Samsung Vibrant. But when I make a phone call, there is no sound. I can dial a number and the callee does get the phone call, but when I speak on my Samsung Vibrant, there is no sound on the other end.

Does anyone know how to fix it?

Thank you.
[Vibrant Android Development] bobshute:
This may be a bit off topic but it is about CM9 with the stock Trebuchet launcher and there's lots of smart people here.

Below I have a screenshot of the home page of my NookColor. My Nook is running CM9 with the stock Trebuchet launcher. I know it's from a Nook install but other than the device tree it from CM9 nightlies.

I like the layout with the apps icon in the top right, search icon top left, statusbar at the bottom with ICS soft buttons and no dock.

Somehow both Trebuchet (and Nova) launchers know if they are being installed on a tablet vs a phone. I would like to spoof the launcher to give me the Tablet UI on my phone and see if I like it.

Any clues of where the launchers determine which Ui to use? Build prop maybe?
[Vibrant Android Development] sixstringsg:
For Trebuchet I believe it is determined at build time. I don't know about Nova. I do know it is not dependant on build.prop though.
[Vibrant Android Development] bobshute:
Darn...I had changed the build.prop to:

ro.build.characteristics=tablet

ro.cm.device=encore

But it didn't do anything. I also grabbed the trebuchet.apk from my nook and put it on the Vib but it still used the phone UI. Oh well. Thanks for the answer.:)
[Vibrant Android Development] sixstringsg:
Then I guess I was wrong about trebuchet. I'll ask my tablet friends.
[Vibrant Android Development] sixstringsg:
Upon further investigation, it has to be set at compile time in the configs. Maybe in the future either CM9 or the launcher devs will create a manual toggle so that you can switch, we'll see.
[Vibrant Android Development] bearsfan85:
the launcher is based on the DPI, the phone tablet toggle is only for the system and for About Phone/Tablet stuff, Powering off ect
[Vibrant Android Development] sixstringsg:
No matter what I set the DPI to on my Nexus S, the launcher doesn't switch to tablet mode. Then when I switch the config, it goes into tablet mode on stock DPI, but that's just one guy's experience.
[Vibrant Android Development] bobshute:
Yeah. I just changed the dpi to 160 like my nook and still got the phone UI. Funny looking though. Lol.
[Vibrant Android Development] bearsfan85:
I was messing around with it on my tablet, and mine turned into a phone UI, well I have no clue
[Vibrant Android Development] josepr0218:
Someone has a battery mod for this rom build 14 igot one from perka mod but doesnt work in this rom someone can help.
[Vibrant Android Development] trailblazerz11:
Perkas does work. Its just that it won't install on vibrant. Have to change build.prop or modify perkas install script.
[Vibrant Android Development] Smartassassin:
or just push it via root explorer. That is what I have done

Sent from my phone, not yours.
[Vibrant Android Development] josepr0218:
Doesnt work for me i edit the scrip and pushed with root explorer but both ways failed share your mod.
[Vibrant Android Development] Dougfresh:
Go to the zip and extract the Systemui.apk and paste it in system/app and set permission and the original apk rename it .bak just in case..
[Vibrant Android Development] :
woot

can't wait for an update! keep up the good work!
[Vibrant Android Development] ursubpar:
just so you know, the device name(s) in build.prop should be "SGH-T959"

not "Vibrantmtd"

other than that, this rom and kernel is ****ing amazing.
[Vibrant Android Development] :
Woot build 15 just dropped for i9000 hope this means it'll follow up for the vibrant :)))
[Vibrant Android Development] trailblazerz11:
Its a bit smoother, biggest difference is they are starting to put in cyanogenmod settings.
[Vibrant Android Development] :
Whoa how'd you get it already? or are you using an i9000?
[Vibrant Android Development] trailblazerz11:
I just flashed the i9000 build with vibrant glitch, correct keys and modem. I'm impatitient, best wait for kang. probably new glitch kernel today :)

One good thing T-Mobile did was not modify too much from i9000. Similar enough to be able to flash i9000 with minor issues.
[Vibrant Android Development] :
nice lol i think I'm just gonna wait. Im not sure what changes id have to make to the rom to make it run correctly.
[Vibrant Android Development] ew:
Can anybody give me some instructions on what needs to be changed in the install script.

Thanks,
[Vibrant Android Development] Robert8457:
How does this compare to Neo's build?

Sent from a ics infused vibrant
[Vibrant Android Development] :
its probably easier to just change the build.prop
[Vibrant Android Development] sixstringsg:
I haven't looked at his script yet, but if it uses getprop, then modifying the build.prop won't work, as it checks default.prop.
[Vibrant Android Development] :
ah sorry i didn't know that sorry for the bad info
[Vibrant Android Development] manjish:
waiting eagerly for build 15.....

thumbs up to u my friend
[Vibrant Android Development] ew:
How would I need to change the build prop?
[Vibrant Android Development] trailblazerz11:
If I remember correctly script checked ro.build.version.incremental=eng.pawitp.20120126.192427.

Checks the 1st number above I think.

Perka should be releasing build 15 mod today that includes the Bluetooth quickswitch off.
[Vibrant Android Development] :
wonder if a new kernel will accompany build 15 =] hehehe
[Vibrant Android Development] sixstringsg:
I will probably wait to push Build 15 until Beta 2 kernel is ready to push.
[Vibrant Android Development] :
Sweet thats good news. Build 14 with kernel 14b1 is running amazing thus far. battery has improved drastically for me since I've flashed from Passion
[Vibrant Android Development] ew:
I see the version_installer.sh (in the flashable file) contains:

Is there something in that file that I can modify so that it will work for the Vibrant?
[Vibrant Android Development] Xenoism:
Agree :)

I keep forgetting where I placed my charger ever since I've flashed this ;)
[Vibrant Android Development] trailblazerz11:
Check in build.prop what your ro.build.version.incremental=
[Vibrant Android Development] ew:
Sorry if I am slow, but I see that it is

What do I do with that though.

Thanks,
[Vibrant Android Development] :
update

im glued to refreshing this page waiting for an update lol
[Vibrant Android Development] treyvaporizer:
Its smoother for me

Sent from my iced vibrant
[Vibrant Android Development] :
Better on battery also
[Vibrant Android Development] :
new glitch kernel has been released =]!
[Vibrant Android Development] treyvaporizer:
Definitely

10char

Sent from my iced vibrant
[Vibrant Android Development] Robert8457:
Does this rom have cm settings?

Sent from a ics infused vibrant
[Vibrant Android Development] trailblazerz11:
Build 14 can flash it but very minimal. Only option is like notification toggle.

Build 15 has more cm settings integrated now.
[Vibrant Android Development] :
you can flash it from the OP its in Alpha right now
[Vibrant Android Development] :
Hey six you gonna have time to post b15 today? Or should I come back tmrw? Thanks man
[Vibrant Android Development] sixstringsg:
Typically I don't post ETA's.... But I'm almost done putting it together now, so it'll be posted tonight if all goes well.
[Vibrant Android Development] :
Sorry its just we were chatting about it in the irc room and you mentioned it being almost complete. :) thanks man I appreciate it
[Vibrant Android Development] JettyLife:
Can't wait for v15 I just might have to get off passion for a while

Vibrant + ICS
[Vibrant Android Development] sixstringsg:
Team Hacksung Build 15 with Glitch Beta 2

Without gapps: http://goo.gl/6O0Cz

With gapps: http://goo.gl/60THg

Note: as I don't have a Vibrant, these two zips are completely untested. While there is no reason that they shouldn't work, you have been warned.
[Vibrant Android Development] :
Do we have to wipe before install?
[Vibrant Android Development] sixstringsg:
No.
[Vibrant Android Development] :
I have two calendars and two gallery.
[Vibrant Android Development] Richcar:
thanks six,this **** is fast and smooth as hell wi-fi and everything else work great even GPS work haven test it yet after deep sleed.but i dont used it so i dont care for it much.thanks to you and your team build 15 along with Beta 2 kernel is Solid as a Rock.
[Vibrant Android Development] Smartassassin:
how is the download speed?

Sent from my phone, not yours.
[Vibrant Android Development] sixstringsg:
Download speed is dependant on signal strength and area. There are a few ROM and kernel things we can do, but they don't make much difference.
[Vibrant Android Development] djf8:
So I noticed team hacksung mention a mute/unmute big fix in the captivate build 15.

Could that fix work for the vibrant?
[Vibrant Android Development] trailblazerz11:
This build is pretty much the same so it does have the fix but pawitp said fix was hopeful.
[Vibrant Android Development] jad3675:
The mute/unmute issue still exists with 15; had a call an hour after I upgraded with the issue.

FWIW, I think I only have the issue when the CPU minimum speed is set at 100 and the phone has been idle for a long time.

John
[Vibrant Android Development] Smartassassin:
Okay, the only trouble I had with build 14 was the super slow download speeds.

Sent from my phone, not yours.
[Vibrant Android Development] DontJoinTheDarkSide:
GPS not functional for me. Coming from a clean install.

Also had 2 calendars and 2 galleries.

Also had an error when I installed, said offset 0x267 reinstalled and had the same error but a different offset number.
[Vibrant Android Development] meamgood:
Is anyone else having this issue? When I restart my phone, all my sound selections reset, e.g. the notification ringtone and such will set back to default. I am using the Glitch Beta kernel if that makes a difference
[Vibrant Android Development] ursubpar:
offset isnt an error. its a security feature implemented for ICS.

-nottrolling-
[Vibrant Android Development] djf8:
So I was testing to see if I could force my phone to do the mute/unmute bug. I noticed something wierd. When the other phones mic is muted I can't produce the bug.

But if I make the test call again and have the test phone unmuted the bug happens. It's like the incoming audio messes up your outbound audio.