yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] razorloves:
Hey everyone, is the new build (without the cdma patch) working normal?

The official builds will be signed with a new private key, instead of the public test key that cm roms always used. It is a much needed move that provides a more secure rom. You can read more about that here. That will require everyone to wipe. But, some devs are trying to come up with a transition solution that avoids having to wipe. You can see the progress here:

https://review.lineageos.org/156047

https://review.lineageos.org/156327
[Nexus 5 Original Android Development] quimbexa:
Working fine for me
[Nexus 5 Original Android Development] hourwatch:
I sugest you to use face slim. It's open source, requires less permissions and uses less battery

https://f-droid.org/repository/browse/?fdfilter=facebook&fdid=org.indywidualni.fblite
[Nexus 5 Original Android Development] santi1993:
:(

will that app works with wav?
[Nexus 5 Original Android Development] santi1993:
from web is fine, you only need to use browser first marker to create a widget and voila, free facebook app :pView attachment 4002194
[Nexus 5 Original Android Development] ANDROIDRAZRM:
Will this ROM ever support CDMA networks on the Nexus 5 (i.e. is this even technically feasible?) or should I be looking into switching carriers so that I can use Nougat?
[Nexus 5 Original Android Development] mkoev:
Would apps such as cpu-z display an old battery's health as good?
[Nexus 5 Original Android Development] Co.Tibi:
Most likely. I changed my battery when it only lasted me a couple of hours. Every app i tried said that "battery health" was good. I think health doesn't equate for stamina.
[Nexus 5 Original Android Development] revik2:
Hoping that https://review.lineageos.org/#/c/64932/ will eventually get CDMA working. :fingers-crossed:
[Nexus 5 Original Android Development] metalfeild:
This built is probably the smoothest of all the lineageOS builds. Been using it for 2 days, also the battery is better.
[Nexus 5 Original Android Development] razorloves:
New nightly :good:

lineage-14.1-20170115-UNOFFICIAL-hammerhead.zip

Changelog: https://www.cmxlog.com/14.1/

Stats: https://stats.lineageos.org/
[Nexus 5 Original Android Development] Eeverion:
20170115

Works like a charm. Thanks!

Addendum: I still get the "slow charging" when I charge from a wall socket. It's just the text; the phone charges at normal speed.
[Nexus 5 Original Android Development] 7-down:
Using Franco Kernel; the text gets fixed on that.
[Nexus 5 Original Android Development] quimbexa:
Doesn't it break livedisplay and hotspot?
[Nexus 5 Original Android Development] razorloves:
I don't have custom kernel or any mods and mine says "Charging". Maybe you're only seeing 'slow' cause the battery or phone is hot and it's lowering the charge current to prevent over heating? Or maybe you're not using good wall charger? idk
[Nexus 5 Original Android Development] quimbexa:
I use the original charger and it also shows Slow Charging, almost all of the time. I think it's a bug present ever since Nougat was introduced in Hammerhead.
[Nexus 5 Original Android Development] 7-down:
Nope. I think it was fixed on the last update. Franco updated 2 days ago, try that.
[Nexus 5 Original Android Development] razorloves:
Oh, not all the time. hmm. Have any of you noticed any pattern to it?
[Nexus 5 Original Android Development] quimbexa:
It's basically everytime except for those wtf moments. I've tried quite a few chargers but it stays the same.

When I was running another ROM I had the same bug (it's everywhere), but it went away because I flashed blu spark. So I guess third party kernels have something that stock doesn't have..

EDIT: oh wait, I just tried two different chargers and the wireless one and it showed slow charging. Now I connected to the PC and it shows just Charging. Wierd...

What about the CM Browser just sharing pics for the page and not the link? What's the deal with that?

EDIT2: Ok, it works fine with apps other than Facebook Messenger.
[Nexus 5 Original Android Development] amnher:
What is your mAh on Ampere app?

What i notice on most nougat roms is that if the charging rate is above 1200mAh, it says "Charging" wherein on stock Marshmallow it shows "Charging Rapidly"

Anything below that like 1000mAh will show "Charging Slowly" while its counterpart on Stock Marshmallow is "Charging"
[Nexus 5 Original Android Development] aaargh777:
For me it always shows slow charging regardless which charger I use, however, real charging speed seems to be normal.

Happens to me since I use CM/Lineage Nougat Rom (which is the first and only Nougat Rom I used)
[Nexus 5 Original Android Development] quimbexa:
Maybe we should just change the text?
[Nexus 5 Original Android Development] Co.Tibi:
I'm experiencing the same thing. Original charger shows as slow charging, a 2.4A fast charger shows as slow charging also. The same fast charger but on a second output with a regular 1.2A current shows as just charging. Weird

---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------

On slow charging it's really slow to charge. It's not just text
[Nexus 5 Original Android Development] mimox:
I accidentally flashed the last build offered by the CM update service. This took me from CM 13 to 14. After manually flashing Gapps, things seemed to work fine first but now often messages from e.g. WhatsApp do not arrive until WhatsApp is started manually.

Is this a known bug in the final CM build or do you think it is caused by dirty flashing?

Also, is such a bug known in the current LOS build?
[Nexus 5 Original Android Development] GR0S:
You have to use older camera app since Nexus 5 isn't supported anymore
[Nexus 5 Original Android Development] glocksman:
Thank You

..for the unofficial nightlies.

So far I haven't ran into any issues, but other than web browsing and occasional pictures, I'm not that much of a heavy user.

Anyway, I haven't felt the need to migrate back to the last CM13 snapshot.

Thanks again for your hard work.:)
[Nexus 5 Original Android Development] razorloves:
New nightly :good:

lineage-14.1-20170117-UNOFFICIAL-hammerhead.zip

*NOTE: As we've discussed previously, the change that removes su (root access) has now been merged. More and more apps are no longer working on rooted devices, so now it will be possible to use lineage with those apps, without the user having to do some hacking to remove su.

There will be an su addon zip provided by the lineage team for users that want to add root access to the rom. But since this addon zip is not available yet, my unofficial roms that I post here will continue to have root. I will let you know when I remove root from my builds.

You can see the discussion about su removal here.

*SURPRISE* There's a new change included in this new nightly. I don't want to spoil the surprise so I'll let you see it for yourself. :D

Changelog: https://www.cmxlog.com/14.1/

Stats: https://stats.lineageos.org/
[Nexus 5 Original Android Development] sethjustseth:
Geeze, I'm used to flashing every other, but I'm too curious--I'll have to try this build now!

Also, not everyone has problems with their device. Mine has been running great and I've been dirty flashing every other release ever since CAF was discontinued and I switch over. My battery is consistently 3.5-4h sot which is pretty good for a 2.5 year device! Thanks for all the support razorloves!
[Nexus 5 Original Android Development] Eeverion:
I love it! It looks nice. :cyclops:
[Nexus 5 Original Android Development] gregfrankenstein:
In the future, after flashing the SU addon, will there still be built-in access control in Privacy Guard?
[Nexus 5 Original Android Development] Karan_Brar:
Download bait above 10000
[Nexus 5 Original Android Development] suchks:
Is the protected app feature working with Pixel Launcher? I get a crash of the Pixel Launcher whenever I try to open a protected app. I installed Pixel Launcher via gapps.
[Nexus 5 Original Android Development] Vinicius Bode:
Lost all the permissions and most settings today. I didn't do anything to trigger it, the phone died and when I turned it back on it went to that initial LineageOS screen, and that's it. No data loss, but I'll have to setup the device all over again and it takes a bit of time. Can you enlighten me on what could've happened? Because I have literally no idea and I don't want that to happen again.

Edit: I forgot to mention that the Device ID was also changed. Which got me even more scared
[Nexus 5 Original Android Development] osm0sis:
I'll be curious to see if this change makes my tap banking app "RBC Wallet" happy, since currently not even unrooting the ROM appeases it.. (and yet SafetyNet passes..)
[Nexus 5 Original Android Development] razorloves:
1440mA when I was at 74% charge, and it showed "Charging". But later when I was at 80% charge, it was down to 1020mA and showed "Charging Slowly".

Here's the code that determines what charge speed is shown on the lockscreen. It's the same in aosp too.

https://github.com/LineageOS/androi...ckages/Keyguard/res/values/config.xml#L26=L30

yes

weird. don't know what could have caused that. no one else has reported that.

This change in lineage would be the equivalent of deleting the su binary and su symlink in system/bin and system/xbin. So if you did that before, I guess maybe your banking app is looking at something else too. Idk
[Nexus 5 Original Android Development] amnher:
That's why. Its suppose to be Charging rapidly on 1400 may and "Charging" on 1040mah if we base on stock MM of nexus 5
[Nexus 5 Original Android Development] osm0sis:
Yes, it does seem that way since that is my current setup. Though I'm curious if the name change from CM to LineageOS alone will resolve it, since even CM's zImage kernel string would trigger SafetyNet.
[Nexus 5 Original Android Development] quimbexa:
We need this change to get the charge speeds right again..
[Nexus 5 Original Android Development] 7-down:
What is it? :confused:
[Nexus 5 Original Android Development] quimbexa:
Soft reboot and enjoy
[Nexus 5 Original Android Development] frauhottelmann:
You could make it show charging extremely fast on the lock screen, but that would change anything about the actual charging rate! The text is determined by the charging rate, not the other way! Changing the threshold for the text shown doesn't change anything...
[Nexus 5 Original Android Development] quimbexa:
But takes shows the correct rates given the Nexus 5 hardware. Nougat wasn't concieved for our phone so it will always show slow charging although it's charging at the normal rate. That's the adjustment I'm proposing. Basically copy past from the marshmallow tables.

Edit: are we having blur back? :)
[Nexus 5 Original Android Development] amnher:
I think in MM stock this is the standard for Nexus 5

