Database Info

[Q] Haipad M701 and fingerprint reader

Hi ,
I have a Haipad M701 with me,
It is having this config:
4G Memory
Telechips 89xx board
Android 2.1-update1
MID-1.1
Kernel 2.6.29
I am trying to make a external USB fingerprint reader work with it.
The fingerprint device driver source was obtained from the vendor.
To enable the device i need to cross compile the fingerprint drivers.
But before i cud do that, i upgraded the firmware to Android 2.3(gingerbread) which is available in haipad.net(*w/o taking a backup*)(that is kernel 2.6.35).
Now, i am not able to cross-compile driver cos i took the kernel source (for 2.6.29) which telechips publicly opened to public.
So, Right now, i need the old Eclair(2.1,2.6.29) firmware, can anyone provide me that?
If not, is there any other way to achieve the cross-compilation?

In the meantime, i downloaded kernel source from android.com and branched to 2.6.35 which is the kernel version on device.
I compile the kernel and then cross compiled the fingerprint driver.
It compiled w/o any issues.
But when do a 'insmod', i get error:
Code:
mod_usbdpfp: version magic '2.6.35.7+ mod_unload modversions ARMv5 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
What could be the issue here?

You have two problems:
First on the tablet, copy the file /proc/config.gz out on your build pc.
Extract and copy file to .config in the 2.3.35.7 source.
Now you are ready to configure the kernel sources that you compile the vendor driver against.
do make menuconfig;
Fix problems:
1: wrong name of kernel.
Insert "-tcc" in general setup --> Local version.
You seem to have a "+" now. I do not know how you got that. If it is not in the kernel config, look in the Makefile in the root folder. The version is in the top. Make sure the 4th version line just says ".7" - no more.
2. Wrong system type.
You are compiling the modules for an Armv5 instead of Armv6. Go to Arm system type and choose Samsun S3C64XX. That is an Armv6.
The selector might look really strange. If that is the case, scroll to the bottom and scroll back up (now names appear one at a time), until you see the ()amsung S3C64XX.
Configure Makefile for crosscompile.
Now do a make dep; make modules.
Now you can compile the vendor driver against this source and get the correct module. Use modinfo modulename.ko; to see that the name and type corresponds to "'2.6.35.7-tcc mod_unload ARMv6".
I have just done this (for an usb net driver), and the resulting driver crashes the tablet So even if you can get a module build and loaded, it might not work because the system architecture (S3C64XX) is not really correct. In that case we really need the telechips 2.6.35.7 sources to build correct module.
But try it out, and good luck!

Thanks for the suggestion, xdamala.
I will try it out today itself and let you know

@xdamala,
I had to do 'make s3c6400_defconfig'
But, Now i get this error.
Code:
mod_usbdpfp: version magic '2.6.35.7-tcc-g67bb0cf-dirty mod_unload
ARMv6 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
I dont know how the 'g67bb0cf-dirty' gets added.
Each time i edit 'include/config/kernel.release' which contained that text, it automatically is updated on running 'make'.
Any idea??

I am not 100% on how the version string is constructed. But I think it is created from the top 4 lines in Makefile and the string you set in configuration.
I should not be necessary to do that s3c6400_defconfig. It is probaly what changes the string. I might have told you the wrong order of things in my other answer. It is important to set up Makefile first.
Do the steps (in order):
Start with clean 2.6.35.7 kernel code
edit Makefile in kernel root folder
Check version number in top
edit cross compile section to:
ARCH ?= arm
CROSS_COMPILE ?= ../../arm-eabi-4.4.3/bin/arm-eabi-
#or whatever fits your compiler. Note that this android tree gcc 4.4.3 is the one running M701 kernel is compiled with, so I prefer to use the same.
extract tablets /proc/config.gz to .config in root of kernel source (to remove unnecessary modules)
make menuconfig;
set -tcc in local version
choose S3C64XX system type
Exit (Save)
make dep ; make clean ; make modules; #Note you do not actually build the kernel, only modules.
In the Makefile from your driver there probably is a section something like this:
KDIR = /lib/modules/$(CURRENT)/build
edit to point to the folder of your kernel source.
make;
transfer fingerprintdriver.ko to tablet
Cross fingers, throw salt over your shoulder, pray, etc. etc.
insmod fingerprintdriver.ko;

@Xdamala
Code:
mod_usbdpfp: version magic '2.6.35.7-tcc+ mod_unload ARMv6 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
Still the plus seems to be issue.
I checked in the main Makefile there is no '+'.
But in include/generated/utsrelease.h, there is
Code:
#define UTS_RELEASE "2.6.35.7-tcc+"

Well I use a kernel from kernel.org, not from the android tree.
Might be the reason for the "+".
I do not think that it makes any difference in this case.
Try with the kernel.org one. If it works it works, if not we might try to look at that "+"
By the way if all fails you can reinstall 2.1 on the tablet and build against the 2.6.29 kernel released by telechips. It should work.
The downside: 2.1 sucks, and usb in general sucks a lot on M701 2.1.
See my posts here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r-d129-just-ordered-g10-haipad-m701.html.
In that case go to telechips kernel source:
make tcc8900_defconfig
make menuconfig. Exit + save.
make modules.
Then compile your driver against these sources.
Your driver should then work (this time we use the correct system type), but usb is quite bad on 2.1. So if I was you I would try a lot to make 2.3 work first.
Links:
Telechips kernel. Use Internet explorer to download (FF not working):
https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
Latest 2.1 firmware from Haipad:
http://u.115.com/file/c4rgup4f

