yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] zapjb:
This is just a maybe. Since the N6 there's been 3-4 versions of faster & faster chargers. Are u sure thats the original turbo charger & not a newer version?
[Nexus 6  Original Android Development] mahir555:
yes i got it with the phone. Here it is
[Nexus 6  Original Android Development] clintongsan:
I've had the camera issues as well as issues attempting to use Trebuchet as my Home app.

BUT, MORE IMPORTANTLY

, has anyone noticed any issues with Google Fi? I've attempted multiple installs and didn't have any issues with my service or the Fi app using LINEAGE16, before 17.1 was released. Every time I turn the phone on or restart I get a full size window that says "Download the Google Fi app in order to activate your SIM" (My SIM is already active I have LTE and service but get weird text messages.) When I click download app or obtain the Fi app through Play Store, it will launch and repeatedly give error code T508. I noticed someone had said that they flashed the 117 radio and latest bootloader, then install Lineage, and it fixed this very issue but this did not work for me. Any ideas or advice would be greatly appreciated because as most of you may already know, Google Fi support is terrible they're just clueless.

PS Lastly, my IMEI and correct phone number/ICCID all populate accurately in the About section, so I'm 100 percent sure that I did not accidentally damage any partitions or software. If I flash the entire N67--- stock firmware, all works great and the Google Fi app is already supplied when the phone turns on for the first time.
[Nexus 6  Original Android Development] Muhammadha_xiq:
Launcher not working

I have installed full open gapps file in my lineage 17 due to which official trebuchet launcher don't work. Their is also a bug when you use Google keyboard
[Nexus 6  Original Android Development] mrk2815:
just wondering does the may 1 build have the may security, or will that be coming in the next set of lineage nightly builds.
[Nexus 6  Original Android Development] Dhalsim43:
No it's still on April
[Nexus 6  Original Android Development] zzenyoo:
If you can sacrifice speed (charging) try ACC/AccA. You can limit battery temp. (pause charging). It's very healthy for battery.
[Nexus 6  Original Android Development] linus207:
Thanks for mentioning acca. Now I can charge my devices overnight without any damage :)
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Anyway I can help fixing this?
[Nexus 6  Original Android Development] Elektroschmock:
Most probably we don't have the right apn for your provider in our APN database.

https://github.com/LineageOS/android_vendor_lineage/blob/lineage-17.1/prebuilt/common/etc/apns-conf.xml

You can check if it is right. If it's wrong just submit a patch.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Mobile data is working perfectly it's just I'm unable to send and receive SMS.

Also my carriers APNs are on that list

---------- Post added at 01:55 AM ---------- Previous post was at 01:44 AM ----------

If I use a SIM card from another carrier I'm able to send and receive SMS

And on LOS 16 everything was working perfectly even with carrier it's not working with right now
[Nexus 6  Original Android Development] githyanki:
Sounds like your APN is wrong. Just because it was detected and listed does not mean it was right. Check with your carrier what the settings are supposed to be.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
APNs are used to access the internet right?

Is there any relation between it and the ability to send and receive SMS?
[Nexus 6  Original Android Development] githyanki:
Yes. SMS and MMS.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Thanks for the help

But I checked and the APN is correct.

Any idea what might else be the reason?

Thanks
[Nexus 6  Original Android Development] dvdram:
I've set my N6 to one click to the left ("efficient") for a slightly longer battery life. Still, my N6 works great and I don't see too many lags. Even my navigation app (Osmand+) works fast enough - well, at least 95% fast enough. There are noticeable lags in screen re-drawing sometimes. Not too much, but yet big enough to be noticed, especially when driving faster then 100 km/h.

I know that this is to be expected and regarded as totally normal when using a navigation app with restricted CPU power. But I wonder if there's any way to choose a power profile per app? Say: app X is to use battery setting "normal", app Y is to use battery setting "efficient". That would be very very helpful.

I know I can set battery optimization for each app, but that's not quite the same, is it?
[Nexus 6  Original Android Development] maddog3030:
Who's the carrier you're having problems with?

and who is the carrier that currently will work on your phone?

you said you swapped Sims and one did work in the other one did not.....
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Jio is not working

BSNL is working

