yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] makelegs:
Atinm-

Thx for dropping by the thread, and adding clarification to this matter. All of your development work is greatly appreciated. While some folks may have a hard time accepting your position, I think I can understand and really don't blame you one bit.

While you don't know me from Adam...please feel free to reach out to me if I can help the cause in some way. Sounds like vibrant is dead even for ICS. But should some opportunity present itself, I'd be happy to run some builds and I'm sure these #crackflashers would gladly help test some stuff out. Same exact thread exists for captivate and fascinate.....same offer applies there, too.

-Cheers
[Vibrant Android Development] nomadrider123:
You don't deserve a working rom. A classless act like you have been posting just shows how much of a momma's boy you really are. ;)
[Vibrant Android Development] robertd0619:
Vibrant is very much alive for ICS. Checkout neobuddy ICS. Version 7 is about to drop soon with the gps fix and hopefully video recording fix hence the ics source code release for the nexus s which is what neo needs to fix it. :-)
[Vibrant Android Development] atinm:
Actually, the reason is all of them put together and it was the 911 issue that broke the camel's back (the others are really the same reason if you think about it - the hardware is weird, which is why 911 doesn't work, we don't have the Vibrant so we can't test anything anyway, and then finally the guy who decided to take it upon himself to try to contact his employers to "blacklist" me professionally while sending me personal emails with all kinds of insults in them and made it unpleasant to work on the Vibrant and then there are users like you that I didn't mention as a reason for the Vibrant really being unpleasant to work on). Oh, and I'm glad I am no longer working on the phone because I hate the thought of users like you using work that I have spent days and nights on.

Everyone else, go back to Samsung framework based ROMs - the risk is too high otherwise. The same goes for the ICS builds - they'll have the same issue. Vibrant AOSP builds are really just meant for developers now until someone can fix the 911 issue.
[Vibrant Android Development] atinm:
I really have no solutions to offer on the Vibrant - the best I can say is that someone needs to go thru their framework code and try to figure out what exactly happens when the emergency call connects. This will mean decompiling the framework from the Vibrant and most probably extending the SamsungRIL.java code that we wrote to support Galaxy S and Captivate and had hoped would also fix Vibrant. Turns out even SGS2 uses SamsungRIL from us just fine, it really is just Vibrant (and maybe other tmo samsung phones - we don't have Hercules fully working yet to know whether that has broken 911 as well).
[Vibrant Android Development] masterotaku:
Seems to be a fairly straightforward explanation. I am unsure why it is creating any drama (except among drama queens).

If you want to direct any unresolved anger, direct it at T-Mobile and Samsung. They have the source and documentation needed to resolve the issue. Whether or not they will actually care is another matter entirely.
[Vibrant Android Development] makelegs:
CM 10.1

The wait may be over, guys...

Skanky 10.1 is compiling as we speak! (assuming it completes)

Just a reminder...this is untested, as I don't own a vibrant, and this is literally my first attempt for 10.1 on vibrant. Newest gapps are mirrored on the site or in goomanager. I have absolutely no clue if a full wipe is needed. I didn't have to wipe on grouper or toro. But in all fairness, I ran into some funky stuff on toro and wiped a few times before I figured it out (still may not have needed to wipe, though). When we moved to JB some of the aries folks were having to flash 2 and 3 times before it would "stick." Be prepared for anything!

Sooo....please make a backup, first. (DUH!) Be prepared to wipe if needed or preferred, and to try a few different ways/times. And if one of you figures out or already knows some vibrant-specific trick, please share with the room. :)

Cheers.
[Vibrant Android Development] :
I just got my hands on this phone from a buddy. I'm using until my Galaxy S III get sent by Asurion and it's been a pretty great phone so far. The GS3 doesn't even have a 10.1 alpha yet lol

Can't wait for your build to finish, thanks for the hardwork

edit:downloading now :D
[Vibrant Android Development] mohamobo:
Running without problem. Thanks for the love.
[Vibrant Android Development] makelegs:
Good to know!

Any trouble flashing?
[Vibrant Android Development] mikka06:
No troubles here. Flashing was ok on phone with EU bug.
[Vibrant Android Development] josh2020glacier:
Cm 10.1 skank running pretty good just a few clitches here and there but other then that great work. Thanks
[Vibrant Android Development] samsgun357:
Hey josh, can you elaborate?

