yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] RockyTV:
I used the Pico package from OpenGApps, it comes only with the Package Installer and the Play Services. Anything else you may need you can then install from the Play Store.
[X 2014 Original Android Development] alx1880:
I ran into this problem yesterday. I kept it charging for 10 minutes even with the "?" on, manually rebooted into recovery, then booted into system and kept charging from there.
[X 2014 Original Android Development] fabiozon:
Does this prompt you to restore apps/data from the cloud? Is the battery any better than it was on the unofficial CM 14.1?
[X 2014 Original Android Development] Vicalvi:
Guys, what is the correct way to do a dirty installation by TWRP? Do I install the latest rom and then the Gapps over the old install?
[X 2014 Original Android Development] ThomSlo:
1. Go to TWRP. Clear cache/dalvik.

2. In the TWRP recovery, flash the new ROM files

3. Flash GAPPS

4. Flash Custom Kernel (optional)

5. Reboot to system

If You have problem with storage space go back to TWRP and agian clear cache/dalvik.
[X 2014 Original Android Development] Gus Ghanem:
Dec. 6 Nightly:

CM Camera: switching to video is causing a reboot. Clear the camera's data, and don't switch to video for now.
[X 2014 Original Android Development] ffoo3d:
No Widevine on 20161205 nigthly build

Hmm, it looks like de Widevine DRM agent is not implemented or not implemented correctly.

All apps using widevine drm do not work (ex. Play Movies, Molotov.Tv)
[X 2014 Original Android Development] vista178:
Has anyone had success with the recoveries? I'm thinking the issues I'm having with them may stem from this yet-to-be-merged patch - https://review.cyanogenmod.org/#/c/174166/
[X 2014 Original Android Development] invisiblek:
FYI: If you're posting bugs in this thread without logs, you're completely wasting your time.
[X 2014 Original Android Development] RockyTV:
Unfortunately not, I think. I installed it yesterday and it didn't prompt me to restore apps and data from cloud.
[X 2014 Original Android Development] danielcepa:
https://review.cyanogenmod.org/#/c/174333

Mic fix incoming. Fingers crossed
[X 2014 Original Android Development] Aroch925:
The only big problems I'm having (other than the ones already reported) are that my phone is stuck on 3g and it freezes when trying to discover Bluetooth devices. The 3g problem seems like it's an xt1096 problem. And the Bluetooth problem has been there since cm13. Here's a log
[X 2014 Original Android Development] tj13:
Is the mic problem with just recording? Does it work with phone calls?
[X 2014 Original Android Development] fabiozon:
Ok, good to know. There's a fix on the crDroid thread; you have to flash something after Gapps and it works.
[X 2014 Original Android Development] archerscope:
i just install this app and set permisive the SElinux and is working for all now

http://xdaforums.com/devdb/project/dl/?id=12506
[X 2014 Original Android Development] GustavoAvellar:
No, the mic does not work with several apps (Dialer, WhatsApp, Google Assistant, Google Voice Keyboard).

It works after setting SELinux policy to permissive.
[X 2014 Original Android Development] Cybertron713:
For anyone that doesn't know how to set SELinux to permissive, there's an app that makes it really easy to do, SELinuxModeChanger: http://xdaforums.com/showthread.php?t=2524485&page=51
[X 2014 Original Android Development] Sdobron:
Worked fine with a phone call I made last night on speaker phone... Haven't tried anything else
[X 2014 Original Android Development] sendmespammails:
I have XT1095 and got the same problem. it doesn't seem to connect to LTE, I can only force it to 3g and connect to H+
[X 2014 Original Android Development] bernardo94:
Once i have this issue, the problem is the APN its not properly configurated... Search a APN of your company and change manually

Enviado desde mi XT1095 mediante Tapatalk
[X 2014 Original Android Development] bbs2web:
Got it working by clearing Google Play Services data and following the same steps again.

Back on 20170317 now...
[X 2014 Original Android Development] dego_:
You'll never get bored with a custom ROM :)
[X 2014 Original Android Development] ericcostes:
good remark !

;)
[X 2014 Original Android Development] dlfollmann:
True. My phone powered off around 19pm, when I had just arrived home, because it was low on battery. Now (20:20pm) it is stuck in a bootloop.

I was using 0317 version with Evolution Kernel, and so far all was ok.

