[ROM] FLB-Mod 1 (Based on Android 2.1)

[Guest biron_w]

I just have first phone freeze on 5.1 ROM

I wa reading ebook thru FbReader when the phone just froze....

Need to pull the batery out and reboot

I've had a few freezes but i've had them with every rom i've installed. I think it's a general problem with getting 2.1 on the pulse.

[Guest Simon O]

Update on A2SD bug.

This only happens when dalvik-cache is moved to the SD card.

When this is done and the phone rebooted, Dalvik-VM is unable to find it's cache.

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@[email protected]@classes.dex': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@framework@[email protected]': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): Can't open dex cache '/data/dalvik-cache/system@framework@[email protected]': No such file or directory

06-28 01:32:26.671: ERROR/dalvikvm(1167): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:

/system/framework/com.huawei.android.launcher.jar:/system/framework/widget_multimedia.jar:/system/framework/widget_info.jar'

06-28 01:32:26.671: WARN/dalvikvm(1167): JNI_CreateJavaVM failed

06-28 01:32:26.671: ERROR/AndroidRuntime(1167): JNI_CreateJavaVM failed[/code]


I should mention that these errors do not happen when Dalvik is left on the device so it's clearly an issue with a2sd. I'm not sure why it's happening but perhaps the ext partition is not being mounted before dalvik-vm wants to access it's cache. I could be wrong though.


I had a look at the a2sd code and it seems to be trying to read the wrong partitions for system and data (at least it looks that way). But, again, I could be wrong.


I have reported this over at XDA but the guy that writes this a2sd only works with HTC devices so cannot offer too much help for us. 


I want to try and fix this because I have been experiencing random slowness, force close (not all the time) and slow booting when dalvik cache is moved to the ext partition on the SD.

Edited June 28, 2010 by flibblesan

[Guest tuxuy]

I just have first phone freeze on 5.1 ROM

I wa reading ebook thru FbReader when the phone just froze....

Need to pull the batery out and reboot

Same problem, same "solution", using facebook for android..

[Guest brack]

My area network supports 2g the best, so I select an option "Use only 2G" or something like this in networks menu, but this option keeps unselecting by itself every now and then, whenever I go to airplane mode or reboot the phone, I have to set this option again, otherwise I have no network connection. My question - is there any way to make this option default?

[Guest Totyasrác]

Just wondering... Our main issue (after a2sd+ is made to a working level I guess, at least now we have enough place to install programs to) is the extremely low amount of RAM. At the moment if I check this (via menu/settings/apps/running_apps) I can see that there's 8.3MBs, and "other" 17MBs. Now if I want to start anything that don't fit in there something has to be killed. This results in performance slowdown, and also when trying to go back to whatever I used before (like Home or browser after receiving a call) it takes a while (sometimes even have to start gtalk or anything again).

Now the root of the problem (I guess) is that some running processes "eat up" the memory available -> isn't there a way to create a ROM with the least necessary processes running by default? I mean then we might end up having 20 or more MBs of RAM available until any app is started by me (and also after quitting that app). If it takes not using live wallpapers / weather widget it's fine with me (I think many replies will offend my point on this :lol:) but there must be a way for 2.1 to work better on our phones.

It would be much easier to buy any other Android phone (either a used Hero) to fix this issue but then there's no challenge :D I mean 1.5 was pretty nice (at least MCRs were doing the job) but with 2.1 we are just not there yet...

So isn't there any system (or system initiated) process that could be taken out painlessly?

Again: just thinkin' about that today :D

[Guest dodge-167]

Flb, how to update ADW to a new vesion???

[Guest introkun]

We flash this rom to Huawei u8230. Wireless not working, camera's autofocus not working too. Is it possible to adapt Hungary fix for Huawei u8230?

[Guest goce.nakov]

Flb, how to update ADW to a new vesion???

Download ADW on your PC

Rename it "Launcher.apk"

Replace Launcher.apk with the new one in system/app

Done

[Guest Simon O]

Flb, how to update ADW to a new vesion???

