yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Themes and Apps] belmont007:
CellTrack is great but

CellTrack is great but we need a similar application for Windows mobiles. I am a telco professional as well and so many fellow eng use Kaiser. Sure we have tools as well, but sometimes we like to play with cell infos when we are not at work. Telco is our hobbi as well :)
[Tilt, TyTN II, MDA Vario III Themes and Apps] iso|ated:
riping data

Hi there,

is there a posible way to get all info saved to a file as seen in the 'field test' program.
[OnePlus 6T  Questions & Answers] rob!n:
This is happening often then not. Screen doesnt wake up instantly or wakes up late after pressing power button or trying waking from douole tap to wake. Screen wakes up after 5 seconds or so. Doesn't happen every time but it is. Tried clearing chahe from my stock recovery with locked bootloader but didn't help.

Any help pls.
[OnePlus 6T  Questions & Answers] akmsr:
same here, started happening yesterday. following this thread.
[OnePlus 6T  Questions & Answers] rob!n:
Glad to know to know problem persist and not only with me.

Thanks for response. Let me know if you find something too.
[OnePlus 6T  Questions & Answers] rob!n:
Are you on 9.05?
[OnePlus 6T  Questions & Answers] omerbagi10:
Just ordered the 6t from aliexpress, and now I've noticed that they started selling global variants of the 6t on aliexpress (same seller).

Does anyone know the difference between them?
[OnePlus 6T  Questions & Answers] _nkay_:
Most probably the frequency bands
[OnePlus 6T  Questions & Answers] KOLIOSIS:
You may have ordered a OnePlus 6T with Hydrogen OS, which is what's used in China.

The rest of the world gets Oxygen OS.

https://www.oneplus.com/cn/6t/specs

You may be able convert yours to the OOS version, but, if it were me, I'd cancel the order & buy direct from OnePlus outside of China, or if you still need to buy from AliExpress, find a seller who can verify the exact model they're selling.
[OnePlus 6T  Questions & Answers] omerbagi10:
Thanks, just did a little search and apparently it comes with global firmware and the global versions cost more for some reason (the only place where I can get a oneplus device in my country is through aliepress).
[Ascend Mate 7 General] DarkCancer:
i am using Huawei update extractor for flashing my phone and the cmd command but this is what i get

first i extract the app file to the extractor destination

https://imgur.com/zNeTP35

then uses this command

https://imgur.com/yArnYNs

and thats what i get

https://imgur.com/QxBUZoB

how can i resolve this problem !!
[Ascend Mate 7 General] erayrafet:
Tell me that you have a P9 Lite.

To fix this issue you have to unlock your bootloader again.
[Ascend Mate 7 General] DarkCancer:
indeed i have mate 7 and i didin't find how to unlock it without dc unlocker that i havn't it

and i figure out that there is another solution to rebrand it with funkyhuawei tool but it is

expensive to use it
[Ascend Mate 7 General] erayrafet:
The firmware shown on your screenshots is indeed for a P9 Lite. Instead you need a firmware compatible with your model.
[Xiaomi Mi 5s Questions & Answers] pres1o:
Hello, i d like to flash the latest miui 10 global beta android 8 rom. Do I need to do anything other than just flashing with fastboot? Sorry for newbie question. Thanks!
[Xiaomi Mi 5s Questions & Answers] Sn4pdragon:
I believe you also need to have the bootloader unlocked
[Xiaomi Mi 5s Questions & Answers] NightRaven49:
his bootloader is already unlocked, since he is already running a custom rom.

anyway, to answer op, no you do not need anything apart from the fastboot rom and miflash. you can even choose to relock the bootloader from miflash, but I don't see any reason to.
[Samsung Galaxy Note 9 Questions & Answers] Pannam:
Has anybody manages to use note 9 snapdragon with game guardian. Without root ofcourse ? If so. Can u show. I used virtualxposed everything is ok but cant install google services.

