[OLED+TFT] 09/Feb r12: MoDaCo Custom Froyo ROM download + Online Kitchen

[Guest abc_123_]

I have loaded Alpha 3 onto my Orange San Francisco, and was really impressed with it - great work. However, I have one problem - the ZTE dialer crashes whenever I attempt to manually dial a number.

I can dial successfully using a saved contact, but if I type in a number and press "Call", the dialer crashes with the following error message:

"The process android.process.acore has stopped unexpectedly"

I tried installing a 3rd party dialer (Dialer One) and was able to dial successfully using that.

This is the log output from the phone when it crashes:

12-24 02:50:30.418: ERROR/ViewRoot exit(3053): Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@3127ee50

12-24 02:50:30.442: DEBUG/PowerManagerService(193): UnPartial wakeLock reactivate ,flags=0x6 tag=StayOnWhilePluggedIn Screen Dim

12-24 02:50:30.442: DEBUG/PowerManagerService(193): UnPartial wakeLock reactivate ,flags=0x6 tag=StayOnWhilePluggedIn Screen Dim

12-24 02:50:30.442: DEBUG/PowerManagerService(193): setTimeoutLocked now=9962327 nextState=3 when=9968327

12-24 02:50:30.442: WARN/WindowManager(193): waitForLastKey: mFinished=true, mLastWin=null

12-24 02:50:30.442: DEBUG/PowerManagerService(193): setTimeoutLocked now=9962328 nextState=3 when=9968328

12-24 02:50:30.448: ERROR/ViewRoot enter(3053): Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@3127ee50 touchevent action is 1 X= 277.3428 Y=771.12787

12-24 02:50:30.448: ERROR/ViewRoot exit(3053): Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@3127ee50

12-24 02:50:30.448: WARN/dalvikvm(3053): threadid=1: thread exiting with uncaught exception (group=0x2aacc8a0)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): FATAL EXCEPTION: main

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): java.lang.NullPointerException

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at com.zte.smartdialer.DialerApp.getIpNumber(DialerApp.java:1960)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at com.zte.smartdialer.DialerApp.onClick(DialerApp.java:970)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.view.View.performClick(View.java:2408)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.view.View$PerformClick.run(View.java:8816)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.os.Handler.handleCallback(Handler.java:587)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.os.Handler.dispatchMessage(Handler.java:92)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.os.Looper.loop(Looper.java:123)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at android.app.ActivityThread.main(ActivityThread.java:4653)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at java.lang.reflect.Method.invokeNative(Native Method)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at java.lang.reflect.Method.invoke(Method.java:521)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:876)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:634)

12-24 02:50:30.448: ERROR/AndroidRuntime(3053): at dalvik.system.NativeStart.main(Native Method)

12-24 02:50:30.458: WARN/ActivityManager(193): Force finishing activity com.zte.smartdialer/.DialerApp

12-24 02:50:30.468: WARN/WindowManager(193): updateFocusedWindowLocked newFocus=Window{313965e0 com.zte.smartdialer/com.zte.smartdialer.DialerApp paused=true} mode=0 mCurrentFocus = Window{313965e0 com.zte.smartdialer/com.zte.smartdialer.DialerApp paused=true}

12-24 02:50:30.498: WARN/WindowManager(193): updateFocusedWindowLocked newFocus=Window{3149e6b0 Sorry! paused=false} mode=1 mCurrentFocus = Window{313965e0 com.zte.smartdialer/com.zte.smartdialer.DialerApp paused=true}

12-24 02:50:30.508: WARN/WindowManager(193): updateFocusedWindowLocked newFocus=Window{3149e6b0 Sorry! paused=false} mode=3 mCurrentFocus = Window{3149e6b0 Sorry! paused=false}

12-24 02:50:30.968: WARN/ActivityManager(193): Activity pause timeout for HistoryRecord{31473e78 com.zte.smartdialer/.DialerApp}

12-24 02:50:30.998: WARN/WindowManager(193): updateFocusedWindowLocked newFocus=Window{3149e6b0 Sorry! paused=false} mode=3 mCurrentFocus = Window{3149e6b0 Sorry! paused=false}

12-24 02:50:31.008: DEBUG/Launcher(292): onResume+

As mentioned above, I can use a 3rd party dialler OK, so not a critical problem, and the rest of the ROM seems to work really well for me. Thanks for all the good work.

[Guest mikey223]

Thanx works great except for the GPS sometimes gives my location wrong and I can never find my location through wifi which is slightly annoying!

[Guest Wilb]

Yeah its only a string in framework and my theme thread even had the stock theme but with location fixed. :-)

Thanks mate :-)

[Guest dneill2006]

Is the wifi sleep problem fixed in this rom?

And can the kitchen be used for both OLED/TFT devices?

