[ROM] 26/Jan r0.2: de-crossed (cheque) ROM for ZTE Blade / Orange San Francisco [froyo] [OLED+TFT]

[Guest jass0]

I am fairly sure that is the problem! I did apply r0.2 without checking the checksum. Thank you! I will post back once the r0.1 is flashed.

edit. Yes, that was it :lol: Now it works flawlessly. I'm sorry for being careless.

Edited January 27, 2011 by jass0

[Guest SWOriginal]

not going to install untill frankish releases some themes ( cant Be botherd with mucking around with it myself),

A few questions-

Facebook Contacts sync works?

Contacts Joining works?

Messaging app enables you to select multiple contacts?

I only ask as this is what KK fixed his self by building the contacts app & messaging from AOSP...

[Guest whatcolour]

Facebook Contacts sync works?

Contacts Joining works?

not tested

Messaging app enables you to select multiple contacts?

yes

[Guest SWOriginal]

Facebook Contacts sync works?

Contacts Joining works?

not tested

Messaging app enables you to select multiple contacts?

yes

Thanks :lol:, can someone on R1 test the other 2 please :)

[Guest maximus121]

does this rom works ok with sendinh mms ?

my latest rom didnt send mms. only receive..

[Guest edge123]

Internet (or more specify DNS servers) doesn't work over WiFi :lol:

/data/data/com.teslacoilsw.quicksshd/home # traceroute google.com

traceroute: bad address 'google.com'

So DNS doesn't work.... But...

/data/data/com.teslacoilsw.quicksshd/home # traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.137.1 (192.168.137.1) 2.997 ms 2.307 ms 1.633 ms

2 192.168.1.1 (192.168.1.1) 8.948 ms 5.910 ms 8.988 ms

3 * * *

4 * * *

5 * * *

6 * * *

7 94.25.127.53 (94.25.127.53) 50.403 ms 53.477 ms 51.609 ms

8 87.226.133.178 (87.226.133.178) 94.792 ms 108.127 ms 96.145 ms

9 79.133.94.38 (79.133.94.38) 88.627 ms 82.903 ms 86.550 ms

10 72.14.239.254 (72.14.239.254) 134.110 ms 145.236 ms 135.040 ms

11 72.14.236.251 (72.14.236.251) 154.494 ms 152.593 ms 152.065 ms

12 209.85.254.112 (209.85.254.112) 152.540 ms 150.800 ms 150.352 ms

13 209.85.254.126 (209.85.254.126) 157.383 ms 161.613 ms 209.85.249.162 (209.85.249.162) 152.552 ms

14 * * *

15 * * *

17 * * *

18 * * *

19 * * *

20 * * *

When using 3G everything work fine. The DNS problem present only with WiFi connection.

:)

[Guest fonix232]

Internet (or more specify DNS servers) doesn't work over WiFi :lol:

/data/data/com.teslacoilsw.quicksshd/home # traceroute google.com

traceroute: bad address 'google.com'

So DNS doesn't work.... But...

/data/data/com.teslacoilsw.quicksshd/home # traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.137.1 (192.168.137.1) 2.997 ms 2.307 ms 1.633 ms

2 192.168.1.1 (192.168.1.1) 8.948 ms 5.910 ms 8.988 ms

3 * * *

4 * * *

5 * * *

6 * * *

7 94.25.127.53 (94.25.127.53) 50.403 ms 53.477 ms 51.609 ms

8 87.226.133.178 (87.226.133.178) 94.792 ms 108.127 ms 96.145 ms

9 79.133.94.38 (79.133.94.38) 88.627 ms 82.903 ms 86.550 ms

10 72.14.239.254 (72.14.239.254) 134.110 ms 145.236 ms 135.040 ms

11 72.14.236.251 (72.14.236.251) 154.494 ms 152.593 ms 152.065 ms

12 209.85.254.112 (209.85.254.112) 152.540 ms 150.800 ms 150.352 ms

13 209.85.254.126 (209.85.254.126) 157.383 ms 161.613 ms 209.85.249.162 (209.85.249.162) 152.552 ms

14 * * *

15 * * *

17 * * *

18 * * *

19 * * *

20 * * *

When using 3G everything work fine. The DNS problem present only with WiFi connection.

:)

Check build.prop for a line saying

wlan.default.dns[N]=[IP]

