Hi,
My father and I have nexus 4s, I've flashed mine with lollipop from an official image because I couldn't wait for OTA and father got the OTA.
My phone has never really run better while his has recently gotten some huge bug or a virus. The phone can't connect to play services, it can't install apps even from unknown sources, it cannot connect to a PC for data or camera
storage. And the weirdest thing is the fact that after a reboot all notifications and apps in overview stay, so in the overview is filled with like 100+ apps.
The whole thing seems locked down which is really weird, with a lot of experience with ROMs, android, bugs and bricking devices I've never seen anything like this, yet this phone has never been rooted or messed with.
I've managed to backup photos to dropbox because it was installed before the bug and now I've done a factory reset and will be keeping you up on the story.
Any similar situations?
EDIT 1:
It did boot on a 2nd try after like 15min, thats kinda lot of time to build up dalvik istn't it?
Related
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
Hi guys.
I'm here to share a problem I'm having with my Nexus 6P: it often gives a crash randomly, needing to be restarted by force.
This does not happen because of a specific app and sometimes happens even at boot , when Google logo still not appeared.
I already using the phone about two weeks.
I received him with rom stock 6.0.1 and had the upgrade to Nougat available.
I thought the upgrade to 7.0 would correct the problem, but it was not what happened.
From the update I also felt that the crashes were more frequent when the battery was at a very low level, between 20 and 15% (as commented in a reddit threat that I can't copy here).
Following some recommendations that I found , I formatted the Nexus 6P with the factory settings to see if the problem returned.
Yes, it happened again.
I formated again and was gradually installing my apps to check if it was not a specific app.
I did it at last three times.
On these occasions, apps like Google Keep, Duolingo, ES File Explorer, Google Fit, Podcast Republic and even the Play Store gave the crash.
I formatted again and installed each app one by one again to try to identify a culprit and had the same results.
To try to work around the problem, I decided to go for a clean install of the entire OS with the latest build using the SDK (adb and fastboot).
Even with the flash of the latest build I continued to have this crash problem.
So I decided to go for custom roms.
I installed Pure Nexus and Sinless, and continued having problems with crash.
I tried to install the CyanogenMod, but failed. After flashing the rom, GAPPS and vendor image, the device crash in the Google logo.
My last attempt was to go deeper and replace the kernel as well.
I installed ElementalX (7.0) and Pure Nexus as ROM.
In the beginning, I still had many crashes, so decided to make some changes in the kernel ElementalX.
In a desperate attempt, I decreased the CPU clock all to minimum (1248 MHz).
Interestingly the crashes started to occour less frequently, but they still happen randomly and unexpectedly.
I have no idea if this reduction in CPU speed had any effect or was placebo.
What matters is that I'm still having crashes and I wonder if anyone has any idea of this solution to my problem.
Thank you guys!
PS.: the return of the phone is not an option. I'm in Brazil.
PS2.: sorry for my bad english.
Wow you have exhausted every idea... Return sounds like all that's left unless you wanna try putting the phone in the oven to see if it's just bad solder.
Sent from my Nexus 6P using Tapatalk
I'm thinking you've got some damaged or corrupted internal storage there.
Sent from my Nexus 6P using Tapatalk
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.
Hello everyone, I did some searching on what I'm going to ask but it seems as though all I've read were due to rooting and pertained to logins.
I have a new Moto XPE running the stock Sept. 1st Patch. I can log into Snapchat just fine, my issue lies after I'm using the app. Messages won't load in Snapchat and stories become stock on loading as well. On some Snapchat stories that are loading, after looking at a few images, the screen goes black and is again stuck on loading. Eventually the app crashes and sometimes the phone will crash as well to the point where other apps like YouTube just won't open up and the phone will either reboot on its own or require one from myself manually. Has anyone with a Moto XPE or Moto X Play experienced any of the issues I've described?
Thank you.
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
jDally987 said:
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
Click to expand...
Click to collapse
It happened on my BlackBerry Priv too. I just switched over from that device a few days ago
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
iks8 said:
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
Click to expand...
Click to collapse
Yeah same here, it can get a little laggy sometimes for me but I just log out and back in and it works fine.
This might not be here nor there for this specific issue, but if you use Xposed/Snapprefs/rooted etc etc...One thing I noticed that REALLY causes a lot of lag with snapchat is overlays. Especially the FB Messenger app. If you have those chat heads on your screen with Snapchat open as well, things are basically unusable until you get back to the home screen and force close both apps. Could be happening without Xposed as well. Just a thought.
On a side note about Snapchat in general- it has always run like crap on every phone I've owned.
Snapchat kept screwing up, even tried the beta. Decided to try Casper and so far it's working great
So I am debating on loading a custom ROM. I have had the lineage rom on my Nexus 6p before. But it went in for warranty repair and I have kept it stock since. I have noticed that after some time on Oreo and all the apps I use, it was getting a bit slow... so I factory reset it and it seemed fine for a while. But now it is back to acting up where occasionally I get majorly bad lag time when launching apps or even trying to access the keyboard. I don't know if this is an OS problem under load or perhaps a hardware problem. Does anyone know if putting on a custom ROM (oreo) is likely to resolve this? I would hate to spend the time if it is a lost cause.
Even better... is there a phone app out there that will give me a real deep diagnostic of phone CPU and memory? Seems like antutu and all the others really dont do that much.