Database Info

Unable rebuild Galaxy Note2 LTE (N7105)

Hi Experts,
I have tried to rebuild the kernel for Galaxy Note2 LTE (N7105) from the source downloaded from opensource.samsung.com.
The kernel can be compiled without error and I use ramdisk from latest firmware to create boot.img. After that, boot.img can be flashed without problem to the phone and it can reboot correctly.
But, the two button (MENU and BACK) does not work and exFAT module can't be loaded.
I have no problem doing this for Galaxy S3 (i9300) and Galaxy Nexus (i9205) but only this time I always fail.
Can anybody point what are the things I missed out?
Thanks in advance.

AW: Unable rebuild Galaxy Note2 LTE (N7105)
aatjitra said:
Hi Experts,
I have tried to rebuild the kernel for Galaxy Note2 LTE (N7105) from the source downloaded from opensource.samsung.com.
The kernel can be compiled without error and I use ramdisk from latest firmware to create boot.img. After that, boot.img can be flashed without problem to the phone and it can reboot correctly.
But, the two button (MENU and BACK) does not work and exFAT module can't be loaded.
I have no problem doing this for Galaxy S3 (i9300) and Galaxy Nexus (i9205) but only this time I always fail.
Can anybody point what are the things I missed out?
Thanks in advance.
Click to expand...
Click to collapse
IIRC, the sources for touchkeys are missing for some reason in this release. There should be a thread about this, at the beginning of this development section.
What's your error with exfat module?
Gesendet von meinem GT-N7105 mit Tapatalk 2

DerTeufel1980 said:
IIRC, the sources for touchkeys are missing for some reason in this release. There should be a thread about this, at the beginning of this development section.
What's your error with exfat module?
Gesendet von meinem GT-N7105 mit Tapatalk 2
Click to expand...
Click to collapse
Thanks for pointing that...
I do comparison between 7100 source and 7105 source and I found 1 folder missing under /driver/input/keyboard/cypress...
The error message I got while trying to load the module is Exec Format Error as attached.
Put this command "if(!strncmp("exfat_", mod->name, 6)) return 1;" under kernel/module.c (original code by AndreiLux) seems doesn't help..
Sorry for this noob questions...
EDIT: Found something interesting reading about FTRACE... going to test it tonight...

No success
After playing around with N7100, I manage to make the capacitive button works again.. but no succes to load exfat module
Any idea highly appreciated...
Thanks..

AW: Unable rebuild Galaxy Note2 LTE (N7105)
aatjitra said:
After playing around with N7100, I manage to make the capacitive button works again.. but no succes to load exfat module
Any idea highly appreciated...
Thanks..
Click to expand...
Click to collapse
There also is a thread here already: trying to load proprietary kernel modules, like exfat.
There are already some information.
Also, what did you change at the kernel already?
Gesendet von meinem GT-N7105 mit Tapatalk 2

DerTeufel1980 said:
There also is a thread here already: trying to load proprietary kernel modules, like exfat.
There are already some information.
Also, what did you change at the kernel already?
Gesendet von meinem GT-N7105 mit Tapatalk 2
Click to expand...
Click to collapse
Yes. I read that thread yesterday. I also got the same message as mentioned in that thread.
I believe something is wrong with the source as I tried to rebuild the kernel without any change to the code. This is normally what I did, I mean, I will try to rebuild the kernel without modification to see if it is working. If yes then I start to modify the kernel based on cherry pick enhancement and recompile it.
So when I tried to rebuild this N7105 kernel, I found that the kernel is not working properly.
Anyway, thank you very much for your respons. Really appreciate that.

Looking for a couple of fixes

Hello all,
I recently compiled my own version of CM10.1 from source on my Ubuntu dev machine. I absolutely love it, and the fact that I am running my own ROM!! I only have a couple issues, and I've searched high and low, but can't seem to find any fixes (that work anyway). I would greatly appreciate it, if someone could point me in the right direction.
-Bugs-
1. Camera fc's when changing ANY setting, requiring a reboot.
2. GPS is ALL KINDS of jacked up..
3. Bluetooth doesn't work, or if I try to use speech to text I have to wipe/install in order to even be able to type a message.
Thanks in advance for any assistance. It will be GREATLY appreciated! I'm also sure that I could find my way to that infamous "Thanks" button. I could maybe buy you a beer, even.

