Long time reader, first time poster.
So really weird thing happened. I've installed a Launcher Pro today. Looks good etc. Phone seems to be running faster too.
But, when I've tried to connect my phone to my laptop via USB I get the following error msg on my phone: "PC connection is only available on idle screen. Close running applications. ".
I checked everything is closed through the task manager. Nothing is running and it is in the idle screen...
Suggestions?
Solution has been found on another forum. TY anyway. :>
just unable the launcher pro than everything is going to be fine and normal...
Just download home switcher and revert to default launcher whenever you want to connect to pc.
Sent from my GT-I9000 using XDA App
Exactly what I did on someone's advice murphy. Thank you for response.
Apparently this will not be an issue with Froyo release. Fingers crossed.
I had a similar issue, but for me the problem was the samsung supplied USB cable. I tried with another aftermarket USB cable and it connected correctly
hello
previously, on my rooted Xperia T (ICS .223) with kernel SiyahAlpha2, output to my TV via MHL cable worked without any problems.
Today, I have tried it again (but on recently upgraded phone to Assaye 2.0.1 with DoomKernel v5), but the SmartConnect app keeps turning on and off (again and again) the TV out + associated tasks (the default ones, like wifi on, TV launcher, rotate screen).
Phone seems to detect something, but no sing of this on TV.
Any idea, if it is a bug in new ROM or I did something wrong?
thanks
Hello,
I've got a problem with my setup.
I connected Chromecast through the HDMI to VGA adaptop (with audio output) - the setup worked fine straight after connecting power to the Chromecast.
Everything was fine for a day or so and then I turn on the TV and the screen was black.
I checked the connections etc but no joy - I tested all components separately and everything works as expected.
I think the issue might be related to the recent Chromecast update... is that possible?
Does anyone else has a similar problem? What I could check/do to sort it out?
Thanks!
Hi,
Not sure if this can help, but I had a similar (blank screen) issue when the chromecast device was starting up with my monitor turned off (connected with a hdmi/analog audio splitter - for audio transmit only). After turning the monitor on and restarting the chromecast everything seems to be fine, guessing chromecast would initialize the display at boot time only.
Hi up until recently I was able to use android auto in my car. A week ago it stopped working just a message on car computer screen saying no media data from usb. It's asking to connect a compatible device. I haven't made any changes to my phone etc. I have changed the data cable. Reinstalled AA. Turned fone off/on. Deleted the cache etc. I have read there is a problem either with Google or AA. All I use it for is the navigation on my car computer screen. Is there even an app I can use for this? I've tried to use Waze but getting the same problem. I'm using an Huawei p30 Pro with no problems until now. Thanks
Hi I wonder if anyone else is using this wireless dongle for AA and CP for Android HU only. I also wonder if there is a modified Autokit apk which would allow to us to use non-official apps like Fermata player etc.... Alos 6 tap restriction would also be nice to be removed.
I have carlinkit ccpa-cpc200 wireless AA/CP dongle for Android HUs. I have one issue with it. Using Android Auto (no matter, if wired or wireless), the only way to make automatic dark mode to work is to set it up manually during which time it should change (i.e.: one has to set sun set and sunrise times manually and adjust them), and this also only works if after a wake-up (hotboot) of the radio the Autokit apk is killed and restarted. If it is not forced stoped and restarted then automatic dark mode will not work even if you have configured under manually under the settings as written above. So what i did is wrote a Macrodorid "script" to kill the app when screen is turned on. Then once usb connection is established it restarts the Autokit app. This method also doubles the time which it would normally take to connect and start the wireless Android Auto. I wonder if someone else has faced this or similar issues.
Sorry for resurrecting an old thread. Anyone able to load the new coolwalk UI? I was able to load it by plugging it straight to the car's usb port but connecting to autokit still triggers the old split screen UI.
matrixx1 said:
I have carlinkit ccpa-cpc200 wireless AA/CP dongle for Android HUs. I have one issue with it. Using Android Auto (no matter, if wired or wireless), the only way to make automatic dark mode to work is to set it up manually during which time it should change (i.e.: one has to set sun set and sunrise times manually and adjust them), and this also only works if after a wake-up (hotboot) of the radio the Autokit apk is killed and restarted. If it is not forced stoped and restarted then automatic dark mode will not work even if you have configured under manually under the settings as written above. So what i did is wrote a Macrodorid "script" to kill the app when screen is turned on. Then once usb connection is established it restarts the Autokit app. This method also doubles the time which it would normally take to connect and start the wireless Android Auto. I wonder if someone else has faced this or similar issues.
Click to expand...
Click to collapse
Hi there, would you have the script that you wrote. Thanks
Hello all, i received one ccpm-cpc200but i cannot connect with my peugeot 308 from 2018, any help?
Pedrojamiranda said:
Hello all, i received one ccpm-cpc200but i cannot connect with my peugeot 308 from 2018, any help?
Click to expand...
Click to collapse
Hi I did you install autokit APK on the Android headunit? If you have factory radio with AA then this dongle is not for you. You will need to buy other type of dongle to make your factory AA wireless
matrixx1 said:
I have carlinkit ccpa-cpc200 wireless AA/CP dongle for Android HUs. I have one issue with it. Using Android Auto (no matter, if wired or wireless), the only way to make automatic dark mode to work is to set it up manually during which time it should change (i.e.: one has to set sun set and sunrise times manually and adjust them), and this also only works if after a wake-up (hotboot) of the radio the Autokit apk is killed and restarted. If it is not forced stoped and restarted then automatic dark mode will not work even if you have configured under manually under the settings as written above. So what i did is wrote a Macrodorid "script" to kill the app when screen is turned on. Then once usb connection is established it restarts the Autokit app. This method also doubles the time which it would normally take to connect and start the wireless Android Auto. I wonder if someone else has faced this or similar issues.
Click to expand...
Click to collapse
Is it possible to get the script? TIA.
hi, well its possible to share of course, but i dont know if it will help you because its very specific to my Headunit set-up.
The part which anyone can use fom it, in order to get the dark mode to work (if you set the day time and night time manually in the autokit apk) is very easy. Just put a trigger in macrodroid: screen unlock, and then put an action kill app and choose Autokit apk. It will only work if you have root rights on the headunit.