Database Develop

How to make a website only viewable by android phones?

Does anyone know how to make a website that can only be viewed by an android phone? Like how the iPhone has websites only viewable by iPhones & iPod Touches? If you do can you post a tutorial on how it could be done? Thanks

Check the "User-Agent" from the HTTP request.

Short php code that switch the site (not tested, should work)
PHP:
<?php
if(preg_match("/android/", $_SERVER['HTTP_USER_AGENT']))
{
header('Location: androidSite.php');
}
else
{
header('Location: normalSite.php');
}
?>
Or you use getBrowser()
And then you have just to fit the design of the design or do what you want

The only way to actually stop non-android devices from accessing the website is to force the android users to install an android-only plugin to be installed in the browser (not supported by default browser) or to use a custom browser. Said plugin will authenticate with your service using only-you-know credentials, thus preventing any non-android device from accessing it. The user agent is REALLY REALLY simple to fake.

lbcoder said:
The only way to actually stop non-android devices from accessing the website is to force the android users to install an android-only plugin to be installed in the browser (not supported by default browser) or to use a custom browser. Said plugin will authenticate with your service using only-you-know credentials, thus preventing any non-android device from accessing it. The user agent is REALLY REALLY simple to fake.
Click to expand...
Click to collapse
If you want to be absolute about it, it would not be outside the realm of possibility to reverse engineer the authentication output of the hypothesized plugin and create a workaround. Furthermore, as the plugin would likely be an arm binary library, there's probably not that much preventing it from being run (reasonably) on any arm-based system.
user-agent is probably (i'm guessing) enough for what the OP has in mind.

Here you can generate your own script:
http://detectmobilebrowsers.mobi/
For example: iPhone devices redirect to ebay for buying a android device
and Android Browsers comes in.
PHP:
include('mobile_device_detect.php');
mobile_device_detect('http://shop.ebay.com/i.html?_nkw=android&_armrs=1&_from=&_ipg=','http://website.com/android.html',false,false,false,false,false,false);
Download the PHP script for non commercial sites here:
http://detectmobilebrowsers.mobi/#download

It may be possible to reverse engineer it (not necessarily in case it is actually well designed), but even if it is, it would be non-trivial, even if implemented by an idiot. Changing the UA *is* trivial, even to a complete moron.
And who says it has to be an arm binary library? Maybe go with something in javadroid instead.... and link it to the device IMEI... using a time-based crypto function that only runs on your server, i.e. device --> server crypto service --> device with magic enabler key --> web server authentication. You can make something REALLY MESSY that nobody would bother to reverse, and something that can only run in android (i.e. dalvik). Sure dalvik can be run on other 'nix systems, but by doing so, they become quasi-droid anyways...
jashsu said:
If you want to be absolute about it, it would not be outside the realm of possibility to reverse engineer the authentication output of the hypothesized plugin and create a workaround. Furthermore, as the plugin would likely be an arm binary library, there's probably not that much preventing it from being run (reasonably) on any arm-based system.
user-agent is probably (i'm guessing) enough for what the OP has in mind.
Click to expand...
Click to collapse

idea for a framework

hello,
what i dont like about developing apps for phones is that you dont have such a broad choices of programming languages
here is the idea to circumvent this:
progamm a phonegap app that exposes its api to a certain web server.
the actually app code is on the server.
we only need some sort of bridge to use the javascript from the web server script
what do you think?

nomoral said:
hello,
what i dont like about developing apps for phones is that you dont have such a broad choices of programming languages
here is the idea to circumvent this:
progamm a phonegap app that exposes its api to a certain web server.
the actually app code is on the server.
we only need some sort of bridge to use the javascript from the web server script
what do you think?
Click to expand...
Click to collapse
Way too serious for off-topic. Maybe the other programming sections?

[Q] Hidden APIs to access public folders

Hi,
Write file access on Windows Phone 8 is very restricted. In fact 3rd party apps can only write pictures to the public picture folders. Other types, such as music, documents, or video folders cannot be accessed.
Are there hidden API calls available for accessing these folders (I am aware that applications using these APIs will probably fail Marketplace submission)?
Greetings,

Yes, there are but you need special permission from MS to use them.

Do you have more details about these API calls?

No...not really. I know there are APIs for everything we can't do as ordinary devs, but MS only releases these to certain groups (typically recognized development studios).
These include:
Native compiled APIs, to use with C++/C#
Appointment API (other than live calendar)
Bluetooth APIs
and some others.

thanks, this really explain a LOT of things.

Do you have an idea how to get access to these APIs? I already tried it with the MS developer support but they say that they don't know

I don't know exactly. But you can't get them through the usual ways. Maybe if you send them a physical letter asking xD?

There are native APIs accessible to regular users. You can read all Calendars since WP7.5 and starting with WP8 you at least can create a new Appointment in a Calendar but only through a Task so the user has the ability to edit it and he must confirm it. Bluetooth-APIs are also open in WP8 although not everything can be done through them.
There might be additional APIs you can gain access too if you work with Microsoft directly. I would suggest you contact one of the Microsoft Dev Champs near you (there is a "Find my Champ" App in the Marketplace) and get into contact with him.
But unless your App gains special permissions through Microsoft even though you might know about those APIs your App would not be able to use them.

And then they cry that Google won't give them the API for a youtube app....the irony

The problem with YouTube is more that there are APIs but that YouTubes Terms of Service prohibit using those APIs for competitors in the search engine space. So Microsoft is specifically prohibited because they own Bing. I hope you can understand the difference but I have a feeling you won't.

Thanks for all your comments. Please don't abuse this thread with company bashing because the situation is often more difficult than it seems. Thanks :good:.

I think wp8.5 may see some more APIs open up. Wp8 is rushed and many existing APIs on win8 simply does not exist on wp8.
Ms is taking a more cautionary approach for APIs as they don't want junior devs mess up the phones user experience like they did with Android.
Sent from my RM-820_nam_canada_246 using Board Express

Accessing features in Windows phone 8(.1) development

When developing an application for desktop windows, there's always a way to access functionality - sometimes through back doors like the registry, etc... I'm developing an application for Windows Phone 8.1, but there are certain pieces of functionality that aren't exposed in the PRT APIset that is available to me. For example, we want to ensure that the user has password protection on the lock screen when using the application. There doesn't seem to be any associated APIs to readily use. So my question is, are there back door ways to do such things? How? Is there a way to access ALL system settings - like a registry or something of the like?

proch said:
When developing an application for desktop windows, there's always a way to access functionality - sometimes through back doors like the registry, etc... I'm developing an application for Windows Phone 8.1, but there are certain pieces of functionality that aren't exposed in the PRT APIset that is available to me. For example, we want to ensure that the user has password protection on the lock screen when using the application. There doesn't seem to be any associated APIs to readily use. So my question is, are there back door ways to do such things? How? Is there a way to access ALL system settings - like a registry or something of the like?
Click to expand...
Click to collapse
Another question would be - if something like intune can enforce lock screen password policies, shouldn't I be able to do it the same way that intune does it? If so, how? If not - why not?

It's not possible to check if user enabled lock screen password or not as far as I know
but if you want to made your app secure (because it may include important data)
you can create a password for your own application !
I did it in a little notepad app my password page allow user to set a password with all English and Persian Characters , numbers and special Chars like [email protected]#$ and etc.

Sent from my RM-994_eu_poland_1183 using Tapatalk

It's pretty easy to check, using the registry, but at least in 8.0 that's not allowed at all for store apps (your app would get rejected). I don't know if the rules changed for 8.1. There are ways to sneak past the store checks, but they could pull your app from the store if they ever found out. I know of at least three ways to access the registry APIs (4 in WP8.1) and two of them are pretty hard to detect unless somebody checks for them specifically... but they're the kind of technique that malware uses, so such checks may be in place.
I don't know what InTune is doing, specifically - I'd need to pull the app apart to see - but there are special application capabilities (not normally available to third-party developers) that can query and even set policies. Apps without those capabilities will get Access Denied if they try to use the same methods though, and normally you can't add those capabilities to your app.

GoodDayToDie said:
It's pretty easy to check, using the registry, but at least in 8.0 that's not allowed at all for store apps (your app would get rejected). I don't know if the rules changed for 8.1. There are ways to sneak past the store checks, but they could pull your app from the store if they ever found out. I know of at least three ways to access the registry APIs (4 in WP8.1) and two of them are pretty hard to detect unless somebody checks for them specifically... but they're the kind of technique that malware uses, so such checks may be in place.
I don't know what InTune is doing, specifically - I'd need to pull the app apart to see - but there are special application capabilities (not normally available to third-party developers) that can query and even set policies. Apps without those capabilities will get Access Denied if they try to use the same methods though, and normally you can't add those capabilities to your app.
Click to expand...
Click to collapse
Thanks for this great and detailed information. See, that's exactly what I'd do if I were developing a desktop app - since i know that intune does it, I'd figure out how intune does it and voila. I'm finally getting over the idea that the same methodologies apply to windows phone development.
For my own educational purposes (since I want to understand this platform better), I would really like to know specifically how you go about accessing the registry APIs (for example). If there's any way for you to describe any number of these methods, I'd greatly appreciate it. Thanks again!

My NativeAccess libraries (check my signature, or search on the forum or on Codeplex) contain an example of one way to access the registry. The code is open-source; you may use the libraries as-is (don't expect to get them into the store, though I won't stop you from trying), use the source code as a reference, or modify/build them yourself; the license is very liberal (MS Permissive). The functions I use are generally documented on MSDN, in the desktop APIs section; the phone has the same functions, although the DLL names are changed and the header files hide them.

[APP][NST/G] Mantano Reader [MOD]

Edit 1-8-23: I've updated the Mantano apk file. Seems there were still some issues with the aspect ratio of the default.png (book cover) image. Fixed now at 1.5!
I keep my NSTG on FW 1.2.1 because there are issues with Tasker and plugins on FW 1.2.2. The resulting apps are OK, but development is a problem unless I do it on FW 1.2.1. So that one device has B&N apps removed. AlReader has been my go-to reader app. Until now.
While working on some thorny issues with a Tasker app update I came across a book I wanted to read. Unfortunately it was only available in PDF format and AlReader can't handle that. I soon found that something like EBookDroid really couldn't deal well with a PDF file that begged for text reflow (problematic as that is). I wanted something that was at least as good as the stock reader. I could have just picked up one of my other NSTs and read the book that way, but when you abandon the B&N system you should at least break even, not lose. So I went searching through the forum for some ideas.
Mantano Reader caught my interest. Not only can it reflow PDF text (pretty much like the stock reader-don't get too excited), it can also display PDFs as a continuous scroll, with zoom. It can handle Adobe DRM books! And the TTS works (not a big deal). So I looked around and started with version 2.2.12 from Apkpure. This is the last version for Android 2.1. I found that full-screen reading was broken in this version and I couldn't see why, so I worked my way back until it wasn't broken. That was version 2.2.3.
Not for everyone
Those are some of Mantano's virtues, but it's not for everyone. I think it's chief drawback is the absence of full font support. There is only the default (admittedly not bad) and although there is provision for user fonts, there are issues. More on that later. Then there is the really tiny user interface. The colors render somewhat muddy on the NST also. Those are really tough issues to address, certainly beyond my pay grade. Also, none of the syncing, cloud, downloading of dictionaries, OPDS books, fulfilling of .acsm files, additional fonts, user manuals, etc., works. Can't be fixed. I looked. Finally, the reader options are pretty simple, about what is available for the stock reader (except for fonts). So if you like the hundreds of setting combinations in something like AlReader or FB Reader, this app is not for you. If you want something straightforward so you can just read a book without all the B&N hoopla, Mantano may be worth a look.
Mods
When I started getting serious about this I decided to try to learn by doing. My goal was to remove (or at least hide/disable) stuff that did not work. Almost all of my modifications were in the resources folder of the apk file. There was also one annoying issue with the aspect ratio of book covers that required a minor change in two smali files (thanks to @Renate). Here's a short list:
1. Removed Bookstore (OPDS) tab on home screen (formerly "My Catalogs" as described in User Guide)
2. Removed menu icons for sync and cloud
3. Disabled sections in Settings that don't work (Login, Sync, Dictionary download, Fonts, User Manual download)
4. Corrected font colors in some local dialogs so text is visible
5. Made the page number black, smaller, and with a transparent background for less visual distraction
Also, there were a few dialogs with invisible text that used the system framework to generate the window. The only way to fix this was to make a few very minor changes in framework-res.apk. This worked well and even helped with a few other apps that formerly had invisible text. A win-win. You can update your framework-res.apk using the CWM zip provided below. Despite its filename, it is not an "update" zip. You'll just be installing a zip file with CWM.
Making do
Overdrive Library epubs: No app will be able to fulfill .acsm files on the NST/G. The SSL is just not up to it. So there's no point in registering the device with Adobe. That just wastes one of your allowed devices and so I disabled that first Settings selection. However, the app can read Adobe DRM books, understands due-dates, etc. You just need to introduce your device to ADE running on your PC (ver. 3.0 works well for me on Windows) and transfer fulfilled books from there, just as you would with the stock reader.
Fonts: You can, in theory, supply your own TrueType fonts and place them in /sdcard/Mantano/fonts. When a book is opened, the lower menu options include "Themes". This odd term is for adjusting the appearance of the book (fonts, margins, justification, line spacing, colors). You can make a new theme or edit the default one. Either way, you will get to select a font. You will see the font you added in the folder (you can copy any font you like from /system/fonts or from anywhere else). The problem is that Mantano has no way to deal with font families. For example, I prefer Malabar. Of course, there is the base font, the bold instance, italic, bold italic. Mantano makes you choose one of these. Clearly you choose the base font (no need to copy over the others). If there are italics or bold type in a book, the reader uses the default font. This would not be such an issue for small sections of emphasized text, but the font scales are not the same. Malabar is larger than the default font. So any italics is obviously smaller. I tried a software package for scaling the font but it just turned it into rubbish. I am learning to like the default font. This issue was fixed in version 2.4.6, based on what I've read. But that won't run on the NST, of course.
Dictionaries: The reader has the ability to go out to find definitions on the WWW. Big pain. Although you can't download any dictionaries from within the app, Mantano does play nicely with ColorDict and there are plenty of dictionary options for that. Easy fix.
User Guide: I poked around and found a guide labeled "Version 2.1". That was the best I could do. It seems pretty close, although what was the "Bookstore" tab in this version (which I have removed) is referred to as "My Catalogs" in the manual. Either way, it's non-functional and gone. The same goes for references to cloud, accounts and sync. None of it works and all of it has either been removed from view or disabled in this mod.
Extras
Unlike AlReader and FB Reader, Mantano's main activity is the library view. That means there is no simple way to use the "reading now" status bar button to go directly to your current book.
I also like to be able to use the current book cover as a screensaver. AlReader and CoolReader both have this capability. Mantano does not, but it does create thumbnails for each book (if you let it) and one of those is screensaver size (default.png). For some unknown reason, all the thumbnails of various sizes for display in the library have the correct aspect ratio except for default.png. I fixed this in the app with a view to using it as a screensaver image.
To address these issues, I have used Tasker to create two small apps. Mantano_Extras1 enables a listener for when the reader is closed (either by two presses of the back button or simply by pressing the "n" button). When that happens, the Mantano database is queried for the last reading point/book. This is stored in a variable. Accessing Mantano_Extras1 after setup sends a command to open that file. If Mantano is your default app for epubs and/or pdfs, the book will open automatically to the right place without passing through the library. Thus assigning Mantano_Extras1 to the "reading now" button with NookTouch ModManager restores the function of that button.
Mantano_Extras2 does everything described above. During setup it also creates the folder /media/screensavers/CurrentBookCover. When the reader is exited and the database information stored in a variable, it copies the default.png for the current book to that folder. If you select that folder in your NST Settings app for the screensaver, the current cover will be displayed during sleep.
I should add that both apps check to see if the current book has changed before they do anything. If there is no change, they simply stop.
As these are Tasker-generated apps (but don't require Tasker to run), they have a dependency on two small library files. If you don't have one of my other Tasker apps already, you need to copy the two files in the zip as below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
The apps also use sqlite3 and busybox. If you rooted with NookManager you already have busybox. A few other special packages probably include it. If you have it, you will find it in /system/xbin. If it's not there, copy the file from the zip to that location and set permissions to rwx-rwx-rwx.
If you don't already have sqlite3, move the file from the zip to /system/bin and set the permissions to rwx r-x r-x.
When you have prepared the way, reboot and then install whichever of the two "Extras" apps you want. When you first tap on the app icon there will be a pause while things are set up and then a request for root access. Once that's done they are good to go. Use NTMM to assign the app to the "reading now" status bar button and set your screensaver directory to "CurrentBookCover" (if you installed Mantano_Extras2).

This is nice work. I have heard good thing about Mantano reader before. I believe it still exists although under new name I think. Its sad that you had to remove app options to make it work on NST. Still I am glad that you make some improvement that could if exploited properly make this device better than before. I believe that solving invisible text message is best of what you did and if understood properly can make number of apps that had this problem before usable again for this device. I would not dismiss even TTS working as I remember that someone tried to implement that on NST before yet I do not remember it was solved. So if it work out of box with Mantano reader it might be prudent to see what makes it work if it is fine TTS not some hardly intelligible sound generator. This options you removed how did you confirmed that they are not working? For cloud I believe it was NST lockout and now enforced TLS1.2 it can not reach that gives you hard time. Yet for syncing it is little harder to understand. For the rest like OPDS and such I guess my knowledge is not sufficient to guess how that even work so if you know more than me I am more than ready to listen.

SJT75 said:
I believe it still exists although under new name I think.
Click to expand...
Click to collapse
Now Bookari.
SJT75 said:
Its sad that you had to remove app options to make it work on NST.
Click to expand...
Click to collapse
I didn't so much remove options to make it work. It worked as-is, but not the login/download components, and they are not necessary for the reading functions.
SJT75 said:
I believe that solving invisible text message is best of what you did and if understood properly can make number of apps that had this problem before usable again for this device
Click to expand...
Click to collapse
It's possible. I noticed improvement in dialog boxes for ES File Explorer. But there are other types of dialog boxes and I only dealt with what was needed for this app. Spillover is a gift.
SJT75 said:
I would not dismiss even TTS working as I remember that someone tried to implement that on NST before yet I do not remember it was solved. So if it work out of box with Mantano reader it might be prudent to see what makes it work if it is fine TTS not some hardly intelligible sound generator.
Click to expand...
Click to collapse
Well, that could have been me. Pico TTS (if not removed) always worked on the NST if you downloaded some voices. I have a post about this somewhere with links. But the quality is really wretched. I looked at this further awhile back and found that Google TTS began with Android 2.2 (of course). There is a "bridge" system involving a custom settings app but each application must include this custom code to work. I did a MOD for AlReader to enable this, but it's not easy and would be (nearly) impossible for Mantano as very few of the smali files have descriptive names. Most are just "a.smali, b.smali", etc. So it's really difficult to track down what you want.
SJT75 said:
This options you removed how did you confirmed that they are not working? For cloud I believe it was NST lockout and now enforced TLS1.2 it can not reach that gives you hard time. Yet for syncing it is little harder to understand. For the rest like OPDS and such I guess my knowledge is not sufficient to guess how that even work so if you know more than me I am more than ready to listen.
Click to expand...
Click to collapse
It's not all SSL. Or it may be that also. The URLs in the apk file don't go anywhere, even on my PC browser. So far I've gotten up to version 4.5 and still no working URLs. Perhaps when Bookari emerged as the name the old URLs were abandoned and the old Mantano apps became crippled in this way.

Thanks nmyshkin you clarified some things. I agree that change to new platform and abandoning the URL domain for cloud use could be cause for that option not functioning anymore. Yet unless the syncing have not be performed through a same route (login account on the same domain) sync should function fine from one device to another for example. About the rest you are correct I have come to a same conclusion that even slight upgrade of Android on this device would make vast improvement in options available to exploit. Sadly B&N did not go that way. I will look upon PicoTTS to see if something about the way it actually work can be understood to evaluate if it is worth the effort or it maybe can be discarded as irrelevant for this device.

Just crossed my mind... nmyshkin did you tried to hunt down inside apk file exact spot where that URL is written/coded and change it to something else like IP address of your computer/drive/*/*/sync folder ?

SJT75 said:
Just crossed my mind... nmyshkin did you tried to hunt down inside apk file exact spot where that URL is written/coded and change it to something else like IP address of your computer/drive/*/*/sync folder ?
Click to expand...
Click to collapse
No, it didn't occur to me. I only read on one device so that's not the kind of thing that interests me. Also, I just transfer books over from my PC to the Nook when I get them, usually via FTP.
I did see cloud, sync, etc., URLs but I suspect that just changing them would not produce the capability you seem to be hinting at. It's likely a lot more complicated than that. It seems to me that syncing implies active communications from both ends. Teaching your PC to respond to the overtures of the Nook would be a whole other rats nest.

You are correct. Using URLs to connect to PC is not safe. Therefore some home workgroup network or SFTP access are more reasonable way. Maybe if you change cloud sink URL to Dropbox folder you get something?

SJT75 said:
You are correct. Using URLs to connect to PC is not safe. Therefore some home workgroup network or SFTP access are more reasonable way. Maybe if you change cloud sink URL to Dropbox folder you get something?
Click to expand...
Click to collapse
I don't think so. The app innards were designed for negotiating with certain remote servers and expect a certain dialog. Just changing the URL doesn't address these issues. Using Dropbox as an example, there are login credentials to be supplied and other issues to be addressed before files can be freely moved in either direction.

Well yes unless dropbox folder is public shared one what I wrote will not work. What if you link sync/cloud to internal folders on device inside Dropbox application that also initiate script written to execute Dropbox synchronization? Then login credentials would come from Dropbox app I think.

SJT75 said:
Well yes unless dropbox folder is public shared one what I wrote will not work. What if you link sync/cloud to internal folders on device inside Dropbox application that also initiate script written to execute Dropbox synchronization? Then login credentials would come from Dropbox app I think.
Click to expand...
Click to collapse
1. I am not a Java programmer. What you are suggesting is going to require significant changes in the app. It's not in the same league as the modifications I made.
2. I have no interest in the feature. People who must have synchronization with myriad other devices would be better served by selecting an app that currently has this feature working (like FB Reader).
3. If someone who is a Java programmer and is interested in this feature wants to take a crack at it, more power to them. I personally think it's a dead end. Just about the time you get it figured out, Dropbox will no longer work on the NST. Any modification that relies on exchange with an external commercial server has a built-in self-destruct timer, just waiting for tightening external server access rules. It's over for Android 2.1.

nmyshkin said:
Just about the time you get it figured out, Dropbox will no longer work on the NST. Any modification that relies on exchange with an external commercial server has a built-in self-destruct timer, just waiting for tightening external server access rules. It's over for Android 2.1.
Click to expand...
Click to collapse
Amen to that. Making NST more cooperative with Calibre is much better option anyway. Commercial server could be also a trap. There was an outcry when Remarkable for example started charging access to their services out of blue and without warning.