Regards
[Xiaomi Mi A2 / 6X Questions & Answers] jigs4wkiller:
As the title suggests, I can not connect mtp to Linux, but it works in Windows. Other phones of mine do not have this problem under Linux. Does anyone have a solution or the same problem? I've already tried several versions of the stock rom and it also doesn't work in the pie beta either.
[Xiaomi Mi A2 / 6X Questions & Answers] AsItLies:
My A2 connected with mtp under Linux all the time. No issues.

I'd suggest turn on adb, keep the developer selections open, make the connection, then if no mtp, bring settings back up and in the usb settings section, select mtp.

It seems Linux has some built in detection's for devices, product ID's etc. Many times it results in a 'default' setting of 'charge only'. So you have to change it back after the connection.
[Xiaomi Mi A2 / 6X Questions & Answers] Ironmaniaco:
What Linux distribution are you using? I have no problems whatsoever using Arch Linux + Nautilus inside i3wm Window manager.
[Xiaomi Mi A2 / 6X Questions & Answers] jigs4wkiller:
I already tried this. What I personally find the strangest thing is the file transfer via adb push / pull works but when I try in the file manager to open the phone comes the error that the device could not be mounted because of a udev error.

I tried it on 2 PC's one with Cinnamon and the other with xubuntu and it doesn't work.

My other phones (Xiaomi Mi5s and Mi A1) are working flawless on both PC's.
[Xiaomi Mi A2 / 6X Questions & Answers] Ironmaniaco:
Well, now you have a north to go.

Take a look at the DebuggingUdev wiki from Ubuntu.

Maybe it's just a missing udev rule. Execute

sudo udevadm monitor -e

After, connect your device and you should get better logs.
[Xiaomi Mi A2 / 6X Questions & Answers] jigs4wkiller:
If I understand the log correctly, it tries the device instead of mtp with ptp to mount. But to be honest, I do not really understand what's there stand.

Here the output from the command:

UDEV [388.551499] bind /devices/pci0000:00/0000:00:15.0/usb1/1-2 (usb)

ACTION=bind

BUSNUM=001

COLORD_DEVICE=1

COLORD_KIND=camera

DEVNAME=/dev/bus/usb/001/011

DEVNUM=011

DEVPATH=/devices/pci0000:00/0000:00:15.0/usb1/1-2

DEVTYPE=usb_device

DRIVER=usb

GPHOTO2_DRIVER=PTP

ID_BUS=usb

ID_FOR_SEAT=usb-pci-0000_00_15_0-usb-0_2

ID_GPHOTO2=1

ID_MEDIA_PLAYER=1

ID_MODEL=SDM660-MTP__SN:07081BDD

ID_MODEL_ENC=SDM660-MTP\x20_SN:07081BDD

ID_MODEL_ID=ff48

ID_PATH=pci-0000:00:15.0-usb-0:2

ID_PATH_TAG=pci-0000_00_15_0-usb-0_2

ID_REVISION=0404

ID_SERIAL=Xiaomi_SDM660-MTP__SN:07081BDD_10fa792

ID_SERIAL_SHORT=10fa792

ID_USB_INTERFACES=:ffff00:ff4201:

ID_VENDOR=Xiaomi

ID_VENDOR_ENC=Xiaomi

ID_VENDOR_ID=2717

MAJOR=189

MINOR=10

PRODUCT=2717/ff48/404

SEQNUM=5817

SUBSYSTEM=usb

TAGS=:uaccess:seat:

TYPE=0/0/0

USEC_INITIALIZED=388518849

adb_user=yes
[Google Pixel 2 XL Questions & Answers] Nettwerk:
Hello all. Ok at all finaly phone lock removed what can I do next? (Phone lock - Operator Lock/Works now on any network).

What is best and fastest way to sync phone with Macintosh?
[Pixel C Android Development] Vartom:
Long thought to upload his own version of AOSP or not, but still decided.

So version of AOSP Pie with corrections in the device tree from Vartom.

Updated Selinux rules.

