yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Raistline:
How is it trolling when I am just posting a word of advice for anyone who has not read this before while sharing my experience of it soft bricking my phone.

I guess any post is trolling nowadays.:mad:
[Vibrant Android Development] pault949:
Did calling 911 really brick your phone? Has anyone else observed this? This is why I thought you were trolling because it sounds absurd. If not, I apologize.
[Vibrant Android Development] Kaik541:
dialing a phone number CANNOT brick your phone, come on.
[Vibrant Android Development] pault949:
That's exactly what I was thinking... absurd.
[Vibrant Android Development] ChristoA1:
The closest I could come up with for this being anywhere *near* remotely possible, is it *crashing* the phone, not "[soft] bricking" it...

Dialing 911 does (should) run code different from a regular phone call, so if that code was corrupt, you could get a FC or posssssibly a full crash, but yeah, not a brick.

That said, trollers gonna troll. :D
[Vibrant Android Development] SeanFloyd:
Damn, that sucks if development is really stopping. CM is basically the last saving grace for our phones, the last really interesting thing to happen before the Vibrant is ditched altogether.
[Vibrant Android Development] Raistline:
Yes my phone really did Soft Brick from calling 911. I called, my phone hung and the Voice connection did not go through. I could not end the call, or force close the service. I rebooted my phone, then got a call on my work phone --via Google Voice re-routing -- asking if I had an emergency.

My phone never rebooted. It got stuck at Cyanogen Kernal screen. I tried rebooting multiple times. I could not get into Recovery mode as it only showed pure black but with the soft button lights on. I tried to flash a different Kernal Via Odin, still no luck. Since I could still get into DL mode I finally had to flash stock and then re-install Cyanogen.

So yes, to all you disbelievers, calling 911 did SOFT-brick my phone. If I ever have a real emergency I will Dial 0 for the operator and ask to be connected to 911.

---------- Post added at 01:14 PM ---------- Previous post was at 01:10 PM ----------

I would also like to add, I love Cyanogen and even with the few issues it has, I cannot see going back to another ROM. Ever since nightly 136 it has been the most stable ROM aside from Stock that I have used. I have it OC'd and have not had a single crash (911 incident aside) since nightly 136.
[Vibrant Android Development] ChristoA1:
There's no way that dialing 911 did that. I'm not doubting that all happened, and yes, it could have been at the same time you also were trying to dial 911, but neither the code behind making a call nor the code behind making an emergency call would be able to have any affect on the recovery partition... It could be possible bad code caused the radio to lock up perhaps, but a full battery pull and discharge would clear that...
[Vibrant Android Development] user900:
camera sound

hello. first off - nice rom. thank you

i've tried to mute the camera sound from cyanogen menu, but it doesn't work.

also is there a way to get another camera software for this rom?

i liked very much the hacked camera from froyo.
[Vibrant Android Development] Genesis3:
Folks, I'm a CM7 dev (I'm the guy who has been "making it work" on the Triumph - look in that forum or just look on Github under "tickerguy".

I'll pick this up and FIX IT but to do so I need kernel source to one of the "working" kernels, as there are SEVERE sleep problems (yes, STILL) with what's there now.

This is not CM7's fault, it's the KERNEL that's doing it.

I can almost-certainly fix this but to fix it I need the SOURCE to the kernel to be used. I already know how to build CM7 and fork off whatever I want (or need) to change for the Vibrant in that regard.
[Vibrant Android Development] atinm:
I am sorry that your phone soft-bricked. I don't think there is anything that should have soft-bricked, but we do know that audio will not go thru in 911 calls. We'd love to fix this, but a fix is unlikely given that we don't have the code or knowledge we need to fix this because the code is closed and it deals with the modem and network which the manufacturers and carriers don't like to give out.

