yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] hurtz777:
Sweet. Will that be in the next build? I want to change the battery bar to white to match ICS colors.
[Vibrant Android Development] makelegs:
Confucius say: "custom color on ur device in 15 minute"

:D
[Vibrant Android Development] matutemhn:
what kernel should i flash, what you recommend? your response is truly appreciated

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

what kernel you recommend to flash? thanks for your response !!!:confused:
[Vibrant Android Development] bearsfan85:
either Streamline by Eugene

or Glitch by Tk-Glitch/Sixstring

MAKE SURE YOU DOWNLOAD THE GB VERSION NOT THE ICS ONE I'M MAKING THIS LONGER TO MAKE SURE THIS IS READ BECAUSE THEY BOTH HAVE ICS KERNELS OUT UNDER SIMILAR NAMES
[Vibrant Android Development] matutemhn:
thanks, i just flashed glitch and will give it a try tomorrow, have a 16 hrs day at work and hopefully it will be better, after flashing this kernel i tried the BLINKY app but it says that my rom doesnt have the bln mod installed, what that means? i thought the kernel flashing was supposed to activate that feature... thanks againg for response.:cool:
[Vibrant Android Development] Se7eN43:
Here are 2 kernels that support the BLN app if you would like the flashing led notifications. Download BLN from the market.

(99 Problems Kernel)

http://xdaforums.com/showthread.php?t=1322020

(Platypus Kernel)

http://xdaforums.com/showthread.php?t=1102280
[Vibrant Android Development] hurtz777:
You will get the best battery with Neo R18 update 2 using ondemandb governor. Zach also added 600mhz stepping and with Smartass V2 it flies!
[Vibrant Android Development] djf8:
I found the best kernel for stability, speed, and battery life was Eugenes Streamline kernel.
[Vibrant Android Development] creeve4:
+1 to this
[Vibrant Android Development] djf8:
Might just be me, but has anyone else noticed that the mute/unmute bug has returned since the 911/e911 fix?

It hasn't been on every incoming call, more like 50/50.
[Vibrant Android Development] core123:
Yeah I noticed that too and so did people that call. I don't really mind but people sure do get mad hahaha
[Vibrant Android Development] djf8:
So the libaudio.so that fixed 911/e911 broke incoming call audio sometimes haha. It seems like the vibrant devs always have an uphill battle.
[Vibrant Android Development] makelegs:
Is EVERYONE noticing this??
[Vibrant Android Development] duboi97:
Yeah I am too. I can live with it though
[Vibrant Android Development] creeve4:
I get it too, about 50% of the time
[Vibrant Android Development] makelegs:
****!!!

Rest assured.........................I have NO IDEA how to fix it! :eek:
[Vibrant Android Development] makelegs:
Look out!!!....

.....this build just got a lil bit SKANKIER!!!

View attachment 856025
[Vibrant Android Development] duboi97:
You should pm Roman I think he was the first one to fix it.
[Vibrant Android Development] makelegs:
Unless he submits a patch to gerrit....it will not find its way into this build.
[Vibrant Android Development] strictlyrude27:
Can anyone talk about the GPS reliability?

does GPS lock quickly?

what's accuracy like?

are locks maintained?

does GPS crash when no lock is achieved and you exit out of a GPS using app?

if i exit out of a GPS-using app (lock obtained) and try to use it again after a while, does it come back up okay?

does using GPS disrupt deep sleep? does deep sleep disrupt GPS?

does GPS survive reboot?

I'm selling my Vibe to a friend and GPS is his top priority (which makes it a pretty bad deal to take my phone tbh). I was wondering if I should put him on Samsung 2.2 ROMs or CM7..
[Vibrant Android Development] makelegs:
Try it out, and report back!!

Sent from my Galaxy Nexus
[Vibrant Android Development] hurtz777:
I have to use the latest gps fix v2 along with angrygps set to msbased with Xtra set to off. I also use KB5 modem which gives fastest data speed and GPS lock. With this setup I get 3-5 sec locks down to 3m accuracy indoors! I haven't had the mute/unmute issue yet with calls. Love the rom makelegs!
[Vibrant Android Development] djf8:
Did you wipe your data and start over when you flashed this? Just curious...
[Vibrant Android Development] hurtz777:
I odined JFD build and then wiped all data and caches and flashed.
[Vibrant Android Development] djf8:
I'm in the middle of testing different libaudio.so files from the other Galaxy S variants.

So far one seems promising but I don't know enough to know for sure that it has fixed the mute/unmute bug. I've only been using it for a few hours.

