Jump to content

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


Recommended Posts

Guest Pakatus
Posted

Anyone can explain me how to set the stock launcher?

1 - From the Online Kitchen option...stucks with successive reboots @ first boot.

2 - From the Flibble's Framework added to online kitchen ...the same result.

So please...anyone give me a short "how" to set it please.

Guest Grisu112
Posted
Anyone can explain me how to set the stock launcher?

1 - From the Online Kitchen option...stucks with successive reboots @ first boot.

So please...anyone give me a short "how" to set it please.

I have the same problems as soon as the SIM card is inserted.

When i used the modacolockscreen it works :)

Guest paulsss
Posted

I'm currently experiencing the screen lock issue alot so I should be able to get a dmesg/logcat. I was wondering if there is some way to unload and load the touch screen driver once it does stop responding? lsmod insmod etc seem to behave a little strangely. Is it a kernel module or built in? Is there a way to kill zygote/restart just that part from adb?

Guest PeTiNgA
Posted (edited)
I'm currently experiencing the screen lock issue alot so I should be able to get a dmesg/logcat. I was wondering if there is some way to unload and load the touch screen driver once it does stop responding? lsmod insmod etc seem to behave a little strangely. Is it a kernel module or built in? Is there a way to kill zygote/restart just that part from adb?

Hi,

Do you have any of these applications installed: http://android.modaco.com/index.php?act=at...st&id=67161

This is what I have, and I'm getting freezes on lockscreen also.

Thanks in advance

Edited by PeTiNgA
Posted
Hi,

Do you have any of these applications installed: http://android.modaco.com/index.php?act=at...st&id=67161

This is what I have, and I'm getting freezes on lockscreen also.

Thanks in advance

Restore the stock rom and clear the cache/factory reset and see if you still get the problem.

I do, although the touch-screen works for a couple of minutes and then stops - even on Orange's froyo.

Posted

paul, any progress being made in alpha 4? its been a few days with no info of new features or fixed bugs.

Guest tronads
Posted
I'm currently experiencing the screen lock issue alot

I was experiencing this a lot on Alpha 3, one morning on my alarm clock...which made damn sure I got up, when I had to remove the bloody battery !

However since I installed Alpha 4, some 4 or 5 days ago, not one touchscreen lockup (so far).

Posted
I'm currently experiencing the screen lock issue alot so I should be able to get a dmesg/logcat. I was wondering if there is some way to unload and load the touch screen driver once it does stop responding? lsmod insmod etc seem to behave a little strangely. Is it a kernel module or built in? Is there a way to kill zygote/restart just that part from adb?

I couldn't agree more with paulsss here. It seems strange that more people aren't talking about this issue more. For me its the only major issue with moving to 2.2. Luckily I've only had it twice on Alpha4 so far but I'm sure it will become more frequent like it did with my previous 2.2 ROM.

Guest southpaw1
Posted (edited)

