yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Demiurgic:
volume fix is easy go into /system/usr/aries-keypad.kl and switch volume up and volume down

you can always use androidscreen http://code.google.com/p/androidscreencast/ to see recovery.

If you must flash while away from a computer flash zip thru rom manager but if something goes wrong you might be stuck without a working phone.

However, most things short of roms/modems/kernels you can just manually do thru root explorer anyways:D
[Vibrant Android Development] Br1cK'd:
Hey White, not so much a question about the build here, more about the uh, interesting tags at the bottom of the page.

One of these things is not like the other

One of these things just doesn't belong

Can you tell which thing is not like the others

By the time I finish my song?

I swear I'm not the wiseguy, but thats funny, nearly made me cover the monitor in a fine mist of coffee. :D
[Vibrant Android Development] bartek25:
lol not to trash even moew but i just noticed them and bu......haha :P
[Vibrant Android Development] buddahlou:
Thanks Demiurgic it worked!!!! :-)

(This is to get the volume keys working the right way)​

For those interested i've attached the file already changed just extract .zip file and using root explorer copy it to the system/usr/keylayout folder and change permissions to rw-r--r-- and reboot phone afterwards that's it :-)

I posted this yesterday also....

IDK if someone else would like to give this a try...... I've been using the MIUI music app, i've listened to music outloud, through my headphones and computer speakers and i haven't had any issues with the sound and phone going crazy.

I've attached the .apk just place into system/apps using root explorer and change permissions to rw-r--r-- and reboot phone afterwards..

Hope this helps!!!!
[Vibrant Android Development] Slow50:
This is pretty nice, It is fast, and fun to play with. Keep up the good work.
[Vibrant Android Development] Zeno78:
unable to get phone to be recognized by windows when in Download mode.

says device not reconized. Yes i have the usb drivers installed

Windows 7 64bit
[Vibrant Android Development] DonutYankee:
Odin won't see it? Have you previously connected it to your PC via USB with this ROM? I noticed windows detects and installs new drivers with this ROM.
[Vibrant Android Development] Demiurgic:
you could try a different usb port or going and uninstalling device thru device manager then unplug for a few sec and the pc should re-install the driver

or..just use heimdall it comes with a usb driver
[Vibrant Android Development] Zeno78:
that fixed it. Thanks!

Going back to eugene's ROM listed in my sig... Need wifi calling to work and pandora doesn't play nice etc...
[Vibrant Android Development] DonutYankee:
Bug: definitely a memory leak. Using this for two+ days now and the slowdowns seem to be caused by the phone running out of memory. Doing a clear memory in task manager solves the issue for a time until it comes back.
[Vibrant Android Development] Locksmith81:
This is no real 4g yet in NA for GSMs at least for AT&T and T-Mobile. Tmo is on UMTS HSDPA not until their LTE network rolls will full 4g @ 21mbps

Sent from the Galaxy Honeybread-CM7
[Vibrant Android Development] jfs999:
The way forward from here...

I have a quick question for the next step. I understand that this ROM is a beta version. It works pretty well. I have noticed a lot of the same issues that I have read through out this thread. There isn't much with this ROM that I cannot live with for a short while. It does seem really fast and snappy.

My question is this, since we cannot get to recovery while using this ROM then is there going to be a path out of here whenever a update to this ROM comes out? I guess the next rendition of this ROM will have to be a TAR so that we can ODIN it? Or can I use a Clockwork to install any new ROM without having to boot into the actual recovery mode?

Also, since I'm asking questions, can I use ODIN to push a ROM that would normally be flashed via recovery?

Thanks folks.

JS
[Vibrant Android Development] Rawat:
http://xdaforums.com/showpost.php?p=11827847&postcount=1059

http://xdaforums.com/showpost.php?p=11831371 - doesn't have Swype fix.

http://xdaforums.com/showpost.php?p=11844952&postcount=1100

EDIT: Had to reboot for it to work.
[Vibrant Android Development] Rawat:
You'll need to use ODIN to go back to an older ROM, then update to the newer one.
[Vibrant Android Development] Rawat:
There's a problem with Samsung's minfree settings, and the ROM wasn't set to free memory at the correct settings.

I set Activity/process management to normal in Spare parts, and it seems to fix it. (haven't used it much since then, so I'm not sure.) Tried Aggressive, but it kills LauncherPro every time I would load another app :rolleyes:
[Vibrant Android Development] Demiurgic:
you can use rom manager (with supercurio's test kernel) to install but the best way is

- just to odin/heimdall a kernel with working recovery without auto reboot or just batt pull when done

- then flash the new rom (pretty much how you install cm7)
[Vibrant Android Development] Demiurgic:
sweet thanks ..also your file in the 3rd link is mis-spelled missing an "i" in build
[Vibrant Android Development] Rawat:
Thanks :-) Fixed.
[Vibrant Android Development] DonutYankee:
Rawat, so regarding the link you posted, one needs to simply adb push or use Root Explorer to replace the build.prop and reboot? Anyone tried this on their Vibrant? Results? (Rawat, I see you are in London so I'm just trying to make sure this will be fine with the Vibrant)
[Vibrant Android Development] player4lifeov:
Can I flash this over cm7?
[Vibrant Android Development] Demiurgic:
yeah just use root explorer to replace build.prop and reboot. Also, supercurio updated his kernel with the new build.prop.
[Vibrant Android Development] apollo15rover:
Pretty impressive. Best I am getting with CM7 is about 1550..
[Vibrant Android Development] DonutYankee:
Odd. For some odd reason Root Explorer tells me the system folder is read-only and I cannot replace build.prop. I have never encountered this before. Any suggestions? I definitely have allowed Root Explorer superuser permissions.
[Vibrant Android Development] wildklymr:
Click mount r/w at the top in root explorer
[Vibrant Android Development] DonutYankee:
Thanks, wild. That did the trick. I never noticed that button...embarassing.
[Vibrant Android Development] plane501:
where is the voodoo kernel(ext4) ????:confused:
[Vibrant Android Development] mr.orange303:
I don't care about wifi calling or gps. But I do use internet,vids and music a lot.

Is this stable for a person like me?

And is the data ok now?
[Vibrant Android Development] cundiffr:
yes at times, but if you have alot going on in the browser it will lag really bad and then clear up

other then that its really stable, i used it all day, calling using the headset toggle widget works great, data is there! the occasional lock up which required a battery pull was there but i didnt care, but its smooth as hell, almost a daily as it is, i cant wait for a more stable voodoo kernel, this is "great success" for vibrant owners ;)
[Vibrant Android Development] mr.orange303:
Awesome thnx. Ill wait a little longer.
[Vibrant Android Development] DonutYankee:
Yeah, browser is really a sore spot. Sucks up RAM and brings the whole thing down. I use Dolphin browser with this ROM for now and it's been a bit better.
[Vibrant Android Development] avio07:
So just to make sure this is a ported version with no touchwiz 4.0? Is it faster? Stable?
[Vibrant Android Development] Demiurgic:
Here is temp fix for the audio until the problem with H2W switching can be fixed. Phone will now boot normally - thinks no headphone is in. You still have to use the toggleheadset widget for headphones. Also, if toggled to headset the calls will be like before - speakers switched. To install just unzip and use root explorer to push services.jar to /system/framework and reboot

http://dl.dropbox.com/u/14392977/tempsoundfix.zip
[Vibrant Android Development] wildklymr:
Awesome work, you've done a lot for this build. Thanks! I'm currently running cm7, but i've been following this because of the jit optimizations for the hummingbird chipset. I think cm7 uses the snapdragon jit. I might try this for a while if they get working recovery.
[Vibrant Android Development] roffee:
how about linpack

ooo.. new voodoo can't work in vibrant?
[Vibrant Android Development] roffee:
linpack is still 14, so weired
[Vibrant Android Development] iwapu:
Wanna give this a try. Does the provided kernel has BLN or Voodoo sound?

Accroding to OP kernels other than the provided one wouldn't work. Still the case now?
[Vibrant Android Development] STiGLOGiC:
*Firmly places face in to palm*
[Vibrant Android Development] shockjock:
I downloaded the beta but still have the volume key issue. Also cant find the toggle headset. This rom is amazing. cant wait for final product.
[Vibrant Android Development] iwapu:
Same issue with volume key.

Toggle headset is a widget. Add that widget to your screen, not trying to find this app in the list
[Vibrant Android Development] buddahlou:
If you guys go back a couple pages Demiurgic found a fix and I created a .zip file to fix the volume key issue. Download the .zip and follow the instructions I put, let me know if it worked out for you....

The toggle headset is a widget :-)

Hope that helps..
[Vibrant Android Development] dxtrlabs:
Hey is there a way to port the tvout from this to CM7? just curious
[Vibrant Android Development] DonutYankee:
Any word on possible updates? Any progress?
[Vibrant Android Development] hitman818:
Its in the third post.
[Vibrant Android Development] wildklymr:
I think you misunderstood. I think he was talking about the tv out, as in using a cable to view output on a tv, and not the tv shutoff animation since cm7 already does that.

