yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It's possible to reverse engineer the HAL - it's just a MASSIVE pain in the ass and VERY time consuming.

25% chance arcee's legacy HAL wrapper works for ICS->JB (but given that GB->ICS didn't work with wrappers for our HAL... not a higher chance.)

50% chance the whole thing gets written from scratch

25% chance all the developers burn out before completion
[AT&T Samsung Galaxy S II SGH-I777] VanillaCracker:
Wouldn't it be more likely to work from ICS->JB than it would have from GB->ICS, since JB is much more similar to ICS than ICS was to GB?

:victory:

Balls.

I have a strong feeling this last part may be a likely outcome, seeing as how it's been a kick-start into JB, and the last thing devs are gonna want to do is create a whole HAL just for the GSII line up... :crying: . We'd love you guys forever though :D . For reals, this means so much to so many people words can't explain haha

Thanks for the update though, it was getting to the point where we needed another confirmation. Seems you have a knack for timing
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
their pianos are good :)
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
@vladm7 The Piano is their product and that is named using their brand name. What entropy said was "never want to buy

anything with their crap in it again

"

I hope it's clearer now...

Just a heads up on Development of Jelly bean for the i9100 in the thread below

http://xdaforums.com/showthread.php?t=1779526
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
oh, I'm sorry my message wasn't clear enough that it was a joke :)
[AT&T Samsung Galaxy S II SGH-I777] jmahr1127:
Possible Audio Fix?

OK so I was looking on the touch pad forums, and someone had posted an audio fix from their Atrix running JB. According to him, this file is just a general file and has nothing atrix-specific in it (which is why they posted it in the TouchPad forums. It probably wouldn't fix the driver issues, but maybe it would help any issues that may come up after the driver is there?

ANYWAYS, HERE'S THE ORIGINAL POST. I COPY-AND-PASTED THE TXT CAUSE I DIDNT KNOW HOW TO LINK TO THE POST

[FIX] Sound for Jelly Bean (CM10) ROM's

Share Thread:	Newsworthy Thread?

atrix4g18	Yesterday, 10:31 PM (Last edited by atrix4g18; Yesterday at 10:36 PM.) #1

Member - OP

Thanks Meter 12

Posts: 43

Join Date: Jun 2012

[FIX] Sound for Jelly Bean (CM10) ROM's

This is the fix for Audio/Sound on any Jelly Bean ROM on the HP Touchpad

JB needs this file "/system/etc/media_codecs.xml"

This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.

Here is a link to the file:

http://xdaforums.com/atta...9&d=1342668760

Steps:

- Extract "media_codecs.xml"

- Copy it to /system/etc/

- Make sure to mount system as R/W (read/write) before pasting the file

- Reboot

- Sound Fixed!
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
This doesn't help us

Sent from my Sony Xperia Ion
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
@vladm7 Apologies if so. My bad!
[AT&T Samsung Galaxy S II SGH-I777] aznkenshin:
Galaxy S III will get Android 4.1 soon Samsung test Android 4.1 for Galaxy S II

The insiders of SamMobile reported that Samsung is testing Android 4.1 for the Galaxy S III and Galaxy S II.

Samsung is almost ready to update their Galaxy S III devices to Android 4.1.

There is no date planned yet but it could be around August / September.

More good news is for the Galaxy S II. Samsung started the first tests with success.

If Samsung will update the Galaxy S II is still a question, but because the Galaxy S II is still very hot the chances are very high.

According to the insider of SamMobile Samsung will update the Galaxy S II if the porting to Android 4.1 on the Galaxy S II goes well.

There are no words yet about any other devices.

But the insider told us that Samsung will update the HIGH-END devices more and more. That’s why the chances for the Galaxy Note will be bigger than ever.

There is still no public statement of Samsung about the Android 4.1 updates.

We of SamMobile put our bets on these three devices after the Galaxy S III.

- Galaxy S II

- Galaxy Note

- Galaxy Tab 7.7
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
It would be nice of Samsung to do so but I highly doubt they doing so. And porting Jelly Bean would be harder on the i9100 because of the Stupid Yamaha Chip which what is holding up the devs. from porting Jelly Bean.
[AT&T Samsung Galaxy S II SGH-I777] salleq:
Why do you doubt? There was a good reason HTC Desire didn't get gingerbread and a good reason why the original Galaxy S didn't get ICS. Except that the Desire did get gingerbread with some apps stripped, the reason for that was limited internal storage. Only it was made an optional update for "experienced users".

For Galaxy S, they said its performance wasn't satisfying. And although Galaxy S has unofficial builds without Touchwiz of whose performance I have no idea, I've tried ICS on my Desire and the performance is so bad I had to go back to GB.

And why do I compare these two phones? They were released within a short amount of time between them, and had similar performance.

Finally, if Samsung does NOT release JB for SGS2, that is for financial reasons and makes them greedy bastards. :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Interesting. If we get audio blobs for I9100 and N7000, things get much easier. :)

