- Jan 16, 2022
how can I delete this double post or delete posts this new one was an accident typing from my google pixel 4a using firefox
Yes I said I needed more information and yes what about modding compiled images by bad on that part. I’m new to the modding and mainly just curious about how to do it for compiled apps and adding them to compiled images with boot loaders and main system.img. I thank you for giving me more direction. If you find more info or have more on this my email is [email protected] also I can remove that from this post if that’s against the forum rules or just message here or directly to my xda account if possible.Problem with that specific display is that it uses SPI for the display interface (SPI for touch interface is fine). Not to endorse anything but e.g. Waveshare also has small displays that use DPI/DSI/HDMI as the display interface (see selection guide section at e.g. https://www.waveshare.com/7inch-hdmi-lcd-c.htm). HDMI displays are of course the most used so shouldn't require much additional effort.
My first Android phone from 10+ years ago had display with 480x800 resolution (ironically what the official Raspberry Pi 7" display also has). So, let's just say that that or anything smaller than that is not what you'd expect for device running modern Android these days. Just having a display resolution/density related discussion above. Very small resolution/density can also cause all kinds of issues (UI on the OS itself because no one else in the world uses such low resolution anymore, app compatibility issues because of missing low density drawables because no one needs them anymore, etc.). https://developer.android.com/training/multiscreen/screendensities
My Raspberry Pi builds use standard ext4 partitions (system, vendor, data - FAT is used for boot partition). You can just directly mount the sdcard on your Linux machine and edit contents of any of the partitions. There's simg2img/img2simg tools to pack sparse images most Android devices use. Mounting the image writable (and what fs it uses - ext4/F2FS/etc) is another story.
Your links refer to adding precompiled apps when building Android from source.
1. I can't reproduce any issue with searching the settings, works fine for me. You need to be more precise than that.Hello, can you tell me how to fix these things:
1. Search doesn't work in settings
2. Short press of navigation bar power turns screen off instead of going to lock screen.
I've read on Bluetooth jitter and gapps already.
And GPS with ublox 9 is solved with another gnss hal, which works with both ublox 7 and 9.
I have to say so far this is a very nice release. Thank you.
Well when I go to settings and type something I want to find in the search box nothing appears. It doesn't work.
Well when it also turns off touch response and you don't have a gpio switch its pretty counterproductive to remove the power and reboot in order to get a screen back. Thought I'd mention it.
Searching the settings works just fine so something wrong at your end.
Touch input stopping working after switching the display off is not expected behavior. It's been reproduced on both the official DSI touchscreen and USB touchscreens and was discussed at https://forum.xda-developers.com/t/...raspberry-pi-4-b.4356891/page-2#post-86008999 It works on previous Android versions so some issue with Android 12 that I haven't still looked into.
Thanks. I've been aware of this and been meaning to give it a test sometime. The antenna on my U-Blox 7 module is really bad and/or there's too many floors of concrete on top me so it's difficult to get a location fix to do any meaningful testing, though.
Logcat? I can't reproduce any issue with my USB sound card at least. IDK why USB DAC would be different.
Why would my reply be any different that the last two times you posted this exact same thing? Still haven't seen any logs.
Audio through the 3.5mm jack works (please read the OP and FAQ). There's no support for composite video. You can use HDMI and DSI connectors for display with this build.
No logs yet.
I did look at the op and under not working I couldn't see any mention of composit video, for allot of people it's a big feature, I would add it under the not working area to avoid simular questions like mine, do you plan on adding support for it?
Composite video is 1950s technology so it's hardly relevant these days and barely anyone uses it (nor should). I don't have any hardware so I have no plans to support it. Here the latest discussion about composite video on Android: http://disq.us/p/2lftnz2I did look at the op and under not working I couldn't see any mention of composit video, for allot of people it's a big feature, I would add it under the not working area to avoid simular questions like mine, do you plan on adding support for it?
Do you know of generic USB touch digitizers will work with this build? I know it works with raspbian and stock Android and stuff, no sure about this setup though, was also planning on hooking up a dvb tuner to it.
You can't. You can consider Android as an OS for embedded devices. It needs to work just on the hardware that the device has built-in and nothing else. It's not designed to support every possible hardware and configuration in the world at the same time.
Thank you!You can't. You can consider Android as an OS for embedded devices. It needs to work just on the hardware that the device has built-in and nothing else. It's not designed to support every possible hardware and configuration in the world at the same time.
There is a know issue with bluetooth audio and Google location services after installing gapps. This only happens with gapps installed and if you've enabled location access during the gapps setup. Google location services scan nearby bluetooth devices to determine the device location which doesn't work great when your using bluetooth audio at the same time. There's also workaround available if disabling Google location access is not enough https://forum.xda-developers.com/t/...aspberry-pi-4-b.4212945/page-14#post-85769441
MicroG requires a patch for signature spoofing that is not included in LineageOS for security reasons. I think this is also something that can be achieved using Magisk (which is now supported) but haven't looked into it.
I'm pretty confident it will work eventually. Soon(™) is also a relative term.
And that didn't even take too long. \o/ But yes, H.264 V4L2 hardware decoding can work on Android on the Pi 4!