At this point I haven't had a single incoming call bug out on me. Also I called 911 and asked them to verify that they were receiving valid ph2 wireless location data correctly and they said that they were receiving everything perfectly fine and told me where I was at.

Thanks for letting us know what to ask renardk764. =)

Only time will tell I suppose. I'll continue to call myself to see if it eventually breaks.
[Vibrant Android Development] djf8:
Just wanted to update you guys. So far since I've replaced my libaudio.so I haven't had the mute/unmute issue once.

I waiting on someone with far more skill than myself to verify everything is working properly.
[Vibrant Android Development] strictlyrude27:
Can you post here? Maybe this could get included into the kang?
[Vibrant Android Development] JediDru:
This was posted in the Ics streamline kernel thread IM using it now.

Here is the libaudio file I've been using that seems to work.

http://db.tt/r72ukQez

Again though I'm not 100% sure it is a fix yet.

Sent from my Com-Link
[Vibrant Android Development] HaloMediaz:
Is this CM9 or will we still have to wait?
[Vibrant Android Development] makelegs:
It's CM10....awesomeballs!!!

Sent from my Galaxy Nexus
[Vibrant Android Development] joe98200:
OH gosh golly I thought it was CM11.
[Vibrant Android Development] JediDru:
As I understand you must wait. lib audio is not in the same place and must be reorganized. Earlier today in the cm9 streamline thread I think some folks are working on this.

Nevermind didn't pay attention lol.

Sent from my Com-Link
[Vibrant Android Development] djf8:
That was just me trying to help with the mute/unmute bug. I'm no dev though so I'll leave it to them at this point.
[Vibrant Android Development] ew:
After a bunch of testing I have finally decided that for now, I will stick to the Kang made by Genesis3 with the Glitch Kernel.

Of all the various GPS fixes, I have found the Genesis3 Kang to be the most reliable for my device. Please not that the DPS for my phone is very unreliable and most of the GPS fixes did not work. The Genesis version seemed to work the best of all. The more recent Kangs were worse from a GPS standpoint, and the other cherry pick features were not worth it to me.

As far as kernels, the native kernel is slightly better than the Glitch kernel from a gps perspective. Sometimes I did not have to reboot to get a good GPS signal on the native kernel, but I always have to on the Glitch kernel. However, the fact that I CAN get a gps signal after reboot and the improved battery and overall performance with the Glitch kernel make me want to stick to it.

I have tried a bunch of other kernels (bali, streamline and neo), but they seem to tank my gps.

The best gps solution for me is an external bluetooth gps receiver. I picked up a tomtom MK11 on ebay for about $13. It gives me a firm lock and sometimes gets down to 10ft accuracy with 0 drift.

I do have to say that for GPS performance, the froyo roms were a bit better. I ran for a while on trigger and bionix and both gave me better gps performance than the best I can seem to get from any gingerbread solution.

I hope this information helps the group.

Edit:

Furthermore, using the Genesis3 Kang with the glitch kernel:

-I have not experienced the mute/unmute bug

-the "delayed answer" bug that I have had forever (when I answer the phone, it takes a second or two until I can begin my conversation) has gone away.

-Prior to this, I have had a problem terminating a conversation with my Bluetooth button. Instead of hanging up the phone, it would begin a voice search. Perhaps that was a bug in the streamline v7 kernel (or a bug somewhere else), but that problem has disapeared.

-the glitch kernel has a voice booster. My bluetooth sound is low - this really helps.
[Vibrant Android Development] jrafael:
I downloaded CM7.1 from Nesus S and pulled the libaudio.so file and push it to the most recent kang (011612) and it's working very well. I havent test 911/e911. Wich galaxy variant/rom you pulled the file that you uploaded ? (asop based, samsung, cm7 ?)
[Vibrant Android Development] Demetris:
Please can you add in your build this:

Fix Galaxy S 1 & 2 devices market filtering (android_vendor_cyanogen)

Thanks
[Vibrant Android Development] makelegs:
It's already merged.... and it was in the build, already, before that.

Sent from my Galaxy Nexus
[Vibrant Android Development] hurtz777:
Does anyone have any ideas on how to get GPS to lock as fast as Nightly #182 with GPS Fix 2 and KB5 modem? GPS is very hit and miss for me on makelegs kang.
[Vibrant Android Development] bigtom624:
Try Eugene's kernel. When I was on #182 and even now on the latest Kang I get GPS to lock everytime.
[Vibrant Android Development] VeryCoolAlan:
Lol how old are you??!?

