yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] zno_oze:
Why are apps from verizon ,sprint , motorola present on lineageos for this device ? I don't have them on other lineageos devices.

list of apps:

Always on voice ( com.motorola.triggerenroll)

com.motorola.motocit

com.motorola.triggertrainingservice

com.motorola.motosignature.app

com.motorola.android.buacontactadapter

com.android.sdm.plugins.sprintdm

com.vzw.apnservice

Can i get pure lineageos without this ? how ?
[Nexus 6  Original Android Development] BootloopedMillennials:
I think LineageOS was the problem. I went back to fully stock and it solved my problems. Not only is it keeping an LTE connection but the signal is more consistent. Same radio as I was running on LineageOS, the latest radio.

I couldn't tell you what changed in LineageOS to cause this problem, it was running fine until recent builds.
[Nexus 6  Original Android Development] Elektroschmock:
Those apps are on stock rom too. They are for project FI and for hotworddetection.
[Nexus 6  Original Android Development] zno_oze:
hmm.. but is there a way to compile LOS without them ?

I don't use Gapps and this apps just make me want to switch to a different phone. I always disable them via openAPK(f-droid) . Wasn't stock rom on nexus supposed to be open-source + Gapps ?
[Nexus 6  Original Android Development] athulele:
They're just device specific features.

If you don't use them, none of those apps will be running.

If you yourselves want to build LOS without them, you could always remove them from this file. No guarantees on how it'll work without those packages.

https://github.com/LineageOS/android_device_moto_shamu/blob/cm-14.1/device-proprietary-files.txt
[Nexus 6  Original Android Development] razorloves:
You can also just disable them in settings, or via command line in a terminal. Or delete them by adding them to the script in /system/addon.d/
[Nexus 6  Original Android Development] zelendel:
Not even close. No rom is pure AOSP from Google. Google has always used different files then what they push to AOSP. Also some of those apks are for features of your device like double tap power to activate camera.

Also just a side not each and every device uses closed sourced files for their OS so you will NEVER see a fully open source OS that has every part open.
[Nexus 6  Original Android Development] duhec:
Greetings.

I've been on the last CM13 snapshot (cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y6-shamu) that is working really well for me for some time now and wanted to give Nougat another go to see if it's ready to be a daily driver because I like the new features and I only encountered two problems, one negligible and the other one more serious.

The negligible part is that the QuickPic 4.5.2 app, the version before Cheetah took over, the Share button doesn't work and crashes the app immediately, so I had to use the default gallery app.

The serious part is the now well known Nougat bluetooth battery drain problem. I tried several methods, namely disabling the optimiziation of the BT module, but the drain is still there. Is not so bad, but the main reason for going Nougat was to stop using apps that force the device going to doze and if it's not working... well. :rolleyes: The only thing I didn't try was having Nougat and an app (ForceDoze, Greenify, etc.) like in CM13 Marshmallow.

This thread doesn't really mention the drain so I wanted to ask you all if you guys have problems at all with the BT battery drain or are you just keeping BT off and that's it?
[Nexus 6  Original Android Development] Shadow53:
I have my Bluetooth always on, sometimes connected to a headset, sometimes not. Over the course of ~90% battery drain, I've had Bluetooth take a whopping.... 2%. I can't speak for others, but no Bluetooth drain here.
[Nexus 6  Original Android Development] zelendel:
I agree here. I have used every rom out there and never had any BT battery drain. Mine is on all day and connected to my BT headset for about 10 hours out of the day. The one thing in common I have seen is hooking it up to a car. Which I disabled in my car so cant say anything about that.
[Nexus 6  Original Android Development] id242:
If you're still using Bluetooth 2..x or 3.x devices to connect with your N6, you might want want to consider upgrading them to Bluetooth 4.x so you can take advantage of Low Energy (Bluetooth Smart). If your N6 has to support Bluetooth2/3. this is possibly where your power drain is probably coming from.

Are you using Bluetooth and GPS radios at the same time (for real time turn-by-turn GPS such as waze/google maps), with the screen on, and the GPU constantly redrawing, for long periods of time? This will definitely cause your device to heat up, making the battery warm and depleting it quicker.
[Nexus 6  Original Android Development] duhec:
Hm, strange. I'll tell you what I did and maybe we will find which step I did that was wrong.

