Develop Bugs

Zopo Zp920 Octa Core Mtk 6752

New ZOPO ZP920 OCTA CORE 5,2 inches
New thread for the new model Zp920 Octa Core Mtk 6752
ZOPO ZP920 MT6752 Octa Core 4G LTE 802.11ac 2GB 16GB Android 4.4 Smartphone 5,2 inches
{
"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"
}
​
Everybody are Welcome!​
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

Photos Section​
​

Details Section​​
ZOPO ZP920 4G LTE
ZOPO ZP920 comes with high-grade specifications, On top is a 5.2inch 1920*1080p display which is now standard for a high-grade phone. Under the hood, the ZP920 packs the 1.7GHz Octa Core MTK MT6752(28nm HPM), the RAM being identical at 2GB. ZP920 included an 13.2 mega-pixel rear with an f/2.0 rear camera with a selfi-compatible 8 mega-pixel front. ZP920 support Hotknot, which will make share file much easy. the most important is that after test theZP920 sample, we found the GPS Signal is awesome!!! it come with Glonass Tech. We will make a detail review of all these features by English video.
Specifications:
BRAND and MODEL
Brand: ZOPO
Model: ZP920
Carrier: Unlocked
Sim card: Dual Micro sim dual standby
Multi Language: Afrikaans, Bahasa Indonesia, Bhasa Melayu, Catala, Cestina, Dansk, Deutsch, English, Spanish, Filipino, French, Hrvatski, IsiZuzu, Italia, kiswahili, Latviesu, Lietuviu, Magyar, Nederlands, Norsk Bokmal, Polski, Portuguese, Romana, Rumantsch, Slovencina, Slovenscina, Suomi, Svenska, Tieng Viet, Tagalog, Turkish,Greek,Bulgarian,Russian, Serbian, Ukrainian, Hebrew, Urdu, Arabic, Persian, Amharic, Hindi,Thailand, Korean,日本語,Traditional Chinese, Simple Chinese 
OS and CPU
Operating System: Google Android 4.4 Kitkat OS,
CPU: MTK MT6752 1.7GHz, 28nm HPM Octa Core process
GPU:ARM Mali760 MP2 700MHz
MEMORY
Internal phone storage: 16GB ROM
RAM: 2GB
Memory card support : MicroSD Card up to 64GB
NETWORKING
TD-LTE+TD-SCDMA+GSM+WCDMA+FDD-LTE
2G: GSM：850/900/1800/1900MHz
3G: WCDMA: 900/1900/2100MHz
TD-SCDMA: 1880-1920/2010-2025MHz
4G: FDD-LTE: 800/1800/2600MHz
TD-LTE: 1880-1920/2300-2400/2555-2655MHz
CAMERA and VIDEO
Rear camera: 13.2MP, LED Flash 
Front-facing cam: 8.0MP
Video capture: 1080P(1920X1080)
ENTERNAINMENT
Video play formats: MP4/3GP/MOV/MPEG/MKV/FLV, ...
Audio play formats: MP3/AMR/AAC/ASF/Ape/Flac ,...
Ring Tone: MP3/AAC/ASF,...
Picture formats: JPEG/PNG/GIF/BMP,...
CONNECITIVITY and COMMUNICATION
USB support: 5pin Micro USB v2.0 
WiFi:802.11ac /a/b/g/n
WiFi Hotspot functionality, Tethering & portable hotspot - Synchronization via Exchange ActiveSync
Bluetooth technology: Bluetooth v4.0
GPS satellites: GPS,A-GPS,GLONASS,BEIDOU
Sensor: Gravity Sensor, Compass, proximity sensor
USB OTG View what is OTG on Wiki
HOTKNOT
Breathing Light
WIFI Display
Gesture
Smart Awake


DISPLAY
Screen Size: 5.2-inch
Color Support: 16 Million Colors
Screen Technology:，Capacitive Multi-Touch Screen , IPS, GFF
Screen material: Glass
Display resolution: 1920*1080 pixels
PRE-LOADED APPLICATIONS
Google Maps
Google Talk
Google Mail
Google Calendar
Google Play Store
Facebook
Twitter
Skype
Deleted all Chinese APP, English Version

BATTERY
Battery:2300mAh
SIZE
Dimensions: 145mm*72.8mm*8.7mm
Weight(Including battery) : 150g

Software Section​
New firmware:
Lollipop Android 5.1 (20150717-153831)
http://www.4shared.com/rar/3-N-ueDVba/20150717-154446_zp920_lollipop.html
How to have right root on zp920
This procedure is to receive right root on STOCK official firmware
Drivers :
http://www.4shared.com/rar/THPrHzDxce/USB_VCOM_Driver.html
https://www.dropbox.com/s/125r5twipmdt1wn/MT6589 drivers.zip
Recovery Modded
Carliv touch 3 ported for zp920
http://d-h.st/UmxA
Carliv CWM ported for zp920
http://d-h.st/MQ6k
Carliv CWM ported for zp920 (lollipop version)
http://www.4shared.com/file/_DWX9FtQba/recovery_cwm_base_for_lollipop.html
Remember after received the right root is not possible to apply the update of new firmwares.
Flashtool V.5.1444
Version Only for zp920
http://www.4shared.com/rar/AU4kSVORce/SP_Flash_Tool_exe_Windows_v514.html
Section setup Software:​
Drivers Installation :
Procedure :
To install the USB drivers VCOM the phone must be turned off and connected to the PC with or without a battery depending on the type of device,
get a screen like this in the device manager of the computer
Once you have installed the terminal will be shown in this way (the COM port may be different)
For those who have problems with the installation of these drivers and have had in the past a terminal mtk
they may have a driver conflict, or even if you just do the confusion and installed it different,
to solve, you can try to use the program
usbdeview:
http://www.nirsoft.net/utils/trans/usbdeview_italian.zip
select all items in that report as VCOM USB Preloader in the Mediatek figure right click Unistall and restart the PC
Installation of the Firmware:
PROCEDURE
1) Setup new Firmware
download the new firmware.
Unzip the compressed file and insert into the firmware folder:
a) recovery modded (is necessary for receive right root)
Phone off without usb cable and possibly removed the battery and put back for a perfect reset .....
and hold mode 'of off without usb cable connected!
Run Flashtool version octa-core ..... select the file, and then scatter firmware upgrade ...... NOW ONLY CONNECT USB CABLE not before!
Wait for the end of the installation procedure of the firmware and eventually restart the phone!
This' whole simplified procedure for installing the original firmware.​

ROOT Section​​
Root Section
PROCEDURE (SuperSu)
1) Download the SuperSu App from the Xda Web SIte
http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
or
http://download.chainfire.eu/644/SuperSU/BETA-SuperSU-v2.42.zip
Copy it to your SD card .
2) Go into recovery modded
Select SuperSu v.xx and install
Reboot into android S.O.
You should see the app installed Super Su.
3) Install Busybox (from files or from GooglePlay store)
open the app and give the right Su power and wait for it's scan
4) Install the binary from the Busybox menu' "normal install"
After correctly installed the binary ...Reboot the phone
And you will have your rights as a Root​
Utility Section​
Many Thanks to:
Jessica Tang, Feng, Xiaoyi Tang, Jaynes,Lee,
All My Friends here and from other web site and forums
Carliv,Yuweng, Codelover,Bigrammy,SevenMax, Marsapa, PaoloTHL, Command0, M3N3chm0,Biobio,ICEMAN,Mrjavum,
I apologize in advance if not list them all!​

