Guest IronDoc Posted February 26, 2011 Report Posted February 26, 2011 Yeah I had data working for the short time I tested it. Couldn't get in to wireless and network settings though iirc. May just have been cos of the dodgy touchscreen performance.
Guest Jekle Posted February 26, 2011 Report Posted February 26, 2011 First Impressions Going into settings and selecting something doesn't work No Dialer When going into lanscape mode the accelerometer doesn't go back to portrait ro.sf.hwrotation=180? When going into Contacts I get android.process.acore has stopeed unexpectedly. Please try again. Sometimes I see a red bracket around the screen. but theres more ups than down's! It would be alot easier if friggin' ADB would work.
Guest sebbo90 Posted February 26, 2011 Report Posted February 26, 2011 Not totally working but still really really cool
Guest hecatae Posted February 26, 2011 Report Posted February 26, 2011 (edited) just found new hardware files at git clone git://codeaurora.org/platform/hardware/msm7k.git got to be honest, I dont know what .cpp means, edit ok it c preprocessor. Edited February 26, 2011 by hecatae
Guest Arr Too Posted February 26, 2011 Report Posted February 26, 2011 .cpp normally refers to a C++ source file.
Guest ThrashMan Posted February 27, 2011 Report Posted February 27, 2011 Sweet work guys.....OS boots and looks kinda groovy. Good job :huh:
Guest hecatae Posted February 27, 2011 Report Posted February 27, 2011 (edited) Has non working sound got to do with libaudioflinger.so? nook color devs could not get sound working, seeing if they fixed it, edit they fixed it but video wont work until aosp Edited February 27, 2011 by hecatae
Guest Ippe H Posted February 27, 2011 Report Posted February 27, 2011 (edited) First Impressions Going into settings and selecting something doesn't work No Dialer When going into lanscape mode the accelerometer doesn't go back to portrait ro.sf.hwrotation=180? When going into Contacts I get android.process.acore has stopeed unexpectedly. Please try again. Sometimes I see a red bracket around the screen. but theres more ups than down's! It would be alot easier if friggin' ADB would work.You can get in to some settings select it then press back button, and then press home screen to select last app back to settings. Then you can get it open. :huh: Btw,ADB is enabled in setteings, but it's not working, i think the problem is in kernel part on boot.img. Yes dialer is not working, i got sms with that image. So i think that RIL is working like in CM images. But crash some reason, can't say why becoss no adb.. :) Sometimes I see a red bracket around the screen. <-- is this mean some crash or kernel panic? i dont know yet. You can force rotation with camera app.. for testing.. Edited February 27, 2011 by Ippe H
Guest tomdubs Posted February 27, 2011 Report Posted February 27, 2011 Going into settings and selecting something doesn't work it works with the "proper" honeycomb ui, perhaps it just doesnt work full stop in this interface mode on honeycomb?
Guest fonix232 Posted February 27, 2011 Report Posted February 27, 2011 it works with the "proper" honeycomb ui, perhaps it just doesnt work full stop in this interface mode on honeycomb? The settings screen in portrait isn't huge enough to see the whole screen, that's why you can't see the settings. Going into landscape, selecting biggest font size in spare parts, and you can see the stuff.
Guest Jekle Posted February 27, 2011 Report Posted February 27, 2011 (edited) It won't let me select anything in the settings with the largest size and in landscape And the Accelerometer doesn't work properly, I can't remember what I did but it wouldn't go to landscape by its self I had to do something (CAN'T REMEMBER!) and it would go into landscape Edited February 27, 2011 by Jekle
Guest hecatae Posted February 27, 2011 Report Posted February 27, 2011 (edited) You can get in to some settings select it then press back button, and then press home screen to select last app back to settings. Then you can get it open. :huh: Btw,ADB is enabled in setteings, but it's not working, i think the problem is in kernel part on boot.img. Yes dialer is not working, i got sms with that image. So i think that RIL is working like in CM images. But crash some reason, can't say why becoss no adb.. :) Sometimes I see a red bracket around the screen. <-- is this mean some crash or kernel panic? i dont know yet. You can force rotation with camera app.. for testing.. adbd is present in the boot.img and init.rc has this # adbd is controlled by the persist.service.adb.enable system property service adbd /sbin/adbd disabled # adbd on at boot in emulator on property:ro.kernel.qemu=1 start adbd on property:persist.service.adb.enable=1 start adbd on property:persist.service.adb.enable=0 stop adbd I'll remove disabled to enable adb and upload the boot.img attached Edited February 27, 2011 by hecatae
Guest Bazd123 Posted February 27, 2011 Report Posted February 27, 2011 Cool, gave this a try today and one first boot up get the error "The Application Launcher (process com.android.launcher) has stopped unexpectedly. Please try again". Once I've forced closed seems to load up but with a Gingerbread looking launcher.
Guest Ippe H Posted February 27, 2011 Report Posted February 27, 2011 ramdisk from SDK11 init.rc # adbd is controlled by the persist.service.adb.enable system property service adbd /sbin/adbd class core <--- that line misssing disabled # adbd on at boot in emulator on property:ro.kernel.qemu=1 start adbd on property:persist.service.adb.enable=1 start adbd on property:persist.service.adb.enable=0 stop adbd default.prop # # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=0 ro.allow.mock.location=1 ro.debuggable=1 persist.service.adb.enable=1
Guest hecatae Posted February 27, 2011 Report Posted February 27, 2011 (edited) ramdisk from SDK11 init.rc # adbd is controlled by the persist.service.adb.enable system property service adbd /sbin/adbd class core <--- that line misssing disabled # adbd on at boot in emulator on property:ro.kernel.qemu=1 start adbd on property:persist.service.adb.enable=1 start adbd on property:persist.service.adb.enable=0 stop adbd default.prop # # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=0 ro.allow.mock.location=1 ro.debuggable=1 persist.service.adb.enable=1 ok added class core boot.img i'll go up and delete the previous, default.prop matches already Edited February 27, 2011 by hecatae
Guest Ippe H Posted February 27, 2011 Report Posted February 27, 2011 (edited) ok added class core boot.img i'll go up and delete the previous, default.prop matches alreadyStill no ADB Finaly i got it looks like honeycomb :huh: :) - Settings working - Contacts working Edited February 27, 2011 by Ippe H
Guest Bazd123 Posted February 27, 2011 Report Posted February 27, 2011 Still no ADB Finaly i got it looks like honeycomb :huh: :) - Settings working - Contacts working Oh that's awesome!
Guest Jekle Posted February 27, 2011 Report Posted February 27, 2011 Great Ippe H! Will you be uploading your new build? Is it slow? Have you got the sound to work yet? I'm still baffled!
Guest hecatae Posted February 27, 2011 Report Posted February 27, 2011 (edited) Still no ADB Finaly i got it looks like honeycomb :huh: :) - Settings working - Contacts working ok, I'll keep looking then, just built my own kernel using latest source Edited February 27, 2011 by hecatae
Guest Ippe H Posted February 27, 2011 Report Posted February 27, 2011 (edited) Great Ippe H! Will you be uploading your new build? Is it slow? Have you got the sound to work yet? I'm still baffled!Soon.. Yes it's kind of slow, no 3D acceleration.. I havent even try sounds, still want that adb first, then it's much easyer debug everyting else. Edited February 27, 2011 by Ippe H
Guest tomdubs Posted February 27, 2011 Report Posted February 27, 2011 (edited) Still no ADB Finaly i got it looks like honeycomb :huh: :) - Settings working - Contacts working I thought it was a "design choice" to have the other interface, the first thing I did when I downloaded it was getting that interface working, also I think su wasnt working, I just copied over the binary from the nexus 1 port on XDA, which fixed it Edited February 27, 2011 by tomdubs
Guest fonix232 Posted February 27, 2011 Report Posted February 27, 2011 I thought it was a "design choice" to have the other interface, the first thing I did when I downloaded it was getting that interface working, also I think su wasnt working, I just copied over the binary from the nexus 1 port on XDA, which fixed it That can't work, ARMv7 and ARMv6 binaries aren't compatible.
Guest tomdubs Posted February 27, 2011 Report Posted February 27, 2011 That can't work, ARMv7 and ARMv6 binaries aren't compatible. well I copied over the su binary and now it works.......
Guest hecatae Posted February 28, 2011 Report Posted February 28, 2011 Soon.. Yes it's kind of slow, no 3D acceleration.. I havent even try sounds, still want that adb first, then it's much easyer debug everyting else. I'll have a hack at the latest cm boot.img later, hopefully it is just that one line, but I edited the boot.img in honeycomb a2 and it made little difference
Guest Ippe H Posted February 28, 2011 Report Posted February 28, 2011 Audio working soon.. :huh: I/AudioHardwareMSM72XX( 149): get_audpp_filter I/AudioHardwareMSM72XX( 149): open /system/etc/AudioFilter.csv success. D/AudioHardwareInterface( 149): setMode(NORMAL) I/AudioHardwareMSM72XX( 149): Set master volume to 7.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now