[AcerDroid]

ya i am willing to demo the uses however i dont have any device to record one except my liquid so sorry

[Sponsored Links]

[Ogglord]

It's very easy to test, I just tried it without flashing ofc. It was nice, perhaps too small sometimes but much more screen space. Icon spacing needs to be smaller. And scandinavian keyboard rendered far too small, most native apps worked except youtube player. 50% of the games was played in ~half the screen. And so on, but still nice to test.

edit: nice work btw

This post has been edited by Ogglord: 31 December 2009 - 01:37 PM

[AcerDroid]

Ogglord, on Dec 31 2009, 13:36, said:

It's very easy to test, I just tried it without flashing ofc. It was nice, perhaps too small sometimes but much more screen space. Icon spacing needs to be smaller. And scandinavian keyboard rendered far too small, most native apps worked except youtube player. 50% of the games was played in ~half the screen. And so on, but still nice to test.

edit: nice work btw

thanks

[liquid_it]

AcerDroid, on Dec 31 2009, 12:50, said:

Now I am expecting Apps on SD or Boot from SD modding here, If you succeed, let me know I want it also!

Ok, I started looking how to move apps to sd.
I'm going to share here what I'm doing, maybe someone more skilled will help!

After partitioning the sd with a primary fat partition and another primary ext2 partition (512Mb large), I was able to mount on /data/apps2 (a folder I made) and copy in it all apps from /data/apps, using busybox port for android.
Once checked the copy was successful I put my sd back on the liquid and renamed apps to apps_old (with every single app running crashing ), renamed apps2 to apps, and mounted again ext2 partition to /data/apps, and..
..everything worked!
Now I'm going to modify init.rc to mount the ext2 partition (with the apps I copied in it) on /data/apps on boot, and create the new boot.img with the modified init.rc..
Any suggestion?
Am I missing anything?

This post has been edited by liquid_it: 31 December 2009 - 02:41 PM

[behnaam]

So my mkbootimg worked? Good work!

[liquid_it]

behnaam, on Dec 31 2009, 15:37, said:

So my mkbootimg worked? Good work!

Still didn't made boot.img, there's something wrong in what I did: every app that was autostarted seems to crash when I go back to the old app directory on internal mem. (i.e.: unmounting the sd from app, removing app and renaming app_old back to app)
The only wy I found to fix it is to reinstall those apps, not so bad, but not even the "cleanest" way to hack my phone..

[AcerDroid]

yup behnaam thanx for that, wow liquid_it keep goin i will continue my modding after going back to my pc, i now start feeling my acer liquid desktop functionality. our family is waiting for new year, happy new year to all!!

[AcerDroid]

liquid_it, on Dec 31 2009, 15:15, said:

Still didn't made boot.img, there's something wrong in what I did: every app that was autostarted seems to crash when I go back to the old app directory on internal mem. (i.e.: unmounting the sd from app, removing app and renaming app_old back to app)
The only wy I found to fix it is to reinstall those apps, not so bad, but not even the "cleanest" way to hack my phone..

wow did it work after all? i cant wait to get it working on mine too maybe im going to concentrate on how we can boot from sd so porting android 2.1 roms from other devices will be easy. after i discover how to boot from sd, ill post it here and i expect alot from you guys that we can enable multitouch in liquid

[TheNano]

AcerDroid, on Dec 31 2009, 16:28, said:

wow did it work after all? i cant wait to get it working on mine too maybe im going to concentrate on how we can boot from sd so porting android 2.1 roms from other devices will be easy. after i discover how to boot from sd, ill post it here and i expect alot from you guys that we can enable multitouch in liquid

it should be easy , make a yaffs partition on the sd, use the recovery image we have to unyaffs system.img into that , change the rc_script in one boot.img so it mounts the right disk as system (maybe make other parations for data ... chache etc.) and then it should just work! another approach is chrooting into sd paritions from the rc script. now fastboot boot the image to boot from sd
These are just IDEAS , not testet

[blc]

I apologize for a bit of offtopic, but I have rooted my phone with Paul's superboot. Can I get the same result by adding "ro.sf.lcd_density=160" to build.prop (or perhaps some other .prop)?

[liquid_it]

AcerDroid, on Dec 31 2009, 16:28, said:

wow did it work after all? i cant wait to get it working on mine too maybe im going to concentrate on how we can boot from sd so porting android 2.1 roms from other devices will be easy. after i discover how to boot from sd, ill post it here and i expect alot from you guys that we can enable multitouch in liquid

Yeah, it worked indeed, I have just to find out which is the problem with those apps: it looks like crash happens only on marke-installed apps.

[AcerDroid]

blc, on Dec 31 2009, 16:07, said:

I apologize for a bit of offtopic, but I have rooted my phone with Paul's superboot. Can I get the same result by adding "ro.sf.lcd_density=160" to build.prop (or perhaps some other .prop)?

nope, that is the first method i tried first, i tried editing several props but no luck, you must do it in /default.prop

wow, im gonna try that thenano and i will post it here

nice liquid_it, but i think i will do boot from sd first and try motorola milestone rom to get the multitouch

This post has been edited by AcerDroid: 31 December 2009 - 04:26 PM

[liquid_it]

AcerDroid, on Dec 31 2009, 17:19, said:

nice liquid_it, but i think i will do boot from sd first and try motorola milestone rom to get the multitouch

Great!

[behnaam]

Ok guys gonna get drunk tonight and work hungover tomorrow on getting moto droids recovery img on the Liquid. It has some interesting features that could be handy on Liquid.

[AcerDroid]

behnaam, on Dec 31 2009, 17:25, said:

Ok guys gonna get drunk tonight and work hungover tomorrow on getting moto droids recovery img on the Liquid. It has some interesting features that could be handy on Liquid.

good luck

[liquid_it]

behnaam, on Dec 31 2009, 18:25, said:

Ok guys gonna get drunk tonight

I bet I won't flash your first release..

[luthepa1]

Ok this method still does not work for me. :-(

If perform all the same steps as AcerDroid does in his post. But the result for me is that when using fastboot-linux to boot the img with the phone in bootloader mode it still reports invalid boot image.

fastboot-linux -i 0x0502 boot ./newsuperboot.img
comes back with;
downloading 'boot.img'... OKAY
booting... FAILED (remote: invalid boot image)

I performed all the unpacking, editing, repacking, and hex editing under a emulated i386 Ubuntu Karmic 9.1 in VirtualBox. I then copy this back to my host sytem which is Ubuntu Karmic 9.1 64bit and peform the fastboot-linux commands to boot the new image. My host system is what I use to perform all my nand flashing like the original superboot.img for rooting. Never had any probs there. I am also using the base address and modded mkbootimg binary.

Any ideas? I am still interested to know Pauls method for how he made the liquid.superboot.img.

[AcerDroid]

luthepa1, on Jan 1 2010, 00:36, said:

Ok this method still does not work for me. :-(

If perform all the same steps as AcerDroid does in his post. But the result for me is that when using fastboot-linux to boot the img with the phone in bootloader mode it still reports invalid boot image.

fastboot-linux -i 0x0502 boot ./newsuperboot.img
comes back with;
downloading 'boot.img'... OKAY
booting... FAILED (remote: invalid boot image)

I performed all the unpacking, editing, repacking, and hex editing under a emulated i386 Ubuntu Karmic 9.1 in VirtualBox. I then copy this back to my host sytem which is Ubuntu Karmic 9.1 64bit and peform the fastboot-linux commands to boot the new image. My host system is what I use to perform all my nand flashing like the original superboot.img for rooting. Never had any probs there. I am also using the base address and modded mkbootimg binary.

Any ideas? I am still interested to know Pauls method for how he made the liquid.superboot.img.

you forgot to copy the first 12 bytes read the instructions again

[luthepa1]

AcerDroid, on Jan 1 2010, 14:23, said:

you forgot to copy the first 12 bytes read the instructions again

I did copy the first 12 bytes Like I said I followed your first post instructions so my boot.img had this

ANDROID!pk! or 41 4E 44 52 4F 49 44 21 70 6B 21 00

I dont know... I must be making a silly mistake somewhere

[luthepa1]

OK some what SUCCESS!!!

I still can not test a boot.img out (using the boot command) to see how it performs, which I am finding strange. Not sure if anyone knows why? Here is what I execute and get in return;

fastboot-linux -i 0x0502 boot ./newboot.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: invalid boot image)

If I issue the same command on Paul's superboot.img or AcerDroid's image they will boot (without flashing just using boot command).

OK now here is the strange but good news for me. Using the same boot.img I repacked that failed above when issuing the boot command, if I instead flash it to the boot partition it is successful! And reboot the phone and all works and I can see the modifications I made.

fastboot-linux -i 0x0502 flash boot ./newboot.img
sending 'boot' (2338 KB)... OKAY
writing 'boot'... OKAY
fastboot-linux -i 0x0502 reboot = SUCCESS!

Can anyone make sense of this?

[Sponsored Links]