Video Section and Custom Roms​
New Zp 920 Custom Rom V.1 Based Official Firmware LOLLIPOP Os With Right Root​
New Custom Rom for this Octa core will be pubblished soon!!!!
Details
New Rom V.1 Android LOLLIPOP 5.1
Zp920 20150717-153831
(new VERSION lollipop for zp920+)
1) Base LOLLIPOP original (zp920+ 20150717 Stock firmware );
2) Launcher base + nova all custom by me;
3) Samsung melody mod for Lollipop ;
4) Custom Applications always the best the most 'used on the Web;
5) Rights root 100%;
6) root browser
7) Screen off
8) Es file manager
9) Quickboot
10) DOLBY DIGITAL SYSTEM
11) walkman
12) Home smack
13) Recovery Carliv CWM 6 Ported BY Me
14) Supersu
15) Lollipop HD Theme for Nova Launcher
16) new boot logo
17) new boot animation
18) Camera Fx-5
and more others thricks
Installation Procedure
1) Unpack the archive to a folder
2) launched Flashtool (ver. For 67xx)
3) select the scatter file in the firmware
4) to make DOWNLOAD flashtool
5) Only NOW connect the phone to the PC with the USB socket
and wait for the process to finish
P.S.
If flashtool give error definitely do not have the recognition of the device drivers on your operating system
So, go on the dedicated thread and install the required drivers.
Links : files n.5
1/5
http://www.4shared.com/rar/9apa6i-4ce/Zp920_lollipop_Ghost45_V1part0.html
2/5
http://www.4shared.com/rar/Ehub1WT3ba/Zp920_lollipop_Ghost45_V1part0.html
3/5
http://www.4shared.com/rar/_FRKuRwFba/Zp920_lollipop_Ghost45_V1part0.html
4/5
http://www.4shared.com/rar/7nWQ6o4yce/Zp920_lollipop_Ghost45_V1part0.html
5/5
http://www.4shared.com/rar/KEoIK8vZce/Zp920_lollipop_Ghost45_V1part0.html
​

got it!
I just received mine this mourning still testing it.
Looks great, seems fast and performing... was searching a safe way to root it, though. Any help?

Quick review and questions
Thanks ghost45 for starting this thread.
My ZP920 arrived yesterday.
It seems pretty quick, but antutu froze during the 3d graphics test and the final score was only 32000 ??
Battery life seems very poor at present, down to 1% after 24 hours, although about an hour of that was on wifi, my old ThL W8 would do better. I've noticed that when I switch off and connect charger the screen immediately shows 27% charge, not the 1% before switch off. Anybody any clues ? faulty battery ?
Does anybody know which usb drivers are required and (ideally) a solid method for rooting the mtk6752 ?
I'm looking forward to progressing with this phone and hoping it is as good (well much better than) my old faithful - but slow - W8.

gmincca said:
Thanks ghost45 for starting this thread.
My ZP920 arrived yesterday.
It seems pretty quick, but antutu froze during the 3d graphics test and the final score was only 32000 ??
Battery life seems very poor at present, down to 1% after 24 hours, although about an hour of that was on wifi, my old ThL W8 would do better. I've noticed that when I switch off and connect charger the screen immediately shows 27% charge, not the 1% before switch off. Anybody any clues ? faulty battery ?
Does anybody know which usb drivers are required and (ideally) a solid method for rooting the mtk6752 ?
I'm looking forward to progressing with this phone and hoping it is as good (well much better than) my old faithful - but slow - W8.
Click to expand...
Click to collapse
Hi,
Probably antutu not have the necessary info to test this new phone with 64 bit architecture.
The problem about the battery is hard but i will hope after 7or 8 cycle of recharge the battery will be good.
I will test it immediately after that i receive it in my hands.
See you
Sent from my GT-I9505 using XDA Free mobile app

feedback
gmincca said:
Thanks ghost45 for starting this thread.
My ZP920 arrived yesterday.
It seems pretty quick, but antutu froze during the 3d graphics test and the final score was only 32000 ??
Battery life seems very poor at present, down to 1% after 24 hours, although about an hour of that was on wifi, my old ThL W8 would do better. I've noticed that when I switch off and connect charger the screen immediately shows 27% charge, not the 1% before switch off. Anybody any clues ? faulty battery ?
Does anybody know which usb drivers are required and (ideally) a solid method for rooting the mtk6752 ?
I'm looking forward to progressing with this phone and hoping it is as good (well much better than) my old faithful - but slow - W8.
Click to expand...
Click to collapse
More;
USB drivers all installed automatically when plugged in to Windows 7 x64 laptop, adb driver included see jpg clips.
tried framaroot no success, mtkdroidtools does detect phone, but has an error. No root so far....
Tip: 64Gb SDXC not recognised until it was formatted by the device, now working fine.

testing....
gmincca said:
My ZP920 arrived yesterday.
It seems pretty quick, but antutu froze during the 3d graphics test and the final score was only 32000 ??
Click to expand...
Click to collapse
I ran antutu smooth on my device and scored 41333 (device recongnized but result "not verified"), very close to the tests published on YT
gmincca said:
Battery life seems very poor at present, down to 1% after 24 hours, although about an hour of that was on wifi, my old ThL W8 would do better. I've noticed that when I switch off and connect charger the screen immediately shows 27% charge, not the 1% before switch off. Anybody any clues ? faulty battery ?
Click to expand...
Click to collapse
Yeah, the battery will probably be the real pain in the @ss, but i was pretty aware of that when i saw the specs....2300MAH
gmincca said:
USB drivers all installed automatically when plugged in to Windows 7 x64 laptop, adb driver included see jpg clips.
tried framaroot no success, mtkdroidtools does detect phone, but has an error. No root so far....
Click to expand...
Click to collapse
Same here, waiting for the gurus help
Last note on the camera.... doesn't seem performing at all, pretty slow on focus and pics are too "noisy"

Right root Zopo zp920
Right root is now possible, soon the procedure and the recovery modded only for zopo zp920

ghost45 said:
right root is now possible, soon the procedure and the recovery modded only for zopo zp920
:d
Click to expand...
Click to collapse
yeah thx so much!