Thanks for the help
[Nexus 6  Original Android Development] esysfound:
As suggested above, it sounds like you need to check with your provider and CHECK ALL the settings. It is a pain but I would look on their website or ring Jio and go through all (adding it as a new APN if needed, not just relying on the phone to pick all up). See here https://www.bt.com/help/mobile/getting-set-up/how-to-change-apn-settings-on-an-android-mobile-phone for good list of settings.
[Nexus 6  Original Android Development] maddog3030:
You could also check the Sims status live in the about phone about Sim while you have each SIM inserted make sure that both Sims are fully connected.

You might need to reset the phone parameters under the phone info menu in "*#*#4636#*#*" (dial this from your phone pad), and check to make sure that your provisioning is triggered and that your band select is either set to the correct or Auto.

****** Strong caveat in the phone info menu you could really mess things up so tread lightly ******.

If you care to post pictures of these screens so we can look at them make sure you block out your IMEI and phone number.
[Nexus 6  Original Android Development] Event_Horizon:
which TWRP version or file if any is there FBE version or something then please let me know
[Nexus 6  Original Android Development] runekock:
I looked, and I simply cannot find the way to set the SMS center number. It's not part of the APN, and not in the settings of the Messaging app.

But for me it just works out-of-the-box.

Perhaps the setting has been removed because auto-setup works for practically everyone?

(But anyway check that ordinary voice calls work for you. If not, you may lack 3G coverage at all).
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Just checked that the SMSC number is also correct

I wonder what changed from LOS 16 to 17.1 as it worked perfectly there
[Nexus 6  Original Android Development] linus207:
Hey, i can't connect to any cellular data except LTE. Am I doing something wrong?

PS. Messing with *#*#4636#*#* is not getting any results.
[Nexus 6  Original Android Development] Gysper:
I can confirm that I plugged in my MintMobile Sim into this N6 and it works without messing with any settings. Running the May 1 build. I can also confirm that I updated the bootloader and radio per instructions on OP. Please let me know if did all of those things before troubleshooting further.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Yes, everything as instructed

My other SIM cards are working fine it's just my main SIM isn't

Can I help with logs or anything?

---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------

Also when I switch my phone on, mobile data never works on it's own. I have to enable airplane mode then disable it then it works perfectly but SMS don't work even after that
[Nexus 6  Original Android Development] wrsg:
Was there a significant change to how MTP works in Android 10/LOS 17.1? I'm doing a copy over MTP on LOS 16.0 and its taking like 10x longer.

It also seems to take up a lot more CPU time on the Windows side.

Turned out to be a poor-quality USB cable.
[Nexus 6  Original Android Development] Gysper:
Try download a different SMS app like GoSMS. Issue could be related to how SMS communicates with the mobile data. If downgrading from LTE to 3G in the settings make a difference, then most likely the ROM has an issue using LTE to send messages. But since it works with a different SIM I wouldn't have any clue on what causes it.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
The carrier Jio is LTE only so no fallback to 3G/2G

I have tried with with the default Messaging app and also with Google Messages.

Can you think of anything else that might be wrong?

Thanks for your help.
[Nexus 6  Original Android Development] Markeee:
I've had these APN issues before with my carrier on previous roms and finding working solutions can be very difficult but here are a few things that worked in the past you might want to try

Pull your sim card out reset network settings and apn setting reboot then reinstall the sim card try that a few times sometimes it works to reset to your proper apn settings

This also worked for me sometimes copy and save an old telephony.db file from a previously working rom that has your good working apn setting in it

Then paste it into the new rom overwriting the telephony.db file.

That file can be found here on your phone

Device/

/data/user_de/0/com.android.providers.telephony/databases/telephony.db

Good luck at some point if all else fails you may have to more on to a different rom thats what I had to do in the past
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Thanks for your help

I'll try that

