yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] Cypher2:
Pretty damn well yes!
[Raspberry Pi Original Development] maxi_power:
Hi,

I can not install open gapps tvstock 11.0...

Error 20
[Raspberry Pi Original Development] KonstaT:
Yeah, doesn't the error message already explain it all?

Also please read the FAQ.
[Raspberry Pi Original Development] maxi_power:
Perhaps, for those who are experts in this.

In which part of the faq.?

Spoiler content hidden.
[Raspberry Pi Original Development] KonstaT:
One could probably assume the part about installing Google apps is relevant to installing Google apps?

And before you ask, I don't have anything to do with any gapps release.
[Raspberry Pi Original Development] Tom33231:
I mean yes very true just also curious about what’s possible as well. I mean this single board computer rocks as far as embedded projects go and etc. Wondering the implications of android being almost completely usable and almost all functions at this point working.
[Raspberry Pi Original Development] Tom33231:
I know more work has to be done for full compatibility and documentation for external and internal software mods on this pi4. Like for hardware and software compatibility and kernel drivers to make the porting process from Debian Linux to android Linux kernel modules and such easier and more possible.
[Raspberry Pi Original Development] Tom33231:
how can I delete this double post or delete posts this new one was an accident typing from my google pixel 4a using firefox
[Raspberry Pi Original Development] Tom33231:
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 thomasquad202@gmail.com 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.
[Raspberry Pi Original Development] Zyanx:
Hi

iam using your Rom on my Pi 4 2 GB and it rly work Great (using it as Homepanel Dashboard for Homeassistant).

But i have one Bug or may itz normal or my Pi is Defect , so i wanted to ask:

When I play Musik 100% Volume i got little noise/scratch on the outcome, it doesnt matter if i use the 3,5 jack or bluetooth. When i play it on 90 % or less it seems to work fine.

Someone else got this Problems? I only have 1 Pi 4 so i canot check with an other one.

Thx in Advance and Thx for the Nice Rom.

Greetings
[Raspberry Pi Original Development] Ajtaji:
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.
[Raspberry Pi Original Development] KonstaT:
1. I can't reproduce any issue with searching the settings, works fine for me. You need to be more precise than that.

2. Well, yes that's what pressing the power button does on Android devices in general. If you want to have a lockscreen when turning the display back on you need to enable one from Settings -> Security -> Screen lock.

Which GPS HAL did you use? Maybe this is something that can be included in the builds by default.
[Raspberry Pi Original Development] Ajtaji:
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.

android9_gnss_hal_driver/gnsshal/gps_zkw.c at master · zxcwhale/android9_gnss_hal_driver

Contribute to zxcwhale/android9_gnss_hal_driver development by creating an account on GitHub.

github.com

With line modifications: Obvious Line 45 & 46 and then

Line 73 changed to "static float report_time_interval = 5;"

The gps time is reported wrongly but it works with both usb modules.

if Line 73 is not changed it does the same as your supplied hal module. Perhaps yours has a reporting overload as well.

Thanks KonstaT
[Raspberry Pi Original Development] KonstaT:
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://xdaforums.com/t/dev-rom-uno...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.

Input event from any device (mouse, keyboard, touchscreen, etc) will wake the display in any case, not just pressing the power button.

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.
[Raspberry Pi Original Development] risant:
no sound when using usb external dac...what tweaks to be done ?...lineage 18 there's sound with usb external dac ..please help
[Raspberry Pi Original Development] Ajtaji:
I've noticed that this android likes to turn the sound down on usb dac. Maybe that's your issue.
[Raspberry Pi Original Development] jeff862:
What's the workaround for usb dac to work on lineage 19? Even the bluetooth audio crackling noise ... usb dac working on lineage 18.1 please help
[Raspberry Pi Original Development] KonstaT:
Logcat? I can't reproduce any issue with my USB sound card at least. IDK why USB DAC would be different.

There's been some reports about issues with USB DACs with Android 12 in general.

Google Pixel 6 bug is preventing audiophiles from using external DAC to listen to music

(Don’t) let the music play

www.androidpolice.com

Why would my reply be any different that the last two times you posted this exact same thing? Still haven't seen any logs.
[Raspberry Pi Original Development] anton2k:
Hey, does composite video and audio output work via the jack? or has it been tested? just thought I would ask the question before I go out and buy the cable, thanks!
[Raspberry Pi Original Development] risant:
the bluetooth audio crackling noise has been solved ,,, the location services must be turn off,,, only problem android 12 no sound external usb dac.. i think it's android 12 bug ,, no update yet
[Raspberry Pi Original Development] KonstaT:
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.
[Raspberry Pi Original Development] anton2k:
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?

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.
[Raspberry Pi Original Development] KonstaT:
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/2lftnz2

