This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
Related
That actually have bluetooth stereo working? getting bored flashing my phone back and forward constantly now with no successes, is there any that run? Cheers.
just to add for a 32b. thanks.
It is possible to get stereo bluetooth working.
You can use the ZeroXD or MoDaCo. I feel the ZeroXD is the best one out at the moment. You need the 5.1 version. It's buried within the thread. There are also the instructions to get A2DP working.
I can confirm A2DP is working on the ZeroXD 5.1 release on a 32b device.
I located the post:
http://forum.xda-developers.com/showpost.php?p=4484079&postcount=222
When you follow the instructions for BT make sure you type in all lower case.
naplesbill said:
It is possible to get stereo bluetooth working.
You can use the ZeroXD or MoDaCo. I feel the ZeroXD is the best one out at the moment. You need the 5.1 version. It's buried within the thread. There are also the instructions for pushing the necessary bluetooth files to get A2DP working.
I can confirm A2DP is working on the ZeroXD 5.1 release on a 32b device.
Click to expand...
Click to collapse
The same process can be used on a lot of Hero ROM's.. At this moment, only the 2.x Modaco's based ROM's are not working and they have this files already, so prob unknown!
ricardomega said:
The same process can be used on a lot of Hero ROM's.. At this moment, only the 2.x Modaco's based ROM's are not working and they have this files already, so prob unknown!
Click to expand...
Click to collapse
That is true. But, this is the only rom I've found (so far) that includes a script that enables bluetooth directly from the phone. Are there other roms like this?
naplesbill said:
That is true. But, this is the only rom I've found (so far) that includes a script that enables bluetooth directly from the phone. Are there other roms like this?
Click to expand...
Click to collapse
What do you mean exactly with that enables bluetooth directly from the phone?
Edit: Bluetooth has to be enabled from the phone!
ricardomega said:
What do you mean exactly with that enables bluetooth directly from the phone?
Edit: Bluetooth has to be enabled from the phone!
Click to expand...
Click to collapse
I guess enables is the wrong word. I'm talking about actually enabling it to function. Yes you can turn it on but it doesn't work. There is a fix that requires using ADB to push two additional files. ZeroXD uses a script to make the bluetooth function without the use of ADB push. This same script also changes the rom to function for the myTouch or G1 depending on the option you choose.
is it just me... or do we see this question ALL THE TIME... just saying I'm about 99.9% sure if you took about 5min to look through this forum you would of found your answer...
naplesbill said:
I guess enables is the wrong word. I'm talking about actually enabling it to function. Yes you can turn it on but it doesn't work. There is a fix that requires using ADB to push two additional files. ZeroXD uses a script to make the bluetooth function without the use of ADB push. This same script also changes the rom to function for the myTouch or G1 depending on the option you choose.
Click to expand...
Click to collapse
Ok.. Not all ROM's came defected and depending on this fix.. For instance a very old version of myhero, the v0.0.8 already came with the all the files there. Is not a script, it means that this files were included on the original package. Script is that will follow some command to do a rule.
ricardomega said:
Ok.. Not all ROM's came defected and depending on this fix.. For instance a very old version of myhero, the v0.0.8 already came with the all the files there. Is not a script, it means that this files were included on the original package. Script is that will follow some command to do a rule.
Click to expand...
Click to collapse
It is handled via a script because his rom is for both the dream and the sapphire platforms. You have to run the script to fix wifi and bluetooth depeding on which platform option you choose via the script. I had not seen any other rom with the bluetooth working without using adb push commands. I did notice evil released a rom late yesterday with the bt fix included.
Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
loveheaven said:
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
Click to expand...
Click to collapse
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
http://forum.xda-developers.com/showpost.php?p=5793964&postcount=667
Firerat said:
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
Click to expand...
Click to collapse
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
loveheaven said:
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
Click to expand...
Click to collapse
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Firerat said:
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Click to expand...
Click to collapse
loveheaven said:
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Click to expand...
Click to collapse
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Firerat said:
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Click to expand...
Click to collapse
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
loveheaven said:
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
Click to expand...
Click to collapse
CE1.2 with my vid patch
wait for CE2
or Kings 1.8 AOSP
or
check the code in this
http://forum.xda-developers.com/showpost.php?p=5889900&postcount=4
with a bit of deduction, you could figure out what is missing/different
as I said in my last post, I can't help you as I have no idea what ROM you are trying to get mp4 to run on.........................................
Installing/Pushing CE-12-Patch_3D_Vid_signed.zip
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
will4958 said:
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
Click to expand...
Click to collapse
the v4 is a different beast
King's Eris has working video
King's Eris CachHacked has working video and is a lot faster
CE-12-Patch_3D_Vid_signed.zip
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
will4958 said:
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
Click to expand...
Click to collapse
/data not working?
if data wasn't working it wouldn't boot past the bootanimation splashscreen
if data is 'full' reboot, it will correct itself
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
will4958 said:
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
Click to expand...
Click to collapse
ahh, sorry I'm getting all mixed up, because everyone is stressed out over FR-a2sd using /data for something useful instead of leaving it as an empty,wasted space.
yes, data connection is not working, tbh I don't know why the Market doesn't work even if wifi is working..
The CE-12-Patch_3D_Vid_signed.zip isn't going to do anything for FR-v4OL-CH-0-1_S.zip
its just a 3D kernel , and libs I took from the eris dump which got video working.
infact , the libs are 'mostly' the same as the ones already in v4OL
( which means I'm totally not understanding why video is dark, got to be a framework thing, maybe, I don't really know, just guessing )
Flashing / pushing CE-12-Patch is just going to kill v4OL
I did CE-12-Patch a long time ago, shortly after re-visiting xda after initially rooting my g1 way back in Feb '09.. kinda wished I'd stuck around then.
anyway, CE-12-Patch WILL break v4OL, is it doesn't mount mtdblock4 in the right place.
the v4OL is beta , lots of things don't work
if you get your kicks trying to fix broken things, or making yourself understand things you don't understand ( i.e. you self teach )
then it is for you.
if you want things to work 'out of the box' ,
King's Eris mostly works
ce12 cachehack works
ce2.0 works ( with a 'lil' fixup, facebook fix is in the thread FR*S.zip coming soon.. )
OE1.3.0.1 has things working ( anyone flashed ce12-patch over oe1.3 ? )
and good ol' SuperD works very well.
personally I think your best root is the CE12 CacheHack
It's fully functional, and best of all, CE2.0 is a *no wipe* update
You can flash CE2.0 , just a couple of fixes that need to be consolidated
they are in the thread , minor fix is at post #1401 ( which I will update to a "no hassle,flash straight after CE2.0" soon )
Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers
dventurin said:
Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers
Click to expand...
Click to collapse
3) As far as I can tell, all of the alternative kernels have this module. The Infused ROM contains the Voodoo kernel, but I believe you can run the Voodoo or Infusion kernels on the stock ROM.
ok I see.
Could you suggest to me a starting point to deal with the custom roms?
I'm have a good experience with linux since years but not enough on smart phones and android in general.
For instance, is there an official website for Infused ROM?
Any tip is welcome.
Thank you!
@dventurin - I had the same issue. I have the Infused rom installed and it has the same issue. I installed SL4A and wrote my own scripts, the app is what's broke everything works at the CLI. I then used Tasker but I think you can do it with Gscripts as well build my own shortcuts. As for where to find the Infused ROM look in the Dev section here. There a several ROM's available but I've only used Infused.
@3GBeyotch
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?
dventurin said:
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?
Click to expand...
Click to collapse
If you want the Infused ROM, head over to the "Infuse 4G Android Development" forum....
http://forum.xda-developers.com/forumdisplay.php?f=1161
From there, you will want to look at 2 threads....
1. You need to root your device first. Check out the very first thread (entitled: [How To] Root the Samsung Infuse 4G) shows how to root your device.....
http://forum.xda-developers.com/showthread.php?t=1082247
(the second link under SOURCE: has a video tutorial)
Side note: When downloading Superoneclick, make sure to get the one that has the drivers included. Also, make sure your external SD card is unmounted!
======================
2. Next, you'll need to install the Infused ROM. Look at the thread (entitled: [ROM] Infused v1.5.0 - (06/18/11) - Faster and smoother than ever!), which has the instructions, etc, for installing the Infused ROM.....
http://forum.xda-developers.com/showthread.php?t=1105413
You basically need to root your device first, then install the Infused ROM.
As far as feeling comfortable with using the sources from the forum, you have nothing to worry about. In regards to the Infused ROM, gtg465x is the one who developed it. All you have to do is follow the instructions, and if you feel uncomfortable about doing one of the steps, ask someone here!
I've had the Infused ROM installed now for a few weeks, and I have not been disappointed! Hope this helps.
Open VPN on Infused ROM tun.ko problems?
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.
iovchinn said:
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.
Click to expand...
Click to collapse
What's the error?
Entropy512 said:
What's the error?
Click to expand...
Click to collapse
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.
iovchinn said:
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.
Click to expand...
Click to collapse
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?
Entropy512 said:
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?
Click to expand...
Click to collapse
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.
iovchinn said:
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.
Click to expand...
Click to collapse
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
It seems, you are right. /system/lib/modules/ has only one file in it and it is tun.ko. That one did not load. Must be some left-overs from previous reincarnation. The one in /lib/modules/ has lots of different *.ko files and tun.ko among them. This one loads just fine.
Again, thank you very much for your help.
Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Unfortunately someone else will have to help you there - I haven't used VPN functions on my phone.
iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Having the same problem, am able to connect to openVPN running on ddwrt but the phone isn't directing traffic through it. Anyone have any ideas?
Anyone read about this today?
http://bcmon.blogspot.com.au/2012/09/working-monitor-mode-on-nexus-one.html?m=1
Cyanogen 9 & GS2 (I9100)
Download the zip: http://bcmon.googlecode.com/svn/trunk/bundles/gs2_bundle.zip
Extract the zip on your device (your sdcard will do fine)
Run 'sh setup.sh' on some terminal (adb ssh, terminal emulator, ...)
Now you have a wifi interface named wlan0 in monitor mode
Now run 'iwconfig wlan0' and check that you get an output similar to the one above
With all the i9100/i727 differences, I'll keep you posted on my install! If anyone else feels brave, or is cool with wipe/davlik, with CM9, keep us posted on details.
any progress on this? this looks like it could be alot of fun but, i have no idea what i'm doing
I get permission denied errors...I'm assuming its trying to write to /mnt?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I rebuilt the kernel module for a CM9 nightly, but it doesn't work. Basically there is a bug in the firmware code where they are accidentally freeing a packet twice (which doesn't happen on the International version of the SGS2, that they officially released for), and the card crashes. Here is the response I got from them:
I checked in the firmware and the address 0x80e308 is the function pktfree so I guess we have a double free bug. My problem is that I can't reproduce the bug since my phone is the nexus one and all my friends have the international gs2 version.
Sorry
Click to expand...
Click to collapse
They don't seem willing to help until they get the packet injection working. Kind of sucks...