Database Develop

DroidX source posted! tun.ko should be possible now

Sources are here:
opensource.motorola.com/sf/frs/do/viewRelease/projects.droidx/frs.droidx_source.shado_x3_1_13_5_10
Hopefully I'll get some time to work on tun.ko for openvpn or vpnc.
But if someone beats me to it, please post it here.
Jeb

Downloading the source and pre-req's now. Will work on the tun.ko when I get back from dinner if no one else has it done.

Droid X source code! What!? Does this mean a bright future could be ahead for us?
XDA App = Pwnage

jebc4 said:
Sources are here:
opensource.motorola.com/sf/frs/do/viewRelease/projects.droidx/frs.droidx_source.shado_x3_1_13_5_10
Hopefully I'll get some time to work on tun.ko for openvpn or vpnc.
But if someone beats me to it, please post it here.
Jeb
Click to expand...
Click to collapse
What exactly is this?

drew630 said:
Downloading the source and pre-req's now. Will work on the tun.ko when I get back from dinner if no one else has it done.
Click to expand...
Click to collapse
Good luck to you and all for any work on this sweet phone. You rock!
Sent from my DROIDX using XDA App

Hi Drew,
Did you have any luck with tun.ko?
Thanks & all the best!

You can click in the bottom right of that that link and download all the files in one zip. SHADO_X3_1.13.5.10.zip is around 275MB.
I have unzipped that, then untarred all the individual archives.
According to the README, you need some files from source.android.com, but their link doesn't work, so that will take some more digging. (maybe I missed something...)
It appears to be the complete build process. I was just hoping to jump in and get a tun.ko modules compiled, but I still can't find the kernel config (I was just quickly looking around).
Anyway, bottom line is that I will have to get up to speed on the android build process, not just the cross compiled kernel process. This will take me some more time.
If anyone gets one before me, please post.
Thanks, Jeb

Anyone had any luck yet?
Sent from my DROIDX using XDA App

hmmm... I think that you should be able to compile the kernel with the default config options, but just enable the tun/tap module... I don't think that the module would really depend too heavily on any of the other config options?

I have compiled the module multiple times with multiple config files but none work. I get a exec failed error which is presumably because i compiled for the wrong architecture.
I have tried all the omap3 configs i found and the defconfig with no luck. I am away today but will look at it again tomorrow.
Sent from my DROIDX using XDA App

I'm no droid expert but it looks like according to the droid readme file you want ARM arch, but the compiler that youo should be using is arm-eabi-gcc (comes from the prebuilt tools from android) - in the Makefile set CROSS_COMPILE to /path/to/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- (or whatever the path to the file is on your build environment)
All the best,

Okay, after a bunch of hours I finally got it compiled
The 'exec format error' that you were probably seeing is not because it was compiled for the wrong architecture. I originally compiled the kernel modules with the default .config file that 'make menuconfig' generated.
When I tried to load it, I got the 'exec format error'. 'dmesg' showed:
<3>[46706.378570] tun: version magic '2.6.29 mod_unload modversions ARMv5 ' should be '2.6.29 preempt mod_unload ARMv7 '
So, that gave me a big hint - after a few hours of customizing I finally got the .config file to a version that will properly compile and load the openvpn module.
I'm attaching the .config file (config.zip) and tun.ko file (tun.ko.zip)
*NOTE* - I have not tested the kernel module yet, so I have no idea if it works. Even if it does work, the .config file is the default one that I manipulated so that the tun module would compile. You probably don't want to use the .config file as it may not match all of the hardware and configs of the droid x. If someone has the actual droid x .config file used by motorola then that would be very helpful.
*update* - the attacked files *do not work*. The working version is available at http://forum.xda-developers.com/showthread.php?p=7417520

Hmm... it looks like tun.ko does compile and install, but is not working properly
# lsmod
tun 11392 0 - Live 0xbf00c000
sec 4808 0 - Live 0xbf000000
# cat /dev/net/tun
/dev/net/tun: No such device
#
The response should be 'cat: /dev/net/tun: File descriptor in bad state'
If we only had the .config file from motorola this would be a lot easier.