Even one leak will probably get us enough for a reasonably solid solution... But it may in the end still prove beneficial to try and reverse engineer the HAL until we have an open source one to fix crap like notification volume.
[AT&T Samsung Galaxy S II SGH-I777] nimper:
What, if anything, does this patch mean for audio support on our devices?

http://review.cyanogenmod.com/#/c/19721/

"Add support for ICS audio blobs" under CyanogenMod/android_hardware_libhardware
[AT&T Samsung Galaxy S II SGH-I777] Nosferatu.:
I'd like clarification too. From what I'm understanding that link is showing that whatever is available for ICS on audio is portable to JB no??? :confused:
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
Pretty much what I was thinking.

Sent from my Galaxy S2 running Task650 & Ktoonsez AOKP
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
I feel like people are throwing around words and searching for stuff without knowing what the real problem is so id like to point your attention at few things:

HAL: http://www.slideshare.net/jollen/android-hal-introduction-libhardware-and-its-legacy

the problem does not lie with the driver. most drivers when recompiled with the new kernel work, the really temperamental one is the wifi one as it really needs to be compiled with the kernel every time. the rest seem to me that they work without a recompile. so im pretty sure the drivers will work with the new kernel. its the level of communication above the drivers. the HAL. see the drivers handle the interface between the hardware, that means power and cpu to chip and I2C( a communication bus analogues to pci in a computer) the HAL or HARDWARE ABSTRACTION LAYER is what then communicates the hardware to the software. it is a set of libraries. think of them as a dictionary or a translation book that interfaces hardware level messages into things the os can understand and visa versa. on top of that is some more libs that are general, they tend to be less device specific. then we have the framework. it is the services that android provides to the applications and this is where hacks happen. small changes in the framework are work around to an improperly working lib...

we all want to help the devs get this out faster but trust me, a layman cannot decipher the problems.... ive tried. one must gain a deeper understanding of the code, then look at the source, then scratch his head a lot and hope things work....

EDIT: driver-->HAL/lib/.so-->audio flinger--> application?
[AT&T Samsung Galaxy S II SGH-I777] VanillaCracker:
I wish every noob had knowledge of this. Very informative post. The last paragraph is very wise :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
thanks.

and in response to the whole petition thing. Yamaha music and Yamaha bike? divisions arent the same. so their support may be a little more helpful, but then again maybe not. and samsung seems like it wants to stay in somewhat good graces with the tech community. in any case, they dont need to release a JB rom... they just need to open source the HAL. the hal is stored in a lib file. i think they are written in c... unlike the framework which is in "java". anyways the lib is written in C then compiled (read: translated to a machine runnable code) then shoved in the rom. entropy mentioned reverse engineering it by means of watching the framework interact with the lib for a very long time hoping to catch the calls needed to write your own. anyways it doesnt even need to be JB HAL it just needs to be A HAL. or even documentation on the chip would be useful enough information to cut down dev time by a lot.
[AT&T Samsung Galaxy S II SGH-I777] tocirahl:
I could've sworn HALs were below the Kernel. Doesn't it kinda defeat the purpose if they're above the kernel?
[AT&T Samsung Galaxy S II SGH-I777] casey_:
Nothing is below the kernel drivers, those are the interfaces that talk directly to the hardware. Each driver may have different ways of initializing, being told to play a sound, adjust a volume, etc. As an application developer you don't want to have to handle the a different case for every sound driver, so the framework exposes an API that you can use that is a constant across all the different hardware. The framework however needs to know how to talk to all of the different drivers and that is what hardware abstraction layer does. An analogue to desktop linux would be ALSA or OSS which provides an interface to the sound subsystem independent of the underlying sound driver or hardware, though the concept of a HAL is generic and not bound to a specific subsystem. The HAL is the glue between the API and the drivers, it translates "Volume down" from the API to whatever the driver needs to be told to reduce the volume, etc.
[AT&T Samsung Galaxy S II SGH-I777] :
I had the Captivate a Galaxy S variant and I can tell you the performance on ICS is buttery smooth, they already have a working JB ROM thanks to similar hardware with the Galaxy Nexus and Nexus S with a few issues so, I believe the inability to have TW + ICS was the real reason not that its performance wasn't satisfying and Sammy won't release an AOSP ROM
[AT&T Samsung Galaxy S II SGH-I777] salleq:
ICS + tw was my point exactly but I guess I wasn't clear enough
[AT&T Samsung Galaxy S II SGH-I777] patsmike:
Some good news. Looks more official for s2 than what sammobile reported earlier in this thread

