Database Info

Logitech Bluetooth Keyboard+Tf300T problem

Hello, so I recently installed cynaogenmod 10.1 on my device, and everything went smoothly. I bought a Logitech Bluetooth Keyboard(it comes with a pocket-like leather piece/stand). However, I'm able to connect it and the tablet asks for a series of numbers, i input them and then it says connected! I go to any app or even try the home/back keys on the keyboard and nothing responds. The keyboard works because I tried it with the iPhone and my laptop to make sure. Batteries are brand new, is this a cynaogenmod problem? Also, at times when I'm trying to turn on the bluetooth it'll go on and then immediately off no matter what. I have to reboot and then it works again.
Thanks!

Amirocassar said:
I'm able to connect it and the tablet asks for a series of numbers, i input them and then it says connected! I go to any app or even try the home/back keys on the keyboard and nothing responds. The keyboard works because I tried it with the iPhone and my laptop to make sure. Batteries are brand new, is this a cynaogenmod problem? Also, at times when I'm trying to turn on the bluetooth it'll go on and then immediately off no matter what. I have to reboot and then it works again.
Click to expand...
Click to collapse
I believe this is a known issue with CM10.1.
Sent from my Transformer Pad TF300T using Tapatalk HD

[KERNEL] [4.2.2 CM10.1][m4xx3d0ut][kexec,ath9k,rtl8187,USBhost][5/2/13]

so i thought this kernel may be helpful to others so i decided to post it. its a recompiled version of the cm10.1 kernel with Tasssadar's kexec patch applied (thanks Tasssadar!), added support for ath9k, and added support for rtl8187.
this will allow you to use TWRP multirom and boot android or pwnie express's pwn pad backup in which ever order you prefer.
also you may allow them to share the kernel and use (for example) an Alfa AWUS036H or a TP-link TL-WN722N usb wifi adapter with both.
it will allow multiple radios to be used at the same time via a usb hub (pictured) and packet injection works as well.
this is the part that i say "attempting to crack the key to a wireless network on which you are not authorized to is ILLEGAL and i do not condone such actions"
i am a security researcher and only conduct tests on my own networks or ones i am authorized to do so on, i recommend you do the same.
also, if anyone has an ubertoothone or some an industrial bluetooth adapter let me know if they work. if they do not i will recompile and we can retest, i intend on purchasing one as soon as i have the extra funding.
please let me know how it works and ill keep this thread updated with any optimizations i make in the future. enjoy!
edit: NEW UPDATE!!! kernel now implements host mode charging (charges with usb devices connected, power injection cable required) thanks Timur!!!
also i have designed a new power injection cable with a toggle switch for host mode charging.
it allows for a hub, external nic's, or whatever you want to be powered 1 of 3 ways.
1.) with an external power source (in this case the usb battery pack) sending power only to the external devices, therefore not adversely affecting the battery life of the nexus 7.
2.) switch flipped to the other position, nexus 7 will power attached devices and work as a normal usb cable plugged into otg.
3.) both nexus 7 and external devices will be powered by external source
first pic is n7 with 2 wireless nic's, a 4 port hub, and a usb battery pack
second pic is the switchable host power injection cable
third pic is screenshot of second wireless device up and charging icon on
fourth pic is basic schematic for power injection cable (note mine has extra female usb for 1 device at a time)
then last few are some picks from airmon-ng and aireplay-ng in a kali chroot
edit: NEW UPDATE 12/21/13!!! V3 NOW INCLUDES RT2800 AND SYSVIPC! POSTGRESQL NOW WORKING IN KALI!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

just recompiled today with some new features. last week i whipped up a nifty new power injection cable. enjoy!

Nice
Sent from my Nexus 7 using XDA Premium HD app

Super nice! I was going to build my extra cables tonight as well, but realized I was out of small heat shrinks. I need to order more.
"What do you tell a man with two black eyes? Nothing. He has already been told twice."

the cable is working out just as expected, gonna do some testing this week (ie- plug it in and test reaver against wps and leaving it plugged in on my network and launch some reverse shells from remote locations)