I'm gonna guess 17 or 18?!!?
[Vibrant Android Development] hurtz777:
Well I think I found the perfect GPS combination with makeleg's kang. Using Neo R18 Update 2 and GPS CM7 GPS fix 2 I am able to first time lock in 5 seconds with 4m accuracy. You also won't need to reboot after your first use of GPS because with Neo R18 Update 1 the GPS properly closes and opens without a reboot like it should. Glitch v13.1 would take forever to lock and I could never get it to get better then 30-40mm accuracy and it would sometimes require a reboot to reopen GPS after first use. Makelegs could you include the new libaudio.so that seems to fix mute/unmute issue with this rom. All in all I think I have fixed all of the issues with this kang rom and I thank you very much for your time makelegs!
[Vibrant Android Development] makelegs:
Somebody please remind me where this libaudio.so came from.

I won't simply "add it" to the build. If it's legit, I'm happy to reach out to the devs, though. It's a bit complicated, now, without a maintainer. Please remember that, despite this feeling like cm7, it's a completely unofficial kang (unlike captivate and fascinate), so support from the usual suspects cannot be assumed.

Sent from my Galaxy Nexus
[Vibrant Android Development] djf8:
The libaudio.so came from a nexus s ginger bread build.

It was me just playing around trying to find something to fix it.

Tbh I wasn't sure if it fixed it.
[Vibrant Android Development] ipnekgs:
I have a question to all vibrant owners that use their vibrant with a 32GB MicroSD card and CM7. Do your MicroSD card starts disappearing and eventually become corrupted? It only happens when I run CM7, card can be reformatted again and if I come back to a 2.2 rom it works fine no problems.
[Vibrant Android Development] makelegs:
Ok, vibrant peeps....I'm trying to get that mute/unmute patch added the correct way.

We need some logcats, first, though. Who wants to help out???

Sent from my Galaxy Nexus
[Vibrant Android Development] ehall2k7:
Can you please post a link to Neo R18 Update 2? I've searched and all I can find is R18 Update 1. Thank you.
[Vibrant Android Development] Relikk356:
I want to help but I'm in class. Anyone sign up yet?
[Vibrant Android Development] hurtz777:
Ehall2k7 I'm sorry it was R18 Update 1 from 12-03 with led and didle.
[Vibrant Android Development] makelegs:
Please raise your hand if you know how to pull a logcat....cuz I needz one related to the mute/unmute bug. This is why we Kang, guys!

Help a brutha out!!

Sent from my Galaxy Nexus
[Vibrant Android Development] sixstringsg:
The call volume script doesn't work on anything other than our kernel. There are some sysfs' that are required for it to function.
[Vibrant Android Development] hurtz777:
I didn't know that six and thank you for pointing it out.
[Vibrant Android Development] Relikk356:
I'll run one this weekend if someone doesn’t beat me to it. I don't even have this Rom installed, lol. I'm still running the no-dialing 911 rom cm7 nightly. Like 182 or something.

Just a side note/ quick fix, Back when cm7 first came out they had this same issue. I think it was Burgertime, but someone hacked the phone dialer app so that it auto mute, unmute when you received a call. Doesn’t fix the problem but it hides it and could be a short term solution if 911 is working again. I’m surprised people haven’t done this with the ICS roms either.
[Vibrant Android Development] makelegs:
Install aLogcat (from market) > clear log > make phone experience mute/unmute bug > pause aLogcat > share log to pastebin > post pastebin link > profit!!!!

Sent from my Galaxy Nexus
[Vibrant Android Development] makelegs:
mute/unmute bug update...

djf8 was the only one who grabbed a log. Thanks, dude! :D

I sent djf8 a link to a flashable patch to try out. Hopefully he is able to confirm some positive result. The patch is not mine.... I'm just the middleman. But if it works, then I have reason to think we can get it thru gerrit and into this build.

:cool:
[Vibrant Android Development] djf8:
Sorry I was in a movie when you pm'ed me. What a waste of money....the new under world sucks ha ha.

Will try the patch and report back asap.
[Vibrant Android Development] makelegs:
Anything with Kate Beckinsale is worth the price of admission......justsayin!
[Vibrant Android Development] djf8:
She was the only good part if the movie.....and I'm not saying her acting either ha ha.
[Vibrant Android Development] djf8:
Just to let the public know I've been testing a couple of patches from makelegs and one seems to be very promising.

I haven't had the mute/unmute bug show up yet since I've been testing the latest patch. Hopefully it will prove to work 100% of the time and make its way upstream!

Thanks makelegs and whoever else was helping you. =)
[Vibrant Android Development] makelegs:
It's already made its way upstream :cool:

