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

[Guest brack]

Does anybody know what mms settings i should use and where do i fill in the setting? :)

I have Swedish Tre as operator.

Everything exept mms works very well for me and I really like this ROM.

For future reference of all who using Swedish operators - here is full info about apn setup for all Swedish operators: http://www.swedroid.se/wiki/index.php/APN-inst%C3%A4llningar

[Guest Totyasrác]

ok, After all troubles and tries, I'm back to 5.1beta1. I'm so happy with my phone now, everything is working and working fast. I tried 1.0 with all patches, to make it work on my device. Tried it with and without, LauncherPro but 1.0 is so slow, sometimes unusable for me, specially right after boot and wakeup. Will wait for different version or will try to build my own rom on vacation.

Pretty interesting... From beta3 I upgraded to beta5.1 but was soo slow I went for a different option (MCR WIP ROM). Then I loaded FLB v1.0 and am still extremely happy with it. The fastest custom 2.1 ROM ever on Pulse - no errors, no freezes, no slowdowns (at least for the amount of RAM we have of course...). There MUST have been something going wrong with your installation (unsuccessful wipe(s) for example?).

My roadmap was on my Pulse (U8220): T-Mobile official 2.1 (Hungarian, without localization) -> MCR -> FLB beta3 -> FLB beta5.1 > MCR (minimalistic baked a2sd+) -> FLB v1.0.

Never experienced touchscreen problems, all SMSs received, wifi/GPS/3G working every time.

[Guest brack]

Pretty interesting... From beta3 I upgraded to beta5.1 but was soo slow I went for a different option (MCR WIP ROM). Then I loaded FLB v1.0 and am still extremely happy with it. The fastest custom 2.1 ROM ever on Pulse - no errors, no freezes, no slowdowns (at least for the amount of RAM we have of course...). There MUST have been something going wrong with your installation (unsuccessful wipe(s) for example?).

My roadmap was on my Pulse (U8220): T-Mobile official 2.1 (Hungarian, without localization) -> MCR -> FLB beta3 -> FLB beta5.1 > MCR (minimalistic baked a2sd+) -> FLB v1.0.

Never experienced touchscreen problems, all SMSs received, wifi/GPS/3G working every time.

Yeah, I guess it works for you nicely, the new kernel with 1.0 was super fast but since I had problems with touchscreen and I had to apply all little patches recently put up here by flibblesan. After all it would take about 5sec. for ADW to start up. Whenever I would slide to unlock the phone, I would see 4-5sec of black screen. The LP wasnt any better. My road-map: Dec update, MCR 1.7, Official HU with CUSTOM_HU, Oscillation, 2.1 minimalistic, MCR WIP, FLB beta3, beta5, beta5.1, beta5.1update1, flb 1.0, timemachine, Official tre, timemachine, dec update, Official tre, timemachine, dec update, Official HU no CUSTOM_HU, flb 1.0, Official HU no CUSTOM_HU, beta5.1update1

You can see I was experimenting a lot, a lot of wipes are done etc, etc, etc. I just have no time anymore, Maybe will try new version when it comes.

Thank you flibblesan for the roms I'm convinced they are the best on this forum.

[Guest Ellia]

I think it was a mistake using the Tre kernel in the FLB 1.0 rom. I've replaced it with the t-mobile kernel and everything works as it did before with the advantage that touchscreen works for people that lost it. SMS receiving and sending still works.

I'll try and get an update uploaded in the new day or two.

How is it possible that the SMS bug is cleared with the old kernel from HU? I thought it was an issue triggered by the old kernel?

[Guest Simon O]

ok, After all troubles and tries, I'm back to 5.1beta1. I'm so happy with my phone now, everything is working and working fast. I tried 1.0 with all patches, to make it work on my device. Tried it with and without, LauncherPro but 1.0 is so slow, sometimes unusable for me, specially right after boot and wakeup. Will wait for different version or will try to build my own rom on vacation.

Sorry that you and others have been having problems. Version 1.0 of FLB-MOD is built upon the same base as the later beta versions. The main difference is the newer kernel from the Tre rom which I believe is causing the issues.

The reason I switched to the Tre kernel was in the belief that this resolved all issues regarding the sending and receiving of SMS messages. Personally I have never had this issue and quite a few users haven't either. Whilst the Tre kernel may have some advantages over the older kernel which are currently unknown, I have to make a serious choice with regards to stability and user satisfaction.

