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

[Guest Totyasrác]

A couple of people have reported issues with SMS not being received, but this is the same for almost every other 2.1 rom. I don't think I've ever seen it reported by a T-Mobile user.

Zsolabola suffers from the same issue (I think he has reported it at least once) and he's a T-Mobile (Hungary) subscriber...

(I think he mentioned me once that he hadn't experienced that with Paul's WIP ROM though. He's on holiday but upgraded to FLB v1.0 before so we'll see how it works for him wnen he gets back.)

[Guest Ellia]

Strange, does someone encountered same trouble ? (France, Bouygues Telecom, Huawei U8230)

Could you find "Goggles" too ? It is unavailable for me too.

No, I can't found Goggles in the market.

[Guest meinnit]

For those with the SMS issue, to eliminate the low memory theory I would recommend installing AutoKiller from the Market and setting to Moderate or Strict setting and see how it goes. Remember to also enable settings on boot so that settings are also applied when you reboot.

[Guest drossco]

Just installed. Unrooted stock swedish rom -> amon-ra -> full wipe -> SD partitioning -> flb-mod 1.0 flash -> a2sd cachesd (4gb a-data class6 card, 1gb to ext)------> FULL OF JOY. Everything worknig as expected.

Fast as hell, and I have lots of apps but lots of memory... thanks flibblesan. :angry:

What precise SD Partitioning did you do before upgrading to FLB 1.0 ? Data? EXT2? SWAP?

Thanks!

[Guest Samlock]

flibblesan, just wanted to say that you have made my phone useable again. I love this ROM! Perfect homescreen layout, built-in clock widget and brilliant menu system. Love it! Thank you!

[Guest Ellia]

For those with the SMS issue, to eliminate the low memory theory I would recommend installing AutoKiller from the Market and setting to Moderate or Strict setting and see how it goes. Remember to also enable settings on boot so that settings are also applied when you reboot.

Can you explain what this app do? Is this app able to differ between important and unimportant apps and kill the unimportant or what is the way how the Autokiller works?

[Guest biron_w]

Oh that one. Not seen it myself but it will almost certainly be caused by low memory. The phone will probably just panic and crash.

Well if you go back to t-mobile and I get them again then i'm hunting you down :angry:

[Guest meinnit]

Can you explain what this app do? Is this app able to differ between important and unimportant apps and kill the unimportant or what is the way how the Autokiller works?

It makes it very easy to tweak the Android memory management settings. You simply select a profile of your choice from a pre-defined set of profiles. Profiles are simply a threshold in MB when memory manager will start to kill processes.

It does differ between important processes to some extent.

I would suggest reading the technical details here:

http://andrs.w3pla.net/autokiller/details

Most useful points from that article:

In other words: You can say "if free memory goes below XXXX then kill some process with oom_adj greater then YYY; if free memory goes even more below than ZZZ then start to kill some processes with oom_adj greater than XYXY. and so on.."

So it's possible to define multiple memory criterias and matching processes which can be killed in these situations. Android seems to group running processes into 6 different categories (comments taken out of "ActivityManagerServer.java"):

FOREGROUND_APP:

// This is the process running the current foreground app. We'd really

// rather not kill it! Value set in system/rootdir/init.rc on startup.

VISIBLE_APP:

// This is a process only hosting activities that are visible to the

// user, so we'd prefer they don't disappear. Value set in

// system/rootdir/init.rc on startup.

SECONDARY_SERVER:

// This is a process holding a secondary server -- killing it will not

// have much of an impact as far as the user is concerned. Value set in

// system/rootdir/init.rc on startup.

HIDDEN_APP:

// This is a process only hosting activities that are not visible,

// so it can be killed without any disruption. Value set in

// system/rootdir/init.rc on startup.

CONTENT_PROVIDER:

// This is a process with a content provider that does not have any clients

// attached to it. If it did have any clients, its adjustment would be the

// one for the highest-priority of those processes.

EMPTY_APP:

// This is a process without anything currently running in it. Definitely

// the first to go! Value set in system/rootdir/init.rc on startup.

// This value is initalized in the constructor, careful when refering to

// this static variable externally.

These 6 categories are reflected by 6 memory limits which are configured for the lowmemorykiller in the kernel.

Fortunately, it is possible to configure the lowmemorykiller at runtime! :angry: (But only if you are root). The configuration is set in the file: "/sys/module/lowmemorykiller/parameters/minfree"

So if you want to see the current settings, you can do:

# cat /sys/module/lowmemorykiller/parameters/minfree This should produce output like this (or similiar): 1536,2048,4096,5120,5632,6144

These values are the 6 memory limits on which Anedroid starts to kill processes of one of the 6 categories above. Be careful, the units of these values are pages!! 1 page = 4 kilobyte.