Will let it charge a couple of hours, then we'll see.
[X 2014 Original Android Development] Eduardo.s:
Here happened the same thing in the update of the day 17 finished the battery and did not start more, It was in the ROM logo and it vibrated every 3 seconds, I had to do a new clean install
[X 2014 Original Android Development] dlfollmann:
Had no luck reinstalling ROM. Cleaned system, cache, dalvik, data, reinstalled rom; tried installing another rom (sideloading and pulling it in with adb), no luck either. Tried older version of LineageOS too, same result.

I gave up.

Right now charging it to install official firmware with RSDLite.

My only luck is that I don't have nothing really important on the phone.
[X 2014 Original Android Development] RockyTV:
Same thing happened to me a few weeks ago, I tried reinstalling Lineage but it didn't work. I just installed the stock ROM and then reinstalled Lineage.
[X 2014 Original Android Development] BootloopedMillennials:
This battery drain is getting a little crazy and I know its not my battery going bad. Android system at 20% battery, 615 mAh used. Android OS at 11%, 333 mAh with over 3hrs 35min keep awake.
[X 2014 Original Android Development] RockyTV:
So, the same thing happened to me today. I was at ~35% battery, battery saver on. Turned on Snapchat, suddenly my phone reboots. I thought it was dead because that always happens with Snapchat, but then when I turned it back on, it rebooted again and was stuck in a bootloop (stuck in the Lineage boot screen).

I tried fetching some logs, but for my surprise, here's their content.

cat: can't open '/proc/last_kmsg': No such file or directory

/sbin/sh: exec: line 1: logcat: not found

My guess is that something weird is going on behind Lineage's code and is wiping the kernel.

EDIT: dmesg is not empty, attached it to the post.

EDIT2: tagging [MENTION=2385005]invisiblek[/MENTION]
[X 2014 Original Android Development] dego_:
curious, who's brave enough to try a new weekly build :)
[X 2014 Original Android Development] ericcostes:
lol !

;)

I will be se second brave if you want ! :angel:
[X 2014 Original Android Development] SkullDeath:
The only check-in for Victara kernel this week seems to be for updating version string, was that causing the reboots or am I missing something ?
[X 2014 Original Android Development] BootloopedMillennials:
Ill be the Guinea pig. My Moto X is a backup of a backup nothing to lose.
[X 2014 Original Android Development] GustavoAvellar:
I can confirm that this procedure restored my Moto X from bootloop.

But I did it with the following builds:

LineageOS 20170228

OpenGApps Nano 20170208

LineageOS 20170317
[X 2014 Original Android Development] ericcostes:
for not sufficient because I also lost my root too > have to reinstall the special root arm program from lineageos site
[X 2014 Original Android Development] ericcostes:
dring dring, it is available for test !!!

:)
[X 2014 Original Android Development] BootloopedMillennials:
Its not on the download site yet.
[X 2014 Original Android Development] vista178:
Flashed without hesitation. Was not disappointed. It worked.
[X 2014 Original Android Development] BootloopedMillennials:
Worked here
[X 2014 Original Android Development] SkullDeath:
Updated from which build?
[X 2014 Original Android Development] vista178:
20170317
[X 2014 Original Android Development] ericcostes:
:p:D
[X 2014 Original Android Development] SkullDeath:
Flashed now, everything seems okay [emoji106]
[X 2014 Original Android Development] raynayx:
There's a new update on the lineage site. Anyone tried?
[X 2014 Original Android Development] vista178:
It doesn't read.
[X 2014 Original Android Development] Gus Ghanem:
March 31, 2017 Build seems fine; I flashed it clean from stock, twice, once with Open Gapps, then again with Delta Gapps, no issues, no errors, no crashes, no bootloops. Too early still, but seems stable so far.
[X 2014 Original Android Development] ericcostes:
that's good for me too

:good:

this version has corrected the not cleared downloaded queue, nice:p

I wonder why the build size is 2MB more than the precedent ???
[X 2014 Original Android Development] defdice:
Dirty flashed the mar 31 build over the mar 17 build on verizon 1096. All working great so far.

Interesting side note. I finally decided to unlock bootloader and give Lineage a try.....on March 24. Surprise and a slight amount of panick. Anywho, been using the mar 17 build since and What a Great ROM. Finally love my phone again. Only have/use 64 apps, but I have been only loosing about 5% battery overnight. All hail the Lineage Devs.

