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

[Guest TheBigAK]

My experience with the latest FLB version and ADW has been near perfect. I have full bluetooth functionality, camera button working to launch app and take shots, excellent WiFi speeds etc.

The only bugs I can report are probably the ones that can't be fixed easily:

1. Phone freezes and requires battery pull when using 3G and CPU heavy apps.

2. Both google navigation and copilot freeze when using GPS after about half an hour. This bug made me arrive 30 minutes late for a job interview and cost me the position!

Do you think we will ever solve these problems, because I am seriously thinking about selling my phone for a Galaxy S or Streak... I almost smashed it when I was late for that interview and had to do battery pull and reboot on a dual carriageway!!!

[Guest xarxiusxiii]

My experience with the latest FLB version and ADW has been near perfect. I have full bluetooth functionality, camera button working to launch app and take shots, excellent WiFi speeds etc.

The only bugs I can report are probably the ones that can't be fixed easily:

1. Phone freezes and requires battery pull when using 3G and CPU heavy apps.

2. Both google navigation and copilot freeze when using GPS after about half an hour. This bug made me arrive 30 minutes late for a job interview and cost me the position!

Do you think we will ever solve these problems, because I am seriously thinking about selling my phone for a Galaxy S or Streak... I almost smashed it when I was late for that interview and had to do battery pull and reboot on a dual carriageway!!!

I have the same annoyances, which is why I'm getting a Nexus One... This phone is great, and has an excellent community behind it, but I've had it with the frustrations it brings me...

This is a great ROM though, it's the best experience I've had on this phone, well done.

[Guest Pq2son2]

First, thanks coz this community it's really really fast to answer the post!!

And sorry, maybe I don't explain fine the bugs that I found. I don't have many reboots, only 2 or 3, since I was flashing the official 2.1 update. Then for me the problem, that I'm thinking that can be resolved, it's every time that I exit from the Android Market (if I browse apps or install them) the AWK reload the home.

I believe that it could be because I have or 4 widget on the home and, as we know, the Pulse doesn't have a lot of RAM.

By the way, the widgets are: My calendar, Analog Clock, Power Control and News and Weather (the last one only used to show the weather).

Have some other person the same problem? Can it be solved? Can I unblock the lasts 18M that (if I can trust the Systemmonitor) my pulse has?

Thank you!!

Pd. The freezed problem I resolved using only the GRPS (yes I know "damm it!"), I use the Google Maps Navigation, over GPRS, for ~40mins without any problem and freeze system.

Edited July 6, 2010 by Pq2son2

[Guest rikkiej]

Is anyone noticing the following bug:

When rebooting your phone after another freaking freeze. The pulse boot animation keeps on going untill I press the unlock key twice when I will be presented with a sim card unlock.

P.S. off topic: THE NETHERLANDS RUUUUUUUULE ALL!!

[Guest ogiogi]

Is anyone noticing the following bug:

When rebooting your phone after another freaking freeze. The pulse boot animation keeps on going untill I press the unlock key twice when I will be presented with a sim card unlock.

I got this after flashing Hungarian ROM on top of SWE Tre ROM, or from ADW system version which i flashed both on Hungarian and FLB's ROM. Don't really know for sure. And the bug was present on both Hungarian and FLB's ROM's. Had to time machine -> December update -> Hungarian 2.1 just to be sure.

[Guest killahtm]

do you plan soon doing froyo? :)

[Guest dodge-167]

or a 2.1 update?

[Guest Simon O]

Froyo will be a seperate ROM once we have a working kernel compiled and working vendor files so Froyo can be compiled for our devices.

There will be an update to FLB coming soon once I'm happy that current testers have no issues.

[Guest gusthy]

Froyo will be a seperate ROM once we have a working kernel compiled and working vendor files so Froyo can be compiled for our devices.

There will be an update to FLB coming soon once I'm happy that current testers have no issues.

yiiip

what will be the changes?

How can one become a tester? :))

[Guest flip360]

here, here :) wanna know too

[Guest naniteboy]

There will be an update to FLB coming soon once I'm happy that current testers have no issues.

Great :) But then I have a question ... I'm very satisfied with FLB currently (have latest update) but I still have problems with one thing.

It seems that after the phone was on for a few hours and I was using it normally - some services cease to run propely.

News&Weather widget doesn't update, clock widget doesn't update (I'm using Digi Clock widget - but I tried with some others - same thing), GMail doesn't update as it should and so on ... as I said - like background services simply stop running (but they are loaded into memory - checked with MemInfo app).

Any solutions for that?

[Guest de_shepherd]

Great :) But then I have a question ... I'm very satisfied with FLB currently (have latest update) but I still have problems with one thing.

It seems that after the phone was on for a few hours and I was using it normally - some services cease to run propely.

