Hi..
im so curious about this, what is the difference between:
1. AOSP Webview and Google Webview?
2. What are the advantages of them?
3. Which one is better (or suggest) to using in custom roms nougat?
i noticed, mostly all custom roms preinstalled with AOSP webview (as you can see it in dev. options on "webview implementation".) but once we donloaded google/android system webview in playstore it automatically replaced the AOSP webview with Google one. and theres no option to switch or choose between them.
4. does the Dev's or AOSP webview will always be updated?
(since google webview always does within playstore)
If anyone have ideas about them, a bit of explanations which one should i pick on custom rom, i would be much appreciated, and im sure people would like to know also, thanks a lot!
Good questions out there. I'm curious about them too But since you've opened the thread at a specific section like "oneplus 3T questions", don't expect much replies.
Not many people gonna see this
aosp is the bundled web view with the aosp roms just like the keyboard. they cant be updated from playstore whereas google web view can be updated.
I've used both and didnt find any particular issue or advantage with either of them. currently i'm using chrome webview.
Chrome webview. It is supposed to be more memory efficient.
Sent from my OnePlus 3T using XDA Labs
I upgraded from O to P, then rolled back to O after a few days of trying out P (have my own reasons, one of which is that of Magisk and the number of issues that I and others experienced/are experiencing on P).
Before the upgrade, I received a Play Store update for the Nokia Camera that was at v90.9.xx at the time. It was working well with O despite issues here and there. Then I made the jump to P, which came with the v91.9.xx Nokia Camera.
Now that I rolled back to O with Sept 2018 patch level, I was surprised to find out that the Nokia Camera from the Play Store disappeared. I could no longer update the app that came with a v8.xxx. It is now marked as incompatible with my device. As a workaround, I sideloaded the latest v91.9.1130.40 available apk from apkmirror. It installed and ran normally but then would immediately FC after a few minutes. No amount of clearing appdata/cache would make it run on O without FCing. So I settled with the last version that ran without issues, v90.9.1125.10.
My question is, would anyone have any idea if HMD is removing support on O for future versions of the Nokia Camera starting with v91.xx?
In the app description it still says there for requirements a Nokia smartphone running at least Android O 8.0 and the apk, even though its target SDK is api28 (Pie), its minimum SDK is api26 (Oreo).
EDIT: Even though I'm using a gcam port for my shots, I would still like to have an updated stock cam on Oreo for its other features like bothies, PRO mode, and 16MP selfies ?. I plan on staying a little while longer on O. ?
I have updated to Pie among other reasons, for new camera software since I get use to on Nokia 6.1
miljenko said:
I have updated to Pie among other reasons, for new camera software since I get use to on Nokia 6.1
Click to expand...
Click to collapse
That's a valid point, but not quite helpful in my inquiry. The Nokia Camera SHOULD be made available to at least Oreo and later. There hasn't been a complete rollout of Pie in Nokia's entire device lineup, but the Play Stores marks the current version v91.9.1133.80 incompatible with Oreo, locking out devices that still have no Pie update available and denying updates and bug fixes to the stock camera.
braveheartleo said:
That's a valid point, but not quite helpful in my inquiry. The Nokia Camera SHOULD be made available to at least Oreo and later. There hasn't been a complete rollout of Pie in Nokia's entire device lineup, but the Play Stores marks the current version v91.9.1133.80 incompatible with Oreo, locking out devices that still have no Pie update available and denying updates and bug fixes to the stock camera.
Click to expand...
Click to collapse
But it is available on Play store for Nokia 6.1 2108 running Oreo.
braveheartleo said:
I upgraded from O to P, then rolled back to O after a few days of trying out P (have my own reasons, one of which is that of Magisk and the number of issues that I and others experienced/are experiencing on P).
Before the upgrade, I received a Play Store update for the Nokia Camera that was at v90.9.xx at the time. It was working well with O despite issues here and there. Then I made the jump to P, which came with the v91.9.xx Nokia Camera.
Now that I rolled back to O with Sept 2018 patch level, I was surprised to find out that the Nokia Camera from the Play Store disappeared. I could no longer update the app that came with a v8.xxx. It is now marked as incompatible with my device. As a workaround, I sideloaded the latest v91.9.1130.40 available apk from apkmirror. It installed and ran normally but then would immediately FC after a few minutes. No amount of clearing appdata/cache would make it run on O without FCing. So I settled with the last version that ran without issues, v90.9.1125.10.
My question is, would anyone have any idea if HMD is removing support on O for future versions of the Nokia Camera starting with v91.xx?
In the app description it still says there for requirements a Nokia smartphone running at least Android O 8.0 and the apk, even though its target SDK is api28 (Pie), its minimum SDK is api26 (Oreo).
EDIT: Even though I'm using a gcam port for my shots, I would still like to have an updated stock cam on Oreo for its other features like bothies, PRO mode, and 16MP selfies . I plan on staying a little while longer on O.
Click to expand...
Click to collapse
I am in the same shoes like you. I also want to stay on Oreo for some more time until they fix graphic glitches and some small bugs on Pie.
Last time I rolled back from Pie beta to Oreo, Nokia camera was also not showing on the Play store, and after a week or so, the update came...
We shall see about this time.
Btw. camera version you marked as one to be working, is also crashing for me, especially when I try to use the silly faces and masks from the top shortcuts...
miljenko said:
But it is available on Play store for Nokia 6.1 2108 running Oreo.
Click to expand...
Click to collapse
I'm surprised that it appears on a Nokia 6.1 2018 running Oreo. Does the v91.9.1133.80 work flawlessly with it without crashing? Are the AR stickers working as well? (Though I have my doubts about that, I don't know if AR is supported in that device, lemme know ?)
pujolsk said:
I am in the same shoes like you. I also want to stay on Oreo for some more time until they fix graphic glitches and some small bugs on Pie.
Last time I rolled back from Pie beta to Oreo, Nokia camera was also not showing on the Play store, and after a week or so, the update came...
We shall see about this time.
Btw. camera version you marked as one to be working, is also crashing for me, especially when I try to use the silly faces and masks from the top shortcuts...
Click to expand...
Click to collapse
Hey thanks for dropping by. Regarding that crash with stickers on v90.9.1125.40 yes I experienced that as well and wrote it off as a bug ?, needing a fix. But that's not possible atm because Nokia Camera in the play store on on this phone is marked incompatible, at least on Oreo.
I too am thinking the same way as you, when issues with Pie iron out. The UI glitches I find inconvenient and distracts from the experience. More than that, Magisk is incompatible with Pie on this device, causing certain system functions to go missing, further making the experience unbearable ?. But I do like the improvements Pie brings to the table.
braveheartleo said:
I'm surprised that it appears on a Nokia 6.1 2018 running Oreo. Does the v91.9.1133.80 work flawlessly with it without crashing? Are the AR stickers working as well? (Though I have my doubts about that, I don't know if AR is supported in that device, lemme know ?)
Click to expand...
Click to collapse
Everything works normally, no glitches.
miljenko said:
Everything works normally, no glitches.
Click to expand...
Click to collapse
Thanks for the sitrep on that end. But here it's a different story. ?
Hmm this is weird. I never had the application available on the store for my Nokia 7 plus (O and P)
@braveheartleo : I have the same issue. TA-1046 September patch 8.1.0. The update was showing 1-2 weeks back. I had updated earlier (successfully) but downgraded because of the missing HDR option (autoHDR was not working effectively for me). So I disabled and re-enabled it, going back to factory version. The update was visible but for the last couple of weeks it's not appearing in play store at all.
I had tried to re-update a while back, but it would always get stuck after downloading about 84mb, exactly after downloading the app itself and before downloading "extra data" part that goes upto 150mb. I think its an obb file.
So a couple of days back I found an obb file, around 150mb inside Internal Storage/Android/obb/com.hmdglobal.camera2/.
I wasn't able to delete it, so I forcefully removed it root and went to retry the app update where I found it had disappeared. I obtained the play store url in google, opened it as a webpage, clicked the button to "show in play store".
The app appeared but showed as being incompatible with this device.
I have tried to sideload it (a while back when I could't update), it installs fine but FCs at certain modes (unfortunately I don't remember correctly). Seems I have to use factory one for now.
Gravemind2015 said:
@braveheartleo : I have the same issue. TA-1046 September patch 8.1.0. The update was showing 1-2 weeks back. I had updated earlier (successfully) but downgraded because of the missing HDR option (autoHDR was not working effectively for me). So I disabled and re-enabled it, going back to factory version. The update was visible but for the last couple of weeks it's not appearing in play store at all.
I had tried to re-update a while back, but it would always get stuck after downloading about 84mb, exactly after downloading the app itself and before downloading "extra data" part that goes upto 150mb. I think its an obb file.
So a couple of days back I found an obb file, around 150mb inside Internal Storage/Android/obb/com.hmdglobal.camera2/.
I wasn't able to delete it, so I forcefully removed it root and went to retry the app update where I found it had disappeared. I obtained the play store url in google, opened it as a webpage, clicked the button to "show in play store".
The app appeared but showed as being incompatible with this device.
I have tried to sideload it (a while back when I could't update), it installs fine but FCs at certain modes (unfortunately I don't remember correctly). Seems I have to use factory one for now.
Click to expand...
Click to collapse
Thanks for chiming in. ?
We have the same experience regarding the stock cam. Although I haven't been using stock for taking photos, I too noticed the FCs you have seen. Regarding manual HDR toggle missing from v90.x onwards, I found an earlier version on apkmirror that has HDR toggle in the UI, v85.9.1124.31. Perhaps you can try that out as a stop-gap to the issues we are getting starting with v90.x
One other here commented that the latest Play Store version is compatible with Nokia 6.1 on Oreo, but I wonder how compatible it is in practical terms (no FCs, etc.).
braveheartleo said:
Thanks for chiming in. [emoji16]
We have the same experience regarding the stock cam. Although I haven't been using stock for taking photos, I too noticed the FCs you have seen. Regarding manual HDR toggle missing from v90.x onwards, I found an earlier version on apkmirror that has HDR toggle in the UI, v85.9.1124.31. Perhaps you can try that out as a stop-gap to the issues we are getting starting with v90.x
One other here commented that the latest Play Store version is compatible with Nokia 6.1 on Oreo, but I wonder how compatible it is in practical terms (no FCs, etc.).
Click to expand...
Click to collapse
Apparantly a new camera version has been uploaded to Google play (here) with some new features. Unfortunately, it's still showing as incompatible. Not just for us, but folks on Nokia 8 and Nokia 6.1 also confirmed the same in a telegram group.
HMD is truly going bananas and nuts.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
HMD is truly going bananas and nuts.
Click to expand...
Click to collapse
"going"??????? :laugh:
Gravemind2015 said:
Apparantly a new camera version has been uploaded to Google play (here) with some new features. Unfortunately, it's still showing as incompatible. Not just for us, but folks on Nokia 8 and Nokia 6.1 also confirmed the same in a telegram group.
HMD is truly going bananas and nuts.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Speaking of, have you noticed how the Nokia Mobile Support app quickly jumped from one version to another (it's now at 2.0.9 as of this writing, starting from 2.0.3)? Sure, quick fix releases are commendable, but then you start to wonder how QC for software development is on their end.
divvykev said:
"going"??????? :laugh:
Click to expand...
Click to collapse
At this point, it should be safe to say that they've "gone" now :laugh:, with all the bugs people are experiencing on Pie (3.22C), their unstoppable streak on releasing new phones (and now the change to confusing global naming scheme as well), and missed targets on timely releases of monthly updates, resulting in a release that is rushed (and buggy compared to the betas). :laugh:
braveheartleo said:
Speaking of, have you noticed how the Nokia Mobile Support app quickly jumped from one version to another (it's now at 2.0.9 as of this writing, starting from 2.0.3)? Sure, quick fix releases are commendable, but then you start to wonder how QC for software development is on their end.
At this point, it should be safe to say that they've "gone" now :laugh:, with all the bugs people are experiencing on Pie (3.22C), their unstoppable streak on releasing new phones (and now the change to confusing global naming scheme as well), and missed targets on timely releases of monthly updates, resulting in a release that is rushed (and buggy compared to the betas). :laugh:
Click to expand...
Click to collapse
Yeah exactly.
Gravemind2015 said:
Yeah exactly.
Click to expand...
Click to collapse
Love it when they do that.
got the same incompatible thing on the play store with 2 nokia 7 plus... but its installed. lol
Some problem with novatek-07 displays , what happens with nokia hmd ??
Really they have to repair all novatek displays ? Cant fix it wiyh software ?
A little backstory: As most of you probably know, you are/were able to run up to 4 instances of most apps on your phone. One download from Play Store, one from Galaxy Store, then repeat inside Secure Folder. Obviously with apps like Facebook, you could also use the Dual Messenger feature to run yet another instance.
I'm assuming the October update broke that feature, as I was prompted to update Pokemon Go today (I manage four accounts on one device) and it wouldn't let me update because it's already installed. At the time the issue store, I could access 3 instances that were already up-to-date (both Play Stores and one Galaxy Store). Thinking it was just a glitch, I uninstalled the working Galaxy Store version and tried to reinstall. Would not install, citing that it's already installed. So I uninstalled one Play Store download. Same thing.
In conclusion, I went from four working versions to three, and finally two (one from each store).
So my question is: has anyone else come across this issue AND does anyone have a workaround/solution?
My first thought would be to just downloads the updated APKs via a mirror, but I don't know the phone decides whether to overwrite or install a second instance (that is, how does it install the second instance and is there a way to force it to do that instead of overwriting?) I've also considered downgrading, but I'm on a Snapdragon phone and I /do/ want to stay as updated as I can.
I know it seems like such a minor thing, but it's pretty important to me to be able to manage my accounts on the fly without extra devices or constant logging in/out.
It's time to clean my phone so I might as well update. I'm currently at Pie November update. My question is what are the main Android 10 issues in summary with our device and are there any serious hiccups for the average everyday user like me? How is the battery life like and such? I need an adequate answer not something like "it sucks" so if you're going to write something of that sort, please refrain from doing so. Thanks in advance.
DON'T UPDATE YOUR PHONE FIRST SEE THIS
Basic things work but I face issues many times. Most common Ghost Touch, Phone Freezes for 10-25 secs and then comes a popup System UI not responding and then wait or reboot for phone to get normal. Everything else works properly but update only if you can handle these on daily basis. I have 4/64 GB variant and my usage is somewhat basic to medium with 3-5 apps in memory and phone starts freezing. Also I would say compared to pie the battery loss has increased
I rooted and stripped out all the garbage (feedback etc.) including most of the Google stuff, and I have zero problems.
I would say, however, that battery life isn't the greatest but that may just be the phone and not the OS.
Exxdeea said:
I rooted and stripped out all the garbage (feedback etc.) including most of the Google stuff, and I have zero problems.
I would say, however, that battery life isn't the greatest but that may just be the phone and not the OS.
Click to expand...
Click to collapse
Could u pls add more detail what r those bloatware s.. planning to root soon
Wireless range and speed tanked (you can find kernel with pie driver as workaround. Most custom roms use pie driver as well).
Slow emmc that causes the well known frequent hangs. Even just typing on keyboard you often get stutters.
Settings suggestions won't go away.
Battery charging behavior changed: it charges at full speed with screen off, but with screen on it throttles to 1000ma or 500ma as battery temperature increases.
If you're gonna bother to reset and stay rooted, I'd suggest going custom rom already.
foolfunda said:
Could u pls add more detail what r those bloatware s.. planning to root soon
Click to expand...
Click to collapse
I disabled all of these, though obviously you can pick and chose which ones you want to keep:
Android accessability Suite
Android Auto
bookmark prov
calendar
calendar storage
call log back up/restore
carrier services
chrome
com.android.partners.partnerbookmarks
default print sevice
device health services
digital wellbeing
drive
duo
Exchange Services
feedback
gmail
google
google contacts sync
google location history
google news
google one time init
google news
google partner setup
google play movies
google play music
google play store
GSF
home screen tips
html viewer
keep notes
lens
market feedback agent
musicFX
photos
print service recommendation
print spooler
proxy Handler (com.android,proxyhandler)
setting sugestions - com.andorid.settings.intelligence
tags
you tube
I have been reading the various threads and GitHub issues for popular custom AA apps and it seems nobody has really explained the real reason the apps are not working any more: any apps developed using an unofficial AA app SDK (aauto-sdk) OR using the internal AA APIs will no longer run (crash on start - the screen just blinks and goes back to AA launcher) because of this Exception:
java.lang.SecurityException: Wrong signature - go/gearhead-retail-device
There are temporary workarounds such as downgrading the Android Auto APK and preventing server-side config from downloading to device but currently, for normal non-rooted users which have auto-update on these apps won't work. Renaming their package names won't help either as they will still trigger the Exception when trying to show their UI on AA screen.
For AA developers: Google wants to limit the functionality of AA apps for various reasons, including safety while driving. The only official way to develop AA apps is to use the Android for Cars App Library. This library does of course not allow for low-level API access which custom AA apps relied on - no longer can you just manipulate your own Activity and draw normal Android UI. It also limits the amount of text/interaction permitted. This means any custom apps will have to workaround using the very limited APIs available in this library - a full redesign will be needed.
Perhaps load older version and either use a adb edit or a package disabler to kill updates on stock devices.
OTA updates is the first thing I lock down on a stock Android... once bitten, twice shy.
Any directions what someone which is rooted should do so, never need to update android auto? I have a dedicated phone for android auto in car. I use it only for this. But every now and then, android auto doesn't work and force you to update to last version. (in which last version custom apps doesn't work).
Some suggest use firewall for Google play services and android auto, to cut internet from those. I tried it but I'm not sure it's working..
sosimple said:
Any directions what someone which is rooted should do so, never need to update android auto? I have a dedicated phone for android auto in car. I use it only for this. But every now and then, android auto doesn't work and force you to update to last version. (in which last version custom apps doesn't work).
Some suggest use firewall for Google play services and android auto, to cut internet from those. I tried it but I'm not sure it's working..
Click to expand...
Click to collapse
You have to ID what are the offending update app/UID(s).
Google play Services can be temporarily disabled but it has dependencies like Gmail and certain 3rd party apps. The update app(s) may also be dependencies of this service.
Not a practical solution.
Each case is unique. Sometimes it's a force update to an app like in my Samsung's case, Wearables. The update screwed my Buds+ sound proper. Wearables checks for updates everytime it's used.
Solution: uninstalled new version, install older previous backup copy and use Karma Firewall* to ID the app's and/or UID when it connected to the internet.
Repeat above process as when it connected it again updated Except the second time around I firewall blocked Wearables (there are actually 2 that needed to be blocked) internet access.
Took close to an hour to troubleshoot, quit irritating.
Updates, destroyer of worlds
Yes, well... play with it
*Karma's valuable logging feature is blocked on Android 10 and higher. You can still ferret out the offending app/UIDs but it's harder
Actually app are working correctly on android 9\10\11 installed using aaad, kingInstaller or aaease. Unfortunately this error is showed on android 12 devices and can't find a workaround for now
fcaronte said:
Actually app are working correctly on android 9\10\11 installed using aaad, kingInstaller or aaease. Unfortunately this error is showed on android 12 devices and can't find a workaround for now
Click to expand...
Click to collapse
is Android Auto not working on Android 12 ?
Ze2ro said:
is Android Auto not working on Android 12 ?
Click to expand...
Click to collapse
As now on android 12 will work only with version 6.9xxxx44 but Google is start showing a notification to update, you can avoid it for now but I don't know how lot will work this trick. The other solutions is working with new version but is really annoying and practically you need to clear data of android apps every time you want to connect to the car and use custom app