Do you have any idea why it worked on LOS 16 and everything before that it's not working now?
[Nexus 6  Original Android Development] Markeee:
I have no idea why it works on some roms and not on others but in the past I have struggled with the same apn issues big time going back years and with previous versions of android and the issue has only gotten worse with newer versions of android on some stubborn roms There are other solid working roms out now for Nexus 6 (shamu) running Android 10 I suspect you may have to resort to one if all else fails I have
[Nexus 6  Original Android Development] Elektroschmock:
Thanks for the feedback. I was trying to reproduce your issue, but wasn't able to.
[Nexus 6  Original Android Development] Elektroschmock:
I can only write it again. If this issue bothers you, you need to do an official bug report in out gitlab. Writing here won't acchieve anything, as nobody is going to go 3 pages back and look what you have already tried. In the bug tracker it's much easier to track - hence the name.

Also somebody with access to Jio Sims and Jio network might pick your Problem up.

For somebody not familiar with Jio it's quite confusing why they need a sh1tload oft different apn.
[Nexus 6  Original Android Development] wrsg:
Sorry to report a false-positive. I did hit another problem which actually did happen with a known-working USB cable.

When copying files over MTP that start with a "." at the start of the filename or if one of the folders in the path starts with a ".", it takes a little longer than the other files. it's most noticeable when copying thumbnails over as the thumbnail folders usually all start with a ".". I resolved it through just deleting all the thumbnail folders. The difference in time taken to copy isn't very bad but it is noticeable once you copy a lot of files.
[Nexus 6  Original Android Development] SteveYoungs:
There's plenty of activity on the changelog, but there hasn't been any new builds since May 1st. Is there a problem with the build server?
[Nexus 6  Original Android Development] Gysper:
8 days ago, LineageOS was hacked. Most likely this affects all devices, but no new builds are being processed.

https://mobile.twitter.com/LineageAndroid/status/1256821056100163584

See http://status.lineageos.org for more info.

---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------

There is a setting under Network&internet >> Mobile Network >> Preferred network type. Unless you're telling me you don't have the option to change it.

You can also do a factory reset to see if it makes any difference. Here's a reddit post from another user who ran into the same problem https://www.reddit.com/r/LineageOS/...1_beryllium_cant_send_sms_after_upgrade_from/

Otherwise, there really shouldn't be any difference why it works in 16 but not 17. Like you said yourself, 1 sim works but the other one doesn't, but because they are different providers can't really say it's a problem with the ROM.
[Nexus 6  Original Android Development] Lawstorant:
Nice. Pixel Launcher works OOTB without some iffy Magisk modules. You're doing amazing work keeping N6 up to date! I switched to "quick" performance profile and I am quite amazed by how good this phone still works. Is it just me or or is 10.0 actually faster on our old shamu than 9.0?

When it comes to mobile internet I too sometimes struggle with no connection after restart. Changing preferred network types a few times or toying with airplane mode seems to fix it after few minutes. Just a minor thing but still worth pointing out. I'll get back with full logcat when I'll have some more free time.
[Nexus 6  Original Android Development] Elektroschmock:
Not really faster, but there should be much less skipped frames - so it should stutter less and feel faster.
[Nexus 6  Original Android Development] Thimoteo:
Custom TWRP for Nexus 6 shamu with Lineage 17.1 | Android 10

Can anyone recommend a custom TWRP (or other recovery) that will reliably make and restore nandroids with this rom?

I had no trouble flashing TWRP on a OnePlus 5T, booting to recovery and making a nandroid ... but the nandroid wouldn't restore. The TWRP web site says that Android 10 isn't supported.

https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

I think some phones have custom TWRPs that now support Android 10. Does anyone know of something similar for the Nexus 6 shamu?
[Nexus 6  Original Android Development] esysfound:
As this thread says on the first page, and on the OS 17.1 Download page, there is a Lineage Recovery file. I have not used it as there are advantages to TWRP if you ever wanted to try another non Lineage ROM.