Thanks again for testing :)
[Vibrant Android Development] djf8:
Tested the new build with 5-10 calls and no bugs so far. Looking good!
[Vibrant Android Development] makelegs:
suh-weet!!!

#DISCO
[Vibrant Android Development] hurtz777:
Thanks for the latest build makelegs. Everything works flawlessly including no mute/unmute issue and GPS with Glitch 13.1. I have grown to like the status bar battery with 34B4E3 color code along with my tiny battery modified ICS v1.6 CM7 theme. It is extremely fast and smooth with no need to overclock with the smartass v2 governor.
[Vibrant Android Development] makelegs:
Glad to hear, fellow #crackflasher

Sent from my Galaxy Nexus
[Vibrant Android Development] claucXC:
I had a couple of questions I hoped someone could help with:

1. Are there any special steps to take when coming from an ICS ROM? I'm on the latest NB ROM and I wiped data, cache, dalvic and formatted system. I then flashed the 1-21 version of this and it errored out at the assert.

2. I was able to flash an earlier version but could not log into the market. Do I need to replace the market in the gapps zip with another version? if so, why?
[Vibrant Android Development] Young Cardiac:
Tried to install this and I'm getting assert failed: getprop ("ro.product.device")
[Vibrant Android Development] JediDru:
On 01212012 my Girlfriend and I still have mute unmute. Is this fix in the 22 build? I'm at work and haven't tried a newer one. We both were on 01212012 maybe that has something to dowitg it lol. "OK we have mute unmute fixed. Just dont call anyone else on cm7." I'll see about 01222012 tonight. Does anyone know about a build sans 911 without mute unmute? Please and thank you.
[Vibrant Android Development] bigtom624:
I just flashed the latest nightly 1/22/2012 and the boot animation is not showing up. I looked in the system/media folder and it is in there, but it doesn't work on the phone for some reason. Other than that everything is working fine. Thanks for keeping this up to date makelegs.
[Vibrant Android Development] makelegs:
CCL Hack...

Ok, guys....this is a little hacky, but here goes.

I updated the OP to include a link to a mostly barebones build that has custom carrier label (CCL) fully in tact. As it stands, now, the current build allows existing CCL's to be maintained without the ability to change/enable/disable the function. The settings part conflicts badly with both MIUI battery and Skank Style rings. So....instead of squashing 2 to achieve 1.....or 1 to achieve 2....I chose to include the frameworks aspect of CCL, so that existing settings could remain in use without having to kill MIUI or Skank Style.

Long story short....if your CCL is already working, and you are happy with it, then do nothing. However, if you do not currently have it in use, or wish to change the label somehow, then you can flash the hack build, set the label, and then update to the current build.
[Vibrant Android Development] djf8:
You're the man! Just thought I'd remind ya. =-)
[Vibrant Android Development] ew:
Error

I get the following error

"The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again"

when I boot up (just after I flash).

My statusbar gets hidden. This also happens when I use the Cyanbread theme.

I am coming from the Kang that Genesis3 did to fix the 911 bug. I have tried flashing both the minimum CCL build and the latest Kang from 1/22.

Any ideas as to what can be causing this? I would really like to use this.

Edit: I tried wiping cache, Davlik Cache and fixing permissions - that did not help.

Thanks,
[Vibrant Android Development] makelegs:
I got the same thing on first boot after a full wipe of my passion over the weekend. Worked fine after I set everything up. Did you wipe? If so, it should work fine. If not....might be time. Seems to be working well for the majority.

Sent from my Galaxy Nexus
[Vibrant Android Development] ew:
I didn't wipe. I was hoping that I would not have to. I have not wiped for a CM7 installation in a long time....

Thanks,
[Vibrant Android Development] makelegs:
Eventually.....everyone has to wipe from time to time. If you've tried wiping cache/dalvik/fix perms, and cleared your data/data to sd, and it's still acting funky, then a wipe may be in order.

#lifeofacrackflasher

Unless you're running some funky theme that conflicts for some reason

Sent from my Galaxy Nexus
[Vibrant Android Development] souleater11:
This is my first time flashing cm7 nightly. My main screen has a written display of problem loading widget. How do I removed widget? I can't even move my app icons
[Vibrant Android Development] makelegs:
Widgets don't restore. Unlock adw and then delete and replace widgets manually.

Sent from my Galaxy Nexus
[Vibrant Android Development] souleater11:
Thanks but how do I unlock adw?
[Vibrant Android Development] makelegs:
from home screen.....menu > more