1100mAh and above = "Charging Rapidly"

in between is "Charging"

500mAh and below = "Charging Slowly"

while in accross in all nougat roms for Nexus 5 everything below 1100mAh is "Charging Slowly" and above 1100mAh is "Charging" which I think is wrong
[Nexus 5 Original Android Development] fence:
Fast charging currents have dramatically increased since hammerhead's release in 2013, therefore what is fast charging for our device is slow by modern hardware standards. Hence the Nougat charging text is inaccurate and should be reverted to Marshmallow behaviour.

Also I'm seeing a lot of commits for other devices regarding SDCardFS, are there any major performance advantages to this over FUSE and if so could it be enabled on hammerhead?

Finally battery life on [MENTION=614507]razorloves[/MENTION] current build is phenomenal :good:
[Nexus 5 Original Android Development] kissme99:
I want to give a try to this ROM. Can you tell me, is there any major bug? And, which gapps should I flash to get fully working camera? I saw some posts, that in the newest version of Google Camera HDR doesn't work.
[Nexus 5 Original Android Development] fence:
No major bugs for me, occasional settings FC but thats about it. Use opengapps but don't let it install Google Camera, instead get an apk of hammerheads last supported version 3.2 and install manually.
[Nexus 5 Original Android Development] Respect!:
Five hours? Really phenomenal!

