Franco why don't you leave links to older versions of your kernels? I wanna get back to #2
Sent from my Galaxy Note with DarkyROM 3.3
Here you go
Franco why don't you leave links to older versions of your kernels? I wanna get back to #2
Sent from my Galaxy Note with DarkyROM 3.3
updated to version #5. Got the app
Franco, Why did you removed the OC support and you do have any plans to bring it back?
I never had OC
Ok last night I did a rebase and removed useless code. Also staying at 2.6.35.7 to avoid problems coming from stupid and useless mainline kernel patches. Going to test this over the day and see how it goes but initial testing looks veeery good.
Sent from my GT-N7000 using xda premium
ok, I installed v5 over cf-root (xla6) and the installation went fine.
I went to use tun.ko but could find it in /lib/modules...
I then realized I had a permission problem...
trying fix_permissions script gives me bus error..
and trying to run "fix permission" from cwm doesn't work...
Any idea of what I should do ?
Ok, Now i'm confused. I can't remember if it was #2 or #3. But SetCPU allowed overlock. up to 1.6something.
Samsung releases patch's to kernel or their full kernel?
---------- Post added at 03:03 PM ---------- Previous post was at 02:48 PM ----------
If the file isnt there this isn't a permission problem.
It's the file missing.
Use Francos App to load Tun module. Works like a charm.
Tun is a module used to connect vpn networks using openvpn for example.
Can somebody help me with this permission issue ?
when you go in shell with better terminal, su -,then find / -name tun.ko, I get a load of permission denied...
Can somebody tell me how can I fix it ?
Also, using fix_permissions is shell gets me bus error and fix permissions in CWM doesn't change anything...
# pwd ; ls -l tun.ko ; uname -a
/lib/modules
-rw-r--r-- 1 501 20 25986 Feb 17 00:00 tun.ko
Linux localhost 2.6.35.13-franco.Kernel-5 #13 SMP PREEMPT Fri Feb 17 02:14:07 WET 2012 armv7l GNU/Linux
# insmod tun.ko
# lsmod
tun 13408 0 - Live 0xbf05d000
What governor are you using btw? Can you try to reproduce the sleep of death and then start adb? If you can start adb with the screen of death then I'm 99% sure it's a rom problem because if it was kernel **** it would simply kill the phone altogether.
I never had OC
Ok last night I did a rebase and removed useless code. Also staying at 2.6.35.7 to avoid problems coming from stupid and useless mainline kernel patches. Going to test this over the day and see how it goes but initial testing looks veeery good.
Sent from my GT-N7000 using xda premium
#5 seems much easier on the battery compared to #4, but I will need more time to be sure. I did change the governor to ondemand if that's interesting to know. But again a job well done!
Does the rebase and removal of useless code resulted in #5 or will it be gonna be #6?
Franco is that kind of guy i guess, he's just ignoring people when they report bug , same thing was happening with his GB kernel #10, i think there was at least 100 people tellin him that he has a problem with SOD and what he did? Nothing, just ignored them
I guess now it's the same thing with WiFi
Franco , Franco where r u ?
Another big moment in Gnote history.
@Galaxy Note™…