Android 4.1 "Jelly Bean" Heading To Selected HTC, Asus And Samsung Devices

http://www.forbes.com/sites/adriank...ing-to-selected-htc-asus-and-samsung-devices/
[AT&T Samsung Galaxy S II SGH-I777] thetaminator9274:
I can't wait. :)
[AT&T Samsung Galaxy S II SGH-I777] knightsh:
Sgs2 just having bad luck here. I passed my old Motorola Bravo on to my wife when I got the Sgs2. Now I read that it's closer to getting Jellybean than we are. That little dinky phone. What luck!
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
Yeah. I know how you feel :(
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
I'm not really sure what this means? Complaining that other devices are getting it before the S2 is useless. The Bravo's hardware is two years old and obsolete so I'm not sure how good JB would run on it anyway :cool:
[AT&T Samsung Galaxy S II SGH-I777] desitexan:
:eek:

Man, JB early builds have been dropping left and right today for a lot of devices:

https://plus.google.com/117962666888533781522/posts

No sight of S2 yet.
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
Heads up on the progress of Jelly Bean for the i9100

https://plus.google.com/111398485184813224730/posts
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
Audio still seems like the only big issue as to not having JB yet :(
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
Yeah! It sucks having to know that we have the slimmest android smartphone samsung ever built with a gorgeous screen, Quality camera, heaps of connectivity and then realize that they have fitted it with a crappy audio chip!

It's a very baad feeling!....
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
I guess when i get a new phone down the road i will have to look at what audio chip it has :D
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
anyone read this? http://www.gizbot.com/news/samsung-galaxy-s2-and-s3-to-get-android-jellybean-update#
[AT&T Samsung Galaxy S II SGH-I777] tylercarter:
yeah i saw that. s3 will get it first and then most likely we will wait a while. AT&T will most likely not update to it but who knows. time will tell.
[AT&T Samsung Galaxy S II SGH-I777] :
Nobody here will want AT&Ts bastardized version of JB anyways. Just wait for the good Devs here to whip us up something once it drops for the i9100 guys.
[AT&T Samsung Galaxy S II SGH-I777] tylercarter:
absolutely!!!!
[AT&T Samsung Galaxy S II SGH-I777] ricktherick:
+1

Besides, AT&T/Samsung didn't give us ICS until at least a month after I was running CM9 nightlies
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
From the issues he had getting ICS up and going and now JB, Im afraid to say i might be with codeworkx on this one, my next device wont be Exynos... As much as i love the performance it seems like it's been a pain for the Devs, and a pain in the butt chip will cause Devs to leave soon as they get the chance, and makes it harder to get future updates after the device is old and forgotten. Samsung needs to drop the codes for these drivers to the Devs. That way IDC if they update it. They can drop the device as far as I care lol:p
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
Its not really the Exynos, but rather the Yamaha audio chip. Why release something with no audio? That's why we haven't seen any JB roms yet.
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
Yeah thats what i meant, the audio chip, but the point remains the same. It's a pain in the butt to the Devs. They have to write the HAL and etc from scratch...Im no dev...buut doing that seems like not fun...esp if you have another device you could be dev'ing for
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Anyone seen this yet?

http://xdaforums.com/showthread.php?p=29280423

EDIT: Caution... that's an i9100 build so don't flash it! It's just exciting that it's been adapted so soon!
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
your problem is not with yamaha alone. if you can recall a while back we had wifi roaming broken bc we didnt have the drivers... many phones have trouble with the GPU drivers... tegra may be the worst in terms of open source support.. and yes even the exynos line has relatively good support for the dev community... you will NEVER find a phone with everything in line.... oh wait yes you can its called the nexus line. that is IT. (btw even the 4g cdma nexus's werent in full open source until recently but google did deliver and i dont think they will make that mistake again.)

if you want a phone that is garunteed dev work... its the nexus line, it attracts deves like magnets when they first launch. they are easy to work with... thy get the os straight from el goog when supported, and the source drops instantly... and as an added bonus. when a dev wants to show off. he takes a device thats old and unsupported and gets the latest and greatest to run on it.......... before anyone else.
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
Surprised It's not hellraised yet. Seems like they got audio working
[AT&T Samsung Galaxy S II SGH-I777] vs8:
That only means we will get JB sooner than later! :)
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Entropy posted and said he needs to fix the i777 and n7000 trees so it will be coming soon
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Should I stay up? :) lol....I cant sleep now...
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
There is a tree already for i777. Codeworkx pushed it.

https://github.com/teamhacksung/android_device_samsung_i777/tree/jellybean

Now it's just a matter of compiling it and testing. :)
[AT&T Samsung Galaxy S II SGH-I777] desitexan:
Nice!
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Somebody do something!! Lets get this sucker rollin :)
[AT&T Samsung Galaxy S II SGH-I777] djmurphix:
+1 :D
[AT&T Samsung Galaxy S II SGH-I777] desitexan:
Amazing dedication!