I'm thinking of jumping on one of the 4.2 ROMs but want to do my recon first. I've been running P.A.C.man ROM for the last 2 weeks and really dig it. Its gonna be hard to leave.

Thanks buddy

I am Jack's complete lack of surprise.
[Vibrant Android Development] josh2020glacier:
In on it now everything is great its smooth most of the time once in a blue moon thing slow down a little then are fine again. Not a big deal. Trust me when i say give it a try im really loving these new features that 4.2.1 are giving us.
[Vibrant Android Development] josh2020glacier:
Yes yes keep the 4.2..1 updates coming lol
[Vibrant Android Development] josh2020glacier:
In loving the update def. See aliitle improvement in the speed. Only issue i see is the home screen dock devider does not show.
[Vibrant Android Development] makelegs:
Similar report from manta user. I think I just confirmed on grouper. I use nova on everything, so I don't really recall what trebuchet it's supposed to look like.

Either way...it's probably the "wallpaper hack" I added. I'll drop it, next build, unless it gets updated.
[Vibrant Android Development] josh2020glacier:
Yes I'm actually using the new xperia ICS launcher and everything works great thank you.
[Vibrant Android Development] danilkov:
makelegs, I'm having an issue with the tethering. If I configure it to use WPA2, N7 fails to connect with the "authentication problem" message. WPA works, though.
[Vibrant Android Development] makelegs:
Funny you mention that...I have the same problem using tethering from toro. Open & WPA both work, but WPA2 is a no go. Could be a samsung prop file problem. Truth is I'm not sure.

As long as WPA works, I'm fine with it. Keep in mind that the vibrant 10.1 build is even moar unofficial than most! Lots of work still to be done.

#notforthefaintofheart
[Vibrant Android Development] mohamobo:
WiFi are working fine for me except Bluetooth not working, cant turn on.
[Vibrant Android Development] makelegs:
I'm having serious issues just getting this to build again. There is a Bluetooth commit that seems important to your problem. Not sure what the compiling issue is though. I'll keep trying to sort it out.

#lifeofacrackflasher
[Vibrant Android Development] Androidwhiz:
WiFi isn't turning on for me. Will kernels from cm10 work with this ROM i.e. sephamore 2.5
[Vibrant Android Development] gunks:
Nope. You would need a 4.2 specific kernel. They are most likely underway from Devil and Sephamore.
[Vibrant Android Development] samsgun357:
And maybe semaphore as well. Lol

I am Jack's complete lack of surprise.
[Vibrant Android Development] Dougfresh:
I'll just leave this Sema kernel for 4.2.1 for the 959 here for a day :D. *deleted *
[Vibrant Android Development] makelegs:
Did that last build work, guys?