update..
zut72 said:
I ran antutu smooth on my device and scored 41333 (device recongnized but result "not verified"), very close to the tests published on YT
Yeah, the battery will probably be the real pain in the @ss, but i was pretty aware of that when i saw the specs....2300MAH
Same here, waiting for the gurus help
Last note on the camera.... doesn't seem performing at all, pretty slow on focus and pics are too "noisy"
Click to expand...
Click to collapse
Hi, update,
Antutu v5.5 works well gives score 41450! (v5.6 still hangs at 3D graphics test ?? bug? also it doesn't list 64bit/32bit cpu test?)
Camera on mine works brilliantly for stills and video - skype video is best ever.
Battery life getting better after a couple of recharge cycles, now getting nearly 4 days mostly on standby.
Has anybody tried the Ghost45 rooting method yet ??
If I root manually (by su binary adb push from linux host etc) will this still void warranty and block future ota updates (i.e. to Lollipop)?

gmincca said:
Hi, update,
Antutu v5.5 works well gives score 41450! (v5.6 still hangs at 3D graphics test ?? bug? also it doesn't list 64bit/32bit cpu test?)
Camera on mine works brilliantly for stills and video - skype video is best ever.
Battery life getting better after a couple of recharge cycles, now getting nearly 4 days mostly on standby.
Has anybody tried the Ghost45 rooting method yet ??
If I root manually (by su binary adb push from linux host etc) will this still void warranty and block future ota updates (i.e. to Lollipop)?
Click to expand...
Click to collapse
My Update :good:
- yes the camera, overall is pretty good, excellent with decent lighting
-battery life is getting better every day (i'm at the 5th recharge cycle): after a full working day with medium usage, i'm still at 71%
-i found a post on zopomobileshop forum explaining how to root the device with the alert:
Remember after received the right root is not possible to apply the update of new firmwares.
Still havent tried yet, was hoping to get Lollipop on it.

gmincca said:
More;
USB drivers all installed automatically when plugged in to Windows 7 x64 laptop, adb driver included see jpg clips.
tried framaroot no success, mtkdroidtools does detect phone, but has an error. No root so far....
Tip: 64Gb SDXC not recognised until it was formatted by the device, now working fine.
Click to expand...
Click to collapse
The only procedure that run well is described in first page.
Sent from my GT-I9505 using XDA Free mobile app

Hi,
I interested this phone, but i don't know what's about battery life. How many ours can you use the smartphone (time on screen in battery setting) in normal usage (wifi, 3G, games etc.)? Thank you in advance.

Could someone please run androbench and post the first 4 results. And if you run the benchmark several times, does performance drop significantly?
Thanks

Androbench
semo.pz said:
Could someone please run androbench and post the first 4 results. And if you run the benchmark several times, does performance drop significantly?
Thanks
Click to expand...
Click to collapse
Hi,
as requested..
Sequential read 104.96 mb/s
Sequential write 30.18 mb/s
Random read 17.0 mb/s 4354.48 iops 4k
Random write 1.53 mb/s 393.39 iops 4k
any help?

@gmincca very nice, thanks. I have been considering the Elephone P6000 as it also have very good IO stats but it seems to have issues I'm not prepared to put up with
http://bbs.elephone.hk/thread-1815-1-1.html#.VM-yH51FDIV
How are you finding the ZP920? Any annoying issues (e.g., Bluetooth, gps while driving, call quality, touch screen issues, etc...)
Thanks

Android reversing mirror model rt01

Android 4.4 Reversing Camera Mirror With A10,A23,A33 CPU​
These mirrors come in many different flavours now. At time of edit post A33 x5 quadcore is the latest with 16GB. This newer unit can be rooted with kingroot apk version. I find I lose root after reboot for some reason. I haven't found a firmware for this mirror version as of yet. For some reason my mirror does not have a wifi antenna attached so poor signal unless 4 meters line of sight. Please becareful as from experience from buying 3 mirrors now, there can be huge differences to build quality even thou they look the same.
I'm not updating this thread with RT01 firmware anymore. Please check Baidu link below
Also need this to load firmware to TF/microsd
PhoenixCard_V310_20130618.rar
To load new firm run Phoenixcard - Select image - Insert TF card/ Microsd - Choose burn (Try until magic) - Insert Tf Card into mirror and shutdown - After mirror firmware loaded you must format to normal or Tfcard will flash mirror again on reset
You may also find your firmware here. Let me know if you can't download it(use iPad to view)
http://pan.baidu.com/wap/share/home?uk=4026862827&third=0
Yfgo.apk - Radar program (you need mirror with radar function)
Yfgo.apk
Thx to nyinyiwale
How to get root access:
Download this settings.apk and run it! Thanks to Nick Nick
Setup.apk (A23)
Now you should have developer options - Enable usb debugging
Now install on windows machine http://pdanet.co/ for android
Then install kingo root http://www.kingoapp.com/android-root/download.htm
{
"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"
}
Specifications
Processor - Allwinner A13 Cortex A8 1.2GHz Dual Core
Smart systems - Android 4.4 OS
Screen - 5.0 inch HD 5 point touch screen
Diplay resolution - 800X480 pixels
DDR - Built in 512MB DDR 3
Nand Flash - Built in 8GB (systems will occupy 1.72GB )
External storage - Support Maximum 64GB TF card(not included)
Image Sensor - 5.0 million pixel HD camera, 350 degree rotate front lens
Lens angle view - Front 140 degree +back 120 degree
Video Resolution - Front: 1920*1080(30f/s)/HD1280x720(30f/s) - Rear: 640X480 30f/s
Video format - MP4
Picture format - JPEG
Compression - H.264
Speaker - Built in
MIC - Built in
External I/O port
1*USB 2.0
1*TF card port:
1* GPS port
1*AV IN (support auto reverse function)
Dimensions - Main product size: 310x90x20mm (L x W x D)

Just got this item off eBay. Url removed
Screen looks great. Touch screen works a treat. Nice and bright and good angle also.
There are a few things different listed that the seller on eBay has not listed correct.
It comes with android 4.4.2 And not 4.0
Has a A23 dual core and not A10
Kernel version 3.4.39
And it has a battery which would last a couple of days with no use - make sure you turn off wifi when not on power
This is a true android with some very basic functions missing. Starting it has no google services. So no google play store, no where to login to google account in settings. The launcher looks good(you can't change it) expect there is no access to app list. You can click on navi button - which holds no navigation software funny enough. Once inside the navi button you can hold on the screen and then it brings you up a app selection screen giving you option to add icons(still no gps map softwares)
Once connected to Internet apps start updating when you open them which is pretty cool.. There is an update option under andriod version screen which fails to find any update with an error(searches Internet for update or you can local upload file).
Overall I'm pretty impressed with this device and its speed. I was able to install google maps by browser. But once I closed it I could not open it again cause no icon to click on. Google maps ran a little bit sluggish but was acceptable. I'm now chasing the seller for a solution to google play store as the play store ask won't open after installing.

I was able to side load apps quite easily with the browser. Seems most work if the don't depend on play store or accounts being setup in google settings.
Synic gps software won't work as it wants to use playstore to download more files.
Es explorer works fine.
I don't think I will be able to get root access as there is no developer menu, but after clicking on firmware build number says you are already a developer

i have this one and have Google playstore, i have installed nova launcher without problem, all is fine

Hi, is it model rt01?
Do you have the same firmware 4.4.2 and specs?
Does it have an option to add google account inside android OS?
As mentioned above no google account in my OS which means no history in google maps. Very frustrating.
Could I also grab the seller as I my have to purchase a new one
Thank you if you can help

hello, i bought mine to this seller from Aliexpress, received in 8 days via DHL
http://fr.aliexpress.com/item/5-inch-Android-Mirror-Monitor-GPS-1080P-Digital-Video-Recorder-Rear-view-Camera/2021095296.html
The item has exactly the spécifications as described from top of topic and is a rt01 model, else allwinner A23 Inside, android 4.4.2 KitKat Inside
i have in native Google playstore and i have created my account without problem as soon as i powered up for the firs time the mirror
best regards

Thanks for your help appreciated.
Need to try a scab a firmware update as my seller refuses to speak with me now.
Might just buy what you got I think.

you can try to communicate via aliexpress with the store, seller is Mr wilson cao and ask him for a firmware, it's a pleasant person who respond to me very fast, also after my purchase for details. Try to say you're a friend of me (Superboost) and have same miror and you want the same OS, give a try, good luck.
---------- Post added at 06:38 PM ---------- Previous post was at 06:32 PM ----------
at this time i'm trying to root for install some progs. Framaroot = KO, kingroot not able to connect at his cloud for exploit. At this time not result. If i can, also put a twrp or other and save firmware and tranfer to you? Have an idea of rooting ?

I have seen a update.zip file for root on the net. I was thinking doing it that way.
I'll give it another go as I was more focused on gapps.zip before.

Do you have development option to activate usb debugging? I don't have this option, so it makes it hard for me.
That's why I suggested an update.zip method.
If you have usb debugging (lucky you) then try http://www.shuame.com/en/root/
Also sent a msg to your seller. I think he would have to be very nice to give time for nothing being a business man

I have not the "usb debugging option" and no more the menu security for the possibility to "accept unknown sources" option. I think it will be impossible to root the item.....
tell me if you have a response from seller, have a good day

I was going to try to enable usb debugging by a terminal command but gave up after I couldn't install gapps
Try this maybe
http://forum.xda-developers.com/showthread.php?t=893434

hello, i have installed usb drivers of the mirror (hold down volume button and plug USB) and found an unknown device, i downloaded livesuit pack V1.9 and in the usb directory, it found the driver.
Now i can lauch livesuit but it wait for an .img image file for flash.... that's all for this time.... perhaps a way for future rooting?, have a good day

Your seller is very nice.
Thank you also.. Now have to work out how to install
This is a link I found on google
http://pan.baidu.com/wap/link?uk=4026862827&shareid=3212962299&third=0
Link from your seller
http://en.mail.qq.com/cgi-bin/ftnEx...1e4459433274&t=exs_ftn_download&code=231c0681

hello, happy for you, i expect you can flash this firmware and having opérationnal Google on it.
This seller is very nice, i put it a 5+++++ stars on aliexpress
have a good day

It's a puzzle..
You have an img file.. And Phoenixcard..
Putting in sdcard and selecting startup it puts the android OS on the sdcard and you boot from that so you can test the image I suppose.
Could not see any google account. Also I have alarm next to the radio icon. When I put this one on I got the browser instead.
Can I ask under settings about tablet is your build number 20150410 ?

in the info i have : rt01-eng 4.2.2 KVT49L 20150410 test-keys
It's seem that is the same build than downloaded
perhaps puting applications in "download" folder of the program will put them on the image for flashing ?

Thank you so much. You are a legend.
Its as I figured.
running the phoniexcard program you select Startup to run off sdcard.. which is way slow.
So I took the plunge and hit production and it setup my sdcard which in turn updated my unit.
Now its usable and I cant thank you enough!

have you all you want in ? Google account possible? the next challenge : rooting...
---------- Post added at 01:24 PM ---------- Previous post was at 12:45 PM ----------
Because it's difficult to find this firmware, i put it on a Mega download
https://mega.co.nz/#!ZEwxzAyJ!HzowmA3-bVbcCdZpY7tHsQ5sV2kLQ8d6lwX6Y4Q0IXY
It include the program Phoenixcard for generate the bootable SD card for update firmware
for someone else who search

Yes rooting is on the cards now...
Just enjoying play store for the moment..
Plus I've noticed a huge increase in speed.
Large improvement in firmware need to keep eye open for future releases

USB-OTG app access in Nougat - solution?

I decided to start a new thread about this since I have been searching high and low in the forum about this particular issue. I copy and paste my post I wrote in the RR thread since I think it is worth to bring it to more public attention.
I also found some comments on this very issue in the Redmi Note 3 Kenzo forum about Nougat/RR 5.8.2 and in other forums (about nVidia Shield) as well. The basic issue is about app access (Kodi for example) to USB-OTG flash drives. It also affect MX Player and FX File Explorer. Here is my earlier post:
There is one thing I would like to point out - perhaps a solution can be found:
App access to external USB flash drives
Nougat and some ROM/kernel combinations seems to act differently than Marshmallow in this regard - it cause some issues with Kodi (as one example) and also some file managers (FX File Explorer). The symptoms are:
1. USB flash drives doesn't show up as 'regular' storage volumes in FX (the app demand the user to 'connect to the drive' and insist on transferring every file in order to view them - videos is a typical example). It happens with Root Explorer as well in some cases.
2. Kodi is unable to access a USB flash drive. It can navigate the file tree down to the /mnt/media_rw but is unable to access the drive itself (i.e. nothing happens when selecting media_rw).
3. StickMount doesn't help either - the USB disk remains inaccessible for Kodi and FX.
Apps such as MiXplorer and Files (the native file manager, not the CM one) is able to manage the USB disk properly.
The ajmsg78 packaged RR 5.8.1 with Nebula v1 seems to operate similar to Marshmallow in this regard - FX File Explorer and Kodi are able to treat a USB disk in the same way as a memory card (browse files, selecting a folder as a Kodi source etc).
It only works on that particular ROM/kernel combo - flashing Nebula v2 or Harfix R2 immediately change the storage access (i.e. FX want to 'connect to storage' and Kodi loose the ability to access the disk).
I think the main issue is the way Nougat handles app access to those disks. There are no problems with accessing the regular microSD card - Kodi and FX are able to handle it perfectly well. It is only when a USB flash drive is connected that the problem arise.
The easiest way of checking it is:
Install FX File Explorer and/or Kodi. Connect a flash drive and see if it shows up in FX and/or become accessible in the Kodi file browser. If FX want to 'connect' to storage instead of simply mounting it or Kodi is unable to browse it - then the issue is present.
There are something in the ajmsg78 packaged RR 5.8.1 by marchetto96 with Helium fixes including Nebula v1 that make it work. Flashing another kernel (Nebula v2 or Harfix) revoke the access. StickMount doesn't help. So there are something special about the Nebula v1/RR 5.8.1 combination (I don't think it is the ROM itself but the kernel - flashing that ROM version with Harfix R2 before setting it up means no USB flash drive access).
It would be interesting if a solution can be found. I have been trying the latest Kodi 18 Leia nightlies without success (can't browse the media_rw). SPMC (the Android fork based on Kodi 16) is also unable to get such access.

Tested in LAOS by Nijel8 on default kernel.
My experience with Kodi is as follows:
After inserting usb_otg drive...
- when I access the usb_otg and in the popup from MiXplorer do not allow it to mount the drive but from notifications select Android system>drive name>Explore> and select the new drive , then enter root explorer and in there I tap the file to be played > select Kodi to play it, it does not work (files are present in /mnt/media_rw/xxxx-xxxx/)
- when I insert usb_otg and in the popup from MiXplorer allow it to mount the drive, it is invisible in /mnt but visible in MiXplorer, furthermore when I tap the file to be played in there and select Kodi, it plays correctly. But the drive and it's content is invisible to the system and other apps. It does not seem that the files are copied to internal storage as opening 3GB movie from usb (mp4 file format) took only 7 seconds.
MiXplorer has a custom driver for USB OTG,
{
"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"
}
and Kodi just isn't compatible with new permission system present in Android 7 (or 7.1.1 as the case here).
Also even with the custom driver, usb_otg drive is not visible in Kodi and files must be started in MiXplorer.
If the kernel allows for old-style mounting of external storage then Kodi will work (AFAIK).

This seems comparable with my own results. MiXplorer work perfectly.
I am back on the RR 5.8.1/Nebula v1 combo packaged by ajmsg78 - it seems like that particular kernel is the key for success. Kodi are able to browse the file tree and reach the disk under /usbstorage/xxx-xxxx, which is the issue otherwise.
It feels like this is a major issue for several apps under 7.1.1 and it would be great if it is possible to make newer kernels that allow the older mounting mode, at least until there are clear indications that the new permission model is properly managed.
It is important to notice that Kodi have no issues whatsoever with internal microSD cards. It can navigate them properly - the issue is only when a USB flash drive is being used.
Edit: FX File Explorer is the other app with issues - it can access the drive but insist on transferring files for playback. It just can't play them directly because of its insistence on 'connecting to the drive' like it is a remote volume or something.

Just trying to contribute a little (I'm no developer!). The only way my galaxy t810 (nougat) recognized the USB stick is when I change the USB configuration of tablet to rndis (USB ethernet). Don't know why! But only work for pendrives, still doesn't work for my HD (even with root and with paragon or any other app). Didn't tested with accessories (like a mouse).
Update: stop working...

I've (finally!) got app access to usb-otg using stick-mount, it mounts it at '/storage/emulated/0/usbStorage/sda1' and is accessible to every app I've tried so far (inc Fx), I don't use kodi so I can'check that. I'm using ResurrectionRemix 5.8.5(latest ver) with Elemental kernel.

Sausageandeggs said:
I've (finally!) got app access to usb-otg using stick-mount, it mounts it at '/storage/emulated/0/usbStorage/sda1' and is accessible to every app I've tried so far (inc Fx), I don't use kodi so I can'check that. I'm using ResurrectionRemix 5.8.5(latest ver) with Elemental kernel.
Click to expand...
Click to collapse
Elemental kernel!?

Sorry! Elemental X 'elementalx.org'

Sausageandeggs said:
Sorry! Elemental X 'elementalx.org'
Click to expand...
Click to collapse
Not that... You must be in wrong device forum... We don't have ElementalX kernel...

uConnect 6.5 (Alfa / Fiat) Root Access

I thought i would start this thread, separate to the Jeep one as the Jeep thread is for the 8.4" uConnect and uses some different files to the 6.5" version.
The aim of the thread is to be able to gain some sort of 'root' access to the file system to be able to update the maps on the system. So far I know cm0002 and Leighm0 have done some great work with the 8.4" - Most of which we can use on the 6.5".....once we have access to the file system.
The problem we seem to be facing is finding a swdl.iso that is old enough to be modified for our 6.5" units.
Mission Accomplished.... mostly
Disclaimer: I can not be held responsible for any damages to your uConnect, Car or your hair falling out from running this modification.
That being said, if you do have a problem please contact me and I will see if I can help you fix it.
For all those people still on v17.07.46 or older uConnect 6.5 firmware I offer you a “jailbreak”, you can now update your maps to the latest versions (currently offering EU 2018Q3 / NA 2018Q1 in my pack). I have to warn you though, the process can take a lot of time!
For those of you who have updated your 6.5 uConnect to v17.35.41 or v18, I am still working on how to update those, FCA / Alfa changed the locks with that update!
For a Full EU / NA update, if you follow my instructions fully, it will take approx. 4hours during which time your uConnect must remain powered on. This time can be greatly reduced by only updating the country or countries you need, or if you are feeling brave, skipping Step 1.
Files / Items needed:
uConnect 6.5 running v17 or older firmware -Supporting Alfa, Fiat and Jeeps too!
At least 8gb USB Drive ***preferably with a flashing led light so you can see file access***
Files from
https://mega.nz/#F!kURhTCbJ!uJhKPMyGiESbvQSDb33CvQ
Stage 1 – Backup your files
Download:
1 Magic -Alfa pre UPD.zip -For Alfa
1 Magic -Fiat & Jeep pre UPD.zip -For Fiat / Jeep
2 Backup.zip
Process:
1. Download and expand “1 Magic -XXX.zip” and “2 Backup.zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, in my case it took 1h25 to complete this stage, it should popup a window about there is a update that you MUST answer NO to
6. Pull USB, and power cycle the uConnect*
After that you now have a backup of all the system and map files we are going to change on your uConnect.
KEEP THEM SAFE!
Either use a second USB for stage 2, save the backup folder to your computer or if your like me and use a 16gb USB stick you can leave it where it is.
I have now uploaded copies of the official EU Map Packs from (A) 2013, 2015 and 2017, NA Map Packs (B) 2013, and ROW Map Packs (C) WIP that will function as a backup or official upgrade for anybody needing them, restoring your uConnect back to stock.
***If you have a newer set of Original Map files please contact me, and I can add them to the drive for all to benefit from***
Stage 2 – Modify your uConnect
Download:
1 Magic.zip --You should already have this if you completed Stage 1
D EU Custom 2018 HNEU2018Q3v2.zip --Full EU
E NA Custom 2018 HNNA2018Q1.zip --Full North America
Or
D UK Custom 2018 HNUK2018Q3.zip --UK Only
D FR Custom 2018 HNFR2018Q3.zip --France Only
D DE Custom 2018 HNDE2018Q3.zip --Germany Only
D IT Custom 2018 HNIT2018Q3.zip --Italy Only
***There will be other country / State only update packs soon***
Or
A EU 2013 Original NQEU2012Q4.zip --Stock 2013 Maps, Original EU Release
A EU Update 2017 HMEU2015Q4.zip --Newest Original Map files released 2017
B NA 2013 Original NQNA2013Q4.zip --Stock 2013 Maps, Original NA Release
Process:
1. Download and expand “1 Magic.zip” and “D XX Custom 2018 HN….zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx. 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, depending on file used - If country / State only pack approx. 15min if full EU then approx. 2h, it should popup a window about there is a update that you MUST answer NO
6. Pull USB, and power cycle the uConnect*
If all gone well you will now have a uConnect 6.5 with updated maps!
As I am sure you can understand, there are still some little bugs to work out;
Problems:
UK postcodes > Only 5 digit search
Speedcams > Not working at all
Anything else… you tell me
Fixed:
UK TMC now working
France TMC working again
Italy TMC (paid version) working
There may be other little problems, but I am unable to test them, please let me know and I will look into them and try to fix!
*To Power cycle:
Either remove key, lock car, wait 10min, unlock and restart)
Or use engineers menu to reset the uConnect (Press Radio, More and Browse until menu pops up, scroll down to Reset Radio, answer YES)

I have uploaded some of the files, more to come.
The URL:
https://mega.nz/#F!kMYjlSKB!MCC6U1jclb0_aHc-NdocrA
If you have anything else to share please message me.

So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!

Jeep Renegade
Hi.
It is possible in jeep?

SquithyX said:
So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!
Click to expand...
Click to collapse
any news?

Update....
The 15.18.xx file is ROW and after modifying it to work for any model, I get a authentication error on inserting the USB!!!!

Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!

Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?

Icaro03 said:
Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!
Click to expand...
Click to collapse
I can upload for you if you want, however until I hack has been found to be able to modify the system, they will not work!
Sent from my CLT-L09 using Tapatalk

andri98 said:
Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?
Click to expand...
Click to collapse
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got.
{
"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"
}
Sent from my CLT-L09 using Tapatalk

it would be great to see some development on this system

SquithyX said:
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got. View attachment 4611300
Click to expand...
Click to collapse
I found a datasheet searching JY455
It seems to be an eMMC Memory from Micron (MTFC??GLGDM) with a build in MMC-Interface
Maybe it works like an MMC-Card.
If someone build an adapter for the white connector and USB, maybe we can read and write the flash like an MMC-Card on an USB reader.

for you may this works for really? have a look for "Alfa Romeo Giulietta UConnect Apple CarPlay & Android Auto retrofit Kit" in a search engine. it's very expensive but they say you can use touch screen as well to interaction when usually all the video interface i have found say not possbile, only video signal. what do you think about this?

So close, but broken lol
Success......kind of, I have managed to modify a swdl.iso to enable loading of different / modified files, on my Alfa 6.5 uConnect running 17.07.55.
The problem now is I seem to have completely broken navigation!!!!!!
I used the idea from post #216 in the Rooted Jeep Cherokee thread and modified the manifest.lua file in the swdl.iso (17.07.55) to load a script from usb before running the update.
Process goes power on uConnect > wait for it to boot up and display "Hands free ...." > insert USB and wait...it seems like its not doing anything but the script is running in the background > after some time the do you want to update question and answer No.
The fact that is has asked if you want to update is confirmation that the script has finished, however unfortunately there is no indication that the script is being run or how long it will take unless you have a usb with a flashing light, then it will show you something is happening at least! **my usb does not have a flashing light
I tested it with a splash screen update.... that worked perfectly, so no more boring Alfa Romeo logo on silver background for me at start up, I then pushed the modified NaviServer2, nav.sh and navRestart.sh files and rebooted.... new splash screen working perfectly but on pressing Nav button I just end up on a screen saying "Activating Navigation"
I am in the process of uploading the modified files to the mega share if anybody whats to have a look or are feeling brave

Navigation now fixed! working on making a 2018q2 map pack for it now.

SquithyX said:
Navigation now fixed! working on making a 2018q2 map pack for it now.
Click to expand...
Click to collapse
Really????' you are the MAN! could you please share everything you have used and step by step? do you think even with firmware 18 installed is possible updating maps?
thanks

Ok, here is a test image (working with v17 and earlier.... unknown for v18).
https://mega.nz/#!IUZDQATI!o1OBd8qbA...mQ5lunDb0opDvs
For anybody wanting to try it, and let me know the outcome.
The script I have included will:
Backup your MAPS license files to the USB
Backup your original Alfa Splash Screen to the USB
Copy a dbver file to the USB, that should contain information about your version of MAPS installed
Push the modified Splash screen and set its properties on the uConnect
Steps:
1. Download and expand
2. Copy onto USB drive (at least 4gb) ***preferably with a flashing led light so you can see file access***
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and hope
5. After some time it should popup a window about there is a update (with v17) that you answer NO to. With v18 i dont know what it will do, it may popup a window saying newer version installed, Error or maybe not do anything at all.
If that is the case use the led on the usb to make sure no file access is going on and then maybe wait 5 min extra, just to make sure.
6. Pull usb, and power cycle the uConnect - either power off the car (lock car, wait 5min, unlock and restart) or use engineers menu to reset the uConnect
7. Watch it boot....the boot image will be different if success!!!!! (there will also be some new files on the usb)
It is very important NOT to let it run the update, if it offers

I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!

SquithyX said:
I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!
Click to expand...
Click to collapse
did you modify the swdl.iso? or just the script.lua?

sofro1988 said:
did you modify the swdl.iso? or just the script.lua?
Click to expand...
Click to collapse
I have used a modified 17.07.55 swdl.iso with a script.lua - if you download the test above it contains some of the modified files. The rest are currently being uploaded / are already available online.
I have done a very quick video of progress with the uConnect here:
https://youtu.be/ed0O-xXNHdg

[DEV][ROM][UNOFFICIAL] LineageOS 18.1 (Android 11) for Raspberry Pi 4 B

Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.
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.
{
"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"
}
LineageOS 18.1 (Android 11)
for Raspberry Pi 4
konstakang.com
There is also Android TV version available.
LineageOS 18.1 Android TV (Android 11)
for Raspberry Pi 4
konstakang.com
Working:
Audio (HDMI, 3.5mm jack, 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)
HDMI display (and HDMI-CEC)
I2C
IR remotes (using external GPIO IR modules e.g. TSOP4838)
RTC (using external GPIO I2C modules e.g. DS3231)
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 (USB touchscreens, Waveshare SPI touchscreens)
USB (mouse, keyboard, storage, etc)
USB-C (ADB, MTP, PTP, USB tethering)
Wifi (and wifi tethering)
Not working:
Hardware video decoding & encoding (software decoding & encoding works)
Issues:
Stock camera app is not working - many third party camera apps seem to work
SELinux is in permissive mode
and more…
Sources:
kernel
Thanks:
Peter Yoon and android-rpi project
Roman Stratiienko and GloDroid project
AOSP reference board developers (dragonboard, hikey, yukawa)
E. Anholt for V3D graphics driver
Maxime Ripard for Pi 4 KMS driver
Android-x86 project
LineageOS team and everyone who has contributed to LineageOS 18.1

How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card.
If you’re running a recent build (20220121 or newer) 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-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-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-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-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
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/rpi4/LineageOS18/
https://konstakang.com/devices/rpi4/LineageOS18-ATV/

Merged commits not mentioned in the changelog.
12.5. changelog:
also available as OTA package
add support for Compute Module 4
fix DAC audio device selection on CM4 & Pi 400 that don’t have 3.5mm audio jack
fix USB storage (Pi 400 as well?)
add support for the RTC on the I/O board
use OTG mode for USB to support ADB, MTP, PTP, USB tethering on the micro-USB port on the I/O board
update boot firmware for newer Pi 4 hardware revisions
various drm_hwcomposer updates e.g. support for headless mode (thanks to Roman Stratiienko)
automatically set density based on display resolution
add support for APDS9930 ambient light/proximity sensor
update to TWRP 3.6.1_11-1-KonstaKANG
update to Mesa 21.3.8
update to Linux 5.4.191 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 May 2022 (merged)
21.1. 2022 changelog:
fix reboots related to Hotspot 2.0 networks/ANQP requests (see issue #6)
Vulkan 1.1 (thanks to people at Igalia for Vulkan 1.1 conformance and Roman Stratiienko for latest Mesa fixes)
add new options to Raspberry Pi settings (force rotation & CPU governor)
prepare for OTAs
update to TWRP 3.6.0_11-1-KonstaKANG
update to Mesa 21.3.4
update to Linux 5.4.173 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2022 (merged)
23.11. changelog:
add support for BME280/BMP280 temperature/pressure/humidity sensors
add option to select HDMI-CEC device
add option to show virtual volume down, volume up, and power keys on navigation bar
add option for old TCP-based ADB over network
show IP address and port for ADB/SSH/VNC options
fix resizing data partition that broke with previous build
update to TWRP 3.6.0_11-0-KonstaKANG
update to Mesa 21.3.0
update to Linux 5.4.161 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 November 2021 (merged)
26.10. changelog:
switch to 64-bit kernel & userspace
switch to minigbm gbm_mesa and [email protected] API (thanks to Roman Stratiienko)
update to Mesa 21.2.4
update to Linux 5.4.155 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
11.10. changelog:
add support for Vulkan
rework bluetooth (thanks to android-rpi)
update to Mesa 21.1.8
update to Linux 5.4.152 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 1 October 2021 (merged)
20.7. changelog:
switch to using HDMI-CEC HAL
update to Mesa 21.1.5
update to Linux 5.4.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 July 2021 (merged)
11.4. changelog:
add initial support for HDMI-CEC
add built-in VNC server
update to Mesa 21.0.2
update to Linux 5.4.111 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 April 2021 (merged)
14.2. changelog:
add support for LSM303DLHC accelerometer & magnetometer sensor
add separate TWRP flashable su add-on (see FAQ)
allow switching display off with power button
add support for USB-C (ADB, MTP, PTP, USB-tethering)
enable bluetooth tethering
add settings option for mouse back button feature
update to TWRP 3.5.0_9-0-KonstaKANG
update to Mesa 20.3.4
update to Linux 5.4.98 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 February 2021 (merged)
4.1. changelog:
initial LineageOS 18.1 build
add support for sensors (LSM6DS3 & MPU6050 accelerometer & gyroscope on I2C)
add support for more serial USB GPS devices
drop support for SwiftShader software renderer which also means dropping support for the official 7” touchscreen for now
update to Mesa 20.3.2
add option to switch between gbm and minigbm gralloc
update to TWRP 3.4.0-2
update to Linux 5.4.86 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 December 2020 (merged)
Previous builds:
AndroidFileHost

Will you share an atv variation 18.1?
Thanks for your hard work.

onukomer said:
Will you share an atv variation 18.1?
Thanks for your hard work.
Click to expand...
Click to collapse
What does Android TV 11 offer that is not already available in the latest Android TV builds for the Pi 4 (https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/)? Yeah, I know - big version number, much WOW! But besides that, what's the point?
From user perspective I highly doubt you're going have the slightest clue whether you're running Android TV based on Android 8, 9, 10, or 11 unless you go specifically into the about device settings. Android TV builds are also pretty much useless without installing Google Apps. There's currently hardly any working Android 11 gapps packages available and there's certainly no Android TV gapps for Android 11.
From technical perspective I'm currently not aware of any reason why Android TV 11 builds wouldn't work just as much as before but there's just not going to be much reason for it in a long long time.

KonstaT said:
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.
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!
https://konstakang.com/devices/rpi4/LineageOS18/
lineage-18.1-20210104-UNOFFICIAL-KonstaKANG-rpi4.zip
https://www.androidfilehost.com/?fid=17248734326145708986
md5:4775eb4b2a89859ebf4d16dbf306cea2
Working:
Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)
Bluetooth
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)
HDMI display
I2C
IR remotes (using external GPIO IR modules e.g. TSOP4838)
RTC (using external GPIO I2C modules e.g. DS3231)
Sensors (using external GPIO I2C modules e.g. LSM6DS3 & MPU6050 accelerometer & gyroscope)
Serial console (using external GPIO serial console adapters e.g. PL2303)
SPI
Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens)
USB (mouse, keyboard, storage, etc)
Wifi
Wifi tethering
Not working:
Hardware video decoding & encoding (software decoding & encoding works)
Issues:
Stock camera app is not working - many third party camera apps seem to work
SELinux is in permissive mode
and more…
Sources:
kernel
Thanks:
Peter Yoon and everyone who has contributed to android-rpi
Roman Stratiienko and GloDroid project for graphics fixes
brobwind for bluetooth fixes
Eric Anholt for V3D graphics driver
Maxime Ripard for Pi 4 KMS driver
Android-x86 project
LineageOS team & everyone who has contributed to LineageOS 18.1
Click to expand...
Click to collapse
BITGAPPS ARM Android 11
BiTGApps-arm-11.0.0-R19_signed.zip
drive.google.com
Its portability is incredible, everything works fine, but the only problem I'm having is that version 17 and 18 doesn't work with the mouse in the GeForceNow application, the right button just doesn't work. I tested the OMNI Android 11 version and it works perfectly, however it is full of bugs and poorly optimized. Can you fix this for us? Having a Raspberry PI 4 that works GeForce Now is incredibly awesome!
Another suggestion is how to disable the physical keyboard shortcut keys like F1-F5, because when we try to play on GeForce Now they simply close the application, at least give a function to remap the buttons.

dhtm15 said:
Its portability is incredible, everything works fine, but the only problem I'm having is that version 17 and 18 doesn't work with the mouse in the GeForceNow application, the right button just doesn't work. I tested the OMNI Android 11 version and it works perfectly, however it is full of bugs and poorly optimized. Can you fix this for us? Having a Raspberry PI 4 that works GeForce Now is incredibly awesome!
Another suggestion is how to disable the physical keyboard shortcut keys like F1-F5, because when we try to play on GeForce Now they simply close the application, at least give a function to remap the buttons.
Click to expand...
Click to collapse
If it helps md5sum for BiTGApps-arm-11.0.0-R19_signed.zip I've used to test is 299182a2d72b977a04360439ed06db8a. It's of course entirely your decision if you trust a download source you can find. You can find more mirrors e.g. in the BiTGApps XDA thread (https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/).
My recent builds map right mouse button to back key. Are you saying that there's Android apps that actually make a difference between left/right mouse clicks? I could add a setting option for that feature in future releases (that's actually already been on my endless list of TODOs).
You can revert to the default keyboard mappings by removing /vendor/usr/keylayout/Generic.kl (or edit that file to change the keymappings to whatever you want).

KonstaT said:
If it helps md5sum for BiTGApps-arm-11.0.0-R19_signed.zip I've used to test is 299182a2d72b977a04360439ed06db8a. It's of course entirely your decision if you trust a download source you can find. You can find more mirrors e.g. in the BiTGApps XDA thread (https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/).
My recent builds map right mouse button to back key. Are you saying that there's Android apps that actually make a difference between left/right mouse clicks? I could add a setting option for that feature in future releases (that's actually already been on my endless list of TODOs).
You can revert to the default keyboard mappings by removing /vendor/usr/keylayout/Generic.kl (or edit that file to change the keymappings to whatever you want).
Click to expand...
Click to collapse
I think I saw something related to this, that the function of the right mouse button when programmed to return can affect applications that use the right button, this is the case with GeForce Now, which does not recognize the right mouse button in any way, all other buttons are functional. I also tried to see how to remap the keyboard buttons and tried to change these files by adding another one, but it didn't solve the problem, I opened it to edit and I didn't find the F1 function until F5, can you show me where exactly i can edit to remove this?
I found this GApps on the 4PDA forum, I think it's safe because it was a topic dedicated to that.
edit: Correction, I had entered the / root / system / usr / keylayout folder so I hadn't seen the changes.