https://plus.google.com/111398485184813224730/posts/SNGDDJQ4KkB
[AT&T Samsung Galaxy S II SGH-I777] mzaur:
They got audio working. Saw a post by Entropy. We will hopefully have jelly soon!
[AT&T Samsung Galaxy S II SGH-I777] herofmm:
I flashed I9100 CM10 preview on my I777. Almost everything works.

If you cannot wait, just grab I9100 zip file and edit updater-script file ( remove assert command ). and flash with gapps0717. I had to flash modem for data to work. By doing this, LED keys are screwed up, but you can taste some of JB. I'm sure some one will make proper zip file soon.

Don't forget to do nandroid backup before you doing this. Enjoy.

Edit : voice on call does not work. I can make&receive calls but no sound coming through.
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
Word of advice:

In-call audio DOES NOT work. Needs a i777 kernel.

With the device tree up it's basically sync and build if you have the environment set up.

I'll give it a shot myself in ~6 hrs at work.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
device tree needs fixes - nfc stuff is killing the build

If I don't succed in the next 10 min or so I'll be going to bed.

We're close though - we got lucky. Using backwards-compatibility wrappers for Gingerbread audio in ICS failed - but the ICS->JB wrappers seem to be doing the trick.
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
Check the latest commit from codeworkx, he seems to have fixed that. :good:
[AT&T Samsung Galaxy S II SGH-I777] k1ska:
Entropy, your hard work has me in awe. You are an amazing person to help bring Jelly Bean to us, if I had extra money I'd definitely donate to you.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
+1,000,000
[AT&T Samsung Galaxy S II SGH-I777] kleinschmizzy:
Maybe take back your bottles and cans and donate?
[AT&T Samsung Galaxy S II SGH-I777] memphian:
Thanks to all the devs that worked on this. Now to temptation to sell my gs2 for gs3 has subsided. Now I think I can wait for the next nexus :)

Hopefully it as an as noticeable difference as the captivate, because that with JB flies.
[AT&T Samsung Galaxy S II SGH-I777] rk249:
+1
[AT&T Samsung Galaxy S II SGH-I777] flucks:
Shouldn't be too long now!!!! So excited.

https://plus.google.com/101093310520661581786/posts/5GfDbDYZ98d
[AT&T Samsung Galaxy S II SGH-I777] Nosferatu.:
Oh boy I"m excited this is amazing!!!
[AT&T Samsung Galaxy S II SGH-I777] nash2018:
suspense is killing me!
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
+ pi!
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
AHHHHH Yea!!!! *Happy Dance*:victory:
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
y so soon happy dance? :confused:
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
because..1) I do what I want

