So some of the filters work, while others make the camera pop up and say
"The camera has stopped unexpectedly" when choosing a filter.
I coulda swore when i got the phone brand new out of the box there was a samsung app where i downloaded the filters. now i cant find it? The phone is stock, i dont plan on rooting or what not until my warranty is up (can't afford to pay out of pocket if something breaks). I havent changed anything that i know of. in the settings....etc Phone is running:
Android 5.0 model: SM-G900V
Android security patch: 2015-11-01
Kernal Version: 3.4.0
Second question, when will i get the Verizon update for android 5.1?
MY Girl friends LG G2 got the 5.1 update?
I am happy the Volume settings are back to what they were before the last update i believe it was android 4.9 or something where you had to go through several menus to adjust other volume settings (what a real pain in the butt)
Bump....
Hey, does anyone have any help with this? Please.
Related
(Sorry the english. I used the google translator)
Hello everyone!
A few days ago I upgraded my XPeria X10a (branded) Android 2.1 to version 2.3.3. The new version of ROM is XPeria X10i (debranded). The ROM was obtained right here at XDA, but it is official.
Everything is working fine since then, but yesterday I decided to take a picture in low light conditions, and the LED lighting (which I call a camera flash) did not activate automatically. I'd Look for an option in the settings and saw that there is an option to "turn on the flashlight." By turning on the "flashlight", the LED was turned on and activated continuously.
I'm absolutely sure that when I first bought the phone (Android version 2.1, i guess, before upgrading to 2.3.3) and tested a photo, and remember that the LED was turned on automatically in low light condition, and this does not seem longer be happening.
I wonder if this is a bug or a feature is removed from the new version of Android, or if I did something wrong when I upgraded.
This sounds silly, but so far I'm loving the new Android and was wondering if I did something wrong.
I am willing to give more information if you need it.
Thank you!
Pretty sure we never had flash with any stock firmware. You had to use a third party app.
Yeah, always had to turn on the flash manually with stock camera.
Hi, I rooted my phone just to get ps3 controller capability using sixaxis, but I decided after rooting that all the lag, sluggish performance, horrible stability(at least for me, had a boot loop after I restarted the phone bc an app kept on crashing and had to restore phone to fix it ) and overheating wasn't worth it for one app, might as well just buy another bt controller for my gear vr. So I searched around looking for the right stock, but it was nowhere to be found. I understand that ATT is a little harder to find since they don't always release their stock firmware, but here are my model + baseband just in case someone has come across it...
SM-935A
Baseband: G935AUCS2APH1
If anyone knows where to find this ROM to unroot my phone any help is greatly appreciated.
Thanks!
Good morning XDA,
Situation: My Galaxy Note 4 (SM-N910A) died. Wouldn't turn on or anything, got a replacement N910A and it wouldn't register on the network or anything. NOW i have a SM-N910P board with a custom ROM running MM but unfortunately whenever i try to make a call it freezes the phone and restarts it. Can the original MM ROM be loaded to resolve this issue? How can this be resolved?
Current device:
Samsung Galaxy Note 4
Model: SM-N910P
Baseband version: N910PVPU4DPH4
Build Number: MMB29M.N910PVPU4DPH4
Could someone point me in the right direction to resolve this issue ASAP.
idon-kush said:
Good morning XDA,
Situation: My Galaxy Note 4 (SM-N910A) died. Wouldn't turn on or anything, got a replacement N910A and it wouldn't register on the network or anything. NOW i have a SM-N910P board with a custom ROM running MM but unfortunately whenever i try to make a call it freezes the phone and restarts it. Can the original MM ROM be loaded to resolve this issue? How can this be resolved?
Current device:
Samsung Galaxy Note 4
Model: SM-N910P
Baseband version: N910PVPU4DPH4
Build Number: MMB29M.N910PVPU4DPH4
Could someone point me in the right direction to resolve this issue ASAP.
Click to expand...
Click to collapse
So i came across something very interesting. I was doing a hard reset, got into recovery mode and saw this...
Android Recovery
MMB29M.N910PVPU4DPC1
why is recovery mode saying something dif from whats in the device config re Build/baseband ???!!!???
Still unable to make/receive call.
It could be your phone app. Try setting it as default calling app in settings. If you can't, try another phone app, like the Asus Zen phone app.
My Note 2, running MM had the same issue but I managed to solve that issue my playing around with some 3rd party phone app.
mha93 said:
It could be your phone app. Try setting it as default calling app in settings. If you can't, try another phone app, like the Asus Zen phone app.
My Note 2, running MM had the same issue but I managed to solve that issue my playing around with some 3rd party phone app.
Click to expand...
Click to collapse
Naw i tried many apps before and got ntn, and by ntn i mean the same rebooting issue, it's useless as is rn
Turn network to 2g only....I mean GSM only...
Have you tried setting the phone app as the default app? In settings - app - configure app - default app
I searched around and it seems to be a pretty common issue with cm13. I did both the setting the phone app as the default app and changing around the phone app and it seems to work so far for my phone
I know this is an old thread, but I was recently given a Note 4. I'd like to give it to my son to use, but it's having the same issue. It reboots when it receives or makes a call. It does have an aftermarket battery, do you think that would have anything to do with it?
Maybe it has issues with other apps
On my phone the same thing happens, I realized that being in ultra energy saving mode does not have that problem so I intuit some application installed on my phone is having conflict with the call application, disable a call recording application and I was able to make the call without restarting the phone, this may be the problem even though I have to comment that before I had no problems with the recordings of the calls.
It is November 1 security patch. It is a 157.75MB download. The update brings us to version N950USQS2BQK2.
Just got it about 20 minutes ago.
Here is the current update details:
Android 7.1.1 Nougat
The details
Release date: December 4, 2017
Android version: 7.1.1
Security patch level (SPL): November 1, 2017
Baseband version: N950USQS2BQK2
Kernel version: 4.4.21-12461033
Build number: NMF26X.N950USQS2BQK2
Build fingerprint: 7.1.1/NMF26X/N950USQS2BQK2
Previous versions required: N950USQU2BQJA
File size: 157MB
The updates
What's changing: Android device security updates, including BlueBorne fix (on SPLs September 1 or later)
Just got my alert for it too. But I have learned, the hard way, to wait for others to go first.
Just make sure you uninstall any Substratum themes before you take the update.
Also ALWAYS have a good reliable connection. Bad service is the number one way an OTA gets botched up. It fragments the download and can cause all sorts of wonky stuff.
Just did the download myself. Installed fine. No issues.
Camera has a new live focus helper... Seems a bit useless, but I guess if people were having big issues with it then it might be helpful.
Also just for anyone who is interested
ShrekOpher said:
Camera has a new live focus helper... Seems a bit useless, but I guess if people were having big issues with it then it might be helpful.
Click to expand...
Click to collapse
I updated about an hour ago without issue, but I had that camera feature before today. It appeared after I did a factory reset about two weeks ago.
Anyone know if this had the KRACK fix in it? Verizon's got this in their update along with the Nov Sec update and Live Focus update, just last week .
I've had a issue with the gallery since the update before this one. When scrolling through it randomly jumps back up or is almost unresponsive to my touches. The only way to scroll smoothly is by using the blue scroll button on the side. It's incredibly frustrating! I've done a factory reset and and it still occurs, even after this update.
It only occurs in the gallery app btw
nolimit06 said:
I've had a issue with the gallery since the update before this one. When scrolling through it randomly jumps back up or is almost unresponsive to my touches. The only way to scroll smoothly is by using the blue scroll button on the side. It's incredibly frustrating! I've done a factory reset and and it still occurs, even after this update.
It only occurs in the gallery app btw
Click to expand...
Click to collapse
In the settings menu of the Gallery app, are the first two settings turned on? I think this happened on mine a while back (although I'm not sure I'm remembering correctly) and I turned off the Samsung cloud sync and image analysis and it stopped. If this doesn't work, I must be thinking of something else. Sorry.
Edit: I have all the options in settings turned off and my gallery seems ti be working smoothly.
Faceunlock still broken for me with exchange EAS
No update for me yet. Anyone else still yet to receive?
Sent from my SM-N950U using Tapatalk
Hello,
I recently bought a Nokia 6 (2017) to my mother. However, phone is keep crashing and freezing while being not used. When this happens back and overview buttons are light up kept it like that. I can only start phone again by pushing power and volume + buttons simultaneously.
Phone is updated Oreo 8.1 with March security update and there are only whatsapp and instagram installed other than the regular apps.
I tried hard ressetting the phone vut it didn’t work either.
Does anyone have this problem? Or anyone knows how to fix it?
Thanks.
TA-1043 is Nokia 6.1 (2018) rather than Nokia 6(2017). Are you sure about phone model? Show screenshot from About with model & Android build
Sorry that’s my bad. It’s a 2017 model, I know the model for sure because it has a SD430.