yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nerdino:
Found this thread with a search for the same problem (not specific to device so rather than start a new thread I have added here)... couldn't find a proper fix for it though!

I have two folders with several apps in them. I do not want to have to remove and then replace each app that has had its icon replaced with the generic android icon - that would be an utter ball ache!

Does this issue arise due to apps being on the SD card? (I use Apps2SD). Is there some sort of icon memory cache that gets wiped every now and then for icons in folders? Could it be program updates?

This is perhaps only a small thing but it makes my carefully constructed specific folders look rubbish, and should be easy to fix with some sort of "refresh" command maybe?

My Sensation XE is unrooted and it is only the icons in folders that suffer this problem.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Erykwidday:
I have the same problem as above also on Sensation. It only happens when I move an app to the SD card and put it in a folder. Does Anyone have any solutions?
[Nexus S Q&A, Help & Troubleshooting] insanemachine:
The phone is unlocked, and I believe all nexus s come with a Tmobile SIM in the US, since it will only work on Tmobile's Network for 3G. From what I can find about NTT DOCOMO, it sues 3G 2100 band, so i don't see a reason why it would not work.

http://www.mobileworldlive.com/maps/network_info.php?nid=5234&org_id=4222&cid=3027#ninfo
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
Hi, thanks for the reply. Honestly I have no clue whatsoever why it won't work either. But as I mentioned it's not just the Nexus S, it's also every other phone I've bought (save for the HTC Mini as mentioned) and even some that I tried out and didn't buy because they didn't work. Docomo just keeps spitting out their lame "We can't be sure about any phones not sold by Docomo" excuse that basically amounts to them lacking the technical expertise to answer a basic question about their own network infrastructure.

