Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
These scripts is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: These scripts is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting these scripts fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move the scripts to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-06
Last updated: 2019-10-25
Note: The changelogs have been strictly moved to the release posts.
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
freebee269 said:
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
Click to expand...
Click to collapse
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
On 2xl there was a file wich showed that mod works. How about 3 xl?
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
xFirefly93 said:
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
Click to expand...
Click to collapse
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
blaze9090 said:
On 2xl there was a file wich showed that mod works. How about 3 xl?
Click to expand...
Click to collapse
Gordietm said:
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
Click to expand...
Click to collapse
For now, you have to manually create a folder in your internal storage named "logs" (without quotes) because of some security kind of thing that Google have addee which prevents "automatically" created folders to even be made at all.
Otherwise the specific output log, that tells you if the script could execute or not, won't be generated because of a non-existing path / folder.
I will though look around for a possible workaround and see if it can be added directly within the BlackenedMod script for maximal flexibility directly on-the-fly.
freebee269 said:
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
Click to expand...
Click to collapse
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
gaseoso said:
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
Click to expand...
Click to collapse
Enjoy!
xFirefly93 said:
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Click to expand...
Click to collapse
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
freebee269 said:
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
Click to expand...
Click to collapse
Try with clean flashing stock firmware.
*Deleted*
xFirefly93 said:
Try with clean flashing stock firmware.
Click to expand...
Click to collapse
that worked. i backed up my current system image and data in twrp. then did the flash-all.bat without -w. then went back into twrp and rooted the stock kernel. then went back into twrp and restored my backup. thanks a lot. will report back on how its gone after a couple days.
Telegram:
Not for going off-topic far too much now but..
If you want to hang out a little, try previews / betas of BlackenedMod for Pixel 3 (XL) before they are officially released or just want to meet a lot of awesome people from every possible corner of the woeld - then join the official Telegram group, fully dedicated to the P3(XL) line-up here.
:highfive:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Gordietm said:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Click to expand...
Click to collapse
I am keeping it universal with everything good / great / greater than greatest from every kernel organized in the same package and place.
so i followed instructions, got it all done, rebooted, i'm good to go? don't need to do anything just set it up and go right?
Is there a way to tell if this is working?
Related
===============================================================
Issue closed, read:
http://forum.xda-developers.com/showpost.php?p=42638124&postcount=17
===============================================================
l2_hsic issue
l2_hsic running amok (GT-P7500, GT-P7501) is ONE considerable reason for abnormal battery drain.
The so far known counter measures (HC, Stiffmeister + its xda derivate, WiFi-ROM) do not comply to my requests:
- CM10.1 nightlies
- 3G usage
- no l2_hsic hassle
l2_hsic root cause
Analysis of kmsg files provide a consistent pattern. Function if_usb_suspend(..) from modem_link_device_hsic.c does not call wake_lock_timeout(..) in wakelock.c in case of l2_hsic is running amok.
The missed call to wake_lock_timeout is obviously caused by a non cancellable USB-connection.
It is a single non expiring wakelock, what makes trouble.
Inside of modem_link_device_hsic.c I lost track on further explanations.
Candidate to fix the issue
Since I cannot correct the root cause, I tried to fix its consequence.
Basis is the current pershoot P4 CM10.1 kernel.
There are a few spots in its source code, where one could obtain the so called prevent_suspend_time of a l2_hsic wakelock.
A monitor is installed in such place. It triggers, when a l2_hsic wakelock’s individual prevent_suspend_time exceeds >10s (empirical value).
In this case the function wake_lock_timeout is called, which ignites the wakelock’s expiration.
Next the trigger is reset and the monitoring becomes active again.
As a second and measure of last resort the tab is shutdown, once l2_hsic’s total prevent_suspend_time exceeds >1h (never happened so far).
All these events are logged:
--> /proc/grzwolf shows current status
--> /proc/kmsg is extended by a couple of messages
Verification
The described modified kernel was installed on my Tab months ago.
Since then DS works perfect to me.
Furthermore I did not experience any side effects.
This kernel-mod had been announced at
http://www.android-hilfe.de/samsung...s-10-1n-mit-stock-4-0-4-a-69.html#post5550736
Meanwhile the kernelmod is integrated:
BeeGee(Ganbarou), AAccount(A1 Kernel), kasper_h(Team Infamous/AOKP) and twa_priv(CM10.1/SGT7)
Preconditions for installation
- the kernelmod applies only for P4 devices (GT-P7500, GT-P7501)
- no need to contiue, if you don’t have a l2_hsic issue
- if you continue, you should know what you are doing
- I don’t take any warranty
- after flashing a Nightly ROM, the kernelmod needs to be installed again
- CM10.1 is installed on P4 according to the OP of thread http://forum.xda-developers.com/showpost.php?p=36077123&postcount=1
Kernelmod installation
- comply to the preconditions above
- within CWM make a Nandroid backup of a running isntallation
- copy 'P4 kernel' (see downloads below) to your Tab
- install 'P4 kernel modified' within CWM and check functionality after booting up
- if not ok, restore in CWM your Nandroid backup
Credits
- pershoot (Kernel)
- MapleSyrup (Kernel build)
- nakedninja42 (CM10.1 Installation)
Changelog
Rev. 2013.04.10-19.44
first release
Downloads
- CWM flashable kernel zip, Rev. 2013.04.10-19.44
- md5 sum of kernel zip
- source code
- readme source code
All hail grzwolf! Thank you so freaking much for finally finding the fix that no one could. I now don't need to flash a WiFi ROM to get rid of the l2_hsic issue.
Sent from my GT-P7500 using XDA Premium HD app
Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?
C-o-M said:
Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?
Click to expand...
Click to collapse
Root Cause
According to my current testing (next revision kernelmod), I'm almost convinced it's caused by a race condition
between modem and modem interface (most likely the "kill_urb stuff").
Just by adding the extended logging in "if_usb_suspend" seem to have wiped the issue with the missing "wake_lock_timeout".
As next I'm going to switch back to the erroneous behaviour, verifying this theory.
If this approach would stand, the extended logging could be replaced by reasonable delays.
Not impossible, that the whole silly detection & triggering in wakelock.c is not needed.
Usage
That would be fine to me, so no problems at all with code re use.
You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?
C-o-M said:
You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?
Click to expand...
Click to collapse
That's what I'm currently trying out.
I would never had come up with this assumption, without the wish to understand the logic behind.
Since the nature of this presumable race condition is a fickle ***** (if my assumption is correct),
it may take a while to have solid evidence.
Although, it sounds tempting.
Thank YOU!!!
Thanks for this fix grzwolf, works as it should. Now my P7500 is great with cm10.1 and good battery life. :good:
theone
Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks
saigon66 said:
Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks
Click to expand...
Click to collapse
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip
CHN Kernel
grzwolf said:
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip
Click to expand...
Click to collapse
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks
Phibs said:
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks
Click to expand...
Click to collapse
Your suggestion is absolutely conclusive and would be definitely worth a follow up.
Afaik only Samsung knows, what sources and settings were used to build this specific Chinese Kernel,
Means, they are very unlikely available. Otherwise the magic would have been unveiled long time ago.
I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta
doctorow said:
I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
At least for me.
Afaik it would end up with machine code / assembler language.
Another tool were required to translate it into C.
Even then, there were no really meaningful function and variable names.
Means, one couldn't easily compare this with existing sources.
Finally the whole exercise could result in already known source code.
Not impossible, that the "magic of the China-Kernel" is caused by very specific compiler or optimization settings, which cannot reverse engineered.
Too many if and may be ...
Comparing kernel sources is a very good idea.
Pershoot's p4 kernel is based on Samsungs kernel sources for GT-P7510, Opensource Update 2, released in April 2012 (AFAIR).
For the p5 kernel, I always rebased pershoot's kernel to the latest sources (to GT-P7300_HK_ICS_Opensource_Update1.zip in September, to GT-P7300_ICS_Opensource_Update1.zip in December). No one has ever reported the l2_hsic bug on CM for p5. Neither on CM10 (where I used the chinese kernel sources), nor on CM10.1 (updated to the official ICS sources). But the bug occured for example on AAcount's kernel which isn't rebased. So Samsung seems to fixed the issue in the kernel instead of doing some "magic hacks".
I commited a lot of different p4/p5 kernels to github to make it easier to compare them. I guess you'd like to take a look on those changes:https://github.com/cmorlok/android_kernel_samsung_p5/tree/P7300_ICS_U1/drivers/misc/modem_if
Great, of course I would. Thanks.
Just kdiffed modem_link_device_hsic from your recent P5 against P4, there are non trivial differences.
I'll give it a try right away.
hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx
pershoot said:
hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx
Click to expand...
Click to collapse
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.
Do you think this will get merged into where ever it is that the cm team get their kernals from?
grzwolf said:
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.
Click to expand...
Click to collapse
cool thx grzwolf.
Lol, shows how much I pay attention. I completely missed pershoots post.
Edit:
Ok, looks like this should be in the nightlies now....
http://forum.xda-developers.com/showpost.php?p=42680093&postcount=1875
BASIC KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
PRO KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
synapse support (installs with kernel)
cpu oc/uv support
gpu oc/gpu support
battery tweaks
network tweaks
... and much more
This branch is mainly based on skyhigh kernel (@UpInTheAir)
PRO-VTFB KERNEL
The same as pro branch with vt and fb enabled support.
if doubt, do not use it.
note: booting is longer as usual
CHANGELOG:
v1.3:
- optimization and performance tweaks
v1.2:
- Synced with SkyHigh kernel 1.9
DOWNLOAD
Basic branch v1.0 https://yadi.sk/d/IYF-XNCGbbrPh
Pro branch v1.3 https://yadi.sk/d/SKdK47o1bwJTT
Pro-vtfb branch 1.3 https://yadi.sk/d/XbwusUz8bwJUQ
CREDITS
UpInTheAir, xluco, halaszk88, AndreiLux and many others
SOURCE CODE
https://github.com/bonuzzz/kernel_p900
Great a lot of people have been waiting for this will flash and test it out later tonight
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
ExtremeRyno said:
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
Click to expand...
Click to collapse
I'm a retired deveopler and don't mind helping out a little where I can. I've enjoyed tweaking my P900 to the max & I'm also glad to finally see some stuff coming out here on XDA for the P900 wifi version. Not much activity on any other forum for this device either. Most likely because of the price of the device and people worring about the Knox tripping issue. I noticed on another forum that someone had compiled a fully functional kernel however they too were experiencing issues with the camera. Anybody have any ideas of whats causing the camera issue? I can possibly help out with the developement of a AOSP rom, or a blazing fast slimmed down ROM. I have plenty of developement knowledge in this area, if there are any interest for one. As for the Kernel issues I'm not too familiar with the compiling however most likely could figure it out.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Flashed this kernel and my tablet won't boot
golfinggino said:
Flashed this kernel and my tablet won't boot
Click to expand...
Click to collapse
? I hope you made a backup of your stock kernel before flashing...
Has anyone else flashed this kernel and can confirm if it is booting or not?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
golfinggino said:
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
Click to expand...
Click to collapse
Can you describe what happens when you select the "Camera" application. Does it force close, not launch, display some type of error. If you could provide the details of what happens, it may be possible to provide a working solution or "Work around."
Also, try installing another camera application from the Android Market and see if that application works. Maybe using another camera source will work and that could be a temporary work around till the issue us resolved. Let us know. Thanks!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Mine says warning camera failed
golfinggino said:
Mine says warning camera failed
Click to expand...
Click to collapse
Ok, Thanks. We'll see if we can figure this thing out...
Did you try installing another camera app from the play store and see what happens when you launch it?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Sterist said:
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Click to expand...
Click to collapse
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
flashlight doesn't work
bonuzzz said:
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
Click to expand...
Click to collapse
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Sterist said:
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Click to expand...
Click to collapse
i think there is problem with permissions but i can't find where is exactly
bonuzzz said:
i think there is problem with permissions but i can't find where is exactly
Click to expand...
Click to collapse
probably SElinux
Sterist said:
probably SElinux
Click to expand...
Click to collapse
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
if anyone want to help, this is a kernel without any mods https://yadi.sk/d/-RWbv8htbYW28
ps: replaced link above. logcat is working here
bonuzzz said:
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
Click to expand...
Click to collapse
that might be the app not able to turn on this tab's LED
torch apps work
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Spere said:
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Click to expand...
Click to collapse
p900 doesn't have dialer
z device test detects both cameras..
i now realize why it seems much faster - i am running with interactive and fiops and it is contantly at 2000mhz no lower frequencies are being used - i though it was like this on performance not interactive - obviously the battery is not great right now lol
Mod edit: Thread closed on owner's request!
exNoShadez-EAS Kernel
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard VPN kernel module support (more info soon)
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on this subject below => in the 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/SailfishStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/sailfish/twrp-3.2.2-0-sailfish.img
WARNING: This shouldn't need to be said, but we did have someone who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip. ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as opposed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation. Therefore; I do NOT support installing TWRP....
I like it so far, very good kernel.
Awesome! Always nice to have choices
I've seen you post around that you made x change to your own kernel, glad you finally made it public!
Does it have all of franco's wakelocks blocked by default?
グリッチ said:
Awesome! Always nice to have choices
I've seen you post around that you made x change to your own kernel, glad you finally made it public!
Does it have all of franco's wakelocks blocked by default?
Click to expand...
Click to collapse
hey, it includes franco's wakelocks stuff. I don't think all are blocked, I actually don't touch them in my init rc. ... but some are blocked by default, for sure. can be set by user...
yeah, I've got my kernel to a point now, where it is somewhat unique && is drawing in most of the best features from every custom kernel for the pixel (my opinion). very stable too, thus far. so makes sense to make it public.
it's got the RCU (read copy update) infrastructure from linux-4.9... a ton of core, sched, Walt, etc from linux-4.4+ (specifically, from EAS-Project / msm8998 OP5 - which was painful to backport. wish we didn't have a 3.18 kernel. lol) afaik, it's the only Marlin kernel with Dynamic Stune Boost and aside from CopperheadOS; the only marlin kernel with a subset of the PAX/grsec kernel security enhancements and the Mac randomization... also has all of the audio enhancements from the kernel ur running ?
siheals said:
I like it so far, very good kernel.
Click to expand...
Click to collapse
Hey! thanks for testing it out. let me know how things go, your impressions, etc.
I'll be updating this kernel constantly, so if u end up liking it; you can expect that it will always include security patches, linux LTS incremental patches, etc...
it's my daily driver, so i keep on top of it.
Superb! Thanks for clarifying.
I will give it a run when November update releases cuz I'm lazy >.< but am excited and looking forward to it ^_^
グリッチ said:
Superb! Thanks for clarifying.
I will give it a run when November update releases cuz I'm lazy >.< but am excited and looking forward to it ^_^
Click to expand...
Click to collapse
no probz. As soon as the november updates arrive, i will be adding whatever patches are needed... so expect that to be there...
i also pull from Code Aurora msm-3.18 for 8996, so my kernel gets updates to drivers, core, etc that google hasn't picked up yet.
Just Testing 3.18.79 + latest Code Aurura updates for today ....AND;
re-enabling a hardening feature that I thought was draining battery life (Likely not, was probably another removed patch - that isn't in the current release.)
I'll update the link later on and - on my github; where I link to for downloads; there will be older releases labeled - ie:
exNoShadez_eas.zip (current release / link) will become -> exNoShadez_eas_3.18.78_oct.zip,
when it is replaced by 3.18.79 + other updates / patchwork.... The current release will always be -> exNoShadez_eas.zip
UPDATE:
While I haven't updated exNoShadez_eas.zip link/version, * I have posted a zip with the above changes - I'll be testing it for a while before updating the link because it's hard to gauge battery life without a lot of testing / time spent.... So I would say, if anyone is eager - they can test it, but wait at least 12-24hours from testing the current available release - so you can actually make some sort of real-usage comparision.
link: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_3.18.79_harden.zip
Glad to see you have posted this man. Setting up a pixel for my friend and as i was browsing the forums noticed you have a lot of good kernel work. Was literally about to PM you a few days ago for your kernel and then happened to see this post today. Can't wait to try it out!
Warrimonk said:
Glad to see you have posted this man. Setting up a pixel for my friend and as i was browsing the forums noticed you have a lot of good kernel work. Was literally about to PM you a few days ago for your kernel and then happened to see this post today. Can't wait to try it out!
Click to expand...
Click to collapse
All good, man.
It only makes sense that I would share my kernel, when I felt it was ready for that - just keep in mind, that for now - I have marked it as Beta / Testing, as it's pretty new (although, aside from the EAS code / Dynamic Stune Boost - the rest has been thoroughly vetted)....
So yeah, give it a run, let me know how things go! thanks
Unsure if I am doing something wrong or not, but when I try to flash your kernel I get an error stating : "New Image larger than boot partition. Aborting...."
EX Kernel flashed fine. Using TWRP 3.1.1-1
Warrimonk said:
Unsure if I am doing something wrong or not, but when I try to flash your kernel I get an error stating : "New Image larger than boot partition. Aborting...."
EX Kernel flashed fine. Using TWRP RC1.
Click to expand...
Click to collapse
Why aren't you using the newest stable version of TWRP?
RC1 = release candidate 1
afaik, latest release is 3.1.1-1 stable for the pixel.... https://dl.twrp.me/sailfish/
Using an old version might be your issue. Update, then try.
nine7nine said:
Why aren't you using the newest stable version of TWRP?
RC1 = release candidate 1
afaik, latest release is 3.1.1-1 stable for the pixel.... https://dl.twrp.me/sailfish/
Using an old version might be your issue. Update, then try.
Click to expand...
Click to collapse
Apparently I am using TWRP3.1.1-1 . The thread was called RC1 So I mistakenly assumes that was still the current version.
Warrimonk said:
Apparently I am using TWRP3.1.1-1 . The thread was called RC1 So I mistakenly assumes that was still the current version.
Click to expand...
Click to collapse
Can confirm this, I'm on 3.1.1-1 too and got this issue.
I'm running 8.0.0 (OPR3.170623.008, Oct 2017) build.
Keasby said:
Can confirm this, I'm on 3.1.1-1 too and got this issue.
I'm running 8.0.0 (OPR3.170623.008, Oct 2017) build.
Click to expand...
Click to collapse
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
32MB is the boot image max size AFAIK.
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
Maybe it's caused by the image size. Other custom Kernels are sized bout 13mb.
I'm running the Google Stock Build OPR3.170623.008, October 2017.
Hope you can fix it - TIA!
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
Personally I tried on these 2 firmwares:
sailfish-ota-opr3.170623.008
sailfish-ota-opr6.170623.012
The phone was originally a Project Fi device.. if that matters. Dev which firmware and TWRP are you using?
Warrimonk said:
Personally I tried on these 2 firmwares:
sailfish-ota->>>>opr3.170623.008<<<<<
sailfish-ota-opr6.170623.012
The phone was originally a Project Fi device.. if that matters. Dev which firmware and TWRP are you using?
Click to expand...
Click to collapse
I'm using the latest twrp-3.1.1-1 (but and idk if this makes a difference or not), I only use the twrp fastboot img (Ihave ZERO reason to actually install TWRP on my system).... and also, Others have installed and are using my kernel - so it must be a difference in firmwares / boot partition size (or image size)
Keasby said:
Maybe it's caused by the image size. Other custom Kernels are sized bout 13mb.
I'm running the Google Stock Build >>>>>OPR3.170623.008<<<<<, October 2017.
Click to expand...
Click to collapse
So yeah, I'm using a different build **OPR1.170623.027**, Oct 2017, Fi/Canada.... you both are having problems on >>>>>OPR3.170623.008<<<<< ~> Something is different in that build... If you like (and happen to have that image kicking around, you could send me the boot.img and I'll compare it to mine? later on)
I'm thinking it's not the kernel size, although - I do plan on making the kernel smaller on production builds, by reducing a lot of debugging that really isn't needed on a production build (I already have a defconfig for doing so);
I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
{
"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"
}
What is Dotos?
dotOS is an Android ROM which focuses on performance and stability. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get most out of his/her device.....
Make Sure You Have TWRP 3.6.0
Download the latest build (gapps included)
Reboot to recovery
format data
flash multidisabler
Flash the ROM and Kernel (the one linked below)
Flash Magisk (Magisk) (only this one)
Reboot
extract zip
flash!
Code:
Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
------------------------------------------------------------Bugs and their Workarounds-----------------------------------------------------------------
Read all the steps correctly
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot and it will be hard to get back into the system (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
shorturl.at/uAKO2 (rom download)
-------------------------------------------------------------------------Boot-fix and tweaks-------------------------------------------------------------------
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Gcam: download latest bsg and a70 config
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Get fast charging
by default a70 on pe charges really slow this enables fast charging for the a70 on dotos
to install download from https://drive.google.com/file/d/1KguCeLD-VHShm0MYzKhYrsAv-rZAuJeA/view?usp=sharing
Now install the module it will ask you to use volume keys follow the insturctions and choose 4500mah 27w once installed reboot! now enjoy faster charging (note: this will not affect battery/ will barely affect battery )
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
also type in /extraopt everything (do this once a week)
- Go to the settings tab and use the AUTO settings for FDE AI.
install gms doze magisk module
GitHub - gloeyisk/universal-gms-doze: Optimized and adjusted Google Play servicesOptimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk
[MODULE] CloudflareDNS4MagiskHello, As John Graham-Cumming announced, Cloudflare now offers its own DNS service. And surprise of the Boss if we believe his words: your history of browsing isn't saved on their servers ! DNS ?? Gne ?? What's this ? To make it...
forum.xda-developers.com
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
download bsg gcam latest (not providing here cause it keeps getting updates and i cant keep up)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik to get safteynet working
Lmao
Why on Earth would someone go through so much to render their A70 almost useless? Why would one remove a fully working stable operating system to replace it with a half ass working one that may or may not become a paperweight?
Stock 11 with custom recovery twrp rooted with magisk, passing saftynet with saftynet fix and then fully debloat manually...... I have to tell you, i have no issues, no bugs, everything works except, well wait, nope, everything works......
Come on people, I get wanting custom rom over stock but this is getting ridiculous.
MarvinMod said:
Why on Earth would someone go through so much to render their A70 almost useless? Why would one remove a fully working stable operating system to replace it with a half ass working one that may or may not become a paperweight?
Stock 11 with custom recovery twrp rooted with magisk, passing saftynet with saftynet fix and then fully debloat manually...... I have to tell you, i have no issues, no bugs, everything works except, well wait, nope, everything works......
Come on people, I get wanting custom rom over stock but this is getting ridiculous.
Click to expand...
Click to collapse
lol
this is stable i dont get it LOL
why are you on xda if you dont like custom roms?
Zainullahk1234 said:
lol
this is stable i dont get it LOL
why are you on xda if you dont like custom roms?
Click to expand...
Click to collapse
Never said i didnt like custom roms, in fact i wish i could use Lineage os. However, development on the A70 is just a repeat of the next. The same bugs formally listed above has not changed or been fixed since the start of said development. As of now, in my opinion, developers are pushing custom roms out like water but its a downgrade. Calls dont work, need to do work arounds to get it to work, if you can get it to work and forget dual sim altogether. Camera stuck on 8mp. Headphones may or may not work. Major bluetooth bugs. Battery issues and the risk of not being able to charge but hey lets throw in a work around that is still risky. Invalid cpu configuration causing lags and overall harder workload on the graphics. Invalid overlays creating a blinking dot where the proximity sensor is.
Random reboots should the u.i. hang.
I mean, the list goes on and on and the bug list is getting bigger with each new rom or kernal. When i realized that samsung would never release the proper drivers for this device, I stopped and removed my development on the project. Installing a custom rom on this device at this point in time make the device worse then stock. At least with stock, twrp and magisk v23, you can debloat and still enjoy your device with everything working as it should. If developers wish to continue development for this device then work on fixing the bugs rather then how many roms they can push out. Thats in my opinion.
You will find that there are more the 10+ roms or kernals all with the same bugs if not more and no development on fixing the bugs so my question is why would someone want to downgrade and deal with a very unstable device just to say they have custom this or that? Makes no sense.
MarvinMod said:
Never said i didnt like custom roms, in fact i wish i could use Lineage os. However, development on the A70 is just a repeat of the next. The same bugs formally listed above has not changed or been fixed since the start of said development. As of now, in my opinion, developers are pushing custom roms out like water but its a downgrade. Calls dont work, need to do work arounds to get it to work, if you can get it to work and forget dual sim altogether. Camera stuck on 8mp. Headphones may or may not work. Major bluetooth bugs. Battery issues and the risk of not being able to charge but hey lets throw in a work around that is still risky. Invalid cpu configuration causing lags and overall harder workload on the graphics. Invalid overlays creating a blinking dot where the proximity sensor is.
Random reboots should the u.i. hang.
I mean, the list goes on and on and the bug list is getting bigger with each new rom or kernal. When i realized that samsung would never release the proper drivers for this device, I stopped and removed my development on the project. Installing a custom rom on this device at this point in time make the device worse then stock. At least with stock, twrp and magisk v23, you can debloat and still enjoy your device with everything working as it should. If developers wish to continue development for this device then work on fixing the bugs rather then how many roms they can push out. Thats in my opinion.
You will find that there are more the 10+ roms or kernals all with the same bugs if not more and no development on fixing the bugs so my question is why would someone want to downgrade and deal with a very unstable device just to say they have custom this or that? Makes no sense.
Click to expand...
Click to collapse
camera is 12mp LOL (and gcam makes it 10x better)
headphones work bluetooth works
battery is good invalid cpu?
just stop chatting here if you dont care
Zainullahk1234 said:
camera is 12mp LOL (and gcam makes it 10x better)
headphones work bluetooth works
battery is good invalid cpu?
just stop chatting here if you dont care
Click to expand...
Click to collapse
No, camera is supposed to be 32mp and gcam is just another bloatware built by google. Headphones and Bluetooth work? You mean "when" they work...
Battery is good yet dont let it die or youll have a paperweight?
Yes sir, do you not check your cpu limits? Very high usage i must say, i mean one invalid or mistyped code just couldn't cause any issues right!?
Im not trying to harp on your work or anyone elses but it seems that you guys are dead set on pushing out roms that are doing more harm then good to the device. Custom roms for the A70 is a downgrade from stock and thats just facts. Custom roms are supposed to be better then stock but for this device at this point in time, its not.
MarvinMod said:
No, camera is supposed to be 32mp and gcam is just another bloatware built by google. Headphones and Bluetooth work? You mean "when" they work...
Battery is good yet dont let it die or youll have a paperweight?
Yes sir, do you not check your cpu limits? Very high usage i must say, i mean one invalid or mistyped code just couldn't cause any issues right!?
Im not trying to harp on your work or anyone elses but it seems that you guys are dead set on pushing out roms that are doing more harm then good to the device. Custom roms for the A70 is a downgrade from stock and thats just facts. Custom roms are supposed to be better then stock but for this device at this point in time, its not.
Click to expand...
Click to collapse
oneui also takes on 12mp LOL
also oneui is bloat gcam is notbloat its 1000x better
oneui is trash bloat
and yesh eadphones and bluetooth work in content and everything but calls which they are kinda buggy
also nobody ever forced you to use a custom rom this is your choice if you want to install or not
also who ever asked you?
your just a puny child with 0 knowledge who justs complians like a baby
MarvinMod said:
Never said i didnt like custom roms, in fact i wish i could use Lineage os. However, development on the A70 is just a repeat of the next. The same bugs formally listed above has not changed or been fixed since the start of said development. As of now, in my opinion, developers are pushing custom roms out like water but its a downgrade. Calls dont work, need to do work arounds to get it to work, if you can get it to work and forget dual sim altogether. Camera stuck on 8mp. Headphones may or may not work. Major bluetooth bugs. Battery issues and the risk of not being able to charge but hey lets throw in a work around that is still risky. Invalid cpu configuration causing lags and overall harder workload on the graphics. Invalid overlays creating a blinking dot where the proximity sensor is.
Random reboots should the u.i. hang.
I mean, the list goes on and on and the bug list is getting bigger with each new rom or kernal. When i realized that samsung would never release the proper drivers for this device, I stopped and removed my development on the project. Installing a custom rom on this device at this point in time make the device worse then stock. At least with stock, twrp and magisk v23, you can debloat and still enjoy your device with everything working as it should. If developers wish to continue development for this device then work on fixing the bugs rather then how many roms they can push out. Thats in my opinion.
You will find that there are more the 10+ roms or kernals all with the same bugs if not more and no development on fixing the bugs so my question is why would someone want to downgrade and deal with a very unstable device just to say they have custom this or that? Makes no sense.
Click to expand...
Click to collapse
Absolutely true!
The best thing for the A70 is stock One UI, rooted, and debloated
huh ! kids playground
stop it morrans
ScottThijs said:
Absolutely true!
The best thing for the A70 is stock One UI, rooted, and debloated
Click to expand...
Click to collapse
Just dont update magisk past v23 if you want to keep safetynet pass.
kiarash0 said:
huh ! kids playground
stop it morrans
Click to expand...
Click to collapse
You right
MarvinMod said:
Just dont update magisk past v23 if you want to keep safetynet pass.
Click to expand...
Click to collapse
totally incorrect
flashing universal safteynet fix works perfectly
Zainullahk1234 said:
totally incorrect
flashing universal safteynet fix works perfectly
Click to expand...
Click to collapse
Update magisk to 24.1 then show me it works considering magisk hide options were removed in v24 as well as saftey net checks.
MarvinMod said:
Update magisk to 24.1 then show me it works considering magisk hide options were removed in v24 as well as saftey net checks.
Click to expand...
Click to collapse
yup here you go LOL
easy pass (btw the safteynet test from bitgapps is broken all others work)
Why did you share a GSI and claim it's official?
ataberkozen said:
Why did you share a GSI and claim it's official?
Click to expand...
Click to collapse
it is official (by dotos) by official i meant official gsi im sorry if the title was misleading ill change it