Meaning of screen buttons in "Learning of steering wheel" menu - Android Auto General

What does menu buttons 0, 3, 5, 10 mean?
#5: What is "LUD"?
What is difference between #0 and #10?
{
"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"
}
I interpreted each as:
0 = MUTE1
1 = DVD
2 = NAVI
3 = RADIO
4 = PLAY PAUSE
5 = LUD
6 = PREV TRACK
7 = NEXT TRACK
8 = ANSWER
9 = HANGUP
10 = MUTE2
11 = EQ
12 = MODE
13 = VOL-
14 = VOL+
15 = BLUETOOTH
16 = SEEK BACK
17 = SEEK FWD
18 = HOME
19 = BACK
20 = POWER

LUD is for Loud sound effect. #0 is mode/Mute function, just program it to a button, short press is mode function, long press will be mute function.

Thanks for the info; especially #0.
Is there a way to have the radio go to the next Preset instead of seek up/down? My original stereo could do that, but I cannot find a way to do it with the Android unit.

how do you get to this menu?

Related

Android Bluetooth Control Device allow you to control various electrical devices

Android Bluetooth Control Device
Android Bluetooth Control Device Application is to allow you to control various electrical devices up to eight devices and independently controlled.
Use Android Bluetooth mobile device to remote control your device with Bluetooth Receiver hardware Device.
{
"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"
}
The program features.
- control up to 8 devices.
- Can be set Timer to ON / OFF the device and show the time.(the timer can be set to 1 minute, 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours).
- Use with Receiving device (Bluetooth Receiver Box).
Design for the Android version 4 and a screen resolution of 480 x 800 (WVGA).
Freeware with AD (free software)
More info about hardware :
http://microcontrollerkits.blogspot.com/2012/02/arduino-control-8-devices-via-android.html
More info about Apps :
http://androidcontrol.blogspot.com/2012/02/android-bluetooth-control-8-devices.html
Google Play Market
https://play.google.com/store/apps/details?id=com.app.control

[GUIDE][How to Change Colour of RAM Info Bar]

Requirements
1.Brain & Knowledge about Decompiling & Recompiling
2.Tool for Decompilng & Recompiling
3.Settings.apk
GUIDE
1. decompiled files Settings.apk
2. Go to the folder
smali / com / android / settings / applications and
open file LinearColorBar.smali
3. Locate the following
line: .method public constructor (Landroid / content /
Context; Landroid / util / AttributeSet V then the code
below find the following code: .prologue const v0,
-0x23d7e9
4. Replace -0x23d7e9 with color code
you want (-0x23d7e9 code is somewhat red color)
5.
Save, recompile. sign, and push it to the system
Here's
a list of color codes: White = 0x0 Red = -0x10000
Yellow = -0x100 Pink = -0xFF01 Blue = -0xFFFF01
Green = -0xFF0100
Search for other by yourself & share here
{
"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"
}

How to set up a margin for navbar icon?

I am using BottomNavigationview and I want to animate the height of it, so it is extendable. My problem is that the Items stay centered vertically, but they should have a fix top-margin of e.g. 5dp. How is it possible to move them up with the top of the navbar?
My XML for one of five Items (with text!) (in menu folder):
HTML:
<item
android:id="@+id/testid1"
android:icon="@drawable/ic_test1"
android:title="@string/Overview"
android:state_pressed="true"
/>
The XML for the Navbar:
HTML:
<com.google.android.material.bottomnavigation.BottomNavigationView
android:id="@+id/bottom_navigation"
android:layout_width="match_parent"
android:layout_height="56dp"
android:layout_gravity="bottom"
android:background="@color/white"
app:elevation="0dp"
app:itemIconSize="26dp"
app:itemIconTint="@color/NavBarGrey"
app:itemRippleColor="#B5F1F1F1"
app:itemTextColor="@color/NavBarGrey"
app:layout_constraintBottom_toBottomOf="parent"
app:layout_constraintEnd_toEndOf="parent"
app:layout_constraintHorizontal_bias="0.0"
app:layout_constraintStart_toStartOf="parent"
app:menu="@menu/bottom_nav_menu" />
Here the Kotlin-Code for the "up" animation:
Code:
val anim = ValueAnimator.ofInt(convertDpToPixel(56.0).toInt(), convertDpToPixel(400.0).toInt())
anim.addUpdateListener { valueAnimator ->
val `val` = valueAnimator.animatedValue as Int
val layoutParams: ViewGroup.LayoutParams =
bottom_navigation.getLayoutParams()
layoutParams.height = `val`
bottom_navigation.setLayoutParams(layoutParams)
}
anim.setInterpolator(OvershootInterpolator(1.0f))
anim.duration = 450
anim.start()
Here is how it looks right now.
{
"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"
}
The round items should move up to the top like the blue button (which is an extra object and not part of the navbar)

GPS reports wrong time when affected by GPS week rollover on S10

It shows sonething in 2003 now. It is said it only affects "older devices".
https://gitlab.com/LineageOS/issues/android/-/issues/1446 says it was fixed in LineageOS in 2020.
Why do I have this bug now on an S10 with the latest official Lineage 19.1 for beyond1lte?
{
"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"
}
Apparently it was just bad reception ... but it is strange nevertheless.
No it's still happening even with perfect conditions.
This fix https://review.lineageos.org/c/Line...ommon/+/276241/11/gps/core/LocApiBase.cpp#248
is nowhere in the 'beyond1lte' lineage source. But it most probably should be ...
That fix apparently works for beyond1lte, too.
Diff:
--- hardware/qcom/gps/core/LocApiBase.cpp~ 2023-02-06 09:49:31.000000000 +0100
+++ hardware/qcom/gps/core/LocApiBase.cpp 2023-02-06 22:36:25.225063952 +0100
@@ -243,6 +243,12 @@
location.gpsLocation.bearing, location.gpsLocation.accuracy,
location.gpsLocation.timestamp, location.rawDataSize,
location.rawData, status, loc_technology_mask);
+
+ if (location.gpsLocation.timestamp > 0 && location.gpsLocation.timestamp < 1580000000000) {
+ location.gpsLocation.timestamp += 619315200000; /* 1024 * 7 * 24 * 60 * 60 * 1000 */
+ LOC_LOGV("week rollover fixed, timestamp: %lld.", location.gpsLocation.timestamp);
+ }
+
// loop through adapters, and deliver to all adapters.
TO_ALL_LOCADAPTERS(
mLocAdapters[i]->reportPosition(location,
(if it wasn't fixed elsewhere in the source since the last official download package ... is that so much behind the source? ...)

LineageOS 20 + Waveshare 7.9 HDMI == very small laucher screen

Hi.
I try to combine a Raspi4B with a Waveshare 7.9 HDMI Screen.
after installing the KonbstaKang Android 13 from March with an alternative Display (10").
then switching to the WaveShare Display, modifying the resolution.txt in the boot folder to 400x1280 and adjusting the hdmi settings in config.txt to:
hdmi_group=2
hdmi_mode=87
hdmi_timings=400 0 100 10 140 1280 10 20 20 2 0 0 0 60 0 43000000 3
in origin mode (Rotation = 0) everything is fine.
when I rotate to 270° my launcher screen is about 2cm in width.
{
"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"
}
playing around the Trebuchet launcher crashes.
I tried Nova Launcher, butz it has the same little space as before.
every app uses the full space, except the launcher.
any ideas, what I can change to make it usuable?
many thanks in advance for any help
kind regards
Patrick
ok, I found the solution myself.
I had to allow rotation in Trebuchet Launcher

Categories

Resources