Related
cud anyone share with me how to get sync fixed and wifi fixed on eclair??
Im compiling an elair sapphire rom, ive got it booting, and it runs ok. just no wifi or sync.
please help!
bump!
cmon guys... i need help with this, im a noob to developing....
think i dun ok gettin it to compile and boot!
please help me out... and share ur fixes... it'll only mean more choice of roms!
I dont know a lot but I imagine its two seperate things.
the WiFi I imagine is a driver issue, and the sync is because you are missing the google apps.
I am guessing, but after compiling my own 1.6 rom and overcoming some of the strange things I found in doing that its a somewhat educated guess.
you re right! it is two seperate issues..
i have compiled the rom with the google apps from the milestone included. however i am experiencing the same issues with the sync that other devs did when they started working on eclair.
i am wondering how the other devs fixed the issues as this is the only thing preventing me releasing the rom
can anyone shed any light on these issues for me??? will credit u appropriatley on release.
bump again! sorry
can a dev help me out then??
thought this community was about sharing knowledge??
i think this would be a question that actually does belong in development. try there.
this thread already got moved from the development section!
just need pointin in the right direction, will figure the rest out myself!
bump, bump, bump!
can no one help me with this??!!
im guna try and pull sum stuff from the nexus one dump.. see if that works...
feels like im bangin my head against a brick wall tho..
ive downloaded loadsa roms off this site... and now im tryin to put something back, no one will help me out!
cmon devs, pm me, help me out with a fix for sync and wifi.
thanks!
ok, first of all, you're making a sapphire build but is it for the sapphire or the magic? They both use different kernels. If you're building for the sapphire (32b) then the stock kernel and wlan modules work fine. You might have a bluetooth problem, so, if bluetooth won't start, in your /vendor/htc/sapphire-open look for init.sapphire.rc and at line 59 change where it says "texas" to "texasalt". If you don't have bluetooth problems then don't change it.
Did you change your kernel by any chance? This could happen if you're using somebody else's boot.img or if you knowingly used another kernel and packed it to the default boot.img, or further, if you built your own kernel.
If you used somebody else's kernel, then you need to replace the wlan.ko module, again, in /vendor/htc/sapphire-open with the wlan.ko module from the kernel you took.
If, instead, you built your own kernel, then you need to rebuild the wlan.ko module doing the following (taken mostly in part from Johan de Koning's blog), ~/mydroid reffers to your working android path (mine's ~/Desktop/android/master):
Code:
export PATH=$PATH:~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.X.X/bin
(replace X.X with the toolchain version numbers you used to build your kernel)
Code:
cd ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32
export KERNEL_DIR=~/mydroid/kernel/
make
and then copy the just-created module to sapphire-open
Code:
cp wlan.ko ~/mydroid/vendor/htc/sapphire-open
And about the sync problem? I'm wondering myself too. My last AOSP master build had gapps on it, but sync was still broken (you had to disable it), and so is still everybody else's based on AOSP, except for JAC/Cyanogen's.
The only other eclair build out there with working sync is Manup's, but his is based on the 2.0.1 sdk system image and he didn't fix sync, it just works on 2.0.1, so whatever was preventing sync from working on the 2.0 aosp build was fixed on 2.0.1, he just tossed the gapps in there and they worked.
I'm interested too in learning how Cyanogen worked out the sync problem on AOSP, he tweeted something like "I think I know how to solve the sync problem" a few days ago, but he didn't elaborate. We have to find someway to lure him to this thread and let us know how to fix it on our repos rather than copy his own.
If you do find out about fixing the sync problem (programatically), let me know please, I'm also interested.
Actually, looking through cyanongen's github, I think I found the answer. I'll make a quick eclair build and test.
http://github.com/cyanogen/android_...mmit/eea38a1ad7a61b4426612222a654da610e02855a
---edit---
nope, not it.
Here's the sync fix:
http://github.com/cyanogen/android_frameworks_base/commit/9fb8bb8a9542dfcaf9f546d9cee545517a03bed1
I think this would be pretty easy to patch into a non-AOSP build using smali/baksmali too since it's so simple.
Not sure what kind of wifi problem you have.. I've had no problems with it.
thanks 10chars
---edit---
nevermind
thanks guys.. i will start my own build as soon as i get home!
Also.. You should be able to build using my sources and get a system.img that actually works 100% and can be fastbooted.
I found out the hard way that apparently the WPA2 implementation in Android is faulty. This means it can not connect to WPA2 secured APs which enforce strict specs:
https://forum.openwrt.org/viewtopic.php?id=25870
Would it be possible to fix that in CM ?
Cheers,
Karl
Android is using wpa_supplicant, it doesn't implement the protocols on its own.
So you are saying the bug is actually in wpa_supplicant ?
Should i try to make them aware of the problem ?
First time I hear that, although I have at home WPA2 personal and my Legend connects with it normally.
I have a WPA2 personal network both at home and at my dorm, and my HeroC has been able to connect to them fine no matter what ROM I've used (stock, Sense 2.1 custom ROMS, and CM6/7)
According to the openwrt link i posted above it seems to be a problem with the drivers on openwrt enforcing strict RFC compliance and the wpa_supplicant not sticking to it. So it might just be a problem for a specific setup.
However, the question now is if that should be fixed in android or if openwrt should relax its rules.
I just try to find out which community would be the right one to address...
Hey AliBa !
People at openwrt think its a problem of the TI wireless drivers, and that it could be fixed in CM:
This is not a problem with OpenWRT, hostapd, or wpa_supplicant (the latter two are the same project, and mostly written by one person). This is a bug with Android wifi drivers that do not properly follow spec.
The TI Wilink driver I referred to is particularly at fault, and disabling WMM on the router is a band-aid to the problem - not a fix or a real solution. wpa_supplicant is not even involved in this process since the Wilink driver generates the RSN on its own.
The people who need to address this are TI, not openwrt or CM or someone else (or CM can put in a patch to fix the TI Wilink driver, which is probably a good idea anyway).
Click to expand...
Click to collapse
https://forum.openwrt.org/viewtopic.php?id=25870
There are two RSN settings in tiwlan.ini:
Code:
RSNPreAuthentication
RSNExternalMode
...try setting latter to external.
Hey BlaY0 !
This .ini file is in the build tree, not on the phone, right ? Or can i set that on my phone ?
If its a part of the build files, do you think I should file a bug at CM ?
It's on the phone... /system/etc/wifi/tiwlan.ini. It's configuration file for driver itself.
Might be a noob-problem, but i am unable to write to the file.
I tried terminal emulator, su, vi /etc/wifi/tiwlan.ini, but its read-only.
Any other way i can try this ?
Use recovery to do that or you can use system overlay.
Sent from my HTC Legend
Tried switching the RSN..-config to external as mentioned, but it's not working here.
Hmm, anything else we can do ?
AliBa, are you sure you could not fix this ?
People at openwrt think it could be patched in CM:
https://forum.openwrt.org/viewtopic.php?id=25870
Cheers,
Karl
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Hey !
ali ba said:
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Click to expand...
Click to collapse
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
karl_k said:
Hey !
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
Click to expand...
Click to collapse
It's a royal PITA, and we all dislike HTC, Motorola, Samsung etc. for doing it. That said, the CM team do an unbelievable job of dealing with it as well as they do
karl_k said:
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Click to expand...
Click to collapse
Every Google device was as close to open source as possible with all kernel sources being released. It's companies like HTC that corrupt that whenever they can. For example they put code into the framework that would normally go into the kernel just to not having to release it.
Moreover, the sources for wl12xx were open sourced by TI using a BSD-like license. The even sadder problem is that HTC modified them and then deliberately removed those modifications (headers) from the kernel sources they released.
So its a dead end, and really nothing can be done about it?
Can't believe that!
I upgraded my HTC sensation XL to ICS with kernel 3.0.16, I am trying to hook sys_call_table. How can I get the address od sys_call_table?
scottwen said:
I upgraded my HTC sensation XL to ICS with kernel 3.0.16, I am trying to hook sys_call_table. How can I get the address od sys_call_table?
Click to expand...
Click to collapse
hey, what makes the sys call table..? and for what you need...maybe you must compile a kernel with a patch of this (github commits)..also some things can be changed with an init.d script
with kind regards..Alex
Alex-V said:
hey, what makes the sys call table..? and for what you need...maybe you must compile a kernel with a patch of this (github commits)..also some things can be changed with an init.d script
with kind regards..Alex
Click to expand...
Click to collapse
I am trying to develop a loadable kernel module to protect my private data from accessing by unauthorized apps. I have downloaded the source codes of the kernel 3.0.16 from htcdev.com. I can find the file System.map which keeps the address of sys_call_table in kernel 2.6.35, but System.map no longer exists in kernel 3.0.16. Do you know in which file I can find the address of sys_call_table? Is it "init.d"?
Best regareds,
Scott
scottwen said:
I am trying to develop a loadable kernel module to protect my private data from accessing by unauthorized apps. I have downloaded the source codes of the kernel 3.0.16 from htcdev.com. I can find the file System.map which keeps the address of sys_call_table in kernel 2.6.35, but System.map no longer exists in kernel 3.0.16. Do you know in which file I can find the address of sys_call_table? Is it "init.d"?
Best regareds,
Scott
Click to expand...
Click to collapse
not sure if i could help...heared of this the first time...just did a quick google search
https://www.google.de/#q=sys_call_t....,cf.osb&fp=3feb6ca7e010caf6&biw=1366&bih=646
http://code.google.com/p/bricked/source/browse/arch/avr32/kernel/syscall_table.S
http://faculty.kfupm.edu.sa/ics/salah/091/ics531/slides/Understanding The Linux Kernel.pdf
PS: init.d (if its activated in kernel ramdisk) is a folder in system/etc/init.d in this you can put scriptes...eg to handle ram or undervolt on the fly..or zipallaign on each boot...
with kind regards
Hello there, as you know, building a rom isn't simple, not at least until you get the hang of it. I know that not many people (actually, it seems it's just me) build for this phone anymore, so I thought I'd make a little thread to help you.
Here are a few patches to make your builds stabler:
Deep Sleep Patch-
https://github.com/XePeleato/hisi_f...b5fe589a7cc2223a344e56d84e450041756656a.patch
NFC Patch-
https://github.com/Meticulus/androi...mmit/646011845bedc537c157f490d95e98d5e3f01057
Network Toggles Patch-
https://github.com/Meticulus/androi...mmit/ed6563e6fb5747fd0eedc9258aae37ec06891d05
Bluetooth Patch-
https://github.com/Meticulus/androi...mmit/c4fc752cdd31c0c6b2fa29af080cb6af206d8293
RIL Patch (If it stops working across reboots)-
https://github.com/Meticulus/androi...mmit/447f899531949d4d03769fe7235ca7137af3443b
P.S
Some of these may have to be applied manually rather than using the usual patch command.
GPS Patch is in my AOSiP thread.
I think this is all,
Enjoy!
Is there any way to pass any of those to a .zip file to install it in the ROM instead of doing all the construction? Add it to the system as a simple patch
matamata15c said:
Is there any way to pass any of those to a .zip file to install it in the ROM instead of doing all the construction? Add it to the system as a simple patch
Click to expand...
Click to collapse
Nope. These are patches that are applied to the rom sources, and those are different from one to another.
kernel-plus for Nokia 6
This project is made to enhance user experiences using the Linux kernel on the Nokia 6 phone.
What this kernel have:
Additional CPU governors (alucard, nightmare, darkness, bioshock, blu_active), with "darkness" as the default governor for stability and battery life
SafetyNet compatibility
Enforcing SELinux (can be easily changed by modifying the flashable ZIP)
exFAT and NTFS read/write drivers (userspace programs will be necessary to access those functionalities) << THE FIRST ANDROID KERNEL TO HAVE NTFS KERNEL DRIVER
Latest patches from kernel.org for its respective release version (in this case 3.18.y)
Latest commits from CAF for its respective release version (in this case msm-3.18)
/proc/config.gz support for you kernel builders out there
What this kernel will have in the future:
EAS support with schedutil (currently work-in-progress)
Double tap to wake support (planned)
Overclocking support (planned)
Different kernel release upstream branch (planned)
>Is it safe to use the kernel? Have you done any tests?
Yes. I personally am using it with pirrat25's LineageOS 15.1 custom ROM (Oreo 8.1) on my Nokia 6 and it just works. I don't really know yet about long term usability so let me know in the thread!
>So, it has never been tested on stock ROM?
No, it has been tested to be not working (on Pie). YMMV, though. So go and try it! (Don't forget to give feedback in the thread if you do, thanks!)
>Will you add more features to the kernel? It's so barren!
Yes. That feature roadmap list is definitely not final. I will try and get as many features as I can to the kernel, so please stay tuned! Also, YOU can also contribute and add new features to the kernel. Just fork the source code on GitHub and make a pull request when you think you've got enough work on it.
XDA:DevDB Information
kernel-plus, Kernel for the Nokia 6
Contributors
xaedoplay.modder.xda, Linux Foundation, AOSP, Qualcomm, and HMD/FIH kernel engineers
Source Code: https://github.com/rmnscnce/android_kernel_PLE/tree/plus-3.18.y
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.18.140-plus_v1.5
Stable Release Date: 2020-10-18
Created 2020-10-18
Last Updated 2020-10-28
Here you can download the prebuilt kernel images
Format: Flashable ZIP Archive
Latest version link: Direct download || Release page
Version archives (direct download links):
3.18.140-plus_v1.5
Changes:
- Merged tag LA.UM.6.5.r1-11500-8x96.0 from CAF
Code:
msm : adsprpc: maintain local copy of rpra offloaded to DSP
Make file credentials available to the seqfile interfaces
ext4: only look at the bg_flags field if it is valid
ext4: don't update checksum of new initialized bitmaps
ext4: verify the depth of extent tree in ext4_find_extent()
ext4: add more inode number paranoia checks
diag: Prevent out-of-bound access while processing userspace data
diag: Prevent out of bound access while getting build mask
diag: Check command size against the minimum before parsing
msm: adsprpc: maintain local copy of rpra offloaded to DSP
msm: ais: Remove dead code from Camera drivers
asoc: Ratelimit error logs to avoid excessive logging
soc: qcom: smem: validate fields of shared structures
msm: sensor: actuator: fix out of bound read for bivcm region params
FROMGIT: binder: create node flag to request sender's security context
ext4: avoid running out of journal credits when appending to an inline file
jbd2: don't mark block as modified if the handle is out of credits
jbd2: speedup jbd2_journal_dirty_metadata()
ext4: add corruption check in ext4_xattr_set_entry()
ext4: always verify the magic number in xattr blocks
- Compiled all drivers directly into the kernel image to prevent cases of incompatible .ko files (Pie not being able to use Wi-Fi)
3.18.140-plus_v1.4
Changes:
- Reverted integration of several drivers (readded /system/vendor/lib/modules files compilation)
- Added exFAT support in the kernel (submodule github:arter97/exfat-linux::branch=old)
- Added NTFS support in the kernel (Paragon NTFS3 GPL R/W driver)
- Fixed mistake in cmdline patcher
3.18.140-plus_v1.3
Changes:
- Streamlined the package by including all (necessary) drivers in the kernel image (eliminated /system/vendor/lib/modules dependency)
- Signed the flashable ZIP
3.18.140-plus_v1.2.1
Changes:
- Switched default CPU governor back to 'darkness'
- Removed 'lionfish' because of reboots when the battery is 35% or lower
3.18.140-plus_v1.2(DO NOT USE)
Changes:
- Removed "bloat" CPU governor 'conservativex' (it never worked)
- Changed default CPU governor to 'lionfish'
- Now using stock ramdisk
3.18.140-plus_v1.1
Changes:
- Applied SELinux compatibility kernel patch
- Modified kernel command line to boot on SELinux enforcing
3.18.140-plus
Changes:
- Initial release
Big thanks for GitHub for hosting my project repo and builds
Installation Guide
How to install the kernel?
Simple answer: "Just flash it using TWRP"
---
Well, it's that easy. Just flash the file you have downloaded using TWRP, and reboot the phone. Nothing fancy, just flash and it's all set.
Additional note: For some (unknown) reason Magisk would not survive the kernel flash procedure. You will need to flash Magisk installer zip after flashing the kernel to use it.
-----
How to change the kernel to boot into permissive SELinux mode?
While for security (and SafetyNet) it is not recommended to set the kernel to boot into permissive SELinux mode, you can easily modify the kernel flash script to do so (you can even disable SELinux altogether, but it is STRICTLY NOT RECOMMENDED)
To modify the kernel flash script, you must edit the "anykernel.sh" file.
From this
Code:
patch_cmdline androidboot.selinux=permissive androidboot.selinux=enforcing
-
To this:
Code:
patch_cmdline androidboot.selinux=permissive androidboot.selinux=permissive
or to this - if you want to disable SELinux altogether:
Code:
patch_cmdline androidboot.selinux=permissive androidboot.selinux=disabled
After it is done, you can repack the ZIP (I don't recommend applying compression to the ZIP) and flash it on TWRP
hello, I tried this but it doesnt work on stockrom base on Pie.
I also made a kernel based on nokia source V6* weeks ago with the kernel ver 3.18.120 from nokia, with pre enabled permissive mode and enabled some on menuconfig and governors and it seems to work everything, did it for personal purpose.
I also tried to upstream it, but I'm stuck got lots of error cuz I directly jump to the last version of kernel which is 3.18.140. did tried adding also EAS to the kernel, but there is alot of file to be added and fixing the error and symlinks manually so I didnt continue there since im doing it on my Celeron laptop.
anyway this one wont flash on TWRP, gets error using anykernel3 zip, something error like " update error:1" I dont remember exactly the whole text.
same thing for fastboot. I replaced the kernel from stockboot.img from this one and get Remote failed: dtb not found. (tried 3x) I know the compiled sources are dtb file but it doest get read,
which is the same procedure when I compiled my kernel which works.
thank you for making a time doing it for the N6 users. hopefully it will work soon.
JinbrianZ said:
hello, I tried this but it doesnt work on stockrom base on Pie.
I also made a kernel based on nokia source V6* weeks ago with the kernel ver 3.18.120 from nokia, with pre enabled permissive mode and enabled some on menuconfig and governors and it seems to work everything, did it for personal purpose.
I also tried to upstream it, but I'm stuck got lots of error cuz I directly jump to the last version of kernel which is 3.18.140. did tried adding also EAS to the kernel, but there is alot of file to be added and fixing the error and symlinks manually so I didnt continue there since im doing it on my Celeron laptop.
anyway this one wont flash on TWRP, gets error using anykernel3 zip, something error like " update error:1" I dont remember exactly the whole text.
same thing for fastboot. I replaced the kernel from stockboot.img from this one and get Remote failed: dtb not found. (tried 3x) I know the compiled sources are dtb file but it doest get read,
which is the same procedure when I compiled my kernel which works.
thank you for making a time doing it for the N6 users. hopefully it will work soon.
Click to expand...
Click to collapse
Thanks for the reply!
>anyway this one wont flash on TWRP, gets error using anykernel3 zip, something error like " update error:1" I dont remember exactly the whole text.
Can you please take note of the error message? It would be impossible for me to fix if you don't give me the details
>I replaced the kernel from stockboot.img from this one and get Remote failed: dtb not found. (tried 3x) I know the compiled sources are dtb file but it doest get read
This looks really strange. Is it possible that dtb layout from Oreo differs to the one on Pie? If it is, then I'll need to patch more and create a specific custom Makefile option to make it possible to compile more than one dtb image per source.
I will update the OP to let people know that this doesn't work (yet) on the stock Pie ROM
Cheers!
xaedoplay.modder.xda said:
Thanks for the reply!
>anyway this one wont flash on TWRP, gets error using anykernel3 zip, something error like " update error:1" I dont remember exactly the whole text.
Can you please take note of the error message? It would be impossible for me to fix if you don't give me the details
>I replaced the kernel from stockboot.img from this one and get Remote failed: dtb not found. (tried 3x) I know the compiled sources are dtb file but it doest get read
This looks really strange. Is it possible that dtb layout from Oreo differs to the one on Pie? If it is, then I'll need to patch more and create a specific custom Makefile option to make it possible to compile more than one dtb image per source.
I will update the OP to let people know that this doesn't work (yet) on the stock Pie ROM
Cheers!
Click to expand...
Click to collapse
> I will check it later.
or maybe because of TWRP, I use the bootable version which 3.2.3-0, but I can flash any zip on it. except for the anykernel zip that gets same error, which is also I did before for my compiled kernel.
and only gets to work when fastbooting the .img
Also when I compiled the kernel sources based on pie V6 from nokia, I got a dtb file size of about 18mb. where the stockboot image is 21mb. the one you compiled is in smaller size which maybe there is something missing files to get to work on pie I think?
JinbrianZ said:
> I will check it later.
or maybe because of TWRP, I use the bootable version which 3.2.3-0, but I can flash any zip on it. except for the anykernel zip that gets same error, which is also I did before for my compiled kernel.
and only gets to work when fastbooting the .img
Also when I compiled the kernel sources based on pie V6 from nokia, I got a dtb file size of about 18mb. where the stockboot image is 21mb. the one you compiled is in smaller size which maybe there is something missing files to get to work on pie I think?
Click to expand...
Click to collapse
Thanks for the reply!
>or maybe because of TWRP, I use the bootable version which 3.2.3-0, but I can flash any zip on it
Maybe try to use the official TWRP? It has full support and stuff, but I couldn't manage to flash the custom ROM there so to each their own
>he one you compiled is in smaller size which maybe there is something missing files to get to work on pie I think?
Yeah, maybe that's the culprit. Is it because I don't integrate all modules inside the kernel image? I will try and compile all the modules inside the kernel. The final ZIP size is 25MB though so it is actually bigger in total compared to the stock boot image.
Like I said, I will fix this issue once I got the real problem, so that all Nokia 6 user can enjoy using custom kernel images :fingers-crossed:
Finally a custom kernel for our phone! looks like i really need to unlock the bootloader now. Thanks for your effort from making this one!
btw sorry if it's OOT but is the LOS 15.1 ROM stable enough for daily driver use?
MYR-12.v2 said:
Finally a custom kernel for our phone! looks like i really need to unlock the bootloader now. Thanks for your effort from making this one!
btw sorry if it's OOT but is the LOS 15.1 ROM stable enough for daily driver use?
Click to expand...
Click to collapse
Thank you for the reply!
>is the LOS 15.1 ROM stable enough for daily driver use?
Yes – only if you wouldn't mind not being able to use the fingerprint scanner (and the button backlights). Other than that it's good! As an added bonus, the built in camera firmware is on par with the GCam port for this phone, without the shutter lag
I installed latest plus kernel on stock pie. it works now on my device. but wifi doesnt work.
if u set CONFIG_PRONTO_WLAN=m into CONFIG_PRONTO_WLAN=y on PLE_defconfig wifi will work. hope this error is due to this, kind of a sign error i hope so. I experienced this same error when i tried to build los.
cbkottege said:
I installed latest plus kernel on stock pie. it flashed well but didn't boot into system,it rebooted into bootloader.
Click to expand...
Click to collapse
Thank you for the reply!
So, it cannot boot on Pie, right? I will work for Pie ROMs on a separate branch, then!
I really thought there weren't going to be any changes in userspace compatibility between Oreo and Pie. Turned out I am wrong
xaedoplay.modder.xda said:
Thank you for the reply!
So, it cannot boot on Pie, right? I will work for Pie ROMs on a separate branch, then!
I really thought there weren't going to be any changes in userspace compatibility between Oreo and Pie. Turned out I am wrong
Click to expand...
Click to collapse
sorry man, can u check my previous reply again. i edited it. now its working.
I wiped cache and flashed magisk again then it worked..
but wifi doesnt work
cbkottege said:
sorry man, can u check my previous reply again. i edited it. now its working.
I wiped cache and flashed magisk again then it worked..
but wifi doesnt work
Click to expand...
Click to collapse
Thank you for your reply!
I checked the previous reply:
cbkottege said:
I installed latest plus kernel on stock pie. it works now on my device. but wifi doesnt work.
if u set CONFIG_PRONTO_WLAN=m into CONFIG_PRONTO_WLAN=y on PLE_defconfig wifi will work. hope this error is due to this, kind of a sign error i hope so. I experienced this same error when i tried to build los.
Click to expand...
Click to collapse
> if u set CONFIG_PRONTO_WLAN=m into CONFIG_PRONTO_WLAN=y on PLE_defconfig wifi will work
Okay, so I guess I had to merge drivers into the kernel again, huh? Will do! (Expect new version later today with even more updates)
>I experienced this same error when i tried to build los
You built LOS? What version? I would like to have it if it's working and is LineageOS 16 or later!
xaedoplay.modder.xda said:
Thank you for your reply!
I checked the previous reply:
> if u set CONFIG_PRONTO_WLAN=m into CONFIG_PRONTO_WLAN=y on PLE_defconfig wifi will work
Okay, so I guess I had to merge drivers into the kernel again, huh? Will do! (Expect new version later today with even more updates)
>I experienced this same error when i tried to build los
You built LOS? What version? I would like to have it if it's working and is LineageOS 16 or later!
Click to expand...
Click to collapse
Thanks for ur efforts on kernel plus! keep this going on. we will hope later updates
I tried to build los 16 but i failed. I built los 15.1 using pirats tree. tried to fix fingerprint,hotspot and backlight bugs . Only i managed to fix hotspot bug also i managed to set Selinux to enforced on los 15.1 userdebug build without any major issue.
cbkottege said:
Thanks for ur efforts on kernel plus! keep this going on. we will hope later updates
I tried to build los 16 but i failed. I built los 15.1 using pirats tree. tried to fix fingerprint,hotspot and backlight bugs . Only i managed to fix hotspot bug also i managed to set Selinux to enforced on los 15.1 userdebug build without any major issue.
Click to expand...
Click to collapse
Thank you for your reply!
>Thanks for ur efforts on kernel plus! keep this going on. we will hope later updates
Stay tuned! I'm ~65% done on the next update!
>I tried to build los 16 but i failed
Aw, that's quite unfortunate :\ Maybe you could try building 17.1 tree made available by someone on GitHub?
>tried to fix fingerprint,hotspot and backlight bugs . Only i managed to fix hotspot bug also i managed to set Selinux to enforced on los 15.1 userdebug build without any major issue
There's a hotspot bug? I don't experience anything strange on it here. Anyways could you please share the fixed build (on the respective pirrat's thread)? Any fixes' a goal!
xaedoplay.modder.xda said:
Thank you for your reply!
>Thanks for ur efforts on kernel plus! keep this going on. we will hope later updates
Stay tuned! I'm ~65% done on the next update!
>I tried to build los 16 but i failed
Aw, that's quite unfortunate :\ Maybe you could try building 17.1 tree made available by someone on GitHub?
>tried to fix fingerprint,hotspot and backlight bugs . Only i managed to fix hotspot bug also i managed to set Selinux to enforced on los 15.1 userdebug build without any major issue
There's a hotspot bug? I don't experience anything strange on it here. Anyways could you please share the fixed build (on the respective pirrat's thread)? Any fixes' a goal!
Click to expand...
Click to collapse
>I did it for my personal use. about hotspot bug when we switch between hotspot and wifi system got restart after a while.
>I tried that los 17 tree posted by samu , it also not working. I'm new for these stuff. i think we have to add some symlinks manually to upstream the tree. But i dont know much about it. :crying:
> I'll post my work on that thread soon. I have to find the working zip file now. There are lots of zips on my pc and are not organised well
I want to know does pirrats los 15.1 having any battery issue quick discharge in idle or any kind of a unusual battery usage???
In my build im having a unusual battery usage cant even find what is the cause for it. i thought it was due to tree . let me know if u have a quick battery drain in idle on urs.
cbkottege said:
>I did it for my personal use. about hotspot bug when we switch between hotspot and wifi system got restart after a while.
>I tried that los 17 tree posted by samu , it also not working. I'm new for these stuff. i think we have to add some symlinks manually to upstream the tree. But i dont know much about it. :crying:
> I'll post my work on that thread soon. I have to find the working zip file now. There are lots of zips on my pc and are not organised well
I want to know does pirrats los 15.1 having any battery issue quick discharge in idle or any kind of a unusual battery usage???
In my build im having a unusual battery usage cant even find what is the cause for it. i thought it was due to tree . let me know if u have a quick battery drain in idle on urs.
Click to expand...
Click to collapse
Thanks for your reply!
>>I tried that los 17 tree posted by samu , it also not working. I'm new for these stuff. i think we have to add some symlinks manually to upstream the tree. But i dont know much about it. :crying:
I really want to help on this but sadly I don't have much storage spaces left on my workstation so kernel it is! Maybe if I finally got my hands on more storage? I hope so!
>I want to know does pirrats los 15.1 having any battery issue quick discharge in idle or any kind of a unusual battery usage???
Maybe? I don't know, I started the kernel development almost immediately after I got my hands on 15.1. For what I know, the battery drains but I think that's because of my battery breaking down (thinking about having ~2500mAh left intact) (this kernel is really good at maintaining idle battery life through HW controlled deep sleep though, thanks to "darkness" governor)
xaedoplay.modder.xda said:
Thanks for your reply!
>>I tried that los 17 tree posted by samu , it also not working. I'm new for these stuff. i think we have to add some symlinks manually to upstream the tree. But i dont know much about it. :crying:
I really want to help on this but sadly I don't have much storage spaces left on my workstation so kernel it is! Maybe if I finally got my hands on more storage? I hope so!
>I want to know does pirrats los 15.1 having any battery issue quick discharge in idle or any kind of a unusual battery usage???
Maybe? I don't know, I started the kernel development almost immediately after I got my hands on 15.1. For what I know, the battery drains but I think that's because of my battery breaking down (thinking about having ~2500mAh left intact) (this kernel is really good at maintaining idle battery life through HW controlled deep sleep though, thanks to "darkness" governor)
Click to expand...
Click to collapse
Can u join me on telegram ""t.me/cbkings"" . :fingers-crossed: maybe we can talk little about development just in case .
Thanks for making a custom kernel, i tried it with Lineage OS 15.1, but everytime when i deploy it with TWRP 3.4.0, it soft-bricks my android installation. (or even TWRP itself also, but i am not sure)
Also im using TA-1033.
Edit: Changed TWRP to 3.3.1 and installed Magisk before applying, now it boots, but GUI is messed up.
cbkottege said:
I installed latest plus kernel on stock pie. it works now on my device. but wifi doesnt work.
if u set CONFIG_PRONTO_WLAN=m into CONFIG_PRONTO_WLAN=y on PLE_defconfig wifi will work. hope this error is due to this, kind of a sign error i hope so. I experienced this same error when i tried to build los.
Click to expand...
Click to collapse
Hey! Just wanted to inform you that the new kernel release (plus_v1.5) got all the drivers built into the kernel image. Hopefully now the Wi-Fi will work on stock Pie ROM.
Please give an update if you're trying it out!
Wapitiii said:
Thanks for making a custom kernel, i tried it with Lineage OS 15.1, but everytime when i deploy it with TWRP 3.4.0, it soft-bricks my android installation. (or even TWRP itself also, but i am not sure)
Also im using TA-1033.
Edit: Changed TWRP to 3.3.1 and installed Magisk before applying, now it boots, but GUI is messed up.
Click to expand...
Click to collapse
Thanks for the reply!
>but GUI is messed up
Have you tampered the GPU drivers? You can try to wipe the GPU cache (also the /cache partition and runtime (dalvik) cache) to fix issues with broken UI elements