Added fixes to drm_hwcomposer.

Applied fixes preventing spam to the kernel log.

Saved device name as Pixel C.

drm_hwcomposer

Device tree

Download -r16

Changes

Corrections in wifi direct.

Cleaning the system from old libraries.

Download -r21

Changes:

-add aptx-hd codec.

Download -r34

Changes:

- Google security updates -> April 2019

- No kernel updates

Download -r35

Changes:

- Google security updates -> May 2019

- kernel updates

disabled kernel lowmemorykiller, enable MEMCG, switch lmkd to userspace.

Download -r39

Download -r42

Changes:

- Google security updates -> March 2020

- in kernel - battery fix/hack

Download AOSP 10-r32

Changes:

- Google security updates -> April 2020

- camera enable( but freeze after a minute of use).

- disabled touchbust for CPU and GPU.

Download AOSP 10-r33

AOSP updates will be in this thread

Full Treble and GSI system on the Dragon
[Pixel C Android Development] Alex93917:
Thanks but no gapps installation is allowed. Error text is about Android 7.1 which is installed.
[Pixel C Android Development] Vartom:
What gapps have you tried?

I did not have problems installing gapps.
[Pixel C Android Development] Monfro:
Works great!!

Thank you!!
[Pixel C Android Development] linzinan:
Mtp can export files ，but cannot import file
[Pixel C Android Development] 夜霜行:
Good job:svetius:
[Pixel C Android Development] Vartom:
Once again checked, everything works without errors.

If you have errors, make logs. syslog.
[Pixel C Android Development] AlfreGarcia98:
How is it going? Do you reccomend me to update from lineageos 15.1?
[Pixel C Android Development] Vartom:
I did not use lineageos 15.1/16.0, I used the official firmware all the time. After the first versions of Android 9 appeared, I use my versions of AOSP Pie firmware.
[Pixel C Android Development] AlfreGarcia98:
And what would you say? Is it better than stock? How is battery, multitasking going? I'm going to install pie but don't know what rom

Enviado desde mi ONEPLUS A5010 mediante Tapatalk
[Pixel C Android Development] Vartom:
I wanted to say that I can not make the comparison proposed by you, because I did not use the firmware you specified.

In comparison with the official firmware, I did not find significant advantages for myself. Just an updated version of android. Autonomy in my opinion improved slightly by 1-1.5 hours. Multi-tasking remained at the same level.
[Pixel C Android Development] imlk__:
thank you
[Pixel C Android Development] Vartom:
+r34.
[Pixel C Android Development] Monazite:
Thank you for keeping AOSP updated!!!
[Pixel C Android Development] Everio9000:
Amazing, thank you !!! Our Pixel C still updated :) :)
[Pixel C Android Development] AlfreGarcia98:
Sorry but I'm a bit lost. Wich one do you think is better, the discontinued pixel experience, this aosp or lineage? Thanks

Enviado desde mi Aquaris E5 mediante Tapatalk
[Pixel C Android Development] xxiaowei:
thanks ! from nexus 9 to pixel c , i always use your ROM.
[Pixel C Android Development] MrPhilo:
What this hwcomposer update in your OP relate to?
[Pixel C Android Development] Vartom:
I use a slightly modified updated https://github.com/vartom/android_external_drm_hwcomposer/commits/dragon-piev2
[Pixel C Android Development] Monfro:
Thank you Vartom for your constant and important commitment for the development of Nexus 9 and Pixel C.

This AOSP rom is running really great.

However April version needs more time to load browser pages, Facebook pictures etc. compared to March rom and the previous one.

Maybe is better to perform a fresh install (i am running the rom since November)?

Someone know if restore wizard has been fixed in latest gapps?

Back in October-november you had to skip it and set everything from scratch.
[Pixel C Android Development] Monfro:
I performed a fresh install.

Gapps still have the problem of neverending search for system update; without connecting to WiFi the wizard manager ends its work well.

Rom is really fast and smooth.