m4xx3d0ut said:
the cable is working out just as expected, gonna do some testing this week (ie- plug it in and test reaver against wps and leaving it plugged in on my network and launch some reverse shells from remote locations)
Click to expand...
Click to collapse
Looking forward to hearing some results. I still need to order my ext wifi, so it will be a bit before I can get started.
"What do you tell a man with two black eyes? Nothing. He has already been told twice."

i recommend TP-link TL-WN722N. its only $20 and it uses an atheros chip. as far as i have seen it yields the best all around results, it can also operate in master mode if you want to turn your ride into a wifi hot spot

m4xx3d0ut said:
i recommend TP-link TL-WN722N. its only $20 and it uses an atheros chip. as far as i have seen it yields the best all around results, it can also operate in master mode if you want to turn your ride into a wifi hot spot
Click to expand...
Click to collapse
Sounds good. I dont need a hotsopt though. I have an old linksys router loaded with dd-wrt in my car and set up as a wireless bridge.
Once I get the tp link, I want to add it to my small parabolic setup. I want some RANGE on the go, lol.
"What do you tell a man with two black eyes? Nothing. He has already been told twice."

funny you should say that, i was gonna set up a parabolic on my roof and a yagi for my adapters and see if i could get my network from the beach (only 1 block). they are next on my list so ill run some long range test too and post results.

For my house, I just jacked up my router tx to 210 mW, from 71. I can pick it up about 2 blocks from my house with little issue. Granted, I live in a more rural area and my "block" may very well be much smaller than yours. I have also thought about making a parabolic for here. I have a large 2 story and there is already a vacant dish network stand on the peak. I have an los of about 3 miles, so I think I could really get out there.
Btw: We talked about host mode charging on Ubuntu for N7. Looks like they released 13.10 Suacy Salamander today. Gonna see if they finally got it into thier kernel.
"What do you tell a man with two black eyes? Nothing. He has already been told twice."

Wow!
Could you please add support for the rt2800 driver? This driver allows dozens of compatible usb wifi devices based on the following ralink chipsets: rt3070 (ALFA AWUS036NH), rt5370, rt2770+rt2750(ALFA AWUS051NH/AWUS052NH), rt8070 (nano sized usb wifi superior to 8192cu-based edimax 7811).
Basically, the rt2800 driver seems to have far wider hardware support, including wifi cards with dual band, 5ghz capability.
Here are a couple of lists of compatible devices:
http://wireless.kernel.org/en/users/...800usb/devices
http://wiki.debian.org/rt2800usb
The rtl8187 is great but BG only and has a tendency to get warm (even hot). The AR9271 adds N but lacks the range and still 2GHz only. Don't get me wrong, I have both of these cards (I have four 036H Alfas, two AR9271-based cards, one is tplink 722n).

looking into it, ill pick up an adapter to test with asap

Hi all, just refered to this thread (thanks), I have the pwpad nexus 7 , community free image, it flashed ok and works as it should, I have the correct TPLink wifi, and bluetooth dongle(not ubertooth) as per pwniee site, incedentally I have it on the 16g wireless only model and it states req'd 32g and 3g, it doesnt seem to matter tho... the only think holding me back so far is lack of linux knowledge(learning fast...) as its new to me. I'm trying to have the TPlink usb wifi usable in both andriod and linux software and leave the internal chip wifi asleep forever...its range isnt good and it doesnt inject etc.So I was refered here and am delighted to see your work, Ive downloaded the kernel and will now 'swat up' on proceedures to flash it, will this do what I want?
Regards
Jay

well I flashed the kernel and it hasnt allowed the android aps to 'see' or use the ext TPLink wifi dongle, the functionality is the same as my previous custom kernel from pawnie, except I now have a few errors cropping up, more research required from me I guess and a flash back to the orig kernel to I know some more.
Regards
Jay

Hi,
could you please explain how to flash it with multirom ?
I would like to continu using my Kernel with Android Roms, and your Kernel with the Pwnpad community build
Many Thanks in advance

I don't believe you can flash it with multirom

