yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] scotolsen:
so i'm uploading my initial "it works" video to vimeo. or rather it's done but vimeo has to convert it (ugh). so 30 mins unfortunately :/

no force closes but the pain in my ass right now is that the home and back keys are flipped...but that does put the home key where it is on my nexus haha. so far i detect some sluggishness but i can't decide if that's just the TW launcher or not. i'll run some tests to see how it does.

FINDINGS SO FAR (will update):

-3.5mm jack does NOT work (as OP stated) really depressing since this is my music player.

-Swype is present but does NOT work (says it is registered to another device; can someone get me a working apk?).

-my best linpack score was 14.83 so it does seem clear that JIT is not activated on this version of 2.2.

-none of the buttons work as the "home" key. both home and back function as "back" keys (so no app switcher)

-no flash in the marketplace...sigh...

-mobile AP does NOT work (will break your wifi til reboot)

NOW, WITH MORE VIDEO!:

http://vimeo.com/13778661

http://www.youtube.com/watch?v=gGmUvFfizS8
[Vibrant Android Development] rhcp011235:
Thanks truly appreciate it.

Does the mobile AP work?
[Vibrant Android Development] Anderdroid:
Any luck with getting a different launcher to work? I installed both Launcher Pro and ADW and neither are giving me the option to use them when I hit the home button (or back button)

And yeah. I imagine that swapping the volume buttons and home and back buttons to normal shouldn't be too hard to do? I'll stay tuned ;)

Actually it doesn't seem like the home and back buttons are swapped... They're just both back buttons. They both do the same thing.

And yea. The feeds and updates widget is pink? aha

Also, Facebook contacts aren't syncing properly? Like won't update the pictures for my Google contacts or show any Facebook contacts at all in my Contacts. Or well, contacts aren't automatically linking with the same names like they did on 2.1
[Vibrant Android Development] AustinKnight45:
I already had a scare with "real fix lag" just came back from the whole "flip phone ! CPu" screen think I'll watch to see how this pans out, I really thought my Vibrant was done but I think this Phone is a little harder to brick then what I thought not saying jump at every bark but just keep your schooling up. I cant wait for 2.2 or someone to touch the kernel like they did on the Galaxy like the "real lag fix" because it was really fast I'm just happy to be back to rooted stock vibrant thx to all folks on xda.
[Vibrant Android Development] scotolsen:
when i try and activate it it hangs and never really goes. when i hit back to cancel and the try again it says "error" :/
[Vibrant Android Development] dmolition:
Thanks for the video, I see there is no much difference between 2.1 and 2.2 so I will be waiting for a more stable version. Thanks again.
[Vibrant Android Development] rhcp011235:
Anyhoot, I am off to bed.

Eugene great job on getting this to work non-brickable and able to go back to US version. I hope you keep this incase we need for others :)

I am not going to flash this. as i see there is no differnce and things are broken. Ill just wait on TMO 2.2

BUT, you did beat CM on a 2.2 release :) I dont count MS_GURU one. because all it did was mess peoples radio/basebands. I only count yours :)
[Vibrant Android Development] rsfaze:
Really? First you post a link to this thread in MS_Guru bashing them and now you are saying this.

And about "beating" CM to a release.. why don't you get all of the facts before you make an ass of yourself. I can only assume you don't follow Eugene on twitter because if you did, you would see him talking to a couple members of team CM to get this Froyo working WITHOUT bricking.

This is a community of people that are here to help one another. Your negative demeaning posts help no one.
[Vibrant Android Development] tissimo:
If home doesn't work, restart to chose what launcher you want, that should work. At least thats how vanilla android was on 2.1, haven't tried with touchwiz ui.
[Vibrant Android Development] eugene373:
Um?..... that was in regards to them slide rom.

But I agree, lets not bash anyone! Its not about. Beating anyone, it's for the community.
[Vibrant Android Development] rsfaze:
and you sir are a great addition to this community :)

looks like my facts were too off.. <open mouth insert foot>
[Vibrant Android Development] didyourecognize:
so im an idiot and realized what i was doing wrong..... i really do miss swype though....
[Vibrant Android Development] DAKIDD236:
Nice job Eugene, It's running great on my vibrant! Nice to see some great developers like you and Jac on the vibrant development team!!!
[Vibrant Android Development] eugene373:
Reboot after downloading another home app. Will prompt you to choose. ..
[Vibrant Android Development] defconoi:
now that we have clockworkmod recovery why dont we all focus on creating roms for that instead of using Odin? I dislike having to flash roms via windows lol