I can't even begin to express how infuriating this is, because Japan is so horribly behind the times with mobile phones. It's ironic that the country that basically created mobile technology has no ability to further it's development. I remember coming here in 2003 (I'm from the US) and was blown away at the phones having 3G, front facing cameras, VIDEO chat, etc. Yet lo and behold Japan only got LTE THIS month (and only via DOCOMO's USB dongle at that) though to be fair it had Wi-MAX since last July (though to this day there is not a single phone that uses it).

We just got the Galaxy S at the end of October for crying out loud. People here want garbage like 1Seg wireless TV and the mobile wallet (Stored Fare) system and thus the Japanese manufacturers (specifically Sharp and Toshiba) have made phones that have said features but they are just plain awful. Sharp in particular can't seem to make phones that work efficiently as the Lynx and Galapagos models are quite unresponsive. So naturally I want to get something like the Nexus S because it's both state-of-the-art and (IMHO) a great phone.
[Nexus S Q&A, Help & Troubleshooting] dinan:
Can't really help you much but based on the specs those phones you got should technically work on the networks there...

I've been to Tokyo with my Nexus One but left my AT&T sim in it (yea I was using AT&T in the US when the phone was meant for T-mobile) and we desperately had to use Google Maps since we were lost in Roppongi... so I bit the bullet and enabled data roaming and it picked up a 3G signal and was actually quite fast for the few minutes I used it. That's all the help I can offer, sorry, lol.
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
Thanks for the reply...I think perhaps it worked for you because of roaming agreements and whatnot between AT&T and Docomo.

I can't be sure, but something tells me that the Japanese carriers actually ban foreign mobiles from accessing their network directly via IMEI, but that fails to explain why the HTC Mini worked without a problem.
[Nexus S Q&A, Help & Troubleshooting] harveydent:
I have the feeling that you need to enter a specific set of connection settings for DoCoMo.

You mentioned that the HTC mini worked just by inserting the SIM card. On my Xperia X1 (also WM), it would automatically change my settings depending on which SIM card/carrier I inserted. Why don't you insert your DoCoMo into the Mini, copy the connection settings (manually copy all the values) and then use them on the Nexus S?
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
Thanks/Problem Solved

Thanks to everyone who offered help. I've no idea why, but the APN "MOPERA U" worked, though it didn't originally the first dozen-or-so times I tried.
[Nexus S Q&A, Help & Troubleshooting] mingkee:
As far as the 3G bands go, NS can take band I/IV/VIII while Japan uses I/V/IX (850/1700-1800/2100).

Band IV runs on 1700+2100 aka AWS.
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
[Q] Quick Carrier Question (Unlocked...TMobile?)

Hello. It's been ages since I've been in the USA and thus have become somewhat unfamiliar with some aspects of the telecommunication companies.

Can someone explain why it is that the [unlocked] Nexus S will only work with TMobile? Does this have to do with their network infrastructure? How is it possible that with all the bands the Nexus S supports, it only works with T-Mobile? I don't even understand why Google would sell an unlocked phone if (for US residents) it ONLY works on the one carrier. They might as well lock it.
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
The phone will work on any GSM network for voice.

It will work on any GSM provider for EDGE.

It will only work on T-Mobile in the US for 3G/HSPA because it doesn't support all 3G bands (like AT&T uses 850 and 1900, neither of which is on the Nexus S).

Edit, here are the frequencies it supports: GSM frequencies 850 / 900 / 1800 / 1900 and HSDPA frequencies 900 / 1700 / 2100.

A lot of people get confused because they think the GSM 850/1900 means it should work on AT&T, but that's voice/EDGE only. Different radio for the data side.
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
Ah, I see. Thanks. It's funny, when I lived in the US and had T-Mobile (up to around 2006) it was by far the worst carrier with absolutely HORRID reception.
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
It still is. LOL.

Actually, like every other cell carrier, it just depend on where they live. T-Mo's great near my office, it sucks at my house.

P.S - as someone pointed out in your other thread I just read, T-Mo uses AWS for 3G...it splits the up and down traffic over the 1700 and 2100 data freqs. I don't know if it will actually work on an exclusive 1700 or exclusive 2100 network.
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
I did a test on it, it will not work, it only gets EDGE

you need both bands 1700+2100 to work properly to get 3G
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
Make sure the Cell Phone Service Provider works with 1700 + 2100 to get 3G

it will NOT WORK if you only have 2100 or only 1700

it needs both to do a proper AWS connection
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
So the phone doesn't really support 1700/2100, it supports AWS (1700+2100). That's not surprising, but the specs can be confusing, especially since on some phones they say AWS/1700/1900/2100...differentiating between AWS and 1700 or 2100.

What network did you test it on?
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
my test, might have been inaccurate

I tried my Bell, Fido, Rogers SIM on the SNS (900/1700/2100), it all worked, but was EDGE only at best

I also tried the WIND (Tmobile) SIM on the SGS (850/1900/2100) it briefly gave a bleep of 3G indicator then it went away

so my theory was that WIND should work on 2100, but nope, it needed the 1700 to form a proper 3G connection

... my real intention was to keep using my SGS i9000m, if the test was successful :p

seems like now my choices are either stay with the SNS or go with the SGS SGH-T959
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
That's the T-Mo US Vibrant, right? I love that that phone will work on T-Mo and AT&T 3G (1900 only) here in the states. I got my friend one to use on AT&T. Ironically, he hates it and usually uses his crappy old iPhone 3G (he just can't make the paradigm shift from iOS to Android). I've told him he should give it back to me, but he won't. LOL.
[Nexus S Q&A, Help & Troubleshooting] gns168:
Congrats, but you should be wary of huge data charges.

I have an SGSVibrant (Bell) and took it to Japan as well last November. It seems that docomo blocks non-docomo imei (hence you can connect for a split second initially) and you "should" have needed (because you seemed to have gotten it to work now) to get a docomo employee to unblock the imei. It only cost ~400yen.

