Related
I have had my Vario III for almost a year now (used to have a Vario II before this), and I've never had this problem before.
All of a sudden yesterday, my phone screen just went dim. I didn't install anything new and it didn't fall or anything. Since then, I cant use the power button on the side to switch the screen off, and the phone simple wont charge. I've tried doing a soft reset many times.
While the phone is restarting, the screen starts off bright as usual, but while in the loading process (10 secs after it starting rebooting), the brightness goes down approx 60-70%.
If I keep the power button down for a while, I get the option if I want to switch my phone off. If I say yes, the loader keeps spinning and the phone doesn't switch off, regardless how long I wait.
The phone is still usable and all the programs still work.... but its not charging and screen wont turn off. What should I do?
By the way, I haven't changed the ROM. I still use the original ROM that came with T-Mobile.
... And you didn't drop it right? Sounds like there was a hardware failure for sure...
Any Ideas?
My phone ran out of battery now. Still not charging. Its my only phone and its annoying me. I don't know if its the ROM thats gone buggy. If I need to change the ROM on it, I HAVE to get the battery fully charged right?
I cant think of any other possibilities. Any ideas would be great.
Digital Outcast said:
... And you didn't drop it right? Sounds like there was a hardware failure for sure...
Click to expand...
Click to collapse
No, I didn't drop it. I was just using it normally and it just decided to do that. I wasn't connected to the internet at that time either.
Well the ROM on the phone wouldn't cause it not to charge. The ROM is obviously not even taken into consideration when the device is off and charging (or in your case, not charging).
Have you tried different cables to see if it is working, i.e. USB vs wall-charger?
Digital Outcast said:
Well the ROM on the phone wouldn't cause it not to charge. The ROM is obviously not even taken into consideration when the device is off and charging (or in your case, not charging).
Have you tried different cables to see if it is working, i.e. USB vs wall-charger?
Click to expand...
Click to collapse
Yup... tried different chargers and different wall sockets.
The problem I explained earlier did happen before, about a month ago, and it had same symptoms. And even then it happenned for no particular reason. But after soft resetting it a few times, it sorted itself out. This time, nothing seems to work.
Man that stinks. I hate to say it but it definitely sounds like a hardware failure
Digital Outcast said:
Man that stinks. I hate to say it but it definitely sounds like a hardware failure
Click to expand...
Click to collapse
Well... Good thing I sync'd my phone last night and transferred all data onto the memory card.
I'll just keep working on it, see if I can figure something out. If I do, I'll post the solution here for future reference. Till then, if anyone has any ideas, please let me know.
Thanx
ok so here's the situation. I know that my battery is bad but i don't know if that's causing the problem. I was working on my car today and noticed that i had a text, so when i tried to open it, the phone froze. I thought no biggie and soft reset the phone. Here's where the problem began. It was on the loading screen.....and never did anything else. So i reset again and again until i plugged it to a wall. Same thing. It eventually booted up all the way, but it was acting way too slow. It would take more than 2 minutes to respond to an input. When I tried to make a call after it was on the phonepad, it took 3 minutes to even dial the speednumber and make the call. The call went through with no events. I patiently went to my back up program to try to back up my info and whatnot and it was so slow that it didn't back anything up. Has anyone had this problem before? I hope I explained it clearly.
My current rom is Solace 3.1 from mbarvian.
The best is if you replace the battery. It can be so slow cause of the battery. But it can also be your ROM. You could try a different ROM but I wouldn't recommend that until you have a better battery.
truth be told, i was holding off on the battery until the pro touch 2 came out for AT&T, but now i think it's best, even if i don't keep the phone. I have it plugged into the wall right now and it still doesnt want to finish backing up my stuff.
Is that a 6.5 ROM?
Get a replacement battery. You can try eBay. I have had good luck with battery there.
Once you have battery, backup your data and note down all you settings and then hard reset. After reset, redo your settings, restore your data. It should be fast as new.
seems strange that it would be a battery causing the phone to lock up, normally it is a program or something that causes it. If you have the phone plugged in to the wall and it still happens then I would say " how could it be the battery when that's not the power source"..
Keep trying to back it up, then hardreset the phone.
to answer a few posts back, it's a 6.1 rom. As far as the battery goes, i left it plugged for 24hours and then when i tried turning it on, still slow as always. I'm beginning to think that it's a combination of a corrupt rom and bad battery. I NEED to back up my stuff, but i wonder how i can do it if it's acting all slow.
I think it's just a problem with the rom. Good luck backing stuff up.
ChumleyEX said:
I think it's just a problem with the rom. Good luck backing stuff up.
Click to expand...
Click to collapse
yeah no kidding. haha. i can't even access half of the stuff on that phone. I wonder what caused it to go bad after 2 months or so of use with that ROM.
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
try flashing hard spl 1.01 it looks like you got an old version of the spl. read the sticky on flashing for newbies i belive it tells you how to do the hard spl if you are having difficulty by usb connection other than that i wouldnt know what to tell you i nver had that problem only bad flashes but those could be solved by reflashing another ROM
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Make sure the battery has a good charge, nothing else springs to mind
PS. the qualcomm thing is what appears when it's flashing via USB
also maybe try formatting your SD card and put the stock ROM back on there, or try diff card
chasejones8 said:
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Click to expand...
Click to collapse
it sounds like you dont have your sd card formatted make sure its format to FAT32 go to your computer inserd sd card & reformatted (make sure its a micro sd & that its less than 2g) then transfer the ROM to the card already renamed to RHODIMG then inserd ur card on your phone & flash it. it should work. let us know what happens
MadBeef said:
Make sure the battery has a good charge, nothing else springs to mind
Click to expand...
Click to collapse
I wish I could. I have no means of checking the battery status. I've had it plugged in pretty much constantly for about the last two days.
MadBeef said:
PS. the qualcomm thing is what appears when it's flashing via USB
Click to expand...
Click to collapse
I figured that's what that was, I was just a little shocked that it said CDMA.
And I tried wiping the card and reflashing, but it did exactly the same thing.
See at the top of your bootloader readout, where it says RUUNBH? That means the RUU flag is set, and that needs to be unset before you can do other things. What you need to do is establish a connection with your device via MTTY. Follow the instructions here about how to do that. Once you get an MTTY connection established with the device (it may take awhile since MTTY is quirky sometimes), type
Code:
Set 16 0
You may need to manually soft reset afterward, but otherwise you should be in the clear
The TMO Stock ROMs can install via PC even if your phone has a faulty USB connection. The stock ROM installer will keep restarting the phone's USB connection automatically as needed if your phone can't appropriately flash in one straight attempt. You can get the newest stock ROM here. And definitely install HardSPL again after getting the phone up and running on the stock ROM.
You might also try MTTY.exe. When connected, run the command 'set 16 0' then 'task 8' then 'task 0'. If your phone doesn't automatically soft reset, then manually soft reset with the stylus.
will MTTY.exe work via parallels on a Mac? I haven't tried it yet, but I have limited access to a PC. also, I tried doing the HardSPL and the TMO rom via PC, but the phone just does the same thing. It will connect, but then the RUU tries to check the phone settings and the phone shuts off. this is the problem i am having. i just cant get it to say on long enough to do anything. I'll try the MTTY.exe through parallels and if it won't respond, I'll have to wait to try it on a PC. I'll let you know how that goes.
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
DaveTheTytnIIGuy said:
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
Click to expand...
Click to collapse
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
chasejones8 said:
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
Click to expand...
Click to collapse
I haven't had any problems with this SPL, but then again, this is the only end-user version of HardSPL for GSM devices that's been made available. The SPL isn't even your problem, the only problem is that a bootloader flag is set which shouldn't be.
As for the EnergyROM sleep of death problem, that's not what you're suffering from. The sleep of death problem is when your device won't resume after being put into standby, meaning one must soft-reset their Rhodium and lose any unsaved data in open programs. It's a somewhat common problem among many HTC devices, from the old ones like the Kaiser to the newer ones like the Rhodium (though I don't think any Android device has this problem).
jdep1 said:
try flashing hard spl 1.01 it looks like you got an old version of the spl.
Click to expand...
Click to collapse
Eh ? Sorry, but I think you're confused. He's running 0.85 HardSPL, which is the one and only version for GSM Rhodiums.
I got to a PC and tried MTTY.exe
I can't seem to get it to connect. It just says "USB port can not open."
Any suggestions?
EDIT: I can get it to connect to a different version of MTTY.exe for a short time, but I can't type anything. All I get is a blinking cursor.
chasejones8 said:
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
Click to expand...
Click to collapse
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
bfgarzilla9k said:
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
Click to expand...
Click to collapse
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
chasejones8 said:
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
Click to expand...
Click to collapse
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
bfgarzilla9k said:
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
Click to expand...
Click to collapse
thank you so much! that fixed everything. they weren't quite the same battery, the one from the HERO isn't quite as wide. it did work, though. I'm charging my tp2 now. not sure if the battery is shot or not. everytime i unplug it, it shuts off. i'll have to charge it for a while and see if that changes anything. again, thanks so much!
My nook was rooted and I was happily using it for about 3 weeks.
It was a ver. 1.0.0 model.
One night I went to turn it on and it wouldnt come on. I thought somehow the battery must have drained out. I plugged it in when I got home, but after a while I tried to start it and it still wouldnt.
What I have noticed is that the backlight comes on, changes intesity a couple times, goes off and then comes back on, like some sort of loop.
There is no message screen or N screen. There is no booting from SD, as far as everything I've tried to burn to SD and boot from.
I've tried all the key combos, some result in different variations of the backlight sequence but nothing else.
I think it is caught in some sort of loop before looking for any bootable system.
I want to try everything I (and everyone else) can think of before I go to the trouble of shipping it back to B&N.
Can you put the original stock system on an SD, even though I doubt it would boot from that either, but just a thought.
Thanks,
Phil
Looks like you are going to be enrolling in the NC advanced class. I really can't help on this but this weekend I plan one doing a the group install internally and I should be knowledgable afterwards.
Start by looking into creating the froyo image one a sdcard. There is a thread. The NC should be able to boot from that card. If it does great. Now look for thread about recovering images and using dd to write images. Someone did post the stock images 1.01
have you tried booting Nookie Froyo through an SD card? Then you could probably flash a stock rom (zip is in the forums) and restore.
Froyo
Yeah, I have Froyo on an SD card right now. Doesnt make a difference.
I have pretty much run out of things to try, unless there is some new, secret key combo that fixes everything.
I really don't think its even getting to the OS, I think I must have some real hardware failure that has nothing to do with the stock or rooted OS.
Sounds like it may be time for a warranty claim...
spiicytuna said:
Sounds like it may be time for a warranty claim...
Click to expand...
Click to collapse
i agree, if its not even getting to the point where it can boot from sd then theres nothing that i can think of that will work, at the point your at i dont think it can recognize any button input or usb data as there literally is nothing it knows how to do
Is this possibly the first successful Bricking?
I hope not!! Keep us posted on what works and what doesn't work.
Good luck, mate.
Cheers!
Received new Nook Color.
Well I did a warranty claim.
It was a very long wait on the B&N help line. I hung up and used the online chat window. That was a very long wait as well, about 25 minutes, but I finally got through.
After explaining all the things I tried and what the nook was doing, she wanted me to hold the power button for 10 seconds. I was like, "Ok, I've tried holding it for several minutes at a time, several hundred times, but what the hell." Then she wanted to know if I dropped it or not. Mine was pristine though, not even a scratch.
So finally she said I qualified for a replacement.
The deal is they give you a ups shipping label and they ship you a new Nook. If they determine that your nook got wrecked because of your own stupidity or whatever they bill you for the new one. She said the new one would ship the next day, but it didn't ship for over a week. I shipped mine the next day with the label they sent me.
So now finally I have my new nook. I haven't rooted it yet, though I probably will. I don't believe my problem was ever related to the software things I did, I dont believe that could wreck the hardware.
Also I never mentioned rooting it or anything.
Did you try burning CWR onto a SD card and seeing if it boots?
Hi everyone, I'm new to this forum (first post), I've owned my Continuum for a few months now happily with no problems. I actually love the phone! But recently I ran into a pretty big problem...
Let me give you a little background on my phone first, I have used SuperOneClick on it, to grant super user permissions, I've used the program to grant me access to the phone tethering apps that are out (currently using Open Garden), and the AdFree app in the market. I havn't used anything else in regards to 'hacking' my phone so I'm a bit confused as to why I'm getting trouble.
Anyways here's my problem, lol! Well the other day I turned off my phone and tried turning it back on and I would get a grey battery with the spinning disk, and it wouldn't turn on :\! I tried holding all the buttons, for over 10 seconds, no avail. It still turned on to the battery and nothing. I tried taking the battery out for a whiiiile and nothing. Eventually I plugged in my phone to the wall and it magically worked. Actually that's the only way I've been able to get my phone to turn on lately. It works fine once it's on but every time I turn it off the same thing happens .
So that's truly why I'm here... Is my phone 'bricked', or are these some symptoms of being 'bricked'? Are there any fixxes I can go about taking to you know...fix the problem ?
Any help would be Greatly appreciated,
Thanks everyone,
-Matt
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
detex said:
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
Click to expand...
Click to collapse
In short, you're not bricked, but there's obviously some fishy stuff happening. At this point, it would be good to determine whether it's a hardware or software issue. On that note, just a few quick questions:
1. Has anything happened (hardware-wise) recently that you're aware of? E.g. it was dropped, got wet, etc?
2. What sort of charger are you using? Is it the Samsung one that came with the phone?
3. What USB cable are you using to charge the phone? Again, Samsung original or something else?
4. Can you get into any sort of recovery (when booted, hold Vol+, Vol-, and Power at the same time until it shows the AT&T screen twice) or download mode (when off, hold V+ and V-, then insert USB cable)? This may not have anything to do with your issues, but it will help in troubleshooting.
Hello there, I found out that I wasn't supposed to really post this thread here so I went ahead and posted it in the Continuum section, where they had me do as you said, hold the vol- button and turn on the phone. It's currently "Downloading... Do not turn of Target!!!" I'm not really sure what it's doing but that's what it says (it's been doing this for 15 minutes lol). But to answer your questions, I took the phone with me on vacation this past weekend and I had it on the beach in some pretty hot weather, but I always kept it in the shade (I treat my things pretty well) so it shouldn't have gotten too hot, and I didn't drop it or get it wet or anything either! As far as the charger goes, it is the same charger that came with the phone, from Droid. And jsyk I'm with VZW if that changes anything, because I know you mentioned AT&T.
Thanks for the help , I'll let you know what goes on with the phone once it finishes doing what it's doing haha.
detex said:
Hello there, I found out that I wasn't supposed to really post this thread here so I went ahead and posted it in the Continuum section, where they had me do as you said, hold the vol- button and turn on the phone. It's currently "Downloading... Do not turn of Target!!!" I'm not really sure what it's doing but that's what it says (it's been doing this for 15 minutes lol). But to answer your questions, I took the phone with me on vacation this past weekend and I had it on the beach in some pretty hot weather, but I always kept it in the shade (I treat my things pretty well) so it shouldn't have gotten too hot, and I didn't drop it or get it wet or anything either! As far as the charger goes, it is the same charger that came with the phone, from Droid. And jsyk I'm with VZW if that changes anything, because I know you mentioned AT&T.
Thanks for the help , I'll let you know what goes on with the phone once it finishes doing what it's doing haha.
Click to expand...
Click to collapse
Oh, ok. Good luck - hopefully you find what you need in that forum.
(By the way, you'll never see the end of the downloading screen. Unless you're actively doing something to you phone (like flashing a ROM) at that screen, it will just sit there until something tells it to reboot.)
Wow, I feel like a dumbass! I've been waiting for it to do something lmao. No I'm not flashing it with a ROM or anything so should I just hold the power button or something?
detex said:
Wow, I feel like a dumbass! I've been waiting for it to do something lmao. No I'm not flashing it with a ROM or anything so should I just hold the power button or something?
Click to expand...
Click to collapse
Don't feel bad - I'm pretty sure all of us have done that same thing at one point or another.
As long as you just dumped it into download mode with the button combo you mentioned, just pull the battery out and try to restart the phone like normal. Assuming everything is the same as it is on the Captivate, you should be back to where you were.
Alright I pulled the battery out and stuck it back in, and tried turning on my phone normally and it turned on just fine. Pretty funny that it just worked just like that. Thanks lol. Also, any recommendation with what to do with my charger and the USB action it occasionally takes on my phone?
As a test, try turning on USB debugging (Settings-Applications-Development-USB Debugging) and see if you still get that set of options. You could also look on the applications menu for something about having it ask when you insert the cable, and change from that option to the one you use most often.
The only time I've had my phone do that to me in a strictly-charging scenario is when I hook it up to my car USB charger, but that's a non-Samsung charger.
Alrighty, I put it on that setting and I'll leave it that way. Hopefully it doesn't do that again, and if it does I'll try out another charger since I have two that are identical.
Thanks again for all the help,
-Matt
PS. one quick question ! What are mock locations?
You're welcome.
As far as the mock locations go, my understanding is that it lets you tell applications that your phone is a different location than what it actually is (think something like DVD regions). I'm not 100% clear on its use, but my guess would be that it either allows you to see more apps in the market than you normally would, or that you can run apps that are specific to a different region than where you are.
I see, thanks, I've been wondering what that was. See you around!