yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] Misterxtc:
That sounds similar to my issue with my P8P from Verizon. I had the 21 ultra and traded it in for the 6 Pro. The zoom was far superior on the 21 than the P8P and P6P and performance is very similar on all three. I would be more inclined to go for the S24 Ultra as of now.
[Google Pixel 8 Pro] derausgewanderte:
I used to have an S21 Ultra, have an S22 Ultra that my wife now uses and the P8P. One of the weaknesses of the P8P is 5G compared to the S22 Ultra. Overall I am getting better coverage and reception on the S22 Ultra. From my experience in my area I'd be pessimistic for the P8P to be any faster.
[Xiaomi Poco X3 Pro] ahmedezzattr:
Icant find any lecia camera version compatible with my device poco x3 pro always crashing after installation

i have arrow with android 13 (rooted),

but cant install , i need a suitable version zip file

any advice?!!!?
[Xiaomi Poco X3 Pro] Binarybard:
It's not the zip file it's the ROM you're using. If your ROM doesn't support Leica then you can't use it.

You can try ROMs that have Leica.
[Xiaomi Poco X3 Pro] ahmedezzattr:
so can i flash any miui camera compatible with android 13 rom
[Xiaomi Poco X3 Pro] Binarybard:
You didn't understand.

You can flash in any ROM. But if you want that camera working then you need a ROM that is compatible with Leica.

Or use crDroid, EvolutionX etc that has Leica installed.
[Xiaomi Poco X3 Pro] kd276:
Well, Arrow is compatible with Leica, but only, for now, the unofficial release:

Releases · dogpoopy/messed-up-roms

Contribute to dogpoopy/messed-up-roms development by creating an account on GitHub.

github.com
[Redmi Note 12 Pro / Pro Plus 5G] jasonhelene:
Hey all,

i see a lot of people talking about the 12 pro but nobody is talking anything about the 12 pro plus?

What are the options for custom rom on that? What are the recovery options for note 12 pro plus? How to debloat official rom?

i swear i googled a lot but everybody is speaking about the 12 and not about the pro plus so i need some info, thanks.
[Redmi Note 12 Pro / Pro Plus 5G] dkionline:
Pro 5G and Pro+ working with the same firmware.
[Redmi Note 12 Pro / Pro Plus 5G] iCrop:
the ROMS for the Redmi Note 12 Pro 5G are also for the Pro+
[Redmi Note 12 Pro / Pro Plus 5G] rudiratlos57:
Easiest with "ADBAppControl-1.8.3"
[Android TV General] Stevyn7:
Hi, I would like to awake my Android TV box on a certain time and certain channel (to safe data or to schedule recording). Is there nay app or addon that can do this ?
[General Topics] dd0bb:
What phone you had the best experience with haptic feedback in the Android world?

I really care about haptic feedback. Few years ago I send my OnePlus 8T back because of the weak vibration motor. It was so bad that I never will forget it.

Xiaomi's haptic feedback was probably the best in the Android world.

View attachment 6054823

Mi 10 Pro was so good! Not just in quality but also in the way it's integrated throught the system. It also got one of the best speaker system but all these end with Mi 11. Compare to iPhone 13 Pro Max it was alnost the same experience but on IOS I can't use haptic feedbaxk on keyboard, so it was useless.

Second place go to OnePlus 7 Pro

View attachment 6054826

It was also really good but not as good as Mi 10 Pro.

Looks like with the OnePlus 12 they are back.

https://twitter.com/i/web/status/1732052546158805130

WhyLab from China got a list. Meizu 21, a cheap 400€ device are in the top 3.

微博

随时随地发现新鲜事！微博带你欣赏世界上每一个精彩瞬间，了解每一个幕后故事。分享你想表达的，让全世界都能听到你的心声！

m.weibo.cn

My Galaxy S23 Ultra is far behind. It's not bad but it's not good, just "ok" score.

So, what was your best/worst haptic feedback experience?
[Touch HD General] Cap Loz:
Now that the BBC have seen fit to support the HD, I've changed the user-agent back to default but I still get a very distorted and Pixellated playback through both the live feed and Catch Up. (As I did previously with the workaround)

I thought I'd cured it by setting the maximum media buffer (25 secs) in options but it is still the same.

This is through WiFi as I am with O2 and of course that's not (hopefull) yet supported.

I don't have any problems with the video playback of any other video files.

Anybody help please.

?? :confused:
[Redmi Note 11 (spes/spesn)] VIS_HNU:
Is redmi note 11 (spes) in india is eligible for hyper os
[Redmi Note 11 (spes/spesn)] sbhajband:
Some rumour says hyperos update is available in next some months. But Android 14 update is not available for our Redmi Note 11.
[Redmi Note 11 (spes/spesn)] ensarman:
so what if I flash my global phone with the Indian firmware, could I get the HiperOS update?
[General Questions and Answers] gldev:
I have a Motorola Moto G8 Power Lite smartphone (XT2055-1,Type: M546D) with a 6.5-inch screen and adaptive brightness disabled in screen settings.

Nevertheless, the brightness of the display often decreases while reading web pages, and the only solution I have left is to turn off the screen with the power button and then turn it back on to restore normal brightness.

Page scrolling does not restore normal brightness.

Any suggestions about this problem ?
[General Questions and Answers] blackhawk:
Try in safe mode. Clear system cache if you have that option. Try a hard reboot too.

Probably a 3rd party app screwed up hidden user settings.

Use manual brightness control; auto brightness never worked well and it waste battery.

A factory reset may be needed even if the app that caused it is uninstalled.

If a factory reset fails, reflash to last known good stock version. If all the fails it's likely a hardware failure.
[General Questions and Answers] gldev:
The only solution I found is to leave the adaptive brightness enabled, otherwise the brightness does not stay at the set value, and when the drop occurs as described above, you have to turn the screen off and on again.
[General Questions and Answers] blackhawk:
Try in safe mode to rule a 3rd party app as the cause. If that fails...

The user partition or the rom has become corrupted. Factory reset.

If that fails reflash to last known working version.

If all the fails it's a hardware failure. The first cause is the most likely.

If you installed some kind of book reading app (including Google as it screwed up my display on my N10+) it's a prime suspect. Simply uninstalling may not be enough as it may have altered hidden settings and isn't uninstalling clean. I strongly suspect a 3rd party app caused this.

On the hardware side you can run some of the hidden self tests too if these phones have them. Free Devchek can also show sensor outputs.
[Raspberry Pi Original Development] KonstaT:
Here’s my build of LineageOS 20 for Raspberry Pi 5. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.

Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build! You can contact me by email to discuss creating customized Android builds for commercial purposes.

LineageOS 20 (Android 13)

for Raspberry Pi 5

konstakang.com

There is also Android TV version available.

LineageOS 20 Android TV (Android 13)

for Raspberry Pi 5

konstakang.com

Working:

Audio (HDMI, USB microphones, bluetooth speakers/headphones, etc)

Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)

Bluetooth (and bluetooth tethering)

Camera (using official Pi camera modules & UVC USB webcams)

GPIO

GPS (using external USB modules e.g. U-Blox 7)

Ethernet

Hardware accelerated graphics (V3D, OpenGL & Vulkan)

Hardware video decoding (H.265 decoding)

HDMI display (and HDMI-CEC)

I2C

IR remotes (using external GPIO IR modules e.g. TSOP4838)

Power button

RTC

Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3, LSM303DLHC, BME280/BMP280, and APDS9930 accelerometer, gyroscope, magnetometer, temperature, pressure, humidity, ambient light, and proximity)

Serial console (using external GPIO serial console adapters e.g. PL2303)

SPI

Touchscreen/multi-touch (official 7” touchscreen, USB touchscreens, Waveshare SPI touchscreens)

USB (mouse, keyboard, storage, etc)

USB-C (ADB, MTP, PTP, USB tethering)

