yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] atinm:
I should apologize - no, it isn't the whole community. But there are enough users here that come off way too rude to the developers. But we normally don't care what any user thinks/writes. If we could do the Vibrant easily enough, like we have been, we would have continued. We don't want the device, because we will not be able to continue without source, and it would be wrong to accept the device or donations (I don't accept donations anyway) if we feel we cannot really continue. We still might continue depending on how quickly we get Captivate and Galaxy S working (we are almost done), but there are more and more issues as we don't have the source we need and Vibrant has actually fallen behind its own peers due to lack of source. Things like lack of 911 are also just plain dangerous, and I'd actually encourage you to stay on Samsung ROMs just because of that!
[Vibrant Android Development] Demetris:
So atinm you say that if GB rom comes out from T-Mobile your are willing to support ICS on Vibrant?
[Vibrant Android Development] VeryCoolAlan:
GB source...so if a GB rom came out where have to wait another month or two for source ..
[Vibrant Android Development] lawalty:
Don't worry guys about the nightlies.. I own a HTC G2 and also haven't gotten a nightly CM7 build in about 3 days.

Believe you-me guys! I'm also suffering from LOF (lack of flashing). Sometimes my day isn't complete until I flash the lastest CM7 nightly build.

The Vibrant has some MAJOR life in it. Hell, I'm on a G2, which without the 4G data speeds, its mostly an inferior phone.

The magic of the xda devs will continue.
[Vibrant Android Development] barribow:
Look at this link:

http://www.compare-cellphones.org/Samsung-GALAXY-Nexus-vs-Samsung-Galaxy-S-II

It's not only a matter of camera MP, or sd card. There are more things: like faster data speed (not important for me), GPS-assist (important), super AMOLED plus (important), 32 GB vs. 16 GB (important).

I think this is mostly marketing issue because samsung doesn't want everybody switch away from Galaxy S series to a google phone so they didn't include some of their features.
[Vibrant Android Development] atinm:
No. I said if we have the binaries and source we need and it is easy enough to support ICS on Vibrant, we'll do it. Otherwise someone else will have to do it. Getting the binaries we need is unlikely though, let alone getting the source.
[Vibrant Android Development] KWKSLVR:
A few things:

1) Only Europe is stuck with the 16 GB variety. Verizon is getting 16 or 32.

2) Those max data speeds are theoretical. You'll NEVER come close to that. The fastest I've ever seen my 4G MiFi was 21 Mbps, and that was LATE at night. Tmobile and ATT will never come close to that. Non-issue.

3) Samsung put the best screen possible. Most people haven't even seen it in person and are judging it because it's pentile. I'll take the higher resolution.

4) GPS Assist makes a slight difference if you just got off a plane because it's starting with cell tower triangulation. I've had phones with it and with out it, it's not a big deal.

You're not talking about the difference between a 2 seconds lock and a minute lock. It's spec sheet hype.

If you like the SGSII, get it, it's a great device. Either way, don't buy any device with the expectation that it'll get this or that (like ICS). Especially on Tmobile.
[Vibrant Android Development] Oxirane:
As a little side note.... The Galaxy S1 screens are also pentile, as are the s2's
[Vibrant Android Development] Kaik541:
galaxy s 2 is not pentile. you're right in that the galaxy s 1's are, though.

the "plus" from SAMOLED+ is the lack of pentile.
[Vibrant Android Development] barribow:
I guess we have to wait and see what variations will come to US. There is no question that it's a better phone compared to s2, because it is 6 months newer too. But my question is that why they dropped some useful features on their latest phone? It can be only marketing/business strategy.
[Vibrant Android Development] KWKSLVR:
It's been hashed and rehashed all over XDA. The Nexus is a dev phone. Google decided that MicroSD was a hindrance and removed it after the N1. MicroSD has ALWAYS, I repeat, how ALWAYS slowed down smart phones. I'm glad the hardware is gone. I still don't know anyone that walks around with a pocket full of microSD cards trying to use their phone as a laptop replacement.

Google did not "remove" anything. People talk like google "removed" crucial thing. These are things that no one can really tell a difference with like S+++AMOLED, a useless eleventy billion megapixel camera, the ability to make toast and a battery that last 17 years on a charge.