and invisiblek!!! :victory::good:
[X 2014 Original Android Development] raynayx:
Will this ROM get a theme engine any time soon?
[X 2014 Original Android Development] dego_:
With Greenify night battery drain can be even less.
[X 2014 Original Android Development] kedar a.k.a. 3K:
Cyanogen theme engine has been scraped , try using substratum instead
[X 2014 Original Android Development] dego_:
After latest update my phone shows a new available build and the release date is January 1, 1970. Nothing critical, but a bit weird.
[X 2014 Original Android Development] kedar a.k.a. 3K:
So lineage os was planned all along , from such a long time ago.
[X 2014 Original Android Development] BootloopedMillennials:
This seems excessive. guess is because I blocked internet access to Setup Wizard but why does that need access long after setup
[X 2014 Original Android Development] dego_:
I can confirm that Substratum themes work smoothly on Lineage.
[X 2014 Original Android Development] joseph_1802:
Here are some GSAM stats, showing Android OS and Android System as some of the top usage apps. I hope they help.
[X 2014 Original Android Development] fabiozon:
The last build has wrecked the battery life. Android system is eating 20%.

How can I give you a useful log?
[X 2014 Original Android Development] hrncs:
yes similar here :(

and the signal of carrier is low
[X 2014 Original Android Development] ericcostes:
same here : signal low and very bad quality in 3G mode

:(
[X 2014 Original Android Development] Beneduzi:
After the 24/03 update the screencast/airplay/DLNA stop working, just me or anyone else?
[X 2014 Original Android Development] Gus Ghanem:
April 7, 2017 Build, dirty flash went fine. You get a really aweful boot animation, and a Br0zip icon that's basically just a file manager, both April fools stuff, in case you haven't read the blog.
[X 2014 Original Android Development] petrena:
WiFi not reconnecting

Hi,

I have a problem after leaving WiFi at home and returning home, my phone doesn't reconnect automatically, I have to restart the phone.

Had this problem also with other phones with Lineage, might this be OS related?
[X 2014 Original Android Development] julian.c28:
I have this problem often. I live on campus and I have to constantly restart my phone :(
[X 2014 Original Android Development] dego_:
Same happens quite often with my office wifi network.
[X 2014 Original Android Development] thetakerfan:
FYI for the issues with reconnecting to WiFi, you can toggle airplane mode off and on to get it back instead of having to wait for a full reboot of the phone. I was doing the same thing until someone mentioned that awhile ago.
[X 2014 Original Android Development] vista178:
Yes, airplane mode toggle fixes the issue. I'm not sure​ how capture the log for this problem. Any suggestions?
[X 2014 Original Android Development] RockyTV:
You can also toggle WiFi on/off, so it will reconnect to your WiFi network.
[X 2014 Original Android Development] dego_:
it didn't help in my case
[X 2014 Original Android Development] julian.c28:
I'll try the airplane mode toggle the next time I get disconnected, thanks for the tip!
[X 2014 Original Android Development] fabiozon:
The April 7 update is working flawlessly!

Clean flashed with openGapps and the lineageOS superuser.
[X 2014 Original Android Development] shawndak:
April 7th update is working well. Will update with battery life later. Every time I update the WIFI Scanning turns back on. That seriously KILLS your battery. This should be default off!

Also camera with flash kept crashing, wiped data of the app and now works fine.

The new boot animation is fun, but could we do it with a black background for battery reasons and night time turn on. It blinds you restarting at night!!! I know AMOLED screens do use less power with darker pixels as well

Thanks for the great ROM!
[X 2014 Original Android Development] shawndak:
*Update

What's with the poor battery life on the past few updates??? I'm barely getting 3hr OST when a month ago I was at 4-5 hrs.

I believe the late Feb - early Mar update was the best for battery life.

I actually might downgrade as this hasn't gotten any better for a month now.

https://xdaforums.com/showpost.php?p=71241722&postcount=452

Also can we once and for all fix the incorrect battery percentage shut off issue?
[X 2014 Original Android Development] LexX-V:
Founded bugs in lineage-14.1-20170407-nightly-victara-signed

Here is the list of founded bugs:

1. In the Gallery at the zoom of the image. If you do nothing 2 seconds, then all buttons disappear (it should be so) and the zoom is dropped to the center of the image, and not in the image area where I was.

2. When you try to take a photo in the dark (the flash is auto), the camera makes a flash and falls. The image is not saved. Is the camera trying to shoot in HDR and falling? I'm in the auto-HDR settings.

3. After the reboot, the time is reset.

I've already posted these bugs on jira.lineageos.org
[X 2014 Original Android Development] shawndak:
Delete data in camera app and report back.
[X 2014 Original Android Development] LexX-V:
It helped. How much will it work?
[X 2014 Original Android Development] shawndak:
I haven't had an issue now the past couple days so I assume permanent. I noticed it on an earlier update as well.
[X 2014 Original Android Development] midnightdevil66:
Dirty flashed 4/7 over 3/10, so far been running whole day line a champ. So far no issue to report.
[X 2014 Original Android Development] SkullDeath:
I've got the incorrect battery / shut down at 20% issue with April 7 build again. The only other change from previous builds is that I had to encrypt the phone for installing Airwatch.

Today's build has failed ☹️
[X 2014 Original Android Development] lichengqi:
April 07 drains battery fast, often stops at 82%

Anyone the same?
[X 2014 Original Android Development] BootloopedMillennials:
Yep drains fast. Even on clean install. It will be fine for awhile and then LineageOS system goes crazy with battery drain.

I'm legit frustrated with this phone. My Nexus 6 is running a similar setup without this issue.
[X 2014 Original Android Development] lichengqi:
Hope the coming update may fix this issue.
[X 2014 Original Android Development] lichengqi:
Time reset after reboot.
[X 2014 Original Android Development] shawndak:
The battery drain is terrible!!! Honestly the last time I got excellent battery was the late Feb update. Its gotten consistently worse since. Do the Devs know about the battery life issue??? I'm getting 2 hour OST when I used to get 4+!!!
[X 2014 Original Android Development] CaptainGoSlow:
I clean installed 07/04 build with mini OpenGapps and getting good battery life. Sounds like more to it than it being just Lineage causing the drain.

Cheers devs for supporting the X 2014.
[X 2014 Original Android Development] RockyTV:
You do realize that the phone get its time from NTP, so when you reboot it has to connect to the internet before retrieving the correct time.
[X 2014 Original Android Development] pokereth:
Why? I've noticed this and admit to being frustrated by it. Does the phone not have an internal clock? Can it not be set? The fact that every time I reset the phone it is off by the exact same number of hours and minutes from the correct time suggests the phone has an internal clock, but it isn't being set for some reason.

This bugs me because when I restart the phone I often have to cancel alarms that were set for many hours previous.
[X 2014 Original Android Development] kedar a.k.a. 3K:
I think the phone gets the time from the cellular network rather than the internet , at least that was my experience on my older phone. Have you set any secondary time zones in the clock app? Do you have any SIM card inserted?
[X 2014 Original Android Development] pokereth:
My question is, why does it need to get the time at all? Why can't it remember it from before I rebooted? Of course it needs to check periodically to see if the time is still correct, and I think you're correct that it uses the cell network, not the internet.

But notice that 1) this happens every time I reboot, and 2) the clock is always at the same wrong time when I reboot (something like 4 hours and 4 minutes before the correct time). This implies that the phone has an internal clock, but it is set wrong and is not being set correctly when Android sets itself.
[X 2014 Original Android Development] julian.c28:
Is this why whenever my phone turns back on my alarms from the morning randomly ring for about a second or two before shutting off? That would make a lot of sense...
[X 2014 Original Android Development] pokereth:
It's exactly why. If you look carefully you'll see the time change at the same time.
[X 2014 Original Android Development] G4 Man2:
I can't remember the last time I didn't have alarms go off after rebooting. I can confirm it's not an issue of the network setting the time and then ntp changing it. I use Google Voice for everything so I always have airplane mode on and still get this issue.
[X 2014 Original Android Development] lichengqi:
When's the next nightly?
[X 2014 Original Android Development] dlfollmann:
Normally they are released on fridays.
[X 2014 Original Android Development] Gus Ghanem:
Probably Friday, as is usual for Victara, if the build doesn't fail yet again... I just got Lineage 7.1.2 on my Nexus 7 2013 flo.
[X 2014 Original Android Development] Jaytn:
That doesn't seem to make sense to me - if you're on airplane mode, how can you use Google Voice? Do you mean you are on WiFi only (no cellular)? Then your phone will update the time over the network, via NTP (= Network Time Protocol).

I have that exact setup (airplane mode + WiFi on) and just double checked - after reboot time was wrong (exactly 2:55pm instead of 1:57am) until I connected to WiFi when it switched back.
[X 2014 Original Android Development] G4 Man2:
Wifi only, no cellular. I was making the point that the cellular network doesn't seem to make a difference. It seems like there is in fact a hardware clock that is not being updated and is then overridden via NTP.
[X 2014 Original Android Development] alanzhoffmann:
The wrong time is the same one that shows on TWRP. I tried adjusting it, but after a reboot it goes back to what it was before
[X 2014 Original Android Development] pokereth:
Exactly. This is what leads me to believe that the time is set wrong in the phone ('hardware') clock. A few seconds after booting the phone--using cell or internet data--appears to update the time inside Android (e.g. 'software' clock). But for some reason it doesn't also correct the time in the hardware.
[X 2014 Original Android Development] G4 Man2:
A solution for the hardware clock being off seems to be running the command hwclock --systohc which sets the time according to the current system time. The problem with this solution is that the LineageOS kernel doesn't seem to support this as it results in an error. It looks like we would need to either flash a kernel that supports this and then run the command or try a different rom, run the command, and then switch back.
[X 2014 Original Android Development] Beneduzi:
You have to run this kind of query as root, at least in regular linux. Normal user dont have direct accesses to base kernel devices, just like shutdow a module or service.

And by the way, the clock is realy off set

OK, I tested it a bit more and the kernel just cant see the real hardware clock, I poked it a little bit, but I dont want to get a kernel panic, and clocks are pretty good in doing it. It appears that, this current kernel is using the wrong module for our device. But I cant find the correct module.
[X 2014 Original Android Development] lichengqi:
Thanks

---------- Post added at 01:08 PM ---------- Previous post was at 01:06 PM ----------

Looking forward to further discovery
[X 2014 Original Android Development] Jaytn:
Then I misunderstood. That's exactly my thought as well.

Though I thought that sometimes the RTC is just a simple ticking (non changeable) clock and the corrected local time is saved as an offset from that - at least that's what I recall from some older PCs, might be wrong there.
[X 2014 Original Android Development] dagmoller:
Please devs, update thread title to [OFFICIAL][WEEKLY][7.1.1] LineageOS 14.1 for Moto X 2014 (victara)
[X 2014 Original Android Development] G4 Man2:
As it turns out this is a known issue because the RTC driver on Qualcomm chipsets are read-only. The time ends up being reset during some flashes and when it's reset it goes all the way back to 01/01/1970. As I said in my last post, some people have had some luck being able to change the RTC time using different roms and kernels. Most of the success I've seen is from people using more exotic roms like MIUI. So if it's really bothering someone, you could try flashing MIUI and running

hwclock --systohc

However, there's a real possibility that the RTC time will be reset during another flash so it's probably not worth it.

A fix for this issue would be abandoning the RTC altogether and implementing a utility that can actually be written to. I believe Sony has something like that.

I've been running desktop Linux for most of my life now, I'm running a root command just about every day :p
[X 2014 Original Android Development] dego_:
they keep the ghost of dead CM with us :)
[X 2014 Original Android Development] dagmoller:
I think there is a problem with notifications or GCM...

