༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Welcome to yet another stock kernel for the Z3 Compact!
Kernel12s
It's different this time because there's an S. Trust me.
AMAZING FEATURES:
They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:
Additional CPU and GPU steps
Faux123's Intelli_plug and Intelli_thermal
adreno_idler
Memory fixes up the arse
Countless battery life and overall performance optimizations
Obviously there's more so go ahead and check my Github!
DOWNLOADS:
Always read the changelog before downloading and flashing!
Changelog: http://j.mp/changelog12_stock (includes concept and stock branches of this project)
Downloads: http://bit.ly/kernel12s
Quick link to concept downloads: http://bit.ly/kernel12c
Generously hosted by the good guys on Androidfilehost.com
HOW-TO:
* Flash using recovery
* If you're using systemless root, you need to re-flash the supersu zip after updating the boot.img
SERIOUS DISCLAIMER!
Code:
I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace
I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974_stock
༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ
XDA:DevDB Information
kernel12s, Kernel for the Sony Xperia Z3 Compact
Contributors
someone755
Source Code: https://github.com/someone755/android_kernel_sony_msm8974_stock
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-09-06
Created 2016-07-25
Last Updated 2016-09-06
A quick FAQ that you'd better read before posting.
1. So what's the naming convention this time?
A: Cutting the bullsh*t this time 'round, all builds are permissive (unless demand for enforcing ones is raised). The number after the "s" tells you which build number this is. The number after the dash tells you what stock version the kernel was designed for (unless otherwise specified in the changelog).
2. How do I flash this?
A: Flash through recovery. If you're using systemless SuperSU and want to update your boot.img, just flash the boot.img, then flash your SuperSU zip over it. Works like a charm.
3. My bootloader is locked, HALP! OR I'm on AOSP/CM7/the Moon.
A: Then you don't get to install this kernel. Pretty simple but still, tough luck.
4.. What app do you recommend for dealing with CPU settings?
A: Kernel Auditor works for me. Go around the internet, try different apps and see what works for you, then keep it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe! OR My phone exploded, HALP!
A: Go away. I do not respond to bug reports without a proper description and log.
6. I want to support you and your work!
A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate! The more people we get on this bandwagon, the faster I'm forced to work.
7. OP is arrogant, I'm gonna call the Internet Police? OR Why are you such a derp and asshole
A: Indeed I am. Deal with it.
8. Where may I find the discussion thread?
A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!
Special shoutouts to (in no particular order, all help is equal help):
AndroPlus, funiewski, Myself5, sm4tik, nelvinchi, franciscofranco, Freexperia and jerpelea, faux123, Google, Sony and HTC, all Nozomi developers, letama, oshmoun, olivieer, and that other guy (his name is tomascus by the way, he's a cool dude).
reserved?
Huge shoutout to my boys @oshmoun and @Myself5 for the help, drop them a thanks if you can be bothered!
i thought i had a reason for a third OP but i guess not, anyone have ideas?
Is it compatible with 23.5.A.1.238?
@someone755:
This was unexpected!
Big thanks to stay with xda communitiy. Thought we lost another dev because of "some" discussions (weeks/month ago)
And of course big thanks for this release...
alenbernardis said:
Is it compatible with 23.5.A.1.238?
Click to expand...
Click to collapse
According to the release notes I believe no, but you could always give it a try:
More testing, this time on Marshmallow. Clean, based off .575, no bugs found as of GMT 00:56, 25 July 2016. Only tested with .575, compatibility with .570 questionable. Further testing and development required.
Click to expand...
Click to collapse
Thanks someone755, I've installed it and so far so good.
I use this kernel with SLIMM v2.2 and is awesome thanks so much!
alenbernardis said:
Is it compatible with 23.5.A.1.238?
Click to expand...
Click to collapse
Oh come on dude please you're the first post.
Granted it's not explicitly stated but if you'd read the FAQ and changelog you'd know that 1) s3-575 is based around .575 and that 2) it's only been tested and reported working with .575.
Also to note is that .575 is the latest tarball available for shinano. I don't know if .238 has a different kernel or ramdisk, and I can't check, so I can't vouch for anything. You're free to test and report back so others don't have to worry though.
fluffi444 said:
@someone755:
This was unexpected!
Big thanks to stay with xda communitiy. Though we lost another dev because of "some" discussions (weeks/month ago)
And of course big thanks for this release...
Click to expand...
Click to collapse
Unexpected to say the least lol. I can't blame anyone but xda's collective hivemind for what has happened and is happening, but I needed this kernel for myself anyways, and honestly any feedback I can get is useful. You're not losing this dev for at least 4 more months!
Also thanks to everyone else for their contributions, if you don't get any errors on .238 (or Slimm 2.2 or whatever) I'll mark it as compatible. Cheers!
Has Sony released sources for the kernel used in Concept?
I'd love to have a few other governor options if this would work on MM Concept.
undervolting?
h4waii said:
Has Sony released sources for the kernel used in Concept?
I'd love to have a few other governor options if this would work on MM Concept.
Click to expand...
Click to collapse
Sadly, no. I don't know whether it works for that as well, and I still think they're breaking the GPL by not releasing them.
Does loading them as kernel modules work? If so you could just try that (though you'll need to compile those modules, if they'll even work with a different kernel).
aceoff27 said:
undervolting?
Click to expand...
Click to collapse
Well it's there, yeah. What you intend to do with it is all up to you though, I could never get anything stable other than the stock voltage table lol.
wow, great work man, I just installed and works perfect with SliMM 2.3. Looking forward for the next updates.
Keep up the great work
someone755 said:
Sadly, no. I don't know whether it works for that as well, and I still think they're breaking the GPL by not releasing them.
Click to expand...
Click to collapse
@someone755 I've asked them about sources on G+, here is my question and the answer(from today):
Q:
"I've asked about it earlier without any answer, so once more.
I've used Sony since Xperia Ray and the concept rom is the best one of any kind (official or custom like CM, omni, AOKP, you name it), but there is a really big flaw. Kernel sources are not published which stops development.As long as I understand the GPL Sony is obligated to publish them, so why are they not?"
A:
"Henrik Baard
+2
+ xxxxx, we are required by licence to upon request provide source code. Usually we put source in a location available so users can download GPL source.
We will look into providing this asap."
Now it's a possibility it will happen......
funiewski said:
@someone755 I've asked them about sources on G+, here is my question and the answer(from today):
Q:
"I've asked about it earlier without any answer, so once more.
I've used Sony since Xperia Ray and the concept rom is the best one of any kind (official or custom like CM, omni, AOKP, you name it), but there is a really big flaw. Kernel sources are not published which stops development.As long as I understand the GPL Sony is obligated to publish them, so why are they not?"
A:
"Henrik Baard
+2
+ xxxxx, we are required by licence to upon request provide source code. Usually we put source in a location available so users can download GPL source.
We will look into providing this asap."
Now it's a possibility it will happen......
Click to expand...
Click to collapse
**** this is some potentially good news. Just hope this doesn't turn out to be the Half-Life 3/Rocket League Linux client/Amiga Walker of kernel sources.
EDIT: Goddammit xda stop censoring my excrement.
Underclock values for psv8
For those who want to do undervolt I use these values are quite stable and save battery
Only for PSV8 bin MSM8974AC
268 Mhz - 650 mv
300 Mhz - 655 mv
422 Mhz - 670 mv
652 Mhz - 675 mv
729 Mhz - 695 mv
883 Mhz - 705 mv
960 Mhz - 715 mv
1036 Mhz - 745 mv
1190 Mhz - 765 mv
1267 Mhz - 775 mv
1497 Mhz - 805 mv
1574 Mhz - 815 mv
1728 Mhz - 840 mv
1958 Mhz - 885 mv
2265 Mhz - 945 mv
2419 Mhz - 975 mv
2457 Mhz - 980 mv
frixed said:
*snip*
Click to expand...
Click to collapse
Please don't before you get somebody's phone fried.
This phone comes in a couple different variations in terms of binning. Use these values on a chip from a different bin and you'll either be unable to boot (not enough power) or fry it (too much power). Not to mention the OnePlus One is a different device in the sense of thermal dissipation -- its larger surface area allows it to conduct heat away from the chip and phone faster than our Z3 Compact can.
That said, I would like to ask you to either remove this or to specify your bin and chip version, and wrap a
tag around the table.
someone755 said:
Please don't before you get somebody's phone fried.
This phone comes in a couple different variations in terms of binning. Use these values on a chip from a different bin and you'll either be unable to boot (not enough power) or fry it (too much power). Not to mention the OnePlus One is a different device in the sense of thermal dissipation -- its larger surface area allows it to conduct heat away from the chip and phone faster than our Z3 Compact can.
That said, I would like to ask you to either remove this or to specify your bin and chip version, and wrap a
tag around the table.
Click to expand...
Click to collapse
Sorry there edit specify what is my version PSV bin
I have saved drm keys, locked bootloader and latest slimm , how can i use with this kernel my keys? Or isnt necessary, becouse drm fix included to the kernel?
fromhungarytolnacounty said:
I have saved drm keys, locked bootloader and latest slimm , how can i use with this kernel my keys? Or isnt necessary, becouse drm fix included to the kernel?
Click to expand...
Click to collapse
If you apply the DRM keys you'll also relock the bootloader. So there's that.
If you want the DRM workaround hack or whatever you'll just have to flash it yourself.
someone755 said:
If you apply the DRM keys you'll also relock the bootloader. So there's that.
If you want the DRM workaround hack or whatever you'll just have to flash it yourself.
Click to expand...
Click to collapse
Ok. Thank you. After the bootloader unlock, what i have to do, for my drm keys working with this kernel?
Related
This kernel is distributed with several overclock modules.
The modules doesn't have GPL in their licenses. The sources for modules are private.
*** The frequencies below are not real. Sorry for that. I know little about detailed architecture for U8500 CPU... ***
available frequencies:
50MHz,100MHz,500MHz,1000MHz,2000MHz(can be set by modules)
Kernel Link: http://pan.baidu.com/s/1gdmXlyN
Module for overclocking to 1.2 GHz(Stable): http://pan.baidu.com/s/1pJz8i6Z
Module for overclocking to 1.5 GHz(Stable): http://pan.baidu.com/s/1jG3giWI
Module for overclocking to 2.0 GHz(Still testing): http://pan.baidu.com/s/1bnfDNBp
If you like the kernel any donations are welcome: alipay account: 15190852698 I will build a kernel for you if you donate me
If you want to use this in your ROM:
1. PM me first
2. Don't touch the kernel(e.g. extract or modify zImage or ramdisk). You will easily get problems e.g. not booting and wifi not working
3. Don't put anything that you can get money from it in your ROM.
Recovery:
Camera button only after vibrate will bring you into TWRP
Power button only after vibrate will enter CWM
If you press both keys after vibrate you will enter kexec bootmenu.
***Read this before you flash the kernel!***
The kernel only supports /data and /cache of f2fs filesystem. You will get a bootloop if you use ext4 for the two partitions. But use ext4 for /system.
mkfs.f2fs_arm link: http://pan.baidu.com/share/link?shareid=855746158&uk=3137347581
Don't ask me for source. It's from internet.
******
Kernel source: https://github.com/FandroidRelease/android_kernel_sony_u8500/tree/overclock
XDA:DevDB Information
Fandroid Kitkat Kernel, Kernel for the Sony Xperia P
Contributors
zhy0919, XperiaSTE, Sony, CM11
Kernel Special Features: based on XperiaSTE's overclock source, with overclocking modules
Version Information
Status: Beta
Created 2014-08-31
Last Updated 2014-08-31
deleted
big-A said:
deleted
Click to expand...
Click to collapse
What do you mean??
Bootloop
I installed your kernel with cm 11 M9 and slimkat 7.6 and everytime i get a bootloop
How to install those modules? How to access recovery, power button?
This kernel looks promising, but could you please provide more information such as the recovery that comes with it, if theres one; or the features besides having the overclock modules that it has etc. Thank you. Good job overall.
big-A said:
I installed your kernel with cm 11 M9 and slimkat 7.6 and everytime i get a bootloop
Click to expand...
Click to collapse
Sorry I didn't mentioned some important information in my post.
Please format /data and /cache to f2fs if you want to use the kernel.
And also, if you flashed another ROM, you will need to mkfs.f2fs again.
mkfs.f2fs_arm link: http://pan.baidu.com/share/link?shareid=855746158&uk=3137347581
macabrocabral said:
How to install those modules? How to access recovery, power button?
Click to expand...
Click to collapse
Post updated
ArtemisRider said:
This kernel looks promising, but could you please provide more information such as the recovery that comes with it, if theres one; or the features besides having the overclock modules that it has etc. Thank you. Good job overall.
Click to expand...
Click to collapse
Thanks. Post updated.
Novathor chips can go up to 1,3ghz. 1.2 ghz is a safest option. Overclocking that much a novathor SoC without changing voltages will only consume severe power leading to overheat. Due too the aluminium design of xperia p you will not notice so much heat but when graphics artifacts start to occur then i hope you have the budget needed to buy several phones to payout the users.
Cheers
nicolassp said:
Novathor chips can go up to 1,3ghz. 1.2 ghz is a safest option. Overclocking that much a novathor SoC without changing voltages will only consume severe power leading to overheat. Due too the aluminium design of xperia p you will not notice so much heat but when graphics artifacts start to occur then i hope you have the budget needed to buy several phones to payout the users.
Cheers
Click to expand...
Click to collapse
Even i have read that 1.2ghz is the safest option for novathor overclocking. thnx for confirming.
Dammit!
I thought that fake overclocks and/or underclocks will die with the real overclock, but as I can sadly see this is not true. First of all, the commit which increases frequency in the repo of the GitHub link provided does NOT change the needed registers to increase frequency. Secondly, if the work of this thread would work at 50Hz the phone would die and at 2GHz everything will crash automatically, this is just placebo effect, a nonsense placebo effect.
Garcia98 said:
Dammit!
I thought that fake overclocks and/or underclocks will die with the real overclock, but as I can sadly see this is not true. First of all, the commit which increases frequency in the repo of the GitHub link provided does NOT change the needed registers to increase frequency. Secondly, if the work of this thread would work at 50Hz the phone would die and at 2GHz everything will crash automatically, this is just placebo effect, a nonsense placebo effect.
Click to expand...
Click to collapse
Thanks and sorry. But can you tell me why the total current of the phone seems to be much higher when at the highest frequency?
zhy0919 said:
Thanks and sorry. But can you tell me why the total current of the phone seems to be much higher when at the highest frequency?
Click to expand...
Click to collapse
What do you mean with "current of the phone"?
Garcia98 said:
What do you mean with "current of the phone"?
Click to expand...
Click to collapse
current_now in ab8500_fg
zhy0919 said:
current_now in ab8500_fg
Click to expand...
Click to collapse
I don't get you, do you mean charge_now?
Garcia98 said:
I don't get you, do you mean charge_now?
Click to expand...
Click to collapse
/sys/class/power_supply/ab8500_fg/current_now
zhy0919 said:
/sys/class/power_supply/ab8500_fg/current_now
Click to expand...
Click to collapse
For me that value is very similar even with real overclock, and it changes a lot from second to second. To check if overclock works the best idea is to make a benchmark and check ARM PLL registers.
I agree with Garcia98. The overclock cannot be done on this motherboard/CPU and the 2GHz overclock will fry the components in no time.
Garcia98 said:
For me that value is very similar even with real overclock, and it changes a lot from second to second. To check if overclock works the best idea is to make a benchmark and check ARM PLL registers.
Click to expand...
Click to collapse
Really thanks... By the way where can I find documentations about novathor CPUs? And how to modify u8500 cpu's pll register(what value can be set and why)? Thanks for your answer!!
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
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
Compatibility:
LineageOS 14.1 based roms; reported working with most 7.1.2 ROMs.
Download:
See attachments.
How to install:
Flash the zip.
If you come from another kernel, dirty flash your rom or LineageOS's boot.img before flashing this one (that also includes ROMs that come with a different kernel built-in).
Features:
Flash and forget
All cores are unlocked and unshackled
No hotplug (see: https://forum.xda-developers.com/showpost.php?p=72198795&postcount=140)
Spectrum support (Info: https://forum.xda-developers.com/showpost.php?p=72804608&postcount=192)
Reduced idle power consumption (don't complain about 3rd party wakelocks)
some wakelocks are blocked by default (thanks to @franciscofranco)
Credits:
@franciscofranco's zips.
Powered by: AnyKernel2 - @osm0sis
Extra thanks:
@karthick and @chaubeyprateek - Hyper Kernel
Interactive how-to: [GUIDE] [AKT] Advanced Kernel Tweaks by @Asiier, @patalao, @Mostafa Wael and @Senthil360
I am trying this out.Will you add d2w?
Working here on a6020a40 sd415 indian varient.
bodafranus said:
Compatibility:
Android Nougat 7.1.1 Lineage OS 14.1 based roms.
A6020 (tested only on l36 variant)
Download:
http://www106.zippyshare.com/v/IcjLb4RP/file.html
(will move to AFH shortly)
How to install:
Flash the zip.
Features:
Flash and forget
All cores are unlocked and unshackled
Reduced idle power consumption (don't complain about 3rd party wakelocks)
Wakelocks blocked by default (thanks to @franciscofranco)
Changelog:
https://gist.github.com/LegendMaster/767d12c93c5fc53dc5f214b4e10fce29
Source:
https://github.com/LegendMaster/android_kernel_lenovo_msm8916/tree/experimental
Known bugs:
Minimum frequencies on big cluster reverting to 960MHz. CPU Freq driver doesn't seem to remember policy->user_policy.min when waking up from suspended state.
You tell me. :good:
Credits:
init.rc all from @franciscofranco zips.
Powered by: AnyKernel2 - @osm0sis
HMP Scheduler and insights: [GUIDE] [AKT] Advanced Kernel Tweaks
Extra thanks:
@Dreamstar - Vegito Kernel
@chaubeyprateek - Hyper Kernel
Click to expand...
Click to collapse
Finally someone developing a different kernel! Very much appreciated!
Take a look at ExtremeKernel, it adds some bits missing from stock Kernel that would be nice to see here (Extreme seems to be discontinued).
Gonna follow this thread and try it!
@bodafranus thanks for a great kernel! Working here o a40 sd 415 indian variant. Here one bug though.. touch response is not working on ambient display.. it has been fixed in latest commits by Karthik. Kindly include these fixes in next version. Thanks!
Waiting for Alpha1 to try it! When will it be available?
Changelog seems to be promising!!
New version:
alpha1
1. changed governor and HMP scheduler values.
2. added bw_hwmon shenanigans to ramdisk (responsible for controlling some bus frequencies)
3. updated some drivers
4. merge 'caf/LA.BR.1.2.9_rb1.12' (kang from: karthick111)
If you experience any problems, send logs. (some can be found at: /sys/fs/pstore)
tanx said:
I am trying this out.Will you add d2w?
Click to expand...
Click to collapse
Not my priority, still have tons of patches to apply.
You can use Gravity Screen with everything but "Turn Screen ON by Proximity" disabled.
dr.bathman said:
Working here on a6020a40 sd415 indian varient.
Click to expand...
Click to collapse
Thanks.
IagoJevaux said:
Finally someone developing a different kernel! Very much appreciated!
Take a look at ExtremeKernel, it adds some bits missing from stock Kernel that would be nice to see here (Extreme seems to be discontinued).
Gonna follow this thread and try it!
Click to expand...
Click to collapse
You're welcome.
dr.bathman said:
@bodafranus thanks for a great kernel! Working here o a40 sd 415 indian variant. Here one bug though.. touch response is not working on ambient display.. it has been fixed in latest commits by Karthik. Kindly include these fixes in next version. Thanks!
Click to expand...
Click to collapse
I haven't seen anything in his commits related to this. Could you be more specific?
IagoJevaux said:
Waiting for Alpha1 to try it! When will it be available?
Changelog seems to be promising!!
Click to expand...
Click to collapse
Available now.
Is it working on a46?
Sent from my Lenovo Vibe K5 Plus using XDA Labs
AmithNRG said:
Is it working on a46?
Sent from my Lenovo Vibe K5 Plus using XDA Labs
Click to expand...
Click to collapse
You'll have to test it yourself or wait for somebody else's feedback.
The OP only has the l36 variant.
It's working on a46. I have it and working. Thanks for the work.
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
dr.bathman said:
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
Click to expand...
Click to collapse
@bodafranus
List of bugs:
timer_rate fixed on Little cluster, unable to change it.
minimum frequency on big cluster reverting to default after CPU wakes from suspended state.
AmithNRG said:
Is it working on a46?
Click to expand...
Click to collapse
Should work.
tanx said:
It's working on a46. I have it and working. Thanks for the work.
Click to expand...
Click to collapse
Thanks for letting me know
dr.bathman said:
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
Click to expand...
Click to collapse
That's strange, can you try flashing over latest official Lineage, after a Factory Reset wipe?
Try to grab a logcat while in bootloop, if it persists (see: https://forum.xda-developers.com/showthread.php?t=2274119)
I will check Ambient Display after I fix some issues.
bodafranus said:
List of bugs:
timer_rate fixed at 60000 on Little cluster, unable to change it.
minimum frequency on big cluster reverting to default after CPU wakes from suspended state.
Should work.
Thanks for letting me know
That's strange, can you try flashing over latest official Lineage, after a Factory Reset wipe?
Try to grab a logcat while in bootloop, if it persists (see: https://forum.xda-developers.com/showthread.php?t=2274119)
I will check Ambient Display after I fix some issues.
Click to expand...
Click to collapse
Ok.. I tried it on official lineage 10/4 build with fresh flash and the lm kernel alpha 1 is working without any problem like bootloop/stuck to bootlogo.
i am not using this kernel even not other, but having big trouble with lineage OS, basically cpu core bug i can say and i asked on its respective thread, page 72 and 73, dev and other users helped me but partially solved you can refer if you want to, but i will explain anyway here shortly,
i am using 20170410 built, and kernel adiutor, selinux permissive, i tried switching all possible options like core control, clock speed, governor, other thing, the only thing bug me is governor, like interactive and ondemand, max 1497mhz and min 200mhz i set, but it always on 1497mhz when even idle little process and core directly goes offline when no use, and never downclock, i also found too much over heating when any games or heavy task.
(**this is not bug of this kernel,
and this exactly same paragraph i'll be posting on lineage os thread, so if you like to suggest me about this bug you can in that thread )
so back to main track, will this kernel solve this problem?
also i see alpha 2 change log but no built.
dr.bathman said:
Ok.. I tried it on official lineage 10/4 build with fresh flash and the lm kernel alpha 1 is working without any problem like bootloop/stuck to bootlogo.
Click to expand...
Click to collapse
Great.
bik95122 said:
i am not using this kernel even not other, but having big trouble with lineage OS, basically cpu core bug i can say and i asked on its respective thread, page 72 and 73, dev and other users helped me but partially solved you can refer if you want to, but i will explain anyway here shortly,
i am using 20170410 built, and kernel adiutor, selinux permissive, i tried switching all possible options like core control, clock speed, governor, other thing, the only thing bug me is governor, like interactive and ondemand, max 1497mhz and min 200mhz i set, but it always on 1497mhz when even idle little process and core directly goes offline when no use, and never downclock, i also found too much over heating when any games or heavy task.
(**this is not bug of this kernel,
and this exactly same paragraph i'll be posting on lineage os thread, so if you like to suggest me about this bug you can in that thread )
Click to expand...
Click to collapse
Wrong thread. If you demand CPU power obviously it'll deliver, so expect it with heavy tasks. Overheat is a problem inherently of our device and its chassis, after all metals are good heat conductors...
Check your target_loads and background processes if you encounter this problem while idle.
bik95122 said:
so back to main track, will this kernel solve this problem?
Click to expand...
Click to collapse
It may, because tunables are already set up properly by default.
bik95122 said:
also i see alpha 2 change log but no built.
Click to expand...
Click to collapse
Yeah, no point in releasing a build with minimal changes. Next one will come up shortly with some bug fixes.
bodafranus said:
Wrong thread. If you demand CPU power obviously it'll deliver, so expect it with heavy tasks. Overheat is a problem inherently of our device and its chassis, after all metals are good heat conductors...
Check your target_loads and background processes if you encounter this problem while idle.
It may, because tunables are already set up properly by default.
Yeah, no point in releasing a build with minimal changes. Next one will come up shortly with some bug fixes.
Click to expand...
Click to collapse
really appreciate , i am gonna try this right now and sure will giving you some feedback, thanks.
quick feed, changes i see. A46 device
- little cores working very good as expected now, clock speed interactive as on demanded, which i prefer.
-but big core just stay at 1497 mhz constant (which i know its not problem on this kernel, it from lineageos rom that why i tried using this kernel to see fix) but i know someday may be solved by this kernel,
-one more thing i notice on small core, as its clock speed is as on demanded, but all 4 core speed same, instead of individual.
-now no core get automatically shutdown, even if no demand of an individual core. which is good as well as bad (i am kind of confused for this)
that all, this changes i looked as after flash just now.
bik95122 said:
-but big core just stay at 1497 mhz constant (which i know its not problem on this kernel, it from lineageos rom that why i tried using this kernel to see fix) but i know someday may be solved by this kernel,
Click to expand...
Click to collapse
this problem solved, this above mentioned problem is related to problem below quoted one
bik95122 said:
-one more thing i notice on small core, as its clock speed is as on demanded, but all 4 core speed same, instead of individual..
Click to expand...
Click to collapse
actually, its kernel adiutor doing, when i used cpuz, it showed all cpu at 200mhz which i set, and kernel adiutor need 2 full speed core to work smoothly, so kernel throttles to max clock speed of all 4 big core, instead of 2,
so far i am happy, thnks :good:
bik95122 said:
this problem solved, this above mentioned problem is related to problem below quoted one
actually, its kernel adiutor doing, when i used cpuz, it showed all cpu at 200mhz which i set, and kernel adiutor need 2 full speed core to work smoothly, so kernel throttles to max clock speed of all 4 big core, instead of 2,
so far i am happy, thnks :good:
Click to expand...
Click to collapse
How is the battery usage in this kernel
There's a new kernel working on our P10, it was made for Honor 9 and updated to make it work on P10.
Here is the link to the thread Proto8 Kernel
Everything is working, wifi, bluetooth, hotspot, just try it yourself! The kernel is stable and very fast.
FEATURES
- Compiled with Linaro AArch64 GCC 4.9 2017.01 (ARMv8,A53 Optimized)
- UV (UnderVolt) on both CPU Clusters and GPU for better efficiency (All thanks to @nutcasev1.5)
- Energy Aware Scheduling (EAS) with "Sched" CPU Governor
- Kirin Hotplug Flow
- Aggressive GPU Suspend on Low Frequencies
- Swap disabled
- Reduced Kernel Wakelocks
- Advanced TCP Algorithms with "Westwood" Default
- Reactivation of the "setenforce" command
- Wireguard VPN Support
All the credits to @JBolho and @nutcasev1.5 for their work (hit the Thanks button :good
Download link: [url]https://www.androidfilehost.com/?fid=11050483647474829090[/URL]
Latest version: Version 2.0R - 06.29.18
Major Milestone Update
- Upstreamed to 4.4.73
- New Optimal Timer Frequency - 156HZ Set as Default
- Go Tickless - Enable Full Dynticks System
- Power Efficient Workqueues can now be toggled
- Revert CPU DDR Link Enabling and other HiSi CPU Functions
- Keep Kirin Specific SMP Flow but move to ARM big.LITTLE CPUFreq Driver
- Reduce Kernel Max Wakelocks down by 90% relative to Stock
- Minor RAM and DevFreq Tweaks
- GPU Scene_Aware Tuned for Power Efficiency
- Minor Log Spam on CPU's Silenced
- Reduce Timeout to Stop Processes and Enter Sleep
- Optimized Sound Output Gains and Eliminate Rates below 16Khz
- Implement UKSM 0.1.2.6
- Upgrade SchedTune Boost to v3
- Major Update to Spectrum Profiles to accomodate new features as well
- Update Wireguard to 0.0.20180620
sfoot13 said:
There's a new kernel working on our P10, it was made for Honor 9, here's the link: https://forum.xda-developers.com/honor-9/development/kernel-proto8-kernel-t3780551
I installed it yesterday and the only thing that is not working is the wifi and bluetooth.
Click to expand...
Click to collapse
Hey man, glad you liked it, but at least you could mention the Developers and at least give me a heads-up like "Hey, can i share the thread on the P10 forums?"
Kind of taken by surprise here
Thanks for the support.
JBolho said:
Hey man, glad you liked it, but at least you could mention the Developers and at least give me a heads-up like "Hey, can i share the thread on the P10 forums?"
Kind of taken by surprise here
Thanks for the support.
Click to expand...
Click to collapse
I'm sorry bro., I was going to add the credits later, but it was a mistake not to ask you before, sorry. (I'll edit the thread now)
Your kernel is very fast :good:
sfoot13 said:
I'm sorry bro., I was going to add the credits later, but it was a mistake not to ask you before, sorry. (I'll edit the thread now)
Your kernel is very fast :good:
Click to expand...
Click to collapse
Thank you. And it's not just me, @nutcasev1.5 is also Developer of the kernel.
kernel without wifi and bluetooth is kind of useless.
DallasCZ said:
kernel without wifi and bluetooth is kind of useless.
Click to expand...
Click to collapse
Not for me.
JBolho said:
Thank you. And it's not just me, @nutcasev1.5 is also Developer of the kernel.
Click to expand...
Click to collapse
@JBolho Done, I added the credits bro.
I don't know if is possible to fix the wifi and bluetooth for our device, I know that it was made for Honor 9, so if it is not possible, don't worry bro, and thank you so much
sfoot13 said:
@JBolho Done, I added the credits bro.
I don't know if is possible to fix the wifi and bluetooth for our device, I know that it was made for Honor 9, so if it is not possible, don't worry bro, and thank you so much
Click to expand...
Click to collapse
It's possible that it's just a matter of drivers, I'll look into it when I have the chance, but no ETA of course.
JBolho said:
It's possible that it's just a matter of drivers, I'll look into it when I have the chance, but no ETA of course.
Click to expand...
Click to collapse
Yes! :laugh: :fingers-crossed:
Thank you so much, take your time, I never ask for ETA.
One question: You'll need the stock drivers? Because I was searching and their are placed into Vendor/lib/modules, so what if I backup my stock drivers, flash your kernel and restore my stock drivers... I'll see if it works
Update: It didn't worked
sfoot13 said:
Yes! :laugh: :fingers-crossed:
Thank you so much, take your time, I never ask for ETA.
One question: You'll need the stock drivers? Because I was searching and their are placed into Vendor/lib/modules, so what if I backup my stock drivers, flash your kernel and restore my stock drivers... I'll see if it works
Update: It didn't worked
Click to expand...
Click to collapse
The proper stuff needs to be compiled in the kernel, don't brick your device in anticipation
JBolho said:
The proper stuff needs to be compiled in the kernel, don't brick your device in anticipation
Click to expand...
Click to collapse
While I'm waiting, I'll keep using your kernel
Thank you so much for the support. :laugh:
sfoot13 said:
While I'm waiting, I'll keep using your kernel
Thank you so much for the support. :laugh:
Click to expand...
Click to collapse
You have a PM, check it out.
JBolho said:
You have a PM, check it out.
Click to expand...
Click to collapse
Thank you so much, I'll check it
As confirmed now by @sfoot13 this kernel is now fully compatible with the P10. Separate download link added on thread's OP because both devices require separate compiles.
Remeber this was originally designed for the Honor 9 but from now on it should continue to be 100% compatible with the P10 as all incompatibilities have been apparently solved.
All the thanks to @JBolho :good: he made it possible
Thank you all for giving us a Kernel
I hope you don't mind the question: So it uses another energy management, does that mean there is no 'scrollable widgets freeze' bug?
Yes I could unlock and try myself but it's my daily phone at the moment :-|
Swaddy said:
Thank you all for giving us a Kernel
I hope you don't mind the question: So it uses another energy management, does that mean there is no 'scrollable widgets freeze' bug?
Yes I could unlock and try myself but it's my daily phone at the moment :-|
Click to expand...
Click to collapse
If there's such a bug, I've never experienced it, and it's more likely a rom thing, not the kernel fault...
My device is the only one I have and I need it everyday, so... This is not some "alpha ultra experimental thing" that may or may not explode on your pocket, so don't worry
Unlocking the bootloader does force a factory reset though. It's a pain, i know...
I also never had problem with widgets on this kernel and also on stock kernel.
To the actual users: how this is compared with hyperkernel from p10 plus?
Kernel has been updated to v1.2R, new and tuned I/O and updated CPU drivers and Sched Gov.