Hello,
Try somebody to rollback on 7.1.1? I have request that few days ago but nothing happen.
i read that there is an option from the beta menu...don't know for sure i am still using 7.1.1 but can you/did you check in the system menu or developers etc?
i cant even get into the "boot menu" using volume up +power button. very odd
Starting from yesterday Rollback from Oreo beta to Nougat is working, i got OTA and i'm back to Nougat.
i had to rollback to android 7 via OTA because the camera only worked once and then never again (black screen).
even a factory reset on android 8 didn't help (camera was again able to take only one picture and then black screen again).
of course i immediately reported the problem via feedback function.
wondering why noone in here noticed and reported that so far...
for me, a phone is useless without camera working.
anyways.. now after rollback i am stuck with september 1st security update (rom version 3.08B).
before i entered the ad8 beta, i could receive october security patch on ad7 (rom version 3.09A).
anyone else also stuck and not receiving october-patch when back on android 7?
HD2Owner said:
i had to rollback to android 7 via OTA because the camera only worked once and then never again (black screen).
even a factory reset on android 8 didn't help (camera was again able to take only one picture and then black screen again).
of course i immediately reported the problem via feedback function.
wondering why noone in here noticed and reported that so far...
for me, a phone is useless without camera working.
anyways.. now after rollback i am stuck with september 1st security update (rom version 3.08B).
before i entered the ad8 beta, i could receive october security patch on ad7 (rom version 3.09A).
anyone else also stuck and not receiving october-patch when back on android 7?
Click to expand...
Click to collapse
You're the first person I've heard have issues on Oreo. No problems with camera for me.
mitchst2 said:
You're the first person I've heard have issues on Oreo. No problems with camera for me.
Click to expand...
Click to collapse
ok.. that's surprising since even a hard-reset did not solve-it for me.
i used the ported google camera-app with hdr+.
and after taking one initial picture, neither the nokia cam, nor the google cam was working anymore.
nokia cam reports that it can't connect to the camera hardware even after deleting google-camera app.
is noone using the google camera and experiencing the same problem?
After your post google camera uninstalled from my Nokia
HD2Owner said:
i had to rollback to android 7 via OTA because the camera only worked once and then never again (black screen).
even a factory reset on android 8 didn't help (camera was again able to take only one picture and then black screen again).
of course i immediately reported the problem via feedback function.
wondering why noone in here noticed and reported that so far...
Click to expand...
Click to collapse
because it might not have happened to anyone else. I don't have any issues so far on beta. NIL I have installed the google camera and that app works heaps better than the nokia stock.
edit. No errors of any sort, black screens or hang. Just buttery smooth. Just wondering if the model variant is the cause. I have the 1012
Does the rollback formats/resets the phone?
stuffynet said:
Does the rollback formats/resets the phone?
Click to expand...
Click to collapse
It does and iirc that warning was given.
I am sick of asking nokia and sarvikas on twitter and elsewhere maybe XDA can help in this matter. As there is no official PC suite of sorts for nokia android What is the best option available to create a local backup including( or mainly ) app data. I need something that can restore it after the roll back as it will be wiped out for some reason. MIUI didn't do that.
Related
Hi guys,
First of all, sorry for my really bad use of the English language;
Second: I recently switched from a Nexus 6P to an E6553 (because...reasons), and I'm really feeling home with my new smartphone.
The only thing is driving me crazy is...the camera focus.
What's the problem? Simple: it doesn't work, I'm sure it's a software problem and I'll let you know why I think this.
Just after the Setup Wizard, the camera works, and works really really well (it shots awesome pics!). Focuses even little objects such as insects, without the littlest issue. An example is the first attachment: I shot that pic just after a factory reset.
But the problem comes when I restore my apps, my photos and then reboot the phone. Then, the focus literally DIES. No way to get it working, it just stucks. End.
The only way to get it working is...formatting the phone another time and then never reboot it again!
I tried a factory reset from setting, a software repair via Xperia Companion, I even tried to refash the stock ROM through Flashtool (which...simply stucks at "Writing data", and the only thing I can do is repairing the software with XC).
Nothing to do: the camera works flawlessly after a reset/repair/flash, but after a reboot it becomes unusable.
And focus isn't the only problem (as it was a little one ????) : opening the Video Mode in camera makes the device freeze, meanwhile using third party apps for the camera makes me see an huge amount of glitches. The strange thing is that everything works without issues until a reboot, so it's certainly a software bug, but I don't know related to what. And no, it's not an app or something I installed: focus doesn't works even when booting in Safe Mode or creating a new user from settings.
And no again, bootloader is not unlocked, it isn't even unlockable, so no DRM Keys fault.
What you suggest me to do? I really love that phone, but using it with this camera is just impossible.
Uh, last details: I'm on the latest firmware, 32.1.A.1.185, Customised IT (Italy). I tried to flash another firmware (CE1) but as I said before, it stucks on "Writing data".
Thanks in advance.
Today I'm going to send it in warranty for replace the camera. It will be back in a couple days, I'll let you know if the bug is solved.
I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.
Oveana said:
I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.
Click to expand...
Click to collapse
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Thanks for your Solution. KEEP US UPDATED
ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Sorry, I did not understand what you did. Could you say that again with different words?
Oveana said:
Sorry, I did not understand what you did. Could you say that again with different words?
Click to expand...
Click to collapse
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.
ale29-09 said:
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.
Click to expand...
Click to collapse
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.
Oveana said:
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.
Click to expand...
Click to collapse
Why you unlocked bootloader Man?
arokososoo said:
Why you unlocked bootloader Man?
Click to expand...
Click to collapse
For rooting
Oveana said:
For rooting
Click to expand...
Click to collapse
If you again lock bootloader+ Ta restore, then camera problem gonna stay as it is now I.e no focus?
Hi, phone (EVA-L09) was previously Vodafone branded and freshly upgraded to nougat.
After that the touchscreen sometimes doesn't respond to user input.
It's like you scroll down and if you want to immediatly scroll up it's not responding.-
Wait 2 minutes and it works again.
It's not bound to a specific region on the screen.
I downgraded to Android 6 via the debranding method and the touchscreen worked again as expected.
I then upraded to Nougat (B183) via OTA update and the touchscreen showed the same weird behaviour.
Also did a factory reset incl. internal storage.
Still no chance.
Anybody an idea, why the touchscreen isn't working in Nougat but works flawlessly in MM?
kwasi76 said:
Hi, phone (EVA-L09) was previously Vodafone branded and freshly upgraded to nougat.
After that the touchscreen sometimes doesn't respond to user input.
It's like you scroll down and if you want to immediatly scroll up it's not responding.-
Wait 2 minutes and it works again.
It's not bound to a specific region on the screen.
I downgraded to Android 6 via the debranding method and the touchscreen worked again as expected.
I then upraded to Nougat (B183) via OTA update and the touchscreen showed the same weird behaviour.
Also did a factory reset incl. internal storage.
Still no chance.
Anybody an idea, why the touchscreen isn't working in Nougat but works flawlessly in MM?
Click to expand...
Click to collapse
Do a HARD RESET
Rafa Mistry said:
Do a HARD RESET
Click to expand...
Click to collapse
I already did that but still no luck
Same problem here. With c432b386 the touchscreen works bad. B182 works perfectly. I don't know how to repair this...
Anybody around here with a high Version. Is it probably fixed in later versions? - or anybody with the same problem?
PiX3LaDo said:
Same problem here. With c432b386 the touchscreen works bad. B182 works perfectly. I don't know how to repair this...
Click to expand...
Click to collapse
Just made an interesting discovery.
I you switch the phone to landscape the touchscreen is working fine.
So it's somehow related to the display mode.
Can you confirm this?
...and the next finding:
I enabled "Show visual touch feedback" which shows a marker wherever a touch is registered on screen.
All touches are registered correctly and shown by the marker there are just times where the OS doesn't react upon these touches.
It's like if the GUI thread gets stalled for some reason and then works again.
Definitly not a HW problem buzt also no idea how this can be fixed
-Go to settings>smart assistance and try disabling enabling gloves mode. (It changes the screen sensitivity)
-Do you have a tempered glass screen protector?
When yes try removing it.
- Try installing a Rom like BlueWei or Moonlight (With BlueWei v3.7 you get Nougat B390)
Same issue
I have the same exact issue i debranded ee uk p9 now im running nougat.
I have to slightly swipe and press the screen to use it properly did you find any fix for that?
Same problem for me. Any EMUI 4.x.x works fine, but any EMUI 5.x has scroll issue. Someone found fix for that?
Video
I guess I am not alone with this issue. I can run ANY version of Marshmallow just fine but as soon as I update it to Nougat (B361 or B389) my touchscreen will not allow me to scroll. I can tap an icon and launch any app but I cannot scroll anywhere on my screen. No fixes???
Same issue here. I had to switch to custom rom to solve this issue. Resurrection remix works good.
Do you have a refurbished or repaired P9?
Rucha said:
Do you have a refurbished or repaired P9?
Click to expand...
Click to collapse
Mine is refurbished.
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
BussanyiG said:
Same issue here. I had to switch to custom rom to solve this issue. Resurrection remix works good.
Click to expand...
Click to collapse
Thanks for the info. I may give this a try.
On mine I did myself the repair of the screen, because it was cracked. But this error with the touchscreen started to appear only when I updated the phone to the EMUI 5.
It looks like all we have not original screens that is not supported in EMUI 5 anymore. Probably they changed driver in new version.
It can be possible. Custom rom is better for me, I just miss the EMUI camera app.
BussanyiG said:
I just miss the EMUI camera app.
Click to expand...
Click to collapse
It's a big deal!
The quality of the picture from the RROS rom is good by I think the black& white camera is not working. Just the RGB one.
Taking touch/display driver from RROS and using it by overriding existing one in original ROM would be good solution.
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Stransky said:
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Am on 8.1 global variant. How are you still on Feb?
Scarkinyua said:
Am on 8.1 global variant. How are you still on Feb?
Click to expand...
Click to collapse
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
AchinPakhi said:
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Click to expand...
Click to collapse
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
They've also removed the functionality in which you can navigate using the fingerprint sensor ?
After the may 2018 update I noticed some 4G connectivity issues: no more internet. By moments, the phone would switch to 3G and then internet would work.
I thought I did something bad, so I reset APNs, etc. no luck. I even completely wiped the phone, but that did not change anything.
Then I saw this thread on Nokia forum:
https://community.phones.nokia.com/support/discussions/topics/7000025066
For now, by forcing 3G, I can get internet all the time, but I hope this fix will be temporary.
Scarkinyua said:
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
Click to expand...
Click to collapse
ah sorry for a super late reply.. if u have already set up trusted face then it's already been activated.. just lock the screen and turn on using the power button.. there will be a small face icon at the bottom middle of the screen .. when it recognized ur face it will show a unlocked lock(open lock) icon.. then just swipe up the screen...
TA-1062
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Stransky said:
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Much easier with the roll back firmware and sideload using ADB or straight from recovery.
Done the ADB and got 8.1 April version (no wipe and everything seem to work fine).
After that got OTA update to May security patch.
More here: https://forum.xda-developers.com/showpost.php?p=76546067&postcount=56
It may be working without enrollment to developer preview. Someone uploaded the zip.
Alfaroerik87 said:
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Click to expand...
Click to collapse
I'm also stuck on 8.0 1062.
Flameboy42 said:
I'm also stuck on 8.0 1062.
Click to expand...
Click to collapse
I'm on 8.1 :/
Alfaroerik87 said:
I'm on 8.1 :/
Click to expand...
Click to collapse
What's your location?
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
tkiafar said:
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
Click to expand...
Click to collapse
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
Flameboy42 said:
What's your location?
Click to expand...
Click to collapse
I'm from Chile
Alfaroerik87 said:
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
I'm from Chile
Click to expand...
Click to collapse
Main directory is the same directory you open first when you connect your device for file transfer, that contains "alarms , android, data" directories. I put the file there without renaming it, and dialed the code. There are posts on the same thread that cover file not found issue, check them out. In any case if it doesn't find the file the only option is ADB sideload.
Face unlock was added
Face unlock was added and security patch updated to may
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
Every since accepting and updating my Moto G6 (US Retail) to 9.0 (PPS29.118-11-1), it has been laggy. The lags seem to happen mostly when there is some type of I/O operation (like opening an app), or when a background app is doing something on the network - email getting delivered, etc. I've rebooted to recovery, and wiped the cache, but now I am considering doing a factory reset. Anyone else experiencing this? Anyone got any ideas that don't involve me reloading all my apps and data?
Thanks in advance.
-Chris
yeah, i'm also getting some lagginess. it's mostly when i unlock my phone using the fingerprint reader. the transition takes a super long time. i feel it's mostly the animation that's causing the ton of lag. initially after i updated to 9, opening and closing apps would take forever as well. but changing the animation with nova launcher made it a bit snappier; although it's still slower than 8.
No lag here
You guys might want to do a clean firmware install, I don't have any lag on this version I didn't take the OTA just flashed the firmware.
I think I may have resolved at least some of the issue. First, I use a SD card to hold some pictures, and videos, and other data (no apps). I reformated the card from android, and this resolved about 80% of my lag issues. Not sure if there is some kind of disk polling that is done, but with the clean format on the SD card, things most run smoothly now. The other area I'm still seeing a little lag is when scrolling over something in apps like google news where it is trying to pull a video or large image file and there seems to be some delay in the network. At this point, I think the issue is in my wifi network, not my phone (although I'm still no ruling it out). But at least it is better.
kc6wke said:
You guys might want to do a clean firmware install, I don't have any lag on this version I didn't take the OTA just flashed the firmware.
Click to expand...
Click to collapse
Dead on. While I was able to make my G6 better, it was still laggy at times. Yesterday, I bite the bullet, backed up my data, and did a clean flash of the current firmware. Now the phone is smooth as glass. Good call.
Thanks,
-Chris
Noticed the same thing. Reflashed for some other reason and instantly saw the lag that had been getting more and more noticeable disapear.
What do you mean by 'reflashing'? Is that the same as 'restore to factory settings?'
I've read a thread on the Motorola forum where users have done that, with no noticeable results.
Nightwing-1 said:
What do you mean by 'reflashing'? Is that the same as 'restore to factory settings?'
I've read a thread on the Motorola forum where users have done that, with no noticeable results.
Click to expand...
Click to collapse
No, I literally reflashed the ROM.
I downloaded the current official ROM from here:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/
(note the link is for the US Retail channel distribution, if your phone is not RETUS channel, find the matching ROM for the channel your phone is.)
Once downloaded, I used the RSD lite app to flash the phone.
http://download.canadiancontent.net/RSDLite.html
You can google exact directions to use the tool, but basically, you reboot your phone to the bootloader, start RSD Lite, connect the USB cable (I had to use the factory cable on a USB 2.0 port to make this work), select the ROM file, and press Start.
Note: This will wipe your phone! So make a backup of your data.
I'm not familiar with flashing ROMs etc. And I don't want to mess up my phone any further.
Despite the fact that Motorola insist that there is no problem, I'm hoping their forum will convince them that there is.
Thanks for the help, but I'll keep it as it is. Meanwhile I'll be looking around for a dependable Android One phone.
I found one thing that helped:
Go in to 'Settings', 'system', 'Motorola privacy'' and uncheck both the slides in the menu. And I disabled the Google feed on my start screen (Swipe access).
The restart your phone.
The phone is a lot less laggy after that.
update! the August security patch update kind of helped with the lock screen lag I was experiencing.
blueberryapple said:
update! the August security patch update kind of helped with the lock screen lag I was experiencing.
Click to expand...
Click to collapse
Just did a check on my phone, and there is an update on the RETUS channel.
PPS29.118-15-11 / Security patch level: August 1,2019
A few questions about this. Through pure dumb luck, I didn't accept the Pie update, and have turned off automatic system updates in the Developer's options. It gives me a notice of new firmware a few times a day, which I decline, but so far has not updated without my consent. I realize it may do that at any moment regardless of the Developers setting.
So I'm still on Android 8, and would be delighted to stay there. But, if I'm forced to go to 9, would I be able to flash 8 again using the files here? Would that accomplish anything, or would it still insist on going to 9 after I had flashed 8?
The earlier reference to the "current official" rom - does that mean the latest 9 rom?
Why would installing the same v9 rom over again produce any different result from the OTA update to that rom?
Is there any way to turn off the firmware update notices? I've tried lots of things, but they still come.
Just trying to figure out what my options are, and what I should do. There's a 42-page thread on the Lenovo forum about this problem, with no indication that Lenovo/Motorola will lift a finger to fix it, apparently being content to see some unknown number (perhaps all) of the G6's ruined by the update to 9. I called Moto CS, and they blamed Google for the problem. Obviously, I bought the wrong brand of phone. Actually, it's my first smart phone. It seems beginners luck is a myth. At least I know better than to buy a Lenovo computer when Windows 7 becomes dangerous in January.
Anyway, I would appreciate any comments on the G6 thing.
Hello, is it required to have unlocked bootloader when doing re-flashing the official rom?
ici0606 said:
Hello, is it required to have unlocked bootloader when doing re-flashing the official rom?
Click to expand...
Click to collapse
I posted this in another related thread:
-------------------------------------------------------
JimmiH on the Lenovo forum has found "Lenovo Moto Smart Assistant", a new utility from Motorola, which is installed on your PC (Win 7 or 10). Included in the utility is a "rescue" function which appears to do the same thing as RSD Lite - resurrect a phone from any software issues. It downloads the correct official rom and reflashes it to the phone. JimmiH will be reporting back over the next few weeks as to whether the rescue has permanently solved his Pie lagginess issues.
The advantage of this LMSA over RSD Lite is that it runs on Windows 10, and presumably works with USB3 ports, while apparently neither was the case with RSD Lite. And of course you don't have to go hunting for the right rom.
----------------------------------------------------------------
My understanding is that this utility does not require unlocking, and it does not root the phone.
Hello, I tried LMSA for flashing, but it says not supported device, I have model XT1925-4.
ici0606 said:
Hello, I tried LMSA for flashing, but it says not supported device, I have model XT1925-4.
Click to expand...
Click to collapse
RSDLite will work on Windows 10, I have been using it, even on the newest Windows 10 version 1909. It will not work on usb 3 ports though. If you have any USB 2 ports available, plug the cable into one of those and it will work.
xfrobex said:
RSDLite will work on Windows 10, I have been using it, even on the newest Windows 10 version 1909. It will not work on usb 3 ports though. If you have any USB 2 ports available, plug the cable into one of those and it will work.
Click to expand...
Click to collapse
Hm I have just USB 3 on my PC, ok will try on some older one.
But is it required to unlock bootloader, when using RSD Lite?
Thanks.
ici0606 said:
Hm I have just USB 3 on my PC, ok will try on some older one.
But is it required to unlock bootloader, when using RSD Lite?
Thanks.
Click to expand...
Click to collapse
No. RSDLite doesn't require unlocked bootloader.
Peabody424 said:
I posted this in another related thread:
-------------------------------------------------------
JimmiH on the Lenovo forum has found "Lenovo Moto Smart Assistant", a new utility from Motorola, which is installed on your PC (Win 7 or 10). Included in the utility is a "rescue" function which appears to do the same thing as RSD Lite - resurrect a phone from any software issues. It downloads the correct official rom and reflashes it to the phone. JimmiH will be reporting back over the next few weeks as to whether the rescue has permanently solved his Pie lagginess issues.
The advantage of this LMSA over RSD Lite is that it runs on Windows 10, and presumably works with USB3 ports, while apparently neither was the case with RSD Lite. And of course you don't have to go hunting for the right rom.
----------------------------------------------------------------
My understanding is that this utility does not require unlocking, and it does not root the phone.
Click to expand...
Click to collapse
Count me among those watching this thread, in particular looking for evidence that LMSA (or RSD Lite) actually eliminates the lag problem for more than a few days. My phone is a bone stock model XT1925-6 running Android 9, PPSS29.118-15-11-2. Lag improved after the October update but returned in about a week.
I appreciate the efforts of this group in trying to resolve this problem.
My sister-in-law recently switched to TMo and ended up with a "free" G7 Power running Android 9. It's very smooth with no lag at all, so Moto apparently knows how to resolve this problem, they're just not helping us with the G6.
Hi all,
I am writing from India. I am using a nokia 9 pure view device. I have not gotten the Android 10 update. I am on Android 9, the November security patch.
I am blind so use talkback. I know there is a way of loading the ota update via using adb and the recovery mode. However, in recovery mode, talkback does not work so I am wondering how to get this update.
I have contacted Nokia support without success. The India support did not have any official information on the update and when I contacted Nokia on twitter, I was told to wait as the update would be rolling out in patches. This was in December. I understand that we are up to the first security patch of Android 10 and still no update. I cannot determine if this is a problem with India or something with my phone.
What can I try to get the update?
Pranav
Other than continuously trying to run the Update check manually via System Settings, not sure there could be an alternate solution.
Or, perhaps a fellow Android enthusiast around your area who is familiar with running adb commands may help you out?
Good luck with updating, hope your phone receives it soon.
graphreak said:
Other than continuously trying to run the Update check manually via System Settings, not sure there could be an alternate solution.
Or, perhaps a fellow Android enthusiast around your area who is familiar with running adb commands may help you out?
Good luck with updating, hope your phone receives it soon.
Click to expand...
Click to collapse
PL] Thanks for your message. I have been checking since December 6 without success. However, I have extracted a logcat dump after running the manual check for updates via adb. The log is on my blog but I do not see how to paste the link because I am not permitted to do for anti-spam reasons. I'll try below and hopefully someone will be able to put the link together.
techesoterica dot com /wp-content/uploads/2020/01/update01.txt
something that's easy to miss is to make sure you don't have ad blockers running. I had blokada and it interfered with the phone's ability to detect the update.
It's not a problem with your device.
Nokia 9 Pureview in UK and India are not getting their updates delivered on time. Others having the same device are also experiencing this problem.
Hi all,
I have fixed the update issue and am posting the solution here for completeness. I do not think I can post links. The answer is on my blog at techesoterica dot com.
The fix involves using recovery mode to apply two updates manually after which the regular patches show up.
February security update has been issued.
Does it fix A10 issues? Wont upgrade to 10 again unless they are fixed...
Webghost DK said:
Does it fix A10 issues? Wont upgrade to 10 again unless they are fixed...
Click to expand...
Click to collapse
It doesn't