Database Info

No matter what ROM I flash, my phone ends up slow as hell

What is wrong with this? My current ROM, like most ROMs, started off fast as anything. And it is still relatively fast, it is just it has immense trouble with Text Messages, and crashes frequently when I try to use them.
Is this a Windows 6.5 problem? Is this a Windows problem? Is this a TouchFlo 3D problem? Why does it just gunk up and become almost unusable so much? I love Windows Mobile, but I just wish it would work.
Guess I'll be flashing it again soon.

well 6.5 roms around are still beta roms
so they are bound to have some issues
also if you install other programs which slow
your device down then slow is what you get

I don't install programs to slow my phone down. And I don't install many programs. Beejive and Opera are all I install. But I still have to soft reset my phone very often.
My Windows 6.1 ROMs had the same issue, except everything was slow as can be.

Try the process of elimination. Flash the phone, after it finishes and gets to the part where you align the screen, HARD RESET it again. Let it proceed til it is finished. As much as a pain in the rear, DON'T install ANYTHING other than what it came with, & DON'T tweak anything. Run it for a couple days and see what happens. If it is ok, install ONLY one program, run it for a few days and so on, adding programs one at a time, using it for a day or two and see if you spot anything. If it continues to run ok, then tweak one thing at a time.
If, on the other hand, a bare install, it still locks up, try just a different radio, or, take it all the way back the way it came from the factory, including the radio, and the SPL. Then, install (if it is an at&t phone) the factory issued update, and see what happens. If it still is acting up, warranty it for another one, sounds like a hardware problem.
Tracking down intermittent problems is a PITA, but, you have to have a lot of patience, and try things one at a time to see what is causing the problem.

p51d007 said:
Try the process of elimination. Flash the phone, after it finishes and gets to the part where you align the screen, HARD RESET it again. Let it proceed til it is finished. As much as a pain in the rear, DON'T install ANYTHING other than what it came with, & DON'T tweak anything. Run it for a couple days and see what happens. If it is ok, install ONLY one program, run it for a few days and so on, adding programs one at a time, using it for a day or two and see if you spot anything. If it continues to run ok, then tweak one thing at a time.
If, on the other hand, a bare install, it still locks up, try just a different radio, or, take it all the way back the way it came from the factory, including the radio, and the SPL. Then, install (if it is an at&t phone) the factory issued update, and see what happens. If it still is acting up, warranty it for another one, sounds like a hardware problem.
Tracking down intermittent problems is a PITA, but, you have to have a lot of patience, and try things one at a time to see what is causing the problem.
Click to expand...
Click to collapse
Hey, thanks for the advice. While you're here, what do you think of radios? My latest flash, the internet runs EXTREMELY hot on my phone, and it's never come close to that hot before. Think I could process of elimination solve this with new radios? Or new roms?

thehyecircus said:
I don't install programs to slow my phone down. And I don't install many programs. Beejive and Opera are all I install. But I still have to soft reset my phone very often.
My Windows 6.1 ROMs had the same issue, except everything was slow as can be.
Click to expand...
Click to collapse
I can confirm major issues with 6.5 roms and beejive. However, I cannot remember what actually took place because I removed beejive from my device within an hour of installing it.

I guess it could be the radio. If one isn't up to snuff, and can't capture the signal then it might be trying to increase the power of the phone (transmitter) to get a good capture. I'm not up to snuff on the cellular radio, but, if it works the way I think it does, the phone uses the least amount of "RF" to get a good lock on the tower, so if the radio isn't "hearing" the tower, it has to crank up the power (even though these things only output less than a watt), the more power, the higher the drain on the battery. I had really good luck with the
1.02.25.19 Raphael radio, which fixed a bug I was having (and a lot of other people) with the GPS not locking. I then tried the newer 1.14.25.35 Raphael
radio, but, went back to the .19 radio because I was experiencing issues
with it not locking in HSPDA mode. It only wanted to lock in Edge only.
Tried flashing it several different ways, hard resets etc, no dice. I've
seen posts where two people have basically the same phone, but the same
radios won't work. Screwy...
Also, it will also depend on where you are located as to how hot your phone
might get. If you are at the fringe of a tower location, it's going to take more power. You might try, if your phone is locking in [H], to go into the comm manager, and switch off the 3G radio and, even though the internet will be slower, see if it still gets hot. If it doesn't, then that might be the issue, you're at the fringe of an HSPDA signal.
Try a different radio, can't hurt, and you can always flash back to the original radio, if you have it downloaded.
thehyecircus said:
Hey, thanks for the advice. While you're here, what do you think of radios? My latest flash, the internet runs EXTREMELY hot on my phone, and it's never come close to that hot before. Think I could process of elimination solve this with new radios? Or new roms?
Click to expand...
Click to collapse

