Jump to content

Android 4.0 Ice Cream Sandwich source code !!!!


Guest munnaraaki

Recommended Posts

Source code is platform and hardware independent. It means only more or less work to do.

The question is what happens with Cyanogenmod, why download page and NB are down? What a hell means that joke "..and we're off. check back in 2 months :) #cm9 #ics" ????

Link to comment
Share on other sites

Guest t0mm13b

mikegapinski has got ICS running on LG GT540

http://forum.xda-developers.com/showpost.php?p=19507512&postcount=608

There seems to be munged up sources from reading the thread, armv6-vfp (which is what is on our blade) is missing/absent. Copying from the CM7 tree seems to break the compile of the dalvik code... :(

Hmm... and yeah, have had to fix up some LOCAL_MODULE_TAGS within the hardware/msm7k directory, which were absent...

Edit:

Was under that impression either the code repo sync is incomplete or that google dropped armv6 which is used in budget smartphones such as the Zte Blade. :)

Edited by t0mm13b
Link to comment
Share on other sites

Guest KonstaT

There seems to be munged up sources from reading the thread, armv6-vfp (which is what is on our blade) is missing/absent. Copying from the CM7 tree seems to break the compile of the dalvik code... :(

Hmm... and yeah, have had to fix up some LOCAL_MODULE_TAGS within the hardware/msm7k directory, which were absent...

Edit:

Was under that impression either the code repo sync is incomplete or that google dropped armv6 which is used in budget smartphones such as the Zte Blade. :)

Yeah, and after you've sorted that you'll still have various other problems with copybit, libaudio, audiopreprocessing, webrtc, etc. Some useful info can be found here:

https://github.com/mikegapinski

https://github.com/TeamICS/ICS_Fixes

I first started to just to see if my computer could handle the ICS build. It takes about 1h20min to build ICS for emulator in my laptop (core i5, 6gb). That worked out great so I decided to try if I could get it to boot in blade. I've been building it for armv5te because that is supported. After sorting various issues, I've got it to compile without errors. What comes to the booting part - not so succesful. It does boot, but into a black screen with this looping in logcat:


I/DEBUG ( 94): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 94): Build fingerprint: 'generic/zte_blade/blade:4.0.1/ITL41D/eng.tuomas.20111120.132659:eng/test-keys'

I/DEBUG ( 94): pid: 97, tid: 97 >>> zygote <<<

I/DEBUG ( 94): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr b27488be

I/DEBUG ( 94): r0 4094213a r1 b27488be r2 00000073 r3 00000000

I/DEBUG ( 94): r4 000b39a0 r5 000b3eb0 r6 00000000 r7 000b3eb0

I/DEBUG ( 94): r8 be8da620 r9 41fa8e94 10 41fa8e80 fp be8da634

I/DEBUG ( 94): ip 4095a10c sp be8da478 lr 4093bdfd pc 40012150 cpsr 20000010

I/DEBUG ( 94): #00 pc 0000e150 /system/lib/libc.so

I/DEBUG ( 94): #01 pc 0004bdfa /system/lib/libmedia.so (_ZN7android13MediaProfiles18addStartTimeOffsetEiPPKc)

I/DEBUG ( 94): #02 pc 0004bf6a /system/lib/libmedia.so (_ZN7android13MediaProfiles19startElementHandlerEPvPKcPS3_)

I/DEBUG ( 94): #03 pc 000058e4 /system/lib/libexpat.so

I/DEBUG ( 94): #04 pc 00005e72 /system/lib/libexpat.so

I/DEBUG ( 94): #05 pc 0000202e /system/lib/libexpat.so (XML_ParseBuffer)

I/DEBUG ( 94): #06 pc 0004b04c /system/lib/libmedia.so (_ZN7android13MediaProfiles25createInstanceFromXmlFileEPKc)

I/DEBUG ( 94): #07 pc 0004b520 /system/lib/libmedia.so (_ZN7android13MediaProfiles11getInstanceEv)

I/DEBUG ( 94): #08 pc 0000c4ec /system/lib/libmedia_jni.so

I/DEBUG ( 94): #09 pc 0001ec30 /system/lib/libdvm.so (dvmPlatformInvoke)

I/DEBUG ( 94): #10 pc 00059328 /system/lib/libdvm.so (_Z16dvmCallJNIMethodPKjP6JValuePK6MethodP6Thread)

I/DEBUG ( 94): #11 pc 0004cb72 /system/lib/libdvm.so (_Z21dvmCheckCallJNIMethodPKjP6JValuePK6MethodP6Thread)

