Develop Bugs

tun.ko for kernel 2.6.29-36d5cb8d (Stock 2.1 firmware)

Hi everyone!
Just wanted to ask if anyone could upload their tun.ko for the said kernel. I'm trying OpenVPN and it is one of the requirement for the program to run.
Thanks a lot in advance!

blue_algae said:
Hi everyone!
Just wanted to ask if anyone could upload their tun.ko for the said kernel. I'm trying OpenVPN and it is one of the requirement for the program to run.
Thanks a lot in advance!
Click to expand...
Click to collapse
You can't build a loadable kernel module without recompiling the kernel, hence theoretically you must also change the kernel....
I think that the stock kernel has this model built inside the kernel, so you should be able to just run OpenVPN and it should work, no need to load anything.
If this still does not work for you, look at the FlyKernel from my signature, it should solve the problem for you (if you try it and there are problems let me know on it's thread).

Thanks for the reply! I cant find tun.ko anywhere so I guess it is missing from the official rom. Im getting tired of the stock rom anyway so maybe its time to load up some custom prepared eclair or froyo.;-) i'll try cronos droid as im curious of what divx library is for. Maybe it can paly divx natively? Anyway, thanks again!

blue_algae said:
Thanks for the reply! I cant find tun.ko anywhere so I guess it is missing from the official rom. Im getting tired of the stock rom anyway so maybe its time to load up some custom prepared eclair or froyo.;-) i'll try cronos droid as im curious of what divx library is for. Maybe it can paly divx natively? Anyway, thanks again!
Click to expand...
Click to collapse
I'll try to clarify what I tried to say above: To the best of my knowledge there is no tun.ko in the official ROM. This is the way it should be. And yet openVPN will still work for you. Did you try to use OpenVPN and have some problem with it?

hey, thanks for taking time helping me out.
I was able to install openvpn. I can enable openvpn too, however, may problem is I can't use my openvpn configuration. For some reason, I can't make my openvpn configuration enabled. No error whatsoever. When I click the check mark for the configuration, it just blinks. Here's my hunch, In the tun module settings, there is this option: "path to tun module" which I dont know where to point to since the stock kernel does not have tun.ko. I downloaded a couple of tun.ko that I saw here and a couple of others I found using google. But since these are all not for the kernel that I have, it all didn't work. what do you think should I do?

blue_algae said:
hey, thanks for taking time helping me out.
I was able to install openvpn. I can enable openvpn too, however, may problem is I can't use my openvpn configuration. For some reason, I can't make my openvpn configuration enabled. No error whatsoever. When I click the check mark for the configuration, it just blinks. Here's my hunch, In the tun module settings, there is this option: "path to tun module" which I dont know where to point to since the stock kernel does not have tun.ko. I downloaded a couple of tun.ko that I saw here and a couple of others I found using google. But since these are all not for the kernel that I have, it all didn't work. what do you think should I do?
Click to expand...
Click to collapse
Ok, I was sure for some reason that openVPN should work well with the stock kernel (personally I don't use VPN so can't really check it myself).
I think your best bet now is to try a different kernel. You can try my kernel from my signature (flykernel) which should work on almost any ROM. Or if you where planning to checkout different ROMs, go for it and hopefully it will work for there.

just finished reading your kernel details and it sounds interesting! I'll give it a try now.
and yea, thanks for the help and for your kernel.

Logcat from stock Tmobile ROM to fix WIFI calling app on CM

As subject says, Devs need a logcat from a factory Tmobile ROM with WIFI calling app in order to get it working on CM 7.1: maybe you have kept the stock ROM because CM doesn't have WIFI calling! If you have the stock ROM installed please consider posting a log spanning an instance of starting the WIFI calling app and letting it connect to the network. This is your chance to be a productive cog towards progress round these parts so someone please kick in!
The dev requests that the following be added to the build prop:
"set ro.sys.atvc_allow_gki_log=1"
BTW, if you are not familiar with all the jargon of adding a line to your build.prop and using ADB to get a logcat but still want to help now is your chance to learn. Several of us would be more than happy to guide you through the process!
Progress on this issue can be tracked here: http://code.google.com/p/cyanogenmod/issues/detail?id=4283
Thanks!