How? Wich kernel?
[Nexus 5 Original Android Development] fence:
Just the stock lineage kernel. I've always found custom kernels to either be placebo or worse in terms of battery life. Also this was with mobile data switched off and location set to battery saving as I was at home the whole time. I get a fair bit less when out and about as I use mobile data and high accuracy for location.
[Nexus 5 Original Android Development] crisis_trustee:
New Lineage-14.1 bootanimation
[Nexus 5 Original Android Development] GR0S:
Can I switch from CAF to aosp without wiping on cm14?

I know it worked out fine on cm13
[Nexus 5 Original Android Development] ssauger:
Same as on CM13 you can dirty flashes LineageOS 14.1 CAF <> AOSP

sent from Nexus5
[Nexus 5 Original Android Development] tom0769:
As always, dirty flash could be the 1st try and then see, how things behave.

If you run into trouble, do a clean flash and restore apps/data with e. g. TitaniumBackup.

Your nandroid backup will save you from data losses.
[Nexus 5 Original Android Development] mkoev:
Guys, I have a problem with notifications from whatsapp, viber, etc. Problem is that after I restored from a twrp backup those stopped popping up, I must manually go into the app to get the messages. Occurs on both data and wifi. I was on the build from Jan 6th and it was working great until after the restore:( I dirty flashed latest nightly, but problem still occurs. Any ideas? Using twrp 3.0.3-0.
[Nexus 5 Original Android Development] armando_rod:
Restore what exactly? Maybe your GCM ID changed and you restore data from another build with an old ID, if that happens push notifications stops working
[Nexus 5 Original Android Development] fence:
I once had a similar issue, never found out what happened but I seem to recall a factory reset sorted it out.
[Nexus 5 Original Android Development] thedamager:
I experienced something similar when restoring fron TiBu. Try this:

Backup the app data using built-in in-app mechanism

Uninstall the app

Install again from Play Store

Restore the app data using built-in in-app mechanism
[Nexus 5 Original Android Development] razorloves:
It's currently being worked on https://review.lineageos.org/#/q/topic:charging-sounds-settings+(status:open+OR+status:merged)

That won't help. The sound file is not missing. The setting is just broken. See link above. Just fyi ;)

It's new and a bit too buggy for my taste. If you look at the sdcardfs changes in the changelog, a lot of them are reverts. Google is working on it and applying fixes, so I will revisit in the future.
[Nexus 5 Original Android Development] razorloves:
New nightly :good:

lineage-14.1-20170119-UNOFFICIAL-hammerhead.zip

Changelog: https://www.cmxlog.com/14.1/

Stats: https://stats.lineageos.org/
[Nexus 5 Original Android Development] batman2142:
Can I dirty flash this over p4rot's unofficial build - 2nd January nightly? I think it was a CAF version, is this one CAF too?

Do I need to flash GApps again after it or will a dirty flash with Wipe Cache work fine and keep all my apps the way they are?
[Nexus 5 Original Android Development] SubAtomicFlux:
No this is not a CAF ROM.

You should probably wipe /system & /data when coming from another branch to avoid conflicts and other errors, this makes things easier in the long run personally, even if it isn't strictly necessary. Just remember to make a nandroid in any case.

Obviously you will have to Flash Gapps if you wipe /system. I recommend using the December 15th release as, from what I've heard, the setup is broken after that. osm0sis may correct me if I'm wrong on that point.
[Nexus 5 Original Android Development] mkoev:
Complete restore. I backed up data. system, etc from TWRP, wiped data, tried another ROM, did not like it and restored the Jan 6 build. I did not restore data from another build. I later flashed the build from Jan 17 over the one from Jan 6th after I had restored it, but problem still occurred. Will try to back up messages , uninstall and then reinstall Whatsapp :)
[Nexus 5 Original Android Development] quimbexa:
"can't connect to camera" error. Anyone had this? I know this is pretty common on CM, had it in other devices as well. What's the fix?
[Nexus 5 Original Android Development] ebinzzi:
Really nice ROM, keep up the good work :good:
[Nexus 5 Original Android Development] cyprox:
I installed Pixel launcher from play store and moved it to /system/app so the swipe for google now works. The problem is that it of course gets deleted everytime i flash a new nightly. Can i do some thing to fix this?
[Nexus 5 Original Android Development] Julosch:
Yeah, just download and flash open gapps aroma and choose to install pixel launcher and the necessary applications like wallpapers etc. then it should stay.
[Nexus 5 Original Android Development] cyprox:
Can you delete Aroma afterwards? It was pretty big, 878 MB...sorry never used this before, just got back from living with stock for a few years :)
[Nexus 5 Original Android Development] Paolo_lav:
[MENTION=614507]razorloves[/MENTION]

In both builds, caf and non-caf, there are some problems in using streaming app like Google Play Movies and it seems DRM issue.

More info in the last post of THIS page and in those following.

[MENTION=4145479]experience7[/MENTION] is trying to figure out the issue here https://review.lineageos.org/#/c/157122/ for hammerheadcaf.

Thank you for your work!

EDIT: logcat attached to this post.
[Nexus 5 Original Android Development] Julosch:
Well, I did, and it is still working :P I hope it will work for you too
[Nexus 5 Original Android Development] razorloves:
It's not just nexus 5 issues. It's been a problem since day 1 of cm14.1 on numerous devices.

Many lineage device maintainers have been attempting to fix it by using drm & widevine blobs from newer nexus devices. You can see all these changes on gerrit over the past couple months. Sometimes it works, most times it does not. Sometimes they'll get google play movies to work, but then netflix will be broken. Then they fix netflix, and google play movie will be broke again. Like playing whack-a-mole. lol.

But I'll try to take a look at it today and see if I get lucky.
[Nexus 5 Original Android Development] gr-e:
Is there any way to disable battery LED with screen on?
[Nexus 5 Original Android Development] theShadow800:
[MENTION=614507]razorloves[/MENTION] Is there some way to disable the screenshot and camera shutter sounds while the phone is on silent mode? I have been deleting the camera click.ogg to make it permanently off, but it would be convenient it could be implemented.

Thank you!
[Nexus 5 Original Android Development] razorloves:
They already are. I just checked both.
[Nexus 5 Original Android Development] theShadow800:
For me both in vibrate only and in do not disturb's total silence the screenshot click and camera click plays. Im using osmosis' google camera zip btw
[Nexus 5 Original Android Development] razorloves:
For anyone that can test video on demand apps, like netflix, google play movies, hulu, amazon, myCanal, etc...etc...

please try out this new nightly and let me know if those work. thanks

