I read the module FAQ and the code page and tried out module & xposed code and I was not able to get around my problem. I'm not sure that it was supposed to get around my problem though, but I was hoping to get your take on things. I can't find much data, though I can find a few people asking the same questions as I.
I installed an android 4.3 ROM (http://forum.xda-developers.com/showthread.php?t=2121063) on my phone and tried to connect to an OpenVPN based VPN provider. I got an error and contacted their support. Part of that process was to try another app, so we tried the OpenVPN COnnect app, the official OpenVPN app. I got a different error with that app.
One says that "your android firmware does not support the VPNService API("
OpenVPN Connect says "Sorry, due to a known issue in this version of android, it is not possible to gain permission to open a VPN tunnel"
There seems to be a few problems popping up with OpenVPN based VPNs in various Android 4.x OSs, but none complaine about 4.3 specifically. Usually they complain about 4.4 or back when 4.0 and 4.1 were new. I found this article talking about it on OpenVPN, and they're just pointing the finger, but I can't find the actual bug referenced:
https://forums.openvpn.net/topic13772.html
I came across your code on this page:
https://code.google.com/p/ics-openvpn/wiki/FAQ
And decided to try loading xposed and your module after emailing OpenVPN Connect and receiving a response right away. The guy who replied seemed to think the error is related to the fact that the confirmation acknowledgement dialog is not able to be summoned. I figured maybe the ROM wasn't bypassing it properly or missing some part of it, so I tried your way of bypassing it.
After loading xposed and your module, and selecting the 2 VPN apps, I still get the same results.
What are your thoughts? Should I give up and find a new ROM?
What are you talking about? If you're asking about a specific module (looks to me that way,) you should do that in the appropriate thread.
After some more research and experimentation yesterday, it's looking more like those OpenVPN clients that "support" the VPNServiceAPI actually *require* it, and that annoying/nasty little dialog that google enabled to "protect" the user just serves to piss off advanced users like me. This is my hypothesis at this point, though I have not confirmed this. I suspect this because I just tested on Jelly Bomb, a 4.1 based ROM and see the same results so far.
As far as what I was talking about in my OP, I copy/pasted an email to the author of the xposed module here and tried to reformat it to fit the message board, and apparently I missed a few pronouns. By far not the most egregious use of the English language I've seen on these boards, so what's with the attitude? I don't see specific sub forums for each and every module, so I don't get what you're implying. I only saw the one xposed board, so where else was I supposed to post?
No attitude, I honestly didn't understand how your issue was related to the Xposed framework. I just searched the repo for "VPN" and now see what you're talking about.
The Auto VPN Dialog Confirm doesn't have a thread here on XDA. Reading your post again, you're trying to use Xposed to fix a bug with the app if I'm not mistaken? I'd first try checking the logcat and forwarding that to the author of the VPN app if you haven't already.
I can't answer the rest of your questions since that's up to the module's author. That being said, it looks like a module specific question/request, not a framework query.
My understanding of the issue described here is different, probably because I'm trying to solve the same problem On the other hand, I'm not on ICS anymore, but am using Sammy 4.1.2 stock with DorimanX Kernel 8.43 at the moment.
OpenVPN should be usable for establishing a connection on boot. Out of the box, this creates a dialog to trust this application. Even though I trust it and confirm, there is no way of saving that preference permanently. It seems to be kept for a while (disconnect / reconnect doesn't trigger it again at least ) Therefore, it always reappears each time I boot.
The only possible solution I could find was the Xposed Module "Auto VPN Dialog Confirm" - the same module mentioned by the OP.
I used it together with the OpenVPN Client by colucci.web.it (paid version in my case, because I also wanted TAP support and auto connect functionality as well as the option of controlling it via Tasker).
After installing "Auto VPN Dialog Confirm" it recognized the installed OpenVPN client and offered to allow VPN API connections from it without confirmation. The VPN client also has an option to automatically create connections when Wifi is up and allows to be triggered either when seeing a specific SSID or when connecting to a network which does not have a specific SSID. The latter one is the typical condition for untrusted networks.
Therefore, it achieves what I wanted - being able to route my traffic via OpenVPN in case I'm not connected to my home WiFi
Regarding the issue encountered on ICS - maybe getting in touch with the Developer of the Xposed module might be the best option, unless someone else has already found a solution for it. It could also be good to exactly specify the OpenVPN client used as clearing the Xposed logfile and having "AutoVPN Dialog confirm" run as the only Xposed app (and fail). Afterwards, the log hopefully contains useful feedback for the developer to investigate further (Support URL listed for the module)
Related
I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!
Is anyone using OpenVPN app? I've been using it for several months with no problem, downloaded it from the market.
Yesterday I installed NQ (for no particular reason, searched for spyware within the market and that was one of the first options) then ran a system test, it only detected OpenVPN as a thread with the virus a.remote.legacy.something (don't remember exact type)
Now, I am very paranoid when it comes to something from China. NQ, as I later checked, is a chinese company, and the description of that virus only comes from NQ website itself, other sources call it LeNa.
Can anyone with OpenVPN run that test and report results? I think it's a false positive to force people to remove OpenVPN from their phones. Avast doesn't show any thread.
I don't know what I pretend with this post, maybe reinforce my "paranoia"
Hey folks!
I followed the instructions posted by allcaps33 at http://forum.xda-developers.com/showthread.php?p=53549710 to get provisioning disabled, and the native hotspot app is working for me now! I just wanted to confirm if this was an operation similar to running Wifi Tether Router on an unlocked/rooted device (I had an S2Sky prior that I tethered off of regularly). I've got one of those too-rare Unlimited Data plans and am traveling cross-country, made possible by being able to tether my laptop to my phone to work. Just wanting to confirm that this was relatively as secure as using the Wifi Tether Router on my S2Sky. On a semi-related note, that app doesn't seem to want to run properly on my S5; when I click Enable Router it turns on the Wifi, which immediately connects to the house's wired router. It still broadcasts but doesn't send data, and it's hit or miss if a device can even connect to it from there.
Next question - I'm used to flashing a CM ROM within the first couple days of getting a new phone, which doesn't seem feasible just yet with the S5 (from what I can tell anyway; I'm not used to having a current-gen device). I've heard about the myriad evils of OTA updates, and was hoping to get help on how to disable them. I would like to avoid my device upgrading to a point where my above-stated desired functionality is disabled. Ideally, I'd like to get rid of the various bloatware apps as well, though am not sure how to go about that.
I appreciate your time and support, and thanks for being a community that's always been there for me as I derp along with my fancy internet boxes!
Hi!
The absolute easiest way is to use Rom Toolbox. I have the pro version, but I believe it's available in the lite version as well.
Download and open up RTB.
Tap on "App Manager"
Then scroll down until you see "AT&T Software Update"
Tap on it.
A popup will display. Swipe from right to left, and you will be on the "Advanced" tab.
Scroll down and tap on "Advanced Freeze."
You will come to a screen which shows you the Activities, Recievers, Services, and Providers. Tap on EACH box/line. This will Disable OTA services.
We're not done yet!
Go back to the App Manager screen again, and repeat the process for an app called "LocalFOTA"
Finished!
I also Disable most of the bloatware and Knox this way.
Have fun!
---------- Post added at 12:58 PM ---------- Previous post was at 12:49 PM ----------
Now for the hard part...
Yes this can be as secure as the other the tether. Ensure you use and change the password service with the app.
As for the tether turning your wifi on, it is supposed to do that. The best way to get this to work is to turn the tether on and off (then on again). If this does not work, try emptying the data/cache for the built-in tether app. And start from scratch.
allcaps33 said:
I also Disable most of the bloatware and Knox this way.
Click to expand...
Click to collapse
KNOX - What is it? I'm under the impression it's some sort of security for the phone, to protect from malicious activity that you might not be aware of, but also that it'll "tattle" on you if you mod your phone in a way AT&T doesn't approve.
Knox is two things.
1) It is a security container for apps. It works as both a license/drm type software for Samsung official apps.
And
2) Android contains a root environment at all times. This is what makes SU possible. It used to be quite easy to invoke Android system calls as root.
Root is actually separate from super user. Knox, like SEPolicy, helps dev companies detect, halt, and/or hinder apps, not su itself, but apps that that use these root system calls.
Be wise, even though Knox itself does not "report" these types of actions, it still logs them. And there are other apps that can read these logs and send out these reports. I should say (and I'm only guessing) that only work/company issued phones are setup like this. Not your personal phone.
In fact, our phones actually contain a file which logs all root system calls. It has nothing to do with Knox but, I believe this binary is what hinders us open devs, but makes it easy for Samsung and AT&T to restore/repair our phones.
For more info on Knox:
https://www.samsungknox.com/en/partners/app-developers
Thank you for all you hard work, I have been a user for many releases prior and love that your software has always been "there and working well". So why only speak up when I have a problem, so for that I apologize.
I have managed to obtain a version of Xposed (Systemless) ported for Magisk installed on my phone (SDK 23) and while Magisk lists Xposed in its installed module list with a check box saying it is active, the Xposed menu shows the green notification area that says it is working, when I install XprivacyLua, and while after the installation of XprivacyLUa, in the Modules section of Xposed there is a check box showing that XprivacyLua is installed and active, the problem is that the Xprivacy app thinks it is not loaded. I sent trace logs captured via adb to the Xprivacy developer and he says that Xposed believes the XprivacyLua app is not installed (even though all indications are that it is active).
Someone who knows more about this than me stated my problem was likely with Toybox being on the phone and something about symlinks where he gave another suggestion about loading Busybox and then following with loading a BusyBox binary zip package via TWRP. All this does is render me not able to access MagiskManager any longer.
Do you know anything about such an issue and how I might get around it? I am saddened that using this valuable tool is being made so difficult from all the new hardware changes. I normally stick with age old phones, but accidents happen, the old one's cracked and my new one won't seem to work with Xposed.
Thanks!
BLU STUDIO XL 2 16/2G
MT6737
ARMv7 Processor rev4 (V71)
armv71
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Donphillipe said:
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Click to expand...
Click to collapse
What about making system run in permissive mode?
have you tried?
I have not "jumped" from superSU to majisk so my method is to use superSU.
I have a recovery install package that sets file in place to make permissive and force superSU to install systemless.
you can give a try.
the updater-script prints out a message it was made for "blu tank xtreme pro" but it is fine for other phones too. I made it for/ with other dev who wanted to have one step to make root and permissive.
I do not know how will respond to majisk, so better off to try ununstall that first, and start fresh.
Not all users could have it, but VPN "bug" (I use quotes since I'm not so sure it's a bug and not a wanted behaviour...) on stock ROM appears on post Feb23 A12 builds to date (don't know if root related or not).
It's composed by two parts (fact which lead me to be suspect...):
1. - VPN menu is missing in Network & Internet section
2. - every VPN app (not already installed before the Feb23 build) fail to work
To date there is NO official fix from Motorola, from others or... from me.
BUT I've found a couple of workaround for both issues which can be applied to have your preferred VPN app working fine (and that's the important thing! ).
I'm sorry but root is needed (well, not at all, but we'll see it in details after...) to fix both the issues...
Let's see in details...
1) VPN menù exists & works fine, it's only hidden in Settings.
The workaround is to create a direct "shortcut" to the VPN menu using one of the shortcuts apps you can find on Play Store or, as in my case, using the "Create shortcut to Activity" function embedded in my launcher (Nova).
The name of VPN menu is: .Settings$vpnSettingsActivity
You'll get an Icon you can use to open VPN Settings!!
2) Now that you have the settings back you could think that your VPN apps will work. Wrong!
It's needed a second step...
I've studied a lot the issue and I've found that when your app should show a confirm dialog to create the needed VPN it doesn't show anything at all and no VPN is created...
Looking better I've found that this happens because the system directly deny the permission instead to let app to ask user!!
So... to correct this (wrong) behaviour the simplest fix is to use an app called App Ops Permission Manager (available on Play Store) which allow us to modify app permissions values.
We just have to go to our VPN app and modify the activate VPN value from ask to allow!!
If you use several VPN apps this has to be done for everyone...
Only problem is that App Ops requires Shizuku to run and Shizuku requires... root!
Well, not exactly to be honest... Shizuku can be actived without root too using the "Wireless debug USB" trick they well described in their app. I can confirm it works fine. Only issue is that it has to be enabled again at every boot, BUT I think modify done by App Ops should be "permanent" until app is not removed (or updated... not sure about this...), so Shizuko start could be needed a single time or so (in any way once VPN has been created in VPN settings the VPN app should be happy with it and shouldn't ask any more confirm!).
I hope you'll find all this clear & useful...