Database Info

SGSII ICS leak = Port for the brave

http://www.engadget.com/2011/12/15/touchwizzed-ice-cream-sandwich-leaks-for-samsung-galaxy-s-ii/
any brave devs?

I think we should wait our rom officially release...there not much talented dev on this tab forum.. We should wait bit more
Sent from my GT-P6200 using xda premium

Since there is no Development per say, Im moving this to General.
Thread moved.

At least Sammy is working on this which is good, but the ROM is in very alpha stage...

Is there development of ICS on the 8.9 or 10.1 forums? You would need an ICS kernel of some type to even begin porting, if the other tabs have one that may work for the 7 too with some tweaking. Not sure if a kernel for a phone will even work on a tablet. ROMs I have some experience building, kernels I do not.

kzoodroid said:
Is there development of ICS on the 8.9 or 10.1 forums? You would need an ICS kernel of some type to even begin porting, if the other tabs have one that may work for the 7 too with some tweaking. Not sure if a kernel for a phone will even work on a tablet. ROMs I have some experience building, kernels I do not.
Click to expand...
Click to collapse
I'm pretty sure our tabs run off an entirely different chipset as well.
Sent from my PC36100 using xda premium

true, would be a pain I'm sure. ICS will be released soon enough.. I hope...

abowlby said:
I'm pretty sure our tabs run off an entirely different chipset as well.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I think you'd have to find a ICS kernel for the exynos processor in the 7 not sure if the current Honeycomb kernel would even work. Porting itself is basically taking the system and boot images off of your current device and replacing the ones in the ROM you want to port with them. The easiest ports are from devices with similar hardware. For the more difficult ports getting things like the sdcard to mount and wifi and bluetooth working can be a ***** and takes some expertise. Way beyond what I could do. I know enough to make ROMs using the kitchen and how to insert premade mods into them and also a little about decompiling and modding apks. All the info is pretty much on this site scattered about in different forums. I've been hesitant to even try anything with my Tab as you can easily brick it playing around I'm not familar enough with it to get it back if I even soft bricked it. My phone has an unlocked bootloader and I can recover it from pretty much any disaster. This thing I'm not even sure how it all works yet, samsung devices are totally new to me.

[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_ics_cm/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.
problems building aac, due to asm code, currently disabled a blocker
problems building srec due to audio issue, disabled
haven't ported camera
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.

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!

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)

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

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)

Thanks for sharing! Hard!

Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...

whoshotjr2006 said:
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)
Click to expand...
Click to collapse
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

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 !!!!!

Source is out!
https://groups.google.com/forum/#!topic/android-building/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.

Shelnutt2 said:
Source is out!
https://groups.google.com/forum/#!topic/android-building/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.
Click to expand...
Click to collapse
I change my mind, i do think the hero can run jb BUT im not to sure about 5.0 or whatever they call it.. i upgraded to the evo shift and love it!! Just letting y'all know because this might be the last upgrade sadly said :/
Sent from my BNTV250 using xda premium

awesome, cant wait to see the first source build
ill help in whatever way i can, i just cant dl source because of my crappy internet connection (but if i can find someone to borrow faster internet from for a few hours ill most definitely dl source and try to contribute back that way)

Lol may take me a while before I can start porting for the hero again..
My current projects for the evo shift:
Motoblur
Porting Sense
4.1
3.0
Thats pretty much it =)

Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:

Shelnutt2 said:
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Click to expand...
Click to collapse
So excited. My Hero has a sweet tooth.

Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..

megaghostgamer said:
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
Click to expand...
Click to collapse
I dont know about AOKP. Sure it was ported, but what work has there been done on it since? Honestly ICS ran super smooth for me on my Hero, especially coupled with V6SuperCharger. I was using LauncherPro on ICS to add to the smoothness, but the V6SuperCharger allows for smooth use of Apex.

yeah, it wasnt aokp that accelerated our cause, aokp has only been around for a few weeks for us so far. it was jaybob's ics aosp rom that really kicked things into gear. that and stritfajt with the camera fix, and the guys over at hero gsm for all the different tweaks and fixes, and mongoosehelix over at eris that kicked butt with evervolv for us. im sure im missing some people, but it doesnt make them any less important to the cause.
and last but not least all the testers and rom flashers that gave excellent feedback
i look forward to seeing jb run like ics