Yes, USB touchscreens work as listed working in the OP.

There's no support for TV tuner hardware. I don't have any. There's third party Android apps to support some specific TV tuner USB dongles, though.
[Raspberry Pi Original Development] Fodor Gábor:
Hi!

How can use usb bluetooth dongle? I have only Linux driver for the usb bluetooth dongle. I use this os for car pc. When bluetooth and wifi on is, than is interferenc.Musik play skipping.

Thanks for reply.
[Raspberry Pi Original Development] KonstaT:
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://xdaforums.com/t/dev-rom-uno...aspberry-pi-4-b.4212945/page-14#post-85769441
[Raspberry Pi Original Development] Fodor Gábor:
Thank you!
[Raspberry Pi Original Development] s0m3f00l:
I tried the Android TV:

lineage-19.0-20220114-UNOFFICIAL-KonstaKANG-rpi4-atv.zip

from the website on my Raspberry Pi 4 8GB Model B. It enters a bootloop when I flashed it and never makes it to the Lineage loading screen.

lineage-18.1-20220121-UNOFFICIAL-KonstaKANG-rpi4-atv.zip is working fine however.

Thanks for the build.
[ASUS ROG Phone 5 / 5s] Trash.umu:
Edit: I am keeping the information below intact, just incase someone goes through the same issues that I had gone through.

My recommendation is follow through with Johnny886 video on his installation guide and just skip any steps that aren't applicable to your set up. I recommend using his 0-update_image_edl.bat and not using Qfil or xiaomi. His video ends up showing most of the steps required to accomplish the repair, with exception of showing the phone and when you have to bring your phone into bootloader mode and what not.

I can personally attest to the fact this does bring a hard bricked phone from the grave. When I mean hard bricked, I mean black screen and in edl mode (shows up as a usb devices or port on your PC).

I am not a regular on these forums so I probably won't be here for long. I'll help if I see your posts, if I can help.

//////////////////////////////////////////////////////

Hello,

I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).

It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.

I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).

I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)

Anyone have a way forward with dealing with this firehose/sahara issue?

I am also in windows 10 test mode.

EDIT, Fix found:

So I found out what was wrong. It shows "program speaks firehose protocol while your target is speaking sahara" because I was using the ddr.elf file.

If you pay attention to it, which I didn't at first, it says this:

"

This can mean

1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13: prog_firehose_lite.elf)

2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target"

I found out you are suppose to use the prog_firehose_lite.elf file (or whatever file it say is the device programmer first).

When using the QFIL program, I was using the prog_firehose_ddr.elf and this caused the error to appear.

I will post an image showing how it is suppose to look like when configured correctly.

NOTE: (I ended up bricking my phone to the point of not having an accessible bootloader/recovery when ONLY using raw program 0 and patch 0 files). This made it so you can only turn on the phone using the - volume and power button and it gets stuck on the "republic of gamers" splash screen. I have a solution for that issue further down in the thread.
[ASUS ROG Phone 5 / 5s] JazonX:
Try here

Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW

Success is disgusted by some people, and will not share any files for free in the future.

xdaforums.com
[ASUS ROG Phone 5 / 5s] Trash.umu:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
[ASUS ROG Phone 5 / 5s] johnny886:
You need to install the correct Qualcomm driver, and then your folder cannot have spaces or some unsupported characters.
[ASUS ROG Phone 5 / 5s] johnny886:
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.

After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
[ASUS ROG Phone 5 / 5s] Trash.umu:
So my phone attempted to install the firmware but now it does not have a bootloader, it does not connect to the PC and it can only get up to the point of showing the republic of gamers logo and letters.

I am guessing the only way forward is opening this thing up or buying a new phone. Unless you have a way out of this?

1. It is no able to go into edl via computer through adb.

2. It does not appear on device manager nor disk management.

3. It does not have a recovery option appearing and pressing +volume and power button does nothing.

4. You can only press the - volume and power button, the regular power button does nothing and when using the - volume button and power button, it just gets stuck on the republic of gamers screen.

5. It does not go into edl mode when connected to either the bottom or the side port on the phone.

6. It does not connect to the computer even if you delete the device, the drivers, reinstall the drivers and device. reset the computer and device and all forms of these things in different orders.

If the only way forward is possibly removing the battery and maybe shorting two pins together, do you have an idea which pins these are?

EDIT, Fix found:

So I found out that if you connect the ROG 5s phones side port to the computer while it is frozen in the republic of gamers logo for about 20 minutes, it resets and the android recovery screen pops up with only the options of "try again" and "factory data reset" and appears as an asus I005D in universal serial bus devices on my device manager. Now that I have it connected to the PC, I have a way forward.

