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

[Guest screwface]

Issues:

Music player doesn't work

Contacts display incorrectly (Surnames first no matter what settings you change)

No native portable hotspot setting in the settings application.

[Guest Sebastian404]

Issues:

Music player doesn't work

Contacts display incorrectly (Surnames first no matter what settings you change)

No native portable hotspot setting in the settings application.

Did you wipe your phone before installing it?

[Guest screwface]

Did you wipe your phone before installing it?

of course my good man.

[Guest chocman]

Hi, when i change vm heap size to 48 youtube is playing in black and white not seen this with other roms.

[Guest nuvola]

I use recovery 2.5.1.8. the recovery work fine.

but I use this rom,my phone proximity is not work.

[Guest xionation]

Little Question.. Hows the battery life on this ROM anyone?

The only problem ive ever had with Froyo ROMS are the battery life

Thanks in advance :(

[Guest rbbrslmn]

Hi, when i change vm heap size to 48 youtube is playing in black and white not seen this with other roms.

I had that at 38 with mcr r4

[Guest cobhc]

Little Question.. Hows the battery life on this ROM anyone?

The only problem ive ever had with Froyo ROMS are the battery life

Thanks in advance :(

Give people a chance to test it, it only came out yesterday!

[Guest chocman]

I had that at 38 with mcr r4

it seems fine at 46, is 46 a good number to have it at?

[Guest t0mm13b]

it seems fine at 46, is 46 a good number to have it at?

Two things:

1. LED's for the home/menu key not working (can understand that there's some kernel hackery involved by comparing with the eclair??? am willing to help out nail this one down....) the return key is working fine....

2. Using the default Launcher, hold down Google Search bar, and try delete it, the behaviour looks 'different'... in that you are refused to move up the search bar, if you move it up, it appears in the bottom?! Can anyone confirm this erratic behaviour? For an example, I was trying to add the power widget, but it is fixed, in that I cannot push it up near the notification bar.... it wraps around it.... :(

Blazing fast though, I scored 951 on it which is incredible....

[Guest cartierv]

Two things:

1. LED's for the home/menu key not working (can understand that there's some kernel hackery involved by comparing with the eclair??? am willing to help out nail this one down....) the return key is working fine....

2. Using the default Launcher, hold down Google Search bar, and try delete it, the behaviour looks 'different'... in that you are refused to move up the search bar, if you move it up, it appears in the bottom?! Can anyone confirm this erratic behaviour? For an example, I was trying to add the power widget, but it is fixed, in that I cannot push it up near the notification bar.... it wraps around it.... :(

Blazing fast though, I scored 951 on it which is incredible....

Being a relative noob to Android I'm not familiar with this benchmark app everyone is using. But I thought people were posting ~400 ish for 2.1 Stock.

Sounds like the ROM I've been waiting for.

[Guest Simon O]

What's the reason for using an older kernel and not the kernel that came with the recent Froyo ROM?

[Guest paraselene]

What's the reason for using an older kernel and not the kernel that came with the recent Froyo ROM?

Hope this will answer you :(

# cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 00500000 00020000 "recovery"

mtd1: 00500000 00020000 "boot"

mtd2: 00180000 00020000 "splash"

mtd3: 00080000 00020000 "misc"

mtd4: 02580000 00020000 "cache"

mtd5: 0dc00000 00020000 "system"

mtd6: 0a280000 00020000 "userdata"

mtd7: 01500000 00020000 "oem"

mtd8: 00180000 00020000 "persist"

[Guest grygry]

What's the reason for using an older kernel and not the kernel that came with the recent Froyo ROM?

agree..... :(

[Guest Simon O]

Hope this will answer you :(

# cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 00500000 00020000 "recovery"

mtd1: 00500000 00020000 "boot"

mtd2: 00180000 00020000 "splash"

mtd3: 00080000 00020000 "misc"

mtd4: 02580000 00020000 "cache"

mtd5: 0dc00000 00020000 "system"

mtd6: 0a280000 00020000 "userdata"

mtd7: 01500000 00020000 "oem"

mtd8: 00180000 00020000 "persist"

The boot dump will be 5MB as that's the size of the partition but the actual boot.img is 3.16MB once you have removed all the blank data from the end of the file. I can't make a working boot.img using the DSIXDA kitchen app and I don't know how to make a working boot.img for the blade any other way. But I can't see any reason why the kernel itself won't work on the san francisco.

[Guest kallt_kaffe]

The boot dump will be 5MB as that's the size of the partition but the actual boot.img is 3.16MB once you have removed all the blank data from the end of the file. I can't make a working boot.img using the DSIXDA kitchen app and I don't know how to make a working boot.img for the blade any other way. But I can't see any reason why the kernel itself won't work on the san francisco.

Except that it doesn't. One thing that is different is that all blade kernels has CONFIG_PHYS_OFFSET set to 0x02a00000 while the softbank kernel has it set to 0x02600000. However I've even tried to hexedit the CONFIG_PHYS_OFFSET in the Softbank kernel but it still doesn't boot. There is propably more stuff that's different. When we get the kernel source we can propably make a working Blade kernel ourselves.

[Guest Rasped]

The boot dump will be 5MB as that's the size of the partition but the actual boot.img is 3.16MB once you have removed all the blank data from the end of the file. I can't make a working boot.img using the DSIXDA kitchen app and I don't know how to make a working boot.img for the blade any other way. But I can't see any reason why the kernel itself won't work on the san francisco.

Flibblesan: Can I get an update on my phones please?

[Guest MDCFan]

Flibblesan: Can I get an update on my phones please?

Offtopic, but I have read the page in your sig and couldn't you open a dispute in paypal or do chargeback?

[Guest Simon O]

Offtopic, but I have read the page in your sig and couldn't you open a dispute in paypal or do chargeback?

Yes it's off topic. But if Rasped want's to play games then by all means let him.

[Guest Simon O]

Except that it doesn't. One thing that is different is that all blade kernels has CONFIG_PHYS_OFFSET set to 0x02a00000 while the softbank kernel has it set to 0x02600000. However I've even tried to hexedit the CONFIG_PHYS_OFFSET in the Softbank kernel but it still doesn't boot. There is propably more stuff that's different. When we get the kernel source we can propably make a working Blade kernel ourselves.

Ah right. I did wonder if it was the kernel itself that wasn't compatible. I'll see what I can do about chasing ZTE for the kernel source.

[Guest dadashi]

Ah right. I did wonder if it was the kernel itself that wasn't compatible. I'll see what I can do about chasing ZTE for the kernel source.

people have been "chasing" ZTE for as long as the SF has been out and they still haven't released the proper kernel...maybe ask Orange...?

Edited December 28, 2010 by dadashi

[Guest kallt_kaffe]

people have been "chasing" ZTE for as long as the SF has been out and they still haven't released the proper kernel...maybe ask Orange...?

We have an ongoing dialogue with ZTE (mailinglist) where they've stated that we may get the 2.6.32.9 source before the end of this year. But yes, you are right, the stuff they've released so far has incompelete and have not even compiled without some modifcations. They also haven't released a source that supports the 5mpixel kamera (Saunalahti) even though the phones have been on the market for quite some time now.

However, asking Orange is pointless. The source we have so far does in fact cover the Orange phones (at least after fixing the broken TFT support in the source). I suppose you owned a real Softbank 003Z you could try to put som pressure on Softbank. Let's hope ZTE stays true to their word and releases the source this week.

[Guest dadashi]

We have an ongoing dialogue with ZTE (mailinglist) where they've stated that we may get the 2.6.32.9 source before the end of this year. But yes, you are right, the stuff they've released so far has incompelete and have not even compiled without some modifcations. They also haven't released a source that supports the 5mpixel kamera (Saunalahti) even though the phones have been on the market for quite some time now.

However, asking Orange is pointless. The source we have so far does in fact cover the Orange phones (at least after fixing the broken TFT support in the source). I suppose you owned a real Softbank 003Z you could try to put som pressure on Softbank. Let's hope ZTE stays true to their word and releases the source this week.

does the pope sh*t in the woods... :(

Edited December 28, 2010 by dadashi

[Guest Meizirkki]

They also haven't released a source that supports the 5mpixel kamera (Saunalahti) even though the phones have been on the market for quite some time now.

Why cannot we use the 003Z kernel? It seems to be exactly the same hardware. (5mpix camera, TFT screen)

I asked the same question yesterday but it got ignored. What's the problem with 003Z kernel?

[Guest rayraven]

@kallt_kaffe,

Anyway to disable that annoying popup when dialing calls that asks me if the call is to Japan?

Hate to keep asking but its driving me crazy, i make a good number of calls and the issue persists even with third-party dialers.

Thanks