So the example above says that Anddroid starts killing EMPTY_APP processes if available memory goes below 24MB (=6144*4/1024). And it starts to kill unused CONTENT_PROVIDERs if available memory goes below 22MB (=5632*4/1024).

So if you want to try if your Hero goes faster when fewer processes are running you can try to adjust these settings. For example if you practically do not want any empty processes you can set the corresponding value very high. For example, you can set the values like this:

# echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree

This example will tell Android to kill unused Content providers if less then 60MB is available and kill empty processes if available memory goes below 90MB.

All other processes will stay untouched! Do you see the advantage compared to process killers?

Edited July 14, 2010 by meinnit

[Guest petz20099]

Hi Flibblesan,

do you or anyone have the italian package for touchpal?

consider to insert HTC_IME from XDA in next release. What do you think?

Ciao

Petz :angry:

[Guest deadphill]

Sorry if this has been posted already. I did a search but couldnt see a definative answer.

Has the marketplace issue whereby you cant find google goggles amongst other apps been fixed in this rom?

Cheers

Phill

[Guest Simon O]

Sorry if this has been posted already. I did a search but couldnt see a definative answer.

Has the marketplace issue whereby you cant find google goggles amongst other apps been fixed in this rom?

Cheers

Phill

To a degree, yes. But Google Goggles still doesn't appear in the market.

[Guest gusthy]

Zsolabola suffers from the same issue (I think he has reported it at least once) and he's a T-Mobile (Hungary) subscriber...

(I think he mentioned me once that he hadn't experienced that with Paul's WIP ROM though. He's on holiday but upgraded to FLB v1.0 before so we'll see how it works for him wnen he gets back.)

+1, I am a tmobile user.

[Guest bounty123]

Zsolabola suffers from the same issue (I think he has reported it at least once) and he's a T-Mobile (Hungary) subscriber...

(I think he mentioned me once that he hadn't experienced that with Paul's WIP ROM though. He's on holiday but upgraded to FLB v1.0 before so we'll see how it works for him wnen he gets back.)

I'm a T Hungary user too, and experienced the SMS delay once with Paul's WIP rom. Haven't had the problem yet with FLB 1.0 though. But I had Paul's ROM for many weeks, FLB just since 1.0 came out.

[Guest flash2004]

Sorry if this has been posted already. I did a search but couldnt see a definative answer.

Has the marketplace issue whereby you cant find google goggles amongst other apps been fixed in this rom?

Cheers

Phill

Download google goggles from here and install it manually using either estrongs or astra

http://www.megaupload.com/?d=RU4V00E5

[Guest Richard van Nieuwenhuizen]

Just started ASTRO on my FLB v1.0 and it came back with "This Beta program will expire in 1 day." ;) :angry:

What's up with that flibblesan??!! :D

[Guest Simon O]

Just started ASTRO on my FLB v1.0 and it came back with "This Beta program will expire in 1 day." ;) :angry:

What's up with that flibblesan??!! :D

Update it via the market.

[Guest goce.nakov]

Update it via the market.

And have your ad's ..... :angry:

[Guest Richard van Nieuwenhuizen]

Update it via the market.

So simple that I didn't even think of that :angry:

[Guest Simon O]

And have your ad's ..... :D

which are very easy to remove :angry:

[Guest Simon O]

So simple that I didn't even think of that :angry:

Well truth is I didn't realise it was a time limited beta. So updating would resolve the issue, but give lovely ads. Ads which can easily be removed if you have apktool :D

[Guest darkdevil1]

For those who have a ''broken'' touchscreen, try clearing dalvik cache and repair ext2. Had this problem for the first time this morning and it fixed it for me.

[Guest Ellia]

It makes it very easy to tweak the Android memory management settings. You simply select a profile of your choice from a pre-defined set of profiles. Profiles are simply a threshold in MB when memory manager will start to kill processes.

It does differ between important processes to some extent.

I would suggest reading the technical details here:

http://andrs.w3pla.net/autokiller/details

Most useful points from that article:

At each start of Autokiller there comes the popup and the text is about that you must be root and so on. It's just an annoying popup and everything works or doesn't it have correct root access? It should work because we are using an Custom rooted ROM? Is there any way to check whether AutoKiller works properly or not?

[Guest Ellia]

double post

Edited July 14, 2010 by Ellia

[Guest Epic-Emodude]

Well truth is I didn't realise it was a time limited beta. So updating would resolve the issue, but give lovely ads. Ads which can easily be removed if you have apktool :angry:

you can change a file that blocks pretty much all adds. If I could remember which file it was I would upload the one im using.

[Guest meinnit]

At each start of Autokiller there comes the popup and the text is about that you must be root and so on. It's just an annoying popup and everything works or doesn't it have correct root access? It should work because we are using an Custom rooted ROM? Is there any way to check whether AutoKiller works properly or not?

Is there an Always Allow option?