Related
This is the kernel module for smb/cifs mount.(windows shares)
You need it for example for this: hxxp://forum.xda-developers.com/showthread.php?t=756158
I didn't found a compatible cifs.ko for samsung s anywhere so I had to compile it.
[recommended] cifs.zip - Eclair(2.1)
[recommended] froyo.zip - Froyo(2.2) - cifs.ko & slow-work.ko (insmod slow-work.ko first)
cifs_froyo_slow_work.zip - Froyo(2.2) - cifs & slow_work in one .ko Do NOT use this because its buggy (slow, reboots when rmmod)
could you pls explain what is this for? Experts needn't, but there're lots of newbies hangin aroud here, like me . Thanks
It's a kind of file system like ext2/3/4, for example.
Sent from my GT-I9000 using Tapatalk
This is the kernel module for smb/cifs mount.(windows shares)
You need it for example for this: hxxp://forum.xda-developers.com/showthread.php?t=756158
I didn't found a compatible cifs.ko for samsung s anywhere so I had to compile it.
Awsome. We can now mount samba shares! Freakin awsome
Sent from my Apple Newton 2100
You have my gratitude
Very usefull! thank you!
i'm back, when i'm trying an insmod i have cifs.ko : invalid module format
i use a jm5 samset 1.9f roms.
I use jm5 (mimocam's fix + root) and I've compiled the module from source-code provided by samsung (opensource.samsung.com) using arm-none-eabi-(Sourcery G++ from codesourcery.com). Maybe samset used something else which is incompatible.
ickyboo said:
Sent from my Apple Newton 2100
Click to expand...
Click to collapse
Bwahahahaha
ethanfel said:
i'm back, when i'm trying an insmod i have cifs.ko : invalid module format
i use a jm5 samset 1.9f roms.
Click to expand...
Click to collapse
Setenza said he'll add Cifs in the next SamSet release.
can you make one that is compatible with the Vibrant version? Either stock Vibrant kernel or any working kernel compatible.
Greatly appreciated
I've tried the module, but also get the "invalid module format" message.
However, I'm using JM5 + root using kernel 2.6.29 built on Fri Jul 30 15:12:44 KST 2010 armv71 GNU/Linux
Can you tell us for which kernel you've build this module?
thoriam said:
I've tried the module, but also get the "invalid module format" message.
However, I'm using JM5 + root using kernel 2.6.29 built on Fri Jul 30 15:12:44 KST 2010 armv71 GNU/Linux
Can you tell us for which kernel you've build this module?
Click to expand...
Click to collapse
I've compiled for kernel 2.6.29.2 using samsung's sources
my phone says he has kernel 2.6.29 [email protected] #1
I'm attaching the module compiled with latest toolchain I could find(binutils-2.20.1, gcc-4.5.1,newlib-1.18.0)
ctran81 said:
can you make one that is compatible with the Vibrant version? Either stock Vibrant kernel or any working kernel compatible.
Greatly appreciated
Click to expand...
Click to collapse
No idea if will work bc I don't have a Vibrant.
In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.
Thanks for your effort. I'm using JM5 +samset1.9f and couldn't get the cifsmanager to work with all 3 of your cif.ko . I've just dont know why the size the last 2 versions are huge compare to the first one? Thanks anyway. Hope you can come up with something.
thoriam said:
In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.
Click to expand...
Click to collapse
darkbyt3 said:
no idea if will work bc i don't have a vibrant.
Click to expand...
Click to collapse
thank you very much. It's working on my stock vibrant kernel! YOU ROCK SIR! (using attached vibrant.zip)
Now I can stream all my media files!
(I'm vary curious how you did this, if you can point me to some guides that would be awesome, (I can write some C/C++ code))
Works great for me - had been looking around to see if anybody had compiled the CIFS module for the Galaxy S. I started reading up on how to cross compile kernel modules myself but didn't get very far.
Anyway; I have a slight problem. while mounting and browsing from the terminal as root and through adb as non-root work, I can't seem to browse in any mounted folders actually on the device using either the stock 'My Files' or Astro which was what I was aiming to do.
What I do to mount said:
\\\\192.168.0.0\\Directory /sdcard/smbshare -o user=Username,pass=password,uid=1000,gid=1015
Click to expand...
Click to collapse
Without setting the user and group settings I can't browse unprivileged as everything in the share is 'owned' by root.
I also tried using mount -t smbfs //192.168.0.0/Directory /sdcard/smbshare with the same result.
Anybody else having a similar problem? Maybe it's just something obscure about my setup.
thoriam said:
In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.
Click to expand...
Click to collapse
Sorry for the noob questions:
- Can you please give more details on how to enable cifs in the kernel config?
- Is there a specific plate to copy the cifs.ko module?
- Is there a simple (one-click) way to install this?
- is the module dependent on the kernel version? has to be exactly the same?
- is there a easy way to check if it's working (I'm using cifsmanager and get some error saying cannot access device / folder not found -not sure about the exact message text)
Thanks in advance
https://github.com/untermensch/asus_kernels
getting started with building kernels:
http://source.android.com/source/building-kernels.html
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
update 11-21-2012:
add cifs, md4 modules
update 10-27-2012:
add data2sd support
uncap sd card DTR
add DUB-E100 revision C dev id
update 10-11-2012:
add zram support
add zram swap
add init.d
add OC kernel for the TF300TL, TF300TG
update 10-05-2012:
fix exFat mounting
revert MosChip MCS7830 driver
update 10-04-2012:
NTFS R/W via ntfs-3g
noauto_da_alloc added to fstab.cardhu
updated MosChip MCS7830 driver
added GPU overclock to 520Mhz from Motly-git
added user voltage control from Motly-git
possible I/O latency tweek
update 10-02-2012:
NTFS mount fail fixed (read only)
all I/O scheduler's included
support for MosChip MCS7830 based Ethernet adapters added
attached is the current snapshot of the repository.
changes:
debug stuff removed
OC to 1.6GHz
simple I/O scheduler as default
pegasuq governor added
zcache and cleancache enabled
CWM flash-able
Great move... lets see if someone dedicates some time to this wonderful gadget
Sent from Chanook 300 using Tapatalk 2
I'm running the source built kernel now and it appears that all the devices work
you may want to start a dev.. go ahead
untermensch said:
I'm running the source built kernel now and it appears that all the devices work
Click to expand...
Click to collapse
Hi !
..also I compiled the 10.4.2.9 kernel source code , and seems to be stable and no issue !
:good:
I have somme issue with dock keyboard ...as soon as it is connected = frequent reboot in any JB rom ( stock or custom !)
I hope this latest update 10.4.2.13 to resolve this ! :good:
untermensch said:
https://github.com/untermensch/tf300t_kernel
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
Click to expand...
Click to collapse
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Valantur said:
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Click to expand...
Click to collapse
the official ASUS kernel source is based on 3.1.10 so I am not porting anything, I am using
github to display the differences between the source released by ASUS and the base Linux
3.1.10 source it was built from. I do believe that the repository would be helpful to port to
a newer kernel, after the patches have been applied it is basically the ASUS source, but I
did fix a few things so it would build.
applied patch for the 10.4.2.13 kernel source
untermensch said:
applied patch for the 10.4.2.13 kernel source
Click to expand...
Click to collapse
Good .. that should fix the reboot issue which afaik occurs if you have a SD inserted in the dock
Sent using The Beast via Tapatalk 2
CPU over clocking to 1.6Ghz pushed to the repository
add
Code:
CONFIG_TEGRA_OC=y
to your .config
and remove
Code:
CONFIG_TEGRA_EDP_EXACT_FREQ=y
from your .config
or make xconfig and tick the TF300T Over Clocking check box
well that is nice. Can you post your OC Kernel for us?
mikaole said:
well that is nice. Can you post your OC Kernel for us?
Click to expand...
Click to collapse
here is the kernel plus the modules that go into /system/lib/modules
see this post for install instructions
http://forum.xda-developers.com/showpost.php?p=31944448&postcount=34
Thx, but Kernel is not flashable
untermensch said:
here is the kernel plus the modules that go into /system/lib/modules
Click to expand...
Click to collapse
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
normally you just flash the kernel in Recovery and you can copy the modules with root explorer. But flashing the Kernel fails in TWRP.
nothing I do will ever be "flashable" because people are stupid and will flash anything on to
any device.
install the kernel vi fastboot
Code:
fastboot flash boot kernel.blob
modules are optional install via adb while in recovery
Code:
adb shell sh -c "rm -fr /system/lib/modules/*"
then cd into the directory with the modules
Code:
adb push ./ /system/lib/modules
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
thx, just saw the blob myself. Its already done
Works fine here. Big THX
untermensch said:
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
Click to expand...
Click to collapse
Two other questions:
1 - I have the TERP recovery, is that a problem?
2 - OC frequencies can be selected?
1. no problem at all, have TWRP, too
2- Yes can be selected in the OC app like set CPU or Antutu Master
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r27. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
2015/04/01
please visit http://forum.xda-developers.com/showpost.php?p=59827552&postcount=8 to see more information:
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108/.157 or any ROM based on it.
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
sharonliu said:
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r25. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108 or any ROM based on it
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
Click to expand...
Click to collapse
cocafe mentioned that the wifi modules has to be original from stock ROM, so i replaced them before flashing the kernel, but wifi does not turn on.
thank you for reporting this problem, it should be resolved next release.
Nice to see another stock based kernel around!
Only .108 or also .157?
Schlengge said:
Nice to see another stock based kernel around!
Only .108 or also .157?
Click to expand...
Click to collapse
from cocafe´s post:
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Click to expand...
Click to collapse
so imho for .157 too
sharonliu said:
thank you for reporting this problem, it should be resolved next release.
Click to expand...
Click to collapse
i think this solves the problem: LINK
moonryder said:
i think this solves the problem: LINK
Click to expand...
Click to collapse
Thanks for the information. Just like DooMKernel, my goal is no need to compile wlan module. If I am not luck, I will build the wlan module in this weekend.
Changelog :
wlan is working
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Insturaction:
If you want back to stock kernel, remember reboot to recovery and flash stock wife modules.
sharonliu said:
...flash stock wife modules.
Click to expand...
Click to collapse
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
moonryder said:
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
Click to expand...
Click to collapse
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
sharonliu said:
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
Click to expand...
Click to collapse
ok
btw flashed new build from today and wifi works like a charm.
thx
Thanks for this kernel
The only thing I noticed is that the notification light turns white when the battery is full
Normal it's green
Don't know if it's I bug but I noticed it
It's not a bug. Cocafe made it so the led will notify you of the real eoc. You can change the led color though here I believe "/sys/kernel/qpnp-charger/eoc_led"
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
moonryder said:
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
Click to expand...
Click to collapse
get terminal emulator from the play store and type it in there
or use adb shell
adb shell
su
Click to expand...
Click to collapse
it should work if you type these scripts. In my opinion, DoomKernel is the best custom kernel, bu nice to see another stock based kernel around.
sharonliu said:
...DoomKernel is the best custom kernel....
Click to expand...
Click to collapse
you are so right bro
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
a1b2c3901 said:
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
Click to expand...
Click to collapse
why do you use exFAT format?
Do you have files > 4GB in use?
moonryder said:
why do you use exFAT format?
Do you have files > 4GB in use?
Click to expand...
Click to collapse
Sometimes I will watch movie in the journeys, and that files may be oversize.
a1b2c3901 said:
Sometimes I will watch movie in the journeys, and that files may be oversize.
Click to expand...
Click to collapse
get "MLUSB Mounter" from the play store, you can use the USB hard drive (formatted NTFS, exFAT).
Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?
Hello,
it's possible to compile N for the wave... But I don't really see the use in it...
Wave's ram is too low....using android 7 with it will be so slow
Honestly best ROM made for wave till now is ICS....it is fast and uses less ram
Best Regards
yes
yesterday , galaxy s1 has released cm 14
so lt will be posible
---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------
ghostbiceps said:
Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?
Click to expand...
Click to collapse
yes
yesterday , galaxy s1 has released cm 14
so lt will be possible
Very possible. @fire555 you can apply commits from kernel N of S1 to Wave and port CM14 of S1 to Wave?
You can tell me version of gcc to build kernel for wave? Thanl you
i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank
thinhx2 said:
i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank
Click to expand...
Click to collapse
Using GCC 4.7 should be fine. Maybe newer too.
fire855 said:
Using GCC 4.7 should be fine. Maybe newer too.
Click to expand...
Click to collapse
You can send me link of gcc 4.7?
@fire855
thinhx2 said:
@fire855
Click to expand...
Click to collapse
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.
xc-racer99 said:
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.
Click to expand...
Click to collapse
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs
thinhx2 said:
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs
Click to expand...
Click to collapse
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)
xc-racer99 said:
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)
Click to expand...
Click to collapse
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try
thinhx2 said:
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try
Click to expand...
Click to collapse
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.
xc-racer99 said:
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.
Click to expand...
Click to collapse
I no build rom,because wave can run rom of s1 normal with kernel of wave. I think no need build rom. I only merge new commits of kernel 7.0 s1 to wave. I patched comeplet but i have problem. I will try tonight
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 ...