Related
Hello
I was wondering if there are any Nexus 4 ROMs using JustArchi's optimizations (link). I did my best to compile OmniROM with these fixes, but I am not very experienced with Android development.
+1 to this post
Looks like our devices are too fast to use these "insignificant" compiler optimizations
I'll give my 5 cents these days to try compiling it..
Cheers
+1 for this thread.. I asked just the same thing in the general Q&A thread and nobody answered.. I'd like to see CM, ParanoidAndroid...etc.. built with ArchiDroids optimizations..
Like to see that too!
I've been searching for a rom with f2fs support + JustArchi's optimizations. Can be possible?
I created a topic earlier here
opssemnik said:
i can tell from personal experiences, its mostly placebo, tried archi´s rom on my gs3, and aside from the fact that the google camera dosent crash after first shot(witch occors on alot of roms ,even official cm, again on my s3), the rom is same speed, if not less than official cm. (on my s3 i9300)
Click to expand...
Click to collapse
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
joefso said:
I created a topic earlier here
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
Click to expand...
Click to collapse
yeah i saw those,luck for them, thats why best rom threads are not allowed on xda, people get different results on their devices ,i plan to compile aosp with those just to test on the n4, but i doubt i will :/
No one is going to try this anytime soon.
The code is no where near perfect and it sets up an environment where there is a lot of room for errors which will result in VERY bugy, glitchy, crashing Roms.
The code is really sloppy and so far only JustArchi is the only one that has successfully used this in a ROM with out error.
There is still a lot of going back and forth in whether this really works since android isn't 90% thumb
All this is good for is benchmark scores. Just like F2Fs its all placebo in real world performance.
With a quadcore 2 gig phone... You're not missing much.
Legecy devices will benefit in the least from this.
Sent from my SM-T217S using Tapatalk
First build is ready!
It is mako-userdebug.
I used Linaro toolchain(JustArchi's link) and JustArchi "JustArchi's ArchiDroid Optimizations V3" - https://github.com/JustArchi/android_build/commit/d8cc50d2472e497b431b5652516c9248ad7f3947
It is without Gapps (so PA Gapps must be used).
Build Env :
Debian GNU/Linux testing (with make downgraded from 4.xx because AOSP lunch require this).
AOSPA soruces 4.4.2_r1 used for the build.
No ART patches! ART will fail if you try using it.
Will test this today on my phone, and if successfully boot, I'll post a link for the ROM.
p.s : From back these days, where people find that AMD64 arch is here, Linux builds started to optimize the speed of your GNU/Linux for your specific CPU (Gentoo for example, or Debian GNU/Linux moved from i386 to i686 and after that to AMD64). Well, the tests and builds performance charfs finished with this : improvement of the speed was was something like 0.6/0.9% ... So in the real world reality do not expect much from this!
Regards ...
Edit:1
Boot failed
Next time, I'll enable the proprietary drivers in the build.
Currently new build is running with enabled prop drives settings like:
Source:http://nosemaj.org/howto-build-android-nexus-4
To use these proprietary files, comment out this line in device/lge/mako/full_mako.mk:
#PRODUCT_RESTRICT_VENDOR_FILES := true
Cheers!
This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21
Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.
Reserved
Reserved
Thanks, working great on CM12.
Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.
Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?
Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.
Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe
diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.
meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective
diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.
meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated
diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025
Custom kernel Is Completely New Concept For Meizu M2/Mini Users So I Am Going To Clarify About It In This Post
Note:I am not responsible for any kind of damage to your device nor a developer is responsible for it.You are only&only responsible for it
Important Suggestion Please Take A Recovery Backup Of Boot.img Before proceding
How to Take Backup? See Below
1)Boot To Recovery (TWRP Suggested)
2)Go to backup and restore menu
3)Select Backup
4)In Menu Just Select Backup of Boot.img
5)Create a backup of it. :fingers-crossed:
6)You are done
Requirements
1)Bootloader Unlocked+Custom Recovery flashed
2)Device Specific Meizu M2/Mini
As you guys may noticed in before post of mine about Lineage OS&Resurrection Remix Rom post I have mentioned about custom kernel
So today i am going to clarify it how it works how it make our phone to work more fluently or degrade it performance and many more features of it :fingers-crossed:
First of All A Honourable Mention For Our Developers of Meizu m2 /mini :angel:
Qus1 (Custom kernel Devloper)
Divis 1969 (Custom Rom Developer)
Crezil1 (ROM Porter (Resurrection Remix))
Yusuf (ROM Porter)
Slasher (ROM Porter(Miui))
Vasiliy.Ivanov (Device Tree Founder For M2/Mini)
Remind me if i forget anyone :silly:
So lets Begin!
Custom Kernel
Difference Between Stock Kernel & Custom kernel.
Stock Kernel Is developed by Flyme For there os (which is Preconfigured by them)
There kernel is good for performance and good in ram management but sucks in battery for most people they all complain about battery this is an alternative way to do so
Qus1 Developed Custom kernel Big.Litle is Stable now
Stable Kernel:
Kernel V4.6 Information: Vibration standard. many supplements on the CPU.
Information about V4.6biglittle kernel:
Works with biglittle, optimized governor interactive, interactiveplus; low vibration. With specific Roms improve energy saving process.
Information about kernel V4.7 + 4.7biglittle:
Livedisplay added from source divis1969 support cm, Lineageos& Resurrection Remix.[/SIZE]
Kernel Notes v4.9: added governor: INTERACTIVEPLUS, CONSERVATIVE, THUNDERX (will suit lovers of energy savings); added tcp: BIC, HTCP, HYBLA,added ioscheduler: bfq; added dynamic synchronization fs; Off Gentle fair sleepers; Optimization added battery during charging; added 3 WiFi control mode; added ThunderQuake Engine 1.0 - Vibration Intensity Controller forvibration button and the phone is regulated in the appendix). gestures to awakening on custom bikes, sweep2wake left to right on the screen and off doubletap2wake on screen off. AIC adjustment core functions. original post varun.chitre15, were taken from the changes.
Kernel Notes V4.9biglittle: works with biglittle, optimized governor interactive, interactiveplus (max freq 1170 both); low vibration. Target nucleus improve energy saving process. Core with additions of the CPU can be used as a biglittle, and without.
Starting with V4.9 + 4.9biglittle: ksm added, initially turned off, you can turn on placing script in the system / etc / the init.d / ksmON
I Call It Big.Little Kernel :silly:
Personal Suggestion tested by me So Don't worry
Cons?
Yes it Do Have Cons Too.
What are Those ?
1)If a noob use this and tweak it improperly it can bring very strange Results. :silly:
2)Makes Display Dim so that it can save more power (If you want to use it with brightness increase brightness thats it) (In Kernel) :crying:
3)If you Enable Double Tap to sleep& Double Tap to wake function in Kernel and you stop that function in setting of OS it will still work
4)it has power to change Vibration Control Modifying it again and again can cause a hardware Failure
5)Lowering down power of cpu can cause Deep sleep
Features
1)Big.Little
Presenting you the New Innovative Big.Little Custom kernel For Meizu M2/Mini :laugh:
1)You can modify vibrations level of your device
2)You can enable double tap to wake and double tap to sleep in any rom
3)Can modify frequency of CPU
4)Cpu governers like Interactive plus,ThunderX included
5)Can tweak for IO schedulers
6)Low memory killer
Why it is powerful and How it is useful see it here here
https://www.arm.com/products/processors/technologies/biglittleprocessing.php
Tweaking suggested By kernel Dev Qus1
Download Kernel Auditor
from play store
Open it
And grant Root access
and modify according to your need
My settings
Cpu max frequency 1170Mhz
lowest 299Mhz
Cpu governor Interactive plus or ThunderX
Enable Option Start At Boot and it will start working from next boot
ThunderX Kernel is now implemented in Big.Little Kernel
Is this only available for custom ROM ?
Ans Nope It is available for Flyme too
Download Link of all Custom kernel Available for different roms Choose wisely
For Flyme 4.5.4I
ThunderX :good:
https://yadi.sk/d/X-IttS7R3GPkjo
For Flyme 6.7.23.8 :good:
Big.Little
https://yadi.sk/d/ZP_lV5TG3GXxf3
For Flyme 6.7.4.11G [Beta]
Big.Little
https://yadi.sk/d/er4snR0w3GuTp7
For Flyme 6.1.0.0G [Stable]
Big.Little
https://yadi.sk/d/Zyg2pusl3K45rB
For Cm12.1 :good:
Big.Little
https://yadi.sk/d/V_9jHzkI3GZZAr
Lineage OS (0.4) :good:
Big.Little
https://yadi.sk/d/79Ha6NU83GZYVb
Lineage OS OMS Edition/V5 :good:
Can Be Used With Rom 7.1.2 Lineage OS 14.1.0 too
Big.Little
https://drive.google.com/file/d/0Bz6Fq2POoJTlX254OVB5cEM2Zm8/view?usp=drive_web
XOSP Xperia Open Source Project Custom Kernel :good:
Big.Little
https://drive.google.com/file/d/0Bz6Fq2POoJTlMkRGb2pGcWxaS1E/view
Xenon HD Custom Kernel :good:
Big.Little
https://drive.google.com/file/d/0Bz6Fq2POoJTlM0RaQVR6dFRPYUE/view
CrDroid Custom Kernel :good:
Big.Little
https://drive.google.com/open?id=0Bz6Fq2POoJTlT2duQ3VjV3BSdlk
Aosp Extended Custom Kernel :good:
Big.Little
https://drive.google.com/open?id=0Bz6Fq2POoJTlOG9HYk9GU0RmVFE
Resurrection Remix 5.8.3 Custom Kernel :good:
Note:This Can Be Used With RR 5.8.3 Compiled from source by Crezil 1
Big.Little
https://yadi.sk/d/tZBEK4aU3HKumm
MIUI :good:
MIUI8 8.1.3.0 Global latest stable
ThunderX
https://yadi.sk/d/Z8cciroC3GHjcG
MIUI8 7.1.1.2
ThunderX
https://yadi.sk/d/WeTx3Ya43FoXtS
MIUI 7.6.8
https://yadi.sk/d/rz7H6bNF3K43Hk
Kernel Sources
Get it here!
https://github.com/divis1969/android_kernel_meizu_meilan2
Dont Liked This Kernel? Simply restore your backup
How to Take Restore a Backup? See Below
1)Boot To Recovery (TWRP Suggested)
2)Go to backup and restore menu
3)Select Restore
4)In Menu Just Select Backup file of Boot.img
5)Just Tap on it swipe it and restore your backup :fingers-crossed:
6)You are done
Credits Goes To Our Beloved Custom Kernel Dev Qus1
Hit Thumbs Up :good: :good: if you found this useful
Suggestions Are Welcomed :good:
Comment Down your Opinion :good:
Regards~
Murtaza Piplod
Bootloop
Hi, I have the rom 7.1.2 Lineage OS 14.1.0 - Nougat Source 2017 installed on my Meizu M2 mini and when I try to install this custom kernel I go the recovery, install the zip and then wipe dalvik & cache but then when I reboot to the system I always get a bootlop and I need to restore the original boot. Any idea of what's the problem? Thanks
I installed it on CM12.1 v0.13 but now how to change vibration intensity?
Edit: Okay got it, from ThunderZap app
how to get this????
Resurrection Remix-N-v5.8.5 L-ROM.RU for MEIZU M2 Mini VIP.
Link: http://l-rom.ru/topic/254-resurrection-remix-n-v585*-l-romru-for-meizu-m2-mini/
techno_crysis said:
how to get this????
Resurrection Remix-N-v5.8.5 L-ROM.RU for MEIZU M2 Mini VIP.
Link: http://l-rom.ru/topic/254-resurrection-remix-n-v585*-l-romru-for-meizu-m2-mini/
Click to expand...
Click to collapse
Apparently our dear friend lunik loves to keep his work for himself and brag about it. He's afraid people will post it elsewhere (i.e xda) and all people will go to these websites except his.
TL;DR: Befriend him
What about battery life with this kernel? How many days phone work on single charging? SOT - how many hours?
S_O_L_92 said:
What about battery life with this kernel? How many days phone work on single charging? SOT - how many hours?
Click to expand...
Click to collapse
I'm on CM 12.1 using this kernel and the battery lasts all day with average usage. With intensive usage it barely finishes the day
I don't know how to install the kernel.
Charistom said:
I don't know how to install the kernel.
Click to expand...
Click to collapse
You have to flash the zip from twrp.
All links got restricted why?
adarshm4you said:
All links got restricted why?
Click to expand...
Click to collapse
Qus 1 account deleted from yandex :/ I can't help in this
murtaza1326 said:
Qus 1 account deleted from yandex :/ I can't help in this
Click to expand...
Click to collapse
Just want to try miui 9 beta u posted.I didn't have that custom kernal.Its ok.
murtaza1326 said:
Qus 1 account deleted from yandex :/ I can't help in this
Click to expand...
Click to collapse
I think that account is not deleted.I can download kernel from cm 12.1 post.
adarshm4you said:
I think that account is not deleted.I can download kernel from cm 12.1 post.
Click to expand...
Click to collapse
i don't know he said me in pm :v that his old files are no longwr available and his account is deleted
may be he created new one
Tweaked as you said.What you mean by brightness will be reduced?I didnt experienced it.No much idea about this customing yet.Atleast I tried it now.I didn't find thunder x in cpu governor.Only interactive I found.Can you share some more settings that i can easily and safely done in kernal adiutor.As you said I am taking much caution on every step I do in it.I know if something gone wrong,my phone will be dead.
Sorry am commenting on a wrong forum. There is no Thread for my phone. Without a custom kernel, can someone flash Nougat ROM. I am using Gionee to be precise. I have tried many Nougat ROM but none of them booted.
Please help.
blogthetech said:
Sorry am commenting on a wrong forum. There is no Thread for my phone. Without a custom kernel, can someone flash Nougat ROM. I am using Gionee to be precise. I have tried many Nougat ROM but none of them booted.
Please help.
Click to expand...
Click to collapse
You can flash noughat if the rom is supported by your phone but in most cases it will not bootup if you don't have custom kernal.
Pretty good!
thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Sent from my XT1254 using XDA Labs
I would expect it to arrive in March, probably with some bugs.
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
ceelos218 said:
thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
Click to expand...
Click to collapse
I going have to check with my local church about that, I may not be able to work on Oreo....
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
bhb27 said:
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
Click to expand...
Click to collapse
first, technically a cross in general and period is sun god worship in itself. so if your church doesn't have any issues with a cross i don't see why it would care about a double cross.
second, that double cross is just on the oreo. it is the nabisco symbol. so if it is evil so is nabisco
I agree with you though where do people come up with this stuff
Safer, smarter, more powerful! All with the Movie trailers voice. Coming this fall*
*TBD
ready to provide support!
bhb27 said:
I going have to check with my local church about that, I may not be able to work on Oreo....
Click to expand...
Click to collapse
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
you need to search on how is done what you wanna to do, simple things as build a ROM there is plenty of tutorial, kernel not so many but there is tutorial + my how to on kernel tread helps you to understand how I do build a kernel (of course is needed basic shell and/or kernel Knowledge, those are available is searches) or the readme in the device tree can explain the basic, I do this for years this is not a thing I learn over night took me years to now a little thing, some times took me weeks to do a very simple thing to work the things is if you wanna don't ever give it up, rest and try again later but don't just give it up, so you search about, like I wrote there is dedicated xda thread on how to build tihngs, you find those and post yours problems there, if is a quark specific help, open yours on general help thread and post the specific problem you have, but really search before you post anything somethings are simple like I wrote is just a question of patiently read and do exactly hat the tutorial says.
TheSt33v said:
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
Click to expand...
Click to collapse
source is not ready yet for any device, even after it may not be ready for quark for some time... + kernel, device and vendor changes are needed...
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
Well I've looked in the same way of you and now I've made it (twice actually (AEX and ViperOS)). Everything that I learned it was just searching here in XDA, taking a look on some videos at YouTube and Google it. But we can't forget the stuff necessary, like a strong computer with Linux (any distro it's fine) or Google Cloud, and, of course, a good internet and patience.
Just building it's simple when you look for the "real" development (working in kernels, device trees, and vendors)
[EDIT]Have a bunch of good ROMs to build. Try look for someone that you liked.
It feels like I'm getting really close, but I didn't get to test to see if it boots . Hopefully I can get it to recognize the device, install, then boot! If I get something stable then I will share it soon.
...
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
calsurferpunk said:
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
Click to expand...
Click to collapse
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
bhb27 said:
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
Click to expand...
Click to collapse
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
calsurferpunk said:
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
Click to expand...
Click to collapse
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Thanks. I'll check it out and see how far I can get. Anything I can contribute to getting it ultimately working will be worth it. I had to make a good number (not major) of device changes already so I'm comfortable with that as well.
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Hey again @bhb27. I just finished incorporating all of those changes and updating other files (mainly in the fs. directory). It still just starts to boot, but quickly goes back to the bootloader again. Any other suggestions on what I could check to see what causes that?
I'm leaning towards a file partition change that it doesn't recognize now, but just a random guess. It still doesn't install the .zip either (still error 7) unless I modify the device check assert (making me think it can't find the build.prop (due to some other format/partition change).
Here's a link to my repos and the .zip in case it helps. Thanks again for the help but I understand if you don't want to get too involved at this point.
Repo: https://github.com/calsurferpunk
Zips: https://androidfilehost.com/user/?w=settings-dev-files&flid=218810
Update 1: I'm also checking to see if there was anything specific about the cm-14.1 to lineage-15.0 device tree and it looks like there might be a little more.
https://github.com/LineageOS/android_device_moto_shamu/compare/lineage-15.0
Update 2: It looks like everything should be good with the device setup as well. I'm wondering if it's more of a TWRP issue since I've seen references of needing a custom version to install AOSP 8.0/LOS 15 in other device forums.
Update 3: I noticed there were a couple kernel config flags missing according to:
https://source.android.com/devices/architecture/kernel/modular-kernels#core-kernel-requirements
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
Added those, but still no luck. I've been comparing device/kernel files locally in hopes of finding a key difference, but after seeing the kernel requirements match I'm still pretty lost.
Update 4: I was able to find the failed kernel boot log under:
/sys/fs/pstore/console-ramoops
It looks like the error preventing booting is from these lines (attached):
...
1.586240,2] init: init first stage started!
[ 1.586318,2] init: First stage mount skipped (missing/incompatible fstab in device tree)
[ 1.586345,2] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
...
[ 2.131621,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_6axis_update_rate 1008 1008 660
[ 2.131679,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_9axis_update_rate 1008 1008 660
[ 2.145657,0] drv260x driver found: drv2605.
[ 2.146248,0] drv260x probe work succeeded[ 2.246181,0] ueventd: Coldboot took 0.310706 seconds
[ 2.255910,3] init: Command 'wait_for_coldboot_done' action=wait_for_coldboot_done returned 0 took 262.268ms.
[ 2.255959,3] init: processing action (mix_hwrng_into_linux_rng)
[ 2.256179,3] init: Mixed 512 bytes from /dev/hw_random into /dev/urandom
[ 2.256212,3] init: processing action (set_mmap_rnd_bits)
[ 2.256263,3] init: Cannot open for reading: /proc/sys/vm/mmap_rnd_bits
[ 2.256287,3] init: Unable to set adequate mmap entropy value!
[ 2.256303,3] init: Security failure...
[ 2.256318,3] init: panic: rebooting to bootloader
[ 2.256336,3] init: Reboot start, reason: reboot, rebootTarget: bootloader
[ 2.256367,3] init: android::WriteStringToFile open failed: No such file or directory
[ 2.256391,3] init: Shutdown timeout: 6
[ 2.256422,3] init: terminating init services
[ 2.256476,3] init: Terminating running services took 0.000134532 seconds with remaining services:0
[ 2.256892,3] init: vold not running, skipping vold shutdown
[ 2.357286,3] init: powerctl_shutdown_time_ms:100:0
[ 2.357305,3] init: Reboot ending, jumping to kernel
[ 2.658702,0] mdss_fb_release_all: try to close unopened fb 1! from pid:1 name:init
[ 2.658715,0] mdss_fb_release_all: try to close unopened fb 0! from pid:1 name:init
[ 2.659433,0] Restarting system with command 'bootloader'.
[ 2.659442,0] Current task:init(1) Parent task:swapper/0(0)
[ 2.659457,0] Going down for restart now
[ 2.660756,0] Calling SCM to disable SPMI PMIC arbiter
It appears to be related to not finding the file partitions and this: https://lkml.org/lkml/2015/12/21/336 and https://lkml.org/lkml/2015/10/28/828.
Phoenix Kernel for J2 Prime
If you're looking for a fast, battery friendly. stable with extended features for your Samsung Galaxy J2 Prime, J2 Ace, Grand Prime Plus and other variants. if it's G532 G/M/F/MT this is for you!
The kernel was originally built by renoxtv, reproduced by Shadisnx255 in his rom and now been fixed and optimized by me.
Other informations? check the Changelogs/History
Phoenix Kernel Changelogs/History :
June 10-12
-Initial Release :
10 Multi touch
Private Mode Fix
Double tap to wake
Cpu Governors (Cultivation, Wheatley, Impulse, Ondemand_x, Pegasusq, Smartmax_eps, Smartmax, Smartass v2, Intellidemand, HYPER, Electrodemand, dancedance, blu_active, bioshock)
I/O Governors/Scheduler (fifo, sio, sioplus, tripndroid, vr, zen)
Bugs : Kernel die when phone turns off/power off
August 10-13 [V1.1]
-1st bug-fix attempt :
Kernel die when phone turns off/power off - FIXED
Selinux default always set to Permissive
Others (oof, i forgot)
August 23-27 [V2]
-Attempt to fix RANDOM PHONE REBOOT : Fixed
Lock wakelock for some services
Added Dynamic Fsync 1.5
Power Suspend - Implemented, but not working fine
TCP Working fine with some added.
Touch Boost
Optimized SLUB
Added KSM
Added Frandom
Many performance changes. (crc and other checks are disabled)
September 13-15 [V3]
-Most of the bugs are fixed
Removed io blockplugs for better performance
Network tweaks, Responsive settings.
Tweaked Mali for more faster rendering
MTK Dynamic Boost
SecurityLogs are now active to provide me logs if bugs will happen
Random Crashes Fixed
Fixed more than 6 default values, to improve battery performance and gaming performance
Kernel loggers added
Battery monitoring is now much detailed/accurate.
Memory bus
ZSWAP Tweaks
Thermal settings (not changeable due to the fact that phoenix is using only default thermal hotplug)
The Kernel now speaks for itself
Idle power consumption reduced to the absolute minimum
Nothing more, nothing less.
No useless placebo patches, or "magical" optimization
October 19 [V3.1]
-Bug fixing
Fixed some random logs
Cleaned dumps and removed something
Removed tons of useless scripts
OEM Security Disabled
November 6 [V3.2] [LATEST]
-Optimization
Stock Gov (interactive) was retuned to much "tamed" one, since the default was too agressive
Fixed samplingrate values
Fixed freqstep values
Fixed treshold values
Re-configured some Governors (electrodemand, bioshock and cultivation)
Others (sry i forgot xd)
------------------------------------
Links :
Direct Installer : https://drive.google.com/open?id=1UfAoX6C7hU6vImE9NKtqMwKDwv8o--fg
W/ Verity : https://drive.google.com/open?id=1dAx0GXpPsv5T8R6GB1mvoCEQOBKtwJxZ
------------------------------------
If you have doubts, PM me.
------------------------------------
FAQ
What Desktop/PC/Laptop
-I'm using Samsung Chromebook 3 500C13-K04
How old am i?
-15 Years of age
Where do i live?
-Philippines
How i managed to fix/add/improve this kind of job? (you're just 15)
-Researchs, studies, i also have the requirements to do.
How can i use this kernel?
-You can download it on some of my sources.
What software/program are you using to edit this kind of files?
-Kernel Kitchen, sometimes i rebuilt it.
Github Account
-https://github.com/LionSinOfPride
Facebook Account
-https://www.facebook.com/Escanorlulzsec
Contact Email :
[email protected]
Credits :
Renoxtv
ShadisNX255
Deepak Singh
Dylan AES
Long
J2 Prime Reborn
J2 Prime Users Group
J2 Prime Philippines
J2 Prime Viet Nam
and others, that i always bother asking at late night. thanks for your help!
if you feel your missing in my list, PM me.
XDA:DevDB Information
Phoenix Kernel, Kernel for the Samsung Galaxy J2
Contributors
Shiroyuki82, Shadisnx255, Renoxtv
Source Code: https://github.com/LionSinOfPride/G532G-Phoenix-Kernel
Kernel Special Features: Additional 14 CPU Governors, 6 IO Schedulers, Custom TCP and pretty tuned kernel. 10 Multitouch and others.
Version Information
Status: Stable
Current Stable Version: V3.2
Stable Release Date: 2019-11-09
Created 2019-11-09
Last Updated 2019-11-09
You created three threads of this.
TBM 13 said:
You created three threads of this.
Click to expand...
Click to collapse
it shows error, then it really got posted wtf.
Shiroyuki82 said:
it shows error, then it really got posted wtf.
Click to expand...
Click to collapse
this is absolute nuts, xda is having problems in it's server. now it's confusing to have 3 threads
What is the difference between the two versions below "Links" ? What version should I use ?
thatha said:
What is the difference between the two versions below "Links" ? What version should I use ?
Click to expand...
Click to collapse
direct installer doesn't have no-verity installed, most useful in custom roms and if you want to update your magisk and other thing that has connection with boot.img/kernel.
verity installer has no-verity inside the installer.
RESERVED
nice remake bruh
renoxtv said:
nice remake bruh
Click to expand...
Click to collapse
thanks!
Nice kernel, thanks
Nice kernel, thank you!
So would this work on J200G ?
PRemBh0i said:
So would this work on J200G ?
Click to expand...
Click to collapse
nope, only for G532x
Hey thanks for the kernel! everything seems okay but I noticed that after I flashed it, when I turn on the wifi in the second time it forgots the password automatically. By the way pinoy din ako J2 prime user hahahahaha tapos main phone ko to sana mafix mo po thanks!
UziGrey said:
Hey thanks for the kernel! everything seems okay but I noticed that after I flashed it, when I turn on the wifi in the second time it forgots the password automatically. By the way pinoy din ako J2 prime user hahahahaha tapos main phone ko to sana mafix mo po thanks!
Click to expand...
Click to collapse
stock rom? edit mo build.prop
ro.securestorage.support=true
to
ro.securestorage.support=false
normal yan, lalo na sa mga full dump stock rom
Stock rom pala to sige thanks sa info hahahaha
Wala pa kaseng stable na custom rom dito eh hinihintay ko ying lineage os na para sa j2 prime
UziGrey said:
Stock rom pala to sige thanks sa info hahahaha
Wala pa kaseng stable na custom rom dito eh hinihintay ko ying lineage os na para sa j2 prime
Click to expand...
Click to collapse
marami na, yung lineage habang pakonti ng pakonti yung bugs pahirap ng pahirap, months or year pa aabutin bago maging stable yon.
Hades
Enigma
Aether
Xtreme Ultimate
good work but can u make lite version of phoenix kernel? like not add additional CPU Governors, IO Schedulers, keep westwood tcp, etc.
khanghy10000 said:
good work but can u make lite version of phoenix kernel? like not add additional CPU Governors, IO Schedulers, keep westwood tcp, etc.
Click to expand...
Click to collapse
well it's kinda pointless if i'm gonna make that and i need to revise the source because all of the custom things are directly in the source. tho thanks for the feedback
if you doesn't need them you can just use the default and just edit the things that you want ^^
Shiroyuki82 said:
well it's kinda pointless if i'm gonna make that and i need to revise the source because all of the custom things are directly in the source. tho thanks for the feedback
if you doesn't need them you can just use the default and just edit the things that you want ^^
Click to expand...
Click to collapse
Thanks btw, is your kernel source on github stable?