Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 I'd imagine cause they wanted to and it was a challenge that they thought would be fun (or at least worthwhile) to tackle. I agree with the fun, and if any of the native applications work, we could look at backporting to 2.3 or 2.2, I think the lockscreen would look nice Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 what a waste of time and energy... these guys should focus on CM7 I'm testing cm7 daily, honeycomb is for fun and a good learning experience Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 24, 2011 Report Share Posted February 24, 2011 D'you need Linux (Ubuntu to decompress the ramdisk and recompress?) D'you have any instructions to do so, I'd like to help out. Link to comment Share on other sites More sharing options...
Guest Ippe H Posted February 24, 2011 Report Share Posted February 24, 2011 D'you need Linux (Ubuntu to decompress the ramdisk and recompress?) D'you have any instructions to do so, I'd like to help out. http://discuz-android.blogspot.com/2008/01...ramdiskimg.html Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 http://android-dls.com/wiki/index.php?titl...ack_Boot_Images the above is what I followed, specifically Unpacking, Editing, and Re-Packing the images, you need to unpack the boot.img and decompress the ramdisk. then in the working folder you will find init.rc Linux would help, you could use a Wubi install or a Virtual Machine, these would not affect your windows setup Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 24, 2011 Report Share Posted February 24, 2011 I have it on the a different partition so I've got Windows 7 and Ubuntu 10.10 Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 24, 2011 Report Share Posted February 24, 2011 Out of curiosity, what device was this? I really cant remember, there was a series of tablet and phones I looked at... apart from the ZTE stuff, and something else I signed an NDA nothing really stood out for me,.. The thing you have to remember about MWC tho, us a lot of stuff never shows up to market, or in the form that they show... I was at MWC last year and I remember playing with a Blade that was running 1.6..... I wonder if ZTE still have that build somewhere :huh: Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 24, 2011 Report Share Posted February 24, 2011 Android 1.6 would be pretty pointless going on the Blade, but on the overhand it could be very fast. Link to comment Share on other sites More sharing options...
Guest Lew247 Posted February 24, 2011 Report Share Posted February 24, 2011 I've merged these two topics - no need for 2 seperate threads on the same thing Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 I really cant remember, there was a series of tablet and phones I looked at... apart from the ZTE stuff, and something else I signed an NDA nothing really stood out for me,.. The thing you have to remember about MWC tho, us a lot of stuff never shows up to market, or in the form that they show... I was at MWC last year and I remember playing with a Blade that was running 1.6..... I wonder if ZTE still have that build somewhere :huh: or in other words you know who it was but the Non Disclosure Agreement stops you from saying. we could get a donut build up and running if you need, the boot.img provided with this honeycomb port is 3g vmsplit not 2g vmsplit Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 24, 2011 Report Share Posted February 24, 2011 But surely were going backwards if we put Donut on our devices? Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 But surely were going backwards if we put Donut on our devices? I'm not saying we should but it would be nice to get our hands on that build to have a look at it. Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 24, 2011 Report Share Posted February 24, 2011 But surely were going backwards if we put Donut on our devices? it would be an interesting historical curiosity.... Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 (edited) motorola xoom honeycomb system dump is here http://www.androidpolice.com/2011/02/23/mo...le-to-download/ might be something to work through, build.prop etc android police mirror http://lts.cr/PWj motorola claimed dmca on the original dump, someone download it quick Edited February 24, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest fonix232 Posted February 24, 2011 Report Share Posted February 24, 2011 No use, SMALI does not support HoneyComb yet... no deodexing :S ... No new music app! Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 (edited) Uncompress boot.img-ramdisk.gz ADD the dnsproxy line in init.rc for netd daemon service Code: service netd /system/bin/netd socket netd stream 0660 root system socket dnsproxyd stream 0660 root inet <---- Recompress edited ramdisk finally done the above, uploading now, should boot, though I'm going to be checking the xoom build.prop. okay the system dump has no build.prop? 19df4c91f30d6367626235841844fce9 signed_022411_213531.zip http://www.multiupload.com/MH6ZL5F03I though there is a vendor folder, containing a firmware folder with the wireless stuff inside booting to upside android, that's progress Edited February 24, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 No use, SMALI does not support HoneyComb yet... no deodexing :S ... No new music app! just noticed that, tried to deodex all files, no go Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 (edited) ok boots, but screen upside and no sensors work, but it boots to homescreen Edited February 24, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest Ippe H Posted February 24, 2011 Report Share Posted February 24, 2011 ok boots, but screen upside and no sensors work, but it boots to homescreen yeah :huh: nick work!! adb not work :) Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 24, 2011 Report Share Posted February 24, 2011 (edited) current build.prop is below, anyone want to suggest modifications or supply a modified build.prop? no dalvik vm cache in build prop as of yet, ril not working due to missing drivers, same with wifi, same with egl drivers # begin build properties # autogenerated by buildinfo.sh ro.build.id=HONEYCOMB ro.build.display.id=sdk-eng 3.0 HONEYCOMB 104254 test-keys ro.build.version.incremental=104254 ro.build.version.sdk=11 ro.build.version.codename=REL ro.build.version.release=3.0 ro.build.date=Wed Feb 16 19:26:18 PST 2011 ro.build.date.utc=1297913178 ro.build.type=eng ro.build.user=android-build ro.build.host=android-test-15.mtv.corp.google.com ro.build.tags=test-keys ro.product.model=sdk ro.product.brand=generic ro.product.name=sdk ro.product.device=blade ro.product.board= ro.product.cpu.abi=armeabi ro.product.manufacturer=unknown ro.product.locale.language=ldpi ro.wifi.channels= ro.board.platform= # ro.build.product is obsolete; use ro.product.device ro.build.product=generic # Do not try to parse ro.build.description or .fingerprint ro.build.description=sdk-eng 3.0 HONEYCOMB 104254 test-keys ro.build.fingerprint=generic/sdk/generic:3.0/HONEYCOMB/104254:eng/test-keys ro.build.characteristics=default # end build properties # # system.prop for generic sdk # rild.libpath=/system/lib/libreference-ril.so rild.libargs=-d /dev/ttyS0 # # ADDITIONAL_BUILD_PROPERTIES # ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=Alarm_Classic.ogg ro.kernel.android.checkjni=1 ro.setupwizard.mode=OPTIONAL xmpp.auto-presence=true ro.config.nocheckin=yes net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt[/codebox] Edited February 24, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 25, 2011 Report Share Posted February 25, 2011 (edited) It boots but the screen is upside down and the touchscreen doesn't work. At least were making progress Everyone needs to add this to the # ADDITIONAL_BUILD_PROPERTIES section in build.prop ro.sf.lcd_density=240 qemu.sf.lcd_density=240 Instead of it being so hard see Edited February 25, 2011 by Jekle Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 25, 2011 Report Share Posted February 25, 2011 It boots but the screen is upside down and the touchscreen doesn't work. At least were making progress Everyone needs to add this to the # ADDITIONAL_BUILD_PROPERTIES section in build.prop ro.sf.lcd_density=240 qemu.sf.lcd_density=240 Instead of it being so hard see Jekle, if you can provide a full build.prop to work from I'd appreciate it Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 25, 2011 Report Share Posted February 25, 2011 (edited) # begin build properties # autogenerated by buildinfo.sh ro.build.id=Honeycomb ro.build.display.id=sdk-eng 3.0 HONEYCOMB 104254 test-keys ro.build.version.incremental=104254 ro.build.version.sdk=11 ro.build.version.codename=REL ro.build.version.release=3.0 ro.build.date=Wed Feb 16 19:26:18 PST 2011 ro.build.date.utc=1297913178 ro.build.type=user ro.build.user=android-build ro.build.host=localhost.localdomain ro.build.tags=test-keys ro.product.model=ZTE Blade ro.product.brand=ZTE ro.product.name=P729J_SBM ro.product.device=blade ro.product.board=blade ro.product.cpu.abi=armeabi ro.product.manufacturer=ZTE ro.product.locale.language=en ro.product.locale.region=GB ro.wifi.channels= ro.board.platform=msm7k # ro.build.product is obsolete; use ro.product.device ro.build.product=generic # Do not try to parse ro.build.description or .fingerprint ro.build.description=sdk-eng 3.0 HONEYCOMB 104254 test-keys ro.config.ringtone=Terminated.ogg persist.sys.timezone=Europe/London ro.build.fingerprint=generic/sdk/generic:3.0/HONEYCOMB/104254:eng/test-keys ro.build.characteristics=default # end build properties # # system.prop for generic sdk # rild.libpath=/system/lib/libreference-ril.so rild.libargs=-d /dev/ttyS0 # # ADDITIONAL_BUILD_PROPERTIES # ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=Alarm_Classic.ogg ro.sf.lcd_density=240 qemu.sf.lcd_density=240 ro.kernel.android.checkjni=1 ro.setupwizard.mode=OPTIONAL xmpp.auto-presence=true ro.config.nocheckin=yes net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt [/codebox] I've havn't edited any RIL related things, because my I tried to replace libsurfaceflinger.so or libcm.so or libril-qc-1.so I'd stay stuck on the Green Android (libcm.so libril-qc-1.so make the RIL Work) Delete all files in system\usr\keylayout and replace that with the one i've attached (get the power button to work lock and unlock)keylayout.zip Edited February 25, 2011 by Jekle Link to comment Share on other sites More sharing options...
Guest Jekle Posted February 25, 2011 Report Share Posted February 25, 2011 (edited) Found this hecatae this may be able to flip the screen around. (Found in old San Fran 2.3 Topic) by MDCfan Ok guys, I have hacked libsurfaceflinger.so file so screen is no longer upside down! Open libsurfaceflinger.so using hex editor, go to offset 220EA and change byte 00 to 02. Then flash your ROM and enjoy. P.S. Touch is upside down, but this is because Tom G fliped it in alpha2? EDIT: attached edited file just in case somebody needs it. EDIT2: removed file. See new one here: http://android.modaco.com/content/zte-blad...t&p=1513377 Edited February 25, 2011 by Jekle Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 25, 2011 Report Share Posted February 25, 2011 EDIT2: removed file. See new one here: http://android.modaco.com/index.php?s=&...t&p=1513377 link takes me to front page of site? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now