FLB-MOD 1.0 problems

[Guest Simon O]

Of course I think it's a ROM problem. The SMS issue is well known and others persons have the same error.

I don't think it's a network operator issue because the sending person got a successful delivery report.

Very very few people have the issue with receiving SMS messages. It is not an issue I can fix myself no matter how many times people complain about it on this forum.

If you have having SMS issues then the absolute best option is to not use any sort of custom ROM on your phone. It is an issue that affects a very small number of users and WILL be caused by memory usage. If you have many widgets and applications running on your phone that run services in the background then this will affect your phone to the point where the messaging service will be killed. This means you won't receive any SMS.

A delivery report simply means that your phone operator received the message for delivery to your phone. It does NOT mean that your phone has received the message.

[Guest Simon O]

Success at last!!

I rebooted twice and now touchscreen and wifi works!!!!

Yippee!

Excellent. But seems that your phone is suffering from the issue where leaving recovery makes the touchscreen not work. I'm trying to get a newer recovery made.

[Guest Ellia]

And that is the interesting point: I don't have a lot of apps installed. And in the backgrounds there are only the default Android apps, K9 and Handcent running. I use only a calender widget and the default energy control widget. I don't think that is too much for the memory.

Your ROM is in relation to the original 1.5 ROM a new world and the Pulse is a new phone with it.

Is there any way to check if there was a memory problem (maybe with dmesg)? May it be useful to set AutoKiller to more aggressive settings?

/In the morning I got a voice call which was directly forwarded on the mailbox. Maybe a related issue?

Edited July 18, 2010 by Ellia

[Guest topspinserve]

Excellent. But seems that your phone is suffering from the issue where leaving recovery makes the touchscreen not work. I'm trying to get a newer recovery made.

My phone crashed. On reboot, the touchscreen will not work at all. I have tried powering off and then manually power on, and also tried rebooting from recovery. Wifi has also stopped working.

I flashed flbmod_kernel and touchscreen is back, but wifi doesn't work.

Is it possible that my phone is a different batch of U8220?

[Guest Simon O]

My phone crashed. On reboot, the touchscreen will not work at all. I have tried powering off and then manually power on, and also tried rebooting from recovery. Wifi has also stopped working.

I flashed flbmod_kernel and touchscreen is back, but wifi doesn't work.

Is it possible that my phone is a different batch of U8220?

Possible. What model number does it list under the battery?

Also when you flashed the kernel did you also flash the wifi update after?

[Guest topspinserve]

Possible. What model number does it list under the battery?

Also when you flashed the kernel did you also flash the wifi update after?

under the battery it says U8220

After flashing the kernel, touchscreen worked but wifi didn't.

I then tried the wifi update afterwards which appeared not to have made any difference

[Guest Simon O]

under the battery it says U8220

After flashing the kernel, touchscreen worked but wifi didn't.

I then tried the wifi update afterwards which appeared not to have made any difference

Ok, well I'll upload an update by the end of the week which will be in two forms. One with the newer kernel, one with the older kernel. I've made several changes and fixes to the build process so at least one of these should work for you. I can't do it sooner as I'm currently stuck on 3G and it'll take hours to upload the roms.

[Guest Ellia]

And that is the interesting point: I don't have a lot of apps installed. And in the backgrounds there are only the default Android apps, K9 and Handcent running. I use only a calender widget and the default energy control widget. I don't think that is too much for the memory.

Your ROM is in relation to the original 1.5 ROM a new world and the Pulse is a new phone with it.

Is there any way to check if there was a memory problem (maybe with dmesg)? May it be useful to set AutoKiller to more aggressive settings?

/In the morning I got a voice call which was directly forwarded on the mailbox. Maybe a related issue?

AutoKiller get a FC after each restart (I set AutoKiller to apply the settings after each boot). Is there any link between this?

[Guest Simon O]

AutoKiller get a FC after each restart (I set AutoKiller to apply the settings after each boot). Is there any link between this?

Not sure. I'm using manual settings I put into the kernel ramdisk, not AutoKiller, and I've not had any force closes like that.

[Guest Ellia]

Perhaps I rebooted the phone and AutoKiller had a FC and couldn't apply its settings. After that, I lost the SMS. Yes, it sounds very designed, but I don't want back to 1.5.

Is there a easy way (practicable for me) to apply the settings to the ramdisk? And it is necessary to apply the settings with AutoKiller at each reboot?

[Guest topspinserve]

Ok, well I'll upload an update by the end of the week which will be in two forms. One with the newer kernel, one with the older kernel. I've made several changes and fixes to the build process so at least one of these should work for you. I can't do it sooner as I'm currently stuck on 3G and it'll take hours to upload the roms.

Thank you! Can't wait!

[Guest Simon O]

Perhaps I rebooted the phone and AutoKiller had a FC and couldn't apply its settings. After that, I lost the SMS. Yes, it sounds very designed, but I don't want back to 1.5.

Is there a easy way (practicable for me) to apply the settings to the ramdisk? And it is necessary to apply the settings with AutoKiller at each reboot?

Not really. It involves extracting the ramdisk and kernel from the boot.img, unpacking the ramdisk, editing init.rc, building the ramdisk again and creating boot.img

AutoKiller is no longer required. I'm using moderate settings and not had any issues. Phone feels better than it has done.

[Guest Ellia]

Thanks the informations. Your knowledge seems to be very big.

I'm really looking forward to your next release.

Just a a few closing questions: Is there any way to check if the lost SMS was an memory issue? By using dmesg, logcat or something different. Is the SMS delivered to my phone and is only not shown up or will the message be delivered in the future? After a reboot I didn't get the message, in my opinion the SMS must be somewhere on the phone. But where?