anybody advise me how to change the boot screen , would love to kick that 80`s throwback modaco fella in to touch , ideally would like to replace with this

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

found the boot screen images in "system/media/bootanimation" but not sure how to go about replacing with animated ones , anybody know please

will these commands and method from the link work with blade

adb shell mount /system

adb push C:\bootanimation.zip /system/media/

adb reboot

Edited by southpaw1
Guest paulsss
Posted

Also using astrids tasks i get the following error in logcat which prevens the filter lists from working. This also happens on stock orange but did work fine on the first froyo roms. Astrid tasks definitely works without a hitch on other phones, g1 (2.2 cyanogen mod), desire, x10, hero etc.

I/ActivityThread( 1716): exit process activity msg = 101

I/ActivityThread( 1716): enter process activity msg = 100

I/ActivityThread( 1716): exit process activity msg = 100

I/ActivityThread( 1716): enter process activity msg = 113

I/ActivityThread( 1716): exit process activity msg = 113

W/WindowManager(  204): updateFocusedWindowLocked newFocus=Window{312d5418 com.timsu.astrid/com.todoroo.astrid.activity.FilterListActivity paused=false} mode=3 mCurrentFocus = null

I/ActivityThread( 1716): enter process activity msg = 113

E/Parcel  ( 1716): Class not found when unmarshalling: com.todoroo.astrid.api.Filter, e: java.lang.ClassNotFoundException: com.todoroo.astrid.api.Filter

I/ActivityThread( 1716): exit process activity msg = 113

W/WindowManager(  204): updateFocusedWindowLocked newFocus=Window{312d5418 com.timsu.astrid/com.todoroo.astrid.activity.FilterListActivity paused=false} mode=2 mCurrentFocus = Window{312d5418 com.timsu.astrid/com.todoroo.astrid.activity.FilterListActivity paused=false}

W/WindowManager(  204): updateFocusedWindowLocked newFocus=Window{312d5418 com.timsu.astrid/com.todoroo.astrid.activity.FilterListActivity paused=false} mode=2 mCurrentFocus = Window{312d5418 com.timsu.astrid/com.todoroo.astrid.activity.FilterListActivity paused=false}

I/ActivityThread( 1716): enter process activity msg = 113

E/Parcel  ( 1716): Class not found when unmarshalling: com.todoroo.astrid.api.IntentFilter, e: java.lang.ClassNotFoundException: com.todoroo.astrid.api.IntentFilter

Posted

alpha 3 keeps reboot at boot screen?..alpha 2 was working properly now alpha 3 is not working??..i clear everything at clockrecovery mode..:)..can someone help me?? and have check the md5sum of file is same as at first post..

Guest jurrasstoil
Posted (edited)

Hey,

I'll be getting a SF (swiss TFT version) soon and after reading this and another forum for 4 days now i'm still not sure which rom to choose. Every rom seems to have some not so minor issues that really cut into the usability.

From what i've read the lockscreen freeze is the one issue that would keep me from installing this rom.

Does it really freeze or is it just that the touchscreen doesn't respond? If the latter then is there a way to unlock it via the buttons on the SF (like holding Home for 2s or something) and would it work normally after unlocking it via buttons when the lockscreen froze?

Thanks in advance.

Edited by jurrasstoil
Guest Frankish
Posted (edited)

That's a good idea actually. Maybe if Paul decompiles the android.policy.jar for the zte lockscreen and enables menu unlock we would see if it is a lockscreen issue or if it affects the whole unit...?

Using the stock lockscreen for at least 3 days now and no freezes on that though!

EDIT: Hmm actually i think menu unlock seems to be set in framework-res.apk bools.xml...

Edited by Frankish
Guest PeaNut_HU
Posted

I had no freezes with the new lockscreen neither with the stock froyo one. In alpha2 the "new" lockscreen was laggy, but on alpha3 and 4 i don't had this problem anymore, but now that i have adfree subscription i still chose the stock android lockscreen (alpha4), i like it much better, and still no freezes.

Posted
Wazzat?

silly me, I mean't oranges 2.1

Although I can't restore the stock roms, I get the error:

E:board does not support mtd utils.E:Failure at line 78

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted

for B05 or B08

Lucky I took a nandroid backup first.

Guest Arr Too
Posted

You could have answered that one with a quick search. Use ClockworkMod 2.5.0.9, not the latest one.

Posted

Can we change a dialer of MCR to flb-froyo-r3 dialer??..

i really like dialer of froyo beta one rather than this one//

Posted

any updates on alpha 4 prebake.

wanna switch to this rom buh i wanna know the main problems with it, can any one help me please?

Guest paulsss
Posted

just to clarify the lock screen problem, only the touch screen stops working, the hardware buttons work as normal, holding down power brings up the switch off menu but nothing can be selected due to no touch screen. In the logcat when the touch screen stops working no logcat messages are despatched for touch events any more (usually there are loads of touch events when you touch the screen)

Guest Gerson2k
Posted (edited)
anybody advise me how to change the boot screen , would love to kick that 80`s throwback modaco fella in to touch , ideally would like to replace with this

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

found the boot screen images in "system/media/bootanimation" but not sure how to go about replacing with animated ones , anybody know please

will these commands and method from the link work with blade

adb shell mount /system

adb push C:\bootanimation.zip /system/media/

adb reboot

You don't need to mount, just drop the zip file to where your adb.exe is and then

adb push bootanimation.zip /system/media/

alternatively you if you PC is windows based you can use Android commander which has a GUI interface.

Edited by Gerson2k
Guest southpaw1
Posted (edited)

thanks Gerson2k , will give it a go now , cheers mate

edit

cool , worked perfectly , many thanks

Edited by southpaw1
Posted

alpha3 _ wifi enabled but lost connection after gone to sleep or screen goes blank and after unlocking screen , im lost where we are with this

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.