Recent content by wawyed

No, the return box is to dispose it, so you don't have to.

According to a kernel developer on this forum, he noticed a comment in the previous nvidia kernel source code disabling QC 2.0 charging to avoid battery swelling issues. They've probably removed that line of code, hence the increased risk. If they are doing a mass recall must be for a reason...

Easy fix hopefully :D

Check my edit I've just got it working by manually loading the modules: insmod fscache.ko insmod md4.ko insmod cifs.ko There must be a way of loading those modules at boot time.

I just flashed KS-033 with TWRP since it wasn't working with the other recovery, unfortunately the problem persists. I tried a different app but no results. I also tried mounting through command line but same error. I can see that the module is in the lib/modules folder but for some reason is...

Same problem. I also found this in the app thread that I'm using: "No such device". A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support. http://forum.xda-developers.com/showthread.php?t=756158

Did you find out if there is a problem with cifs/smb mounting or is it something in my end? Anyone else having problems with cifs/smb?

Yes same app but I was using a different kernel. The app is cifs mountmanager. Sent from my SM-G920F using XDA Free mobile app

Is CIFS shares working with 3.0? I'm getting mount: No such device.

Can't wait to get this kernel in OTA 3.0 so I can get CIFS working again :)

We've got another kernel that works with CIFS, maybe it's the implementation of it that you are using that's causing the issue?

How do you calibrate the touchscreen sensibility?

Would it be possible to add CIFS support?

Should we wait then?

Awesome man :D. Waiting for it :)