More importantly...did lockscreen sliders work???
[Vibrant Android Development] josh2020glacier:
No not really as soon as I flash fc's system ui. I also tried to flash your first build then update to no success. Sticking with your last build. Thanks
[Vibrant Android Development] mohamobo:
Same me :(
[Vibrant Android Development] makelegs:
Please test

I need someone to test this build and confirm function before I u/l anything to euroskank, please...

http://goo.gl/HxGoY
[Vibrant Android Development] josh2020glacier:
Give me a sec downloading and testing

Edit-----------------------------

so far o good everything seems to be working great thankyou. I had no problems installing this time around. All is good go ahead and upload to euroskank.

Thanks dev.

By the way that was with a fresh install. Feel free to p.m. me with test if you need.
[Vibrant Android Development] makelegs:
Thanks for testing man. I feel like I caused a week of pain for folks on multiple devices by uploading derped builds. So I really wanted to make sure that the next build actually works!

Regards
[Vibrant Android Development] mohamobo:
Confirm working no system ui FC and blue tooth working too... :good:
[Vibrant Android Development] josh2020glacier:
Im glad to see that you care so much about your builds and the people in the xda community that right there alone makes your roms so great.( t.l.c) thankyou
[Vibrant Android Development] makelegs:
Can't have folks scared to flash! :)
[Vibrant Android Development] josh2020glacier:
O yeah let us know if you do any last minute changes cause I see this build ain't posted on euroskank website yet.
[Vibrant Android Development] makelegs:
I think we're back to business as usual. Had to get my repos nailed down so that manta and vibrant both work. They appear to, now. Next build will upload and tweet as usual.

:D
[Vibrant Android Development] closedcircuit:
Just did a wipe/format and flashed this along with gapps (gapps-jb-20121130-signed)MD5 FDA2660E94D9B9079B23E7B67EF012B0. Upon boot into Android setup, I get system ui FC. Basically the same thing I've been getting with 1201 and 1204.
[Vibrant Android Development] josh2020glacier:
No prob for me
[Vibrant Android Development] makelegs:
Any chance you flashed the wrong file?? I, for one, have done that many times. If not, re-d/l and flash again.

Hope that helps. I'm pretty sure it works ;)
[Vibrant Android Development] josh2020glacier:
Hey man I just flashed 3 times just to see if I can make it not boot bit it works no prob for me.
[Vibrant Android Development] makelegs:
Dammit! It's got that "boots every time" bug! :D
[Vibrant Android Development] josh2020glacier:
Lol
[Vibrant Android Development] josh2020glacier:
I see an update for me.

This update is great lock screen looks real good

Thanks

New update is off the chain def a daily driver for me let you know if any bugs come up.
[Vibrant Android Development] gunks:
Running a lot smoother and bug free than 2 weeks ago (Along with Semaphore). Thanks a bunch man.
[Vibrant Android Development] sourcewop:
Hello , i see no instructions for flashing, me currently on unofficial cm 10.1 alpha. Some 1 please give me instructions

THanks
[Vibrant Android Development] gunks:
Flash Jelly 10.1

Flash 4.2 gapps

Optional flash of a kernel

Reboot

Deliciousness

If you start seeing problems... just wipe and reflash... simple as that.
[Vibrant Android Development] josh2020glacier:
Been running all day now the latest build. All seems good. Got everything themed out. Thanks

Edit........8:28am................12/21.......

On build 1220 the 2nd one so the latest build. Everything runs great just camera lags a little for me. Thanks
[Vibrant Android Development] jpchopper:
Mine keeps getting the sd card not mounted error, hit or miss getting it to work. Don't think last build had that problem for me, looking forwards to next build.
[Vibrant Android Development] josh2020glacier:
I've been running for few days no problems what so ever.
[Vibrant Android Development] jpchopper:
Edit:

1220 is not the latest, it ran good for me also. The 1223 release is the one giving me problems.
[Vibrant Android Development] josh2020glacier:
Yes and I have been running 12/23 for a few days no problem at all. But I was on 12/20 then did wipe dalvik and cache and installed 12/23 all is good for me got it themed and all.
[Vibrant Android Development] jpchopper:
Good for you I guess, mine didn't start messing up until the 1223 version. Possibly unrelated, but in the mean time playing with some other ROMs until a new version is out.

Really pleased with the GPS lock time, but everything fc due to sd card drives met nuts. Perhaps there's an easy fix but I don't know it.
[Vibrant Android Development] gunks:
I don't know if this is a Jelly or CM10.1 bug but... When I take a picture with the stock Camera app it'll continue to take 2 more pictures after the first, one after another until the app freezes and then crashes. I've checked my settings, both default and mixed and still the same outcome. I even did a full wipe/flash today and still the problem persists. Any help is appreciated. Thanks.

(On latest Jelly nightly, along with 1212 gapps, and Semaphore kernel).
[Vibrant Android Development] makelegs:
Hmmm....first I've heard of that one. Not sure
[Vibrant Android Development] c-pimp:
Just tested my camera, never used it on jelly, in currently on cm10.1 12.28 nightly and do not have any problems....
[Vibrant Android Development] gunks:
Well it used to work for me... This has just happened with the past few nightlies in the new year. If anyone else on a Vib can test it on a more current nightly that'd be sweet.
[Vibrant Android Development] gunks:
So I figured out it most likely has something to do with the HDR setting in the Camera app. Does not work and when applied bugs out the camera as I described before. I switched to CM 10.1 official and it works perfectly.
[Vibrant Android Development] makelegs:
why not just turn the setting off?
[Vibrant Android Development] gunks:
Believe me I tried but once you enable, or try to enable it, it seems you can't revert it and bugs out for some reason.
[Vibrant Android Development] testomat:
New Update

cm-10.1-20130321.0840-SKANKY-vibrantmtd.zip

http://goo.im/devs/Euroskank/jellybro/vibrantmtd
[Vibrant Android Development] makelegs:
Device retired

Greetings folks,

I regret to announce that I am retiring this device from my personal stable of builds.

I've never owned an Aries phone, so without these builds I might not have met many of you. I appreciate all of the support that has been shown to this build. I am certain that our device paths will cross again.

For now, I will continue building skank for tf300t, grouper, and manta. I will likely start building for Flo, today. Hope to see all of you around, again. I'm amazed that these Aries phones are even still in operation, out there!

TIME TO UPGRADE!!! :D

Thanks again for all the love!
[Vibrant Android Development] jrongi1:
We hate to see you go but we understand. Thanks for all the time and effort you put in on our behalf.

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] Dougfresh:
Jelly Bro is golden man. Thank you Makelegs so much. This ROM is badass and should be on top. Thanks again
[Vibrant Android Development] Cooptx:
I understand that OP dropped support for this ROM, but can somebody upload the latest build? With his permission of course :3 I recently wiped my SD card and no longer have this ROM and I want to return to it. Sadly, it appears that the download has been removed.
[Vibrant Android Development] i n f a m o u s:
After observing atinm's response to every negative post relating to CM7, I have to say I really respect you for replying in a very mature and polite way despite how ungrateful or unappreciative some of the members are.
[Vibrant Android Development] makelegs:
There are lots of those types of builds being worked on for many devices. I am only interested in a CM9 variation, as that's what I'm set up to compile. I don't own a vibrant, so non-CM ROMs don't matter at all to me. That does not, in any way, imply that those ROMs are not perfectly good products. In fact....they might be your only ICS option for an unknown/indefinite amount of time, unfortunately.
[Vibrant Android Development] Exel:
^ Great read, thanks.
[Vibrant Android Development] ali1276:
OP, maybe we should turn this thread into CM9 now. http://xdaforums.com/showthread.php?t=1363593