where [N] is a number while [iP] is a valid IP address. If it is commented out (so begins with a sharp, #) then IDK what is it, if it isn't commented out, edit and try restarting.

[Guest Ibcus]

ping works

# ping google.com

PING google.com (74.125.230.112) 56(84) bytes of data.

64 bytes from 74.125.230.112: icmp_seq=1 ttl=52 time=25.8 ms

64 bytes from 74.125.230.112: icmp_seq=3 ttl=54 time=41.8 ms

64 bytes from 74.125.230.112: icmp_seq=4 ttl=54 time=24.4 ms

[Guest edge123]

# getprop | grep dns

[wlan.default.dns1]: [168.95.1.1]

[net.change]: [net.dnschange]

[net.dnschange]: [2]

[dhcp.wlan0.dns1]: [192.168.137.1]

[dhcp.wlan0.dns2]: []

[dhcp.wlan0.dns3]: []

[dhcp.wlan0.dns4]: []

[net.dns1]: [192.168.137.1]

p.s. on JJ ROMs evething worked fine :lol:

p.s.2 I have notebook and WM phone connected to this AP. There's also no prob.

[Guest edge123]

Hmm... there's something I can't get...

I'm changed default DNS to 8.8.8.8 (google dns) and it doesn't help ;(

# setprop wlan.default.dns1 8.8.8.8

# getprop | grep dns

[wlan.default.dns1]: [8.8.8.8]

[net.change]: [net.dnschange]

[net.dnschange]: [213]

[dhcp.wlan0.dns1]: [192.168.137.1]

[dhcp.wlan0.dns2]: []

[dhcp.wlan0.dns3]: []

[dhcp.wlan0.dns4]: []

[net.dns1]: [192.168.137.1]

# nslookup google.com

Server: 0.0.0.0

Address 1: 0.0.0.0

nslookup: can't resolve 'google.com'

What can be wrong?

[Guest edge123]

getprop | grep dns

[wlan.default.dns1]: [8.8.8.8]

[net.change]: [net.rmnet0.dns2]

[net.dnschange]: [222]

[dhcp.wlan0.dns1]: [8.8.8.8]

[dhcp.wlan0.dns2]: []

[dhcp.wlan0.dns3]: []

[dhcp.wlan0.dns4]: []

[net.dns1]: [8.8.8.8]

[net.wlan0.dns1]: [8.8.8.8]

[net.rmnet0.dns1]: [8.8.8.8]

[net.rmnet0.dns2]: [8.8.8.8]

[net.dns2]: [8.8.8.8]

Doesn't help either ;(

[Guest Len Ash]

Couple of observations...

Couldn't log in to Google Account with WiFi connected, no way, no how. No 3G near me, but 2G worked. Had to switch WiFi OFF, reboot. Not just switch WiFi off... go figure.

FIXED: GPS fine, Maps fine, but Navigation via Car Home (a bit vital for me) sits permanently with "Checking navigation availability"...

Fix - hit restore defaults in app.... oddballs

Edited January 27, 2011 by Len Ash

[Guest sumdumguy]

edge123, try this.. settings/aplications/manage applications/all/browser/clear the cache, clear data

don't bother clearing the cache from inside the browser settings, don't work

[Guest Sebastian404]

well, my mood has not really gotten any better....

I've broken the F key off my keyboard, that means another argument with apple store...

Also I'm in a hotel tonight trying to re-upload the file.. 4KB/sec....

Im going to leave it going over night, hopefully it will be done in the morning....

[Guest jt_mcg]

well, my mood has not really gotten any better....

I've broken the F key off my keyboard, that means another argument with apple store...

Also I'm in a hotel tonight trying to re-upload the file.. 4KB/sec....

Im going to leave it going over night, hopefully it will be done in the morning....

Wednesday Morning :lol:

Thanks and sorry about your F key.

[Guest Len Ash]

Another observation

After an overnight sleep, WiFi did not reconnect. However, noticed that WiFi sleep policy was set to "Never" by default, will try later with my much preferred "When screen turns off"

(JJ9 and R11 MCR both reconnect after overnight sleep)

Edited January 28, 2011 by Len Ash

[Guest edge123]

edge123, try this.. settings/aplications/manage applications/all/browser/clear the cache, clear data

don't bother clearing the cache from inside the browser settings, don't work

Doesn't help. It's not an APK problem. There's something wrong with kernel\wifi driver and DNS.

[Guest Sebastian404]

Ok, link on the first page updated... please CHECK the MD5 before you install!|

[Guest socialworker]

@edge123

DNS works just fine here, I really think it's a problem with your ap.

I noticed maybe a little bug with coarse positioning:

It's off about 10 km from where I really am, anybody else can confirm this?

The distance seems to be always the same and moves with me, looks like there is some kind of fixed offset :-)

If I turn on the actual gps it's spot on in seconds.

[Guest Len Ash]

Ok, link on the first page updated... please CHECK the MD5 before you install!|

The Rapdshare d/l hash is OK...

[Guest ZakMcRofl]

I dont have the documents to hand, but I'm fairly sure that's 'expected behaviour', they want you to register over the air... its not a 'fix' your looking for but a 'work around'....

If it was expected behaviour (not activating via Wifi) I'm sure Google would have implemented a proper error message for it. As it stand it just waits/tries for a while and then complains about an unstable network connection.

Anyways, this clearly isn't a showstopper as most people will configure their APN first. It's just a little confusing.

[Guest dannejo]

This rom is so perfect that it wont let me sign in with my google account..

tryd both r0.1 and r0.2. My internet connection works fine.. I have tested with and without wifi, doesent help.

Edited January 28, 2011 by dannejo

[Guest mELIANTE]

Testing this right now.

Made some changes to the rom but until now it is extremely stable. Been using Jellyfish for a couple of days and had some stability issues, hope it gets better with this one, as I bet it will, Seb404's roms never let me down :lol:

[Guest manji]

Any news, mELIANTE?

[Guest mELIANTE]

Any news, mELIANTE?

Yeah. No reboots until now, still can't have an opinion about battery life but I have hw acceleration enabled and other modifications so it wouldn't be a consideration about a stock de-crossed rom.

Anyway, it doesn't have A-GPS toggle switch available, but GPS.conf has A-GPS settings so I bet A-GPS is there, only it is always on when GPS is enabled.

Messages app is different from the one in JJ, it has a contact frame next to the contact imput box but if you press it nothing happens, you can't use it to add contacts to message.

Overall, I'm liking this better than JJ, mostly because stability issues that I was having with JJ, but that could be only with me and might not have to do with the rom itself :lol: