Database Develop

Cyanogenmod 7 stable

Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?
http://download.cyanogenmod.com/?type=stable&device=legend
AND
http://wiki.cyanogenmod.com/index.php?title=HTC_Legend
Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?

Because right now the ROM is stable but not complete that's why nightlies are still going on.

I propose an idea
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sz1a said:
Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?..
Click to expand...
Click to collapse
Yes it is, for the second time (first on 11.04 second from last night)
sz1a said:
...Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?
Click to expand...
Click to collapse
Because after first stable was out, there were still issues with GPS (in fact with the bearing during navigation). Later CM team has found a solution that was included in the nightlies, it was tested few days and most of us gave a positive feedback. Also some new things included (that "tablet" status bar was nice even if removed in #55). So, a new "stable" release was made to incorporate these.

50-3 said:
Because right now the ROM is stable but not complete that's why nightlies are still going on.
Click to expand...
Click to collapse
Nightlies are built every night and as long as the servers work they will be built every night.
Nightlies don't have anything to do with stable releases or feature completeness.

Ok, thanks. Surprised there isn't a thread dedicated to the stable release since more ppl would know about it then. I'll give 7.02 a go then, just flashed 7 stable last nite and pretty impressed so far (after new radio and the gps fix).

Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.

Rapier said:
Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.
Click to expand...
Click to collapse
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.

Check that your cpu speed isn't set too low when sleeping

bonesy said:
Check that your cpu speed isn't set too low when sleeping
Click to expand...
Click to collapse
CPU settings were not altered from the begining. I run at 787 with min set to 245, interactive. It is like this from the first nightly that had the CPU OC included. It's not happening allways and also didn't had such problems with nightlies or other stable versions. That's not a big deal anyways...

By the way.. no questions in Dev section..
Sent from somewhere outta space using my phone..

beastie-boy said:
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.
Click to expand...
Click to collapse
Having the loud speaker problem too, it's pretty annoying! Is it possible to revert back to 7.0.2 without wiping and just flashing?

sz1a said:
...Is it possible to revert back to 7.0.2 without wiping and just flashing?
Click to expand...
Click to collapse
Yes but won't solve the problem. This is present in all CM ROM's I've tried

Rapier said:
Yes but won't solve the problem. This is present in all CM ROM's I've tried
Click to expand...
Click to collapse
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..

And it seems it's somehow hardware dependent. I never had any "loudspeaker" problem with CM 7 stable or nightly.
regards

sz1a said:
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..
Click to expand...
Click to collapse
Yes, sorry, my mistake. I was talking only about CM7 ROMs, CM6 didn't had this

beastie-boy said:
After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off).
Click to expand...
Click to collapse
Holy crap I thought I was the only one who had this. CM6 worked perfectly, since the update CM6 -> CM7.0.3 the ringtone plays, I accept the call, and can hear the other person on the (handsfree) loudspeaker for about 1 sec until the sound is switched back to the internal speaker.

It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.

oysteivi said:
It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.
Click to expand...
Click to collapse
I dont get it and I have the ringtone on. Some hardware version dont have it and some do it seems.

I also have the problem with background data dropping when going into sleep mode after a while. When I wake my phone up the status bar icons are all white and I have to manually check gmail, etc. The phone establishes a connection with Google services again after a while and they go back to green but it is really annoying. Didn't notice this on 7.0.2. Apparently nexus s owners are having similar problems.

[KERNEL-DEV][WI-FI FIX][ARP Offloading][Push Notifications][19 June][UPDATED]

