Here is kernel for Nokia 6.1, N7, N7plus and other snd630/660 aka "Nokia" phones.
VERSION = 4
PATCHLEVEL = 4
SUBLEVEL = 78
EXTRAVERSION =
NAME = Blurry Fish Butt
Click to expand...
Click to collapse
Also Sharp Aquos S2, S3 mini, S3 (but sharp dts is not included)
/* Sharp DTS can be separated from stock kernel and added manually
Or if you know how to do you can mod nokia dts to bring sharp dts , not much diff */
http://nokiaphones-opensource.azureedge.net/download/phones/Nokia6.1_V2.22J.tar.bz2
Thanks for sharing!
Is that kernel of nougat or oreo releases?
Psyl0w said:
Thanks for sharing!
Is that kernel of nougat or oreo releases?
Click to expand...
Click to collapse
VERSION = 4
PATCHLEVEL = 4
SUBLEVEL = 78
EXTRAVERSION =
NAME = Blurry Fish Butt
Click to expand...
Click to collapse
I believe it is latest one?
While unpacked kernel config of C10 gives ..
#
# Linux/arm64 4.4.78 Kernel Configuration
#
CONFIG_ARM64=y
CONFIG_64BIT=y...
Click to expand...
Click to collapse
I will experiment with Sharp Aquos S2 kernel making, but I don't have device to test
My new nick on 4pda is BestBeer!
heineken78 said:
I believe it is latest one?
While unpacked kernel config of C10 gives ..
I will experiment with Sharp Aquos S2 kernel making, but I don't have device to test
My new nick on 4pda is BestBeer!
Click to expand...
Click to collapse
I can help in testing. What can you improve in the kernel?
kkffiirr said:
What can you improve in the kernel?
Click to expand...
Click to collapse
Having a "native" twrp for sharp devices would be cool and piece of cake for Heineken
The best of the best would be to make operate B20 band of the modem (maybe kernel source helps for that or may be not). But it's challenging and I speculate he needs a device for that kind of reverse ingineering.
Any findings in the kernel yet?
If someone is interested, you can try with this source. Works fine on my Nokia 6.1. You are welcome to do PR as well. If someone is interested in testing, kindly tell me as well.
https://github.com/nokia-dev/android_kernel_nokia_sdm660
TheImpulson said:
If someone is interested, you can try with this source. Works fine on my Nokia 6.1. You are welcome to do PR as well. If someone is interested in testing, kindly tell me as well.
https://github.com/nokia-dev/android_kernel_nokia_sdm660
Click to expand...
Click to collapse
Already completed 4.4.153 for FIH 630/660 =P
Here on this Nokia Open Source page (https://www.nokia.com/phones/en_int/opensource) you can see that the devices (Nokia 6.1, 6.1 Plus, 7.1 and 7.1 Plus) have the same end of file (V4.15E.tar.bz2), does this indicate that everyone is the same? Also, is any of these compatible with the Nokia 7 TA-1041?
I'm sorry for the questions, but I'm a beginner on the subject!
sulamerica_auto said:
Here on this Nokia Open Source page (https://www.nokia.com/phones/en_int/opensource) you can see that the devices (Nokia 6.1, 6.1 Plus, 7.1 and 7.1 Plus) have the same end of file (V4.15E.tar.bz2), does this indicate that everyone is the same? Also, is any of these compatible with the Nokia 7 TA-1041?
I'm sorry for the questions, but I'm a beginner on the subject!
Click to expand...
Click to collapse
@theimpulson Any insight to above quoted questions?
sulamerica_auto said:
Here on this Nokia Open Source page (https://www.nokia.com/phones/en_int/opensource) you can see that the devices (Nokia 6.1, 6.1 Plus, 7.1 and 7.1 Plus) have the same end of file (V4.15E.tar.bz2), does this indicate that everyone is the same? Also, is any of these compatible with the Nokia 7 TA-1041?
I'm sorry for the questions, but I'm a beginner on the subject!
Click to expand...
Click to collapse
Oswald Boelcke said:
@theimpulson Any insight to above quoted questions?
Click to expand...
Click to collapse
Yes, they are the same. All Nokia and Sharp SDM660 devices (except Nokia 6.2 and 7.2) can boot from the same kernel and vendor images. My kernels itself boots on Nokia 6.1, Nokia 7.1, Nokia 6.1 Plus, Nokia 7 as I have got users having these devices test.
My kernel source: https://github.com/LineageOS/android_kernel_nokia_sdm660
It can be compiled using the latest GCC or Clang toolchain of choice.
Related
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
64bit kernel sources for Redmi2/2A/Prime
SHARING 64BIT WORKING KERNEL SOURCES FOR OUR DEVICE
WE ALL KNOW THAT OUR DEVICE HAVE A 64BIT CPU, BUT IT COULDN'T USE THAT 64BIT POTENTIAL BECAUSE OUR DEVICE WAS LAUNCHED WITH KK WHICH DO NOT SUPPORTS x64, BUT LATER XIAOMI RELEASED L FOR THE DEVICE BRINGING SUPPORT FOR MANY FEATURES LIKE VOLTE.
BUT ONE OF OUR DEVELOPER WAS ABLE TO CREATE 64BIT KERNEL SOURCES FOR OUR DEVICE. NAME "SEIRYU-2I"
HE ALSO CREATED WORKING MIUI8 64BIT BASED FOR OUR DEVICE. [url]https://goo.gl/2l1oqZ[/URL]
FEATURES: ARM64 BASED (PHEEWW)
SENSORS WORKS FLAWLESSLY
TOTALLY SUITABLE FOR VR AND DAYDREAM
BATTERY LIFE IS NOT COMPROMISED
AVAILABLE FOR BOTH MIUI AND CM (SEPERATE BRANCHES)
HAVEN'T FOUND ANY BUGS TILL NOW
NO PROBLEMS WITH VOLTE
SURPRISINGLY FAST
WE HAVE 64BIT KERNEL NOW!! SO, I WOULD LIKE TO INVITE ALL DEVELOPERS OUT THERE TO START WORKING ON 64 BIT ROMS LIKE, LIKE TESLA, DIRTY UNICORNS, AICP, CM14, ZYPHER AND DEVELOPERS OF OTHER GREAT ROMS OUT THERE AND KERNEL DEVELOPER LIKE JERRICA, LATTE AUTMN AND OTHERS.
[url]https://goo.gl/7AT5fS[/URL]
"THE SCORES HAVE BEEN UPDATED AS PROOF, GO GUYS TEST IT OUT YOURSELF"
AND PLEASE LET ME KNOW IF I AM MISSING SOMETHING.
SORRY FOR MY BAD ENGLISH and thank you :silly:
Let's go to the future. Thanks anyway.
Dyt199412syam said:
Let's go to the future. Thanks anyway.
Click to expand...
Click to collapse
lets see if the developers will work on this....
and if you can do please ping developers about this
fix the link dude
solomonR15 said:
fix the link dude
Click to expand...
Click to collapse
Fixed bro :highfive: :good:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Slight corrections required in the post
These sources are not x64. They are ARM64
x64 refers to 64 bit Intel CISC Chips like Atom whereas ARM64 Refers to 64 bit ARM RISC chips like Qualcomm SnapDragon and MediaTek Helios
Our Redmi 2 comes with Qualcomm ARM64 chipset ( albeit running a 32 bit OS) not x64 chipset
so make the necessary corrections
taalojarvi said:
slight corrections required in the post
these sources are not x64. They are arm64
x64 refers to 64 bit intel cisc chips like atom whereas arm64 refers to 64 bit arm risc chips like qualcomm snapdragon and mediatek helios
our redmi 2 comes with qualcomm arm64 chipset ( albeit running a 32 bit os) not x64 chipset
so make the necessary corrections
Click to expand...
Click to collapse
corrections made brother ... Btw thank you
didhiy said:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Click to expand...
Click to collapse
:fingers-crossed::good::highfive:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
seiryu.2i said:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
Click to expand...
Click to collapse
Thanks for your great works :good:
seiryu.2i said:
well thank you for posting this thread :d
if anyone can make this kernel better then it would be good, as i only have limited free time to see the world & don't have any pc or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like cm, then you can always pick any existing device tree for our device. Remove "force_32_bit=true" from boardconfig.mk and put "$(call inherit-product, $(src_target_dir)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(src_target_dir)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some c/c++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
Cheers
seiryu
Click to expand...
Click to collapse
lets hope .... If we could see cm 14 based on it
....
Is the cm branch in seiryu's repo good to go?
iamsubhranil said:
Is the cm branch in seiryu's repo good to go?
Click to expand...
Click to collapse
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
What? how can you get this performance? I only got 20876
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
Ya here's the point. Using just a 64bit kernel won't do anything much. The ROM has to be 64bit too.
iamsubhranil said:
ya here's the point. Using just a 64bit kernel won't do anything much. The rom has to be 64bit too.
Click to expand...
Click to collapse
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
abhishek 9650 said:
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
Click to expand...
Click to collapse
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
iamsubhranil said:
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
Click to expand...
Click to collapse
I guess the kernel sources has been ported from Redmi 3 (IDO) which has SD 616 and not SD 430.
As of 10th November 2016, Xiaomi has released the kernel sources for Xiaomi Mi Pad 1 to the masses. How soon can we expect someone to pick this device up and give us some sweet custom ROMs for the device?
I would really like to see ROM devs like Official CM team or Official Mokee team or other teams like them to pick this device up and free use from the bonds of Kitkat oppression.
I also wouldn't mind seeing a functional build of MIUI 8 on top of Android 6.0.1 for Mi Pad 1.
I'll start to work on it pretty soon but I will need time since this is my first rom developpement, if anyone wants to join :
Device Tree (from Nexus 9) : https://github.com/vickdu31/android_device_xioami_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
[/COLOR]
vickdu31 said:
I'll start to work on it pretty soon but I will need time since this is my first rom developpement, if anyone wants to join :
Device Tree (from Nexus 9) : https://github.com/vickdu31/android_device_xioami_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
Click to expand...
Click to collapse
The Nexus 9 has 64 bit K1 dual core 'denver' processor
Mipad has 32 bit quad core k1 processor
Nvidia Shield has a variant with 32 bit quad core k1 processor as well.
Would it be easier for you if you use the shield's device tree instead ?
Sure, didnt notice that.. Anyway i dont have much time now and if im alone i dont know if its ever gonna happend but if i keep everything in a clean way then its easy for more people to join. I'll change and anamyse device tree and see
Hello, please also take a look at the following GitHub repositories:
vartom/android_device_xiaomi_mocha
vartom/android_vendor_Xiaomi_mocha
There's a mostly working CM11 build from this developer, so I think these repos may be useful.
vickdu31 said:
I'll start to work on it pretty soon but I will need time since this is my first rom developpement, if anyone wants to join :
Device Tree (from Nexus 9) : https://github.com/vickdu31/android_device_xioami_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
Click to expand...
Click to collapse
Oh! Nice man. Thanks in advance. By the way, What should we look forward to ? A Marshmallow build? Or A Nougat Build ? Or a KitKat Build ?
Whatever it is, best of luck man. We will be looking forward to your good work.Best wishes for your success. A lot of hope will be riding on you.
I don't have time now so I will see how we should proceed. The point would be to gather devs in a group or something
vickdu31 said:
I don't have time now so I will see how we should proceed. The point would be to gather devs in a group or something
Click to expand...
Click to collapse
Okay man. Whatever it is, the effort is appreciated.
If you are creating any thread regarding the development, please share the link here. So would like to follow you guys along.
CM-13 for Mi pad
skroychowdhury said:
Okay man. Whatever it is, the effort is appreciated.
If you are creating any thread regarding the development, please share the link here. So would like to follow you guys along.
Click to expand...
Click to collapse
Already built the rom need testers Cm-13 link
Not so soon as u want
I was planning to buy this amazing device but i'm a little bit worried about the long term usage(atleast 2years) because of MIUI and Deminsity 1000+ .. so is there any chance of getting custom roms and gcam stable port? Because Redmi Note 8Pro is also on mediatek chipset but it has a lot of gcam port and custom rom support.
This is a phone made for China, I don't think there will be alot of custom roms. And I don't think there will be a gcam as well.
A Custom ROM basically doesn't depend on Android device's chipset.
The general approach to finding one is Googling for "YOUR_PHONE_MODEL ROM" or something similar, optionally including the wanted Android version. Try it out - you'll find what you want.
I will build rom for this line. There are international languages.
vandieutot said:
I will build rom for this line. There are international languages.
Click to expand...
Click to collapse
Very happy to see this and will be following eagerly @vandieutot . I really like my phone but the software is a big let down. Too many issues and workarounds required to get it working properly.
In preparation for this, could you tell me what will be required?
I currently have the K30 Ultra but its still standard phone. No root or anything else as yet.
Cheers. S'n'D
vandieutot said:
I will build rom for this line. There are international languages.
Click to expand...
Click to collapse
vandieutot said:
I will build rom for this line. There are international languages.
Click to expand...
Click to collapse
We will really appreciate it if you can build rom for this Redmi k30 ultra.... Please Help Us Develop Rom... Thanks...
vandieutot said:
I will build rom for this line. There are international languages.
Click to expand...
Click to collapse
Hi,
Planning to get this phone too... But no french language is kind of a draw back.
I do not build anymore (no time) but I can offer a build server in case you need something to build rather fast.
If you need it, send me a PM.
Regards.
vandieutot said:
I will build rom for this line. There are international languages.
Click to expand...
Click to collapse
If your rom safe to flash(no brick) im ready to help in testing.
If you can make a custom rom, that would be wonderful. Many k30u owners in China want it. There is a guy that made an Aosp rom for it, but he can't fix the bugs（fingerprint bluetooth）so if you can just help us, that would be great!
cxk菜虚鲲 said:
If you can make a custom rom, that would be wonderful. Many k30u owners in China want it. There is a guy that made an Aosp rom for it, but he can't fix the bugs（fingerprint bluetooth）so if you can just help us, that would be great!
Click to expand...
Click to collapse
where can i find this aosp firmware for redmi k30 ultra?
here's the QQ number: 235099024, that guy post the roms here.
Hello all does somebody knows how to build kernel from source for K30 Ultra for LineageOS
Here is complete public source so its expect to be many custom roms..
GitHub - MiCode/Xiaomi_Kernel_OpenSource at cezanne-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
i really hope that somebody make a rom for this device .
guys, do you want a modified miui or aosp similar?
nikitos2323 said:
guys, do you want a modified miui or aosp similar?
Click to expand...
Click to collapse
Yeah！
nikitos2323 said:
guys, do you want a modified miui or aosp similar?
Click to expand...
Click to collapse
I mean, the closer to stock android, the better.
Love you dude!
Alkowskey said:
I mean, the closer to stock android, the better.
Love you dude!
Click to expand...
Click to collapse
understood, though I could try to collect miui with languages and google. but about clean firmware like aosp not to me
if someone is interested in what tool can be used to build the firmware, I managed to build it with this tool. supports 10 android, 11 is not supported yet.
Unpacker Kitchen for Android(UKA)
version: 4.9.4 Last update of the program in the header: 04/06/2020 Developer: kory-vadim For the program to function, root privileges are required. Install: flash as Magisk module Short description: Unpacking, assembling and converting...
forum.xda-developers.com
nikitos2323 said:
guys, do you want a modified miui or aosp similar?
Click to expand...
Click to collapse
I'll take anything at this point, lol..
nikitos2323 said:
guys, do you want a modified miui or aosp similar?
Click to expand...
Click to collapse
AOSP, LineageOS native android clean rom not MIUI than own launcher Lighting launcher , substratum engine etc.
Can anybody compile lineage os 18.1 for this device?
I know there is the GSI ROM for this device and I have been using it, but it has bugs. Would be great to get a device specific rom. Thanks!
gnomiik said:
Can anybody compile lineage os 18.1 for this device?
I know there is the GSI ROM for this device and I have been using it, but it has bugs. Would be great to get a device specific rom. Thanks!
Click to expand...
Click to collapse
No or few development with soc Media Tek.
NOSS8 said:
No or few development with soc Media Tek.
Click to expand...
Click to collapse
What is the reason for this? Is media tek considered worse than snapdragon?
gnomiik said:
What is the reason for this? Is media tek considered worse than snapdragon?
Click to expand...
Click to collapse
Xiaomi has started equipping models with soc mediatek for the Indian market.
To have the source code for the development you have to pay a license to Mediatek for each model and then pay teams of developers, which would have increased the price of these phones in India and would not have been profitable.
(he was also banned in 2014 from selling xiaomi to soc mediatek in India).
Wh
gnomiik said:
Can anybody compile lineage os 18.1 for this device?
I know there is the GSI ROM for this device and I have been using it, but it has bugs. Would be great to get a device specific rom. Thanks!
Click to expand...
Click to collapse
Which GSI have you been using and what are the bugs that you've encountered?
NOSS8 said:
Xiaomi has started equipping models with soc mediatek for the Indian market.
To have the source code for the development you have to pay a license to Mediatek for each model and then pay teams of developers, which would have increased the price of these phones in India and would not have been profitable.
(he was also banned in 2014 from selling xiaomi to soc mediatek in India).
Click to expand...
Click to collapse
I've heard that Xaomi releases the source code of some of the Mediatek SoC .
Note :- Mediatek doesn't release the source code to the public , it only releases them to the smartphone manufacturers which uses their SoC.
NeXTT said:
Wh
Which GSI have you been using and what are the bugs that you've encountered?
Click to expand...
Click to collapse
GPS is broken in Lineage 18.1. Speaker volume is low for calls, but fine when using whatsapp / telegram. Also screen fades in the sun, very annoying.
gnomiik said:
GPS is broken in Lineage 18.1. Speaker volume is low for calls, but fine when using whatsapp / telegram. Also screen fades in the sun, very annoying.
Click to expand...
Click to collapse
How broken is the GPS? I've been meaning to try a GSI but am not sure which one to use. Any other bugs that you've encountered?
NeXTT said:
How broken is the GPS? I've been meaning to try a GSI but am not sure which one to use. Any other bugs that you've encountered?
Click to expand...
Click to collapse
Read my post here https://forum.xda-developers.com/t/gps-very-laggy-and-broken.4435975 . It doesn't matter which GSI rom you use, it is broken on all of them since the core comes from AOSP by phhuson and GPS is broken there as well.
rickviper said:
I've heard that Xaomi releases the source code of some of the Mediatek SoC .
Note :- Mediatek doesn't release the source code to the public , it only releases them to the smartphone manufacturers which uses their SoC.
Click to expand...
Click to collapse
As written above No or few
6 months between the source code and the first rom
https://c.mi.com/thread-2450980-1-0.html
https://forum.xda-developers.com/c/redmi-note-8-pro.9291/