Database Develop

[WIP] Portable OUYA console (Shield Mod)

Concept- Import as much of the OUYA frameworks and applications as possible to make the experience as similar to a portable OUYA console as possible. This will ideally include direct access to the OUYA store for app download and in app purchase though official means of downloading OUYA software.
Endstate- A full custom rom because it's not as simple as installing an app (it's supposed to be, but it isn't) and to get full functionality a bit of system level changes are going to be needed (keymapping/framework). My goal with this is to make this a portable package to be installed via recovery so anyone that wants to add it to their own rom without developer support will be able to do so. If successful on shield, then other phones/tablets should be able to benefit from this as well with additional custom mappings for PS3/XBOX360/MOGA/OUYA controllers
--------------------------
-What fully works-
OUYA live wallpaper
OUYA Button mapping (custom mapped only, need to create 2nd functions so shield can keep it's current mapping function in tegra/android games and streaming)
-What partially works-
OUYA OOBE (initial console setup application, can connect wifi, but can't create a new account)
OUYA games start up and are playable when side loaded (need to fix ouya framework for complete compatibility, non-functional framework)
OUYA framework (use NDK 1.0.2 or prior)
OUYA launcher (use NDK 1.0.2 or prior)
-What doesn't work-
OUYA Store (can't access OUYA store or login with OUYA account)
-Haven't tried yet-
OUYA browser
OUYA onscreen keyboard
OUYA boot animation
HDMI/MIRCAST output
BLUETOOTH OUYA controller
others?
-----------------------------
Lessons Learned-
OUYA ODK offered official support for non-native hardware, but is now broken (has been broken since 1.0.2 OUYA acknowledges but hasn't fixed) discussion
http://forums.ouya.tv/discussion/1782/odk-1-0-6-included-ouya-launcher-apk-crash-nexus-7
Latest ODK & setup
https://devs.ouya.tv/developers/odk
https://devs.ouya.tv/developers/docs/setup
Last known ODK to work with non-OUYA hardware
https://devs-ouya-tv-prod.s3.amazonaws.com/odk/odk-1.0.2.zip
OUYA button mapping is slightly different than shield ABXY (uses BUTTON_O BUTTON_U BUTTON_Y BUTTON_A) see below under "constants"
https://devs.ouya.tv/developers/docs/controllers
OUYA launcher is a home launcher activity, will give option to replace default launcher like any other home launcher replacement when home button is pressed.
OUYA framework will permanently break the nvidia/power button bringing up the shield game/store/stream interface. Must be launched as app from that point forward.
OUYA framework will permanently break the shield's android browser (chrome is fine)
Alternate OUYA webstore android app confirmed working (if we can't get officially sanctioned one to work)
http://forum.xda-developers.com/showthread.php?t=2385950
OUYA stock based rom I have been working off of/importing from
http://forum.xda-developers.com/showthread.php?t=2347214
OUYA launcher is expecting 1080p output for launcher and cuts off about 20% off the bottom of screen

Sounds interesting. If it works, well, ends the old OUYA vs Shield threads argument once and for all (although thankfully that thread seems to be long dead). Only thing the OUYA would win on would be cost.
How would you handle the extra touchpad on the ouya controller? just use the screen? not sure if that would work without some heavier mods, the ouya touchpad is exposed as a bluetooth mouse, hell, it apparently works on windows sometimes.

SixSixSevenSeven said:
Sounds interesting. If it works, well, ends the old OUYA vs Shield threads argument once and for all (although thankfully that thread seems to be long dead). Only thing the OUYA would win on would be cost.
How would you handle the extra touchpad on the ouya controller? just use the screen? not sure if that would work without some heavier mods, the ouya touchpad is exposed as a bluetooth mouse, hell, it apparently works on windows sometimes.
Click to expand...
Click to collapse
haven't gotten that far yet, but I imagine the apps that use the the mouse also respond to touchscreen events as that's what it's simulating, might need to turn analog mouse on/off, but who knows. Cross that bridge when we get to it.

Hi,
I have been working on this too but seams the OP is further along then i am. I have got games launching and have found an earlier ODK version with working launcher (Screenshots attached below running on my Tegra 3 Sony Xperia Tablet S and my Xperia Z)
Here are the v1.5 apks if will help - http://www22.zippyshare.com/v/58968936/file.html
I can launch, select menus and boot into / play ouya games but i have still not found away to sign in and download games straight from the store or even sign in to enable games like Final Fantasy to run.
Any help or updates on the progress made by the thread OP will be helpful.
Thanks

Excellent, you found a piece I've been looking for, (zero response from the ouya dev community, my very specific request for any legacy mirror remains unanswered)
I will have a go at it this weekend.
I'm under the assumption your sign in data is generated and stored after successfully going through the OOBE app and creating/singing in a ouya account, that data gets handed to the launcher/store. This is of course is/was an untestable assumption until we had a working framework.

This is pretty awesome to see, thanks to both of you for your efforts.

This is really cool. Wish I could buy some of the games.
Seeing the Ouya startup screen on my Shield was awesome though.

This would be a great rom for dual boot on the shield to switch back and forth.

Found links to AWS hosting for previous ODK versions such as 0.0.6 and 1.0.2, unfortunately my super lurk status prevents me from posting here. I'll PM the links.

Furyus said:
Found links to AWS hosting for previous ODK versions such as 0.0.6 and 1.0.2, unfortunately my super lurk status prevents me from posting here. I'll PM the links.
Click to expand...
Click to collapse
Nice find thanks a lot
With the 1.2 version I can actually begin to register/Sign in with an Ouya account without force close. Only issue now is that Ouya servers won't respond to logins. Time to look for a way round this and fool the Ouya servers into thinking we are running this on a Ouya console.
{
"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"
}
You can add the Ouya account to the main list in your device settings too. This has issues with auto login as apparently "Sign in issue - could not get registry token for console"
Sent from my C6603 using Tapatalk 2

It's disappointing. I would certainly buy a few OUYA games without any expectation of support, etc.

poo-tang said:
Hi,
I have been working on this too but seams the OP is further along then i am. I have got games launching and have found an earlier ODK version with working launcher (Screenshots attached below running on my Tegra 3 Sony Xperia Tablet S and my Xperia Z)
Here are the v1.5 apks if will help - http://www22.zippyshare.com/v/58968936/file.html
I can launch, select menus and boot into / play ouya games but i have still not found away to sign in and download games straight from the store or even sign in to enable games like Final Fantasy to run.
Any help or updates on the progress made by the thread OP will be helpful.
Thanks
Click to expand...
Click to collapse
When you say you've been able to launch/play games, what games were you able to play? I tried the demo to Chronoblade and was able
load to the start screen (regardless of the launcher) but no buttons are detected after that. Buttons worked fine in Ouya launcher, though.

cp_kirkley said:
When you say you've been able to launch/play games, what games were you able to play? I tried the demo to Chronoblade and was able
load to the start screen (regardless of the launcher) but no buttons are detected after that. Buttons worked fine in Ouya launcher, though.
Click to expand...
Click to collapse
Well the only Ouya exclusive game that worked/have tried with my HID (Xbox) controller was Super Crate Box so far. The other games that worked are games which also have copys on Google Play (these have both HID and Ouya programmed).
I myself have not found away yet to change the native button mappings to the Ouya coded Button_O/Button_U/Button_Y/Button_A as simple remapping apps like gamekeyboard don't seam to support these key codes.
I would like to see how the OP managed to remap these? as far as I can tell the native Google virtual keyboard code does not contain these key codes to be remapped too.
Sent from my C6603 using Tapatalk 2

poo-tang said:
Well the only Ouya exclusive game that worked/have tried with my HID (Xbox) controller was Super Crate Box so far. The other games that worked are games which also have copys on Google Play (these have both HID and Ouya programmed).
I myself have not found away yet to change the native button mappings to the Ouya coded Button_O/Button_U/Button_Y/Button_A as simple remapping apps like gamekeyboard don't seam to support these key codes.
I would like to see how the OP managed to remap these? as far as I can tell the native Google virtual keyboard code does not contain these key codes to be remapped too.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
OUYA controller is apparently just a regular bluetooth HID under the hood. Windows even recognises it. The touch region in the middle is a bluetooth mouse,

SixSixSevenSeven said:
OUYA controller is apparently just a regular bluetooth HID under the hood. Windows even recognises it. The touch region in the middle is a bluetooth mouse,
Click to expand...
Click to collapse
Does this mean the controls can be spoofed by a program like tincore? If no one gets to it before I do, I'll take a look tonight. From my understanding, TKM already supports the ouya controller layout.

cp_kirkley said:
When you say you've been able to launch/play games, what games were you able to play? I tried the demo to Chronoblade and was able
load to the start screen (regardless of the launcher) but no buttons are detected after that. Buttons worked fine in Ouya launcher, though.
Click to expand...
Click to collapse
Chronoblade is somewhat unique compared to other OUYA games as it's the only one i've found that flat out REQUIRES an OUYA controller to control it. I messed around with it a bit when it first launched a few months ago and the problem is deeper than remapping the hard keys. Pretty much any other OUYA game will work with a (properly mapped)controller for the most part.
What might be a better solution for this would be to design a custom made launcher(not a mod of the OUYA one) that incorporates the download schema these guys use - OUYAlytics.com , and an Xposed style mod of the OUYA framework.

poo-tang said:
Well the only Ouya exclusive game that worked/have tried with my HID (Xbox) controller was Super Crate Box so far. The other games that worked are games which also have copys on Google Play (these have both HID and Ouya programmed).
I myself have not found away yet to change the native button mappings to the Ouya coded Button_O/Button_U/Button_Y/Button_A as simple remapping apps like gamekeyboard don't seam to support these key codes.
I would like to see how the OP managed to remap these? as far as I can tell the native Google virtual keyboard code does not contain these key codes to be remapped too.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
you can manually change the keycode name, it requires root access. I haven't messed with it beyond my own proof of concept. I wanted to make secondary functions for the shield's keycodes as if released in it's current state would break the controller working with most shield software.
here's relevent information if you want to make the changes yourself before I solve the secondary function problem. It may need redoing some kcm files which aren't as easily modified.
http://source.android.com/devices/tech/input/key-layout-files.html

johnsongrantr said:
you can manually change the keycode name, it requires root access. I haven't messed with it beyond my own proof of concept. I wanted to make secondary functions for the shield's keycodes as if released in it's current state would break the controller working with most shield software.
here's relevent information if you want to make the changes yourself before I solve the secondary function problem. It may need redoing some kcm files which aren't as easily modified.
http://source.android.com/devices/tech/input/key-layout-files.html
Click to expand...
Click to collapse
It's also possible that the game is looking directly at the scan codes, which would require a hack in the input service to remap, but is definitely doable. Not sure how one would make it "toggleable", though.

I am willing to help as much as I can with this. I think if this can eventually progress into a "Dual-Boot" type thing I would DEFINITELY incorporate it into my Toolkit! Let me know when you need someone to test or need some feedback

If anyone needs me to test anything or wants logcats I have a rooted OUYA on hand and can make an OUYA account for testing if need be.

[APP] ACUI: New Car Frontend for Android

Hi,
We worked on this project for months and since we're almost ready (very few days left) to launch the first beta on the PlayStore I think that it's time to share some info around the web and not only on our community.
ACUI is a set of four apps: ACUI Key&Touch, ACUI Touch (and ACUI Touch with material) and ACUI Base (which include three different themes), designed to best improve your Android experience in your car.
GOOGLE PLAYSTORE LINK
Finally we have a little teaser for ACUI A2DP feature.
Please remember that in order to listen the audio you will need of a little piece of hardware we will release later this year (a preorder sale will be open soon).
Click to expand...
Click to collapse
Together with these UI app we will release also two very simple and easy apps that will allow you to share your GPS connection from your phone to another android device.
But ACUI is not just software. We will open a preorder sale on IndieGoGo for a couple of piece of hardware we're working on:
- a bluetooth HID controller for standard 4-Wire resistive touchscreen (price around 80$)
- a custom controller (price around 50$)
Every single $ for both the IndieGoGo campaign and the PlayStore sales will be used to produce and keep as low as possible the price of these two product, as we previously said on our Google+ Community we really want to provide you the best experience for the lowest price.
Here's the links to our site and to our Google+ Community
http://www.acuiautomotive.com
http://plus.google.com/communities/112087817837785037612
We have a list for people who are interested in a full list of feature available now for the first release of ACUI. Note that our A2DP feature will be available as soon as possible (the base code is almost ready).
- Full AppDrawer
- Six shortcut for third party app in the main screen (this feature is not available in ACUI Key&Touch)
- Send eMail
- Send SMS
- Read Inbox SMS
- Read Sent SMS
- Make a Call
- Check last outgoing call
- Check last received call
- Check last missed call
- Internet browser (will open an external app**)
- Music player
- Control and get info from GooglePlayMusic
- Play Video (will open an external app**)
- Image Gallery (will open an external app**)
- Navigation (will open an external app)
- Sygic, Waze, GoogleMaps, TomTom integration
- 5 Day weather info
- Lap timer
- 0-100Km/h (0-60MPH)
- Toggle Bluetooth
- Get list of paired devices (In the future releases you will be able to search for new devices, connect to device, disconnect to device and everything you are able to do with the standard bluetooth settings)
- Toggle Wi-Fi
- Open Android Wi-Fi Settings
- Backlight Settings (Max, Min, -/+)
** This feature will open an external app but we will develop and internal solution in the future releases
Click to expand...
Click to collapse

I see the video...it is amazing...can't wait to use it on my S150 Android 2 DIN car Head Unit replacing the orrible chinese UI!!!!

royalhawk2002 said:
I see the video...it is amazing...can't wait to use it on my S150 Android 2 DIN car Head Unit replacing the orrible chinese UI!!!!
Click to expand...
Click to collapse
The app has been uploaded on the playstore I will post as soon as everything will be available.
ITA:
Le app sono state caricate sul playstore, posterò qua appena saranno disponibili per il download.

Neverbe said:
The app has been uploaded on the playstore I will post as soon as everything will be available.
ITA:
Le app sono state caricate sul playstore, posterò qua appena saranno disponibili per il download.
Click to expand...
Click to collapse
I see the Apps on the Market, but it seem are not compatible with my S150 Android 4.03 Headunit....:crying:

royalhawk2002 said:
I see the Apps on the Market, but it seem are not compatible with my S150 Android 4.03 Headunit....:crying:
Click to expand...
Click to collapse
We're solving the problem.
Please check out our Google+ Community for "live" update.

ACUI is now available on the PlayStore!!!
https://play.google.com/store/search?q=ACUI&c=apps&price=2

Neverbe said:
We're solving the problem.
Please check out our Google+ Community for "live" update.
Click to expand...
Click to collapse
Hello, any chance to install it on S150?? it is still incompatible on Playstore. And what version should i download? normal one or tablet one?

junior2001 said:
Hello, any chance to install it on S150?? it is still incompatible on Playstore. And what version should i download? normal one or tablet one?
Click to expand...
Click to collapse
Same issue for me.....

For non-phone devices the Tablet version will be fit your needs.
I tested it on a Samsung Galaxy Trend which have a 1Ghz SingleCore CPU and 512Mb of RAM so it should also work on the S150.

Will it work on the S150 Android 2.3 version?

screamhouse said:
Will it work on the S150 Android 2.3 version?
Click to expand...
Click to collapse
I'm so sorry but ACUi will only work on 4.0.3+.

Sorry, double post.

Just a little news.
We have almost done with the development of both ACUI A2DP feature (which will be available for every version of ACUI) and ACUI A2DP hardware. You will be able to read sms, make calls, answer call, send sms and a lot more!

hi, i purchase the app, i have a car android 4.0.3 S150 but not install in google play, system not compatible message. any idea?

The A2DP code is ready and working like a charm. We will record a video really soon.
The first proto of our bluetooth adapter is ready too. There was some noise but we managed to reduce it at 90%, I think that we will manage to completely reduce it. To use this module you will only need of just one aux input in your car. The module will be connected to the aux input. The tablet with ACUI will be connected to the module via AUX cable and the phone will be connected to both the bluetooth module and to the tablet with ACUI installed. The module will also allow you to have one extra AUX input in this way you won't have to unplug the module everytime you want to plug another MP3 player or whatever you want.
After that you WON'T need to touch your phone anymore. You will be able to answer/reject a call, access out/in/missed calls, send and read SMS (using both android keyboard and your voice), access to phone contact list, create a new contact and listen to the music stored in the phone.
New feature will be added in the future.
Please note that this feature will be absolutely FREE if you have ACUI Key&Touch, ACUI Material or ACUI Touch.
screamhouse said:
Will it work on the S150 Android 2.3 version?
Click to expand...
Click to collapse
Sorry but it will only work on 4.0.3+ devices

Theres really no app out there that At least I found could replace HTC Car and it seems you guys have done it! Kudos to you, whe this comes out I think I will definitely be down to buy it.

We have just finished with YouTube, MxPlayer and PowerAmp integration we really hope to upload a new update asap.
.Ryker said:
Theres really no app out there that At least I found could replace HTC Car and it seems you guys have done it! Kudos to you, whe this comes out I think I will definitely be down to buy it.
Click to expand...
Click to collapse
Glad you like what we're doing

Here's ACUI's PowerAmp integration
{
"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"
}
This is what will be shipped with the next version of ACUI Key&Touch
Dacia, Renault car logos
MXPlayer integration
YouTube integration
PowerAmp integration

A new version of ACUI Key&Touch is now available in the store. This new version will feature:
Dacia, Renault car logos
MXPlayer integration
YouTube integration
PowerAmp integration

Hi Guys!
We've great news for you.
As we previously said we're preparing ACUI Key&Touch to work with hardware buttons but we also:
- Deeply changed the way MeteoInfo are gathered by ACUI. We made the code far lighter but we also add a couple of feature like home city, destination city meteo and meteo update when GPS location change.
- Improved YouTube integration (recording a video now)

ROM for Android Auto

Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?

AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
Last I checked a few months ago no, at least among popular Android 5.1 ROMs, which I think are mostly derived from CM.
I've never checked some Ancient 5.0 ROMs though, and 5.0 is the minimum for AA.
Basically, the H.264 video encoder does not work, and the CM dev did not expect that to ever be fixed or even fixable.
Same for GT-N7100, GS2/Note1 and even GT-I9000.

Android Auto working on i9300 custom ROM
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
FFmpegExtractor: suppoted codec(h264) by official Stagefright
Click to expand...
Click to collapse
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
01-16 13:38:10.575 15461 15461 I FsmController: fireEvent(EVENT_VANAGON_MODE_STARTED)
01-16 13:38:10.595 15461 15461 D FsmController: State stack (size=1)
01-16 13:38:10.595 15461 15461 D FsmController: 0: com.google.android.projection.gearhead.frx.SetupFsm$VanagonCapabilityCheckState
01-16 13:38:10.625 15461 15496 W CAR.SERVICE: Not supported: total mem 867790848 is lower than minimum 891289600
01-16 13:38:10.625 15461 15496 I CAR.SERVICE: check device capability result false iframe interval -
Click to expand...
Click to collapse
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=62464
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=15360
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC3=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_SECURE=50176
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_NORMAL=4096
CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TVOUT=0
CONFIG_VIDEO_EXYNOS=y
CONFIG_VIDEO_EXYNOS_MEMSIZE_FIMC_IS=12080
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE0=10240
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE1=10240
# CONFIG_VIDEO_EXYNOS_MIPI_CSIS is not set
# CONFIG_VIDEO_EXYNOS_TV is not set
# CONFIG_VIDEO_EXYNOS_ROTATOR is not set
CONFIG_VIDEO_EXYNOS_FIMC_IS=y
# CONFIG_VIDEO_EXYNOS_FIMC_IS_BAYER is not set
CONFIG_MEDIA_EXYNOS=y
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_TESTDEV is not set
#
# Graphics support
#
# CONFIG_DRM is not set
CONFIG_ION=y
CONFIG_ION_EXYNOS=y
CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE=71680
# CONFIG_ION_EXYNOS_CONTIGHEAP_DEBUG is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
Click to expand...
Click to collapse
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
{
"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"
}
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133

RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.

RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Could you make this release available? Tks.
---------- Post added at 06:52 PM ---------- Previous post was at 06:47 PM ----------
avidsukhoi said:
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.
Click to expand...
Click to collapse
Did you get any version that supports Android Auto for Galaxy S3?

AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.

JRFabbi said:
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.
Click to expand...
Click to collapse
But, do you can connect, with this ROM, to your car multimedia? I'm asking this cause I have a ROM that supports Android Auto, but the car multimedia doesn't accept the connection.
Tks.

Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .

RawthiL said:
Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .
Click to expand...
Click to collapse
Thank you so much. If you find in your backup and upload I really appreciated. Tks.

Hi @RawthiL,
I'm also interested in making AA work on my S3, could you please explain how you managed to get the error log when launching the app ? I'd like to check if requirement changed in recent version. If not, I'll be interested in your custom ROM (if you still have it)
@RRvello if @RawthiL sent it to you privately, I'm interested in getting it too
Thanks Guys

I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?

RawthiL said:
I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?
Click to expand...
Click to collapse
Thanks @RawthiL for the file and the command, I'll try them and let you know !

really
very useful and helpful thread
thanks

It does work, Thanks @RawthiL !
I used to have "Your Device is not compatible ..." with all CM and Lineage version I tried, and now the connection to the car is established. Didn't make much tests, but it looks laggy, nothing surprising for a 7 years old device.
Next I will try the mirroring hack, not sure it will be usable because of the under powered phone, but I'll give it a try.

AA mirror works, without much lag !
I just followed the usual tutorial, no need to downgrade Google Play Services or anything else:
- root GS3
- install AA unlock/AA mirror
- launch unlock, grant root access, unlock, reboot
- launch AA mirror, configure settings you need
- connect phone to the car, go to speedo icon, choose AA mirror
Sound and video are working great, I don't have a touchscreen on my car (Audi A4 B9), so I have to navigate with the phone touchscreen (I enabled the Show Taps dev option to see where my finger is).
Of course it's not safe to play with phone / stare at screen while driving...
Thanks again to @RawthiL for making this test a success on my old unused GS3 !

Great to hear that!
Thanks for sharing how to enable the screen mirroring, I was not aware that you could do that. The lag issue is indeed annoying in AA...

lenuisible2 said:
AA mirror works, without much lag !
Click to expand...
Click to collapse
Hi,
Someone can confirm is still works?
I have an old S3, and want to give it a way to use it with my android car (soon to own that).
If so, what ROM, kernel, and root do you use?
Thank you

[App][5.1+][Alpha] AnyAutoAudio - Use any audio app in Auto

{
"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"
}
AnyAutoAudio
So I was tired of not being able to use the audio apps I normally use in Auto and decided to try and do something about it. This app is the result :fingers-crossed:
How does it work?
By using the notification listener permission, the app is able to access the media session of any audio app that is running. This is then passed to Android Auto, which makes it possible to control as any normal Auto app. This also means that it is necessary to run the audio app(s) first before running Auto.
I have several ideas for future features, but would like some feedback first and get rid of bugs. Take it for a spin!
Howto:
- Setup AnyAutoAudio from the app
- Open and run music app(s)
- Run Android Auto from phone or dashboard
Latest progress update & ideas for the future:
https://forum.xda-developers.com/showpost.php?p=72587291&postcount=67
Download:
https://labs.xda-developers.com/store/app/dk.jonske.AnyAutoAudio
Install AnyAutoAudio directly from apk:
If downloading the APK directly you need to allow unknown sources in Auto,
- In the Android Auto app, tap the Hamburger menu.
- Tap About.
- Tap About Android Auto header 10 times, until a toast appears thar says "Developer mode enabled". Now you can access developer mode by selecting the overflow menu dots on the top right of the handheld screen.
- Select Developer settings from the overflow menu and check unknown sources.
Source: https://developer.android.com/training/auto/testing/index.html#phone
Release notes
0.1.0
- Startup tutorial
- new settings interface
- FAQ
- Feedback
- Analytics
- Pinned apps (browsing)
https://forum.xda-developers.com/showpost.php?p=73426860&postcount=108
0.0.4
- No more need for app list! Just run the music apps and open Auto.
- Issue with controls not responding should be fixed
- Lots of bug fixes
0.0.3
- Apps already with Auto implementation is filtered out
- Queue implementation
- If audio app is destroyed, just pause
- Smaller app size
- Error include audio app name
0.0.2
- System apps now allowed in app selection.
- Basic voice control implementation. So far only "play music" seems to work ("pause", "play" etc. fails on Google's side)
0.0.1
- First alpha release
- Basic control and metadata

Hi,
Tested and working with "Google Play Books". :good:
I suggest to try to support the FM Radio App.
Perhaps, you feel I'm fool but I like to check one DAB Radio App running in my phone... my car doesn't have DAB radio.

manos78 said:
Hi,
Tested and working with "Google Play Books". :good:
I suggest to try to support the FM Radio App.
Perhaps, you feel I'm fool but I like to check one DAB Radio App running in my phone... my car doesn't have DAB radio.
Click to expand...
Click to collapse
Great to hear it works!
Do you have a link for the app? It should work as long as the app is playing audio the standard way in android, so I'll have a look

jvvpc said:
Do you have a link for the app? It should work as long as the app is playing audio the standard way in android, so I'll have a look
Click to expand...
Click to collapse
For the RADIO (FM) it's the stock FM App... Try it in your phone, it isn't detected in the list of Audio Apps.
Regarding the DAB App it's this:
http://play.google.com/store/apps/details?id=com.ex.dabplayer
Please, continue improving this great App!
For example, your App can send button events to the controlled App? Back, Play/Stop, Next...

This is the app:
http://androidstereo.mobile.eu.org/default-apps/2.7.4/com.tw.radio_78cc.apk

manos78 said:
For the RADIO (FM) it's the stock FM App... Try it in your phone, it isn't detected in the list of Audio Apps.
Regarding the DAB App it's this:
http://play.google.com/store/apps/details?id=com.ex.dabplayer
Please, continue improving this great App!
For example, your App can send button events to the controlled App? Back, Play/Stop, Next...
Click to expand...
Click to collapse
Ahh, the list is filtering out system apps. I will include them in the next update
There shouldn't be any problems with the DAB app. Have you tried it?
Yes, it will handle all button events like play, pause, next etc. I will look into if it can take special buttons some apps use

Jusrt tested with local files and vlc and this works well. Its a Great idea.. Ill be a really happy camper if u can get it to pull the audio from firefox and chrome.
Youtube/netflix/hulu etc could all be nice too. But the browsers obviously would be top priority cuz then u could do anything (live tv news etc etc) in my opinion.
Regardless..Great job and idea!
keep at it. I Will report back after more experience with it.

jvvpc said:
Ahh, the list is filtering out system apps. I will include them in the next update
Click to expand...
Click to collapse
Great! Waiting for it! :fingers-crossed:
jvvpc said:
There shouldn't be any problems with the DAB app. Have you tried it?
Click to expand...
Click to collapse
No. It's a wish for the future... if your tool works, then I'll purchase the dongle.
jvvpc said:
Yes, it will handle all button events like play, pause, next etc. I will look into if it can take special buttons some apps use
Click to expand...
Click to collapse
It will be interesenting if you introduce some additional interaction with the audio app. :good:

Version 0.0.2 is now released, with system apps included and basic voice control.
Mac31284 said:
Jusrt tested with local files and vlc and this works well. Its a Great idea.. Ill be a really happy camper if u can get it to pull the audio from firefox and chrome.
Youtube/netflix/hulu etc could all be nice too. But the browsers obviously would be top priority cuz then u could do anything (live tv news etc etc) in my opinion.
Regardless..Great job and idea!
keep at it. I Will report back after more experience with it.
Click to expand...
Click to collapse
As i have now included system apps Chrome works. Just tested it with a radio website The video apps wont run i the background so we cant use Android Auto at the same time, this is a Android limitation. I have read reports that some find it possible to open Youtube in Firefox though?
manos78 said:
Great! Waiting for it! :fingers-crossed:
No. It's a wish for the future... if your tool works, then I'll purchase the dongle.
It will be interesenting if you introduce some additional interaction with the audio app. :good:
Click to expand...
Click to collapse
See if the Radio FM app works now

jvvpc said:
Version 0.0.2 is now released, with system apps included and basic voice control.
See if the Radio FM app works now
Click to expand...
Click to collapse
Installed! Thank you!
Results:
- App FM don't show in the list. :crying:
- Voice control: Please, explain how to use it.
- No bugs detected. :good:
Regards.

manos78 said:
Installed! Thank you!
Results:
- App FM don't show in the list. :crying:
- Voice control: Please, explain how to use it.
- No bugs detected. :good:
Regards.
Click to expand...
Click to collapse
If a app dosent show up, it is because it is not made in the standard way Android handles media. Maybe try a different FM app from the Play store? Just find one that has a notification widget, then it should work. I dont have fm in my phone so cant test it myself
For the voice control, only "play music" seems to work ("pause", "play" etc. fails on Google's side). This is a requirement from Google, so couldnt update the app without including this, but will expand it furter like "Play Chrome on AnyAutoAudio".

jvvpc said:
If a app dosent show up, it is because it is not made in the standard way Android handles media. Maybe try a different FM app from the Play store? Just find one that has a notification widget, then it should work. I dont have fm in my phone so cant test it myself
For the voice control, only "play music" seems to work ("pause", "play" etc. fails on Google's side). This is a requirement from Google, so couldnt update the app without including this, but will expand it furter like "Play Chrome on AnyAutoAudio".
Click to expand...
Click to collapse
For most android head units you can not use a different FM radio app as far as i'm aware. The DAB app does not show up either which is a big shame, oh well.

jvvpc said:
If a app dosent show up, it is because it is not made in the standard way Android handles media. Maybe try a different FM app from the Play store? Just find one that has a notification widget, then it should work. I dont have fm in my phone so cant test it myself
Click to expand...
Click to collapse
The stock FM Radio in my Moto G4 has "a notification widget". It's like any other audio app.
Please, can you provide some technical info about how you search for Apps? Can you include some logging tool inside your App?
jvvpc said:
For the voice control, only "play music" seems to work ("pause", "play" etc. fails on Google's side). This is a requirement from Google, so couldnt update the app without including this, but will expand it furter like "Play Chrome on AnyAutoAudio".
Click to expand...
Click to collapse
Great! You will start the "AudioApp" when the command "Play [AudioApp] on AnyAutoAudio" is done, or will be required to have the AudioApp already open?

Dec64 said:
For most android head units you can not use a different FM radio app as far as i'm aware. The DAB app does not show up either which is a big shame, oh well.
Click to expand...
Click to collapse
Ahh so its a unit with Android onboard? Well it should still handle the apps the same way. The way this apps works is by connecting to the MediaSession that an audio app should create, if you follow Android Docs. But apps can still play audio without this, and some does so. I have tried it with different audio apps, and so far have not found other ways
manos78 said:
The stock FM Radio in my Moto G4 has "a notification widget". It's like any other audio app.
Please, can you provide some technical info about how you search for Apps? Can you include some logging tool inside your App?
Great! You will start the "AudioApp" when the command "Play [AudioApp] on AnyAutoAudio" is done, or will be required to have the AudioApp already open?
Click to expand...
Click to collapse
My fault I assumed that audio apps with notification used standard implementation, but not all does have I found. Also see answer above
For the filtering it works by finding apps that use the intent "ACTION_MEDIA_BUTTON". This is what an audio app is required to use to be able to handle volume and playback control, so any audio app using MediaSession will have this. Also in 0.0.3 it will filter out apps that already have Android Auto implementation
EDIT: Answer to last question
You will still need to have the audioapp already opened. I might be able to change that for head units but for the Auto app I can't as calling new apps will open ontop and that violates the rules..

jvvpc said:
Ahh so its a unit with Android onboard? Well it should still handle the apps the same way. The way this apps works is by connecting to the MediaSession that an audio app should create, if you follow Android Docs. But apps can still play audio without this, and some does so. I have tried it with different audio apps, and so far have not found other ways
My fault I assumed that audio apps with notification used standard implementation, but not all does have I found. Also see answer above
For the filtering it works by finding apps that use the intent "ACTION_MEDIA_BUTTON". This is what an audio app is required to use to be able to handle volume and playback control, so any audio app using MediaSession will have this. Also in 0.0.3 it will filter out apps that already have Android Auto implementation
EDIT: Answer to last question
You will still need to have the audioapp already opened. I might be able to change that for head units but for the Auto app I can't as calling new apps will open ontop and that violates the rules..
Click to expand...
Click to collapse
So it's not possible to get the FM radio apps in question to work at all?

jvvpc said:
EDIT: Answer to last question
You will still need to have the audioapp already opened. I might be able to change that for head units but for the Auto app I can't as calling new apps will open ontop and that violates the rules..
Click to expand...
Click to collapse
Hi,
Perhaps a root mode to launch an App as background can be a temporal alternative.
What you think?

Dec64 said:
So it's not possible to get the FM radio apps in question to work at all?
Click to expand...
Click to collapse
Well the problem is not in the FM itself, you might be able to find other FM apps that will work. I will continue to seek solutions that will work across most apps
manos78 said:
Hi,
Perhaps a root mode to launch an App as background can be a temporal alternative.
What you think?
Click to expand...
Click to collapse
That's a good idea! I will add it to my todo list, but will focus on the basic features for now. I will look into it when that is working properly
:good:

Also has anyone tried it with a head unit yet? When I use the emulator, the icons on the list of chosen apps in Auto disappears after first load. Not sure if this is a emulator error or in the app, as i don't get this on my phone

Can you please pm version .02 as that allowed spotify to show up. For some reason after the 2.3 update to android auto my spotify no longer shows up at all. This app was only the way for my spotify to work.

App installed... works as promised. Very useful, thanks! Will test next versions for sure...
@chocolatet: as I already wrote in other thread, to restore Spotify, you must install that app from adb shell (not from Play store).

[APP][5.0+][Alpha] AA Passenger - Stream audio, control nav, show pics

AA Passenger
https://github.com/martoreto/aapassenger
What's this
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
play any music via car speakers (for now this requires root on passenger's device)
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel you're driving to looks like)
What's new
1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume
1.9-alpha8
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
note that both driver's and passenger's apps must be updated to work together
Installation
https://github.com/martoreto/aapassenger/blob/master/README.md#installation
Screenshots
{
"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"
}

Can you describe some more what exactly you can do with this and how?
Can we install this android auto sdk somehow and use this?
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Thanks,
Sent from my SM-T700 using XDA-Developers Legacy app

Thanks for bringing additional functionality to AA!
I hope your SDK will bring more devs support for AA apps

sosimple said:
Can you describe some more what exactly you can do with this and how?
Click to expand...
Click to collapse
You mean this app or SDK? I assume app.
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel they're driving to looks like so the driver would easily find it)
play any music via car speakers (for now this requires root on passenger's device)
sosimple said:
Can we install this android auto sdk somehow and use this?
Click to expand...
Click to collapse
The SDK itself is for developers. It allows writing new Android Auto apps.
It rather won't help much in modifying existing apps to run on AA, as the logic behind AA apps is quite different than for normal apps.
The SDK is used like any other Android library.
I published an example demo project (linked in README) which shows how.
sosimple said:
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Click to expand...
Click to collapse
It is somewhat possible, for example by creating a new Andoid Auto app which mirrors the screen of the phone on the car screen and then somehow circumvents the fact that Android Auto displays its own graphics on the phone screen.
It's also possible to modify an open-source navigation app (I'm experimenting with OsmAnd recently) and implement the Android Auto functionality.

Many thanks for description. Very good. I would pay for an app mirroring passenger screen to android auto screen.. (showing anything passengers screen shows, video, navigation, etc).
I think many others would like this, if anyone could implement it..
Sent from my SM-T700 using XDA-Developers Legacy app

Any ideas for what other things than navigation, watching videos while stopped and dangerously distracting the driver while driving would this be useful?

Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay

Sissi1991 said:
Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay
Click to expand...
Click to collapse
Hi @Sissi1991, thanks for trying the app.
I see good news that you established the wireless connection successfully, which was one of the major concerns I had with the app.
You're right, sending photos should work without root. I saw another report in the SDK thread, when the example app could behave similarly.
Just to make sure it's the same: when you take the screenshot, the screen on Android Auto becomes black for about a second, and then appears the AA home sceen?
Also, does the same happen when trying to send some other picture than a screenshot (like Gallery -> <some photo> -> Share -> Send to Android Auto)?
A note about rooting: it's required only on passenger's device (to make audio work).

@Sissi1991, feel free to try the new release:
https://github.com/martoreto/aapassenger/releases/tag/0.9-alpha2

Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'

Kill Me said:
Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'
Click to expand...
Click to collapse
Ok, this looks like another issue and alpha 2 rather won't make any difference here.
This error shows on the passenger's device, right?
If possible, please PM me links to:
- Android bugreport captured after this error (Settings -> Developer options -> Take bug report)
- The picture which failed to send
Thanks for trying this out.

Thanks for developing such a great idea
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Enviado de meu Nexus 6P usando Tapatalk

@Sissi1991, @Kill Me, here's 0.9-alpha3 with "error resizing image" fixed. Give it a try!
https://github.com/martoreto/aapassenger/releases

bladerj said:
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Click to expand...
Click to collapse
Yeah, I expected that Wifi Direct may have some connection issues. Nevertheless, please do this:
On driver's device open "AA Remote Settings" -> "Enable discovery".
On passenger's device open "AA Passenger"; if the setup wizard shows up, go to the "Pairing" page.
Wait 5 minutes.
On both devices, capture Android bug reports, upload them somewhere and PM me the links.

Thank you, ill give it a try.
Pairing through Wifi direct isnt indeed ideal and it takes a while to get connected, i get why using 'passenger' smartphone, but as the driver is driving the passenger could use the connected AA phone i think

@martoreto installed and tested new version! Works perfect. Keep on your good work!

Kill Me said:
but as the driver is driving the passenger could use the connected AA phone i think
Click to expand...
Click to collapse
Just my 3 cents on this idea: some things can be done with this AA-connected phone, and this doesn't need any special app mostly.
I don't know how it is on other phones, but on my HTC One M8 I can open any app even when AA is connected using tricks like opening notifications drawer, going to Settings, Apps etc.
But even then Maps can't be open on both AA and the screen. It can't render at the same time to 2 destinations.
Then, fiddling with the cable can easily disconnect the nav.
That's why I go with the idea of using the passenger's phone, with his/her music library, maps favourites, bookmarks, whatever context etc., to make car travel a more "together" experience.

Let me announce a new major release: 1.9-alpha8
It has two new main features, namely:
Audio streaming without root, as rooting was rather a major blocker for
this feature to be useful.
Hotspot mode. Now the apps don't rely on Wi-fi Direct only (but it's still supported).
They will work also if the passenger's device is connected to the hotspot started
on the driver's device.
Full release notes:
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
Note that both driver's and passenger's apps must be updated to work together.
Enjoy!

1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume

Deleted