The issue???
With all current kernels I and many other have been receiving delays in receiving notifications, in both screen on and off from 15mins to 2hours. Google should have released at least a minor update to fix this issue but they haven't and it bothers me.
As the title states I've worked on fixing WiFi and notification issues, its hasn't gone under mass testing so that's why I've created this thread for it, i have personally tested my device goes into sleep/deep sleep and i can ping the device when its in deep sleep, push notifications also work instantaneously I've received them within seconds
This should be used with Stock Android or Close to Stock e.g. AOSPA, Running on ROMS like MIUI will not work (tested)
Recommendations:
.54 Radio located here:
Push Notification Fixer (PNF Found in Play Store):
Installation:
1. Download this fix: Flashable zip wifi fix
Download: http://db.tt/NuQq7kk3
2. Download .54 radio:
3. Install Push Notification Fixer from Playstore:
4. Reboot into recovery
5. Flash zips in this order, radio, wifi fix, wipe cache & dalvik cache
6. Reboot into OS
Test for you:
1.Does my Device sleep?, let it sit for 10 minutes (device usually deepsleeps within 5 mins, allow your device to sit for 10mins)
3. Can you ping the device while its in deepsleep?
4. Any wakelocks showing? Mainly is there a suspend wakelock?
Once this has been tested ill push out another update, thank you!
Current issues:
On some devices suspend wakelock (Should be fixed)
Very rare occasion, 3/4 packets successfully received (packet lost while pinging)
Heartbeat interval can possibly be improved (haven't checked yet)
Ping to device when in deepsleep can be upto 1200ms which is too long for my opinion should be
Source code: https://dl.dropboxusercontent.com/u/58024932/prima.zip (PRIMA DRIVER)

Creditz & FAQ
Note to everyone: sooner i get results from more people, the sooner I can release the fix/ work on it quicker
Thank you @faux123 for your kernel base
Thanks to motley for his kernel base (wheres the dude gone?)

reserved

Dalidah said:
Hello,
dropbox link broken ...
Click to expand...
Click to collapse
Dropbox link working now, removed the previous version as it had trouble with cpu freq, the cpu freq went to min n locked on minimum lagging the whole OS, Just fixed now

I dont see any code posted in here http://forum.xda-developers.com/showthread.php?t=2272140 ... so why pouncing on someone who wants to help ? give him some time and he will release when its done.

Shaky156 said:
Dropbox link working now, removed the previous version as it had trouble with cpu freq and screen stutterin, the cpu freq went to min n locked on minimum lagging the whole OS, Just fixed now
Click to expand...
Click to collapse
Correction think there may be an issue with fauxs enhacement on locking with cpu at lowest freq, but my screen was lagging mainly cause o set gpu at 128mhz lol

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested deep sleeps perfectly fine

Anyone flashed this? Feedback?

Shaky156 said:
Anyone flashed this? Feedback?
Click to expand...
Click to collapse
Phone not sleeping. Tested in 3 different APs.
I don't wan't to be rude but what exactly are the Technical stuff that you've changed here? Sure you can say wifi but what part? Firmware? Drivers? If you just said that people won't be bashing your thread.

sigma392 said:
Phone not sleeping. Tested in 3 different APs.
I don't wan't to be rude but what exactly are the Technical stuff that you've changed here? Sure you can say wifi but what part? Firmware? Drivers? If you just said that people won't be bashing your thread.
Click to expand...
Click to collapse
3 people reported deepsleep, 2 person reported no deepsleep.
Changes in kernel, which ive already stated in thremcins hsic wakelock thread
Source code releasing within next few days
Sleeping like a baby

Hi,
I just tried it and my phone is not sleeping at all either. Why is it so hard for you to release the source code? This is quite suspicious to be honest.
I mean you say you want to release it within the next few days - lulz, why not now? Will anything change until then? I guess not.
I repeat: This is _NOT_ meant rude and I don't want to start a flame war.

They say seeing is believing id like screenshots of no deepsleep, release within the next few dayz as i have 2-3 kernels for testing, if alot of people do not get deepsleep then ill output another kernel, the point is to fix n release code, i have 2-3 kernels 1 of them will work for sure for people that cannot achieve deepsleep

Also my name is on that kernel like 100 times so i need to go through it n clean off comments
Edit: test this on stock ROM or Paranoid ROM, highly recommended, god knows whats causing the wakelock
And always provide screenshots

sorry for the question...but what is the point of this kernel?
i don't have a lot of time to lurk all topics, if someone can explain me why faux kernel need a wifi fix and what version of kernel has this problem (i'm not up to dated)...i'd be very grateful.
thx

