[ROM] [eclair] Finnish Fillyjonk RLS5 [2011-01-05]

[Guest oker]

Costom mp3 ringtones are not working, I've tried several market apps for it, they didn't work

[Guest LordKickapoo]

Costom mp3 ringtones are not working, I've tried several market apps for it, they didn't work

I installed music ringtone app from market....I chosed a song downloaded it to my Blade, opened it from my ringtones from app that opened some app so i can edit the ringtone and then saved it as default ringtone....That worked

[Guest kallt_kaffe]

What about the Proximity and Light Sensor that sometimes after reboot has to be initialzied to work properly. Any fix for this?

If this (through adb or terminal (as root) fixes it then I think I can fix it:

/system/bin/proximity.init -r

[Guest Smiff2]

kallt_kaffe, sorry to bother you, have you tried K9 mail? it crashes very often on both phones i've tried your ROM on. this is the only remaining issue I have and i'm not sure if ROM related, guess i should try another ROM but nervous now i've got almost everything else nicely set up!

thanks for the great work, i had some suggestions to make, but first are you still maintaining this ROM please?

if i want to remove included apps, would i delete them from the .zip, then flash that (without clearing cache or data) and they'd be gone? trying to delete included apps through appbrain doesn't work of course and i'm running out of space.

Edited January 5, 2011 by Smiff2

[Guest PeterDreher]

If this (through adb or terminal (as root) fixes it then I think I can fix it:

/system/bin/proximity.init -r

Nope this did not fix it. Any other commands i could try? proximity.init -z or something like that?

Z-Device said they are fine, and really they showed right values when testing Proximity (cm) and Light (lux). But still not working in Caller and no Auto-Brightness.

Dialed *#26***# and tested proximity and light and they both worked again.

Funny thing is that it is not happening after ever reboot. Needed 3 reboots to reproduce. Other time it did not work after one reboot.

Could you please make a call while charging and then unplug the cable? Call will be interruped. Fix? Not happening in Stock Firmware.

Thanks a lot!

[Guest Arr Too]

Dialed *#26***# and tested proximity and light and they both worked again.

The dialler code (Engineering Mode) invokes this static method:

android.hardware.SensorManager.sensors_data_calibrate();

[Guest kallt_kaffe]

The dialler code (Engineering Mode) invokes this static method:

android.hardware.SensorManager.sensors_data_calibrate();

I suppose someone with some Android app coding skills could make a small app that runs at boot that calls that method? However I'm considering making a slim ROM out of the Swedish Comviq blade. It's about a month newer than the Finnish one and one file that has changed is the promixity.init file.

[Guest kallt_kaffe]

RLS5 in first post. Apart from updating lots of apps the main reason for the new release is that I've made the "lite" version less than 128Mb for those advanced users that have modified their partition sizes (instructions in second post)

Edited January 5, 2011 by kallt_kaffe

[Guest kallt_kaffe]

Nope this did not fix it. Any other commands i could try? proximity.init -z or something like that?

Z-Device said they are fine, and really they showed right values when testing Proximity (cm) and Light (lux). But still not working in Caller and no Auto-Brightness.

Dialed *#26***# and tested proximity and light and they both worked again.

Funny thing is that it is not happening after ever reboot. Needed 3 reboots to reproduce. Other time it did not work after one reboot.

Could you please make a call while charging and then unplug the cable? Call will be interruped. Fix? Not happening in Stock Firmware.

Thanks a lot!

Try this, half-done, ROM, based on the Swedish Comviq ROM: http://www.mediafire.com/?p1ogbbfvlamvffa

It has some quirks like compass is not working correcly but it's a WIP. Let me know if it solves any of the issues. It's a lite version and fits within a 128Mb system in case you have changed your partition layout.

EDIT: The hangup on removing charging seems to be related to the custom kernel. With the original kernel it doesn't happen. I think this was introduced in the latest source from ZTE and I think I know what to change to fix it.

Edited January 5, 2011 by kallt_kaffe

[Guest panteraz]

***** sorry wrong topic *****

Edited January 5, 2011 by panteraz

[Guest uptime]

Great work, kallt_kaffe. Just updated to RLS5, looks fine so far. :unsure:

[Guest TigerDigi]

Great! I think it should be the final version of 2.1 ROMs...Tks 4 ur work!

[Guest PeterDreher]

EDIT: The hangup on removing charging seems to be related to the custom kernel. With the original kernel it doesn't happen. I think this was introduced in the latest source from ZTE and I think I know what to change to fix it.

What are the advantages of the costum kernel?

Would be great if you find a fix. thanks

Edited January 5, 2011 by PeterDreher

[Guest JingleManSweep]

Release RLS5 has been added to Android Guide site:

http://www.androidguide.co.uk/release/finnish-fillyjonk-rls5

[Guest jasonXXx]

Release RLS5 has been added to Android Guide site:

http://www.androidguide.co.uk/release/finnish-fillyjonk-rls5

Hi kk any chance you can make a No AHB bus overclocking untill over 600 with all the extra kernal stuff like you did with rls3 thanks in advance.

[Guest BoDyTaNk]

I'm currently using RSL4 rom with A2SD on an EXT3 partition. Since my 2GB SD card is running out of space, I need to upgrade it with a larger capacity one.

Is the following procedures ok?

(1) do a NANDROID backup

(2) copy the clockworkmod/backup directory from SD card to my PC

(3) partition my new SD card with proper EXT3 partition

(4) copy the clockworkmod/backup directory from my PC to the new SD card

(5) restore the NANDROID backup

[Guest kallt_kaffe]

What are the advantages of the costum kernel?

Overclocking and some other things, but mostly overclocking.

Would be great if you find a fix. thanks

The removing/inserting charger breaking calls is now fixed in the custom kernel I'm running on my phone now. However I'm still interested if the comviq build I posted helped with the promximity problems. It has a different proximity.init binary so they may have fixed something. Another thought. Does it make a difference if you have auto brightness enabled or not?

Edited January 5, 2011 by kallt_kaffe

[Guest PeterDreher]

The removing/inserting charger breaking calls is now fixed in the custom kernel I'm running on my phone now. However I'm still interested if the comviq build I posted helped with the promximity problems. It has a different proximity.init binary so they may have fixed something. Another thought. Does it make a difference if you have auto brightness enabled or not?

Ok Buddy, here we go.

1. tried your Test-Firmware. Worked fine. Rebooted about 15 times. No issues. Best part: csipsimple (best voip-client) finally really hangs up when ending a call! It did not do this with RLS or the deoranged Firmware. But with the Test-Firmware it did. Sweet.

2. tried a complete wipe with factory defaults and wipe cache and tried RLS5 again. Rebooted about 10-15 times. No Problem with the Proximity or Light. Could be that i used to upgrad RLS2 to RLS4 and somehow that Proximity and Light-Error accrued. Maybe there is a widget that triggers that issue. I don't know. Worked fine with a clean Version.

3. All you have to do is include Launcher Pro. All others suck or could be installed later. No version needs something else but Launcher pro :unsure:

4. I really don't like the bootup logo of RLS. Maybe you can use the Android-Dude and print your Credits? This logo is really not worth your hard work. It really destroys this awesome piece of work, really.

What are the differences in that test-firmware? I really seem to like that one. Hope you get all problems sorted out. Compass, anything else?

Why should i change my partition layout? Could not find the advantages.

Thanks a lot for everything you do.

Edited January 6, 2011 by PeterDreher

[Guest Smiff2]

flashing original kernel did not fix the K9 crash problem :/

i can reflash the full archive with some apps removed, to remove included apps?

i think you could consider including some of the following in FAT package (where allowed?)

Quick Boot

Fancy Widget

Z-DeviceTest

Wifi Analyzer

Edited January 6, 2011 by Smiff2

[Guest omel31]

Hi I'm currently running a Finnish Fillyjonk RLS4..If I'm going to update/upgrade to Finnish Fillyjonk RLS5, Do I need to wipe my cahe/data?

Edited January 6, 2011 by omel31

[Guest uptime]

Hi I'm currently running a Finnish Fillyjonk RLS4..If I'm going to update/upgrade to Finnish Fillyjonk RLS5, Do I need to wipe my cahe/data?

I don't think so. I didn't wipe and everything works fine.

[Guest uptime]

4. I really don't like the bootup logo of RLS. Maybe you can use the Android-Dude and print your Credits? This logo is really not worth your hard work. It really destroys this awesome piece of work, really.

Well, believe it or not, my wife loves that Fillyjonk on her SF. I can already anticipate the discussions when I'll update her phone to Froyo soon. I bet she'll make me put that Fillyjonk boot logo on it. :unsure:

[Guest omel31]

I don't think so. I didn't wipe and everything works fine.

ok great coz i'm just worried of my save game in my phone and i really dont know how to use a titanium backup

anyways if i dont wipe... my save game will be there and it will work after i update Finnish Fillyjonk RLS5??

thanks

Edited January 6, 2011 by omel31

[Guest uptime]

ok great coz i'm just worried of my save game in my phone and i really dont know how to use a titanium backup

anyways if i dont wipe... my save game will be there and it will work after i update Finnish Fillyjonk RLS5??

Yes. But I recommend making a backup with clockworkmod before any update. You can restore the full state of your phone in case anything goes wrong.

[Guest jyrppa]

Is it possible to somehow get AHB OVERCLOCKING on with RLS5 with 5mb camera blade?

Is there default_kernel_addon with AHB_OVERCLOCKING somewhere?