Netflix on stock 5.0.1 black screen.. - Nexus 6 Q&A, Help & Troubleshooting

Morning everyone,
So I hope I don't get flamed to bad but search turned up nothing on xda in conjunction with just a google search in general.
I am on stock 5.0.1 with elemental x kernel latest release and root. I can't watch netflix to save my life. I pull up a video and its just a black screen with no audio. I feel like i've always had this issue but I also haven't done a factory reset in "recent" times. (i've factory reset when 5.0.1 came out).
Bottom line:
If there's no threads complaining about this particular issue, can I assume that netflix works fine on this phone?
Thanks

Working fine here. I'm not on stock but that shouldn't be an issue. Using latest elementalX kernel

Try uninstalling netflix, reboot phone, and reinstall netflix. I had a similar issue and this fixed it for me.

Of course it works
PDP///M said:
Try uninstalling netflix, reboot phone, and reinstall netflix. I had a similar issue and this fixed it for me.
Click to expand...
Click to collapse
and of course after I post and get help it starts to work magically. Thank you for chiming in that way I know it if happens again its my stupid phone and I should reformat again or something.

Related

[Q] Audio only works after reboot

The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
Your search method must be flawed, as this is a known & frequently discussed issue.
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
It's defective. Get a new one.
Thanks for the reply.
Now to unroot...
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
When you get your hands on the new one, before you leave the store do this. After power on & such, try the audio (V0l + -). Works? Put to sleep for >10sec. Wake & test audio. No-work? Reboot, (Long power press) Try sleep/wake sequence again. If it works you are golden, now check a few other things & go home & root it! If it fails the test, don't let the Nook Genius tell you that you should let it charge for at least 4 hrs. before testing. The three that I have received had between 50% & 90% charge OOB. That's plenty for it to work properly, assuming the battery level meter is accurate. Put together your own checklist based on info on this forum. Crossword to test edges of screen, kbd. when charging from wall adapter etc.
Good luck, when you get a good one they are solid!
kev
trumpet444 said:
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Interesting! That would support the thinking that this issue is related to timing & initializing the audio codec or something related. Hardware specs may be skewed just enough for it to not work when waking up. That's actually encouraging! Means that all those with this problem may see a F/W fix if they don't want to re-clock it.
Cheers,
kev
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
timmyjoe42 said:
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
Click to expand...
Click to collapse
That's interesting. I had the audio/sleep problem with 1.0.0 & exchanged it for another 1.0.0 that worked fine. ?????

Droid4 Stock ICS Bugs

All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?

Random Reboots?

Not sure what is going on. I experienced it on stock rom, and I'm also experiencing it on Android Revolution HD Rom.
It seems like whenever the phone is tasked by an app opening or closing, I experience a random reboot.
Anyone know whats causing it?
Yeap me too, but only after closing final fantasy IV.. Dunno what's the deal here
°° no rest for the wiCKed °°
anyone?
S_Dot said:
anyone?
Click to expand...
Click to collapse
Me, too, but I didn't catch any regularity, yet.
I am on stock ROM.
One time a had a crash report from htc, but most times I only realize it, because I have to re-enter my pin.
Today I realised, that long-pressing the power-button does restart the phone without any other input.
Maybe it's that?
I'm using developer edition and have been suffered from heavily random reboot.
The phone rarely rebooted (2 or 3 times) while I was using it but just kept rebooting if I left it idle (5 reboots in 20 mins). I cannot reproduce the reboot because it was so random. One day, it just kept me annoying by rebooting itself more than a dozen time. The other day it just went super smooth and stable. This reboot has been happening on both completely stock and custom (Rom, kernel).
Anyone got a clue?
If you know a certain action is causing the reboot get a logcat, there's an app called catlog on the play store. Press record, repeat the action, after it reboots get the logcat and post it here
Sent from my Tricked out HTC One
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Sylpher said:
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Click to expand...
Click to collapse
I'm using Android Revolution ROM on 4.2.2., same thing. It happens once in a blue moon, and it's only on wake when I hit the power button. The whole phone freezes and reboots.
Is everyone here on the Developer's Edition?
I'm having the same issue, dev edition stock except recovery, and root. Some days it reboots, other days its fine. Not exactly sure whats up w/ that
Sent from my HTC One
I'm gonna go ahead and bump this, seeing as I'm facing the same issue on my 2 day old device.
At first I thought it was a problem with 4.1.2, but even after upgrading to 4.2.2 the issue is still there.
ViperOne 2.1.0 the same trouble
Hello,
I confirm the same problem on ViperOne ROM. I have tried out ElementalX 3.4 and Bulletproof kernels. But it seems to be kernel independent.
I attached the log, my configuration is as described in my signature except that I use Bulletproof kernel right now.
It is quite frustrating cause I just wanted to play a movie on my TV using Hama MHL cable, but everytime I connect my phone to the adapter the phone reboots, then it gets stuck on HTC logo, then I have to reboot it manually holding power button. I am also experiencing a reboot right after phone boots up.
This is such a serious issue that I am thinking of going back to stock kernel, but I am not sure if it will help
Any hints?
EDIT: I just installed stock kernel, but still the same, really does not seem to be a problem of the kernel
EDIT2: still trying to find the out whats the problem, I did a clean reinstallation of everything, even w/o using Titanium Backup, well, MHL still causes reboots

