Database Develop

[Q] [WANTED]: Dev Assistance with Captivate Sleep-lock/Charge-lock

I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)

chipsharpdotcom said:
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)

BWolf56 said:
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
Click to expand...
Click to collapse
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)

chipsharpdotcom said:
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.

BWolf56 said:
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
Click to expand...
Click to collapse
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.

chipsharpdotcom said:
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
Click to expand...
Click to collapse
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe

billyjed said:
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for the tip...I'll try that if all of the above doesn't work. At this point, I'm all flashed up and running test cases.

So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.

chipsharpdotcom said:
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
Click to expand...
Click to collapse
Have you tried it with a different clock app? I mean, if I understand this correctly, it seems to be narrowed down to your current clock apk, which is different than the stock GB one. So I would suggest freezing (or unistalling) your current one with Tibu and trying a different one.

That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.

chipsharpdotcom said:
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
Click to expand...
Click to collapse
Haha first time I ever get that question but leaving your camera on should do the job (or video playing)

[ROM][5.1.1] Unofficial CyanogenMod 12.1 for HTC Incredible S [04/02/2016]

CyanogenMod 12.1 for HTC Incredible S​
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About CyanogenMod
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Not Working / Bugs
Rotation of capacitive soft keys (intentional)
Graphical distortion in photos taken using the front camera
How to Install
Download the ROM from below
Download GApps (I recommend Pico, because it will keep your phone running fast)
Download and install this recovery
Attach the phone to your computer
Copy the ROM to your phone
Copy the GApps to your phone
Boot into recovery
If this is your first time installing this ROM then factory reset the phone from recovery
If you want to upgrade the ROM, flash the new version on top, and only wipe cache and dalvik cache
Go to Install and select the ROM zip file
After ROM has finished installing, flash the GApps
Go to Reboot -> System
First boot will take long time, depending on the GApps you have flashed
After the phone is booted, it might be hot, because it was booting for a long time (~5 mins for Pico GApps)
If the phone is hot, then Power Off and let it rest for a while. Then turn it on and set up the phone.
Download
CM12.1 Version 2.0 - 04/02/2016
Google Apps (Pico package recommend for optimal performance)
XDA:DevDB Information
CyanogenMod 12.1 for HTC Incredible S, ROM for the HTC Incredible S
Contributors
rqmok
Source Code: https://github.com/rqmok/android_device_htc_vivo/tree/cm-12.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: HBOOT 2.0, TWRP 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-01-22
Created 2016-01-22
Last Updated 2016-02-04