beren said:
sorry for the question...but what is the point of this kernel?
i don't have a lot of time to lurk all topics, if someone can explain me why faux kernel need a wifi fix and what version of kernel has this problem (i'm not up to dated)...i'd be very grateful.
thx
Click to expand...
Click to collapse
All kernels have an issue with wifi, basically i have always recieved notifications late with both screen on and off from 15-mins to 60-mins, what i have done is fix this issue, some people reporting no deepsleep, me + few others have reported device sleeping and notifications on time. I chose faux kernel as his has a defconfig, didnt continue to test with francos hos doesnt include a defconfig making the source code uncompilable, this thread is here to fix and test wifi cuz i got tired of recieving late notifications

Sent from my Nexus 4 using Tapatalk 4 Beta

buster041284 said:
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I seeee deeeeepsleeeeeep!!!

Shaky156 said:
I seeee deeeeepsleeeeeep!!!
Click to expand...
Click to collapse
yea its sleeping and iam getting notification right away i stand corrected

Ok, latest update, fresh CM install, standard WiFi network I use (which never causes suspend_backoff on a kernel with my other notification solution). I think the screenshots speak for themselves.
Side Note: When I added another SSID to my network and blocked all internal and external multicast/broadcast traffic I did get some deep sleep but that's not a solution to the problem since most people wouldn't have access to do this nor would they want to if they could. I can also get the device to deep sleep on 3G/4G.
I remain skeptical that this fix works.
Sent from my Nexus 4 using Tapatalk 4 Beta

thracemerin said:
Ok, latest update, fresh CM install, standard WiFi network I use (which never causes suspend_backoff on a kernel with my other notification solution). I think the screenshots speak for themselves.
Side Note: When I added another SSID to my network and blocked all internal and external multicast/broadcast traffic I did get some deep sleep but that's not a solution to the problem since most people wouldn't have access to do this nor would they want to if they could. I can also get the device to deep sleep on 3G/4G.
I remain skeptical that this fix works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i was skeptical but look at my screen shots i did not have no wake locks how can this be your the dev i have no idea