1. I had the latest CM13 snapshot (2016-12-21) with Marshmallow radio and bootloader (don't remember which one) on and then I went to TWRP 3.1.1 and wipe the phone completely. Go to advanced wipe and tick all the boxes.

2. Then I proceed to flash the latest stock version of Nougat (N6F27C, May 2017) from Google images so that the phone is 100% stock with everything flashed automatically, radio and bootloader. I then let the first boot to stock happen but immediately boot to fastboot.

3. Flash the latest TWRP 3.1.1.

4. Copy the following files to internal storage and then flash them in this order:

- latest LOS 14.1 (26. 5. 2017)

- FED patcher v8 (to disable force encryption)

- addon SU from Lineage for root user

- latest BeanGapps Mini

- DSP Manager 5.0.8 (for sound and sub bass enhancment)

- latest SuperSU (in this case was the "old" v2.79 that worked)

5. After everything was flashed I then went to Format Data and wiped all user data and internal storage.

6. When 1st boot was complete I proceeded as normal, log to Google, install apps.

The battery wasn't draining that fast, although faster than normal, but in the battery stats I'm pretty sure it was saying bluetooth was consuming a ridiculous amount of battery, like 5000mAh+.

Do you suggest I flash the extracted radio and bootloader manually? Are you using some other kernels? Although I'd like to stay Lineage stock. Was the problem that I flashed everything in one go?

I'm not new to flashing and I flashed other devices with CM in the past (Samsung, LG) which required far more work but maybe I'm missing one simple step, I don't know. :(

id242: the drain is happening while bluetooth is enabled and no device connected, probably also while it's operating but I didn't test it that way. I'm only connecting to my BT headset Platronics Explorer 10, which is a version 3.0 BT device. I'm only talking about the drain while the device stationary and with screen off.
[Nexus 6  Original Android Development] snowrelyt:
Disable instant tethering in Google settings
[Nexus 6  Original Android Development] classic757:
I'm running stock rooted Nougat 7.1.1 and I have basically no bluetooth battery drain (maybe 1 or 2%.) and my bluetooth is on virtually all day. So no issue here.
[Nexus 6  Original Android Development] Xenosis:
This is an interesting prospect. I have a AppRadio ARU setup that's almost definitely using 2.0 but it was $300 and any new replacement would likely be around $400+ so upgrading is definitely not on my radar.

That being said, I've seen the excessive drain after I've already disconnected from the device. The phone which was around 70% charged when I disconnected, hours later, was at 20% with the battery page showing Bluetooth drained the vast majority of the juice.

I'll see if I can get a reproduced screenshot without any other activity.
[Nexus 6  Original Android Development] razorloves:
New blog post https://www.lineageos.org/Changelog-10/
[Nexus 6  Original Android Development] duhec:
First of all I'd like to thank everybody who helped with their suggestions. I knew there was some small thing to do or to uncheck and here it is.

That did the trick. :victory: Many thanks, snowrelyt. :good:

I followed the exact steps again I mentioned before and for now the problem seems fixed. I also found this thread mentioning the crazy BT drain. Having found that topic before I'd would have saved many headaches.

There is another thing I'd like to say that seems relevant to our whale of a phone. In the past I also had the strangest problem where, upon unlocking, then screen would go full blast for a good 5-10 seconds and then slowly fade to normal brightness. This happens when you have auto brightness on. The solution was to turn the Location History off in Google Settings and now a similar problem with the BT occurs because of a setting in Google.

I have to remember next time a strange problem will pop up it will probably be because of some new Google feature. :eek:
[Nexus 6  Original Android Development] dbrickg:
just installed this morning's lineage os nightly, 20170602. all's well so far
[Nexus 6  Original Android Development] 8zabi:
I can access and use quick tiles when the phone is locked, can you? is it a new bug?
[Nexus 6  Original Android Development] dbrickg:
Hmmm, mine doesn't do anything when it's locked. The only way to unlock it is to press the power button. But I've seen some options to change that behavior. Or maybe I'm misunderstanding what you mean by "locked." Make sure you don't have "tap to wake" or "on body detection" turned on. There are probably a few other options hidden away someplace.
[Nexus 6  Original Android Development] razorloves:
New blog post about Safetynet... https://www.lineageos.org/Safetynet/
[Nexus 6  Original Android Development] LordDeath:
I need root for two reasons:

device independent app backups together with their configs (via Titanium Backup)

system-wide ad-blocker on web sites (via AdAway)

If the Android-ecosystem turns hostile to root users I can have both of these features without any system modifications on iOS.

Additionally I will have longer device support cycles without the need to install LOS after a couple of years.

Why am I using Android again?
[Nexus 6  Original Android Development] dbrickg:
Android is just protecting you from your self :) Arghhhh. It sure seems like a bad turn of affairs to me. I suppose it's driven by $$$. <sigh>
[Nexus 6  Original Android Development] zelendel:
This is not unexpected. Everyone knew this would Come to pass.
[Nexus 6  Original Android Development] dbrickg:
Actually, I"m surprised. I thought google and android were above that kind of thing. I guess they must have been stuck in a pretty difficult situation. Not sure what, but I imagine it has something to do with controlling the phones closely enough that financial institutions will trust them with money. But it could be any number of other things. Anyway, it'll be interesting to see how this all turns out....
[Nexus 6  Original Android Development] zelendel:
Well see it is exactly that. On one side you have the huge need for security (in some opinion) and on the other you have the moders. Which require certain security protocols to be bypassed. You can't have both really. Because if weekend hackers and devs like the ones all over the internet can break into the device so can the bad guys. Remember moders make up about 1% of android users. Can't really compare when you have companies buying thousands of device but they have to be secure.

