[OFFICIAL] LineageOS 18.1 for the moto x 2014 - X 2014 Original Android Development

[OFFICIAL] LineageOS 18.1 for the moto x 2014 - X 2014 Original Android Development

{
"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

Related

[CLOSED][DEPRECATED] OmniROM 5.x

OmniROM
Lollipop - Android 5.x

A new "unified" Galaxy Tab 2 section was added to our forum because we don't make a difference between p31xx an p51xx specific roms.
Please use the Thread here for Omni 5 related questions and feedback

Reserved
Downloads:
Unofficial Builds by me
ROM Downloads for all supported devices can be found here
SuperSU http://download.chainfire.eu/supersu
GApps:
by @Deltadroid http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
or http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330

Can't wait to try this out. Loved omnirom ROM 4.4.4 on my tab until I tried your recent SlimLP ROM on it
Sent from my Nexus 5 using Tapatalk

New builds late this evening
Send from OnePlus One using Tapatalk

Android-Andi said:
New builds late this evening
Click to expand...
Click to collapse
Will definitely try this out - Omni 4.4.4 was perfect - I expect nothing less here (over time of course). Thanks Andi.

Builds are up
Send from OnePlus One using Tapatalk

FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...

cheeseous said:
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
Click to expand...
Click to collapse
Likewise with a P5113 here, booted first time after clean flash with pico Gapps and supersu 2.40... but after first reboot and 2 force reboots... still hanging on boot screen with a blank faced android blinking and wondering. Black to SlimLP for now. Thanks again Andi.

Lolli!
I installed the latest build and its working great in my P5110
I didn't even had any major bug yet (Only clock app not working)

Android-Andi said:
Builds are up
Click to expand...
Click to collapse
Reporting: Did an update from last years version.
Wiped C + DC
Flashed Rom + SuperSU
Rebooting .... took approx. 7 minutes ... done
Settings done,
Reboot,
Stuck at boot logo ... left for about 15 minutes
Wiped C + DC again,
Rebooted successfully this time.
Used for an hour or two, than reboot again, stucked at boot logo again...
After wiped C + DC again without no apparent reason: Booting successfully.
Restoring SlimLP with TWRP. Will test next build Andy when available.

@Gregzi thx for testing. I'll run new builds tonight...
Send from OnePlus One using Tapatalk

Testing Build 20150107
Testing latest build:
- Clean flash Rom + Gapps + Supersu 2.40
- Boot time reduced to 3 minutes
- Setting everything
- Noticed that SuperSU is this time correctly pushed into the system (in previous builds I had two:
one in Launcher and one in Settings ==> sometimes problems with root - TBackup)
- Shutting down the tablet
- Booting - again stuck at Omni boot animation (left it for about 10 minutes)
- Force reboot to TWRP (with two button combo)
- Reboot into the system from TWRP without cleaning anything
- Booting normally in 1 minute
When OC the frame rate is now 32,8 fps (Nenamark2), so better than previous builds, so certain progress is done.
The tablet feels smoother - especially noticeable when opening app drawer.
BR

installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad ?
Cheers and thanks alot, s.
sent over omni

sebastel23 said:
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad
Cheers and thanks alot, s.
sent over omni
Click to expand...
Click to collapse
Home button gets fixed by flashing Gapps!

DarKnighT916 said:
Home button gets fixed by flashing Gapps!
Click to expand...
Click to collapse
thanks, but actually i had flashed Gapps (pico) already just after the ROM.
however, i'll try again later. :fingers-crossed:
in the meantime, i re-flashed gapps, with no change in behaviour.
for the time being, i'm back to 4.4.4.

bt issues
cannot connect bt headset. other features working fine, any toughts

only a question
I have a p5110 and runs pretty well but I've a problem with the minimum brightness it's very dark I can't see anything. any solution?

I loaded the 1/29 build last night on a clean install (with the latest Nano PA Gapps and SuperSU install zip, all on Andi's latest TWRP build). So far so good, here's a few observations:
-The first boot took a pretty long time but from what I've read this is normal. I didn't reboot again until the next day but for the second boot, the bootanimation never loaded, it just went straight from the brand logo to the launcher, long black wait in between. After that, all fine. Later I loaded the stock lollipop bootanimation I had been using previously (I do like the omni one a lot, though), and it used to lag a bit at the end on 4.4.4 but now it runs smooth all the way through, so that's encouraging.
-Turning the screen off (or letting it time out) is usually buggy, the screen flickers on/off for a second instead of any type of animation (I believe Lollipop is supposed to do a monochrome fadeout?) Edit: On closer inspection I see it is doing the monochrome fade, but then the screen flashes at the end of the animation.
-Re-installing apps was painfully slow and seemed to hang if I let the screen turn off (I'd find it sitting on the same install several minutes later). Downloading seemed a lot slower than KitKat ever was, too. I looked at the stats in settings->apps->running at on point in the process and the Play Store was listed as Restarting, perhaps this indicates poor memory management? Running the app in the foreground didn't seem to help at all, though.
-The material updates to the stock browser app are pretty swanky, I'm a fan. (I saw that in the gerrit and got excited. Not done yet but looks great.)
-Cast screen doesn't seem functional, doesn't find my chromecast. I've tested both Netflix and Localcast to connect just fine, LocalCast was a bit finicky the first time I tried but I think that may have been a network issue.
-I was testing a video call in in Hangouts and tried to mute the sound (was testing with my phone in hand and there was audio feedback loops because of that), but couldn't. Using the volume buttons, it wouldn't go all the way down, and if I dragged the bar the rest of the way it just wouldn't stick. Not sure exactly which volume control that was (lollipop's sound settings still confuse me in general), but I think it must be a bug of some sort that it wouldn't go down to mute.
-I had only just got around to trying to use my tablet's IR blaster (P5113) for TV control a few days earlier, and I found that the top several smart remote apps in the store don't work at all. Peel actually forces a soft reboot when it gets to the "push this button to test turning the device on" step, consistently. I did get one app working, which only includes remote IR support as a secondary function, TV Guide by Mini Group. Unfortunately the app isn't quite polished enough to be useful to me, but it was notable that it just worked where the others all get nothing. I didn't re-test all of the apps on lollipop but the ones I did(both of the ones linked here and a couple of the others that didn't work) behaved the same way.
-Visual performance generally seems a bit laggy but overall performance is fine (i.e. animations may freeze or lag but the tasks they're covering up don't suffer). Maybe all the animations in lolipop are just a bit rough on older hardware? I find them a bit overdone now that I've played around with things a bit more, personally (not that this reflects on the ROM). I don't really like stuff like shadows bouncing around as I scroll menus, though some of them are a nice subtle touch.
Overall I was happy with KitKat, but I think I'll let lollipop grow on me, these quirks are all minor. Idle battery life seems a bit worse but it's hard to make that call, I've been fiddling with the tablet more than usual to test things anyway.
Edit: Actually after letting it sit overnight unplugged, the idle battery is better than I was ever getting on KitKat. Granted, I made a point of closing all apps before and I think on KitKat I was having issue with casting apps holding wakelocks overnight and that's yet to be tested, but 1% over 12 hours is a pretty damn good baseline. Not sure what caused that wifi drop towards the end, after holding the connection (it gets a good strong signal) for about 11 hours, though.

Hey together!
Seems like we have some faulty eMMC chips, some reports of broken devices appeared.
I pushed a commit to address the issue and prevent other devices from damage.
I will recompile latest Lollipop roms and recoveries within 1 week.
For more information please read http://forum.xda-developers.com/showthread.php?t=3016879
Follow the instructions please to check your eMMC information.
Best regards and wishes!
Andi
Send from OnePlus One using Tapatalk

Internet sharing (mobile hotspot) doesn't work

[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][Jem][CM13][6.0.x] Temasek's UNOFFICIAL Builds

Other new ROM!!!

NEW UPDATED BUILD (DEEP SLEEP FIXED)
https://www.androidfilehost.com/?fid=24591000424955347

Can anyone confirm if Youtube works properly? On the other ROM (http://forum.xda-developers.com/kindle-fire-hd/8-9-development/rom-beanstalk-t3436434/page2) it stops working if the device sleeps and requires a reboot.

sirp0p0 said:
Can anyone confirm if Youtube works properly? On the other ROM (http://forum.xda-developers.com/kindle-fire-hd/8-9-development/rom-beanstalk-t3436434/page2) it stops working if the device sleeps and requires a reboot.
Click to expand...
Click to collapse
This seems like a long standing issue since cm12 and possibly cm11 to a lesser extent. Your only hope is to start a logcat, reproduce the issue, and post the result. Still no guarantee of a resolution however. Otherwise best workaround would be to get a google cast receiver and use the tablet as a remote.
EDIT: Relevant log output. Only occurs after tablet enters deep sleep. Current workaround is to keep tablet plugged in and charging to prevent deep sleep after video playback.

r3t3ch said:
This seems like a long standing issue since cm12 and possibly cm11 to a lesser extent. Your only hope is to start a logcat, reproduce the issue, and post the result. Still no guarantee of a resolution however. Otherwise best workaround would be to get a google cast receiver and use the tablet as a remote.
EDIT: Relevant log output. Only occurs after tablet enters deep sleep. Current workaround is to keep tablet plugged in and charging to prevent deep sleep after video playback.
Click to expand...
Click to collapse
Ok thanks. I didn't have the problem on RessurectionRemix when I was using it but the Youtube app had to be closed occasionally as the videos started lagging. Too bad, but I know I'm asking a lot of an old tablet. I works amazing as a comic reader though.

YouTube Fix
sirp0p0 said:
Ok thanks. I didn't have the problem on RessurectionRemix when I was using it but the Youtube app had to be closed occasionally as the videos started lagging. Too bad, but I know I'm asking a lot of an old tablet. I works amazing as a comic reader though.
Click to expand...
Click to collapse
Can you flash this in recovery and try to reproduce the issue again? I can't get it to break again myself, though a few variables changed such as youtube app update and different video being played.
I suspect the newer kernel changes in RR are causing lag and crashes. Beanstalk and temasek are using an older kernel that's known to be more fast and stable.
EDIT: Newer firmware seems to break camera and cause a longer boot (sounds familiar). I don't recommend flashing it right now.
EDIT2: The reason why I thought newer firmware resolved this issue is because it technically did. Not because of fixes in ducati, but because the kernel failed to load the firmware entirely which subsequently broke the camera and caused a longer boot resulting in this kernel message. If loaded correctly, this message will result. So instead, as a fix for this youtube issue, it is best to disable hw decoding for avc entirely. You can flash this zip in recovery to get a quick fix which will also be in future builds.
More importantly, I think this explains why the camera is broken and longer boots occur in transi's newest roms. I haven't checked myself, but I'd bet that ducati-m3.bin is failing to load on boot. This is despite the proprietary firmware being unchanged. It might be something in his newer kernel changes is causing ducati not to fit within designated memory.
EDIT3: @transi1 This seems to be the offending commit for broken camera/long boot issue. This commit introduced some lag. And this commit resolves the youtube issue.

r3t3ch said:
Can you flash this in recovery and try to reproduce the issue again? I can't get it to break again myself, though a few variables changed such as youtube app update and different video being played.
I suspect the newer kernel changes in RR are causing lag and crashes. Beanstalk and temasek are using an older kernel that's known to be more fast and stable.
EDIT: Newer firmware seems to break camera and cause a longer boot (sounds familiar). I don't recommend flashing it right now.
EDIT2: The reason why I thought newer firmware resolved this issue is because it technically did. Not because of fixes in ducati, but because the kernel failed to load the firmware entirely which subsequently broke the camera and caused a longer boot resulting in this kernel message. If loaded correctly, this message will result. So instead, as a fix for this youtube issue, it is best to disable hw decoding for avc entirely. You can flash this zip in recovery to get a quick fix which will also be in future builds.
More importantly, I think this explains why the camera is broken and longer boots occur in transi's newest roms. I haven't checked myself, but I'd bet that ducati-m3.bin is failing to load on boot. This is despite the proprietary firmware being unchanged. It might be something in his newer kernel changes is causing ducati not to fit within designated memory.
Click to expand...
Click to collapse
Wow, thanks! I'll flash this as soon as I can.
EDIT: I'm using the BeanStalk ROM from another thread and flashing the Youtube Fix did seem to make difference. Waking up from sleep and resuming/playing new videos now seems to work. Cheers.

FINAL BUILD (Temasek retires)
https://www.androidfilehost.com/?fid=24591000424960127

SUPERSU INSTALLATION

So does this ROM support OTG by default? No powered USB hub or anything?
Edit: I noticed that you have another CM13 ROM thread, though the other is not from Temasek. However your source links go to the same place between this post and the other. The second post has a ROM that was built later though (2016-10-25), does the other ROM also have OnTheGo mode like this one is supposed to since its using the same source? The other thread is titled "[ROM][Jem][UNOFFICIAL][Marshmallow 6.0.x] CyanogenMod"

I love this ROM. It truly emulates the options and abilities ALL Android devices should have. If there was any one ROM that really brought out the true potential of this absolutely incredible tablet, it would be this ROM.
The only issue I have is the window animation in developer options. Setting it to 0 will cause random screen flashes and sometimes pixilation. It also caused a random reboot or two as well.
Aside from that, this ROM is probably the best one I've ever used.

bob__ said:
Edit: I noticed that you have another CM13 ROM thread, though the other is not from Temasek. However your source links go to the same place between this post and the other. The second post has a ROM that was built later though (2016-10-25), does the other ROM also have OnTheGo mode like this one is supposed to since its using the same source? The other thread is titled "[ROM][Jem][UNOFFICIAL][Marshmallow 6.0.x] CyanogenMod"
Click to expand...
Click to collapse
Did you ever end up flashing one (or both) of these 2 ROMs?

CornellEngineer said:
Did you ever end up flashing one (or both) of these 2 ROMs?
Click to expand...
Click to collapse
Yes, the other one is much better, this one has multiple useless features such as a USB OTG app, which does not work. The other one functions in almost every way better, and has less bulk as well.

bob__ said:
Yes, the other one is much better, this one has multiple useless features such as a USB OTG app, which does not work. The other one functions in almost every way better, and has less bulk as well.
Click to expand...
Click to collapse
Thanks. I know that DragonFire (the poster after you) is impressed with Temasek's ROM so I was just looking for a second opinion. I'll check out the other thread you mentioned. Gonna flash my first ROM in the next few days and was hoping to pick a decent one and be done with it.

CornellEngineer said:
Thanks. I know that DragonFire (the poster after you) is impressed with Temasek's ROM so I was just looking for a second opinion. I'll check out the other thread you mentioned. Gonna flash my first ROM in the next few days and was hoping to pick a decent one and be done with it.
Click to expand...
Click to collapse
No problem, as I said, they are basically the same thing this one just has bloat.

bob__ said:
No problem, as I said, they are basically the same thing this one just has bloat.
Click to expand...
Click to collapse
Bloat is easily removed

Deleted double post

bob__ said:
No problem, as I said, they are basically the same thing this one just has bloat.
Click to expand...
Click to collapse
Well, assuming you are still using the custom ROM we're talking about then you must be satisfied enough with its performance to keep on your tablet. I don't use my Nexus 7 2013 all that much even though it's a great device, but I have found that the USB OTG is a very nice feature to have, especially when I travel. But if it doesn't work in Temasek's version, then it doesn't work.
To be honest, I'm probably gonna hold off flashing a ROM for a while, in part because I am still not totally sure which one to try and in part because I am still squeamish about mucking up the flash. I have spent MANY hours over the last week or more pouring through umpteen threads and a ton of posts, but just when I get to the point that I think I have enough knowledge to attempt it I will come across a new thread with a bunch more posts (like the CM13 one you referenced last night) and find myself getting all confused again and it shatters any confidence I had to give it a go.
This forum is a treasure trove of great info posted by some very smart and helpful people and I think I've learned a lot in a relatively short time, but it can also be maddeningly frustrating the way it's laid out. Not sure why I am having such a hard time grasping and retaining some of the basic concepts, but it is what it is. It's not from a lack of effort on my part...maybe when it comes to these Android gizmos, I'm just a very slow learner...LOL.

CornellEngineer said:
Well, assuming you are still using the custom ROM we're talking about then you must be satisfied enough with its performance to keep on your tablet. I don't use my Nexus 7 2013 all that much even though it's a great device, but I have found that the USB OTG is a very nice feature to have, especially when I travel. But if it doesn't work in Temasek's version, then it doesn't work.
To be honest, I'm probably gonna hold off flashing a ROM for a while, in part because I am still not totally sure which one to try and in part because I am still squeamish about mucking up the flash. I have spent MANY hours over the last week or more pouring through umpteen threads and a ton of posts, but just when I get to the point that I think I have enough knowledge to attempt it I will come across a new thread with a bunch more posts (like the CM13 one you referenced last night) and find myself getting all confused again and it shatters any confidence I had to give it a go.
This forum is a treasure trove of great info posted by some very smart and helpful people and I think I've learned a lot in a relatively short time, but it can also be maddeningly frustrating the way it's laid out. Not sure why I am having such a hard time grasping and retaining some of the basic concepts, but it is what it is. It's not from a lack of effort on my part...maybe when it comes to these Android gizmos, I'm just a very slow learner...LOL.
Click to expand...
Click to collapse
OTG works, just the app that's in the ROM doesn't...at least not that I can see. The device is OTG capable as it is a hardware feature Amazon surprisingly never blocked. You don't need an app for it to function, but you do need an OTG adapter.

[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?

[ROM][12.L][UMI][White-Wolf-Kernel][OFFICIAL] Descendant

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page.
Sources
Github
Same as any ROM.
Do the necessary wipes, Format Data and flash the ROM.
No wipes are needed between updates from Descendant itself, unless specified.
Firmware is included in the zip no need to flash it
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct
Android OS version: 12.L
Security patch level: May

my worse download experience .... meh

Best rom for the Mi 10 I have come across. Really stable with all features working + Magisk. Heaps better than Miui. Only little 'bug' is that sometimes after the fingerprint reader the brightness randomly goes up or down.

Do faceunlock works?

yes works fine

Is anyone daily driving this ROM?
What are your thoughts on it?
I'm looking to switch from MIUI but every ROM for umi I tried so far was pretty disappointing.

I've been using it as a daily for a couple of days now and it works pretty well. It's definitely a bit more heavy on the battery than miui is, bit overall the experience has been nice. The bugs I've ran into are: automated brightness is a bit hit and a miss. I can't seem to switch the bottom buttons, which is annoying with my muscle memory. I had 1 or 2 apps that won't start, but I guess that's more of a dev issue than a rom issue. Lastly, I don't think quick charge is working, it really takes a lot longer to charge my phone. Overall, I'm a happy user, but I think I'll go back to miui once 13 is available for global.

thanks, I ended up switching to this ROM but after 2 days went back to xiaomi.eu.
Battery drain was quite high plus it charged pretty slow.

RW2882 said:
thanks, I ended up switching to this ROM but after 2 days went back to xiaomi.eu.
Battery drain was quite high plus it charged pretty slow.
Click to expand...
Click to collapse
Seems like every A12 rom has battery drain, this and evox version.

I flashed the rom via twrp recovery but im stuck on the boot, usually takes more or less 10-15 minutes depends of the rom but in this case i have more than 30 minutes on the logo image. Its normal? im come miui firmware 12.5.10
P.D: Ok i fixed, i flashed previuosly another rom and now it works. but when i would like to enter on recovery mode, come in a loop and never finish. This behaviour don't happen on evolution x rom
P.D: Fixed start loop when i want to enter to recovery. Just flashed another recovery with A12 support (https://xiaomi.eu/community/threads/twrp-for-android-12-mi-10-and-other-models.64186/)

Hello, I like this ROM very much. Do you plan to build this ROM on xiaomi10 pro(cmi) ?

Sphinix said:
I've been using it as a daily for a couple of days now and it works pretty well. It's definitely a bit more heavy on the battery than miui is, bit overall the experience has been nice. The bugs I've ran into are: automated brightness is a bit hit and a miss. I can't seem to switch the bottom buttons, which is annoying with my muscle memory. I had 1 or 2 apps that won't start, but I guess that's more of a dev issue than a rom issue. Lastly, I don't think quick charge is working, it really takes a lot longer to charge my phone. Overall, I'm a happy user, but I think I'll go back to miui once 13 is available for global.
Click to expand...
Click to collapse
so automated brightness is something no dev can do much about due to the kind of sensors we have in all new phones nowadays...
about the apps that are not opening please provide some logs about that.. (also try the new build its gona be up soon maybe it was just a random thing)
about the battery.. so if you just turn off aod and pocket mode the battery will become very good! its just that we have a wakelock issue with the proximity sensor thats preventing the phone from gowing into deepsleep and even into good idle so just try turning pocket mode off ( the switch for it will be available in the new build again coming soon)
about the charging.. i didnt see any issues personaly... i use the 30W stock xiaomi charger that came in the box and i always get 30+ watts according to FKM but the ui on the lockscreen doesnt always report the speed correctly but am working on fixing that but in general the phone charges very fast and even faster that miui for me so idk what the issue could be for you...
anyway am working on fixing everything at the end this is my daily driver and i only work on this rom and am gona switch to a new Device tree and kernel very soon and hopefully i get everything more stable than ever
if you or anyone got any qustions or any issue feel free to DM me on telegram @mountaser_halak

chiyulj said:
Hello, I like this ROM very much. Do you plan to build this ROM on xiaomi10 pro(cmi) ?
Click to expand...
Click to collapse
right now am focusing on getting umi stable then yah maybe i will build for cmi so just give me some time xD

download so slowly...
but tks for your work anyway！its an amazing rom

I flash the ROM (20220118 version) for a few days. It works well. I appreciate that it could freely control the network for most of the system and user's apps, therefore I need not use LSPosed or XEdposed to deal with it.
The battery drain is a little big. Variation of the automated brightness is unsatisfactory, and a few apps occasionally do not response.

This is simply the best ROM I tested with a ton of features but something in this rom prevents having full screen and battery is bad but I think this is the problem of all A12 Rom

my bad, wrong

reverting from this to xiaomi.eu google messages chat service stopped working and the phone kees getting recognized as google pixel 2 instead of Xiaomi Mi 10.. any fix for this?

@mountaser halak thanks for your work.
Could It be possible to implement chinese firmware in next builds?
It would enable double sim support.

LOLO-Sbd said:
@mountaser halak thanks for your work.
Could It be possible to implement chinese firmware in next builds?
It would enable double sim support.
Click to expand...
Click to collapse
I am using China firmware already

Database Develop

welcome