I/DEBUG ( 94): #12 pc 00030a8c /system/lib/libdvm.so

I/DEBUG ( 94): #13 pc 000342d0 /system/lib/libdvm.so (_Z12dvmInterpretP6ThreadPK6MethodP6JValue)

I/DEBUG ( 94): #14 pc 0006c4fc /system/lib/libdvm.so (_Z14dvmCallMethodVP6ThreadPK6MethodP6ObjectbP6JValueSt9__va_list)

I/DEBUG ( 94): #15 pc 0006c51a /system/lib/libdvm.so (_Z13dvmCallMethodP6ThreadPK6MethodP6ObjectP6JValuez)

I/DEBUG ( 94): #16 pc 0007680c /system/lib/libdvm.so (dvmInitClass)

I/DEBUG ( 94): #17 pc 0007697e /system/lib/libdvm.so (_Z12dvmFindClassPKcP6Object)

I/DEBUG ( 94): #18 pc 00070674 /system/lib/libdvm.so (_Z18dvmFindClassByNameP12StringObjectP6Objectb)

I/DEBUG ( 94): #19 pc 000724e4 /system/lib/libdvm.so

I/DEBUG ( 94): #20 pc 00030a8c /system/lib/libdvm.so

I/DEBUG ( 94): #21 pc 000342d0 /system/lib/libdvm.so (_Z12dvmInterpretP6ThreadPK6MethodP6JValue)

I/DEBUG ( 94): #22 pc 0006c4fc /system/lib/libdvm.so (_Z14dvmCallMethodVP6ThreadPK6MethodP6ObjectbP6JValueSt9__va_list)

I/DEBUG ( 94): #23 pc 000550c6 /system/lib/libdvm.so

I/DEBUG ( 94): #24 pc 00049b3c /system/lib/libdvm.so

I/DEBUG ( 94): #25 pc 00041748 /system/lib/libandroid_runtime.so

I/DEBUG ( 94): #26 pc 0004228c /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcS2_)

I/DEBUG ( 94): #27 pc 00008f46 /system/bin/app_process

I/DEBUG ( 94): #28 pc 000164c6 /system/lib/libc.so (__libc_init)

I/DEBUG ( 94):

I/DEBUG ( 94): code around pc:

I/DEBUG ( 94): 40012130 0afffff9 e20330ff e0630c20 e49d4004

I/DEBUG ( 94): 40012140 e12fff1e e3100003 0a000006 e4d02001

I/DEBUG ( 94): 40012150 e4d13001 e3520001 21520003 0afffff8

I/DEBUG ( 94): 40012160 e0420003 e12fff1e e52d5004 e52d4004

I/DEBUG ( 94): 40012170 e3a02001 e1822402 e1822802 e201c003

I/DEBUG ( 94):

I/DEBUG ( 94): code around lr:

I/DEBUG ( 94): 4093bddc 00006386 0001e064 1c0eb5f0 b0836891

I/DEBUG ( 94): 4093bdec 1c141c07 d00d2900 44784810 efd6f7e8

I/DEBUG ( 94): 4093bdfc d0172800 490f480e 44784a0f 447a4479

I/DEBUG ( 94): 4093be0c e9a6f7e9 008020af 34901c3c 46699001

I/DEBUG ( 94): 4093be1c 96001c20 eeb4f7e8 1c204669 eeaaf7e8

I/DEBUG ( 94):

I/DEBUG ( 94): stack:

I/DEBUG ( 94): be8da438 000b37a8

I/DEBUG ( 94): be8da43c 401b6858

I/DEBUG ( 94): be8da440 000b6614

I/DEBUG ( 94): be8da444 401a78e9 /system/lib/libexpat.so

I/DEBUG ( 94): be8da448 000b38cc

I/DEBUG ( 94): be8da44c 000001b4

I/DEBUG ( 94): be8da450 be8da620

I/DEBUG ( 94): be8da454 be8da484

I/DEBUG ( 94): be8da458 00000000

I/DEBUG ( 94): be8da45c 00000000

I/DEBUG ( 94): be8da460 00000000

I/DEBUG ( 94): be8da464 000b39a0

I/DEBUG ( 94): be8da468 000001b0

I/DEBUG ( 94): be8da46c 00000000

I/DEBUG ( 94): be8da470 df0027ad

I/DEBUG ( 94): be8da474 00000000

I/DEBUG ( 94): #01 be8da478 00000000