Edit: anyone want to post a nandroid backup of 2.2? :D
[Vibrant Android Development] ttabbal:
You don't need a kernel to apply the lag fix. Check the userinit/apps2sd thread. :)
[Vibrant Android Development] Beast84:
Agreed!!! Now that we have a way to flash zip ROM's, shouldn't we use it? Or did Koush do all that work creating his recovery for nothing?
[Vibrant Android Development] mastermind278:
Eugene seeing that you jumped to the Vibrant actually makes me now consider getting this phone. Eugene knows Samsung phones way to well and will definitely have wonderful ROMs for the community.

Congrats on the baby too!!
[Vibrant Android Development] stepinmyworld:
ive been interested in flashing the froyo rom but if i cant flash it by clockworks or regular recovery, it must not be 100 percent stable. i will just wait until clockworks gives you an option to download a vibrant rom. Too scary to do this Odin stuff. it was much easier when i had my nexus. im sure there are less complicated ways because i cant stand using command promps etc.

much love and thanks to all of the developers.
[Vibrant Android Development] Digitalthug:
Odin is hangin on me all over again...I was havin this same problem with the Stock 2.1 that JAC posted. Im doin the same thing I did that solved it for me with that one...

loaded the files and stuck at "Firmware update start..." "cache.rfs"

I hate Odin............. :mad:
[Vibrant Android Development] kaizasoshi:
Congrats on your new baby boy Eugene!! May he grow to be as wise and humble as his dad..Congrats and thanks again for this awesome ROM!!
[Vibrant Android Development] Disconn3ct:
I miss swype and home.
[Vibrant Android Development] Anderdroid:
Any chance you'll get swype and the home key working?
[Vibrant Android Development] rsfaze:
he just had a new addition to his family, he posted something on twitter about being mia for a few weeks.

more than likely we will see other froyo roms come out before Eugene may get a chance to get back to this..
[Vibrant Android Development] Sawawa:
Can anyone who has installed this confirm whether or not the Calendar application in 2.2 allows you to choose a custom ringtone?

Also, is the "Vibrate only when silent" option available in the messaging application?
[Vibrant Android Development] Disconn3ct:
Input settings

So, I took a quick look at fixing home/back.

It looks like a kernel issue, although I'm not sure where it is coming from (since this flash is the same kernel as stock).. maybe the wrong modules?

getevent shows the same codes for home and back, and so android handles it appropriately. I'll take another look at it tomorrow probably..

# getevent /dev/input/event2

( Menu press )

0001 009e 00000001

0000 0000 00000000

( Menu release )

0001 009e 00000000

0000 0000 00000000

( Home press )

0001 001c 00000001

0000 0000 00000000

( Home release )

0001 001c 00000000

0000 0000 00000000

( Back press )

0001 001c 00000001

0000 0000 00000000

( Back release )

0001 001c 00000000

0000 0000 00000000

( Search press )

0001 006b 00000001

0000 0000 00000000

( Search release )

0001 006b 00000000

0000 0000 00000000

Stock:

( Home press )

0001 008b 00000001

0000 0000 00000000

( Home release )

0001 008b 00000000

0000 0000 00000000
[Vibrant Android Development] defconoi:
I think we all need to abandon odin for the recovery, we need some sort of standard, there is too many issues with odin, windows being one of them
[Vibrant Android Development] Disconn3ct:
Since odin can recover it when recovery is completely hosed, you'll need to get a logic analyzer and reverse engineer the protocol. Let us know when you have got it and I'm sure tons of people will come forward to help write native apps.
[Vibrant Android Development] ivanmmj:
The keymapping is controlled by one of the files in /system/usr/keychars/

I'm not sure which one for this device. (possibly melfas-touchkey.kcm.bin since it has the compound word touchkey in it.) I supposed you can try replacing the ones in this ROM with the ones from the 2.1 ROM and seeing if it fixes the problem. *shrug*

Same thing with swype. Try the version that came with the phone. *shrug*

Maybe I'll take a crack at it later when I get some free time.

EDIT: I was wrong. It's /system/usr/keylayout/melfas-touchkey.kl
[Vibrant Android Development] bobj:
I did try this by replacing the complete keychars and keylayout folders from the 2.1 stock and it did not change anything.
[Vibrant Android Development] th3fallen:
Do you know what that event is for the stock kernel if so just set it accordingly (not to sound condescending in any way.) :)
[Vibrant Android Development] ivanmmj:
Should be

0001 008b 00000001

0000 0000 00000000

for home.

0001 008b 00000000

0000 0000 00000000

