yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] d'sebling:
desperately need help here, i always get this bluetooth keeps stopping message when i flashed the 0221 build, i first flashed the 0220 build and the bluetooth is working fine managed to transfer files through it. but when i flashed the 0221 it started to show up and even when i clean flash the 0220 back it also showing this message, i've tried to clean flash, and flash every build from 0218-0221 to no avail, but when i installed the LOS 14.1 the bluetooth is perfectly fine. what did i do wrong? i'm using the twrp-3.3.1-1_UA-hh. it's so frustating because i tried this rom and it is great.
[Nexus 5 Original Android Development] nikiiv:
Great work.. Seems quite snappy on my Nexus 5.

Quick question - is there a way to remove the navigation buttons?
[Nexus 5 Original Android Development] z3DD3r:
I guess something is wrong with your /persist partition. If u didn't do anything with this partition yourself then everything can be fixed. Contact me in pm and i can help u.

What do you mean? There is no option to remove the navigation buttons. U can only switch between different navigation styles in the settings. Or u can disable navigation bar in props... But this file is readonly in Android Q because of SAR (system as root)
[Nexus 5 Original Android Development] eurochild:
[MENTION=7268092]z3DD3r[/MENTION]

finally able to boot with magisk with a replacement display but getting the black screen and no boot when flashing criterion kernel, is the fix on the kernel side? should we inform the developer to include something for it to work ?

thanks for the work!
[Nexus 5 Original Android Development] jjsan:
settings -> system -> Advanced -> Gestures -> System navigation -> Gesture navigation
[Nexus 5 Original Android Development] z3DD3r:
The fix is on kernel and device tree side. So criterion kernel should be updated to work properly on new los builds. Everything is opened on github...
[Nexus 5 Original Android Development] FlyingInTheDark:
Ok, I modified QCamera2 makefiles to include hardware/qcom/media/msm8974 and hardware/qcom/display/msm8974 and now the build is successful. I flashed it on my phone and it boots OK, but the bluetooth doesn't work:

02-23 15:22:11.153 4904 4904 F DEBUG : pid: 4859, tid: 4900, name: bt_main_thread >>> com.android.bluetooth <<<
02-23 15:22:11.153 4904 4904 F DEBUG : uid: 1002
02-23 15:22:11.153 4904 4904 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
02-23 15:22:11.154 4904 4904 F DEBUG : Abort message: '[FATAL:btm_ble_gap.cc(501)] Check failed: p_vcs_cplt_params->param_len >= BTM_VSC_CHIP_CAPABILITY_RSP_LEN.

The bluetooth is working fine in z3DD3r's image, so it means there is something wrong with my build.

[MENTION=7268092]z3DD3r[/MENTION] can you please post the build instructions somewhere? I'm not able to reproduce your build using source code from github, and lineage-17.1.
[Nexus 5 Original Android Development] rolex0815:
I'm experiencing the same error, maybe the remote repositories aren't updated.
[Nexus 5 Original Android Development] jwalker9715:
So far so good except, has anyone been able to get signature spoofing in Microg checked?

Fakegapps and dialing the number did not work.
[Nexus 5 Original Android Development] candra yudha tama:
Anyone try install viper4andoid this is rom ???? Working or not ????
[Nexus 5 Original Android Development] cornu8:
I'm at the same point, made the changes to QCamera2 makefiles and have it successfully running with microg on my Nexus 5, but Bluetooth crashes. Any help [MENTION=7268092]z3DD3r[/MENTION]?
[Nexus 5 Original Android Development] FlyingInTheDark:
[MENTION=4594721]rolex0815[/MENTION] [MENTION=10578231]cornu8[/MENTION]

QCamera makefile issue has been fixed already in the latest patch to device, thanks z3DD3r.

But the bluetooth issue still remains and I also have some trouble with boot animation.

The code which is triggering bluetooth assertion was added fairly recently when android-10.0.0_r27 tag was merged on February 9th.

I think z3DD3r's image is working fine because he is not building the lastest branch but some older revision of 17.1.

[MENTION=7268092]z3DD3r[/MENTION] can you please tell which git commit you have in /system/bt ?
[Nexus 5 Original Android Development] FlyingInTheDark:
I take it back, tried the older version of system/bt and it still fails with a similar reason. Something not right with HCI_BLE_VENDOR_CAP_OCF.

I wounder if it would help to disable BLE_VND_INCLUDED as a workaround.

EDIT:

Yes, removing BLE_VND_INCLUDED did the trick. Now Bluetooth is working fine.

Now my only issue is non working boot animation:

21:33:06.516 SurfaceFlinger (263 398) W Faking VSYNC due to driver stall
21:33:06.517 BufferQueueLayer (263 263) W [StatusBar#0] Timestamp 26304408070 seems implausible relative to expectedPresent 0
21:33:06.517 BufferQueueLayer (263 263) W [BootAnimation#0] Timestamp 25250329529 seems implausible relative to expectedPresent 0
21:33:06.576 SurfaceFlinger (263 397) W Faking VSYNC due to driver stall

Maybe there are even more fixes missing on z3DD3r github?
[Nexus 5 Original Android Development] rolex0815:
With the last fixes, I was able to compile it.

I made an upgrade from LOS 16 to 17.1.

Even I managed to get it running with the old partitioning scheme and opengapps 10 - pico:

Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p25 0.9G 0.9G 3.1M 100% /

Notice the space left in '/' :D
[Nexus 5 Original Android Development] z3DD3r:
Nobody tells that Android Q can not be installed with Pico gapps without repartition ;)

For [MENTION=4594721]rolex0815[/MENTION], [MENTION=10568417]FlyingInTheDark[/MENTION], [MENTION=10578231]cornu8[/MENTION], and others who interested.

Let me describe a bit current situation with LOS 17.1 for hammerhead...

First of all builds of LOS 17.1 are made daily. I've setup a task which runs every day. That task fetches latest patches from LOS repos, latest patches from my tree, applies required patches to LOS tree, tries to build an ROM and in case of success this task uploads new fresh build to sourceforce. All builds are clean, i.e. made without caches. Everyday u will see a new build with latest changes on sourceforge if nothing was broken. Don't think that i'm using old android tag or old source code...

But not all changes can be included in device trees. Some patches are picked from gerrit.

The compilation error with camera can be fixed in different ways. First one is to set hardcoded paths to AOSP hals as some users shows here. That works, but it breaks CAF builds. Second way is to revert one commit in vendor/lineage repo and bring back the qcom-* pathmap. This will work for any builds. Currently my tree contains modified make files for the camera which allows to build CAF and non-CAF builds without any issues.

Bluetooth bug is also can be fixed in different ways. We can disable BLE entirely with BLE_VND_INCLUDED or we can revert some changes in system/bt. I need BLE so the second way is more appropriate for me.

There are also some other patches on gerrit that i included and/or dropped...

In any case i will not post list of these patched on forum. The reason is pretty simple. I don't want to support this list. These patches can be merged tomorrow and my info will be inaccurate. This happend some times already. I don't want to maintain such list on forum...

In the end i want to show you one example of how things can be easily broken. Today were merged some patche with selinux policies to LOS repos. These patches broke my builds cos of duplication. In order to fix it i've rebased my device tree and removed some in order to build the ROM...

PS: Everything u need is availabe on gerrit!
[Nexus 5 Original Android Development] sant514:
As always, [MENTION=7268092]z3DD3r[/MENTION] your explanatory analyzes are perfect.

And today, and with the BT Fix and with the TWRP Recovery encryption-decryption.

Thank you about your excellent informations but and for your good job with our nexus 5.
[Nexus 5 Original Android Development] FlyingInTheDark:
[MENTION=7268092]z3DD3r[/MENTION]

Thanks for the info, I see your point now. Unfortunately this doesn't help me much, because I have to build from source. I was hoping this rom can be built without changes to LOS since there was no mention of it in the head post. Now all is clear, I was wrong, building this rom is not so easy after all. Which is very unfortunate but nothing I can change.

Thanks, have a good day
[Nexus 5 Original Android Development] ClashTheBunny:
Truly amazing

Thanks so much for all the hard work you have put into this! This is truly amazing having Android 10 on my Nexus 5. It's great to have gesture navigation and I have been wanting root for so long (but never gotten around to doing it on stock).

I tried 20200226 first and it didn't ever pass the boot screen. I went ahead and tried clearing things better, and not just clearing cache, but I didn't try 26 again, I just tried 20200225. So I don't know what of the two things I changed fixed it. It booted up right away.

One thing that I have tried that didn't work is a slim port HDMI cable, which shows the screen perfectly, but locks up the phone. Nothing responds, the clock doesn't increment, and a power button hold is all I can get to bring the phone back. I was wondering if anybody has gotten it to work?

Edit:

The display does seem to work in landscape mode. I was able to pair my bluetooth keyboard and start termux and type for a while before I rotated the screen and the screen locked up again. The system still works fine and ADB as well as ssh'ing in are fine. If you would like a logcat of the event, I can try to figure out what's actually happening.
[Nexus 5 Original Android Development] wvanstraalen:
The hidden and protected app menu within the launcher settings doesn't seem to open on my phone.
[Nexus 5 Original Android Development] z3DD3r:
[MENTION=1079255]ClashTheBunny[/MENTION],

can u send me logcat and dmesg logs?

[MENTION=5496578]wvanstraalen[/MENTION],

This happens if u setup lockscreen pin/password/pattern. Disable it and u will be able to open protected and hidden apps. Do everything u need and reenable your lockscreen pin/password/pattern. This is an trebuchet issue...
[Nexus 5 Original Android Development] ClashTheBunny:
[MENTION=7268092]z3DD3r[/MENTION], sure! I forgot to get a dmesg, so I'll do that in a bit. What's the best way? Github issue?
[Nexus 5 Original Android Development] wvanstraalen:
[MENTION=5496578]wvanstraalen[/MENTION],

This happens if u setup lockscreen pin/password/pattern. Disable it and u will be able to open protected and hidden apps. Do everything u need and reenable your lockscreen pin/password/pattern. This is an trebuchet issue...[/QUOTE]

Yes, you are absolutely right, thanks for pointing me in the right direction!
[Nexus 5 Original Android Development] z3DD3r:
No need to create an issue on github. Just post logs here or send them in the pm
[Nexus 5 Original Android Development] charles.milette:
I installed the latest dev build (feb 29th) with GApps pico and Magisk without wiping my /data from LOS 16. For some reason, I can't see the navigation bar, even though the 3 button navigation option is enabled in settings. Toggling between gestures and 3 button nav does nothing. So now I'm stuck in the settings app
[Nexus 5 Original Android Development] z3DD3r:
LOS 17.1 is in beta state (at least my builds for hammerhead). Upgrade process can be unstable. Make a clean installation.
[Nexus 5 Original Android Development] charles.milette:
The issue was an outdated install of the QuickSwitch Magisk module, works fine now.
[Nexus 5 Original Android Development] jacakk:
Does anybody have problem with Android Auto?

I have only blank white screen for a sec after connecting and message at car's screen "Problem with Android Auto".

It's working with another phone without any problem.
[Nexus 5 Original Android Development] GiZeta:
I can't install pico gapps, I have NOTHING but the rom installed on my phone, but it still says I don't have enough space.
[Nexus 5 Original Android Development] sant514:
[MENTION=5559776]GiZeta[/MENTION] This ROM needs repartition. Please see here ...TWRP 3.3.1-HH
[Nexus 5 Original Android Development] RukusX7:
sensors

Has anyone else but me noticed that sensors do not work in this rom?

I tried the sensor fix floating around where you delete folders/files

/persist/sensors/sns.reg

/data/system/sensors

/data/misc/sensors

That did not fix anything for me.

I reverted back to razorloves builds of 14.1 and all sensors work.

Sensors tested using Sensor Box for Android in play store.
[Nexus 5 Original Android Development] sant514:
Do you have made clean flash?

The sensors work normally to me, with clean flash from 14.1 (razorloves) to 17.1 (z3DD3r).
[Nexus 5 Original Android Development] RukusX7:
I'll clean flash to 17.1 again and test one more time.

On that note, I only deleted sns.reg. If issues ...persist... I should I delete the entire /persist/sensors folder? reading back through the thread, that's the one difference I did not try.
[Nexus 5 Original Android Development] sant514:
Remove /persist/sensors folder. You can do it from TWRP for example. Mount the Persist partition and remove /persist/sensors folder via the FileManager. DO NOT REMOVE OTHER FOLDERS!

More informations please see here from z3DD3r
[Nexus 5 Original Android Development] RukusX7:
Looks like that did the trick. I deleted /persist/sensors in TWRP and then installed Lineage 17.1 and all sensors now work.

Thank you for pointing this out to me!
[Nexus 5 Original Android Development] z3DD3r:
Maybe u can send me logcat and dmesg logs? Unfortunately i can't test Android Auto myself :(
[Nexus 5 Original Android Development] z3DD3r:
Hi there!

I've included some patches for USB-OTG in build 20200302. Starting this build USB-OTG should work with FAT(16/32)/EXFAT/NTFS/EXT(2/4).

PS: These patches are available on gerrit but not merged yet in LOS 17.1 repos for some reason. Maybe because they are not ready. So USB-OTG mounting can have issues.
[Nexus 5 Original Android Development] sant514:
Thank you [MENTION=7268092]z3DD3r[/MENTION]
[Nexus 5 Original Android Development] z3DD3r:
You are welcome! Thank you for reporting an issue with OTG ;)
[Nexus 5 Original Android Development] z3DD3r:
Hi there