This is the way I see things playing out. At some point in the near future you will end up with bootloaders so secure they can't be hacked, Google will start using the security that is built into the Qualcomm chips, and only a few devices will be moddable. If that doesn't work they have one ace up their sleeve and that is to pull the Play store from all uncertified devices. This option may not seem to likely as that would hurt many smaller oem but they tend to use 3rd party app stores anyway.
[Nexus 6  Original Android Development] dbrickg:
Hmm, yeah, maybe so. But I'm hoping that SafetyNet is an attempt by google/android to let us have it both ways: rather than simply lock down their phones and os, they're saying: go ahead and play with your phones as much as you want, but if you change certain things, we're going to give vendors the option to stop parts of their services from working.... or something like that :)
[Nexus 6  Original Android Development] razorloves:
A new nightly is available on the download portal and it's based on the new N6F27E June monthly update from google. These are the changes for that update:

https://github.com/LineageOS/androi...mmit/747445a78fc591cbf1e729c12f5803c02fc64e38

https://github.com/LineageOS/androi...mmit/1c63a65577f2722a32a8939266fd47ac0a5d7fe8

https://github.com/TheMuppets/propr...mmit/29a6b2649c6b52362dbee500729c9a9a81fe4fc9

The radio and bootloader img in the new update from google are the same as what was in last month's update, so if you already have them, you don't need to flash them. Links are in the first post if you need them.
[Nexus 6  Original Android Development] dbrickg:
just installed 20170609. booted up without a problem. wifi and cell both working well. thanks, all
[Nexus 6  Original Android Development] BoredAtWork:
which GApps and what package (micro, nano?) is everyone using ?
[Nexus 6  Original Android Development] dbrickg:
The OP says:

But there appear to be several other possibilities. I think I'm using OpenGAPPS pico, but I'm really not sure, since it's been months since I flashed it, long before Lineage OS even existed. I've just been dirty flashing Lineage over my old CM nightly ever since Lineage started and haven't had any problems with it. But if you're coming to Lineage from anything other than CyanogenMod (or, even if you *are* coming from CM) it's probably best to follow the instructions in the OP :)
[Nexus 6  Original Android Development] giannis_mathiou:
I always used OpenGAPPS alongside with Cyanogen so I did with lineage too. I never had a problem with.