Plus, given that none of us actually develops on the Vibrant, and none of us wants to deal with many of the users with CM on Vibrant, there is less incentive to try very hard. It is just easier to stop all development, and maybe remove it from the supported phone list.
[Vibrant Android Development] ChristoA1:
I'm not horribly up-to-date on the 911 situation, but to clarify, is it that audio doesn't go through, or the call doesn't connect at all now... If it's the former, that's at least an improvement, but again, I'm not horribly up to speed. The wife has the Vibrant, it's just my job to update it whenever ;)
[Vibrant Android Development] atinm:
CM7 includes the kernel and the source is online in our github repositories. We'd welcome your input if you actually know what you're doing. Given that the issues are related not only to deep sleep, but also to devices not being put into deep sleep due to their not having kernel space interfaces, I hope you realize that the issues on the Samsung Galaxy S phones are quite specific to these phones.

Repositories in my signature below. You want https://github.com/teamhacksung/samsung-kernel-aries specifically. If you know how to build CyanogenMod, you can just follow the instructions for getting the source and binaries on http://wiki.cyanogenmod.com and adding

<project path="kernel/samsung/aries" name="teamhacksung/samsung-kernel-aries" remote="github" revision="android-samsung-2.6.35"/>

<project path="buildscripts" name="teamhacksung/buildscripts" remote="github">

<copyfile src="samsung/build.sh" dest="build.sh" />

</project>

<project path="tools/samsung/galaxys2" name="teamhacksung/android_tools_samsung_galaxys2" remote="github" revision="gingerbread"/>

to your local_manifest.xml in .repo and sync up and just use the build.sh shell script to build the kernel and ROM.
[Vibrant Android Development] Raistline:
Hey don't worry about it. It was only a soft-brick which is easy enough to recover from, the worst part is losing SMS messages since last backup. I don't ever expect any single ROM to run 100% for everything. Besides, I can only blame myself for not using stock :). CM is by far the most stable ROM out there for the Vibrant otherwise and I sincerely hope that development and support for this device is not cancelled.

Right now, the actual call does hit the 911 switchboards, but the call fails to connect voice. So if you were to have GPS on and working while calling it, Emergency units would surely be called to your location.
[Vibrant Android Development] ChristoA1:
Much appreciated! That's exactly what my thought process was: If the call was at least properly *reaching* E911, then you'll get some sort of result, versus it not going through at all...
[Vibrant Android Development] Genesis3:
Cool.... I'll see if I can find time to take a crack at it.

This stuff (no driver source in places you really need it) is lots of fun and I dealt with it on the Triumph. The only place I wasn't able to fix it was the Wifi driver, but even that wasn't an impossible job - I stuck a test in the SDIO code to see if the wifi driver (the libra driver) was loaded, and if not, then allow a drop to S3, if so, hold a wakelock. I had to hack in AMSS 50001 support in CM7 too as the Triumph's GPS wanted that, plus a separate ioctl to turn on/off the LNA, and there were some other oddities too. I also fixed the keypad light code in the kernel so PWM brightness control works as well (that was just plain STUPID to not expose that, given that the hardware is perfectly happy to do PWM.)