News&Weather widget doesn't update, clock widget doesn't update (I'm using Digi Clock widget - but I tried with some others - same thing), GMail doesn't update as it should and so on ... as I said - like background services simply stop running (but they are loaded into memory - checked with MemInfo app).

Any solutions for that?

Isn't this just a symptom of the lack of memory ... as more things get run over time more memory is consumed and eventually some things which should continue to run get told to save state and stop.

[Guest gusthy]

Isn't this just a symptom of the lack of memory ... as more things get run over time more memory is consumed and eventually some things which should continue to run get told to save state and stop.

AutoKiller seems to help.

[Guest gusthy]

Isn't this just a symptom of the lack of memory ... as more things get run over time more memory is consumed and eventually some things which should continue to run get told to save state and stop.

AutoKiller seems to help.

[Guest Simon O]

AutoKiller seems to help.

Won't be needed :D

as for testers I have enough right now but if I need more I'll contact some people at random :)

Edited July 7, 2010 by flibblesan

[Guest DanWilson]

Won't be needed :P

as for testers I have enough right now but if I need more I'll contact some people at random :)

:D

(If I don't get random contact :P )

[Guest gusthy]

Won't be needed :P

as for testers I have enough right now but if I need more I'll contact some people at random :D

Is there a way to hack random generator to include people whose name begins with "gust" more frequently? :)

[Guest Simon O]

Is there a way to hack random generator to include people whose name begins with "gust" more frequently? :)

Well if somebody has a U8220-6 then that would be helpful. Some -6 users had issues with wifi using the Tre rom and I want to make sure that the changes I made to FLB doesn't kill wifi for those users.

Also I'd like a U8230/RMB2 tester if possible please?

I currently have enough standard pulse testers (3)

[Guest DanWilson]

Well if somebody has a U8220-6 then that would be helpful. Some -6 users had issues with wifi using the Tre rom and I want to make sure that the changes I made to FLB doesn't kill wifi for those users.

Also I'd like a U8230/RMB2 tester if possible please?

I currently have enough standard pulse testers (3)

Yeah but you really need me! JKJK

Any new features that I may have missed? Or are we converting to the Tre ROM?

[Guest Stevos]

Just trying out beta5.1...

I know the first boot sometimes takes a while, but should I be looking at the boot animation for more than 10 minutes?

Process: (from FLB beta3)

* full wipe, wipe all settings

* flash 5.1

* reboot

I also tried flashing the 5.1update1 directly after the main rom (without a reboot) to see if it made a difference. Still taking forever to boot.

Edit: ah crap now the beta3 update has the same problem. Time to go back to something earlier and start again perhaps...

Edited July 7, 2010 by Stevos

[Guest snikje]

odd. i cant get the hungarian 2.1 to install. it tells me:

E: no signature(7 files)

E: verification failed

after some thinking i tried installing it via upgrade in the settings menu . i figured since it is an official update it probebly should be installed that way

but no luck there either it tells me upgrade wasnt found.

anyone know what to do now?

Edited July 7, 2010 by snikje

[Guest Stevos]

Maybe go back to the 1.5 december (via the huawei reset rom thing)

then install hungarian 2.1, then try to install again ?

I mildly hosed my update system. When running updates via the dload folder (such as the reset rom, the december 1.5 and the hungarian 2.1) using the {red button} plus {volume up}, I got corrupted black and white lines on the bottom inch of my screen, and the hungarian 2.1 locked up on the static "android" boot logo.

Going right back again to 1.5 dec -> hungarian 2.1 seems to have solved the corruption issue, but the permanent boot animation when booting FLB beta5.1 seems to remain. I just can't get it to boot.

[Guest Andy Veliz]

Well if somebody has a U8220-6 then that would be helpful. Some -6 users had issues with wifi using the Tre rom and I want to make sure that the changes I made to FLB doesn't kill wifi for those users.

Also I'd like a U8230/RMB2 tester if possible please?

I currently have enough standard pulse testers (3)

i can help u with the u8220-6 :)

[Guest gusthy]

Maybe go back to the 1.5 december (via the huawei reset rom thing)

then install hungarian 2.1, then try to install again ?

I mildly hosed my update system. When running updates via the dload folder (such as the reset rom, the december 1.5 and the hungarian 2.1) using the {red button} plus {volume up}, I got corrupted black and white lines on the bottom inch of my screen, and the hungarian 2.1 locked up on the static "android" boot logo.

Going right back again to 1.5 dec -> hungarian 2.1 seems to have solved the corruption issue, but the permanent boot animation when booting FLB beta5.1 seems to remain. I just can't get it to boot.

maybe you dont do full wipe before flashing flb?

[Guest Andy Veliz]

1000 replies 4 this topic...

xD

Edited July 7, 2010 by Andy Veliz