Develop Bugs

Open Source Bootloader for Redmi 1S

Hey folks! :highfive:
Source code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
Github repo: https://github.com/redmi1s-dev/lk
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-27

What's the purpose of this?

sinnerz2000 said:
What's the purpose of this?
Click to expand...
Click to collapse
I think you can achieve dual boot with this. Not sure tho.

Syssx said:
I think you can achieve dual boot with this. Not sure tho.
Click to expand...
Click to collapse
If you really want, you can boot WinRT too.

hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master

where is the sources?

thewisenerd said:
hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master
Click to expand...
Click to collapse
pgreed said:
where is the sources?
Click to expand...
Click to collapse
Take a look at Downloads tab.
Grub is already ported, and working. :angel:

balika01 said:
Hey folks! :highfive:
Soruce code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-26
Click to expand...
Click to collapse
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for

balika01 said:
Take a look at Downloads tab.
Grub is already ported, and working. :angel:
Click to expand...
Click to collapse
There ain't no 'downloads' tab :|

rohit choudhary said:
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for
Click to expand...
Click to collapse
You can make it, but you have to repart your nand. This is dangerous, and you can easily make a brick.

Reversed? How you reverse engineered on Bootloader?

Forever Alone said:
Reversed? How you reverse engineered on Bootloader?
Click to expand...
Click to collapse
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.

balika01 said:
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.
Click to expand...
Click to collapse
can you do it with kernel too bro????

Hey.. can someone fetch me link of working build of grub? Caz I got some multiboot stuff coming up for our armani.

Multiboot isn't really that useful on our phones since we'll be flashing android anyway, if we had say Ubuntu and android dual boot then that would be something

We got grub workin on our device.... Ubuntu ain't no impossible-thing I guess... mate... Just to kick things off.. android dual boot would do.

device with Same configuration exists with kernel source out
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100

Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Belive me it's not that simple.

Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Source for msm8226 has been released by qcom. When i try to boot it, it just crash whitout last_kmsg. (I think stg free it, before lk starts running. F*ck xiaomi.)
(In code msm8228 same as msm8226, thats why cpuz says msm8226.)

Most Apps reads from what data are given in the system files.
Lets say, the build.prop itself says msm8226, and if you dig around in the / (root) folders, almost all files are for msm8226 cpus.
I still dont get, why the hell did XIAOMI implemented msm8226 drivers and other details for msm8228 cpu.!!!!!!

MoKee Open Source 51.1 (Unofficial)

MoKee Open Source 51.1 (Unofficial)
STATUS: Abandoned.
Features:
Odexed, quicker first boot
March security update
Archived Downloads
Sources

Chance to get a new experience. xD

Very good , exellent rom my friend

Great work! It's very pure like AOSP? Or have themes too?

lohhans said:
Great work! It's very pure like AOSP? Or have themes too?
Click to expand...
Click to collapse
it is a CM-based rom so it has CM themes app.

tank0412 said:
it is a CM-based rom so it has CM themes app.
Click to expand...
Click to collapse
OK, thks, sorry for the ignorance haha...

Another custom rom...great job dev.
Sent from my ASUS_T00F using Tapatalk

For experiment i ported my CM12.1 kernel to this Mookee rom:
https://drive.google.com/file/d/0B-Fin8UxrD6PTjRHbVBDTUY2dWM/view
This kernel was compiled from X Anwar source so it has a ton governors + i/o stuff.
Note: MTP is working.
Maybe it will be needed for someone.
Note2: Kernel from other roms will be incompatible with this Mokee rom without ramdisk bring up for Mokee.

NOTICE
Update your Kernel
The kernel I've released with the first build was a SELinux Enforcing kernel (which I don't give support anymore).
I've forgot to update command-line, sorry.
A new SELinux Permissive kernel has been just released, and the SELinux Enforcing kernel was deleted.
Now, download bootMK-20160324_2-SELinuxPermissive.img and flash it:
Code:
fastboot flash boot bootMK-20160324_2-SELinuxPermissive.img
fastboot erase cache
fastboot reboot