xdamala said:
Latest 2.1 firmware from Haipad:
http://u.115.com/file/c4rgup4f
Click to expand...
Click to collapse
Thanks xdamala, thats what i needed, will check it out and let you know of the result tomm.

I will warn you that 2.1 comes with its own problems when it comes to usb.
Attach the device directly. Do not use a hub.

xdamala,
Method 1: Compile kernel source of 2.6.35.7 from kernel.org - Success
insmod driver.ko installed w/o any errors.
But, it seems i would need a power source for the fingerprint reader.
i dont think currently the Haipad support that mode.
Method 2: Flash(downgrade) m701 to 2.1 and try with the public kernel source which telechips have released - Failure
The FWDN program gives CRC check error while loading tcc8900_mtd.img.
Maybe bcos of corrupt download or the Haipad i have is a 4G memory one.
Which u think wud be?
Even if i accomplish providing power to the fingerprint device, i would need the C++ sample provided by the fingerprint vendor to be cross-compiled.
Otherwise, how can i test if the device works?
How to do that??

Hi
I did not see your post because it now came as page 2.
The tablet should provide some level of power to the reader. If you use the white converter cable that came with the tablet, it should tell the tablet to provide power (USB On The Go, see Wikipedia). It works with memory sticks and even hard drives. But I do not know if it is enough for that reader.
With 2.3 firmware you could use a power hub to give power to reader (still use white converter cable between tablet and hub). Do not use hubs on 2.1.
To check if tablet recognizes reader do this:
adb shell:
#dmesg -c
#insmod driver.ko
#dmesg
--Insert reader in usb
#dmesg
The output of dmesg should tell you how the kernel reacts when driver is loaded and reader inserted.
You can cross compile c++ code using same compiler as for the kernel. But you will have to compile program/libs statically, since android does not have the C++ libraries.
You can probably achieve this by putting a static keyword in a Makefile.
Also you need to direct the gcc to point at the cross compiler.
An other approach is to install Debian on the tablet inside an file image. I have done this. It is very nice. It gives you a complete (non graphical) Linux system. Compiler, libs and all. Also lsusb and other useful tools.
It is much easier to make Linux programs work like that.
But this Debian will run inside chroot, and cannot see the android system.
I used this tutorial:
http://www.saurik.com/id/10
However I used a bit different approach for starting up Debian system (using Debian own rc scripts).
If you can make the Debian Image, I will be happy to provide you with my scripts to manage it.
I do not know why you cannot install 2.1. It was the one you got fro my URL?
I just see now that Haipad has released a brand new 2.3 this night.
Do not attempt to load it. Last one did not work unless you had the very new tablet. I will try this new one tonight.
What is this project with the fingerprint reader? Tell me more.

Thanks xdamala,
Ya if it is possible, i would surely like to have a Debian on the pad.
I am just exploring things on it, so that we can have a external device work on the pads.
Let me check this url and will let you know
http://www.saurik.com/id/10
Click to expand...
Click to collapse
Ya, if you can help through the process, i will gladly accept it
Also, i didnt get any cable with my pad.
That was the first of issues. Had to buy it separately.
I had done the dmesg check as you told, but it didnt give any noticeable output.
The 2.1 firmware link that you gave, throwed a CRC error. what to do?

if you get a crc error on firmware it is probably because its the wrong firmware.
There are several different versions of this tablet so it can be a bit tricky.
This firmware is for a M701-R 4GB HY
There is 2 GB and 4GB versions. You have a 4 GB right.
There is HY and non HY versions (type of nand memory).
There a re with and without remote control. That is not so important.
I think any mix of the above is possible.
How to figure out if you have a HY version:
Insert usb to pc and enable usb storage.
If nan memory is shown as 3,08 GB (I think) it is an HY.
If it shows less (2,7 GB Ithink) it is a non-HY.
Determine your version and we can see if we can find a FirmWare for it.
Anyway I think you should keep your 2.3 for now. It just is better for USB.
What is the filename of the rar file with 2.3 rom you installed, and where did you get it from? (this might help me identify your tablet).
About usb cable. I now understand why you have no power on reader. If you read the wikipedia article about USB OTG (wikipedia) you will understand that the tablet is in slave mode and will not provide power and probably not talk to devices.
Also see here: http://www.maxim-ic.com/app-notes/index.mvp/id/1822
Can you get a memory stick to work?
You need something like this:
http://www.amazon.co.uk/Host-Cable-ARCHOS-Internet-Tablet/dp/B004TJC1IM/ref=sr_1_3?ie=UTF8.
It will short the correct pins in the mini usb plug, telling the tablet to be master and provide power.
It is possible to fix a cable yourself but I will not recommend it:
http://www.youtube.com/watch?v=COkLEJGo6vo&feature=youtu.be
I am a bit surprised that loading the driver produces no output in dmesg.
But if the tablet is not in host mode, it is not surprising that no output comes from inserting the reader. The tablet is not responding to it since it is in slave mode (like connection two usb sticks. Nothing happens).
I can not help you through the Debian. I used the tutorial I already linked.
If you do the same and add my scripts you should be able to make it work.
Alternatively you can get my Debian Image, but it is 1 GB file, and I need to clean out personal stuff and passwords.