That is super stable. All we need is a kernel dev that can change button mapping, audio routing, and GPS with every new build.
[Vibrant Android Development] Genesis3:
I9000 builds (including of CM9) will

probably

have the 911 calling issue. Beware.
[Vibrant Android Development] Genesis3:
Incidentally, here's another interesting tidbit.

Attempting to force your local landline to be an "emergency number" (which I attempted to do to test some things) is a bad idea :)

The code did indeed pass down my local number to the radio, which turned around and called 911 anyway, despite what I had told it to dial. That was interesting...... and not to be done more than once by accident.

It appears that any "Emergency" call passed into the radio is automatically dialed as whatever the emergency number(s) are that are programmed into the SIM irrespective of what YOU keyed. Beware.
[Vibrant Android Development] PowSniffer0110:
Yes great read! Thanks for the info given... I really hope we can get this fixed and get some real support. CM team seems like heavy-headed ass holes that are better than everyone. Glad to see we still have people that care about this phone and care about general problem solving and not throwing problems to the side that are beyond them.
[Vibrant Android Development] es7241:
So basically 2.2 based roms would be the only ones without this bug?
[Vibrant Android Development] Genesis3:
2.2 T-Mobile-based ROMs. I would not trust those from other Galaxy S-series phones.

In all probability, yes. There is at least one "port" that does (from testing) have 911 calls go through but as noted the radio layer CRASHES when it does -- although the call does not get dropped. For obvious reasons I would not expect it to work if ever used "in anger" -- it might, and might not when it really has to, which is even worse than knowing it's broken.
[Vibrant Android Development] Jasonhunterx:
I would say ecotox but he fell of face off the earth I think
[Vibrant Android Development] makelegs:
As device branches get merged into CM9, I will compile them. It may or may not ever be relevant to this device, though, by the sound of things. Current merged devices are sparse. Primarily just Nexus S and G-Nex. Been trying all weekend to get LTE G-nex to build, but either my end is jacked or something in repo is (prolly on my end). I got the AOSP to build, but it wouldn't boot. So I just continue to wait for the actual developers to do their thing. I'm not smart enough to do much else. In due time (hopefully soon) there should be CM9 skangs coming, but so far it's been pretty frustrating...especially having to run my g-nex stock/rooted so far. :eek:
[Vibrant Android Development] jrafael:
Just for testing I tried crisys rom port (I9000 based) dialed 911 phone ran one time then it disconnect itself and radio interface crashed, it showed at like stop sign in place of signal bars, I tried to re start the radio by going into airplane mode, but the radio didn’t responded to that so I have to adb reboot to get my phone working again.