dhtm15 said:
I think I saw something related to this, that the function of the right mouse button when programmed to return can affect applications that use the right button, this is the case with GeForce Now, which does not recognize the right mouse button in any way, all other buttons are functional. I also tried to see how to remap the keyboard buttons and tried to change these files by adding another one, but it didn't solve the problem, I opened it to edit and I didn't find the F1 function until F5, can you show me where exactly i can edit to remove this?
I found this GApps on the 4PDA forum, I think it's safe because it was a topic dedicated to that.
edit: Correction, I had entered the / root / system / usr / keylayout folder so I hadn't seen the changes.
Click to expand...
Click to collapse
Yeah, I checked the md5sum and it's the same what I have for the file I downloaded about a month ago.
I uploaded a TWRP flashable patch that will restore the default mouse button behavior and adds an option to Settings -> System -> Advanced settings to enable back key on right mouse click.
Edit. removed, not needed with latest builds anymore.
Deleting custom Generic.kl from vendor partition will use the default unmodified one from system partition. These are the changes that have been made https://github.com/lineage-rpi/andr...001-rpi3-modify-generic-keyboard-layout.patch

Hello, I try to use this great rom (and others) since 3 days with my PI4 , and "Location" (with waze and maps) never works instead of version 17.
Someone knows why ?
Thank you