[Guest axino]

Ok, well I'll upload an update by the end of the week which will be in two forms. One with the newer kernel, one with the older kernel. I've made several changes and fixes to the build process so at least one of these should work for you. I can't do it sooner as I'm currently stuck on 3G and it'll take hours to upload the roms.

I seem to have the same problem with the touchscreen, so looking forward for your next release.

Thanks for your efforts.

[Guest menno2]

is anyone succesful installing the following dutch shopping app on this rom?

Albert Heijn Appie

please let me know I cannot get it installed!

[Guest Simon O]

menno2: What is the error you get?

[Guest Simon O]

Update on the touchscreen issue affecting some people with the Tre kernel.

I have extracted and compared the kernel configs from the T-Mobile kernel and the Tre kernel. Both are identical as far as hardware support and touchscreen support go. The only differences are the additional of IPv6 and netfilters in the Tre kernel and these won't cause any problems with regards to the touchscreen not working.

Needs more investigation.

Update: The Tre update may have upgraded the touchscreen firmware. This would explain why I have no problems with the tre kernel or the tmobile kernel. If somebody that currently has the touchscreen issue would be willing to flash the Tre update to their phone instead of the t-mobile update then install recovery and FLB as normal, please report back if this has resolved all issues with the touchscreen please.

Also I'd be interested to hear from anybody that has lost 3G with FLB 1.0 to see if flashing the Tre update resolves that issue also.

I should point out that installing the official Tre rom doesn't cause any problems and you can install the 1.5 time machine and go back to t-mobile at any time. The updated firmware will stay updated.

Edited July 19, 2010 by flibblesan

[Guest tido]

That simply means that your SD card is too slow to be used with A2SD

Is a Kingston class 4 8Gb card too slow? :S

[Guest topspinserve]

I have touchscreen issues with TMobile 2.1 and flbmod (touchscreen just doesn't work unless I flash the kernel)

I have also tried flashing the Tre kernel, but found that touchscreen didn't work at all (at least with TMobile, it worked until I flashed flbmod 1.0-- working with other roms eg oscillation and flb beta)

My other issues:

* wifi: worked with oscillation and flb beta, but not current flbmod

* bluetooth car kit: doesn't work with all versions of 2.1

For now, I have gone back to 1.7MCR. Bluetooth works, wifi works and touchscreen works

But, compared to 2.1, 1.5 sucks :angry: :

* poorer battery life

* less sensitive touchscreen

* fewer range of apps

* I have some problems with phone calls (mic seems to be muted)

Can't wait for next update. Hope it solves above issues ?!

Update on the touchscreen issue affecting some people with the Tre kernel.

I have extracted and compared the kernel configs from the T-Mobile kernel and the Tre kernel. Both are identical as far as hardware support and touchscreen support go. The only differences are the additional of IPv6 and netfilters in the Tre kernel and these won't cause any problems with regards to the touchscreen not working.

Needs more investigation.

Update: The Tre update may have upgraded the touchscreen firmware. This would explain why I have no problems with the tre kernel or the tmobile kernel. If somebody that currently has the touchscreen issue would be willing to flash the Tre update to their phone instead of the t-mobile update then install recovery and FLB as normal, please report back if this has resolved all issues with the touchscreen please.

Also I'd be interested to hear from anybody that has lost 3G with FLB 1.0 to see if flashing the Tre update resolves that issue also.

I should point out that installing the official Tre rom doesn't cause any problems and you can install the 1.5 time machine and go back to t-mobile at any time. The updated firmware will stay updated.

[Guest menno2]

menno2: What is the error you get?

Well i cannot find in the market to begin with, it returns no find.

But I got it from a dutch forum which is quite trustworthy.

The error i get is simply "Cannot install" it does open the installer but after a minute

it says cannot install.

Maybe I dont see it in market cause my country i probably not set to Holland in your rom?

Can you find it in Market? and install it?

[Guest menno2]

menno2: What is the error you get?

Well i cannot find in the market to begin with, it returns no find.

But I got it from a dutch forum which is quite trustworthy.

The error i get is simply "Cannot install" it does open the installer but after a minute

it says cannot install.

Maybe I dont see it in market cause my country i probably not set to Holland in your rom?

Can you find it in Market? and install it?

[Guest irvine]

Well i cannot find in the market to begin with, it returns no find.

But I got it from a dutch forum which is quite trustworthy.

Can't find it in the Market here either Menno, though I haven't installed the latest update (which fixes market fingerprint).

But my ASTRO backed up version installs perfectly! I'll put it on my dropbox if you want.

Edit: Link for AH Appie app.

Edited July 19, 2010 by irvine

[Guest Richard van Nieuwenhuizen]

After a FC today I had to restart on my Pulse 3 times for my touchscreen to work.

Yes I have installed the HU_patch.

I tried to go all the way back to 1.5 but when I tried the downgrade went very fast and with no result other then that it still was 2.1 FLB Mod.

Anyone got a manual?! or other solution.

[Guest whackster]

After a FC today I had to restart on my Pulse 3 times for my touchscreen to work.

Yes I have installed the HU_patch.

I tried to go all the way back to 1.5 but when I tried the downgrade went very fast and with no result other then that it still was 2.1 FLB Mod.

Anyone got a manual?! or other solution.

the downgrade (time machine patch) only allows you to flash 1.5 (dec. update again), so you have to flash 1.5 again (the usual way- dload folder on sd)... :angry:

[Guest John Hamelink]

flibblesan, any news on the 3G issues?