Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,312 Members 39,078 Now Online
XDA Developers Android and Mobile Development Forum

[4.1] JellyBean Dev thread

Tip us?
 
Shelnutt2
Old
(Last edited by Shelnutt2; 10th December 2012 at 03:21 AM.)
#1  
Recognized Developer - OP
Thanks Meter 1,642
Posts: 811
Join Date: Mar 2010

 
DONATE TO ME
Default [4.1] JellyBean Dev thread

I'll keep this post upto date with the last on the status of the build.

I've updated the manifest and it's inline with cm10. https://github.com/TeamICS/manifest_...tree/jellybean
Builds are located here.
Nightlies are here or here

If you are not using firerats or don't know what that is make sure you use one of the "_shrunk" nightlies.

Currently the room boots. Lots of things work, here is what doesn't:
Bluetooth (pairing)
HW Acceleration (not likely)
Anything missing from CM10


Known issues are:
Headphone + speaker plays when headphones are in











<--previous-->
IT LIVES!
The build doesn't flash, but it successfully built. You need to use firerats as the system partition is over 173mb by itself. Not sure of optimal settings as it doesn't flash but we're getting closer.


Complete repo diff and repo status is here:
https://gist.github.com/3095432

Things disabled at build:
audioinwrapper from srec
libaac/libFDK
compiler-rt
maybe others.

Please note I haven't cleaned anything so it's quite messy and some stuff isn't pushed up to the repos yet. However it builds and that's a big step. It's off to bed and work tomorrow so I won't get a chance to work on it until the evening/friday.



Very close to a build, libaac is the only blocker, I've reached out to cyanogenmod guys to see if they have any ideas to fix aac, without completely rewritting the asm code. The problem is armv6j doesn't support smmul, clz and others in thumb mode, but armv7 (and the few devices with thumb2 on armv6t2) do. I don't have enough experience with arm asm to figure out how to rework the code to convert from 32 bit operations to 16bit operations. Also valgrind is not supported in armv6 (and can't be) so its disabled.
  1. problems building aac, due to asm code, currently disabled a blocker
  2. problems building srec due to audio issue, disabled
  3. haven't ported camera


[strike]So far there is only two show stoppers, first is the audio because its changed again slightly. Shouldn't be too hard to work around. Second is cm team is still porting over all armv6 patches. Building on armv5 get stuck at audio, but armv6 get stuck on some asm code in bionic.[/sstrike] aac. AAC is being a really PITA!



<--Original Post-->
So I'm sure some of you guys are watching the I/O live. For those that aren't it's offical Jellybean will be 4.1. It's got loads of new and nice features. A lot of performance upgrades and the most important thing is the annoucement of the platform development kit. It's got all the low level details and apis need to port hardware to android.

Source code will be released in mid july, which is when the real development starts.

The hardwork everyone did on ICS, jaybob, matt, evervolv team and everyone from the G1, hero and eris forums laid the foundation. The main issue that has always held the heroc back has been the drivers. We have a great .35 kernel but with ICS a lot of the framework, that is hardware <-> software interactions changed. Thats what our audio issue was at first, and the camera. Audio was fixed by porting gingerbread patches and legacy audio support. The camera was tougher but eventually fell to the power of the community! The only two major things left are camcorder and full gpu acceleration.

The PDK will hopefully provide the last little bit we need to get acceleration working fully. It's no magic but from the keynote sounds like it might provide the information we need. Or it might not. Won't know until it lands on the web.

Overall jellybean is a step further from our old heroc's but there is still almost 20k devices officially running cm7! We obviously still have a community here who has yet to upgrade so the new goal is jellybean or bust!

As more information and sources are released I'll update the thread. I plan to port our TeamICS github account to Jellybean as soon as it's released. With luck everything will compile and be in the same boat as ics but only time will tell.
The Following 24 Users Say Thank You to Shelnutt2 For This Useful Post: [ Click to Expand ]
 
megaghostgamer
Old
#2  
megaghostgamer's Avatar
Senior Member
Thanks Meter 737
Posts: 1,206
Join Date: Nov 2011
Thank you so much for posting this thread! I would have never knew about this. I'm willing to contribute to Jellybean although I'm with the Evo Shift now. I can make AOSP whenever the first jellybean Rom is released hopefully fixing some things!
 
whoshotjr2006
Old
#3  
whoshotjr2006's Avatar
Senior Member
Thanks Meter 374
Posts: 699
Join Date: Jun 2010
Location: toledo

 
DONATE TO ME
count me in, i still have a few months on my heroc left until i upgrade