So the reason it's unflashable was because it's over the 170mb limit of the phone. Even though I'm using firerats there still seems to be a hard limit of the recovery and fastboot. The solution is to use a newer recovery, anything cwm 3.x or higher works. The dev phone I'm using had 2.5 cwm and that was the issue. Now it flashes fine. Only problem is for some reason sh didn't build, so now I'm looking to see why it didn't build.

we can cut out some cruft, like live wallpapers, and ringtones/notification sounds. live wallpapers dont work well on heroc anyway.
the sh error is boggling me too, supposedly its mksh symlinked as sh, which should have worked as thats how it is in ics roms.
im on the job lol
edit: yeah something is definitely rotton with those permissions, i checked them against an ics rom and everything checks out, but we still get the permissions error. i'm wondering if its the update binary possibly? ill do some checking and let you know one way or the other

So with ICS out, is there a better chance of a dev porting Jelly Bean?

So just like the title says, I was wondering with ICS now out is it more possible or likely that we will see a dev port a version of Jelly bean?

This type of speculation really doesn't do any good. ICS has been on devices for less than 2 weeks now. Let's just let it filter out and get widespread before we go on to the Next Big Thing. Developers will do what they do, which is develop. The best way for you to get what you want is to help them by learning how to do work on the device and software.
This community needs more giving back, and less demanding and taking.

Im looking at signing up for some C++ clases so I can start learning to start giving back

KazeOne said:
Im looking at signing up for some C++ clases so I can start learning to start giving back
Click to expand...
Click to collapse
I don't really know what that dude's deal was in the other thread. C++ is in no way needed. A firm understanding of how the components of a Linux based operating system work is far more useful. Very few, if any, "devs" in the Android community are doing real, low level, kernel development. The vast majority of work on Android is nothing more than building in modules and rearranging/writing simple scripts.
Basically, start learning why things are like they are. It is flat out amazing to me that it took literally MONTHS to figure out the DHCPCD script was just wrong in the CM9 builds. It blows my mind that this took months, and that's the only reason I am starting to get involved with this device now. I am perfectly happy with stock operations.

http://www.gottabemobile.com/2012/0...update/?utm_source=dlvr.it&utm_medium=twitter
Galaxy S2 might even get jelly bean. If THEY get it I would sure hope we would get it too. But either way all we need is a similar exynos device JB release, oh and source code wouldnt hurt either.
How long has it been since Austia ICS released for 7.7 and 7.0 plus? almost 2 weeks?
does it take that long to add their CSC bloat? perhaps they're going striaght to JB and just gave us the one ICS build they had to tide us over, considering they released it around the same time JB was announced.
we will see.

I think you don't need to worry about Jelly Bean right now. We can consider ourselves already very lucky there's someone working on porting CyanogenMod 9 on this fine tablet.
When CM9 is finished, their devs will start on CM10 (based on JB) right away. They stated the work for this version is not as big as with CM7 --> 9. If the same is valid for porting CM10 to a P62xx, just follow the Cyanogenmod page for updates and you'll be fine.

Is it possible...

Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500

You'd be better off asking the Infuse devs, I doubt any NS dev is going to be able to do anything to help you since they don't have the device to work on. The hardware is pretty similar so it could be doable but you're definitely going about it the wrong way.

DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
it is probably possible but you are likely to run into numerous errors, that is if you even get it to boot !
we just recently got jelly bean a few days ago and it is still improving so using that as base would likely result in a very unstable port.. but you are welcome to give it a try and see how it goes. the worst that can happen is having to go back to stock
if you happen to have a capable PC, you might want to try building your own rom from source! it should be a great learning experience and is much more likely to work compared to a port

DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
not sure about porting but there is a working JB rom on the Dev section

galaxy s line
i believe you'd actually be closer by using the CM10 for the fascinate that just landed yesterday, but i digress. the JB CM10 in the dev section is working better than CM9 for me.

I would definitely like to learn how to build a rom from source. But isn't there a lot of coding involved in that process? If there is, I would have to learn all that as I go. And I'm also going to check the development section right now, as soon as I post this reply. Seeing as I have a Nexus S and not an Infuse(my girlfriend does), I don't check this forum that often. Thank you all for the replies.

There are a few guides around that tell you how to set up the building environment on your PC, and how to sync repos and build for your device.
The complicated part might be fixing errors in your build , but thats how we all learn
Sent from my sweet and buttery Infuse

KitKat 4.4

Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag

There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app

Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk

The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk

lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:

Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.

just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....

I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though

pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro

pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.

Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs

pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!

Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.

pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.