Related
I was never really interested in them and was happy to find out thats good, because they eat up battery..
BUT!! I just came across the Live Pond wall paper.. downloaded it and was in AWWWEE over the quality and look of it.. It really looks amazing and we all love bragging rights and showing off our phones and nothing IMO does it better..
My questions is simple..
How much energy is this really taking up? When I actually see my homescreen its about 1-3 seconds before I actually click an app that I need, the home screen is barley on.. My question is this thing running even when its not on the screen? for example I am surfing the web, or on a phone call.. Is it still running in the background? Or does it only start up when I see the screen?
Thanks!
i think some do, im not sure. but you can check, start up a wallpaper and go to messaging app or something, then go back. if the wallpaper starts up from the same spot when you first left the homescreen then its not running in the background, but if its jumped ahead, then it is. I dont think they kill the battery THAT much though.
Just use your phone with that wallpaper for like a week, the first couple of days its probably gonna seem like its killing your battery but that may be some kinda placebo effect because everyone says its killing your battery so it seems like it is. After a week you should know if its really killing your battery.
Thanks man!
What about the vibrating keyboard and such? I still have that on, because well.. I like it, but if it eats up power...
let me start over.
With all these threads has anyone ever tested things?
Is there a list of what eats the most to the least?
Not just the typical, turn off WIFI and go here and go there, but an actual list of what is more power hungry than not?
Depends on the rom really....other than the usual GPS, Wifi, 4G and whatnot, i think it depends on the person and their use.
For me of heavy heavy use today, i squeezed out 7 hours on CM6 with wifi on, vibrate on my keyboard, display close to 50%, screen never off, music always on the whole 7 hours, twitter updates every 15mins, wordfeud running in the background...7 hours is pretty decent with all of that. But at the same time I didnt have autosync on..
Autosync is a guzzler no matter what rom you're on. Autosync is also pretty much unnecessary..just think about it:
Weather - this is a mobile phone, you know the weather when you step outside
Google - Autosync contacts is a waste unless you are always adding contacts
gmail: is important if you have to have an email the moment it is sent, if not, no need, just open the app
calender: you dont really need this either if you can pick a rom and use it for more than a week
facebook sync: waste. after you first sync contacts for their pics you dont need it anymore, unless you MUST have that person's current profile picture
twitter: depending on which app you use, you dont need this. if you dont use HTC peep, then you do not need this at all, just edit the notification settings in the twitter app you use.
Sound and Vibration on the keyboards havent killed my battery, and I don't see how it can, so I turn them on for some keyboards because i find it easier to text with the vibration on with some keyboards.
Some of the kernels out there are part of the whole placebo effect I think. Like with Havs, every single kernel with that option runs the same and gives me the same battery life, I havent used one kernel (either King's, Netarchy's or Snap's) that just blew my mind with battery life, i pretty much get the same no matter what when compared to stock. The kernel I like the most is the latest CM nightly kernel, that kernel is doing work for me, and I see a difference with it, so I have to keep it.
At the end of the day, it's all up to you. You gotta take what everyone else says with a grain of salt, cant take it to heart since everyone uses their phones differently. There are way too many variables you have to take in account before you can trust someone else, like..some people's batteries are newer than others, some ppl are on different roms and kernels, some people have autosync all on or data always enabled or disabled..you really just have to play with it for a good week with what you think will save battery before you can come to any conclusions.
ms79723 said:
Depends on the rom really....other than the usual GPS, Wifi, 4G and whatnot, i think it depends on the person and their use.
For me of heavy heavy use today, i squeezed out 7 hours on CM6 with wifi on, vibrate on my keyboard, display close to 50%, screen never off, music always on the whole 7 hours, twitter updates every 15mins, wordfeud running in the background...7 hours is pretty decent with all of that. But at the same time I didnt have autosync on..
Autosync is a guzzler no matter what rom you're on. Autosync is also pretty much unnecessary..just think about it:
Weather - this is a mobile phone, you know the weather when you step outside
Google - Autosync contacts is a waste unless you are always adding contacts
gmail: is important if you have to have an email the moment it is sent, if not, no need, just open the app
calender: you dont really need this either if you can pick a rom and use it for more than a week
facebook sync: waste. after you first sync contacts for their pics you dont need it anymore, unless you MUST have that person's current profile picture
twitter: depending on which app you use, you dont need this. if you dont use HTC peep, then you do not need this at all, just edit the notification settings in the twitter app you use.
Sound and Vibration on the keyboards havent killed my battery, and I don't see how it can, so I turn them on for some keyboards because i find it easier to text with the vibration on with some keyboards.
Some of the kernels out there are part of the whole placebo effect I think. Like with Havs, every single kernel with that option runs the same and gives me the same battery life, I havent used one kernel (either King's, Netarchy's or Snap's) that just blew my mind with battery life, i pretty much get the same no matter what when compared to stock. The kernel I like the most is the latest CM nightly kernel, that kernel is doing work for me, and I see a difference with it, so I have to keep it.
At the end of the day, it's all up to you. You gotta take what everyone else says with a grain of salt, cant take it to heart since everyone uses their phones differently. There are way too many variables you have to take in account before you can trust someone else, like..some people's batteries are newer than others, some ppl are on different roms and kernels, some people have autosync all on or data always enabled or disabled..you really just have to play with it for a good week with what you think will save battery before you can come to any conclusions.
Click to expand...
Click to collapse
Thanks.. whats CM6?? Is that stock??
I just noticed the live wallpaper with the fish is NOT running in the background.. As when I open something up, the fish are in the same spot as when I left them, lol..
fastfed said:
I was never really interested in them and was happy to find out thats good, because they eat up battery..
BUT!! I just came across the Live Pond wall paper.. downloaded it and was in AWWWEE over the quality and look of it.. It really looks amazing and we all love bragging rights and showing off our phones and nothing IMO does it better..
My questions is simple..
How much energy is this really taking up? When I actually see my homescreen its about 1-3 seconds before I actually click an app that I need, the home screen is barley on.. My question is this thing running even when its not on the screen? for example I am surfing the web, or on a phone call.. Is it still running in the background? Or does it only start up when I see the screen?
Thanks!
Click to expand...
Click to collapse
Just thought I'd toss in that you can always go to Settings>About Phone>Battery Use to see what's using up your battery life. I know when I was running a live wallpaper (Galactic Core), it used up about 2-5% of my battery. Whether that's significant for you or not, I don't know.
Also, I would definitely recommend DLing and running JuicePlotter for this week of testing you're doing. That'll give you some quantitative data.
fastfed said:
Thanks.. whats CM6?? Is that stock??
I just noticed the live wallpaper with the fish is NOT running in the background.. As when I open something up, the fish are in the same spot as when I left them, lol..
Click to expand...
Click to collapse
CM6 (cyanogenmod 6) is stock on steroids.
I have found that my One X often kills apps I have running when I press the power button and put it away for more than a few minutes. I know Android will try to reclaim resources starting with background apps but this is killing the app I am currently looking at.
I have almost nothing else running and my system normally has 200-300 mb of available memory so it is a very unexpected behaviour. A typical example is I have something like firefox displaying a page. I read a bit then press off. I come back 10 minutes later and it needs to restart and reload the page. With previous phones the app would still be in the foreground the next time I turn it on and unless I navigate away it would stay that way.
I have a nexus s running ICS and that does not happen.
I have a desire running GB and is doesn't hapen.
I have a desire running Froyo and it does not happen.
Is there any way to force a less aggressive memory management on HOX?
There is an option for this, in settings > developer options, furthest down under apps section, first one; "Don't keep activities" check if it is enabled.
Sent from my HTC One X using xda premium
.. also beneath it, there is a restriction "Background process limit", it may also cause immediate kills if "no background process" is set
Sent from my HTC One X using xda premium
Thanks for the suggestions but those were set normally.
Tried using the built in browser instead of firefox and the problem was significantly reduced. It seems the system has a bias against non google apps. Even so - this HOX is behaving different in this respect to my other phones. It is my expectation as a user that if I am doing one thing, that thing should still be there the next time I look at my phone.
Something on the device may be leaking and the result is this need to stop stuff. My money is on sense ( mainly because of the observed ripple/flicker on the home screen ).
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Seeing the same issue on my One S.
This happens with Dark Meadow. If the screen times out, or you hit the lock button, the game kind of "crashes". Not sure if this is the One X killing it or whether it's how the app is coded.
It's irritating anyway ><
Applications with a notification icon have not this behavior. Is there a possibility to set a higher priority to applications without root?
I'm having the same problem.
With cm9 @ Desire Z, I could, say, restore my 3000 sms within GoSMS (which takes a while) and meanwhile do whatever I wanted with the phone, eg. browsing, texting and so on.
With the H1X, after a certain time, the apps gets killed/suspended and therefore anything that happened within the app - which is pretty annoying. Any solution in sight?
H1X @ ARHD
I get this too. Annoying.
ViaraiX said:
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Click to expand...
Click to collapse
Sense launcher closing is not cos of the over-aggressive app killing. It's cos the system needs more RAM, so closes Sense since it's not directly in use right now. I do notice that some apps are getting closed after a period of inactivity, probably a default ICS setting that we can tweak when kernels and ROMs get more mature releases
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
harryshepard said:
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
Click to expand...
Click to collapse
If your battery is that bad you have a bad app running rampant or your battery is faulty.
For everyone else, even in settings if "Don't keep activities" is unchecked, try checking it and unchecking it. I read that sometimes it is still set to "Don't keep activities" even if it is unchecked and checking and unchecking it could solve the problem if this is the case. Doesn't hurt to try.
Hopefully one of the devs will make a Rom/kernel with better oom adjustments... I'm hoping.
the multitask implementation on this phone is terrible. I was using runkeeper, stopped to check something in my settings during the ride, phone closed the runkeeper application deleting my ride. It is getting annoying ...
Now that ics has been out for a while, is it a good idea to have this on?
It does make the phone faster and only affects two of my apps but i still dont know how does it affect battery or RAM(i read somewhere it affects ram)
Do you guys use it?
Sent from my Galaxy Nexus
It's useful for scrolling in 2d apps. Although on xda makes the pictures not come up. I only use every once in a while.
Sent From My Sprint Galaxy Nexus
I've chosen to not use it. It was useful in the early days when not a lot of apps worked well on ICS, but nowadays it breaks more than it fixes in my experiences.
I don't use it. I find it makes many apps laggy. Though it does boost a quadrant score.
In theory, it would be better to the let the GPU render stuff as it takes the strain off the CPU. Too bad it breaks many apps, though.
nope dont use it. does more problems than good
I use it, never encountered any of this, EXCEPT for a GUI glitch in Power amp. Besides that, every works perfectly.
On side note, back when the Samsung Vibrant first got ICS (somewhere around December), I found that many apps just crashed when using it, such as trying to pick out a wallpaper in GO SMS. Nowadays, nothing besides that Power amp glitch I've noticed. And battery life is somewhat better too.
Sent from my Galaxy Nexus using Tapatalk 2
The United Airlines app used to have problems when this was on -- would show up as an incredibly tiny rectangle on the screen, as if scaling was totally thrown off. I was flying a lot then, so I unchecked the option. The United app has been updated a few times in the past few months, and I tried checking force GPU, and the latest version of the United app works again... I've got 104 apps installed, and the only other one I've seen that complains is Flipboard -- got a message once, yesterday, that it's not designed to work with forced GPU and that I should turn it off. I ignored the message, though, and Flipboard seems fine -- as does everything else I'm using.
I'll leave it turned on until / unless I run into incompatibilities with apps that I find important...
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.
Hello everyone, im going to choose a phone for my cousin and i was looking to s20+ exynos. Its a great phone but when i bought it in 2020 summer, it was heating up a lot even when doing normal tasks like using chrome or watching youtube. For comparison, when using zoom s20+ got up to 42-43 Degree battery and was really hot, same conditions s10+ was something like 31battery. After 2 days i returned the phone. Now i suspect this was due to software problems and wanna know if phone still heats up like this during normal use.
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
blackhawk said:
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
Click to expand...
Click to collapse
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
theblitz707 said:
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
Click to expand...
Click to collapse
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
blackhawk said:
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
Click to expand...
Click to collapse
just out of curiosity, what did you do to stop your phone from overheating?
theblitz707 said:
just out of curiosity, what did you do to stop your phone from overheating?
Click to expand...
Click to collapse
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
blackhawk said:
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
Click to expand...
Click to collapse
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
theblitz707 said:
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
Click to expand...
Click to collapse
That's a minimum. When Gookill is misbehaving it's battery usage far exceeds that and extends into when the screen is off.
My battery usage when sleeping with AOD on touch demand is 2-3% for 6 hours.
That 1 or 2% is also after much of the Gookill junkware was disabled.
Google and Samsung apps are the prime suspects... as usual.
My stock 10+ is heavily reconfigured, I have no quick fixes for you because none of mine were quick
As for updates, they ain't got nothing for me. Last thing I want is Q loading on this device.
It would gut Karma Firewall's functionality and destroy trusted overlay apks... for what?
I've already archieved all my favorite apks so I'm not longer dependent on Playstore. Playstore will eventually alter or delete them.