redbandana said:
I can confirm major issues with 6.5 roms and beejive. However, I cannot remember what actually took place because I removed beejive from my device within an hour of installing it.
Click to expand...
Click to collapse
Beejive had a little issue a few weeks ago with logging on. I wanted to get a site-wide quest through the code or settings to see what it was using to log in.
But the issue is fixed, and Beejive works 100% the same it did on 6.1

p51d007 said:
I guess it could be the radio. If one isn't up to snuff, and can't capture the signal then it might be trying to increase the power of the phone (transmitter) to get a good capture. I'm not up to snuff on the cellular radio, but, if it works the way I think it does, the phone uses the least amount of "RF" to get a good lock on the tower, so if the radio isn't "hearing" the tower, it has to crank up the power (even though these things only output less than a watt), the more power, the higher the drain on the battery. I had really good luck with the
1.02.25.19 Raphael radio, which fixed a bug I was having (and a lot of other people) with the GPS not locking. I then tried the newer 1.14.25.35 Raphael
radio, but, went back to the .19 radio because I was experiencing issues
with it not locking in HSPDA mode. It only wanted to lock in Edge only.
Tried flashing it several different ways, hard resets etc, no dice. I've
seen posts where two people have basically the same phone, but the same
radios won't work. Screwy...
Also, it will also depend on where you are located as to how hot your phone
might get. If you are at the fringe of a tower location, it's going to take more power. You might try, if your phone is locking in [H], to go into the comm manager, and switch off the 3G radio and, even though the internet will be slower, see if it still gets hot. If it doesn't, then that might be the issue, you're at the fringe of an HSPDA signal.
Try a different radio, can't hurt, and you can always flash back to the original radio, if you have it downloaded.
Click to expand...
Click to collapse
Well, see, on other flashes, my phone did not get this hot. Not unless I had it on all night playing videos on my TV. Now it burns up in seconds. So I really doubt it's the radio... but I don't know what would make it do this.

thehyecircus said:
Well, see, on other flashes, my phone did not get this hot. Not unless I had it on all night playing videos on my TV. Now it burns up in seconds. So I really doubt it's the radio... but I don't know what would make it do this.
Click to expand...
Click to collapse
I had the same issue when I was flashing multiple ROMs till I read the thread about the rildll sticky on the first page of the ROM development section fo the forums. Once I installed the right cab file from the thread to my phone the issue was solved.

barrydavisjr said:
I had the same issue when I was flashing multiple ROMs till I read the thread about the rildll sticky on the first page of the ROM development section fo the forums. Once I installed the right cab file from the thread to my phone the issue was solved.
Click to expand...
Click to collapse
Okay I checked the thread out (even the "what is rildill?) but I am a little confused over what this is, and how I find the right one for my phone.
And I just install the CAB and I'm good? It sounds like it could be very dangerous...

depending on which radio you installed, you'll want to make sure you have the right rilphone file. I think if you install the wrong one, it won't work at all (as a phone anyway)..

The thing is, I never installed a radio. That is what confuses me about this sudden really hotness of my phone.

[Q] Should I consider a custom ROM yet?

So I'm looking over the current options and right now it's not really looking like it's promising. I have my Galaxy S3 rooted and with the help of tools like TitantiumBackup I've managed to clean up the stock ROM pretty well. Another thing of note is I actually get some surprisingly good sound quality out of my SGS3. I realize the US models aren't supposed to have the Wolfson DAC, but somehow mine sounds absolutely incredible with no noise that I can hear or anything (it's enough that I've been wondering if Samsung might have slipped the Wolfson into this one and perhaps there is variance in the DACs actually being used.) It even drives my headphones (modified HD555s -- basically you can consider them to be like the HD595s since of course I did the foam mod, but with the soundstage mod and a custom cable they're actually a bit better possibly) extremely well. It's worth noting that I have frozen the built in equalizer or whatever it was that I thought seemed like it was meant to mess with the sound (I like my devices to produce a relatively neutral sound.) Despite some complaints out there, I actually like the sound out from my US model SGS3 better than things like my Cowon D2 (which, btw, has a Wolfson DAC) and don't even use my CMoy (which has an AD8620 OPAMP that makes it sound far better than a typical OPA2132 CMoy IMO at only the cost of a bit of battery life) which I love the sound of because to me it sounds amazing on its own.
I only mention all of this because while I'm not a true audiophile per se, quality is of extreme importance to me all the same and I'm reading of issues with sound in the current custom ROMs which is not something I'm ok with. I want it to continue to sound this amazing. The idea of losing sound quality with a custom ROM bothers me. I like the idea of a few of the updates like Project Butter (though it's worth noting that mine does run fairly smoothly since I keep the number of programs running all the time as minimal as I can) and I really like the idea of having a custom ROM where I could maybe tweak more things (perhaps including better battery life options like maybe a better CPU governor built in? It drives me crazy how much my phone can run down over just a few hours while the screen is off even with SetCPU set to set the CPU to 384MHz and switch to the powersave governer with WiFi and mobile data both disabled and me not receiving any calls or texts.) For that matter, even while on it's not helping as much as it seems like it should, but I can't help but to notice that there are some more advanced CPU governors that I don't seem to have as an option and I wonder if perhaps a custom ROM could even help there as well. Plus I just plain like being able to tweak more things to my exact preferences instead and again a custom ROM helps. But, if I have to give up that sound quality that's a big problem. I think also it might be a problem to lose the camera. I don't use it a lot, but every now and then I really do kind of want to have it. Especially it would absolutely suck to lose the ability to scan QR codes or to have to do so via the front camera, but every now and then I do take some actual photos to share.
So my question is, have any of the custom ROM options out there reached that level of stability and quality to actually be worth updating and without losing those two things? The SGS3 has been out a fair while now, so it's hard for me to believe that there hasn't been a bit more progress along these lines, but I realize that it's no simple process to create a custom ROM all the same. (In fact, I only think more progress would have been made than what I've read thus far because the SGS3 is just so very popular. If it had been a less popular phone I wouldn't necessarily expect that much, but between its features, hardware, and etc, it's a pretty popular phone.) I want all the benefits of a custom ROM, but what I've read so far of them says to me that it's just not worth the trouble. Once I find one that really works I kind of want to stick to it as much as I can as I have a lot of apps installed and configured just so for my preferences. It sounds like I'm going to have to wait a good while yet though. Or have any of the custom ROMs finally "gotten there yet"?

ive been using CM10 roms for daily use and tehy do everything i need them to do without any limitations.
i suggest you make a nandroid of all your current setup and play with some custom roms. you can always revert back if you dont liek it or cant configure them match your usage. it made my S3 experience much better, btu everyone is dfferent.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
there are also sound mods and stuff that are accessible with ROMs. ive never tried them but some people swear by them

You don't have any sound issues of any kind? Does the rear camera work perfectly?
BTW, I don't want any sound mod that actually changes the sound. I want it to basically leave the sound alone and produce it as well as it can without modification. None of that Beats or whatever like some do (I think that was what HTC was pushing?)

beats is a sound thing, yeah. it hink its just an equalizer though. i have used audio through headphone jack and over bluetooth to my headphones and the quality is fine for me. im not an audiophile though. it all kinda sounds the same to me lol
the only sound issues i have with my ROM are after flash some sounds do not function until you slide the volume slider from 100 to 0 then to 100 again. Its these types of quirks that come with custom rom sometimes.
my camera is working perfectly. its not as good as the touchwiz one however.
edit: heres a sound mod that might/might not interest you
http://forum.xda-developers.com/showthread.php?t=1883262
long as you do a nandroid you can always revvert back to your preferred current setup. you should also backup your IMEI

There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.

I actually prefer to avoid all sound modifications whatsoever. Even equalizer. I like the results of a relatively neutral sound being fed to these headphones, it comes out just perfect for me. That's part of what I was worried about as some of the custom ROMs sometimes try to have stuff like that built in (and I guess that equalizer or whatever it was was Samsung or Verizon kind of doing that in the stock ROM even.)
About the camera, I actually have a commercial camera app anyway. If the only problem people have been having was the built-in app, that's a non-issue.
What's this about sounds not working until you go to zero and back though? Does this interfere with anything such as receiving phone calls (eg does it sometimes not ring because the sound isn't playing?)
BTW, where do I actually find the "official" CM10 for this phone?

