Hello,
when using my universal's casing in pda mode, but the display content in notebook mode, then after switch off/on the display has been automatically reoriented to pda mode by the system itself.
Does anybody know how to disable this "feature"?
Best regards,
tomestos
I agree, I'd like to be able to disable it as well. I can see how it's very handy and at first I was like "Ooh that's neat!" but now I'd just rather it STAYED in landscape all the time unless I said otherwise. Weird? Perhaps, but that's my choice
YEah you would think there might be a registry hack for this to disable the reorientation.
Lets keep the thread going and see what we can get, as I have to admit it would be handy to deciede if it should rotate or jus thaving it stay in LS mode.
me too - I have mine mounted horizontally in the car - it'sa bit of a pain having to hit the rotate from time to time - would like to be able to set the mode
OK
My SPV M5000 sets the screen orientation correctly depending on how the screen is swivelled. This works fine.
However, I have a landscape holder in my car which grips the phone with it open in the portait orientation. ie, phone is in portait mode but sits on its edge (USB downwards to charge).
Is there a way that I can tell it that if its in portrait AND being charged to rotate the screen appropriately.
Thanks
Ross
Join the club,
You can use PhoneAlarm. It can automatically detect ChargingOnly mode and rotate the screen to Landscape for you.
I do not use PhoneAlarm to save RAM, instead I made a shortcut with wisbar to easily rotate the screen.
Hi,
I have the same config for the car holder of my Universal. For rotating screen properly, I use PocketZenPhone 6.0. I have configured a profile called car wich rotate screen in the right orientation and activate BTheadset on call. But I have to activate this profile by pushing screen, hardware button or voicecommand or programming on calendar...not working automaticaly...
I configured another profile called navigation wich activate bt for gps mouse, choose the right orientation and...launch TT5.21 on one click...
I have the acer iconia a500 and a samsung monitor with pivot function. if i plug in the hdmi cable i would like to use the tablet in portrait mode, but i found no way. have anybody an idea how to use the tablet in portrait mode if it is plugged to the monitor.
YES
My samsung tv does this also.. GO into the settings of the Monitor/ tv.. there is a toggle to change this in there... You cant do it from the tablet. unless you try the Rotation lock app in the marker.. That could work thou i have not tried it...
thanks for the fast answer. i have a picture attached so you can see how i use my computer monitor. in the monitor settings i can't change nothing. and using a rotating lock app have no effect. the tablet turns every time into landscape...
more ideas??
Hi,
I have a unique scenario I am trying to solve. I am looking for a Screensaver or AOD app that can be toggled on or off depending on a Bluetooth connection, that will also activate when the screen goes off, but can still accept google voice commands.
Scenario:- I get in my car and Android Auto comes on the phone. I don't have the screen always on as want to save battery and just don't need it on. But I still want to pass Google Voice commands to the phone, for Maps, Music etc. But this can't be done on the S8 with the screen off. I started looking at AOD apps, and found one on the Play store. Using Tasker I was able to have it start up when connected to my car, and it would display just fine, giving me the ability the say voice commands and do what I needed. The trouble was when I set Tasker to kill the app on disconnect it couldn't really do it, and i'm not root so couldn't use that option or issue a shell command to do it.
So I'm half way there, but wonder if anyone has come up with something similar or knows of an app that can be used in conjunction with BT in this way. The app doesn't have to be pretty, just display a black screen with a moving clock.
I know that there are many purpose-built Android DIN units that have some sort of resistive keypad interface. More than that I don't know a whole lot. I'm not talking about those.
I'm talking about normal Android tablets, like my Nexus 7 (2013) that sits on a gimble mount to my right. I do USB and Bluetooth so that's what I tried. Android has KeyEvents for a few things, like phone call, contacts and calculator. It doesn't have KeyEvents for Google Maps or your different audio apps. So your USB or Bluetooth device has to be different than a standard HID input device as you'll want to send custom info. Because you'll need to send intents, you have to make sure that your steering wheel is connected all the time to a specific Service or Activity. A normal HID input device belongs to the system and goes to the foreground app, not some random background app. So you need a custom USB or Bluetooth and an Activity or Service.
My steering column currently has just the single wire. I figure that I will use Bluetooth and steal a bit of power (milliamperes, not enough to actuate the horn) so it doesn't need batteries.
So, I threw together a proof-of-concept using USB. It works fine on my Android 9 devices, I set hot keys for a few different apps. I should be able to either add a second HID interface for "normal" buttons like volume, call or simply add that to the Activity or Service. There are currently permission wrinkles to get over on Android 10. Switching this from wired USB to Bluetooth is trivial.
Am I missing something? Is this old hat? How else is this done?
I've been doing some more work on this. I'm a bit surprised that I've gotten no resonance on this or anyone saying that they already do this some other way.
The 16 buttons can each do one of three things
A hot key directly to an app (not simply "next app" or "app switcher" dialog)
Go to a specific webpage using (and reusing) a specific browser tab (I've got onboard systems that host status web pages)
Normal Android keys like VolUp, VolDn, MediaPlay, etc.
The USB version works fine. It uses a daemon to inject the normal keys. The Bluetooth version is coming along. I've switched to using raw GATT instead of HID over GATT.
Na? How about this then?
Hi Renate,
I think these units you are talking about are not that often to find in cars. I don´t know anyone who uses a tablet in his car and the Nexus 7 is a real outdated unit, slow on startup and in usage.
The car units themselves normally provide SWC via CAN or resistance based.
To have an additional keypad beside the radio is not needed, as you are able to use the SWC buttons individually... at least for the most ones which are working resistance based.
That is the reason you won´t get any answers in this forum. Sorry for bad news...
Hi rigattoni: Thanks for the response. I'm just trying to figure out how people are using stuff in this whole Auto department.
I didn't think that anyone would be impressed with my Nexus 7 (2013), it's just what I'm using at the moment. In my vehicle (a Chevy G30 1 ton truck) a DIN unit is not as visible as a gimble mounted tablet. I do have space for a dual DIN. Currently I have a single DIN $20 stereo with Bluetooth. That's good enough.
But my theme was mostly: Do people have app-specific keys (without using the screen)? Can you go to Google Maps, your favorite streamer, your local audio collection (without using the screen). Would you like to? If you have CANBUS SWC you probably don't have a dedicated button to display your propane & fresh water tanks.
Aren't SWCs mostly normal Android KeyEvents? How can they get you to a specific app?
On CAN there is no possibility to change the SWC buttons to different apps.
If they are resistance based as a lot of the cars (even if I would like to get all things done via CAN) there you have an internal app included to register your buttons based on different resistance.
On a lot of units you even are able to set your SWC buttons to specific apps.
On top there you have this menu button on the SWC where you can toggle between FM radio, launcher, phone, MP3 and navigation, you name it...
I don´t use Google Maps, instead I use TomTom and if you set TomTom as standard navigation app, you can do so.
Additional buttons in form of a number pad I personally don´t need. By using an aftermarket launcher and have all my needed apps just in front.
For tablets like you use, the num pad is a nice thing as you don´t have these possibilities.... sure.
BTW: If you use an android car unit, there is no full BT stack implemented. That means that you would not be able to connect with your unit to the propane or fresh water tank or something like that. The implemented BT stack can only be used for phone calls and for BT OBD scanner.
Thanks again. Wow, it seems like those DIN units are more like radios than like Androids if they don't have full Bluetooth. Resistance keypads are kind of bush league too.
Actually, my tanks, power, HVAC, tilt come over WiFi from my Raspberry Pi. The OBD comes over USB from the microcontroller that runs my instrument display. (I've got to take a new photo since I replaced the display with a larger yellow one.) The PRNDL indicator indicates shifter position and which gear I'm actually in. The "5th gear" on a 4 speed is just what I call it when the torque converter locks. It kind of is another gear. I really love the lower left engine running time so that I remember to take coffee breaks!
I threw the keypad back on the steering wheel. For testing I just have 2 x AAA batteries. I'll add the current "stealer" later.
I use similar head unit to this one:
And I use analog (or resistive, whatever) SWC. It can be configured as in video above. I mean you can map any of those 16 functions to any button in SWC
Renate said:
Do people have app-specific keys (without using the screen)? Can you go to Google Maps, your favorite streamer, your local audio collection (without using the screen)
Click to expand...
Click to collapse
I'll try to answer as best as I can, because I'm not sure if I got your point.
Its possible to open some apps by SWC. For example button 4 opens navigation app, which can be selected in head unit options (it can be every navi app installed on your head unit - google maps, here maps, sygic etc)
11 opens FM radio app
9 pick ups a call (if actually is someone calling) or opens bluetooth app where you can make calls (contact list can be synced from phone, call history also). Also by this BT app you can stream music from phone to car audio.
As you can see its very limited. In my head unit there is no way to open e.g youtube app by SWC.
other functions which can be used:
1(play/pause), 2 ,3 ,5(mute),6,7, 10 no explanation required I guess
12 depends on how the Chinese implemented it In mine : press once - mute/unmute sound. press & hold for while - somehow locks the screen (like in smartphone), black screen with date and time is displayed. Sound is muted too.
13 'home' button - works like in smartphone, brings you to main menu
14 back - works like in smartphone
15 turns off display (but plays music/ navigation commands in background)
16 'mode' one of most useful - cycles through active apps
8 AFAIK it opens google assistant, but it doesnt work in mine.
Thanks, wotii098. It seems like you're reinforcing my point. Besides "Navigation" and "Radio" most of the actions are generic Android KeyEvents. I'd think that MEDIA_NEXT and MEDIA_PREVIOUS only work correctly when your music app is in the foreground? When it gets to the nitty-gritty, I use 3 different mapping services and I need to switch between them. If you are wondering what keycodes exactly are being generated (or just to check) you can use my UsbMode.apk (in the sig). Probably "Navigation" and "Radio" don't exist as KeyEvents.
Renate said:
Thanks, wotii098. It seems like you're reinforcing my point. Besides "Navigation" and "Radio" most of the actions are generic Android KeyEvents. I'd think that MEDIA_NEXT and MEDIA_PREVIOUS only work correctly when your music app is in the foreground? When it gets to the nitty-gritty, I use 3 different mapping services and I need to switch between them. If you are wondering what keycodes exactly are being generated (or just to check) you can use my UsbMode.apk (in the sig). Probably "Navigation" and "Radio" don't exist as KeyEvents.
Click to expand...
Click to collapse
No, Renate, that also works if the audio or navigation is working in background as the translated button press throws an intent. Even Navigation and Radio or any other app can be started (or taken to foreground) by mapping a keycode to a specific app.
For radio you even are able to switch stations without bringing the app to foreground. That all happens in the background by intents.
So nearly any modern Car radio with Android is working like that. You even are able to connect 2 different key panels to the units. That´s what I did... My SWC buttons are connected to the key 1 cable and an additional thingi in my cup holder in the middle console has different settings and is connected to the key 2 cable. So the preconditions in Android car radios are fine to fire the intents to every single app you programmed.
You even are able to use long-click intents to switch to different functions.
Examples:
Station forward is a short click, station search is a long click.
Volume down works in a long click as mute/unmute button.
Menu button calls navigation on long click
the green phone button takes the call, on long click I open the voice dialer
...
Well, clearly your (custom) radio app is working on Intents and not KeyEvents.
The problem with long presses is that it delays the immediate action of a press (until it determines whether it's a long or short press).
Ok, in mode switching applications that's not a killer. For page-turn it is. Being impatient, I expect action on the down press. I defeated the long/short logic on my Android ereader.
I replaced my old Nexus 7 (2013) with my cheapy Walmart ONN 8" tablet. Although the battery was fine, I decided to do a "battery-ectomy". The first reason is, I don't like the USB cord coming in the bottom of the tablet where I can catch my knee on it when I turn around. The Onn 8 is pretty standard with a 10k resistor from the white lead to ground to simulate a thermistor. I didn't want to give up the USB connector entirely as I can/will use it for my custom ODB. I was going to solder in an extension so that I didn't have to use the connector out the bottom. It turned out easier than that. The little PCB for the USB can be unscrewed and the flex printed circuit for it can be routed out a hole in the back of the tablet. I may epoxy the board to the back of the tablet, but for now it's dangling. The round thing in the center is a sawed-off microphone holder (5/8-27 thread) epoxied to the back of the tablet. It screws on a gimbal mount by my right hand. The red/black wires get fed 4V from a Velleman buck converter.