yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] trailblazerz11:
On my way home now. I think I will use i9000 kernel for now. If it boots ill try to compile kernel for vibrant myself.

---------- Post added at 03:10 PM ---------- Previous post was at 02:33 PM ----------

Gets stuck at boot animation, Trying to debug now....

My logcat http://pastebin.com/YM6scQYj line 91 seems to be the fatal error.

FYI I will be busy tonight, will upload what I have, hopefully someone else can fix.

Don't download unless dev!!!!!

http://www.mediafire.com/?kinlv5xmatngv6e

Includes sema kernel, use devil from i9000 jb thread for logcat.

I have tried init.trace.rc and init.rc changes but seem unrelated to error.

Will sync and compile. Try again tomorrow.
[Vibrant Android Development] xriderx66:
get the **** out of this development section.
[Vibrant Android Development] oka1:
From the Moderator

Sorry Guys, I shoulda got on this sooner........ This is as stated before a Pre-Alpha tester essentially nothing works really.....

Remember to read my Post in General about the When to expect a Real Jelly Bean Rom....... I talked with the Real developers of ROMS and I posted their opinion as to an appox ETA in my posting.......

This is rom-cooking only and in order to prevent anyone Borking their phone.... when they have a completed ROM that Really works correctly they can open a new thread with the perfected ROM ...until then.....

..........THREAD IS CLOSED...........

caveat emptor

~ oka1
[Vibrant Android Development] taurus193:
ali1276 great job....i remenber you since froyo ROMs......THANKS......
[Vibrant Android Development] L1LK1LLERZ:
Just Great!! :D
[Vibrant Android Development] mattb6288:
i was going to get a galaxy s 3 at the end of the month when my contract ends, but once this is up and running (around beta) i think i'll wait for the better phones at the end of the year.
[Vibrant Android Development] nbhnohome:
Wow. Its butter smooth even.in Alpha stage. Cant wait for future progress :)!!!
[Vibrant Android Development] zbt1985:
Anyone have trouble getting you phone to boot back into ICS. I keep getting stuck in a boot loop...I don't particularly want to odin...

EDIT: WORKING, JUST DID A FULL WIPE, INCLUDING CACHE THEN FLASED CM9 AGAIN, THEN RESTORED MY BACKUP, SEEMS TO BE WORKING!
[Vibrant Android Development] Moped_Ryder:
What are the chances JB also has the EU bug?
[Vibrant Android Development] ali1276:
We had that when we were first porting it, but we fixed it, so I highly doubt you will get that.:good:
[Vibrant Android Development] FaultException:
How did you fix that?
[Vibrant Android Development] ali1276:
mkalter was the one who fixed it. He is from the Galaxy S forums and part of the team. I might PM him if you wanted to know.
[Vibrant Android Development] tgamble160:
Got project butter on my amaze can't wait for this to be finished gonna go on my girls phone.

sent from one badass htc amaze with ics jellybean
[Vibrant Android Development] Screwhead24:
This is just AWESOME!!! Where do I donate?
[Vibrant Android Development] Woody:
I would be extremely interested in knowing how he fixed it and what he found the cause was. I have been diligently working on the EU bug since January and have also been working with a few developers in the Captivate forums.

If you did solve it, there will be many, many grateful people to know the how and why.

Thank you for your efforts and if you would like to PM me instead of posting in the thread, I understand that too.
[Vibrant Android Development] FaultException:
I PMed who he said but no reply...
[Vibrant Android Development] xriderx66:
Hmm...

FE, you're in TAJB too?

I swear I didn't see your name there yesterday on the team list..
[Vibrant Android Development] hurtz777:
Woodrube MK found that the JB kernel wasn't properly mounting the data partitions and he just enabled proper mounting and that got rid of the EU bug.
[Vibrant Android Development] Woody:
I've had a suspicion that it was kernel related but couldn't put my finger on it. Mr_psycho was heading in the same direction also.

FE thanks for the heads up. If MK does reply to you can you forward to me? If that puts you in an awkward position just let him know that there are people who have a vested interest in the findings and I can relay those to our Cappy friends.

@E1 - this is a JB thread that is still a WIP, so lets not contaminate this thread. Any info related to the EU bug just either let me know or post here: If you are running or going to run ANY ICS rom::::LOOK HERE FIRST
[Vibrant Android Development] ali1276:
I recruited him today :). But I think we will separate from the guys in the i9000 forums because they don't do real development, all they know how to do is copy/paste files and then they get mad if someone tries to develop. Also, they lie about fixes. This mkalter guy claimed to fix wifi but when I asked him how he did it, he replied via PM, "that's just a bunch of ****"
[Vibrant Android Development] FaultException:
Nice. Any specifics or am I going to have to tear down the ramdisk myself?
[Vibrant Android Development] hurtz777:
Possible EU Bug Fix For Jelly Bean Kernel

