Database Develop

[Q&A] CM-12.0 (LP) UNOFFICIAL nightly builds

Q&A for CM-12.0 (LP) UNOFFICIAL nightly builds
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CM-12.0 (LP) UNOFFICIAL nightly builds. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Is this a unified build for all carriers?

network issues with xt1093 uscc
great rom! everything seems to work smoothly. the only issue i have had is trying to connect to my network. Do i need to configure the APN to my carrier or is there something i am missing? i installed correctly using TWRP, factory reset, flash zip, cleared dalvik, reboot,....

I'm assuming we'll lose the moto things like active display and the phone talking when at home and on the road?

network issues with xt1093 uscc
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.

NOOBSABOT said:
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.
Click to expand...
Click to collapse
I think that the radio is broken on the last couple of nightlies across many different devices. Try an older version and see if you have better luck.

i'm on stock 5.0 rooted xt1092
doing nandroid and flashing last build this evening.

flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?

michyall said:
flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?
Click to expand...
Click to collapse
Did you enable it in developers options?

matt99017d said:
Did you enable it in developers options?
Click to expand...
Click to collapse
Yes sir. I've solved fastbooting again CF. Maybe after format you loose root permissions.

No Network
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.

CrepuscularSoul said:
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.
Click to expand...
Click to collapse
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).

crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
---------- Post added at 01:31 PM ---------- Previous post was at 12:38 PM ----------
CrepuscularSoul said:
I'm pretty sure that's what I'm on. System is 22.21.11.victara_tmo.en.US, build LXE2246-11, and Baseband MSM8974_4125.184.08.27.01R
If that's not the latest let me know and I'll grab the updated ones and flash those through fastboot and try again. If they are is there anything I could grab with the syslog app or adb that might help in figuring it out?
Click to expand...
Click to collapse
Got it. The APN protocol for fast tmobile com in my stock rom was IPV6, and when I flashed this it was IPV4. Changing that got my data connection working.

crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
I have the T-Mobile pure and left the base as 4.4.4 and flashed cm12. Signal is awesome as are the transfer rates.
I've tried liquid and slim with the same results.

How will the battery? Better or worse than stock?
Works in XT1097, right?

I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?

loic5032 said:
I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?
Click to expand...
Click to collapse
you have to go into TWRP, then WIPE then Format Data. then install rom and gapps.
you will format your memory loosing everything on your phone. i used to plug an usb otg with rom and gapps files.

double tap
Can we get some double tap to wake love? That was basically my favorite thing about my oneplus one and i put cm12 on that and works great
Let me know if thats going to happen or not because i cant live without that or the moto display

I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed

michyall said:
I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed
Click to expand...
Click to collapse
Well i mean just having the option would be nice
its personal preference and my case makes it very difficult to press the power button

Nexus 6 with Android 7 on T-Mobile

I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?

Klownicle said:
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Click to expand...
Click to collapse
I don't know of any reason why you can't just download the NBD91P image from here and flash each partition manually from the bootloader using fastboot, or download the NBD91P OTA image from here and flash it following the instructions on that page. I haven't heard or read anything at all that the stock factory image won't work on a T-Mobile Nexus 6.
Edit: If you haven't manually flashed an image before I have always used the instructions under "Method 2 : (Long, but works always)" on this page.

I would just load the OTA. There isn't any issues with it on t-mobile. was running the stock ROM for awhile. Now testing out CM14.1

I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.

Dopemusic89 said:
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Click to expand...
Click to collapse
I've never had any issues. My wife and nephew and older brother all have nexus 6 phones with nitro installed and have had zero issues on Tmo. Off hand have you checked your APN settings? Have you tried a fresh clean install? When I do a clean install I go and wipe, data, system, cache, etc, but leave internal storage alone. I know it gets wiped on install but I do it anyways to be sure. Other then checking APN settings and or fresh install I am stumped why anyone should be having issues. Sorry I can't give more insight. I guess the other issue could be your radio ....May want to look into flashing a different radio to see how it fares
Edit -. Link for flashable radios
http://forum.xda-developers.com/showthread.php?t=3066052
Hope any of these suggestions help
Sent from my Nexus 6 using XDA-Developers mobile app

So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.

Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Note10.1Dude said:
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Click to expand...
Click to collapse

What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.

voyageurs60 said:
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Click to expand...
Click to collapse
I just posted this same response in a separate, but similar thread.
It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.

I have build number NBD92G. No issues for me; I took it as an OTA. It has baseband MDM9625_104670.31.05.42R. T-mo did not push a May security update that I am aware of; I hope that indicates they are trying to validate a 7.1.1.

