yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] mero01:
Ok so i have a update

I followed the following steps.

* Files located here : https://github.com/fries/android-external-openvpn/downloads

A) Not sure if this matters or not but i copied LeeDroids iptables file from the Desire.

B) Implementation:

1. Unzip/copy openvpn-static-2.1.1 to file to device.

1.a rename to openvpn

1.b replace the current openvpn file in /system/xbin with this new one

adb remount
adb push openvpn /system/xbin/
adb reboot

2. Make folder /system/xbin/bb

adb remount
adb shell mkdir /system/xbin/bb

3. Make symbolic links to ifconfig and route

adb shell ln -s /system/xbin/ifconfig /system/xbin/bb/ifconfig
adb shell ln -s /system/xbin/route /system/xbin/bb/route

7. Install/Configure OpenVPN-Settings

7.0 Install OpenVPN-Settings-.apk. Market or

adb install OpenVPN-Settings.apk

7.1 On device, launch OpenVPN Settings.

7.2 Long press openvpn.conf, Preferences.

7.3 Check "Use VPN DNS Server"

7.4 Enter your VPN DNS Server

7.5 Script Security Level Select Built-in + scripts

7.5 press back

7.6 Click click the sub-menu option select Advanced

7.7 Load tun kernel module and make it 'insmod /system/lib/modules/tun.ko' before starting openvpn.

7.8 Change path to openvpn binary to /system/xbin/openvpn

i got rid of the error received before but (unable to redirect default gateway) but now am given with a new one ? it seems to connect perfectly and then this

Linux ifconfig failed:could not execute program what program ?

and then disconnects :(

I have attached a screen shot of new progress/problem.

Oh yeah im testing the connection using "OpenVPN Settings" and "TunnelDroid" as they both seem to work but "OpenVPN" lacks the Log support .
[Desire HD Android Development] mero01:
( i found most of this info from this http://code.google.com/p/android-openvpn-installer/issues/detail?id=2 and http://xdaforums.com/showthread.php?t=551512&page=6

What i posted above seems to have fixed that and brought another issue of

MANAGEMENT: Client disconnected
Linux ifconfig failed: could not execute external program
Exiting

there was more steps but they didnt work....posted below.

6. Modify your openvpn.conf to call script after routing, or pass it in as a command line argument. I did the modification to script file.

Code:

#remember that I use tap, I don't know about tun

dev tap

route-up "/system/bin/sh /sdcard/openvpn/up.sh"

Here is my config anyways for reference and here is my client config

client
dev tun

proto udp
remote XXX.XXX.XXX.XX 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert mero-android.crt
key mero-android.key
comp-lzo
verb 6
script-security 2
[Desire HD Android Development] mero01:
Have also realised if you go terminal and do following gives you nice log :)

basicly , su root, cd to your openvpn folder location, run openvpn on your client conf

su
cd /sdcard/openvpn
openvpn client.ovpn
[Desire HD Android Development] mero01:
SOLVED AND WORKING!!!!!

THINK I AM THE FIRST PERSON IN THE WORLD TO HAVE OPENVPN ON DESIRE HD!!!!!!:D:D:D:D:D:D:D:D

will setup a thread will full tutorial and instructions later tonight very tired been doing this since 3AM its 5:45 now :P
[Desire HD Android Development] Walker Street:
Hi Mero1, maybe we tied. I got it working with the CyanogenMod rom. But I'd be really interested in how you got it working with LeeDroid!
[Desire HD Android Development] mero01:
Ahhh haha!!! we shall call it a ty!!!!

i didnt even think about it being the ROM, ow well stuck too it and got rewarded :)

How did you manage to do it on CyanogenMod ? did you encounter the same problems... ?

You can do a tutorial on "CyanogenMod OpenVPN" and i shall do "LeeDrOiD OpenVPN" haha
[Desire HD Android Development] Walker Street:
Hi my tutorials now pasted in my first post. There were none of the problems. It worked straight off the bat.
[Desire HD Android Development] mero01:
:O

Going to have to ask Lee about that then :( ow well mights working and im still on LeeDroid loving it :)
[Desire HD Android Development] Walker Street:
LOL, I'm going back to LeeDroid. I need Bluetooth more than I need OpenVPN at this stage. However, if CyanogenMod gets bluetooth, I'll probably go back to that. Oh bother.
[Desire HD Android Development] mero01:
Im going to write a Tutorial for LeeDroid untill Lee can fix the problems iv sent a email.
[EVO 4G Q&A, Help & Troubleshooting] Marlowr05:
ok so I recently upgraded to cyanogenmod 6.1 and I love the rom. I am wondering though when I would normally use wifi tether in the market i would have a lot of trouble keeping a connection with my laptop or my phone would suddenly disappear from the wifi list on my computer. It seems to do it a lot with Fresh 3.3.0.1. I am wondering is there a way for me to get the built in wifi tether/hotspot feature on Cyanogenmod to work on Fresh's or any other rom? Also if i could get better battery life in CM 6.1 I would just stick with that rom. Thanks again.
[EVO 4G Q&A, Help & Troubleshooting] cesarcerros31:
The one in 6.1 uses wireless tether from the market try cyanogen to see if it works