People that look at hardware specs are missing the entire point.
[Vibrant Android Development] creeve4:
Why have no nightly's been built for the last week?
[Vibrant Android Development] b1337:
Aids
[Vibrant Android Development] bosox86:
pathetic..
[Vibrant Android Development] KWKSLVR:
You must have missed the memo over the past several pages about CM7 support for the Vibrant being dropped.
[Vibrant Android Development] atinm:
Actually no - it is just buildbot that died and its disks have to be rebuilt. We are considering dropping Vibrant for ICS - and even that is not a done deal, we'll see how it goes after we're done with Galaxy S and Captivate.
[Vibrant Android Development] creeve4:
Thanks for the answer and potentially good news :)
[Vibrant Android Development] VeryCoolAlan:
This somewhat made my day!
[Vibrant Android Development] Demetris:
I really enjoy this kind of news.
[Vibrant Android Development] mohamobo:
Love u atinm.. <3
[Vibrant Android Development] fishman0919:
That's great news... Here's to hoping we don't get left behind
[Vibrant Android Development] RoxAbout:
Yes Im glad I missed the memo that said that you "KWKSLVR" speaks for the CM7 Dev team...

That said I'm glad you missed the memo about the hard drive crash and they rebuilding..AND Still working on the Vibrant.

oh ye of little faith!
[Vibrant Android Development] KWKSLVR:
If the CM7 team doesn't want people to think that they've dropped Vibrant support, then I suggest they don't respond to all the incessant *****ing in this thread with responses stating that they're going to drop support, and then act surprised when people assume they have. Frankly, I've grown weary of reading every post in this thread, especially the way the last few weeks have been (referring to end users, not our fantastic developers).

I'm going back to a flip phone and a beeper. ;)
[Vibrant Android Development] mrbradeli:
I really hope you guys decide to keep supporting the Vibrant. I know our user base might be a little... retarded at times, but there are some out there that REALLY appreciate your work. The only reason I haven't thrown my phone away and wasted money on a Nexus S mid contract is you guys making CM7 run PERFECTLY on my Vibrant.

You guys really are awesome.
[Vibrant Android Development] asdf916:
Please do go back to a flip phone and beeper so that you can stop with the same generic responses defending the CM team. I understand your intentions mean well, but your smart-ass responses aren't any better than from those not in "the know."
[Vibrant Android Development] KWKSLVR:
One second thought, I think I'll just hold on to my Vibrant and keep responding since it seems to annoying all the 16 year old whiners. Thanks for playing though. ;)
[Vibrant Android Development] wergeld:
I am on CM7 (last "official"...think it is CM 7.1.0.1). This does not happen every time but enough to be really annoying/frustrating. I am using default everything - no different kernel or GPS fix or modded settings.

Sometimes when I hit the power button to check something I am unable to unlock the lock screen. It does not matter what lock screen I use from the CM7 settings.

What happens is I swipe to unlock (no code lock or anything like that) but the 'ring' or 'bubble' does not move and my phone stays locked. It then turns the screen off in the normal time out span. The capacitive buttons on the bottom of the screen light up when I touch them so I am thinking my digitizer is still working (and when the phone does unlock I have no issues using the touchscreen). I do not believe my phone is "lagged" or anything after I wake it up. I can see the clock re-adjust itself if it has been a while since it had done so, the network icons are animated, I sometimes see the grey icon switch to green, the WiFi connect, etc. So my phone is doing something.

When I logcat the phone when this happens I see no information relating to unlock screen being used or that the touchscreen is actively responding.

When I do turn on the power button I see the following:

The second to last line is when the screen times out.

The ways I have seen this fix itself in the past are:

1) Phone screen goes off and I try again and it works

2) Reboot to recovery and wipe Cache and when rebooted it works

3) Reboot to recovery and wipe Dalvik Cache and when rebooted it works

4) Reboot to recovery and wipe both Dalvik and Cache...uh...Cache and when rebooted it works

5) Plug into USB charger (either wall or PC) and unplug it and it works

In all 5 scenarios it eventually fails again.

I should also mention that the battery is in any state of charge. It does not matter. It also does not matter when I had last successfully unlocked the phone.

Any ideas here?
[Vibrant Android Development] Pielvrx:
If i had atinm's skills, I'd build you a custom ROM for you for Christmas and have it take a poop on you lol
[Vibrant Android Development] Jasonhunterx:
What's so special about CM9? Don't get new features it add to ics
[Vibrant Android Development] aznpandaman:
Headset Controls?

Has anyone been able to get the headset controls to work on CM7? Specifically those 3 button and mic wired headsets.