But if you read the TWRP page carefully, it says this is not an issue for the sexy Nexy 6-just newer Pixel phones and others with A10 stock. To quote it: "Older non-Pixel devices that shipped with older versions of Android and receive upgrades to Android 10 are not affected." Maybe your OnePlus was affected but doubtful this is an issue with Nexus 6 (though to be honest I don't know-have not yet tried). I did roll it back to another A9 ROM via TWRP during earlier experiments, with no problem.

You could easily test this yourself on the Nexus 6 - use TWRP, install the May build, make a backup. Then just update some apps. Then try to roll back to the original install using TWRP, and let us know.
[Nexus 6  Original Android Development] Thimoteo:
Thanks for the reply, esysfound.

I thought your suggestion was worth a try. I downloaded the latest 17 nightly, wiped in TWRP, then installed 17 on the Nexus. I made a few changes, rebooted to recovery, made a backup, wiped again, and restored the backed-up 17. No error messages.

Unfortunately, the restored 17 wouldn't boot. It hung on the lineage logo start-up screen. The same thing had happened with a restored nandroid of version 17 in the OnePlus. I'm too lazy to search past messages in this forum, but believe that at least one other Nexus user here also couldn't get a usable nandroid out of version 17 with TWRP. Now I'm the second one. ;)

As for the Lineage recovery: it's bare bones, doesn't make nandroids.

I'll just hope that contributors continue to update Lineage 16 for the Nexus, or that someone customizes TWRP for Lineage 17.
[Nexus 6  Original Android Development] esysfound:
TRWP Problems

Hi- good you did this for the troops, and if it is so, this is actually a very big deal.

One preliminary issue - you did not install TWRP in the system partition right? See p1 here.

Just to clarify, as always the devil is in the details:

1. When you say "wiped" - what exactly did you do? Also after the restored recovery, did you wipe Dalvik/Cache?

2. Is your phone now just looping - what exactly happens when you turn it on - what is the exact current status?

3. You could try - reinstalling Magisk 20.4 from TWRP, then restarting-tell us what happens.

There is some chatter about this here:

see most recent at https://xdaforums.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673/page84

https://www.reddit.com/r/essential/comments/emu29w/update_to_android_10_jan_2020_update_root_and/

4. You could also try using the old but useful Wugfresh Recovery Tool to deal with a bootloop. https://nexus-root.com/download/

Let us know because if there is no reliable way to use TWRP recovery, that is quite serious in my world.

[MENTION=3383960]Elektroschmock[/MENTION] - any thoughts on this, once we hear back with some more info?
[Nexus 6  Original Android Development] Thimoteo:
Hi, esyfound: Please see my responses below.

1. When you say "wiped" - what exactly did you do? Also after the restored recovery, did you wipe Dalvik/Cache?

Factory reset / standard wipe option in TWRP. I didn't go to advanced settings. I don't remember if 'factory reset' wipes Dalvik/Cache. As for the install of TWRP: With platform tools, I installed with the command fastboot flash recovery.

2. Is your phone now just looping - what exactly happens when you turn it on - what is the exact current status?

I restored the Lineage 16 configuration, so would have to start from scratch to test. On boot the Lineage logo came up -- the crescent with the circle that moves from side to side -- and then stayed there, with the circle moving endlessly. The same thing happened on the OnePlus. I waited three to five minutes.

3. You could try - reinstalling Magisk 20.4 from TWRP, then restarting-tell us what happens.

I only rooted a phone once, decided since that I don't need root, and haven't used Magisk.

4. You could also try using the old but useful Wugfresh Recovery Tool to deal with a bootloop. https://nexus-root.com/download/

For me, this would make Lineage 17 more trouble than it's worth. I can swap nandroids in Lineage 16 in just a couple of minutes.

Let us know because if there is no reliable way to use TWRP recovery, that is quite serious in my world.

[MENTION=3383960]Elektroschmock[/MENTION] - any thoughts on this, once we hear back with some more info?[/QUOTE]

Maybe someone else can get it to work. If so, I hope you'll share. My guess is that we'll have to wait for a custom TWRP.
[Nexus 6  Original Android Development] Elektroschmock:
Maybe someone else can get it to work. If so, I hope you'll share. My guess is that we'll have to wait for a custom TWRP.[/QUOTE]

It's a bug in TWRP which doesn't set the selinux lables back to the original label. This should be fixed in TWRP, but it is unmaintained for shamu.

I could modify shamu's sepolicy to work around that, but that would weaken the security a bit. I haven't decided yet.

In the other hand TWRP is way outdated an can't handle encrypted data partitions.

You can still backup/restore your stuff using ADB. TWRP is just more conveniant.
[Nexus 6  Original Android Development] xuxu1:
U can install current lineageos (+ gapps + magisk) and then restore only data, then it works.
[Nexus 6  Original Android Development] maddog3030:
Maybe someone else can get it to work. If so, I hope you'll share. My guess is that we'll have to wait for a custom TWRP.[/QUOTE]

