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.
Related
Helllllo everyone!
So I apologize for being one of those people who just come here to ask questions. Unfortunately life doesn't have room for me spending time playing with my Android devices anymore, so having it 'work' is more important to me.
I am on 4.3, ParanoidAndroid 3.96. I am not on the latest because it took some time to have the app TouchControl work (with my Franco kernel), and Secure Settings etc. that I chose to just stick with it because it worked really well for me.
The problem!
I recently noticed that if I tried to switch to the front facing camera, it'd hang. After that, I would not be able to use my torch/led, and going into the camera would tell me that "The camera is not connected" or something like that. I could only fix this by clearing all the data on my Gallery, and shutting down, and then turning on again. Reboot would not work.
If I did that, I could go into my camera and use the rear camera fine. Take pictures, record video, etc. Torch works as normal. It's just that once I attempt to go into the front camera, this problem happens.
It's weird because I didn't flash anything or change any settings when this happened. I DID install https://play.google.com/store/apps/details?id=eu.mrogalski.saidit which wouldn't let me record a video while being used, but I since disabled/uninstalled it which solved that problem.
I have done a lot of googling on this problem, and noticed that I am not the only one who has this problem. For some people it seems like their phone is new, and some it just happens out of nowhere. For that reason I suspect it might be a hardware problem that can occur randomly, but it's weird that after triggering the problem, that my torch won't work anymore as well. Unless the torch is somehow tied to the camera/flash, and by triggering the problem when I try to access the front camera, it isn't able to 'call' the camera/flash anymore as a result?
I bought my Nexus 4 from Google in May 2013, so I believe I still have until May 2014 to RMA it, correct? Would I get another Nexus 4 at this point, or maybe I'd get a Nexus 5 instead?
Thanks in advance for any insight into my problem!
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply.
I tried installing the latest PA rom, but came up with an error. I had the rom I was on originally still, so I tried wiping and flashing it again. Finished flashing, went and opened the camera and it still happened. Looks like it's a hardware problem then!
I guess I'll go look up a guide to flashing back to stock now.
Good morning android experts
I have recently bought my s5 model Sm-G900F)
The phone has an issue which it randomly crashes and auto restart it was happening alot but after I searched many forums what i did to the phone was trying hard format,installing latest firmwares (i did that alot) i even installed CM11 for the phone and it still did keep crashing randomly and auto restart but after the firmwares it was fewer it crashes about 10 times a day now which is something really bothering me especially when you buy a last model phone and it is still new and does that you get frustrated i know have installed back the latest firmware of samsung back because CM didnt stop the issue plus that on CM there is no use of the finger print scanner and i tried uninstalling and disabling the bloatware apps
And an another issue is that there are many applications which when they start the instantly crash the phone like trix (card game by mayslawrd) and hitman go (the game)
Please i need some help because i am really frasturated and i am starting losing hope that it is a software issue on the bright side i am waiting for the lolipop update maybe the device will stop crashing
Please i need some help i am really getting hopeless.
Sent from my SM-G900F using XDA Free mobile app
Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...
Hi,
first of all, I love my Mi 9t. But I'm using android auto everyday and it is still full of bugs. First to paint a picture of my setup:
-Mi 9t Global 11.0.6.0
-Car: Skoda Fabia 2019, tried different USB Cables, everything works perfect with a Samsung Galaxy S9
List of Bugs:
1. Crashing of Media apps after disconnecting Android Auto
After disconnecting Android Auto the active media app crashes. I have to completly restart the app. Doesn't matter if using a podcast app like "antenna pod" or "podcast addicted" or "sportify". All of them are crashing.
2. Can not start media apps inside Android Auto
If the phone is connected to a car I'm not able to start any media app by using the cars display. There is just a message saying that the app isn't avaible at the moment. I have to pickup the phone and start the app directly on the phone.
3. Spontaneous crashes of Android Auto
Sometimes Android Auto just crashes out of nowhere. It automatically restarts after a few seconds, but after that I have to restart the media app by picking up the phone. (see bug number 2 and 1). It happens more frequently during calls.
4. Android Auto is lagy
It's not a bug, but in comparision to the Samsung Galaxy S9 Android Auto is a bit more lagy. It's not unusable but every command needs a few more moments then on the galaxy S9.
I tried different things to solve these problems. Using different usb cables, trying different media apps, changing the energy saving settings. Nothing helps so far.
These bugs are very annoying, therefore I thinking about using a custom rom or switchting to another brand. I got my Mi9t for a year now and these bugs are still not fixed. Some of them can lead to dangerous situations, because I have to pickup the phone during driving.
Does anybody having any ideas what else I can try. I don't want to do a factory reset now, because all the work I have to do setup the phone again. Does anybody else have similar problems?
Thank you all
Sorry, I am using Android Auto with Havoc 3.6 in an Audi Q3 and I don't have any of the issues. Works nice, no lag or crashes.
I even use AA Mirrow to get the TomTom app on my car's screen. Works most of the time as well.
I know this is not helpful, but just saying it's not the phone`s fault.
Thank you for your help. Now I have at least a recommendation for another rom I can try.
viper2035 said:
Thank you for your help. Now I have at least a recommendation for another rom I can try.
Click to expand...
Click to collapse
If you are going to try another ROM then you need to backup your data.
I would suggest you try the xiaomi.eu MIUI 12.1 weekly ROM. I have been using it for well over a month now and it is relatively stable, almost completely ad-free, and it also includes the latest security updates for Android 10.
update firmware of your car's multimedia. I use AA everyday with lineage, but I have had miltiple ROMs without an issue
Hi XDA,
I'm having an issue where every time i unlock my phone using a lock screen notification to go directly to the app, my phone crashes and goes back to the lock screen. Is anyone else having this issue? Is there a fix?
Thank you
Hello is you phone still standard or mod?
I was watching a review just this morning on youtube about the same problem on firmware latest Nothing firmware.
But it's seem to be hit and miss with user of this device..
Nyssa1104 said:
Hello is you phone still standard or mod?
I was watching a review just this morning on youtube about the same problem on firmware latest Nothing firmware.
But it's seem to be hit and miss with user of this device..
Click to expand...
Click to collapse
My phone is standard, no root or anything.
im on 1.1.2
Had the same issue since I got it. There is no fix until they fix it software side.
I have the same issue! Running latest 1.1.2 software, no root.
I'm from Germany by the way, were are you from guys? Would be interesting to see if devices from a certain area have the same issues.
This ****ty software feels so beta its unbelievable.
UK here, had the problem since launch day
Another EU version here with the same issue. Located in the Nordics
I'm also having this issue and the new update should resolve it!