Related
FOR DEVS ONLY
THIS IS A DEVELOPMENT THREAD FOR PORTING THE LINUX 3.10 KERNEL TO THE HTC ONE S (VILLE) S4 EDITION
MODERATORS PLEASE DELETE ANY POSTS THAT ARE NOT RELATED TO THE DEVELOPMENT OF THE KERNEL (OTHER THAN THESE FIRST POSTS USED TO CREATE SOME DOCUMENTATION)
XDA:DevDB Information
3.10 Kernel for the HTC One S, Kernel for the HTC One S
Contributors
javelinanddart
Kernel Special Features:
Version Information
Status: Testing
Created 2015-01-15
Last Updated 2015-01-15
This thread is a development thread for porting the Linux 3.10 Kernel to the HTC One S
All Devs are welcome to step forward
https://github.com/javelinanddart/android_kernel_3.10_ville
This will be done from the CM 12 Source Code
This IS NOT an easy task, it will take a lot of time and lot of things will need to be changed
CyanogenMod might have to be rebuilt from source to have this work properly
Look at the mergeconflicts.txt to look for things to fix, look at the fixedconflicts.txt for things that are fixed
Advantages:
-Officially Supported (3.10 is what the Nexus 6 & 9 and Android Wear Devices are Using)
-Future Android Compatibility (Android Framework and Kernel are Decoupled but Still Matters)
-Better Performance (Somewhat)
-Bragging Rights (xD this is a joke)
-Better and Newer Drivers
-More Features
-More Optimized
-Longer Support Date (Most Likely)
-Most Future Devices will Run 3.10 Kernel (Keeps our Device Current)
-Lower RAM Usage
-Support for F2FS (a faster file system for nand flash storage devices)
Contributor List
@intervigil (Ethan Chen)
@AKToronto
@mikronac.ns (Mikronac)
FAQ
Why?
Because I can (lol)
Check the Advantages list
Changelog
Initial Upload of Source
Merge tag v3.10
Resources
http://elinux.org/Kernel_3.4_to_3.10_porting_guide
A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product
javelinanddart said:
A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product
Click to expand...
Click to collapse
yeah, I am just looking in it...
mikronac.ns said:
yeah, I am just looking in it...
Click to expand...
Click to collapse
1 sec then, I'm merging with the aosp source rather than mainline linux because it includes some android specific changes
Look at the mergeconflicts.txt or try compiling it.....
My god... never seen THAT many errors in the Kconfigs
wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware
dd98 said:
wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware
Click to expand...
Click to collapse
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too
javelinanddart said:
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too
Click to expand...
Click to collapse
I'll gladly help but still only getting there on the kernel development, hope I have some free time
dd98 said:
I'll gladly help but still only getting there on the kernel development, hope I have some free time
Click to expand...
Click to collapse
What's your github username? I'll add you as a collaborator rather than pull requests. It works faster
@javelinanddart F2Fs already works on Ville I already ported it [emoji1]
Flashalot said:
@javelinanddart F2Fs already works on Ville I already ported it [emoji1]
Click to expand...
Click to collapse
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?
javelinanddart said:
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?
Click to expand...
Click to collapse
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp
Flashalot said:
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp
Click to expand...
Click to collapse
Thanks. If we can switch to F2FS and use a Universal TWRP, developers will have a better time on source-based ROMs. It will also help speed up the file system actions. I tried compiling twrp but I couldn't figure it out
What source are you editing the 3.4 kernel source or the 3.10 kernel source ?
Wahaj.47 said:
What source are you editing the 3.4 kernel source or the 3.10 kernel source ?
Click to expand...
Click to collapse
"3.10 porting"
Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?
rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app
haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up
[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.
Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu
Man, you do a lot of great work.
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
left it open haky..maybe they are busy for now..we need it bro
haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested
haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work
why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others
3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.
3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...
no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.
Coconut Kernel for HAVOC OS - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is tested on HAVOC OS 2.2 - 2.4 PIE. This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
The kernel should also work on every ROM that Holydragon kernel supports.
Requirements
Oxygen OS 5.0.8 firmware is required. The wifi adapter wont work on older firmwares. Those who are using Havoc OS would most probably be on 5.0.8 firmware so this is just a remainder for others and/or anyone who have trouble making this work.
How to install
Make sure that you are rooted with magisk/supersu/any superuser
Download kernel from attachment and flash in TWRP Recovery
Reboot and download any terminal app like Termux
Plugin the USB Wifi card and open Termux
Type the command su
Then type ifconfig wlan1 up
This is how you can test whether it works or not
The kernel works fine with Nethunter as well as other chroot applications like Linux Deploy.
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Credits
@HolyAngel for HolyDragon Kernel Source
Source
https://gitlab.com/HolyAngel/OP3
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Victroid said:
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Follow the tutorial above for kernel building.
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.?
DoN LoUhI said:
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.
Click to expand...
Click to collapse
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
fredrickz said:
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
Click to expand...
Click to collapse
Fair enough, thank YOU:laugh::good:
You explicitly mention this:
This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
Click to expand...
Click to collapse
And the kernel source points to:
https://gitlab.com/HolyAngel/OP3
Click to expand...
Click to collapse
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Click to expand...
Click to collapse
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
anupritaisno1 said:
You explicitly mention this:
And the kernel source points to:
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Click to expand...
Click to collapse
I dont want to break any gpl.. the thing is that all my changes are local. Im not used to github. This kernel and all others i posted werr just for my own use. I have been using @ZaneZam kernel for oneplus3. But the Oreo kernel wasnt working fine. Thats the reason i tried to compile one my own. I shared it with a friend of mine some time ago and he insisted that i should post it so that others may also benefit. The kernel i posted doesn't have tonnes of feature list because i mostly stick to stock. I just added the wifi drivers and was using them. My friend asked me to add support for DriveDroid and i just did that. I don't know much about git and didnt have time to learn.
If this is against the rules then maybe ill post the source later. Im currently out of town.
for now if you want to know what changes i did,
1. Prepare the kernel for standalone build (except holydragon kernel)
2. Added just the wifi drivers mentioned in the nethunter wiki. I didnt add support for usb Bluetooth or sdr.
3. Added support for DriveDroid from official post in xda making changes to adapt the code to 3.18 kernel.
4. Added a fancy name to the kernel.
5. Published it.
DoN LoUhI said:
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
Click to expand...
Click to collapse
Im out of town bro. Ill add it when i reach home.
fredrickz said:
Im out of town bro. Ill add it when i reach home.
Click to expand...
Click to collapse
Very thankful, have a good time..:good:
Coconut Kernel for LineageOS 18.1 - With Nethunter Support
Code:
***I wont be responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
Just flash the kernel from recovery for supported ROMs.
You can use this kernel for Nethunter functions and other chroot applications like Linux Deploy.
HID and DriveDroid patches are also included.
Note:- The USB Wifi adapter firmware collection is also included with the zip and will be automatically installed. No need to use additional magisk module for installing firmwares.
Source
https://github.com/xpz3/android_kernel_oneplus_msm8996-2
hi, does it work with PE A11? thanks
mohawahba said:
hi, does it work with PE A11?
Click to expand...
Click to collapse
This is compiled from los 18.1 kernel source with modifications for nethunter. I don't use custom rom much, so i don't know about specific features that a custom rom like pe have. If the android version is same, it should work, but if the rom has any special feature that's dependent on the kernel it may or may not work. You can try flashing and see. If it doesn't work, just go back to the old kernel.
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
jobsdonn said:
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
Click to expand...
Click to collapse
Whats the issue you're facing?
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
fredrickz said:
Whats the issue you're facing?
Click to expand...
Click to collapse
I have the same problem with TP-LINK TL-WN722N (RTL8188EUS) - it looks nice in lsusb, no problems are reported in dmesg, but no wlan1 device ... Do i miss something?
nadastry said:
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
Click to expand...
Click to collapse
Flash generic arm64 installer, then this kernel
Which toolchain do you use to build your kernel?
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it？
jlock. said:
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it？View attachment 5895271
Click to expand...
Click to collapse
fixed the problem，just need to flesh agian
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
lemongrass1717 said:
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
Click to expand...
Click to collapse
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Official nethunter requires android 10, last official oxygenOs is android 9 but the only available lineageOs for op3t is 18.1 on android 11. Probably Im doing something wrong but I still couldn't make wifi adapter work
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
KernelSu is a new root solution for android kernel, there shows some docs about kernel source compilation and module integration. I've tried several times, not so hard but so messy，lots of trivial details(such as adding lost source, changing argvs for compiler.....) you should search for solutions and solve.
Building Kernels | Android Open Source Project
source.android.com
How to build KernelSU? | KernelSU
A kernel-based root solution for Android GKI devices.
kernelsu.org
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Followed you guide:
1. Downloaded kernel source
2. Patched it with https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch
3. Getting Error on compile
I also tried to add this drivers manualy to kernel https://github.com/aircrack-ng/rtl8188eus and run compile. Seems it compiled OK but on TWRP I get Unsupported Device Error
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
lemongrass1717 said:
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
Click to expand...
Click to collapse
Awesome! I mean if you want to use the same kernel, and just adding some patches, clone the already existing NH kernel source. Nice
I slightly modified and compiled the kernel from tImIBreakdown, put it in .zip installer. It doesn't have overclocking and lots of governors or i/o schedulers, because I couldn't find a kernel supporting them on android 11. If you want to help me, I will be very glad.
My Changes:
The conservative governor is enabled
Added Nethunter support
Minor changes to the dtc for the compiler
Several patches from Undermind
Install: flash the zip file through custom recovery
If this caused a bootloop, then you can format /system and flash the firmware again, and since you did not format /data, your data will be saved.
Tested on Arrow-OS 11 and crDroid 7.18
Source code:
Github: github.com/tImIbreakdown/android_kernel_leeco_msm8976/tree/lineage-18.1
The work is in progress... wait...
Is it specific for Android 11 or does it work also on Android 10?
devel13 said:
Is it specific for Android 11 or does it work also on Android 10?
Click to expand...
Click to collapse
I do not know, but I am doing this on a fork of the lineage 18.1 kernel from tImIbreakdown. I can try after this kernel to make another one on kernel 17.1 if it won't work on android 10.
trottling said:
I do not know, but I am doing this on a fork of the lineage 18.1 kernel from tImIbreakdown. I can try after this kernel to make another one on kernel 17.1 if it won't work on android 10.
Click to expand...
Click to collapse
Thanks. There is a big issue with the lineage kernels: the GPS lock time is very, very long.
On oldest kernels, I mean the ones affected by the echo in call issue, the GPS lock time was fast.
So, as usual, one issue fixed and a new one introduced.
I wonder if you brand new kernel is just a tuning of the governors or could affect also the GPS driver.
devel13 said:
Thanks. There is a big issue with the lineage kernels: the GPS lock time is very, very long.
On oldest kernels, I mean the ones affected by the echo in call issue, the GPS lock time was fast.
So, as usual, one issue fixed and a new one introduced.
I wonder if you brand new kernel is just a tuning of the governors or could affect also the GPS driver.
Click to expand...
Click to collapse
Сan you send me the version of your firmware and kernel? Maybe I will be able to transfer the GPS drivers from there to the new version.
It will be much better if you also find the location of these files and show me the source code of the kernel with a high-speed GPS. Here is an example of the kernel source code on which I make this kernel: (github.com/tImIbreakdown/android_kernel_leeco_msm8976/tree/lineage-18.1)
I am now seriously busy implementing hotplug and about 20! new governors.
To tell the truth, I didn't understand your problem very well, I use a translator and it distorts the essence. Tell us in more detail.
trottling said:
To tell the truth, I didn't understand your problem very well, I use a translator and it distorts the essence. Tell us in more detail.
Click to expand...
Click to collapse
OK, sorry. I've just investigated further and the GPS issue seems related to a wrong default gps.conf and not to the kernel itself, although the GPS signal is quite weak.
So go on with your kernel development and, when you have finished, I will try it.
Thanks
devel13 said:
OK, sorry. I've just investigated further and the GPS issue seems related to a wrong default gps.conf and not to the kernel itself, although the GPS signal is quite weak.
So go on with your kernel development and, when you have finished, I will try it.
Thanks
Click to expand...
Click to collapse
New kernel forum.xda-developers.com/t/kernel-x52x-android-11r-ballistic-kernel-v1-1-with-nethunter-support.4455463/