vertab7 said:
well I flashed the kernel and it hasnt allowed the android aps to 'see' or use the ext TPLink wifi dongle, the functionality is the same as my previous custom kernel from pawnie, except I now have a few errors cropping up, more research required from me I guess and a flash back to the orig kernel to I know some more.
Regards
Jay
Click to expand...
Click to collapse
I'm not sure why you needed to flash this kernel since the Pwnie PwnPad image is supposed to support the rtl8187 and ar9271.

vertab7 said:
I don't believe you can flash it with multirom
Click to expand...
Click to collapse
I understood it should work according to the OP.
m4xx3d0ut said:
with Tasssadar's kexec patch applied (thanks Tasssadar)
this will allow you to use TWRP multirom and boot android or pwnie express's pwn pad backup in which ever order you prefer.
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium

you can flash kernels with multirom, just use the option to inject current boot sector then select the image.
i say this kernel is usable with multirom because is was compiled to support kexec system calls (google kexec). this allows one running kernel to boot into another without shutting down. its a requirement of multirom.
as for android apps seeing your adapter i dont know of any that will, other than android pcap seeing an rtl8187. you need to manipulate your adapters from the command line. best way is with a chroot. you can use them to connect to ap's using tools like wpa supplicant, and any command line scanning tool will see them as long as you manually bring the interface up.

I mistakenly thought it may give fuctionality for the android tools to also use the ext TPLink dongle, not just the liux apps, my mistake. I have a few android tools (ie: Z-Anti, Dsploit) and want them to use wlan1 not onboard wlan0.
Learning fast...
Jay
---------- Post added at 11:06 PM ---------- Previous post was at 11:02 PM ----------
I can bring up wlan1/tplink ok in a terminal window/ssh, and scan, see ap's etc. but if I fire up an android app it says not connected .... is a little beyond me, at the moment. Not sure how android finds its device... maybe a question for an android dev forum.
regards
Jay

might be a simple fix

ok so i just got mk808 android stick.
came home plugged it into my tv via hdmi - mini hdmi adaptor
plugged in the usb power to a 5v - 2amp charger from my nexus 7
the screen on my tv switched over to hdmi 1 blue screen,.......and thats all
i dont have a clue what ido to start it up or anything?
i got a mele air mouse 10 thrown in the deal too which is working on my tab but yeah how do i start up this thing? the blue light comes on and the tv switched to hdmi but thats all.

The MK808 has a blue light that has to be on when powered and blinking when streaming from the net. It shoud boot up by itself after you plug it in.
Check to see that your TV is set to the right HDMI input.
I have mine on HDMI 1. Make sure that yours matches your MK808 HDMI input.
Other than that, try another TV.....

premiatul said:
The MK808 has a blue light that has to be on when powered and blinking when streaming from the net. It shoud boot up by itself after you plug it in.
Check to see that your TV is set to the right HDMI input.
I have mine on HDMI 1. Make sure that yours matches your MK808 HDMI input.
Other than that, try another TV.....
Click to expand...
Click to collapse
thanks for your reply i managed to get it working today with a new usb cable now happily using but trying to find a way to switch it of from remote,. "air mouse f10"

If yours is rooted, install "Rom Toolbox" that it have a widget called "Reboot".
Clicking that will give you all the settings ....

