Users hoping to use a wired connection to display the contents of their Samsung Galaxy S III onto their TVs will have to purchase an entirely new and updated MHL connector to connect the newly launched smartphone via an HDMI connection tot heir HDTV. Unfortunately, Samsung had made some changes to the device’s connector pins that makes the Galaxy S III incompatible with older MHL connectors, like those used on past Samsung phones like the Galaxy Note or Galaxy S II
Previous MHL Connector bought for my G Note cannot work
i mean i want to flash back to the rom before the custom rom... so can i nandroid recover to go back to prior rom or i have to flash back the stock rom then only recover from nandroid?
Don't really understand what you want Stock rom if you have done a nandroid backup you can easily restore it from recovery restore If you forgot to do it which is a big carelesss mistake you can flash it using odin in pc or using mobile odin Always keep such a backup of stock rom through recovery mode backup
Haha... That is what i am referring to. Ok here is the detail...
I wAnt to flash a rom.... I want to flash back stock rom if i dont like the custom rom...
I have done nandroid backup... Now i flash the custom rom... Find the rom not suitble i wnt to restore back my stock rom... So the question was can i restore back the stock rom via the nndroid backup or do i have to flash the stock rom again instead of restoring back...
If i use via nandroid method... I select the restore at cwm right?
Just select restore your stock backup at recovery restore will do
Uncle benny, the page i'm refering to is after the "Book A Flight" page, followed by "Departure" option whereby we need to select an airport (Please select an airport). When I click that, it will show a list of departure airports available. At that page, the screen is dark bluish in colour. It's at that page that it shows this discoloration at the middle part as per my previous picture. Pls do try to set brightness level to highest to easily spot this problem. Thank u very much for ur time..
P/s: I have done all the tests at *#0*#, but could not detect this problem at that test.
I am still outside without my S3 with me. Tested with my G Note again at max brightness quite same as your S3 - at center part can see some greenish lines; so I think is an app issue here
This is a debatable topic. Personally I don't use any Task Killers. The official stand from Google is Task Killers are unnecessary for Androids. I quote from Google :
By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications. A content provider is active only while it's responding to a request from a ContentResolver. And a broadcast receiver is active only while it's responding to a broadcast message. So there's no need to explicitly shut down these components. Activities, on the other hand, provide the user interface. They're in a long-running conversation with the user and may remain active, even when idle, as long as the conversation continues. Similarly, services may also remain running for a long time. So Android has methods to shut down activities and services in an orderly way.
Many users still having Windows mentality and find it difficult to change. They still think Android works like Windows. Those who come from Mac OSX might be able to accept the concept of not using task killers better
Almost everyone has used these at one point in their Android life. And in most cases, reps at carrier retail stores will install these upon buying any of their Android phones with or without your knowledge. Its part of this HUGE misconception that Android needs these to run properly. Couldn't be further from the truth.
Everyone knows one of the main benefits with Android is the fact that it, unlike certain other OS's, can run apps in the background. And the more RAM on your phone, the more apps you can have open at one time for true multitasking. This is one of the reasons RAM is a highly sought after spec when comparing Android devices.
Most people know Android sucks when it comes to battery life. It's definitely a problem in Android. We know this. The misconception a lot of people have is that the reason for the horrible battery life is largely in part because of all the apps "running" in the background. This is one of the reasons these misinformed reps install these Task Killer apps onto phones thinking they're helping, but they're not. First, Android doesn't necessarily keep apps "running" in the background like a car. Using gas/CPU without you knowing. Android will pause those apps until you return to them. If you don't come back to the app for awhile, Android will eventually close the app altogether.
The other misconception people have with using a task killer is that it's some how making their phone faster. This usually has something to do with the thought that "freeing up RAM" is going to make your phone speedier and quicker when doing everyday tasks (I used to believe this as well). But not so. First off, even if you close out 20 apps in the background, 20 more will open up in their place. Like Bebe's Kids. They don't die -- they multiply. Resistance is futile. Second, it's not like Android keeps running apps in the background until you're completely out of RAM. That would cause your phone to completely freeze and lock up. Instead, it will begin closing the oldest apps still open in the background to make space for new ones. I mean think about it, do you have to manage the RAM on your home computer? No. It just works, right? Same with Android.
But just like your computer, there are those times when things go wrong. Sometimes an app can misbehave and become unresponsive. Or perhaps you changed some options in an app and it needs to be closed/killed/stopped so that it can be opened and refreshed. Or maybe you have a game that has gone rogue and really is, in fact, running in the background sucking CPU and RAM and causing your phone to run to a crawl. It's only in these rare occasions that using a task manager is acceptable. Even then, for your average user, a simple reboot will solve these rare problems.
So for techy people that like to monitor and micro manage everything that goes on in their phone, yes, using a task manager is acceptable. But for your average soccer mom/gf/grandma/Joe Schmo, there really is no excuse for them to have these apps installed on their phone. More often than not, they're going to ruin their user experience with the phone, doing more harm than good, and it will cause them to run to the iPhone where they don't have to worry about this sorta stuff. So with that. I am done here, folks. I hope this Public Service Announcement helped shed some light on a murky subject with Android. Now go uninstall that Task Killer. Now.
restarted my phone again and the sim card is detected once again
hope its able to last and a friendly tip, just to be safe than sorry, always switch off your phone 1st before removing any casing
Any particular reason for this ?? I never bother with such - i even always just take out battery without even switching off phone. Never face any issues in all the phones I have used to date including this S3
yesterday when i removed the casing from my phone, suddenly the sim card turns undetected now its vry unstable. sometimes able to detect and sometimes it would just go undetected
I think you have a hardware issue here - don't think it has anything to do with removing casing. If so my phone already same problem as I often also switch sim cards without even switching off phone. Each time I just take out battery and put in simcard . Same practice I always used in other phones too
just a freakin crazy thought: do you think d safety/ anti theft tint film which is used for car windows suitable for S3 screen protector? if it does, sure would b a hell of SP.
I don't even bother to use any sp which till now I feel us waste of money. I better spend buying a good covered casing for it
Added on June 24, 2012, 11:09 am
QUOTE(JonnY @ Jun 24 2012, 11:08 AM)
My S3 keep showing there was 1 unread message but I had read all of it.
Anyone know how to solve it?
Another repeated questions Don't you ever search before asking
This post has been edited by benny888: Jun 24 2012, 11:09 AM
curve part ??? where or my full cover meaning not same as you guys ? what I mean is almost full cover front side, still got left some place didn't fully cover screen is fully cover, that 2 virtual button almost fully cover haha same here, s2 G user, nothing to do at all just root only ya haha, btw where to download stock kernel miss the link already, need to save it, can't google it @@
Guys need all your help or input. Bought my s3 2 weeks back. Notice the I am on network mode gsm/cdwma which give 3g, I notice my phone become hot after idling for 5 to 10mins. Sometimez when I put in my bAG the phone becomes even more overheating. Why like that?
What do you mean " hot " ??? What temperatures are you recording ?