I was following this thread @ http://xdaforums.com/showthread.php?t=1747042 and http://xdaforums.com/showthread.php?t=1740651&page=41 full of a lot of BS but mkalter credits stratosk and derteufel for fixing the EU bug which was most likely fixed by uncommenting some lines related to cache and /data and /datadata partition mounting in the kernel's init.rc. Here are the lines in the kernel's init.rc that probably need to be uncommented to fix the EU bug:

on fs

# mount mtd partitions

# Mount /system rw first to give the filesystem a chance to save a checkpoint

mount yaffs2 mtd@system /system

#mount yaffs2 mtd@cache /cache

#mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime noauto_da_alloc

#mount yaffs2 mtd@datadata /datadata

FE and Woodrube I would recommend contacting either derteufel or stratosk on how he fixed it if you can't find the right lines to uncomment. I flashed JB and it felt extremely fast considering no major functions were working yet. JB will run amazing on our Vibrants and let us keep our phones until SGS4!
[Vibrant Android Development] Sugartibbs:
Agreed, but it needs to be pushed a little further down the road, WIFI first.
[Vibrant Android Development] xriderx66:
Yep.

However Bluetooth IS important, I do think Audio should go before, but you guys are the devs.
[Vibrant Android Development] FaultException:
Wouldn't commenting the mounts for /data, /cache, and /datadata also at the same time just make the ROM so it can't use them also.
[Vibrant Android Development] ali1276:
Well Bluetooth will be a lot easier to fix. That is why it's higher.
[Vibrant Android Development] hurtz777:
FE take a look at my second link where derteufel came up with the idea of uncommenting the lines when he compared Slim ICS's kernel init.rc and JB's kernel init.rc. The EU bug was showing up because the data partitions weren't mounted and therefore the kernel couldn't access them.
[Vibrant Android Development] Woody:
I agree. Audio is important but if BT is so easy to fix, just get it done, out of the way and off the list.
[Vibrant Android Development] FaultException:
Yeah but that looks like a bug they only encountered with the same result, except they got it all the time (i.e. because it was commented out it wasn't mounted at all), whereas in the ICS ROMs, we do mount it, so it should be able to access it.
[Vibrant Android Development] Woody:
I looked at the second thread to and went back a few pages and read it to the end. Looks like something was solved but no one "really " explains how. Could be an init patch and another says it could be a build.prop edit. No real concrete answers just more towards getting JB up and running.

Ali - sorry for the thread hijack but this is an important find.

@E1 else - wanna move this encryption party out of this thread or is it still relevant to this ROM development? We can always move it to my thread I linked a few posts ago.
[Vibrant Android Development] ali1276:
Nope, it's wonderful. It's actually REAL development instead of BS posts.
[Vibrant Android Development] Sugartibbs:
Ran this rom, Its Alpha and Im afraid any EU fix is JB specific. There may be clues but until there is more to go on, let it develop.
[Vibrant Android Development] frr1:
Please port to cappy Ali!

You ported JB to vibrant but not captivate? not fair

Please port to cappy as soon as possible

all the cappy owners would appreciate it! :)
[Vibrant Android Development] ali1276:
I'll try to port to the Captivate once we get this at a good enough level. BTW, I own a Vibrant which is why I ported the rom...
[Vibrant Android Development] mr_psycho:
I agree with FE here. I can't speak for all the kernel devs, but my init.rc (for ICS) already had these partitions mounted (ie. uncommented).

I think they saw the same error message, triggered by the same "end-result" of not having /data and /sdcard mounted. However, the root-cause in their case was VERY different.

MP
[Vibrant Android Development] frr1:
Oh ok thanks I can't wait till all the basic features work I'm gonna keep my phone now and wait till next year to upgrade

Thanks to you & all the devs that made it possible! :)
[Vibrant Android Development] Sugartibbs:
Most likely doing you a favor at this point, JB is alpha, The Vibrant is more difficult to brick, let the Dev do his thing, this is very new, and we all know people will flash anything and then complain,.. patience..
[Vibrant Android Development] Mr. Galaxy:
This pleases me!
[Vibrant Android Development] uurrnn:
So excited for this. Keep it up guys.
[Vibrant Android Development] xriderx66:
Just a curious mind here,