[Q] camera issues

I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.

Cannot turn on WiFi T713

Every few hours the WiFi in my T713 would hang up. If I turn off the WiFi then it refuses to turn on until I reboot the tablet. Super annoying.
Google around, this seems to be a problem that had affected samsung devices since at least 2014, but none of the fixes I saw applied to recent versions of Android or the S2. Mostly the solution called for installation of a specific version of a Kit Kat modem.
Any suggestions? I am rooted but other than AdAway I am bone stock.
On a related note, how do I start a new topic with the XDA app on th T713? The bottom menu is gone and try as I might I dont see a "New topic" option.
GroovyGeek said:
Every few hours the WiFi in my T713 would hang up. If I turn off the WiFi then it refuses to turn on until I reboot the tablet. Super annoying.
Google around, this seems to be a problem that had affected samsung devices since at least 2014, but none of the fixes I saw applied to recent versions of Android or the S2. Mostly the solution called for installation of a specific version of a Kit Kat modem.
Any suggestions? I am rooted but other than AdAway I am bone stock.
On a related note, how do I start a new topic with the XDA app on th T713? The bottom menu is gone and try as I might I dont see a "New topic" option.
Click to expand...
Click to collapse
try to flash latest official firmware for ur region then do a factory reset and check if the problem have been solved or not
There are a few threads about wifi problems. Try some of the suggestions there.
messi2050 said:
try to flash latest official firmware for ur region then do a factory reset and check if the problem have been solved or not
Click to expand...
Click to collapse
I am already at the latest T713XXU2APJ1_T713XAR2APJ1_XAR, currently re-downloading, will re-flash and try it again.
Factory resets are painful so will do it only if re-flashing does not solve the problem
madsquabbles said:
There are a few threads about wifi problems. Try some of the suggestions there.
Click to expand...
Click to collapse
I had done that and, as noted in the OP, everything is dated circa 2013-2014 when the problems seems to have first cropped up. The suggestions involve flashing a specific modem file, no way I am putting a 2014 modem on a 2016 firmware release. Will try YouTube.
GroovyGeek said:
I am already at the latest T713XXU2APJ1_T713XAR2APJ1_XAR, currently re-downloading, will re-flash and try it again.
Factory resets are painful so will do it only if re-flashing does not solve the problem
I had done that and, as noted in the OP, everything is dated circa 2013-2014 when the problems seems to have first cropped up. The suggestions involve flashing a specific modem file, no way I am putting a 2014 modem on a 2016 firmware release. Will try YouTube.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tab-s2/general/tab-s2-wifi-issue-thread-t3450874
None of this solutions helped me. The only thing that worked was going back to stock. Rooting seems to give my tablet problems with certain APs.
I decided to stay rooted and deal with the intermittent dropouts.
madsquabbles said:
https://forum.xda-developers.com/tab-s2/general/tab-s2-wifi-issue-thread-t3450874
None of this solutions helped me. The only thing that worked was going back to stock. Rooting seems to give my tablet problems with certain APs.
I decided to stay rooted and deal with the intermittent dropouts.
Click to expand...
Click to collapse
I *may* have fixed my Wifi issues. I remembered that a few days ago a dialog box came up offering to turn on power saving options via some built-in Samsung app. Sounded like what Greenify does so I said sure. I think my troubles started soon thereafter. This morning I disabled it and Wifi has worked without a hitch ever since
Settings -> Smart Manager --> Battery --> go down to "App power saving" section and click "Detail" --> turn off in the next screen
A day later wifi is still working. Anyone having WiFi issues should try turning off the Samsung per app power saving function
Okay I just turned it off, for I've been experiencing the exact WiFi issue lately.
I've the same model as you SM-713.
Fingers crossed.

Categories

Resources