For holding in the button, me thinks.
[Vibrant Android Development] jroid:
I'm soo pissed right now. the samething happened to me and now I cannot get into download mode. this stupid graphic keeps showing up with the phone and the laptop and flashes over and over and over and over and over and over again and never gets to dl mode. i've done virtually every combination there is including usb plugged in/out with no luck at all. i'm getting very fustrated and feel like launching it at a damn wall

EDIT: I finally got into dl mode, but the flash keeps getting stuck at cache.rfs and doesn't get any further then phone just turns black and have to re-do process again.

EDIT2: Just booted up froyo, apparently what got it past cache.rfs is u have to load the files promptly after plugging into odin then flash immediately. that's what did it for me. Glad I finally got it to boot up
[Vibrant Android Development] Andrmgic:
Without JIT, is there really any benefit to being on Froyo?

Losing ADW and Swype without the speed boost doesn't seem like a good trade..
[Vibrant Android Development] stepinmyworld:
hey people, i am sorta a newbee lol but I know a little about flashing and why isn't adding this rom easy as flashing via clockswork recovery? why having to use adb, download mode and all of this other stuff and why use a rom that disables your home button? is there any benefit to this rom? any extra widgets, flash 10.1? faster phone, better battery? hopefully someone can answer me. I'm simply curious.

please get back to me
[Vibrant Android Development] Disconn3ct:
The 0 is when you release. It issues change events, not state events. (The first one says "008b is pressed" and it is assumed to stay that way until the third says "008b is released".)

The weirdness is that that should come from the kernel, and the kernel didn't change.. (the other weirdness is that this didn't submit 2 hours ago when I hit submit. Sigh.)

I wonder if there isn't a firmware file somewhere that is being loaded. I'll take a look at the 2 images later today and see what I can turn up.
[Vibrant Android Development] Disconn3ct:
This one does use a new kernel. Sigh. So it is in there somewhere.. anyone know if we have a build env yet? (Don't send me a bunch of links to the source, that's not what I'm asking about and it is incomplete anyway.)

Once we have kernel building working (without boot loops) it should be pretty simple to fix.
[Vibrant Android Development] TGA_Gunnman:
No reason I can see at all. Other than being bored and adventurous.

I'm waiting for stock update or CM6.
[Vibrant Android Development] jroid:
I've noticed proximity sensor doesn't work either on calls, neither do the ui interactive sounds i.e sound on press and sound on unlock
[Vibrant Android Development] stepinmyworld:
lol yeah. thanks for replying
[Vibrant Android Development] eugene373:
Personally, I think everyone needs to Cut back on the Snide Remarks..

It's in a Dev. Forum for People wish to work on it, Nothing More...

If you Don't know what things do nor Offer any help on fixing things or have time that is... Don't flash.. It that Simple :rolleyes:

After all, If your Scared of taking a Risk, or Need to play 20 Question's... Just stay on stock & Unroot.

~Eugene
[Vibrant Android Development] stepinmyworld:
well those are clearly defensive remarks dressed up with a smile. we are only asking questions. You didn't even bother to answer any. In the initial post, it doesn't even say what this rom entails.... what new features are there? I don't think people are afraid but is it worth installing?
[Vibrant Android Development] eugene373:
Clearly you read into stuff that's not there, but..

For the typical User, no it's not something they would be Happy with.

For tester's, it's more than Usable.

Feature?

Use the Search.

Taking the Time to Answer in Detail?

Just had a New born, only on here posting while he's asleep.. I'm not here to Hold hands.
[Vibrant Android Development] stepinmyworld:
Congratulations BTW!!! And thanks for your work non the less man

:)
[Vibrant Android Development] eugene373:
np, always happy to help... Just strapped on time currently & lacking sleep. :)

Sorry if anything came out wrong, I'm just tired of see like 1000's of question is all. lol...

~Eugene.
[Vibrant Android Development] TGA_Gunnman:
Yeah, I didn't mean to cut you down if you took it that way. Since the G1 I have always enjoyed your ROMS and efforts. I was just answering a question with my honest feelings about it.

I mean hell you were like the second dev to get a cease and assist order (next to Cyanogen) from Google. :p You're almost android royalty. lol j/k You Suck!! ;)

My Apologies. I won't tie up your thread anymore. I was trolling here looking for success stories thinking of flashing it myself and came across a question. Couldn't help but answer it.
[Vibrant Android Development] trevorwhopkins:
Ya in all honesty if you don't know what froyo is besides a new version of android you definately should not be flashing your phone. The articles all over the web showing the leaked Tom with videos and all show exactly what's in it. Not to mention the fifty thousand articles on froyo.
[Vibrant Android Development] TGA_Gunnman:
Ok lets not make a debate about this let's squash it! Start a new thread in General if you want to debate that statement.
[Vibrant Android Development] Arr MiHardies:
Any chance of a nandroid release of this?
[Vibrant Android Development] almyz125:
Just curious on how long it takes oden to flash, it hasnt moved past this:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> cache.rfs