I didn’t wanted to keep testing any other I9000 based rom for obvious reason, but If we all (end user) make at least 1 call, we can at least determine which roms have 911 working correctly.

This needs to be a community effort and just not the work of a few.
[Vibrant Android Development] atinm:
What you forgot to mention is that I asked you first whether you were willing to work in the CyanogenMod repositories.

You refused and wrote that anything you did would not pushed into the CyanogenMod repositories even if you had access to them but rather it would be up to us to pull from your repositories, just like your Triumph repositories that are not part of the CyanogenMod codebase because you haven't taken the time to get them merged yourself, leaving the ~1300 users of the Triumph have remained outside of CyanogenMod support.

You were not willing to work within the CyanogenMod repositories, nor use Gerrit, and therefore, there was nothing I could say to the team to persuade them to allow you access to private repositories given your preference, and I stopped responding to you.

But that didn't stop you from writing more snide emails about the openness of CyanogenMod. I don't have the time, nor the inclination, to deal with a diva developer who has ~1300 users on a phone that isn't part of CyanogenMod (compared to say ~80,000 users on the phones I developed CM for, including may I add, the Vibrant), I responded by telling you to put up or shut up.

I stand by my words, if you wanted to work as part of the CyanogenMod team or at the very least, within the CyanogenMod code base - I would have persuaded the developers of the Hercules to give you access even though I do not have any control over them because, at the time I thought you had something to offer us. (Your "strong response" included personal insults directed at me and a threat to put me in your "email blacklist" that you share with your employers, but I'm going to leave that alone).

CyanogenMod is a large team, with developers working on many phones and the usual mode for developers is to work within the Gerrit review system for open repositories and within the codebase for closed ones until release. But as you weren't willing to work within the CyanogenMod repositories, you have no reason to be upset when you didn't get access to them, and you can wait until the device maintainer does a release to get at the Hercules source just like everyone else who has never contributed to the CM code base.

As far as disabling emergency calling on the Vibrant, but continuing support for the Vibrant with a disclaimer, we're not going to leave this phone without the ability to dial emergency numbers - and therefore we're not going to resurrect support for it. If this issue is solved, and there are developers willing to maintain CyanogenMod for the Vibrant , then it is very possible it will get resurrected.
[Vibrant Android Development] CM Wave:
Wonder why they haven't announced they're dropping the i9000.
[Vibrant Android Development] javacody:
Can't we all just get along?
[Vibrant Android Development] Genesis3:
I doubt it, but true open source -- were it to exist -- would make it irrelevant whether we did or didn't. It would also probably lead to a branch of Android that was actually (1) decently documented, (2) maintainable without being part of a "cabal", and (3) that version would ultimately "win" in the market as it would be more stable and more-easily debugged when problems were found.

Google blew it, basically, by not mandating this in some form or fashion (e.g. GPLing the entire codebase) and have IMHO compounded that error over time with out-of-date or simply missing documentation and a lack of it internally in the code itself. Then you add the proprietary extensions which are fine in the area of user experience but when they extend to functional elements, especially those necessary to talk to a

regulated

network, you have problems.

This will ultimately turn into a huge problem for Android as time goes on, as enterprise customers are going to have an increasing number of concerns with security over time. Spaghetti code, undocumented nonsense and proprietary bits for the sake of doing it sounds great and makes for nice usability upticks right up until your company's security is penetrated and intellectual property is stolen. Right about then things get rather dicey; CIQ is a tiny piece of the trouble that could be coming down the pipe in that regard.
[Vibrant Android Development] atinm:
I9000 and Captivate have no issues with 911 on their networks - the problem is a tmobile issue with the Vibrant.
[Vibrant Android Development] atinm:
I9000 and Captivate have no issues with 911 on their networks - the problem is a tmobile specific issue with the Vibrant and possibly other Samsung phones on the tmobile network that use the framework code we wrote (rather than Samsung's closed code).
[Vibrant Android Development] ursubpar:
didnt roman create a fix for 911 months ago?

He implemented it into his trigger rom

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