witch wakelocks i need block to get better battery perfomance?

karabeen said:
witch wakelocks i need block to get better battery perfomance?
Click to expand...
Click to collapse
Nothing.
If you disable system wakelocks, device will not turn on due call or something like this. (IMHO)

can you try carbon os

shobint7 said:
can you try carbon os
Click to expand...
Click to collapse
Maybe one day, I just can't maintain many ROM's for Zenfone. I'm sorry
Plus, that soon I'll be moving to Motorola

Very good!

dgadelha said:
Maybe one day, I just can't maintain many ROM's for Zenfone. I'm sorry
Plus, that soon I'll be moving to Motorola
Click to expand...
Click to collapse
Good choice there!

tank0412 said:
For experiment i ported my CM12.1 kernel to this Mookee rom:
https://drive.google.com/file/d/0B-Fin8UxrD6PTjRHbVBDTUY2dWM/view
This kernel was compiled from X Anwar source so it has a ton governors + i/o stuff.
Note: MTP is working.
Maybe it will be needed for someone.
Note2: Kernel from other roms will be incompatible with this Mokee rom without ramdisk bring up for Mokee.
Click to expand...
Click to collapse
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk

Ale uto said:
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
No.

Ale uto said:
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
This kernel version above will work on Mokee only.
But this version below is working on my CM-based roms:
https://drive.google.com/open?id=0B-Fin8UxrD6PZWt6UWIxQmdMT3M
On dgadelhas CM12.1 builds it can boot but it is not guaranted. (It can have troubles with SElinux)

tank0412 said:
This kernel version above will work on Mokee only.
But this version below is working on my CM-based roms:
https://drive.google.com/open?id=0B-Fin8UxrD6PZWt6UWIxQmdMT3M
On dgadelhas CM12.1 builds it can boot but it is not guaranted. (It can have troubles with SElinux)
Click to expand...
Click to collapse
Being Permissive I guess it will work right

how i can flash .img without computer
plz give me instruction

[KERNEL] -> tegra-3.18_unified_dragon_kernel_11_v201218 (DISCONTINUED)

Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy

flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.

dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14

followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.

Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!

New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers

followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/

redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers

Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.

nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks

followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/

followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.

redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.

nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img

redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.

NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:

NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?

redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !

followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!

Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers

Port for Kali.Nethunter kernel

Thread closed.
For new thread , go to this link.
https://forum.xda-developers.com/le...t/kernel-kali-nethunter-t3813746/post77016833
I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!

Atharva Ambre[AT said:
;76155798]I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Click to expand...
Click to collapse
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready

Atharva Ambre[AT] said:
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Click to expand...
Click to collapse
Wrong architecture maybe? Z2 is arm64.

JashanjotSidhu said:
Wrong architecture maybe? Z2 is arm64.
Click to expand...
Click to collapse
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try

Atharva Ambre[AT] said:
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Click to expand...
Click to collapse
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?

JashanjotSidhu said:
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
Click to expand...
Click to collapse
Ya sure
Note the major errors are in proc.c

Atharva Ambre[AT] said:
Ya sure
Note the major errors are in proc.c
Click to expand...
Click to collapse
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.

JashanjotSidhu said:
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
Click to expand...
Click to collapse
Oh I'm sorry my bad here's the right file

Atharva Ambre[AT said:
;76282414]Oh I'm sorry my bad here's the right file
Click to expand...
Click to collapse
Sorry again same wait take this

Atharva Ambre[AT] said:
Sorry again same wait take this
Click to expand...
Click to collapse
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.

JashanjotSidhu said:
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
Click to expand...
Click to collapse
Will try and I got it from github its the open sources kernel , its available on most of the ROM first page , I got it from aex intro page on XDA
U won't find it bcoz the CPU freq file is inside Linux/include/CPU so its not android based file it's the main working of Linux so u won't find any specific chip based also it won't mention sd820 bcoz its open source u can port it as long as u are able to get it right without bugs its an open source so its open for many devices and many chipsets.