Since you said that Project Butter is "coding improvements", would something like Project Butter be able to be "ported" or used onto ICS roms?
[Vibrant Android Development] FaultException:
Project Butter is not coding improvements. It's vsync to 60fps, triple buffering, and more. Of course you could port it back I imagine, but why would you want to?
[Vibrant Android Development] xriderx66:
I guess it would be easier/faster to port an actual JB rom than just features it brings. Just a curious mind.
[Vibrant Android Development] CWalkop:
@frr1 Hey, I want my JB on my Vibrant more than you do! Definitely! *cough cough*

@xriderx66 I agree, I doubt that you can simply code in Project Butter by hand. Google would have done something like that a long time ago if they could have done it easily. Its obvious they spent considerable time on it. You would probably have to edit a significant chunk of code and application code as well in order to get something similar working.

@WoodRube Sorry to bring this off-topic, but I wouldn't have been able to get this JellyBean ROM without your help with flashing ICS onto my Vibrant a few months back. I am still eternally grateful. Thanks again.

Anyway, to bring this post back on topic: I'm curious what's going on in audio development for Jelly Bean on the Vibrant. I heard there have been a LOT audio optimizations for Jelly Bean. Audio latency has been reduced by a couple factors, USB support for audio devices has been added, HDMI multi-channel audio, and more. Yes, I know the Vibrant doesn't have a USB or HDMI port (of course), but the point still stands that there are some pretty significant enhancements to audio performance in JB. Will you guys be working on implementing that for the Vibrant?

Also, any plans to incorporate Voodoo Sound and/or display controls? I love that on my current ICS ROM for the Vibrant (ExRom 2.0).

Thanks for this!
[Vibrant Android Development] xriderx66:
I think they want to just get this ROM stable enough for daily use before doing Voodoo stuff haha.

Don't worry though, soon as its even a bit stable, you'll see 8 other JB roms with their own flavor added on top, probably will include voodoo.
[Vibrant Android Development] trailblazerz11:
These are kernel features included in Semaphore and only some minor changes had to be made to kernel, so kernel wise ok and they might work with voodoo app and Galaxy s Settings. But like above said this is Alpha 1, most things not working with Rom.

Sidenote:

Thanks Ali, I remember you from Revolution Rom days xD

Didn't think I would be seeing JB ported so quickly to vibrant, Thanks TAJB, great preview for whats to come.

Though honestly just waiting on source to drop =P
[Vibrant Android Development] FaultException:
Actually on V2 we're using me & creeve4's Stock+ kernel with the init.rc from JB.
[Vibrant Android Development] ali1276:
I am asking for the help of anyone here. To fix the internal/external storage, I need to make some edits in services.jar; however, whenever I make those edits, the system does not boot. The edits you have to make is you are supposed to replace all the mountservice.smalis with the ones from cm9 and you need to replace the usb folder with the one from CM9. That is how they fixed it on the i9000, but when I try it, it fails. Can anyone help?
[Vibrant Android Development] FaultException:
Try decompiling with baksmali first then smali it back the same and see if that boots, that way you can figure out if it's a smali error, or if it's something you're changing.

Are you sure they replaced the whole mountservice.smali file, or just made changes? Replacing the whole file might cause problems.

I would find the difference between the two and see what's different.
[Vibrant Android Development] trailblazerz11:
Yeah I just saw StockPlus Github :)

So JB only needs change to init.rc? Thats very convenient.
[Vibrant Android Development] ali1276:
Alright, it is not a smali error. It booted fine with the services.jar i just compiled without changing anything. Now the question is, how do we fix it?
[Vibrant Android Development] CWalkop:
Of course, I understand that isn't something that would be implemented in the short-term - still need to get sound WORKING before even thinking about sound enhancements, etc. I'm really looking forward to seeing this thing come to fruition. I'll be checking back on the hour ;)

Thanks for the info. Its helpful.
[Vibrant Android Development] FaultException:
Well, that got it booting, there may be other differences that would make it run better.

StockPlus on GitHub is the original (which is meant for CM9) with the CM9 ramdisk.

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

We need to find out what's required and only implement that in the mountservice smali. So run a diff on the original and CM9 one.
[Vibrant Android Development] ali1276:
Run a diff, sorry?:confused:
[Vibrant Android Development] FaultException:
Are you on linux or windows?

On linux you can do this:

diff cm9_mountservice.smali jb_mountservice.smali > diff.txt

The resulting file will contain the text differences between the two.

