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

[Guest comeflywithme]

For people who need chinese input urgently,

this might help: (not tested myself thought)

http://forum.xda-developers.com/showthread.php?t=576302

[Guest Ihan]

For people who need chinese input urgently,

this might help: (not tested myself thought)

http://forum.xda-developers.com/showthread.php?t=576302

thank you~~

[Guest IZIIZI]

just apps & data is fine, the included kernel doesn't use swap files based on sd partition, check out its dedicated thread

http://android.modaco.com/content/htc-hero...pache-ramzswap/

its all explained

Dickie

Just updated this morning, my phone is showing less space than before! 19mb...

In recovery there was only an option for swap/data/apps, so I take it that couldnt be the cause of it?

Should I try to partition again, then install 2.9 update again?

Edited November 10, 2009 by IZIIZI

[Guest teknologist]

Just some feedback from my experiences with the suggestions made here to move dalvik-cache.

After lots of automatic reboots of the phones while using "Wifi tether for Root users" v 1.6pre3 and 1.6-htc, I moved back dalvik-cache to its original place and solved the issue...

Just my experience here...

[Guest t3monkeyboy]

Having updated to modaco 2.9 and the updated radio, i seem to have a problem with the call history not logging any calls and sms ive sent not showing?

Anyone else having any issues like this?

[Guest t3monkeyboy]

sorted now i think, when updating the new radio it was resetting the date and time to 1980, so was it was displaying the call history and messages in chronological order meaning they werent where i was looking for them. reloaded the old radio and then loaded the new one and it happened again. has aanyone else had this?

[Guest kendon]

sorted now i think, when updating the new radio it was resetting the date and time to 1980, so was it was displaying the call history and messages in chronological order meaning they werent where i was looking for them. reloaded the old radio and then loaded the new one and it happened again. has aanyone else had this?

yes. i think a radio update does reset most of the "variable" system settings like time, date, gps data and i don't know what else.

[Guest Keramidas]

Just updated this morning, my phone is showing less space than before! 19mb...

In recovery there was only an option for swap/data/apps, so I take it that couldnt be the cause of it?

Should I try to partition again, then install 2.9 update again?

This is because the dalvik-cache (/data/dalvik-cache in internal flash memory) is about 25MB larger than before. I agree that it makes /data space a bit tight, especially if you have many apps installed. It is possible to move the dalvik-cache to another place, which frees up A LOT of space in /data, but it must be done manually and is to be done by advanced users. If you want to do it, look at the previous messages to find out how :)

[Guest TheMathMan]

Hi.

I am new to this site and Android. I got my HTC Hero (which I assume is stock and carrier unlocked as O2 don't carry this device) - White on O2 via buymobilephones.net and have upgraded to the latest build via the HTC website 2.73.405.5 146733 CL#61267

I would like to put on this custom ROM.

So far I have tried the following - installing the patched recovery ROM via Terminal on a Mac. I got into the bootloader but it wouldn't let me do it giving me this: downloading 'boot.img'... FAILED (remote: not allow)"

I read that with flashrec I might be able to do this but read there are issues and that this ROM disables rooting?

Is there a way to do this as the threads in the flashrec bit seem to show bricked devices that get stuck in reboot loops!!

I have so far downloaded three zips and can use Terminal. I have the ADB folder, the 1.1 recovery image folder and the 2.9 hero custom rom core folder.

Any help for the n00b here would be greatly appreciated!!! :)

I just really wana get rid of all the excess baggage like Stocks etc

[Guest brettlzz]

Hi.

I am new to this site and Android. I got my HTC Hero (which I assume is stock and carrier unlocked as O2 don't carry this device) - White on O2 via buymobilephones.net and have upgraded to the latest build via the HTC website 2.73.405.5 146733 CL#61267

I would like to put on this custom ROM.

So far I have tried the following - installing the patched recovery ROM via Terminal on a Mac. I got into the bootloader but it wouldn't let me do it giving me this: downloading 'boot.img'... FAILED (remote: not allow)"

I read that with flashrec I might be able to do this but read there are issues and that this ROM disables rooting?

Is there a way to do this as the threads in the flashrec bit seem to show bricked devices that get stuck in reboot loops!!

I have so far downloaded three zips and can use Terminal. I have the ADB folder, the 1.1 recovery image folder and the 2.9 hero custom rom core folder.

Any help for the n00b here would be greatly appreciated!!! :)

I just really wana get rid of all the excess baggage like Stocks etc

hey mate.. there is an easy way to root the htc hero an load a custom rom.. follow this link for rooting

http://theunlockr.com/2009/08/27/how-to-ro...o-in-one-click/