Hi xdamala,
Ya, it seems to be a non-HY, cause i have around 1.4G space in nand
The file i downloaded was M701_2.3.rar, which i downloaded from haipad.net
I did buy the cable like u showed in amazon.com link, using that only am connecting the reader to pad.
And No, a memory stick also is not getting detected on that cable.
Attached that cable image.

Hi xdamala,
I have started creating the debian image, can you tell how you use the rc scripts?
Also, were you able to find the 2.1 image for M701 non-HY?
PS: I got the clockword mod recovery image from here http://androtab.info/telechips/firmwares
I used the one marked "Haipad M701 GB ROM 4K"
It worked for me.

Hi
Several things:
1: I think you have an 2GB version (non HY), not a 4G version.
2. It seems like the cable you bought is not correct. It has to be a HOST adapter/cable. Since nothing works with it I think what you have is just a male min-usb to female usb. It is not enough.
3. About Debian image. Which version of Debian are you using?

By the way I found out how to get rid of the "+" when using the Android kernel source. Move the folder .git to git. This will break git usage (unless you move it back). But it removes the "+" in version string.
Using Android kernel source might be better than stock kernel source.

Hi again,
1. Its a 2GB?? Oh but when i followed this link (translated it english)
Code:
http://www.inzipad.com/thread-334-1-1.html
My result was 4096, so i thought its a 4G one.
2. Oh. Then i will try to buy then one u have recommended.
3. I have dropped the step of building a Debian, cause i have a android application running and the input from the usb reader has to be sent to that application. So, I have to make it work natively on Android.

xdamala said:
You have two problems:
First on the tablet, copy the file /proc/config.gz out on your build pc.
Extract and copy file to .config in the 2.3.35.7 source.
Now you are ready to configure the kernel sources that you compile the vendor driver against.
do make menuconfig;
Fix problems:
1: wrong name of kernel.
Insert "-tcc" in general setup --> Local version.
You seem to have a "+" now. I do not know how you got that. If it is not in the kernel config, look in the Makefile in the root folder. The version is in the top. Make sure the 4th version line just says ".7" - no more.
2. Wrong system type.
You are compiling the modules for an Armv5 instead of Armv6. Go to Arm system type and choose Samsun S3C64XX. That is an Armv6.
The selector might look really strange. If that is the case, scroll to the bottom and scroll back up (now names appear one at a time), until you see the ()amsung S3C64XX.
Configure Makefile for crosscompile.
Now do a make dep; make modules.
Now you can compile the vendor driver against this source and get the correct module. Use modinfo modulename.ko; to see that the name and type corresponds to "'2.6.35.7-tcc mod_unload ARMv6".
I have just done this (for an usb net driver), and the resulting driver crashes the tablet So even if you can get a module build and loaded, it might not work because the system architecture (S3C64XX) is not really correct. In that case we really need the telechips 2.6.35.7 sources to build correct module.
But try it out, and good luck!
Click to expand...
Click to collapse
Thsi really works thanks for that

[Q] ndk-building does not link stdio properly?

I am working with some large open source projects and some smaller custom C code. I can successfully compile and link these using the ndk-build API even when linking against shared object files within the Android tree. I get functional shared object files and executables for the Android platform. However, it seems that when the applications are built as stand alone (meaning outside the Android source code tree using only ndk-build) the stdio functions do not operate properly. When the same code is placed under external within the Android source code tree and built with Android, the stdio functions work exactly as expected.
I have tried building with ndk r4 and r6, then we tried building with the ndk r4 from within the Android tree. (2.2.1)
the functions in question are
close() - hangs a process when the process is forked
fprintf() - nothing gets written
fopen() for write - the file does not get created as a new file
remove()
unlink()
etc.
I have not tested beyond these functions.
The question is why does the stand alone built code not function properly while the same code built within the Android tree executes properly?
Any insight would be greatly appreciated.
Thanks,
Adam

Edit your post and add a meaningfull thread title.

additional info
Seems in particular that close(0), close(1), and close(2) cause a process hang when fork() is used.
When built with Android code under the external directory, everything works as expected.

Android-x86 4.0RC2 NEW Releases with patch for ARM Binary Translator included

