User feedback on Official Cyanogenmod 13 for N5100 - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

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

Related

[Q] SideSync with Galaxy S Tab + S5 -- can't operate touchscreen

I am using:
Galaxy Tab S 10.1 (SM-T800)
TMobile S5: Stock rooted late May build, Xposed is installed, Knox apps are disabled (about all the possible relevant things I can think of)
So I fire up Sidesync 3.0 on both devices to try out this much touted feature. I get connected just fine, but I cannot operate the phone's touchscreen at all from the tablet. There's just no response. However, the menu/home/back virtual buttons do work.
A search has turned up empty, which included trying one of the level one script readers from Samsung support. They literally had no information about tablet to s5 connections.
Disabled my exchange administrator thinking it's some security lockdown on my phone, but nope... removed my account, rebooted, didn't fix it. I'm out of ideas.
I figure this is the place to ask. I'm figuring I'm right.
Phreaker47 said:
I am using:
Galaxy Tab S 10.1 (SM-T800)
TMobile S5: Stock rooted late May build, Xposed is installed, Knox apps are disabled (about all the possible relevant things I can think of)
So I fire up Sidesync 3.0 on both devices to try out this much touted feature. I get connected just fine, but I cannot operate the phone's touchscreen at all from the tablet. There's just no response. However, the menu/home/back virtual buttons do work.
A search has turned up empty, which included trying one of the level one script readers from Samsung support. They literally had no information about tablet to s5 connections.
Disabled my exchange administrator thinking it's some security lockdown on my phone, but nope... removed my account, rebooted, didn't fix it. I'm out of ideas.
I figure this is the place to ask. I'm figuring I'm right.
Click to expand...
Click to collapse
All I can offer is to say that I had no trouble with my Verizon GS5 and my Tab S 10.5 (not 10.1). I controlled it a little yesterday evening. Even made a call through it from my tablet. I tend to keep my phone up on the bar and my tablet with me on the couch so I have sidesync on the phone all evening.
HughesNet said:
All I can offer is to say that I had no trouble with my Verizon GS5 and my Tab S 10.5 (not 10.1). I controlled it a little yesterday evening. Even made a call through it from my tablet. I tend to keep my phone up on the bar and my tablet with me on the couch so I have sidesync on the phone all evening.
Click to expand...
Click to collapse
After some searching around I have found I am not the only one. I was very hopeful a minute ago when I found I didn't have the latest version installed on the S5, but it didn't resolve the issue.
I got this resolved. The issue was with the S5, not the tablet. I needed to install the June S5 update. Ran into a snag where I couldn't install the OTA, so, it was time to bite the bullet and flash a recovery and ROM. Did TWRP + BeansTown's stock rooted (http://forum.xda-developers.com/showthread.php?t=2789850)
...and now it all works. A full restore from titanium and I'm right back in business, now with working SideSync!

Korean Galaxy Note 2/Note 2 LTE keeps restarting

Hello everybody,
got this mobile a few months ago, latest Android officially available release, only thing I did was rooting and adding some software, I use it as a second device mostly to check email and online services, I use my other smartphone as a phone and for calendars, phonebook and notes.
I noticed that the device all of a sudden restarts without me doing anything, my son (who uses Android since longer than me but who doesn't really know much about it...) said it could be the heat (it's always in the shade) or too many options on (wi-fi in primis) but I checked and there are just a few apps running (mail, phone, phonebook, sometimes Instagram), what can I check to find how does it restart without any notice or action from me?
Thank you
soory
I had an issue where my Note 2 would randomly reboot, I also had an issue where my power button was dodgy.
What it ended up being was the ribbon for the power button, got this replaced, and this fixed my dodgy power button issue, as well as the random reboots.
I paid to get this done in a shop, but it seems you can do this yourself.
Sorry i can't post links - hope this makes sense
youtube com/watch?v=T5zPvP4btDA
Of course, your problem might be different
Giuann said:
Hello everybody,
got this mobile a few months ago, latest Android officially available release, only thing I did was rooting and adding some software, I use it as a second device mostly to check email and online services, I use my other smartphone as a phone and for calendars, phonebook and notes.
I noticed that the device all of a sudden restarts without me doing anything, my son (who uses Android since longer than me but who doesn't really know much about it...) said it could be the heat (it's always in the shade) or too many options on (wi-fi in primis) but I checked and there are just a few apps running (mail, phone, phonebook, sometimes Instagram), what can I check to find how does it restart without any notice or action from me?
Thank you
Click to expand...
Click to collapse
Dear Giuann
What you are experiencing is know as SOD (silence of death) on our Android World
If your phone is rooted and you have custom Kernel then it would be due to the kernel... change your kernel to stock or a more stable one as per your device.
If you have a stock kernel... then clean your cache.. etc.. or better reflash stock ROM...
alternately use Betterbattary stats to identify if you have any rogue application which is causing issues...
I have experience this issue when I did rooting.. re root it with the correct method....
I did only root it as to install software I download from the internet, everything is as it originally was, ROM is the stock one.
Which are the steps to perform to clean the cache and to check if some app is making the OS crash?
Thank you

Android Auto work ok for you?

Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
omniphil said:
Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
Click to expand...
Click to collapse
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Andy4Shurr said:
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Click to expand...
Click to collapse
Is that the Xiaomi EU rom in the rom section?
And just to double check, Does android auto actually display on your car's screen ok? (I can launch Android auto on the phone fine)
omniphil said:
Is that the Xiaomi EU rom in the rom section?
Click to expand...
Click to collapse
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Andy4Shurr said:
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Click to expand...
Click to collapse
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
omniphil said:
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
Click to expand...
Click to collapse
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Andy4Shurr said:
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Click to expand...
Click to collapse
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
omniphil said:
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
Click to expand...
Click to collapse
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
MIUI PRO, No Dice
Andy4Shurr said:
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
Click to expand...
Click to collapse
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Damionix said:
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Click to expand...
Click to collapse
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Andy4Shurr said:
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Click to expand...
Click to collapse
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
omniphil said:
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
Click to expand...
Click to collapse
Glad you got it working mate, I couldn't live without Android Auto now I'm used to it!
Xiaomi.eu No Go
I tried the latest Xiaomi.eu ROM yesterday and got the dreaded Error -16 on it.
I just have no luck, and I need Android Auto work . Anyone have any suggestions?
I've got the same issue, really want AA to work again...
//Miui 10 CN stable
Ioniq electric
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Done
omniphil said:
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Click to expand...
Click to collapse
I have done joined your bug reporting. I hope more people voice their concerns on this topic.
Just to add some info to this... I am on MIUI 9 Global rom 9.6.8.0. I can get Android Auto to work by toggling the USB debugging in Developer settings. It doesn't seem to matter if its on or off, I just have to toggle it and android auto fires right up and connects to the car.
Very weird indeed, there is still some work needed to be done with these roms and Android Auto it seems.
Potential AA solution for Mi Max 3
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
jageanke said:
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
Click to expand...
Click to collapse
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
omniphil said:
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
Click to expand...
Click to collapse
Ah sorry to hear this.
Mine won't stay in USB debug mode anyway, but shame it hasn't sorted for you.
If it's an issue with other applications though, it would be good to figure out which one upsets it being detected right away.

'Call not sent' error on Android 10 beta

Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.

Xfinity Mobile SGS9 got stuck on Android 10 OTA :(

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 ???

Categories

Resources