Just got this phone 2 days ago after years of nexus /pixel usage. Great phone but the camera freezes my phone about half the time. After launching the camera my phone will become nonresponsive and I'll will have to power cycle it to regain access. Stock rom, stock camera app. This also happens with ported Google pixel cam app.
I've tried factory resetting, clearing cache, and clearing program data several times. Is this an intermittent hardware issue? Should I just return or try exchanging it?
Exactly the same here. On two occasions the phone became responsive again after a few minutes but now is the second time it hangs and I'll have to wait for the battery to drain down.
Did you flash anything? I thought it might be because I flashed a custom kernel, rooted it with Magisk. But I guess not.
Happens on stock Camera app + Google pixel app.
rooted with magisk. everything else stock, stock kernel as well. I was able to force reboot it (vol up + power). but it happens pretty consistently with any carmera app
Same problem here after rooting with Magisk. I don't seem to have the problem with the open camera app.
My front camera is not even functional for me. I can even use face unlock as it says that another system app is using it. Also I can not even swap camera to the front facing camera. I called support and hope to hear something from them on it
I unrooted (flashed stock boot image in fastboot) and the camera freeze issue seems to go away... Pretty strange bug tho
Never realized how many ads there were until you stop using adaway
Try out Blokada! It's an open source ad blocker that uses a VPN to filter out ads instead of he hosts method that AdAway does. It doesn't require root.
I used AdAway for years, but finally switched to Blokada because it's a lot more convenient. You can enable and disable it on the fly and add things to the whitelist when you find pages you actually want to view are being blocked. As you may have noticed in your usage, when that would happen with AdAway, you'd have to figure it out and then reboot because Android doesn't reload the hosts until rebooted.
Please see my thread https://forum.xda-developers.com/oneplus-6t/help/camera-settings-crashes-t3865560
cool ill check it out... right now using vanced youtube and ms edge browser which has built in adblock. seems faster than chrome
you notice any battery drain from blokada?
I don't. Technically, running a VPN should cause _some_ amount of battery drain, but it seems negligible. My battery usage didn't noticeably change when I started using it.
Related
The surfaceflinger seems to have indeed been fixed, but there is still a memory leak in the system, which I now encountered it for the 2nd time. I wanted to make screenshots, but just after I made the 2nd one, the tablet soft rebooted. It didn't freeze, it didn't show any google logo, it went directly to the boot animation and then the tablet booted. This seems to have been fixed it, unlike the previous surface flinger issue where you needed a normal reboot.
Anyway, in the 1st screenshot you can see 44h of uptime, in the 2nd one I took a pic in quick system info which displayed 198mb of free ram, just after I cleared all the processes, but then the tablet immediately soft rebooted and apparently didn't save the screenshot.
Running "ps su" in terminal emulator showed 56 rss, if I typed "su" 1st and then "ps su" there were 2 rows, one with 56 rss and the second with 116 rss, so the surface flinger has apparently been fixed.
Running factory image 4.3, rooted, deodexed, stock kernel. Has anyone experienced this issue on 4.3 so far?
LE: Oh I forgot to attach the first screenshot, sorry. Anyway it's a pic from cpu spy, which displayed 44h of uptime, so it's not that important.
I had just nearly the same phenomen. But my n10 softrebooted when I was starting to examine the process table. I just had found surfaceflinger, so I'm sure it was not that process, but sadly I hadn't found the mem-eater, when the colored X appeared.
I had done a dirty flash from aokp-pub, so I am not sure to blame android-4.3. But mem-leaks stick like sh** on a shoesole, so I'm sure, if it does not result from dirty flashing, we will hear soon from a new memory leak... (hopefully in some opensource part - cm and aokp team are faster in n10 support then google...)
I haven't had a single reboot since I flashed 4.3. My uptime is up into the 90+ hours range, and it would be higher if i hadn't had to reboot to install root, Adaway and the AOSP browser. I mainly use the tablet to browse the internet (using the AOSP browser) and reddit (via reddit news app), plus some youtube videos (using the youtube app) occasionally. I rarely play games, though I have played a little Real Racing 3 since the last bootup.
My advice is to download the stock rom from the google developers website, and completely wipe the tablet clean via the "flash-all" script. Re-install only the bare minimum apps, and see if the issues persist.
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Amiga4ever123 said:
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Click to expand...
Click to collapse
Same here on Nova
Sent from my Nexus 10 using Tapatalk HD
Ladies and gentlemen, I present you the "suspect": Google's Chrome, the all time crap browser.
I also mostly use the AOSP browser and occasionally Opera for some downloads that I can't do with the stock browser. I installed Chrome a few days ago to see how it works in 4.3 and it does indeed work better, but the 1st memory leak I encountered happened the day I used chrome, I'm sure of it. I wasn't much impressed with it so I went back to AOSP browser and everything worked fine, then I decided to give it another try: bam, memory leak again, yesterday, the day I used chrome again.
Also, I read some comments on the forums about people having reboots on 4.3, WHILE using chrome.
In fact, in 4.2.2 while we had the surface flinger problems, I remember that chrome was the main cause.
I am back to using AOSP and Opera and everything is working superbly.
Amiga4ever123 said:
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Click to expand...
Click to collapse
malikalhaji said:
Same here on Nova
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Are you rooted? If so, there is a bug in SuperSU V1.41 which causes CPU usage to sit at 100%...
Ref:
http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
Yep rooted. My Chrome is disabled. I hope update supersu will solve the problem with cpu usage. Thx for info about it
stiggy2012 said:
Are you rooted? If so, there is a bug in SuperSU V1.41 which causes CPU usage to sit at 100%...
Ref:
http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
Click to expand...
Click to collapse
Same here, might be SU fault, but I was using 1.43 when the tablet starts to lag heavily without rebooting. Couldn't find what the culprit was, CPU usage was normal, there was plenty of ram, even tried killing all background apps and services with no luck. Not even a hot boot could fix the lag.
Since then I've updated to SU1.5 so we'll see how that goes.
Sent from my Nexus 10 using Tapatalk 4 Beta
I got a reboot last night. Opened Google Now and it went to the bootanimation. Stock 4.3 with the Flaming Monkey Kernel, SU 1.45. It was my first reboot since January, when I went to custom ROMs. Went back to stock kernel, we'll see if that helps. Also, what AOSP Browser are you guys using? The one from the Installer from the play store closes every 5-10 minutes, and the apk ripped from CM 10.1.1.0 crashes on start-up...And I stopped using Chrome in January, and never had a reboot until Chrome was installed on 4.3. Coincidence? Probably not...
Sent from my MB855 using xda app-developers app
Never had any issues even on 4.2.2 with any sort of memory leak. Was able to go at least 5 days without any reboots and that's with using the chrome browser. I haven't used 4.3 long enough to post my findings with it but so far after 3 days it seems to be about the same. The only thing I can think of is that I bought my Nexus 10 in May so I don't know if a newer hardware version would make any difference.
Also, those of you with random reboots have you tried updating your boot loader yet? Not sure if or how it would make any difference but it's worth a shot.
Sent from my Nexus 10 using Tapatalk HD
Hi guys,
Has anyone noticed heavy lag and freezing when using the phone. I don't have a lot of apps installed and i have disabled most apps that i don't use and the phone is still giving me issues.
Any advice is appreciated. [emoji4]
I switched from RAZR MAXX HD and this phone is a space rocket in comparison to my old Droid. Have you tried factory restore? Then if it lags - I would try to return it to Moto.
Check CPU utilization. Maybe some app hangs on. I've noticed that noozy (music player) lags like hell when album is over and player remains in notification bar.
emineh17 said:
Hi guys,
Has anyone noticed heavy lag and freezing when using the phone. I don't have a lot of apps installed and i have disabled most apps that i don't use and the phone is still giving me issues.
Any advice is appreciated. [emoji4]
Click to expand...
Click to collapse
I have the same problem, I tried to removing as much as possible automatic start calling but often when I uncheck the receiver this puts me "failed" in Rom Toolbox, I have tried Xposed Auto Boot module, but I do not feel that it works.
But for me, I have a lot of app instaled and my UI is very modified (Nova Launcher, Gravity Box, various Widget), so I know why he lag, but I still find it overheating lot and that's what most do slow.
Hi, I am having same issue. My configs was same as you, @Trinytix, but I had uninstalled all of them because lag issues. And now I continue to have same lag issues. When I use the standard cam for five minutes it become freezy and lag and sometimes I lose some photos. All the time it is burning. Just stops to burn when I leave it without work about 30 minutes. I think the problem is the snapdragon 810 but in other foruns some say that the problems with this processor was fixed.
I've been having similar issues, I got really into theming (using nova prime) the last couple of months and at the end of January the phone started to really lag hard. A couple weeks ago I stopped being able to open any apps other than the phone and google's messenger. I tried to factory reset from settings and could not (device gets stuck un the power down sequence), so I went the recovery mode route. reinstalled a fraction of my apps, put back a much stripped down version of my theme, and things were mostly ok, if a little laggy. However, the phone insisted that there was no SD card (internal or external) despite there being a 64GB card, which would sometimes show up when viewed in settings, some apps (podcast addict) were able to access the internal memory, but others couldn't (cameras, sms, photos, music). Yesterday the keyboard ceased to launch for more than a split second at a time, and would not take any input (you would not believe how infuriating this is unless you've experienced it first hand). In an attempt to regain some functionality I started uninstalling everything that I don't consider vitally important (bus app, podcasts, messenger) couldn't get through more than 1 or 2 at a time because multiple windows would stack telling me processes like "motorola" "android" and "media" had stopped. I did succeed in stripping away all the automation apps and theming apps (tasker, nova, icon packs, etc). I can't even place a phone call on the first try.
Oh and to add insult to injury I have to darned green lines about 0.5cm wide now.
Looks like hw problem or system got corrupted. Try to re-flash whole system but if is hw...
Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.
I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.
Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.
Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.
Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
TheNupster said:
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
Click to expand...
Click to collapse
A factory reset is probably the next step if you prefer not to root. Also try to identify the source with a monitoring app like BBS or GSAM (I prefer the latter). You'll need to grant a few extra permissions via ADB on an unrooted device to get the full picture. GSAM walks you through the procedure via the overflow (3 dot) menu. Good luck.
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
TheNupster said:
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
Click to expand...
Click to collapse
If it's the 1768 then the retail firmware should be fine (I'd say preferable even). Unless you need that extra software that is.
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
TheNupster said:
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
Click to expand...
Click to collapse
Did you grant permissions (via ADB) to allow GSAM to disambiguate resource consumption on an unrooted device. Try using Greenify to rein in bad app behaviors. Works a treat on rooted devices and *should* be effective on user installed apps if unrooted.
I'll try that. And yes, despite using my laptop to give GSAM permissions, it only showed Android system as using the power. I'll install Snapchat, see if the problem appears again, open GSAM, and give it some time. I'll also install the other app and set that up too.
Between those two, I should be able to determine if Snapchat is causing this issue; and if so, what part is. (Phone is unrooted, because I don't want to void warranty (Motorola needs to give me the key to root, and I don't want to do THAT just yet) so we'll see what happens)
Okay. After extensive testing, the phone has finally "cooled down". Snapchat no longer hogs battery, and now I get more battery life than before this problem even began. I wonder if, somehow, somewhere, a system file became corrupted, instead of Snapchat causing the problem...
Whatever the cause, a full system reset forced the loop to break.
Now I'll use Snapchat (and every other app) with caution now... I have a CPU monitoring app running 24/7 (it uses almost no battery)
Feel free to close this thread
So I have my phone rooted, mainly use it for music and video chatting with my fiancée (away at school). I currently have the latest LOS and Gamma Kernels installed. No BusyBox or anything like that. Just Magisk with V4A and the debloat module to get rid some of the baked-in apps that I use alternatives for.
I seem to run into this issue on a pretty regular basis. I'm noticing that it tends to happen most when the phone dies, but many of the features become unresponsive. The fingerprint scanner stops working, WiFi stops working and becomes unselectable, mobile data disables itself, the navigation bar becomes mostly unresponsive and does nothing when you tap the home or task manager button. The phone basically becomes pretty unusable.
I'm wondering if maybe this is something that I'm doing, or if it's maybe a bug within the LOS software? Is there any known fix for this? Am I maybe doing something wrong when flashing the ROMs and kernels?
Often times, maybe once every 3-5 weeks, I have to wipe the phone and re-flash everything, which is getting pretty annoying at this point since I often lose data on some of my apps, pictures that hadn't been able to back-up via Google Photos, etc.