I've tried search though the forum but couldn't find any solid leads.

Thanks
[Vibrant Android Development] creeve4:
Not supported by CM7 for the Vibrant
[Vibrant Android Development] xuanphucn:
People please help me. Idk why the battery life of this rom is so short. one day with couple phone calls. that sucks. any suggestion?
[Vibrant Android Development] Exel:
What kernel are you using?
[Vibrant Android Development] xuanphucn:
i use bali kernal http://xdaforums.com/showthread.php?t=1181167 :mad:
[Vibrant Android Development] Goten310:
I use the same kernel and I average 10 hours daily. Have you tried rebooting your phone as soon as you take it off the charger? That has worked for me and allows the phone to enter deep sleep when the screen is turned off.
[Vibrant Android Development] barribow:
Go to settings -> about phone -> battery use

Check maybe you have an app that eats your battery
[Vibrant Android Development] t1h5ta3:
Im on eugenes kernel, 15 hours and change, 55% left... No issues here...
[Vibrant Android Development] vahdyx:
What's the best way to upgrade CM7? I don't mean actual method of doing the upgrade, I mean more of less hassled way right before the flash.

Meaning is it better to not wipe your SD Card flash and just upgrade redownload everything from market. Or wipe SD card, flashand download everything from market. Or titanium back up, flash then restore from titanium. Or not upgrade at all. The only issue I'm having now is HD video recording and random restarts once every other week.

Thanks in advance
[Vibrant Android Development] CM Wave:
http://www.cyanogenmod.com/blog/cm9-progress-update

Glimmer of hope?
[Vibrant Android Development] Kaik541:
that post was made by cyanogen himself, who mostly deals exclusively with HTC devices and a few sony ericsson ones (lightly). he has little experience with samsung devices (when it comes to CM, especially since he works with them and reverse engineering technology of a company you work for is ridiculously illegal), and, quite simply, it isn't really up to him if vibrant will be supported or not.
[Vibrant Android Development] :
I thought porting from the Nexus S isn't all that bad. Sure GPS will probably not work but we already expect that.

I think we might see official CM9 support due to how easy it appears to be to get ICS working on the Vibrant. We already have several solid roms.
[Vibrant Android Development] betam4x:
You guys do realize that Cyanogen works for Samsung now, right? :)

It isn't illegal for him to work on Samsung phones, it could technically be breach of contract if samsung asked him not to, however, i think the reason they hired him IS because of Cyanogenmod. I've never seen any actions that indicate that Samsung doesn't like the firmware/mod community.
[Vibrant Android Development] atinm:
Except that if he were to start releasing CyanogenMod for Samsung phones, giving out code that is supposed to be internal to Samsung (the exact pieces of the code that we are missing for any number of Samsung phones when it comes to CM), that would be breach of contract.

It isn't Cyanogen who is deciding whether Vibrant is going to get continued support - he doesn't have one either, and he doesn't do development for it. The people who have done most of CM7 development for Vibrant have been part of teamhacksung, and a couple of other developers here and there. We will decide whether to continue supporting Vibrant, and that totally depends on how easy/hard it will be to support it once Galaxy S and Captivate are done. We shall see - but we're mostly tending towards letting other developers step forward after we release the source for Galaxy S and Captivate which should be soon after CM9 is released.
[Vibrant Android Development] KWKSLVR:
Also, it's not necessarily like he has total access to everything that Samsung puts into a device. It's cool he got hired by Samsung, but a lot of people have the wrong impression of what he's doing. It's not like he's running Samsung's entire Android Software Development Team. I don't know why people think that him being hired by Samsung will somehow translate into every Samsung Android Device having CyanogenMod support forever.

