10/Mar 3.2 - MoDaCo Custom ROM for GSM Hero (now with online kitchen)

[Guest Paul]

Remember if you are going to wipe, wipe BEFORE you flash, otherwise wipe then reflash the update (as wiping removes the stuff from the update in the data partition!)

P

[Guest Zeppu]

I just installed 2.8 and WaveSecure 2 days ago and since then battery life has been going down incredibly fast. From 100 to 12% takes approximately 6 hours or normal usage.

Yesterday, I realized that the awake time for the Hero was 100%. I quickly managed to pinpoint this down to WaveSecure which I closed using a task killer. Since then awake time has gone down and battery life has gone to normal. I tried rebooting the phone and same thing happened.

For some reason WaveSecure doesn't let the phone go to sleep. Is this normal? Is it a known issue?

If therei s no fix I'm afraid I'll uninstalling the application (which BTW, I don't know how to do either).

[Guest cdcuk]

Remember if you are going to wipe, wipe BEFORE you flash, otherwise wipe then reflash the update (as wiping removes the stuff from the update in the data partition!)

P

Paul, Q: I wiped 2.7 before installing 2.8. How to find/reinstall voice search?

[Guest kendon]

i had the same problem, battery completely drained in max 8 hours. i didn't install wavesecure at all with 2.8, though i like the application. but as long as the battery problem is not fixed it is a no go, and i still would like to see gps being used...

as for uninstalling: either flash the core rom again or delete /system/app/com.wsandroid.apk via adb...

[Guest uk786]

Paul Great work my device is so fast and slick its unbelievable and the apps2sd is really useful and also the spare parts app GOOD JOB!

[Guest GodsDevil]

Paul, Q: I wiped 2.7 before installing 2.8. How to find/reinstall voice search?

Voice search is already there in 2.8. If it is not working for you do what Paul suggested in a previous post...go to recovery, wipe and re-flash 2.8. I believe that should fix the problem.

Cheers

D

[Guest cdcuk]

Voice search is already there in 2.8. If it is not working for you do what Paul suggested in a previous post...go to recovery, wipe and re-flash 2.8. I believe that should fix the problem.

Cheers

D

wipe/reinstall/restore fixed it -- thanks.

[Guest clarkEEE1]

I don't think you need to wipe and flash again well I didn't just uninstall and reinstalled worked straight away again.

[Guest Ajitsu]

Does anyone know how to uninstall "wifi status"?

Doesn't work via "advanced task manager".

[Guest kendon]

Does anyone know how to uninstall "wifi status"?

Doesn't work via "advanced task manager".

remove it via adb... /system/app/com.schwimmer.android.wifistatus.apk

Edited October 30, 2009 by kendon

[Guest Ajitsu]

remove it via adb... /system/app/com.schwimmer.android.wifistatus.apk

Thank you, it works fine.

[Guest worcester4x4]

Whoa! Been away for a couple of days and suddenly another 10 pages are added here! Wow.

I'm too bushed at the moment to catch up on all of this so can I be lazy and ask a question? What is everyone recommending now? Am I cool to go with:

Amon-Ra recovery image

Then flash with 2.8 core

Then 2.8 enhanced

Then Wavesecure

Then Teknologist's new ROM?

Is this a good plan or should I consider other options?

[Guest Ludolf]

Does anyone know how to uninstall "wifi status"?

Doesn't work via "advanced task manager".

Just had the same wish and did this:

adb remount

adb shell rm /system/app/*wifistatus*[/codebox]

[Guest kendon]

Whoa! Been away for a couple of days and suddenly another 10 pages are added here! Wow.

I'm too bushed at the moment to catch up on all of this so can I be lazy and ask a question? What is everyone recommending now? Am I cool to go with:

Amon-Ra recovery image

Then flash with 2.8 core

Then 2.8 enhanced

Then Wavesecure

Then Teknologist's new ROM?

Is this a good plan or should I consider other options?

i (and others) have problems with wavesecure draining the battery, so you gotta see if you install it. other than that for me the setup is:

amon-ra

2.8 core

black-sense 1.1

evils lockscreen for 2.5.1

teknologists kernel 1.7

by now on an ext3 partition, but only because i was too lazy yet to convert it :D

just tested this with a wiped phone, applied all updates in series without restarts in between them, seems to work!

[Guest Streetdaddy]

Loving the latest update! Once again performance seems to have gotten better, and is it just me or has battery life also improved? I'm going on almost 48 hours and still 24% remaining, definitely a record for me... nb. i'm not using Wavesecure, just the latest custom rom, enhanced pack and radio.

[Guest Chatt76]

I wanted to install this (NEW VERSION 1.7-hero-teknologist-custom-autosetup-signed) and I deleted the swap and turned ext3 to ext4 in gparted Ubuntu (9.10).

But booting ended in loops.

I tried everything nandroids, wipings, formattings sd, new 2.8 flashing,...etc. but nothing had worked.

At the end I did automatically partitioning with RA 1.2.3 recovery, turned ext2 to ext3 and my nandroid backup worked again.

So it looks like ext4 is really not working!

Thanks for your development and hard work! Good job!

[Guest keef319]

I wanted to install this (NEW VERSION 1.7-hero-teknologist-custom-autosetup-signed) and I deleted the swap and turned ext3 to ext4 in gparted Ubuntu (9.10).

But booting ended in loops.

I tried everything nandroids, wipings, formattings sd, new 2.8 flashing,...etc. but nothing had worked.

At the end I did automatically partitioning with RA 1.2.3 recovery, turned ext2 to ext3 and my nandroid backup worked again.

So it looks like ext4 is really not working!

Thanks for your development and hard work! Good job!

I'm having no probs with ext4...think it's the same for most people. :D

[Guest kendon]

I wanted to install this (NEW VERSION 1.7-hero-teknologist-custom-autosetup-signed) and I deleted the swap and turned ext3 to ext4 in gparted Ubuntu (9.10).

But booting ended in loops.

I tried everything nandroids, wipings, formattings sd, new 2.8 flashing,...etc. but nothing had worked.

At the end I did automatically partitioning with RA 1.2.3 recovery, turned ext2 to ext3 and my nandroid backup worked again.

So it looks like ext4 is really not working!

Thanks for your development and hard work! Good job!

try to do it with amon ras recovery image, works for me. use the sdparted tool in an adb shell session:

would be for a 512mb ext4 and remaining space to fat32:

adb shell

sdparted -es 512M -ss 0

sdparted -ufs ext4

Edited October 31, 2009 by kendon

[Guest keef319]

Do many people actually use the "Scenes"?

I never do...I just set my phone up how I want it, and that's it whether I'm at work, weekends, whatever.

Just wondered if it's something that takes up unnecessary space in the ROM?

[Guest Chatt76]

try to do it with amon ras recovery image, works for me. use the sdparted tool in an adb shell session:

would be for a 512mb ext4 and remaining space to fat32:

So the only difference in your method is to partion sd in another order...!?

Your partition order seems to be

1. Partition: ext4

2. Partition: fat32?

But I did it the opposite way. Everywhere I read they told to do in the order I did...confusing.

I think there's no difference by formatting an partitioning with ra recovery's adb shell or ubuntu's gparted. What do you think?

[Guest kendon]

So the only difference in your method is to partion sd in another order...!?

Your partition order seems to be

1. Partition: ext4

2. Partition: fat32?

But I did it the opposite way. Everywhere I read they told to do in the order I did...confusing.

I think there's no difference by formatting an partitioning with ra recovery's adb shell or ubuntu's gparted. What do you think?

idk about the order, or whether it makes a difference with what tool you create the partitions (probably not), but this way is convinient, fast and works for me.

[Guest Chatt76]

idk about the order, or whether it makes a difference with what tool you create the partitions (probably not), but this way is convinient, fast and works for me.

I think you have to care the order of your partitions. RA recovery cannot mount sd if you do like you did.

I did try now and I had to partition fat32 as the first partition.

And still ext4 ist not working. I dont know why.

Still partitioning with Ubuntu gparted instead of sdparted because I dont know how to run script sdparted.txt in linux.

[Guest kendon]

I think you have to care the order of your partitions. RA recovery cannot mount sd if you do like you did.

I did try now and I had to partition fat32 as the first partition.

And still ext4 ist not working. I dont know why.

Still partitioning with Ubuntu gparted instead of sdparted because I dont know how to run script sdparted.txt in linux.

after using the sdparted tool from amonra usb mass storage works fine in recovery, if you mean that. according to mount the fat32 partition is the first partition:

/dev/block/mmcblk0p1 on /sdcard type vfat

actually it would be strange if the recovery image would create partitions it cannot handle itself... :D

[Guest bazzawhite]

Ok I tried as some other users said about wiping the phone clean and then reflashing the 2.8 ROM. I am still having problems with Googlemaps and directions. Googlemaps itself loads up but pressing directions just causes a few second pause and the nothing shows up. Any more ideas are welcome.

One thing though I restored my nandroid backup after the reflash I don't know if it is a setting that might be causing the problem.

The order of things I did:

1. Nandroid backup

2. Wipe data/factory settings

3. Installed 2.8 ROM

4. Install latest radio

5. Install latest kernel (Teknologist)

6. Nandroid restore

Any ideas would be welcome.

Thanks

[Guest bricky]

Ok I tried as some other users said about wiping the phone clean and then reflashing the 2.8 ROM. I am still having problems with Googlemaps and directions. Googlemaps itself loads up but pressing directions just causes a few second pause and the nothing shows up. Any more ideas are welcome.

One thing though I restored my nandroid backup after the reflash I don't know if it is a setting that might be causing the problem.

The order of things I did:

1. Nandroid backup

2. Wipe data/factory settings

3. Installed 2.8 ROM

4. Install latest radio

5. Install latest kernel (Teknologist)

6. Nandroid restore

Any ideas would be welcome.

Thanks

Why did you do Nandroid restore? That put you back where you started.

Edited November 1, 2009 by bricky