Jump to content

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


Recommended Posts

Guest Simon O
Posted
Either way, flash or push for me results in version 0.8.7

Another thing - can you publish changelog here as well? otherwise I have to go to the market every time to see it.

From http://twitter.com/Dr_Cloverdale/status/16986484767

"ADW Launcher 8.8 will read 8.7 in settings. @anderwebs forgot to change that. I assure you that it was done from the most recent source."

ADW changelog will always be at http://jbthemes.com/anderweb/

Guest Simon O
Posted
The author of LPro has removed that setting to be default, you have to set it in the settings. But it's possible, that the launcherpro setting makes it really unkillable, which is bad. The app_adj tweak just makes it harder to kill, but it will go if necessary.

It was removed for two reasons. First it caused a lot of force closes for users of some devices. Secondly Google really really do not like non-system apps being made system persistent.

The app_adj tweak basically tweaks Androids built-in task killer to ensure the current launcher is always in memory and only unloaded at a very last resort. It's not ideal behaviour and not really how Android should work.

As it's far easier to uncheck a setting in the launcher than edit and push local.prop files, I made the decision to remove the manual tweak. I can honestly say I haven't seen any difference since removing it and enabling the setting inside ADW.

Guest Spooke
Posted

Just wanting to check, I'm on 2.1 R7 Modaco, so can I just wipe etc. flash rom??

Guest bounty123
Posted (edited)
The app_adj tweak basically tweaks Androids built-in task killer to ensure the current launcher is always in memory and only unloaded at a very last resort. It's not ideal behaviour and not really how Android should work.

I think that is exactly how android should work - keeping the launcher in memory as long as it is possible while not affecting the stability of other programs, because the launcher works basically as a task manager, it is used most of the time. I agree, that it's more convenient to set it inside a program setting. But i'm not sure if you reach the same result. With app_adj you set the priority a bit higher, which is not a real 'always in memory' setting, what could cause problems. If the launchers make themself unkillable by the system, that might not be good.

Anyway it's like 20 seconds to enter or disable the tweak in a terminal, so it should not be a big issue for anyone.

Edited by bounty123
Guest Spooke
Posted

Just flashed this rom, all was well until I got passed the setup screen where it rebooted itself, back to 1.5 for me!

Guest brack
Posted
It was removed for two reasons. First it caused a lot of force closes for users of some devices. Secondly Google really really do not like non-system apps being made system persistent.

The app_adj tweak basically tweaks Androids built-in task killer to ensure the current launcher is always in memory and only unloaded at a very last resort. It's not ideal behaviour and not really how Android should work.

As it's far easier to uncheck a setting in the launcher than edit and push local.prop files, I made the decision to remove the manual tweak. I can honestly say I haven't seen any difference since removing it and enabling the setting inside ADW.

Yesterday I mentioned that I would apply adj tweak and then report the result, so, I didn't apply the tweak but just removed autokiller. Everything is faster now and I don't see delays in loading adw as well as there are no unloads of adw. I didn't apply any tweaks though.

Guest bounty123
Posted
Yesterday I mentioned that I would apply adj tweak and then report the result, so, I didn't apply the tweak but just removed autokiller. Everything is faster now and I don't see delays in loading adw as well as there are no unloads of adw. I didn't apply any tweaks though.

If you set adw to prevent unloading itself, than it's no surprise, that it doesn't. If you didn't, than it's strange :lol: You either use the tweak or the app's setting, both at the same time is redundant - the question is, which might be the better way to keep the home app longer in memory. If the app's way makes it a system app and prevents the system from killing it, than it is not the right way and the tweak might be better.

Guest Stoned Rider
Posted

Hi guys...

I've notice some problems with last update...

Phone keeps restarting several times on day and beautiful widgets home weather icon is not working (last 3 versions).

Also, battery life is shorter..

Everything else is pretty good... Speed is fine...

Phone is on 2.1 update and before flashing last update, full wipe was preformed.

Guest tgomas
Posted (edited)

Couple of questions:

I installed the latest beta 5 and added all my apps. After doing this I downloaded the ADW update and flashed the zip like one flashes a rom, I then flashed the Espresso Black firmware and made some build.prop tweaks to make the clock visible. All seems to be running okay, did I do this right? (May I have slowed down my phone?)

Thanks

BTW, This rom with black notification bar, fancy widget and adw launcher looks amazing!