Sometimes it take too long time to notify on new messages (telegram, gmail, etc...) even in wifi or mobile network.

So when I take de device and unlock/turn on screen all notifications apear at same time.
[X 2014 Original Android Development] BootloopedMillennials:
I dont have these issues on the latest build. The others are either features or apps I dont use, no comments there.
[X 2014 Original Android Development] InnerSanctum:
Mario Run doesn't work on rooted devices, sadly. It only works on devices which SafetyNet passes, so if your devices is rooted, you can try unroot it or use magisk root+magisk hide instead. I remember reading somewhere that you can run It deleting a file on /data, but not remember the steps, sorry.
[X 2014 Original Android Development] dego_:
Anyone tried April 21 build?
[X 2014 Original Android Development] xabr3:
Just dirty flased it.. no issues so far :) it is 7.1.2
[X 2014 Original Android Development] Gus Ghanem:
April 21, 2017: I was on stock, so I did a clean flash, I used Delta Gapps to install/replace only the apps I want (which is a bit of a hassle with Open Gapps). First setup went perfectly (no Setup Wizard crash). I disabled AudioFX since I don't use it (it's still there). I didn't install Google App (to reduce battery drain), nor any Google PAY apps. All good so far, no issues...

(Pixel Launcher in the pix)
[X 2014 Original Android Development] G4 Man2:
Just did a clean flash of the 21st build. Root access seems to be borked. Even after flashing the root zip the only options I'm given in the developer settings are "adb only" and "disabled".
[X 2014 Original Android Development] lichengqi:
Root is going to gone after flashing an update?