lineage-14.1-20170119-UNOFFICIALdrmfix-hammerhead.zip
[Nexus 5 Original Android Development] Paolo_lav:
Great! Google play movies now works! Unfortunately I haven't accounts for other apps to test them. Thanks
[Nexus 5 Original Android Development] WSeb:
I confirm Google Play Movies and MyCanal work well now. LaBox TV still crash (it's probably a Nougat compatibility problem). Great work Razorloves. Thanks !

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] gregfrankenstein:
EDIT: ignore this post. I couldn't remember where the setting was to change lock screen icons and thought maybe it wasn't in the unofficial build yet. If anyone's curious, it's in security; hit the gear next to "screen lock". I'm not smart.
[Nexus 5 Original Android Development] sethjustseth:
Netflix worked fine on 20170117 and still works on 20170119drmfix.
[Nexus 5 Original Android Development] caliban2:
Netflix and Amazon work fine on drmfix-version.

Which is good, because they were also fine on every cm14/LOS nightly I used since mid-december. Just hope any fixing attempts won't breake them for me. ?
[Nexus 5 Original Android Development] osm0sis:
Yeah it's all good now since like Dec. 28. :)
[Nexus 5 Original Android Development] armando_rod:
Dont know the exact commit changelog for 20170119 but it boots way faster than other builds
[Nexus 5 Original Android Development] swapnildixit3:
I didn't felt any difference
[Nexus 5 Original Android Development] razorloves:
Awesome. Thanks for testing. I merged the fix. :good:

https://github.com/TheMuppets/propr...mits/9c021fb0ed29fe4a317221d7b59f6c98f9dc9966
[Nexus 5 Original Android Development] metalfeild:
Same here since I first flashed CM 14.1 i.e October last year I guess, flashed other roms and wiped the phone a numerous times since then. These sounds even play on alarm only mode.
[Nexus 5 Original Android Development] razorloves:
Paging [MENTION=4544860]osm0sis[/MENTION] ... cleanup on page 69. :D
[Nexus 5 Original Android Development] osm0sis:
It's just the same APK as from the Play Store, but re-signed to make it not auto-update, and the libraries have been deflated within the APK so that they will be read correctly from the /system partition.

No code/smali has been touched, so there's really no explanation there.

More importantly though I also can't reproduce the issue. I'm using the final CM14.1 build, and the shutter sound and lock sounds, etc. all properly play and respect Do Not Disturb.
[Nexus 5 Original Android Development] theShadow800:
Okay, so I guess I'll just make a backup and do another clean flash

Thank you :)
[Nexus 5 Original Android Development] rompip:
Does "extended power menue" only not work for me or is a bug in the latest nightly (19.1.2017)?

Edit: my bad, works fine!!!
[Nexus 5 Original Android Development] razorloves:
Ah, ok. I figured it was your zip causing it since it's not a problem with the rom by itself. Apologies. :o

Guess they are flashing something else to cause the issue. Or maybe some app is doing it.
[Nexus 5 Original Android Development] theShadow800:
So I clean flashed latest lineage build, tried both open gapps and dynamic gapps (if they even make a difference wrt the issue) and didnt flash anything else, and right after the boot on the setup screen if it put the phone on silent and then take a screenshot, the click sound is there

So like I don't understand what might be causing it at my end, any idea?
[Nexus 5 Original Android Development] razorloves:
hmm, idk. did you wipe system?
[Nexus 5 Original Android Development] theShadow800:
Yup wiped every partition except my internal storage
[Nexus 5 Original Android Development] razorloves:
Some good info for everyone:

http://lineageos.org/Update-and-Build-Prep/
[Nexus 5 Original Android Development] malek_anas_97:
Just in time ??

I'm getting super excited hehehe

I'm on the latest factory image rooted and have twrp installed and ready for it

Should I flash one of your builds and then update to the official one or just wait for it ?
[Nexus 5 Original Android Development] planet33:
When I send a message in Allo, the app emits a strange sound like an interference
[Nexus 5 Original Android Development] metalfeild:
Same here man have tried everything. Not a big deal but seems like only we both are having this issue.

Edit: Never tied custom kernel though, have you?
[Nexus 5 Original Android Development] osm0sis:
I believe [MENTION=6404745]MastahF[/MENTION], [MENTION=5849464]mikeoswego[/MENTION] and I have previously come up with a possible fix you could incorporate for the resetting app permissions for the CM -> LineageOS migration builds to make it more seamless. :)

See Mike's "Major updates" and my "v8" commits in my gappsintegrator experiment repo:

https://github.com/osm0sis/gappsintegrator/commits/master