Next build (2020-03-04) will contain a fix for launching hidden & protected apps in trebuchet when lock screen pin/pattern/password enabled.
[Nexus 5 Original Android Development] candra yudha tama:
ROM last version 304 can't booting when reboot from twrp always back to bootloader....I try twrp 331-H and 3310 still back to bootloader....install ROM version 304 success I reboot back to twrp but when installed gapps pico error 20...I try hh_repart -r success but still error 20
[Nexus 5 Original Android Development] z3DD3r:
Well, there is a bug in installation process of this build. I'm already found what is wrong and rn discussing it with LineageOS team. It is not related to gapps or repartition. The problem occurs only in case of clean flash. I won't describe entire problem cos i believe it will be fixed in next build. Build 2020-03-04 removed from sourceforge but if someone already downloaded it and wants to install it then do next:

1. Install 2020-03-03 build.

2. Install 2020-03-04 build without wiping system.

3. Install Gapps, Magisk and other stuff.

4. Reboot into system.

Fixed in build 2020-03-05
[Nexus 5 Original Android Development] dahawthorne:
Just for info, before reading this last message I dirty-flashed the 0304 build over 0302 and it worked fine.
[Nexus 5 Original Android Development] z3DD3r:
Yea, dirty flash works fine. I've submitted a patch to gerrit. I hope he will be accepted quickly...
[Nexus 5 Original Android Development] bigsupersquid:
thanks again for sharing all source trees.