Edited by tgomas
Guest Simon O
Posted
Couple of questions:

I installed the latest beta 5 and added all my apps. After doing this I downloaded the ADW update and flashed the zip like one flashes a rom, I then flashed the Espresso Black firmware and made some build.prop tweaks to make the clock visible. All seems to be running okay, did I do this right? (May I have slowed down my phone?)

Thanks

BTW, This rom with black notification bar, fancy widget and adw launcher looks amazing!

You have done it right and won't have slowed the phone down :lol:

Guest Gyurci
Posted

you're welcome :lol:

Thank you for the writing :D
Guest Fusion0306
Posted (edited)

Maybe a little off topic, but what does "ro.config.hw_isCustomize=false" in build.prop stand for? What does it change?

And how about "ro.config.BlackButton=true"?

EDIT: mine was "ro.config.hw_isCustomize=true" (vanilla-ish rom) changed it to "=false" and it changed my settings menu background color to black

Edited by Fusion0306
Guest Simon O
Posted
Maybe a little off topic, but what does "ro.config.hw_isCustomize=false" in build.prop stand for? What does it change?

And how about "ro.config.BlackButton=true"?

EDIT: mine was "ro.config.hw_isCustomize=true" (vanilla-ish rom) changed it to "=false" and it changed my settings menu background color to black

ro.config.hw_isCustomize turns the Huawei framework customizations on or off. So if it's enabled and you have vanilla look then the settings menu will be white background. With it switched off it'll be standard Android look.

Guest Fusion0306
Posted
ro.config.hw_isCustomize turns the Huawei framework customizations on or off. So if it's enabled and you have vanilla look then the settings menu will be white background. With it switched off it'll be standard Android look.

Thanks :lol:

Guest llaszlo
Posted (edited)

I use your's ROM r5.1 It's great. :lol: Thanks. :D

But I try install and set the sshd. sshd howto

but not working. If you can do install and setting this, please make a flashing.zip for me.

Thanks.

Edited by llaszlo
Guest tuxuy
Posted

Awesome job dude! version 5.1 is your best work far away! Thanks!

Guest demetr1os
Posted

I found some beautiful themes for the espresso. can I install it in vanilla beta 5.1??? through recovery...

Guest Androidboy
Posted
:lol:

Formatting SYSTEM:...

Copying files...

E: Can't symlink /system/xbin/[

E:Failure at line 13: symlink busybox SYSTEM:xbin/[

Installation aborted.

Installed the 2.1 and all went smoothly except the phone does not recognise the sd card, although my pc recognises it. Any idea how to fix this. I did the apps2sd option and partition sd as instructed. Thanks for any help.

Guest Simon O
Posted

Amazing how my ROM is travelling the world! Today I see that the guys over at HiAPK have been following the progress of FLB-ROM and have been making their own versions with Chinese language support. I'm pretty amazed this is happening.

感谢您对我的工作的客气话。我希望大家喜欢用这种 ROM。如果您有问题,请写在这个论坛给我。谢谢。

Wish I could understand Chinese without having to use Google Translate.

So if any of the guys here are Chinese and want FLB-ROM with better Chinese support head on over to HiAPK. Just excuse the rather dodgy copy of Rootexplorer they are so keen to add to my ROM :lol:

Guest Simon O
Posted
Installed the 2.1 and all went smoothly except the phone does not recognise the sd card, although my pc recognises it. Any idea how to fix this. I did the apps2sd option and partition sd as instructed. Thanks for any help.

Backup your SD card to your PC then partition it using recovery. That should work.

Guest Simon O
Posted

Just a quick request from me to all of you. Anybody here good at making custom boot screens? I've been trying to make one myself but I'm utterly rubbish.

Reward would be exposure in all future editions of FLB-MOD :lol:

Guest Fusion0306
Posted
Just a quick request from me to all of you. Anybody here good at making custom boot screens? I've been trying to make one myself but I'm utterly rubbish.

Reward would be exposure in all future editions of FLB-MOD :lol:

Sure, no problem! :D What would be the theme?

refferences (lol) : Boot animations

Guest Totyasrác
Posted
Amazing how my ROM is travelling the world!

No wonder - incredible ROM with awesome support!

Keep it up, mate, and cheers :lol:

Guest VitaminCBU1
Posted

I love your Rom, espacially the vanilla Style :lol: Very good work !

But i noticed that the version 5 is a bit slower then the version 3, or not ?!

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.