BUT, if it is a non-docomo phone it is not covered by any of the flat rate unlimited data plans but subject to per $/Mb tethering charge (read. HUGE costs). Search the SGS forums for a more detailed discussion (can't find it right now, sorry)
[Nexus S Q&A, Help & Troubleshooting] mingkee:
The frequency number thing is too confusing for 3G, so using band code is much more ideal.

T-Mobile and Wind use band IV

ATT, Bell, and Rogers use band II and V
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
ironically i find these band things even more confusing

the band numbers might be geeky but it goes straight to the point, and it's a way easier to remember than remember which carrier is on which band block, which makes you wonder what's the real frequency behind

Phone advertisement and spec sheets don't sell them listing band grouping, rather they advertise by the actual frequency
[Nexus S Q&A, Help & Troubleshooting] samoya22:
Unlock and Root

You may need to unlock and root the phone before you can use it with other providers. So far as I can tell, an OEM unlock might be all you need.

Just google: How to OEM Unlock and Root Nexus S.

Because I'm new, I can't post links.

-J
[Nexus S Q&A, Help & Troubleshooting] jivemaster:
That's not correct. It should work out of the box. His problem is network provider related. No oem unlock is required.

-Joel
[Nexus S Q&A, Help & Troubleshooting] sisconda:
So is this thread confirmation that the Nexus S does work with voice/data in Japan using Docomo service but with a MOPERA APN that you have to manually set?

I live in the US and own a Nexus S but am planning a trip to Tokyo/Kyoto sometime in March and was wondering if I could just go there and pick up a simcard rather than buying a prepaid phone while there.
[Nexus S Q&A, Help & Troubleshooting] rassam:
u need a jap id card to be able to get a Pay as you go sim.

unless you know someone here who can use their alien ID card to get one for you then forget it. its strange here i know.

I suggest Donkeyhoteh which is a cheap department store that sells everything. usually they stock paug softbank sims. the phone shops them selves dont sell them.
[Nexus S Q&A, Help & Troubleshooting] prnoct90:
So I am thinking about ditching my iPhone. I really want to purchase a Nexus S. Does anyone know if the Nexus S is confirmed as working on any of Japan's Networks? Softbank, AU, or Docomo? I am currently using Softbank, so if it works on them, that would be the best.
[Nexus S Q&A, Help & Troubleshooting] TokyoGuy:
The Nexus S will work with Docomo, if you have Mopera service.
[Nexus S Q&A, Help & Troubleshooting] cavanman:
You can rent Sims at the airport. Some are free for incoming calls and usually charge $1+ /min outgoing. They also have data plans.

You'll need to pre reserve. Plenty of different vendors. Search for sim rental narita. I rented one last summer. It was easy.
[Nexus S Q&A, Help & Troubleshooting] kuroneko007:
I'd use the Nexus S on Softbank. You can just put your iPhone SIM into the Nexus S (if it is an iPhone 3xx).

Softbank doesn't do the IMEI filtering thing, so no problem. There is, however, a separate APN for iPhone (black) SIMs and for other SIMs. The iPhone one is smile.world, and the standard one is open.softbank.ne.jp; so if you have an iPhone contract you'll want to stick with the first one.

Docomo will charge ANY phone that wasn't bought through them 10,390 yen a month for data plan. It is a very expensive option.
[Nexus S Q&A, Help & Troubleshooting] corizo:
Are you sure on this? I would be very happy if it is, cause I'm in Japan from August for a year again and just bought me Nexus S.
[Galaxy S I9000 Android Development] Chainfire:
I9000M_JL2_JL2_JL2_JL2_UG_BMC

ro.build.date = 2010.12.21 23:29:56 KST

ro.build.fingerprint = samsung/GT-I9000M/GT-I9000M/GT-I9000M:2.2/FROYO/UGJL2:user/release-keys

http://www.multiupload.com/UTFJCCIP5H

NOTICE: I do not have this device model, nor have I tested the ROM, I'm only telling you where to find it.
[Galaxy S I9000 Android Development] tjsooley:
anyone know if this is 2.2 or 2.2.1?
[Galaxy S I9000 Android Development] zorxd:
BMC? So it's a Bell Mobility Canada ROM?
[Galaxy S I9000 Android Development] tjsooley:
what is the file SBI.bin
[Galaxy S I9000 Android Development] Felixpau86:
Looks like bell. Lets hope bell users can finally upgrade
[Galaxy S I9000 Android Development] montrealguy:
Someone said it was already on Kies, but this is what I get:

JK4: "This device's version cannot be upgraded."
[Galaxy S I9000 Android Development] Chainfire:
See "fingerprint", it's 2.2.

Probably, but I'm not sure.
[Galaxy S I9000 Android Development] AllGamer:
look at the updated GUIDE sticky
[Galaxy S I9000 Android Development] SaneinOne:
@Chainfire Awesome, thanks very much for posting!
[Galaxy S I9000 Android Development] spectre85:
It's showing up for me on kies, obviously you need to do the registry hack.....i'll give it a go over lunch and let you guys know if there is anything different from JK4.....
[Galaxy S I9000 Android Development] spectre85:
Yes, BMC means Bell Mobility Canada, check the screen shot. I used the reg hack to spoof JG9 and also used BMC

http://flic.kr/p/93Q4dV
[Galaxy S I9000 Android Development] mssmison:
I'm just charging up my battery, I'll give it a shot when it's charged if no one else has.
[Galaxy S I9000 Android Development] montrealguy:
Already loaded it. It kills the GPS. No GPS lock at all, despite different settings! It detected 1 satellite when normally it detects 10.
[Galaxy S I9000 Android Development] mssmison:
did you notice anything else different?
[Galaxy S I9000 Android Development] montrealguy:
Yes- there are weird force closes sometimes when you restart. If you touch anything on the screen it will go completely blank. Now I wait until everything loads until I touch anything.

Seems less stable than JK4. I'm wondering whether I should revert to JH2 before my SD card crashes.
[Galaxy S I9000 Android Development] montrealguy:
Just an update: I've tried many different GPS settings on JL2 and the GPS does not work. The best setting I got was with Auto-config + secure socket and even then it found 3 satellites and never locked on for 15 minutes.

Does anyone have another solution? Can I load a GPS kernel from another ROM? JPO had worked perfectly.
[Galaxy S I9000 Android Development] spectre85:
for me personally my GPS got ****tier after going from 2.1 i'm running JK4 right now and it's OK but not like it was in 2.1. i'm going to give this a shot and see how my device fairs. my hardware is an august build or earlier so might affect my device differently. not sure, will report back though
[Galaxy S I9000 Android Development] spectre85:
LOL....after downloading the binary Kies tries to decrypt it and I get an error that says "crypto error" that's it. so looks like i'll be running JK4 for a while longer now, not that it's a huge issue, This one is apparently only 2.2.....still waiting for the 2.2.1 with the upgraded kernel.
[Galaxy S I9000 Android Development] montrealguy:
The crypto error is a known problem- it just means that the download got interrupted and the files were corrupted. Just keep on trying until it works. The problem is on Samsung's side, not yours.

I got the crypto error, but it worked on the second try.

Be forewarned though- this firmware has problems. See my posts above.
[Galaxy S I9000 Android Development] dm-digital:
I'd give this a try but I've been flashing so much lately and it's just becoming a pain. I'm currently running JK3 as I've found this to be the best firmware so far. Great battery life, fast w/no lag, good GPS and stable. JH2 was good but didn't have the 2.2 features I wanted. JK4 wasn't very good, unstable at times, random wifi issues and used battery at twice the rate of JK3.

The next ROM I flash will either be the next official if it greats good feedback or CM7/AOSP Gingerbread when it's available.

I'm still curious and looking forward to hearing more reports from users running JL2.
[Galaxy S I9000 Android Development] galaxywolf:
did they disable gps testing code *#*#1472365#*#* on jl2, cuz it doesnt seems to work?
[Galaxy S I9000 Android Development] shadoslayer:
If you flash a custom rom though cwm from jl2, you should be ok, but there are around 8 pages in this thread about problems flashing back to JH2 or similar and problems with roms that do not include dbdata or sbl.

I strongly suggest reading through those pages so you know what you're getting in to if you get stuck in a galaxy s logo-loop.
[Galaxy S I9000 Android Development] lgkahn:
different on froyo.. try this

*#3214789650#
[Galaxy S I9000 Android Development] galaxywolf:
Thx it work, wander y they change it
[Galaxy S I9000 Android Development] SaneinOne:
Refer back to my previous post in this thread.
[Galaxy S I9000 Android Development] pervert:
Flashed JL2 lastnight with odin on a bricked phone. it just died (during a backup while i was still downloading the new rom). before the jl2 was finished, i tried jk3 but nothing. when the rom finished downloading, i flashed:

no repartition

+bootloader

pda with the jl2 tar selected

I had to reset/wipe from recovery to get jl2 fully booted.

This rom might save a lot of phones. now i'm back on jpy, and happy that the phone works. Hopefully the internal memory issues are fixed permanently, but even if i can simply recover from a /system corruption with this rom, i will be content. just keep backups :)

since the phone died some time during my backup, i was unable to restore everything but c'est la vie.
[Galaxy S I9000 Android Development] xxgg:
Has JL2 bricked any i9000M's yet ?

Just wondering about the failure rate with JL2
[Galaxy S I9000 Android Development] Samdroid_G_S:
Well its been about a week or so and I have not heard many complaints about JL2 and I follow nearly every Bell thread, I used it for a week but switched to a custom rom cause I like the themes/animations well and blue tooth was giving me problems but a factory reset may have fixed that but im unsure cause I never bothered trying. Ive flashed this new 10.12 replacement phone at least 10 times or more since I received it dec 23 , soft bricked it once but easily revived it with JL2 it was not the sd error though, just a modem flash gone wrong. It is possible it was something software related causeing the sd to die and it seems like it since theres not any complaints of JL2 killing a phone yet, where jk4 there were phones dyeing within the first 24 hours.
[Galaxy S I9000 Android Development] jojo le popo:
modem file

JL2 working great here... have a little problem though : voice calls and mobile network aren't working with my videotron sim card!

I guess I need to change the HSPA/UMTS frequecies of the phone from 850/1900/2100 Mhz to Videotron frequencies (1700/2100 MHz --> Band I (2100); Band IV (1700); Band II (1900)

From what I've read in the forums, I have to flash a modem file using Odin in order to change the phone frequencies.

The T-Mobile Vibrant uses 1700/2100 MHz bands... but I'm not sure JL2 has been released in the US, so not sure i can find a compatible modem file...

Well, I'm not too sure how to solve this, if anyone has a clue it would be greatly appreciated.
[Galaxy S I9000 Android Development] zorxd:
I don't think you can do this. It's not only software, it's also hardware.
[Galaxy S I9000 Android Development] zshakespeare:
The T-Mobile Vibrant, and the Bell Vibrant are two completely different devices with different antennas. Which do you have? If you have the Bell Vibrant it will not, nor will it ever work on videotron's network.
[Galaxy S I9000 Android Development] mad2x:
I did the jk3 update with odin a while back. I dont have any issues with my phone yet. Im wondering if i should bother with jl2. Only reason i can see is to prevent the sd card defect. But if i do the upgrade through kies will it save everything ive got on my phone?
[Galaxy S I9000 Android Development] GOTFrogqc:
It did when I went from JK4 to JL2
[Galaxy S I9000 Android Development] brynm:
So far pretty happy with JL2 flashed on Dec 24th.

Last couple days though I am having a lot of trouble with Social Hub / Samsung email. When I try to open it my phone will vibrate and come up with samsung email just under the notification bar, then vibrate twice and pop with a Force Close error saying:

I've tried a factory reset, downloading the latest version off Samsung Apps, wiping data, and wiping cache. It will sometimes work for a day and then have the same issue again.

Any ideas? Anyone else having problems?
[Galaxy S I9000 Android Development] adamge:
brynm, Hi. Can you explain why you use those two programs? I have a SGS on Sasktel as well and am still learning the many ways to use it. I use the default email program, and default text messaging program. Are the Samsung programs better?
[Galaxy S I9000 Android Development] shadoslayer:
social hub is basically an app that throws email, facebook, etc all into one program... a big meh for me, but some people like it.
[Galaxy S I9000 Android Development] jojo le popo:
Gt i9000m... So theres no hope? Thanks for the help!
[Galaxy S I9000 Android Development] Lokks:
\

I am having the same problem as well with the Bell Samsung Vibrant, my wifi does not work either it. I fix the Samsung hub issue by re-downloading the the app from the Samsung apps.
[Galaxy S I9000 Android Development] brynm:
Never really used the regular email client. I just liked the way that Samsung Email was set up for having multiple accounts.
[Galaxy S I9000 Android Development] jirkaz:
I have a quick question.. I have bought a Bell Vibrant phone SIM/Network unlocked and I am using it on Rogers network. If I upgrade to jL2 Froyo, will my phone stay SIM unlocked or will it get locked to Bell ? Thanks Jiri
[Galaxy S I9000 Android Development] Biffin:
Nope, you will still be unlocked. I am with Rogers as well and have had no issues upgrading or flashing different custom roms.
[Galaxy S I9000 Android Development] ovt:
Waking from the dead...

Well, I have a 10.09 hardware. I came with Eclair (2.1).

I upgraded it to JK4 via Kies as soon as it came out (10.12). The internal sd crashed less than a week later. Some apps were still running, download and recovery modes were also functional. Camera, music player and others that depend on the sd were down. The external sd was also unaccessible. Format did not work for both cards.

I upgraded to JL2 again via Kies. It did'nt help.

Then flashed speedmod K9A 256 via Odin 3 v1.7. In the beginning it kept giving me the same error messages for the sd format/f.reset. After a couple trials, including a format on the external card (recovery mode on the speedmod kernel has lots of options) - detail: I had taken the external card out before anything - it showed me that amount of memory after boot-up. That was the clue for a format within the OS. It came alive!

Just flashed JL2 with Odin afterwards. Working beautifully. Now it's the matter of data recovery.

Will have a beer! :D:D:D
[Galaxy S I9000 Android Development] jirkaz:
Thanks - I am glad that somebody is in the same situation and tried it. I have inquired at the place I purchased the unlocked phone (newayci) and was told that the phone will get re-locked to Bell after upgrade (did not make sense to me)