Hi guys,
I've been trying to get full mirroring on my peugeot with mirrorlink without any success.
1 . WITH STOCK PHONE (no root) :
Mirrorlink is working with my car when I plug it, but due to restrictions you can't use what you want. I can only use authorized apps like deezer but loose the equalizer.
In order to use WAZE or MAPS, I followed many topics.
I tried with Button Savior method and LG mirrordrive, it doesn't work. For me this is purely a software restriction beacause Messenger pop-up come to my screen and I can fully respond on my car's screen !
I found a topic saying you can modify database of Mirrorlink app (with Android tools for example), to add authorized apps, I had exactly the same folder as in the topic but couldn't modify (no root)
2. WITH ROOT on stock firmware from sammobile
Android tools now fully works, but I don't get the same files in the Mirrorlink Database... strange
I tried tu plug-in to my car : it says on my phone "connected to your car with mirrorlink" but nothing on my car's screen, then after few moment I've got a message on my car like "authentification of the app is not valid"
So when I'm rooted, I can't use Mirrorlink anymore. (with SuperSu)
I tried flashing again with Magisk and hide root, no way.
I feel this is only little software security something but pretty annoying
I'd like this topic to be a reference for ANDROID 7.1.1 or Note 8 devices facing the same issue, because there no hint on the internet about this particular problem. It doesn't seem to be a problem on rooted android 6.0 devices...
I've found topic about screen mirroring fix (add line in build.prop), found about snapchat fix etc but no fix for Mirrorlink.
I tried to uninstall but forbiden even in root, and to install previous version, as well no way...
HELP !!
Fed up, I flashed my Note 8 with stock rom again.
After long long long try, I managed to get full mirroring with the classic method : Rock Scout screen, use Button savior tu initiate any app, and keep trying to clic on LG mirrordrive to get (or not) to full mirroring.
This is very instable, flickering, lagging... Useless but fun !
I saw a method with root to fix flickering but I'm not ready to root again if no one as a better solution.
Pirate-X said:
Fed up, I flashed my Note 8 with stock rom again.
After long long long try, I managed to get full mirroring with the classic method : Rock Scout screen, use Button savior tu initiate any app, and keep trying to clic on LG mirrordrive to get (or not) to full mirroring.
This is very instable, flickering, lagging... Useless but fun !
I saw a method with root to fix flickering but I'm not ready to root again if no one as a better solution.
Click to expand...
Click to collapse
Same problem here.
I figure out that I can't use different firmware from another country. I'm in Brazil, then I need Brazilian firmware in my phone. If I use another firmware my car don't recognize the apps Certification - doesnt matter if phone is root or not.
I'd like root my phone again but after December security update I think noone get root A5 again... .... I wanna change the mirrolink database and put there: android auto, google maps, waze.
You can use Samsung Car Mode - not very good, but fun. Problem: all whatsapp messages are read for you when you r driving, even when you dont want.
Hello
Did you find a solution to make work mirrorlink with root ?
Nope. I gave up.
Hello, i bought an app on google play that can launch any app on mirror link.
It's named "full mirror for mirrorlink" developped by SB-SOFTWARE.
Before pushasing the app, i looked for it on all apk plateforms but it's not available.
That works fine with youtube (maybe 0,5 sec sound delay).
On vlc, mx player, and other video players, i coudn't press play button.
Edit : no root needed
I finally can launch any app on mirror link in my car just doing what is describe in this video:
https://youtu.be/P6yUPC-Ukc4
Without root!
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.