Is it the unmodified cm source you are compiling? Did you extract the prebuilts?
Gesendet von meinem GT-N7105 mit Tapatalk 2

DerTeufel1980 said:
Is it the unmodified cm source you are compiling? Did you extract the prebuilts?
Gesendet von meinem GT-N7105 mit Tapatalk 2
Click to expand...
Click to collapse
I'm unsure of exactly what you mean by "unmodified."
Yeah, I extracted the prebuilts, and pulled the device specific code/drivers from the phone.
Vielen dank for the timely response!!

Snypercell said:
I'm unsure of exactly what you mean by "unmodified."
Yeah, I extracted the prebuilts, and pulled the device specific code/drivers from the phone.
Vielen dank for the timely response!!
Click to expand...
Click to collapse
I am referring to your own version of cm. I am wondering if you changed some parts of code
Gesendet von meinem GT-N7105 mit Tapatalk 2

Snypercell said:
I'm unsure of exactly what you mean by "unmodified."
Yeah, I extracted the prebuilts, and pulled the device specific code/drivers from the phone.
!
Click to expand...
Click to collapse
This could be your problem. The prebuilts we use are specific blobs from the different builds and many probably are not longer valid when pulled directly from the phone
Instead of using prebuilds, use the "TheMuppets" repo (https://github.com/TheMuppets/proprietary_vendor_samsung)
EDIT: Just realized I was looking in the wrong forum. These blobs should work with the developer edition but i'm not 100% sure.

DerTeufel1980 said:
I am referring to your own version of cm. I am wondering if you changed some parts of code.
Click to expand...
Click to collapse
Ahh.. Okay, sorry.
No, I didn't change anything at all. I just wanted to get a good, clean build first, then I will start customizing more and more. Thanks again. :good:
Desterly said:
This could be your problem. The prebuilts we use are specific blobs from the different builds and many probably are not longer valid when pulled directly from the phone
Instead of using prebuilds, use the "TheMuppets" repo (https://github.com/TheMuppets/proprietary_vendor_samsung)
EDIT: Just realized I was looking in the wrong forum. These blobs should work with the developer edition but i'm not 100% sure.
Click to expand...
Click to collapse
I really appreciate you looking into this for me. I read in a few forums about TheMuppets repo, but I haven't gotten around to trying it out. I am in the process of moving at the moment, but when I get my machine set back up I will give it a shot. Thanks.

Maybe really just try the muppets.
How did you get your device specific repos? Did you clone them manually, or did roomservice grep them for you?
Gesendet von meinem GT-N7105 mit Tapatalk 2

DerTeufel1980 said:
Maybe really just try the muppets.
How did you get your device specific repos? Did you clone them manually, or did roomservice grep them for you?
Click to expand...
Click to collapse
Immediately after running "./get-prebuilts," I cd'd to the root of /android/system, and ran "source build/envsetup.sh" to first get all of my cmds working, then I ran the breakfast cmd.
After the device specific code downloaded, I then ran the "extract-files" script with my phone connected via usb to pull the proprietary blobs.
I REALLY hope to get my Ubuntu machine up soon... I will then try TheMuppets repo. Thanks again.

[Kernel] Stock Lollipop Kernel with extras

If you have any feature requests let me know via the Feature Requests button above (the same goes for bug reports)
Downloads
Follow me on Twitter
Update App<--- Needs Testers
For CIFS
You have to use a patched version of cifs manager from here and add "noperm" in the options field.
I'm adding this functionality to the my app now.
XDA:DevDB Information
SuperPichu's Custom Lollipop Kernel, Kernel for the Nvidia Shield Tablet
Contributors
SuperPichu
Source Code: https://github.com/SuperPichu/shield-tablet-kernel
Kernel Special Features: CIFS Mount Support,SELinux Permissive,kexec-hardboot,Ext-SD Write Fix
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2015-02-24
Created 2014-12-09
Last Updated 2015-02-24

Nice work love to see where this is going

cheers! any plan for LTE version soon?

w.0.o.t said:
cheers! any plan for LTE version soon?
Click to expand...
Click to collapse
I would love too but I'm not sure how to build it for that. Would you be willing to test?

SuperPichu said:
I would love too but I'm not sure how to build it for that. Would you be willing to test?
Click to expand...
Click to collapse
i'll be more than happy to help.

Erm...sorry, I tried to figure out it via google but...Anybody could explain the benefits that came from a kernel with CIFS support? Thank you ^_^"

Alfonso87 said:
Erm...sorry, I tried to figure out it via google but...Anybody could explain the benefits that came from a kernel with CIFS support? Thank you ^_^"
Click to expand...
Click to collapse
transparent file streaming. meaning no buffer time. it's as if you're accessing the file in your internal storage. useful for streaming large files (like HD films) from your computer.
someone please correct me if I'm wrong though.

w.0.o.t said:
transparent file streaming. meaning no buffer time. it's as if you're accessing the file in your internal storage. useful for streaming large files (like HD films) from your computer.
someone please correct me if I'm wrong though.
Click to expand...
Click to collapse
It doesn't mean no buffer time but it essentially means that any app can access it and you don't have to rely on per-app support.
Buffer time is also usually lessened.

This really looks promising, gotta give a try. Thanks, man

SuperPichu said:
It doesn't mean no buffer time but it essentially means that any app can access it and you don't have to rely on per-app support.
Buffer time is also usually lessened.
Click to expand...
Click to collapse
thanks for the explanation.
I seem to recall if I use apps like es file explorer to access videos on pc, I'd have to wait until the full file being transferred to the device (I assume some sort of local temporary file would be created), and then only the video starts playing. however with cifs this was not the case. the video would just play normally as if it was located in the phone storage. note that this was my experience a couple of years back though.

Isn't the kernel the source for the knock on feature for waking up or closing the screen?
Sent from Bad Azz VZW LG G3 Cyan Tapatalk

Awesome work! thanks!,
Would it be possible to add some I/O Schedulers, like BFQ and such? and maybe faux sound?
That would be super epic if possible!

If someone could provide the boot.img or zip to flash that would be highly appreciated. I flashed the development kernel from the other thread and I'm getting a few random reboots.

kickassdave said:
If someone could provide the boot.img or zip to flash that would be highly appreciated. I flashed the development kernel from the other thread and I'm getting a few random reboots.
Click to expand...
Click to collapse
Interesting...
Do you have access to the nVidia developer site? You can grab the stock one from there before try this one.

CM17X said:
Interesting...
Do you have access to the nVidia developer site? You can grab the stock one from there before try this one.
Click to expand...
Click to collapse
To be fair. I think it may have been my deadline scheduler changes that caused the issue. Changed back to bfq and now OK.
Regarding using this kernel, I'm used to recovering from boot loops, blank screens etc etc. I have no issue testing beta/alpha stuff and appreciate the risks

SuperPichu said:
I would love too but I'm not sure how to build it for that. Would you be willing to test?
Click to expand...
Click to collapse
Build the same kernel, but swap the ramdisk. Having a published kernel doesn't ban you from asking questions in the kernel development thread. There is no point trying to reinvent the wheel when you could be driving.

twistedumbrella said:
Build the same kernel, but swap the ramdisk. Having a published kernel doesn't ban you from asking questions in the kernel development thread. There is no point trying to reinvent the wheel when you could be driving.
Click to expand...
Click to collapse
to be fair, that's what he did. my LTE connection still works upon flashing his LTE kernel, so all is good.

w.0.o.t said:
to be fair, that's what he did. my LTE connection still works upon flashing his LTE kernel, so all is good.
Click to expand...
Click to collapse
I didn't intend to be unfair by offering to help, but such is xda I guess.

twistedumbrella said:
I didn't intend to be unfair by offering to help, but such is xda I guess.
Click to expand...
Click to collapse
Wasn't implying you were being unfair honestly. English is not my native language, so it might have come across differently to you. Any help is obviously much appreciated.
Anyway, I'll let the thread to go back to kernel development. Cheers.

w.0.o.t said:
Wasn't implying you were being unfair honestly. English is not my native language, so it might have come across differently to you. Any help is obviously much appreciated.
Anyway, I'll let the thread to go back to kernel development. Cheers.
Click to expand...
Click to collapse
I wasn't cereal.

f2fs and encryption

Does anyone here know why the oneplus one completely poops itself when I attempt to encrypt an f2fs-formatted partition? Seems like it would only be a small issue. Or maybe it has to do with our drivers? Its always been a question of mine since I purchased this device.

F2fs encryption isnt enabled in the f2fs kernel driver. So it doesnt work.
Sent from my A0001 using XDA-Developers mobile app

DerRomtester said:
F2fs encryption isnt enabled in the f2fs kernel driver. So it doesnt work.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Is there any way to trigger it? I heard that f2fs encryption/decryption was disabled in kernel 3.4. Thanks.

jimmy19990 said:
Is there any way to trigger it? I heard that f2fs encryption/decryption was disabled in kernel 3.4. Thanks.
Click to expand...
Click to collapse
The support for f2fs encryption for the 3.4y kernel has been dropped. If you are a coding genius you can get it working with a lot of time and effort.

DerRomtester said:
The support for f2fs encryption for the 3.4y kernel has been dropped. If you are a coding genius you can get it working with a lot of time and effort.
Click to expand...
Click to collapse
Someone already has. Looks like it was a pretty simple solution too. F2FS on /data and /cache is working with full data encryption with an extra long custom boot password, on Tomom's 20190710 Linage Pie rom with Sultan's camera Hal. I thought it was too good to be true but it works, and it works great.

Stock kernel and F2FS support

Hello everybody.
After reading a thread in Oneplus 7 Pro kernel and roms subforum there it says that 7Pro STOCK kernel supports F2FS.
Do you know if the same happen with Oneplus 7 (not pro) on OOS 9.5.8?
Thanks in advance!

Teso79 said:
Hello everybody.
After reading a thread in Oneplus 7 Pro kernel and roms subforum there it says that 7Pro STOCK kernel supports F2FS.
Do you know if the same happen with Oneplus 7 (not pro) on OOS 9.5.8?
Thanks in advance!
Click to expand...
Click to collapse
Yes, F2FS works in stock ROM.
But I suggest you to flash Arter97's kernel and F2FS-optimize. The kernel is pretty updated with the F2FS sources.

Dan_Jacques said:
Yes, F2FS works in stock ROM.
But I suggest you to flash Arter97's kernel and F2FS-optimize. The kernel is pretty updated with the F2FS sources.
Click to expand...
Click to collapse
We just need now unified ROMs with the 7 pro boys! Getting dialog with them is the hard part as I keep getting ignored!!!!

Dan_Jacques said:
Yes, F2FS works in stock ROM.
But I suggest you to flash Arter97's kernel and F2FS-optimize. The kernel is pretty updated with the F2FS sources.
Click to expand...
Click to collapse
Do you know an updated guide to convert to f2fs for mobiles with slots A/B?
The ones I found aren't good or detailed enough.
(Neither haven't had replied from Arter's telegram channel nor xda thread)
Thanks in advance

Teso79 said:
Do you know an updated guide to convert to f2fs for mobiles with slots A/B?
The ones I found aren't good or detailed enough.
(Neither haven't had replied from Arter's telegram channel nor xda thread)
Thanks in advance
Click to expand...
Click to collapse
I just changed the /data filesystem through TWRP, rebooted and... ta-dah!

Dan_Jacques said:
Yes, F2FS works in stock ROM.
But I suggest you to flash Arter97's kernel and F2FS-optimize. The kernel is pretty updated with the F2FS sources.
Click to expand...
Click to collapse
That's fine but what about stock KERNEL (not just OOS). Or do we always have to flash a custom kernel in order to use F2FS
Regards

Teso79 said:
That's fine but what about stock KERNEL (not just OOS). Or do we always have to flash a custom kernel in order to use F2FS
Regards
Click to expand...
Click to collapse
When I mention stock ROM I mean all stock (ROM, kernel, fstab...). Just boot TWRP, format /data F2FS and everything will work.

I am under open beta 6 .Twrp 3.3.1-74 conversion data into N2fs without problem.