Related
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
I have an AMOLED AT&T-banded Nexus One running stock Android 2.3.6. I use the default/stock News and Weather app quite regularly, and I have "Auto-refresh" unchecked in the refresh settings. Probably about once or twice a week, I'll notice that this setting becomes re-checked again.
This becomes a problem because I don't have data or WiFi enabled in the background (I only turn them on if I'm actively using them). Normally, without data enabled, I'd be able to open the app or check the home screen widget and still be able to read news headlines or see my forecast, but when the auto-refresh setting becomes enabled and I have no data connection, the app and widget become blank and want me to refresh.
It's worth noting that this behavior has been happening for a few months, back to when I was still on stock 2.3.4. Is there any reason that the auto-refresh keeps becoming checked on it's own or is there any way to fix it?
Thanks.
Unfortunately, this app just seems to get worse and worse over time. I actually like the auto-refresh and had it set up to do it every hour. Well, after the update to Gingerbread, that no longer functions, and it now updates whenever I actually go into the app.
I don't think there is anything you can do to change the behavior of the app, and unless they put out a working update, I think we are both stuck with our problems
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time
My widgets are very slow to update. It may take him a half hour or longer to update. I have checked battery optimization is not on for those apps, although one of those two apps that I have the problem with background data is grayed out. So I can't turn on allow background data. Not sure why that would be great out.
Any thoughts?
Wunderlist Task List.
DTG/GTD
But, I did some things poking around, don't remember for sure what all, but I had read that changing the Animation Scale etc to .5 would help. I did change that.
Before posting, I had found that Wunderlist was on battery optimization. Changing it didn't appear to help, so I posted. But now, it seems to be working. Maybe it's fixed. I'll post back in a day or two and indicate if it is still working or has stopped again.
Well, no, I'm not saying that. I'm just saying that's the only change I made, and at that point it had started working.
Are you having same problem, albeit different widgets?
FYI... mine is now not working again. I'm not surprised. But am frustrated.
Update...
I am finding that it does eventually update. It feels like the phone has been taken over by something. But, then, other things don't seem slow.
I just installed Gsam battery monitor, and ran the ADB cmds to try to identify apps using battery. Maybe I'll find something using a lot of battery and hence cycles.
My battery does seem to be going down quite a bit faster than it should.
It cleared up for a while after a factory reset,But it's back, and, I find that notifications from Lightflow come in 30 minutes after recieved.
It's like the phone is operating in molasses.
I'm beginning to think this phone is crap. If I switch back to my old Mate 9 it works fine.
jd14771 said:
certain apps aren't syncing well with pie. i had this same issue with Beautiful widgets, could not get the weather or time to update unless i manually updated it.
Under <Problem APP's> App Info > Battery
1.A Make sure the app is allowed background activity
1.B Make sure the app is not set to "optimized"
. (note: by default, the optimized list will only show apps that HAVEN'T been optimized, . you have to select "ALL" at the top to see all apps.)
Under <Problem APP's> App Info > Mobile Data
2.A Make sure "allow background data usage" is enabled.
2.B Make sure "allow app while data saver is on" if you have data saver enabled.
. (enable this if you want to be sure an app will receive background data.)
Click to expand...
Click to collapse
Thanks for the suggestions. I don't seem to be having any luck with that. Had already done those.
But!! ...
I just found a post after doing a global search for another issue I am having that seems to coincide with the widget issues, which is, Play Store freezing during updates. The post was in a Xaiomi forum. He said that he found if he had blue tooth on, his play store would constantly freeze. He turned off BT, and rebooted, and it worked.
I just did the same thing...and it is working...both the play store, and widget updates.
Interesting to have the great feeling of success, along with the frustration of a new (newly realized) issue yet remaining (BT).
Looking for a little further and through the settings on Bluetooth, I turned off Bluetooth scan. Now at first I would still have problems with Bluetooth on even though Bluetooth to scan was off. That of course would be very quickly after turning it on or off at cetera.
so this morning I get up having left Bluetooth on all night, with scan off, and everything's working fine. I did find last night that when I would first turn Bluetooth on even with skin off, the problems would be there. But of course when you first turn Bluetooth on it's going to scan anyway.
so I will update this thread little later after I see a little more about weather. Just having scan off actually cures the problem, in case someone else runs into this and it helps them.