So, T-mobile is still on 92G for the last 3 months without security update. With the rumors of 7.1 being pushed again, anybody seeing anything? We will be EOL in October for security updates, and I plan to side-load the final one if T-mobile doesn't push it, but I do think they should be doing their job and letting our phones take the latest updates.

[GUIDE] A Potential Fix for High CPU + Battery Drain on LOS/AOSP/OOS 7.x-based ROMs

I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads

Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!

madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome

I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.

I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.

The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0

peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/

That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.

sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.

peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..

Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.

peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!

lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:

After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?

Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks

AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it

Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237

Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app

Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!

I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?

[Discussion] Resurrection Remix 7 for Hammerhead (Android 9 Pie)

Hello everyone. I am opening this thread for the sake of convenience of us users of this ROM so that we stop hijacking the Oreo version thread and have a "clean" place where we can discuss about our experience with this great ROM. So I suggest anything regarding this ROM to be posted here!
You can find the official builds here: https://get.resurrectionremix.com/?dir=hammerhead
DISCLAIMER: I am by no means a developer or maintainer of this ROM, so this cannot be considered an official support thread, just conversation, plain and simple! Moderators can close this thread as soon as an official support thread opens.
Cheers!

I just installed the rom,came from stock. My first impressions are:
-It took 2 reboots to get the camera working. Installed google camera app since the integrated one doesnt show up on app drawer(you can access it from lockscreen though) and it seems to work kinda bad(picture goes black on it sometimes).
-It runs a bit hotter than stock rom. It might be just me though,I have opened the phone a few times to fix the power button which seems to get stuck for me once in a while.
-The default DPI doesn't seem right,everything looks a little bit smaller than it does on stock rom. There is an option to change it though, I set mine to 380 and it looks about right.
I haven't found any other issues yet.
Another note,I think the rom fixed my notification led lol. It didn't work for me on stock rom for some reason.
Pretty good rom overall,I haven't faced any stability issues yet.
edit: Is there any way to lower the resolution?

I upgraded from RR's Oreo build. Before flashing I repartitioned the phone using the method described here and the even more detailed instructions posted by douguluskaien on page 12 of that thread. The flash went very smoothly and although the phone initially ran hot it cooled back to normal after a few hours of what was probably background processing. With the 1.5G system partition I was able to install the micro version of GAPPS. I've had that experience after flashing new ROMs on other phones as well. I also discovered the bundled camera doesn't work and installed Google Camera. After starting up Google Camera, the original camera worked also. I tried connecting bluetooth headphones, and even though I could pair the headset I couldn't get the phone to send audio - it just kept playing through the phone speaker. I also found the default font size a little small, but changing it to Large in the Font Size menu got it back to what seems like normal.
I have one major issue which I realize is not directly related to the ROM. A custom version of TWRP is required to support the non-standard partitions, and that version is based on TWRP 3.2.3 and doesn't support device encryption. Does anyone know if an updated TWRP will be available that will allow me to encrypt the phone and still do recovery-related stuff?
In summary, this is impressively well along for a build that's only been live for a couple of weeks. This isn't my daily driver so I don't need absolute stability, so this is plenty for me for now. I just won't leave the house with it until I can encrypt.

I've been using this ROM for about a month now as a daily driver, so here's my feedback:
ROM is very nice and smooth and feature rich (as expected for RR). I installed it with Opengapps nano, rooted with Magisk. It works very well with the Pixel launcher I grabbed from here.
Some drawbacks I noticed:
Battery life is rather bad. I get 1h30m SOT at best with very mild usage (mostly site browsing and a little bit of social apps and YT video watching) . Then again I am still using the 5yr old battery that came with the phone...
The phone runs very hot (too hot to hold!) after using it for some time. It cools down rather fast if you let it be for a while, though.
Sometimes the camera is crashing (the notorious "can't connect to camera" error). usually a reboot fixes this.
Sometimes it takes a while for the device to wake up after pressing the power button.
I got some soft reboots under device heavy load. Mostly I get them when using the Rocket player music app, and it tries to load a large music folder. Phone freezes, then soft reboots.
SElinux is set to permissive and the build is signed with test keys. Maybe the first thing is caused by the latter, I don't know really....
Overall, it is a good ROM with room for improvement. However, I am concerned about its maintenance status. No update since May 14, so I keep my fingers crossed.

New build (28/07) uploaded!

hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
I am not able to install it giving me ERROR 7

hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
Do you know about change log??
What features added?
I want to update it tonight

As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
m.morcielago said:
Do you know about change log??
What features added?
I want to update it tonight
Click to expand...
Click to collapse
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...

I flashed this build this morning by dirty way
Unfortunately Bluetooth is not working
It can find the other devices but can not connect to them
1- How can I fix it?
2-How can I downgrade to previous build?

