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

[Guest Victor von Zeppelin]

Is a wipe needed to go from RLS4 to RLS6? It has new kernel from what I understand, so that probably means a wipe. Lazy me doesn't want to go through the work of setting everything up again :D

No, actually. Wipe's probably for the best, but I went Sebs -> RLS5 -> RLS6 with no wipe...and it's vaguely working (but i've mucked around with it a lot)

[Guest StevenHarperUK]

I Have moved from 5a-6 no wipe

However if you go for the TPT install is does wipe everything

[Guest Waaang]

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.

[Guest Vepo]

Works like a charm, ty!

[Guest Afrodude]

Buggery, really? It's not something i particularly wanted to do. And anyway... the battery drain issue is still there, so it was so no use changing to a different dialer.

Can I therefore make the claim that the dialer is not the problem?

I'm going to assume you have moved from 2.1 to 2.2 without a wipe, right?

You can backup all your apps with Titanium Backup if it makes it easier.

Who knows. There is something that sometimes stops the phone from sleeping. I've only experienced the no-sleep problem once.

[Guest Victor von Zeppelin]

I'm going to assume you have moved from 2.1 to 2.2 without a wipe, right?

You can backup all your apps with Titanium Backup if it makes it easier.

Who knows. There is something that sometimes stops the phone from sleeping. I've only experienced the no-sleep problem once.

Ooh no, i've been using 2.2 for about a month, almost as long as i've had the phone. I've just gone from Sebs to the last 2 releases of Jellyfish. And i've had problems with this in all the Japanese based 2.2 ROMs. It's just the fact that I thought that replacing the dialer with one that is from most other Android phones might solve the battery usage problem.

[Guest cobhc]

Facebook sync is not mentioned under known issues. Does this mean it now works?

It's fixed in FLB r6 due to using the new kernel with the stock dialer, however this rom has the ZTE dialer, so it's still not fixed.

I've been seeing if we can port the other dialer over.

Edited January 9, 2011 by cobhc

[Guest veehexx]

That's because the widgets would be on sdcard, use old school a2sd or keep widgets in phone memory. Everyone knows this! Other than you :D

And yes ckpd-daemon is in RLS6 and behaving itself. :P

i know it now B)

reinstalled rls6 and everything working fine now. not sure what caused it though.

ah well, widgets and email working fine!

thanks for the info!

[Guest IronDoc]

No, tried reflashing but everytime I restored the texts from backup messaging would no longer worked.

I needed a working phone with battery that would last today so quickly went back to RLS3b. Restorin texts on that works fine. I might look at some other way to back up texts so that I can restore them later on a newer release...

You want /data/data/com.android.providers/telephony/databases/mmssms.db. This stores all your texts.

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.

Try deleting the above file and rebooting. Keep a copy in case it doesn't work.

[Guest Waaang]

You want /data/data/com.android.providers/telephony/databases/mmssms.db. This stores all your texts.

Try deleting the above file and rebooting. Keep a copy in case it doesn't work.