an this link for installing modacos rom once u have rooted the device..

http://theunlockr.com/2009/08/27/how-to-lo...-your-htc-hero/

hope this helps.... :D

[Guest iNasar]

Hi paul. great work with the MCR. truly a wonderful ROM. However, is it just me or is there someone else ehre who thinks that 2.9 is running considerably slower than 2.8?

[Guest Phanes]

Hello Gentleman,

me as a total n00b (coming from S60) in Android, would like to say thank you Paul for your work you´ve done.

My experiences with 2.9 are that I do feel that the latest version has a slightly bigger lack of reaction time than the 2.7 version. 2.7 felt smoother and snappier.

I would like to ask the Pro´s in the Forum to maybe generate a easy to understand virtual "hand out" what exactly the steps are from A-Z.

E.g. I tried the "The Unlockr" way, but it did not worked for me. (to root) After a search on the web I found Instant Root as a very easy way to root. (hope I did not wrote something wrong, concerning connections and agreements and "who promotes who")

It is extremely hard to follow you guys when you discuss things like ext3, the swaper thing and apps2sd etc. etc. If there is somebody with fundamental knowledge I would appreciate a short notice for question/answer chat. Thank you!

P.S.: If there is anybody who already disassembled a Hero please give me a hint. I have disassembled my Hero already completely and put it back together (working without any problems), but I couldn´t figure out how the digitizer is mounted to the front cover.

Edited November 10, 2009 by Phanes

[Guest ndall]

I have updated from 2.6 to 2.9. I'm not sure I've particularly noticed a speed increase - if anything there's slightly more delay. But I suppose this can be quite subjective so if that's not the general experience I'm quite happy to accept that I could be imagining things!

My main (noob) question is about something else. After updating to 2.9 the available space was down to 63 MB. Not sure from exactly what but I see that this is to be expected. What is confusing is that after installing 3 more apps I'm down to 59 MB. Is this normal? I partitioned my SD card when I installed my first custom rom (2.1 I think) so from my basic understanding I would have expected installing apps to make little difference. Do I need to check that A2SD is working? Is there a way I can do this? Or is there something I'm missing?

Thanks for all the fantastic work.

Edited November 10, 2009 by ndall

[Guest IZIIZI]

I have updated from 2.6 to 2.9. I'm not sure I've particularly noticed a speed increase - if anything there's slightly more delay. But I suppose this can be quite subjective so if that's not the general experience I'm quite happy to accept that I could be imagining things!

My main (noob) question is about something else. After updating to 2.9 the available space was down to 63 MB. Not sure from exactly what but I see that this is to be expected. What is confusing is that after installing 3 more apps I'm down to 59 MB. Is this normal? I partitioned my SD card when I installed my first custom rom (2.1 I think) so from my basic understanding I would have expected installing apps to make little difference. Do I need to check that A2SD is working? Is there a way I can do this? Or is there something I'm missing?

Thanks for all the fantastic work.

i have the same problem, only 50mb free. read this: http://android.modaco.com/content/htc-hero...sd-not-working/

[Guest Igniztion]

After updating to MoDaCO 2.9 Core without any add-on packs I have encountered a fairly annoying issue.

Every now and then, about every other day, the system crashes and leaves me with no other option than to reboot the device. I haven't been able to have the logger running when the issue starts happening, but here is the log output from when I press Force close and the error pops up again. PID 1928 is the system process.

11-11 00:34:02.576: ERROR/AndroidRuntime(1928): Uncaught handler: thread main exiting due to uncaught exception

11-11 00:34:02.596: ERROR/AndroidRuntime(1928): java.lang.RuntimeException: Unable to get provider android.content.SyncProvider: java.lang.IllegalStateException: not initialized

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installProvider(ActivityThread.java:3857)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installContentProviders(ActivityThread.java:3659)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3618)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.access$2500(ActivityThread.java:112)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1729)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.os.Handler.dispatchMessage(Handler.java:99)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.os.Looper.loop(Looper.java:123)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.main(ActivityThread.java:3948)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at java.lang.reflect.Method.invokeNative(Native Method)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at java.lang.reflect.Method.invoke(Method.java:521)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at dalvik.system.NativeStart.main(Native Method)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928): Caused by: java.lang.IllegalStateException: not initialized

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.SyncStorageEngine.getSingleton(SyncStorageEngine.java:138)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.SyncProvider.onCreate(SyncProvider.java:21)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.ContentProvider.attachInfo(ContentProvider.java:607)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installProvider(ActivityThread.java:3854)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 ... 12 more

The trace above is usually followed by a lot of errors reporting "Failed to find provider info for <whatever application that crashes>" Example:

11-11 00:35:51.826: ERROR/ActivityThread(1972): Failed to find provider info for com.htc.launcher.setting.LauncherSettingProvider

11-11 00:35:51.826: ERROR/SettingUtil(1972): loadSettings(), cursor == null, content provider is not exist

Here's a trace for the system_process process:

11-11 00:35:50.496: ERROR/SurfaceFlinger(138): not enough memory for layer bitmap size=299008

11-11 00:35:50.506: ERROR/SurfaceFlinger(138): resizing buffer 0 to (320,232) failed [fffffff4] Unknown error: -12

11-11 00:35:50.686: ERROR/ViewRoot(138): OutOfResourcesException locking surface

11-11 00:35:50.686: ERROR/ViewRoot(138): android.view.Surface$OutOfResourcesException

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.Surface.lockCanvasNative(Native Method)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.Surface.lockCanvas(Surface.java:196)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.draw(ViewRoot.java:1195)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.performTraversals(ViewRoot.java:1045)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.handleMessage(ViewRoot.java:1504)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.os.Handler.dispatchMessage(Handler.java:99)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.os.Looper.loop(Looper.java:123)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1153)

11-11 00:35:50.746: ERROR/SurfaceComposerClient(138): surface (id=12, identity=221) is invalid, err=-12 (Out of memory)

11-11 00:35:50.906: ERROR/SurfaceFlinger(138): not enough memory for layer bitmap size=585728

11-11 00:35:50.906: ERROR/SurfaceFlinger(138): createNormalSurfaceLocked() failed (Out of memory)

It might be a memory leak somewhere since it reports out of memory. I've uninstalled all applications that I've installed after upgrading, but it hasn't fixed the issue. Anyone experiencing this issue or have some thought on what it might be?

[Guest iNasar]

After updating to MoDaCO 2.9 Core without any add-on packs I have encountered a fairly annoying issue.

Every now and then, about every other day, the system crashes and leaves me with no other option than to reboot the device. I haven't been able to have the logger running when the issue starts happening, but here is the log output from when I press Force close and the error pops up again. PID 1928 is the system process.

11-11 00:34:02.576: ERROR/AndroidRuntime(1928): Uncaught handler: thread main exiting due to uncaught exception

11-11 00:34:02.596: ERROR/AndroidRuntime(1928): java.lang.RuntimeException: Unable to get provider android.content.SyncProvider: java.lang.IllegalStateException: not initialized

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installProvider(ActivityThread.java:3857)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installContentProviders(ActivityThread.java:3659)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3618)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.access$2500(ActivityThread.java:112)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1729)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.os.Handler.dispatchMessage(Handler.java:99)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.os.Looper.loop(Looper.java:123)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.main(ActivityThread.java:3948)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at java.lang.reflect.Method.invokeNative(Native Method)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at java.lang.reflect.Method.invoke(Method.java:521)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at dalvik.system.NativeStart.main(Native Method)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928): Caused by: java.lang.IllegalStateException: not initialized

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.SyncStorageEngine.getSingleton(SyncStorageEngine.java:138)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.SyncProvider.onCreate(SyncProvider.java:21)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.content.ContentProvider.attachInfo(ContentProvider.java:607)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 at android.app.ActivityThread.installProvider(ActivityThread.java:3854)

11-11 00:34:02.596: ERROR/AndroidRuntime(1928):	 ... 12 more

The trace above is usually followed by a lot of errors reporting "Failed to find provider info for <whatever application that crashes>" Example:

11-11 00:35:51.826: ERROR/ActivityThread(1972): Failed to find provider info for com.htc.launcher.setting.LauncherSettingProvider

11-11 00:35:51.826: ERROR/SettingUtil(1972): loadSettings(), cursor == null, content provider is not exist

Here's a trace for the system_process process:

11-11 00:35:50.496: ERROR/SurfaceFlinger(138): not enough memory for layer bitmap size=299008

11-11 00:35:50.506: ERROR/SurfaceFlinger(138): resizing buffer 0 to (320,232) failed [fffffff4] Unknown error: -12

11-11 00:35:50.686: ERROR/ViewRoot(138): OutOfResourcesException locking surface

11-11 00:35:50.686: ERROR/ViewRoot(138): android.view.Surface$OutOfResourcesException

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.Surface.lockCanvasNative(Native Method)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.Surface.lockCanvas(Surface.java:196)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.draw(ViewRoot.java:1195)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.performTraversals(ViewRoot.java:1045)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.view.ViewRoot.handleMessage(ViewRoot.java:1504)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.os.Handler.dispatchMessage(Handler.java:99)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at android.os.Looper.loop(Looper.java:123)