no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
http://get.cm/?device=d2vzw&type=snapshot
i think that these M builds are the monthyl most stable ones.

Personally I'm waiting for something built on the official VZW JB release. And yes I know I have months to wait... :-\
Sent from my SCH-I535 using xda app-developers app

There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus. Qualcom is making the best arm chips right now. Can't wait to see how insane the 4 core S4 is!
I COMPLETELY AGREE WITH MY FELLOW MEMBERS WHEN IT COMES TO AVOIDING ALL THOSE STUPID AUDIO MODS LIKE BEATS AND SOME OTHERS OUT THERE. THEY SUCK AND DISTORT THE AUDIO!
Sent from my SCH-I535 using xda premium

ddurandSGS3 said:
no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
Click to expand...
Click to collapse
Ah, have I misunderstood? Do you just mean it only needs this to be done after the initial flash of the custom firmware itself? That's definitely no big deal at all...
prdog1 said:
There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.
Click to expand...
Click to collapse
Well, I want to try to do this just once or at least no more than minor updates after this hopefully, so if I'm going to go ahead I want to go ahead and go straight to Jelly Bean.
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
mike216 said:
There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus.
Click to expand...
Click to collapse
Interesting... I do definitely wonder why some people have complained about hearing noise and such then. Perhaps a bad setting and/or that MusicFX app (finally had time to dig through the list to find out what exactly it was called and that's the one that I just assumed was probably an equalizer/effects processing thing that would modify the sound, but honestly I never had any use for it even if it's not and never bothered to try it.) I'm glad to hear that I'm not the only one who thinks that the US SGS3 actually sounds good. I was beginning to wonder if my ears were maybe just getting that bad somehow even though I'm still far pickier than everyone I personally know, lol.
Let me ask you this, is the so called "Voodoo Mod" any good at least? I was never clear on exactly what it was supposed to do for audio. I know things like Beats probably mostly rely on a bit of processing to increase bass and probably play with things like stereo separation or something, but I've never been clear on what that one was trying to do exactly other than that people claim it's actually an improvement for many devices.
Anyway, back on the topic at hand, I think I'm more or less convinced to at least go ahead and give CM10 a shot. I'll use that newer monthly build from earlier this month after clearing enough space to make a full backup. (Besides CWM's backup option I've already backed up my apps and settings using TitaniumBackup, so in a worst case scenario it shouldn't be too painful if things go wrong and I have to go all the way back to a stock image with a factory reset or something. Is that option in CWM the correct thing, or must I use something separate for a Nandroid backup?) Also, it may sound silly, but how exactly do I backup my IMEI? I was looking for that already upon digging through a large tutorial thread a while back and it seemed to require something I couldn't get to work (when I try the numbers mentioned in the dialer I don't get any hidden menus, just a dialtone. Other than that I could only find something about manually restoring it if it has been completely damaged or lost which wasn't a fun looking process.)

Nazo said:
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
Click to expand...
Click to collapse
It is sold that way. Depends on the manufacturer of the device. On stock HTC kernel it will lock 2nd core at max speed, kill battery life and cause heating problems. That is why I said it may not work correctly and without another app to monitor CPU you don't know what it is doing. How it works with Samsung I wouldn't know as I run custom kernels when possible and don't worry about clocking on stock kernels as they are under performing already.

Don't restore system apps with titanium backup! Only data apps (apps from the market)
CM is great good choice. I love the theme engine CM10 has and all CM10 based roms.
I'll tell you a super easy way to backup your IMEI! Need Root!
Download (terminal emulator)
Enter these commands. su (hit enter)
reboot nvbackup (hit enter)
It will reboot and create the backup on a built in backup partition on your SD card. The only way you could delete the backup is if you formated your SD. Super easy I just hope it works lol....
Sent from my SCH-I535 using xda premium

Two quick questions before I take the final plunge.
1. Is the CWM backup to external flash function sufficient, or do I need something further for a true backup? (It says "Nandroid" in one part, but otherwise I'm not sure if it's truly "Nandroid." It seems like it just backs up each individual file or something and I get the impression that Nandroid is more of an image of the firmware? If it isn't sufficient, what should I use?
EDIT: Found this tutorial. Basically that's what I've done except instead of bothering with Odin I used the EZ-Recovery app to flash CWM directly from the phone itself (along with EZ-Unlock 1.2 from here to unlock the bootloader) as per another tutorial. The other tutorial just didn't call it a "Nandroid" backup, so I wasn't sure.
2. If anything goes wrong, is there a stock ROM image I can use for the Verizon SCH-I535 with Odin? So far my searching has taken me to a site that practically has every stock ROM for the SGS3 but that one... (Or at least if it has that one I couldn't find it on there, which isn't saying much since every single region was listed separately...)

The best way to get recovery is to get the latest recovery from the man who's created them all from the very beginning.
Get rom manager and flash the latest straight from that app. You must make sure your bootloader is unlocked. If you took the latest OTA from Verizon it locked your bootloader.
As long as your unlocked and rooted you can go straight in rom manager and flash touch recovery especially for your Verizon galaxy s3.
I've been using the latest touch recovery on my D2tmo, nexus 7,galaxy nexus and Asus infinity and it's worked perfect.
Make a backup of your current rom for safety before flashing. You can create a backup and rename it to whatever you want straight from rom manager!
I personally wouldn't back up to the external. It might work fine but when it comes to backups I just go straight to the internal
Sent from my SCH-I535 using xda premium
---------- Post added at 08:33 AM ---------- Previous post was at 08:26 AM ----------
I soft bricked my phone because after taking the latest OTA it locked my bootloader! Recovered it fully from here
http://forum.xda-developers.com/showthread.php?t=1840030
I seen the take to your local Verizon store bla bla bla.
Got in download mode at 4am and recovered in 15 minutes.
I wish I had someone that knew what I now know and that's why I'm here to help my fellow members!
Sent from my SCH-I535 using xda premium

Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.

Nazo said:
Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.
Click to expand...
Click to collapse
Strange that you are having so many issues. First off, when I flash a new ROM I put the ROM and the latest GApps on the sdcard. Do a factory reset, clear dalvik cache, install the ROM then the GApps. As far as wifi, I didn't have a problem when I ran CM10, but maybe there is something messed up in the latest version. Are you running the nightlies or the M versions?

The M version from the link above (the 2012 10-11 one.) At first I thought the issue I was having was the one from before where it would decide that my network with the hidden SSID was out of range automatically the moment it lost connection (either me leaving the area or turning off WiFi) but I not only tried to use the hidden SSID enabler, but also even went so far as to just re-enable the SSID broadcast on the router, so it's no longer hidden. It seems like it's having troubles initializing the WiFi. Maybe I somehow managed to freeze/remove an app that did something or other along these lines (though I just can't see how given that it can work, it just has issues.) I'm having to turn it off and on once or twice to get it to finally reconnect. I guess it's not bad since I have the power widget in the notifications tray that makes this a bit easier, but that doesn't make this any more fun at all to deal with. EDIT: In fact, whereas the hidden SSID issue I ran into previously had it just show up as being out of range after it lost the connection until I "forgot" the network setting and reconfigured it again, it looks like nothing shows up at all until I turn it off and on -- but I don't have to redo the network setting, so this is definitely a completely different issue. I think actually it's like it's just not correctly enabling the wifi on startup if it was left on when I rebooted so I have to turn it off and back on to get it to truly turn it on in the first place.
And yeah, I cleared the cache and did a factory reset before installing. Well, bear in mind that it naturally was showing up as a different device and all. So some initial configuration was definitely going to be required to even get started, and I was switching from ICS to JB (and completely different sorts of ROMs besides) so some initial fight was inevitable even if CM10 were the most established and stable build ever made just going from the one to the other. Actually, one interesting feature of Titanium Backup Pro (once I finally got it to recognize that I had the Pro version in the first place) is apparently the ability to change the device ID to seem to be the same as far as installed programs and such go, so now Google Play among other things thinks this is the same exact device as before now as opposed to being a new device. It's actually weird because the "new" one doesn't even show up on Google Play's settings anymore (and Google still hasn't gotten around to fixing it such that we can remove devices, so I still have my old Archos 43 PDA listed in there for instance.) Between everything, Google now is letting me once again access my software without re-buying or relying on backups (which is especially good because a few things seem to just get stuck when I try to restore them -- it just sits there forever, not ever really installing.)
BTW, I lost all the Verizon-specific special numbers such as *86 for voicemail. Apparently CM10 doesn't bother to list them (but then as they are vendor specific I guess that's not a big surprise.) Is there any sort of list of the numbers Verizon uses out there -- maybe even including whatever special numbers that might be more specific to this phone itself (such as that hidden menu or whatever)?
EDIT: Ok, so far things are starting to come together slowly but surely. One oddity though, I noticed at the end of my work shift that, rather than the usual 10% or so of battery time lost, it seemed to have lost about 20%. I wouldn't go so far as to say it's double -- it might be more like 15% many times -- but it is very odd all the same. I thought I was seeing a bad trend along these lines last night, so went ahead and put SetCPU back on there with the profile to do powersaving and serious underclocking when the screen is off and in both cases I used the "conservative" CPU governor for the normal use with the maximum CPU speed at about 1GHz (conservative is supposed to be like ondemand with a better tendency towards power saving at the expense of taking longer to scale the CPU upwards when needed.) As this is CM10, there should be no room for doubt that the CPU is being scaled down -- in fact in the performance menu I often see the CPU at a mere 384MHz (which is my minimum setting) -- so I'm just not sure what to think just yet. The settings menu for the battery life shows mostly just basic system processes like the screen, idle, and etc being the main culprits for battery usage, so again odd since the screen is the main thing yet is off during my working hours (with the very short exception of my breaks.) I don't think the automatic brightness setting is any higher or anything either and, in fact, configured it to use generally lower settings until the maximum brightness.
Guess more tweaking and testing is needed to be sure, but it's odd all the same. If anything CM10 is running LESS all the time by way of hidden services and such (though as far as things that actually show up in the likes of Android Assistant I'm having to fight far more things including an "analog clock" that isn't even in the app list so I'm hoping is just the normal clock despite the fact that "analog clock" in normal firmwares is actually a separate extra thing.) Guess I'll still have to wait and see to some extent.
Edit2: Haha, I just read that you have to recalibrate the battery meter after flashing, so it'd probably just not being very accurate is all. I grabbed an app to help do that so hopefully this is all that was going on (and if I go by Android Assistant's voltage status I'd say that it definitely is off.)
Edit3: (Just kind of adding as I go along here.) Now that all the basics are in place and I had some time and the desire to drain the battery more quickly (as part of the recalibrate process you're supposed to drain it until it automatically shuts down) so I plugged in my headphones and started listening. So far so good. I was really hoping that one of the advantages of a custom ROM would be a more precise volume control (Google really dropped the ball on that one! Sometimes you're trying to get it just right and end up stuck between either a bit painfully too loud or annoyingly too quiet with no in-between) but other than some dissapointed wishful thinking, it seems sound-wise this release of the SGS3 CM10 is just fine. I don't really hear any bloat or distortion in the bass and in general the usual modifications that they do to the sound just aren't there (or at least if they are they are subtle enough to fool my, let's say "bronze" ears since I'm definitely at the bottom of the audiophile chain, lol.) In one thread where someone asked how the Qualcom compared to the Wolfson sound-wise someone said it was a bit tinny, but if it is it's far too subtle for me to notice (and this is bearing mind that these are headphones with a slight bass roll-off, so it does seem like I'd notice any significant loss in the lower ranges pretty quickly. In this respect I'm happy or at least satisfied that nothing has gone wrong.
Also, one way or the other the wifi issue seems to have gone away. I'm guessing it was an app I had frozen that I reenabled, but that's just a guess. It's so hard to be 100% sure with these things unless you apply a long painful scientific process every single step of the way...
I'm STILL trying to figure out a way to configure the haptic feedback level. It seems to be all on or all off with no ability to reduce strength of feedback that I've found so far.