But anyone who flashes now why not follow the OP instructions?
[Nexus 6  Original Android Development] razorloves:
Bi-weekly changelog blog post https://www.lineageos.org/Changelog-11/
[Nexus 6  Original Android Development] orgert:
i read on the changelog this :

- You can now prevent tasks from being removed when clearing all apps in the recent apps view

any idea how does this work ?
[Nexus 6  Original Android Development] rivernov:
It was merged 2 days ago then I guess it will come in the next update.
[Nexus 6  Original Android Development] dwardo:
Hello,

Since last friday's "weekly" I'm regularly losing mobile data (once or twice a day - haven't figured out what causes it) and the only way to get it back is to reboot. Anyone else seeing this ?

Dwardo
[Nexus 6  Original Android Development] EminSG:
Hi!

Am I the only one who has some issues with music playback, especially Google Play Music? Sometimes app says music is playing but actually it's not

And this bug appears only in this ROM

Running latest nightly btw

Upd: seems to be resuming playback when device locks/unlocks
[Nexus 6  Original Android Development] torecdude:
I read somewhere google play music has battery issues if you are using ad blocking, but i guess its related. Maybe worth trying to disable ad blocker?
[Nexus 6  Original Android Development] EminSG:
Impossible in my case cause I don't use any ADBlock apps/modules
[Nexus 6  Original Android Development] jessyjoseph2044:
Short of going through the whole thread I have an issue I can't seem to find a fix for.

Running the newest nighly, nexus 6 shamu with all correct software.

I've had this issue for quiet sometime and it recently became a big issue.

So, since I've been running the lineage os ROM on my nexus 6 my battery seems to have issues, its not BT related I don't think since I very rarely ever use BT.

But the issue is every time my battery percentage hits 25% or lower my phone shuts off and registers that its dead, 0% battery. So I plug it in...and it shows 25% battery. So I turn it back on and it dies again, registering once again 0%.

For the longest time it did this at 15% and recently with the newest update is doing it at 25%. How can I fix this? Its a huge inconvenience.
[Nexus 6  Original Android Development] dbrickg:
It seems to be a fairly common complaint with batteries, and a fairly common suggestion to fix it: fully discharge the battery and then recharge it. The big problem appears to be figuring out exactly how to fully discharge the battery, since most phones will simply shut down when they think the battery is getting too low. The solution proposed by angourakis below is, basically, to put the phone in bootloader, which isn't so *smart* as to try to shut down automatically, and leave it in bootloader till the phone dies, then do it again, and then recharge the phone.
[Nexus 6  Original Android Development] mobitote:
Are you using greenify or some other doze related app? If you are "undoze" it that should fix it hopefully.

Or, wipe cache/ dalvik; reinstall google play music
[Nexus 6  Original Android Development] EminSG:
Nope. Clean installation without modifying system. Haven't gained root and did nothing like greenify or so.

I guess there are some issues with gaining audio focus
[Nexus 6  Original Android Development] genti.b:
I also think that it has to do with the battery, which has started to wear off or is defective somehow. My phone also shuts down or restarts for no reason, sometimes with 30% or more battery left. Furthermore, the SOT is very low, like 3h at most, no matter which ROM do I use, or settings do I apply.

I also used another method to fix this by going into the bootloader, scrolling down to bootloader logs, pressing the power button until the phone restarted itself, but to no avail.

What I'm doing now is that I bought a new battery and when it arrives I'm gonna replace the battery (by myself), which a lot of users on other XDA threads advise to do (not to replace the battery by yourself off course, that's up to you). For my part, this seems to be the only fix left for this.
[Nexus 6  Original Android Development] mobitote:
That's strange. I am on the latest ROM and use gmusic all night with headphones all night shift. Never had a problem.

I am rooted, greenified, adblocked , on latest bean gapps and latest radios and bootloader. Fyi
[Nexus 6  Original Android Development] EminSG:
Try "I'm feeling lucky" option a few times in a row. I get some problems everytime.

Don't think it's GApps problem cause I didn't have any problems with them on other ROM

The only think I did related to music somehow is that I disabled Eleven player
[Nexus 6  Original Android Development] Irisservice:
Anyone else have Camera issues...

seem like after using my camera phone runs slow and sluggish till i reboot.

Camera APP?

Any better choice for camera app?
[Nexus 6  Original Android Development] dbrickg:
I've lost track of which is which, so I'm not sure which comes with the phone by default, and which I've installed from the google store, but I use the google camera, and that doesn't give me any problems ... so far
[Nexus 6  Original Android Development] Nofe92:
Hello guys,

Is there any simple way to disable force encryption on Lineage kernel or is it a parameter set at compile time?

As much as I hate to think that my data could be stolen I would still like to have a functioning phone. Sure encryption is bearable when all 4 cores are active but as soon as temperature or charge are not optimal the phone becomes to most annoying thing ever.

And sure, I can flash the thermal.config but it still disables cores and the phone gets randomly hot (which does not happen in the un-encrypted scenario, at least not that often).

I would just use the stock rom with modified kernel if it wasn't for the aptx codec.

I still can't understand how no one ever mention it in any review....this processor and those NEON instruction are not efficient enough for encryption and it feels like the battery can't deliver what it should as soon as you reach 50-60%.

Things like this just makes me want to buy an iphone, how can I know that things like this won't happen on my next Android phone?

Btw great rom
[Nexus 6  Original Android Development] torecdude:
Delta flashed the latest build, everything is working perfectly smooth. Especially the camera!
[Nexus 6  Original Android Development] dbrickg:
downloaded and flashed the 6/16 build. seems to be working well so far

---------- Post added at 08:09 AM ---------- Previous post was at 08:07 AM ----------

"Delta flashed"? I didn't think that was possible with the lineage os builds? Obviously I'm misunderstanding something :)
[Nexus 6  Original Android Development] torecdude:
This awesome app notifies me when a new build is available and it delta flashes it :)