Hello, I'm glad to bring you this new, the Android-x86.org Team was released a NEW build 4.0RC2 (based in the source code 4.0.4r2.1) with gapps included, lot of fixes, and the best part, a patch included, a patch to be able to use houdini the intel binary translator which allow run ARM apps in the x86 architecture (this hack comes from Buildroid.org you can read about this here), I wanna paste here the RelaseNote4.0RC2
ReleaseNote 4.0-RC2
Android-x86 4.0-RC2 (Ics-x86).
The Android-x86 project is glad to announce 4.0-RC2 release to public. This is a second release candidate for Android-x86 4.0 stable release. Live CD ISOs are available from our sites, as usual
http://www.android-x86.org/download
http://code.google.com/p/android-x86/downloads/list
Key Features
The 4.0-RC2 release is based on the Android 4.0.4 (Ice Cream Sandwich branch). We have fixed and added x86 specified code to let the system runs smoothly on x86 platforms, especially for tablets and netbooks. Except the features in 4.0-RC1, the additional features in this release are
Kernel 3.0.36 with more drivers and bug fixes.
Enable Dalvik JIT compiler support.
Support some 3G modem.
Ready to run arm translator. (You still need to install Intel's libraries from BuilDroid.)
Physical keyboard layout selection.
Support two cameras.
Fake SD card is replaced by internal storage support.
We create targets optimized for different x86 platforms. Choose a suitable image for your platform.
android-x86-4.0-RC2-amd_brazos.iso for AMD Brazos platform
sha1sum: 41685b2fd9a0fcd101fc21aeb84882015a6fd976
android-x86-4.0-RC2-eeepc.iso for ASUS Eee PC family
sha1sum: 1953717ac1d606d57fc7d7293b367f8025c51b65
android-x86-4.0-RC2-asus_laptop.iso for some ASUS Laptops/Tablets
sha1sum: fa4a38fcb3e0191523b1673114d9fa076c461671
android-x86-4.0-RC2-tegav2.iso for Tegav2
sha1sum: 106b07aee820511077980275cc744c4327352394
android-x86-4.0-RC2-s103t.iso for Lenovo S10-3t tablet
sha1sum: 3ca23c78183da7b23f516f9c507d60d82b11ab5e
android-x86-4.0-RC2-thinkpad.iso for IBM thinkpad tablet
sha1sum: bc99ec3ace54c0c15c92e4e8eca87385c130ec1d
android-x86-4.0-RC2-tx2500.iso for HP tx2500
sha1sum: 303765d6da5fdb7d8d3979575f0728185e6fb120
The iso files are hybrid format. That means you can dump the iso into a usb drive and get a bootable usb stick, like
$ dd if=android-x86-4.0-RC2-xxx.iso of=/dev/sdX
where /dev/sdX is the device name of your usb drive.
Known issues
Suspend and resume doesn't work on some targets.
Not support Ethernet.
Source code
The source code is available in the main git server,
$ repo init -u http://git.android-x86.org/manifest -b ics-x86
$ repo sync
as well as the SourceForge mirror:
$ repo init -u git://android-x86.git.sf.net/gitroot/android-x86/x86/platform/manifest.git -b ics-x86
Click to expand...
Click to collapse
At the same time, I wanna share with you, my personal and custom Unofficial builds one for Asus EeePC T101MT (Exclusive for my device ) and another one for EeePC Generic, with all included, you can find more info and some captures, a full description of my changes and a video demo of my build in action here.
Also, I did a little howto add houdini libs in our devices (the tutorial from BuilDroid is to apply in your source code and now part of this method isnt necesary, now you just need to copy some libs) you can fin more info here
COOKING TIME WITH ARNDROID-X86!
Enjoy!, Cheers.

installed the thinkpad version on my dell inspiron 1300. I can load the broadcom b43xx via debug mode but it does not scan or show or connect to any wifi networks. that is the only issue I have so far.

http://www.webupd8.org/2012/07/android-x86-404-ics-rc2-released-with.html

dorfd1 said:
installed the thinkpad version on my dell inspiron 1300. I can load the broadcom b43xx via debug mode but it does not scan or show or connect to any wifi networks. that is the only issue I have so far.
Click to expand...
Click to collapse
Same with Broadcom BCM4310 USB Controller on HP Compaq 6830s NN328ES
The solution that has helped me: disable WPA2 encryption, leave only WPA
Vaka++ (C)
Strange, but the authors of the assembly did not put the firmware for the devices, but the modules were collected, respectively, because this device does not work, such as my wi-fi card.
Added many different firmware for devices wi-fi (especially for my zd1211rw) and touchscreens and different chipsets.
archive with firmware
Unpack the archive to the /system/lib/
Click to expand...
Click to collapse

hello! I need an android iso where they can run the appps arm, and use it with virtual box and have an Internet connection
can you help me?

Point me in the right direction

Hello,
Recently I purchased the Tronsmart MK908II and am hoping to make it work with a touch screen located here http://www.cvtouch.com/. Now the company has stated that it will work with Android version 4.2.2 and Kernel version 3.0.36+. They have provided an android driver(a patch file), but they say "your SW engineer need to add it into the kernel".
So my question is, how difficult will it be to patch the kernel, and if not too hard, what are the tools/software I would need to make this happen?
They did originally recommend the Podoor 518 android box, but I only saw one on Amazon and wasn't sure about buying something that seems a bit older. Any guidance or help would be appreciated, thanks!!
Also the most I've done is follow directions to root/unlock some cell phones and install custom roms. I somewhat understand what is going on there, but have little to no idea about the magic behind that.
I've also attached the patch file? and the driver folder
The instructions with the patch file are as follows:
Support CVTouch Multitouch Simple User Manual
Modify your kernel source code refer to drivers\hid files.
1 kernel3.0+\drivers\hid\hid-ids.h
Define CVTouch VID/PID macro in about line 209.
2 Kernel3.0+\drivers\hid\hid-core.c
Add CVTouch VID/PID to struct hid_have_special_driver in about line 1378 to 1538.
3 Kernel3.0+\drivers\hid\hid-multitouch.c
Modify the CVTouch VID/PID at array mt_devices[] in about line 624 to 2054.
4 Confirm if the drive have added the hid-multitouch module in kernel config file.
Run make menuconfig in command terminal to select HID Multitouch panels.
Device Drivers --->
HID Devices --->
Special HID Drivers --->
HID Multitouch panels

Bump! Any help at all? or point me to where I could start learning to do this?

[KERNEL] [Q] N9600 klabit kernel

As most of you guys know Magisk will not work for us on the international snapdragon S9, S9+, and N9
So, I have made a custom kernel that will allow us to have root on stock pie firmware..
Files needed:
N9600:
klabit kernel V6.5
FK Manager n9600 kernel download configuration link
FK Manager n9600 GSI kernel download configuration link
Copy the n9600_q_vx.zip to your external sd card.
Make sure you have TWRP installed with instructions found in this thread.
Flash the n9600_q_vx.zip
Flash Magisk (only necessary if you have not flashed Magisk previously or if coming from a clean install from stock)
Reboot to system.
If you currently do not have a working lockscreen/pin/fingerprint setup, you will need to restore your stock boot.img either via backup or extract your boot.img from the official firmware and flash the img then flash my kernel.
Changelog:
Code:
V6.5
[LIST]
Merge OSRC: N9600ZHU5FTK1
[/LIST]
V6.4
[LIST]
Merge OSRC: G9650ZHS6DTG2
Merge OSRC: G9650ZHS7ETH1
Remove additinal SafetyNet flags from /proc/cmdline
Proc: Fake CMDline
Merge OSRC: G9650ZHU7ETI3
Merge OSRC: G9650ZHU7ETJ2
Expanded GSI kernel compatibility for Android 11 support
[/LIST]
V6.3
[LIST]
Merge OSRC: G9650ZHS6DTF1
Merge OSRC: G9650ZCU6ETF6
[/LIST]
V6.2
[LIST]
Merge OSRC: G9650ZCS6DTD5
[/LIST]
V6.1
[LIST]
Add powersave governor
Add conservative governor
Add ondemand governor
[/LIST]
V6.0
[LIST]
[*]7e123dad108c Import crownqlte && starqlte defconfigs
[*]824f70f8d070 Add .gitignore
[*]7d3612a88cbf Import G9600 and N9600 defconfig && initialize
[*]c1e7a35e59a7 Import G9600 and N9600 dts with verity removed
[*]0a587fae1745 Add option for gsi mtp driver
[*]10b851dfaa03 star2qlte: Initialize defconfig
[*]5f38f4cc0d99 Remove verity
[*]101dedaf7aec scripts: remove localversion + from kernel version strings
[*]c1b726584344 selinux: enable selinux faking
[*]70ed91e9c15a star2qltechn: Enable Samsung MTP driver
[*]9c88019d96fd drivers: usb: add separated Samsung MTP option
[*]6c54f88a648b star2qltechn: Update defconfig
[*]13a223ea3ed9 dts: disable avb,verify
[*]5c36fed8d37b Regen configs
[*]9a37c1921037 (osrc) OSRC: G9650ZCU6DTA9
[/LIST]
V5.9
- Small version bump to 5.9.
- Integrate auto patch of security patch date since Samsung slow af. (Credit to [user=4280397]@djb77[/user])
- Better GSI compatibility.
- Better OneUI compatibility for recent/most up-to-date firmwares.
V5.8
- Fix compilation issue for n9600
- Version update to V5.8
- Add changelog
- Update crownqlte defconfig
- OSRC: G9650ZCU6CSJ2
- Merge SM-N9600 defconfig and dts
V5.7
- Merge G9650ZHU5CSH6 source which includes fix for the recent zero day on android binder driver
- Prevents potential wake-lock while on wireless charger
- Merge G9650ZCU5CSI3 source which includes some Note9 camera integrations
- Adds support for wireless adapters based on Broadcom 43436 chipset
- Increased wifi security
- Increased wifi hotspot security
- DHD 100.13.36.1 - 2019.07.31
Security Patch
- CS8424803(By Choi Hyeonu) SI-14869: Moved the length check routine for the nlioc variable before accessing it in the wl_cfgvendor_priv_string_handler() function
DHD 100.13.36 - 2019.05.24
New Feature
- CS5350346(By Jung Junyeop) Fake AP - Fixed to provide correct channel information for beacon receive result
- Enable to support Fake AP
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
- WIPS attack warning reporting
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
Security Patch
- CS8069399(By Kang Hyung Wook) SI-13926 Fixed use-after-free in the wl_cfg80211_set_mgmt_vndr_ies function
Others
- CS7939107(By Kim Tae-Yong) Included memdump value prints in the dump information
- Added missing options into the Kconfig file
DHD 100.13.32 - 2019.04.26
Kernel Panic
- CS7696936(By Min SungBin) Fix misspelling of CUSTOMER_HW4_DEBUG definition
- CS7706946(By Min SungBin) Fixed to avoid kernel panic due to race condition of cfg->scan_request
Security Patch
- CS7860687(By Kang Hyung Wook) SI-12455: Fixed use-after-free write in dhd_set_monitor() function
- CS7949699(By Choi Hyeonu) SI-14074: Fixed Security issue, Potential stack-based buffer overflow in dhd_pktfilter_offload_set
- CS7956197(By Choi Hyeonu) SI-14130: Fixed the multiple NULL pointer dereference in wl_cfgvendor.c
Others
- CS6844193(By MinSoo Kim) Changed log level of LQCM report
- CS7099653(By Nitesh Suthar) Enabled frameburst to enhance throughput for BCM43436 projects
- CS7362375(By Gu Ja Heon) Added Private command in order to receive every beacon in Suspend
- CS7526157(By Suthar Nitesh) Fixed DualBandConcurrency field in .softap.info
- CS7765577(By Park Heebae) Wifi-on time reduction by reading necessary CIS information
- CS7827257(By Choi Hyeonu) Fixed kernel panic caused by invalid memory access
- CS7834653(By Kang MinHo) Removed redundant TX error prints during suspend in SDIO
- CS7884436(By Beom Jip Kim) Fixed to cancel p2p listen offloading by framework scan request
- CS7892037(By Sun Yinghan) Fixed to support W2018/KELLY Android P OS upgrade
DHD 100.13.31.1 - 2019.04.19
Others
- CS4726130(By Min Hyun-Ki) Added User priority to AC mapping in case of various DSCP types that may not compatible with RFC8325
- CS6951980(By Min Hyun-Ki) Changed the UP to AC mapping of CS6 based on the RFC8325
DHD 100.13.31 - 2019.02.15
Others
- CS7241767(By LEE EONJI) Added more logs for the DPC schedule error debugging
- CS7299641(By Kim MinSoo) Enabled LB_TXP for MSM8998 Platform
- CS7323375(By kwon Jaecheol) Enabled the softap.info file support in BCM4359 platform
- CS7362527(By Hyeonu Choi) Cancel P2P listen offloading operation when SoftAP brings up
- CS7363197(By Junhak Lim) Fixed prevent issues
- CS7386068(By Lee Gibum) Disabled frameburst for "2.4Ghz + SoftAP" (Drame & Great projects)
- Fixed the scan failure when p2p listen offload is triggered
- Fixed to abort scan when connection/disconnection requested
- Prevented the bus suspend by the PCIe Runtime PM from abnormal ISR status
V5.5
- Merge G9650ZHU5CSG8 source which includes some stock Samsung debugging sanity checks and increase of stability
- Prevent possible IO/wake-locks when accessing sdcard
V5.4
- Merge G9650ZCU5CSFB source which includes additional ethernet support and additional battery stats support
- Removed more verity from the appended dtb
- Finally fixed FK Manager compatibility!! (ie no longer need to reflash Magisk)
V5.3
- Added Conservative gov for G9600 (sorry I could have sworn I included this in V5.2)
- Fix stability issues
- Remove Interactive governor
V5
- Removed Defex
- Removed Samsung rooting protections
- Removed RKP (Realtime Kernel Protection)
- Added Conservative cpu governor
- Sanity checks for video drivers and the power share feature
- Added support for broadcom 43456 wireless cards
- Added ddhd random mac scanning
- Added more security to wifi hotspot to protect from ARP attacks,
- CS7111512(By LEE EONJI) Detect turn on failure in factory binary
- CS7299329(By Kim Yu-Kyoung) Fixed SoftAP CTS fail due to interface creation failure
- Blocked WLC_E_ROAM event to fix wakes-up frequently under weak signal AP
- Changed error results of GETSTAINFO private command to BCME_UNSUPPORTED if the BIGDATA_SOFTAP is not supported
- Fixed kernel panic during mfg mode interface creation
- CS7091164(By Kang Hyung Wook) SI-13561: Fixed kernel heap overflow security issue at dhdpcie_downloadvars
- CS7091371(By Kang Hyung Wook) SI-13584: Fixed kernel panic due to access to not allocated memory
- CS6785460(By Jeong Min Cheol) Send HANG event to the framework for the sequential private command failure
- CS7003600(By Kang MinHo) Support android private command for restoring roam/scan parameters
- CS7094302(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7103552(By LEE EONJI) Fixed the recovery routine to fix the D3_ACK timeout issue
- CS7119174(By Kim Seong Hwan) Avoid HANG event indication due to sequential private command failures in case of unsupported error
- CS7137399(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7141596(By Suthar Nitesh) Fixed MHS operates with STA mac address
- Control HANG report for consecutive Android private command failure by sysfs
- Increased the NUMBER_SEQUENTIAL_PRIVCMD_ERRORS from 4 to 7
- Taking a SOCRAM dump in the sequential private command error case
- CS6935603(By Hong Min Whoa) SI-13638: Fixed Kernel warning message by restructuring the DMA_LOCK and DMA_UNLOCK
- CS7091347(By Kang Hyung Wook) SI-13585: Fixed kernel panic due to write buffer exceeds the size
- CS6650676(YeJi Yoon) Fixed mismatch connect status between framework and DHD
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6715508(By Choi Hyeonu) Exported sysfs for ADPS bad AP list
- CS6744438(By Yoon Jae Ho) Fixed duplicated roaming notification to WPA supplicant during FT roaming
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6856753(By kwon Jaecheol) Added the dual interface capability filed in the SoftAP info file (.softap.info)
- CS6870793(By Tae-Yong Kim) Fixed prevent issues
- CS6871138(By Lee Gibum) Configure AER registers to debug PCIE ERROR ATTN issues
- CS6880409(By Sung-gi Choi) Fixed prevent issues
- CS6887298(By Min Whoa Hong) Fixed prevent issues
- CS6928243(By Sung-gi Choi) Fixed prevent issues
- CS6935678(By Hwang MinSik) Fixed array out of bound issue from sysfs mac address
- CS6984743(By Min SungBin) Print DPC schedule request timestamp for ROT issue
- CS6985032(By LEE EONJI) Enabled DHD_RECOVER_TIMEOUT for D3_ACK missing case on 4359C0 and 4361B0
- CS6993967(By Jeong Min Cheol) Added last_d3_inform_timestamp to check root cause of ROT
- CS7042030(By Min SungBin) Implemented the new API to sync up the status between RC and EP to avoid unwanted L1ss configuration
- Changed the DHD_COMMON_DUMP_PATH for non-BCM4375 Android P OS projects
- DHD driven random mac enable by default for 4361B0
- Enable frameburst for standalone 2.4GHz SoftAP on Dream and Great project
- Wi-Fi Sharing-Lite feature support for Android P OS
- CS6461136(By Min SungBin) Fixed for kernel panic due to stack overflow at get_roamscan_channel_list()
- CS6302259(By Kang Hyung Wook) Supported DHD driven Random MAC feature
- CS6324532(By Choi Hyeonu) Port files under /data/vendor/conn to sysfs after Android P OS
- CS6396705(By Min SungBin) Added additional timestamp log to debug resumed on timeout issue
- CS6398346(By Hyeonu Choi) Fixed prevent issues
- CS6516071(By Choi Hyeonu) Fixed for corner case of schedule_timeout() API at dhd_timeout_expired()
- CS6536174(By Choi Hyeonu) CS6433018(By Choi Hyeonu) Fixed prevent issues
- CS6594869(By Min SungBin) Triggering Kernel panic for the scheduling problem only if the memdump mode is enabled
- CS6600348(By LEE EONJI) Implemented 4359c0/GraceR P OS Wi-Fi sharing feature
- CS6658253(By Choi Hyeonu) Fixed random mac setting issue instead of otp mac
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6713692(By Kim MinSoo) Fixed NET_RX delay issue
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6791516(By Lee Gibum) Fixed the unexpected frameburst enable on standalone SoftAP in 2GHz
- CS6791556(By Hwang MinSik) Removed CR/LF character at .cid.info including sysfs
- CS6809444(By Hwang MinSik) Unified DHD_COMMON_DUMP_PATH for the Android P OS project of all chips
- Changed the timestamp value to Kernel local time to debug resumed on timeout and scan timeout issues
- Defer RxBuf post size based on the rxbufpost_sz iovar return value for monitor mode
- Disabled DHD_LB_IRQSET for Exynos8890 platform
- Dump AER HeaderLog registers in configuration space for PCIe debugging
- Dumping PCIe registers for PCIe debugging enhancement
- Fixed VHT features enable issue from GraceR project
- Fixed unexpected RSDB mode configuration for legacy RSDB chip
- Implemented the debug code to check if the scan timeout or resumed on timeout happens due to the DPC scheduling problem
- Refined TDLS initialization code
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
Thanks to @djb77 for the ramdisk patches
You guys are the best!

Reserved

I've had it working for a while using your instructions.. something I'm missing here ?
Sent from my SM-N9600 using Tapatalk

mentathf said:
I've had it working for a while using your instructions.. something I'm missing here ?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
I don't understand what you mean.
This is an updated pie kernel.
I haven't made anything for pie on the note9 before.
Sent from my Pixel 2 XL using Tapatalk

It feels so good to be rocking pie rooted on the n96000. Kinda hilarious because i went and purchased an n960fds last month to get pie/root. I no longer have to live without google camera as it doesnt work on eynos .Thanks alot!

Thank you so much @klabit87 for your continued support of this amazing phone

@klabit87 Thanks a lot for the kernel. I just wonder if after flash, something get lost.. for example encryption.. Samsung health.. or any knox crap dependencies.. Thanks!

andrew.mackew said:
@klabit87 Thanks a lot for the kernel. I just wonder if after flash, something get lost.. for example encryption.. Samsung health.. or any knox crap dependencies.. Thanks!
Click to expand...
Click to collapse
Anytime you trip Knox when you unlock your bootloader you will loose something. Encryption is an option and a choice.
Health and whatnot can be fixed but the kernel is not responsible for it.
Sent from my Pixel 2 XL using Tapatalk

Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
You guys are the best![/QUOTE]
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull

Homefix said:
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
You guys are the best!
Click to expand...
Click to collapse
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull[/QUOTE]
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.

klabit87 said:
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull
Click to expand...
Click to collapse
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.[/QUOTE]
OMG I have been googelin for 2 days ,Not a mention of that. Going to try now.

Homefix said:
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.
Click to expand...
Click to collapse
OMG I have been googelin for 2 days ,Not a mention of that. Going to try now.[/QUOTE]It was mentioned in the official kernel source release notes which should be included in the osrc branch.
Sent from my Pixel 2 XL using Tapatalk

How did the test build go @Homefix ?
Sent from my Pixel 2 XL using Tapatalk

In light of the most recent update to FK Manager see here for details ------->> https://twitter.com/franciscof_1990/status/1215673739435704320?s=20
I have added support for the kernel download configuration which will allow you to update directly within the app. It will also notify you when an update is ready.
Check the OP for the links to the configuration.
Just copy the link address and paste into the "Import a kernel download configuration" box and done.
You can remove and add different ones if you want as well.

Also wanted to note that I will still post the updates in the OP. I am not going to make the updates only available through the app.
With that said, V5.8 will drop today

New minor update to v5.9.
This will make using gsi and most up to date/latest firmware versions much easier and more compatible.
Sent from my Pixel 2 XL using Tapatalk

klabit87 said:
New minor update to v5.9.
This will make using gsi and most up to date/latest firmware versions much easier and more compatible.
Click to expand...
Click to collapse
Awesome, thanks man! Flashing through FKM worked perfectly as well. Everything seems to be running great.

klabit87 said:
How did the test build go @Homefix ?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sorry I was away,
Yes it went perfect. Thank you.
However since android 4.4 I have compiled kernels and modules with ease.
I really don't have the time to commit to my hobby(Debian on Android) like I used to, so my reading and experience has slipped a bit.
Now I read Android 8.0 and up have "Modular Kernel splitting the device kernel into a system-on-chip (SoC), device, and board-specific deliverables ".
For reasons "ensure a workable booting system remains on the disk during an over-the-air (OTA) update. This approach reduces the likelihood of an inactive device after an update, which means fewer device replacements and device reflashes at repair and warranty centers" as explained here: https://source.android.com/devices/tech/ota/ab_updates.
Well that's all fine but I still cannot figure out how to tell the system upon bootup to load a specific module. How would I load the module from adb or terminal. The older way ,depmod -a , insmod , modprobe, seems to have no effect with android 8 and up.
I have successfully built modules with:
CONFIG_MODULES=y (and not with...CONFIG_MODULES=m)
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
After flashing kernel, I can see the module folders under /sys/module and within that folder is another, "parameters" and an empty "uevent" file. Within the "parameters" folder is a file "oom_pages" the content is "256"
So how would I load say "virtio"
The old way would work:
1st: depmod -a
2nd: modprobe virtio
Not working with android 8
By the way Im using ubuntu 16.04 image mounted here: mount -t ext4 -o rw,noatime /dev/block/mmcblk0p2 $mnt
$mnt=/data/local/Linux
As a side note: I like to play around with qemu , virt-manager, (windows-xp runs fast enough to be usable with this snapdragon)
and I can run full Minecraft , haha.

Homefix said:
Sorry I was away,
Yes it went perfect. Thank you.
However since android 4.4 I have compiled kernels and modules with ease.
I really don't have the time to commit to my hobby(Debian on Android) like I used to, so my reading and experience has slipped a bit.
Now I read Android 8.0 and up have "Modular Kernel splitting the device kernel into a system-on-chip (SoC), device, and board-specific deliverables ".
For reasons "ensure a workable booting system remains on the disk during an over-the-air (OTA) update. This approach reduces the likelihood of an inactive device after an update, which means fewer device replacements and device reflashes at repair and warranty centers" as explained here: https://source.android.com/devices/tech/ota/ab_updates.
Well that's all fine but I still cannot figure out how to tell the system upon bootup to load a specific module. How would I load the module from adb or terminal. The older way ,depmod -a , insmod , modprobe, seems to have no effect with android 8 and up.
I have successfully built modules with:
CONFIG_MODULES=y (and not with...CONFIG_MODULES=m)
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
After flashing kernel, I can see the module folders under /sys/module and within that folder is another, "parameters" and an empty "uevent" file. Within the "parameters" folder is a file "oom_pages" the content is "256"
So how would I load say "virtio"
The old way would work:
1st: depmod -a
2nd: modprobe virtio
Not working with android 8
By the way Im using ubuntu 16.04 image mounted here: mount -t ext4 -o rw,noatime /dev/block/mmcblk0p2 $mnt
$mnt=/data/local/Linux
As a side note: I like to play around with qemu , virt-manager, (windows-xp runs fast enough to be usable with this snapdragon)
and I can run full Minecraft , haha.
Click to expand...
Click to collapse
I haven't messed with modules in a long time. I just include what I want in the kernel instead of building modules lol.
I would have to do a little investigating to find the answer you're looking for tbh.
But that's awesome that you can run such different software on your device, mainly the qemu stuff.
If I recall correctly, you need to allow unsigned modules to be loaded as well as remove lkmauth from the kernel.
Sent from my Pixel 2 XL using Tapatalk

Kernels are updated and live for Android 10!