My Galaxy s2 Is having really annoying problems!
First off it rotates the screen even screen rotation is off.
Secondly, It keeps telling me i am connected Via USB Device to a computer when i'm not.
Then it keeps taking me off the screens im wanting to view.
Also It just keeps opening desk clock.
Then when i do plug it into my computer, It opens voice talk, then my computer also tells me that it isn't a recgonised device.
I formatted my phone this morning, it was good for abour 5-6 hours then it begun playing up like this.
I turn the phone off, take out the battery and let it sit for a bit, Then as soon as i put the battery back in the phone turns it self on without me pressing anything...
Heres some pics I managed to get of whats happening after fighting with my phone xD
This one shows the desk clock that keeps coming up.
http://tinypic.com/view.php?pic=2cgbgas&s=5
Here we have it showing me that im connected via USB
http://tinypic.com/view.php?pic=e9hqbl&s=5
Then this one is showing my phones details, Version etc.
http://tinypic.com/view.php?pic=2d842hi&s=5
If anyone can help it will be much appreciated.
Whats up XDA.
So I have a galaxy tab sch-i800 running on cyanogenmod 9. I plan to fit my tablet into the dashboard of my car, I have everything worked out except how I'm going to turn it on and off. since I won't be able to access the power button I need a way for it to power on/off by its self, that way its not occasionally dead when I start my car.
At first I planed to use tasker to turn the tablet on when plugged in (or when I start my car, it turns on). and then turn off after an hour of inactivity (or an hour after I've turned off my car).
But now that I'm looking at tasker it won't let me use the command "turn on" (even though I'm rooted) and I don't see a turn off command.
Is there any apps out there that can help do exactly what I want?
I have noticed that 4.2+ automatically boots when it is plugged in, I'm on 4.0, would upgrading screw up cyanogenmod?
Thanks!
Auto On/OFF
Carson-TL said:
Whats up XDA.
So I have a galaxy tab sch-i800 running on cyanogenmod 9. I plan to fit my tablet into the dashboard of my car, I have everything worked out except how I'm going to turn it on and off. since I won't be able to access the power button I need a way for it to power on/off by its self, that way its not occasionally dead when I start my car.
At first I planed to use tasker to turn the tablet on when plugged in (or when I start my car, it turns on). and then turn off after an hour of inactivity (or an hour after I've turned off my car).
But now that I'm looking at tasker it won't let me use the command "turn on" (even though I'm rooted) and I don't see a turn off command.
Is there any apps out there that can help do exactly what I want?
I have noticed that 4.2+ automatically boots when it is plugged in, I'm on 4.0, would upgrading screw up cyanogenmod?
Thanks!
Click to expand...
Click to collapse
To Switch ON
I think you may have to rewrite the Bootloader code to switch ON the Tab when Charging starts instead on that Large Green Battery Animation. Search it ..
Hint : I have seen it(the code) somewhere while I was looking for OTG in P1000.
To Switch OFF
Try these apps and do post their results
MarcroDroid
Carson-TL said:
Whats up XDA.
So I have a galaxy tab sch-i800 running on cyanogenmod 9. I plan to fit my tablet into the dashboard of my car, I have everything worked out except how I'm going to turn it on and off. since I won't be able to access the power button I need a way for it to power on/off by its self, that way its not occasionally dead when I start my car.
At first I planed to use tasker to turn the tablet on when plugged in (or when I start my car, it turns on). and then turn off after an hour of inactivity (or an hour after I've turned off my car).
But now that I'm looking at tasker it won't let me use the command "turn on" (even though I'm rooted) and I don't see a turn off command.
Is there any apps out there that can help do exactly what I want?
I have noticed that 4.2+ automatically boots when it is plugged in, I'm on 4.0, would upgrading screw up cyanogenmod?
Thanks!
Click to expand...
Click to collapse
What you hope to accomplish with it turning on from a full power off is not possible without rewriting the bootloader or somehow rewriting the power switch (open the tab, solder wires to the switch terminals, and use an external relay or transistor to short the wires).
I picked up a Chromecast a couple of days ago but am having trouble with it and I can't find a decoder ring for the status LED. I don't see a Q&A form for this device or the info in the FAQ so I'm posting here.
Here's my issue: After initial setup/connection I was able to cast youtube/music/pandora just fine. I noticed that the status LED during that time was solid white. My assumption is that this is the status which the device should always be in. However in the morning (same thing 2 days now) I no longer get the cast icon in any of the apps, even though the chromecast app says that the device is "ready to cast". At this point the LED is blinking white. Does this mean disconnected from router? Unplugging/plugging the unit back in from power/HDMI fixed the problem but it just reoccurs the next morning. Any thoughts?
I'm using a Linksys E3000 router running Tomato 1.28 I believe. AP isolation is OFF.
Anyone have a full breakdown of the LED meanings?
Ps: i forgot to add that for a successful reconnect I have to unplug both power and HDMI, plug power back in until the LED goes solid white, and then plug HDMI back in. Just cycling power does not work.
Wayno-san said:
However in the morning (same thing 2 days now) I no longer get the cast icon in any of the apps, even though the chromecast app says that the device is "ready to cast". At this point the LED is blinking white. Does this mean disconnected from router? Unplugging/plugging the unit back in from power/HDMI fixed the problem but it just reoccurs the next morning. Any thoughts?
...
Ps: i forgot to add that for a successful reconnect I have to unplug both power and HDMI, plug power back in until the LED goes solid white, and then plug HDMI back in. Just cycling power does not work.
Click to expand...
Click to collapse
Don't trust the status given in the Chromecast app - it has a tendency to be incorrect with respect to Ready to Cast, Needs Setup, etc. Always go by what Chromecast shows you on the TV screen.
Blinking white - Chromecast is not connected to a WiFi access point (this is also the state it goes into when it needs to be set up)
Solid white - Chromecast is connected to a WiFi access point (it may or may not have access to the Internet)
Solid Red - booting, or settings reset triggered (by holding button down)
As for your problem...
The first thing I'd try is using the HDMI Extender - that will reduce the amount of WiFi signal interference/blockage you get from your TV.
Check your router's (advanced) settings for any power-saving features. Some APs reduce signal strength when there's little/no WiFi activity, so it might be dropping the signal enough that Chromecast loses its connection.
Not sure why you have to unplug HDMI - you shouldn't, unless your TV is providing enough (or more than zero) power on the HDMI port to keep Chromecast alive or semi-alive. Does it show any light or attempt to light when you plug it into HDMI but don't have the power connected?
I already have the extender on. No power through the HDMI but it won't reconnect unless I unplug it. I have it powered externally and not via TV's USB port. Don't remember any energy saving features on the router but I'll take another look.
I get excellent reception during streaming so I don't know why it's disconnecting...
Wayno-san said:
I already have the extender on. No power through the HDMI but it won't reconnect unless I unplug it. I have it powered externally and not via TV's USB port. Don't remember any energy saving features on the router but I'll take another look.
I get excellent reception during streaming so I don't know why it's disconnecting...
Click to expand...
Click to collapse
Well, I'm not sure what happened (maybe there was a firmware update?) but Chromecast has remained connected and stable for the last 3 days.... I didn't touch anything... go figure.
Wayno-san said:
Well, I'm not sure what happened (maybe there was a firmware update?) but Chromecast has remained connected and stable for the last 3 days.... I didn't touch anything... go figure.
Click to expand...
Click to collapse
If it makes you feel any better, either we're both crazy, or both not.
The same thing happened to me. WiFi simply would not stay connected with 12072, everything was fine on 13300. It would complain on first boot, then would reconnect in a few minutes and stay connected.
Yeah, seems like whatever happened fixed both problems because it now even reconnects after a power cycle (previously I had to disconnect HDMI also for it to reconnect). Sweet!
I got a connection issue similar to this then other day and had to run the installation app again to get it to reconnect.
Zammo76 said:
I got a connection issue similar to this then other day and had to run the installation app again to get it to reconnect.
Click to expand...
Click to collapse
Couple of months old this thread, but had the same issue, watch a movie through Avia yesterday, came home from work today and it was blinking white, reboot didnt help, unplug and reboot didnt help. Had to reset with the button pressed for 20-25 seconds.. works as it should now tho.. :cyclops:
I've done a few things recently that seemed to have all but stopped my Chromecast connection issues.
1. Changed my phones IP from DHCP to Static. You do this by selecting you're Wifi access point and holding down on it until Modify Network comes up, select it, then check the Show advanced options box, then you'll seee the option to change the IP settings from DHCP to Static.
2. Go into Avia's setting and make sure the Lock Wifi on box is checked. Be warned though this does cain you're phones power so switche it off when you've finished casting.
Zammo76 said:
I've done a few things recently that seemed to have all but stopped my Chromecast connection issues.
1. Changed my phones IP from DHCP to Static. You do this by selecting you're Wifi access point and holding down on it until Modify Network comes up, select it, then check the Show advanced options box, then you'll seee the option to change the IP settings from DHCP to Static.
2. Go into Avia's setting and make sure the Lock Wifi on box is checked. Be warned though this does cain you're phones power so switche it off when you've finished casting.
Click to expand...
Click to collapse
#2 is the main one here, though your phone might have been hopping between IP leases if you router's DHCP lease time is set very low. Usually it's ~8 days which should more than cover your phone disconnecting WiFi and reconnecting a few times, unless you're binge-watching multiple seasons of something.
Hey guys I am having a similar issue with my chromecast and I am unable to tell if my chromecast is bricked or is it some software issue, I was able to cast all my apps in the morning but when I reconnected my chromecast back with the tv it showed me an error with yellow exclamation mark but after that when i reconnected my chromecast nothing comes on the tv and there is a constant red and white led blinking on my chromecast since.
If anybody could help me out with it I would be grateful.
Yesterday my bluetooth won't turn on. It has been working good but all of a sudden you go to settings to turn it on and the on button changes color a little but not bright like it usually does and in an minute or so it will go back to off. The bluetooth logo never shows atr top of screen. Any help appreciated.
Added info. I googled and found that sometime a app. will cause this. I haven't recently installed a app and bluetooth has worked since last app install
L.D.
I have found if I shut phone down and restart bluetooth can then be turned on. However, Later bluetooth can't be turned in until another restart.
I'm joining the chorus of complains about my Samsung Tab S2 9.7" SM-T810 purchased April 2016. I used it a lot and it still works well, except for a weird problem, which could be due to a recent software update.
Assume the screen turns off, without turning off the device. For example, I just leave the tablet unattended for 2 minutes, which is the timeout period. When I return to the tablet and try to turn the screen on (by pressing Home briefly) the screen won't turn on. In this zombie state, the device is still functional. Pressing Home+Power simultaneously makes the sound expected for a Screendump. Later on, I can recover the image file which shows how the screen should have looked if it was on. A long-press on Home brings up the Google Assistant and I can hear it talking to me.
But I can't turn the screen on for a while, no matter what. As if there was an internal timeout of 1-3 minutes which prevents the screen from turning on. The device probably believes the screen is on, and perhaps does not bother changing its status.
After a minute or two, the tablet eventually responds to the Home button and turns on. Then it works perfectly for hours - unless I allow it to turn off again.
Now I just ordered a new tablet (the P-205) so the old SM-810 will soon go into retirement. Would it make sense to try going back to a prior version of Android ? I have no experience with root on Android, although I "used to be" computer literate in the previous four decades.