I was just looking on the VZW support website and it appears there is a new OTA update coming today 3/24.
https://www.verizonwireless.com/support/lg-g3-update/
Anyone that is on stock 46A and takes the OTA, can you verify if this includes WiFi calling capability with Advanced Calling?
WTF! Wow. Thanks for the news. I expected a "minor" fix but that was even faster than I thought would happen. Awesome (hopefully)!
I am starting to lose hope that WiFi calling was added to this update. Of course I don't have confirmation yet but I looked at the last software update for the LG G4 and the Note 5 and they explicitly list WiFi calling as new feature of the update. No such details for VS98547A. I am in a bad cell area and work from home and my office is in my basement, so WiFi calling has been a much anticipated feature.
I installed iOS 9.3 on my wife's iPhone and she has WiFi calling now but has no idea why she needs it. Seems to work pretty well too...
I ordered a Moto X Pure and if WiFi calling is coming, I may stick with my G3. Come-on BIG RED!!!!
@jdgesmlls
I'm interested to find out if there's some minor fixes to the handling of USB OTG with this update, but it won't surprise me if there isn't. I'm hoping there's at least one "final" update to 6.0.1 along with finishing touches of fixing/adding these things if this one doesn't.
I'm receiving the OTA now but I'm not 100% stock, just going to retrieve the OTA files for the helluvit, then I'll restore to stock 35B and hopefully get both sets of OTAs.
78.7 MB
roirraW "edor" ehT said:
I'm receiving the OTA now but I'm not 100% stock, just going to retrieve the OTA files for the helluvit, then I'll restore to stock 35B and hopefully get both sets of OTAs.
78.7 MB
Click to expand...
Click to collapse
Given the size, I would guess it probably does just cover the security updates. Fooey! If you had asked me if there were going to be 2 updates for the vs985 on MM, I would have said no way... Here is to hoping the third is a reality and not too far off!
http://www.verizonwireless.com/support/lg-g3-update/
This update provides faster display response from a sleep state, and the latest Android security updates.
Downloading now. Hopefully this might also fix my Game of War issue where the keyboard hides the chat window rather than the chat window getting pushed up above the keyboard.
UPDATE: Regarding the chat window above, the issue is with a setting in the Battery section. In there, is a setting for Game Optimizer If this is turned on, it causes the chat window to be hidden in Game of War. When I turn it off, viola. No more hidden chat window.
Swiftkey helps with that in that I can undock the keyboard and move it up, but it's still hard to type and have my hands/wrists obscure the chat window.
Can only hope...
Still, VZW and LG are on the ball with this MM update. Can believe how quickly we got MM and how stable it was for me. Only reason I'll take this latest OTA is for the security patches. Root be damned. I like root, but I haven't a need for it on this phone.
iBolski said:
Downloading now. Hopefully this might also fix my Game of War issue where the keyboard hides the chat window rather than the chat window getting pushed up above the keyboard.
Swiftkey helps with that in that I can undock the keyboard and move it up, but it's still hard to type and have my hands/wrists obscure the chat window.
Can only hope...
Still, VZW and LG are on the ball with this MM update. Can believe how quickly we got MM and how stable it was for me. Only reason I'll take this latest OTA is for the security patches. Root be damned. I like root, but I haven't a need for it on this phone.
Click to expand...
Click to collapse
If you are on stock 46A, and you are taking the OTA... please confirm there is/is not an option for WiFi Calling under Advanced Calling. I am 99% sure there is not but would be nice to get the confirmation... Thanks!!!
jdgesmlls said:
If you are on stock 46A, and you are taking the OTA... please confirm there is/is not an option for WiFi Calling under Advanced Calling. I am 99% sure there is not but would be nice to get the confirmation... Thanks!!!
Click to expand...
Click to collapse
I don't have advanced calling activated on my phone. So I'm not sure if there would be more under that menu if I did.
Sorry I couldn't be of more help.
Also, my keyboard issue in GoW wasn't fixed. Not sure why it doesn't work on the G3, but it works on other MM devices I have. Weird.
jdgesmlls said:
If you are on stock 46A, and you are taking the OTA... please confirm there is/is not an option for WiFi Calling under Advanced Calling. I am 99% sure there is not but would be nice to get the confirmation... Thanks!!!
Click to expand...
Click to collapse
I'm 100% stock, and just upgraded to 47A. There is "HD voice" (I have Advanced Calling enabled), but no "WiFi Calling" option. Perhaps it's automatic (see below).
That having been said, my dad also has an LG G3 (on 6.0), and a couple weeks ago he asked why, when he received two calls in quick succession from me, does the "answer the phone" screen sometimes show a square rectangle to be pressed, and sometimes show a round button to be dragged to the center. I assumed that one call was over the 4G network, and one was WiFi. That's just a wild guess on my part. Other explanations welcome.
DeanGibson said:
I'100% stock, and just upgraded to 47A. There is "HD voice" (I have Advanced Calling enabled), but no "WiFi Calling" option. Perhaps it's automatic (see below).
That having been said, my dad also has an LG G3 (on 6.0), and a couple weeks ago he asked why, when he received two calls in quick succession from me, does the "answer the phone" screen sometimes show a square rectangle to be pressed, and sometimes show a round button to be dragged to the center. I assumed that one call was over the 4G network, and one was WiFi. That's just a wild guess on my part. Other explanations welcome.
Click to expand...
Click to collapse
Round answer is when the phone is locked/screen is off, square is when the phone is unlocked/in use. It has nothing to do with WiFi calling.
snolds said:
Round answer is when the phone is locked/screen is off, square is when the phone is unlocked/in use. It has nothing to do with WiFi calling.
Click to expand...
Click to collapse
Confirmed; thanks! Just another thing to confuse my father, who is 99 years old.
So not sure if this is the right thread to ask the question but is this update worth taking and do you lose root if you do?
blueis300 said:
So not sure if this is the right thread to ask the question but is this update worth taking and do you lose root if you do?
Click to expand...
Click to collapse
You can't take OTAs when you're rooted, since 23C. Whether it's worth taking is a subjective question, depends on each person.
roirraW "edor" ehT said:
You can't take OTAs when you're rooted, since 23C. Whether it's worth taking is a subjective question, depends on each person.
Click to expand...
Click to collapse
Thanks for just answering the question without making me feel like a fool. So we cant go back then take the update because thats where the bootstack,modem last boot loader that was able to be bumped plays a role.
blueis300 said:
Thanks for just answering the question without making me feel like a fool. So we cant go back then take the update because thats where the bootstack,modem last boot loader that was able to be bumped plays a role.
Click to expand...
Click to collapse
Sure, you're welcome.
You have multiple options:
1. If you have TWRP custom recovery, you can wait for a 47A-based ROM to be released and flash it.
2. You can restore to 100% stock unrooted using the 35B KDZ or the 10B TOT (along with the .DLL from the 35B KDZ) and take OTAs to get to 47A.
For what it's worth, it's the very smallest OTA update for the VS985 yet. Only 78 MB. The 35Bto46A OTA was around 780 MB.
Added information in my manual downgrade partions to install TWRP thread that that method works from 47A. You can additionally still use the TOT method to downgrade to 10B by using the .DLL from the 35B KDZ (you don't need to do the steps in that thread in order to use the TOT method).
Took 47A ota, rooted with Kingroot worked ok, replaced kingroot with Supersu and when I reboot it gets stuck at the Verizon screen, Not sure whats up just posting results.
So... I am on Azadi and this update auto downloaded on my phone. How do I get rid of it?
Related
Just came off of having to put up with using Razr M's for the last two years. I bought two used G3's this week and am now attempting to figure out which way to go.
These are our first LG products since flip days. The specs of the G3 really grabbed my attention when I read up on it.
I've spent the last (7) hours crawling around this forum and am now somewhat burned-out, overwhelmed, confused, ETC. (and the beer supply ran out...)
The two (new to me) phones are in great shape. One is @24B and the other is @10B
The 24B unit pulled down the 35B update today and is waiting/holding to update.
The 10B unit when I select 'Check for Updates' is pulling down a 110MB update, however when I select 'Install', it reboots, attempts upgrade and then returns a error #0x1111004. I got a feeling that the PO didn't execute something quite right when he wiped it before selling it.
Since these units are at a stage where I can wipe and flash at will, I'm trying to determine if I should go custom or just accept the 35B.
I'm leaning towards Jasmine 9 or Xdabbeb. Once I get these setup & configured I'll most likely stay with it. I'll tinker but that's about it.
I want stability and reliability and won't be flashing just to try out the latest. (i may have to get ahold of another for that )
One feature that caught my eye that I would truly, dearly like to have is 'Record Call'. (if possible)
So if I may ask for some opinions on which way to go I would appreciate it.
Thanks in Advance,
_Dan
middle_road said:
Since these units are at a stage where I can wipe and flash at will, I'm trying to determine if I should go custom or just accept the 35B.
I'm leaning towards Jasmine 9 or Xdabbeb. Once I get these setup & configured I'll most likely stay with it. I'll tinker but that's about it.
I want stability and reliability and won't be flashing just to try out the latest. (i may have to get ahold of another for that [emoji14])
One feature that caught my eye that I would truly, dearly like to have is 'Record Call'. (if possible)
Click to expand...
Click to collapse
Hi and welcome! First, any used phone who knows what state they left the phone in so I would use LG Flash Tool 2014 with the 10B KDZ in Windows PC after having installed the Verizon LG drivers, which are different than the drivers for the other G3s, and then rebooted the PC.
Look for the return to stock thread in the Verizon G3 General section. It might mention the TOT method too, I prefer the KDZ method because it's easier.
Then root with the Stump app, install TWRP v2.8.7.0 with the TWRP Manager app and flash the custom ROM you want.
I'm using @xdabbeb 's and my personal opinion is that it's awesome. Very, very debloated. Runs cooler, battery lasts even longer.
Be warned that on this phone sometimes when you reboot it will go to a black screen and not actually boot up.
Sometimes you can just hold the power button in for up a while (not sure on the count, maybe 30 seconds or so) and that will shut it off and it you held it long enough it will power back on, too.
Once you have your ROM set up, if you decide to try another stock ROM, use the built in LG Backup (in settings). It's faster, easier and more reliable than Titanium Backup in my opinion and in the opinion of some others on here, although there are some users who have had trouble with LG Backup working for them.
I use it with every new updated stock ROM.
One caveat of LG Backup is that when you make a backup, it stops a bunch of things like the clock app for the alarm and they stay stopped until you run them once again, just like right after you restore apps with either Titanium Backup or LG Backup.
@xdabbeb 's ROM includes call recording although any stock ROM (not sure about Cyanogenmod) can use Xposed and the G3TweakBox app to give that functionality too.
If you ever do go straight stock and get to the 35B update, once you take it the ONLY way so far of downgrading so you can reroot is the TOT method with a different, new .DLL than what is referenced in the TOT instructions.
You can get everything I referenced by using Google to search XDA such as:
Code:
XDA VS985 10B KDZ
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
roirraW "edor" ehT said:
Hi and welcome!
Click to expand...
Click to collapse
- Thanks!
roirraW "edor" ehT said:
First, any used phone who knows what state they left the phone in so I would use LG Flash Tool 2014 with the 10B KDZ in Windows PC after having installed the Verizon LG drivers, which are different than the drivers for the other G3s, and then rebooted the PC.
Click to expand...
Click to collapse
- Isn't that the truth?! The one that's on 10B is acting a bit funky.
I've got a laptop with a fresh install of Win7 sitting here just awaiting setup for the G3 specific drivers.
Did not want to mess around with one that has all sorts of drivers on it going back (4) years. From HTC to Samsung to HPTP items.
Also have a 'Nix with ADB installed, JIC I really mess up. Altough it seems like it's a quite a bit more straight forward than years past...
roirraW "edor" ehT said:
Look for the return to stock thread in the Verizon G3 General section. It might mention the TOT method too, I prefer the KDZ method because it's easier.
Then root with the Stump app, install TWRP v2.8.7.0 and flash the custom ROM you want.
I'm using @xdabbeb 's and my personal opinion is that it's awesome. Very, very debloated. Runs cooler, battery lasts even longer.
Click to expand...
Click to collapse
- More thanks. I had not seen any mention of 'Stump' and also was unsure which version of 'TWRP' to use.
roirraW "edor" ehT said:
Be warned that on this phone sometimes when you reboot it will go to a black screen and not actually boot up.
Sometimes you can just hold the power button in for up a while (not sure on the count, maybe 30 seconds or so) and that will shut it off and it you held it long enough it will power back on, too.
Click to expand...
Click to collapse
- And I hadn't seen any mention at all on this little 'feature'. That would have worried me big time if it happen(s)(ed).
Thanks again for the advice and recommendations, I owe you a brew.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm gonna go grab a fresh cup of coffee and get to it.
_Dan
middle_road said:
- Thanks!
- Isn't that the truth?! The one that's on 10B is acting a bit funky.
I've got a laptop with a fresh install of Win7 sitting here just awaiting setup for the G3 specific drivers.
Did not want to mess around with one that has all sorts of drivers on it going back (4) years. From HTC to Samsung to HPTP items.
Also have a 'Nix with ADB installed, JIC I really mess up. Altough it seems like it's a quite a bit more straight forward than years past...
- More thanks. I had not seen any mention of 'Stump' and also was unsure which version of 'TWRP' to use.
- And I hadn't seen any mention at all on this little 'feature'. That would have worried me big time if it happen(s)(ed).
Thanks again for the advice and recommendations, I owe you a brew.
I'm gonna go grab a fresh cup of coffee and get to it.
_Dan
Click to expand...
Click to collapse
You're welcome! Stump only works pre-12B (from what I remember) so that's why I recommended the 10B KDZ. Also will warn you that although LG Flash Tool 2014 might display misleading dialogs such as "server not found" etc, whatever you do, do NOT bother touching those dialogs, selecting any buttons in them. Just move them out of your way and ignore them. 99% of the time despite these seemingly catastrophic errors, on the G3 within 10 minutes the device will have been flashed, and it will be obvious when it has.
Also note that flashing KDZs/TOTs erases your internal storage so save anything you want to keep from there.
On older LG G3 stock ROMs, you can use TWRP Manager or Flashify to flash the latest TWRP. You can't do that successfully with newer stock G3 ROMs - another reason I recommend a pre-Lollipop KDZ.
Boy that was easy -- on the 2nd phone. Nice and lean, looks very fine at first glance.
(6) hours later... Typical windows drivers problems, even on a fresh/clean laptop install. Of course it's been that way with
windoz for the last 20+ years that I've been dealing with it.
I've got a few questions, ( I did do some searching, however I'm beat and tired.)
- I couldn't get ADB to work on either 'Nix or Windows.
- GApps? is there one? I can't 'push' from the Play store on the PC to the handset. Should I just add the apps?
- The Better Half wanted me to ask if GPS is fully functional. (She's a tad concerned I'm flashing them...)
- That's more but my brain has turned to mush...
Thanks for all the guidance Warrior! Tis Appreciated.
_Dan
middle_road said:
Boy that was easy -- on the 2nd phone. Nice and lean, looks very fine at first glance.
(6) hours later... Typical windows drivers problems, even on a fresh/clean laptop install. Of course it's been that way with
windoz for the last 20+ years that I've been dealing with it.
I've got a few questions, ( I did do some searching, however I'm beat and tired.)
- I couldn't get ADB to work on either 'Nix or Windows.
- GApps? is there one? I can't 'push' from the Play store on the PC to the handset. Should I just add the apps?
- The Better Half wanted me to ask if GPS is fully functional. (She's a tad concerned I'm flashing them...)
- That's more but my brain has turned to mush...
Thanks for all the guidance Warrior! Tis Appreciated.
_Dan
Click to expand...
Click to collapse
Do you have USB Debugging turned on, on the phone? Go to Settings/About device/Software and press the Build # string about 10 times reasonably quickly and that'll put the Developer options menu in the main Settings. From there turn on USB Debugging. The first time you try to access an Android device from a new operating system installation (possibly for different USB ports, too), a pop-up will appear on the screen asking for you to give either temporary or permanent authorization to the PC for adb access.
All stock OEM ROMs come with GApps, and you can't just flash a different/newer GApps over top of it, you just have to update the apps you want to from the Play Store. Personally, I remove all Google apps from the stock ROM's system except for the necessary Play Store, Play Services, and maybe also Google TTS. Since the apps are updated occasionally or frequently, depending on the app, I like to only keep one copy of them in user apps instead of having the system copy and then the updated version still reside in user apps.
You can tell the Play Store on the PC to install such-and-such app to such-and-such of your device in the drop down and it'll install, although I usually find that manually launching the Play Store app from the device gets it started installing faster after doing so.
GPS works great for me, and I use it often.
You're welcome!
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Another tip: Definitely make a backup of your IMEI on each phone, and keep a backup of your backup in a safe place! Sometimes flashing KDZs, TOTs and even ROMs has caused people with this phone to get their IMEI reset to all zeros. Hasn't happened to me in all my flashing over the past ten months, but it's happened to some others.
In TWRP there's an odd partition listed - I forget what it's called, just back up only that and keep a copy of that on your phone and on your wife's in a safe place like Google Drive, so you can restore them if you ever need to.
How to engage Debugging was one of the first things I searched on when the phones arrived -hehe.
Love how 'cryptic' it is now. Following your suggestions, I tried out 'Run as Administrator' and lo & behold
after a bunch of bleeps & booruuups, ADB showed a device attached. Gotta love Windoz...
'Nix laptop still isn't seeing though. Going to mess with that later.
Pushing from the Play store from a PC was only working on the Wife's early this morning before I packed it in.
Now trying mine it's working. That makes it easier to load apps.
IMEI Partition - is this the one you're talking about- The 'EFS' one? :-
Need to go and search on DPI settings now. The 'Home' row buttons are too small for my fat fingers.
You hit 50 and your fingers get mushy and touches aren't precise.
Also need to punch up the text a tad for the eyes. hehe.
Thanks, _Dan
middle_road said:
How to engage Debugging was one of the first things I searched on when the phones arrived -hehe.
Need to go and search on DPI settings now. The 'Home' row buttons are too small for my fat fingers.
You hit 50 and your fingers get mushy and touches aren't precise.
Also need to punch up the text a tad for the eyes. hehe.
Thanks, _Dan
Click to expand...
Click to collapse
Yes! EFS, exactly. texdroider is what I used to change DPI recently. 640 is stock.
You may or may not have not seen you can change the font size in the Display settings.
Almost "fity" myself.
Pretty snappy ROM thus far. I'm liking it and this G3. I actually like where the power and vol buttons are. Doesn't mess anything up when
pulling it out of your pocket.
Grabbed Texdroider but haven't played with it yet.
Got a feeling I'm going to have to mess around with framework a bit or find a mod. Need some things to be more visible w/o glasses.
Figured if I do I'll call it 'Old Goats GUI'. Fat thumbs and aged eyesight.
Google trashed my contacts. Tons of entries from where I used email to send txts. That's going to take a while to clean up.
It is nice though have a clean slate. It's just like wiping your computer and starting fresh.
(Of course there is always a great deal of pain that goes with that.)
A friend called today and she just got a G4 and is getting rid of her G2, and it's got the touchscreen problem.
Hopefully it's just a software fix and I'll have another phone to add to the stable.
They didn't transfer all her stuff so I'll be taking that on this weekend. gives me a chance to get my hands dirty with all three models.
Thanks again, _Dan
Have fun! You're welcome. Changing the DPI, and that font size setting should solve most of any issue you have. I use Nova Launcher Prime which is highly configurable - if you don't use a custom launcher you might want to look into it. You can make everything whatever size you want. Icons, text, how many icons fit on the screen in both portrait and landscape, etc.
Oh, oh. Having problems this afternoon. (should I maybe post this in the ROM forum?)
We're at home today and the phones are dropping off network. They're talking to us saying 'No Carrier'...
I just noticed (using Signal Check Pro) that there is no EV-DO. and watching the phone the last several minutes
it is not shifting into 3G. Usually with the RAZR M's previously, they would drop to 3G depending on where one
was at in the house or out in the yard. I don't see 3G at all on the G3.
Did I mess something up flashing? Figures doesn't it? - (2) days after flashing the devil out of them....
And of course I'm waiting on a very important phone call today...
Thanks,
_Dan
I doubt if you messed anything up in flashing otherwise the ROM wouldn't have worked. Maybe Verizon has an issue in your area.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Gave Tech Support a call last evening, and all they could (or would) say was that there were problems in TN.
Usually they are a bit more specific. Then again I only called them twice over the last few years.
And of course this had to happen two days after I switched our plan to pre-paid and went to two different phones and
flashed a non-OEM ROM and was waiting on a call.
It was only happening on my phone - the wife's didn't do it. I did notice that it finally showed 3G when I was on the backside
of the house, so I'm hoping it's just tower issues.
I'm going to go dink around with Nova Launcher and Texdroider now and wait for the cases to arrive in the mail today...
middle_road said:
Gave Tech Support a call last evening, and all they could (or would) say was that there were problems in TN.
Usually they are a bit more specific. Then again I only called them twice over the last few years.
And of course this had to happen two days after I switched our plan to pre-paid and went to two different phones and
flashed a non-OEM ROM and was waiting on a call.
It was only happening on my phone - the wife's didn't do it. I did notice that it finally showed 3G when I was on the backside
of the house, so I'm hoping it's just tower issues.
I'm going to go dink around with Nova Launcher and Texdroider now and wait for the cases to arrive in the mail today...
Click to expand...
Click to collapse
When my wife and I were on Sprint with two Galaxy S3's, I noticed we would both get different signal/data strength in different areas, including our home. I had gone to a Sprint store where they said that was expected, that two of the same phones in the same place might favor different towers, or something like that. They said were able to change some technical setting in the phone that would hopefully give me a better or at least different tower when I was at home. From what I recall it did definitely make a noticeable difference.
Only mention it as a demonstration that it can be normal to get different service on two of the same phone and ROM at the same location.
That was the first and only time I had pursued a fix of that kind so no idea what Verizon is willing to do or capable of doing. Normally I don't expect much from the carrier stores, technically speaking.
roirraW "edor" ehT said:
When my wife and I were on Sprint with two Galaxy S3's, I noticed we would both get different signal/data strength in different areas, including our home. I had gone to a Sprint store where they said that was expected, that two of the same phones in the same place might favor different towers, or something like that. They said were able to change some technical setting in the phone that would hopefully give me a better or at least different tower when I was at home. From what I recall it did definitely make a noticeable difference.
Only mention it as a demonstration that it can be normal to get different service on two of the same phone and ROM at the same location.
That was the first and only time I had pursued a fix of that kind so no idea what Verizon is willing to do or capable of doing. Normally I don't expect much from the carrier stores, technically speaking.
Click to expand...
Click to collapse
OUI! The S3 with the great antenna design....
A good tech is hard to find. Even more rare are the knowledgeable ones.
(10) years ago I had contacts with engineers at Sprint, US Cell & Verizon. Wish that I had maintained them or that two of them had stayed... hehe.
I've determined that the towers around us appear to be leased as far as I can tell.
USCC, Sprint & Verizon are hanging their birds off of them and I'm getting the impression that maintenance it minimal.
I left USCC two years ago because on the tower closest to us the bird was pointing downwards and the signal likewise.
Over two years now and it still hasn't been re-positioned.
I was at home all day and didn't hear the phone say 'No Carrier' so hopefully it was an infrastructure problem.
I was just nervous with the timing and all.
Better Half was out all day and no problems and actually came home with 90% on her battery.
I'm liking that!
middle_road said:
I was at home all day and didn't hear the phone say 'No Carrier' so hopefully it was an infrastructure problem.
I was just nervous with the timing and all.
Better Half was out all day and no problems and actually came home with 90% on her battery.
I'm liking that!
Click to expand...
Click to collapse
Hopefully you don't get a scare like that again soon. I plan on putting that ROM on my wife's phone sooner or later, too.
Rainy day here so I'm finally attempting to try Nova Launcher and Texdroider.
Backup first - as recommended. Battery was @80%, TWRP finished up and rebooted the system and when
it came back up battery was @60%. A backup operation lasting a few minutes wouldn't use up 20% - would it?
(oh and yeah, I did have on my glasses )
middle_road said:
Rainy day here so I'm finally attempting to try Nova Launcher and Texdroider.
Backup first - as recommended. Battery was %, TWRP finished up and rebooted the system and when
it came back up battery was @60%. A backup operation lasting a few minutes wouldn't use up 20% - would it?
(oh and yeah, I did have on my glasses )
Click to expand...
Click to collapse
I wouldn't expect it to and I don't recall recent backups biting that much out of the battery. Did you backup to internal storage or external? I'm about to do another backup before performing a modification so I'll see what happens for me today.
Texdroider was just what was needed for my ol' eyes. Much better. It came up showing 541 DPI, I took it to 480 first try
just for grins. Boy that messes up the icons. Set it to 640 after that and I can actually see items without glasses on.
Thanks for that suggestion!
Two odd things still going on with the handsets. Just sitting here with it on the desk she'll tell me 'Lost of Service'.
Check the phone and Signal Pro is saying it's fine.
On the Wife's - her's is going into Roaming mode around the house, same vicinity as mine.
So the other day I went to use Snapchat to take a photo of something and noticed it wouldn't switch to my rear camera. After some investigation I discovered that the rear camera wasn't working. I went further and tried using a flashlight app, a few different camera apps from the Play Store and some other ideas that I thought might work. None of them did. Not only that but the front "selfie" camera was now taking very elongated and flipped upside down pictures in the standard camera app. Snapchat they're just fine, reversed like in a mirror, but fine aside from that.
For the next step I did a complete wipe, data and cache as well as a factory reset. Again, this didn't resolve my issue. So I started looking into hardware fixes and decided I would order a new rear camera. They weren't expensive and I felt comfortable enough to install it.
While waiting for the camera to come in from Amazon I went about using my phone as normal, no big deal to not have a camera. One day I left my camera in the car on a fairly warm day and when I came back it said the phone had shut off due to overheating. No biggy, I restarted the phone and for whatever reason decided to check the camera for s&g's and voila! The rear camera was working just fine...until I replied to a message and went to use the camera again. Back to not working. Damn.
Replacement camera arrives and I install it, easy peasy. I restart my phone and....nothing. Still doesn't work. I thought maybe it could be a software thing so I was going to root it and try a Rom, but I have a revision (2) PCB, so I guess that's completely out of the question.
Does anyone have any ideas? Anything I could try? I love this phone and would hate to have to get a new one before the new Nexus arrives. Thanks for any help
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
roirraW "edor" ehT said:
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
Click to expand...
Click to collapse
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
premedicated said:
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
Click to expand...
Click to collapse
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
roirraW "edor" ehT said:
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
Click to expand...
Click to collapse
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
premedicated said:
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
Click to expand...
Click to collapse
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
roirraW "edor" ehT said:
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
Click to expand...
Click to collapse
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
premedicated said:
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
Click to expand...
Click to collapse
Good luck! Let us know how it goes.
Well, didn't work. I tried different camera apps and none of them will work on the rear camera.
At this point I'm not really sure what else to do since I've already replaced the camera. It might be the laser not working and causing the camera to in turn not work...or maybe the flash (?) but regardless, not sure what it is. I guess I'll just abandon it and wait for late October to pick up a new nexus and go back to paying Verizon more $$$... womp womp wooommmmppppp....
Thanks for all your help roirraW "edor" ehT
Sorry to hear that! You're welcome, hope we all find decent solutions when its time for us all to upgrade.
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
benthe1 said:
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
Click to expand...
Click to collapse
My camera is working again! I ended up not opening up my phone. Instead I flashed the camera mod that is supposed to allow 1080 recording at 60 fps. That ended up soft bricking my phone so I had to re-flash the stock ROM I originally flashed which ended up making the camera working again. I'm not sure if it was the camera mod that set something straight or just re-flashing the stock ROM that fixed it. Either way, I hope that helps someone.
My lg v10 was having same problem i installed evry camera app from playstore and wipe cache of gallery any camera app also .. But nothing helping .my problem is actually flashlight says camera app is running .. And camera app unfortunately stoping..... So here us what i have done to solve this
1.in power menu. Long press shutdown /poweroff to prompt safe mode menu .
2. It will ask .. Press ok
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Luigiman765 said:
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Click to expand...
Click to collapse
I use NetGuard to block adds. I purchased the IP filtering and it works awesome. Load in your favorite host table and let it go. It does keep an active VPN but haven't noticed any drain on it.
Here is the app thread http://forum.xda-developers.com/android/apps-games/app-netguard-root-firewall-t3233012/page332#post68312768 Developer is super awesome with replying to questions and helping.
Yup!
http://forum.xda-developers.com/showpost.php?p=68791345&postcount=9
on a good note (no pun intended) the device almost doesnt even need root. you have Good Lock to adjust Notifications and colors, and a Theme Store as well. As OP said, blocking ads is about all one really needs root for on this device. Sure with xposed you can have a circle battery icon, and a few other neat tricks. But these can all be lived without. I am currently staring at my 2 replacement Note7's I just picked up a few minutes ago. Ive got Software Updates disabled, but cant pull the trigger to start the root process, lol.
Luigiman765 said:
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Click to expand...
Click to collapse
I woke up this morning and saw my Note7 auto-updated overnight!
If I reset my phone to factory settings would I be set back to the original firmware, or will I still be on the "Green Battery" update?
TimeshiftR said:
I woke up this morning and saw my Note7 auto-updated overnight!
If I reset my phone to factory settings would I be set back to the original firmware, or will I still be on the "Green Battery" update?
Click to expand...
Click to collapse
Unfortunately, factor resestting won't affect the software, and you'll still be on the same update. I even tried flashing the original firmware files via Odin but that did not work either.
i concur, i bricked my Note 7 trying to root it after i got my replacement yesterday 9/21.
i got an internal usc email in regards to the phe update which states it will only let you postpone it 4 times before it will automatically install.
unfortunately the dbag in the store activated my phone on the wrong line and for some reason thought a firmware update would correct it smh so i didnteven have a chance to root since he already installed my screen protector as well.
elliwigy said:
i got an internal usc email in regards to the phe update which states it will only let you postpone it 4 times before it will automatically install.
unfortunately the dbag in the store activated my phone on the wrong line and for some reason thought a firmware update would correct it smh so i didnteven have a chance to root since he already installed my screen protector as well.
Click to expand...
Click to collapse
that blows! never trust them guys, i took my note7's in without the sim cards, said they were active in other phones right now. the rep looking to avoid work, gladly let me take my replacements home without even opening the boxes
cordell12 said:
that blows! never trust them guys, i took my note7's in without the sim cards, said they were active in other phones right now. the rep looking to avoid work, gladly let me take my replacements home without even opening the boxes
Click to expand...
Click to collapse
awsome! good thinking-
We can use 'Package Enabler' app available in Playstore and disable the Software updates (which is what i did).
Ready, set, ask me anything!
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
supermansbrother said:
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
Click to expand...
Click to collapse
1. Sadly I have no ETA, right now I have an init and a new sepolicy. I'm able to dirtycow the sepolicy but I can't find any way to get the init across without the phone rebooting before it finishes. I need a way to like freeze the init in a way to make it available for transfer. So there's that and the other guy we are working with is gone right now and idk yet when he'll be back and ready.
2. Well, he is helping me out but he had the same issue with the init sadly. So stuck again
3. I have a question for you.. what version of Android are you on currently?
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
All those settings to block calls from verizon are a verizon thing, once it's changed it's changed. Verizon's contract with us says they technically own the phone and we are just borrowing it. So my first guess would be no you can't get that software back. I could look, depends on what you were using. My suggestion though would check out an app on the play store to see what you get. Once we get root you can probably find a good software for it.
Do you expect roms to be available including nougat roms if/when root is achieved?
snapz54 said:
Do you expect roms to be available including nougat roms if/when root is achieved?
Click to expand...
Click to collapse
Maybe I'll start a project for one but it's a big maybe, I'm going to try to also push out the updates to be flashed over twrp.
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
Actually, I've been using contacts+ and dialer+ from the play store on my last several phones and I no longer have to back up my contacts , call log, or texts! And, it has call blocking that does have the block everything not in your contacts. It has made rooting and breaking phones hurt a little less and/or be less of a pain in the @$$. I swear I have nothing to do with them, lol. I'm just a guy who likes to fiddle with this stuff who stumbled on this app purely by trial and error. If I can make one complaint, it's different than other dialers/contacts, and I don't think it's the prettiest app, but once you fiddle with it a while, it gets better. I wish I could skin it though, lol. Sorry for rambling, I just stumbled here and had to comment.
Root for LG V10 VS990 with MM
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
cmccrar said:
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
Click to expand...
Click to collapse
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
See: https://www.engadget.com/2017/05/14/netflix-no-longer-available-for-rooted-android-phones/
Not worried a/b Netflix, thanks though
artcarney said:
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
Not worried a/b Netflix, thanks though!
Click to expand...
Click to collapse
need help here. just bought my V10 refurb unit. they said its H900 at&t unit. its on lollipop with root out of the box so i cannot use any banking app. so i try to diry flash latest H900 firmware via LGUP. phone bootup but i cannot use due to force closed app. so i clean reflash it. now it booting as normal. but i cannot setup any fingerprint as it will force closed. so i came out a solution trying to clear cache and data . phone bootup still same. then suddenly its blank. only black screen with backlit on. so pull out the battery, now phone cannot turn on. only qdloader9008. so its hardbrick. try dismantle mainboard and its turn out im getting verizon vs990 mainboard with at&t firmware in it. now had no idea how to fix it. try those SDCARD using h901 system dumb as i cannot find any vs990 system dumb to work with. no luck, cannot enter download [email protected] fastboot mode. any help will be appreciated.
p/s : now im still not sleeping since yesterday trying to figure it out and my head feel like to exploded.
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Nothing going on
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
No Luck
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
So my Lgv10. Doesn't show that its charging, doesn't turn on, doesn't do anything at all. It does however connect to the computer in the whole qualcomm hs-usb qdloader9008 mode thing. ive been doing the qfil thing because that seems to be the only thing that detects my phone but nothing is working. are there any other options? oh it says its the lgh900. but the motherboard is the vs990. does that make a difference? I have files for both
Been a while since I've touched a LG device but i'll respond to everyone tonight.
Shiah said:
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Click to expand...
Click to collapse
Uh, check in device manager, see if you are in a qualcomm mode
nabilsp said:
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
Click to expand...
Click to collapse
In device manager what is your phone coming up as?
thetestis said:
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Click to expand...
Click to collapse
I would update to the latest version. and I would factory data reset. I would also say that wifi calling is brutal and something that I wouldn't use all that much personally. any more questions you can ask
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.
Thoughts and input? Thanks in advance.
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
Sad to hear it broke.
I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
accessibility service not possible in non-store apps
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
WHAT... That's horrible... ACR won't work ) :
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
Just go to app info, click on 3 dot menu to bypass restriction.
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Jaitsu said:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Click to expand...
Click to collapse
So, even unrooted and stock I have to fuss with the side load update thing?
Frankenscript said:
So, even unrooted and stock I have to fuss with the side load update thing?
Click to expand...
Click to collapse
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.
Basically:
* Your phone has two "system" slots.
* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.
* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)
* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.
* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.
Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time ).
Lughnasadh said:
Just go to app info, click on 3 dot menu to bypass restriction.
Click to expand...
Click to collapse
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
miss said:
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
Click to expand...
Click to collapse
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.
Haven't noticed a downside yet in terms of how I use the phone.
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival