[ROM] [froyo] Japanese Jellyfish RLS9 [2011-01-24] [OLED+TFT]

[Guest Matthew Ferguson]

The AHB is only overclocked if the CPU is above 600mhz, so if you don't manually oc the cpu with setcpu the AHB is not overclocked.

Considering the majority of people having battery issues have that OC option enabled, I'm not sure what to say. I don't have that enabled and my battery life is great :D

[Guest c-m]

I don't like the ZTE Smart dialler, how do i get the Froyo default dialler?

Last time i deleted the smartdialler.apk i lost all ability to dial numbers, and when a reinstalled it, the app would not start.

[Guest FlippyBoy]

whenever i try to open the message applications it force closes immedetely, anyone having similar problem? Ive tried to reboot, install other message applications, wipe the applications data and reinstalling the ROM. Nothing work. Please help.

Have you restored anything with Titanium? Got the same error as you did, wiped and flashed again and didn't restore any of the messaging configs. Seems to work fine for me now.

[Guest Frankish]

As in everthing in /system/framework and /system/app resigned with testkeys? Sure, I can do that.

Only framework-res.apk and everything in /system/app/. APK Manager will do this in a batch operation for you. I've been running it for a full day and no force closes etc, Nandroid works with themes and themes can be applied before flashing the rom :D

I did post a full zip of RLS6 test signed if you want to use that? It's a couple of pages back somewhere.

[Guest pellen]

Considering the majority of people having battery issues have that OC option enabled, I'm not sure what to say. I don't have that enabled and my battery life is great :D

Come on. Just because you don't have OC enabled and are lucky to not suffer from battery drain it HAS to be because the OC? I dont see the connection because I had the problem even before I tested OC'ing.

[Guest Frankish]

I overclock ahb and processor and i don't have battery issues. I last a full day and that's all i ever got out my San Fran and even my Desire. 1 day max.

[Guest IronDoc]

well i did that. Going to try to reinstall it again and only restore the apps and not the systemfiles.

You can grab that file using ADB or Root Explorer. Look up a tutorial for how to pull files with ADB. If you pull that file while in a backup, then you can wipe and install JJ. Then if you push it back after your install (instead of restoring the data for Messaging), all your texts should be there.

If you're still on JJ at the moment, I would try using ADB to pull that file and then use adb shell to remove it. It's been known to cause troubles sometimes. Again, there are guide for ADB all over the place.

That worked for me. Sorry to repeat myself, but you can't restore system files, that causes the acore crash. I did it myself so I know :P

Also, noticing in this thread, I've been reading it since it appeared, and I've noticed a trend. First a person asks "How do I install overclock?" and they're told and they do, then a few posts later "this rom is awful for battery life" ... coincidence? :D

There is absolutely no reason you can't restore data for system apps through titanium after a wipe. And it has been clearly established that the poor battery life has something to do with the dialer, it's not just the OCed CPU eating it up. If there's a correlation (which I'm doubtful of) then the OC is causing some weird effect on the dialer which should be fixed anyway.

[Guest Anjan Tek]

I just installed it after wiping the cache and user data from the MCR 2.1 rom. I don't use overclocking but I installed the GPS fix and I've got HW acceleration enabled.

I have just done a complete wipe (data and cache) and flashed RLS6 afresh. Once rebooted, the only thing I did was to put in my gmail username and password to setup the account.

Then, I entered the WiFi access password. It connected. I started pinging the IP address from my computer while I waited for the phone to go to sleep.

Promptly, as soon as the phone went to sleep, the ping responses stopped. The WiFi is still going to sleep!! The WiFi sleep policy is set to "Never".

What am I doing wrong?

[Guest IronDoc]

I have just done a complete wipe (data and cache) and flashed RLS6 afresh. Once rebooted, the only thing I did was to put in my gmail username and password to setup the account.

Then, I entered the WiFi access password. It connected. I started pinging the IP address from my computer while I waited for the phone to go to sleep.

Promptly, as soon as the phone went to sleep, the ping responses stopped. The WiFi is still going to sleep!! The WiFi sleep policy is set to "Never".

What am I doing wrong?

Nothing, the wifi sleep problem stills exists afaik. It just reconnects automatically with the new kernel.

[Guest SnowblindFIN]

Is there some fix for Saunalahti users like me,as it shows up as roaming currently.

Also the link for RLS4 Saunlahti fix doesn't seem to work.

[Guest Arr Too]

What am I doing wrong?

First of all: are you expecting the battery to last more than a few hours with wifi and the system fully on like that? Secondly, I think that the phone periodically wakes from deep sleep and checks for stuff. Perhaps someone can confirm that? And perhaps the "never" refers to it also enabling wifi during those periods of wakefulness?