Another word to the wise, backup your imei. Not sure if that was mentioned yet
Also, your ROM will work better after a charging cycle or two. It will initially scam for media and such I believe which maybe part if the reason you're seeing slightly higher usage at first. Also, in general you'll get slightly less battery life on aosp. I don't find much use in most battery stats though. They're easily manipulated.
Sent from my Galaxy Nexus using xda app-developers app

Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.) Actually, I was beginning to become quite concerned because the battery was actually going down just doing a few basic things like restoring backups while plugged into the charger despite having the governor on conservative, the maximum CPU frequency at 1066MHz, and the I/O set to SIO (which at least one person claims is better, though I wasn't 100% convinced from what little I could tell -- if anyone has any suggestions for the best balance between battery life and performance in this respect I'm curious. I try to keep it on something that kind of scales so that games and such still work fine without me having to change it specifically for each or something while it could still at least not kill the battery when it's not being pushed as hard.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess. I went ahead and ran it ("reboot nvbackup" from the terminal anyway -- it sure would be nice if it actually properly shut down first instead of doing a cold reboot -- but other than some tiny blue text in the corner that might or might not have said something to the effect of that it was making a backup it just flashed by and booted up normally. I was expecting a recovery menu or something.) But I don't know if it's going to do any good to have run it now. Is there anything other than the IMEI itself contained in that data that I should be concerned about? I think the IMEI is correct still (I checked the numbers in the settings at least and they seem to correspond to what I wrote down from under the battery) but I'm not sure about anything beyond the numbers themselves.

Nazo said:
Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess.
Click to expand...
Click to collapse
No your OK you can get your IMEI underneath where your battery is. There's a tutorial on YouTube
Sent from my SCH-I535 using xda premium

Possible input lag/ Ghost Touches once again

A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?

Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.

I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.

hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again

What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.

Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.

My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.

ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.

Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.

It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.

patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.

hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!

goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x

I have the same frustrating issue

Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)

