Hi Irbis, In general the permissions should be set by the tool or IDE that integrates Crosswalk, what Junwei offered is a workaround to modify them after you have gotten the APK from the build service. We absolutely agree that this shouldn’t be the normal case.
> I could check all the needed permissions from Construct 2 and XDK, upon > export. I’m not too familiar with the way Construct works, but are you saying that there is a way to configure the permissions in Construct and/or XDK and that they are ignored by Crosswalk, and that this wasn’t happening before Crosswalk 14? If that’s the case, that’s a clear bug that needs to be addressed. We are talking to the XDK team to see what is the issue. Regards , Francesco From: Crosswalk-help <[email protected]<mailto:[email protected]>> on behalf of Irbis <[email protected]<mailto:[email protected]>> Date: Monday 7 September 2015 09:29 To: "Fu, Junwei" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Yashash Agarwal <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Crosswalk-help] CrossWalk14+XDK+Construct2: Problems with permissions Hi Junwei. I did some more research already and this is really not a viable solution. As I've said previously - I and others, we are Construct 2 users. We are not programmers "per se". And till now, all the permissions we had to set, could be set - in Construct 2 and in Intel XDK. The process took like seconds. The whole point of this export was it to be fast and effective. And, from almost instant - it went to almost an hour of work. Its a serious downgrade. At this point, its just not worth it. If I have to go through this whole process every time I need to published my game or publish an update to my game - then i'll rather use the old version of Crosswalk. Because there was not problems back then. I could check all the needed permissions from Construct 2 and XDK, upon export. I did not have to unpack the apk, decompile, change, recompile, get it signed with some ancient command line magic, get it zipsigned... Listen, making games in general is a hardwork, specially for mobiles its already a pain in the butt. You are limited by controllers, by OS, by software and hardware. You have 8745678 different resolutions and aspect ratios. And non-existant hardware standards. One smartphone has more horsepower than your PC, when the other is like taken from 8bit era. And your game, regardless of how simple it is - has to have all this optimized and worked out. Half of the time you are actually developing the game. The other half you are wasting, trying to get this damn thing working AT ALL. Construct 2+Intel XDL+Crosswalk is not the best solution. But it was one of two we could you use. Our HTML5 games wrapped with XDK+CW ended up always bigger in size, due to additional files from XDK. The performance was BAD. The most simple games could end up as a slideshow due to low framerate. So we were limited to very slow paced games. Games where the sluggish framerate would not be noticed, or become a burden to the player. Or, like me, we stopped developing games for mobiles. But a hope came with XDK and CW improvements. Suddenly our games run like native. We finally can make some serious games, without feeling like '80,'90 coders, operating with 64kb of RAM. It was great. But regardless how fast and smooth our games run now - we cannot consider publishing them with those default permissions. People won't even try our games when they'll see what sort of power our App is demanding them to give. They will discard our games without even trying them out. And no amount of our explanation will do. The current solution is... Problematic. And I believe it doesn't have to be like that. It was all cool till now. Everything could have been setup from C2/XDK export. Making games for mobiles, as I said, is annoying - at best. Add anything more to already difficult procedure and it might not be just worth it anymore, again. Or we will be forced to use CacoonJS. And believe me - we don't want to. But its either that or quitting mobiles and going back to Browsers/Desktops. It really wouldn't be that sore point but it was all working well just a moment ago and now we like went back 2 years to the past. Can't you just leave the permissions settings to XDK/C2? It was all good a moment ago... :( I really want to keep on using XDK+CW... 2015-09-07 4:37 GMT+02:00 Fu, Junwei <[email protected]<mailto:[email protected]>>: Thanks for trying Crosswalk. You can remove permissions with apktool. 1, decompiled the apk Apktool d [apk name here].apk 2, You must keep the android.permission.ACCESS_NETWORK_STATE for Crosswalk to avoid crash. Can’t detect network if you remove android.permission.ACCESS_WIFI_STATE. Can’t choose file if you remove android.permission.INTERNET. android.permission.WRITE_EXTERNAL_STORAGE can be removed if you don’t use shared mode. You can open the AndroidManifest.xml in the decompiled directory, and delete the line with the permission. <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> 3, recompiling the apk Apktool b [name of folder of apk you decompiled] [desire name of new apk file].apk 4, sign the apk Java –jar signapk.jar certificate.pem key.pk8 [name of apk you just copied].apk [another name].apk More information in https://www.reddit.com/r/Android/comments/11852r/how_to_modify_an_apk. You can also try to use Crosswalk plugin in Cordova, there are no those additional permissions. Cordova plugin add cordova-plugin-crosswalk-webview Thanks, Junwei. From: Crosswalk-help [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Irbis Sent: Sunday, September 06, 2015 4:36 PM To: [email protected]<mailto:[email protected]> Subject: [Crosswalk-help] CrossWalk14+XDK+Construct2: Problems with permissions Hello! I have a problem. I've made a game using Construct 2 game engine. Then I've used the Intel XDK software to export the game for mobiles, using Crosswalk14. The game runs suprisingly well but I have problem with Permissions. Crosswalk14, by default, sets all sort of permissions. Most of which are needless in my case. So I would like to get rid of most of them. But I don't know how. I've figured out, and was also advised, to do so by editing the AndroidManifest.xml file. But either time I do that, the App refuse to install on Android. I tried doing the modifications using notepad, notepad++, OpenOffice, WordPad. Every time with the same result. So I am either using the wrong software to edit it, or I am doing something wrong in general. Do you guys know how can I get rid of those permissions? I need to add - I am not a native programmer. So I don't know how to code directly. Hence why I am using Construct 2. The matter is quite urgent because I am supposed to p[publish the game tomorrow Monday the 7th. But I cannot do so with those permissions in check. The Google Play users will flame me to the ground. Its a simple action game. If such a game would have all those permissions it would look like a spyware device. And people on Google Play are exceptional careful when it comes down to this. So they would discard the game even before seeing the Splash screen. Best Regards Radek -- I_R_B_I_S --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