Enable root access, was a switch under developer options in 17.1 nowhere to be found in 18.1. Tried flashing a SU from TWRP, nothing shows up. Am I missing something here?

myspac said:
Hello, I try to use this great rom (and others) since 3 days with my PI4 , and "Location" (with waze and maps) never works instead of version 17.
Someone knows why ?
Thank you
Click to expand...
Click to collapse
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
williamparker said:
Enable root access, was a switch under developer options in 17.1 nowhere to be found in 18.1. Tried flashing a SU from TWRP, nothing shows up. Am I missing something here?
Click to expand...
Click to collapse
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.

Thank you for your answers !
KonstaT said:
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
Click to expand...
Click to collapse
Oh.. yes, I mean Google network location; so , the problem is on gapps: Ok, thank you. I use : open_gapps-arm-11.0-nano-20210104-UNOFFICIAL_TEST.zip, it was ok with open_gapps-arm-10.0-pico-20201223.zip and your "17 version". I m trying other rom (OMNI) with other gapps and I had the same specific problem: that's why I think it was a "18 rom" 's problem...
KonstaT said:
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.
Click to expand...
Click to collapse
I have and need root access, but it was ok with the FAQ.

Hello,
In Linphone, Bria, ... I can't use my USB microphone (no recorded sound), but it works well in a voice recorder application.
It is also not possible to choose a ringtone.
Do you have an idea about the microphone problem?
Thank you for your work