It appears as in recovery mode in adb. you can not do anything other than enter "adb devices" and "adb reboot edl"

forcing the phone into edl using the adb cmd of "adb reboot edl" makes the device appear as a port device. This will allow me to reinstall the firmware again using the QFIL program.
[ASUS ROG Phone 5 / 5s] Trash.umu:
I seem to keep falling through the same loop of errors. I wonder if there is a firmware error somewhere or if my phone is somehow rejecting the firmware.

I will update if I get anywhere.
[ASUS ROG Phone 5 / 5s] Trash.umu:
NOTE:

If for some reason you can not get your phone to turn on or it turns off as you press the recovery option.

You need to connect the usb port to provide power via the bottom port and NOT the side port.

I am not sure why it is required, maybe the bottom port energizes more things than the side port does and it causes this fault. If you have both ports connected, it disconnects the bottom port and automatically uses the side port.
[ASUS ROG Phone 5 / 5s] johnny886:
There is no error in the firmware, and it is only released after it has been tested and there is no problem.
[ASUS ROG Phone 5 / 5s] Trash.umu:
I'll attempt to figure out why my phone isn't working properly. It may take awhile. Maybe it has to do with multiple attempts of installing the same firmware, or it could be that some of my phones components are already dying and it is just a coincidence.
[ASUS ROG Phone 5 / 5s] Trash.umu:
NOTE: My phone kept failing to properly download johnny886 firmware because my phone (in particular) kept requiring me to switch between the side and bottom ports to keep my phone alive. I am unsure why I this was the case but I was able to finally install the firmware on my phone and my phone is now up and running properly.

I have to give thanks to johnny886 for his files, his video and his efforts. If not for him, my phone would still be a brick.
[Samsung Galaxy Note 9 Questions & Answers] bigboris:
I bought a Note 9 off Facebook marketplace and I think it's stolen. I checked the phone booted up and everything looked OK, but when I got home and started to set it up I get an error saying "This phone is protected by Knox Cloud Service. To continue setup, connect to a Wi-Fi or mobile network." The seller had disappeared by the time I went to message him.

I tried to connecting to my wifi and it seemed to connect, but I can't get through setup. I've been waiting for the cops to knock on my door for the last two months haha. Should I just throw it out or can I get around it somehow?
[Samsung Galaxy Note 9 Questions & Answers] bigboris:
Bump. Anyone know what I can do?
[Samsung Galaxy Note 9 Questions & Answers] iceepyon:
If you purchased it off eBay, I believe you can report it as stolen goods and get a refund.
[Samsung Galaxy Note 9 Questions & Answers] bigboris:
Yeah it was off Facebook unfortunately...
[Samsung Galaxy Note 9 Questions & Answers] iceepyon:
In that case there is not much you can do unfortunately.... I guess you could hand it into your local Samsung Service Center and explain the situation. But I don't think they can help you much with getting your money back. All they can do is take back the device and mark it as stolen.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Phat Phreddy:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.

I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting

It did work prior with stock recovery fastboot.

Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.

Anything obvious to suggest here ??

Poco F3 with TWRP cant detect fastboot.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Phat Phreddy:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..

Can TWRP need any different driver pairing than the stock recovery drivers ??

Worked straight away when stock.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mlcattini:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Phat Phreddy:
But I said its working on ADB..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Phat Phreddy:
Will give this a go..

Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Phat Phreddy:
Strange I thought I replied in here this morning..

Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
then it was definitely a problem in the driver.
[Huawei P20 Lite Questions & Answers] Crotaru:
Hello

First of all, i know its risky and i don't mind it, because the emui os is totally ****ty. So i was trying to install a custom rom, but i ended up in a big unknowness. Recently I installed a custom rom on a samsung device, but that doesnt compare. My version of the phone is ANE-LX1, having EMUI 9.1.0.392. From what i know i should get an unlock code from dc-unlocker (however i totally don't know how:) ) and then just type some commands and get to TWRP, but from what i read there are a lot of errors so if anyone is very kind and guides me i will be very happy:).

Take care!
[Huawei P20 Lite Questions & Answers] Frax3r:
Dc-unlocker doesnt work on emui 9. You have to go back to emui 8 to use it. And if i recall corretly you can't use emui 8 dload packages while emui 9 is installed. You can however use hisuite to rollback to 8. Dc-unlocker doesn't work in the version hisuite puts you to. So you have to downgrade little more with dload packages. I unlocked mine in build .125 or something. Just follow any youtube video demonstrating dc-unlocker once you're back in one of the compatible versions. Dc-unlocker is not your only option btw. You can use a tool called potatonv to get your code. With dc-unlocker you mess with software but with potatonv you have to short some pins on your phones board. Software or hardware, choose your poison.