https://play.google.com/store/apps/details?id=com.paolinoalessandro.cmromdownloader
[MENTION=4490141]dbrickg[/MENTION]
[Nexus 6  Original Android Development] dbrickg:
Hmmm, sounds interesting. I'm still not sure what "delta flash" means in this case, since the builds show up only as a single 450Mb zip file. I thought "delta" meant that it only installed parts that had changed. But there aren't any "parts" in the lineage os builds. If someone can explain that, I'd appreciate it.
[Nexus 6  Original Android Development] torecdude:
At the first time, you need to download a full sized build to the Lineage_Downloader folder, or copy one to there if you have one. The next time it will delta update the zip file that is in that folder and flash it. It downloaded for me the latest build only 45MB.
[Nexus 6  Original Android Development] angourakis:
I know it isn't a good solution, especially when we think that the more you go from 0 to 100, the faster the battery will wear out. Unfortunately, this "solution" was the only one that seemed to work with me.

I recently switched from the Nexus 6 to a Samsung Galaxy S7 Edge and I have no problems with the battery. I'm not sure if we should blame the batteries in Nexuses and Pixels or if it's a software issue.

It's strange, because the Samsung also runs Android, and the batteries are made of the same materials... I just hope Google fix it someday.
[Nexus 6  Original Android Development] dbrickg:
Wow, that's incredible! I still don't understand how that would work. I don't know of any way to download only part of a zip file. Unless the app uses an intermediate server that unzips the file. Or maybe the lineage os servers have some special service that allows the files to be unzipped somehow. I'd sure like to know more about it.

---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------

No, I'm pretty sure there's no way to do it, other than downloading a separate kernel, one that doesn't enforce encryption
[Nexus 6  Original Android Development] dictionary:
From what I remember, it just looks at what's changed since the last update you have installed, and creates an update zip with those changes. Pretty simple actually
[Nexus 6  Original Android Development] dbrickg:
Hmm, well, that's just my point: how do you find out what's changed without unzipping the file? And how do you unzip the file without downloading it? And even if you could do that, somehow, how would you create an update zip that incorporates the changes without unzipping the file, extracting the parts that had changed, and then zipping the extracted stuff into a new zip file? I'm genuinely baffled (not that that's a hard thing to do :)

Oh, never mind ... I'm just being stupid