most of the fixes that happened from eligorom should be able to be applied to jellybean, as its basically the same rom as ics (from early reports)
Devices I've owned in the past
 
Blackberry 7520>HTC Apache>HTC Touch Pro>Palm Pre>HTC Vogue>HTC G1>Moto Q>HTC Hero CDMAx2>HTC Evo 4g>Kyocera Rise>HTC One V CDMA>Samsung Epic 4g


Current: Samsung Galaxy Nexus, LG Volt


Long Live the HeroC!

Roms I've Ported:

The Following User Says Thank You to whoshotjr2006 For This Useful Post: [ Click to Expand ]
 
Hammerfest
Old
#4  
Hammerfest's Avatar
Senior Member
Thanks Meter 278
Posts: 1,590
Join Date: Apr 2008
Location: San Antonio, TX

 
DONATE TO ME
I really need to add it to a signature when here in the HeroC forums, but:

My HeroC has been inactive on a carrier for the last year +, that being said, I still use the crap out of the device when I can, for a clock/alarm, music, GVoice and GrooveIP phone calls when home...

Basically, I would LOVE to see this thing continue to get updates, I still run CM7 over CM9 or ICS because for me, I see the most performance with CM7. Your talk of the PDK has me excited that I might see equal or better performance out of Jelly Bean on my HeroC!


TYVM, keep us updated
Have I in some way helped you?
Perhaps I made a post of an issue that you also have?
Think i'm such a nice/swell guy*
Then hit the THANKS button!

*
I'm not, I'm annoying, if you think otherwise
please seek medical/mental assistance ASAP!

TouchPro, TouchPro2, HeroC, HD2, Evo3D, EvoShift, PhotonQ, GalaxyNote, MORE...
 
whoshotjr2006
Old
#5  
whoshotjr2006's Avatar
Senior Member
Thanks Meter 374
Posts: 699
Join Date: Jun 2010
Location: toledo

 
DONATE TO ME
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us

i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so

from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Devices I've owned in the past
 
Blackberry 7520>HTC Apache>HTC Touch Pro>Palm Pre>HTC Vogue>HTC G1>Moto Q>HTC Hero CDMAx2>HTC Evo 4g>Kyocera Rise>HTC One V CDMA>Samsung Epic 4g


Current: Samsung Galaxy Nexus, LG Volt


Long Live the HeroC!

Roms I've Ported:

The Following User Says Thank You to whoshotjr2006 For This Useful Post: [ Click to Expand ]
 
john9
Old
#6  
Account currently disabled
Thanks Meter 269
Posts: 1,586
Join Date: Oct 2011
Thanks for sharing! Hard!
 
megaghostgamer
Old
#7  
megaghostgamer's Avatar
Senior Member
Thanks Meter 737
Posts: 1,206
Join Date: Nov 2011
Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...
 
EggosEvo
Old
#8  
EggosEvo's Avatar
Senior Member
Thanks Meter 69
Posts: 437
Join Date: Feb 2011
Location: Kansas City
Quote:
Originally Posted by whoshotjr2006 View Post
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us

i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so

from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
So will Project Butter have no effect on the Hero? I would think that it would at least have some effect in adding smoothness.

Sent from my SPH-D710 using xda app-developers app
The Following User Says Thank You to EggosEvo For This Useful Post: [ Click to Expand ]
 
alex_camacho
Old
#9  
Senior Member
Thanks Meter 17
Posts: 191
Join Date: Dec 2010
I have to say I'm really exited about this. I ran ICS a few times on my hero with no problems, but I'm still using it as a daily even though I'm sure it would run fine. Ive been thinking about upgrading, but i don't see why. I really don't like any new phones. Their too big, no track ball, and i just simply don't like any of the new phones out right now. So all that being said... JELLYBEAN :)!!!!!
The Following User Says Thank You to alex_camacho For This Useful Post: [ Click to Expand ]
 
Shelnutt2
Old
(Last edited by Shelnutt2; 10th July 2012 at 12:43 AM.)
#10  
Recognized Developer - OP
Thanks Meter 1,642
Posts: 811
Join Date: Mar 2010

 
DONATE TO ME
Source is out!

https://groups.google.com/forum/#!to...ng/XBYeD-bhk1o

edit: Not quite yet.

I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.

The Following 2 Users Say Thank You to Shelnutt2 For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes