Related
Hi guys. I'm totally new to the android/smart phone world btw. Anyways, I recently got my Samsung Galaxy S2... first thing I noticed, my touch screen wasn't working. I popped the battery in and out and then it started working as it should.
My phone was working fine this morning, then all of a sudden out of no where, the touch screen stopped working again. I've tried turning on/off the phone multiple times. I've taken out the battery and even my SIM card nothing... i'm worried.
Has this happened to anyone else? Is there a fix? Do i have to go through Samsung? I hope not. Incase anyone asks, I did not root my phone.
Any help/feedback would be appreciated.
When the touchscreen stops working... were you charging the phone at that time?
The first time i turned on my phone, was actually by accident and it was charging.
However, just earlier now, it was not. it was just sitting on my computer desk. The home button, lock button and touch capacitive buttons work.... but i can't get past the lock screen
you could try a factory reset to see if its software related, but it sounds like hardware. I would definitely Return the phone .
I guess I can't do a factory reset, since I can't get into any of the menus... man this sucks. I spent $900 *gulp*
To do a factory reset,
1. Turn the POWER OFF, pull the battery out and put it back again.
2. Simultaneously press and hold the Volume Up, Home and Power button
3. If the Samsung Symbol appears, release the Power button
4. A Boot Menu will then show, Use the volume up/down to choose wipe data/factory reset.
touch screen not needed this way.
oo that's interesting... I tried it. and it didn't get to a boot menu. maybe I was doing it wrong. I tried a few different ways, but no success. It turns out I have warranty with the store. They're going to replace it for me Thanks for the feedback guys. Awesome forums.
Something similar happened to me yesterday. When I had the in-box USB cable attached to a BoxWave VersaCharger (combined AC/DC charger), and the VersaCharger was plugged into 120V AC, the touchscreen would stop working. As soon as I unplugged the USB cable from the SGS2, or plugged the VersaCharger into a 12V DC lighter socket, the touchscreen would work fine.
I've got the same problem as the OP... I had my phone charging overnight and this morning when I first went to use the phone I could not unlock the screen. I could wake the screen via the home button, and see I had a missed call etc but it just wasn't responding to touch. BTW I can't remember if when I first tried to unlock the phone if it was charging or not but really this shouldn't matter.... oh and btw, I'm not rooted or anything either! Naturally I rebooted the phone but still the same problem....so I tried a battery pull and still the same problem. Just now I did a factory reset but the touch screen still isn't working! I guess this is a hardware problem so I'm going to get it fixed under warranty by Samsung! Gutted that I will likely be without my phone for a week or 2!
EDIT, UPDATE...
Well, I was just on my way to the repair shop Samsung warranty had told me to take it too, and I took my sim card out to put in my old Hero (the only thing I hadn't tried!) and I couldn't believe it but the touch screen started working fine again! Weird, but that is now my advice if anyone else has a problem with their touch screen not working - oh and I took the sim out whilst the phone was still turned on. Crisis averted!
UPDATE 2
Sadly this has happened about 4 times to me now and I'm just waiting for the inevitable next time. Each time doing a factory reset then taking the sim card out seems to bring the screen back to life (though last time not immediately) but I shouldn't have to put up with this. Problem is, I don't want to send off a seemingly perfectly working phone to get repaired as I fear they will struggle to notice the problem, never mind fix it! I'm hoping a new firmware comes out soon, in the hope that it may resolve my issues...
Me as well ...
I have had this happen to me twice now (Touchscreen not responding).
The first time I had just installed a game and thought it must have been related to that. Pulled the battery and no joy, left it for a while and it came back to life...
Second time I was surfing the web and it stopped responding, pulled the battery and left it for maybe a minute but no joy .... pulled the battery again and left it for probably 20min and it came back to life. When it came back up I noticed the livewallpaper had been turned off and my widgets were gone from the homescreen.
What I did notice when it wasn't working was it had "safe mode" displayed at the bottom left of the screen
Have the Same Problem
Have the same problem i Mine and was super exicedat first it worked fine and after charging the touchscreen stopped working i pulled the battery out and put it back in but no luckso im gonna return mine to the shop hope they replace it
Moral:AT FIRST SUPER EXICTED BUT NOW SUPER ANGRY
Same issue - Is there ANY way to save my data before I send it in for repair/replace?
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
blaubeer said:
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
Click to expand...
Click to collapse
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Nitrile said:
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Click to expand...
Click to collapse
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
blaubeer said:
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
Click to expand...
Click to collapse
get a USB jig off ebay or amazon to reset the flash counter. should not cost more than 5 or 6 euros, shipped.
anyways you need to flash CF-root through ODIN if you are coming from stock. instructions are all in chainfire's cf-root thread.
Nandroid Restore
So I successfully rooted, used CWM to do a Nandroid backup, mounted the sd_card and saved the contents (including the nandroid backup) to my PC, reflashed the stock rom & kernel, usb-jigged it to get the counter back to zero/original and sent the phone in for repair. My efforts paid off as they repaired it without question under warranty. I just received the phone back and today set about restoring my backup:
Copied the sd_card contents I'd saved to my HDD back onto the phone
Re-roooted it with Cf-mod.
Used CWM to restore the backup I took before sending it in
It restored boot/system/data/cache successfully
selected reboot now in CWM
The result is that it is still missing all my apps. It only seems to have the "data" like my camera shots and SMS messages, system settings like whether bluetooth is on or off, the volume level, Wifi networks etc. So something was restored. But there is no Google Account configured, the lock screen picture is the default not the one I had beforehand, and as I said, all the apps - the main reason I did this whole thing as my personal data is all backed up to the cloud on a regular basis anyway - have not been restored. Am I confused? I thought a nandroid backup took a complete snapshot of everything, apps included.
Finding out the list of Apps I had in order to reinstall them is not an issue - I have a list of everything I had installed saved on AppBrain. But if I reinstall the apps, all the settings (or progress in the games) within those freshly installed apps will be back to square one, not where I left them, right? Or should I reinstall the apps and then restore the data partition over the top again?
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
achillies400 said:
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
Click to expand...
Click to collapse
Nope, no screen protector or any kind of case for that matter. Anyway, that isn't my issue anymore. The touch-sensitive unit was defective, the phone was repaired under warranty. My issue now is getting my apps & settings back. I have meanwhile read elsewhere that Nandroid doesn't back up the apps - pretty deceptive "backs up everything!" "it is like time travel" etc comments around here then.
Anyway, I reinstalled all the apps I had previously, and thought by reapplying the data partition from the nandroid backup it might then bring back the settings for the reinstalled apps. Instead all it did was remove all those apps again - now I am really confused. How come the restore DOESN'T bring back the apps I used to have, but DOES remove the ones I subsequently install. Does Nandroid touch the apps or doesn't it?
Touch screen not working
So i am having a very peculiar problem related to the GT-I9100 Touch Screen.
I bought the phone from Saudi Arabia and I live in Bangladesh at the moment. So for now I don't have warranty.
I bought it on 4th of this month. It had 2.3.3. So I updated it to 2.3.5. I did not use the phone much before that so I don't know if this problem was there before.
So here is the problem.
First time I noticed it when i pulled the phone from my pocket and could not unlock the pattern. First I thought I forgot the pattern. After sometime I noticed that i could not touch the buttons. I was dragging my finger over the points but there was no connecting line. I restarted the set. But it still did not work. After sometime I took the battery out. And after that it started normally and unlocked. And the touchscreen is totally fine.
I tested it using *#0*#. And every single point in the screen registers touch.
After that this happened couple of times. First couple of days I thought it was a pattern unlock problem. But i tried PIN and Password even using no unlock. It happened in every case.
So after couple of days it totally stopped happening.
But from yesterday it is happening again. And today it happened 3 times.
So today as I had no unlock protocol i tried tapping Home twice. As this brings on the voice command menu. And for the first time i was in the phone without touching the screen.And first i noticed the Menu and Back Soft keys works.And the touchscreen still does not work. And i noticed some thing weird. Always some thing in the screen is Selected. In Menu the + Icon is selected. In first screen the Map icon is selected. Also in Recent Apps the first App is selected. So after a lot of reboots it is back to normal again. Now i see something interesting. In the Battery Usage Graph i can see some really sharp drops. 3 times. Looks like when this happens phones charge takes a nose dive.
So here is the Gist.
Info related the Problem:
1. Usually happens when the phone is my pant pocket for sometime. It does not happen if it is sitting on the table.
2. Touchscreen gets totally disabled.
3. I have no idea why this happens.The exact reason behind it.
4. Battery Charge takes a nose dive when this happens. See the attached images.
5. I still don't know how to bring it back. Sometimes a simple reboot works. Sometimes I have to pull the battery. And sometimes it works on its own.
6. Every other function of the phone works. Like music playback using my UE 200vi music keys using PowerAMP, Siri(Android version), Call can be received using headset.
Battery nose Dive:
dl.dropbox.com/u/30943431/SC20111115-203017.png
dl.dropbox.com/u/30943431/SC20111116-202913.png
Also the selection
dl.dropbox.com/u/30943431/SC20111116-202146.png
So this is the thing. My biggest problem right now is, I don't know why it happens and I don't know how to bring it back from this situation. If I knew I could make sure I don't get it again or I would just fix it every-time. As when this happens I cant make calls or anything which requires the touchscreen.
So guys help me if you can by giving ideas. As i will not go back to KSA in 6 months. So buying a $550 phone unlocked was a total waste. As i cant use it here.
Thanks a million in advance.
---------- Post added at 09:29 PM ---------- Previous post was at 09:13 PM ----------
Sorry for this. But looks like i cant post outside links before i have 8 posts. So i removed the "ht tp : //" part of the links. Copy paste in browser address bar and it will open fine.
And also the next time it happens i will do a video to shou you guys.
Having the same problem while charging touch screen doesn't work
Stock charger and usb cable
i was on CM7 but that happend so i flashed stock but no luck
I will write more observations
Today I cracked the screen on my sgs2 while it was in my pocket, I have no idea how it happened but the good news is my service provider is replacing the phone for free.
The problem is I only get a blue line across the screen, I know the phone is working because I am still recieving messages and it rings etc but I cant unlock the screen to get it into mass storage mode to retrieve my data!
Any idea if I can get into the phone any other way to retrieve contacts etc?
No backup ???
Or Nandroid backup ??
jje
People should sync with google more. For anyone reading this: go into Contacts, press menu, and select Merge with Google (it should be something like that, my os language is Dutch).
This way you can see al your contacts at contacts.google.com
@topic starter: have you tried looking at http://contacts.google.com if your contacts are stored here?
Have you tried adb as long as debugging was turned on which some roms do by default it should work. Or boot into recovery then use adb.
I have tried adb it doesnt seem to do anything, how do I put the phone into recovery?
dawson8 said:
I have tried adb it doesnt seem to do anything, how do I put the phone into recovery?
Click to expand...
Click to collapse
Vol up--->Home--->Power. Hold this three buttons on the same time and release when Samsung logo apperas
Well, I couldnt get the phone inot recovery mode either, but now my replacement has arrived I guess I just have to bite the bullet and use an older backup.
Is there any app or a way that I can install something on my phone so that if the screen ever breaks again I can access my data not just to back it up but to delete it?
I just assumed you are rooted (most people on this site are) but I should make sure so that you actually had a recovery with adb, are you? I don't know if the stock one does.
If not flashing cf-root using download mode would give you CWM recovery.
No I am not rooted, I was unsure if rooting was reversable and didnt want to void my warranty, Im even more scared off now that I know the screen can break when the phone is in my pocket and hadnt been mis-used or dropped at all!
Well the phone is already wrecked so the warranty is already gone. Just root it so you can get your data.
The main problem is do you remember your software version so you can use the right cf-root kg* kernel.
the phone is still under warranty, and has been replaced. I would now like to know how to prevent this from happening in the case of the screen breaking again?
Wow I never knew of a warranty that would cover physical damage like a broken screen.
For the new phone make sure the first thing you do is to turn on usb debugging so that you can use adb on the stock rom.
Also another possibility for getting data (just a theory) but if any remote control software (VNC etc) in the Market AUTO STARTS with the phone, it could be installed by using market.android.com then control the phone from your computer as long as wifi was on.
I don't know if any exist like that though and a quick search showed one VNC server but you had to open the app and turn on the server.
Edit: I wasn't thinking of the limitations of adb data access when not rooted, so well it is still a good idea for the new phone you may want more ideas from other people
I'm not sure if anyone has experienced this on their 3d before and when I searched the topic there was no real definition or solution. Yesterday while playing around on the phone I had a random reboot (ZR3D Rom using Anthrax) and when the phone booted again I had the message "Safe Mode" in the lower left hand of the screen.
God knows I thought I really screwed something up, booted to recovery, wiped cache, dalvik, and fixed permission to no avail. So this morning I get to work and have some time to look up this safe mode and came across this article:
http://androinica.com/2010/08/how-to-activate-android’s-safe-mode-to-get-out-of-a-force-close-loop/
I had no idea that our phones could do this and its quit the neat feature, in a nut shell if you have a program that keeps force closing and you can not use the phone because of this, the phone can be booted into the safe mode which prevents the phone from loading 3rd party apps so you can remove the app that was giving you problems. All that is needed is a battery pull then hold the menu button while powering the phone on and vice versa to get rid of safe mode.
Like I said I'm not sure if anyone else had this problem or even knew about it but I thought I would share just in case someone needs help.
That's some good info. Thanks.
Holding the volume down once the splash screen appears will put you in safe mode as well, with any reboot no need for a battery pull. You will feel a hard vibrate, stronger than the normal quick one you get on a normal boot.
interesting info... didn't know that.
on another note.... i have never had a third party app repeatedly force close on me. in the ROM flashing world it has always been a system app.... this method would be useless in that scenario lol.
interesting, though, learn something new everyday.
It has actually been helpful for me, finding out what apps are comparable with joelz's cm9 kang rom.
I'm new to this forum, and android too - but I've been using Linux of some sort on my desktop for years so I took a stab at installing cm7 on my Player 5.0 (US). As I'm not I can't post to the dev forum, so I figured I'd share my experience here.
Rooting the device was pretty pretty simple. I found a bash script online somewhere that used the zergkode exploit, and walked through the script manually via adb.
I wanted to watch the root process myself and interact with it in case something went wrong. It worked fine. I had more trouble finding an amd64 version of the adb binary than I did anything else actually.
Next I tried updating the kernel to the entropy's daily. I think the most recent I could find was for last month, but it worked just fine. I briefly considered firing up winxp in a virtualbox to try and get odin working - but considering the problems I've heard others have with kies and drivers - I just bypassed it and looked around for a linux rom flashing solution. Heimdall was easy to find
Checked out the lasted sources out at git://github.com/ambrice/Heimdall.git, compiled, and flashed the kernel with it. I think the command was something like
Code:
heimdall flash --kernel zImage --verbose
Reboot, make a backup of device with the recovery manager. Reboot, copy update-cm-7.2.0-RC1-YP_G70_USA-KANG-signed.zip and gapps-gb-20110828-signed.zip to /mnt/sdcard/external_sd where my microsd card lives. Reboot back into recoverymode.
By the way. I couldn't seem to get the hang of the keypress to kick in the recovery mode or download mode. I'd usually try various combinations of power and upvol until at some point in the boot process it'd kick in. Do you hold the volume key down while depressing power, then releasing it, then volume or is it some other combination? In any case, I rebooted enough times to eventually stumble into recovery mode.
After that, install worked pretty much like what I expected it to. Did a Wipe Data/Factory Reset, install from zip. Installed gapps from zip. Reboot.
CM7 fired up fine, and I thought the bootsplash is nifty. Heck, the whole thing is very pretty and has nice effects. I noticed right away that Google apps didn't take, so I rebooted (again and again) until eventually I manged to find recovery and re-applied the zip. Worked this time.
Fired up Titanium Backup and began restoring apps. Took me an hour or two to get it all working. Some apps didn't want to restore and would freeze Titanium. Especially anything samsung related like the FM Player, which I still don't have installed. In fact, I don't think I have *ANY* samsung apps installed, which I kinda like.
Impressions/Bugs/Annoyances:
* Headphones do not work at all unless you use the stock earbuds that shipped with the player are used. Took me about a halfhour to figure that one out. I imagine that the stock earbuds with their inline mute have some different wiring, and regular earbuds/headphones just aren't seen the same and cm7 doesn't like em. Dunno. Annoying.
* Wifi doesn't work unless you go into airplane mode and enable wifi. I imagine this has something to do with disabling the software that handles the non-existant phone hardware? Is there a way to do this without going into airplane mode?
* Wifi seems flakey, drops connections after 10/15 minutes. Comes back usually, but it's annoying. This is on an open network too. In my experience (with linux), things can become all sorts of extra fun when you start adding wpa/wep to the mix. So I'm not hoping for better behavior when I try on an encrypted net.
* Camera works, but I can't figure out how to use the small one facing me. No big deal, but ... ugh.
* On initial (cold) boot, it seems to reboot as soon as it startes the "scanning media" phase... Once. Subsequent reboots seem to act fine.
* Not a fan of adwlauncher, so replaced it with launcherpro. On first startup, It shows a black screen, sliding to the left or right to another "page" fixes the big black space on the screen. Not sure of this is launcherpro problem or a cm7 one. A little bit annoying, but not a big deal.
* CM7 seems to eat up a lot of space. I have a few gig free on /mnt/sdcard and on /emmc, so I assume the warnings I get when trying to install new apps refers to the root directory. I think I saw some options about where to install new apps somewhere in the settings, which would solve that problem. I could also use Titanium to move system apps back to userspace (terminology right?) I think.
Other than that - everything seems to be running fine. I have other third party software that I used to take care of setting power/cpu profiles which I notice CM can handle on it's own - so I'll probably need to spend some time figuring out how all of that works.
I'm happy for the most part at this point. The earbuds thing and the wifi flake-out are the most annoying bugs, which I can live with for a while I suppose. I never use the FM Radio anyway.
Anyway, thanks to all the folks out there working on the CM project for the Galaxy Player. It's amazing that it works as well as it does at this point. Keep up the good work! I might even try CM9 at some point, but I'll wait until the camera is reported working first.
xterminus said:
I'm new to this forum, and android too - but I've been using Linux of some sort on my desktop for years so I took a stab at installing cm7 on my Player 5.0 (US). As I'm not I can't post to the dev forum, so I figured I'd share my experience here.
Rooting the device was pretty pretty simple. I found a bash script online somewhere that used the zergkode exploit, and walked through the script manually via adb.
I wanted to watch the root process myself and interact with it in case something went wrong. It worked fine. I had more trouble finding an amd64 version of the adb binary than I did anything else actually.
Next I tried updating the kernel to the entropy's daily. I think the most recent I could find was for last month, but it worked just fine. I briefly considered firing up winxp in a virtualbox to try and get odin working - but considering the problems I've heard others have with kies and drivers - I just bypassed it and looked around for a linux rom flashing solution. Heimdall was easy to find
Checked out the lasted sources out at git://github.com/ambrice/Heimdall.git, compiled, and flashed the kernel with it. I think the command was something like
Code:
heimdall flash --kernel zImage --verbose
Reboot, make a backup of device with the recovery manager. Reboot, copy update-cm-7.2.0-RC1-YP_G70_USA-KANG-signed.zip and gapps-gb-20110828-signed.zip to /mnt/sdcard/external_sd where my microsd card lives. Reboot back into recoverymode.
By the way. I couldn't seem to get the hang of the keypress to kick in the recovery mode or download mode. I'd usually try various combinations of power and upvol until at some point in the boot process it'd kick in. Do you hold the volume key down while depressing power, then releasing it, then volume or is it some other combination? In any case, I rebooted enough times to eventually stumble into recovery mode.
After that, install worked pretty much like what I expected it to. Did a Wipe Data/Factory Reset, install from zip. Installed gapps from zip. Reboot.
CM7 fired up fine, and I thought the bootsplash is nifty. Heck, the whole thing is very pretty and has nice effects. I noticed right away that Google apps didn't take, so I rebooted (again and again) until eventually I manged to find recovery and re-applied the zip. Worked this time.
Fired up Titanium Backup and began restoring apps. Took me an hour or two to get it all working. Some apps didn't want to restore and would freeze Titanium. Especially anything samsung related like the FM Player, which I still don't have installed. In fact, I don't think I have *ANY* samsung apps installed, which I kinda like.
Impressions/Bugs/Annoyances:
* Headphones do not work at all unless you use the stock earbuds that shipped with the player are used. Took me about a halfhour to figure that one out. I imagine that the stock earbuds with their inline mute have some different wiring, and regular earbuds/headphones just aren't seen the same and cm7 doesn't like em. Dunno. Annoying.
* Wifi doesn't work unless you go into airplane mode and enable wifi. I imagine this has something to do with disabling the software that handles the non-existant phone hardware? Is there a way to do this without going into airplane mode?
* Wifi seems flakey, drops connections after 10/15 minutes. Comes back usually, but it's annoying. This is on an open network too. In my experience (with linux), things can become all sorts of extra fun when you start adding wpa/wep to the mix. So I'm not hoping for better behavior when I try on an encrypted net.
* Camera works, but I can't figure out how to use the small one facing me. No big deal, but ... ugh.
* On initial (cold) boot, it seems to reboot as soon as it startes the "scanning media" phase... Once. Subsequent reboots seem to act fine.
* Not a fan of adwlauncher, so replaced it with launcherpro. On first startup, It shows a black screen, sliding to the left or right to another "page" fixes the big black space on the screen. Not sure of this is launcherpro problem or a cm7 one. A little bit annoying, but not a big deal.
* CM7 seems to eat up a lot of space. I have a few gig free on /mnt/sdcard and on /emmc, so I assume the warnings I get when trying to install new apps refers to the root directory. I think I saw some options about where to install new apps somewhere in the settings, which would solve that problem. I could also use Titanium to move system apps back to userspace (terminology right?) I think.
Other than that - everything seems to be running fine. I have other third party software that I used to take care of setting power/cpu profiles which I notice CM can handle on it's own - so I'll probably need to spend some time figuring out how all of that works.
I'm happy for the most part at this point. The earbuds thing and the wifi flake-out are the most annoying bugs, which I can live with for a while I suppose. I never use the FM Radio anyway.
Anyway, thanks to all the folks out there working on the CM project for the Galaxy Player. It's amazing that it works as well as it does at this point. Keep up the good work! I might even try CM9 at some point, but I'll wait until the camera is reported working first.
Click to expand...
Click to collapse
Cool... welcome...
I am not a CM7 user as I use CM9, but I wanted to give you clear directions on the Download and Recovery mode key combos.
Download Mode = Power + Vol Down (-) - Hold this key combo from a full power down state. Hold them until you see the Yellow Triangle logo. It should be about 5-8 seconds
Recovery Mode = Power + Vol Up (+) - Same as Download Mode... Hold them until you see the CWM menu.
I usually hold them until I see these menus... I think holding them for about 5 secs or so and letting go of the power button still gets you in those modes.
followup
cvcduty said:
Cool... welcome...
I am not a CM7 user as I use CM9, but I wanted to give you clear directions on the Download and Recovery mode key combos.
Download Mode = Power + Vol Down (-) - Hold this key combo from a full power down state. Hold them until you see the Yellow Triangle logo. It should be about 5-8 seconds
Recovery Mode = Power + Vol Up (+) - Same as Download Mode... Hold them until you see the CWM menu.
I usually hold them until I see these menus... I think holding them for about 5 secs or so and letting go of the power button still gets you in those modes.
Click to expand...
Click to collapse
Thanks, I think the trick is ONLY hold the power button down long enough to get it to boot. Pressing it beyond that point doesn't do anything good. Thanks
Some followup notes on CM7 I didn't cover in my first post:
* By swapping out wpa_supplicant (in /system/bin) for a newer version seems to help with wifi stability quite a bit. There is a link to a rar in the CM7 thread with a few alternative binaries. In any case, I don't have to fool with airplane mode anymore. Wifi just seems to "work" now.
* I've noticed that CM7 seems to suck a lot more juice when "sleeping", or idling with the screen off. I've noticed some mentions of a failure in the kernel to go into deep-sleep, which I suppose makes sense.
* Touching anything bluetooth related (turning it on, scanning, etc) often but not always results in an crash and instant reboot. I don't use bluetooth much, but I can see it's a problem. Disabling all bluetooth settings has helped stability quite a bit.
* The "black screen" I noticed in launcherpro went away when I disabled scrolling widgets.
* I've tried manually installing the FM Radio app (copying apk directly in with appropriate metadata files.) Still not working although it shows up. I suppose in order to get it working I'll have to restore all the samsung apps too. I'll get it working eventually I'm sure. I tried a third party Fm Radio app (Spirit Radio Free), and it didn't work at all either. At least it installed.
* In the calling preferences, where you can select googlevoice as your voicemail provider results in a crash of the google voice app. I also can't get the phone to properly register with a SIP provider with the stock CM7 settings either. I disabled that configuration and restored the Groove-IP app until I can figure out what's going on. I have a proper gv/sip gateway I can use (besides grooveip) - but the phone doesn't seem to want to work with it.
* For this particular ROM, it'd probably simplify everyone's lives if it were possible to remove any reference to most of the phone settings. For example, the Player doesn't have to deal with "Mobile Networks" (under settings/wireless & network settings). Removing the option to enable mobile data makes sense too I suppose. I'm not sure *how* to do it, but I thought I'd mention it.
That's it for now.
Hello
I've had a Samsung Galaxy S3 for ages, unfortunately for me, the phone recently just switched off, then on, then won't go past the "Samsung" screen. Ah, I thought (well, something a bit more sweary) - but I had a backup identical model phone in case one broke, so I started using that. Moved all my apps, installed banking app etc, and then happy.
Or so I thought...
The new (well, it's an old phone, but one I haven't been using, bought as back up) phone now switches off when charging every night, an issue which was going to switch to me charging it during the day when I can stare at it and see if anything happens to make it switch off, but then I realised it switches off each night even when it isn't charging.
I have a bigger battery to hold a charge for a few days, and so even when I don't charge it, just have it next to me as I sleep - and next morning it will be off. I presume it might be switching off around 5am... this is only a rough guide as if I switch it back on, and flick through the phone, I see my unread emails are up to around 5am, and then after a few minutes it logs back into the internet etc and brings me newer emails.
I first thought it was that it kept switching off when charging... but now I know it does it at (I presume) the same time every night even when it's not charging. Can't use it as an alarm clock anymore, as it's off before the alarm goes off. Anyone have any idea what's happening?
Did you copy all of your data and settings?. Most likely you have a software conflict going on.
I highly recommend you backup your data from all 3rd party apps. Do not backup your system apps data, google data, apps or games that cloud sync or phone settings, ie wifi passwords etc.
You must allow samsung apps, google and other cloud apps to sync their own way and you must calibrate the phone for wifi manually.
Beyond that you'll need to reflash stock firmware and start over using the guidlines I have given you above after restoration of the firmware (and root if required).
Beamed in by telepathy.
I assume when I installed on the other phone, it switched settings when I log in to various things. Because I installed everything asap, I've no idea if one thing is causing the issue.
How do I get the phone to calibrate manually? Apologies, I'm not great with techie stuff I add the wifi details, and logged into settings - is that manually? Things are backed up to themselves, so when I log back in it resets to previous settings when it syncs. Should I try and work out how to prevent all things from backing up manually? Haven't logged back into any games, although they might be installed, haven't actually signed in or used them.
How would I go about reflashing stock firmware? Doesn't sound like anything I've ever done before, but up for a challenge
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
shivadow said:
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ahh, cool, gottcha! Ok, will try soon. Surprisingly, I've switched off the phone every night instead of it auto-switching off at around 5-6am, and surprisingly it's so far going well. Had it on for 3 days and only at 47% now, so it's promising, still does switch off occasionally during the day, but I've just ignored that. Will do a factory reset in the next couple of days and report back Thanks for the help