The wifi issue that most people are concerned about is the successful reconnection of wifi when the screen is turned back on. It's probably a good idea to not just say "wifi issue" when you don't mean that one.

[Guest extremedigital]

Hi KK, thanks for all the work on your roms...

First time issue, are you sure gps is fixed in RLS 6 as i applied the zip fix...

I can confirm it works in Google Maps, However It just hangs forever in Google Navigation ??? Please can you look into this asap.

Perhaps you could make a RLS 7 with the gps fix done and hopefully the facebook sync fix added...otherwise thanks for everything...

PS just to see if your 'vanilla' roms does indeed help with battery life so far i have not flashed anything else apart from the gps fix....

However i know it is just a matter of time before i have to succumb to the urge to flash the other parts and Frankish theme...

**Edit** i just went out for a drive so tested the gps function in Google Navigation.....It managed to get a lock after around 10 mins and was fine after that so whilst it does work it seems to be a very buggy still...indoors you dont get a lock at all .....whereas with the older versions i had no issues getting a gps lock indoors at my home location

Edited January 10, 2011 by extremedigital

[Guest Anjan Tek]

Nothing, the wifi sleep problem stills exists afaik. It just reconnects automatically with the new kernel.

Ah! Now, that makes a lot more sense.

But I am sure I read somewhere that the source kernel fixes even the WiFi Sleep Policy setting issue. Could someone confirm that it actually doesn't?

Shouldn't this be mentioned as part of the "Known issues"?

@Matthew Ferguson: But how did WiFi not go to sleep for you, then? Could you please confirm that you are able to ping your phone's IP address even after it goes to sleep?

First of all: are you expecting the battery to last more than a few hours with wifi and the system fully on like that? Secondly, I think that the phone periodically wakes from deep sleep and checks for stuff. Perhaps someone can confirm that? And perhaps the "never" refers to it also enabling wifi during those periods of wakefulness?

The wifi issue that most people are concerned about is the successful reconnection of wifi when the screen is turned back on. It's probably a good idea to not just say "wifi issue" when you don't mean that one.

What do you mean by "system on"?

If the WiFi doesn't stay on, how would the phone receive instant or near-instant email notifications?

I am aware that that there are two different wifi related issues:

1. WiFi going to sleep, despite setting "Never" in the WiFi sleep policy.

2. WiFi not reconnecting when waking up from sleep.

In all my posts, I have clearly referred to problem number 1.

Note that it currently only reconnects when you unlock the screen and not just when you wake up by pressing the power button.

Regarding battery use: I don't think that is an issue here, because if you have mobile data enabled, and if you set the WiFi to sleep, then mobile data is going to be on during phone's sleep. And that is going to consume power. Setting WiFi sleep to "Never" is a way of telling the phone to use the WiFi and not mobile data for background syncing during the phone's sleep. So, any one of the two get used (unless, of course, you have disabled mobile data too, in which case you will get no email notifications).

Edited January 9, 2011 by Anjan Tek

[Guest IronDoc]

Ah! Now, that makes a lot more sense.

But I am sure I read somewhere that the source kernel fixes even the WiFi Sleep Policy setting issue. Could someone confirm that it actually doesn't?

Shouldn't this be mentioned as part of the "Known issues"?

@Matthew Ferguson: But how did WiFi not go to sleep for you, then? Could you please confirm that you are able to ping your phone's IP address even after it goes to sleep?

What do you mean by "system on"?

If the WiFi doesn't stay on, how would the phone receive instant or near-instant email notifications?

I am aware that that there are two different wifi related issues:

1. WiFi going to sleep, despite setting "Never" in the WiFi sleep policy.

2. WiFi not reconnecting when waking up from sleep.

In all my posts, I have clearly referred to problem number 1.

Note that it currently only reconnects when you unlock the screen and not just when you wake up by pressing the power button.

Regarding battery use: I don't think that is an issue here, because if you have mobile data enabled, and if you set the WiFi to sleep, then mobile data is going to be on during phone's sleep. And that is going to consume power. Setting WiFi sleep to "Never" is a way of telling the phone to use the WiFi and not mobile data for background syncing during the phone's sleep. So, any one of the two get used (unless, of course, you have disabled mobile data too, in which case you will get no email notifications).

This is all elsewhere and is just my understanding of what I've read. The wifi chip used has a function which is sort of similar to 'wake on lan' where it goes into a low power state until it receives something or an app attempts to send something. ZTE haven't activated (or have disabled) this ability for whatever reason. In the absence of this android shuts it down completely unless it is actively being kept awake.

Re: Battery

Wifi is more power intensive than 3G. I dunno how much so.

I guess wifi isn't stated in known issues because it is a known issue with all Blades, not with the ROM.