To reboot: instead of the full ROM Toolbox, which BTW is a great app, try Reboot Menu (https://play.google.com/store/apps/...wxLDIxMiwib3JnLnJpY2VrbmlnaHQuZ3MycmVib290Il0). That's all it does, it gives you reboot options (you must be rooted).

got the power menu app cheers
anyone had any experience getting another tablet to work as touchpad?

Try MK 802 lll remote app. Works on a lot of these.

ColinB63 said:
Try MK 802 lll remote app. Works on a lot of these.
Click to expand...
Click to collapse
ive tried droidmote and now this app but i can never find-connect to my mk808? both on same network
edit: got it to connect to the device but i have a bluescreen on phone and tab touching does nothing and the few option i do have seem to do nothing also

kozmo2k4 said:
To reboot: instead of the full ROM Toolbox, which BTW is a great app, try Reboot Menu (https://play.google.com/store/apps/...wxLDIxMiwib3JnLnJpY2VrbmlnaHQuZ3MycmVib290Il0). That's all it does, it gives you reboot options (you must be rooted).
Click to expand...
Click to collapse
I have mine hooked to a wall outlet in my living room that has a light switch to control it... MUCH easier! :laugh:

Robbzilla said:
I have mine hooked to a wall outlet in my living room that has a light switch to control it... MUCH easier! :laugh:
Click to expand...
Click to collapse
You don't want to just just "pull the plug" (or flip the switch) on the unit, it could cause filesystem corruption....
Sent from my SPH-D710 using Tapatalk 2

I have been using quickboot for years.

so theres probably no way to switch on via remote eh?
on a good note i did plug my VERY OLD phillips toucam pro from like 1999 lol and the microphone works!!!
video doesnt camera apps force close but skype works with microphone:good:
also any sixaxis help? seems without droidmote which i cannot get working its a dead end

USB Audio

Hi all,
Just brought a Pixel 32gb coming from the 6P. With the 6p, I'm able to use USB-audio to my cars radio no problem. However, with my pixel - it doesn't want to work. Upon connection, it cycles through the USB modes (Charging, PTP and Audio Source,) which interrupts the connection process. With the 6P, it's a constant 'audio source' USB mode.
I should mention, that the times I've got it working, I've had to wait for the connection to time out, and cause my radio to throw up an 'Android error' (unable to connect.) Then I simply went into developer options and selected 'audio source' as the default method. When this worked, I wasn't able to use the radio buttons (pause / play and seek.)
Nexus 6P - 7.1 dev preview
Pixel - 7.1
Radio: Kenwood KDC200UB.
Thoughts anyone?
Thanks in advance,
Chicken

It doesn't sound like your head unit is demanding "USB audio" and I don't believe it should.. It sounds like your 6P is connecting as a hard drive and you're able to use the head unit to control the tracks. This is how pretty much all after market head units work, I don't believe there are any head units that act like a USB DAC (straight thru USB audio controlled solely by the phone with an analog/digital output).
In my case with my DEH4800BT, my Pixel automatically mounts as storage and the head unit reads the music content and is able to play/pause/skip directly from it. This should be what happens in your case, I had to play with mine a few times in order to get it to work.
Edit: I'm going to play with the OTG adapter and a male/male USB cable to see how my head unit connects. Just as an experiment.

I can assure you, my 6p is not acting as a hard drive due to the radio not supporting MTP. It's a Kenwood KDC200UB. It's using USB-passthrough, and yes, the radio does support it and many others do too.
You may search the radio google, and you'd find a feature called 'hand mode.' This allows Google play etc to pass audio.

You are right, I should have done the research. However your head unit is using AOA and not USB audio in the traditional sense, it's allowing the head unit to be a human interface device and not (just) a DAC .
Your Kenwood head unit technically requires the use of the Kenwood Music Play app however my pioneer also states it needs an app but I don't use one. I did have to cycle my device into midi mode once before it worked you could give that a try or maybe your head unit needs a software update? Are you using the cable that came with the Pixel?
Thank you tho, I never would have fully understood AOA if you hadn't suggested that I look it up.

Last firmware update was last year, the nexus 6p wasn't on the supported device.
It did try to connect to an accessory, which I thought was strange

mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.

k.s.deviate said:
mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.
Click to expand...
Click to collapse
I'm sure AOA2 is still being worked upon, no?

Just an update: popped into a car audio Centre, and tried roughly 40 headunits. Didn't work on any of them. I'm almost positive this is a 7.1 issue

I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.

pixel-painter said:
I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.
Click to expand...
Click to collapse
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT

Suicidal Chicken said:
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT
Click to expand...
Click to collapse
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

pixel-painter said:
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
Click to expand...
Click to collapse
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.

Suicidal Chicken said:
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.
Click to expand...
Click to collapse
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Sent from my sailfish using XDA Labs

nednednerb said:
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Click to expand...
Click to collapse
It works on the 6p with 7.1 Dev preview.
Google's guidelines for nougat were that devices MUST be compatible with AOA. It's a bug.

Having this issue too and it sucks. I had a Nexus 5 and a Pioneer MVH-X380BT and it sounded great with the usb cable. Now with my Pixel my deck says error-19 every time I plug it in. I've tried going into the dev settings and changing the usb configuration and the app SoundAbout and it didn't make a difference. It was a pretty big difference in sound quality on the Nexus 5 between usb and bt and it's lame that the Pixel doesn't have the same audio support.
It would be amazing if Google backported aoa or someone made a mod to add it. That would be worth rootingng my phone for.

I also tried to connect my phone through USB, but it's not successful. Why google didn't provide an easy solution for such a long time?

I have a Pixel 2 and cannot get Audio out of phone to AOA device.
https://source.android.com/compatibility/android-cdd.pdf
In documentation it reads:
SHOULD NOT implement AOAv2 audio documented in the Android Open Accessory
Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0
(API
level 26). (page 102)
WHY must you do this Google!!!! :crying::crying::crying:

Question S22 Ultra and Android Auto (wireless) issue

Does someone else also experience issue with Android Auto?
- When using the cable, it only charges, the S10+ works flawless with AA with the same cable
- When using AA Wireless, it is very laggy, while the S10+ is running smooth with AA Wireless
Any ideas how to fix this?
Saw similar issues on Google Support:
Compatibility with Samsung Galaxy S22 Ultra
Android Auto does not work on Samsung Galaxy S22 Ultra and 2020 Škoda Scala
Update 25-2-2022:
I was able to connect with wired AA by using another USB-C cable, while the USB-C cable that came with the AAWireless device works just fine with my S10+.
But with AAWireless and with Android Auto wired, the screen is very laggy. I don't know if it is related to Samsung's hardware/software or Android 12.
Android Auto Known Issues (Updated: 2/21/2022)
To make AA work, try these steps:
Remove your new and old phone from your car's list of Bluetooth devices
Clear Cache/Remove storage data of the Android Auto app
Uninstall/remove updates Android Auto
Go to Google Play Store and install/update Android Auto
Turn on Passtrough option in AAWireless (works for me without, but it always disconnects after 5 mins, also on the S10+)
For Wired AA, try another cable, that worked for me!
For other detailed steps, try these (thanks to gadinaveh):
https://forum.xda-developers.com/t/s22-ultra-and-android-auto-wireless-issue.4405875/post-86480861

My problem is I use Android Auto wired - because my vehicle is dumb like that - and I've never had issues... used the 22ultra for the first time today (wired) and the Android Auto connection kept dropping... no idea why.

AA wireless won't even setup for me. I see my phone greyed out on my AA screen in my car, but it doesn't do anything otherwise. I haven't tried wired yet, I'll give it a shot tomorrow. Gotta have AA!

Mine won't even connect wired. I plug it in and my car doesn't recognize anything plugged in. (T-Mobile Snap)

Android auto doesn't work properly on my pioneer head unit as well. It tries to set it up and the head unit ends up with a black screen until I disconnect the phone.

Same for me - does not connect to wired or wireless (thru AAWireless). Tried to remove all devices from

Same for me. my S21 was working great before on my AAWireless and with cable (Honda Pilot). I tried to connect with S22 - wired does not work, neither does wireless. Removed all devices from the car and retried - nothing still. very frustrating.
I did see something else that might be related. I can successfully connect my S21 to my Dex on Desktop running on my mac. The S22 will not detect the same Dex (same cable, same laptop). It will successfully work with an external monitor with Dex and with Wireless Dex on my Windows laptop.

So has anyone tried uninstalling AA? Then reinststall?

I have the U.S. Unlocked and after removing my S20 Ultra Unlocked from my 2020 Honda CRV the S22 Ultra connected without any issues at all. Make sure you remove the old phone and the Bluetooth connection settings for old phone before trying to connect with the new phone. Worked for me but then again this is the Snappy version. I have had it 24 hours and not had a single issue yet and I used Smart Switch to setup phone exactly like the old one so they look identical.

Paul_Deemer said:
I have the U.S. Unlocked and after removing my S20 Ultra Unlocked from my 2020 Honda CRV the S22 Ultra connected without any issues at all. Make sure you remove the old phone and the Bluetooth connection settings for old phone before trying to connect with the new phone. Worked for me but then again this is the Snappy version. I have had it 24 hours and not had a single issue yet and I used Smart Switch to setup phone exactly like the old one so they look identical.
Click to expand...
Click to collapse
Thanks Paul for the info.
I used smartswitch but initially did not remove the phone from the car., when nothing worked, I removed all previous devices and cleared storage/cache for AA on the new phone.
Did you (confirming)
1. remove the devices from the car
2. remove the bt connection from the new phone
am i missing something?

gadinaveh said:
Thanks Paul for the info.
I used smartswitch but initially did not remove the phone from the car., when nothing worked, I removed all previous devices and cleared storage/cache for AA on the new phone.
Did you (confirming)
1. remove the devices from the car
2. remove the bt connection from the new phone
am i missing something?
Click to expand...
Click to collapse
My old phone was in there twice in the settings and had to remove both entries. But I didn't do anything to the new phone. I just plugged it into the entertainment port with a cable and made sure Bluetooth on new phone was on and the car recognized the new phone.

Paul_Deemer said:
My old phone was in there twice in the settings and had to remove both entries. But I didn't do anything to the new phone. I just plugged it into the entertainment port with a cable and made sure Bluetooth on new phone was on and the car recognized the new phone.
Click to expand...
Click to collapse
Thanks Paul
Started the same steps on the other honda (civic 2019) and was able to connect with Cable (yay ;-) ).
I then tried to use AAWireless, and while it shows successful connection (phone shows "use AA on your car screen", AA icon shows up on the car screen), AA does not open on the car. In addition, when going into audio when AA is the selected audio source, I see a message of "Loading..." and is stuck there.
Any idea or suggestion will be appreciated

Just received my s22u unlocked. Aa working fine wired, and wirelessly on my Dodge

gadinaveh said:
Thanks Paul
Started the same steps on the other honda (civic 2019) and was able to connect with Cable (yay ;-) ).
I then tried to use AAWireless, and while it shows successful connection (phone shows "use AA on your car screen", AA icon shows up on the car screen), AA does not open on the car. In addition, when going into audio when AA is the selected audio source, I see a message of "Loading..." and is stuck there.
Any idea or suggestion will be appreciated
Click to expand...
Click to collapse
With AaWireless i had the same issue. Until I cleared storage and cache of Android Auto and then Disable Enable it, and then uninstall it. Then i Installed/updated it from the store and it worked with AAWireless, unfortunately still not working wired. Will try removing new phone from my car and then plug in with usb cable.

I have no issue with the connection but the battery drain so badly when using Wireless AA. I did connect through Motorola MA1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

After I got the cable to work, tried the AAW, did not work (I did remove it from the car andn bt earlier), so not sure why this did not work. Before that I cleared storage from AA, and running the latest beta for AA (7.4)

It seems that AA should NOT be transferred from the old phone - after I cleared cache data for both AA and AAWireless it started working albeit VERY slowly - not sure what's up with that. If you are getting just a blank screen - wait for awhile it might come up with the setup screen.

I cleared storage andn cache, and then tried AAWireles (with the AAWireless device) after successfuly completing the cable connection. I was able to connect to the AAWireless device, the phone had the two persistent notification that AA is connected, the headunit showed the AA icon, but when pressing it - AA will not open. So not sure how to fix this or whether there is a step I am missing

Also having problem with aa wireless. Works great with pixel 6 pro works great with s21 ultra. S22 ultra loads in the car but it will not show up on the screen and I can't figure out why. I have deleted the old phone, factory reset head unit. Cleared catch cleared storage. tried many other things. My car is a 2019 Honda Accord. Wire connection works fine

Used wired AA fine today with the S22 Ultra
My current car doesn't allow for wireless AA