I can do it later if you want.
[Vibrant Android Development] ali1276:
OK thanks, I can do that.
[Vibrant Android Development] ali1276:
Here is the diff.txt: Dropbox

There is obviously a lot of stuff that is different.
[Vibrant Android Development] FaultException:
Is the right or left file CM9? We need to find out what that's different is required. Some of the differences look like they're just different variable locations:

< new-instance v0, Ljava/util/ArrayList;
---
> .line 167
> new-instance v3, Ljava/util/ArrayList;

We can use the CM9 & AOSP mount service Java code as reference.
[Vibrant Android Development] ali1276:
The left is CM9, the right is jellybean.
[Vibrant Android Development] Br1cK'd:
Sup gents! Yeah, I still lurk around here sometimes, and have been following this thread a bit. I'm wondering if I might be able to help with the sd mounting.

Back in the early ICZen days, when it was a Crespo port, I was manually fixing the sd mounting to show and mount both sd's. I'm downloading the alpha now so I can take a look at the services and framework-res, and see if I can help y'all out. No promises, but I'll give it that ol' college try.

EDIT - In yours guys testing, have you also been editing the framework-res/res/xml/storage_list.xml? I notice in the alpha its only got the string for the sd, and not the one for the emmc mounting.

EDIT 2 - I got it to boot with an edited framework-res and services.jar, but sysui and settings are fcing on me. Think I'm making progress maybe, gonna try a few more things after dinner.

EDIT 3 - I'm trying, and still failing. Got her booting now, sysui working, but settings is still throwing an fc when I go into storage. I'm running out of time tonight, about to go pick up the gf so I have to put this down for now, I'll pick it back up when I can, and keep an eye on the progress over here.
[Vibrant Android Development] ali1276:
Thanks, do you mind uploading the framework-res and services.jar. Also, yes I was editing the storage_list.xml in framework-res.
[Vibrant Android Development] BIGG13:
Sorry for getting off topic but I had to say this.

Brick your awesome, please help out where you can so that us people that are holding onto the vibrant can continue to show it still has life and can fight the good fight.
[Vibrant Android Development] Br1cK'd:
What I have so far isn't working, I was trying a rush job before I went to pick up my girlie, and wasn't paying that much attention to what I was trying. I don't want to upload it cause its probably way off base and confuse the issue. I'll give it a more detailed run this weekend when I get some time, and upload for you what I have at that point, working or not.

I also tried just the services.jar they used in the i9000 build and it didn't work, I wonder if its really fixed in that rom. It would boot fine, but nothing mounted.

I may not be over here much, but I'm still highly active in Vibrant development on another site. I love how these two year old phones can handle the newest OS's, and outperform many newer devices. Just with ICS, not including this JB, we are running a newer firmware build than the SGS3 ships with out of the box. Gotta love it, and with this many people still rocking it and building for it, Vibrant development is far from dead. I think we have more people building for the Vibe now than we did when I started in pre-EDT days.

Sorry ali, back on topic now. :)

Sent from the ICZen Experience
[Vibrant Android Development] imilleson:
You inspire greatness sir.
[Vibrant Android Development] uurrnn:
Here's to weekend progress!
[Vibrant Android Development] Qverse:
JELLY BEAN wOw !!

Team Android JellyBean! OH Man,,, Bring it on .. Yes can't wait....
[Vibrant Android Development] DerTeufel1980:
Is this based on v1 of the I9000 port? Then you could try my latest kernel, it should fix wifi.

If the rom is based on the newer I9000 build, wifi does not work. There seems to be something wrong with the rom.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] ali1276:
It is based on v1. The reason it does not work with v2 is because of the lib.hardware.legacy.so.
[Vibrant Android Development] FaultException:
Jelly Bean source is out!
[Vibrant Android Development] imilleson:
That my friend, is excellent news
[Vibrant Android Development] taurus193:
my vibrant will stay forever.....
[Vibrant Android Development] uurrnn:
Waking up to this is beautiful.
[Vibrant Android Development] gun:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
[Vibrant Android Development] Waldos:
I'll gonna luv this 4ever! Vibrant never dies!
[Vibrant Android Development] zbt1985:
Any news on how it's coming!?!?! Really excited for this!!!
[Vibrant Android Development] TFordham:
It will come when it comes. Calm down.
[Vibrant Android Development] zbt1985:
Yes I know, but I don't think I've been as excited for an update in...like...ever!
[Vibrant Android Development] BIGG13:
+1

I was actually excited for a paranoid rom update but seems the Porter left it alone.
[Vibrant Android Development] xriderx66:
Changelog from I9000