I am therefore announcing that, starting with the next release, all roms will be built using the T-Mobile 2.1 kernel.

What does this mean for you? Well this means that, hopefully, the stability of the rom will return to the levels of the beta versions. Any users that are currently experiencing issues with touchscreen and 3G service interruptions will find these issues have gone. If you are unlucky enough to not have working 3G on any of these roms then I'm sorry that this issue will continue.

If enough people demand it then I will produce a small update which will replace the kernel with the Tre kernel, and replace the Wi-Fi binaries at the same time. I must stress that this must be done entirely at your own risk and support will be limited.

Users have recently reported the same issues with the official Tre rom which leads me to declare that the Tre kernel contains serious bugs. I cannot accept this into any version of my rom until the bugs are resolved and I am deeply sorry for all issues caused by the addition of this to FLB-MOD 1.0

You guys deserve to have a working stable ROM and I will provide this again. As my mother says, why fix something if it isn't broken?

[Guest Simon O]

How is it possible that the SMS bug is cleared with the old kernel from HU? I thought it was an issue triggered by the old kernel?

It was previously believed by myself that the issue was related to the kernel. However this isn't the case. The actual cause of the issue is the old running out of memory issue. With some careful management this can be resolved or at the very least cut down to absolute minimum.

I'm learning more about Android each day. Sometimes I make a mistake.

[Guest tobbek]

It was previously believed by myself that the issue was related to the kernel. However this isn't the case. The actual cause of the issue is the old running out of memory issue. With some careful management this can be resolved or at the very least cut down to absolute minimum.

I'm learning more about Android each day. Sometimes I make a mistake.

I have a 8220 bought from Tre sweden, and have updated with the hungarian 2.1 and tried beta 3,4,5 and now I am on 1.0 and I am so happy with it, no FC and no other issues, no problem with send or recive sms, and have not had any troubble with the touchscreen either, so thank you for a wounderful rom it so fast compared to the other beta roms!

I just did a full wipe before installing the roms I have tested and have never had any issues.

[Guest wheresmyhead]

It's a shame that some are having issues with this rom, because for me it's the fastest and best one yet. I thought I was having 3G issues but after running the rom for a couple of days, it seems to have settled down.

I think I speak for many people when I say that I really appreciate all the effort you put into FLB. This rom has really transformed my phone and I chuckle at people who spend £600 on a iPhone4 :)

[Guest Totyasrác]

I am deeply sorry for all issues caused by the addition of this to FLB-MOD 1.0

You really shouldn't be, mate!!! You're doin' an excellent job, beyond all /acceptable/ expectations. Whoever works - might make mistakes (and who doesn't... he'll probably won't).

You guys deserve to have a working stable ROM and I will provide this again. As my mother says, why fix something if it isn't broken?

Actually we deserve but that should definitely come from either Huawei and/or T-Mo. The job you're doing is fantastic and helps us to live with our Pulses since the manufacturer (and the vendor) appearently left us alone.

So huge respect to you, Flibblesan!

[Guest Totyasrác]

I have an idea (that I've written here a couple of times in various topics since can't get this out of my mind :)) how Pulse could be made the best possible phone from what we have: resizing partitions. That is a tougher job than anything so far but I believe (without any practical experience with Android and ROM hackin' :D) it is not impossible... Only thing is to puzzle it out how to create a "big" update resizing system partition... Too bad I don't have time to get deeper into Pulse-hackin'...

:P

[Guest Simon O]

I have an idea (that I've written here a couple of times in various topics since can't get this out of my mind :)) how Pulse could be made the best possible phone from what we have: resizing partitions. That is a tougher job than anything so far but I believe (without any practical experience with Android and ROM hackin' :D) it is not impossible... Only thing is to puzzle it out how to create a "big" update resizing system partition... Too bad I don't have time to get deeper into Pulse-hackin'...

:P

There are some clever people already working on this. Once they unravel the mysteries of the updata.app then the sky is the limit. All that wasted space can be used :P

[Guest Basher52]

flibbelsan, your rom is nearly perfect, but could you add a more aggressive memory mangement to init.rc? iam using your rom with autokill setting "optimum" und now my pulse can fly :)

[Guest Simon O]

flibbelsan, your rom is nearly perfect, but could you add a more aggressive memory mangement to init.rc? iam using your rom with autokill setting "optimum" und now my pulse can fly :P

What application are you using to change the settings?

edit: it's OK i found autokiller :)

edit2: Ooh nice, forgot I can set "ro.HOME_APP_ADJ=1" in the init.rc too :D

