Related
I have made a kernel for stock Cyanogen OS12 with the touchscreen firmware fix and the hardboot patch (So you can use the stock rom as primary rom in multirom)
I have attached 2 file types.
The .img files to flash it with fastboot or an kernel flasher app.
The .zip files to flash it with a custom recovery
Here is a Video from savadam How to install the kernel in the recovery.
In the youtube video description you will also find howto unlock the bootloader and install a custom recovery
Update:
Kernel V2 is attached with a modified Ramdisk to fix the not working Settings-display
Update2:
The touchsreen fix is causing an 30mA higher battery drain if double tap to wake is enabled. I can life with it, but if for you the drain is to high you should disable double tap to wake in settings-display.
As soon as a new fix is finish I will provide a new kernel
Update3:
Kernel V3 with the new fix which seems to fix the touchscreen problems without causing an higher battery drain http://review.cyanogenmod.org/#/c/99607/
Update4:
Kernel V4 with fixed Sunlight Enhancement
Update5:
Kernel for CM11s XNPH05Q added
Update6:
Kernel for CM11 M11 Snapshot/Nightly added
Sources: https://github.com/bauner/android_kernel_oneplus_msm8974
Anyone tried this and can confirm it is working?
Sent from my A0001 using XDA Free mobile app
nitramcek said:
Anyone tried this and can confirm it is working?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I would not post it here if it would not work...
I use this kernel since a few weeks on the stock cos12 and since friday with the touchscreen fix.
Hardboot/Multirom support is also tested and working
Kernel V2 is attached in the first post with a modified Ramdisk to fix the not working Settings-display
@bauner it works great, I thought I had no issues, now I can touch even lighter
dev_freak said:
@bauner it works great, I thought I had no issues, now I can touch even lighter
Click to expand...
Click to collapse
Since end of december
bauner said:
Since end of december
Click to expand...
Click to collapse
Nice, I love this phone and I had touch issues, which I didn't knew, now I can touch my screen very light.
confirmed that its working perfectly and my phone is flying
does it work on stock cm12s
chiujiewei said:
does it work on stock cm12s
Click to expand...
Click to collapse
It is made for the stock cyanogen os 12
i already have cm12s as my primary rom and miui6 as my scondary rom in multirom.
will flashing the boot zip for my cm12s conflict multirom?
What about the battery life? Any experience? I flashed FC which fixed the touchscreen issue, but worsened the battery life.
ovanitas said:
What about the battery life? Any experience? I flashed FC which fixed the touchscreen issue, but worsened the battery life.
Click to expand...
Click to collapse
Kernel is stock m8 as described in the topic its been compiled from latest cm stock sources so its the same as stock cm12s.
chiujiewei said:
i already have cm12s as my primary rom and miui6 as my scondary rom in multirom.
will flashing the boot zip for my cm12s conflict multirom?
Click to expand...
Click to collapse
No it will not conflict. just boot into recovery and go to install-choose the kernel and make sure that Inject MultiRom after installation is checked
bauner said:
No it will not conflict. just boot into recovery and go to install-choose the kernel and make sure that Inject MultiRom after installation is checked
Click to expand...
Click to collapse
is kernel same version as 12s?
tsimitsangaz said:
is kernel same version as 12s?
Click to expand...
Click to collapse
It is built from the latest cm12.0 sources with the stock cos12.0 YNG1TAS17L ramdisk
bauner said:
It is built from the latest cm12.0 sources with the stock cos12.0 YNG1TAS17L ramdisk
Click to expand...
Click to collapse
is it possible to compile the same kernel with the touchscreen driver and without MultiRom support?
tsimitsangaz said:
is it possible to compile the same kernel with the touchscreen driver and without MultiRom support?
Click to expand...
Click to collapse
It would be possible but it will not make any differences, because the hardboot patch does nothing if you don't have multirom installed
Video based on this Thread
For those who are interested, here some videos regarding this beautiful rom,
Thank me if i helped you.
Lmao I feel bad for bauner. So many posts asking the same thing pretty much. [emoji12] [emoji32]
Sent from my A0001 using Tapatalk
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png
Hi!
I made patches which will fix some problems in CM13 based ROMs (CM13, Resurrection Remix, AICP etc)
1. ROM which you using on your phone have this bugs?
-no working auto-rotation
-sensors does not works as should
-phones just freezing, look like turned off
YOU NEED THIS:
1. Download my new, final patch LINK!
2. Install latest CM13 or another ROM based on CM, like RR, example link HERE
3. Install patch
4. Wipe caches
5. Reboot your phone
2. Phone just freezing? Auto-rotation, sensors etc works?
YOU NEED THIS:
1. Download this patch: LINK
2. Install latest CM13 or another ROM based on CM, like RR, example link https://www.cmxlog.com/13/g2m/
3. Install patch
4. Wipe caches
5. Reboot your phone
Thats all
*TESTED AND WORKS ON ALL NEWEST ROMS BASED ON CM13, FOR EXAMPLE Resurrection Remix
even if the newest CM13 will be fixed you can use my patches for older version of CM or if you use Resurrection Remix or similar ROM,
i'm sure it will be still usefull
THANKS
Hi Wypier.... Awesome job!!! A big THANKS for this patch. This will be a very good notice for all..
I just have a question... This method can working for cm14 alpha too??
Thanks thanks thanks. :good:
zampotonic said:
I Dev. Awesome job!!! A big THANKS for this patch. This will be a very good notice for all..
I just nave a question... This method can working for cm14 alpha too??
Thanks thanks thanks. :good:
Click to expand...
Click to collapse
Thanks
about cm14 - i dont think so.
WYPIERDAALAAC said:
Thanks
about cm14 - i dont think so.
Click to expand...
Click to collapse
thanks for your quick response. only to better understand ... you have already tried with 14 cm? otherwise I can try on my device. (If they do not use a different kernel! But sure it is different) Last question ... do you think it will be possible to adapt it to the CM14? because now you have found the cause of the problem. thanks again and sorry English
zampotonic said:
thanks for your quick response. only to better understand ... you have already tried with 14 cm? otherwise I can try on my device. (If they do not use a different kernel! But sure it is different) Last question ... do you think it will be possible to adapt it to the CM14? because now you have found the cause of the problem. thanks again and sorry English
Click to expand...
Click to collapse
I didnt tried. Kernel is for another fix. With new mobius kernel phone can wake after lock, on latest cm13 kernels phone just freezing after some time. The problem was good know, but i think no one tried or cant find right libs. I will trying to find one right because not all stuff of patch is needed i think but it works. If the libs from similar phone could works on g2m we can try it on cm14 for g2m.
There will be no problems with irrc patch?
Cherry M said:
There will be no problems with irrc patch?
Click to expand...
Click to collapse
Why would be?
of course no, no problems - but anyway you can reflash irrc patch.
NEW VERSION, THREAD UPDATED
-Cleaned package
-Fixed music player and file manager problems
-Root issues if exist also fixed
-Reduced weigh and generally keeps system libs updated for example camera or stagefright libs which was replaced needlessly before.
WORKS PERFECT BRO!!!! Thank you!!!
thank you works well....(Resurrection Remix)
Hey, new update.
I'm suprised no one seen that visualization of music does not work
nevermind
-cleaned again, less number of libs replacment
-new kernel included (you can install MobiusM kernel if you want but you dont have to now)
-music visualization fixed
I hope it's a final version (it looks it is) thanks for using, good words and testing.
NEW LINKS IN FIRST POST
ps remember, every new update you must install on fresh system.
You're great! All works well Thank you! Greetings from Poland! Good luck!
Where is the source code for your changes?
mttronc said:
Where is the source code for your changes?
Click to expand...
Click to collapse
its not built by source
WYPIERDAALAAC said:
its not built by source
Click to expand...
Click to collapse
So which ROM did you take the libs from?
mttronc said:
Where is the source code for your changes?
Click to expand...
Click to collapse
mttronc said:
So which ROM did you take the libs from?
Click to expand...
Click to collapse
from 20160820-SNAPSHOT, why you asked?
WYPIERDAALAAC said:
from 20160820-SNAPSHOT, why you asked?
Click to expand...
Click to collapse
Just out of curiosity. Hoped there might be a real fix for this issue.
mttronc said:
Just out of curiosity. Hoped there might be a real fix for this issue.
Click to expand...
Click to collapse
yes, you can be sure now all works good with patch. I think will be no official fix because they are focused on CM14 and this bugs are not made by CM team as I know.
The fix is just a rollback to the old sensors drivers.
mobiusm said:
The "fix" is just a rollback to the old sensors drivers.
Click to expand...
Click to collapse
Yes, but worse is nothing bro... At least he was kind enough and trouble to somehow solve this little problem that bothered more than one...
mobiusm said:
The "fix" is just a rollback to the old sensors drivers.
Click to expand...
Click to collapse
Now I feel that you're mean to me little bit, are you?
So why no one else did something after two months if it's just old libs with kernel?
tell you something, no difference between them so this is real "fix" of this bothersome bug/s.
Fix is fix.
I respect you and I want little respect for me
If I got you wrong - sorry.
PS: The anime character "Haruhi Suzumiya" is copyright of its owner
PS: arise fix
Open up a file manager and go to the root folder. You need to have SuperSU installed for this
You'll see a folder called su, go to /su/su.d
In this folder create a text file, label it as "permissive.sh" and put the following code in
Code:
supolicy --live "permissive *"
Then save the file and go to recovery and flash arise and Dolby Atmos addons again and then reboot
It should now work
Stop reading my bs! Here's the download link
https://srv1.botstack.host:8000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
Or
http://srv1.botstack.host:9000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
This is a project that started as a kernel for my ROM and that is what it's going to be
It can be flashed on other ROMs too and I will gladly provide support however I can't guarantee results
Do note that this is a "secure" kernel. It has many of the security patches merged from CAF and selinux enforcing is forced with no way to go to permissive
What about v4a?
Get SuperSU and input these lines in a terminal
Code:
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
allow audioserver audioserver_tmpfs:file { read write execute };"
Wait for a few seconds, swipe away v4a from the recent apps list and launch it again. It should now work
Why isn't a thermal throttling tweak included inside this kernel?
Well in my usage the kernel is so fast that thermal throttling modifications are not needed. You can apply if you want
Currently known bugs?
Nothing
OMG you're copying boeffla!
Relax. I used boeffla's anykernel base as I was in a hurry and didn't have time to make my own zip. Also, boeffla's anykernel zip is one of the best around trust me
What are the features?
Too lazy to write, check back here in a few days but there are quite a lot of features you're gonna like
I'm a nerd, I support the GPL, I'm gonna take you down because you didn't release the source code and neither did you tell me whose toolchain you used!
Bro you need to take it easy
Toolchain: https://bitbucket.org/mdalexca/aarch64-linux-android-6.x
Kernel source: https://github.com/anupritaisno1/android_kernel_oneplus_msm8994_custom
I'll try it when there is ROM with new security patch. Looking forward to it!
NeoVsk said:
I'll try it when there is ROM with new security patch. Looking forward to it!
Click to expand...
Click to collapse
I don't care about other ROMs but I'm actively adding security patches into my kernel's source so relax
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
chxei said:
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
Click to expand...
Click to collapse
Not at all
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
NeoVsk said:
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
Click to expand...
Click to collapse
Known issue
anupritaisno1 said:
Known issue
Click to expand...
Click to collapse
Could you include fast charge in following builds?
NeoVsk said:
Could you include fast charge in following builds?
Click to expand...
Click to collapse
That was my mistake. I forked fast charging from halogenos without realizing that it never worked
This is something I sadly can't fix. You'll have to wait for halogenos devs to update this
Fast charge coming in next build like....
Camera bug fixed!
I don't usually gamble but when I do I buy note7
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
xarisCY said:
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
Click to expand...
Click to collapse
If you start the camera, my kernel fails to turn it off so the camera will be unavailable for use after the first time you use it and you'll have to reboot
I'm working on fixing this bug. Why are you interested in this bug?
Sorry, my mistake. I though was something different.. Sorry
Where can i download naruhi ROM?
Kernel has been updated
All known bugs squashed!
Seems cool but an enforcing only kernel has its downside for me. I'm not sure if arise works with an enforcing kernel, would love to see a permissive version as well.
anupritaisno1 said:
Kernel has been updated
All known bugs squashed!
Click to expand...
Click to collapse
Great job! But I'm still getting only about 700mA when charging
Although the Kernel make the ROM very smooth but it's not battery friendly.
playkish said:
Although the Kernel make the ROM very smooth but it's not battery friendly.
Click to expand...
Click to collapse
On my phone I can't find a difference between my kernel and stock
Also this is a cm kernel. Expect some general battery drain
That being said, I've really worked hard on wakelocks and doze
Hi got your quote on bens kernel page @anupritaisno1, could you explain me more about this kernel. I guess it will break the focus of my camera due to some new commits, etc as bens kernel v5 had done the same to me. Also, as im using bens RR Rom, will this have any bugs or side affects with that rom (i had flashed boeffla kernel and had to face a lot of problems on his rom such as the xposed modules becoming inactive or not performing after some time, etc.) and last main thing, idle battery drain
Custom version of Blackscreen Kernel by mosimchah
Check out this thread for info:
https://forum.xda-developers.com/le-pro3/development/kernel-blackscreen-pro3-aka-zl1-x727-t3594976
Read the second and third posts on original thread for more info on the kernel settings, and features, and how to get better performance and battery life and stuff like that
Install instructions:
1. Download : Blackscreen 3 OR: Blackscreen 3.5.i (14/08/2017) OR: 3.5.i with OC (not oc'd by default)
2. Flash in twrp.
3. Reflash Root
4. Use Kernel Adiutor from playstore to change kernel settings or anything else that tickles your fancy.
AICP ROM with black screen built in:
Build 17/11/2017
https://drive.google.com/open?id=1BSB1V6f23I6xabAXXtRXqrz3ISX9pS6H
Build : 27/09/2017
https://drive.google.com/open?id=0B4k5OpXTXcS9MG5pTXlESmp4MU0
Build : 15/09/2017
https://drive.google.com/open?id=0B4k5OpXTXcS9NmZsdzE4bnI4Njg
Older:
https://drive.google.com/open?id=0B4k5OpXTXcS9aGZvLWFTQ1FKZDQ
One more kernel , onemore choose
i flashed it and camera isnt working anymore,pls fix this flashed with rr build
Can you port kernel from mi5 SlimDragons rom ?) they made good kernel )
Thanks, will try it later is it possible to port EAS?
This is the andr68rus link to various extras, included is the link to the flashable remote files
https://drive.google.com/open?id=0B-2l1xmYBAzsa0pReTA0RWZhN1E
binkaa2 said:
i flashed it and camera isnt working anymore,pls fix this flashed with rr build
Click to expand...
Click to collapse
Weird camera works fine for me but I use cm14.
Can you get a logcat?
What camera app and what happens? Just a blank screen?
infrag said:
Weird camera works fine for me but I use cm14.
Can you get a logcat?
What camera app and what happens? Just a blank screen?
Click to expand...
Click to collapse
same here , camera is not working:crying:
sky104hk said:
same here , camera is not working:crying:
Click to expand...
Click to collapse
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
infrag said:
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
Click to expand...
Click to collapse
So, will this change make stock camera fully working?
Also, regarding signal reception
at my desk the signal is weak
any idea if we could make signal reception better,
as per my experience LOS based roms or Mokee feel like does not have stock like signal reception feature,
feels bit unstable(always trying disconnecting/connecting)...
which causes the main battery drainage(dual sim, both weak signals)
infrag said:
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
Click to expand...
Click to collapse
Tks for ur hardwork, hope u can fix this on the next update bro! I really want to use the kernel, or is there any way to fix the camera problem? Also the flashlight cannot turn on, currently im usingI andr68us's DU build
Hi:
Where is the kernel?
Where can I download the kernel?
Thanks for your job
infrag said:
Thanks to @mosimchah for his hard work on Blackscreen kernel. I've just ported it to X2.
BlackScreen is meant to give you great battery life and performance (depending on how you tune it , more on that later in the second post).
Please read original thread for details.
https://forum.xda-developers.com/le-pro3/development/kernel-blackscreen-pro3-aka-zl1-x727-t3594976
Whats working:
this space intentionally left blank
Fixed Ambient Display
Added in stock LeEco charger settings to fix OTG & USB headphones.
Whats not working:
Dodgy camera as every other X2 kernel/rom atm.
I doubt IR works. Someone want to supply me a .zip with it so I can test? (I cant be bothered extracting)
Install instructions:
Download .zip
link removed while i check camera...
Flash in twrp.
Reflash Root?
Use Kernel Adiutor from playstore to change kernel settings or anything else that tickles your fancy.
Here are some of the features
f2fs not working yet as I dont care and havent turned it on.
(check out the third post on original thread for more info)
CPU:
ability to disable all input boosters
darkness governor- credit to @villarleg for porting it to our device
Lionfish governor-credit to @villarleg for porting it to our device
blue_active governor (not for the eas build)
nebula governor
wheatley governor
lionheart governor
bioshock governor
impulse governor
Alucard Hotplug driver
GPU:
Adreno boost
Adreno idler
I/O:
Improved deadline
improved cfq
bfq
sio
fiops
tripndroid
sioplus
zen
Virtual memory:
various optimizations
entropy:
some optimizations
tcp-algorithms:
bic
westwood
htcp
hstcp
vegas
scalable
lp
veno
yeah
illinois
Misc:
fsync toggle
Many more optimizations
Several wakelocks have been blocked
Added the ability to tweak the thermal throttle settings (be very careful with this)
Read the second and third posts on original thread for more info on the kernel settings, and features, and how to get better performance and battery life and stuff like that
Thanks to:
etc
Click to expand...
Click to collapse
Thanks.
Does this kernel has undervolting capability? Le max 2 has very weak battery.
infrag said:
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Click to expand...
Click to collapse
Nice work, thanks I will use LOS naming system next build. I will repack kernel with my ramdisk and put link for < 05/09 RR-N.
PS. Where I can download kernel?
Hope this kernel gets fixed soon, you're doing great work on the Le Max 2, thanks for your contributions!
Also hopefully you and @andr68rus find the naming fix and that this kernel gets integrated into RR, AOKP, DU and the rest of the Nougat roms, I can see it being a great SoT fix for Nougat ROMs.
( for me this kernel is hopeless ((( my problem with camera on nougat roms seems unfixable for now (((
andr68rus said:
Nice work, thanks I will use LOS naming system next build. I will repack kernel with my ramdisk and put link for < 05/09 RR-N.
PS. Where I can download kernel?
Click to expand...
Click to collapse
Thanks.
I pulled the link as it didnt work on Cr3pts Unoffical LAOS cm14.1 either.
However it turns out he hasnt updated his libc shim name either so I've re-added the download link.
Wheres your new link so I can test on RR?
xuser_ said:
So, will this change make stock camera fully working?
Also, regarding signal reception
at my desk the signal is weak
any idea if we could make signal reception better,
as per my experience LOS based roms or Mokee feel like does not have stock like signal reception feature,
feels bit unstable(always trying disconnecting/connecting)...
which causes the main battery drainage(dual sim, both weak signals)
Click to expand...
Click to collapse
No it wont fix stock camera. I didnt imply that so...
As far as signal reception goes I dont have issues with reception.
I do see some stuff in the logs about disconnecting reconnecting and i'll probably have a look at it one of these days. Not sure IF I can do anything but I'll try.
Gnomchar said:
( for me this kernel is hopeless ((( my problem with camera on nougat roms seems unfixable for now (((
Click to expand...
Click to collapse
Whats your problem on Nougat roms?
I think I read something about focusing or something?
If so I have an idea but you will need to pull some logs while camera is semi working for you.
adb logcat > logcat.txt
adb shell dmesg > dmesg.txt
sky104hk said:
Tks for ur hardwork, hope u can fix this on the next update bro! I really want to use the kernel, or is there any way to fix the camera problem? Also the flashlight cannot turn on, currently im usingI andr68us's DU build
Click to expand...
Click to collapse
Flash andr68us's 'fixed' build. (just renamed a file basically)
His future builds should work with this.