Related
Hello,
I have three Polaris (O2 XDA Orbit 2) here that crash randomly.
a) Sometimes they just refuse to wake up pressing power. Screen stays black, right green network LED blinks normally (as if phone is registered correctly) but the phone is NOT reachable, the mailbox answers the call
b) the device resets and reboots without any obvious reason...
the mentioned problems occur once in 1 or 2 days, not really reproducible...
Does anybody have the same behaviour? Is it a problem of installed Software?
Additional Software installed:
AvantGo
GoogleMaps
TrendMicro Office Scan
PocketCM Contacts 0.19b
Memmaid
Sprite Backup
Resco Explorer 2007, FTP, Registry
WakeUp Tweak
Calendar+
Advanced Config 2.1
TomTom 6
Battery Status Plugin + Clock
What kind of configuration you did with the Advanced Config 2.1?? the others applications are on my phone too, except Battery Status Plugin + Clock and WakeUp Tweak
is there any option to export the config? Its hard to type everything...
WakeUp Tweak is necessary for Alarm Bug prevention (IMHO) and does only set 2 reg keys AFAIK
nobody who has the same issue?
Can DirectPush can be the reason? I am connected with an SBS 2003 Exchange almost all the time...
Thx for an help,
Hmm... I have the same issues and im am using direct push as well. I am going to disable direct push for a few days to see if that will solve the problems...
One more thing. Apart from direct push we are both using resco explorer 2007 but I don´t think that this has something to do with the problems.
I would try to uninstall batterystatus had the issue too had to do hardreset.
The Bleedin' Obvious...
Apologies if this is just too damn obvious to be of any use, but on earlier XDA models I have had problems with poor connections on batteries, so I would check:
1. That your SIM is clean and properly seated - reseat if necessary
2. That your battery terminals are making good contact with no potential obstructions and that it latches properly when closed
3. Try removing, cleaning and reinserting any SD card you may have inserted
That should eliminate any hardware-based causes. The only other thing that I recall having caused problems in the past (on the Artemis) was battery status - especially it's behaviour on boot (and wake??). Might be worth removing it for a bit to see if it makes any difference.
Good luck...there's always return to manufacturer - you might just have a dodgy unit?
Hi, I have the same problem as you (the first one only).
Do you use push mail palmbluetooth? I am trying to test if it has something to do with direct push. I turned it off right after yesterdays post and had no black screen or reboot since. But well... It will take some more days to figure if direct push and these problems are related.
exactly the same problem.
Hi,
I have exactly the same problem of hazardous reboot.
I have a Cruise with the SFR (Vodaphone French) ROM.
I have see it live twice while my phone was on my table without having touch it.
I'll test this like you without 3G a few days and let you know.
hardware is not be the reason, although its worth to check. But it happens also if the unit is laying on the table without touching it at all...
batterystatus is NOT the reason, had reboots without it installed, can someone verify?
Resco Explorer 2007 is NOT the reason, had reboots without it installed, can someone verify?
Direct Push is the open issue to check. Without this enabled, I have a stable unit for 32 days but I'll try many more since this was not so often...
Any comments are appreciated but its definitely NOT a faulty unit since all three of mine have the same issue. Faulty firmware? Faulty OS ;-)
CU
do you have bandswitch installed?
your is a software installed problem mate!
Report here all software installed, bye
Still no reboot or hang since disabling direct push... I did not change something else and had reboots or hangs nearly every day. Would be great to know if it is really direct push/active sync...
same with my device, I think DirectPush is the reason. Can somebody else confirm?
You guys mean to tell me that direct push, which is built into the OS and is a major component of AS on the device for years doesn't work? Come on now. I refuse to believe it. If it truly caused instability like you guys say, that would be an even BIGGER issue than the lack of video drivers!
If anything, there must a software conflict going on that is causing the instability. As a true test, try hard resetting and without installing anything, turn on AS push. Wait a day and let us know what happens.
I'll be getting my TC tomorrow and loading it up to the hilt, including setting it up for my 4smartphone account.
Well... It may sound strange but I really start to belive that this is a direct push issue. I did not have these reboots and hangs right from the start and thought about what I have done before getting the problems. I uninstalled a lot of software and nothing changed. After reading the post of avoigt about direct push I remembered that I did enable this right before the issues started. On the other hand I would not bet all my money that it is really direct push causing the problems but it is the No.1 candidate now.
I am not willing to do a hard reset right now and test just direct push course I need some of the installed components for my working days. I hope someone else is able to test that. I would even offer my exchange server for testing...
Exactly the same problem (Polaris hangs or reboots) several times a day. Removed Direct Push and have not had a problem in three days. I set the schedule in ActiveSync to every five minutes. Also changed the GPRS connection to "Always on".
Same problem!!
My Polaris just cuts completely off a few times a day or screen goes black and can't awaken it. It was working fine for weeks and just started doing this.
I do have bandswitch installed and I do not use direct push.
EDIT: When I push on the battery it turns off. I hope its the battery and not the contacts.
Hi, same problem here.
The original version was the french ROM, and it worked for a week without any problem. (I have the phone for only one week). Last night I flashed it with a english version, and installed only 2 programs, skype and core player.
Facts:
1. if the phone is usb connected with the computer, it doesn't turn off.
2. if the phone is going in power save mode automatically refuses to turn back on by pressing the power button. It's like the display is disabled. If I call my number when is down like this, from the phone that I am calling from I can here the call, but the HTC doesn't ring.
3. it goes off after about 2 minutes if is innactive, and I can turn it back on only by reset. If I am using the phone (playing, browsing, etc.) it doesn't turn off.
I guess it's a soft problem. (but then again, I'm just a beginner user with this phone)
Does anyone has a solution for this?
Thanks
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781
Folks whose devices fit the criteria of what I have (see attached screenshot of my "About Phone" screen), please read on. I say this only so I can figure out what is common between us to be having the following Bluetooth issue:
1) Bluetooth toggle switch is OFF.
2) You slide the switch to "on". The phone sits there for approximately 10-15 seconds, but Bluetooth doesn't come on at any point, eventually the toggle switch in settings slides back to OFF.
3) There is no setting/method in the device that will turn Bluetooth on.
From when I received the phone from Google Play store, the only thing I have done to it is root it following this method.
Clearly, something with the rooting process did this (I am also having one other issue, but that one is less annoying than this Bluetooth one). But everything in my phone points to me still having the stock ROM but just having root access.
If I can just see the common thread between my phone and others having the same issue, maybe I can figure it out.
I don't want to flash my ROM or start from scratch for the fear of making matters worst for myself; the device appears to be working fine otherwise.
If I am completely unable to fix this, my only hope is that the eventual release of 4.4 KitKat would fix it on its own (and probably break my root at that point, haha).
After searching high and low for an answer to this, I ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Thanks to the Android OS, I let my phone charge overnight while on WiFi and by the morning all the apps were reinstalled and updated, including the OS itself. My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting.
Now, I just have to find the absolute least intrusive way to root my phone without any ROMs or system-level updates that could screw up stuff like Bluetooth or USB Connectivity for me.
I have a stock unrooted Verizon Galaxy S5. For several months my phone has been plagued by several issues at startup. Whether I reboot the phone or start it up after the battery has died, it always enters an odd state immediately after loading and seems to get stuck in this state for an undetermined and variable amount of time (anywhere from a few seconds or minutes to hours or even overnight).
While in this state, this is what happens:
1. Screen stays on. Once I unlock the phone, the screen stays on. The side button doesn't do anything to lock the phone or turn off the screen. Holding down the button, however, still triggers the power menu. The screen timeout never triggers, even though it should turn off the screen after 2 minutes of inactivity.
2. WiFi and Bluetooth turned off. Even if they were turned on before I powered down the phone, they are not enabled when the phone first boots up. I can manually turn them on but the WiFi will not connect to a network, even if one is available. It may show it is connecting to the network, but it gets stuck at "Checking the quality of your internet connection" and continues to use the 4G network for data connectivity. This happens no matter what WiFi network I am within range of, so it's not an issue with the network or router itself. If I am not near a network at all I will still experience the other problems of not being able to lock the phone, etc.
3. Startup applications don't load. I have Tasker on my phone, but it doesn't load and show it's notification bar icon.
Otherwise, I can use the phone normally and open applications, surf the web, etc. It seems that loading some applications and using the phone eventually causes the phone to exit this mode, but I haven't been able to find a single particular application or series of steps to fix the problem. If I power on the phone and don't use it that just seems to make it take even longer to fix itself.
Once it gets out of it's weird state, the WiFi connection will become active (it will turn on WiFi if I haven't done so manually already) and it will connect to a known network if one is available, the phone will lock itself or I can do so from the side button, and things like Tasker and Power Save mode will turn on.
I am stumped as to what could be causing this problem or how to fix it. It seems the phone may be doing some kind of check, maybe related to Knox, that hangs during startup and prevents certain things from working until it straightens itself out.
Any clues into what this problem is, what is causing it or how I could further analyze this problem and determine its cause would be greatly appreciated.
Never heard of or experienced these issues. May want to contact Samsung.
Have you installed any official updates from Verizon at any point? I've heard of phones having phantom problems like this after receiving a bad update. I would definitely contact Verizon if you did update at any point. If not then like BigBot96 said, contact Samsung about the problem.
My wife's Note 2 did something similar when the battery died. I had to factory reset. Her phone was rooted/unlocked & running a custom TW ROM, though. May I suggest doing a complete factory reset and Odin. Backup data to computer or external sdcard since this will clear the entire device.
Edit: After rereading OP's post it actually sounds like an app is hanging at startup which could cause this behavior. A logcat should tell you what's going on.
Sent from my SM-G900V using Tapatalk
So, I have been having some extremely frustrating issues with the WiFi on my 6P. I got my phone in January and I have been super happy with it except for this one issue. Since I got it, I was using the stock OS up until the April security patches came out. Before the patches, I had some issues, but the phone was still mostly usable. Especially after that update, however, I have been faced with two very irritating WiFi issues.
When my phone goes to sleep, the WiFi connection inevitably drops out. Sometimes, the WiFi will still be active but not associated, but it will frequently have also switched itself off completely.
I can only stay connected to a network for about 30 seconds tops. The connection will just stall out and then reconnect after several seconds.
In an effort to get better performance, I decided to switch from the stock OS to PureNexus (which I used and loved on my old Nexus 5) and I also flashed the ElementalX kernel. For the first few days, the WiFi performance was rock solid, but slowly it got worse than it was on stock to the point of being unusable now. Now, here's what I have already tried/checked:
The "Keep WiFi awake during sleep" option in the Settings app is DEFINITELY set to Always.
This issue is not specific to any one network. It had occurred on every network that I've used and on 2.4G and 5G networks (although it seems to be worse on 5Ghz)
I tried turning the band selection off Automatic and choosing both 2.4 and 5 only options, both just seemed to make it worse.
I've removed all apps that I installed and checked logcat for any app info that might be related to the issue. All I see is just normal stuff and then BAM! The wifi driver states that it disassociated from the AP.
I tried installing WakeLock to hold WIFI_MODE_FULL at all times. This hasn't made much of a difference with it disassociating while the screen is off.
Has anyone else experienced issues like this? I am to the point now where I might have to send in my phone under the warranty because I don't know if it's just detective hardware or what at this point. The fact that it worked well after a clean install would seem to suggest that it isn't, but the fact that it persisted across two different ROMs suggests that maybe it is.
Either way, I am at a loss and I've exhausted all the diagnostic skill that I have trying to fix this because it's so damn frustrating when you're in the middle of doing something and you can't stay connected for 30 seconds. Any help or ideas would be appreciated immensely!
My issue is the wifi connects but no internet message
Sent from my Nexus 6P using XDA-Developers mobile app
Is this with different Access Points or just at a particular wifi spot? I would factory reset the device, reboot your router, make sure you don't have any odd settings on your router like modified channel bandwidth, etc. If the 6p doesn't stay locked on, it's a hardware issue and I would do a warranty claim. My 6p wifi has been money since January with every ROM.