Related
I'm so mad right now.
My camera app crashed even after several reboots forcing a Hard reset.
I lost all my data and the camera app still crashes.
I can't describe how mad I am.
I press the camera button and it shows for a sec. It then immediately returns to the home screen.
I'm gonna contact Microsoft first thing in the morning.
I might lose a job because of this.
The hard reset didn't fix anything. It still crashes .
Can someone link me the he fastest way to get to Microsoft to help me fix this stuff.
I'm seriously going insane. All me stuff is gone and since its impossible to take a backup I'll never get it back.
Die, Microsoft. Die.
You just made me lose heaps of things because of a camera flaw.
Thanks for letting us know:
1. What you were doing when it crashed.
2. What type of phone you have.
3. Whether or not you're using a 3rd party MicroSD card in the slot.
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
5. Were you on WiFI, EDGE, 3G, GPRS?
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
7. Other trivial information that can cause us to come to better conclusions.
Instead, you plummel us with bad grammar, vulgarities, and a rant that will certainly accomplish nothing due to #s 1-5.
BTW, you should back up all important information on any device. Laptop, Tablet PC, Desktop PC, Smartphone, Thumb Drive, etc. It's not Microsoft's fault if you lose you fault due to data loss. Important information should be backed up and IIRC Windows Phone 7 is capable of keeping the Camera Roll Sync'd up with SkyDrive.
I give you 3/10, though.
Ciao!
You might try Windows Phone Support on twitter. They usually reply pretty fast during business hours.
http://twitter.com/#!/WinPhoneSupport
A side note, if you've got a job that depends on your ability to take pictures, you might not want to depend on a phone's camera and use a dedicated camera.
@Side Note: Still shouldn't matter. Anyone that takes (EDIT) photos for business use with their phone camera should have the SkyDrive Camera Roll Backup/Sync enabled and you can set your Photo Gallery to Private.
The OP's situation is completely avoidable.
badboy70 said:
I might lose a job because of this.
Click to expand...
Click to collapse
This is either a very bad troll or you're a complete moron. I can't decide.
Sent from my GT-I9000M
damn my camera app crashed too yesterday after i was changing some settings.
i turned off light and changed the measurement adjustment.
it crashed when i tried to focus the object. black screen, crash.
so happy a restart fixxed it, i better dont mess with the settings for some time...
Yeah, besides, Microsoft did not MAKE you do a hard reset of your device.
If you read the manual and understood what you were doing before you did it you would have known that a Hard Reset puts the phone back to its initial state.
You must have also disabled image syncing onto Zune which would have backed up your photos everytime you plugged it in or Wifi synched it. Could have also auto-uploaded the pics to Skydrive and had a lower resolution copy on there.
Can't blame Microsoft for this. Yes, the camera should not be broken, but most times a soft reset will fix any software issues.
Bah, sorry.
I was kinda drunk when I posted this.
I was at a party.
But to answer the questions:
1. What you were doing when it crashed.
Nothing. I tried to take a picture by holding the camera button whilit was still locked.
2. What type of phone you have.
HTC HD7
3. Whether or not you're using a 3rd party MicroSD card in the slot.
No, I did not modify my phone
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
It shows the zoom bar on the right, then immediately closes and shows the start screen.
5. Were you on WiFI, EDGE, 3G, GPRS?
Edge
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
Nope, there's nothing wrong with it other than that.
7. Other trivial information that can cause us to come to better conclusions.
Not really, I never did anything special to it.
All I did that evening was texting, calling and updating my status on Facebook because the power blacked out, three times.
Ok, so after the third hard reset the camera works again.
But now all the pictures I take are rotated 90 degrees
I think there's definately something wrong with the camera app.
badboy70 said:
Ok, so after the third hard reset the camera works again.
But now all the pictures I take are rotated 90 degrees
I think there's definately something wrong with the camera app.
Click to expand...
Click to collapse
Sounds more like a HW problem to me (wouldn't be the first for a HD7) as it doesn't happen to everyone else.
Yeah, sounds like a bad HD7 to me too. My first HD7 was an awesome phone, if by awesome, the standard you use is how often it simulated Windows XP by crashing on me.
Returned it and got a new one and it's been smooth sailing so far.
Send that POS back and replace, blame HTC not MS and don't do your business while drunk otherwise it won't be the phone's fault you lost your job.
i don't know which is worse, being unable to identify the cause or blaming something else other than the cause
badboy70 said:
I'm so mad right now.
My camera app crashed even after several reboots forcing a Hard reset.
I lost all my data and the camera app still crashes.
I can't describe how mad I am.
I press the camera button and it shows for a sec. It then immediately returns to the home screen.
I'm gonna contact Microsoft first thing in the morning.
I might lose a job because of this.
The hard reset didn't fix anything. It still crashes .
Can someone link me the he fastest way to get to Microsoft to help me fix this stuff.
I'm seriously going insane. All me stuff is gone and since its impossible to take a backup I'll never get it back.
Die, Microsoft. Die.
You just made me lose heaps of things because of a camera flaw.
Click to expand...
Click to collapse
Honestly, I'm actually surprised somebody hasn't posted Die, Badboy70. Die. because of this post, XDA is maturing. Anyway, your Zune auto syncs your photos by default, I'm assuming if you do this for a living, you'd know not to turn this off. So, I'm going to go out on a limb here and say that you're FOS for saying you're losing a job because of this. I'm betting more on you being a 14 year old who's phone is malfunctioning due to a hardware problem and had to come rant about it instead of asking for help.
Jonno2343 said:
Yeah, besides, Microsoft did not MAKE you do a hard reset of your device.
If you read the manual and understood what you were doing before you did it you would have known that a Hard Reset puts the phone back to its initial state.
You must have also disabled image syncing onto Zune which would have backed up your photos everytime you plugged it in or Wifi synched it. Could have also auto-uploaded the pics to Skydrive and had a lower resolution copy on there.
Can't blame Microsoft for this. Yes, the camera should not be broken, but most times a soft reset will fix any software issues.
Click to expand...
Click to collapse
Just wanted to echo this.
badboy70 said:
Bah, sorry.
I was kinda drunk when I posted this.
I was at a party.
But to answer the questions:
1. What you were doing when it crashed.
Nothing. I tried to take a picture by holding the camera button whilit was still locked.
2. What type of phone you have.
HTC HD7
3. Whether or not you're using a 3rd party MicroSD card in the slot.
No, I did not modify my phone
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
It shows the zoom bar on the right, then immediately closes and shows the start screen.
5. Were you on WiFI, EDGE, 3G, GPRS?
Edge
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
Nope, there's nothing wrong with it other than that.
7. Other trivial information that can cause us to come to better conclusions.
Not really, I never did anything special to it.
All I did that evening was texting, calling and updating my status on Facebook because the power blacked out, three times.
Click to expand...
Click to collapse
Your excuse of being drunk just validates the first part of my phone. You won't know your device is defective without a professional looking at the camera hardware. Just becase nothing else is messing up doesn't mean the camera isn't defective. Considering it worked, and then didn't, especially on factory settings leads me to believe this is hardware related, if it even exists at all. I would try to replace the device.
It's more likely to be a defective HD7 ...
Doesn't a hard reset delete all the data off your phone? So instead syncing it to your PC and extracting the photos you decided to delete. It may be MS fault that your Camera app crashed, but its your fault the data is missing. Why didn't you back your photos up on your computer or even to skydrive? Couldn't had been to important if your didn't.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
Hey all,
I'm becoming increasingly frustrated with my Note 7 (recall replacement one).
1. It lags like HELL! I've done all the animation scaling off/force GPU rendering etc, but I shouldn't have to. Just a simple thing like pulling down the notification bar noticeably lags every couple of times.
2. I use Android Auto, which I always have to reconnect manually to use (never did on the S7).
3. When listening to Spotify over Android Auto, I occasionally get stutter/glitches in the sound. Once the glitch was so bad the phone froze and it had to be reset.
4. The thing gets hot. Annoyingly hot, even if I'm just browsing Chrome, or reading G-mail etc. It's not like I'm gaming!!
5. WiFi is very sporadic. The connection is rock solid, but often it will be downloading an app...sit at 100% of download and progress no further. This happens quite frequently.
With all the above, (bar number 2), none of it applied to the pre-recalled Note 7.
I'm frustrated to say the least. Does anyone else get any of this whatsoever? I can't go through not having a phone again, or sending this for what Samsung will insist on a repair. This phone is jinxed and I'm gutted.
Any suggestions (bar a hard reset haha) will be greatly received.
PS. I have disabled loads of apps with the AppDisabler to try and help it along but I think there's an issue with the RAM or some of the internal modules (at a guess). Thanks all
I have just managed to reduce the lag quite a bit by uninstalling Samsung Good Lock (which was forced upon me earlier today)! I liked it, but serious lag creation!
Did you use Smart Switch to change phones? I've found quite a few apps don't like to be transferred. Android Auto apps don't move right via Smart Switch and I had to uninstall/reinstall them.
Be careful what you disable. Some of Samsung's seemingly benign system apps are called by other apps and if they don't respond are constantly polled. That could cause a lot of background processes and may be a source of your overheating. My pre-exchange phone did what you're describing the first couple of days after I set it up. It would maybe once or twice a day get blocky when scrolling as if something was running in the background. The (U.S.) PH1 update made it go away. But we're S-820 in the U.S. and I think you guys are Exynos. So different problems different solutions.
Thanks for your reply Barry. Actually not Smart Switch, but I let it restore my 100+ apps from my previous Note 7 (near the end of the initial set up). The apps were downloading but strangely, every so often nothing was happening after they'd reached 100% downloaded, just before "installing..." (over WiFi). I cancelled that specific app and the restore continued (this happened over and over). Turning WiFi on and off sorted it temporarily but I couldn't download more than 3/4 without this really strange issue.
I also observed the longest lag ever! I went into the OS update screen, pressed update and the device didn't respond. 5 mins later while doing something completely different, the update screen popped up about 12 times (as I'd pressed it 12 times 5 mins previously). This happened again after a reboot too!
Now, I've just bitten the bullet and performed a hard reset. This time the WiFi seems great, although now I'm speculating that it was getting stuck at 100% post download perhaps because the security thing was having trouble scanning it for malware prior to install.
I also take your note re:disabling stuff! I'm going to do something unheard of and just try it stock for a bit and see how it goes. For such amazing hardware, the fact my note 3 was running 10 times smoother means something drastic is going on. I hope this hard reset is the end of it!
Chances are the hard reset won't do anything, though I hope you have better luck than I did. I went through three phones (on my 4th). I did the hard reset as soon as I picked up the 2nd handset and onward before I did anything with the phone. Sadly you should not have to disable anything, the phone should just work for 900.00. Some will say otherwise.. Wi-FI is good for me but the reception is garbage. On various phones with T-MO including other android devices that colleagues have - they get 4/5 bars and usually double the download speed on Speedtest. The head I had on the first I don't get as bad on this one. But the lag I do...
Did you get the update from your provider as well?
I just picked up my replacement Sprint Note7 today so not much time with it though seems identical except 1 small issue. I had my first Note 7 rooted, Viper4Android and Dolby Atmos flashed along with Xposed and it worked flawlessly. The replacement Note fails with binary invalid using the exact same odin version, Sun7 systemless root etc that I have on my pc from the first Note 7 and the second Note 7 was given to me not updated, in other words its on the exact same firmware as the first one!
I am very proficient with rooting, adb, etc and this has me baffled.
Has anyone successfully rooted a replacement N930p that came with PH9? using freeza's guide?
jonboyuk said:
Thanks for your reply Barry. Actually not Smart Switch, but I let it restore my 100+ apps from my previous Note 7 (near the end of the initial set up). The apps were downloading but strangely, every so often nothing was happening after they'd reached 100% downloaded, just before "installing..." (over WiFi). I cancelled that specific app and the restore continued (this happened over and over). Turning WiFi on and off sorted it temporarily but I couldn't download more than 3/4 without this really strange issue.
I also observed the longest lag ever! I went into the OS update screen, pressed update and the device didn't respond. 5 mins later while doing something completely different, the update screen popped up about 12 times (as I'd pressed it 12 times 5 mins previously). This happened again after a reboot too!
Now, I've just bitten the bullet and performed a hard reset. This time the WiFi seems great, although now I'm speculating that it was getting stuck at 100% post download perhaps because the security thing was having trouble scanning it for malware prior to install.
I also take your note re:disabling stuff! I'm going to do something unheard of and just try it stock for a bit and see how it goes. For such amazing hardware, the fact my note 3 was running 10 times smoother means something drastic is going on. I hope this hard reset is the end of it!
Click to expand...
Click to collapse
Yea disabling seems like a great idea at first but it actually creates problems. I run it completely as is except uninstalling the preloaded games. Didnt disable anything. Disabling stuff caused massive lag on my note 5 and same with note 7.
Thanks chaps.
I've gotta say, the hard reset has made the world of difference. Which to me is strange, I've never had to hard reset a new device, but it's done the trick.
Regarding the disabling of services, there must be *some* that are safe to disable? I agree if you're tinkering with potentially integral things like S-Voice it's not a good idea. But then stuff like OneDrive surely that's okay? Maybe, things like the Disabler package are a bad plan. You can disable software by default without it, but only certain apps. Maybe that's why Samsung prevent the disabling of certain bloat...?
jonboyuk said:
Thanks chaps.
I've gotta say, the hard reset has made the world of difference. Which to me is strange, I've never had to hard reset a new device, but it's done the trick.
Regarding the disabling of services, there must be *some* that are safe to disable? I agree if you're tinkering with potentially integral things like S-Voice it's not a good idea. But then stuff like OneDrive surely that's okay? Maybe, things like the Disabler package are a bad plan. You can disable software by default without it, but only certain apps. Maybe that's why Samsung prevent the disabling of certain bloat...?
Click to expand...
Click to collapse
I only disable the useless apps, such as all the Microsoft bloat (OneDrive, Excel, Word, etc), Facebook (and all its services), and any Carrier bloat.
GibMcFragger said:
I only disable the useless apps, such as all the Microsoft bloat (OneDrive, Excel, Word, etc), Facebook (and all its services), and any Carrier bloat.
Click to expand...
Click to collapse
Disabling facebook services will broke gear VR.
It's a tricky one! I guess it's a bit of trial and error.
yussuf007 said:
Disabling facebook services will broke gear VR.
Click to expand...
Click to collapse
That's cool. I have no interest in Gear VR.
I have heard somethings about latest version of chrome causing batt drain, could possibly contribute to lag also, I cant tell much as I am expecting my note 7 exchange, but I have seen some posting about it
Have no problems when I used package disabler and chose "disable all bloat"...but after doing that, I looked through the list and enabled around 3 to 5 that I thought didn't need disabling.
No problems since.
Oh...that option doesn't disable facebook, messenger, hangouts etc. So if you don't use those, you need to add them.
Thanks all. Well, after all that, and a hard reset my phone is running perfectly again. Then, this morning I received this from Oculus...
"We recently pushed an Oculus Software update that has inadvertently caused some people to experience phone performance issues."
I haven't put my phone into my Gear VR since the hard reset and I can almost guarantee it was that blimmin thing. Samsung have also updated their Good Lock app to remove lag yesterday!
Damn you Oculus!
Oh..and strangely, the first few hours I got the phone..it got pretty hot...especially since I was using it while charging. I turned off fast charging and no difference. Anyways I just cooled it down w the aircon now and then.
Long story short, it doesn't get hot anymore.
Maybe it's because I used package disabler snd greenify...but whatever I do...Even while charging..it barely gets warm...
Shrugs
koppee1 said:
Oh..and strangely, the first few hours I got the phone..it got pretty hot...especially since I was using it while charging. I turned off fast charging and no difference. Anyways I just cooled it down w the aircon now and then.
Long story short, it doesn't get hot anymore.
Maybe it's because I used package disabler snd greenify...but whatever I do...Even while charging..it barely gets warm...
Shrugs
Click to expand...
Click to collapse
Yea they always get very hot for the first few hours while installing all the new apps! I'm not sure you need Greenify these days do you, since android tends to close apps that are not in use (giving you the same options as Greenify)?
Simples
Wipe data start again.
Set up as new phone and download apps again
Sent from my SM-N930F using XDA-Developers mobile app
ChimpNippl3s said:
Simples
Wipe data start again.
Set up as new phone and download apps again
Click to expand...
Click to collapse
^^^^^
This. I just spent two days doing that and its like a totally different phone. I started a thread highlighting my experiences.
i am quite annnoyed with the lag too. it's nothing too bad, but there's noticeable keyboard lag, and whenever you go into settings to search for something, it takes like two seconds to load. i don't even think this is a case by case situation here, this phone just isn't as fast as a oneplus 3, lg g5 or iphone 7 plus. again, it's not terrible, it's just not the fastest or smoothest.
So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.
SonarMonkey said:
So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.
Click to expand...
Click to collapse
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.
toknitup420 said:
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.
Click to expand...
Click to collapse
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.
SonarMonkey said:
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.
Click to expand...
Click to collapse
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.
toknitup420 said:
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.
Click to expand...
Click to collapse
Any particular mods? I've been flashing/modding/etc since my Droid Razr M but reading around on the Pixel XL forums is the first time I've felt out of my depth again - all this A/B partition stuff, changes to the way root and GApps work, etc. seems so different.
My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.