[Q&A] [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015

Q&A for [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Just flashed this without having any trouble during the process until I powered off afterwards - or, attempted to. It hung on the power off screen, so I had to hold down the power button in order to turn it off. After I booted up again, Google Play Store crashed. I managed to get it to work long enough to install a few other apps (Textra, Lookout, Themer, and Dashclock) by disabling the Play Store app and then opening it. Whenever I tried to open these apps, they crashed upon opening and the app icon changed to the Android bot icon instead of the app's normal icon and the package name instead of the app name. After the first downloaded app crashed, then I got an error that Google Play Store crashed, and its icon changed the same way. I then attempted a factory reset within the ROM, but it hung on the power off screen. I held the power button again, booted back up, and it looks like all the preinstalled apps work except Play Store. When I try to test SuperSU, it says that Play Store has stopped and does not load a list of apps. Now, Google Now is saying that I "need Google Play Services, which is not supported by your device." Any idea what went wrong?

Had a similar problem, my mistake was not to follow the procedure EXACTLY as stated. It turns out that I did not wiped everything except from what's in the sd card, did that and boom! A nice ROM to play with. Give it a try.

I might give it a try again, but I know for a fact that I performed the wipe correctly.

Please, do tell how it went.

Worked this time! Thanks for your help!

Works great but have quite poor battery life, refuses to go into deep sleep.
msm-hsic-host wakelock, horrible wakelock pins the cpu 384 mhz min.
bugs ive found-
using the cast screen button renders a blank screen to my chrome cast.

Yup, battery life is pretty crappy. But had a similar battery life with stock NE3 firmware. In a couple of weeks I'll be getting a new battery. Bought my phone from eBay and it came with a used one, I'm just guessing at the moment.

I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.

ChristopherXDA said:
I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.
Click to expand...
Click to collapse
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.

bestestever said:
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.
Click to expand...
Click to collapse
Yep, same here. Phone never enters deep sleep. After about 3 hours lost 10% of battery. 80% of the partial wakelocks were msm_hsic_host wakes.

I think the issue has to do with the wifi. Even though wifi is set to be off when the screen's off, betterbatterystats shows the wifi is on 100% of the time. This makes some sense since there appears to be an issue with the wifi driver where after a full reboot my wifi won't work until I do a hotboot. This happens for everyone else right?
I will try and look into the wifi fix that was part of the masterpatch and see if that provides any fixes.

Google edition pure nexus safestrap i537
tHANKS HOPE IT WORKS
---------- Post added at 08:06 AM ---------- Previous post was at 07:50 AM ----------
Unable to mount system original? that is the last message I get before last reboot. please help.

Littile things
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.

S4 Active Speaker Phone Fix
rockinwaggy said:
The issue with speakerphone, for me, is that the other end of the call doesn't hear anything when using speakerphone. Turn speakerphone off and it's back to normal.
Click to expand...
Click to collapse
ChristopherXDA said:
Is your speaker phone working on calls?
Click to expand...
Click to collapse
McJeg said:
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.
Click to expand...
Click to collapse
This is a known issue on the S4 Active as discussed here: http://forum.xda-developers.com/showthread.php?t=2412645
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.

Ha, oh man thats a little embarassing. You're right, that fix works on this Rom too.
I tried some of the other fixes though like for Wi-Fi in the masterpatch and that doesn't work on this rom.

k3u::straylight said:
This is a known issue on the S4 Active as discussed here: <url>
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.
Click to expand...
Click to collapse
Thank you so much, this issue was bothering me because I kept forgetting and putting people on speaker lol. Fix worked perfectly, I can confirm

Love this ROM, battery life is poop, but, can bear with it. Here is my antutu score.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I see little feedback for this ROM. What can I do to give give more accurate and useful info?

fuel426 said:
I see little feedback for this ROM. What can I do to give give more accurate and useful info?
Click to expand...
Click to collapse
The rom is generally problem free. Aside from the battery life, it's quite solid. Both of his nexus style roms have this msm_hsic_host wakelock problem (I've tested the GE S4 rom). He is aware of this issue. Unfortunately, he has had some personal things happen lately, so he's not available to work on the rom. Family comes first.
Also, I recently test DS Battery Saver from the Play Store. Even on its most aggressive battery saving mode, deep sleep was never entered. So, don't bother.

[OFFICIAL] LineageOS 18.1 for the moto x 2014

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
moto x 2014
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the the moto x 2014.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official Builds:
victara
Unofficial - built once a month by me, includes GApps and Pixel goodies:
victara
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Front camera cam be a little overexposed or blown out sometimes - can't figure it out.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8974

Thanks man!! working perfectly on my moto x 2014.

Update: we are now in the official build roster and queued to get an official 18.1 build on Sunday morning

Hi npjohnson!
I've follow all the steps for the upgrade, that happened without fails (the only unusual thing that i've noticed is that process finshed as OK on the device screen when progress was around 47% on pc cmd adb screen, for the rom and for the mindthegapps), but the device do not unlock when I enter my pin. The screen turns black for a moment and return to lock screen. Any idea of how to solve this?
Update: After restore the backup, I've remove screen lock pin and try again. Now the device is rebooting when try to load the first screen after the boot...

How is this even possible?