KonstaT said:
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.
Click to expand...
Click to collapse
Ok, this is my last tests, all without gapps:
- I take your last rom
- connect an hardware gps by bluetooth
- install by adb the app "GPS Bluetooth" to mock the location
- install waze (by adb)
- install maps (by adb)
After:
- MAPs works
- WAZE: my location is ok but the map is not displayed: I didn't know why (if works with your rom 17).
I took an old waze version: and after re set all permission in the app setting AND by Privacy menu (not same permission when I cick on All permission of waze!!!! ???) => it was Ok too, location and map.
I re take last Waze version, but I never success to display map.
In data/wifi usage of the waze app: 0 ko !!!!
I don't understand why some applications (Android Auto too) can't access to network and why permissions are not the same by app's info and by Privacy setting menu. (It was ok with version 17 of your rom).

KonstaT said:
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, ageOS team & everyone who has contributed to LineageOS 18.1
Click to expand...
Click to collapse
awesome work! i was reading your work and i have a question if you or anyone can chirp in too for ideas.
whats the benefit besides privacy using your build of lineage over raspberrys os?
if it were used offline as storage, but wake on lan when needing access using nextcloud or people recommend nextcloud alternative? also emails nextcloud isnt e2ee, but Tutanota is but i dont think its capable running on nextcloud.
some personal some work so transfering to devices its main purpose is security. maybe running a work chat system e2ee which will also be safer than online apps out there.
TLR: dont want to pay for storage cloud, messaging services online for work when we can do it ourselves and overall safer from uninvited guests