Thanks :(

Edited December 24, 2010 by dneill2006

[Guest meinnit]

Is Menu to wake fixed?

[Guest gusthy]

Is Menu to wake fixed?

As it was explained in this forum very many times, this issue is hardware-related, so it cannot be fixed. All the "solutions" prevent phone from going to sleep properly, so drains battery fast.

[Guest Lord_Snake]

But Power to wake is the normal, not Menu...

[Guest dneill2006]

So installed this rom today and WOW!

Works very well, no more wifi sleep issue! :(

Tried the wifi hotspot and was getting about 6meg just from the HSDPA connectioin =D

Pure Awesome ;)

[Guest Junior Bear]

currently baking an alpha 4

decided to join up :(

am i right in 'deselecting' the stock froyo lockscreen. if i want the normal lockscreen back?

[Guest NightSt@lk3r]

By normal do you mean the Android slider lockscreen or the ZTE spyglass one?

[Guest Palmierini]

hi everyone

just bought a sapo a5 (Portugal) wich is a zte blade with a 5mp camera

does Paul alpha 3 works on both 3.2mp and 5mp camera ?

[Guest Junior Bear]

By normal do you mean the Android slider lockscreen or the ZTE spyglass one?

i dont want the spyglass one

[Guest NightSt@lk3r]

then you want the stock froyo lockscreen checked.

[Guest Junior Bear]

ok cheers,

which is the correct driver for windows vista with alpha 4?

[Guest NightSt@lk3r]

If you mean USB drivers, then http://support.zte.com.cn/support/news/New...?newsId=1000442

[Guest liamdunn]

Settings/wifi and networks /WLAN settings/press menu button/advanced/WLAN sleep policy/set to never

[Guest amranny]

Hi,

I trying to install using clockworkmode (rooted desire gsm lcd) and get

write_failed_error

failed to write /tmp/boot.img

status (7)

can someone help me with this.

Thanks

[Guest Victor von Zeppelin]

Hi,

I trying to install using clockworkmode (rooted desire gsm lcd) and get

write_failed_error

failed to write /tmp/boot.img

status (7)

can someone help me with this.

Thanks

Again- YOU ARE USING THE WRONG PHONE. I distinctly remember you asking a few pages back, and they said then that this isn't a desire rom. This is for the ZTE Blade, Go to the Desire forums if you want Desire Roms.

[Guest TheVirreVirren]

Just installed the alpha3-update-modacocustomrom-blade-kitchen-unsigned and have the following problem.

Getting the following messages again and again as soon as I start the phone:

- Sorry! The process com.google.process.gapps has stopped unexpectedly. Please try again.

- Sorry! The application Setup Wizard (process com.android.setupwizard) has stopped unexpectedly. Please try again.

Please help!

I'm experiencing this problem aswell, was there any solution?

As completly new to android (but quite competent with linux) I just want to thank all of you enthusiasts out there for the continuous development of ROMs! Open-source is indeed the future!

Take care

Victor

Edit:

Solution: use latest ClockworkMod Recovery! :(

Edited December 25, 2010 by TheVirreVirren

[Guest Jickelsen]

I'm suddenly having a weird issue where the wifi tethering isn't working. I'm not sure if it started when I tried activating it from the SwitchPro widget or if the Blade Wifi Fix from market did it, but I uninstalled the latter and it's still there (maybe I should uninstall Keep Wi-Fi keep alive even though I don't use it any longer). Basically, it either gives me an error when I try activating it, or reportedly activates but says the access point name (as in SSID) is the name (ZyXEL) of the network I usually connect to (at a friend's place). I don't know what happened to the SSID name I set earlier, and the settings screen is inaccessable (greyed out) in settings.

It also seems to conflict with regular wifi (activating one either doesn't work or cancels the other out). Anyone else have this issue? What seems really strange to me is that it overrode the SSID...

[Guest blackversion]

Just in case I didn't make it clear btw...

ALPHA ALPHA ALPHA ALPHA ALPHA ALPHA ALPHA! ;)

Make sure you Nandroid before flashing!

P

hey paul i have installed the rom but when i turn my phone on it stays on a modaco logo i really need help fast :(

[Guest AlphaVision]

I have a lot of problems with storage right now. I was wondering how can I make my phone use ext partition to install all the phone apps there. Is there a guide or something? I am using alpha3.

Thank you

[Guest curl66]

hey paul i have installed the rom but when i turn my phone on it stays on a modaco logo i really need help fast :(

wipe cache. if this doesnt help do a factory reset and flash again.

works for me.

[Guest curl66]

double post. sorry

Edited December 25, 2010 by curl66

[Guest cerberus03]

okay had alpha 4 for a while. working great as far as ive used it. few lags here and there but to be expected. only thing that annoys me is youtube videos wont play in any browser i use. and the youtube app tells me i have to be over 18 to watch some videos even when im signed in. annoyance........