Sent from my overclocked Cyanogenmod htc evolution 4g sucka
[EVO 4G Q&A, Help & Troubleshooting] dabbill:
http://code.google.com/p/android-wifi-tether/downloads/list

Use this wifi tether, and if you have connection issues with it, change to channel 1. I am useing pre13 and my notebook stays connected everyday for 8+ hours with no issues. I have it set to channel 1 in the settings.
[EVO 4G Q&A, Help & Troubleshooting] Marlowr05:
Ok thank you. I will definitely give those a try. If cyanogenmod 6.1 could get the same or even better battery life then fresh 3.3.0.1 I would definitely make the switch then. Thanks again and I will let you know what all happens.
[HD2 Windows Mobile 6.5 ROM Development] IzaacJ:
Hello.

I'm about to start cooking for the HD2, and have quite a bit experience of EVK and the Diamond, but I can't seem to get it working with the HD2.

The base rom is the Swedish stock one (1.66.413.2, WM 6.5.2 build 21869) but I'd like to get a more current one, at least 6.5.3 build 23xxx. As stable as possible.

I downloaded SYS 23562, 28240 and 28243, but can't get either of them to work. If I get the ROM to boot, there seems to be a lot of language files missing. Any idea of where I could get my hands on those?

Been trying for about a week so it's starting to get a bit annoying.

Any help is appreciated.

//

Izaac
[HD2 Windows Mobile 6.5 ROM Development] adam1890:
http://xdaforums.com/showthread.php?t=610634

Duttys HD2 ROM Family V8 kommer närmaste dagarna
[HD2 Windows Mobile 6.5 ROM Development] Teoror:
Seems to me you need to update to a more recent stock rom and grag the new .mui files. You know there is a 3.14 SVE stock out?

Regards

Teoror
[HD2 Windows Mobile 6.5 ROM Development] IzaacJ:
Sant. Men är mer intresserad av ett kök :P

Well, I dumped the 3.14 stock ROM but it won't boot. I think I read something about that it doesn't work with HSPL2.
[HD2 Windows Mobile 6.5 ROM Development] adam1890:
This is currently V8 work in progress after today's work with V8

* Release candiadate COM3 Branch 5.2.23148.5.3.11 ChangeLog

* Pagepool reverted to 16mb to compare performance with Dynamic

* Fixed Storage Data encryption.

* Fixed some misc. translations in RUS, FRA, ELL and other languages.

* Fixed Random access in ELL & RUS ROM.

* Fixed Typing in Greek ROM.

* Added aGPS_Confirmation_1_0_20172430_00.

* Added CyberonVoiceSpeedDial_1_2_b100806_Oboe_01 fully translated.

* By pressing and holding down the send key will activate CVSD.

* Thanks to all who supported in some of the language fixes and translations

* Some minor fixes and ROM Optimisation.
[Vibrant General] lotherius:
I really don't want this to come across wrong, but I just have to say it.

Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.

But please, for the love of all that's good - keep an updated list of Known Issues!

It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.

You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.

All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.

Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.

For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.
[Vibrant General] chui101:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
[Vibrant General] kponti:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them

The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
[Vibrant General] heygrl:
They don't care to list them. It's beneath some of them.
[Vibrant General] hellcatrydr:
Maybe AirBus should list "midair exploding engines" as a known issue too...

+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!
[Vibrant General] ionic7:
If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.
[Vibrant General] xent:
The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.
[Vibrant General] jeremiah_mn:
I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene :)
[Vibrant General] N8ter:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
[Vibrant General] swehes:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread. :)

Update: Here is the link for the WIKI page.

http://xdaforums.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
[Vibrant General] PaiPiePia:
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.

"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"
[Vibrant General] JeremyNT:
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.

This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!

I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.
[Vibrant General] swehes:
OK. Looking into Google Code. :)

(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
[Vibrant General] JeremyNT:
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.

The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.

Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.

IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.
[Vibrant General] swehes:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?

http://xdaforums.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
[Vibrant General] Stargazer3777:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.

Otherwise, that looks like a great idea, and possible way of tracking things!

EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....

EDIT EDIT - Fixed it.
[Vibrant General] swehes:
Thanks. :) On both accounts.
[Vibrant General] oka1:
Maybe this should be a post to Microsoft

To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........

Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........

---Maybe this should be a post to Microsoft---
[Vibrant General] All~G1:
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.

If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....
[Vibrant General] JeremyNT:
I think it's a pretty awesome start for sure :)

As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.

Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!
[Vibrant General] Rodriguez92:
if you donate or not these guys are doing this for free and they tell you flash at your own risk..

so if your gunna flash a ROM then READ EVERYTHING. even if that means 1000 pages. this is your phone that your about to flash the rom on so if your taking that chance then read.

i mean yeah it will be better for us to just be able to see all the bugs in the op but these guys do a lot and to report all the bugs and some that they dont even have which is due to people not flashing the rom right isnt fair to the devs they put in all this time and some people just dont know how to read before they go and put their 500$ piece of electronic on the line.

I SAY IF YOUR GOING TO FLASH THEN READ ALL YOU CAN IF ITS NOT IN THE OP THEN TOO BAD JUST READ AND ASK QUESTIONS IF YOU HAVE TO.
[Vibrant General] swehes:
I'm not sure what is the policy either for the wiki. I just went to the already existing page and started adding things. But you are right. It would be nice to have a individual page for it.

As for making it so people will utilize it I will ask the OP for the bible to add the link to it as well as creating a general thread for it.
[Vibrant General] ELStiko:
If you are here to flash roms/kernels, people should also know how to fix their phones when they need to. If a rom does not do all the things you want it to do, an ODIN back to stock, reflash to your last rom, and then a CWM restore takes all of how long to do?

I will admit that it would be a lot easier if Devs posted more complete changelogs and reported and confirmed issues. That can take a bit of time to compile and post in a manner that is all nice and pretty for people with half a brain to be able to comprehend. I honestly like that time spent on the dev doing what they do best, develop.

And also remember bricking a $550 phone is never the dev's fault. it is the fault of the user. All Roms are flash at your own risk.
[Vibrant General] Spokenblurb:
Quick question my keyboard freezes up randomly while typing I'm using smart keyboard and launcher pro paid version can anyone explain why....cause its driving me insane
[Vibrant General] Spokenblurb:
Anybody....?
[G Tablet Accessories] fiendskillz:
Was wondering if there was a car mount for this bad boy? I know ram makes a good car mount for the ipad, but im not sure if their cradle is adjustable because even though this is 10" i dont think it has the same shape haha..
[G Tablet Accessories] eluminx:
i been looking at this one Car Mount it's adjustable so it might just work.
[G Tablet Accessories] akldjian:
I was looking at that one eluminx. It didn't seem to get a good rating. Another one I came across was from the UK amazon site. I haven't looked for it on US site yet. Here's a link... http://www.amazon.co.uk/ULTIMATEADDONS-Mount-Holder-Medion-Netbook/dp/B003CI7Y74
[G Tablet Accessories] insight3fl:
I would like to see one for a cup holder.... how are you possibly going to stick this to your windshield with this large and heavy device???????????
[G Tablet Accessories] beefster:
Check mountguys.com, they have one for an android tablet, looks to be adjustable
[G Tablet Accessories] reynwrap582:
I plan on using a sheet of Kydex to form around my gtab and canibalizing an old suction mount to mount it on. Then I can get those little adhesive suction discs and affix it once I find the best location.
[G Tablet Accessories] dragonfly1113:
I say on your windshield like where people put their sirius radios LMAO, talk about an obstruction of view HAHA
[G Tablet Accessories] aamon17:
Here's mine: http://www.sears.com/shc/s/p_10153_12605_SPM2625697602P?prdNo=16&blockNo=40&blockType=G40

$14 @ Sears . . .
[G Tablet Accessories] pan0k:
How do you mount this bad boy to the windshield?
[G Tablet Accessories] gottifour:
I ordered this one. It's for an Eee pc but it should work.

http://www.amazon.com/PHR-NB-PB2-26...3?s=electronics&ie=UTF8&qid=1293653673&sr=1-3
[G Tablet Accessories] dragonfly1113:
honestly i think that the gtab in the car would be pretty damn cool to use, however i think it just MIGHT be an obstruction of view if you guys were to get the windshield mounts for the tab, believe you will def get a few tickets for that from the local cops looking to meet 'quotas'. maybe if there was something where you can dock it say where the lighter is or in the middle console somehow but on the windshield prob isnt the best place for it, just my 2 cents ;)
[G Tablet Accessories] gottifour:
I agree, big time! :) I plan on mounting mine lower in my work van. I also plan on "fabricating" some sort of recessed dock type enclosure in my truck. I had plans for a carputer but I think a gtab dock would be way more convenient....and way sweeter!

Hoping to tap the knowledge of the guys at this forum. They build some awesome setups here. I know this isn't for the average person, but I am already half way there in my vehicle.

http://www.mp3car.com/vbulletin/fabrication/
[G Tablet Accessories] seymour_butts:
Is it the same size as iPad?

Look at this one

http://www.dealextreme.com/details.dx/sku.44927
[G Tablet Accessories] Bad@ssGtab:
Mountguys has a cupholder version that's adjustable.... I have one on order that should be here tomorrow..

Ill post some pictures....
[G Tablet Accessories] Evo8IKON:
Bad idea... for my car anyways...

I drive an Evo with 600AWHP and a lots of grip. This thing will not be held by some suction cup. :p

I am looking to make a bracket of some sort for the center console.
[G Tablet Accessories] djyellowperil:
Did you get it? I've been eying the cupholder mounts at mountguys. I was hoping that they had one that could handle my gtab and elocity
[G Tablet Accessories] Bad@ssGtab:
Not yet....
[G Tablet Accessories] zyphaz:
I bought one of these iPad suction cup mounts from some random site on BensBargains.net and use it with a beanbag friction dash mount... on my desk. The setup is just too large and cumbersome to be placed on the dashboard. Not to mention the ball head mechanism never seems to get tight enough to hold the tablet steady when I touch anything on either the extreme left or right of the tab.