You either have source or you don't. But either way, people still aren't going to get their hands on the things that are proprietary to Samsung like driver/modem/gps et al source. Even if someone leaked it to you, and you used it for development, you'd promptly be sued for theft. ;)
[Vibrant Android Development] notverycreative:
One of the ICS ROMs we have, the ICSSGS port, works incredibly well on Vibrant. A few things crash and the GPS doesn't work (shocker), but other than that it works very well. If ICSSGS is the team working on the CM9 SGS port, it looks like we will have at least a kanged CM9 build for a while.
[Vibrant Android Development] flapane:
Are the nightly builds still stuck at 16-Nov?
[Vibrant Android Development] notverycreative:
Yup :/
[Vibrant Android Development] VeryCoolAlan:
Eh I'll probably just poop.
[Vibrant Android Development] sjohnjuan:
I have been away from the vibrant and cyanogen section for a while. Are any of the latest releases any good?
[Vibrant Android Development] hurtz777:
Build 182 with Neo kernel is solid and flies!
[Vibrant Android Development] parmijo11:
Yes, once it was done worth download unsuccessful I was able to reinstall.
[Vibrant Android Development] nirogu325:
I can clearly read 05152011 (hint: the date of the update :eek:) on the Mod Version section.
[Vibrant Android Development] atinm:
That is updated. It is mostly the INITIAL that is broken, but since it is common code - I removed all.
[Vibrant Android Development] atinm:
Yes, at first we thought it was an error with all updates - now it looks like just initials, but code is common so at the moment I have taken them all off. You can still install the usual way using CWM recovery.
[Vibrant Android Development] parmijo11:
My thoughts exactly, its working so on good.
[Vibrant Android Development] 12paq:
that's cool. do you think you will put it back up through RM? no eta requested or needed, of course.
[Vibrant Android Development] Sevensix9:
everything failed, so I retried a couple of times no progress, so I ODIN'd to bone stock, everything works, loaded up CM again, same issue. I'm gonna pop back over to trigger and see what happens.

-Alex
[Vibrant Android Development] MStrawder:
I'm running the 05092011 build with the stock kernel and I've been bitten by a rather bad bug. If I use the 2G/3G toggle button in the notification menu to switch to 2G mode, the very next time data becomes disabled and I re-enable it, android.process.phone crashes non-stop. The only way to stop it temporarily is to enable airplane mode. Aside from that I have to wipe data. I've been able to recreate it twice now, but of course I never thought to try and get a logcat.
[Vibrant Android Development] iynfynity:
I think that's a known issue. If you want to toggle 2G only try this.

1.turn off data connection

2.enable 2g only

3.turn on data connection.
[Vibrant Android Development] squish_123:
DOUBLE EDIT: Ok, I installed the gapps .zip from CWM and still no market app etc. I'm pretty sure I picked the correct version, the latest zip for CM7. Any ideas? Should I install the apks manually?

EDIT: JUST READ THE FAQ NOTHING TO SEE HERE THANKS GUYS!

Well I've got a strange issue, and I'm not sure what's going on.

This is the fist time I've messed with my wife's vibrant. I have CWM installed, and I've loaded your INITIAL nightly build from your website.

Everything appears to go ok, CWM starts to flash the rom but about halfway through the progress bar it reboots into CM7 already (not sure if this is a problem or not).

Upon booting I find that I have no market app, and it doesn't want to run through any of the normal initial android setup.

Am I doing something wrong or have I missed a step in the process? Any help would be appreciated, thank you very much!
[Vibrant Android Development] MStrawder:
Will give it a try. I didn't find anything in this thread specifically on it, so figured I'd ask. Using the SuperPower app to control it at the moment and it seems to be working fine.
[Vibrant Android Development] SamVib:
you need to flash the latest google apps.

Download it from here:

http://goo-inside.me/gapps/gapps-gb-20110307-signed.zip

Flash it using Clockwork Recovery and do a reboot. Self explanatory from there.
[Vibrant Android Development] phantomzer0:
You need to install the gapps package.
[Vibrant Android Development] squish_123:
Yeah, I'm dumb and didn't read the FAQ first, I tried the latest GAPPS zip for CM7, installed it via CWM but no luck... no market, no nothing... any ideas?

edit: I've connected to wifi and rebooted.. still nothin'.
[Vibrant Android Development] tsnow247:
So I tried out a different rom, now I'm coming back.

Just to clarify I don't have to use Odin anymore? (for the initial kernel.)
[Vibrant Android Development] cojonesx:
correct, its all in the install instructions
[Vibrant Android Development] barribow:
I installed it and noticed that it doesn't have swype. How can we add that?
[Vibrant Android Development] cojonesx:
same way you should get swype for any rom beta.swype.com
[Vibrant Android Development] Sevensix9:
So here is the situation, the phone was fully wiped, loaded CM7, installed current Gapps, it fails every install, then magically loads a about half of them, market shows them as uninstalled and I cant install any new apps. Also the fails show the package names not app names in the fail. I'm at a loss, everything was fine last night when I first installed it it, till i was messing with dialer apps and f'd the dialer up beyond repair so I reloaded CM now i have this issue.
[Vibrant Android Development] usalee70:
Try T9 flex from the market. Better than swype.

Vibrant ROOTED and on TOXIC CRACK :-)
[Vibrant Android Development] creeve4:
I'm running build 157 and have noticed a bug with the Notification toggle for sound.

To duplicate:

1. In Settings/Sound: Set Vibrate to "Never"

2. In Settings/CyanogenMod Settings/Interface/Notification power widget/Widget buttons/Sound modes: check "Silent" and "Sound"

3. Use the sound toggle in the notification bar to toggle to silent then back to sound.

You will notice that the Vibrate setting in Settings/Sound is now set to "Only in Silent mode"

Can anyone confirm if this bug is fixed in the newer builds?
[Vibrant Android Development] chingoo04:
I have recently downloaded the latest nighlty. I have using the stable version and thought i would try this one. Anyone knows how to fix the touch keys LED light to stay on when the screen is on. It goes away in about 2 seconds. In Nexus S i could use NS tool and change the option but I'm not sure on Cm7 tried going to all the option and i can't find. Anybody?
[Vibrant Android Development] bigtom624:
It's in CyanogenMod settings. Look under Interface then LED Notifications. Then you have to configure each one individually.
[Vibrant Android Development] creeve4:
Will someone running 182 please try this and let me know?
[Vibrant Android Development] androidmonkey:
Has the issue with app data been fixed with CM7 ?
[Vibrant Android Development] VeryCoolAlan:
Nah
[Vibrant Android Development] creeve4:
What is the issue?
[Vibrant Android Development] vahdyx:
Sorry I have to noob it up, but what's the difference between this and regular CM7
[Vibrant Android Development] paypalbid:
same sh*t, different night.
[Vibrant Android Development] androidmonkey:
Thats disappointing... I really liked this ROM but I couldnt install many apps because of the diskspace limit. I mean, how are people using this ROM?

@creeve4, this issue

http://xdaforums.com/showthread.php?p=18164157&highlight=datadata#post18164157
[Vibrant Android Development] jay661972:
Cm7.1.0.1 had old kernel and the new nightly comes with new kernel, option to hide battery, etc. Performance is the same for me.
[Vibrant Android Development] ironlood:
Honestly I get that issue from time to time... I use an app called app cache cleaner that sometimes helps... if that don't work i boot into CWM wipe the caches and all that... if that still fails I do a full clean install
[Vibrant Android Development] creeve4:
Recently I starting experiencing some "screen of death" issues.

For clarification: "screen of death" = screen is off and device will not wake, only a reboot into recovery (3 button method) is possible

I've been running nightly 157 with the stock kernel since it was released and have never had a single "screen of death," until 2 days ago... the phone started having SOD's 4 - 5 times per day.

I had not installed any new apps or changed any settings for at least 1 week prior to the SOD's starting. I want to emphasize, nightly 157 ran perfectly (no SOD's) for weeks and weeks.

I ODIN'd to JFD, wiped my sdcard and flashed nightly 182. I have been running it since last night and started getting SOD's again about 2 hours ago.

Any ideas??
[Vibrant Android Development] ipnekgs:
Are you OC/UV???

I only had one SOD with nightly 182 but I OC/UV Nero kernel to 1.2 GHz. My issue with nightly is that it is doing something to my MicroSD card (32GB). It never "damage it" but after a few nightlys it breaks my MicroSD card and it gives me the "Damaged SD card" and no data is accessible. That is my only complaint.
[Vibrant Android Development] creeve4:
No OC/UV.

Strange thing is that everything was running fine for weeks, then the SOD's started...
[Vibrant Android Development] Phateless:
Run it all stock tw for a couple days to test. If no problems then back to cm7. Could be hardware.
[Vibrant Android Development] sjohnjuan:
same thing happend to me..
[Vibrant Android Development] makelegs:
Kang builds now available...

To whom it may concern...

A new thread for CM7 kang builds with CHERRY-PICKS has been started. It can be found HERE. Currently including custom boot animation, miui battery mod, and some other nice additions. Your participation is welcomed!

:D
[Vibrant Android Development] atinm:
We are sorry, we are going to stop supporting the Vibrant due to issues with 911 calling. Our advice to Vibrant users is to Backup user data via something like Titanium Backup, flash back to stock or another Samsung based ROM and restore user data. No other ROM (that we know of) has 911 working. We cannot get it working without code from Samsung related to the RIL and Audio interactions and neither is likely to be getting to us any time soon.