Related
Good news everyone!
The superfantasticawesome Nameless ROM dev team currently has a very solid 5.0 port currently open for testing! You can find it at http://www.oppoforums.com/threads/5-x-namelessrom-all-variants.22451/ .
Be sure to say thank you to them, and give them the feedback they deserve for this!
TIPS FOR INSTALLING:
Like many ROMs for the Find7 variants, this ROM needs a specific baseband or the proximity sensor gets pretty finicky. However, not all basebands seem to be compatible at the moment. For myself, I found that downgrading to the 2.0.3 beta only worked for me (I'm on a Find7a), but I've also heard that some Find7 people were able to use 1.2.5.
Enjoy your Lollipop, everyone!
Fantastic news. I'm downloading it right now. Will test tonight. Thanks.
Nameless rom works fantastic for me.Very smooth indeed. The only issue is with proximity sensor. Can you please let me know on how youdegraded the baseband version?
manojava said:
Nameless rom works fantastic for me.Very smooth indeed. The only issue is with proximity sensor. Can you please let me know on how youdegraded the baseband version?
Click to expand...
Click to collapse
Use the stock recovery to flash the 2.0.3i beta, then install the 5.0 port. If you're on a non stock recovery, I'd recommend using Tantrum's recovery installer here!
I think there is no need to flash whole COS rom then Nameless LL. If some sensors are not working in LL, like proximity, try to flash other modem, no need for whole ROM.
Go to modem collection here and try to flash 1.2.5 modem, it should work.
If you have chinese model, like me, I have x9007, I flashed Modempackage_1.2.5_zixuan_cn.zip and Nameless LL is working great, only NFC is not working.
Nikola P. said:
I think there is no need to flash whole COS rom then Nameless LL. If some sensors are not working in LL, like proximity, try to flash other modem, no need for whole ROM.
Go to modem collection here and try to flash 1.2.5 modem, it should work.
If you have chinese model, like me, I have x9007, I flashed Modempackage_1.2.5_zixuan_cn.zip and Nameless LL is working great, only NFC is not working.
Click to expand...
Click to collapse
Thank you so much. Its working fine after flashing the 1.2.5 modem. BTW i use find7a.
Nikola P. said:
I think there is no need to flash whole COS rom then Nameless LL. If some sensors are not working in LL, like proximity, try to flash other modem, no need for whole ROM.
Go to modem collection here and try to flash 1.2.5 modem, it should work.
If you have chinese model, like me, I have x9007, I flashed Modempackage_1.2.5_zixuan_cn.zip and Nameless LL is working great, only NFC is not working.
Click to expand...
Click to collapse
That's very interesting. I tried using three different basebands (the 1.2.5, 2.0.3, and a OnePlusOne baseband) but all of them only caused the ROM to bootloop. Glad it worked for you guys though!
Hi folks,
I'm considering unifying since I quickly run out of app space. Is there any word on a L port for unify and if there is a specific unify method that has to be followed?
Thanks for your help, apologies for my ignorance.
darrenpauli said:
Hi folks,
I'm considering unifying since I quickly run out of app space. Is there any word on a L port for unify and if there is a specific unify method that has to be followed?
Thanks for your help, apologies for my ignorance.
Click to expand...
Click to collapse
I believe that this ROM actually supports unified storage. Check out the link that I posted at the top, and you should find unification instructions in the first post.
Great thanks BG!
Cant wait to flash.
This is awesome, I'm happy that I accidentally came to general looking for a new ROM.
Edit:
No dice on flashing the Dec 6th 5.0.1 for me (Find7a not unified)
I tried modem versions 1.2.5i and 2.02i
Edit 2:
Dont wanna rain on anyone's parade but i got the Omni 5.0 ROM to work instead.
Edit 3:
So after finding no Root yet on Omni, i went ahead and flashed NameLess again and for some reason it works. well.. yay! (Dec 6 not unified)
I have to admit it was easier to get Omni 5.0 to work over Nameless 5.0 and I came from Nameless 4.4.4 Kit Kat.
Christendom... said:
I have to admit it was easier to get Omni 5.0 to work over Nameless 5.0 and I came from Nameless 4.4.4 Kit Kat.
Click to expand...
Click to collapse
Hey, that's great! How have you found the battery life so far on Omni? I found that Nameless was a bit better in both the battery and features department, but I've been a huge fan of OmniRom for quite some time now, and would love to support their work too.
BG64 said:
Hey, that's great! How have you found the battery life so far on Omni? I found that Nameless was a bit better in both the battery and features department, but I've been a huge fan of OmniRom for quite some time now, and would love to support their work too.
Click to expand...
Click to collapse
Battery life is good on Omni, however, I have to agree with you that Nameless battery life is better, and their features are more extensive.
On a side note: although the battery and features are a "bit better" on Nameless, OmniRom, in my opinion, is the gold standard for (AOSP) custom Roms. There are no fillers, they are quick to implement cutting-edge advancements, and their Roms just work. Meaning, they are stable.
Christendom... said:
Battery life is good on Omni, however, I have to agree with you that Nameless battery life is better, and their features are more extensive.
On a side note: although the battery and features are a "bit better" on Nameless, OmniRom, in my opinion, is the gold standard for (AOSP) custom Roms. There are no fillers, they are quick to implement cutting-edge advancements, and their Roms just work. Meaning, they are stable.
Click to expand...
Click to collapse
That has really, over the past year, become our primary focus - on our most well supported devices, we are far more stable than many other projects. (Although the EOS guys do a damn good job too).
We're also the only project other than EOS where users of Oppo devices can routinely interact with the developers who did the hardware support of the device.
In the case of CM - Most of the work is Steve swinging his ninja sword, at least Tom does talk to users but much of the work is done by people who never come here.
In the case of all CM derivatives that blind-track CM (Nameless is in this category - in fact it was founded by some Omni maintainers who disagreed with the rest of Omni as far as blind-tracking CM vs. actually solving the problems on your device yourself.) - you're even farther removed from the people actually doing the work.
Omni and EOS both have the guys who are doing the hardware bringup communicating with users directly to look for trends and issues that stand out. (the two teams also communicate with each other...) Gummy did too before they called it quits.
Entropy512 said:
That has really, over the past year, become our primary focus - on our most well supported devices, we are far more stable than many other projects. (Although the EOS guys do a damn good job too).
We're also the only project other than EOS where users of Oppo devices can routinely interact with the developers who did the hardware support of the device.
In the case of CM - Most of the work is Steve swinging his ninja sword, at least Tom does talk to users but much of the work is done by people who never come here.
In the case of all CM derivatives that blind-track CM (Nameless is in this category - in fact it was founded by some Omni maintainers who disagreed with the rest of Omni as far as blind-tracking CM vs. actually solving the problems on your device yourself.) - you're even farther removed from the people actually doing the work.
Omni and EOS both have the guys who are doing the hardware bringup communicating with users directly to look for trends and issues that stand out. (the two teams also communicate with each other...) Gummy did too before they called it quits.
Click to expand...
Click to collapse
Hey, thanks for the post Entropy. I really like hearing developers opinions. In all honesty, I was using your ROM before I switched to nameless (and only did so because it was the first fully functional, stable Lollipop ROM available) and would love to switch back. You guys seem to be pretty avid in releasing your builds as of late, so I'll certainly be keeping an eye out! All I really need in terms of features anyway is the ability to change button configurations and double tap something to sleep or wake the device (I hate using the power button) so once you have those, you'll have one more on the bandwagon. You guys really are doing something right here, and I intend to support it!
Entropy512 said:
That has really, over the past year, become our primary focus - on our most well supported devices, we are far more stable than many other projects. (Although the EOS guys do a damn good job too).
We're also the only project other than EOS where users of Oppo devices can routinely interact with the developers who did the hardware support of the device.
In the case of CM - Most of the work is Steve swinging his ninja sword, at least Tom does talk to users but much of the work is done by people who never come here.
In the case of all CM derivatives that blind-track CM (Nameless is in this category - in fact it was founded by some Omni maintainers who disagreed with the rest of Omni as far as blind-tracking CM vs. actually solving the problems on your device yourself.) - you're even farther removed from the people actually doing the work.
Omni and EOS both have the guys who are doing the hardware bringup communicating with users directly to look for trends and issues that stand out. (the two teams also communicate with each other...) Gummy did too before they called it quits.
Click to expand...
Click to collapse
This is the reason I decided to stay with omni and I am really thankful that there are people like you guys out there that don't let us alone with a great device but awful default firmware (COS).
But I would really like to know your opinion about Paranoid Android, as I always thought they have (sometimes more, sometimes less) good communication to their users and a solid team of Devs that solves issues instead of blind-tracking the solutions from somewhere else.
This is a booting CAF 3.10 kernel for none other than our shiny OnePlus One. Personally, I'm satisfied with my phone as it is with a 3.4 kernel (and 3.10 is a lot of work without proper firmware), so I've given up on developing this 3.10 kernel. This thread is just a free-for-all for anyone who wants to have a crack at developing 3.10.
I threw this kernel together pretty sloppily 2 months ago, so I apologize for the lack of full git history from CAF and some messy code from me. The kernel is based off of the LA.BF.2.1_rb1.xx branch from CAF. The kernel should boot as-is on the official CM nightlies, and it is confirmed to boot on my CM12.1 builds. All it requires is updated WCNSS configuration binaries to boot (flashable zip available in the downloads tab of the thread). The kernel currently only supports JDI command-mode panels, and I compiled the kernel with Google's GCC 4.8 toolchain.
Source code: https://github.com/sultanxda/android_kernel_oneplus_bacon-3.10
What works:
It boots (woo)
Display
Touchscreen
Modem (no mobile data though)
WiFi
Charger (not from wall outlets though)
Battery percentage/health reporting
Volume keys
Sensors
USB
Assume everything else doesn't work. Here's a fun screenie: http://imgur.com/H1UERfr
Good luck with haxing 3.10!
XDA:DevDB Information
CAF Linux 3.10.40 kernel for Bacon, Kernel for the ONEPLUS ONE
Contributors
Sultanxda
Kernel Special Features: It boots
Version Information
Status: Testing
Created 2015-07-05
Last Updated 2015-07-06
@Sultanxda Awesome work bro now if only the Cyanogen.org devs supported devices like Sony
arm: qcom: Add SONY Shinano platform, msm8974pro family - https://github.com/sonyxperiadev/kernel/commit/193c3345565d0c3a202f8feac62a21842b06e347
http://developer.sonymobile.com/kno...sh-a-linux-kernel-for-aosp-supported-devices/
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
http://developer.sonymobile.com/201...ny-presentation-at-embedded-linux-conference/
http://developer.sonymobile.com/201...-xperia-devices-in-sonys-open-device-program/
Awsome work mate. Where can i find the original CAF branch? Somewhere at codeaurora cgit?
Sent from my A0001 using XDA Free mobile app
DerRomtester said:
Awsome work mate. Where can i find the original CAF branch? Somewhere at codeaurora cgit?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/?h=LA.BF.2.1_rb1.39
Sultanxda said:
Yep. https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/?h=LA.BF.2.1_rb1.39
Click to expand...
Click to collapse
Thank you. I am gonna create a full git history with that + your commits. If anyone wants access to it to push some code feel free to ask.
Gesendet von meinem A0001 mit Tapatalk
any inherent benefits of having linux 3.10 over 3.4?
_ASSASSIN_ said:
any inherent benefits of having linux 3.10 over 3.4?
Click to expand...
Click to collapse
http://kernelnewbies.org/Linux_3.10
https://github.com/sonyxperiadev/ke...UX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067
_ASSASSIN_ said:
any inherent benefits of having linux 3.10 over 3.4?
Click to expand...
Click to collapse
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.
RenderBroken said:
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.
Click to expand...
Click to collapse
possibly collab with @DerRomtester?
_ASSASSIN_ said:
possibly collab with @DerRomtester?
Click to expand...
Click to collapse
man, that would be cool but it would be a massive undertaking then you would need a road map for other rom Devs to use to even use the work you have done let alone to even be accepted officially from major Roms out there like CM. This is something I have thought about alot but the work needed to put in doesn't match anything near what I would get out of it. This doesn't mean money necessarily but time, time away from family, etc.
This is still something I will take a look at. I wouldn't mind any input from @DerRomtester at all.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel
evronetwork said:
First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel
Click to expand...
Click to collapse
Pretty sure that most devs would use this as a base if it had the proper driver support as it would provide quite the bump for security
evronetwork said:
First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel
Click to expand...
Click to collapse
Facts. We need way more collabs man. Unity gets a lot done. I personally know nothing about developing, but I'm a great tester. I'm willing to brick my phone.. Test, bootloop and brick it again lol. Everyone can play a part in the grand scheme of things.
@Sultanxda can you share your kernel with me?
I compiled it but i don't get it booting. You have made some ramdisk changes ? You added an dtb file ?
DerRomtester said:
@Sultanxda can you share your kernel with me?
I compiled it but i don't get it booting. You have made some ramdisk changes ? You added an dtb file ?
Click to expand...
Click to collapse
No ramdisk changes, no missing dtbs. Just ran a mrproper and compiled it exactly as it is on my GitHub, and it boots. Compiled with GCC 4.8 from Google using almost the exact same script I use to compile my 3.4 kernel, with the only change being that the dtb path for the dtbtool is arch/arm/boot/dts/, not arch/arm/boot/ (though you probably already figured that out).
Sultanxda said:
No ramdisk changes, no missing dtbs. Just ran a mrproper and compiled it exactly as it is on my GitHub, and it boots. Compiled with GCC 4.8 from Google using almost the exact same script I use to compile my 3.4 kernel, with the only change being that the dtb path for the dtbtool is arch/arm/boot/dts/, not arch/arm/boot/ (though you probably already figured that out).
Click to expand...
Click to collapse
Thank you mate. I think i know the problem
_ASSASSIN_ said:
Pretty sure that most devs would use this as a base if it had the proper driver support as it would provide quite the bump for security
Click to expand...
Click to collapse
If companies released the drivers we would have 3.10.x, 3.18.x and even 4.2.x kernels(someone would try to do it even if it turned out a failure)
Released drivers also would have better optimised roms and would make a 5 year old device to live forever (new android e.g. android 7? no problem)
OmegaBlaze said:
Facts. We need way more collabs man. Unity gets a lot done. I personally know nothing about developing, but I'm a great tester. I'm willing to brick my phone.. Test, bootloop and brick it again lol. Everyone can play a part in the grand scheme of things.
Click to expand...
Click to collapse
I'm the worst kind of programmer, I mean I do own a degree but the programming language was my weakest link, so I can't help and kernel is one of the hardest parts it needs big ..knowledge to do it :silly:
Now lets not go off topic and wish for someone to work on 3.10.x I mean even if it's buggy and a bit unstable it will bring some new stuff and when it gets stable well then the fun will start
RenderBroken said:
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.
Click to expand...
Click to collapse
I wasn't exactly interested in 3.10 until i read yours comment. If this kernel can also make opo work like N6 i.e. running always on quad core mode and still maintain good battery lyf, man i would pray that either opo or cm releases 3.10 kernel.
Sent from OnePlus One
abhibnl said:
I wasn't exactly interested in 3.10 until i read yours comment. If this kernel can also make opo work like N6 i.e. running always on quad core mode and still maintain good battery lyf, man i would pray that either opo or cm releases 3.10 kernel.
Sent from OnePlus One
Click to expand...
Click to collapse
This will never happen. From a business perspective, it costs too much for little benefit, and only introduces the potential for more bugs.
However, here is a hint: Bacon's TrustZone firmware does not check metadata when loading firmware images, so you can technically load firmware from any device (ex: you can use Venus firmware from a totally different device).
If you know what you're doing and you have 3 months of your life to burn on this, then it should be possible to get everything working with the LA.BF.2.1_rb1.xx kernel branch.
Sent from my A0001 using XDA Free mobile app
As the title states. Now that we have root and an unlocked bootloader do you think lineage is will make its way to this device?
Not a fan of lineage code.
We need a aosp rom like Purefusion.
We need Kernel source from Motorola first. They are dragging their feet like always. Without kernel source, we can't get a 100% working TWRP for custom roms to flash
Agreed. We need them to drop source code like they said they would.
Sent from my Moto Z (2) using Tapatalk
Looks like I may be getting this phone instead of the Note 8. Come on Motorola......release that source code.
They aren't going to acknowledge you here. Follow this link and sign up to let them know how you feel.
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/124#issuecomment-331552066
Sent from my Moto Z (2) using Tapatalk
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/nougat-7.1.1-release-nash
Uzephi said:
We need Kernel source from Motorola first. They are dragging their feet like always. Without kernel source, we can't get a 100% working TWRP for custom roms to flash
Click to expand...
Click to collapse
Is there a way to get the kernel ourselfs??
WeUseLord- said:
Is there a way to get the kernel ourselfs??
Click to expand...
Click to collapse
Https://GitHub.com/Uzephi/Nash
Kernel source was given by Motorola. There is my git with the edits for a regular machine running GCC 4.9 to build a kernel that boots and works.
How much less is less?
If you build it they will come.... ("Field of Dreams" movie line) Seriously, though, I do wonder if giving up stability and features is worth it for minimal gains in performance/benchmarks? Motorola's take on Android is already bare-bones compared to Samsung! With Lineage, it's slightly easier to theme, true, but Substratum suffices for many individuals on stock. I haven't tried Substratum yet, because I don't like dark themes. Don't get me wrong, I want Lineage to succeed! The more open-source options the better! But, is it worth it for the principle, or modest increase in speed (maybe)? Bugless and not losing any features, I would run Lineage; so, we'll see, because it will come in due time.
jhofseth said:
If you build it they will come.... ("Field of Dreams" movie line) Seriously, though, I do wonder if giving up stability and features is worth it for minimal gains in performance/benchmarks? Motorola's take on Android is already bare-bones compared to Samsung! With Lineage, it's slightly easier to theme, true, but Substratum suffices for many individuals on stock. I haven't tried Substratum yet, because I don't like dark themes. Don't get me wrong, I want Lineage to succeed! The more open-source options the better! But, is it worth it for the principle, or modest increase in speed (maybe)? Bugless and not losing any features, I would run Lineage; so, we'll see, because it will come in due time.
Click to expand...
Click to collapse
Totally correct. Our device is so close to stock it's ridiculous. We pretty much have a pixel phone with slower updates and mods. Which I'll take over the boringness of a pixel. Yes substratum would be pretty cool but I know things are coming we have a kernel being updated to the latest kernel version available. We're testing twrp right now and have it 95% working and now we have twrp and magisk and an updated kernel all going at once things are coming along slowly but I feel they will pick up soon
Little teaser
joemossjr said:
Little teaser
Click to expand...
Click to collapse
That looks like the stock tmo version [emoji23][emoji23][emoji23].
There should be almost no diference at all.
But i want some LineageOS [emoji41]
Sent from my Moto Z (2) using Tapatalk
I'm confused, the kernel sources still haven't been released?
LGtMgG2t said:
I'm confused, the kernel sources still haven't been released?
Click to expand...
Click to collapse
Yes they where released.
Sent from my Moto Z (2) using Tapatalk
LGtMgG2t said:
I'm confused, the kernel sources still haven't been released?
Click to expand...
Click to collapse
Yes, they were released. Kernel builds fine. For AOSP stuff we need vendor files. We are piecing things together. All builds have failed so we haven't even had a chance to see if it boots.
Why hasn't a kernel been fully released? (Besides the upstreamed one in the custom ROM section) because of encryption not working right in TWRP, you'd lose root when flashing as TWRP can't put the ramdisk back correctly hence no root.
Somebody should start Lineage. I would do it if I had enough experience but I don't yet. Huge tasks like LTE not working, etc., can arise depending upon the particular phone....
The attached screenshot illustrates the dynamics quite well. I was initially mildly surprised by the Lineage developer's response to someone, "When you start paying me." But, for some developers who devote lots of their time to Lineage, I suppose the questions can become tiresome. Every developer is different, of course, and it is a global scale endeavor.
Since Oneplus released the new 4.5.0 OxygenOS update, many noticeable changes has been achieve, better battery life, performance, etc.
On the other hand, Android O is reaching many devices around the world thanks to professional developers on XDA community.
Should I stick with OxygenOs, or use lineage os. Which is better
OXYGEN OS
Lineage hands down. Stock is boring, u wanna stay stock buy an iphone.
So many roms to try, why you would stay stock baffles me. But each to there own ?
I suppose these kind of threads are just for opinion-gathering, but I think there's nothing wrong with that.
On one hand, stock OxygenOS is simply "things that just works." Sure, this is boring, but some people prefers to have a system that works in their day to day life. Boring? Sure. But does it works fine? Yes.
Lineage on the other hand, while stable as is, is still geared towards experimenting, that doesn't mean it's unstable though. Also, Lineage (and most other custom ROM) is pretty good when it comes to keeping devices updated - so once OnePlus 3/T is out of commission and OnePlus drops their support for the device(s), it's going to be a good idea to move to Lineage if you want to continue using the phone.
tl;dr use stock if you just want things to work, and Lineage for the sake of modding and future-proofing.
Should you switch to Lineage? Probably.
Nether if you ask me. They are both garbage when compared to an AOSP based rom like Dirty Unicorns. Both have way too many bugs for any real day to day usage.
zelendel said:
Nether if you ask me. They are both garbage when compared to an AOSP based rom like Dirty Unicorns. Both have way too many bugs for any real day to day usage.
Click to expand...
Click to collapse
We are CAF out of the box. Rom base might be AOSP but all our hardware specific stuff is CAF or LOS
F4uzan said:
I suppose these kind of threads are just for opinion-gathering, but I think there's nothing wrong with that.
On one hand, stock OxygenOS is simply "things that just works." Sure, this is boring, but some people prefers to have a system that works in their day to day life. Boring? Sure. But does it works fine? Yes.
Lineage on the other hand, while stable as is, is still geared towards experimenting, that doesn't mean it's unstable though. Also, Lineage (and most other custom ROM) is pretty good when it comes to keeping devices updated - so once OnePlus 3/T is out of commission and OnePlus drops their support for the device(s), it's going to be a good idea to move to Lineage if you want to continue using the phone.
tl;dr use stock if you just want things to work, and Lineage for the sake of modding and future-proofing.
Should you switch to Lineage? Probably.
Click to expand...
Click to collapse
I like opinion gathering threads since they foster good discussion, but it seems that questions like these are asked every week since users posting them don't bother to search past threads despite the better content in them.
That being said, I agree that LOS is great in the future once device support is dropped, but do you see any downside in keeping OOS installed until support is dropped?
Lineage OS all the way with OMS support. Stock is boring and nothing much then black and regular theme.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The 90s kernel for Pocof3 / Redmi k40 and Mi 11x
Be careful if you have any damage to your device I would not be the cause because it is your choice to install my kernel on your device.
For your reassure, each release of this kernel is verified and tested to be the most stable possible
Kratos Edition​*First initial build
*upstream to 5.15.1
*optimized for Corvus and Xdroid
*Alpha build
*fix Fastcharging
*Don’t with A12 ROMs – Until Next Update
2.0 Changelogs:
*Upstreamed LTS to: 4.19.215
*Focused on Battery and Performance
*fixed Miui not showing up kernel version
*Fixed Low brightness
*Replaced touch drivers (thanks to @Dawfuk)
*Thanks To All My Testers
*Credits :
@Dawfuk
Eclipsia kernel
Optimus Drunk Kernel
1.0 Changelogs:
-----------------
*Initial build
*Based on Quantic
*Added support for A12
*Added CASANOVA Thermals
*Added new efficient frequencies
* compiled using proton clang 13.0.0
*Upstreamed LTS to: 4.19.214
*Upstreamed CAF to LA.UM.9.12.r1-13300-SMxx50.QSSI12.0
*Added a kernel space blocker to don't allow execution of magisk root optimizers such as LawRun, FDE.AI, etc.
Installation :
Backup Boot.img and Dtbo.img
Flash the kernel
Reinstall the recovery
Clean cache and dalvik
reboot
Credits :
*Casanova for Thermal
* Quantic kernel
* Immensity kernel
* Ram potagani
* Shreyansh (the 90s guy yt (Admin))
Download link: https://sourceforge.net/projects/the-90s-kernel/
Source of my kernel: https://github.com/Xtu-Fuszx/The_90s_Kernel
Donate: https://telegra.ph/Donate-to-90s-Guy-09-07
Great job! Seems good so far
Added a kernel space blocker to don't allow execution of magisk root optimizers such as LawRun
What does that mean you can't root with magisk? That's ironic because yesterday I was talking to someone who said the makers of hentai OS don't like root or twrp.
To that I say you guys do understand most of us would rather be rooted stock than on some nonstock rom without root?
It's actually sad when open source coders make a rom and want to say you can't root because it messes it up and we can't fix it so no root. That is what we do at XDA.
Thread open again
strongst
XDA staff
Techguy777 said:
Added a kernel space blocker to don't allow execution of magisk root optimizers such as LawRun
What does that mean you can't root with magisk? That's ironic because yesterday I was talking to someone who said the makers of hentai OS don't like root or twrp.
To that I say you guys do understand most of us would rather be rooted stock than on some nonstock rom without root?
It's actually sad when open source coders make a rom and want to say you can't root because it messes it up and we can't fix it so no root. That is what we do at XDA.
Click to expand...
Click to collapse
Those are not "optimizers" they are doing worse for your device. Then you are the one that complains "x kernel its bad" just because you used one of those "optimizers" that made it bad. However no one forces you to flash anything .
EmanuelCN said:
Those are not "optimizers" they are doing worse for your device. Then you are the one that complains "x kernel its bad" just because you used one of those "optimizers" that made it bad. However no one forces you to flash anything .
Click to expand...
Click to collapse
I don't need to flash custom kernels it's built with stock source code, so it's stock kernel with a gesture or something added but generally speaking they don't perform better or have better battery life. They certainly don't do both battery and performance better than the guys that wrote the stock kernel source could do.
You guys get carried away on Xda. We appreciate anything to contribute but most developers don't do it for free they make money with donations I've seen them get thousands of dollars. That is their hope to it's only I do it for me and no one else when things don't work right.
If someone can produce a kernel that can beat a benchmark score of 713000 on AnTuTu I will be more than happy to try it.
Techguy777 said:
If someone can produce a kernel that can beat a benchmark score of 713000 on AnTuTu I will be more than happy to try it.
Click to expand...
Click to collapse
If you think antutu benchmark matters or any other score in any benchmark it means you don't really know much. The only benchmark to ever matter is UIBENCH jitter test. Where's stock kernel its garbage at as well as any other stock kernel by any manufacture not just xiaomi. The smoothness its not even comparable. Benchmark scores do not matter at all your phone can perform much better including gaming while having a lower score in benchmarks.
EmanuelCN said:
If you think antutu benchmark matters or any other score in any benchmark it means you don't really know much. The only benchmark to ever matter is UIBENCH jitter test. Where's stock kernel its garbage at as well as any other stock kernel by any manufacture not just xiaomi. The smoothness its not even comparable. Benchmark scores do not matter at all your phone can perform much better including gaming while having a lower score in benchmarks.
Click to expand...
Click to collapse
I understand that Benchmarks aren't everything but it does give us a guide to go by. For example I have a S10 lite ultra and it has SD 855 gets about 489k and the Poco f3 got 713k and it does work a slight bit faster side by side opening apps and doing stuff. It's only on XDA that you hear people talking about it means nothing.
Let's not get carried away if people on Xda could build a better kernel than xiaomi or Samsung or whoever they would have to know how to write code and they don't. Xiaomi isn't waiting for their kernel source it's the other way around. You can't use Xiaomis kernel source code and than claim you have made it better performance and battery. Because I've been flashing roms and kernels now on like 20 different devices for 4 years and it never makes a big difference. The best thing a developer can do is make permissive for Samsung kernel. That truly adds something that isn't there already.
No the truth is if there are ways to say something is better or not on Android phones that doesn't show favorable results to whatever someone has built than it's looked at like crap because we don't like the results. You guys try to speak down to people like you don't know crap about anything if you think that matters. Really, I see Amd, Samsung, Google, Intel, pretty much everyone using benchmarks to show their products being 30 percent better. They probably don't know real development.
I'll tell you what what does that jitter test for and you give me your best custom kernel to show it? I'm on EU rom.
It's like best rom? Everyone is different and it depends. No everyone wants the same thing.
Stability, performance, battery there's really nothing different. The only thing that is different is if someone wants pixel rom to mimic pixel devices or OnePlus rom or Samsung one ui rom. Don't get me wrong I enjoy tweaking my devices but is anyone with A/B slots and super partition able to restore device with twrp?
Just today I seen casnova post a screenshot of Geekbench which is weird because he probably didn't realize it doesn't matter Benchmarks. But his was 900s single core and 3300 multiple core so I quickly ran Geekbench to and I scored almost the exact same thing.
Here's why I say this stuff because the so call developers on XDA have took all the fun out of it. Your not developers you take other people's work and slap your name on it while changing as little as 1 thing or sometimes nothing. Your compliers or something like that not developers. You guys belittle noobs because xda allows people that complie code to talk down to newbies who want to ask questions but the truth is that actually makes them look bad because they don't know the answer most of the time. ETAs aren't allowed because developers don't actually know if they can fix anything or if they can build again.
All of the rules are stupid and make no sense unless you make it so people have to act like developers aka compliers are someone special. Who's so smart and just does things to be nice and the donation link.
It's to the point where I just want to see all the new members stop kissing ass and tell the developers your not a developer unless you have a degree or work for a software company but if you did you wouldn't be on Xda.
The xda developers have gone to far, you guys have gotten big heads puffed up chest and think your hot stuff. It's ruined xda completely and it's not a helpful website anymore it's thousands of threads of it's already been answered search the post, nice rom dev even before they flash it. Now if you ask about a feature the doesn't work they just blow you off. That means threads are pointless for information on the software.
Guys, would it work on ArrowOS 12? Can it be flashed via sideload?
Techguy777 said:
I understand that Benchmarks aren't everything but it does give us a guide to go by. For example I have a S10 lite ultra and it has SD 855 gets about 489k and the Poco f3 got 713k and it does work a slight bit faster side by side opening apps and doing stuff. It's only on XDA that you hear people talking about it means nothing.
Let's not get carried away if people on Xda could build a better kernel than xiaomi or Samsung or whoever they would have to know how to write code and they don't. Xiaomi isn't waiting for their kernel source it's the other way around. You can't use Xiaomis kernel source code and than claim you have made it better performance and battery. Because I've been flashing roms and kernels now on like 20 different devices for 4 years and it never makes a big difference. The best thing a developer can do is make permissive for Samsung kernel. That truly adds something that isn't there already.
No the truth is if there are ways to say something is better or not on Android phones that doesn't show favorable results to whatever someone has built than it's looked at like crap because we don't like the results. You guys try to speak down to people like you don't know crap about anything if you think that matters. Really, I see Amd, Samsung, Google, Intel, pretty much everyone using benchmarks to show their products being 30 percent better. They probably don't know real development.
I'll tell you what what does that jitter test for and you give me your best custom kernel to show it? I'm on EU rom.
It's like best rom? Everyone is different and it depends. No everyone wants the same thing.
Stability, performance, battery there's really nothing different. The only thing that is different is if someone wants pixel rom to mimic pixel devices or OnePlus rom or Samsung one ui rom. Don't get me wrong I enjoy tweaking my devices but is anyone with A/B slots and super partition able to restore device with twrp?
Click to expand...
Click to collapse
First of all you have literally no clue on how a kernel works and what those modules do. There is no such thing as "building a better kernel than xiaomi, samsung, etc", no one would be ever able to make a kernel from scratch. The kernel itself firstly comes from Linux where's for our case on snapdragon Qualcomm modifies it and releases sources for each SOC then it goes to the specific manufacture that wants to create their phone and has to add the necessary code in order for their phone to work with the components they chose and usually they try to "tweak" the kernel which is literally doing worse 90% of the time. Qualcomm has a lot of stupid implementations baked into the kernel such as pl, hispeed, WALT, which are the reason the jitter its horrible with stock kernel, instead following mainline which is the best thing to be done. Benchmarks are useless because they are made to run on based on what usually the phones ship with, they are not designed to measure properly the performance of a phone therefore i have a lower score with my kernel but surprisngly jitter its 10 times better on "my' kernel, as well as normal usage and gaming too. I don't care what other devs posted about benchmakrs, i dont think my name is "casnova" or whatever, i dont talk for them i'm letting you know how it work. Also regarding "Your not developers you take other people's work and slap your name on it while changing as little as 1 thing or sometimes nothing", why dont you check github? why do you even talk without knowing what its really happening? its funny how people complain about dumb stuff, as i explained you that blocker its meant for people like you to not use x,y,z modules then to complain that the kernel is bad just because you used some random "tweaking" module and it underperforms. I don't think anyone forces you to donate, as well as barely there are any people donating, also i dont see where i ever asked on my kernel donations or anything, he's free to have a donation link in case everyone likes his work. Regarding using other's work, ever wondered why there is a thing called open source?, why wouldn't i use someone's great work in order to improve the kernel? i should do everything myself because you say so LOL. Please stop being delusional, before you ever write something on xda or anywhere else think twice. Im not here to beef with anyone i was explaining you why they block those "optimisers" that you are talking about, however you started talking about a lot of totally different things than what i said. Also if its that easy why don't you do it yourself and make your own kernel, by your analogy those "optimisers" would be bad too because how they can make a better job than qualcomm, samsung,oneplus blablabla LOL? You dont even know what they actually do. You share a lot of missinformation and you should stop. Have a nice day, i don't even know why i'm even arguing with someone like you, i wont reply to any of your answers after this.
EmanuelCN said:
First of all you have literally no clue on how a kernel works and what those modules do. There is no such thing as "building a better kernel than xiaomi, samsung, etc", no one would be ever able to make a kernel from scratch. The kernel itself firstly comes from Linux where's for our case on snapdragon Qualcomm modifies it and releases sources for each SOC then it goes to the specific manufacture that wants to create their phone and has to add the necessary code in order for their phone to work with the components they chose and usually they try to "tweak" the kernel which is literally doing worse 90% of the time. Qualcomm has a lot of stupid implementations baked into the kernel such as pl, hispeed, WALT, which are the reason the jitter its horrible with stock kernel, instead following mainline which is the best thing to be done. Benchmarks are useless because they are made to run on based on what usually the phones ship with, they are not designed to measure properly the performance of a phone therefore i have a lower score with my kernel but surprisngly jitter its 10 times better on "my' kernel, as well as normal usage and gaming too. I don't care what other devs posted about benchmakrs, i dont think my name is "casnova" or whatever, i dont talk for them i'm letting you know how it work. Also regarding "Your not developers you take other people's work and slap your name on it while changing as little as 1 thing or sometimes nothing", why dont you check github? why do you even talk without knowing what its really happening? its funny how people complain about dumb stuff, as i explained you that blocker its meant for people like you to not use x,y,z modules then to complain that the kernel is bad just because you used some random "tweaking" module and it underperforms. I don't think anyone forces you to donate, as well as barely there are any people donating, also i dont see where i ever asked on my kernel donations or anything, he's free to have a donation link in case everyone likes his work. Regarding using other's work, ever wondered why there is a thing called open source?, why wouldn't i use someone's great work in order to improve the kernel? i should do everything myself because you say so LOL. Please stop being delusional, before you ever write something on xda or anywhere else think twice. Im not here to beef with anyone i was explaining you why they block those "optimisers" that you are talking about, however you started talking about a lot of totally different things than what i said. Also if its that easy why don't you do it yourself and make your own kernel, by your analogy those "optimisers" would be bad too because how they can make a better job than qualcomm, samsung,oneplus blablabla LOL? You dont even know what they actually do. You share a lot of missinformation and you should stop. Have a nice day, i don't even know why i'm even arguing with someone like you, i wont reply to any of your answers after this.
Click to expand...
Click to collapse
First off I have made a couple of custom roms , twrp, and no I haven't made a kernel because it doesn't matter. For instances overclocking used to be a huge deal and now you don't see that ever. It's because it never did anything you could over clock it and if you watch your CPU in a kernel app like kernel auditor or Ex manager it would run at the stock frequencies much like the CPU does now if you try to lower clock speed or max it out. I'm aware that a kernel makes the hardware on the device work mainly the CPU and GPU and every OEM has to add their source to fit it. Here's how I know it's bull crap, now developers are saying kernel is enforcing and made with this tool chain as if the kernel isn't built with enforcing from the get go on stock like that's some feature they added. Me personally not worried about security I still prefer Permissive and yes I know it weakens security but in 5 years of doing this I have never heard of anyone hacking an Android phone. Even with the source code provided it's still difficult to make changes so I don't think people who could do it are going to waste their time. The monthly security patch is not a big deal it's funny that everyone thinks that is great when next month they will tell you last months security patch has security flaws like every month before it. So basically no patch has ever been secure.
If real features were added like double tap to sleep gesture
Color display RGB control
Sound modification so you can add gain on speakers, ear piece or headphones
Those days are gone because no one knows how to do it anymore on new software. Also most kernels say better performance and battery but neither the performance is any better nor does the battery last longer so I don't see how those claims are made. Wait I know because on Xda you can claim anything and everyone just says buttery smooth and long battery life thanks Dev. Before they even flash it.
EmanuelCN said:
First of all you have literally no clue on how a kernel works and what those modules do. There is no such thing as "building a better kernel than xiaomi, samsung, etc", no one would be ever able to make a kernel from scratch. The kernel itself firstly comes from Linux where's for our case on snapdragon Qualcomm modifies it and releases sources for each SOC then it goes to the specific manufacture that wants to create their phone and has to add the necessary code in order for their phone to work with the components they chose and usually they try to "tweak" the kernel which is literally doing worse 90% of the time. Qualcomm has a lot of stupid implementations baked into the kernel such as pl, hispeed, WALT, which are the reason the jitter its horrible with stock kernel, instead following mainline which is the best thing to be done. Benchmarks are useless because they are made to run on based on what usually the phones ship with, they are not designed to measure properly the performance of a phone therefore i have a lower score with my kernel but surprisngly jitter its 10 times better on "my' kernel, as well as normal usage and gaming too. I don't care what other devs posted about benchmakrs, i dont think my name is "casnova" or whatever, i dont talk for them i'm letting you know how it work. Also regarding "Your not developers you take other people's work and slap your name on it while changing as little as 1 thing or sometimes nothing", why dont you check github? why do you even talk without knowing what its really happening? its funny how people complain about dumb stuff, as i explained you that blocker its meant for people like you to not use x,y,z modules then to complain that the kernel is bad just because you used some random "tweaking" module and it underperforms. I don't think anyone forces you to donate, as well as barely there are any people donating, also i dont see where i ever asked on my kernel donations or anything, he's free to have a donation link in case everyone likes his work. Regarding using other's work, ever wondered why there is a thing called open source?, why wouldn't i use someone's great work in order to improve the kernel? i should do everything myself because you say so LOL. Please stop being delusional, before you ever write something on xda or anywhere else think twice. Im not here to beef with anyone i was explaining you why they block those "optimisers" that you are talking about, however you started talking about a lot of totally different things than what i said. Also if its that easy why don't you do it yourself and make your own kernel, by your analogy those "optimisers" would be bad too because how they can make a better job than qualcomm, samsung,oneplus blablabla LOL? You dont even know what they actually do. You share a lot of missinformation and you should stop. Have a nice day, i don't even know why i'm even arguing with someone like you, i wont reply to any of your answers after this.
Click to expand...
Click to collapse
I built 3 roms for 3 of my devices and I didn't start calling myself a developer because I had to get the vendor blob, kernel source, and lineage files from someone. I really think everyone just builds something or makes a flash able zip with a shell or script in it and immediately starts calling themselves a developer. I have owned the Poco f3 for a couple of weeks now and the TWRP thread is a waste of time. In the opening post it says backup and restore because they just copied and pasted the Normal twrp page. But than you search and almost nothing is being said about restore and you ask and no one will answer you and it's because it doesn't work and no one wants the devs feelings to be hurt. Well that's lovely but the point of a help thread is to discuss problems and solutions but it's became pointless the only thing threads are for is to say thanks for the software and to tell everyone that they don't spoon feed noobs to look it up and thats just stupid again that is why the Google search takes you to xda and that thread because you looked it up. Twrp would be able to backup and restore if xiaomi or Samsung made it because they would know how to make it backup slot a or active slot and restore it to inactive slot or whatever slot it needs to be because that's real development. I'm not trying to be a **** but it's gotten stupid I don't even bother looking through threads anymore because it's a serious waste of time because no one can say anything that might upset the person who made it. Well than don't make it I don't really care
a good kernel, I use it for Xiaomi.eu stable
Techguy777 said:
**** but it's gotten stupid I don't even bother looking through threads anymore because it's a serious waste of time because no one can say anything that might upset the person who made it. Well than don't make it I don't really care
Click to expand...
Click to collapse
You taught me something today. I "was" addicted to that, not any more...
shreyanshwithu said:
View attachment 5448595
The 90s kernel for Pocof3 / Redmi k40 and Mi 11x
Be careful if you have any damage to your device I would not be the cause because it is your choice to install my kernel on your device.
For your reassure, each release of this kernel is verified and tested to be the most stable possible
Kratos Edition​*First initial build
*upstream to 5.15.1
*optimized for Corvus and Xdroid
*Alpha build
*fix Fastcharging
*Don’t with A12 ROMs – Until Next Update
2.0 Changelogs:
*Upstreamed LTS to: 4.19.215
*Focused on Battery and Performance
*fixed Miui not showing up kernel version
*Fixed Low brightness
*Replaced touch drivers (thanks to @Dawfuk)
*Thanks To All My Testers
*Credits :
@Dawfuk
Eclipsia kernel
Optimus Drunk Kernel
1.0 Changelogs:
-----------------
*Initial build
*Based on Quantic
*Added support for A12
*Added CASANOVA Thermals
*Added new efficient frequencies
* compiled using proton clang 13.0.0
*Upstreamed LTS to: 4.19.214
*Upstreamed CAF to LA.UM.9.12.r1-13300-SMxx50.QSSI12.0
*Added a kernel space blocker to don't allow execution of magisk root optimizers such as LawRun, FDE.AI, etc.
Installation :
Backup Boot.img and Dtbo.img
Flash the kernel
Reinstall the recovery
Clean cache and dalvik
reboot
Credits :
*Casanova for Thermal
* Quantic kernel
* Immensity kernel
* Ram potagani
* Shreyansh (the 90s guy yt (Admin))
Download link: https://sourceforge.net/projects/the-90s-kernel/
Source of my kernel: https://github.com/Xtu-Fuszx/The_90s_Kernel
Donate: https://telegra.ph/Donate-to-90s-Guy-09-07
Click to expand...
Click to collapse
bro im following you on youtube. can you make your videos english or put some subtitles please. thanks
shreyanshwithu said:
View attachment 5448595
The 90s kernel for Pocof3 / Redmi k40 and Mi 11x
Be careful if you have any damage to your device I would not be the cause because it is your choice to install my kernel on your device.
For your reassure, each release of this kernel is verified and tested to be the most stable possible
Kratos Edition​*First initial build
*upstream to 5.15.1
*optimized for Corvus and Xdroid
*Alpha build
*fix Fastcharging
*Don’t with A12 ROMs – Until Next Update
2.0 Changelogs:
*Upstreamed LTS to: 4.19.215
*Focused on Battery and Performance
*fixed Miui not showing up kernel version
*Fixed Low brightness
*Replaced touch drivers (thanks to @Dawfuk)
*Thanks To All My Testers
*Credits :
@Dawfuk
Eclipsia kernel
Optimus Drunk Kernel
1.0 Changelogs:
-----------------
*Initial build
*Based on Quantic
*Added support for A12
*Added CASANOVA Thermals
*Added new efficient frequencies
* compiled using proton clang 13.0.0
*Upstreamed LTS to: 4.19.214
*Upstreamed CAF to LA.UM.9.12.r1-13300-SMxx50.QSSI12.0
*Added a kernel space blocker to don't allow execution of magisk root optimizers such as LawRun, FDE.AI, etc.
Installation :
Backup Boot.img and Dtbo.img
Flash the kernel
Reinstall the recovery
Clean cache and dalvik
reboot
Credits :
*Casanova for Thermal
* Quantic kernel
* Immensity kernel
* Ram potagani
* Shreyansh (the 90s guy yt (Admin))
Download link: https://sourceforge.net/projects/the-90s-kernel/
Source of my kernel: https://github.com/Xtu-Fuszx/The_90s_Kernel
Donate: https://telegra.ph/Donate-to-90s-Guy-09-07
Click to expand...
Click to collapse
Can i use this kernel for gaming ?
When I install stock miui, next LOS and my apps , every time I have different results with kernels. I do not understand how it is possible to have always different results for the same software for next tries.
It is third installation of all in my poco f3 and after testing some kernels, this one is a winner and consumes only 0.15% battery every hour during the night. Thank you for the kernel v2.
Edit.
The installation of this kernel reinstalled default LOS recovery. When I installed TWRP and again rooted the result was killed. I see 0.56% during night and this is worse result than own LOS kernel has. I lost a time for this kernel I afraid.