I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.

This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.

I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...

HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!

The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version

dead camera....twice

Dear all,
A few days ago, my N5's camera stopped working and none of the usual solutions (reboot, clean data and cache of camera app, even complete wipe and change of ROM) did anything to fix the problem. So I went on ebay, and bought a replacement back camera, fitted it and all was well...for a day!!! It looks like after just one day (and nearly no use at all) the new camera has already stopped working. Is anyone aware of what may be causing it, and of a way to fix it? or is it time for a new phone?
Thanks for your help!!

Is it possible the camera connction on the motherboard is a bit flaky?

audit13 said:
Is it possible the camera connction on the motherboard is a bit flaky?
Click to expand...
Click to collapse
Thanks for your reply. I thought that too after the second camera went wrong. I re-opened the phone and checked the connection, and from what I can see it seems quite solid. I am not sure what could possibly be going wrong that causing 2 camera modules to go bad in quick succession though. While the rest of the phone works perfectly.

Maybe it's just coincidence. I guess you could try a third camera to see what happens.

Can't connect to camera
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.

Maybe it because of your sd card

dixie600mhz said:
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Click to expand...
Click to collapse
Initially I thought this may be a normal issue of age of the phone, but the fact that a few of us are bumping into this so shortly after the marshmallow upgrade makes me think maybe the 2 things are related.
I suppose I could try and install a lollipop rom and buy yet another camera module.

