[ROM] [OFFICIAL] LineageOS 14.X for Oneplus2 | Android 7.X Nougat
- Thread starter Ozzy2403
- Start date
Hi please stop spreading misinformation. You don't need to clean flash a nightly because of a kernel change
If you change something huge in the ROM then you might need a clean flash but you don't need to clean flash if it's just a kernel change
He dirty flashed older nightly, I thought maybe that's the issue.
Last edited by a moderator:
New nightly. Thanks @Ozzy2403 for the rebase, Hoping it will stable!
There's an issue with vibrations on HW keys. It is super soft, unnoticeable.
Vibrations on call and other longer vibrations seems to work fine. Boeffla says he reverted a commit in a test kernel build he posted and vibrations work fine in it.
There's an issue with vibrations on HW keys. It is super soft, unnoticeable.
Vibrations on call and other longer vibrations seems to work fine. Boeffla says he reverted a commit in a test kernel build he posted and vibrations work fine in it.
Me too, black screen right after the reboot with last nightly and boeffla beta 13, three times in a row.
So I tried last nightly with stock kernel and looks very laggy...
Back to 10.01 nightly with boeffla beta 11
So I tried last nightly with stock kernel and looks very laggy...
Back to 10.01 nightly with boeffla beta 11
It's quite the opposite for me. Wiped dalvik cache, flashed the latest lineage, gapps, boeffla, and supersu and didn't experienced any freezes yet. Running pretty smooth. Also battery life is a bit better too.
EDIT: Battery life is better most probably due to I forgot to install A.R.I.S.E
EDIT 2 : Experienced some madness when I was on messenger call and tried to switch from wifi to 4g. Screen started to turn itself on and off really quick. So boeffla didn't stop the weird behavior.
Last edited:
I'm on the last nightly with boeffla beta 12 and op5 camera. Everything is working well... Hardware botton are a little bit soft. I've noticed no lag when the battery drops under 20%,before it used to slow down a lot. Waiting the stock kernel to be stable again...
Inviato dal mio ONE A2003 utilizzando Tapatalk
Inviato dal mio ONE A2003 utilizzando Tapatalk
Google updates their devices from nougat to Oreo without needing a clean flash. So does oneplus and any other manufacturer
I've personally tried cm-13.0 -> cm-14.0 -> cm-14.1 without having any issue
Clean flashing repeatedly causes wear on your storage chip, it also slows down your phone significantly rather than speeding it up. Yes, clean flashing ruins your performance rather than helping it. Your phone will be hotter while charging because it has to do a lot of optimisation all over again. Not to mention your battery life will suffer for almost 2 weeks due to all the optimisation you just forced your phone to redo
Still think clean flashing is good for your device? Think again
I've personally tried cm-13.0 -> cm-14.0 -> cm-14.1 without having any issue
Clean flashing repeatedly causes wear on your storage chip, it also slows down your phone significantly rather than speeding it up. Yes, clean flashing ruins your performance rather than helping it. Your phone will be hotter while charging because it has to do a lot of optimisation all over again. Not to mention your battery life will suffer for almost 2 weeks due to all the optimisation you just forced your phone to redo
Still think clean flashing is good for your device? Think again
Last edited by a moderator:
Installed lastest nightly yesterday and I'm very surprised !
Didn't had any freezes for now and phone is smooth, well not as smooth as with Franco kernel but it's still smooth !
I'll stay with the official kernel for now to test it after the rebase, I've just noticed that in cpu monitoring apps, you can't see the CPU usage but that's a minor problem !
If you can get the kernel as good as Franco's kernel, it would be dope !
Didn't had any freezes for now and phone is smooth, well not as smooth as with Franco kernel but it's still smooth !
I'll stay with the official kernel for now to test it after the rebase, I've just noticed that in cpu monitoring apps, you can't see the CPU usage but that's a minor problem !
If you can get the kernel as good as Franco's kernel, it would be dope !
I've had 2 freezes that forced a hard reboot. Clean flashed with stock kernel.
Why do devs ask to clean flash for most builds?
CUZ THEY DONT KNOW WHAT USERS WILL BE HAVING IN ADDITION TO JUST ROM AND GAPPS.
And saying clean flashing will reduce device life, ofc normal usage will do it. It's like saying "Oh, don't use your storage to read and write files, it'll be worn out soon. Better don't use it all."
Chances of storage losing out completely due to repeated flashing is very low and it happens after an extensive period of time (more than 3 years).
CUZ THEY DONT KNOW WHAT USERS WILL BE HAVING IN ADDITION TO JUST ROM AND GAPPS.
And saying clean flashing will reduce device life, ofc normal usage will do it. It's like saying "Oh, don't use your storage to read and write files, it'll be worn out soon. Better don't use it all."
Chances of storage losing out completely due to repeated flashing is very low and it happens after an extensive period of time (more than 3 years).
Last edited by a moderator:
After kernel rebase, does this still reflect current security situation?
https://cve.lineageos.org/android_kernel_oneplus_msm8994
As more than 50 percent CVEs remain unpatched so not sure something has changed on this front...
1001 nightly was the worst build I ever had on this phone. Worst.
So bad it is pointless to even describe. There must have been commit causing it since nightly before it (which were getting better after disastrous rebase). I am on latest nightly already after kernel rebase so it doesn't matter now.
Running without issues for now, apart from haptic feedback but that will be sorted, check Boeffla thread.
So far it's fantastic, few stutterings here and there but great battery life and just single android.core crash (after 20 s freeze) but no reboots.
https://cve.lineageos.org/android_kernel_oneplus_msm8994
As more than 50 percent CVEs remain unpatched so not sure something has changed on this front...
1001 nightly was the worst build I ever had on this phone. Worst.
So bad it is pointless to even describe. There must have been commit causing it since nightly before it (which were getting better after disastrous rebase). I am on latest nightly already after kernel rebase so it doesn't matter now.
Running without issues for now, apart from haptic feedback but that will be sorted, check Boeffla thread.
So far it's fantastic, few stutterings here and there but great battery life and just single android.core crash (after 20 s freeze) but no reboots.
Attachments
This becomes even worse with Android N
On android N since we have a JIT compiler compilation occurs on the fly and clean flashing just forces the phone to redo the optimisation all over again. Did you ever see android system using a lot of battery after a clean flash? That's because it's re-optimising everything that was already optimised
Since after a clean flash nothing is really optimised and the JIT is still optimising everything CPU cycles are being used up and battery drain does occur.
Okay let's think about charging times.
Read https://source.android.com/devices/tech/dalvik/configure
So when the device is idle and charging it's going to optimise. That means it's going to run hotter and we all know what charging when a battery is hot does to batteries
Now imagine forcing this optimisation over and over again for every build
Storage wear
Let's say that a ROM has weeklies. User clean flashes each weekly and restores a 40 GB backup
Let's see in a month he writes 40 * 4 = 160gb
Oh wait how about a year? 160*52/64 is literally writing to the chip 130 times
Let's add the writes needed to flash the ROM, to backup the data and restore it, to build the dalvik
You'll end up with a count higher than 1000 full writes/year
Oh wait, that's just for weeklies. We got some users flashing nightlies
Oh man imagine what clean flashing could be doing
I have said this countless times and I'll say it again
Do not clean flash unless absolutely necessary
Last edited by a moderator:
Gents,
There are a few posts unrelated to the thread topic. Here I'd ask everyone to take a deep breath, read XDA Rules and have a open and respectful mind to each other.
There shall be no off topic discussion after this post. Consider this as a final friendly reminder.
I'll clean some posts above. OK, done. Some information was left for reference only.
Regards
Jerry
There are a few posts unrelated to the thread topic. Here I'd ask everyone to take a deep breath, read XDA Rules and have a open and respectful mind to each other.
There shall be no off topic discussion after this post. Consider this as a final friendly reminder.
Regards
Jerry
Last edited:
It only happens to me when the battery is not calibrated.
Use your phone until the battery is at 0%. Then charge it up to 100% in one go.
Same unexpected freeze, this time while putting phone to sleep
One looses around 15 percent of battery...
Nothing to do with battery calibration of course...
Edit: put my phone to charger to find out I can't turn it on after 3 hours. As always holding power for 30 seconds to power phone up.
I believe one of the freezes happened but this time battery was 97 percent upon unplugging.
Is quite risky that switching of the phone during sleeping as I need my alarm :laugh:
One looses around 15 percent of battery...
Nothing to do with battery calibration of course...
Edit: put my phone to charger to find out I can't turn it on after 3 hours. As always holding power for 30 seconds to power phone up.
I believe one of the freezes happened but this time battery was 97 percent upon unplugging.
Is quite risky that switching of the phone during sleeping as I need my alarm :laugh:
Attachments
Last edited:
Also one bug to report which I got on couple of builds... Very seldom so bug is rare but happened again so reporting.
Taking picture via stock camera produces sound and all, but the picture won't be there
I lost one this morning, around 3 pictures few weeks back
That's critical as one thinks he took notes via camera (my case) realising they are nowhere to be found
Taking picture via stock camera produces sound and all, but the picture won't be there
I lost one this morning, around 3 pictures few weeks back
That's critical as one thinks he took notes via camera (my case) realising they are nowhere to be found
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone