Related
SOLVED! - at least for me.
I've had my X for about two years now and it started exhibiting the camera error symptom a couple of days ago.
I've done exhaustive research over several Forums, including this one and the "official" HTC Forums - all to no avail.
I've reset my phone to factory defaults a couple times, tried installing other camera apps, etc. Still, nothing "permanently" worked. The camera would boot up, and then crash immediately.
So, after ordering a new HTC One (M8), I spent some time with the X to try everything I could, no matter what it was.
This is what worked for me:
I sent all my pics to Google Drive, and made sure everything was synced
I removed my SIM card (no instructions I read in any Forum stated to do this)
I reset the phone to factory default
When it cycled through the erasure of data and rebooted, I skipped the Google sign-in procedure (including choosing a WiFi network) and got the phone settled to "Emergency Calls Only" (DO NOT CHOOSE THAT OPTION IN THE SIGN-UP PROCEDURE - ALWAYS CHOOSE "SKIP")
Then, I inserted my SIM card, and waited a few seconds to handshake with my carrier's network.
I didn't have to fool with disabling anything, and all features worked - even the camera and another downloaded app - Camera FV-5 (which is awesome, BTW).
Once I confirmed things were back to normal, I went to the PlayStore and downloaded all my apps.
Yep, still working!!!
I've been assembling and troubleshooting PC's for almost 20 years and this is one of the first times that I have come across a unique fix to a very common problem on any device I've seen.
Hope this works for you, too!
Don
Hello guys,
Was wondering if people running the new official CM builds could give the rest of the community some overall impressions about the ROM. Specifically, what's working and what isn't, the issues they've faced so far and suitability as a daily driver. In the dev thread the only thing specified as not working is making calls.
The Dev thread is obviously not appropriate for this discussion and I'm eager to migrate from stock to AOSP since the device has long been abandoned by Samsung.
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
gooberdude said:
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
Click to expand...
Click to collapse
I'm not sure you're responding to the correct thread.
Anyone? Is there a chance the voice calls will work in the future or is it a dead end? Also how well do the cameras work (front and rear)?
Random video issues exist. Colored diagonal lines when using Netflix, Google video, etc. Also glitches sometimes when using various OS functions.
There are two of us with N5110s that have no gps output. Since I use mine for marine charts and the other is used for aviation charts it is more than an inconvenience. Sad to say that the other person (very competent, and specifically something of an expert on GPS) tried to file a bug report about it and was refused!?! Very strange.
What makes this particularly annoying is that the CM12.1 nightlies, very stable for a very long time, were converted to CM13 nightlies without any warning. Imagine my surprise when my occasional update resulted in CM13 booting (with problems) and required a wiping of /data to make it stable. Either a huge warning or a separate line of nightlies would seem appropriate.
Edit: I am also experiencing the occasional video flashing, but it doesn't get in the way of usability.
I am a big fan of CM but it does look like CM13 is still having teething problems.
Greg
The screen flicker issue is still there. Until they do not solve that issue, I cannot comfortably use CM13 on my N5100. I have to stay with CM12.1, and periodically test the nightly releases of CM13, until that bug is completely solved.
Everything else, seems to work fine.
sorry an unrelated question.
is there any cm 12.1 that works fine on n5100 which has fix calling bug.thanks
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
CarinaPDX said:
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
Click to expand...
Click to collapse
Yes, you are right. The flicker issue is solved in nightly release from May 4, 2016.
I have installed it, and make a backup of both, CM 12.1 and CM 13, to be protected if,
for some reason, something wrong will happen.
A workaround to easily change the USB mode from default, that is charging, to MTP data transfer,
will be usefull when connecting the phone to PC. It is very annoying to go every time to
Settings => Developer Options => Select USB Configuration, and choose the desired mode,
or select mode from drop down menu when you are notified for new USB connection presence.
There are third party applications on Google Play, like "USB for Marshmallow",
but it will be better if a solution to problem will be implemented directly in CM13,
that will set default mode to MTP data transfer.
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
parsa.io said:
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
Click to expand...
Click to collapse
have you followed Rgib's instructions on the first post of cm13?
Volte
Add volte support for oneplus one for the next official update
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
andy o said:
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
Click to expand...
Click to collapse
I have 7.1.1 on my 5X. Can't get the initial setup/transfer to work whether I try to use the cable or cloud. "Google Play Services has stopped working" comes up just after I hit "copy" on the old phone, or when I select the 5X backup in the WiFi version, and basically brings me back to the beginning of the process. Not sure why it's happening, spent hours on the phone with Google support last night and didn't get anywhere, other than them offering me a replacement phone. That said, the support person couldn't even send me an RMA link that didn't give a "Internal Server Error" no matter what device or network I used... Anyway I doubt my particular issue is a 7.1.1 issue?
I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!
bife2003 said:
I apologize in advance for the long read.
I recently activated Verizon service on a Note 4 that has been sitting unused since the Note 8 came out. The Note 4 is in perfect physical condition, with no scratches on the screen or body, and has been in a protective case since new. I did replace the battery in it prior to activation, as I expect for the life to have been deteriorated.
I did a factory reset and inserted my Verizon SIM card, and it worked perfectly. I installed my everyday apps and a few games on the phone, and I used it without any issue for about a week. During that time, it did install a couple of OTA updates, but I expected that since it had been "off service" for a few years.
After that first week, I put the SIM card back in my NOTE 8 for a couple of days, after which I went back to the Note 4. Initially, 4G data and cell service worked, but within the same day I started having service drops. If I was on the phone and a call dropped, it would show an error message saying "No SIM / SIM Error".
Her is what I have attempted so far:
First, I replaced the SIM with a new one. There was difference in the frequency of the random service drop.
When that did nothing, I assumed that one of the OTA updates from the prior week had done something to modem / radio. The phone was on 6.0.1 at that time. I unlocked the bootloader and installed TWRP, and first tried downgrading to stock 5.1.1, then to a "modified 5.1.1, then to CM 13, and now Lineage 15 (frequently factory reset / cache wipe. There has not been an improvement (or reduction) to the random service drop.
Yesterday, I happened to be on My Verizon online, and I had a message showing that Verizon no long had the information on my phone (IMEI), and requesting that I open a Chat Window to update my info. At this point, the Note 4 is still running the Lineage 15.1. The Verizon team member asked me for the IMEI, and when I looked under the settings, it said "None" under IMEI. In a quick search, I found a forum on Lineage 15.1 that said turning of the screen lock and rebooting the phone will reload the SIM and IMEI info. That worked, and I was able to view the IMEI and verify connection. I explained my issue with the Verizon support, and she said everything appeared to be good on her end. Over the course of 15 minutes, we tested my connection and it worked. About 30 minutes after that, it dropped service again.
Finally, here is where it is at now:
I start with no service. If I do nothing but restart the phone, it will show LTE service for 2 or 3 seconds, then nothing. If I remove and reinstall the SIM, I will get the same 2 or 3 seconds, then nothing. If I turn Airplane Mode on and off, that does not reconnect the service. If I change the lock screen security to "None" and restart the phone, there is no service, but if I set Screen Lock to "Swipe" and restart the phone, I will have LTE service for at least 30 - 45 minutes before it drops, sometimes a few hours. When it does drop, it does not come back on it's own. The only way I have found to get it back it to "Screen Lock - None, reboot, Screen Lock - swipe, reboot".
Will replacing the modem fix the problem? Is there a specific modem that I need to match up to the ROM? Thanks!
Click to expand...
Click to collapse
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.
kevintm78 said:
I think you might be dealing with 2 separate issues. I'm kind of guessing about the first issue but the second is a common problem.
I think the original problem is that your sim card is not making a good contact in the sim slot. You could try putting a think piece of cardboard or something that will press the sim card to the sim slot contacts (maybe check to make sure that there isn't any dirt on the contacts but from the sound of it I'm guessing your phone is pretty clean).
The second problem is that all of the aosp roms have varying degrees of signal loss that occurs. Some people have a lot and some not as much, but everyone is affected in some way with what people have been referring to as "sim death".
My suggestion would be to run a stock or modified stock rom until you get your sim problem straightened out and then if you still want to switch to an aosp rom then at least you'll know that any further problems are just the normal sim death that occurs from time to time with those types of roms.
If you've already updated your bootloader to a 6.0.1 version you can flash the modified stock rom that I put together. I haven't had any signal/sim issues at all with that and no reports of it. Like I mentioned before though, the only caveat is that it needs to be on a bootloader that is at least CPD1 or newer. If it's not then your wifi won't work.
Rom link If you're interested.
Click to expand...
Click to collapse
Thank you for the reply. I think that you may be onto something with both issues. After posting this question today, I did examine the SIM slot, and although all of the pins looked good, and no dust or debris was visible, the metal guide over the SIM did feel slightly loose from the card. I did put in a thin shim, and the significantly improved the time that the phone stays connected. If that was a true issue, along with the possibility of the ROM causing a separate cause, I am absolutely interested on going back to a stock (or modified stock) ROM. The only reason that I did what I did was an attempt to fix the connectivity issue.
Thanks for your help. I will give your ROM a try and let you know how it works.
A few days ago Xfinity Mobile (or Samsung? I'm unsure) started pushing OTA update G965USQU7DTA5 (One UI 2 upgrade with Android 10).
I successfully updated mine SGS-9 but got stuck on wife's SGS-9 Probably, first attempt of download on this phone was interrupted (my wife went to store, and download was paused 'cause of no WiFi). But after that it's always stopped on 25% and saying "Couldn't download update: Unable to update the software. A network or server error occurred. Try later again". It's a bug in buggy Samsung software updater, I'm 100% positive, but how to fix that stuff without resetting the phone?
Phone is NOT rooted or unlocked; I googled for "offline update" instructions for stock, locked phones but can't find good, clear instructions.
Any suggestions, guys?
P.S. I've never done phone reset on SGS-9, how it works? Is it quick and safe enough? My wife's phone don't have sideloaded and/or pirated apps, everything by original, Google- & Samsung way.
Update: I resolved my issue by updating phone from PC, using Samsung's "Smart Switch" application - everything went smooth and easy.
P.S. Big thanks to this guide: https://thedroidguy.com/how-to-fix-...not-update-to-latest-software-version-1097987
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
sensboston said:
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
Click to expand...
Click to collapse
I think it's more no one has xfinity. I was one of the few and first to have xfinity when I got my s8. xfinity is a weird setup compared to most phones. I had to ditch em when they charged me like 3 or 4 times in one month, it took me almost 4 months to get a refund.
With root you might be able to get the old camera working possibly. Or gcam I'm no developer so I wouldnt know the exacts. And I still run my xfinity s8 ???