mab2 said:
Hmm... it looks like tun.ko does compile and install, but is not working properly
# lsmod
tun 11392 0 - Live 0xbf00c000
sec 4808 0 - Live 0xbf000000
# cat /dev/net/tun
/dev/net/tun: No such device
#
The response should be 'cat: /dev/net/tun: File descriptor in bad state'
If we only had the .config file from motorola this would be a lot easier.
Click to expand...
Click to collapse
I'll post on Motodev board for the running .config (they should have left it in the running kernel at /prog/config.gz ...)
Anyway, thanks trying -- could you post any tips on getting a dev env setup?
I've been using linux for years, but this is my first android setup.

jebc4 said:
I'll post on Motodev board for the running .config (they should have left it in the running kernel at /prog/config.gz ...)
Anyway, thanks trying -- could you post any tips on getting a dev env setup?
I've been using linux for years, but this is my first android setup.
Click to expand...
Click to collapse
I'm in the same boat as you - android newbie, linux veteran.
I started out by getting the whole android environment - http://source.android.com/source/download.html - and ran 'repo init -u git://android.git.kernel.org/platform/manifest.git' - all of that was just so I could get the prebuilt directory with the arm-eabi- files that will be used below.
Then I just downloaded the entire project from opensource.motorola.com - extracted it all, went into the kernel directory and hacked away at the .config file from there.
To compile the kernel I ran:
CROSS_COMPILE=/home/MY_USERNAME/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make -j 4 kernel
CROSS_COMPILE=/home/MY_USERNAME/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make modules
I spent a few hours with it - playing around with environment variables and modifying some Makefiles so I may have left out a small thing or two

It looks like running 'make mapphone_defconfig' created a functioning .config file and I used that to generate tun.ko.
I've posted the files at http://forum.xda-developers.com/showthread.php?p=7417520

Attachments removed as per OP's request.

mab2 said:
I'm no droid expert but it looks like according to the droid readme file you want ARM arch, but the compiler that youo should be using is arm-eabi-gcc (comes from the prebuilt tools from android) - in the Makefile set CROSS_COMPILE to /path/to/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- (or whatever the path to the file is on your build environment)
All the best,
Click to expand...
Click to collapse
Thanks but I already got that, been compiling kernels for other Android devices for a while...

drew630 said:
Thanks but I already got that, been compiling kernels for other Android devices for a while...
Click to expand...
Click to collapse
didn't know that - no harm intended
All the best,

mab2 said:
Okay, after a bunch of hours I finally got it compiled
The 'exec format error' that you were probably seeing is not because it was compiled for the wrong architecture. I originally compiled the kernel modules with the default .config file that 'make menuconfig' generated.
When I tried to load it, I got the 'exec format error'. 'dmesg' showed:
<3>[46706.378570] tun: version magic '2.6.29 mod_unload modversions ARMv5 ' should be '2.6.29 preempt mod_unload ARMv7 '
So, that gave me a big hint - after a few hours of customizing I finally got the .config file to a version that will properly compile and load the openvpn module.
I'm attaching the .config file (config.zip) and tun.ko file (tun.ko.zip)
*NOTE* - I have not tested the kernel module yet, so I have no idea if it works. Even if it does work, the .config file is the default one that I manipulated so that the tun module would compile. You probably don't want to use the .config file as it may not match all of the hardware and configs of the droid x. If someone has the actual droid x .config file used by motorola then that would be very helpful.
*update* - the attacked files *do not work*. The working version is available at http://forum.xda-developers.com/showthread.php?p=7417520
Click to expand...
Click to collapse
i'm having a similar issue, how did you fix this ARMvX Version problem when compiling a module? Thanks in advance!

[DEV] Loadable Modules for Gingersense Incredible [Updated 9/18 - Support for OTA]