Sent from my Galaxy Nexus
[Vibrant Android Development] c-pimp:
robot voice

I am on the 7.2 from the 22nd and people keep telling me that I sound like a robot... anyone else ??? any way to fix?

also im using eugene's streamline for cm7 with no bln
[Vibrant Android Development] jrafael:
Try mute/unmute before answering
[Vibrant Android Development] ew:
I think I found the problem. I have the lockscreen disabled in CM settings>tablet tweaks>Disable Lockscreen? Remove that and the FCs stop. If that is the case it looks like a CM bug.

Would there be a way to resolve this? I wonder whether it would also happen on other devices.

Thanks,
[Vibrant Android Development] bigtom624:
Can anyone please let me know why the bootanimation wont work for me after flashing the last few nightly's? I looked in the media folder and it says its in there. I even tried reinstalling a backup of it and it still won't show up on my phone. Any advice would be appreciated. Thanks.
[Vibrant Android Development] kimbo1986:
I forgot does cm7 have mobile AP or wick tether in there somewhere. I need a wifi tether app for ipad!
[Vibrant Android Development] djf8:
It does have wifi tether built in.
[Vibrant Android Development] ehall2k7:
I was having the same problem after flashing last nights nightly and I do not have the lockscreen disabled. I went back to 1/25/12 nightly and the error is not there so it is something in the most recent nightly that is messing with the status bar.
[Vibrant Android Development] mattb6288:
any way an ffc mod for the camera can be added. the camera software in this sounds a lot better then the normal i9000 cm7 camera
[Vibrant Android Development] c-pimp:
Mute/unmute fixes the robot voice or where it sounds like I'm a mile away.... And here I was hoping the bug was fixed :( either way best ROM to date
[Vibrant Android Development] matutemhn:
HELP

I have no status bar, I tried re flashing it 4times already, I wiped data/cache/dalvik cache/format data/format system flash over and over and I get a msg the application status bar has crashed, what is this how could I fix it? Anyone else has this problem? I downloaded the 01252012-2339 :confused:
[Vibrant Android Development] ew:
Did you disable the lockscreen (in tablet tweaks)
[Vibrant Android Development] matutemhn:
no, haven't messed with that at all:confused:
[Vibrant Android Development] makelegs:
Lemme know if new build still messes with status bar fc's

Sent from my Galaxy Nexus
[Vibrant Android Development] bigtom624:
Working fine for me so far. I flashed it about an hour ago.
[Vibrant Android Development] makelegs:
Had to drop transparent bar, for now. My attempt to manually merge it, for last build, was probably the cause of the FC-party that people were experiencing.

Sent from my Galaxy Nexus
[Vibrant Android Development] ew:
Any idea if that resolves the FC when the lockscreen is disabled in the tablet tweaks? I am experimenting with ICS at the moment so it is not too easy to see for myself.

Thanks,
[Vibrant Android Development] makelegs:
We are now waiting for you to test and report back! ;-)

Sent from my Galaxy Nexus
[Vibrant Android Development] Richcar:
working great thanks for this build. 2 questions is there any battery mod for this and how can i used a ffc on this rom. thanks
[Vibrant Android Development] FaultException:
As you just removed your own feature (transparent status bars) I doubt it would fix it -- as my almost pure CM7.2.0 KANG also had this problem with ewillner.
[Vibrant Android Development] makelegs:
I'm not sure I understand ur point...

Sent from my Galaxy Nexus
[Vibrant Android Development] FaultException:
Just saying that the bug is with base CM not your custom changes, so it's probably still there.
[Vibrant Android Development] makelegs:
I'm pretty sure that whatever I altered on the related xml file was prolly the cause, but u could be right. Reports have been positive, though ;-)

Sent from my Galaxy Nexus
[Vibrant Android Development] VeryCoolAlan:
Hey makelegs....does this have the Pawtip TV out hack like faultexception's rom?

That's the only thing missing
[Vibrant Android Development] makelegs:
That commit was merged, so it should be in there, already....u sure it's "missing"?

Sent from my Galaxy Nexus
[Vibrant Android Development] matutemhn:
????

When I turn phone on or reboot I have the system trying to mount my external SD card and then o get the notification "SD card safe to remove" and when I click on it or just clear it from my notifications bar I get the foreclosure, also had fb, Gmail, market and Facebook messenger foreclosing when trying to launch after fresh install so went back to old build 01242012 I think where everything works perfect for me, I tried wiping everything, format everything re-flased 3 times and the errors were still there so I kinda gave up now I'm on the old build with glitch kernel and everything is just good as it was before.