Update :
I tried again from start I think its the problem with the compiler of ndk will download older version and try out tomorrow...still getting many other errors while compiling from the source kernel
Pls provide me the link of latest stable ROM with it sources updated!thank you!

Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel

Atharva Ambre[AT] said:
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Click to expand...
Click to collapse
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.

JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
Idk I have just right now running Ubuntu on VM I m downloading the files I don't think so that the problem is associated with kernel version bcos the thing is many new Android devices like one plus 3 and other many update android version devices like nexus have official nethunter support so latest android means the kernel will be upgraded to more newer version such as 3.18.xx and all so is our z2 plus to the same version ....anyways gonna give a try in Ubuntu or else have to wait till I get a proper source for kernel.
Can u suggest any good source for this project ?
I'm currently using the Oreo ROM and the source of the kernel is DDrb0h kernel which is the branch of lineage 15.1.

Also I have identified the major error which is in CROSS COMPILE step for android ndk idk why but in Kali Linux I'm not able to get CROSS COMPILE so kinda in lil problem...

JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
I think the problem is associated with the kernel sources same error on ubuntu

Update
Tried my best to compile yet ran into another error
Changed the sources to latest treble one
I got new error with arm-linux-androideabi- gcc error some command is invalid ....I require a little guidance here . So kernel developers pls show me which version of ndk shld I use and sources shld I refer and what extra commands shld I run?

@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..

SteelBodyX said:
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
Click to expand...
Click to collapse
Thank you for ur suggestion. Ya I haved pm him already but didn't receive any update from him and also the work is done.I have made the changes for the project just one step I'm lagging is compiling it......then its free for distribution here.

Roomservice for whyred

Can anyone tell me what i should add in roomservice for whyred, device, kernel and vendor are clear but what else do i need?

sgspluss said:
Can anyone tell me what i should add in roomservice for whyred, device, kernel and vendor are clear but what else do i need?
Click to expand...
Click to collapse
Roomservice? What?

LeekGeek said:
Roomservice? What?
Click to expand...
Click to collapse
roomservice = additional repo

sgspluss said:
Can anyone tell me what i should add in roomservice for whyred, device, kernel and vendor are clear but what else do i need?
Click to expand...
Click to collapse
murigny64 said:
roomservice = additional repo
Click to expand...
Click to collapse
Oh you're making rom or something?

LeekGeek said:
Oh you're making rom or something?
Click to expand...
Click to collapse
i've made builds for wiko peax, alcate lIdol 3, moto g1, g3 and g4. but nothing since a year.
sorry, no more ubuntu for dev on my 2nd pc, only tvheadend backend dvb-t server
:crying:
what do you want to build?

Yes but not public, just build my own lineageos with needed changes for myself.
Actually started a build half hour ago and looks fine sofar (40% done). So did not think that i need more in roomservice.
If everything working as i hope will try to open an gerrit code review (never done) that everyone can use it in offical rom.
Sent from my Xiaomi Redmi Note 5 Pro using XDA Labs

(OOPS - obsolete meanwhile)
I'm quite sure you did already this:
https://github.com/search?p=1&q=xiaomi_whyred&type=Repositories
There's tons of stuff at least....
On reddit there's also much of activity:
https://www.reddit.com/r/LineageOS/search?q=whyred&restrict_sr=1
But no infos about repos. Have you already tried building?
Still have to wait for 26 hours for unlocking the bootloader - getting impatient.... :silly:

Yeah building is running now reached 70% so very soon finished, if its booting then all be fine *fingerscross*.
Just add code to disable notification led systemwide, missed that feature in offical one...
Also add some system.prop tweaks for wifi to save a bit more battery.
Will test everything and if its working will try to open gerrit code review that you'll find it also in offical one, but dont want to commit it without testing it.
About bootloader its annoying but its worth, miui is not bad but lineage is better
Edit:
The patch for notification led is working fine, already commit it for offical one, about wifi battery need to test it more, if its also working fine will commit it also to the offical one.
Sent from my Xiaomi Redmi Note 5 Pro using XDA Labs