Anybody having issues with android auto? When connected I get black screen. If there's a fix please provide thx in advance
OP9P has known issues with android auto. For some people, setting USB mode to file transfer or PTP helps. Disabling USB debugging can help. Lineage OS and some other non-OOS based ROMs don't have the issue. This is one of the major reasons Im on lineage
For me, AA was working with OOS, but every time I connected the phone to my car via USB, I had to change the connection mode (only charging/file transfer/ptp…) once plugged in to "stabilize" the connection, or else it it would keep connecting/disconnecting.
Now I'm on LineageOS 18.1, and AA was not working but it was a Gapps package flashing problem with Nikgapps (the full package, or flashing the AA addon was needed, but I encounter a flashing problem because of a full memory that can be solved by configuration) .
Once fixed, AA is working but I still have the work-around to do to stabilize the connection.
clavelm80 said:
For me, AA was working with OOS, but every time I connected the phone to my car via USB, I had to change the connection mode (only charging/file transfer/ptp…) once plugged in to "stabilize" the connection, or else it it would keep connecting/disconnecting.
Now I'm on LineageOS 18.1, and AA was not working but it was a Gapps package flashing problem with Nikgapps (the full package, or flashing the AA addon was needed, but I encounter a flashing problem because of a full memory that can be solved by configuration) .
Once fixed, AA is working but I still have the work-around to do to stabilize the connection.
Click to expand...
Click to collapse
What configuration change did you make to fit the full nikgapps? I tried changing install partition to /system but it still said it was full and fails
dkcats3 said:
What configuration change did you make to fit the full nikgapps? I tried changing install partition to /system but it still said it was full and fails
Click to expand...
Click to collapse
Just that, setting InstallPartition=/system in nikgapps.config and flashing the full nikgapps from twrp.
clavelm80 said:
Just that, setting InstallPartition=/system in nikgapps.config and flashing the full nikgapps from twrp.
Click to expand...
Click to collapse
hmm I wonder if twrp vs lineage recovery makes a difference. And you placed the config file by just using `adb push nikgapps.config /sdcard/NikGapps/nikgapps.config` ?
clavelm80 said:
Just that, setting InstallPartition=/system in nikgapps.config and flashing the full nikgapps from twrp.
Click to expand...
Click to collapse
Also which TWRP are you using? I know there is one in the forums but I remember seeing mention of a different build people were recommending
For me on wireless Android Auto, it's been fine for the most part on latest OOS. Just thought I'd mention.
dkcats3 said:
hmm I wonder if twrp vs lineage recovery makes a difference. And you placed the config file by just using `adb push nikgapps.config /sdcard/NikGapps/nikgapps.config` ?
Click to expand...
Click to collapse
Awesome thank you will config a shor
dkcats3 said:
hmm I wonder if twrp vs lineage recovery makes a difference. And you placed the config file by just using `adb push nikgapps.config /sdcard/NikGapps/nikgapps.config` ?
Click to expand...
Click to collapse
There was already the config file on my system from installing the basic Nikgapps. I was not authorized to modify it from my file manager in Android (I may have forgotten to try and do it with the root access activated), so I changed it from the file manager of TWRP.
I try to solve my AA problem by different ways before succeeding with the config modification.
I first try to flash the full Nikgapps then only the AA addon with adb sideload on the LineageOS recovery. The install was failing with the full message. The system was still booting, but some Google app where closing unexpectedly.
I then installed TWRP, and try to do the same thing, still failing. I tried to flash mindthegapp but it failed also. Then @iNikhilMenghani (the Nik from Nikgapps) told me on telegram to set the InstallPartition settings, and flashing the full Nikgapps worked.
dkcats3 said:
Also which TWRP are you using? I know there is one in the forums but I remember seeing mention of a different build people were recommending
Click to expand...
Click to collapse
TWRP-3.5.1-lemonadep-Nebrassy-2.img from the thread on this forum.
To get mine to work on stock, I needed to switchy MTP to MIDI
I have no issues with android auto. Im on stock 11.2.7.7AA
All ok on 11.2.7.7 BA.
How do you get wireless Android Auto to work? I try it and it asks me to pair my Bluetooth and nothing happens
biggiesmalls657 said:
How do you get wireless Android Auto to work? I try it and it asks me to pair my Bluetooth and nothing happens
Click to expand...
Click to collapse
Just to be sure, you need a recent car with Wi-Fi that is compatible with AA Wireless. If it's your case, I'll let others help because my car is not compatible with wireless.
clavelm80 said:
Just to be sure, you need a recent car with Wi-Fi that is compatible with AA Wireless. If it's your case, I'll let others help because my car is not compatible with wireless.
Click to expand...
Click to collapse
I have a 2021 Subaru Forester limited so it better be lol
also android auto is the #1 leading cause of suicide.
biggiesmalls657 said:
I have a 2021 Subaru Forester limited so it better be lol
Click to expand...
Click to collapse
Subaru doesn't have wireless AA/Carplay.
entropism said:
Subaru doesn't have wireless AA/Carplay.
Click to expand...
Click to collapse
My Subaru has Apple Carplay, my friend uses it frequently
Yes, I know that, Subary has had Carplay and AA since the 2017 models. It doesn't have WIRELESS apple carplay. (or Android Auto).
Related
i have oneplus 3 which is working on oos 4.0.2 but no sounds
it worked fine on oos 3.1.2 only once & no mic speaker error but now restarting on oos 3.1.2
i tried mega unbrick thread
all guides regarding bootloop & dm veriety guides too
if do dirty update through adb or through OTA i m facing mic & speaker error issue
with clean update mobile again start restarting problem at welcome screen & automatically boots into recovery
tried custom firmwares too & having mic speaker issue
can someone help me to solve my problem
wbr
Mobile Smoker
Have you tried any custom rom? I had same problem on my older device Lenovo p2 and custom rom helped me to solve the problem but I reinstalled different roms 1000 times and it fixed my problem. Even on stock rom
Tried custom roms too but on custom roms facing mic & speaker error u can say no sound at all
Hello..I recently flashed havoc is on my OP3.I am having issue with screen wake up..when I double tap still it won't wake up and even while pressing the power button..just capacitive button lights appear. After pressing power button for 4-5 times it sometimes wakes up..please anyone suggest me the problem.
Is there no expert here who can guide me?
..::Mobile Smoker::.. said:
Is there no expert here who can guide me?
Click to expand...
Click to collapse
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
tnsmani said:
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
Click to expand...
Click to collapse
Really appreciated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
..::Mobile Smoker::.. said:
Really appropriated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
Click to expand...
Click to collapse
Click the thanks button.
Am waiting for your report.
After erase all partitions via twrp
I installed full OOS & rebooted system
On setup screen phone showed factory resetting & restarts in recovery mode automatically
Same thing happened when i tried to format all three options inside official recovery
I dont have any personal data in it i just wanted to boot my mobile in working condition with working speaker & mic
tnsmani said:
Click the thanks button.
Am waiting for your report.
Click to expand...
Click to collapse
Anyother solution bro?
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
..::Mobile Smoker::.. said:
Anyother solution bro?
Click to expand...
Click to collapse
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
emuandco said:
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
Click to expand...
Click to collapse
I did as u said but on first boot showed
Factory Data Reset
Restarting
tnsmani said:
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
Click to expand...
Click to collapse
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
..::Mobile Smoker::.. said:
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
Click to expand...
Click to collapse
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
tnsmani said:
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
Click to expand...
Click to collapse
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
..::Mobile Smoker::.. said:
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
Click to expand...
Click to collapse
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
tnsmani said:
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
Click to expand...
Click to collapse
I tried with headphone no change
Even with bluetooth no audio at all
..::Mobile Smoker::.. said:
I tried with headphone no change
Even with bluetooth no audio at all
Click to expand...
Click to collapse
In that case, most likely a replacement of the daughter board is required ie. hardware error.
tnsmani said:
In that case, most likely a replacement of the daughter board is required ie. hardware error.
Click to expand...
Click to collapse
One my op3 booted in OOS 3.1.2 & audio was perfect
So i dont think so it has hardware problem
Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!
BrickingsSoFunny said:
Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!
Click to expand...
Click to collapse
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?
BrickingsSoFunny said:
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?
Click to expand...
Click to collapse
Since I'm just talking with myself in this thread: From the TMO Stock I managed to install TWRP to last on the device. But anytime I install the LOS ROM and restart the phone stays black and is bricked.
Any ideas? Just to be not so alone?
Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install
ThE_MarD said:
Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install
Click to expand...
Click to collapse
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
@Dany XP that is not advised. As the wiki mentions
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
NOTE: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
Click to expand...
Click to collapse
The reason is when your device boots to system, it is at that point that it should "handshake" with the Google Play servers or there's a risk of stability issues with the Google Play services.
Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
Can you explain the second solution (about the both slots active and the pre-los.zip)
Alruse122 said:
Can you explain the second solution (about the both slots active and the pre-los.zip)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)
Dany XP said:
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)
Click to expand...
Click to collapse
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?
Alruse122 said:
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?
Click to expand...
Click to collapse
No, that's for TMO oreo. Don't flash the prep zip
41rw4lk said:
No, that's for TMO oreo. Don't flash the prep zip
Click to expand...
Click to collapse
I supposed, so, what you recommend ti actívate both slots un pie?
Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...
BrickingsSoFunny said:
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...
Click to expand...
Click to collapse
"One and two Sim cards..." That means u r NOT in tmo right? U must be on -05 or 06 I don't remember...
Sorry but the pre-los zip is onlynfor tmo devices (at least that's my understanding)
Decided a list might be nice to have for those interested in flashing GSI Images
All these GSI's I've tested on a BE2026 Lito, but I'd assume its the same for other models. As long as you can unlock bootloader anyway
GSI List
Havok OS
-- Android 10
-- Pros: Reads SIM cards, wifi functions, bluetooth works, camera works, everything works
-- Cons: Once you flash Magisk using custom recovery, it only boots to bootloader, GAPPS won't flash, had to debrick device after this...
/e/OS DeGoogled GSI
-- Android 10
-- Pros: Wifi/Bluetooth/Camera and system work. Magisk flash with custom recovery works
-- Cons: Doesn't read sim cards at all, Screen stays exceptionally bright at all times even at 0% brightness
LeOS DeGoogled GSI
-- Android 10 and Android 11
-- Pros: Same as /e/OS
-- Cons: Same as /e/OS
DotOS GSI
-- Android 11
-- Pros: Not really any lol
-- Cons: Upon initial boot ,screen flashes, System Force Closes, screen is black. Unusable
Android 12 GSI from Google
-- Android 12
-- Never Boots
crDroid GSI
-- Android 11
-- Pros: nothin
-- Cons: have to delete product_a and _b slot partitions to resize for it to function, never boots, kicks you back to bootloader
- currently flashing
Android 12 if it works I also have a list give me time but some roms need permissiver.zip
Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
EduardoA3677 said:
Android 12 if it works I also have a list give me time but some roms need permissiver.zip
Click to expand...
Click to collapse
KaptinBoxxi said:
Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
Click to expand...
Click to collapse
It may be a problem with the vendor or kernel, I could compile but my laptop broke down and renting a server is very expensive in my country
KaptinBoxxi said:
Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
Click to expand...
Click to collapse
Ok, you have telegram, it makes me a bit uncomfortable to write here
EduardoA3677 said:
Ok, you have telegram, it makes me a bit uncomfortable to write here
Click to expand...
Click to collapse
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such
KaptinBoxxi said:
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such
Click to expand...
Click to collapse
How did you get HavocOS to boot? This specific image never seems to boot no matter what I do. Did you flash any fixes or did it just boot up first time?
Generic123. said:
How did you get HavocOS to boot? This specific image never seems to boot no matter what I do. Did you flash any fixes or did it just boot up first time?
Click to expand...
Click to collapse
Flash this after installing the gsi
KaptinBoxxi said:
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such
Click to expand...
Click to collapse
Hi need your help
EduardoA3677 said:
Flash this after installing the gsi
Click to expand...
Click to collapse
Permissiver on this phone for every rom so far just kicks me back to fastboot.
KaptinBoxxi said:
Decided a list might be nice to have for those interested in flashing GSI Images
All these GSI's I've tested on a BE2026 Lito, but I'd assume its the same for other models. As long as you can unlock bootloader anyway
GSI List
Havok OS
-- Android 10
-- Pros: Reads SIM cards, wifi functions, bluetooth works, camera works, everything works
-- Cons: Once you flash Magisk using custom recovery, it only boots to bootloader, GAPPS won't flash, had to debrick device after this...
/e/OS DeGoogled GSI
-- Android 10
-- Pros: Wifi/Bluetooth/Camera and system work. Magisk flash with custom recovery works
-- Cons: Doesn't read sim cards at all, Screen stays exceptionally bright at all times even at 0% brightness
LeOS DeGoogled GSI
-- Android 10 and Android 11
-- Pros: Same as /e/OS
-- Cons: Same as /e/OS
DotOS GSI
-- Android 11
-- Pros: Not really any lol
-- Cons: Upon initial boot ,screen flashes, System Force Closes, screen is black. Unusable
Android 12 GSI from Google
-- Android 12
-- Never Boots
crDroid GSI
-- Android 11
-- Pros: nothin
-- Cons: have to delete product_a and _b slot partitions to resize for it to function, never boots, kicks you back to bootloader
- currently flashing
Click to expand...
Click to collapse
I'm using Corvus 16.7 and everything works just fine EXCEPT connecting a headset or a speaker. I can't do it no matter if I use a cable or via Bluetooth, which is a shame because I use to listen to music that way.
Everything else works fantastic, so I don't have regrets.
bbabel said:
I'm using Corvus 16.7 and everything works just fine EXCEPT connecting a headset or a speaker. I can't do it no matter if I use a cable or via Bluetooth, which is a shame because I use to listen to music that way.
Everything else works fantastic, so I don't have regrets.
Click to expand...
Click to collapse
Ever since the Android 11 update went through, even if I use the debricking Android 10 software to go back, no gsi boots at all. Even GSI's I had that were working.
Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.
UsedNametag said:
Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.
Click to expand...
Click to collapse
I've had this bookmarked for when I had my laptop working.
https://developer.android.com/topic/dsu
Seems we have the ability to add gsi images and everything.
I'll try Pixel 5 Android 12 Beta 4.1 firmware GSI port too, maybe more stuff works.
UsedNametag said:
Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.
Click to expand...
Click to collapse
Did you use the DSU or did you install something using this method?
MetaruSonikkuX said:
Did you use the DSU or did you install something using this method?
Click to expand...
Click to collapse
I used GSI installation tutorial from this forum. Also issues on GSI might be possible to solve, but I have no idea how...
I've totally forgotten to update about my GSI experience on this phone. Pixel 5 port didn't work properly, but I haven't tried any Phh-Treble images yet.
a(11)-a(12) gsi+gms dsu loader worked fine (its the 'easy' button for flashing)on N10 5G (w/unlocked bootloader).but i noticed my storage space was reduced to like 8 or 9gb,(tryin to recall but i flashed back as soon i saw it).and then almost corupted my sd card.. or it misread it. cant remember if it wiped my phone(it was already wiped)or id just flash back over,but setting up phone again and again sucks.man,i got the memory of a goldfish
limitlessbydesi9n said:
a(11)-a(12) gsi+gms dsu loader worked fine (its the 'easy' button for flashing)on N10 5G (w/unlocked bootloader).but i noticed my storage space was reduced to like 8 or 9gb,(tryin to recall but i flashed back as soon i saw it).and then almost corupted my sd card.. or it misread it. cant remember if it wiped my phone(it was already wiped)or id just flash back over,but setting up phone again and again sucks.man,i got the memory of a goldfish
Click to expand...
Click to collapse
Hm I might have to try this out out of boredom. Mind sharing where you found dsy loader? Never heard of it is it specifically for the N10 5g or just a global tool? Oh yeaahhh, I'd also say my memories are about the same. It's from all that reefer mann.
hey beautiful people, I've got a problem.
my phone wont connect to certain car hifi radios with bluetooth. its all fine when I can select "add new device" on my phone and the cars bluetooth is visible, but when the car only has the option to find nearby devices, my op9 just wont show up? its fine with mercedes and most of third party radios like kenwood or bose, but when I try with a VWs bt module for example, the car just wont fkn detect my phone and im certain its cuz of the following reason:
I rooted my OP9 Pro, flashed magisk and arter.
ive had magisk issues with magiskhide/denylist when I first flashed a magisk canary version, one of the newest, cant recall which one tho.
i neither had the "magiskhide" option in magisk interface, nor could I find denylist anywhere near.
some post in this forum suggested changing your phone type via terminal to op8 pro. ive done that, didnt fix my problem tho. then i found a newer magisk version which i flashed .made my problem oboslete, everything worked fine then. that made me change my phone "ID" back to op9pro (EU version, since im from germany).
i hope ANYONE of u has an idea of wtf i mseed up.
Try clearing the cache of phone via recovery
Mangtas_666 said:
Try clearing the cache of phone via recovery
Click to expand...
Click to collapse
Didnt change anything sadly.. But thx
Kickazz080 said:
Didnt change anything sadly.. But thx
Click to expand...
Click to collapse
It was the kernel you flashed. There were reported Bluetooth issues..... Facepalm. Post in arter thread
Hi guys I am having OnePlus 9 pro it has stoped working since after Android 12 update in OnePlus. Have tried hard reset and my car is baleno zeta. Also tried updating Android auto data clear etc.
same issue
loaded coloros 12
When plugging to the car it tells me android auto is not installed.
I try only store and restore back and does not do anything.
car king said:
same issue
loaded coloros 12
When plugging to the car it tells me android auto is not installed.
I try only store and restore back and does not do anything.
Click to expand...
Click to collapse
I think it's because ColorOS is meant for Chinese OP phones and I have read that a lot of Chinese based phones like Oppo or Xaomi phones have had issues with Android Auto in general.
xdarj said:
Hi guys I am having OnePlus 9 pro it has stoped working since after Android 12 update in OnePlus. Have tried hard reset and my car is baleno zeta. Also tried updating Android auto data clear etc.
Click to expand...
Click to collapse
I think I got it working by going into App Management and giving it all permissions beforehand and making sure I click Transfer file / Android Auto once plugging it in.
Yeah, I had the same issue.
The fix is to enable developer settings and under USB set it to do file transfer instead of charging.
steveli92 said:
Yeah, I had the same issue.
The fix is to enable developer settings and under USB set it to do file transfer instead of charging.
Click to expand...
Click to collapse
But I follow this when connecting cable. I have tried all three options charging and storage. Isn't that same doing it from usb debugging
lukehong9 said:
I think it's because ColorOS is meant for Chinese OP phones and I have read that a lot of Chinese based phones like Oppo or Xaomi phones have had issues with Android Auto in general.
I think I got it working by going into App Management and giving it all permissions beforehand and making sure I click Transfer file / Android Auto once plugging it in.
Click to expand...
Click to collapse
So android auto is working perfectly for you in cos 12?
xdarj said:
But I follow this when connecting cable. I have tried all three options charging and storage. Isn't that same doing it from usb debugging
Click to expand...
Click to collapse
So android auto is working perfectly for you in cos 12?. If so did you install app from playstore and it worked just like that after giving permission?
Atul Menon said:
So android auto is working perfectly for you in cos 12?
Click to expand...
Click to collapse
No I never got it working on cos 12. Sorry I meant that is what I had to do on OxygenOS 12. I dont think it will work on cos 12. Or at least I haven't read about a fix anywhere.
lukehong9 said:
No I never got it working on cos 12. Sorry I meant that is what I had to do on OxygenOS 12. I dont think it will work on cos 12. Or at least I haven't read about a fix anywhere.
Click to expand...
Click to collapse
Hmm, got some hope for few minutes when i read the message and then it shattered again
Atul Menon said:
Hmm, got some hope for few minutes when i read the message and then it shattered again
Click to expand...
Click to collapse
Yeah sorry :/ not getting Android Auto on cos 12 was the main reason why I went back to OxygenOS 12. Not facing any of the issues that others are mentioning.
lukehong9 said:
Yeah sorry :/ not getting Android Auto on cos 12 was the main reason why I went back to OxygenOS 12. Not facing any of the issues that others are mentioning.
Click to expand...
Click to collapse
Same, i hate oos 12, so i dint stay in that. Rn on latest stable 11 with redskul mods. I am wating for a fix for android auto in cos or A12 custom rom with stock camera support. Whichever comes first, will move to that