Performance level that this hardware reaches is incredible; and processor is not getting hot at all.

Probably with Pie Pixel C is the best Android tablet available on the market, even after all these years.
[Pixel C Android Development] a723356:
Thanks for your work. Light bar is not working. Is it a unfixed bug?
[Pixel C Android Development] Vartom:
The light bar has been disabled. I do not understand the meaning of its constant glow while the screen is on. In other cases, it works just like usual.

In this firmware, I did not make a message indicator light bar.
[Pixel C Android Development] Vartom:
AOSP Pie June 2019 - r42

Changes:

- Google security updates -> June 2019

- Google kernel updates for dragon -> android-8.1.0_r0.135

Download
[Pixel C Android Development] xxiaowei:
Great , always thanks
[Pixel C Android Development] Vartom:
Kernel whith the patch disables the adaptive backlight on lcd panel.

Solves the problem of changing the brightness of the backlight, depending on the image on the screen (when a dark picture appears in the text, the backlight decreases).
[Pixel C Android Development] a2b2angelo:
very nice! ....appreciated!

Hope the dark theme gets into more apps and settings menus:)

a2b2
[Pixel C Android Development] Vartom:
dell
[Pixel C Android Development] Burakki:
Hi, Thank you for your efforts

I have installed the rom and the gapps with the twrp 3.3.1-1 (after wipe dalvik/art, system, data, cache)

But at boot the system does not start and the pixel-c returns to the fastboot screen. What did I do wrong?
[Pixel C Android Development] Vartom:
Since I installed the system all the time using .img, I did not check the ota format. Now I tried OTA and could not install it from TWRP. In this regard, I made a zip archive with images for firmware.

One significant bug is noticed:

The system only works when connected to a PC (USB).

Ps I checked another OTA and also a failure, it seems that there are some problems on my device.
[Pixel C Android Development] Vartom:
AOSP 10 r2 build.

Bugs

- camera not work. until added shim support for camera blob.

- and those that you find :)

Try firmware, tell me how it works

Download

OpenGapps https://sourceforge.net/projects/op...64-10.0-nano-20190920-UNOFFICIAL.zip/download
[Pixel C Android Development] Bleedos:
I tried to install the ROM but I get an error

/sbin/mount.ntfs /dev/block/sda1 /usb-otg process ended with ERROR: 11
....
E1001: Failed to update system image.
Updater process ended with ERROR: 7
....

Not sure what went wrong.:confused: I reinstalled a 9.0 ROM juste after that and that one worked...
[Pixel C Android Development] Vartom:
Updated the file.
[Pixel C Android Development] Monfro:
I hope to find some spare time to test the new rom.

Thanks
[Pixel C Android Development] Bleedos:
I redownloaded the file using the link you provided in post #31 but it seems to be the same. All files within the zip are the same size they were. I looked in the first post of this thread but did not find any link for 10_r2. Did I miss something?
[Pixel C Android Development] Vartom:
Have you tried installing or just compared the size? The changes are not so big that you can see the change in file size. Just try installing.
[Pixel C Android Development] Bleedos:
No I did not try to reinstall it.

I will tonight. I'll let you know if if works.

Thank you.
[Pixel C Android Development] Bleedos:
Now I don't get the ERROR 11 but I still get ERROR 7 as I wrote in my first post.

Will restore my backup.
[Pixel C Android Development] Vartom:
Please give me the full log from the recovery.
[Pixel C Android Development] Vartom:
Fastboot version AOSP r2 download
[Pixel C Android Development] KrX38:
No gapps ( TWRP keep telling i need the correct one for the rom )

Hello ,

No gapps can be installed ( TWRP keep telling i need the correct one for the rom )

" This Gapps pkg is for android 10.0.x only ; Please download the correct version for your rom 7.1.2 ( SDK 25 )

Installation tried by sideload and directly with zip file in the tablet .

When i try to install the gapps SDK 25 , i have an error telling me that the correct one should be the SDK29 ...