Thanks for this ROM! I understand a lot of stuff here is still experimental, but I look forward to trying this out. I will be getting a 5-inch touch screen next week sometime so I also plan to test performance with it (it's only 800x480, so not driving millions of pixels with the Pi either.) If I had to estimate, the Pi 4 is about as fast as a Galaxy S5 or S6 was, slightly slower than a snapdragon 820. So it's not midrange or high-end, but I think it is more in the upper parts of the low range in terms of raw performance. You can safely boost the clock to 2.2 gHZ, which works well provided you have the thermal cooling to do it without a throttle. I also use a Pi 400. The Pi 400 runs a lot cooler even at the default 1.8, and I have safely pushed it to 2.2. It makes it slightly faster but not a major boost in Android by any means.
If others have had experience getting the USB Type C working on this rom, let me know. I understand it's commented in config.txt, so I plan to uncomment it there and look in /vendor/etc/init/hw/init.rpi4.rc to change it also with my Ubuntu machine. I'm fully blind, so using ADB on this to get talkback working is essential. So far I have used the network boot to do this, installed both an APK for Google TTS and Talkback, got it working just fine after adding values to securesettings. Great news. At least for now, new users wanting ADB access should connect their Pi through ethernet and then connect to ADB over the network, I think this is easiest. I have a USB type C hub here which is powered so I'm able to hook the Pi directly to my computer and do it that way a bit easier than fiddling around in the router for this stuff, and maybe more secure as it is only over USB. But the network way is probably easier for more folks to get going as well. Ups and downs, just as everything to life, right?
I also am wondering if we can get USB ADB over TWRP. This would be a huge win but I will test this and report back on this thread. Again, my only choice is to use openrecovery scripts, not really to find a sighted pair of eyes and ask them to help out reading the TWRP screens. I actually don't have that help available at the moment as my partner and I are both blind. So everything I get to do I have to do in a commandline or speaking way. But I think even despite those odds, this is doable and the disabled need to push ahead in this space anyway if they too want to be tinkerers as it is.
Thanks for working on this and making Lineage accessible to many. It's been yours and other Pi community hardware enthusiasts' effort which got this up and running. I was actually able to get one of the Pi3 builds you posted running with Talkback but at the time I just didn't find the Pi 3 that good for running Android. Certainly not with 1 gig of ram, something the Pi 4 gives us a lot of choice with at least.

Micka41 said:
Hello,
In Linphone, Bria, ... I can't use my USB microphone (no recorded sound), but it works well in a voice recorder application.
It is also not possible to choose a ringtone.
Do you have an idea about the microphone problem?
Thank you for your work
Click to expand...
Click to collapse
It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.
There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.
myspac said:
Ok, this is my last tests, all without gapps:
- I take your last rom
- connect an hardware gps by bluetooth
- install by adb the app "GPS Bluetooth" to mock the location
- install waze (by adb)
- install maps (by adb)
After:
- MAPs works
- WAZE: my location is ok but the map is not displayed: I didn't know why (if works with your rom 17).
I took an old waze version: and after re set all permission in the app setting AND by Privacy menu (not same permission when I cick on All permission of waze!!!! ???) => it was Ok too, location and map.
I re take last Waze version, but I never success to display map.
In data/wifi usage of the waze app: 0 ko !!!!
I don't understand why some applications (Android Auto too) can't access to network and why permissions are not the same by app's info and by Privacy setting menu. (It was ok with version 17 of your rom).
Click to expand...
Click to collapse
It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.
There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.
entwicklun said:
awesome work! i was reading your work and i have a question if you or anyone can chirp in too for ideas.
whats the benefit besides privacy using your build of lineage over raspberrys os?
Click to expand...
Click to collapse
I guess the main benefit is that it's a completely different operating system. It's Android - it runs Android applications.
htc_Tomi said:
Thanks for this ROM! I understand a lot of stuff here is still experimental, but I look forward to trying this out. I will be getting a 5-inch touch screen next week sometime so I also plan to test performance with it (it's only 800x480, so not driving millions of pixels with the Pi either.) If I had to estimate, the Pi 4 is about as fast as a Galaxy S5 or S6 was, slightly slower than a snapdragon 820. So it's not midrange or high-end, but I think it is more in the upper parts of the low range in terms of raw performance. You can safely boost the clock to 2.2 gHZ, which works well provided you have the thermal cooling to do it without a throttle. I also use a Pi 400. The Pi 400 runs a lot cooler even at the default 1.8, and I have safely pushed it to 2.2. It makes it slightly faster but not a major boost in Android by any means.
If others have had experience getting the USB Type C working on this rom, let me know. I understand it's commented in config.txt, so I plan to uncomment it there and look in /vendor/etc/init/hw/init.rpi4.rc to change it also with my Ubuntu machine. I'm fully blind, so using ADB on this to get talkback working is essential. So far I have used the network boot to do this, installed both an APK for Google TTS and Talkback, got it working just fine after adding values to securesettings. Great news. At least for now, new users wanting ADB access should connect their Pi through ethernet and then connect to ADB over the network, I think this is easiest. I have a USB type C hub here which is powered so I'm able to hook the Pi directly to my computer and do it that way a bit easier than fiddling around in the router for this stuff, and maybe more secure as it is only over USB. But the network way is probably easier for more folks to get going as well. Ups and downs, just as everything to life, right?
I also am wondering if we can get USB ADB over TWRP. This would be a huge win but I will test this and report back on this thread. Again, my only choice is to use openrecovery scripts, not really to find a sighted pair of eyes and ask them to help out reading the TWRP screens. I actually don't have that help available at the moment as my partner and I are both blind. So everything I get to do I have to do in a commandline or speaking way. But I think even despite those odds, this is doable and the disabled need to push ahead in this space anyway if they too want to be tinkerers as it is.
Thanks for working on this and making Lineage accessible to many. It's been yours and other Pi community hardware enthusiasts' effort which got this up and running. I was actually able to get one of the Pi3 builds you posted running with Talkback but at the time I just didn't find the Pi 3 that good for running Android. Certainly not with 1 gig of ram, something the Pi 4 gives us a lot of choice with at least.
Click to expand...
Click to collapse
If you/anyone wants to test ADB over USB-C there's two lines you need to uncomment for testing (both LineageOS 17 & 18 should be OK for this).
One line /boot/config.txt under 'USB-C' section:
dtoverlay=dwc2,dr_mode=peripheral
Another one in /vendor/etc/init/hw/init.rpi4.rc:
import /vendor/etc/init/hw/init.rpi4.usb.rc
I don't have any hardware that would provide enough power for the Pi to test this myself. If anyone has recommendations on powered USB-C hubs that are known to work on the Pi 4 for this purpose I'd appreciate that.
My TWRP builds don't support ADB. This is because TWRP has no network support (wifi/ethernet) and I can't test the USB-C for the above reason.

KonstaT said:
If you/anyone wants to test ADB over USB-C there's two lines you need to uncomment for testing (both LineageOS 17 & 18 should be OK for this).
One line /boot/config.txt under 'USB-C' section:
dtoverlay=dwc2,dr_mode=peripheral
Another one in /vendor/etc/init/hw/init.rpi4.rc:
import /vendor/etc/init/hw/init.rpi4.usb.rc
I don't have any hardware that would provide enough power for the Pi to test this myself. If anyone has recommendations on powered USB-C hubs that are known to work on the Pi 4 for this purpose I'd appreciate that.
My TWRP builds don't support ADB. This is because TWRP has no network support (wifi/ethernet) and I can't test the USB-C for the above reason.
Click to expand...
Click to collapse
I can definitely say that uncommenting those lines did get me ADB over the USB type C port. So it does work in this mode successfully. I could then do adb root and at least have some access similar to TWRP minus the flashing and back-ups.
I think the problem with some powered hubs could be the power delivery. I'm not sure if you have a type-C port already on your machine, but it may provide the full 10 GBPS/3A requirement if it's a direct type C port. The 3.0/3.1 gen1 hubs only provide 1.5A of power and 5 GBps, so while the Pi could run on it, you couldn't power any attached devices and would get the reduced lightningbolt symbol performance as well. The powered hubs have dedicated charging ports, but these wire directly to the hub and not the machine, so while providing more power at a cost.
I also tried installing Gapps (BitGapps) for Android 11 but it failed once I signed in with a Google account. Oh well. 32-bit Gapps are also harder to come by anyway. For now I can always sideload apk files which don't rely on the play stuff and use Chrome for browsing. That's a good start.
The reason I need Android 11 is mostly for accessibility. Unlike for sighted folks where lower Android versions don't make an impact on how and what you can use, for the blind, each Android version introduces changes to the accessibility API. This is important as these changes can allow for things like brand new touch gestures (completely different gestures/ swipes and touches in Android 11 with Talkback ) to actual improvements on what the screen reader "sees" in the UI. So no, I'm not doing this to just have the version number myself, but to benefit from the latest changes to Android's accessibility API. I hope this makes sense.

htc_Tomi said:
I can definitely say that uncommenting those lines did get me ADB over the USB type C port. So it does work in this mode successfully. I could then do adb root and at least have some access similar to TWRP minus the flashing and back-ups.
I think the problem with some powered hubs could be the power delivery. I'm not sure if you have a type-C port already on your machine, but it may provide the full 10 GBPS/3A requirement if it's a direct type C port. The 3.0/3.1 gen1 hubs only provide 1.5A of power and 5 GBps, so while the Pi could run on it, you couldn't power any attached devices and would get the reduced lightningbolt symbol performance as well. The powered hubs have dedicated charging ports, but these wire directly to the hub and not the machine, so while providing more power at a cost.
I also tried installing Gapps (BitGapps) for Android 11 but it failed once I signed in with a Google account. Oh well. 32-bit Gapps are also harder to come by anyway. For now I can always sideload apk files which don't rely on the play stuff and use Chrome for browsing. That's a good start.
The reason I need Android 11 is mostly for accessibility. Unlike for sighted folks where lower Android versions don't make an impact on how and what you can use, for the blind, each Android version introduces changes to the accessibility API. This is important as these changes can allow for things like brand new touch gestures (completely different gestures/ swipes and touches in Android 11 with Talkback ) to actual improvements on what the screen reader "sees" in the UI. So no, I'm not doing this to just have the version number myself, but to benefit from the latest changes to Android's accessibility API. I hope this makes sense.
Click to expand...
Click to collapse
Thanks for confirming that ADB over USB-C is working. This might be something that will be enabled by default in future builds.
Latest BiTGapps (BiTGApps-arm-11.0.0-R19_signed.zip) should work just fine. I haven't received any other reports with issues.
Yes, I totally understand that new Android versions bring improvements, that's the whole point. But IMO simply having a bigger version number shouldn't be any reason for doing releases if it's not otherwise feature ready or some things are broken. This is a bit of problem in this "scene" where early utterly broken stuff is being endorsed just because of the version number.