Banging around in the code got me down to 25ma with Wifi enabled (~40 hours of standby) and about 4ma with Wifi off (~4-5 day standby), assuming you also run Juice Defender (Qualcomm has a SIMILAR problem with their CDMA modem that we also don't have source for when data is connected - bastidges!); it's not so much that it doesn't go to S3, it's that the RIL gets banged with interrupts at a ridiculous rate when data is up and as such you don't get much sleep time.

I'm sure there will be similar compromises but I've been doing kernel work for more than a decade; it doesn't skeer me :-)

(Incidentally if you look at "Tickerguy" on Github and grab the "android" repo as the base for a "repo init -u ..... -b gingerbread" you'll get a merge of your stuff and mine that builds for the Triumph on Virgin Mobile.... :-))

I like CM7 a LOT; the Triumph severely tested my patience due to lots of run RIL crap. The 911 problem is one that will be tough for me to work around because I can't call 911 to debug it - if I COULD then it would be easy, but as it stands if I start trying to test it I suspect the guys in the cars with bubble machines on top will show up at my door.
[Vibrant Android Development] CM Wave:
Our Vibrants need support (and hardware acceleration, and all the other ICS goodies). Don't drop it, please :(
[Vibrant Android Development] a2296455:
Genesis, thanks for tackling this problem. however, it has already been fixed. Eugene373 has already done months of work and released a kernel that is totally meant for the vibrant. I suggest you incorporate his kernel into CM and work from there!

Thanks!
[Vibrant Android Development] Genesis3:
If he has source on Github, that sounds like a good idea. If he's not releasing source then there's nothing to work with.

PS: I have his kernel and tried it. I still have power issues with standby drains in triple digits in milliamps. That renders the phone a 10-hour wonder at best if you don't use it at all - completely unacceptable. IF source is public I'll work on it, but if I can't get kernel source then there's no point in working on this at all, since the problem(s) are in the kernel - not the user space.
[Vibrant Android Development] a2296455:
Eugene said he released it because it's GPL. He said he was going to try to incorperate it in CM but he needs help. I don't know if he's on GitHub or not though...
[Vibrant Android Development] Genesis3:
If it's not on Github that's where it needs to be put. It's trivial to set up; getting the command structure down is a bit of fun (I come from a CVS world as 99% of my work over the last decade+ has been in FreeBSD) but the basic principles are the same.

Once it's on Github I can fork it, set upstream on it and track his efforts along with mine and he can see my work as well. That's the best way to go about this.
[Vibrant Android Development] ginzberg:
Genesis3 - Really happy to see a Vibrant owner that has experience with the sorts of issues that plagued its CM7 implementation. This is not meant as any sort of disrespect to the sgs cm7 folks, I know that they have been pretty much supporting the phone with their hands tied behinds their back, and it has been incredible. Thank you for your interest, and I look forward to following any progress you find.

Eugene's contributions have been polarizing. Many users are fans as he produces kernels and roms that may advertise solutions. Developers question his motivations and practices as he does not contribute with github pulls. Personally, though I have tried his work and in many instances been thankful (first taste of froyo, gps in froyo, etc.) I do question his testing methodology. He is a hobbyist, and that is fine, but not necessarily something to base future work off of.

P.S. I have made donations to Eugene and other ROM publishers over the last year. I value their commitment, and this is in no way meant as a bash.
[Vibrant Android Development] Moped_Ryder:
Odd

His Github was in his sig:

https://github.com/eugene373

they block it at work so I cant see if its in there.
[Vibrant Android Development] renardk764:
Genesis3, I can test any 911 fixes for you. I work for at a 911 center in Texas and have the ability to let them know I'm testing without getting in trouble. PM me and i'll get you my email address.
[Vibrant Android Development] mohamobo:
I'm with you..

Thank you guys so much for your hard work, many of us (if not most) are very grateful!
[Vibrant Android Development] Genesis3:
Looks like Streamline IS there. Will pull it and see what we got.
[Vibrant Android Development] Moped_Ryder:
Coolness - ya Im off work and see it now. He just did an update too btw
[Vibrant Android Development] KWKSLVR:
I still think for some people it's a situation where they've done an improper install. I mean, I can easily get 20 hours out of a battery charge. Don't get me wrong, if I leave 3G and sync on, it's going to net about 12 hours with my level of normal use, but that's about on par with every other ROM I've used.

My phone sleeps perfectly fine, over night with sync on, and through out the day while it's just laying around.

The times I've done a sloppy install, the phone DOESN'T sleep, processes run wild, Google Maps will churn on it's own, all kinds of things crop up and yeah, it'll drain at 10% a minute. People definitely do not RTFM on installing the thing. Shoot, I did and still fubared it, numerous times, until a couple of weeks ago (anyone interested in my saga can just search this thread for me).

That said, and as I've said before, I fully appreciate our dev's and it's awesome to see other people wanting to help. I wish I could do something useful for the device and for CM7 other than test things. People can complain about this or that, but what none of the whiners realize is that most of you all are STILL using CM7 anyway and that's because it really is phenomenal. For a port of a ROM with no source and missing drivers, it's fantastic. Smooth, fast and solid for what it is. I remember being on Froyo Roms based on ports and frankly, I don't find the CM7 experience anything other than superior to those experiences.

You guys trolling and rehashing the same known issues over and over need to stop act like whiny "99%ers" and appreciate the ton of hard work that people have put into YOUR device for FREE so that you can enjoy the option. Again, think about it. People are putting their time and knowledge into work that they don't even get to reap the rewards from (using the final "product") and all they get in this thread is whining and moaning. There's nothing wrong with reporting bugs, there's nothing wrong with asking if this or that has been fixed (although you should just be reading the nightlies) but SEARCH the thread and STOP rehashing the same things every two freaking days.

---------- Post added at 08:33 AM ---------- Previous post was at 08:26 AM ----------

Speaking of bugs, I've noticed that, even after fresh installs, activating Mobile AP takes two tries. The first time will get "error" the second time will work perfectly. Activating it from the Power Control widget never works. Custom SSID, and custom password on WPA2 PSK security.

I haven't seen any mention of it in this thread, maybe I'm just searching the thread with the wrong terms?
[Vibrant Android Development] Genesis3:
What I need on this to get started is the following:

1. Phone connected to the computer with USB Debugging turned on.

2. EVERYTHING OFF (Wifi, Bluetooth, etc) and prefer a clean load (no apps sitting in the background, although if there are I can still work with it - it just makes it a LOT harder as there will be a bunch of unrelated crap in the logs.)

3. The following TWO commands running:

adb logcat >some.file

adb logcat -b radio >some.file.2

Then call 911.

Once it blows up let it sit for a minute or two. If you get a fault out of the Phone process acknowledge it and see if you get a chain of them (you probably will - if so ack it a few times and see if you keep getting them), then terminate those two LOGCATs and send them to me.

What is

probably

happening is that there's an undocumented async upcall being made out of the radio into the RIL. If you look at the RIL code in the framework you'll see that this will throw an exception upstream, which is very bad - it results in faulting the phone process and you're all done.

I had to deal with this on the Triumph when doing the CM7 port as Qualcomm was sending up undocumented async upcalls; in some cases you can just add a case for that specific upcall and ignore it, depending on what it is. In others you have to figure out what that particular upcalls is and how to handle it, or the RIL will keep sending it as it's not being acknowledged. In the latter case it's a *****, but in the former it's literally a 30-second fix to the code.

This shouldn't be particularly difficult to run down and fix but without the ability to trace and debug it (which means being able to dial 911!) you can't do jack and crap. If it IS an unhandled up-call it will be instantly obvious from the above traces as the RIL code will log the exception. If that's what's going on I can stick a dummy "case" in there that ignores the upcall and build another copy of the CM7 release, then post that up on Mediafire and we can see whether it works, since you can dial 911 to test it. If DOES work I can then toss the change up to Gerrit since that one (unlike all my butchery for the Triumph!) should not impact any other device, unless Samsung was so nice as to use an already-existing RIL function code and overload it, in which case it gets much more complicated to do "right."
[Vibrant Android Development] rsdunn:
Admins please remove these useless posts.

They drive down the morale of the already stressed thread, no use in keeping bad karma posts when everyone knows and agrees to certain limitations of this phone. Think positive or don't post.
[Vibrant Android Development] KerryG:
I am on Team Whiskey Bionix 1.3.1, its fast, stable, GPS works great. Is there a good reason to switch yet?
[Vibrant Android Development] napalm393:
hows the battery life on this?

thats the only thing keeping me away from 2.3 roms
[Vibrant Android Development] AustinKnight45:
^^^

LOL It hasn't been out for 24 hours nobody knows, also it is a GB rom so.... I'm going to flash this and check it for all the common bugs:o
[Vibrant Android Development] MailenJokerbell:
Pretty smooth and cute, doesnt recognize my SD card and after installing the Gapps it went on a force close marathon.
[Vibrant Android Development] Emama:
It does recognize the SD card,

it is in different pathway now (somewhere above /sdcard, for me that's quite odd)

btw how could I install thinkfree office now?

The flashable zip file I used to use does not work
[Vibrant Android Development] napalm393:
lol oops i guess youre right. someone please give an update about battery life when they can. thanks!
[Vibrant Android Development] MailenJokerbell:
Thanks, I looked and yes, it is there.

/mnt/emmc

Kind of uncomfortable, but as long as it works...

Now I just wish **** stopped force closing.

And so far it looks like it's only Google-related apps.

Music, etc.

ALSO, I know I may seem like a whinny little noob but, maps says I need to have data for it to work.

I am both connected to Wifi and Mobile data so wtf?

edit: NVM about maps. Installed another version I had around over it and now it works.

edit2: Nevermind. Now the only force close left is from Music, the latest version. But I guess I can part ways with it, too.
[Vibrant Android Development] DonutYankee:
Installed this straight over 7.1 and it works fine.

Only issue I'm having (had it with 7.1 from earlier 10/10, too) is that when I get a notification the LED buttons light up until I unlock the phone. I can't seem to find the setting to disable this. Can anybody give me a hint on this?
[Vibrant Android Development] hazy4days:
Go to settings cyangenmod settings then interface. Led notifications then uncategorized go to messages n led mode n force off
[Vibrant Android Development] daffyno:
the in calling volume is always at the max. If i set to mid range on the next call it come back to the max!

Anyone has this problem?
[Vibrant Android Development] SamsungVibrant:
Are you all getting GPS to work straight out of install?

If so how long does it take to get a lock?

It's taking forever to get a lock, did you all do anything special to get GPS performance to improve?
[Vibrant Android Development] strictlyrude27:
I think I wrote this in General just now:

see sig, below. i and other users have had good luck with it, but ymmv
[Vibrant Android Development] SamsungVibrant:
How do you get contact names/numbers to pop up by dialing in their first few numbers and letters of name?

For example to call my dad, I can go to dialer and dial 323 which spells DAD, but his contact info and number doesn't pop up automatically for me in the dialer.

Make sense?
[Vibrant Android Development] chirantan.f:
even though i installed given GAPPS package, i still had to install all the google apps from market, which wasn't a big issue, but now my gmail wont sync, i have to sync it manually, is there anyway to get it syncing automatically?

---------- Post added at 03:11 AM ---------- Previous post was at 03:09 AM ----------

that functionality is not integrated in CM7 or any other AOSP ROM, its in TW based dialers, but you can get it by using 3rd party dialers such as go contacts or go contacts EX.
[Vibrant Android Development] mainevent3405:
Function works just fine on Stock Miui which is an AOSP rom, so this statement is not true.
[Vibrant Android Development] fileboy22:
Lol ur dum
[Vibrant Android Development] EricDET:
As long as gmail is checked in Settings: Accounts and Sync and you have Sync Automatically checked it should sync just fine... Mine does.

On another note.

After reading through this thread, there are way to many questions being asked that have been known answers to for a LONG time... Use the search button people.

1,100 posts and a guy can't figure out you have to install gapps to get market without asking someone??
[Vibrant Android Development] jay661972:
this sealboy did flash the rom with cwm 2.5.1.2. no prob nd no fc.
[Vibrant Android Development] mainevent3405:
Learn to spell the word DUMB first smart guy!
[Vibrant Android Development] Oxirane:
MIUI is built from CM7, which is AOSP. MIUI's got a lot of other custom MIUI stuff built in though, such as the T9 dialer, Emojii support, etc, which stock android does not. Go try a Nexus phone, and you'll see that stock dialer has no t9 dialing... hopefully they add that in ICS, even my old dumbphone had it :/

I highly suggest Go Contacts til then. It looks sharp and works great. :)
[Vibrant Android Development] danpaganelli:
been searching like crazy cannot seem to find a solution:

I am using this with Simple Mobile, and cannot send or receive MMS messages. Any suggestions? I have check and APN settings for Simple Mobile are correct. :confused:
[Vibrant Android Development] Genesis3:
BTW Eugene's latest update appears to fix the sleep problem but breaks Bluetooth (entirely.) I can't live with no bluetooth so it's a non-answer.
[Vibrant Android Development] danpaganelli:
Hey I figured it out and will post in case anyone else is having MMS issues with CyanogenMod 7

All I did was erase the TMobile APN (it comes with both Tmobile and Simple Mobile), and it worked. So even if you have the one you want to use selected, it looks like having the other one just here messes up MMS. Hope it helps anyone else.:D
[Vibrant Android Development] chadhoard:
What is the best kernel to use with CM7?