hammerheadache said:
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
Click to expand...
Click to collapse
Thanks for the idea, I had just repartitioned, so I had format my entire phone, (before that i had taken the backup ), and I had successfully installed the rom, I got an strange issue of WIFI connectivity, as I am not able to connect to my wifi which is having Hidden SSID, but i am successfully connected with the hotspot from my another primary phone. i haven't tested the bluetooth yet.

I dirty flashed the new build this morning. Haven't tried bluetooth or camera yet, but Wifi is working fine. As usual, the phone heated up for about a half hour after the flash and then the temp dropped and stabilized. Battery life is not great, like the May build, and there is often a long delay responding to the power button, especially shortly after power-up, but the build seems pretty solid.

Casting isn't finding anything to cast to in the most recent build. Camera worked fine.

New build available (Aug 4) as seen at ROM's dl page.

Bluetooth pairing now working for me on last release

Hi installed this ROM in clean maner but i got intermitent issue with sim card. Not sure if it is only sim issue or reboot but phone ask my pin code.

Looks like @voidz777 is the maintainer for RR Pie as well:
https://github.com/ResurrectionRemix-Devices/api/commit/8388c5df5069cf04df04facbdc22a2bfd8890185

New build (09/08) in case someone missed it... Link in OP

sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.

New build (Sep 16) available! Link in OP.

princeknockouts said:
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
Click to expand...
Click to collapse
Thank you for the tip, I followed the thread and was able to install RR 7 without any trouble. This might not be the right place to ask, but would you have any info on how to install SuperSU on RR 7, or is there perhaps another root method that we must use? Thanks in advance, I can't seem to find information on it anywhere and rather than continuing to bang my head against the wall I thought I'd ask.

[ROM][Q][UNOFFICIAL] Lineage OS 17.1with Gapps

This rom is OBSELETE PLEASE USE @Linux4 lineage
https://forum.xda-developers.com/ga...om-lineageos-17-1-galaxy-tab-s6-lite-t4167037

What's working or not working?
Thanks for posting this!!

c_86 said:
What's working or not working?
Thanks for posting this!!
Click to expand...
Click to collapse
Everything is working fine from what I know been using it for a week. I think restarting and turning off takes a while though. That's what I've seen

Ok great but the download link doesn't work.

Fixed

Great thanks it's working now..

It doesn't looks like we have the same version of the Galaxy Tab S6 Lite. On my European SM-P910; I already tried both of you roms and it's always a boot loop. I tried different version of the stock rom before flash (XAR) and with blank vbmeta.tar with factory reset or/and cache but it never works for me. Like the other guy for the AOSP I go back to stock.

S Pen Functionality
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.

asiancurry said:
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.
Click to expand...
Click to collapse
You guyz are lucky. There's no development for Tab s6.

Can you make a microg version?

Greetings!
I successfully managed to install the lineage rom on my SM-P610. Initially i faced infinite boot-loop even after doing a factory reset in the recovery. After some experiments, i made it work. Heres what is did to get it work.
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
2. Keep your rooted boot.img safe.
3. Download the lineage os tar from the thread.
4. Using 7-zip, open the tar package and delete the included boot.img fiile,
5. Replace the boot.img with the rooted boot.img obtained from the first step.
6. Flash the modded lineage package with Odin 3.14.1-3b patched under AP (do not check the re-partition in ODIN).
7. After reboot, boot into recovery and do a factory reset.
8. After a couple of reboots, Lineage logo should appear
Will write what works and what doesn't in my next post.

Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.

gauthamrgramalingam said:
Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.
Click to expand...
Click to collapse
Thanks alot will add this to the list

Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.

Zeropoint said:
Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.
Click to expand...
Click to collapse
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback

Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I figured you wouldn't, but I thought I'd let you know. again, thanks.
---------- Post added at 07:19 PM ---------- Previous post was at 06:49 PM ----------
Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I forgot to ask, does this have root? because I was trying to do some debugging on the issues but I can't seem to get a root shell in adb.

Messing with it more, couple updates:
1. wifi 5g confirmed working.
2. netflix still not working at least for me.
Magnetic cover, might be due to SELINUX. I see this in the adb debug:
kworker/5:2: type=1400 audit(0.0:2321): avc: denied { open } for path="/sys/devices/virtual/sec/sec_key/hall_detect" dev="sysfs" ino=45321 scontext=u:r:kernel:s0 tcontext=ubject_r:sysfs:s0 tclass=file permissive=0
the magnetic cover might use the hall sensor, but not sure. There is another sensor that is getting AVC denied as well. Worth a look.

Awesomeslayerg said:
If it doesnt boot or bootloops thanks @gauthamrgramalingam
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
Click to expand...
Click to collapse
Which thread? Can someone link it?

Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!

Awesomeslayerg said:
Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!
Click to expand...
Click to collapse
awesome, let me know if you need any help.