Moto X 2014 victara Upgrade to LineageOS 18.1 Fail & Workaround
douglasmarx said:
...I've follow all the steps for the upgrade, that happened without fails (the only unusual thing that i've noticed is that process finshed as OK on the device screen when progress was around 47% on pc cmd adb screen, for the rom and for the mindthegapps), but the device do not unlock when I enter my pin. The screen turns black for a moment and return to lock screen. Any idea of how to solve this?...
Click to expand...
Click to collapse
For the Motorola Moto X 2014 (victara) the LineageOS upgrade wiki page now says that you need to format data before installing LineageOS 18.1: https://wiki.lineageos.org/devices/victara/upgrade
In this LineageOS subreddit thread Can't go past locking screen after installing 18.1 on bacon (OnePlus 1) there is a post made by haggertk who is one of the 9 Lineage directors that explains why.
The workaround in that thread posted by OffizierMichael to avoid formatting the Data partition & losing your apps, data & settings was confirmed by a few OnePlus One users but not for the victara yet confirmed by victara user @douglasmarx:
Ok, I got this to work on my Oneplus One, setup before installation:
Lineage OS 17.1
TWRP 3.5.1
Deactivate your unlock protection (pattern, PIN etc.) so it unlocks by simply sliding up
Now, boot into TWRP and install (in same order and without rebooting inbetween)
Lineage OS 18.1
GApps (must be Android 11 of course, like https://nikgapps.com/ - I used Open GApps before but they don't have version 11 out yet)
Remove or rename the file /data/system/locksettings.db by using TWRPs explorer functionality
Reboot and unlock into Lineage 18.1 like normal and reactivate your unlock protection of choice
As mentioned by developers already, it is adviced to format every partition (therefore resetting and removing all settings/apps/files on your phone, be aware of course!) before going for the update.
Click to expand...
Click to collapse

curiousrom said:
Moto X 2014 victara Upgrade to LineageOS 18.1 Fail & Workaround
For the Motorola Moto X 2014 (victara) the LineageOS upgrade wiki page now says that you need to format data before installing LineageOS 18.1: https://wiki.lineageos.org/devices/victara/upgrade
In this LineageOS subreddit thread Can't go past locking screen after installing 18.1 on bacon (OnePlus 1) there is a post made by haggertk who is one of the 9 Lineage directors that explains why.
The workaround in that thread posted by OffizierMichael to avoid formatting the Data partition & losing your apps, data & settings was confirmed by a few OnePlus One users but not for the victara yet confirmed by victara user @douglasmarx:
Click to expand...
Click to collapse
Works for me too (the workaround)! Thank you very much, again!

Hello,
I'm very new here.
I've been able to install the update without any problem (formatted the phone before installing the update).
I would only like to tell that since the update, my phone is unable to connect to Netflix. It's stuck at "Netflix" with black background. I've already reinstalled the app, deleted cache and data multiple times. No luck.
Also, Chrome is now unusable (works for a couple of seconds then it freezes). I'm using Opera right now.
Last, maybe it's my internet, but the phone seems to lose the WiFi connexion more frequently since the update and often doesn't reconnect to our network even if it's within range (I have to either restart my router or reset my phone's network settings).
That said, thanks for all the devs for making my old Moto X still work and compatible with newer apps ^^

Stk14 said:
Hello,
I'm very new here.
I've been able to install the update without any problem (formatted the phone before installing the update).
I would only like to tell that since the update, my phone is unable to connect to Netflix. It's stuck at "Netflix" with black background. I've already reinstalled the app, deleted cache and data multiple times. No luck.
Also, Chrome is now unusable (works for a couple of seconds then it freezes). I'm using Opera right now.
Last, maybe it's my internet, but the phone seems to lose the WiFi connexion more frequently since the update and often doesn't reconnect to our network even if it's within range (I have to either restart my router or reset my phone's network settings).
That said, thanks for all the devs for making my old Moto X still work and compatible with newer apps ^^
Click to expand...
Click to collapse
1. Netflix should be fixed next build, update and let me know
2. Looking into it
3. Not sure, seems fine to me

Lovely work! Thank you for this.
I think both cameras are misbehaving a bit.
For example, lets say I open up the default LOS camera or Open Camera. If I'm pointing at something that's bright while the camera app is opening, then exposure will be correct on screen for that scene and the live preview is fast and snappy as you'd expect on good lighting conditions.
While having the camera app open, if I point it to something dark or black, exposure adjusts a few stops up to compensate, but then it won't readjust back when pointing back to what was bright. Camera preview gets laggy and stays laggy, as if shutter speed got too low.
Front camera tends to always get exposure wrong, too bright, blown out and laggy. I'd guess auto exposure is not working correctly, shutter speed being the problem. Closing and opening the camera app again fixes the issue until it happens again.
Camera behaved as expected on 17.1.
How can I collect and provide more information about this? A logcat? I'm on 18.1-20210418-NIGHTLY-victara, phone is a XT1097, latest Marshmallow firmware. 18.1 was clean installed, the usual factory reset wipes and /data formatted in TWRP.

