Hi,
The screen (LCD+touchscreen) of my i9100G device is completely broken (a few months old...:crying.
I had previously properly installed CM9 RC1, ClockWordMod recovery and rooted with "advanced method 2" from this post http://forum.xda-developers.com/showthread.php?t=1679778.
The system works very well, superuser app installed, root permissions prompted for apps that need root access...etc
Now with the broken screen, i still access the phone via adb for scanning files and directories of sdcard or launch apps (that do not require root access, see after) but without being able to interact with.
It is a rich experience to see how useful a trackball or physical keyboard is ... or the opposite, how many apps need these features to offer basic functions ...
An example: splash screen and first help screen with 4 pages via viewpager to showcase the app ... without a functional display, i was unable to access the main screen of the app ... i even modified the source code of open apps (opensource apps) to have "instant" behaviors or to launch the main action once loaded or if they require interactions, call the related action with the "back" key button (onKeyDown(int, KeyEvent) function).
i found a great app that displays on my ubuntu desktop the screen of the phone (great also to see that only the screen/display was broken) and you can interact with the phone from your desktop (mouse, keyboard) ... but this last feature is available only for rooted devices. The java app is androidScreenCast http://code.google.com/p/androidscreencast/.
My device IS rooted, but ... CM9 has implemented a new security layer preventing root access via adb if option in settings is unchecked, i didn't notice that and leave the option unchecked. Nice for security. But now, i don't see any way to check this option and thus any way to interact with the phone via "androidScreenCast" -like apps to be able to interact more with the phone.
Have you got any ideas to have full root access on CM9 ?
Next step is 1) trying to flash an other ICS ROM or a gingerbread one via ODIN or fastboot (complicated with a broken screen) and 2) replace the display.
Thanks in advance for your reading and help.
======================================
[UPDATE] I solved my problem.
In case it could help someone in similar situation (with cm9, i9100G or else):
1) i found this useful app: http://piglings.blogspot.fr/2011/08/android-screen-control-without-root.html (download the zip file provided by the author here -if someone could paste it on an open location .., then run the bat file from windows)
2) i am now able to interact with the screen (low but greatly enough to allow root access when prompted by superuser !), connect wifi (fortunately it is the first option in menu/settings !) or other things that require clicking on a button to accept (touchscreen is not working, so sliding or scrolling don't work, you will be able to do so in step 6) )
3) i installed webkey app http://webkey.cc/ (Play Store: https://play.google.com/store/apps/details?id=com.webkey)
4) to launch webkey, hit search button in menu from home (search the app with google search app, the keyboard is working from 1) ) and type webkey
5) superuser will prompt permisison dialog, you will be able to click on "allow" (yes !) and webkey will be granted root privilleges
6) an ip adress (local if on wifi) will be provided by webkey from wich you can interact with your phone (with touchscreen and many other features); you can also configure in settings tab a username/password to connect from webpage (user's setting/create user) and other options listed at http://webkey.cc/
7) and there i have all features, touchscreen, scrolling, keyboard, mouse clicks, interaction with apps ... great ! And of course, menu/settings/developer options/root access/adb AND apps !
An other solution also considered was http://www.androidlost.com/ but not tested; it seems nice (requiring no interaction at all, push install from play store, activate via specific keywords in sms, login on remote server to control the phone, erase data/sdcard ...).
... enjoy !
The Past:
I've been working on this app since last 3 months and I'm pretty happy with the progress I made:fingers-crossed:. I was waiting for this day to post the app publicly in the forum which taught me so much:laugh:. Well, some might say this app is completely useless, but other might find it useful. I've considered all kind of users and accordingly added features to make it as productive as possible. This is still an alpha release and you may find several bugs, and I would really appreciate if you guys can report it whenever it crashes:angel:. I'm open to all kind of ideas and feel free to suggest me additional features.
About Floating Commander:
Well, I'm sure you're all are in love with Google Now, but then, so I'm I. But it sucks sometimes, how Google Now can't do many things that I want it to do, may be like setting the brightness of my screen to lets say 50%, changing sound settings and so on.. So, I've tried to accommodate all that in this app. Yes, this is a voice command utility that will do many things which Google Now can't (may be in future, but not now). Moreover, I've seen people who don't like the app simply because it eats up a little bit of data from your data pack and affects the battery aswell. Now, this one also needs data, but just to transform your voice to text, and rest all the features are processed natively and accordingly invoked. Its superfast (atleast on my phone, Galaxy Note 2) and it gets the work done. This app starts a floating widget which can be put on any edge of the screen, or freely (if u choose so in settings), and upon clicking, will invoke a voice recognition utility (Google's own recognizer) to detect your command (English Only for now) and thanks to its SpeechOptimizerEngine, it processes the command very fast and accurately and executes it. You can basically select/de-select each and every feature this app has from its settings and accordingly it''ll take more or less time (which is again negligible). Now, I'm sure there are people who think this is just another bull**** app and they don't need it when they have Google Now. Trust me guys, I have something for you guys aswell. I've put two new options which will be very helpful to most of you, I'm sure. Enable inbuilt "Google Now" mode in settings to launch "Google Now" from any screen using the floating widget, this will completely disable the native feature of the app. Also, another option is "One Touch" mode which can map to any activity, like changing sound profile, opening flash light, running memory cleaner or opening any installed app at the touch of a floating widget from any screen. The battery consumption is almost zero if it is not used, and if used, takes only for the internet data for converting voice to text. There's an additional feature to send the floating widget back to notification area by long clicking (when playing games) and bringing it back by clicking notification area. Its completely add free at the moment and I would definitely try to keep it that way. Overall, this app might or might not be suitable for your, but I would really appreciate if you guys devote some time analyzing and reviewing it here.
Ok, the final and the best thing, I've also tried integrating an offline mode, yes you heard it right.:laugh: But that's only for U.S. folks, since it works on only U.S. English accent. So, please don't review the app badly if it doesn't work offline for others.
Commands to try:
You can launch/open an app by saying:-
- launch <app name | any settings>
- open <app name | any settings>
- start <app name | any settings>
- run <app name | any settings>
Examples:-
- open bluetooth settings
- run cleaner
- launch whatsapp
- open browser
- open messaging
- run flashlight
You can toggle things by saying :-
- turn on <settings name>
- turn off <settings name>
- start <settings name>
- enable <settings name>
- toggle <settings name> on/off
- turn <settings name> on/off
Example:-
- turn on wifi
- start bluetooth
- switch on internet
- enable hotspot
- toggle autobrightness on
- turn rotation on
You can use set commands like:-
- set <settings name> to <value>
- change <settings name> to <value>
Example:-
- set brightness to 60%
- change ringer mode to silent
- change music volume to 80%
- set ringer volume to 100%
- change ringer mode to vibrate
- set all volume to 100%
- set alarm for 8:30 a.m.
- set alarm for 9:00 a.m. every weekday
- set alarm for 10:00 am. on monday tuesday thursday
Miscellanious Commands:-
Examples:-
- clean memory
- dial 12938
- call <contact name>/ <contact number>
- send message to <contact name>/ <contact number> <message>
- send message to joshua I'll be late tonight
- browse to www.google.com
- show my location
- drive from <location from> to <location to>
- drive to <location to> from <location from>
- show way from <location from>
- navigate to <location>
- navigate from <location> to <location>
These are a few bunch of examples, keep trying combinations and I'm sure most of them will work. Let me know if you have a worthy new command in mind. May be I've just wasted time in this, but I'm really looking forward to encouragement here for further development. And I repeat, I'm not doing it for financial gain.
Screens:-
Credits:
This app uses StandOut library by pingpongboss for creating the floating widget. Many thanks to him.:laugh:
This app also uses an open source application Searchlight without which, I couldn't have added an amazingly looking flash light inbuilt in the app. :laugh:
Apart from these, the application has been coded from scratch and supports only 4.1+
Known Issues: :cyclops:
- I've witnessed a few weird things on Nexus devices (it opens and closes the last opened background activity when voice recognizer is called)
- The floating widget doesn't appear on center when launched for first time (something wrong with my calculations)
- One Touch mode has a few drawbacks (all solved in my latest code which I'll upload in a few days)
- The donation section is mapped to whatsapp (since I was testing something on that and whatsapp has an easy package name:silly
- I haven't changed the min sdk version yet, any device from 1.6 and above can install it, but trust me, that's not gonna work for sure. I'll change it in the next update for sure.
- Theme changer and Widget Types are not working yet, thats easy but uploading an app on playstore takes like 6 hrs.
Overall, I'm hoping I've created something useful and I don't expect any financial profit from it, so please review accordingly. Also, I'm also planning to make it open source in future, but let me think about that again. And yes, this app is just of 270 Kb.
Thanks a lot for wasting your time on reading this. This app doesn't have any help section yet, will add one soon.
Download:
Application is deployed on Playstore in alpha release mode. So, please join the following Google Plus community first:-
boggartWare Google Community
Once you're added, you can find the link under "Floating Commander" category. Alternatively, you can click here and select "BECOME A TESTER". Only who joins this community can be a part of beta testing (that's google's policy). Once you've done that, you'll get a link on that same page to download the app from Playstore. Make sure you access all the links and join the community using the same Google id with which you access Playstore on your own phone.
Thanks guys.
<reserved>
<reserved>
Reserved
<reserved>
First off, impressive work.
What's the benefit of something like this vs something like utter?
Never used utter
aagha said:
First off, impressive work.
What's the benefit of something like this vs something like utter?
Click to expand...
Click to collapse
Hey, I've never used Utter, but this one is for those who thinks that Google Now isn't enough to do the needful. I know, getting things done through voice is a little bit odd. But sometimes, when you're alone, sleepy, don't want to scroll through menus to get things done, this one really comes in handy. Apart from that, I've also put two additional modes, "Google Now" mode and "One Touch" mode which are really really useful for anybody. Try and let me know what do you think.
Just updated to Floating Commander 1.8
Just updated the apk in Playstore to version 1.8
Now you can toggle settings by just saying "toggle <settings name>.
Hope you guys like it.
Check out the public release of the app
Get it here - play.google.com/store/apps/details?id=com.boggartware.fcommander
Other apps
.jpg[/img][/url]
How about playing music? I tried saying run music, play song but it only took me to music player.
I played a song and said, stop music. It took me to the music player,music kept playing.
Any suggestions?
This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis.
App links: https://www.b3itlabs.com/prod.php?id=1
PlayStore: https://play.google.com/store/apps/details?id=gb.xxy.hr
Previous XDA Lab purchases can be downloaded using: https://www.b3itlabs.com/download.php
Last edited: 20/04/2023
Version 7.X Released
- It has braking changes for WiFi, this is mainly due to recent Android SDK limits, like toggling WiFi, BT, getting Mac address and others. Therefore WiFi connection now does need a helper app on the phone.
- Dropped GLES20 as too many issues reported by different bad implementations
- Resolution is now automatically detected based on the cars screen.
- SelfMode (running on phone screen) works without the need of activating developer options in Android Auto.
Last edited: 07/02/2021
Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- Added support for native AA Wireless. This will only work on the units where the BT is accessible from the Android, as many of those android powered Chinese units, have a separate BT board. For devices which supports this, no headunit server or no WiFi Launcher is needed.
- Changed key mapping, user can now define their own buttons as they wish.
Last edited: 21/06/2020
Version 5.2 released
- Removed WiFi Direct
- Improved menu UI CREDIT and THANKS TO @sebaw
- Updated margin setting
- Added option to record audio using BT mic (motorcycle helmets)
- Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
- Option to disable touchscreen
- Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)
Version 5 released
- New UI CREDIT and THANKS TO @sebaw
- New over-scan approach allowing any resolution units to work properly (including portrait mode)
- New mic source (should help with speech recognition)
- Added option to keep status bar (user request)
- Added welcome setup
- Added possibility to use old USB driver (android built in one) in case you cannot get it connected with the new version
- Added option for Gain control on mic
- Added option to keep Wifi off (for USB use)
- Changed Wifi Direct implementation (you will need to install the Wifi Launcher for HUR on the phone to use Wifi Direct)
- Removed option to stretch full screen as this is not needed any more (it will always be full screen)
- Fixed Incoming mode not setting password for some devices
- Fixed app crash when Wifi toggled during app running
- Fixed night icon colors for devices running 4.x
- Fixed app freeze if permissions denied
- Fixed app crash after device unplugged when using native android USB driver.
- Fixed day/night calculation if share GPS turned off
- Code cleanup
- Other bug fixes.
Also a big THANK YOU to @ppietak for helping with code cleanup and bug fixes!
Version 4.5 released
- Fixes for USB shuttering
- New USB driver
- Fixes for reverse camera not resuming on some units
- Added support for incoming connection listener (automating Wifi) - Experimental, read below how to connect
Version 4.4 Released
Change log
Fixed broken touchscreen
Changes on WideScreen mode and HD
Fixes for Rotary
Potential fix for black screen for second connection over Wifi
Left/Right hand driving position option (for widescreen)
Buffer setting for mic (could help when Assistant does not hear what you're saying)
Enjoy XDA Ad Free and check out:
Version 4.3 Released
Change log
Fixed double skip on Spotify when using SWC
No more decoder workaround needed (updated code for video playback)
Added support for rotary (arrow keys can be used for non-touch input)
Enhanced mic input (mic sampling rate can be adjusted in settings for better compatibility)
Added intent: "gb.xxy.hr.WifiP2P" for Wifi-Direct start
Added app color scheme (dark menu for night)
Mapped Key N to open Maps (N=Navigation)
Mapped Key L to open Multimedia (L = Listen)
Changed USB code, hoping to help those who suffered for USB disconnection problems
Fixed a serious bug in share GPS code
For some rooted android headunits the app can now disable the default call screen being overlayed when HUR is running (only if HUR is set as the navigation app!) This will require ROOT
Version 4.1 Released
Change log
Removed Google Play Services dependencies
Honda compatibility fixes
Some other small bug fixes
Version 4.0 Released
How to use the app?
USB Mode
Plug in the USB to your device (in case of tablet use an OTG cable), when prompted make sure you allow HUR to be the default app for the action and you check the always box.
If you are running the app on a device with Android 7.0 or higher, you might need to pull down the notification bar and select the connected USB device before the app starts (this is device dependent)
If the app does not start automatically when you plug in your phone, you can always open HUR, tap the USB button and select the phone from the list.
Wifi Mode
READ SECOND POST
Self Mode (when Android Auto and HUR are running on the same device)
Open HUR and press the self mode button. (you need to make sure Android Auto, Google Play Service, Google maps, Google Text To Speech is also installed on the device and it's up to date)
FAQ / Troubleshoot
All I get is a black screen
- If you are using an Android powered headunit (Joying, Xtrons, etc) look for a setting on your device which allows Video Playback during drive
- Try changing HUR settings and enable Software decoding
What does the "Share GPS" do?
- Share GPS actually forwards the GPS data of your device to the phone, so phone will need to do less work, comes really handy if you have an Android powered headunit, with external GPS antenna, however, if you using a tablet which is built into the dashboard, it's possible that you want to turn off this feature, because your phone will have a more accurate GPS fix.
What is the Sink Audio
- This option enabled HUR to work as a speaker for your phone. If you disable this option, all the sounds will be outputted on your phone speaker (or if your phone is connected to a Bluetooth device, then they will be played back on that)
My carrier doesn't provide data allowance for Wifi, what can I do?
Wifi data used between phone and tablet is classed as intranet not internet so it won't count against your data usage, but do be careful if you have auto-updates enabled on the device running HUR those updates will be downloaded over the phone's Wifi hotspot and that will incur data costs.
I have audio-sink enabled but phone calls are coming from the phone speaker. Why?
Android Auto is designed to sink all the audio over USB (Wifi) except phone calls where it will ALWAYS use a Bluetooth headset, if none is connected it will just flip the phone to speaker mode.
Are any hardware keys supported?
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
M Key - Mic
H Key - Takes you to home screen
What about intents?
gb.xxy.hr.playpause Same as pressing the Play/Pause media button.
gb.xxy.hr.next Same as pressing the Next media button.
gb.xxy.hr.prev Same as pressing the Prev media button.
gb.xxy.hr.mic Triggers microphone input.
gb.xxy.hr.phone Same as pressing the dial key (answer phone call when ringing, takes you to dialer screen otherwise).
gb.xxy.hr.day Enables day theme.
gb.xxy.hr.night Enables night theme.
gb.xxy.hr.togglenight Switches between day and night theme.
I need more help.
- Feel free to ask a question on this thread, or you can always drop me an email to [email protected]
How do I collect a bug report / logcat
1. Enabling Developer Mode
1. Open Settings > About phone.
2. Scroll down to the Build number.
3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
4. Return to the Settings menu and select Developer options.
5. At the top of the screen, make sure 'Developer options' is set to On (green).
6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
2. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
1. Hold the Power button down until the menu appears.
2. Select Take bug report. and wait for the device to capture the bug report.
3. Tap the 'Bug report captured' notification when it appears.
4. Share the bug report. (I recommend to email it to yourself.)
5. Download the bug report to your computer.
6. Send the bug report by email to [email protected]
IF YOU UPGRADED TO ANDROID AUTO 2.X
Dial Pad is broken - Workaround available:
- Open AA -> About -> 3 dot menu -> Developer settings -> Application mode -> change to developer. This will bring back the Dial screen.
Version 3.0 Released
Changelog:
- Move USB functions from C to Java
- USB popup numbers limited to 2 and they should remain saved
- App will only start on a phone manufacturer vendor
- App is now running in multi-thread for better performance
- Much enhanced Wifi speed
- Better USB stability
- Should work on RK3188 units as well
- App runs as service so can be run in the background as well
- While running in background supports notification control for media
- While running in background on units running 5.0+ and above you will enjoy Heads-Up notifications for navigation
- Ability to rename the "Headunit" to your own prefered string.
- Fixed Wifi-Direct so can connect over Wifi-Direct as well, but not all devices seems to work
- Moved string to XML so translation to other languages should be implemented in the future
- Fixes some memory leaks
- Supports custom hardware keys
Version 2.5a Released
- Fix for USB close bug in 2.5
Version 2.5 Released - Attention contain BUG
- Left/Right button goes into endless loop
- Added support for ARM64
- Changed car name from Emil to Headunit
- Added mirror output support for HUD display.
Version 2.4 Released
- Improved performance (Wifi should be on par with USB now, even with Audio transport enabled)
- Improved touch sync (no accidental long touches and other strange occasional bugs)
- Option to share the GPS with the phone (reduce battery usage footprint on phone)
- Final fixes for Day/Night calculation and theme switching
- Auto volume adjust fixes (on supported ROM, the volume adjuster is hidden from the user)
- Software decoding works with Audio as well.
Version 2.3 Released
- Improvements and fixes for auto volume adjust
- Improvements and fixes for hardware key input
- Wifi speed improvements (should be able to run smoothly even with transport sound enabled)
- Tweaks for SelfMode (home and recent app button can be used to gracefully exit the app)
And the biggest change:
- Unlimited Browsing support - This is experimental and hacky it's possible that Google will close the loophole at some point but for the time being it works.
Version 2.2 Released - With some major changes
- Fixes for Communication Error 2 received with Play Service 10.X
- New Self mode
- Corrected channels order
- Unlimited browsing working when car is parked (only for Android Auto 1.6)
- Totally changed the Day/Night toggle logic, now the calculations are done inside the headunit app and updated each 10 minutes, so if you're driving all day the sunset/sunrise should be correct. even if you are 500 miles more to the north or west or whatever.
- Added Auto adjust volume option (works for bluetooth audio as well).
- Changed all the key mapping, and using real keys instead of simulated touches:
Supported hardware keys:
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
D key - Changes to Day theme
N Key - Changes to Night theme
M Key - Mic
H Key - Takes you to home screen
The following keys are still usable but they are based on simulated touches:
Up Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
Version 2.0 Released
Changelog:
- Fixed calculated night mode
- Added support for Software decoding (should work now with any device) - If you have problems running HUR, go to settings and enable Software decoding. Do not use software decoding with audio transport, the audio playback will suffer a lot, consider streaming the audio from the phone to a A2DP directly or using a cable to connect the phone Jack to the stereo AUX, or if your phone is rooted you might want to consider Wifi Audio streaming app, it's too much to ask from the Software decoder to do both Audio and Video, unless you have a very strong CPU, but if that is the case I'm pretty confident that the Hardware decoding will work on the device.
- Added option for letterbox display (prevent distortion of stretch)
- Added option to start the app when connected to Wifi
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
Version 1.5 Released - Key features
- Stable Wifi connection
- Added support for Android 7.0 (Self mode as well)
- Self mode running in stable and usable way
- Connecting USB cable will start app automatically (even if phone is running Android 6.0 or 7.0)
- Supports keyboard shortcuts:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
- Uses light sensor (if available) for toggling Day/Night theme.
If you are updating from version older than 1.2 please read:
You won't be able to install it over the old one (Key signature changed!), so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
App requirements:
- Android 4.1 or higher
- H264 Hardware decoding!
How to use the app: (Please read this steps before asking for help)
1) USB OTG
- Plug in the OTG cable to your tablet, connect your phone, done!
2) Self mode (for AA 2.0) - See Video
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Exit Android Auto
- Start HUR and select Self
3) Wifi
- From the phone create a Wifi hotspot
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Connect your tablet to the newly created Wifi hotspot
- Start the Headunit Reloaded app
- HTC ATTENTION! If your phone is a HTC, please change the default IP address to: 192.168.1.1
- Select Wifi
4) Wifi Direct (not supported by all phones/tables)
- Start Headunit Reloaded on the tablet
- Select Wifi Direct
- On the phone go to Settings -> Wifi -> Advanced -> Wifi Direct, join the group. (Do not try to connect as to a normal Wifi it will not work!)
- On the phone start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
Other important notes:
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
To exit the app
If you are connected with USB, just unplug the USB cable, DO NOT use the exit from the menu. If you are running Wifi, Wifi Direct or Self mode, ALWAYS use the exit button from the left drawer menu!
Audio transport option
Will forward (sink) all the audio from the phone to the tablet if enabled, EXCEPT phone call audio, that will go trough the phone speakers or Bluetooth Handsfree if connected. If you wish to stream all the audio from the phone directly to your A2DP bluetooth, then simply disable the Transport Audio option.
Day/Night toggle
The device running the Headunit Reloaded app will be responsible for changing the theme. You can chose between using the light sensor of the device to toggle between day and night mode, or you can use calculated sunset sunrise mode, or even force it to one theme only. If you have previously installed AA Helper to your phone, please uninstall it!
Auto Start on Wifi
This option will launch HUR whenever you are connected to a Wifi (specific Wifi can be named)
Auto increase volume on speed
The logic behind is a very simple approach, every time the speed increases it will send a vol + key to the phone and every time the speed decrease it will send a vol - to the phone. This requires the device running HUR to have a GPS receiver.
OLD STUFF:
Version 1.3 (Wishlist version) - Released
- Added option for easy car mode toggling. (Car mode can be disabled if not using Self mode - avoid conflict with other Car apps)
- Auto Hide status + action bar while running the app no need to use the Hide option from menu
- App will automatically close when Wifi connection is lost
Version 1.2b - Released
- Buffer overflow protection - Special Thanks to invis-zz from GitHub (https://github.com/invisi-zz) - This should random crashes while using the app.
- Removed Send Log feature (it was classed as backdoor/trojan and Google was blocking the app on playstore)
- Updated OpenSSL library to 1.0.1t (used OpenSSL contained vulnerabilities and Play store blocked the app)
- Managed to get the app on PlayStore (wonder if it will stay...) - https://play.google.com/store/apps/details?id=gb.xxy.hr
Signature Key changed!!!!
I had to update the APK signature key (I'm trying my luck with Play Store), this means if you try to install the new version you won't be able to install it over the old one, so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
Version 1.1 Stable - Released
Jumping the version number due to significant amount of changes:
Removed Day/Night/Auto mode (see bottom of this post for a better solution.)
Added new setting for 720p Video - Fully working now (even on Wifi)
Changed Self mode start sequence (if the phone is rooted it will start automatically and then go back to HU), if your device is not rooted, please use the following sequence to start Self mode:
Start HU app
Select Self mode
When AA opens select Start Developer Server
Added support for hardware keys (simulating touches), so if your tablet is integrated with the car remote you can control AA from the remote.
Hardware keys as follow:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
Some other minor tweaks, to improve stability and make Self mode connect 9 out of 10 times.
Fully integrated x86 native binaries
Declared app as CAR HOME, for those using SelfMode it is crucial, that when you get prompted which should be the default CAR HOME app (Android Auto or HU) you select HU!!! - This is needed to be able to bring back the HU on top after a successful connection is established. AA is trying to override everything..... and to block the user out of his phone as soon as it's connected to the car.
Transport Audio option will affect USB connections as well (You can keep the audio on your phone/bluetooth, when connected with the OTG cable)
Version 1.03b released - Beta
- You will find it in XDA Labs (under the Beta version)
- Fixes Wifi/Self mode for some devices which didn't connect before
- Increased stream buffer size to match the DesktopHeadUnit app (128Kb vs 64Kb)
Version 1.02 release
- Fixed wifi not connecting on some device only after numerous attempts (see explanation below if interested)
The issue looks to be related to the timing, on some occasions and on some devices the phone either sends the SSL data too soon, either too late, either to slow and because the TCP socket is set to non-blocking mode, it can end up in a missed packet in the initial Handshake. I have tweaked this now, so the TCP socket will connect in non-blocking mode, but will switch to blocking mode and wait for full message after a successful connection and once the SSL Handshake is out of the way it will revert back to non-blocking mode, uhhh event reading this makes me dizzy
This however could make the initial startup slightly slower than it was.
- Corrected AutoStart option (Working properly now)
- Fixed USB device overlapping Settings text on the drawer menu
- Added "Send Log" function to be used if there are problems for easier debugging.
Version 1.01 released
- Potential Wifi disconnect fix (see: http://forum.xda-developers.com/showpost.php?p=68078605&postcount=16 for details)
- AutoStart option added to the menu
Very sadly Mike passed away this year and his software stopped working after a Google Update, he left us a slightly outdated GPLv3 version of the software at: https://github.com/mikereidis/headunit which I have used to rebuild (or ty to) rebuild up to his latest build with some additional small modifications as well as fixing the issue caused by Google.
The forked version can be found on: https://github.com/borconi/headunit if anybody is intersted.
Since the app released by him isn't working any longer I have created the new version of it and slightly re-name it just to avoid any confusion.
I take almost no credit in this app, except for some minor changes, and finding the fix for what Google have broke (changed), which was a painful task.
I'm not a developer as such, and this app would never have existed if it wasn't for @mikereidis, however I have spent now several weeks studying the app and understanding how it's working and I plan to continue with the maintenance/development of the app.
I have published the app on XDA Labs under the new name: "Headunit Reloaded Android Auto" and it is now available for purchase. As I have stated previously I'm intending to support all of Mike's customers, so if you have purchased Mike's application before, please email me a proof of purchase to [email protected] and you can have a free copy of the spin-off app.
How to use (Self / Wifi ) ?
1) Self mode.
See instructions in version 1.1
2) Wifi Mode
Start AA on your phone, tap the header 20 times till you become a developer, once that is completed from the menu select Start Head Unit server. Now start tethering on the phone, connect the tablet to the newly created wifi hotspot, start HU on your tablet and select Wifi. This will make the HU app try to connect to the default Android gateway (192.168.43.1), if you need to change this, use the Settings menu from the HU option list. If HU doesn't start on first, do try a few more times, first setup sometimes proves tricky. If this is the first time you connect your phone to the a HU, please make sure you answer all the questions on the phone.
3) Wifi p2p
This is not supported by all devices and might not work for your device, plus sometimes it can be slightly buggy. Start WifiP2p on the tablet from the HU. On the phone go to Wifi Direct (this is usually found in Advanced Wifi settings settings - DON'T TRY TO CONNECT LIKE TO A NORMAL WIFI and look for a new available connection. If you can see one tap to join. Once you joined the network, give it about 30 seconds or so, then open the AA on the phone and start the head unit developer server (same as describe it above). If you're lucky it will work instantly, if not you might need to play around with it.
Other Options:
Possibility to toggle the Audio mirroring when using a Wifi connection. By disabling the Audio mirroring, you will keep all the audio on your phone rather than on the tablet (or on the handsfree) if the phone is connected to the handsfree. This will improve the performance greatly, since audio will use up a significant quantity of Wifi bandwidth when communicating between the 2 device.
USB OTG connection.
Have remained unchanged and it will work same way it did till now, see original threader for details.
I will monitor both Threads and will do my best to help and support everybody.
Well done! Thanks so much for your hard work Emil.
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Syphe said:
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Click to expand...
Click to collapse
What version of Android is your unit running? I haven't heard of any with less than lollipop being able to run this so far, h.264 decoding is absent or poorly implemented.
Edit....see the bottom of this post
http://forum.xda-developers.com/showpost.php?p=68010519&postcount=1449
Wifi Mode - Starting with HUR 7.X
Braking changes with version 7.X
Only for phones running Android 9 or higher, if you still use Android 8 phone, you won't be able to connect over WiFi. Device running HUR, can have any version of Android.
Phone Setup:
Install Wifi Launcher for HUR on the phone ( https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur&hl=en_US )
Make sure you give the app all the permissions, including draw over other apps, otherwise it cannot start Android Auto from the background!
Open the app and select the car's BT adaptor from the list (make sure phone is NOT connected to the car's BT, but BT is enabled!)
If you want your phone to create the hotspot, turn on the option to Enable hotspot (this will probably not work if you are on Version in the USA due to carrier limitations!), likewise if you want your car to create the hotspot or you want to use an incar wifi module, leave this option turned off.
Only turn on the legacy option if HUR specifically instruct you so.
Car/Headunit setup:
Connect to the phones hotspot or if you are using an incar WiFi connect to that network. Alternatively if you want HUR to create the hotspot and connect your phone to it, enable the option in HUR settings.
Open HUR
As soon as the 2 devices are on the same network, HUR will fire up on your car screen.
Emil Borconi said:
Hi Syphe.
The core of the app is the same as the original, and the app does require a hardware H264 decoding supported by the OS. Till now we are not aware of any chinese HU which support this. Please contact me by email and I'll refund your purchase.
Click to expand...
Click to collapse
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Christopher Price said:
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Click to expand...
Click to collapse
Yeah I thought about that myself.... will probably create a small check app in the near future (just need to catch up with all my other work now, which has been pushed behind to get this done)
bugger, thought it was quite promising when everything started to connect itself
I've been building my own app to do simple notification mirroring over a wifi tether, but this would have been much easier haha.
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
kevster0522 said:
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
Click to expand...
Click to collapse
Hi.
Yeah the XDA labs app can sometimes play funny, if your having any kind of issues feel free to contact me directly be email, on [email protected]
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
fmark said:
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
Click to expand...
Click to collapse
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Emil Borconi said:
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Click to expand...
Click to collapse
Yes, my phone has 4G connection while tethering.
Lets try the debug output. Could you please send me the .apk with debug messaging? I'm curious to see what is going on when it fails to connect.
Thank you!
Im interested too because isnt working on my s4 and nexus7 2012
wpostma said:
Im interested too because isnt working on my s4 and nexus7 2012
Click to expand...
Click to collapse
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Christopher Price said:
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Click to expand...
Click to collapse
It might be about the Wifi connection, I had some connectivity issues over Wifi myself the last day, but they were fully random, at a first look they point to the TCP socket.... I'm investigating this.
I got some Wifi disconnected myself but it is very random, it can occur after 1-2 minutes or after 3-4 hours... so testing potential FIX for the issue isn't going to be easily. At the first investigation it looks to be something related with the pooling/keeping connection alive. I have tweaked this and made a new build, currently running for about 20 mins and looks OK, but as said the disconnect can occur randomly at any point.
The worst part is that the logs do not give any hint on what could be the cause of this, neither on the HU part, neither on the AA side, they only mention a broken PIPE bu no hint on what can be the cause...
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Christopher Price said:
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Click to expand...
Click to collapse
setting socket to keppalive looks to sort the problem, I'm trying to figure out failing handshake at the moment. On TCP sometimes the handshake fails, trying a few more times passes..., handshake over usb always passes....
Looking at the code and notes Mike seems to struggle with it as well in the past...
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
skitty said:
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
Click to expand...
Click to collapse
Emil Helped me with this problem. You don't actually connect through your wifi networks menu, use Wi-Fi Direct instead. Found here: wifi networks menu > 3-dot menu > Advanced > Wi-Fi Direct
Google Pushes Android Wear 2.0 Back To 2017, Issues Third Developer Beta
Google announced Android Wear 2.0 alongside what later became Android Nougat at Google I/O a few months ago, but aside from a second Wear 2.0 developer preview build in July, we haven't heard much since. There's good and bad news on that front: the good news is that Google is releasing a third Wear 2.0 developer preview today with some new features and tweaks. The bad news is that the final release of the software is being delayed.
Wear 2.0's release date has been pushed back from a vague "this fall" window to an equally vague "early 2017" window, presumably so Google can keep testing and tweaking. To that end, Google will release a fourth developer preview build, and the 2.0 update will begin trickling out to supported watches after that.
The biggest addition to the Android Wear Developer Preview 4 is a watch version of the Google Play store that can browse and download watch apps and watch faces without your phone—developers told Google that they wanted watch apps to be easier to find, and this is Google's answer. Text entry still looks painful, and relatively wimpy watch hardware may slow things down, but if the eventual goal is to make watches that can operate independently of phones, this is an important step.
The watch-exclusive store also means that developers can release watch apps that are totally independent of phone apps. Historically, Wear apps have been bundled in standard phone apps—download a phone app, and then the wearable app would be downloaded to the watch from the phone. Apps can still be downloaded and installed this way, but as of Wear 2.0 it will no longer be strictly necessary.
Other tweaks in the new preview build include permission requests for watch complications, a "recycler view" that lets developers display vertical lists of items in a way that will look good on square and round watch faces (the Wear 2.0 app picker uses the same view), and inline actions for new notifications (you would previously need to swipe down on a notification to expose a quick action menu).
Whether your new watch will receive Wear 2.0 is going to be up to its manufacturer, at least in part. The LGE Watch Urbane 2nd Edition and Huawei Watch are safe bets since they're still the only devices you can use to test these preview builds, but we already know that early Wear watches like the LG G Watch and first-generation Moto 360 will be missing out.
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
kalinskym said:
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
Click to expand...
Click to collapse
What does that really have to do with this article?
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
For windows users: see the post below (Thanks for the tool!).
Otherwise:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder that is referenced in "META-INF/MANIFEST.MF" (search for the string 'apk') in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Diewi said:
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder "res/raw" in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Click to expand...
Click to collapse
for installing apps, you can use this
http://forum.xda-developers.com/huawei-watch/general/android-wear-2-0-apk-installer-t3472766
My project is to use an RPI4b running KonstaKANG ROM in my car as an dedicated AA device. My car have a nice dashboard but there is absolutely no guidance service. The primary goal would be to use an offline map service. I have tested AA and CarPlay with standard cellular over USB and they work.
My first tentative where done with AOSP13-20230130-KonstaKANG-rpi4.zip (not sure about the 6.1 kernel) and lineage-18.1-20220512-UNOFFICIAL-KonstaKANG-rpi4. While they worked well on the device with a keyboard/mouse/hdmi, I later realize my USB OTG cable was in fact just a charging cable. So of course results where negative.
My second attempt, using better cable, was a bit more interesting. But I was feeding only 2.1a to the OTG USB, so the RPI4b felt a bit sluggish because of underpowered I guess, I have some of those cables on order to give required power to the RPI4b but in the meantime I will just need to be patient. I tested using build lineage-19.1-20230313-UNOFFICIAL-KonstaKANG-rpi4.zip. I wanted to use flamegaps but it would say that "version 12 is not compatible with 12.0" so I did try mindTheGapps and NikGapps, both seem to had the same result. I used AA 8.9.630603 with and without the XLauncherUnlocked v2.0.1. My result where at some point I got error 22, which bring me to try this xda-guide. I installed logcat I was able to snap this from the log :
---
W InputDispatcher :
ActivityRecordInputSink comdp.logcatapp/.activities.FiltersActivity will not receive the gesture at 2051644...
I InputDispatcher
Droping event because there is no touchable window or gesture monitor at (90,99) in display 0.
---
I know it's not as useful as full log, but for now it's all I could salvage from this tentative and it's a information so I note it.
I intend to do a third test this week-end with this version AOSP13-20230412-KonstaKANG-rpi4. Hopefully I will have full log to report back.
Aside from XLauncherUnlocked, I want to also try this AA AIO Tweaker that seem quite interesting. It's option to enable widescreen remind me that I had some consideration about if dashboard and AA would not want to connect because running an RPI4b simulate an 1920x1080 screen that would be incompatible to a car dashboard ?
I'm sorry if that post seem a bit picked up for now but I hope the situation will clarify over time as I wont write from memory, wandering files and jolted notes.
- Should I use v8a or v7a when I download a build of AA from APKMirror ? I found recently that Magisk state I have v8a, is it trustable information ? Maybe it invalidate all my test done with v7a. But from what I read about it, I dont think it make much a difference, but could be someone know better ?
- What would be my best option to run AA and see logs ? Since I'm in a car maybe I can bring here a laptop to do ADB over USB would be faster than setting up Wi-Fi ADB ? I think at this point, collecting logs is the most important part of my investigation. But I'm not so sure how to do it efficiently. I would be thinking than to do something like that and collect the log while I try to connect AA to the dashboard would be the way to go.
Cheers
I could test the new configuration this week-end. Unfortunately I did not had much luck but now I have debug log and precise description of what I did. One thing I noted is that AOSP13 was very fast, so the sluggishness was not from the RPI4b lacking power it seems. I could debug with logcat using Android Studio via Wifi, it was awesome to see all this working. Here is the configuration I used :
aosp 13 : AOSP13-20230412-KonstaKANG-rpi4
mindthegapps : MindTheGapps-13.0.0-arm64-20230408_162909.zip
magisk : 25.2
busybox : com.jrummy.busybox.installer_6.8.2
systemizer : app_systemizer-v18.
androidAuto : 8.9.630604-release-89630604_minAPI26(arm64-v8a)(nodpi)
I think systemizer might not be necessary as the AA seem to be already system installed as there was no uninstall option in app info. I could copy the log as systemizer.log attached..
Reading the log it appear obvious to me that it's related to that error you keep on seeing whatever test I do. It would appear twice in the log as soon as I click on the "pair a car" in AA.
Checkbox request failed
jwu: 17: API: UsageReporting.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
it seem this error to appear all the time, but I pursued the test and attached other logs. You can see the full log with the file logcat_aa8.9_1.txt.
+ add AA-AIO-TWEAKER-5.2.2-hotfix-release :
I disabled tab limitation, bt autoconnect, telemetry. The log error was similar so I saved nothing. But this thing seem very hot and I will certainly use it if I ever make it.
+add enabled zygisk, lsposed 1.8.6. shamiko 0.6, AA XLauncher 2.0.1 (w/ kinginstaller), enabled AAXLU in LSPosed :
shamiko 0.7 cannot install because magisk need to be 2.6, but shamiko 0.6 seem to work with magisk 2.5. I did try different way to launch AA using XLauncher but each time the same checkbox related error message in logcat_aa8.9_2.txt.zip.
~replace with NikGapps-basic-arm64-13-20230418-signed
Since it seem related to some API I did try to change the GApps but I'm not sure I can just bump mindthegapps with nikgapps, but I did try. The swap seemed to work but after that I could not log with Android Studio anymore for some reason so I used ADB shell to save logcat, maybe something else can be seen using it logcat_aa8.9_3.txt.zip.
~upgrade to AA projection.gearhead_9.3.631404-release-93631404_minAPI26(arm64-v8a)(nodpi) :
As a last resort, I did try to upgrade to AA 9.3, but the error about missing UsageReporting.API support was again here logcat_aa9.3_1.txt.zip.
I guess now I need to research about that API and understand why it missing... I'm thinking maybe it's because I did not registered google play service with my account to avoid it upgrading AA automatically. I'll check this out and get back later.
Cheers,
I was able to fix the UsageReporting.API is not available on this device. by registering the device with playprotect. Then I systemized gearhead, installed latest version that also work on a cellphone (9.3.631434), put AA in debug verbose mode and I get back with the error log about a leaked windows and dropping event because there is no touchable window at (x,y). I'm using a mouse/keyboard and hdmi display when I try to connect AA with the car, so maybe this is not considered as a touchable windows for AA ? Maybe there is touchable windows emulator I could use ?
At this point I start to get out of idea and it seem I get back to my initial point. Has anybody was able to use an raspberry pi as an AA client device ? I think my next step would be try that aa4mg thing, but I'm not so sure what is microG and if those KonstaKANG rom are compatible with it ... oh well, I guess there is only one way to know it.
Reading about aa4mg lead me to omnirom which seem interesting and look awesome on an rpi4b. I did try the omni-13-202303081341-rpi4-MICROG. Unfortunately I could not quickly install magisk to install aa4mg (there is that tutorial I could try) so I proceed a parallel task to try a fresh version of :
rom :
= lineage-19.1-20230313-UNOFFICIAL-KonstaKANG-rpi4.
install :
+ Magisk 25.2
+ f-droid
+ microG Service Core (via fdroid)
+ aa4mg (via magisk) (! should have volume ctrl here, but default seem fines)
+ aurora store (via fdroid) - AA is not there anymore
+ busybox (aurora)
+ app-systemize (via magisk)
+ kinginstaller
+ android auto 9.3.631434 (via kinginstaller, not rooted)
do :
> systemize : com.google.android.projection.gearhead
> give all permission to AA
> default USB mode : file transfer or USB tether
at this point I get the error "android auto wont run without google play services which are not supported by your device" but what is interesting is that AA seem to run on startup as it would detect the car is plugged. I've yet to receive those power-usb-otg cable so for now I can only say that since AA run on startup of a boot from lineageos if the RPI4b is plugged in the car dashboard.
So what's next ? I will maybe try 8.3 version of AA as I read about the error message of google play services could be fixed using prior version of software, but also review microG Service Core setup as I though this was supposed to replace the play services. Apparently my GmsCore has not the correct signature, so maybe there is the problem since I read it allow GmsCore to pretend to be GooglePlayService. Probably that Konsta KANG LineageOS for RPI4b need extra step to support signature spoofing. So I think I will leave it there for tonight, time goes so fast when you are busy ! According to that wiki, next item on my list of install is Xposed and also lsposed which I already installed in the past https://github.com/microg/GmsCore/wiki/Signature-Spoofing
I could not find procedure to do signature spoofing using zygisk so I did try the riru way :
install :
+ riru-v26.1.7.r530.ab3086ec9f-release
+ LSPosed-v1.8.6-6712-riru-release
+ fake_GApps_4.2_app-release
_> FakeGapps : System Framework (default recommended), added FakeStore 0.0.2, added microG Services Cores 0.2.27.223616
_> AAXLU enable module : Android Auto (default recommended), added System Framework, added FakeStore 0.0.2, added microG Services Cores 0.2.27.223616
I though I had stuff to setup to activate signature spoofing, but apparently a reboot and AndroidAuto would not complain anymore about missing Google Play Service ! Quickly Android, to the Carmobile ! I can honestly say my heart skipped a beat when I saw AndroidAuto authorization start on the car dashboard and car pairing tutorial on the Raspberry Pi 4b . Another good news was also awaiting me there, as I received those USB-USB-C_OTG_Power cable ordered in my first post, and they would work. So I could provide required amp/voltage to the RPI from auxiliary power outlet while using another port for usb data.
The pairing process on LineageOS's AA could not finish as some of the prerequisites apps where not installed, Here is what is missing :
(present) : Android Auto
(missing) : Google App
(missing) : Google Maps
(missing) : Google Text-To-Speech
I also noted you could not start AA from AAXLU in either material3 or stock mode. I will check this out after I will be able to successfully finish the car pairing wizard.
Before I proceed further I will take a clone backup of the microsd and take a break as there is just so much emotion a man can sustain. Of course I dont think I will wait long before install prerequisites and pursue investigation.
I was able to fix prerequisite this way:
+ install GSF from f-droid's microG repo.
~ fix background location servce permission thanks to ploink here.
~+ check permission : dumpsys package com.google.android.gms | grep granted=false
~+ add permission via adb shell su : pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION
+ aurora store : google 14.17.24.28 arm64 (301236347)
+ aurora store : google maps (11.77.0300)
+ aurora store : speech service by Google (require GSF)
So the wizard would finish but keeping reporting that Maps "Permission needed, google maps in android auto needs a certain permission to work effectively. Review this permission in Settings : Location Allows Maps to determine your device's location" even if it is set. Google App would ask me to logon but complain that the account already exist on the phone. For now I'll just skip that. As I more important problems, the developper settings would crash if I try to acces them, the screen would randomly freeze or display garbage when connection the usb.
I will review those error but what I think I will try next is to see if AndroiAuto AIO can provide any insight on the problem. Try to rollback to AA 8.9. See what debug log tell about the problem.
Since I was getting some GMSCore permission problems on LineageOS I thought I would give OmniRom since there is a rom for Rpi4b !
omnirom : omni-13-202303081341-rpi4-MICROG
Note, install nikgapp AA at the very beggining as it will otherwise wipe data and many thing will need to be redone.
Here is what I installed :
+ magisk 2.6.1 (enable zygisk) patching with mkbootimg + unpackbootimg. Instruction from rsaxvc.net.
+ aa4mg-v0.6.1.zip (magisk) : (follow install instruction on github + disable wireless screen)
+ LSPosed-v1.8.6-6712-zygisk (magisk)
+ shamiko-v0.7.1-166 (magisk)
+ android auto (modded to remove nikgapps prerequisites), forum.xda-dev thread
+ google app (aurota store or apkmirror)
+ google tts (aurota store or apkmirror)
+ google map (aurota store or apkmirror)
tested to downgrade google map 10.87.4 using : pm install -i "com.android.vending" <apk>
With this procedure it's the farthest I went so far, although it was not working. Each time I would plug the RPI on the car I would need to redo the pairing wizard, with the green error message that Google Maps need location permission (I think I gave everything I could think of). After that, on the RPI it ask to finish the wizard on the car dashboard which is showing an empty screen. I think I will try with OmniRom Android 12 or lower version I could find, of course if anybody has idea for me I would be more than happy to hear about it.
I installed omnirom 12 for rpi in a similar way as my previous post and results are the same. AA say to continue setup on car screen which is displaying an empty screen. I'm not so sure what to test anymore and start to think it just wont work. I collected a log of when I plug the cable on the car to when I finish the wizard, maybe someone will see something ?