I/DEBUG ( 94): be8da47c 000b6668

I/DEBUG ( 94): be8da480 00000000

I/DEBUG ( 94): be8da484 000b39a0

I/DEBUG ( 94): be8da488 000b3eb0

I/DEBUG ( 94): be8da48c 000b6640

I/DEBUG ( 94): be8da490 00000188

I/DEBUG ( 94): be8da494 4093bf6f /system/lib/libmedia.so

I/ServiceManager( 91): service 'media.audio_flinger' died

I/ServiceManager( 91): service 'media.player' died

I/ServiceManager( 91): service 'media.camera' died

I/ServiceManager( 91): service 'media.audio_policy' died
[/code]

This is actually my first time building from AOSP so I'm quite happy I even got this far. :) I'd appreciate if anyone has good ideas how to get forward.

Edited by KonstaT
Link to comment
Share on other sites

Guest t0mm13b

Hmmm... wonder why is the services dying...? Did you use the CM7's device/zte/blade tree for this? Are you sure that armv5te is the right one?

But well done on getting there :) Unfortunately, I am not sure where to start with myself, and am aware of the missing bits :) it could be the sync is out of date as when it first was announced, jbq did say the sync could be incomplete/partial.... :unsure:

Edited by t0mm13b
Link to comment
Share on other sites

Guest hecatae

Yeah, and after you've sorted that you'll still have various other problems with copybit, libaudio, audiopreprocessing, webrtc, etc. Some useful info can be found here:

https://github.com/mikegapinski

https://github.com/TeamICS/ICS_Fixes

I first started to just to see if my computer could handle the ICS build. It takes about 1h20min to build ICS for emulator in my laptop (core i5, 6gb). That worked out great so I decided to try if I could get it to boot in blade. I've been building it for armv5te because that is supported. After sorting various issues, I've got it to compile without errors. What comes to the booting part - not so succesful. It does boot, but into a black screen with this looping in logcat:

This is actually my first time building from AOSP so I'm quite happy I even got this far. :) I'd appreciate if anyone has good ideas how to get forward.

hi, any chance you can post up your boot.img?

Link to comment
Share on other sites

Guest KonstaT

Hmmm... wonder why is the services dying...? Did you use the CM7's device/zte/blade tree for this? Are you sure that armv5te is the right one?

But well done on getting there :) Unfortunately, I am not sure where to start with myself, and am aware of the missing bits :) it could be the sync is out of date as when it first was announced, jbq did say the sync could be incomplete/partial.... :unsure:

Yeah, I started with CM7's device/zte/blade but it is quite heavily modified now. Armv5te should work, atleast the HTC Hero guys are using it and it worked for them. And I don't even have a clue how to port that armv6 stuff to this source, so I had no choice. :P

I did a repo sync yesterday. It still can't be incomplete? Hopefully support will be added later though...

But this was only a test project. It went better than planned. I did it just to see that it was possible to compile ICS in reasonable time without hex-core, 16gb RAM, SSD, etc monster. I'm sure that there are many much more clever people (CM7/9 guys) working on this.

Link to comment
Share on other sites

Guest t0mm13b

Found this on xda, dalvik now support armv6-vfp.. :)

This ICS build is a nightmare... :lol:

have fixed up most errors including libaudio, libgralloc, copybit, but bombs out on missing liba2dp (bluetooth/audio) and libaudiointerface.a... sigh...

Edited by t0mm13b
Link to comment
Share on other sites

Guest hecatae

Things are looking good for ics a few devices similar spec to the blade have it booting XD

may i suggest donating to the blade cm7 devs? working for free is not much of an incentive to get ics out to community

Link to comment
Share on other sites

Guest furrabbit.nh

may i suggest donating to the blade cm7 devs? working for free is not much of an incentive to get ics out to community

Been using android for a while now and have donated quite alot before now to various devs over at xda for different handsets, ive only just joined modaco really (as an active user) and here will be no exception, i will doncate to CM7 Devs as soon as i have some spare cash, dont get paid for another few weeks. Only work part time so things are tight....

Link to comment
Share on other sites

Guest Bulthazar

Not sure if it has been mentioned on this forum but ICS is already booting on the Blade.

Although there is still alot of work to be done, looks very slow as of now.

Link to comment
Share on other sites

Guest furrabbit.nh

Not sure if it has been mentioned on this forum but ICS is already booting on the Blade.

Although there is still alot of work to be done, looks very slow as of now.

Looks promissing XD

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.