And i wish this could happen, but dont see it easily being done.
[Vibrant Android Development] gatesmarch123:
Maybe i missed something but i cant hear incoming calls.
[Vibrant Android Development] wildklymr:
Yes you did miss something. Use the toggle headset widget. Otherwise you need to use speakerphone
[Vibrant Android Development] gatesmarch123:
Ahh...thanks. <-----Moron.
[Vibrant Android Development] Whitehawkx:
Update coming soon guys. I have calls routing properly to the ear piece and music playing normally/through headphones as well. You can hear calls on headphones but when you plug them in the other person can't hear you. Trying to work that out and then I will post.

Before anyone asks. No I do not have the GPS working yet.

Edit: Headphones during calls work great now. :D
[Vibrant Android Development] DonutYankee:
Awesome! Looking forward to this. Is the browser/RAM issue still present? I'd like to report another bug. After some time, YouTube videos won't play in this ROM without a reboot. What I mean is that all works fine for a while, but after some time tapping on a video just brings you to an infinite loading screen with the spiral; all other apps work fine as this goes on.
[Vibrant Android Development] HRodMusic:
your simple amazing, i cant wait for this update, would it include that new voodoo kernel?
[Vibrant Android Development] Whitehawkx:
RAM issue can be easily fixed by installing spare parts and setting activity/process management to normal. I will be including that app in the update.
[Vibrant Android Development] Whitehawkx:
I'm going to run several installation tests to make sure the voodoo kernel and framework with crt animation can be installed at boot. If everything works then yes they will be included. :)
[Vibrant Android Development] DonutYankee:
Thank you! With that solved this ROM should be all good to go for a daily driver.
[Vibrant Android Development] HRodMusic:
this is awesome cant wait!! thank you soo much!
[Vibrant Android Development] NCn1:
After messing around with this ROM for 3 days i came with an issue after odin back to stock.

E: Can't symlink /system/bin/su

E: Failure at line 16:

symlink /system/xbin/su SYSTEM.bin/su

Installation Aborted.

this happens with any ROM i try to install.

dam...now my phone just does a loop in the Android system recovery and wont go back.

This ROM ****ed up my phone, period.
[Vibrant Android Development] Whitehawkx:
Funny how I've odin'd and installed stock roms with root np after flashing this. Going to be doing it in just a bit, again. So no, this rom did not **** up your phone. If you are getting that error it is a problem with the update script in the rom you are installing and has NOTHING to do with this rom. Period.

Or you don't have the su binary in the correct folder. Again, not this rom's fault. Period.
[Vibrant Android Development] heero01:
Did you try odin back to a stock firmware and have a 512 pit and checked partition
[Vibrant Android Development] dligon:
so is this going to be an update no theme or one when gps is fixed
[Vibrant Android Development] NCn1:
Ok. where does the su binary go into?
[Vibrant Android Development] Whitehawkx:
Look at the update script for the rom you are installing. It will either go into /system/bin or /system/xbin. And just to be clear I am not talking about the Superuser.apk. It's a binary simply labeled "su" no extensions.
[Vibrant Android Development] NCn1:
btw this happened while trying to flash lastest Bionix ROM. alright im doing another odin, if it happens again ill try this.

Thanks
[Vibrant Android Development] Whitehawkx:
When you Odin use the 512 pit and check re-partition.

Also, double-check to make sure the rom you downloaded finished downloading completely.
[Vibrant Android Development] Julianmgn:
Hey white what about recovery was that fixed? Like can it be seen? Sorry if it was asked already
[Vibrant Android Development] Whitehawkx:
It's unfortunate, but until we get our own Vibrant specific leak we probably won't be able to see recovery. You have to install the sbl.bin to not get the double rainbow screen, but NOBODY SHOULD DO THIS. I haven't done it because it will cause problems. I was able to install a rom from this rom using Rom Manager (using Voodoo kernel). It installed everything just fine you just couldn't actually watch it install (double rainbow screen). I waited less then 5 minutes and it rebooted and installed the rom normally. I'm actually right now about to begin doing many diff installation tests to ensure this is as user friendly as can possibly be. Will also test leaving this rom and going to other builds as well and will include full-on instructions for everything.
[Vibrant Android Development] deeznutz1977:
if your running the voodoo kernel u can see recovery on your computer google android screencast
[Vibrant Android Development] Whitehawkx:
Install coming from voodoo went without a hitch. Update will include Supercurio's latest GB Voodoo kernel and the CRT animation (you won't have to install separately). :D

Let me run a few more tests and will post soon.
[Vibrant Android Development] DonutYankee:
Is there a timeline for an updated ROM being available? Just asking since my phone is charged right now and I'm seeing if I should wait for this or go back to stock KA6 for now.
[Vibrant Android Development] Whitehawkx:
I would say within the next 2 hours. And that is being generous with the time.
[Vibrant Android Development] DonutYankee:
Thank you very much. This is a great ROM.
[Vibrant Android Development] gonintendo:
Thanks for the update. most devs would say eff off.
[Vibrant Android Development] gonintendo:
Is it possible to replace the bouncy scrolling with the orange glow?
[Vibrant Android Development] NCn1:
I gave up trying to flash a ROM ;(

ODIN 3 times.

when i try to flash it keeps saying replacing stock recovery with clockwork mod recovery, i tried different versions of clockwork, if it doesnt say that, error line 16 pops up even after moving su to xbin or bin. i tried install rom from sd option but it just keeps replacing and going back to recovery main menu.

This really sucks.
[Vibrant Android Development] scrizz:
HAHAAHAHAH

Whitehawx

good stuff
[Vibrant Android Development] Whitehawkx:
First time it says "replacing stock recovery with clockwork mod recovery" it WILL reboot back into stock recovery. You have to do it a second time for it to bring up clockwork recovery.

EDIT: Just odin'd to stock JFD and got into clockwork recovery no problem.
[Vibrant Android Development] NCn1:
i did it 10 times not exaggerating.

i moved su to xbin and i got the same error, i moved it to bin, same error, i put into both files, same error. idk wtf is this happening.

u didnt get an error when trying to flash a ROM?

What can cause the error? i check ur rom files and other rom files and su is in the same place in all of my rom files...
[Vibrant Android Development] Demiurgic:
I odin'd back to stock and flashed this and other froyo roms from stock without issues. You might just want to backup all your stuff then wipe your internal and reformat with the 512 PIT.
[Vibrant Android Development] cashyftw:
Thanks so much for the update, I will donate immediately (: thanks for putting up with us.
[Vibrant Android Development] jeproxx2:
This rom progressed quickly.. Cant wait to try it out
[Vibrant Android Development] TricH:
When will it be uploaded?
[Vibrant Android Development] :
So just to b sure the only way i can go to another rom is too odin to stock right?
[Vibrant Android Development] Whitehawkx:
Sorry guys. It seems calls are routed properly, but the person on the other end can hear a faint echo when speaking. I'm trying to correct this now. Upload is delayed for time being.
[Vibrant Android Development] hitman818:
Take your time. We can wait.
[Vibrant Android Development] boimarc89:
can we flash GPS fix for this as well as a Theme?
[Vibrant Android Development] pegasus912:
Will RC1 contain the updated build.prop or whatever it was that enabled the Hummingbird optimized JIT? I saw that someone on one of the earlier pages figured out how to enable it, I may be mistaken about whats going on.
[Vibrant Android Development] jcc332006:
Yeh I gave up trying to flash this also. When it first came out I was successful flashing this, but I moved on to another rom and when I decided to reflash again I kept getting the same message. Don't know why. I also odined several times and flashed as I usually do and still no sucess. Also kept kicking me out to recovery main menu.:confused::(
[Vibrant Android Development] Demiurgic:
So will we still have to use the togglewidget or does it switch properly now?
[Vibrant Android Development] Whitehawkx:
So I'm gonna have to use Demiurgic's services.jar instead. The problem is when you typically plug in headphones to talk on the phone the receiver's sensitivity increases so the person on the other end can hear you even if the phone is a few feet away. Well I changed the audio mapping so when it thinks headphones are plugged in the sound comes out the earpiece. The problem is the receiver's sensitivity is still increased b/c it think you have headphones in. As a result the ppl on the other end of the phone can hear every little thing they do.

So in the end I'm gonna just use Demiurgic's services.jar. Only catch is that you have to use the ToggleHeadset if you want to listen to music or talk on the phone through headphones. I will try to upload this before going to bed, if not it will be tomorrow. I have spent 8 straight hours messing with this and need to take a break and spend time with loved ones. Update is coming. It's still not perfect, but is much better than the existing rom. Sorry again everyone.
[Vibrant Android Development] gonintendo:
I have an issue with the browser in the beta. It seems that when you scroll long pages it just stops scrolling randomly.
[Vibrant Android Development] NCn1:
i wanted to flash something else, i wasnt trying to flash this. Im saying that i got all this issues after installing and using this ROM, could be the ROM that cause it but according to OP that its not possible that the ROM ****ed our phones up. I odin 5 times, eugenes files, ive tried every version of clockwork, every recovery version, i tried flashing without clockwork, i tried clockwork but i get a loop of replacing stock recovery with clockwork. i already reformatted my sdcard. if any1 has a fix for this, PM me.

and when i do get thru the loop i get an error

E: Can't symlink /system/bin/su

E: Failure at line 16:

symlink /system/xbin/su SYSTEM.bin/su

Installation Aborted.

im about to go back to iphone even with my hate towards apple.
[Vibrant Android Development] gonintendo:
Thanks man we all really appreciate the work you're putting into this.
[Vibrant Android Development] mr.orange303:
Yay.
[Vibrant Android Development] C-4Nati:
When will rc1 be up
[Vibrant Android Development] Demiurgic:
That's too bad my services.jar isn't a real fix. How did you get it to switch properly I could only get it to switch to the speaker when I inserted headphones lol.
[Vibrant Android Development] Whitehawkx:
I edited the asound.conf in /ect to reverse the audio mapping for the earpiece and headphones.
[Vibrant Android Development] mr.orange303:
A hawx how close are you to rc1?

Should I wait?
[Vibrant Android Development] }{Alienz}{:
Great job!

Am I correct there are no current themes one can use with this?

Specifically interested in the Steel Blue theme for 2.2.1s
[Vibrant Android Development] Whitehawkx:
OP UPDATED!!! :D ;) :) :D ;) :)