Edited January 9, 2011 by IronDoc

[Guest Salsaholic]

Just updated from RLS5 to RLS6 + GPS fix. No new issues so far, haven't been able to try GPS though...

But my issue with network not shown persists - am I really the only one with this???

[Guest JBSCARFACE]

Nice work thx a lot M8 :D

Edited January 9, 2011 by JBSCARFACE

[Guest JBSCARFACE]

Turn on the stagefright lines in build.prop (change false to true). That will enable the broken Stagefright video decoder. That enables some games to work that has videos that isn't playable with the old video decoder. They may just show a black screen where there should be video but at least it can make the game runnable.

I enable it but there is no video only sound ... It works on RLS3-4 but not on on RLS5-6 why?

[Guest zhanglp888]

waiting for rls7!

[Guest Rotmann]

There is absolutely no reason you can't restore data for system apps through titanium after a wipe. And it has been clearly established that the poor battery life has something to do with the dialer, it's not just the OCed CPU eating it up. If there's a correlation (which I'm doubtful of) then the OC is causing some weird effect on the dialer which should be fixed anyway.

A lot of users and I have already established that restoring system apps from a different ROM may result in FC because of incompatibility. I saw this myself for a number of times. I do think that OC is the main reason for the exagerated power drain and not the dialer. The same dialer is on Sebastian404's Froyo and my battery life has increased significantly over 2.1.

I enable it but there is no video only sound ... It works on RLS3-4 but not on on RLS5-6 why?

Delete two lib files from /system/lib which are libOmxAacDec.so and libOmxMp3Dec.so , restart and the sound will work. If you enable Stagefright, make sure to set true instead of false, excepting stagefright-http which should remain false. If you set it to true your HQ youtube videos will have a green bar at the top.

[Guest pxpto]

Hi, this rom is getting better every day!

All my problems with previous releases are now gone!

But I still have the same old problem that brought me to 2.2: "bluetooth voice dialing". I pair my bluetooth car kit to the phone, press the call button and nothing happens! It should activate voice dialing on the phone! If i long-press it then the phone redials.

Anyone knows how to activate Froyo's voice dial function?

Note: voice dial is NOT Google Voice Search! They are different things. Voice dial function works offline while Googles app needs an internet connection.

Btw, i think that the current "lite" releases are great but it should have the stock Filer app. Every OS comes with a basic set of apps + a file explorer.

Keep up the good work!

[Guest The Red]

Not sure if this has been answered before, thread is too long....

OLED SF, Clockwork 2.5.1.8, wiped cache and user data, installed RLS6 from Clockwork menu. After reboot it just hangs at Android man?

Tried installing it again but it does the same.. not sure what else to try?

[Guest IronDoc]

A lot of users and I have already established that restoring system apps from a different ROM may result in FC because of incompatibility. I saw this myself for a number of times. I do think that OC is the main reason for the exagerated power drain and not the dialer. The same dialer is on Sebastian404's Froyo and my battery life has increased significantly over 2.1.

I'm not disputing there are issues sometimes, but employing a blanket policy of never restoring system apps defeats the point of using titanium. I can't believe we're still debating the battery thing. A partial wake usage from dialer of around 40% (it was higher before) is not normal, overclock or not.

Edited January 10, 2011 by IronDoc

[Guest _amano]

Perhaps you could make a RLS 7 with the gps fix done and hopefully the facebook sync fix added...otherwise thanks for everything...

+1

And the update to the new Andorko Radio was great. Pretty usable now :D

[Guest mantokoski]

Thank you for this great ROM! :D

I'm not sure about battery life though yet. I don't see Dialer using the battery much. What does dialer do btw?

For some reason Finnish localisation is almost completely missing, the UI is mostly in English. If you change language to Norwegian or Swedish, you get UI in those languages. I use Swedish Gingerbread keyboard, which is great.

Luckily the News & Weather widget gets Finnish news and weather.

Is there some fix for Saunalahti users like me,as it shows up as roaming currently.

Also the link for RLS4 Saunlahti fix doesn't seem to work.

Here's a working link. It works with RLS6.

http://tinyurl.com/saunalahti-ril

Although in reality Saunalahti is kind of always roaming. But obviously roaming can make things difficult in some devices, like extra warnings etc. The fix changes network's name from Elisa to Saunalahti.

In original Saunalahti ROM the network name is correctly Elisa Oyj, but still it doesn't show Saunalahti roaming, that would be the best situation.

Edited January 10, 2011 by mantokoski

[Guest sukkamehu]

For some reason Finnish localisation is almost completely missing, the UI is mostly in English.

I agree, just few words are in finnish. This sucks. =)

Thank you anyway!