Sorry for being such a noob (:

how do i acess it ?

[Guest Victor von Zeppelin]

It's fixed in FLB r6 due to using the new kernel with the stock dialer, however this rom has the ZTE dialer, so it's still not fixed.

I've been seeing if we can port the other dialer over.

I do believe it is actually Contacts and it's associated apks, as well as AccountsAndSync.

I'm trying all this now. It's not very successful :/

[Guest Matthew Ferguson]

Well, I thought that the WiFi sleep problem was only with the Chinese leak based ROMs. Moreover, RLS5 onwards, Jellyfish has a new ZTE released kernel which I thought fixed the problem. The problem is not mentioned under the known issues for this ROM, is it? Don't blame me for thinking that it has been fixed.

And, as I said before, I did NOT have the problem on Paul's MCR alpha 3. Just to confirm, I may try going back to that ROM.

So, oh!dougal, if I understand you right, does EVERY SINGLE PERSON have the WiFi Sleep problem, regardless of which Froyo ROM they are using?

I'm running JJ and have done since the new kernel was released. There's no longer any wifi sleep issue.

[Guest Matthew Ferguson]

Sorry for being such a noob (:

how do i acess it ?

I think the easiest thing to do would be to backup your texts with an app from the market, and reflash your phone, after deleting data and cache. In future, it's not best to backup system data from other ROMs, it always causes acore to crash.

[Guest Matthew Ferguson]

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.

When you reinstall the rom, wipe the cache and data, then install it. Should work, worked for me when I had this issue.

[Guest Matthew Ferguson]

Is a wipe needed to go from RLS4 to RLS6? It has new kernel from what I understand, so that probably means a wipe. Lazy me doesn't want to go through the work of setting everything up again :D

I've been upgrading in double steps like you and so far have had no issues, so it should work.

[Guest Matthew Ferguson]

As has been said by others, It does seem to be the dialers network usage that is causing the battery problem. If I turn my wifi and 3g off my battery lasts for ever!

The dialer isn't the issue, it's people installing the overclock and expecting the phone, as it's froyo, to last longer than Eclair normally does (and by longer I mean they expect it to last days longer). I've got overclocking disabled and hw acceleration enabled and my phone lasts 2 days without a charge, and in eclair it'd last a day and a half.

[Guest Waaang]

When you reinstall the rom, wipe the cache and data, then install it. Should work, worked for me when I had this issue.

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

[Guest Matthew Ferguson]

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

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

[Guest Anjan Tek]

I'm running JJ and have done since the new kernel was released. There's no longer any wifi sleep issue.

Wow, really? Anything special or different, that you did?

Maybe I should take a nandroid backup and start from scratch, by deleting data and cache.

[Guest Matthew Ferguson]

Wow, really? Anything special or different, that you did?

Maybe I should take a nandroid backup and start from scratch, by deleting data and cache.

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.

[Guest NightSt@lk3r]

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

The battery life issues have been present with this rom since RLS1 long before Overclocking was added.

My phone can go for 3 or 4 days on a charge if i turn wifi and mobile data connection off but if i turn either of them on you can sit there and watch the battery indicator drop 1% every 1-2 minutes, this doesn't happen with other 2.2 roms or 2.1 roms.

[Guest pellen]

The dialer isn't the issue, it's people installing the overclock and expecting the phone, as it's froyo, to last longer than Eclair normally does (and by longer I mean they expect it to last days longer). I've got overclocking disabled and hw acceleration enabled and my phone lasts 2 days without a charge, and in eclair it'd last a day and a half.

Uhm. The battery history in Spare parts says otherwise. The problem (atleast for me) is that Dialer causes a high awake time which makes the battery drain faster. Also worth mentioning is that sure, I have the OC enabled kernel, but I tried out OC with SetCPU just 1 hour ago, so the Dialer problem isn't related to the OC.

[Guest Matthew Ferguson]

The battery life issues have been present with this rom since RLS1 long before Overclocking was added.

My phone can go for 3 or 4 days on a charge if i turn wifi and mobile data connection off but if i turn either of them on you can sit there and watch the battery indicator drop 1% every 1-2 minutes, this doesn't happen with other 2.2 roms or 2.1 roms.

I think overclocking might've been added with RLS1, but I can't remember. It can't be an issue with the dialer if you say it lasts 4 days with 3G and wifi off, but when you say 1% every 1 to 2 minutes, does that mean your phone averages a min of 1.5 hours, and a max of 3.5?

[Guest Matthew Ferguson]

Uhm. The battery history in Spare parts says otherwise. The problem (atleast for me) is that Dialer causes a high awake time which makes the battery drain faster. Also worth mentioning is that sure, I have the OC enabled kernel, but I tried out OC with SetCPU just 1 hour ago, so the Dialer problem isn't related to the OC.

Well I've noticed no such thing, I've got "system idle" using up most of my battery. I have the turn to forbid phone ring disabled in settings and haven't really noticed any issue with battery. Since you have the OC enabled kernel you're still overclocking the AHB.

[Guest NightSt@lk3r]

Since you have the OC enabled kernel you're still overclocking the AHB.

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.