Development Pocket Edge 2.2 NEW Firmware

[ptsenter]

Originally Posted by LiKuiD

Also, for reference...changing the Davlik VM heap size definetely increased the responsiveness of the device...i'm not sure why it was set to 128MB for stock, seems rather large.

New settings:

dalvik.vm.heapsize=32m (definte performance gain)

I'm not going to argue with practice: it always has precedence.
But it’s counterintuitive – usually decreasing the size of the heap causes VM to go into gc more often, which, for end user, looks like a computer got frozen for a while at random moments. And this is completely unproductive time for everybody and everything involved. And different users might need different settings depending on what apps they run more often and entire mixture of apps.
Nevertheless, it’s an interesting parameter to play and try to find optimal value.

[Billbofet]

Dumb question but for the "wifi supplicant" and "lcd density" edits on the build.prop, where are those?

I can't find them in the build.prop file, so I'm not sure if I am missing something, or if these need to be added.

Thanks,
Bill

[ptsenter]

Originally Posted by vicinc

Thanks to ptsenter insistence and generosity of Gunnerp245 we are having the dingo source codes here or here (mirror). Hope they are not useless and they will help the rom chefs.

Also PXA168 source code is here.

Now if somebody can pass a word to setCPU's developer I'm sure he can adjust this app to work for eDGe.
Since I don't play games I'd actually want to underclock mine to prolong battery use per charge.

[vicinc]

I may be tick.
I copied the binaries to sdcard. also disk image.
when trying to run from busybox is telling that flash_erase does not exist.
anybody here to help?

Originally Posted by kronarq

You can try flashing the maintenance (recovery) ram disk. I have been all through the update script and the file is never truncated. The commands used to flash to recovery are:

WARNING BE CAREFUL! These offsets and sizes are from the update script but run at your own risk.

flash_erase /dev/mtd5 0x00100000 48
nandwrite -s 0x00100000 -p /dev/mtd5 ramdisk.maint.gz.crc

ramdisk.maint.gz.crc can be pulled from your update. You will need to get flash_erase and nandwrite on your device as they are only in the recovery. If you can't pull the binaries out of the new ramdisk let me know and I will pull them for you.

[kronarq]

Copy the binaries to like /system/bin or wherever you want just not on a fat fs.
chmod 755 nandwrite
chmod 755 flash_erase

I pulled those binaries from the recovery ramdisk.

Those offsets should just affect the maintenance ramdisk but as always tread with caution as I haven't tested this.

I would also remove them once you are done for security sake.

[muranternet]

Originally Posted by Billbofet

Dumb question but for the "wifi supplicant" and "lcd density" edits on the build.prop, where are those?

I can't find them in the build.prop file, so I'm not sure if I am missing something, or if these need to be added.

Thanks,
Bill

You have to add them.

[ptsenter]

Originally Posted by LiKuiD

windowsmgr.max_events_per_sec=150 (should help with GUI navigation/redraw)
wifi.supplicant_scan_interval=160 (to help battery life)

Originally Posted by muranternet

You have to add them.

Who knows what the default values?

[n6pfk]

So what do we have to modify so that uboot, the kernel and the root file system can be booted and run directly from a storage device to avoid changing the nand? I have a beagleboard that can do this. It makes testing mods so much faster. Anyone have any ideas? Are there any magic button press/holds that enable this already?

[tigerszheng]

download the zip file from http://www.4shared.com/file/dwnR3GOd...ermine-09.html, rename it to update.zip and put it in usb flash driver.

Can't start to upgrade if I use the same method upgrade to Ermine(https://www.entourageedge.com/suppor...barticleid=265

Any suggestion?

[kronarq]

Originally Posted by n6pfk

So what do we have to modify so that uboot, the kernel and the root file system can be booted and run directly from a storage device to avoid changing the nand? I have a beagleboard that can do this. It makes testing mods so much faster. Anyone have any ideas? Are there any magic button press/holds that enable this already?

If you look through the update script the locations for the bootloader are in it. I have no desire to go monkeying around with it until I get my jtag programmer and figure out how to connect it. Has anyone had any luck with that?

[vicinc]

kronarq> thanks, I will test this. seems you are decided here to progress a rom. this is good new. any chance to get together with ptsenter and emusan to see where they are in terms of development?

[vicinc]

New version added with minor speed tweaks

[vicinc]

done all this including the copying into system/bin and chmod
all I am getting now is permission denied when trying flash_erase /dev/mtd5 0x00100000 48 from adb shell

Originally Posted by kronarq

You can try flashing the maintenance (recovery) ram disk. I have been all through the update script and the file is never truncated. The commands used to flash to recovery are:

WARNING BE CAREFUL! These offsets and sizes are from the update script but run at your own risk.

flash_erase /dev/mtd5 0x00100000 48
nandwrite -s 0x00100000 -p /dev/mtd5 ramdisk.maint.gz.crc

ramdisk.maint.gz.crc can be pulled from your update. You will need to get flash_erase and nandwrite on your device as they are only in the recovery. If you can't pull the binaries out of the new ramdisk let me know and I will pull them for you.

[ptsenter]

Originally Posted by vicinc

done all this including the copying into system/bin and chmod
all I am getting now is permission denied when trying flash_erase /dev/mtd5 0x00100000 48 from adb shell

Did you issue

su

prior to flash_erase?

[vicinc]

of course. I read on a another forum that I may need to do flash_unlock on that partition but can not find the tool