Wifi (and wifi tethering)

Issues:

Issues with DSI displays (Issue#58)

Some audio DACs need additional configuration (Issue#5743)

Various issues with CSI camera modules

SELinux is in permissive mode

Encrypting userdata is not supported

and more…

Sources:

kernel

Thanks:

Roman Stratiienko and GloDroid project

Peter Yoon and android-rpi project

AOSP reference board developers (dragonboard, hikey, yukawa)

Android-x86 project

LineageOS team and everyone who has contributed to LineageOS 20
[Raspberry Pi Original Development] KonstaT:
How to install:

Follow the official Raspberry Pi instructions for writing the image to the SD card.

You can also update to newer builds using TWRP flashable OTA packages. OTA updates pushed through the built-in Updater app are stored at /data/lineageos_updates/.

Download lineage-20.0-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi5-ota.zip and save it to your device’s internal storage or use an external USB drive

Boot to TWRP recovery (see FAQ)

Install lineage-20.0-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi5-ota.zip from your selected storage

(Flash Magisk/other add-ons you had previously installed)

Boot out of recovery (see FAQ)

Changes that are backed up and restored flashing OTAs:

Device specific settings changed using Settings -> System -> Raspberry Pi settings

Manual changes to /boot/resolution.txt and /boot/rc_keymap.txt

USB boot configuration in /boot/config.txt

User specific options in /boot/config_user.txt

GApps

Changes that are not backed up and restored flashing OTAs:

Manual changes to /boot/config.txt (and any other manual changes to /boot partition)

Magisk

FAQ:

FAQ is getting quite long and difficult to maintain in several different places. You can find the always up-to-date FAQs here:

https://konstakang.com/devices/rpi5/LineageOS20/

https://konstakang.com/devices/rpi5/LineageOS20-ATV/
[Raspberry Pi Original Development] KonstaT:
Merged commits not mentioned in the changelog.

12.1. changelog:

initial release

Mesa 23.3.3

FFmpeg 6.0.1, AOSP dav1d 1.3.0

alsa-lib/alsa-utils v1.2.10

libcamera master/v0.1.0

Linux 6.1.68 kernel

Android security patch level: 5 January 2024

Previous builds:

AndroidFileHost
[Raspberry Pi Original Development] KonstaT:
Note about GApps on the Android TV release.

GApps are not part of release but since I'm sure this going to get asked. Unlike my LineageOS 20 releases on Raspberry Pi 4, Pi 5 releases need to register Google Services Framework Android ID for Google services to work.

As this gets slightly trickier on Android TV than with the regular tablet UI builds, I've created a TWRP flashable tool that will extract the GSFAID you need to register. Flash this in TWRP with the GApps package.

https://androidfilehost.com/?fid=11701882489785033172

Once you've attempted (and failed) to sign-in on a Google account on the Android TV setup wizard, power down the device and mount the sdcard/USB/NVME on your computer. You should find a file named 'gsf-android_id.txt' on the boot partition that contains the ID number you need to register. Once you've registered the ID, boot the Pi 5 again and sign-in on the Google account.
[Raspberry Pi Original Development] elkir0:
Thank you!! I'm Gonna try this later today.
[Raspberry Pi Original Development] deanfourie:
This is running pretty smoothly on my pi 5.

I'm trying to run this as primary navigation aid for my boat running Navionics.

What I need is a working GPS and compass, and for that I am using onboard serial GPS on UART0. From your previous post (on the wrong thread my bad, one of those days) you mentioned to disable serial console by editing cmdline.txt.

I changed

console=ttyAMA0,115200 no_console_suspend root=/dev/ram0 rootwait androidboot.hardware=rpi5 androidboot.selinux=permissive

to

no_console_suspend root=/dev/ram0 rootwait androidboot.hardware=rpi5 androidboot.selinux=permissive

Any now the PI fails to boot into Linage at all. After changing back to the first line, it stills fails to boot.

Any ideas on this one!

Thank you.

Sorry for making a mess of the posts, ill stick to this thread from now on.
[Raspberry Pi Original Development] KonstaT:
That shouldn't prevent the device from booting of course. If you're a Windows user, make sure you've used a proper text editor with UNIX line endings to edit any of the text configurations or that you haven't corrupted any of the Linux partitions on the sdcard (e.g. by Windows suggesting to "fix" any partitions that it fails to understand).

On current releases UART0 is used for serial console. If/when there are further releases, serial console will be moved to the separate UART connector (https://github.com/raspberry-vanill...mmit/71b154a8bb0facac24c8a27a0bfff93d3fe1aaf5) now that I've got myself hardware to test that it works.

So, to use serial GPS device on the GPIO you would need:

1. Move the serial console away from the UART0 i.e. change ttyAMA0->ttyAMA10 in /boot/cmdline.txt

2. Enable UART0 (GPIO14/15) by adding/having 'dtparam=uart0=on' in /boot/config.txt, you'll see /dev/ttyAMA0 appearing

3. Configure the Android serial GPS HAL to use the right device, edit /vendor/build.prop and change value of 'ro.kernel.android.gps' property ttyACM0->ttyAMA0
[Raspberry Pi Original Development] deanfourie:
Could you please explain a little more how to do this.

3. Configure the Android serial GPS HAL to use the right device, edit /vendor/build.prop and change value of 'ro.kernel.android.gps' property ttyACM0->ttyAMA0
[Raspberry Pi Original Development] deanfourie:
Also,

When attempting to install magisk, I get the following

Have tried multiple downloads, multiple media sources, same result

View attachment 6056023
[Raspberry Pi Original Development] deanfourie:
Ok,

Long and exhausting but heres where im at.

Had to flash Magisk straight after a fresh install, without even booting the ROM, then it was sucessful.

Disabled serial console in cmdline.txt, confirmed enabled in config.txt

With the device rooted, opened ADB

ls /dev/
cat /dev/ttyAMA0

130|rpi5:/ # cat /dev/ttyAMA0^C
130|rpi5:/ # cat /dev/ttyAMA10
^C
130|rpi5:/ # cat /dev/ttyAMA0
�$GPRMC,083221.00,A,3640.78634,S,17442.09394,E,0.097,,160124,,,A*65

$GPVTG,,T,,M,0.097,N,0.180,K,A*24

$GPGGA,083221.00,3640.78634,S,17442.09394,E,1,04,1.80,20.3,M,28.6,M,,*77

$GPGSA,A,3,31,26,03,28,,,,,,,,,6.26,1.80,6.00*00

$GPGSV,3,1,09,01,17,287,24,02,08,309,,03,56,243,31,04,27,238,30*72

$GPGSV,3,2,09,25,07,143,,26,58,035,27,28,44,135,32,31,71,161,34*74

$GPGSV,3,3,09,32,21,081,*4B

$GPGLL,3640.78634,S,17442.09394,E,083221.00,A,A*72

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

$GPTXT,01,01,01,NMEA unknown msg*58

Looks good so far, however I cannot for the life of me figure out how to edit the /vendor/build.prop file. It keeps saying I do not have permission to edit the file. Have confirmed I have root access.

Have tried

127|rpi5:/vendor # sudo nano /vendor/build.prop
/system/bin/sh: sudo: inaccessible or not found
127|rpi5:/vendor #

Also,

rpi5:/vendor # su
rpi5:/vendor # nano /vendor/build.prop

[ File '/vendor/build.prop' is unwritable ]

Any ideas how I can edit this file?

Failing that, if its easier, I can see by default it is set to ttyACM0

ro.kernel.android.gps=ttyACM0

Which UART on the pi would I use for ttyACM0?

Thanks
[Raspberry Pi Original Development] KonstaT:
For example with ADB:

adb root
adb remount
adb shell
sed -i 's/ro.kernel.android.gps=ttyACM0/ro.kernel.android.gps=ttyAMA0/' /vendor/build.prop

or on the device:

su
mount -o rw,remount /vendor
sed -i 's/ro.kernel.android.gps=ttyACM0/ro.kernel.android.gps=ttyAMA0/' /vendor/build.prop

If you'd checked the /tmp/magisk.log you'd probably known exactly why. Most likely you had already installed it successfully once. It doesn't patch the ramdisk if it's already patched.

It's a device that USB GPS devices use. It's not for any UART on the device.
[Raspberry Pi Original Development] deanfourie:
Thank you! That worked perfectly, however still no GPS :(

do you know if only specific device are compatible, or if it just accepts generic NMEA sentances?

Not sure why its not working
[Raspberry Pi Original Development] KonstaT:
Yes, 'cat /dev/ttyAMA0' looks just as it should.

You're likely still missing permissions for the device node. See /vendor/etc/ueventd.rc. There's a following section:

# GPS
/dev/ttyACM0 0660 system radio
/dev/ttyUSB0 0660 system radio
/dev/ttyS0 0660 system radio

Add similar line for /dev/ttyAMA0 there as well. Forgot that it's not already there, will add if/when there are future releases.
[Raspberry Pi Original Development] deanfourie:
Thank you, I will test this shortly.

Is there a log that I can check that will show any issues related to GPS if it does not work?

Thanks for your help!
[Raspberry Pi Original Development] deanfourie:
Hey thank you! GPS is now working! great!

Now, is there any chance you could help me with I2C magnetometer,

1|rpi5:/ # i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1e --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
rpi5:/ #

Found @ 1E, looks like one of these.

0x1E
FXOS8700 Accelerometer/Magnetometer (0x1C, 0x1D, 0x1E or 0x1F)
HMC5883 Magnetometer (0x1E only)
LIS2MDL Magnetometer (0x1E only)
LIS3MDL Magnetometer (0x1C & 0x1E)
LSM303 Accelerometer/Magnetometer (0x19 for accelerometer and 0x1E for magnetometer)
LSM9DS0 9-Axis IMU (0x1D or 0x1E for Accel/Mag, 0x6A or 0x6B for Gyro)
MCP9808 Temperature Sensor (0x18 - 0x1F)

Is it possible and fairly simple to add support for these modules (I dont know exactly which magnetometer it is)?

Thank you so much! This is awesome!

EDIT: With some googling, I think it might be the LIS3MDL
[Raspberry Pi Original Development] KonstaT:
Well done!

To add support for unsupported sensor module, you can look into previous discussion on e.g. http://disq.us/p/2w873fx and https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/28. You would first need to what hardware it is of course.
[Raspberry Pi Original Development] deanfourie:
Im going to take a guess, and start with the LIS3MDL.

Where do I even find a RPI5 android compatible kernel driver for that device.

I havent even started yet and im lost :rolleyes: im worried haha
[Raspberry Pi Original Development] deanfourie:
I am looking at this.

GitHub - STMicroelectronics/st-mems-android-linux-sensors-hal: stm mems sensors-hal for Android and Linux platforms.

stm mems sensors-hal for Android and Linux platforms. - STMicroelectronics/st-mems-android-linux-sensors-hal

github.com

Could you confirm this will work with this port?

Also, which option should I choose? Legacy?

Also is there anything I need to do to add the option to the raspberry pi menu in LineageOS settings?

Android

HAL is compiled using different makefiles in order to support the two different modes. Fortunately this is transparent at the end for the build system, correct declaration is needed in order to choose the version to build and install.

In Android legacy mode (pre full treble) the HAL is build as dynamic library (.so) and the Android framework or HIDL 1.0 service load the library at runtime. In Android HIDL 2.0 and AIDL (full treble) mode, HAL is build as an executable and a service is created to run within it.

You can find the related documentation for Android here:

multi-hal 2.x
HIDL 2.0
AIDL
Legacy

Thank you.
[Raspberry Pi Original Development] deanfourie:
Can you help with when trying to install anything, or executing any command in ADB shell returns,

/system/bin/sh: git: inaccessible or not found

also, APT will not work too.

/system/bin/sh: apt: inaccessible or not found

Same over SSH

Thanks

ALSO, I have tried with a GY-511 which works, however there is a lot of latency.

Thanks
[Raspberry Pi Original Development] deanfourie:
Hi Konsta,

Can you please help me,

I set my USB GPS Speed to 4800 BAUD rate but it reverts back to 9600 on each reboot.

in my /vendor/build.prop I have

# GPS
ro.kernel.android.gps=ttyUSB0
ro.kernel.android.gps.speed=4800
ro.kernel.android.gps.max_rate=1

I can force the BAUD change and it works well with,

stty -F /dev/ttyUSB0 ispeed 4800

However, these changes to do not stick on next reboot.

Can you please help me.

Also, I am having issues with compass calibration. The compass will not calibrate (in my case a GY-511 magnetometer). I did not that the compass can take up to 4 seconds to respond to movements. This could possibly be related to why it will not save calibration data?

Thanks
[Raspberry Pi Original Development] Smokinimages:
When I try to run the resize script I'm getting an error about no such directory /dev/block/sda4?
[Raspberry Pi Original Development] KonstaT:
Seems to be the same driver that is already built into my kernel for LSM303DLHC.

android_kernel_brcm_rpi/drivers/iio/magnetometer/st_magn_i2c.c at android-14.0 · raspberry-vanilla/android_kernel_brcm_rpi

Contribute to raspberry-vanilla/android_kernel_brcm_rpi development by creating an account on GitHub.

github.com

You would need to create a similar overlay entry for it to enable the driver in config.txt.

android_kernel_brcm_rpi/arch/arm/boot/dts/overlays/android-i2c-sensor-overlay.dts at android-14.0 · raspberry-vanilla/android_kernel_brcm_rpi

Contribute to raspberry-vanilla/android_kernel_brcm_rpi development by creating an account on GitHub.

github.com

That's a sensor HAL. This IIO sensor HAL is used on my releases.

GitHub - lineage-rpi/android_hardware_intel_sensors-iio at lineage-20.0

Contribute to lineage-rpi/android_hardware_intel_sensors-iio development by creating an account on GitHub.

github.com

This is Android. Android doesn't have package management like your regular Linux distribution. You also can't use your regular Linux binaries since everything needs to be compiled for Android specifically. Android uses its own C-library (bionic vs. glibc).

You could e.g. add a script to /vendor/etc/init.d/ that does this when booting the device. See other scripts in the directory for reference.
[Raspberry Pi Original Development] KonstaT:
Maybe worth pointing out what storage device you're booting from?

I updated the resize.zip today to support resizing the partition when booting from NVME if related.
[Raspberry Pi Original Development] Smokinimages:
Yeah I was booting from a NVME lol I did a wipe, reinstall and used the useus partition tool which seems to have worked ok

Thanks
[Raspberry Pi Original Development] deanfourie:
Thanks KonstaT,

So if i'm correct, I will create a script to run in /vendor/etc/init.d to execute the command,

stty -F /dev/ttyUSB0 ispeed 4800

This way, it will run on boot? Also, I noticed that when using the power button feature, even after pushing the power button, when turning on again it would have defaulted back to 9600, this was not even a complete shutdown and boot.

Can you give me an idea of how the script looks? Im doing some searching but not finding much!

Thanks
[Raspberry Pi Original Development] KonstaT:
This serial GPS HAL is used on my releases.

GitHub - lineage-rpi/android_hardware_gps

Contribute to lineage-rpi/android_hardware_gps development by creating an account on GitHub.

github.com

The correct way would be to just set 'ro.kernel.android.gpsttybaud=4800' in /vendor/build.prop.

android_hardware_gps/gps.c at lineage-20.0 · lineage-rpi/android_hardware_gps

Contribute to lineage-rpi/android_hardware_gps development by creating an account on GitHub.

github.com