HTC released gingerbread via OTA but they did not support additional modules. This thread has flashable zips for both the leaked kernel and the one from the "OTA".
Added flashable modules to attachments that are flashable in recovery.
I have created a zip of some of the more useful modules for our device:
Code:
cpufreq_conservative.ko
cpufreq_smartass.ko (thanks Chad for the help here)
ext4.ko
jbd2.ko (necessary for me to load ext4)
tun.ko
perflock_disable.ko (I actually compiled this one a little different but confirmed it would load and not get the exec format error)
Update: Smartass is working now with assistance from chad in resolving those errors. Decided to not worry about interactive for now.
Further information:
If you don't use the CWM flashable zip you will need to load perflock_disable a special way as it needs to be called with a special parameter to make it work correctly. Try adding below to a script. Credit to Calkulin for the script.
Code:
if [ -e /system/lib/modules/perflock_disable.ko ]; then
insmod /system/lib/modules/perflock_disable.ko
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
addr=`awk '$3 == "perflock_notifier_call" { print "0x"$1; }' /proc/kallsyms`
if [ -n "$addr" ]; then
insmod /system/lib/modules/perflock_disable.ko "perflock_notifier_call_addr=$addr"
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
echo "ERROR!!! Perflock could NOT be DISABLED"
fi
fi
fi
fi
Credits:
Conap (for BootManager and helping me test ext4 on an SD ROM)
XDA (for teaching me so much about Android)
HTC (for the kernel source)
Chad0989 (for assistance in getting smartass CPU governor working)
Coolbho3000 (perflock_disable)
Calkulin for the module load script
anyone else who inspired me (apologize if I forgot)
I have attached a zip file to this. If you are not a dev you can still use the modules here but some basic ADB/terminal knowledge would be needed. The modules are open for testing though.
Attached zip files and CWM-flashable zip files for both OTA and leak-based ROMs.
inc_modules.zip - Just the loadable modules.
inc_modules_ota.zip - just the loadable modules - OTA-based ROMS (August leak)
inc_modules_ota_091811.zip - just the loadable modules - OTA-based ROMS (actual OTA from September)
inc_modules_CWM_flashable.zip - flashable zip that will also autoload modules at boot.
inc_modules_ota_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (August leak)
inc_modules_ota_091811_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (Actual OTA from September)

I'm glad some one took this up I had been wondering the same thing since HTC opened the dev section. I had found another site that had a more extensive write up on how to build kernels but I'm not very fluent in linux and was a little intimidated at trying. At least I now know that it can be done. Maybe we can get Chad to try and port it over?

Awesome. A ray of hope.

Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.

jermaine151 said:
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
Click to expand...
Click to collapse
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?

tiny4579 said:
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
Click to expand...
Click to collapse
--prefix
Sent from my ADR6300 using XDA App

hightech316 said:
--prefix
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually got them to build but they won't load still. I will play around with it more.

This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)

oh wow this is incredible great job tiny!!! and the reason you probably cant get those other governors to work is because htc released an uncomplete source

jskolm said:
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
Click to expand...
Click to collapse
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.

tiny4579 said:
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
Click to expand...
Click to collapse
would i need to make one for every module?

JoelZ9614 said:
would i need to make one for every module?
Click to expand...
Click to collapse
Joel,
No, just one script should work. I believe Synergy ROM already has the init.d script for some of them. See 00cpufreq_modules in /system/etc/init.d
All,
Updated OP with latest zip file. If you have downloaded previously, redownload to get the latest.

would it be likes this?
http://www.multiupload.com/J9WTSA4VWF

JoelZ9614 said:
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
Click to expand...
Click to collapse
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.

tiny4579 said:
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
Click to expand...
Click to collapse
eeh im not good with init.d scripts lol

ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko

Every shell script should contain
#!/system/bin/sh
Sent from my ADR6300 using XDA App

JoelZ9614 said:
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Click to expand...
Click to collapse
Exactly!
Then just make a line for each module.
EDIT: Though you could just write it like this:
Code:
#!/system/bin/sh
insmod /system/lib/modules/tun.ko
Though to be safe and to make sure you are running that particular insmod command you can leave it the way you have it.

ok done its in my rom RLS3 Thanks Tiny Great work

JoelZ9614 said:
ok done its in my rom RLS3 Thanks Tiny Great work
Click to expand...
Click to collapse
No prob! It's been a good project for me.

[Q] [KERNEL] ARMv6 vs ARMv7 cross-compile question / tun.ko for LG Revo