just to save other people trouble finding it, since microg signature spoofing patcher in nanodroid doesn't work on Q yet, here is a patch for source:

https://github.com/microg/android_packages_apps_GmsCore/pull/957

(I hate stock gapps enough to spend all night syncing sources for Q.)

I'm in the process of building with it to test, as soon as my cell-modem sync is completed, but I see no obvious reason it won't work.

if there's any issues, I'll update.

//edit: couldn't get the settings to show spoofing permissions, so it didn't work out.
[Nexus 5 Original Android Development] z3DD3r:
Known issue. Your app updated correctly. But for unknown reason launcher shows such ghost icon. Just ignore it.

PS: And please edit your message and remove images from the post body (i.e. remove
[Nexus 5 Original Android Development] sant514:
In the Lineage 14.1, the known issue with the "bubbling" sound with recorded video, could be solved by adding a file /system/etc/audio_platform_info.xml , containing the following data:

<?xml version="1.0" encoding="ISO-8859-1"?>

<audio_platform_info>

<acdb_ids>

<device name="SND_DEVICE_IN_CAMCORDER_MIC" acdb_id="89"/>

</acdb_ids>

<backend_names>

</backend_names>

<config_params>

</config_params>

</audio_platform_info>

I added this file in Lineage 17.1 but the "bubbling" sound with recorded video is here again......
[Nexus 5 Original Android Development] z3DD3r:
New build 2020-03-05 is out.

Problems with clean flash and addon.d backup/restore are fixed. This build also contains some selinux updates so i recommend everyone to update.

Well, maybe something was changed in Q. I never used this feature so can't say u rn what is wrong.
[Nexus 5 Original Android Development] sant514:
Is there any way to remove the noise suppression in video recordings in Android Q ?

Because and without the change in the audio_platform_info.xml, and with the AOSP Camera app but and with the Google Camera 3.2, there is the "bubbling" sound with recorded video.

A solution ( temporary ? ) is the using OpenCamera app which it has settings about sound and microphone....
[Nexus 5 Original Android Development] sant514:
[MENTION=7268092]z3DD3r[/MENTION], you were right. In Android Q, the folder with audio configuration files, has moved from /system/etc to /system/vendor/etc

In the folder /system/vendor/etc, there are the "audio_effects.xml", "audio_platform_info.xml", "audio_policy_configuration.xml", "audio_policy_volumes.xml".

The "audio_platform_info.xml" is important about the issue with the bubbling sound in recorded video.

So, i made an addition in this file, in the acdb_ids section, <device name="SND_DEVICE_IN_CAMCORDER_MIC" acdb_id="89" />.

and of course a reboot after the change.

I made a trial video recording with the build 2020-03-05, with AOSP Camera app and Google Camera 3.2.045 app and the sound is perfect. !!!!!!!

Fix in Lineage 15.1 (and for Lineage 14.1)

Here i found the change from folder /system/etc to /system/vendor/etc
[Nexus 5 Original Android Development] z3DD3r:
Then I don't need to fix anything :) Everything works as expected.
[Nexus 5 Original Android Development] sant514:
I believe that, you must make a change in the file

audio_platform_info.xml, in your Device tree, if you want a permanent sound fix. This file, so you can see in your Device tree is blank.... It needs the <device name="SND_DEVICE_IN_CAMCORDER_MIC" acdb_id="89" /> .

Without this addition, we have "bubbling sound with video recorded" ( very very annoying level ...)

This time, i have add a script in the addon.d for saving after flashing.....
[Nexus 5 Original Android Development] z3DD3r:
I will not do this. Patch that u send is Abandoned and not merged to LOS tree. There should be a reason for this. So u should stick with addod.d script if this change is necessary for you.
[Nexus 5 Original Android Development] candra yudha tama:
Do you mean like this ???
[Nexus 5 Original Android Development] sant514:
No, it wrong. You must insert the addition in the acdb_ids section.

My own file is as ....

<audio_platform_info>

<acdb_ids>

<!-- empty -->

<device name="SND_DEVICE_IN_CAMCORDER_MIC" acdb_id="89" />

</acdb_ids>

<backend_names>

<!-- empty -->

</backend_names>

<pcm_ids>

<!-- empty -->

</pcm_ids>

<device_names>

<!-- empty -->

</device_names>

<config_params>

<param key="snd_card_name" value="msm8974-taiko-mtp-snd-card"/>

</config_params>

</audio_platform_info>

It is important to note that, the folder for Android Q is /system/vendor/etc !!!
[Nexus 5 Original Android Development] candra yudha tama:
Nice....Working for me to :D thanks
[Nexus 5 Original Android Development] z3DD3r:
Well this is not related Q. This change was made in Oreo. Patches u shown was submitted to lineage-15.1 which is Android 8.1 (Oreo)
[Nexus 5 Original Android Development] zheega:
Is it just me, or does the latest build (306) feel much slower, stable? I was running 229 before installing 306.
[Huawei Mate 30 Guides, News, & Discussion] wadywadywady:
This app is able to solve the problem for downloading and installing GMS on Huawei Mate 30 , and ensure the normal operation of applications that rely on GMS, gmail,youtube ,facebook,etc.

The follow is the download link:

Mod edit:

url removed.
[Huawei Mate 30 Guides, News, & Discussion] Borden666:
can you explain more?
[Huawei Mate 30 Guides, News, & Discussion] wadywadywady:
With the app, you can install google service framework on your Mate30 Phone.

step1: click button "Detect device"

step2: If there is no gms on your phone, click "REPAIR NOW" bottom button in next page.(You need to

activate device first)

step3: wait...(In fact, gms is downloading & installing in background)

step4: login google account.

Everything is ok.
[Huawei Mate 30 Guides, News, & Discussion] Borden666:
what do you mean by activate device first because everytime I click on "Repair now" it goes back to the application log in screen
[Walmart Onn Tablets General] jordianz:
Im attempting to get info or at least start a thread on the possibility of ROOTING the (Walmart) ONN Surf 100005208 10.1"
[Walmart Onn Tablets General] razredge:
It's a rebranding of the ONA19TB003. Same hardware, new name.
[Walmart Onn Tablets General] Viva La Android R.I.P.:
As [MENTION=551758]razredge[/MENTION] stated, the Onn Surf 10.1 is merely a rebranding of its predecessor tablet. The Surf 10.1 can be rooted with or without TWRP. Follow the guides on rooting the previous Onn 10.1. Everything works exactly the same. TWRP is fully compatible as well.
[Walmart Onn Tablets General] TheUndertaker21:
can you share your stock firmware with me
[Walmart Onn Tablets General] KaosKreationz:
no

the thing was a brick when i attempted the mod its a MT8768WA chipset not MT8163
[Walmart Onn Tablets General] Viva La Android R.I.P.:
Regardless of chipset platforms, both Onn 10.1" tablet variants can be rooted using the same TWRP and the same root method, and without TWRP by fastboot flashing a Magisk patched boot image.
[Walmart Onn Tablets General] KaosKreationz:
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.

---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------

Also how does one patch the image with magisk if the magisk software does not work on said tablet?

As well as how does one dump the images when so flash nor mt software doesn’t recognize the image.
[Walmart Onn Tablets General] Viva La Android R.I.P.:
Well, you just taught me something I wasn't aware of. I have not yet seen the Onn 10.1" variant with preloaded Android 10. My variant (Onn Surf 10.1, Model No. 100005208) came with Android 9 Pie. And I was able to root it using the TWRP build from my tablet's predecessor, which had the same chipset and also rah on Android 9 Pie. You seem to be referring to an entirely new variant that ships with Android 10. What is your exact model number and your current firmware build number? I'll see what I can find out.