and its been sitting for half an hour or so.

EDIT: figured it out sorry apparently im dumb and i didn't know the sim and sd needed to be removed before using oden.
[Vibrant Android Development] mattseg:
Good call, may be a dumb question, but what if someone makes a nandroid backup that has the froyos (from the googles). Would that even work?

Then again, how would you go back, since you lose root.
[Vibrant Android Development] shan564:
I've been trying to flash, but Odin won't go past the "file analysis" message. Any idea what I might be doing wrong? My Samsung unlock code from T-mobile isn't working, so I think this might be the only way for me to unlock my phone...
[Vibrant Android Development] Disconn3ct:
It won't unlock your phone.

As to getting past file analysis, hit cancel, pull the usb/battery and put it into download mode again. Just needs to be redone and it should work..
[Vibrant Android Development] shan564:
I tried it several times, and it still wouldn't work.

So flashing my phone won't unlock it? Samsung's unlock code wasn't working... might that be because my phone is rooted?
[Vibrant Android Development] Disconn3ct:
No and no. (Although if you put the code in wrong too many times, it can only be unlocked at the factory.)
[Vibrant Android Development] shan564:
Any idea why the unlock isn't working? Or what I need to do to unlock it?
[Vibrant Android Development] SkOrPn:
Do you have a T-Mobile store near you? Just go in and explain to them what your doing, and if they get upset at you just get upset back at them and they should help you then, lol. They already provided the code, so just show them its not working and maybe someone there can fix it or provide a working code. Good luck.

P.S. Unroot your phone first though.
[Vibrant Android Development] shan564:
I'm in Australia at the moment... which is why I need to unlock it. I didn't think it'd be an issue, so I didn't bother to get it unlocked while it was in the US...
[Vibrant Android Development] SkOrPn:
Ouch.... So I presume you must be trying this from your Hotel room? Hope you get it sorted...
[Vibrant Android Development] shan564:
So there's no other way to unlock the phone? I'd expect that there must be some ROM out there that takes care of it...
[Vibrant Android Development] TRF-Inferno:
ROMs do not unlock phones. Unlocking is a separate entity of the phone's operating system.
[Vibrant Android Development] shan564:
So in other words, there's no other way to unlock it? One of the unlockers on eBay is telling me that my phone is hardlocked if I tried to input the unlock code more than three times... does that mean that there's no way to use it outside of T-mobile?
[Vibrant Android Development] Disconn3ct:
Most likely. Tmobile might be able/willing to fix it or swap it, but you'd have to go in..
[Vibrant Android Development] shan564:
I just used one of the Samsung "secret" codes to verify that the phone isn't hardlocked. I'm in Australia, so I can't just go into a T-mobile store... but regardless, there should be a software unlocking mechanism. No suggestions?
[Vibrant Android Development] BlackElvis79:
Tethering

I understand that WiFi hotspot tethering is not working, but how about USB tethering?
[Vibrant Android Development] JLundberg:
Battery life on froyo...

Just wondering if the battery life suffered any after your Froyo rom update
[Vibrant Android Development] scotolsen:
i can't stress how un-useable this is as a daily ROM. i could be wrong, but this seems to be a total dev-centric ROM for information and fact-gathering purposes. in that frame it succeeds spectacularly.

-no home button functionality

-3.5mm jack doesn't work

-flash is not in the market (among other things)

-clockwork recovery doesn't function

-lots of app incompatibilities (launchers, et al)

-JIT is not enabled

-wifi hotspot doesn't truly work

-volume buttons are flipped

so you don't get the major benefits of Froyo (flash and speed bumps) and the hardware itself is quite gimped. if you're a dev or have an interest in the cutting edge in ROMs make the leap and have it a good looksie, but if you need this to be your daily-driver you need to pass til either a) this gets updated or b) a Vibrant-centric ROM gets found.