2) the hard part is out the way, the audio issues. Entropy is a boss, he'll knock the rest out in no time

3) When im happy i dance? Do i tell you how to celebrate?
[AT&T Samsung Galaxy S II SGH-I777] flucks:
Looks like the audio is pretty much fixed from what I can tell. Looks like he is having a problem with something pegging the CPU at 100%. I have faith in him. It won't be long.
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
I inquired as in, did you know information other than what we know. I never told you how to celebrate. Lose the attitude kill joy. :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] :
Wow, sore spot much? Who pissed in your cheerios?
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
I know that's what Im saying the audio is done, and that's the hard part, the cpu he said on G+ is the media scanner. which im sure he can handle
[AT&T Samsung Galaxy S II SGH-I777] flucks:
You ready for the Georgia Dome? :)
[AT&T Samsung Galaxy S II SGH-I777] rk249:
hahaha! that was awesome!
[AT&T Samsung Galaxy S II SGH-I777] joshyy_rey:
Not sure...but when I find out i'll be sure to let you know. im curious as well.

you know it. Im just ready for the season. But to be honest im tired of playing you guys haha only so many times I can hear C.L.E.M.S.O......N! haha jk
[AT&T Samsung Galaxy S II SGH-I777] alejobog:
Guys, here is our representative in CyanogenMod developer and says that there is good progress and already fix the sound, but unfortunately hit the road and reach the next week, expect to return to continue.

https://plus.google.com/u/0/101093310520661581786/posts/5GfDbDYZ98d
[AT&T Samsung Galaxy S II SGH-I777] dashoffman:
I think you understood him wrong. He said that he was going in to work late because of the time he spent developing the CM10 build. He mentioned that he would be using vacation time because he was late to work. I don't think he meant that he is taking a vacation/leaving.
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
I have built a i777 kernel from the CM10 tree, if anyone wants to try this out self-hellraised with the I9100 rom.

Remember that you will also need a proper keylayout for the capacitive keys to work:

https://github.com/teamhacksung/and...7/raw/jellybean/usr/keylayout/sec_touchkey.kl

Copy into /system/usr/keylayout

I will only upload the kernel, it's most likely that Entropy will post a more official build tonight.

This is unsupported, unofficial. CM team, I, or anyone else ARE NOT responsible from any issues that might arise. Flash under your responsibility

I have tested it and it works OK in my device, but your mileage may vary.

All credit to Codeworkx, Entropy & CM team for the work on our device tree and for bringing CM10 to us. :good:

Thank you.

Edit: PM me and I'll send it your way, might be too risky to leave it in the open. :confused:
[AT&T Samsung Galaxy S II SGH-I777] dev997:
I tried hailraising the rom using Ktoonez tool using this kernel and UCKH7 modem. Although it booted fine , My data network and Wifi are not working.

As I'm not on AT&T and use it on a diffrerent network I think I have to manually configure APN for that. However biggest qualm is Wifi. Not sure what happened there. Seems like I have to wait for Entropy's build.

Thanks a lot for the kernel though !!! +1
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
I'll try to add the required files for hellraise in a single zip. I'll send it to you by PM.
[AT&T Samsung Galaxy S II SGH-I777] dev997:
THanks a lot !!! got the flashable zip. So I just need to flash it over the i9100's Cm10 build . right ???
[AT&T Samsung Galaxy S II SGH-I777] drakester09:
Correct. Flash the i9100, flash JB Gapps, flash the zip I sent.

Please let me know how it goes. :good:
[AT&T Samsung Galaxy S II SGH-I777] dev997:
THANKS A MILLION MY FRIEND !!!!

everything seems to be working now. You should provide the link to other users too who are craving for some BEANS ... :D :good:
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
lol i need this link now. I cant wait any longer!
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
+1! I might even be tempted to ditch my stock ATT rom for this!
[AT&T Samsung Galaxy S II SGH-I777] rk249:
I wouldn't mind flashing it, maybe tomorrow coz its 3 am here and I'm off to bed. Please do provide some feedback on how everything is.
[AT&T Samsung Galaxy S II SGH-I777] PeteSeiler2010:
Thanks for the info! I am hoping to try this out tonight as well.