Download the latest ADW system version and push to the phone. I'll be producing my own updates for this just as soon as I can figure out how to compile it.

Download ADW on your PC

Rename it "Launcher.apk"

Replace Launcher.apk with the new one in system/app

Done

No no no no no. Bad :lol:

That will replace the system version of ADW with the non-system version. To replace the system version you can download it from this website:

http://www.jbthemes.com/dr_cloverdale/

They are flashable archives designed for CyanogenMod roms. You need to extract the apk from the file, rename to Launcher.apk and push to /system/app

Edited June 28, 2010 by flibblesan

[Guest goce.nakov]

Download the latest ADW system version and push to the phone. I'll be producing my own updates for this just as soon as I can figure out how to compile it.

No no no no no. Bad :lol:

That will replace the system version of ADW with the non-system version. To replace the system version you can download it from this website:

http://www.jbthemes.com/dr_cloverdale/

They are flashable archives designed for CyanogenMod roms. You need to extract the apk from the file, rename to Launcher.apk and push to /system/app

Then still no 8.9 ADW :D

[Guest Simon O]

Then still no 8.9 ADW :lol:

I know. Should be done soon I hope. This is one reason I want to compile it myself.

[Guest goce.nakov]

I know. Should be done soon I hope. This is one reason I want to compile it myself.

We need the MDPI version right?

Not HDPI..... :lol:

[Guest Simon O]

We need the MDPI version right?

Not HDPI..... :lol:

Yep, MDPI

[Guest dobre]

Why in new beta 5.1 rom i can't zoom desktops (to see all my desktops)?

[Guest Azurren]

Why in new beta 5.1 rom i can't zoom desktops (to see all my desktops)?

Because it uses adw launcher not launcher pro. If you want to use launcher pro you would have to flash the patch zip file provided :lol:

[Guest sreeramu]

....

Edited June 28, 2010 by sreeramu

[Guest Richard van Nieuwenhuizen]

Why in new beta 5.1 rom i can't zoom desktops (to see all my desktops)?

You can.

You'll have to press and hold the dots, that represent the number of desktops to the left or right, for a second or so.

Edited June 28, 2010 by Richard van Nieuwenhuizen

[Guest Simon O]

You can.

You'll have to press and hold the dots, that represent the number of desktops to the left or right, for a second or so.

Menu > ADW Settings > System Preferences > Home Button Binding > Show Previews

[Guest robot1000]

I'm having some issues flashing LauncherPro in recovery. I'm reciving the message: "Can't open /sdcard/launcherpro_0.6.3.zip (bad)"

I'm installing it over ADW Launcher (which I didn't like) which I installed yesterday with the 5.1 beta

Anyone know what would be causing it?

[Guest Simon O]

I'm having some issues flashing LauncherPro in recovery. I'm reciving the message: "Can't open /sdcard/launcherpro_0.6.3.zip (bad)"

I'm installing it over ADW Launcher (which I didn't like) which I installed yesterday with the 5.1 beta

Anyone know what would be causing it?

Might be a problem with your SD card or the file is corrupted. Try downloading again and if that doesn't work then format the SD card.

[Guest robot1000]

Might be a problem with your SD card or the file is corrupted. Try downloading again and if that doesn't work then format the SD card.

I just redownloaded and tried flashing it and the same message appears. I tried reinstalling Launcherpro, to check whether it was an SD Card issue, but that worked fine.

[Guest mr.a]

One quick question to flibblesan and the rest of the user

of this rom.

Does bluetooth file sending/receiving work for anyone?

And how do you get it to work?

I am in beta 5.1 and have installed 'bluetooth file transfer'

But it still doesn't work. Any help would be greatly appreciated :lol:

[Guest rikkiej]

Hey Fibblesan,

Would just like to point out that this tread is now the most viewed tread on the pulse forum, that's pretty cool! :lol:

[Guest goce.nakov]

Someone pls which is using this ROM can upload "local.prop" file, I deleted buy accident :lol:

[Guest Simon O]

Someone pls which is using this ROM can upload "local.prop" file, I deleted buy accident :lol:

You should be able to extract it from the rom