hello all -- ive mostly been a lurker (been too busy), but i finally found some time to try and get the ipsec vpn working on my stock-but-rooted LG Revo. despite some ardent googling, i couldn't find a working tun.ko that would work with vpc/VPN Connections. so i decided to compile my own.
i figure since there's certainly nothing in the LG Revo boards here specific to compiling tun.ko for the LG Revo, i'd start this thread and document my steps along the way. i figure other board users can use for reference etc. hope it's ok mods/admins!
the short version/TL;DR:
i have compiled my own tun.ko for my stock/rooted LG Revolution. i have the correct kernel version (etc) but am stuck because i dont seem to be able to compile ARMv7, only ARMv6. this is the error i receive when i try to insmod:
Code:
tun: version magic '2.6.32.9-perf preempt mod_unload ARMv6 ' should be '2.6.32.9-perf preempt mod_unload ARMv7 '
basically i need to compile it for ARMv7 not ARMv6. i don't know how.
the long version, aka the steps i took:
starting in a nice clean folder, download the linux kernel src specific to the version of the kernel on my rooted stock LG Revo. i obtained this earlier (you can check via Settings -> About Phone -> Kernel version. if you have a stock (rooted or not) LG Revolution it will be: 2.6.32.9-perf.
Code:
$ mkdir -p $HOME/tmp/lgrevosrc
$ export LGREVOSRC=$HOME/tmp/lgrevosrc
$ cd $LGREVOSRC
$ wget -q http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.9.tar.bz2
$ wget -q http://dl.google.com/android/android-sdk_r10-linux_x86.tgz
$ wget -q http://dl.google.com/android/ndk/android-ndk-r5b-linux-x86.tar.bz2
$ tar xjf linux-2.6.32.9.tar.bz2
$ tar xzf android-sdk_r10-linux_x86.tgz
$ tar xjf android-ndk-r5b-linux-x86.tar.bz2
earlier, i copied the config file for the kernel specific to my LG Revo by using Root Explorer and copying the /proc/config.gz file. i now copy this into my linux kernel src tree, being sure to gzunzip it first and to copy it to the src folder as ".config", not "config".
Code:
$ cd $LGREVOSRC/linux-2.6.32.9
$ gzip -d ~rickt/tmp/from_my_lgrevo/config.gz
$ cp ~rickt/tmp/from_my_lgrevo/config .config
now we have to edit the .config file and add the tun module so it will be compiled. i added the following line to the .config file:
Code:
CONFIG_TUN=m
now, we compile the modules, being sure to set the environment variables for the architecture we NEED, not the one we're compiling on:
Code:
$ export ARCH=arm
$ export CROSS_COMPILE=arm-eabi-
$ export PATH=$PATH:$LGREVOSRC/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin
$ make modules
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/basic/hash
HOSTCC scripts/kconfig/conf.o
< snipped, for brevity >
LD [M] net/sched/cls_flow.ko
CC net/sched/sch_dsmark.mod.o
LD [M] net/sched/sch_dsmark.ko
$
let make sure the tun.ko module was compiled, and we'll see what type of arch it was compiled for:
Code:
$ find . -name tun.ko
./drivers/net/tun.ko
$ ls -l ./drivers/net/tun.ko
-rw-r--r-- 1 root root 190705 Aug 19 06:35 ./drivers/net/tun.ko
$ file ./drivers/net/tun.ko
./drivers/net/tun.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
$ strings ./drivers/net/tun.ko | grep -i arm
vermagic=2.6.32.9-perf preempt mod_unload ARMv6
BOOM! note the ARMv6. this is important, because when i try to insert the module into the kernel on my android (after copying it over, obviously) i get:
Code:
# insmod tun.ko
insmod: init_module 'tun.ko' failed (Exec format error)
ok, so i start nosing around in the logs to see what i can see, and i see:
Code:
<3>[122130.240509] tun: version magic '2.6.32.9-perf preempt mod_unload ARMv6 ' should be '2.6.32.9-perf preempt mod_unload ARMv7 '
so... i guess this was a long and drawn-out way of saying that i have a great desire to have a tun.ko for our beloved LG Revolution, but i'm not sure how to have gcc on a linux box cross-compile for ARMv7, not ARMv6.
anyone? bueller?

I work quite a bit with cross-compilers in my day job, but I haven't tried to use any of the pre-packaged ones in the Android SDK(s).. however, until I have time to play with them, the ARMv6 versus 7 probably relates to these 2 variables:
$ export ARCH=arm
$ export CROSS_COMPILE=arm-eabi-
Also, gcc has -march and -mtune params that can sometimes be used to select specific CPUs and/or sub-architectures within a main CPU family.. if someone (e.g. LG) gave out an SDK for the Revo specifically, their gcc would probably already be "spec'ed" to march and mtune for the specific CPU..so maybe the generic Android ARM gcc cross-compiler defaults to ARMv6.
I may have time to poke into this later, but it probably won't be today..
- Phil

I've been informed that GCC cannot output ARMv7. I think licensed developer tools are needed. Can anyone confirm this?
RMT.

GCC4.3 added ARMv7 support. This discussion seems to confirm the various details:
I think in GCC 4.3 is where you get ARMv7 architecture support, (see
http://gcc.gnu.org/gcc-4.3/changes.html), which is EABI and at GCC 4.4
you have "EABI-compatible profiling interface for EABI targets." (again see
http://gcc.gnu.org/gcc-4.4/changes.html).
So I've chosen to work on 4.4 just to be sure, and it also supports Cortex-A9, as
well as VFPv3 (yeah!).
Click to expand...
Click to collapse
Full discussion here:
http://freebsd.1045724.n5.nabble.com/ARMv7-EABI-Cross-Compiler-tp4201510p4201523.html
Depending on who is providing the cross-compiler you are trying to use, they may either be using something prior to gcc4.3, or, they are providing a compiler which has not been enabled with the ARMv7 target. You could try using Kegel's cross-tool with a recent gcc (4.4 or 4.5) to build your own ARMv7 cross-compiler, but not sure how deep you want to go with this!
- Phil

I haven't been able to get a working tun.ko for this either. I've having trouble compiling my own. Could you post the adapter you're working with?
I just saw a verizon update come down, but kernel is 2.6.32.9-perf [email protected] #1.

Bumping this ol' thread hoping that progress has been made or someone knows about a thread I missed. Trying (hoping) to get OpenVPN going with my Revo so I'm hoping there's a tun.ko available.

I successfully compiled a tun.ko for mine using the "crossdev" package on gentoo. Just setting ARCH=arm CROSS_COMPILE=arm-eabi- did the trick for me.
I believe older verions of gcc were not yet capable of producing ARMv7.
gcc 4.5.3 certainly is. I would try upgrading to that if possible and that ought to work.
I'd be happy to share my tun.ko with anyone that wants it as well...
Slightly unrelated, I also found that loading the module (insmod tun.ko) did not cause the /dev/net/tun node to be created for some reason...
a simple
Code:
mkdir /dev/net
mknod /dev/net/tun c 10 200
as root, and AFTER loading the module resolves that problem, at least until the next reboot. I haven't figured out how to get it to run a script at boot yet to automate it.
If anyone wants the tun.ko let me know and I'll upload it somewhere.

Bait-Fish said:
Bumping this ol' thread hoping that progress has been made or someone knows about a thread I missed. Trying (hoping) to get OpenVPN going with my Revo so I'm hoping there's a tun.ko available.
Click to expand...
Click to collapse
Blitz includes tun.ko
Sent from my VS910 4G using xda premium

nasaiya said:
I'd be happy to share my tun.ko with anyone that wants it as well...
Click to expand...
Click to collapse
Thanks you very much for the offer. I am a total noob as far as compiling goes!
mtmichaelson said:
Blitz includes tun.ko
Click to expand...
Click to collapse
Damn sweet! I never needed it before so that went right over my head previously. Can I simply extract it or would I have to be on BK? (which I'm not)
Sent from my VS910 4G using Tapatalk

I believe you need to install ClockWorkMod to flash blitz onto your phone. You can backup first and try it out safely with CWM. Just follow the instructions in the thread it's easy.
Here's my tun.ko for anyone that wants it. I found "openvpn installer" and "openvpn settings" apps perfect for my needs (only issue is I still have to manually add the device node -- even with blitzkrieg, but it's no big deal)
http://www.box.com/s/a50pnexofiej4in7s5h7

Bait-Fish said:
Thanks you very much for the offer. I am a total noob as far as compiling goes!
Damn sweet! I never needed it before so that went right over my head previously. Can I simply extract it or would I have to be on BK? (which I'm not)
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
You could try pulling it from the blitz zip and dropping it in your /system/lib/modules and see if it works!
Sent from my VS910 4G using xda premium

Cool, thanks. I'll attempt the 'easy' way first.
Sent from my VS910 4G using Tapatalk

[KernelModule] Overclock

**** Do Not Repost! Link back to this thread! ****
*** Update: This works on Thrill/Optimus 3D. There are seperate kernel modules for Froyo/GingerBread/CyanogenMod kernels***
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
This uses SYMSEARCH by Skrilax_CZ
https://github.com/SkrilaxCZ
Inspired by Milestone Overclock by Tiago Sousa, but totally rewritten for omap kernel 2.6.35-7 and above.
http://code.google.com/p/milestone-overclock/
This is a stripped down version. I'm working on a fully featured version, that will allow you to play with voltage as well. There are some hurdles to overcome before that is ready for prime time... In the mean time, lets see what stock voltage can do... 1188 is my sweet spot on stock voltage, what is yours? I get up to 1235 without reboots, or real noticeable lags but the linkpacks are all over the place, where it stays in the 80's at 1188. And remember, the number is in hz a.k.a. cycles per second, so to get Mhz, you must add 'Six Zeroes' to the end of your desired Mhz.
* Note2Devs: Feel free to put this in your ROM, but please do credit me for the Overclock in your release, and link back to this thread. You can also post a link to your ROM here as a way to make myself and other aware of it. Thanks...
* Echts shows us how he integrate's the module into his own ROM. TY, Echts...
http://forum.xda-developers.com/showpost.php?p=19542521&postcount=52
* Thanks to greenbats for helping figure out the O3D gingerbread kernel issue!
** And don't ask to put it in an app. I won't be happy about that. I'm serious! **
Here go some of my Recording Engineer work...
http://www.youtube.com/watch?v=Je8K_hCej3s
http://www.youtube.com/watch?v=yfBfcdSL1pc
http://www.youtube.com/watch?v=iIU8DO4rdKI
http://www.youtube.com/watch?v=msavF7LIdvY

Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.

It's the same hardware

omgomg said:
Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.
Click to expand...
Click to collapse
Yes, give this a go on the O3D, the module is actually compiled against the cyanogenmod cosmo kernel, which is really for the O3D. Should work.

for test \

How do I install this on the optimus 3D?

greenbat said:
How do I install this on the optimus 3D?
Click to expand...
Click to collapse
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.

tekahuna said:
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.
Click to expand...
Click to collapse
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.

greenbat said:
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.
Click to expand...
Click to collapse
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah

Great invention
tekahuna said:
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah
Click to expand...
Click to collapse
Great invention and congratulations!

Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App

tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse

Type this in scriptmanager shell.

greenbat said:
tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse
What I'd really like is for the ROM making dev's to come to a consensus as to how to integrate this... Mainly, the best place to throw the script that does this at boot on these phones. I know how we did it on droid X, but I haven't dug deep enough into this phone just yet to be sure... I'll update the OP as methods improve and I get more feedback.
Click to expand...
Click to collapse

Or use callmearia kernel and make script for system/etc/init folder... havent tried his kernel but it should support the script at boot up. Acura roms should work that way too.
The way most roms use overclock is the init script that starts at boot...
Sent from my LG-P925 using XDA App

rdannar said:
Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Those would have been based on Milestone Overclock... Which is where I gained most of my knowledge by contributing to getting the droidx/2 side of things working. MO's method of manipulating frequency and voltage no longer works on OMAP4, or rather kernel 2.6.35+... I had to come up with a new way of doing things, which didn't fit well under the existing framework of MO. So, I started from scratch... This is just the tip of the iceberg... Basic, basic, basic...

i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?

I also get the same error: insmod: init_module '/system/lib/modules/symsearch.ko' failed (exec format error)
Is it because I have gingerbread?
Must I use froyo?

borelis said:
i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?
Click to expand...
Click to collapse
Both O3D's, huh? What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source

tekahuna said:
What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source
Click to expand...
Click to collapse
"LINK Boot_2.0 More RAM, No Lags, More Speed.." from acura. Think he uses stock kernel. Im on GB by the way.
Outputs is a bit over my head. Tell me how and i´ll provide it for you.

[PATCH]Patch to fully enable GSM on every Rom | see main thread

This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 4.x
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
-Call Forwarding
I'm constantly updating only this main thread and I will answer only in it, I have no time to update and control every thread in sub-forums.
I'm using this thread only for major notifications.

Mentor.37 said:
This is a patch to fully enable GSM on every rom and on every Android version.
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
The patch and the guide are available here.
If you want you can download a specific patch for the CyanogenMod 10.1.2 here.
Click to expand...
Click to collapse
it's worked on XT894 with Hashcode's CM10.1.2, i have tried it
such a nice work :good:

Does this enable the US GSM bands as well?

No, I'm sorry but it can't enable US GSM.

Awesome, added this to my GSM guide. Thank you.

Lum_UK said:
Awesome, added this to my GSM guide. Thank you.
Click to expand...
Click to collapse
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.

Mentor.37 said:
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Click to expand...
Click to collapse
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?

Lum_UK said:
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Click to expand...
Click to collapse
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.

Mentor.37 said:
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Click to expand...
Click to collapse
Can I use LTE (gsm networks sim) in my country with this patch (Be, Europe) ?

You have to se what are lte frequencies in Belgium.
The lte on xt894 only works at 700 mhz.

Maybe next time you should give credits to the original author... *cough cough*

Are you talking with me?
I'm the original author.

Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
But they differ in a few lines, I think that tobby disabled the LTE. Anyway for nightlies is better to replace only the lines needed.
The world is full of people there is a chance that two of them to work on the same thing.
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Regards
Sent from my XT894 using xda app-developers app

lucize said:
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
Click to expand...
Click to collapse
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
lucize said:
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Click to expand...
Click to collapse
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.

With copy, I was telling the way that you implemented the patch, and regarding to apn it was only a comment because in other cm releases(not motorola), the apn list is full (~180kb vs 17kb).
I personally downloaded the tobby zip first, but I use this device only recently (previous was d3) so who was the original poster I can't say.
Regards
Sent from my XT894 using xda app-developers app

I do not understand why you think I would have copied the way to implement the patch, patches are all made in the same way.
Personally I use my stock rom but several users who use AOSP roms have contacted me exposing the gsm problem and so I easily fixed with this patch using the settings that I use in my rom file build.prop.
At short will release a new version of my rom with a new build.prop file with new settings and I'll update this patch also.
I honestly did not know existed nor Tobby nor his zip, I created this patch because asked me.
Regarding the file APNs-conf.xml depends on the fact that the phone is born to the CDMA network Verizon and therefore not serving the other APNs, the file APNs-conf.xml in the stock rom is ~ 43KB.
What is the Tobby's zip?

Mentor.37 said:
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
Click to expand...
Click to collapse
Ah c'mon. Take a look into your own files. In apns-conf.xml is still my copyright... Its not extracted from Motorola Stock-ROM. Also not from CM. It's based on several sources on the internet (most of it is based on CM, but several more sources were added). It took days to combine the sources, remove duplicates, sort it, use the same style for every entry and so on. It's not a problem to use or copy this. But to say you did this yourself is not fair.
But apns-conf.xml is only one part of your mod. Second part is the automatic build.prop changer. (GSMbyMentor.sh)
Look at your GSMbyMentor.sh:
Code:
#!/sbin/sh
#
# Patch to enable GSM on Verizon by Mentor
# Build: 17.07.2013 17:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=GB/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.modem.mode =1/persist.ril.modem.mode =2/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.vzw.cdma.mdn=/persist.radio.vzw.cdma.mdn=deleted/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc = 1/ro.telephony.gsm-routes-us-smsc = 0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.ap.phonetype=2/persist.radio.ap.phonetype=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
Now let's take a look at the Bash-Script of "TobbysMod":
Code:
#!/sbin/sh
#
# Tobbys build.prop Anpassungen für das Droid 4
# Stand: 15.03.2013 04:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.language=en/ro.product.locale.language=de/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=DE/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.ecclist=911\,\*911\,\#911/persist.ril.ecclist=911\,\*911\,\#911\,119\,118\,999\,08\,000\,112\,110/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc=1/ro.telephony.gsm-routes-us-smsc=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.hwKeyboard.capsLockNoAlt=true/ro.hwKeyboard.capsLockNoAlt=false/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.lte.mm.disable=0/persist.radio.lte.mm.disable=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.lte_on_cdma=1/ro.mot.lte_on_cdma=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dateformat=MM-dd-yyyy/ro.com.android.dateformat=dd.mm.yyyy/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dataroaming=true/ro.com.android.dataroaming=false/g" /system/build.prop > /system/build.prop
Let's take a look at the differences.
- You removed my credit and changed the date
- you removed a few lines which were necessary for the keyboard-mod included in the original mod and necessary for European date-format and emergency calls
The rest stayed the same. Even the sequence/order. And you use exact the same trick for removing spaces. You can't say this was coincidence...
Third part of your mod is the edison install script. This looks different. Seems to be your own work.
Two of three parts in your mod copied from me. It's ok! I always wanted to remove the parts which are necessary for my German friends so everybody can use it, but I didn't have enough time. So it is good someone (you) did that. But please don't say it's your own work when you just copy files...
Link to original Thread for "TobbysMod": http://www.android-hilfe.de/motorol...82-tobbys-automatische-rom-modifizierung.html
Google translation: http://translate.google.de/translat...82-tobbys-automatische-rom-modifizierung.html

I added that apns-conf.xml at the suggestion of an user that tested my patch, I repeat that I'm on stock rom so I have not tested directly the patch. If you wont I can give you his email address.
In a first moment I made this patch as you can see here with the apns-conf.xml that I personally extracted and that I use in my rom for months without any problem. Anyway I removed that file.
About the sed is a common command for any linux user to manipulate text.
About the sequence/order it is different, I used the same in the build.prop.
About the point of the gsm patch, so the build.prop settings there are a lot of differences:
My:
Code:
telephony.lteOnCdmaDevice=0
persist.ril.modem.mode=2
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
persist.radio.vzw.cdma.mdn=deleted
ro.telephony.gsm-routes-us-smsc=0
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
Yours:
Code:
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
ro.mot.phonemode.vzw4gphone=0
persist.radio.lte.mm.disable=1
ro.mot.lte_on_cdma=0
These lines are missing in your:
Code:
persist.ril.modem.mode=2
persist.radio.vzw.cdma.mdn=deleted
persist.radio.ap.phonetype=1
and the lines that are equal in the two files have known each other forever and they are everywhere in the forums so what are you saying?
With the settings in my build.prop users solved their problem on aosp roms.
#Postedit
I found this and this with your patch and then this and this with my patch.

apns-conf.xml: As I said: You don't need to remove the file. It's ok I created this file to help users. Additionally because of the sources, I am not allowed to forbid the usage of this file for some users. You also don't NEED to give credits, because it's already included. I just wanted to mention you are not using your own file. Not more ore less.
Bash-Script: Yes, sed is a common linux command. But it's usage on the phone was a little bit different than on a normal linux machine and the trick with the spaces (sed -i "s/\ =/=/g") is not necessary for the function of this script. It's just to make some things a little bit easier. That's why it's hard to believe you found out the exact same thing as me and used it in exactly the same way. If you did: Grats mate! You must be a soulmate of me If you just used this because you saw it "somewhere" else: please don't remove my credit.
To the missing 3 lines: two of them are included in version 1.3 of 07/16/2013, one day before you created yours. Just "persist.radio.vzw.cdma.mdn=deleted" is not included in my Mod. I am just curious: What does this line do?
But we schouldn't argue about it. As I said: Feel free to use my work. I hope I am allowed to do the same with your work. Instead of argueing we should combine our work!

I reinserted the apns-conf.xml that I use in my rom.
I used the sed command intuitively how I use it.
The line "persist.radio.vzw.cdma.mdn=deleted" deactive the mdn on cdma network. I use these settings from time.
You can use my work without problem.
I just answered your allegations because I spent a lot of my free time for this my mod.
About a possible collaboration I like this idea, the work is much, time is short and one hand is always a pleasure.