The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.

wangdaning said:
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
Click to expand...
Click to collapse
Thanks for your reply. Done, but to no avail. Infact when you flash from fastboot the camera app is not even installed and the torch does not show up in the notification bar.
It is definitely a hardware issue, which is not resolved by simply replacing the camera module, as that seems to break again in a short amount of time. Not sure if I feel investing in a new mainboard and a new camera module.

Phone getting slow after some time

My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.

Try to reinstall the ROM. You can install full ROM without losing data. If that doesn't help, try a clean install.

Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.

Lownita said:
My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.
Click to expand...
Click to collapse
It sounds like a rogue app is taking control of your phone. I checked your Profile GPU rendering screenshot against mine, and indeed, mine never goes much higher above one-half length of the green line, which I think may be the 120fps limit (the green line itself is 16ms or 60fps.)
Seems to me that you need to uninstall some custom/rare apps to troubleshoot this issue.
It is definitely not normal behavior.

carlos67 said:
Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.
Click to expand...
Click to collapse
So my guess is that either people don't notice it, but I think that's quite impossible as even some kernel devs told me they wouldn't experience this. Or it's a fault in oos itself. Or we are using an app or some setting that's causing this. Or it's a kind of defect, which I think is unlikely but not impossible.
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Next idea would be flashing Omni ROM as I believe this is one of the most clean and fluid custom roms. If all of this fails, I would start to believe it's a hardware problem.

Lownita said:
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Click to expand...
Click to collapse
I would suggest you learn adb/ fastboot to do this so you learn to know what, how and why you doing this and that.
Not really difficult but extremly helpful if you face problems.

The large amount of applications and internet uses it may slow. Better cleared all caches and it's working properly.