Tryin to install gapps 9.0 tell me that i need the correct 7.1.2 ( SDK25)

Tryin to install gapps 8.1 tell me that i need the 7.1.2 sdk25

8.0 --> Same

7.1 gapps --> installing core GApps ect ... ( i used the open gapps arm64 7.1 full ) . All install OK via TWRP but when i reboot to the system , no Gapps is visible ( no youtube , no play store ..... nothing ) .
[Pixel C Android Development] Vartom:
Are you sure that you installed the firmware correctly through the fastboot, extracting the files from the archive and flashing each partition(boot, system, vendor) separately?

I gave a link to the gapps that I use myself and which are installed without problems. The link is in this post.
[Pixel C Android Development] KrX38:
Maybe not ... After 3 hours I did not even check what the archive contained ... I'm stupid ... I'd try again after work and test with your link for gapps.

Regards friend ?
[Pixel C Android Development] Bleedos:
Downloading it right now.

I'll try this week. Not sure I will have the time tonight.
[Pixel C Android Development] iancornelius:
So I flashed these files, successfully. I do get the "Internal problem with your device" error which I believe is associated with a mismatched vendor and system `build.prop'.
[Pixel C Android Development] JohnnyChim:
any bugs with aosp 9.0 or 10?

I was using unofficial lineage 17 but there is bugs on the password lock screen which is essential for me.

Does this build has the same bug?
[Pixel C Android Development] Bleedos:
You get an error but does the ROM work?

Thanks.
[Pixel C Android Development] iancornelius:
Apart from the usual no camera working, the ROM seemed to work okay. I haven't tested it fully as the tablet is not a daily driver.

I will note that I flashed the files via fastboot.
[Pixel C Android Development] Vartom:
Update source code to AOSP r9

Fastboot version AOSP 10 r9 download
[Pixel C Android Development] Monfro:
Thank you very much!

Is it possible to have a TWRP flashable file?
[Pixel C Android Development] Vartom:
You can extract from the archive and flash these files through TWRP in the appropriate partitions.
[Pixel C Android Development] Monfro:
Thank you very much!

AOSP Pie is running great, I am going to install AOSP 10 soon
[Pixel C Android Development] Monfro:
Installed AOSP 10 this evening: it really flies!!! [MENTION=6556709]Vartom[/MENTION]: thank you for the hard work!!!
[Pixel C Android Development] QuantumSingularity:
Error 20 - gapps

I flashed the r9 version via fastboot; vendor.img, system.img and boot.img.

When I try to install gapps I get the errormessage:

`this Gapps pkg is for android 10.0.x only ; Please download the correct version for your rom 7.1.2 ( SDK 25 )`

`Updater process ended with ERROR: 20`

I use the version from the link [MENTION=7724239]Varton[/MENTION] provided a few posts ago.

open_gapps-arm64-10.0-nano-20191105-BETA.zip

I also get an error when booting:

`Theres an internal problem with your devies. Contact ....`

Any idea?
[Pixel C Android Development] Monfro:
About gapps: you have to unmount and then mount again system partition before flashing.

No problems here.

About

`Theres an internal problem with your devies. Contact ....`

It should be a warning about vendor mismatch (I have the same); probably the packed one is not correct.

But after that everything works perfectly.

---------- Post added at 01:31 PM ---------- Previous post was at 01:20 PM ----------

About gapps: you have to unmount and then mount again system partition before flashing.

No problems here.

About

`Theres an internal problem with your devies. Contact ....`

It should be a warning about vendor mismatch (I have the same); probably the packed one is not correct.

But after that everything works perfectly.
[Pixel C Android Development] QuantumSingularity:
Thnx. That did the trick.

A needed a couple of mount/remount attempts.

The playservices kept complaining that I neede to enable sms access, but that was enabled. The solution was enabling the location.

The tablet is amazing fast and every works except the google calendar-app. All the other google-apps (youtube,maps,keep) work.
[Pixel C Android Development] Monfro:
After some hours play services will settle and stop complaining.

About Google calendar (and Gmail): I solved downloading and installing a 2-3 months older version from apkmirror.

Everything worked, and apps updated through play store without problems.
[Pixel C Android Development] QuantumSingularity:
Thnx.
[Pixel C Android Development] dictionary:
My issue is root. Won't work no matter which version I flash. Using latest r9 Q (runs fantastic)
[Pixel C Android Development] Monfro:
[MENTION=6556709]Vartom[/MENTION]: i hope there will be future updates for your great AOSP 10 rom
[Pixel C Android Development] Vartom:
Changes:

- Google security updates -> March 2020

- in kernel - battery fix/hack

Download AOSP 10-r32

Reloaded. The correction is associated with increased battery consumption in sleep mode due to a change in the BT driver.
[Pixel C Android Development] Monfro:
Thank you very much!

This evening I am going to install it.

And thank you very much for the battery/cpu fix!

I can't wait to have the tablet always running at maximum CPU speed!
[Pixel C Android Development] jolinnard:
I think I will keep using your AOSP ROM. Simple, but it works sweet and I have all I need. Thank you Vartom.
[Pixel C Android Development] Monfro:
Yes, it is extremely fast and stable.

No lags and no reboots.
[Pixel C Android Development] jolinnard:
Do you use official youtube app? For me crash and can't connect to my account. Newpipe works fine thought...
[Pixel C Android Development] Monfro:
Yes, i am using official YouTube app.

I flashed latest AOSP rom over previous version, so apps and data was configured there.

Try to install an older version from apkmirror
[Pixel C Android Development] jolinnard:
Thanks, finally I have installed Youtube Go and it works. It's enough for me.
[Pixel C Android Development] jolinnard:
I was digging for a while trying to fix my issues with Play Music, Youtube and Google Books not able to login with my default Google account.

After some tests I found a simple fix by modifying build.fingerprint from /system/build.prop, /vendor/build.prop and /vendor/odm/etc/build.prop to the last certified by Google:

google/ryu/dragon:8.1.0/OPM1.171019.016/4503492:user/release-keys

Even changing that in recovery, the ROM still complains in boot that "There's an internal problem with your device. Contact your manufacturer for details." so maybe another prop has to be changed to hide that message. I think that it's in some point of this file core/java/android/os/Build.java in base repo, perhaps here?

Anyway, I'm happy to "fix" my main issue with some Google apps.

PD: I've decompressed Lineage system and vendor and they set their fingerprint to the latest certified too.

PD2: First I tried to set the fingerprint with Magisk Hide Props module, but it results in a broken boot... In logcat I saw that zygote can't be started: "03-29 17:12:19.721 1048 1048 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4fdbf24d in tid 1048 (zygote), pid 1048 (zygote)". Very weird.

EDIT 12/04/2020

And finally I have created this file:

dragon:/ # cat /data/adb/service.d/finger.sh
#!/system/bin/sh
resetprop ro.build.fingerprint google/ryu/dragon:8.1.0/OPM1.171019.016/4503492:user/release-keys

Just set 755 permissions and should put the right fingerprint. After that I have to reset play store data and wait a bit to recover Google Play verification.

Also, with this script the initial message is gone.
[Pixel C Android Development] Vartom:
Changes:

- Google security updates -> April 2020

- camera enable( but freeze after a minute of use).

- disabled touchbust for CPU and GPU.

Download AOSP 10-r33
[Pixel C Android Development] Monfro:
Thank you very much.

R33 is smoother and snappier than previous one; battery life also improved a lot.
[Pixel C Android Development] Vartom:
AOSP updates will be in this thread

Full Treble and GSI system on the Dragon
[G4 Q&A, Help & Troubleshooting] TrueFaith:
Hello

Have you some fixes for audio recording quality on G4? In stock its terrible cause of noise cancelling, but how to disable it on videos?
[G4 Q&A, Help & Troubleshooting] TrueFaith:
up