Close this one out...we have donor logs
We found logs through other means

[Q] kernel(s) with wifi N support?

at firts i am running cm7.2_rc_buzz_kang(03-14-2012),with original radio(never had to flash another,just few times sometimes reflashed to make gps work),custom mtd
i would like to ask devs for this question, but i cant, so i try at least here...
some time ago our router at home has been changed and so has wlan...and that started to cause me problems,because i cant set router up for my phone to provide "g" wifi which works flawlesly..(actually,discovering,that everything is caused by "n" wifi provided by router was very funny,because it was the last thing i thought i could be ) however..after some googling and much xda reading i found app called Wifi fixer,which in most cases fixes my problem,but it doesnt work in 100% cases,and its not the "coolest" solution
few days ago i found Sympnotics kernel,and flashed it,one of reasons was its declared "n" wifi fix,which didnt work...i know,its beta,im not complaining,just saying what i found...btw thats the only thing,that is not good FOR ME on that kernel
so i thought to look for another...
i found infinityplay,which didnt work in "my" way,neither did "official" arco68s,neither last hcdr.kernel_v4.2...
the only one i found working is HCDR.Kernel_v4..
my next idea was (i am noob,so sorry... ) to copy bcm4329.ko (which should be wifi module of kernel) from HCDR.Kernel_v4 to SympKernV4.1..that (surprisingly ) didnt work...at least i tried...
so there is my question...(in this moment,youre the only person who i know is developing kernel,most for Sympnotic) would it be possible to have your kernel with hcdr.kernel_v4 wifi module??
if i have known to do this on my own,i wouldnt bother to ask here, but i have no idea how to build my own kernel,even how to take one,change wifi module and again make flashable zip...
sorry for my english,its not my native language
thx you all here
edit:i have the same problem with cm9,bulit does not matter...btw with hcdr.jacobs v4 wifi does not work...

Hyperdrive RLS10 Issue

I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?

mrpoe222 said:
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
Click to expand...
Click to collapse
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.

BWolf56 said:
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
Click to expand...
Click to collapse
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.

mrpoe222 said:
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
Click to expand...
Click to collapse
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.

BWolf56 said:
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
Click to expand...
Click to collapse
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.

mrpoe222 said:
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
Click to expand...
Click to collapse
Clearing client database means clearing data and cache in the play store app. That's what worked for me on with that issue...or loading another Google account then deleting it then adding your main one.

Verizon Galaxy S3 running RLS10 - call echo issue
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.

jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
the echo is just on your end, correct?
go to settings >accessibility and make sure turn off all sounds is not checked to begin with. now go to settings > sound and make sure your volume levels are correct and sound is turned on.
also, phone > menu > Call settings > additional settings and then uncheck noise reduction. some people have reported less echo and clearer calls with this turned off.

jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
A few have reported the same issue on the thread but no real solution beyond hit speaker on then off and it goes away. Reason that works ? I have no clue.

[Q]S4 Mini LTE After Root Wi-Fi & Bluetooth Not Working

Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye

KyeWalker said:
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
Click to expand...
Click to collapse
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?

TNCS said:
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
Click to expand...
Click to collapse
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye

KyeWalker said:
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
Click to expand...
Click to collapse
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890

summarise.....
TNCS said:
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
Click to expand...
Click to collapse
So I've come to a conclusion after many weeks of testing and searching........ Unfortunately the overclock kernel for "TouchWiz" roms is unstable........ looking through forums I can see that F4k has only realised a "test" version....... on the other hand I have found a kernel from Vikinger (if spelt correctly) that's has fixed my issue and is working great... shame it isn't overclocked nor under and has no additional governors..... any one with ideas please feel free to share..... many thanks.
Kye