Changelog
04/02/2016
- Revert to original data layout
- Fix Audio in calls
- Upgrade SMD to PKG4
- Switch to OpenDesireProject device source (adapted from saga - Thanks ODP)
- Enable Cypress TMA touchscreen driver (I don't know if anyone has this)
- Set Intelliactive as Default CPU Governor
- Clean up sensors and lights code
- Remove useless audio code in kernel
- Fix GPS
21/01/2016
- CyanogenMod 12.1 for HTC Incredible S

Reserved

thanks bro

Congrats bro! I can help you in fixing the capacitive button's rotation, if you need.

szezso said:
Congrats bro! I can help you in fixing the capacitive button's rotation, if you need.
Click to expand...
Click to collapse
I know how to fix that. I just didn't on purpose because I have to change frameworks repo, which means I have to fork it, which means I have to keep periodically merge updates in repo from CyanogenMod.
In short, I am just too lazy

rqmok said:
I know how to fix that. I just didn't on purpose because I have to change frameworks repo, which means I have to fork it, which means I have to keep periodically merge updates in repo from CyanogenMod.
In short, I am just too lazy
Click to expand...
Click to collapse
Will install this evening and report back, thanks...
Actually don't care too much about the capacitive button rotation...
The Automatic Brightness however really makes a difference in useability... Any idea how to enable that?

Infernoken said:
Will install this evening and report back, thanks...
Actually don't care too much about the capacitive button rotation...
The Automatic Brightness however really makes a difference in useability... Any idea how to enable that?
Click to expand...
Click to collapse
I think the light sensor is not functioning properly. I will check again.
But, is it possbile for you to check this as well?

I just installed the ROM (along with TWRP), and everything is running great!
Thank you @rqmok for making the Inc S live once more (I honestly thought dev was dead for good)
Here's my general thoughts after using for around 3 hours
Pros (compared to @szezso's ROM):
- Video recording fixed
- Feels like there's more RAM? Could be just me, but apps are staying in bg for longer
- Some things are definitely faster, like opening Play Store
Cons :
- I can't change what the capacitive buttons (hamburger menu or search) do. Probably has to do with what you said about not forking CM's repo.
- Google camera still crashes when you try to go into its settings. I have no idea why, it's kind of Google's fault, and this happened on szezso's ROM too, so no big worries. Google camera's photo quality is quite horrible anyway. I sure miss HTC noise reduction and image stabilization though...
- Nothing else at the moment? I'll let you know what I think after a few more days (battery life, performance after all apps are installed, etc).
Again, thanks so much @rqmok!
---------- Post added at 06:01 PM ---------- Previous post was at 05:08 PM ----------
Ok the phone appears to be completely silent (used to have sound too...not sure why)
And upon restart, I get a dialog saying com.android.phone has crashed, then the phone hangs and the only way to turn it off is by removing the battery
The sound reappears after I rebooted again, but calls are still silent
Also, I'm unable to make calls

davidchuyaya said:
I just installed the ROM (along with TWRP), and everything is running great!
Thank you @rqmok for making the Inc S live once more (I honestly thought dev was dead for good)
Here's my general thoughts after using for around 3 hours
Pros (compared to @szezso's ROM):
- Video recording fixed
- Feels like there's more RAM? Could be just me, but apps are staying in bg for longer
- Some things are definitely faster, like opening Play Store
Cons :
- I can't change what the capacitive buttons (hamburger menu or search) do. Probably has to do with what you said about not forking CM's repo.
- Google camera still crashes when you try to go into its settings. I have no idea why, it's kind of Google's fault, and this happened on szezso's ROM too, so no big worries. Google camera's photo quality is quite horrible anyway. I sure miss HTC noise reduction and image stabilization though...
- Nothing else at the moment? I'll let you know what I think after a few more days (battery life, performance after all apps are installed, etc).
Again, thanks so much @rqmok!
---------- Post added at 06:01 PM ---------- Previous post was at 05:08 PM ----------
Ok the phone appears to be completely silent (used to have sound too...not sure why)
And upon restart, I get a dialog saying com.android.phone has crashed, then the phone hangs and the only way to turn it off is by removing the battery
The sound reappears after I rebooted again, but calls are still silent
Also, I'm unable to make calls
Click to expand...
Click to collapse
Unable to make any calls? So, when you make a call, what does the ROM say?
Also, relating to the sound going silent, did you install any apps of any sort that you think would do this? Or did you change any settings?
EDIT: Hello. I have been running the ROM for an entire week, and I didn't have any problems like this. I still have audio working. I can also make and receive calls, but there is no in-call audio. I will try to fix this as soon as possible.

rqmok said:
Unable to make any calls? So, when you make a call, what does the ROM say?
Also, relating to the sound going silent, did you install any apps of any sort that you think would do this? Or did you change any settings?
EDIT: Hello. I have been running the ROM for an entire week, and I didn't have any problems like this. I still have audio working. I can also make and receive calls, but there is no in-call audio. I will try to fix this as soon as possible.
Click to expand...
Click to collapse
The ROM doesn't say anything.
The phone says "calling" the way it would usually, but there's no sound.
Then the phone acts as if the other person has picked up and starts counting time.
Two things I've noticed:
1. The other person DOES NOT receive the incoming call. I know because I held the other phone in my hands, and it did not ring. HOWEVER, when the other phone calls, mine does ring, I just hear no sound after answering
2. No money is subtracted from my prepaid account. That means no time was actually spent on network? I'm not sure.
I don't believe any apps would've done this (all the apps I've installed are the apps I've installed on szezso's ROM), and my volume profile is normal. If you need a logcat just tell me. By the way, have you tried calling anyone else on your Inc S? Does it work for you? If it does, I'll do a clean reinstall and see what happens. Right now, my phone is incapable of making ANY sounds at all.

davidchuyaya said:
The ROM doesn't say anything.
The phone says "calling" the way it would usually, but there's no sound.
Then the phone acts as if the other person has picked up and starts counting time.
Two things I've noticed:
1. The other person DOES NOT receive the incoming call. I know because I held the other phone in my hands, and it did not ring. HOWEVER, when the other phone calls, mine does ring, I just hear no sound after answering
2. No money is subtracted from my prepaid account. That means no time was actually spent on network? I'm not sure.
I don't believe any apps would've done this (all the apps I've installed are the apps I've installed on szezso's ROM), and my volume profile is normal. If you need a logcat just tell me. By the way, have you tried calling anyone else on your Inc S? Does it work for you? If it does, I'll do a clean reinstall and see what happens. Right now, my phone is incapable of making ANY sounds at all.
Click to expand...
Click to collapse
Yes, I have tried calling my brother's number with both phones in my hands. I have called both ways, and the call connects, but there is no audio in the call.
If you can provide a logcat that would be nice.

Here you go. Some things may be in Chinese (because that's what I set the language as), so tell me if you need translations.
By the way, do you think you're going to get a fix on this soon? Because my Inc S is still my daily, so I'll need to use it the latest by Monday

davidchuyaya said:
Here you go. Some things may be in Chinese (because that's what I set the language as), so tell me if you need translations.
By the way, do you think you're going to get a fix on this soon? Because my Inc S is still my daily, so I'll need to use it the latest by Monday
Click to expand...
Click to collapse
I'm sorry, I don't think I can get a fix for this by Monday.
If you want to revert back to some other ROM, then flash szezso's recovery and wipe/format everything (including internal storage), then you can install the older ROM.
I'm really sorry this had to happen. I will try to get a fix for this in the next week.
Until then, everyone who needs the call feature should not install this ROM.
EDIT: By the way, have you tried calling someone else as well?
EDIT: Which phone carrier are you with? And which phone carrier was the phone which didn't receive the call?

rqmok said:
I'm sorry, I don't think I can get a fix for this by Monday.
If you want to revert back to some other ROM, then flash szezso's recovery and wipe/format everything (including internal storage), then you can install the older ROM.
I'm really sorry this had to happen. I will try to get a fix for this in the next week.
Until then, everyone who needs the call feature should not install this ROM.
EDIT: By the way, have you tried calling someone else as well?
EDIT: Which phone carrier are you with? And which phone carrier was the phone which didn't receive the call?
Click to expand...
Click to collapse
It's totally fine man. Always here to support dev
I have not tried calling anyone else
My phone network is H2O Wireless (which uses AT&T's network), and I called someone with Verizon Wireless
I already backed up the ROM so reverting will be quicker if necessary
although backing up szezso's ROM is impossible (due to mounting /data or something) so that's slightly annoying

Hello.
I am currently trying to fix the audio bug during calls. I just saw that I was missing some important audio files. The files were there, but they weren't being included in the package. So, I have included those and need someone to test. I will be making some other small changes in the kernel as well. So, if someone wants to volunteer for the testing, then please pm me. I will switch the ROM back to the original data layout just for testing, so it will be easier to install. Why am I asking for a tester? The SIM I was using is not available to me any more, so I cannot test.
Also, @davidchuyaya I think your problem is only specific to you, since I was able to make calls. But, let's just see what the tester has to say first.
EDIT: I have gotten two testers. That will be enough. Thanks guys.

Any news?

Maybe you change ROM flash metod back? Before new layout? We can test it all. Or find same new bags.

Hello guys. This is an update.
It seems the performance of the ROM is laggy, so I am also trying to fix that.
I have fixed the RIL, so that should be working now. But I am still waiting for someone to test it.
Also, I am going to switch the ROM back to the normal data layout, because it seems people were having problems with the new layout.
I will try to release the new version in the next week or so.

rqmok said:
Hello guys. This is an update.
It seems the performance of the ROM is laggy, so I am also trying to fix that.
I have fixed the RIL, so that should be working now. But I am still waiting for someone to test it.
Also, I am going to switch the ROM back to the normal data layout, because it seems people were having problems with the new layout.
I will try to release the new version in the next week or so.
Click to expand...
Click to collapse
Whell. When it comes in old layout i will test it. Cant install new TWRP. Win10x64 maybe. Not mater.
Upd. Having dealt with TWRP. I had to using PG32IMG and do it five times, but then it saw the SD card. I try out a new firmware. Very nice! It looks and wark very promising. Just like all the sound does not work when calling. No dial tone. But it turns calls other phones is true as there is no sound. Later gladly try new firmware version. Sory for translate by google translater.

[ROM][7.x][T710][UNOFFICIAL] LineageOS 14.1 for Tab S2 8.0 2015

{
"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"
}
This ROM is BETA and not ready for daily use at the moment​
As of 8-7-2017 permanently marked as BETA.
The project started out as Experimental, as I had no device. Thanks to @Sarum4n it was temporarely BETA since 27-1-2017 as he loaned me his T710. Thanks to donations a used T710 came into budget and is available to test code.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
@Sarum4n
I used @CTXz his T710 work and @RaymanFX's T815 image to base this lineage 14.1 build on.
Special thanks to @Sarum4n, as he loaned me the T710 to test the builds and debug the boot issue we had.
Before you start
THIS ROM IS ONLY FOR THE SM-T710
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : BETA/EXPERIMENTAL
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
SDCard working again (broke after switch N blobs)
What is not working
Important
Fingerprint scanner not working
Camera (worked on gts28ltexx, died there as well, need to figure this one out)
Adaptive brightness not working (after N blobs?)
Bluetooth not working (broke with switch to N blobs, works on images before 23-04)
Minor
mic not working?
Instructions
How to install Lineage 14.1
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy Lineage 14.1
How to recover from issues
Looks like the reset to recovery (<HOME><VOL-UP><POWER>) is still broken on some or all T710/5 & 810/5 devices with this build.
Press and hold <HOME><VOL-DOWN><POWER> to enter 'download' screen.
Select cancel <VOL-DOWN>
Immediately press and hold <HOME><VOL-UP><POWER> to enter TWRP
Restore back-up made during installation phase
How to ROOT
Install the correct root package from here. (after flash of the image)
In LineageOS 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of LineageOS's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
17-07-2018 - Recompile with latest security patches. (5 jun patchset)
**********
16-12-2017 - Recompile with latest security patches. (5 dec patchset)
**********
19-11-2017 - Recompile with latest security patches. (6 nov patchset)
**********
17-10-2017 - Recompile with krack patches.
**********
6-10-2017 - Recompile with latest security patches. (5 okt patchset)
**********
12-08-2017 - Recompile with latest security patches. (5 aug patchset)
**********
16-07-2017 - Recompile with latest patches, BT seems to work. (needs more testing)
**********
07-07-2017 - Recompile with security level july 5th.
**********
04-07-2017 - Recompile with latest patches.
**********
20-06-2017 - Recompile with latest gts2-common patches.
**********
16-06-2017 - Recompile with june security patches.
**********
28-05-2017 - Adaptive brightness seems to work.
**********
14-05-2017 - Build SDCard fix, SD card works again. (BT still broken)
**********
28-04-2017 - Build with Nougat T815 (common) and T810 (device specific) blobs.
- Broke external SDCard, BT
**********
16/04/2017 - Patched mixer paths.
- Vibrate patch added.
**********
03/04/2017 - Patch to fix netflix (not tested, don't have netflix).
**********
12/03/2017 - Rebuild with patch level of March 5th.
**********
24/02/2017 - Removed rild as changes in that code killed the build.
**********
02/02/2017 - First build from LineageOS Github.
**********
Downloads
Latest LineageOS 14.1 build : https://www.androidfilehost.com/?fid=5862345805528050495
All LineageOS 14.1 BETA releases can be found here : https://www.androidfilehost.com/?w=files&flid=141202
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All our sources can be found here : https://github.com/LineageOS/android_device_samsung_gts28wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
LineageOS 14.1 for Samsung Galaxy Tab S2 8.0 T710, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/LineageOS/android_device_samsung_gts28wifi
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: BETA
Created 2017-02-05
Last Updated 2017-02-05
XDA:DevDB Information
LineageOS 14.1 for Tab S2 8.0 2015, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, RaymanFX, CTXz
Source Code: https://github.com/LineageOS/android_device_samsung_gts28wifi
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: LineageOS
Version Information
Status: Beta
Created 2017-02-05
Last Updated 2018-07-17

Thanks, updated to 02 build. Bluetooth still does not work right. Pairing is slow and input is greatly delayed on keyboards/mice. Using one of those cheap mini keyboard/mouse remotes, but it used to work fine on samsung fw or other devices. What app can I use to capture a segment of the logs? I will try to test on some other Bluetooth device types in a bit, have to borrow some.
WiFi still has ccode set to GB in /etc/WiFi/nvram_net.txt, needs to be set to ALL or US to allow higher freq 5ghz channels.
I remember lower bounds of brightness being lower on Samsung fw, but that may have been with the auto brightness mode enabled, and then brightness sent to lowest. I assume light sensor is part of camera module, which still needs work.

Ok so yesterday, I took the bait and installed this room and so far I am impressed and really happy about it. the basics are fully functional and my tab S2 has found its breath again. Thank you for the work
One note though, the battery seems to drain excessively fast

Please try to make this official so we can have regular updates including the monthly service security updates. Thx!!!!

CarpeNoctem said:
Ok so yesterday, I took the bait and installed this room and so far I am impressed and really happy about it. the basics are fully functional and my tab S2 has found its breath again. Thank you for the work
One note though, the battery seems to drain excessively fast
Click to expand...
Click to collapse
Disable WiFi during sleep? It is on by default.
Also there is no adaptive brightness yet, so set it lower manually.

Left the tablet charging overnight. Screen was off. Picked it up and the whole thing was crazy hot. Did not have anythijg running in the background.

Friagram said:
Left the tablet charging overnight. Screen was off. Picked it up and the whole thing was crazy hot. Did not have anythijg running in the background.
Click to expand...
Click to collapse
Sorry to say that for tablet may be faulty

nostupidthing said:
Sorry to say that for tablet may be faulty
Click to expand...
Click to collapse
It has never done that on Samsung marshmallow. Early lollipop has this heat issue which Samsung patched. Went back to stock rom, and no issues.
Beware of this issue, seems to be caused by lineage

Today is 3rd day on lineage and no problem with charging or heating over night.
Sent from my LG-H850 using Tapatalk

damir_balto said:
Today is 3rd day on lineage and no problem with charging or heating over night.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
Been using it since the first build with screen fix, 1/30 or earlier.
Tablet was fully charged for 6 hours, screen was set to off, was really hot when I picked it up in the morning, like it has been using 100% cpu.
Tablet gets pretty hot with cpu maxed for long periods, over 90c on any rom.
On stock rom there is a bug with chrome that causes this during use, as it does not use full gpu acceleration to render pages unless u alter flags.

Friagram said:
Been using it since the first build with screen fix, 1/30 or earlier.
Tablet was fully charged for 6 hours, screen was set to off, was really hot when I picked it up in the morning, like it has been using 100% cpu.
Tablet gets pretty hot with cpu maxed for long periods, over 90c on any rom.
On stock romantic there is a bug with chrome that causes this during use, as it doespecially not use full gpu acceleration to render pages unless u alter flags.
Click to expand...
Click to collapse
Me and others have no such problems so. You may try reverting back to stock. Keep complaining won't help.

damir_balto said:
Today is 3rd day on lineage and no problem with charging or heating over night.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
nostupidthing said:
Me and others have no such problems so. You may try reverting back to stock. Keep complaining won't help.
Click to expand...
Click to collapse
Reporting problems is not "complaining." The build is experimental/beta and has many issues. IMO this is a very important issue. Sustained heat can cause hardware damage. Much heat is dissipated through the glass screen and aluminum case border. If your tablet is in a case or bag supposedly sleeping, and this happens... you could see problems like warped case/melted adhesive around the screen. Possible that chippsets could burn out as well if heat is not dissapated.
I suspect it has done this 3 times in a week on lineage, it does not do it on stock rom. 2 of the times I woke to find the battery dead, so it drained in a few hours while sleeping. Other users have commented on battery drain iirc, and high cpu usage would be the cause. When on lineage and charging while powered down, there is no issue. The heat originates from the cpu location on the tablet. Likely it is due to a hung process that keeps restarting. I have had some system services that notify they have stopped responding on occasion while using lineage.
I suggest people running the rom keep a temp log and process time log.

Friagram said:
Reporting problems is not "complaining." The build is experimental/beta and has many issues. IMO this is a very important issue. Sustained heat can cause hardware damage. Much heat is dissipated through the glass screen and aluminum case border. If your tablet is in a case or bag supposedly sleeping, and this happens... you could see problems like warped case/melted adhesive around the screen. Possible that chippsets could burn out as well if heat is not dissapated.
I suspect it has done this 3 times in a week on lineage, it does not do it on stock rom. 2 of the times I woke to find the battery dead, so it drained in a few hours while sleeping. Other users have commented on battery drain iirc, and high cpu usage would be the cause. When on lineage and charging while powered down, there is no issue. The heat originates from the cpu location on the tablet. Likely it is due to a hung process that keeps restarting. I have had some system services that notify they have stopped responding on occasion while using lineage.
I suggest people running the rom keep a temp log and process time log.
Click to expand...
Click to collapse
your concerns well noted, notwithstanding it's still only you "reporting" this issue, as people are vocal with problems than those without, it's not likely that others are having the same problem.
since the dev has no such device and you're the only one having this problem, please try to contribute by providing more info e.g. logcat, process monitor...
otherwise there is not much @T_I and others may do to help you

noooooooooooooooooooooooo said:
your concerns well noted, notwithstanding it's still only you "reporting" this issue, as people are vocal with problems than those without, it's not likely that others are having the same problem.
since the dev has no such device and you're the only one having this problem, please try to contribute by providing more info e.g. logcat, process monitor...
otherwise there is not much @T_I and others may do to help you
Click to expand...
Click to collapse
I have been communicating with the dev on this thread and the last. I asked what tool I should use to report back the logs in the other thread, but did not get any constructive responses. Unfortunately "the tons of other people" who have installed this rom either fail to report back issues which have been stated by some others (bluetooth, wifi region, battery drain, etc), or don't even bother to create a forums account to reply. Instead, I'm met with s**tposters that spam rubbish to elevate post count such as "please support the 710" and "please add this or that feature," rather than looking into reported problems or actually offering anything constructive.

@Friagram With stock firmware my tablet gets also hot while charging it. I have no difference here with lineageos.
However, I have a little problem: my tablet hangs and does not react anymore on touch events. The buttons still work. Is there a way to reset the tablet with lineageos? A simple restart would be wonderful!
Otherwise, thank you a lot for this image. It feels really faster than with stock firmware.
Kind regards
Aurel

Still having bluetooth issue described in old thread.
@T_I logcat attached, near the end, from Bluetooth enable, pair attempt (headphones sb735, no pin needed) - fails to pair with any devices.
0202 latest rom

short battery life
Its great to have something new for this tablet, great work.
I'm also experiencing problems with power usage on lineage-14.1-20170202-UNOFFICIAL-gts28wifi with wifi turned off and tablet just left alone over night i get only around 12 hours from fully charged to ~5%
with cm12.1 I could use it moderately for days between charges (wifi auto turned off when screen off)
as a nice bonus my cheap "origami" type case now wakes and sleeps which it didn't do before with cm only stock. I don't think this is related to battery life though as i can lift a corner to peak under and the screen is off with the case flap down

sealne said:
Its great to have something new for this tablet, great work.
I'm also experiencing problems with power usage on lineage-14.1-20170202-UNOFFICIAL-gts28wifi with wifi turned off and tablet just left alone over night i get only around 12 hours from fully charged to ~5%
with cm12.1 I could use it moderately for days between charges (wifi auto turned off when screen off)
as a nice bonus my cheap "origami" type case now wakes and sleeps which it didn't do before with cm only stock. I don't think this is related to battery life though as i can lift a corner to peak under and the screen is off with the case flap down
Click to expand...
Click to collapse
Without any app installed?
Which gapp package you use?

nostupidthing said:
Without any app installed?
Which gapp package you use?
Click to expand...
Click to collapse
assuming you mean the case behavior, no extra app and i don't use gapps

sealne said:
assuming you mean the case behavior, no extra app and i don't use gapps
Click to expand...
Click to collapse
Logcat?

NEWBIE: What is the most stable build right now?

Greetings all, I installed CyanogenMod version 11-20141112_SNAPSHOT-M12-ovation way back. It has always been unstable and frustrating so I just walked away from the project.
Now it is 2018 and I'd like to take another crack at it. Last time I followed a guide I found online but this time I'm trying to put a bit more forethought into it and want to start from the ground up.
So first things first, what is the most stable, responsive build for the Nook HD+? I don't think I need the latest and greatest, I just want my Vudu to not crash, be able to start the dang thing up, and not have my battery drain randomly.
Thanks in advance!

amaces Lineage OS 14.1 lnos_ovation-ota-NJH47F.171021.zip - You must install pico gapps to get through initial setup easily. Apart from that, this rom is very solid. secretwolf98 is also posting builds, but I have not tested them yet.
Unlegacy-Android Nougat ua_ovation-7.1.2-20180111-0528.zip - Has a wifi bug where you lose settings after reboot. The easiest way to work around this is to connect to two wifi networks, and then disable and re-enable wifi two times. You will autoconnect to the first network automatically from then on.
amaces Marshmallow aosp_ovation-ota-MOB30Z.160820.zip - This is the most stable and mature rom in my opinion. The one major bug is that for wifi to connect on boot, you have to pull down the notification bar completely and press the wifi button to show available networks.
Edit: Forgot to mention that all these recent unlegacy-android based roms are much more stable than roms of the past. No more ANR loops, random rebooting, and the need to disable hardware overlays. Everything is generally working and stable.

amaces Lineage OS 14.1 lnos_ovation-ota-NJH47F.171021.zip looks to be the way to go, Thanks!

fddm said:
Everything is generally working and stable.
Click to expand...
Click to collapse
AFAIK HDMI output does not work in recent years (unlike with CM11). Or did it change?

fanoush said:
AFAIK HDMI output does not work in recent years (unlike with CM11). Or did it change?
Click to expand...
Click to collapse
Yes, afaik that is still true. I haven't got around to testing yet, but I think cm11 is still being built and is probably quite stable now days. I don't think I'd recommend buying that hardware as even the Nook's own screen is too high a resolution for it's own processor and graphics chip. I'm amazed it plays YouTube [email protected] as well as it does.

[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