how do i swap the recent and back key?
** nvm, found it, search for swap in settings
** nvm, found it, search for swap in settings
Last edited:
Update: The dev unfortunately didn't answer, but that's not a problem because since the march security patch update, the app works again! So maybe it was a bug with the security patch itself which google fixed, idk. But it works again, that's what countsI suspected that. In Cupertino everything needs to be done in a unique and proprietary way...
You misunderstood me. Since I've no hands on airpods, you need to compare... I just wanted to give a hint, what may be related to the issue.
I fear, you are on your own here: since the bt changes in the rom seem to work for non Cupertino-tainted (SCNR) hardware, los will not revert them (especially if they are part of Q_asb_2021-01); the devs of andropod may help, but will probably focus on stock roms... Sorry.
EDIT: For both of the logs with andropod installed: Did you open the widget before getting the log? Because in both logs there's no attempt to query the battery info of 14:C8:8B:C2:FA:F9 (the bt address of your airpods).
you are right. for airtel if you want volte to work, you need to modify build.prop . the modification is there in this thread.Airtel volte isn't working for me, however other networks are working just fine. (on both los 17.1 and 18.1)
you are right. for airtel if you want volte to work, you need to modify build.prop . the modification is there in this thread.
Could you please be kind with the dev?I tried that, it didn't do anything. It is really disappointing and annoying that no one is doing anything about this problem from such a long time, even tho a ton of builds have been released @dianlujitao could you please pay attention to this?
I am sorry that i lost patience after having waited from previous year. I didn't mean to be unkind and I respect @dianlujitao for what he does for our device.Could you please be kind with the dev?
He is not payed to mantain this rom and you should be grateful that our old device is still receving official builds.
I'm sure that if he could fix he will fix, but please be patient.
Is the Japanese just SBAS?GPS + Glonass lock, I get, when it works. I have not seen any Galileo. Only some Japanese sats
Still searching. Waiting for confirmation. E.g.: https://forum.xda-developers.com/showpost.php?p=82932523&postcount=70
According to this tread for the Zuk Z2 pro, there is Galileo supportThis one?:
https://www.deviceranks.com/en/phone/6235/zuk-z2 (and the z2pro)
This is what the spec's are saying:
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . .GPS, A-GPS, GLONASS, BeiDou, Galileo
Edit 1:
Additional, here you can find a list of all smartphones which are currently able to use Galileo, which are about 30 phones.
Though, I have no idea which one is using 'our' chipset and it seems the Zuk Z2 (Pro) is not one of them...
https://www.usegalileo.eu/EN/inner.html#data=smartphone
Edit 2:
I have compared some lists:
https://www.usegalileo.eu/EN/inner.html#data=smartphone
https://galileognss.eu/is-your-phone-using-galileo/
and
https://www.gizmotimes.com/lists/list-of-phones-powered-by-qualcomm-snapdragon-821/16889
https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-821-msm8996-pro
https://www.akshatblog.com/snapdragon-821/
etc....
Unfortunately this is not giving a match.
So I think we are stuck on the old GPS, GLONASS and BeiDou networks, it seems Galileo is not there for us....
.
What about the Samsung Galaxy Note Fan Edition(SD/US)? It was released the same time as the TAB S3.For galileo:
Please read my previous posts and don't suggest devices w/o native android 9 (or better 10) blobs. The los 16 and 17 builds for the z2 don't use native z2 blobs, but kanged blobs, which doesn't support galileo...![]()
Did you check the prerequisites I've mentioned? What's the samsung model number? What's the los code name?What about the Samsung Galaxy Note Fan Edition(SD/US)? It was released the same time as the TAB S3.
Edit: it's the revised Note 7 that doesnt explode
You know what, I got to existed that there was a US model of the Fan Edition. Actually it's the botched Note 7 so finding firmware will be impossible. But you asked model numbers so here they are:Did you check the prerequisites I've mentioned? What's the samsung model number? What's the los code name?
You know what, I got to existed that there was a US model of the Fan Edition. Actually it's the botched Note 7 so finding firmware will be impossible.
Is there anything not GNSS related that can be salvaged from other MSM8996/pro devices?It's not possible to kang blobs from the firmware, if the firmware is not available/accessible.
I highly doubt blobs for other socs will work on msm8996pro/msm8996.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
# LineageOS build target list
# <device> <build_type> <branch name> <period ("N"ightly, "W"eekly, "M"onthly)>
# Nightly lineage-17.1
beryllium userdebug lineage-17.1 N
chiron userdebug lineage-17.1 N
d850 userdebug lineage-17.1 N
d851 userdebug lineage-17.1 N
d852 userdebug lineage-17.1 N
d855 userdebug lineage-17.1 N
dipper userdebug lineage-17.1 N
discovery userdebug lineage-17.1 N
enchilada userdebug lineage-17.1 N
f400 userdebug lineage-17.1 N
fajita userdebug lineage-17.1 N
gts4lvwifi userdebug lineage-17.1 N
guacamole userdebug lineage-17.1 N
h830 userdebug lineage-17.1 N
h850 userdebug lineage-17.1 N
h910 userdebug lineage-17.1 N
h918 userdebug lineage-17.1 N
h990 userdebug lineage-17.1 N
I01WD userdebug lineage-17.1 N
jactivelte userdebug lineage-17.1 N
jflteatt userdebug lineage-17.1 N
jfltespr userdebug lineage-17.1 N
jfltevzw userdebug lineage-17.1 N
jfltexx userdebug lineage-17.1 N
jfvelte userdebug lineage-17.1 N
kirin userdebug lineage-17.1 N
ls997 userdebug lineage-17.1 N
mermaid userdebug lineage-17.1 N
nash userdebug lineage-17.1 N
[B]oneplus3 userdebug lineage-17.1 N[/B]
pioneer userdebug lineage-17.1 N
polaris userdebug lineage-17.1 N
rs988 userdebug lineage-17.1 N
sagit userdebug lineage-17.1 N
us996 userdebug lineage-17.1 N
vs985 userdebug lineage-17.1 N
vs995 userdebug lineage-17.1 N
z2_plus userdebug lineage-17.1 N
"gcam man" - that sounds interestingAre you the gcam man? If so, thanks a million for your work and your latest works fine and dandy on this build.
I believe it doesn't apply to our device (A only). See the section on recovery in https://lineageos.org/Changelog-19/
Sent from my OnePlus 3T using XDA Labs