Related
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
j.smith said:
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
Click to expand...
Click to collapse
Definitely a feature. I love the clearer lock screen.
Bug: Haptic feedback vibration is very low system wide (not including soft keys).
Bug: Voice Dialer (Voice Dialler) is misspelled in the App Drawer.
Bug: Going to Settings > Display > Font Style causes a crash.
All I remember so far but there has been several.
Enhanced said:
Definitely a feature. I love the clearer lock screen.
Click to expand...
Click to collapse
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Enhanced said:
Bug: Going to Settings > Display > Font Style causes a crash.
Click to expand...
Click to collapse
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
rnewton01 said:
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
Click to expand...
Click to collapse
Go to Settings -> Wireless and network -> Wi-Fi settings. From this screen, hit your menu key and select Advanced and try changing your Wi-Fi sleep policy to Never... perhaps it's set to "When screen turns off" causing you to lose Wi-Fi whenever you lock your phone?
Oh, another bug possibly...
Go to Camera app and open Settings. Open the wrench tab and go to the 2nd page. Click the Update button beside Firmware update. Either of the next two menu choices ("Check version by network" or "Firmware update") seem to freeze the phone (power off required). Doesn't seem to happen all the time, but my first time trying to get the update to do something caused the phone to lock up in to camera mode.
Also, the "It will occur additional fee." message is quite fun... no idea what fees I will incur, or for what reason (and I won't even get in to the grammar issues).
j.smith said:
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Click to expand...
Click to collapse
Well it can't be a Froyo feature because no other manufactures use the same lock screen as they do. So it's a Samsung feature brought on by Froyo. Simply, it can't be a bug.
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
Click to expand...
Click to collapse
Yeah, I had to it some other font besides the default font...guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Enhanced said:
W..guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Click to expand...
Click to collapse
This is real Froyo from Rogers.
Anyone noticing that it's very glitchy and not smooth?
sirknattar said:
Anyone noticing that it's very glitchy and not smooth?
Click to expand...
Click to collapse
Its much faster and smoother than 2.1 stock was for me. Did you set it up fresh? Older settings can cause issues.
you guys have this issue? you may not even know it until you try to use mass storage mode. I use iSyncr (lets me use smart playlists based on ratings) so I need mass storage mode.
http://forum.xda-developers.com/showthread.php?t=907854
My wife and I (each have a Captivate) have had none of the bugs you guys have mentioned.
All we have experienced is a faster phone and WAY better battery life.
The only thing that upset me is that the update deleted my Ocean Wave livewallpaper, but I just redownloaded it.
Did some of you guys experiencing bugs ever run a custom ROM? I am thinking maybe these issues might be because you did...
Re: Haptic Feedback.
I've noticed it too, it's much weaker than before.
I could have sworn that I saw the option to turn up the intensity before, but can't find it now.
I want to update, but all these bugs are not very comforting
Jeffu said:
I want to update, but all these bugs are not very comforting
Click to expand...
Click to collapse
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
shawn122 said:
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
Click to expand...
Click to collapse
I gave it a go on your recommendation. Updated with no issues, now to actually try using it...
Has anyone rooted after applying 2.2? If so, what did you use?
I've been having issues turning on WiFi on my phone ever since I installed the update.
I accidentally clicked Airplane mode on my phone this morning, now my phone has been trying to turn the WiFi back on for about 5 mins....
As for battery life, my phone the first few days after installing Froyo seemed great, but now it doesn't really seem as good? No idea why....
And I've noticed a bit of lag at times while navigating on my phone.
Using LauncherPro Plus as my home screen, haven't rooted or installed any roms or anything.
I have noticed that when you turn the phone on from when it is off, if you don't wait for the wallpaper to display before swiping your phone on, the phone will stall. Mine stalled for about 5 minutes before it responded again.
I'm having a couple of small issues:
1) I can't get the GPS to look position. It just displays "Waiting for Location" and sits there.
2) OCLG - I got about 1000 on quadrant score. It doesn't seem laggy but I wanted to apply this lagfix to see if it can be better. I tried runnig the first option in the menu (z4 rooting), and it tries to launch either a page or the market (not sure which) but says "Page Not Found", but when you close it and press back, it says the root was successful, but all the other options are still "unavailable" so I can't apply the lagfix. There's a second method in the menu to do a root and that one fails as well, so I'm not sure how to get this working.
3) Camera - I got the same problem as a previous poster for the firmware update where it says "fees will occur" then when I click "yes", it tries to launch a page/market (again not sure) and says "Page Not Found".
4) Rooting - not sure how to root because the previous method of putting my update.zip and doing it through the recovery menu fails.
Any help is appreciated.
I was running rooted lagfixed stock Rogers 2.1 before. Removed lagfix first and did a factory reset before updating to 2.2 through Kies.
After updating to 2.2 I re-rooted and lagfixed with no issue.
Things bugs I have noticed on my phone:
- Camera a few times had started up with a black screen only with usual camera options but it's as if it does not see anything from the lens (had done camera fw update on it. You can download it from Samsung Apps app)
- When viewing "Contacts" can't press Back button to exit it so I just press Home button. Small bug
- can't set up smtp outbound email settings on stock email app. Keep getting it can't connect with server even when manually inputting correct settings.
- Battery undetermined as i've been playing with GPS a lot testing it so it drains pretty quick.
- GPS - Had no problems with 2.1 (using GPS + "Use wireless networks") but it's been horrible on 2.2. Locks ok when stationary, fluctuating between 5-9 satellite locks (used lbstestmode to check) but when you are moving or when using it for Navigation, it will be ok for a short bit then would eventually start bouncing all over the place or start getting weak/lost locks. Was using it on the hwy one time and it would suddenly tell me to do a u-turn because it thought I was on a side road. (condition was clear and phone was by windshield).
What it did fix for me:
- Opening Gallery before would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2
- Running latest updated Maps would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2 but still somewhat useless because of issue mentioned previously.
I can live with all the bugs except for the abismal gps.
I am having a major issue with multi touch, and it happened on stock so I don't think it's the rom I'm running (CleanRom Dev).
If I let go of my second touch, the screen loses the first touch location. So, if I am playing Minecraft or Shadowgun, I'll use one touch to move forward, that works, then I'll use one touch to move the screen, that works, but as soon as I let go of that second touch, I stop moving; even though the first touch is still being held on the screen. This happens in any game I play, even with the HTC Gestures off.
I saw a couple other people were having issues with multi touch, but I'm wondering if this is a problem with the kernel or the device. I saw that h8rift mentioned that the kernel's multi touch is a hacky implementation.
Any information is appreciated,
Thanks.
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Edit:
Issue keeps coming back a few minutes after rebooting.
thebest said:
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Click to expand...
Click to collapse
Yeah, same here. It took me forever to figure out that it was HTC gestures that was the culprit
Sent from my HTC One X
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
edit: already said
ThisWasATriumph said:
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
Click to expand...
Click to collapse
Hmmm, maybe this should be under CleanRom development then. I may not have had it on stock, I thought I did, but I wasn't on stock for very long
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
rohan32 said:
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
Click to expand...
Click to collapse
Good to know, I was just worried that my phone was jacked up D: lol
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
I use Holo Locker does that cause issues?
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
Wow, that was the problem. Disabling Holo Locker, then turning the screen off and on resolved the problem. Weird....
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
You're a genius! Holo Locker was causing the issue. Thanks so much.
Yeah I had that problem too, it was being caused by HTC Gestures. I just turned it off because I didn't ever see myself using them.
now me too..but..
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
david244 said:
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
Click to expand...
Click to collapse
GOT IT. :silly::silly::silly:. (after alot of factory resets)
The trigger of the bug is If you select:
Personolize -> Lock screen style -> No lock screen
Try it.
you want to uncheck HTC Gestures. it is used for another purpose not what you think it is only used for when your phone is connected to tv.
Hello colleagues.
I'm new on this forum and, as others before me, first came to you with an issue and kindly asking for an advice.
Facts:
-I bought a HTC One S, new, sealed, 2 months ago. Since then I made the android updates required/indicated by the phone software. Also, I installed latest update for Maps.
- now on the phone there is: Android 4.1.1, HTC Sense version 4+, Software number 3.16.207.4
Issue (which is reproducible):
- few weeks have past and recently I observed a weird behaviour for Navigation:
- after the connection to GPS is made and if few seconds pass, the application ends with a message on the screen: Unforntunately, Maps has stopped, with 2 option buttons: Report and OK. Ofcourse I reported several time this error. This is very frustrating especially when driving.
I have also IGO8 on the phone at it is working fine, it connects to GPS fast enought, no problems.
I tried, as other forums stated, to uninstall Maps updates, to restart the phone. I did not reseted to factory defaults yet.
Did anyone encountered this issue in the past? If yes, what should I do?
Thanks in advance for your time and support.
Best Regards,
Adrian
Try going to settings, scrolling down to apps, clicking on all, down to maps. Clear Data and Clear Cache. Uninstall and reinstall. Maybe that will work...
Sv: Google Navigation suddently stops.
Uninstalling and/or clearing cache won't help. This is a known error on many many One S's when using a JellyBean rom. Google and thou shalt find.
You can stop it from crashing by tapping the compass symbol while in navigation mode. This switches to the 2D mode which for some reason works just fine.
dcaples002 said:
Try going to settings, scrolling down to apps, clicking on all, down to maps. Clear Data and Clear Cache. Uninstall and reinstall. Maybe that will work...
Click to expand...
Click to collapse
I did it already, before posting previous request...No improvement
Fruktsallad said:
Uninstalling and/or clearing cache won't help. This is a known error on many many One S's when using a JellyBean rom. Google and thou shalt find.
You can stop it from crashing by tapping the compass symbol while in navigation mode. This switches to the 2D mode which for some reason works just fine.
Click to expand...
Click to collapse
In deed, your proposal works. In 2D, the Navigation does not crash, in 3D - always.
Is there a way to activate the compass in 2D? The major drawback of the 2D is that the map is "not layed in front of you" as it is done in 3D.
Hi,
after updating my HTC U11 to the official HTC Android Pie Europe release, so far the only real problem i found is, that for some reason the commute notification of google maps are now shown as a notification within a notification. Before the updated they worked fine. If you don´t know what that is supposed to mean, see here:
imgur.com/SQ27lSW
So far that only happens to the commute notifications. Pressing on either of the settings buttons only leads to the commute settings where i can disable the notification completly, which is not what i want.
Before the update it was only one notification with the map in a size where you could actually see something straight from the notification.
I already tried deactivating the function and activating it a few days later withouth any difference. I also tried clearing the cache and data, as it is set as a system app so that is the closest i could get to an uninstall.
As far as i know, i can´t really make a useful bug report through the app itself, as it is a notification i can hardyl make a screenshot of with the integrated bug report tool.
I also tried looking at the notification logs, but could´t see anything out of the ordinary with my simple knowledge of it: imgur.com/Fk9U0dk
After living with this "problem" for the last few months, I wanted to see if someone had the same problem and maybe found a solution in the mean time, which lead me here in the hope of finding such an answer
Thanks in advance for your help
Hi.
Last week I decided to reflash my U11, it's a Europe Pie version too, aka HTC__034. I had several bugs, with apps crashing like Google Assistant, the Dialer (unable to type a number or letter) and others. Flashing the RUU went fine and I got rid of those bugs, and even got better SOT than before (from 4 to 5 hours).
Reading your message, I just realized that I also got rid of another bug I had with the Google Phone dialer app. It also had such nested notifications when I received a call. Now it works fine.
So maybe flashing the RUU could solve your problem.
Hi kurtschmeichel,
thanks for the quick answer.
From what i read, flashing the RUU also clears all your data and settings, or did I get that wrong? As this is currently the only "problem" I have, I think I will not take this route as this entails a lot of reconfiguring.
Yes your phone will be "like new". You have to backup ALL your data before flashing a RUU.
I'm using a Pixel, still on Android 9, and my orientation sensor (and accelerometer) have suddenly stopped working. However, it appears that it's a software issue as the auto-rotation still works when in Safe Mode. I've uninstalled every app that's been updated in the past two days (roughly when I think this problem began) but it's still a no-go. I've also installed a sensor test app and I find the sensors do work initially on boot, but freeze after 5 seconds or so.
Any ideas of how I might fix this?
Clear system cache.
You update, install or uninstall any apps recently?
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
ppuzzlerr said:
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
Click to expand...
Click to collapse
Factory reset time...
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
R
BHZero said:
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
Click to expand...
Click to collapse
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
blackhawk said:
R
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
Click to expand...
Click to collapse
Thanks for the help! How do I do this?
The return to factory settings is in the app under settings.
You can try uninstalling it otherwise.
I don't see that option all the time and you may have to hit uninstall for it to appear.
A forced stop might be enough for troubleshooting.
Typically I use my package disabler for things like this.
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
BHZero said:
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
Click to expand...
Click to collapse
I'm not, Gmaps updates are a back street abortion.
So it was the update that trashed it?
I always keep gmail and maps on the factory load version. Invariably updates make them less user friendly on a Samsung
I set Playstore settings for auto updates by wifi only.
I always keep wifi disabled, effectively preventing any auto updating. I also firewall block and disable Playstore unless I need it. It's a background pocket hog.
Updates generally cause more harm than good if the app is already running well...
I have the same issue, and after guessing which app was causing the problem I found out it's the Google app. I disabled it and all the sensors started working back and also automatic brightness. Also I tried leaving the beta updates of the Google app and whenever the Google app is active the sensors stops working. Probably Google trying to kill the pixel 1 or a new function conflicting with the sensors
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Same problem here, since a couple of days ago, some sensors (gyro, light, accelerometer, compas) stop working after a couple of seconds after reboot. I factory reset my pixel, I tried uninstalling GMaps, I tried deactivating Wifi and Bluetooth,... but nothing is working.
Proximity sensor still work though.
gmsalomao2 said:
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Click to expand...
Click to collapse
Have you tried disabling Google app as mentioned by cristejeda33 above?
I have the same issues, it happens when one or more apps get updated, don't now which one is causing it exactly, but the issue goes away after the next update, and comes back at the next update and so on ..., features like, adaptive brightness, tap to wake, lift to wake, display rotation os and in camera, youtube video rotation....... stopped working and the battery is draining a lot faster. thinking of getting rid of the good old pixel ..
blackhawk said:
Have you tried disabling Google app as mentioned by cristejeda33 above?
Click to expand...
Click to collapse
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
gmsalomao2 said:
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
Click to expand...
Click to collapse
Try disabling Google play Services... just a wild guess.
It's a dependency or a parent app of Google App that's maybe causing the trouble. These can be hard to ferret out... play with it.
You could just go shotgun and revert all Google apps to factory load version -if- it wasn't a system wide firmware update that triggered it.
I've experienced this too many times, updates break things.
On my N10+ I lock down all updates, especially firmware. I'm rarely updated anything because it causes trouble. Result is a very fast and stable operating platform with minimum maintenance required. When there is an issue it's much easier to track down as the system is a known and familiar quantity. My current load is over a year and a half old... still running strong.
Wife and I are using OG Pixels and a couple of weeks ago we both noticed massive battery degradation. Then we both realized that auto rotate is extremely slow as are a bunch of sensors. Skymap doesn't track anymore. Both our phones also get extremely hot.
Google brought us here and we see that stopping the Google app makes the sensors work normally again. Lots of issues being reported in the playstore for this app also. Would love to hear if anyone has made any headway working around this or are we screwed until an update comes out?
What's the best way we can report this to Google publicly? And put the link here
All accelerometer, compass, gyroscope and proximity sensors turned off a few days ago on my og pixel and after disabling the google app all the sensors are working again.
I had a look on the play store and the last update for the google app was on the 21st October, which is exactly when it broke.
I disabled google maps first, then the google app, then sensors worked, so i re-enabled the maps app, I then cleared the cache on the google app and re-enabled that too, and all is still working.
Thank you very, very much for finding the cause of this, I was about to factory reset the phone and then have to reload everything which may or may not have worked anyway. Your efforts are much appreciated, long may your technology function correctly.