Hi, I'm new to these forums, and I'll be glad if someone could help me.
I have a Nexus 4, which has served me well for a long time. I'm not in a financial position to upgrade and I feel that the phone is still fast enough for my needs. However, I have been experiencing a very annoying issue ever since I upgraded to Lollipop back last year. The phone is currently up to date and was running a custom rom before i reverted to stock to upgrade to lollipop.
The issue is that after a while, the phone will just stop loading videos (on YouTube/Vine/Twitter). This wont be fixed until I reboot the phone. This happens almost every day and is extremely annoying. Changing from AwesomePlayer instead of NuPlayer in dev options also doesn't help. I've performed a factory reset, to no avail. Clearing cache also didn't help.
I don't know what to do any more. Any help would be appreciated.
Related
Heya,
So i experienced a lot of problems with the stock ROM on my S4 taking up way too much space and being kinda slow and crappy, so after hearing of CM and the speed increases and benefits it can have, i decided i'd give it a go, and for about a year now its been my daily driver.
However it has some issues, which are recently becoming more of a problem to me.
Now the first one might have seemed like a deal breaker to anyone else but honestly i wasnt too frustrated with it.
This issue is that the 3g connection with the device when im out and about straight up doesnt work. It shows red in the pull down menu and just doesnt work.
Next issue is that the camera has been severely downgraded in image quality.
Now recently i've been requiring the phone more than usual when out and about doing my job as tech support.
My issue is that i want these features to work correctly, but i dont want to run the stock ROM, can anyone advise how i can either fix these issue with CM or can you help me choose a different ROM which doesnt have these particular problems?
Run one of the Google Play Edition ROMs. Fewer problems will be had as these ROMs are versions of Android untouched by Samsung except for the inclusion of the libs needed to properly run the phone.
Another alternative is to go back to stock, but with the addition of some time spent in debloating the ROM, and with the addition of a new launcher to replace the stock version.
Excellent, thanks for the advice, i've now installed JFLTE after a bit of research and it's so far a very pleasant experience, ill report back if i have further problems with the mobile data connection but so far it appears to work.
Hello,
I am getting a 1 second sound delay effecting menu and all apps after the device is left on over night, tried factory resetting and with and without sleep mode. Has anyone else experienced this issue or have a solution for me?
Thanks
I was going to say the same thing. I have random one second lag in YouTube (rarely), BSDroid (always), but not in Plex or Kodi. The problem is fixed by pausing in YouTube and jumping forward on BSDroid. It's a big pain as these issues don't affect the chrome cast I have on the same TV and network.
I don't have to wait, it's pretty much out of the box. I have tried stock 5.1.1, rooted 5.1.1, CM12 nightlies, and all AOSP roms available. I feel like it's an issue with the Google Cast app? I'll try 5.1 and see if the situation changes tomorrow.
I haven't even bothered rooting mine yet, as this issue goes right down into the system. Even moving around the menu their is a 1 second delay in the sound. Only goes away with a reboot.
I think I may have found my issue, it seems that when I put the TV into PC mode to fix the overscan I get this sound lag after the TV turns off and then back on again. still troubleshooting it though.
Waited a while to get some new nightlies out and still the same problem. Tried 3 different TVs, all casted audio is delayed and has to be reset. Guess i have a junker now
I have an SPH-L720T I did saferoot on 4.3 back in May 2014. So rooted but stock. Phone has worked great ever since. I am an avid Ingress player and ever since September the game has started having a fit and crashing all the time. There is no consistency or pattern to the crashing. I can play for several hours, a few minutes or as the game is loading before it crashes. There were no major changes or apps I can recall installing prior to this happening. I think something changed with an update they made to the game (1.83.3), but I have no way of rolling back to find out if that will clear the issue.
I was in New Orleans for the weekend for an Ingress event and everyone was saying LTE is extremely spotty and unreliable in the french quarter, so after a few hours a lot of us realized that LTE wasn't going to work and switched strictly to 3G mode and were able to enjoy the game more. As the weekend went on I realized I was experiencing little to no crashing with the game. I had a few here and there, but so did everyone else, which is understandable given the huge bandwidth consumptions and usage of the game over the weekend.
I think the problem has something to do with network modes switching back and forth. When I got back home and turned LTE on I experienced the same consistent crashing all over again. I am currently in 3G mode only and going to test and see how the game runs over the next week. Sticking to 3G mode obviously isn't desirable... Looking for a solution without doing a factory reset and/or updating to lollipop as I have no other reason other than this game crashing and very much enjoy my phone rooted on 4.3.
Is there some way to force 3G mode only while this app is running or a longshot chance someone here happens to know what is going on/experiencing the same problem? Googling recent Ingress crashes/issues is a tricky thing...
Apologize if this is the wrong forum.
Thanks.
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Juandos23 said:
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Click to expand...
Click to collapse
Don't mean to scare you, but that is exactly what was happening to me right before going into an unrecoverable bootloop. Nothing I tried revived the device, although there have been some that have been able to. I ended up RMA'ing my device as nothing I did brought it back to life. You might be in a different situation but just giving you a heads up.
*Bump*
Stock 7.1.1 and rooted here. I've been on the official 7.1.1 release for our 6P's since early December, and for the past week or so, I've been experiencing freezing as well. I'd be in the middle of typing in Hangouts, streaming music in the car via bluetooth and Spotify, or just waking the phone up from sleep. For the past few days, I've been getting 3-4 freezes per day.
On rare occasions, I've left the phone alone to settle, and it returns to normal, but more times than not, a hard reset is the only 'fix'; until the next freeze.
I reluctantly wiped the phone, unrooted, flashed stock 7.1.1 and re-rooted all via NRT last night. The phone froze again this morning coming off the charger...
Granted, it decided to restore 528mb's worth of WhatsApp history as soon as I unplugged it (why it didn't restore on charger overnight is beyond me though). Will update if it freezes again.
The phone runs butter smooth with zero issues other than these freezing occurrences though. MO, the 6P is the best all-rounded phone currently available, even if it's a year old already.
Appreciate any help or suggestions!!
That's odd try ex kernel and over clock or try HEBF manager on play store
Quick update. Couldn't bear the multiple freezes per day, so I called Google to ask for help. Apparently I've done everything I can on my end (including a factory reset and updating to the latest firmware), so they sent out a replacement 6P to me free of charge. They'll also be covering the courier/shipping costs for my old 6P too. Fantastic customer service. Kudos to them!! I called them Tuesday morning (20th Dec) Australian time, and received my replacement 6P Friday afternoon (23rd Dec). Very quick indeed
Half a day after setting up my replacement 6P, including updating to 7.1.1, I started getting the same symptoms as my old 6P. Freezing, unresponsiveness, etc. Persisted for another day and had enough. I've since done a full wipe and downgraded back to the final 6.0.1 release, and it's been stable as a rock for 3 days now. No freezes, lagginess, nothing.
So I deduce it might actually be a software issue with 7.1.1, and not a hardware problem. It appears a growing number of Pixel and Pixel XL users are also experiencing random freezes on their new phones running 7.1.1 too...
Looks like I'll stick with 6.0.1 until Google makes a formal announcement and something is done about 7.1.1. I've missed Xposed and GravityBox too, so 6.0.1 is all good. Most importantly, it's stable
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
redduc900 said:
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
Click to expand...
Click to collapse
Thanks for the pro tip. I did consider doing that with the replacement 6P, but the only apps that I had installed were the stock Google ones that came with 7.1.1, WhatsApp, Facebook, Twitter, Instagram and SwiftKey. I just assumed if such popular apps were the cause, a lot more people would have pinpointed them as the problem?
I did however read a few users claiming SwiftKey to be the culprit prior to RMA'ing my old device, but even after uninstalling that from my old phone, I was still getting the freezing issues.
Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.