Edited July 13, 2010 by flibblesan

[Guest brack]

What application are you using to change the settings?

edit: it's OK i found autokiller :)

edit2: Ooh nice, forgot I can set "ro.HOME_APP_ADJ=1" in the init.rc too :D

So, is autokiller actually improves things or not? I used this program all the time before beta5.1 but then read from flibblesan that he is not using anything, and I removed autokiller. Found that the rom with ADW became quicker (or maybe I didnt set autokiller properly?).

[Guest Basher52]

Using Android 1. 5, Autokiller wasnt nessesary. But with the great 2. 1 RAM is very limetted, cause Ansroid needs more space.

Try it yoursself, using Optimum or Strict settings, i wont miss it anymore :-)

[Guest Simon O]

So, is autokiller actually improves things or not? I used this program all the time before beta5.1 but then read from flibblesan that he is not using anything, and I removed autokiller. Found that the rom with ADW became quicker (or maybe I didnt set autokiller properly?).

It does improve things and I know a few roms on other devices use custom settings (G1, HTC Hero are two I know of). It really cannot hurt to have some tweaks to this.

I don't like having to run additional apps to change these settings so adding them to init.rc helps.

Adding the ro.HOME_APP_ADJ tweak to this will definitely make a difference (for me, at least. I hate having to add it to all the local.prop files manually!).

[Guest Totyasrác]

Using Android 1. 5, Autokiller wasnt nessesary. But with the great 2. 1 RAM is very limetted, cause Ansroid needs more space.

Try it yoursself, using Optimum or Strict settings, i wont miss it anymore :-)

Well, the main reason against that is that this app also uses memory... But I guess I'll try and see and if I don't see any improvement I'll just uninstall that :)

[Guest Simon O]

Well, the main reason against that is that this app also uses memory... But I guess I'll try and see and if I don't see any improvement I'll just uninstall that :)

I'm not using the application. I've edited init.rc in the boot image and the phone really does feel snappier. :D

[Guest meinnit]

Using Android 1. 5, Autokiller wasnt nessesary. But with the great 2. 1 RAM is very limetted, cause Ansroid needs more space.

Try it yoursself, using Optimum or Strict settings, i wont miss it anymore :-)

AutoKiller on 1.5 is great! It stops apps auto starting apps in the background for no reason, therefore saving a lot of battery.

I would definately recommend using AutoKiller. I use Moderate (30,35,40) setting for every day use and Strict (60,70,80) when I'm desperatly trying to conserve battery.

[Guest meinnit]

Well, the main reason against that is that this app also uses memory... But I guess I'll try and see and if I don't see any improvement I'll just uninstall that :)

AutoKiller does not use memory itself. It simply changes the settings for the internal Android memory management system and then it can be killed itself.

[Guest meinnit]

AutoKiller simply edits this file:

/sys/module/lowmemorykiller/parameters/minfree

Run cat /sys/module/lowmemorykiller/parameters/minfree to view content.

More technical details here:

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

[Guest brack]

AutoKiller simply edits this file:

/sys/module/lowmemorykiller/parameters/minfree

Run cat /sys/module/lowmemorykiller/parameters/minfree to view content.

More technical details here:

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

Why we wouldnt simply edit this file without installing one more app? Flibblesan could you probably build this into next release?

[Guest biron_w]

I am therefore announcing that, starting with the next release, all roms will be built using the T-Mobile 2.1 kernel.

I really hope going back to the t-mobile 2.1 doesn't bring back the screen freezing problem. I had a lot of trouble with that on the beta roms but so far I haven't had it once on the 1.0 release. I also haven't had a single problem with the new rom either.

[Guest MarcusHenrique]

I am therefore announcing that, starting with the next release, all roms will be built using the T-Mobile 2.1 kernel.

I don't understand.. I'm having zero issues with TRE kernel.. It's the best release so far...

I don't get why it differs that much from person to person.. since 2.1 unifies all U8220 versions into same driver specs.

[Guest Simon O]

Why we wouldnt simply edit this file without installing one more app? Flibblesan could you probably build this into next release?

Added to 1.1 already :)

I really hope going back to the t-mobile 2.1 doesn't bring back the screen freezing problem. I had a lot of trouble with that on the beta roms but so far I haven't had it once on the 1.0 release. I also haven't had a single problem with the new rom either.

Remind me about the screen freezing problem again please? I'm not entirely sure what you mean.