[ROM] [eclair] French Fries RLS5 [2010-11-18]

[Guest BillBong]

I installed this rom (after doing a factory reset and clearing data partition through clockwork). It booted in and everything looked good but when I restored some apps through Titanium, it gets stuck in a boot loop when I restarted it. It's just cycling through the "powering up, please wait" message. I've tried re-flashing (after doing a clockwork cache/data/davlick clear several times and this is now still happening on every other boot-up even before I do any restore through Titanium. I haven't installed any of the overclocking zips it and I've tried re-flashing with and without the hardware acceleration but it's still stuck here.

Is anyone else having any problems like this? I like the ROM because it has the A2SD working and seemed pretty quick but it's driving me crazy now so I'm going to re-flash it to what I had before.

[Guest gambieter]

Damn, this is a nice ROM, but a dealbreaker for me is the lack of the possibility to switch off mobile data in the Settings menu. Is this a consequence of using the French ROM, as I also see that it is lacking in the BladeVillain 1.0.1 ROM?

I know there are widgets, but as a prepay user who is mosty using the phone abroad (not for data) I don't want to risk connections.

[Guest Freekers]

Damn, this is a nice ROM, but a dealbreaker for me is the lack of the possibility to switch off mobile data in the Settings menu. Is this a consequence of using the French ROM, as I also see that it is lacking in the BladeVillain 1.0.1 ROM?

This is indeed a consequence of using the French ROM. ( http://android.modaco.com/content-page/323...0/#entry1478428 )

Edited November 19, 2010 by Freekers

[Guest kallt_kaffe]

Thanks for the update ! Is Hungarian ROM better/more stable/faster ?

Some apps that uses the google maps framework that crashes in orange or french builds works fine in the hungarian one. Speedwise I don't think there is a difference. It also have a checkbox to disable mobile data which is something that is missing in the french build. Also the Contacts app is more advanced.

Is the WiFi fixed in that one ?

No, it's just as bad as with the other builds. :)

Also, just a note but I assume you already know, the Hungerian Blade has a TFT screen instead of a OLED one and lower memory :)

I'm well aware of that but the build is very similar to the other blade builds. Just a bit updated and more "clean" out-of-the-box.

Last but not least, could you please tell me if the bootscreens of iDroid84 are compatible with your ROM/Kernel ? B) (See link above). Thanks !

Haven't had time to look at them but any bootanimation that goes into /system/media/bootanimation.zip should work. At least if they are designed for 480x800.

[Guest kallt_kaffe]

Hi kallt_kaffe, for the next release it would be nice if you could set ro.secure to 0 in your compiled kernel.

That's the kernel, that's goes into to the initrd which is a part of boot.img but yes, I could do that but what exactly does it that prop control?

[Guest kallt_kaffe]

I installed this rom (after doing a factory reset and clearing data partition through clockwork). It booted in and everything looked good but when I restored some apps through Titanium, it gets stuck in a boot loop when I restarted it. It's just cycling through the "powering up, please wait" message. I've tried re-flashing (after doing a clockwork cache/data/davlick clear several times and this is now still happening on every other boot-up even before I do any restore through Titanium. I haven't installed any of the overclocking zips it and I've tried re-flashing with and without the hardware acceleration but it's still stuck here.

Is anyone else having any problems like this? I like the ROM because it has the A2SD working and seemed pretty quick but it's driving me crazy now so I'm going to re-flash it to what I had before.

Remove the microsd card and see if it boots. I've had that happens sometimes. Not sure if it was stuff in the apps2sd partition or if it was something in the /sdcard/Android folder. I don't remember exactly what I removed to fix it but it was something on the card that caused the problem.

[Guest kallt_kaffe]

Damn, this is a nice ROM, but a dealbreaker for me is the lack of the possibility to switch off mobile data in the Settings menu. Is this a consequence of using the French ROM, as I also see that it is lacking in the BladeVillain 1.0.1 ROM?

I know there are widgets, but as a prepay user who is mosty using the phone abroad (not for data) I don't want to risk connections.

Use the included APNDroid widget. My next build based on the hungarian ROM does not lack this setting.

[Guest buntoid]

Hi kallt_kaffe,

I am using your RLS5 with the 691mhz overclock add-on and have installed SetCpu and checked it is set to ondemand.

I have noticed that the cpu frequency rarely drops below 691mhz while watching it in SetCpu and when it does it drops to the lowest frequency, from there it rises instantly to 691 again but does not do it incrementally.

I've used other overclocked kernel roms with my Samsung Galaxy and the frequency will incrementally drop when I'm not touching the screen and instantly rise again when I do touch the screen.

Do you know why this is?

Great rom by the way, much faster than r4 especially with the galllery!

[Guest gambieter]

Use the included APNDroid widget. My next build based on the hungarian ROM does not lack this setting.

Thanks for the tip, and that's great to hear that the Hungarian one will contain it. I look forward to that, in the mean time I will start playing with Froyo B) .

Thanks for all the great work, much appreciated!

[Guest Freekers]

Some apps that uses the google maps framework that crashes in orange or french builds works fine in the hungarian one. Speedwise I don't think there is a difference. It also have a checkbox to disable mobile data which is something that is missing in the french build. Also the Contacts app is more advanced.

No, it's just as bad as with the other builds. :)

I'm well aware of that but the build is very similar to the other blade builds. Just a bit updated and more "clean" out-of-the-box.

Haven't had time to look at them but any bootanimation that goes into /system/media/bootanimation.zip should work. At least if they are designed for 480x800.

Thanks for the explanation. I guess I'll wait for the Hungarian ROM release then B)

Did you manage to get your hands on it already ? Didn't see a topic yet with a dump of the original ROM....

[Guest superkryo]

That's the kernel, that's goes into to the initrd which is a part of boot.img but yes, I could do that but what exactly does it that prop control?

To allow the remount of read only file systems so that "adb remount" works and adfree can update. Thanks.

[Guest Flumpster]

Cheers for the reply kallt_kaffe, After doing at least 30 installs in the last 2 days I was going to stay on my heavily modded Pauls rom until 2.2 appeared but if you get that Hungarian Rom working with the Data switch I will definitely install and set up everything one more time before Froyo.

If you are already working on this any estimation on release and how much work involved or is it just applying same fixes you did on french one ?

[Guest oh!dougal]

Some apps that uses the google maps framework that crashes in orange or french builds works fine in the hungarian one. Speedwise I don't think there is a difference. It also have a checkbox to disable mobile data which is something that is missing in the french build. Also the Contacts app is more advanced.

..

I'm well aware of that but the build is very similar to the other blade builds. Just a bit updated and more "clean" out-of-the-box.

...

Bring on the Goulash! (or should that be Gulyás, or what?)

[Guest grmn]

First of all thank you very much for your work, kallt_kaffe. The rom runs great!

Since you seem to know your stuff when it comes to modifying the kernel.. do you think you could fix the issue we are having with most voIP apps (including the current ver. of sipdroid and skype) where the sound only comes out of the speakerphone?

I read somewhere that other devices were having the same problem and that it was fixable in the kernel.

thanks