Related
I am losing my mind with my GPS. I have had my TP2 since last August and I have never been able to find a solution to the horrible GPS quality. I have tried matching up the ports, changing the ports, different software, hard-resets, I have installed the hotfix, I have called HTC, but things are still terrible. The only thing that ever cause an improvement was manually choosing the ports and such, however the improvement was only slight.
I have used GPS on Google Maps on the iPhone under the same provider (Optus in Australia) and the moment I opened the program there was always a GPS lock, not once did I ever have to wait or get it ready, but on my TP2 using Google Maps (or any other application), sometimes I am forced to wait minutes before getting a signal, if at all. I have searched and searched for a resolution but im not finding any. I just don't understand what I paid top dollar for, I chose the TP2 over the Xperia for it's GPS capabilities, but its hardly capable. I feel as if I am out of options, i've had it for too long to get my money back; I would really appreciate your thoughts on this?
I use iGuidance2009 and have no problems, though I do update quickGPS regularly. Google Maps I dont know about as I dont use it.
This has been a problem ever since the Touch Pro. My old Kaiser never had these horrible GPS issues, Touch Pro and Touch Pro 2 do.
What I have found to work well is to toggle the phone in the Comm manager when GPS is not working correctly.
Also, if you can get AGPS to work correctly, that does wonders for GPS lock time speeds! It would take minutes before, but once AGPS is set to work correctly, I can get a lock in 10 seconds! You have to go into the registry and make sure AGPS is set to use the right data connection.
This only improves acquisition times, it does not reduce the lag which was introduced in the original Touch Pro.
Google maps is probably the worst test app for speed. I use TomTom and iGo on Juicy R5 now, default rom before, and both have no lag. Google maps lags as much as 30 seconds, Garmin and also a few free gps apps I tried lagged 10-15 secs. So this is really, really app dependent. Don't know why.
As for lock speed, agps is a must. If QuickGPS/SEASGEE isn't working then you get the same lock speeds that you would get on old, old car gps systems (up to 5 mins to get a lock).
petard said:
This has been a problem ever since the Touch Pro. My old Kaiser never had these horrible GPS issues, Touch Pro and Touch Pro 2 do.
What I have found to work well is to toggle the phone in the Comm manager when GPS is not working correctly.
Also, if you can get AGPS to work correctly, that does wonders for GPS lock time speeds! It would take minutes before, but once AGPS is set to work correctly, I can get a lock in 10 seconds! You have to go into the registry and make sure AGPS is set to use the right data connection.
This only improves acquisition times, it does not reduce the lag which was introduced in the original Touch Pro.
Click to expand...
Click to collapse
It's just you with such serious problems, maybe your phone has problems..
AGPS is key to getting a fast lock. That's where you should be focused.
Some registry tweaks may improve your fix. It rocks for me and others owners, but not sure for every body.
take a look there:
http://forum.xda-developers.com/showthread.php?t=523676
and there:
http://forum.xda-developers.com/showthread.php?t=524655
It could be a good beginning ;-)
khaytsus said:
It's just you with such serious problems, maybe your phone has problems..
Click to expand...
Click to collapse
No, its not. Everyone has position lag. It isn't unbearable, but it is pretty annoying. You take an exit on a highway and it takes about 3 seconds to realize you took it sometimes. What is really weird is it keeps going on one road while the arrow turns in the direction you are headed until it finally places you on the correct road. That part may be due to TomTom though, but I'm not sure.
petard said:
You take an exit on a highway and it takes about 3 seconds to realize you took it sometimes. What is really weird is it keeps going on one road while the arrow turns in the direction you are headed until it finally places you on the correct road. That part may be due to TomTom though, but I'm not sure.
Click to expand...
Click to collapse
As per my personal experience, this is due to internal GPS data filtering by WM, so tweaks recalled by woaloo (I mean reducing of WM's GPS-related data buffer sizes) can help here.
Be careful however with it as too low values will drives GPS to become "nervous" - your position will become unstable, starting to jump randomly with a radius of few hundreds meters.
Another reason of the lag is (most likely) related to the navi software one uses. I use iGO8 and there are for sure settings moderating position behavior from pretty quick (but unstable) to rather slow but noticeable more stable. I personally prefer this last one.
To the original poster, have you tried running a program like VisualGPS? If so, how much signal strength is it showing for the satellites? I see as high as 39 when indoors. I get quick and accurate locks and I am very happy with the GPS performance. I have to believe that you have a hardware problem.
As for the thread drift on the few seconds delay, yes, that is there, but not a big issue.
Personal experience with the GPS... initially could never get it to connect, basically because every time i tried i was inside behind venitian blinds..... never use GPS before so my bad.
Walked outside and it was great. About 10 secs or less to lock, the lag is only a couple of seconds, no more than 5 secs. Added the tweeks and it was improved slightly. The accuracy was within 5 meters or less (used the property boundries in google maps to verify).
Moving at high speed it was pretty good too.
Compared to other phones and iPhone borrowed from a mate there is negligable difference in the accuracy and lag.
BRETT
So the GPS performance on the Touch Pro 2 is not that much better than the Touch Pro? The receiver on the Touch Pro is extremely weak.
At my work we have a GPS re-radiator for use with the equipment that we build. Indoors using the re-radiator I can get a lock in seconds with 11 satellites (the signal is abnormally strong). Outdoors, I'm happy if I can get a lock with 7.
worwig said:
To the original poster, have you tried running a program like VisualGPS? If so, how much signal strength is it showing for the satellites? I see as high as 39 when indoors. I get quick and accurate locks and I am very happy with the GPS performance. I have to believe that you have a hardware problem.
As for the thread drift on the few seconds delay, yes, that is there, but not a big issue.
Click to expand...
Click to collapse
I did try something like that, not sure if it was VisualGPS but it showed me the strength of GPS signal and it was quite accurate with how the GPS appeared to be behaving.
I got the phone's motherboard replaced and that fixed the issue. Thank you all for the replies though, it was possibly faulty.
Have the new Energy rom on but used the GPS hotfix. Seems to have increased lock time considerably.
I'll keep an eye on it though in case the lock time increases...
Wonder if we can find an app that would imbed GPS co-ordinates in any pics we take... Got a Samsung S8300t as well & it does this though the GPS navigation software is non-existant....
ultramag69 said:
Have the new Energy rom on but used the GPS hotfix. Seems to have increased lock time considerably.
I'll keep an eye on it though in case the lock time increases...
Wonder if we can find an app that would imbed GPS co-ordinates in any pics we take... Got a Samsung S8300t as well & it does this though the GPS navigation software is non-existant....
Click to expand...
Click to collapse
One of the extra camera modes you can unlock in the TP2 is a geotagging mode that does exactly that. There's a number of ways to enable them...Rhodium Settings Tool has a switch for each of them individually (burst, sport, video share, and geotagging), or you can just run the cab below
....and, for anybody else on this thread who hasn't tried it already, I'd suggest checking out the cab fone_fanatic put together to help with GPS locks on the TP2, details HERE
I've been having issues with the GN2's performance while scrolling menus and playing games. Jetpack Joyride is the most noticeable, with it stuttering all throughout. This even happens with simple games like Scramble with Friends, making it more unresponsive than it should be. Plugging the phone into the wall seems to lessen the stuttering. It also appears that the longer the app is used it slightly lessens the stuttering.
Strangely, frame rates seem better while playing 3D intensive apps like Death Dome.
My Galaxy S2 did not have any of these problems throughout its entire life span, ever. It did everything buttery smooth, which is strange considering this phone is supposed to be more powerful. The stuttering isn't terrible, but it's definitely there, and I'm not exactly happy with it.
This occurs no matter how many idle programs are closed or what Launcher that is used. I've used TouchWiz, Launcher Pro, and Go Launcher.
Is anyone else having this problem? Is this something that can be fixed or should I return the phone for another?
make sure power save is not enable.go to setting and check
mintu123 said:
make sure power save is not enable.go to setting and check
Click to expand...
Click to collapse
Wow, hahaaa! Thanks a lot! That's silly to think that works. I felt like it was some sort of power related issue and was sooner going to overclock the CPU than suspect that option.
It didn't work immediately after disabling it, but once I restarted the phone everything was fine. THANKS AGAIN!!
In the interest of making things easy for those who are holding off on the KitKat OTA, I thought it might be a good idea to consolidate all of our experiences into one thread. This is intended to cover mainly the changes specific to this OTA over Razr M-flavored Jellybean.
I'll start with my experience/thoughts and edit in additional findings. (Note: I'm bootloader locked, and now unrooted.)
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
My opinion, overall:
It's a nice upgrade, but all of little problems I've encountered (bugs, Verizon blockades, the works) make this feel like a bit of a letdown after the 6-month wait. In the end, after just three days, I find myself wishing I could take the phone back to Jellybean.
Here's hoping for either some exploitable holes or maintenance updates.
My opinion
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
Worth noting that I am using an unlocked bootloader, with CWM and SuperSU (only really did this to remove VZW bloat and install Xposed)
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to show more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
ATTACK said:
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to so more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
Click to expand...
Click to collapse
Gonna be doing some more testing in that regard. Even my M7 with its garbage radios gets LTE just about everywhere in the Metro Detroit area.
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
I have had the KitKat OTA now for 2 days and haven't found anything major wrong. The changes to the keyboard bugged me but I use swiftkey so that was moot. I also have an issue I haven't seen listed yet. The new sound for screen taps....it seems to give that "popping" feedback (that ive seen listed as an issue on driver start-up) ALL the time. I maybe get 1 clear sound out of every 5-6 screen taps. That is the only real "problem" I can find as of this point though. Does anyone have any insight on that?
Also activated Dev Mode and changed to ART runtime. Might be placebo but app response seems to be noticeably better! Not groundbreaking by any means but better than 4.1.2 for sure. Overall I am happy with the upgrade. Rather, will be happy once a root exploit comes up (I miss my debloating! On that note though, disabling apps never seemed to work right with 4.1.2....after hitting disable the app would show back up in active processes after a short time. Now I've gone 24 hours and 3 phone reboots and that damn NFL app is STILL disabled and NOT running as a background process. Might just have been an issue with my phone in particular before, but its fixed now!)
I am generally happy.
It fixed all the issues I had with Dhackers KitKat.
and feels about the same once you have rid of all the Bloat.
I like and I am happy that we still surprisingly got the update unlike the Galaxy S3
Happy =)
Just wanted to comment on the heat issue mentioned above:
I have only had KitKat for 2 days but I have definitely noticed a difference in heat after extended use compared to JB. One of the things I really liked about my Razr M was lack of heat so hopefully this is a fluke and I wont notice it too much in the future.
---
With that said, no big issues.
I don't like the keyboard -seems smaller, or something, The heptic feedback seems to be different too (for the worse IMO).
The lockscreen number pad seems smaller - definitely liked the number pad from JB.
I had to change the messaging app (hated the all white/lack of contrast). Using "8sms" if anyone is curious.
I also changed launchers to use the google-now launcher so the "okay google" thing would work on the homescreen and also get the transparency notification bar. But, in doing that I did lose the circle widgets which I liked. Can't win for losing sometimes...
---
On a positive note, Chrome/google searches seem to be much faster. The UI seems about the same (no complaints with JB).
If battery life can increase then I'll be satisfied with update (so far, no difference).
My experience has been very positive. My phone was bootloader locked and not rooted before (and, of course, after) the OTA. I cleared the cache partition from the recovery menu post-install but have not done a FDR. General impressions:
-- UI is overall much snappier/quicker. Extremely noticeable.
-- Love the new quick settings panel that you can get to after pulling down the notifications shade.
-- KK's changes to how the SDcard works have not been a big deal at all for me. The native "Files" app seems to have complete read/write access, as does ES File Explorer.
-- Like the new clock feature to automatically add a "home" display when traveling outside a pre-defined timezone.
-- Hate the new way you set the alarm on the clock. (Really, whoever came up with that input method should be transferred to a department where s/he can never affect design decisions again.)
-- I miss the audio silencer/mute on the lockscreen.
-- Battery life has been interesting. When I first installed the update (morning of 05/15), battery life was definitely worse, probably by about 50%. It has gradually been getting better, however, and now is probably only about 20%-25% worse than JB. Why it would change I have no idea, but it definitely is (I've been keeping notes, and am sure it is actually happening). I have noticed, using the Battery History details screen, that there are a LOT less wakelocks in KK than JB. In JB, I used to see tons of "Awake" indicators on that screen that did not pair with "Screen On" indicators. In KK, there are very few incidences of "Awake" that are not paired with "Screen On." Someone smarter than me will have to explain how that translates into worse battery life.
-- It may be my imagination, but it seems like the battery charges faster w/ KK. If it's not my imagination, I wonder if that means that the apparent decrease in battery life is really an issue of improper calibration/accuracy.
I have not experienced some of the things others have reported:
-- No random reboots.
-- No changes to WiFi or 4G signals. I don't use Bluetooth so can't comment on that.
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
4039995825
GPlX said:
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
Click to expand...
Click to collapse
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Nidstang said:
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
Click to expand...
Click to collapse
Attempted a FDR on my phone, unfortunately it did not work for me. I will attempt to clear the cache partition to see if that may help the issue if
possible. So far i can only get the boot menu for a couple seconds and im lucky to get a selection in time.
EDIT: I cleared the cache partition, no effect. (NOTE: it seems to get into the recovery menu after selecting it at boot menu, you have to hold power & vol UP for a couple seconds)
crazy4android said:
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Click to expand...
Click to collapse
That is an excellent point. I'll shut off the optimization and will edit my results in after tinkering with it for a while.
EDIT2: Without doing speedtests etc. It is very noticable that the wifi has improved. Youtube & other apps load as fast as they did on 4.1.2
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
kashif87 said:
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you can uninstall updates to the cam in apps
bwer1233 said:
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
Click to expand...
Click to collapse
Lockscreen widgets were introduced in Android 4.2.2.
Just want to let people know that the Google Now Launcher is working great on 4.4.2 including the "ok Google" functionality.
You can't download it from the play store. I just grabbed the apk from this thread.
http://www.xda-developers.com/andro...-and-gpe-devices-apk-mirrored-for-all-others/
Sent from my XT907 using Tapatalk
rooted + cwm
can't use "memory" feature under settings, while calculating settings app would crash
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
tieuvienson2005 said:
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
Click to expand...
Click to collapse
There are many "phone info" apps in the Market. Or create the short cut with Activity Launcher.
Also the Cam sucks on my Wife's m so get the Lenovo from my Moto x signature link.
This caused tremendous slowdown and throttling issues on the S4 but not sure if it is still in effect on the Tab S. Anyone know?
In Wanam Xposed there is an option to disable DVFS under Advanced Settings. I did that and nothing exploded so we'll see. Apparently what DVFS does is dramatically throttle the cpu as the tablet warms up, supposedly to preserve battery life.
Appreciate some expert input on this
Could be 100% placebo effect but here is what I have noticed after disabling DVFS.
1) Tablet feels a bit smoother overall.
2) Previously I noticed after browsing for a while, the keyboard input would begin to bog down. Now that seems to not be happening.
3) Previously after browsing for a while my memory usage would go to 90% and I would have to clear it. Now after an hour of browsing, typing in forums and watching videos, memory usage is only 69%.
So, as I said have no idea if these things are purely coincidence with no meaning. Simply reporting observations. Placebo effect can be strong.
for me, swiftkey seems to lag out horribly in Hangouts if a lot of things are in the memory..hangouts itself sucks and is much laggier when used on a non-stock android device, and swiftkey can also be called lagkey, so when you mix those two on the samsung devices, you have lag central. my GS4 had the same issue. when i clear out everyhting, it seems fine. maybe i'll look into this and see if that fixes it.
jayochs said:
for me, swiftkey seems to lag out horribly in Hangouts if a lot of things are in the memory..hangouts itself sucks and is much laggier when used on a non-stock android device, and swiftkey can also be called lagkey, so when you mix those two on the samsung devices, you have lag central. my GS4 had the same issue. when i clear out everyhting, it seems fine. maybe i'll look into this and see if that fixes it.
Click to expand...
Click to collapse
Yeah run it up the flagpole and see if you can feel a difference.
I tried Swiftkey and gave up on it. It kept freaking out and starting new words in the middle of words I had already typed. People seem to love it but for me it was complete fail. I'm back to the Stock keyboard after running this fix and typing seems much more consistent with no slowdown at all. Would be curious to hear additional feedback.
Other than that everything else just sort of "feels" better although it's hard to actually quantify it.
I have an htc one m8 with android 5.0.1 (lollipop). I am experiencing some stuttering issues. For example, in the app drawer when I scroll up and down for a certain period of time slowly (like for a 1 minute or so), there will be a glitch/stutter where the scroll quickly and automatically goes to next page (it is almost like the app drawer just blinked and refreshed but it shouldn't be doing that right?). After that stutter/glitch then no more glitches/stutters occur.
It usually happens when my cell signal is weak
OR
If i turn ON the cell radio or WIFI after being exiting airplane mode, the phone starts connecting to the wifi or cell signal and a stutter in the app drawer occurs.
But the scrolling everywhere else is fine (ex.scrolling in homescreen pages). There are no glitches,stutters etc. anywhere except for in the app drawer.
So is it doing that since the phone is trying to connect to the wifi/cell radio and causes the stutter?
I suspect that many users will not have experienced this issue even if it exists because not everybody would be focusing so much time scrolling in the app drawer like I do for no apparent reason anyway lol :laugh: . I just wanted to know if it is normal on every htc one m8 or not.
Let me know if I am not being clear enough, thanks!
hc p304 said:
I have an htc one m8 with android 5.0.1 (lollipop). I am experiencing some stuttering issues. For example, in the app drawer when I scroll up and down for a certain period of time slowly (like for a 1 minute or so), there will be a glitch/stutter where the scroll quickly and automatically goes to next page (it is almost like the app drawer just blinked and refreshed but it shouldn't be doing that right?). After that stutter/glitch then no more glitches/stutters occur.
It usually happens when my cell signal is weak
OR
If i turn ON the cell radio or WIFI after being exiting airplane mode, the phone starts connecting to the wifi or cell signal and a stutter in the app drawer occurs.
But the scrolling everywhere else is fine (ex.scrolling in homescreen pages). There are no glitches,stutters etc. anywhere except for in the app drawer.
So is it doing that since the phone is trying to connect to the wifi/cell radio and causes the stutter?
I suspect that many users will not have experienced this issue even if it exists because not everybody would be focusing so much time scrolling in the app drawer like I do for no apparent reason anyway lol :laugh: . I just wanted to know if it is normal on every htc one m8 or not.
Let me know if I am not being clear enough, thanks!
Click to expand...
Click to collapse
I know it sounds basic and simple, but in most cases, a factory reset will fix those kind if issues.
UniversalKID said:
I know it sounds basic and simple, but in most cases, a factory reset will fix those kind if issues.
Click to expand...
Click to collapse
hey thanks for getting back to me! i appreciate it.
i already tried a factory reset as well as wipe cache too a few days ago
but it still occurs. so i am guessing this is not happening on your m8?
hc p304 said:
hey thanks for getting back to me! i appreciate it.
i tried a factory reset as well as wipe cache too
Click to expand...
Click to collapse
So still the same? Some heavy usage must be happening from an app maybe. Check under Power : Battery Usage.
Some app may be slowing down the CPU performance.
Try High Performance mode under Developer options.
UniversalKID said:
So still the same? Some heavy usage must be happening from an app maybe. Check under Power : Battery Usage.
Some app may slow down the CPU performance.
Try High Performance mode under Developer options.
Click to expand...
Click to collapse
all seems ok under the battery usage. but doesn't the high performance mode cause huge battery drain and is not recommended?
also, this isn't something that happens all the time, just when i keep scrolling a lot in the app drawer after i turn on wifi, the stutter occurs.
are you sure this isn't normal?
hc p304 said:
all seems ok under the battery usage. but doesn't the high performance mode cause huge battery drain and is not recommended?
also, this isn't something that happens all the time, just when i keep scrolling a lot in the app drawer after i turn on wifi, the stutter occurs.
are you sure this isn't normal?
Click to expand...
Click to collapse
Just try High performance mode, just to compare. See if it does the same.
Mine doesn't do that.
UniversalKID said:
Just try High performance mode, just to compare. See if it does the same.
Mine doesn't do that.
Click to expand...
Click to collapse
the stutter still happens in high performance mode after i turn off and then turn on wifi again
maybe you could try this:
first turn off wifi and data, and then turn only wifi on and then open the app drawer and scroll slowly back and forth for a few a pages about for like 30 to 60 seconds. wifi again
hc p304 said:
the stutter still happens in high performance mode after i turn off and then turn on wifi again
maybe you could try this:
first turn off wifi and data, and then turn only wifi on and then open the app drawer and scroll slowly back and forth for a few a pages about for like 30 to 60 seconds. wifi again
Click to expand...
Click to collapse
Tried it. No sttuter. But don't worry about it, maybe you have auto connect with saved WI-FI networks and stutter just when the device locks into a network.
I have auto connect and no sttuter. Just ignore it, it's a minor ''issue''