Changelog

-New Devil kernel (Thanks to DerTeufel1980)

-Based on Galaxy Nexus ROM, made by nasif619. Big Thanks to him

-Fixed camera

-Fixed internal/external SD

-Logcat (DerTeufel1980)

-Added NStools (for overclock)

-Added IO file manager

-SU

-Notification Bar lag fix (bhu1)
[Vibrant Android Development] ali1276:
Guys,

Do not worry, I am still working on it. I have gotten WiFi, Bluetooth, and audio fixed. All that is left is GSM and then I will release an update. I am working on a source build.
[Vibrant Android Development] imilleson:
Dude your a bawler! Mad props for your progress!
[Vibrant Android Development] iwillkillyou:
Working fast, I bet you can't keep track of time. I think your more excited on the rom then us lol!
[Vibrant Android Development] awolbrin:
Your the best

Thanks
[Vibrant Android Development] Gerr1985:
OMG LOVE YOU!!!! - no homo
[Vibrant Android Development] Stevethegreat:
The great thing of our device has is that it is identical to Nexus S.... May I ask then why this rom is based on Galaxy nexus? It sounds a bit contradictory especially considering (that) Nexus S has it's own brand of Google's latest sweet...
[Vibrant Android Development] CTown:
I don't think the Nexus S has an offical JB build like the Galaxy Nexus does. Plus, judging from Ali's post from the previous page, this ROM is built from source now (as opposed to modifing the Galaxy Nexus build)!
[Vibrant Android Development] ali1276:
Just an update: source is compiling.
[Vibrant Android Development] Xenoism:
Awesome!
[Vibrant Android Development] kevho00:
Ahhhhh that's so exciting !
[Vibrant Android Development] xriderx66:
update from i9000

"Working:

-Touchscreen

-GPU

-Softkeys/Hardkeys

-Butter

-ADB

-USB

-Internal SD

-Camera

-Audio

-WiFi

-HW Video Acc

Not working:

-Bluetooth

-Call/SMS/Data

-GPS

-External SD

-Google Now"
[Vibrant Android Development] ali1276:
My ROM is no longer based on their rom.
[Vibrant Android Development] L1LK1LLERZ:
Will the Camera work in the next version? Just wondering. :D
[Vibrant Android Development] imilleson:
The post above yours says that the camera will work
[Vibrant Android Development] wolfie083188:
Yeah, but he no longer based his rom on the nexus one. which has the camera working. so it is unknown if His new version he built from source has the camera working.
[Vibrant Android Development] skinzy98:
So if this port is not based off if the gnex anymore, what's working?
[Vibrant Android Development] xriderx66:
:O it's not?

Now i feel stupid.
[Vibrant Android Development] wolfie083188:
Gnex.... i like that nickname.. lol

things aside, hey ali do you think the update will be today? i feel like im 5 years old waiting for santa to bring the presents. im checking this site every 10 min to see lol. i love the rom as some of the core features work. red borders and fc's aside. im dying for the update :D

that compiling post has me exited lol
[Vibrant Android Development] TFordham:
I don't want to be an ass, but have you not learned that you don't ask eta's?! It will happen when it happens.
[Vibrant Android Development] wolfie083188:
sorry about that. dident mean to offend anyone.:o
[Vibrant Android Development] imilleson:
Haha I remember when I first asked about ETA's and got chewed out. Good times...
[Vibrant Android Development] Dougfresh:
Is it out yet? Who long? I'm at 100% waiting.. lol :p
[Vibrant Android Development] TFordham:
I'm coming after you!! ;)
[Vibrant Android Development] wolfie083188:
hmmmmmm

its quiet in here....;)
[Vibrant Android Development] Gerr1985:
Its because we're all afraid he will come after us with wink faces!
[Vibrant Android Development] skinzy98:
Its because were all so anxious
[Vibrant Android Development] TFordham:
That's right.... And stay off my lawn you wippersnappers!
[Vibrant Android Development] N00B_IN_N33D:
But... Can I get my ball back first? :(
[Vibrant Android Development] xriderx66:
Is it out yet?

Battery life?

Will this brick my phone?!?!?!?!?
[Vibrant Android Development] wolfie083188:
cant wait for some more google now :)

i got it on my ics but with no voice:(
[Vibrant Android Development] imilleson:
It bricked mine when I loaded it and tried to revert ;)
[Vibrant Android Development] wolfie083188:
i had to use odin *gasp* ( long awkward silence...) to get back to stock and restart from there. fml;)