either you're a unique case or I am I've been using TWRP successfully to backup and restore 17.1 for a while now as a matter of fact I can back up one Nexus 6 transfer the backup to another Nexus 6 and recover and its just fine.
[Nexus 6  Original Android Development] s_dino:
[MENTION=3383960]Elektroschmock[/MENTION]

I have flashed LOS 17.1 0501 and opengapps stock 0513, when I update the lOS , pixel launcher keeps stopping, is't a bug? or I need flash the lOS and opengapps every time?
[Nexus 6  Original Android Development] esysfound:
Hi-as always super helpful. So

1. All that is needed is to execute this command:

adb backup -apk -system -all -f <drive:\filepath\name>.ab

and the ROM, data, and Apps will be backed up? Have done it with earlier ROMs, Just was not sure with all the new security and partition structure it would work on A10.

And using the adb restore etc. - everything will simply go where it needs to go?

Also -

2. I tried this and my backup.ab file is about 4,5 GB. But the current TWRP backup is about 6.3 GB. I assume I forgot something, likely by not the -shared command parameter, but could it also be possible that TWRP needs so much more info just to manage its UI-API? Just trying to get a feel before I trust it.

3. And since I wrote this, on the CRDroid and Colt threads, it seems some people claim either by copying again a ROM over a recovered install (??), or reinstalling a new base ROM first, and then using TWRP to just copy over backed up Data, they have got around the TWRP A10 problem? Note - in an odd way, these 2 methods/stories might actually be doing the same thing. Have you any similar experience?

Sorry all this uncharted waters for me with A10 and I just want to be really sure I have a backup plan that works.

Thanks
[Nexus 6  Original Android Development] Elektroschmock:
Oh as you say it. I haven't used it for a very long time, as I usually don't need backups.

But it should work if you enable rooted debugging and use adb root.

This might be helpful:

https://gist.github.com/elektroschmock/75d42844db9d78075a9ba15676205e3c
[Nexus 6  Original Android Development] zzenyoo:
After restoring backup with twrp, dirty flash rom.zip (same ver. as in your backup). It worked for me, every setting, gapps & magisk was ok.
[Nexus 6  Original Android Development] Elektroschmock:
This works because flashing the ROM again does overwrite the rootfs where TWRP has set wrong selinux Labels.
[Nexus 6  Original Android Development] Thimoteo:
Success with zzenyoo method

I also thought this was worth a try, and am glad I did.

I installed 17.1 and then did a standard TWRP back-up (system, data, boot).

I then did a standard wipe (data,cache, dalvik), restored the 17.1 backup and, without rebooting, immediately dirty flashed the same Lineage 17.1 installation zip on top of the backup. I wiped cache/dalvik, then rebooted.

Success. Many thanks to zzenyoo and Elektroschmock for input. It looks like I can now use TWRP with 17.1 just as I did before, as long as I remember to do the dirty flash with the same Lin 17 .zip after restore.
[Nexus 6  Original Android Development] Thimoteo:
Ten minute delay for mobile data connection

Now that I have 17.1 up and running, thanks to zzenyoo and Elektroschmock, a new problem ... :confused:

On start-up, I have to wait about ten minutes to get a mobile data connection with 17.1 on the Nexus 6. The mobile data icon shows in the status bar, but without "4G" next to it, and without an internet connection.

Eventually, it comes up, if I turn airplane mode off or on, or turn mobile data off and on in "Network & internet --> Mobile network -- > Mobile data." I also have changed settings for Preferred network type, and tried resetting APNs to default. No particular setting change consistently makes mobile data come on. Every time, I've had to tinker with one setting or another for about ten minutes before mobile data comes up.

The only post I found that looked similar was: https://xdaforums.com/showpost.php?p=82487931&postcount=251 . My situation might be very different, though, as phimeas had no connection at all.
[Nexus 6  Original Android Development] zzenyoo:
Had this problem only ones. After fresh & clean install of 17.1. Since phone finally connect (some tinkering with airplane mode, network type, etc.) for the 1st time, it always connects (in my case).