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

[Guest everal]

Hello,

iam a newbie at android, after many many hours on the last day i have the following items tested on my pulse with uk 2.1 update before

i flashed the version

FLB-Mod v1.5 with ADW.Launcher 1.1.3

Download: flbmod_v1.5adw.zip best performance (63.4 MB) latest MD5 53D057F68AE08B292F375FF1E4D3ECCA

-> the problem was the process "android.process.acore" was broken at startup, no chance to see the android desktop.

every second the error message display

now i flash the

FLB-Mod v1.4.1

Download: flbmod_v1.4.1.zip (63.4 MB) MD5 9C23A57C44B8BF5822ADCC7E7429EC3A

-> everything is ok, android desktop works...no android.process.acore error display on the screen...

question:

-------------

1. when v1.5 is not working with the above message, does v1.5 with the other launcher my be work ?

FLB-Mod v1.5 with LauncherPro 0.7.6.0

Download: flbmod_v1.5lp.zip (64.6 MB) latest MD5 E1F4EAE314814BDB1BDD4657197A6FFE

---------------

2. can i use the update to v1.5 from v1.41 and which launcher is integrated ?

FLB-Mod v1.4.1 - v1.5 update (no wipe)

Download: flbmod_v1.4.1-v1.5nowipe.zip (54.7 MB) MD5 060FC269B6AC7EC6EF78161BE8AC906B

---------------

3. outlook 2010 sync

update: fixed with spf for pc-suite

the t-mobile pc-suite from the 2.1 hu update found my pulse after the

SFP Fix (needed by some people):

Download: flbmod_v1.4.1sfp.zip (291 KB)

was installed

which other appz work for the pulse (think htc sync v2 or v3)

-> no device will be found (is at the moment not working...)

where i can find a working version for the pulse ???

very thanks

Edited September 5, 2010 by everal

[Guest dashmoment]

My phone have problem when i use flb 1.5.

Phone cause Phone would regular force close.

[Guest reinhard-gehlen]

@all: My first posting here (sorry for my very basic english).

I successfully installed the new FLB-MOD 1.5. Nice work, thanks !!

I have two questions:

(1) After customizing my phone with some additional apps, I selected at least a new ADW.launcher theme. I made a backup of the settings before (/sdcard/adw_settings.xml and /sdcard/adw_launcher.db). But when I try to go back to the original theme, the green wallpaper/background with the abreviation "FLB-MOD" isn´t restored. Where can I find this single graphic file for download ?

(2) I´am missing a function/an app, which allows to combine a special ringtone to a single phone number and/or a dedicated group of phone numbers. Now, I can only select one ringtone for all incomming calls.

Kind regards

Edited September 5, 2010 by reinhard-gehlen

[Guest takeshi85]

This program don't worked on this mod! This problem for me.

[Guest SaraJoy]

Hiya,

I installed FLB v1.5 a week or two ago, first time I've installed a custom ROM onto this second hand Pulse which had hardly been used, and I gathered was running the T-mobile stock Android 1.5.

I'm afraid to say I'm finding it a bit sluggish, and also that Launcher Pro keeps having trouble. I usually tell the error message to 'Wait' and for the most part that seems OK.

Is this normal? Does it usually (given the miserly amount of free RAM I expect) show a blank screen for some time before returning to the home screen after hitting the red end call button?

Unfortunately I think the sluggishness may be what will end up putting me off - unless I've done something wonky which I can do better if I install it again?

[Guest Simon O]

Sara you may find things running better if you replace LauncherPro with ADW.Launcher. There is a zip you can flash available on the first page.

[Guest SaraJoy]

Damn, and I installed the LP version because I'd read somewhere that it was snappier! This not the case? Sorry if these questions have been answered many a time before, I've had a good look :S

[Guest Daz555]

Damn, and I installed the LP version because I'd read somewhere that it was snappier! This not the case? Sorry if these questions have been answered many a time before, I've had a good look :S

If you don't want to stick with LP then just flash the ADW zip from recovery. Link on the first page in this thread.

[Guest Simon O]

Damn, and I installed the LP version because I'd read somewhere that it was snappier! This not the case? Sorry if these questions have been answered many a time before, I've had a good look :S

I find that LauncherPro is becoming bloated with all it's built-in widgets. This is taking up valuable memory. The other issue is LauncherPro is causing Android to launcher two system processes which, again, take up valuable memory. The best solution is to use ADW.Launcher which will cut down on the memory usage. It won't be perfect, and sometimes you may have to wait a second or two for the homescreen to come back, but this is the nature of Android 2.1 on the Pulse sadly.

[Guest SaraJoy]

OK no problem - ADW sounds like the way to go, then!

Quite a lot of stuff to read through when trying to mug up on what best to do :P

I'll go have some flashy fun (ooerr)...

..cheers duder, done now and it does indeed seem a little speedier :)

Edited September 5, 2010 by SaraJoy

[Guest niko1986]

OK no problem - ADW sounds like the way to go, then!

Quite a lot of stuff to read through when trying to mug up on what best to do :P

I'll go have some flashy fun (ooerr)...

..cheers duder, done now and it does indeed seem a little speedier :)

You can squeeze a touch more speed out of ADW if you go through all the settings and trim down anything snazzy like animations etc

[Guest twrock]

You may want to free more space (if you have at least class4 SD card) by typing the following command to the same place:

su (only if you exited Terminal Emulator, if not, you don't need to)

a2sd cachesd

That's all.

I'm wondering about the actual value of cache2sd. If cache is not using that internal memory, what will? Will it just sit there empty, doing nothing of value? Why not just let cache use that internal memory if I've got nothing else that will use it? What's the point of adding yet a little more "overhead" to the system (cache2sd) if I don't need to?

Maybe I'm just not seeing it, but after my latest install, I didn't bother with cache2sd. I've got all the programs I want loaded and still have 20+mb free. Is there some reason why that should be of concern? At what point should I really consider "needing" to move cache to sd?

I think the real issue with our phone is RAM, whether because there isn't enough to start with or whether there is some poor memory management going on or both.

[Guest Simon O]

cachesd only moves dalvik-cache to the SD card. All other caches are left on /data. The only advantage is speed.

[Guest twrock]

cachesd only moves dalvik-cache to the SD card. All other caches are left on /data. The only advantage is speed.

So is a class 4(+) sd card faster than the internal memory?

Oh, and I do have one other question, if you will, Fibblesan. I noticed in your vanilla frameworks update file that you replace Mms.apk and not just the framework-res.apk. Why is that? What's in the Mms.apk that needs to be different?

Thanks.

Edit: Correct that. I have one more question. Why can't I get an app to flash to /data/app from within the update I made. I copied the installed app off of my ext partition, and assumed I could just throw it into /data/app and have it install. Any pointers?

Edited September 6, 2010 by twrock

[Guest niko1986]

Oh, and I do have one other question, if you will, Fibblesan. I noticed in your vanilla frameworks update file that you replace Mms.apk and not just the framework-res.apk. Why is that? What's in the Mms.apk that needs to be different?

I think the MMS.apk is specially skinned because the framwork can't change the skinning of it .. or sommat like that :P

[Guest Simon O]

I think the MMS.apk is specially skinned because the framwork can't change the skinning of it .. or sommat like that :P

Yep, Mms.apk was skinned and looks bad with a vanilla framework.

[Guest Simon O]

So is a class 4(+) sd card faster than the internal memory?

Edit: Correct that. I have one more question. Why can't I get an app to flash to /data/app from within the update I made. I copied the installed app off of my ext partition, and assumed I could just throw it into /data/app and have it install. Any pointers?

Class 4/Class 6 is quicker than the phone flash.

Did you add "copy_dir PACKAGE:data DATA:" to the setup script?

[Guest twrock]

Class 4/Class 6 is quicker than the phone flash.

Wow, I did not know that. And that surprises me.

Did you add "copy_dir PACKAGE:data DATA:" to the setup script?

That would be a big "no". :P I was actually working off of trial and error and just repacked your vanilla framework update with the other files I wanted to add. When it worked with the /system files, I assumed it would be just that easy with the /data files. I guess I'm going to have to actually learn something today. :)

Thanks.

[Guest Simon O]

Wow, I did not know that. And that surprises me.

That would be a big "no". :P I was actually working off of trial and error and just repacked your vanilla framework update with the other files I wanted to add. When it worked with the /system files, I assumed it would be just that easy with the /data files. I guess I'm going to have to actually learn something today. :)

Thanks.

Have a look at the script I use for FLB-Mod and base it off that. Should give you some ideas.

[Guest SaraJoy]

You can squeeze a touch more speed out of ADW if you go through all the settings and trim down anything snazzy like animations etc

Cheers yup did that last night too :P

[Guest baotica]

I know that I may be boring, but will someone point me to the section of this forum that tells how to move cache (data/data, NOT dalvick) directory to the SD card, or at least what can be safely deleted in that directory.I fell down to 15 out of 80 MB, and I use A2SD correctly.

Second.If you do not install more than 2 widgets you will have enough memory free so your phone will not stutter and force close apps.Especially do not use widgets like fancy widget, beautiful home widget, my calendar and such.They eat your battery time, and bite to much of your lean memory.Do not use them, this phone has to little memory for those kind of active widgets.

Oh, and those widgets better be static (do not gather any kind of informations active like), if you do this you will always have between 25-35 MB.Enough that you will not have problems like SMS not coming through because phone kills sms app.

[Guest Simon O]

I know that I may be boring, but will someone point me to the section of this forum that tells how to move cache (data/data, NOT dalvick) directory to the SD card, or at least what can be safely deleted in that directory.I fell down to 15 out of 80 MB, and I use A2SD correctly.

There isn't any guide for moving all other caches. There is an app in the market called TA Utility that is suppose to be able to move all over caches to the SD but I've not tried it.

[Guest ogiogi]

I find that LauncherPro is becoming bloated with all it's built-in widgets. This is taking up valuable memory. The other issue is LauncherPro is causing Android to launcher two system processes which, again, take up valuable memory. The best solution is to use ADW.Launcher which will cut down on the memory usage. It won't be perfect, and sometimes you may have to wait a second or two for the homescreen to come back, but this is the nature of Android 2.1 on the Pulse sadly.

Yeap. LP is very customizable and has very nice HTC looking widgets but it's just not optimized for low RAM devices. ADW on the other hand runs very smooth on the Pulse and has a neat shortcut option with eliminates the need of BetterCut. And has themes support. So i just have both on my pulse and switch between them :P

[Guest baotica]

There isn't any guide for moving all other caches. There is an app in the market called TA Utility that is suppose to be able to move all over caches to the SD but I've not tried it.

Know that app, but it only moves only predefined apps cache, not all.Which is not really useful.Why can we not make a cache partition on SD card so entire data folder, which we then could increase to whatever we like.That would be something.This way it clogs up pretty darn fast.

It has to be a way to do this.Android being Linux and all.

[Guest Hakula]

ok one question... in flb 2.1 to use a2sd i just need to make a partiture trought recovery?