but kudos to Eugene for making this work in the first place (and safe to boot!). this community is awesome and apparently there is nothing it can't do.
[Vibrant Android Development] mushufasas:
I just got the phone aweek ago, and I called T-Mobile for the code right in the store. Next day I got the code from them (I've been with them for 2 years now).
[Vibrant Android Development] jroid:
Has anybody tried jac's kernel while on this and see if the capacitive buttons fix or if there's a speed boost?
[Vibrant Android Development] tikidroid:
I am looking into the home button issue as well. Let me start by saying that I am an Android noob and intermediate nix user. I have the ATT Captivate.

I found some interesting things which makes me question if its the touchwiz launcher that is messing with the buttons? Again noob.

Here are my findings:

/dev/input/event2: 0001 001c 00000000 <<<I acutally pressed home button

/dev/input/event2: 0000 0000 00000000 <<<its the same for the back

E/imdg81 ( 2443): IsShutDownStarted()

D/Launcher( 2546): dispatchKeyEvent UP KEYCODE_BACK / MainMenu isOpened=false Info=false <<<<LAUNCHER daemon dispatching event as back keycode

I/KeyInputQueue( 2443): Input event: dev=0x10001 type=0x1 scancode=28 keycode=4 value=0

D/KeyInputQueue( 2443): screenCaptureKeyFlag setting 0

E/wpa_supplicant( 2509): SSS: RecvV Cmd :: [DRIVER RSSI-APPROX]

app_1 2546 2334 278988 34492 ffffffff afd0ebc8 S com.sec.android.app.twlauncher <<<proccess id 2546 is the touchwiz launcher

I used #getevent & logcat then #ps to get the PID of D/Launcher (2546)
[Vibrant Android Development] tikidroid:
I flashed back to stock ATT Captivate today and captured the same logs on 2.1. The process that logcat output after the event call for the home button is completely different than on Froyo 2.2 JP3. I guess thats because of the new kernel code.

I/AlarmManager( 2252): mWakeLock.acquire(500);

/dev/input/event2: 0001 008b 00000001 <<<<HOME BUTTON PRESSED

/dev/input/event2: 0000 0000 00000000

I/KeyInputQueue( 2252): Input event: dev=0x0 type=0x1 scancode=139 keycode=3 value=1

I/PowerManagerService( 2252): ULight 3->7 f0

/dev/input/event2: 0001 008b 00000000

/dev/input/event2: 0000 0000 00000000

I/KeyInputQueue( 2252): Input event: dev=0x0 type=0x1 scancode=139 keycode=3 value=0 <<<<<2.2 JP3 call these much differently.

I/ActivityManager( 2252): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME]

flg=0x10200000 cmp=com.sec.android.app.twlauncher/.Launcher }

V/DevelopmentSettings( 2333): onPause()

D/Launcher( 2321): launcher is resumed

D/NotificationService( 2252): onSetDisabled :: mDisabledNotifications = 0

V/SettingsProvider( 2252): system <- value=1 name=mtp_usb_connection_status

V/SettingsProvider( 2252): property: sys.settings_system_version=156

D/dalvikvm( 2252): GC freed 19874 objects / 1131096 bytes in 86ms

Processes

$ ps

ps

USER PID PPID VSIZE RSS WCHAN PC NAME

system 2252 2204 324964 64688 ffffffff afe0ca0c S system_server

app_0 2321 2204 283828 43104 ffffffff afe0d9c4 S com.sec.android.app.twlauncher

system 2333 2204 215940 29856 ffffffff afe0d9c4 S com.android.settings

------------

So on 2.2 JP3 we would need to figure out how to modify the home button event

from

/dev/input/event2: 0001 001c 00000001

/dev/input/event2: 0000 0000 00000000

/dev/input/event2: 0001 001c 00000000

/dev/input/event2: 0000 0000 00000000

to

/dev/input/event2: 0001 008b 00000001

/dev/input/event2: 0000 0000 00000000

/dev/input/event2: 0001 008b 00000000

/dev/input/event2: 0000 0000 00000000

Why can't someone with the experience and knowledge figure this out already? Sept is not too far away now, I guess.
[Vibrant Android Development] Disconn3ct:
..that is exactly what I posted earlier. The kernel is spitting out the same event for both keys, which means we need to get a working kernel. If you look elsewhere, you'll see I'm trying to get my kernel build environment working so that I can do so..
[Vibrant Android Development] ivanmmj:
Can anyone dump for me the initramfs?

(use swiftp to grab everything BUT the /system folder.)

I think all the problems here have to do with the wrong initramfs. I'll have to mess with this, later...
[Vibrant Android Development] eugene373:
You are correct, I was wondering when somebody would catch this.

~Eugene
[Vibrant Android Development] Disconn3ct:
You can get the initramfs out of the stock images: http://xdaforums.com/showpost.php?p=7431131&postcount=268

(The kernel build will accept the cpio image directly, so you don't need to unpack it and argue with the file list, etc)