Thanks a lot for this build!
My old Moto X is a new phone now!
I have some problems with the flash when taking pictures, the Photo App crashes...not very important for me though...
Other than that, everything seems to work smoothly!!

Can you guys do a logcat while using and post steps to reproduce? It will be really helpful for us. Thanks in advance

Sure, I will try to do it this weekend

Here are the logs:
I rebooted the phone, then I opened the camera and try to take a picture. This happened around 14:15:29.661
The flash was on by default. The timer (3 seconds) started but the picture was not taken. Then I tried few times more, but then the application get non responsive and crashed.
I hope it helps!
Kind regards

Hi
Thanks for the update, just performed a clean install, coming from LOS 17.1.
The echo during calls in Signal is still an issue, as previously reported in the 17.1 thread.
Camera works, indeed it sometimes starts completely overexposed but not always, so closing it starting it again seems to fix it. Strange. Video recording seems to work, it didn't work in 17.1.
Also, there is no AOSP email app. Could be a problem with Mindthegapps, I usually never install Gapps but this is not my phone
To me the major problem is the echo during VoIP calls. Using signal with video and or speaker is just not possible.
Thanks !

jeferson1979 said:
Can you guys do a logcat while using and post steps to reproduce? It will be really helpful for us. Thanks in advance
Click to expand...
Click to collapse
Here you go. This is on yesterday's build, 20210425
First opened OpenCamera while pointing at sunlight, confirmed fluid camera preview with correct exposure, then pointed to something black, reproduced behavior as per my previous post (laggy camera preview as if shutter speed got too low to get the correct exposure on something black, as expected), then pointed back to sunlight to confirm bad behavior (shutter speed stuck too low, camera preview laggy and completely white, too much light captured, not auto correcting back to initial status as you'd expect).
Closed OpenCamera, opened LOS' stock camera, did the same steps, reproduced same behavior, then closed it.
Let me know if you need anything else. Thank you!

ptitrusse said:
Hi
Thanks for the update, just performed a clean install, coming from LOS 17.1.
The echo during calls in Signal is still an issue, as previously reported in the 17.1 thread.
Camera works, indeed it sometimes starts completely overexposed but not always, so closing it starting it again seems to fix it. Strange. Video recording seems to work, it didn't work in 17.1.
Also, there is no AOSP email app. Could be a problem with Mindthegapps, I usually never install Gapps but this is not my phone
To me the major problem is the echo during VoIP calls. Using signal with video and or speaker is just not possible.
Thanks !
Click to expand...
Click to collapse
The echo: we're working on it, its quite tough.
The AOSP email app: It was dropped, old and insecure.

Well, i've installed this build (lineage-18.1-20210425-nightly-victara-signed.zip) and I have to say its incredible. I've installed Lineage on a number of devices (LG G Pad 8.3, Galaxy S5 Plus, LG G2) and none of the builds are as smooth and bug free as this one. I followed the install guide on the Lineage Wiki page and it went exactly as planned (though I did find some old youtube videos to help point in the right direction sometimes such as when going through the Motorola website unlock bootloader process)
I'd given up my old Moto X 2014 but this has breathed new life into it. Many thanks npjohnson!
The only minor thing I can't fix is that I had planned to give this to my 10 year old son and use Google Family Link, but it wont let me do this as it gets stuck in a loop - I think this may be an issue with mindthegapps. Either way, its not a big problem, just happy to have an all new Victara on the latest build
SInce putting this OS on I've also re-discovered what a lovely phone it is - great to hold in the hand (one hand unlike todays huge slabs) and the glass is so smooth. Its just a really nice phone.

sumomogg said:
Well, i've installed this build (lineage-18.1-20210425-nightly-victara-signed.zip) and I have to say its incredible. I've installed Lineage on a number of devices (LG G Pad 8.3, Galaxy S5 Plus, LG G2) and none of the builds are as smooth and bug free as this one. I followed the install guide on the Lineage Wiki page and it went exactly as planned (though I did find some old youtube videos to help point in the right direction sometimes such as when going through the Motorola website unlock bootloader process)
I'd given up my old Moto X 2014 but this has breathed new life into it. Many thanks npjohnson!
The only minor thing I can't fix is that I had planned to give this to my 10 year old son and use Google Family Link, but it wont let me do this as it gets stuck in a loop - I think this may be an issue with mindthegapps. Either way, its not a big problem, just happy to have an all new Victara on the latest build
SInce putting this OS on I've also re-discovered what a lovely phone it is - great to hold in the hand (one hand unlike todays huge slabs) and the glass is so smooth. Its just a really nice phone.
Click to expand...
Click to collapse
FamilyLink is Safety net related I think :/

npjohnson said:
FamilyLink is Safety net related I think :/
Click to expand...
Click to collapse
Sorry - I'm not sure what Safetynet is (even after Googling!) - does that mean Familylink wont work with Lineage?
Thanks

Question Battery Draining, MIUI 13 Update vanish, Task manager.

1. I use redmi note 10 pro. But for a few days my battery is getting drained like 14-20% when the phone is idle, during sleep at night.
I looked in the battery and performance section. There was nothing serious.
I think there's something running in the background which is hiding itself from the system.
In the router configuration page, I found my device sent heavy packages. I thought to do a factory reset but I was thinking if theres another way out.
So I was looking for a task manager which will show me the background running programs cause I can't find it in developer options.
I worry much and I really can't stop thinking that something is mining in my device.
2. And I got an update of miui 13 but I didn't download the update and I can't find it now. I restarted my device several times.
3. The last thing. In the first phase, the 64 MP shots used to take like 30-50 MB and now its like 5-12 MB. And normal shots were like 7-12 MB and now its 2-3. Its so disappointing and theres also details loss. Also I can't find 64 mp in gcam. And gcam .jpg size is totally fine.
Any way to fix them all without installing custom rom?

1. Happens the same to me since I bought it in May. Could not find any solution yet. Sometimes it loses a lot of charge while idle, sometimes it doesn't lose any at all. I tried everything from restricting background usage for all apps that don't have notifications, resetting to factory settings and even flashing MIUI again. Warranty didn't find any problem.
2. Happened to me too for some updates. Got the notification then it disappeared.
3. No idea.
It is so frustrating having this kind of a package only to screw it up with a bad software. Still regret buying this phone.

trojan0 said:
1. I use redmi note 10 pro. But for a few days my battery is getting drained like 14-20% when the phone is idle, during sleep at night.
I looked in the battery and performance section. There was nothing serious.
I think there's something running in the background which is hiding itself from the system.
In the router configuration page, I found my device sent heavy packages. I thought to do a factory reset but I was thinking if theres another way out.
So I was looking for a task manager which will show me the background running programs cause I can't find it in developer options.
I worry much and I really can't stop thinking that something is mining in my device.
2. And I got an update of miui 13 but I didn't download the update and I can't find it now. I restarted my device several times.
3. The last thing. In the first phase, the 64 MP shots used to take like 30-50 MB and now its like 5-12 MB. And normal shots were like 7-12 MB and now its 2-3. Its so disappointing and theres also details loss. Also I can't find 64 mp in gcam. And gcam .jpg size is totally fine.
Any way to fix them all without installing custom rom?
Click to expand...
Click to collapse
Raito Wolf said:
1. Happens the same to me since I bought it in May. Could not find any solution yet. Sometimes it loses a lot of charge while idle, sometimes it doesn't lose any at all. I tried everything from restricting background usage for all apps that don't have notifications, resetting to factory settings and even flashing MIUI again. Warranty didn't find any problem.
2. Happened to me too for some updates. Got the notification then it disappeared.
3. No idea.
It is so frustrating having this kind of a package only to screw it up with a bad software. Still regret buying this phone.
Click to expand...
Click to collapse
I would suggest to change the ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

1. Sorry to say, but the only way i solved it is with flashing a custom kernel. VantomKernel worked the best. From 20% battery drain overnight to 3%. YukiKernel works too, but has an error message every time you reboot the phone.