[ROM] Honeycomb SDK Port 15.07.2011 [GEN2 only]

[Guest Jekle]

Seems like that link has been removed...

Edited February 25, 2011 by Jekle

[Guest hecatae]

xoom build.prop is here http://forum.xda-developers.com/showthread.php?t=967846

a 3 way compare should give us a working build.prop, honeycomb has a new way of doing build.prop

Edited February 25, 2011 by hecatae

[Guest Jekle]

Ok?

[Guest hecatae]

Ok?

xoom build.prop has this:

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=256m[/codebox]


that's a big heapsize

[Guest ThrashMan]

How are you guys getting on? Looks like some progress has been made :huh:

[Guest Ippe H]

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.

In that new libsurfaceflinger.so offset 1ACFA and change byte 00 to 02.

[Guest Jekle]

Thanks for that Ippe H, heres the edited libsurfaceflinger.so

libsurfaceflinger.zip

Edited February 25, 2011 by Jekle

[Guest hecatae]

How are you guys getting on? Looks like some progress has been made :huh:

it boots and the keylayout works.

[Guest Jekle]

What do we need to get the touch working?

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=256m[/codebox]

This Xoom has 1GB of ram so that is a quarter of the ram so for a 512mb Blade we would use 128mb? (heap size)

so 256mb is the heap size and growth limit is 48mb and the start size is 5mb

Why would the heapsize be 256mb when the growth limit is 48mb?

Edited February 25, 2011 by Jekle

[Guest hecatae]

What do we need to get the touch working?

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=256m[/codebox]


This Xoom has 1GB of ram so that is a quarter of the ram so for a 512mb Blade we would use 128mb?


https://github.com/HCDRJacob/proprietary_ve...sors.default.so < this and a couple of other things from https://github.com/HCDRJacob/proprietary_ve...ade/proprietary

[Guest Ippe H]

Thanks for that Ippe H, heres the edited libsurfaceflinger.so

No problem :huh:

To help debug, i need ADB..

signed_022411_213531.zip ADB not work.

signed_022311_233551.zip ADB was working. But stuck to: Unable to start DnsProxyListener (No such file or directory) <-- this boot.img with fixed line to init.rc

Edited February 25, 2011 by Ippe H

[Guest hecatae]

What do we need to get the touch working?

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=256m[/codebox]


This Xoom has 1GB of ram so that is a quarter of the ram so for a 512mb Blade we would use 128mb?


I think same startsize, growthlimit of 24m and 128m for heapsize would do, though previous roms have only had a 32m heapsize, the bigger the heapsize the less cpu usage the longer the battery lasts

[Guest Jekle]

No problem :huh:

To help debug, i need ADB..

signed_022411_213531.zip ADB not work.

signed_022311_233551.zip ADB was working. But stuck to: Unable to start DnsProxyListener (No such file or directory) <-- this boot.img with fixed line to init.rc

Weird it was working in signed_022311_233551.zip (not getting past android boot animation, but signed_022411_213531.zip doesn't work, did you remove something hecatae?

[Guest Jekle]

What's working?

Key layout

Screen right way up (with my fix previous page)

Battery Status

What's not working?

Touchscreen

RIL

Sound?

GPS?

Wi-fi?

Sensors

Camera?

SD Card

Bluetooth?

I don't know much more because of no touch I can't test whats working or not. We are getting there. Slowly....

And I've noticed random restarts

Edited February 25, 2011 by Jekle

[Guest hecatae]

No problem :huh:

To help debug, i need ADB..

signed_022411_213531.zip ADB not work.

signed_022311_233551.zip ADB was working. But stuck to: Unable to start DnsProxyListener (No such file or directory) <-- this boot.img with fixed line to init.rc

interesting, rom from the 23rd was using the config from the zte 2.6.32 github,

rom from the 24th is using Tom G's boot.img from CM7 with the init.rc adjustment, and it boots further than the 23rd rom.

[Guest hecatae]

Weird it was working in signed_022311_233551.zip (not getting past android boot animation, but signed_022411_213531.zip doesn't work, did you remove something hecatae?

I'm going to pull the config from cm7 later and have a look, does adb work with cm7?

reason for using that boot.img is it has the 3g vmsplit, making development easier

Edited February 25, 2011 by hecatae

[Guest Jekle]

Yeah it works with CM7 just tested

[Guest hecatae]

Yeah it works with CM7 just tested

okay. not removed anything. so I doubt it's anything in the boot.img preventing adb, debugging may not be enabled in the settings.apk

Edited February 25, 2011 by hecatae

[Guest Jekle]

What would we need to do to get the touch working is it something to do with egl?

[Guest hecatae]

What would we need to do to get the touch working is it something to do with egl?

egl = enhanced graphics layer, the graphics drivers.

I remember something in framework needs altering sensors.cpp or simialr

Edited February 25, 2011 by hecatae

[Guest hecatae]

What do we need to get the touch working?

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=256m[/codebox]


This Xoom has 1GB of ram so that is a quarter of the ram so for a 512mb Blade we would use 128mb? (heap size)


so 256mb is the heap size and growth limit is 48mb and the start size is 5mb


Why would the heapsize be 256mb when the growth limit is 48mb?


it basically means the heap cant grab 256mb at once, has to grab it in steps


right added your surfaceflinger


and 


ro.sf.lcd_density=240

ro.sf.hwrotation=180

qemu.sf.lcd_density=240


to build.prop

Edited February 25, 2011 by hecatae

[Guest Jekle]

Will a new build be coming later?

Have you been able to fix the touchscreen?

[Guest hecatae]

Will a new build be coming later?

Have you been able to fix the touchscreen?

I think I'm going to get nowhere as the entire system is built for armv7.

[Guest Ippe H]

I think I'm going to get nowhere as the entire system is built for armv7.

I got something, notificantion area say in boot: Preparing sd card :P

can't say is it working correct, becoss no touchscreen or adb :D

Edit: i think it works, becoss in my sdcard is many new folders.. Alarms, Movies, Podcasts, etc...

- RIL working

- 3G data i think becoss i see 3g icon :huh:

I need to remove PIN-code my simcard, becoss can't enter it :)

Edited February 26, 2011 by Ippe H

[Guest Jekle]

We need alot more devs on this topic, we would get through the problem alot quicker!