Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
Important links:
slimroms.org - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for S6 from here
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Thanks!
The entire team who helped with the device tree to make this device get CM. Hats off guys. Really appreciate your hard work.
For dual boot, kindly follow this link.
If you have any other queries, kindly see this link for any issues other users face before posting here.
Working and Not working:
Everything as in CM
/* Supported devices */
Galaxy S6 International (SM-G920F/I, zerofltexx)
Galaxy S6 SK (SM-G920S, zeroflteskt)
Galaxy S6 KT (SM-G920K, zerofltektt)
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRom 6.0 for Galaxy S6 , ROM for the Samsung Galaxy S6
Contributors
a2441918
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2015-12-21
Created 2015-12-16
Last Updated 2015-12-23
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
virulentt said:
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
Click to expand...
Click to collapse
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
a2441918 said:
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
Click to expand...
Click to collapse
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Dude you dont get it. According to XDA you should publish a source for the kernel and I did. Go ahead with the link I posted and it will direct you to the kernel source. It is not necessary that the kernel should belong to Slim.
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Nevermind keep it coming
Sent from my SM-G920F using Tapatalk
bio4554 said:
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Click to expand...
Click to collapse
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
a2441918 said:
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
Click to expand...
Click to collapse
It's like steeling the bigmac sauce's receipe to make your own burger restaurant, but saying that you use a different bread.
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
a2441918 said:
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
virulentt said:
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
Click to expand...
Click to collapse
You could have pointed that out in the first post itself rather than us spamming this thread. I will remove the download link and keep this thread closed for now.
virulentt said:
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Click to expand...
Click to collapse
The only source required to be posted by GPLv2 and XDA requirements is kernel source. Also Slim and CM both have posted open permissions to build.
New build up. See OP for download link.
Download Link is dead for me.
a2441918 said:
New build up. See OP for download link.
Click to expand...
Click to collapse
ripv2 said:
Download Link is dead for me.
Click to expand...
Click to collapse
Try it out now mate.
Up and reachable Ill give it a shot!
a2441918 said:
Try it out now mate.
Click to expand...
Click to collapse
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
bigbossclk said:
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
Click to expand...
Click to collapse
I guess its usable. But a different build for S6 Edge is in the works.
Doesnt Boot on my 920f latest recovery clean install with and without gapps. Never finnishing Boot animation.
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Hi,
this is the development thread for LineageOS development. The first release is out and this thread is for developer collaboration!
Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches!
HELP NEEDED
mixer_paths_tasha.xml and audio_platform_info.xml need tweaking
VoIP needs testing
WifiDisplay support
VoLTE (I can't test this)
Device Trees
https://github.com/cryptomilk/android_kernel_sony_msm8998
https://github.com/cryptomilk/android_device_sony_common-treble
https://github.com/cryptomilk/android_device_sony_yoshino
https://github.com/cryptomilk/android_device_sony_lilac
What about the bootloader?
blackknightavalon said:
What about the bootloader?
Click to expand...
Click to collapse
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
android_fury said:
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
Click to expand...
Click to collapse
And where, exactly, is the tutorial for that? It's not officially supported by Sony yet.
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
android_fury said:
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
Click to expand...
Click to collapse
I just checked a few minutes ago. XZ1C's not on there.
Good news ！
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
Great news! Thank you so much for your efforts to bring us LOS for this really awesome compact beast.
Thank you so far, modpunk! Looking forward to it. The phone is great, but stock rom leaves some things to be desired...
Thanks bro, just do it!
Regarding unlocking: I selected X Compact and followed the instructions. Everything worked perfectly and I'm now running AOSP.
Code:
----- Made recovery image: recovery.img --------
#### make completed successfully (11:06 (mm:ss)) ####
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Gairtial said:
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Click to expand...
Click to collapse
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
modpunk said:
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
Click to expand...
Click to collapse
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Gairtial said:
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Click to expand...
Click to collapse
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
modpunk said:
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
Click to expand...
Click to collapse
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Gairtial said:
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Click to expand...
Click to collapse
You get the errors with -Wmaybe-uninitialized which is a relatively new gcc feature. The Sony 'kernel' repo is their Proof of Concept repository. Yes, sure they are working on it it makes totally sense to try things out there first!
I dunno what EAS is or means ...
Hi all out there.
I just extracted the kernel source code of Samsung Galaxy A80 (SM-A805F/DS) with ROM Base: A805FXXU4BTC3, and I pushed it on Github.
It took few days to upload it because it almost had a 70,000+ files and roughly 1.3GB+ all files.
I made it as public repository and uses GPL 3.0 LICENSE(which is recommended by samsung open source) to make it easy to fork/modify and clone it.
Kernel Source Code is Under GPL 2.0 LICENSE
Here is the link https://github.com/firemax13/android_kernel_samsung_sm6150-sm7150.
You can contact me through github for collaborations. You can also make any custom kernel using this code.
You can clone this by using this git link https://github.com/firemax13/android_kernel_samsung_sm6150-sm7150.git
Thank you all.
Android 10 Kernel Source Code Uploaded Through GITHUB!
* Source code is both under GPL 3.0 & APACHE 2.0 LICENSE
* ROM BASE: A805FXXU4BTC3
*
firemax13 said:
Reserved.
Click to expand...
Click to collapse
Have you pulled it from Android Q? Of yes i'd likes ti fork it
Fulbert95 said:
Have you pulled it from Android Q? Of yes i'd likes ti fork it
Click to expand...
Click to collapse
No, this is still Android Pie based. Samsung Open Source still not providing source code for Android 10, but soon they will release it just don't worry, if the samsung will release I'm gonna pull those new things to github. Gonna update you if I pulled the Android 10 source code to github.
Galaxy A80 Android 10 Source Code
https://opensource.samsung.com/uploadSearch?searchValue=SM-A805F
motobenny said:
https://opensource.samsung.com/uploadSearch?searchValue=SM-A805F
Click to expand...
Click to collapse
Uploaded!
You can now clone it or fork it from my github link that u can found from the first post. It took me 2 hours to upload it, it has 1.3gb when I unpacked it. Feel free to contact me for the link problem or collaboration.
Fulbert95 said:
Have you pulled it from Android Q? Of yes i'd likes ti fork it
Click to expand...
Click to collapse
Updated to A805FXXU4BTC3/Android 10. Check my first post for the github link.
cant download
I want custom rom download
You have to wait for Realme to release kernel sources first
does anyone know how long they wait until they publish a new kernel and is there a way to speed that up? Their github seems to be updated constantly, just not with this kernel
Looks like they've created a new repo for this phone, however there's nothing there yet...
GitHub - realme-kernel-opensource/realme8_C25_C25s_Narzo30_Narzo50A_AndroidR_kernel_source
Contribute to realme-kernel-opensource/realme8_C25_C25s_Narzo30_Narzo50A_AndroidR_kernel_source development by creating an account on GitHub.
github.com
ban_bacon said:
Looks like they've created a new repo for this phone, however there's nothing there yet...
GitHub - realme-kernel-opensource/realme8_C25_C25s_Narzo30_Narzo50A_AndroidR_kernel_source
Contribute to realme-kernel-opensource/realme8_C25_C25s_Narzo30_Narzo50A_AndroidR_kernel_source development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
there are pure I went to the link and there are files
do you know if any rom will be made? will anyone take it?
I hope someone makes a custom rom, chances are low tho, since this community is not very active
It seems that someone Is developing a LineageOS 20 ROM for RMX3242.
Kernel Source code for Realme Narzo 30 5g
https://github.com/realme-kernel-op...5G_Narzo-30-5G_V13_Q3i-AndroidT-kernel-source