11-11 00:35:50.686: ERROR/ViewRoot(138):	 at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1153)

11-11 00:35:50.746: ERROR/SurfaceComposerClient(138): surface (id=12, identity=221) is invalid, err=-12 (Out of memory)

11-11 00:35:50.906: ERROR/SurfaceFlinger(138): not enough memory for layer bitmap size=585728

11-11 00:35:50.906: ERROR/SurfaceFlinger(138): createNormalSurfaceLocked() failed (Out of memory)

It might be a memory leak somewhere since it reports out of memory. I've uninstalled all applications that I've installed after upgrading, but it hasn't fixed the issue. Anyone experiencing this issue or have some thought on what it might be?

well i uninstalled MCR 2.9 and did a nandroid restore to MCT 2.8 and tek-1.7-kernel

i am happy to report that its breezy again :)

though i agree. there seemed to be a memory leak because the phone just felt drained. i have no proof that it was a memory leak and this is just conjecture but it felt like one. the phone was sluggish. apps crashing. and sometimes i had to click an icon two or even three times before the app would execute

hmmm. def warrants some investigation by those who are more tech saavy than me :D

[Guest khunjj]

well i uninstalled MCR 2.9 and did a nandroid restore to MCT 2.8 and tek-1.7-kernel

i am happy to report that its breezy again :D

though i agree. there seemed to be a memory leak because the phone just felt drained. i have no proof that it was a memory leak and this is just conjecture but it felt like one. the phone was sluggish. apps crashing. and sometimes i had to click an icon two or even three times before the app would execute

hmmm. def warrants some investigation by those who are more tech saavy than me :D

After using MCR 2.9 for few days, it seems MCR 2.8 could be better than MCR 2.9. Anyway, still with MCR 2.9 until there are more feedbacks to confirm this. Hope Paul can figure out and make excellent MCR 3.0 for us soon. :)

[Guest Keramidas]

After updating to MoDaCO 2.9 Core without any add-on packs I have encountered a fairly annoying issue.

(...)

11-11 00:34:02.576: ERROR/AndroidRuntime(1928): Uncaught handler: thread main exiting due to uncaught exception

   11-11 00:34:02.596: ERROR/AndroidRuntime(1928): java.lang.RuntimeException: Unable to get provider android.content.SyncProvider: java.lang.IllegalStateException: not initialized

   (...)

(...)

Hi,

I have had this issue several times in a row, over the course of 2 days, about 2 weeks ago. But it was with an older MoDaCo ROM, like 2.6 or 2.7 - can't remember exactly. The problem then went away by itself, and never reappeared since.

I suppose it might have been a temporary problem on the Google side, causing the underlying "google sync" process to go belly-up.

Anyhow, I'm pretty much certain that MoDaCo 2.9 has nothing to do with that problem. Do you use NewsRob ? These problems often happened during/after a heavy sync (~600 articles) with Google Reader...

Edited November 11, 2009 by Keramidas

[Guest Jochr]

Hello,

I have a problem with protected apps not showing in market. Two of them I have bought. This happenend about a week ago.

I run market enabler on my phone since I live in Norway and market is not yet available here.

I have tried all the tricks mentioned earlier in this thread but none of them did help.

Does anyone else have this problem and have managed to fix it?

Please help :)

PS: I'm running MoDaCo version 2.9

Edited November 11, 2009 by Jochr

[Guest anderneo]

I have a problem using 3g with version 2.9.

It keeps dropping out. Turing it to 2g only and then back to 3g fixes it..

Anyone has that problem?

[Guest Keramidas]

I have a problem using 3g with version 2.9.

It keeps dropping out. Turing it to 2g only and then back to 3g fixes it..

Anyone has that problem?

Which radio version do you have ?

[Guest mrfriedhoff]

this was my first root and it went well - everything works great but how do I install the enhancement pack and wavesecure the same way you do the rom? I want to add these on but dont want to mess up the root - thanks guys!

[Guest Keramidas]

this was my first root and it went well - everything works great but how do I install the enhancement pack and wavesecure the same way you do the rom? I want to add these on but dont want to mess up the root - thanks guys!

Yes, just install them the same way that you did for the base ROM pack. If you're scared you can always do a nandroid backup (in recovery mode) before installing the two zip's :)

[Guest kendon]

this was my first root and it went well - everything works great but how do I install the enhancement pack and wavesecure the same way you do the rom? I want to add these on but dont want to mess up the root - thanks guys!

yes

[Guest mrfriedhoff]

yes

awesome thanks for the quick response guys - I sort of figured that's how but I'm a pro at messing things up so just wanted to check first - thanks alot