Please please please read the ENTIRE OP. There is MUCH updated information that everyone should be made aware of to ensure safe flashing. ENJOY!
[Vibrant Android Development] cashyftw:
Dear Whitehawkx,

I LOVE YOU.
[Vibrant Android Development] :
Yay :) idc im flashing 2mm
[Vibrant Android Development] jellette:
Hey White, what was the outcome of what/who we spoke about?
[Vibrant Android Development] scrizz:
very nice, getting rid of CM7 to try this out.

;)
[Vibrant Android Development] gonintendo:
CM7 is great but the battery life was unbearable. this seems to be a nice compromise of speed, stability, and battery life.
[Vibrant Android Development] NCn1:
careful guys, after flashing this im unable to flash any ROM except for this one...i tried everything. Right now my options are to wait for a dev to pm and hopefully help me, even though somebody already told me my issue cannot be fixed but i dont lose hope.
[Vibrant Android Development] DonutYankee:
Went from Beta 1 to Stock to Atriarc and then back to Stock and now Beta 2. Just heard chipmunk Lisa. ROFL does not begin to describe my reaction when I heard that. Speaking of which, as I mentioned there, no problems going to other ROMs after Odinind to stock from Beta 1.
[Vibrant Android Development] scrued:
Were you able to odin back to stock?
[Vibrant Android Development] wildklymr:
If this were happening to me, i would try using heimdall over using odin to flash back to jfd. You need to untar the jfd.tar and load the individual files into heimdall. And for me it never let me start when i loaded a pit so dont worry about that.

Ive had times when messing with experimental stuff put me through loops of not being able to flash stuff. And even repartition in odin didnt fix, but with heimdall and the exact same jfd rom did. Its worth a try. If you already use heimdall then disregard.
[Vibrant Android Development] HRodMusic:
whitehawk! u made my night bro! your amazing! just pure amazing!
[Vibrant Android Development] gonintendo:
Did you try repartioning in odin? Because I was able to odin back to stock and flash beta 2 just fine.
[Vibrant Android Development] NCn1:
Yes I did, I re partitioned 7 times, re formatted my sd card im in froyo now, I used eugenes files. When I try to get into clockwork it just kicks me back to android sys recovery, when I put reinstall files it kicks me back to clockwork. When I put install rom from sd card it puts me into android sys recovery > reinstall files it says installation aborted.
[Vibrant Android Development] wildklymr:
What about loading up froyo, and going into rom manager and at the bottom trying to install an older version of clockworkmod recovery. Maybe the one you have in your update.zip is fubarred...
[Vibrant Android Development] Tha Maxx:
question

this may be tarded but is theme chooser a cm7 only thing or is it included in this rom?