▮ Prepaid Widget ▮ Your Account Balance in Widget Form ▮ - HTC Sensation

Hello everyone! I am the developer of Prepay Widget, a powerful app that allows you to monitor your account balance through USSD requests.
You can find more info about USSD on Wikipedia, but basically these are short, SMS-like messages used by most GSM and some CDMA providers to deliver information
or control account services. The actual information comes to you in the form of popup toasts, which thids app hides and parses into widgets.
You can find the apps landing page on XDA at the following thread:
http://forum.xda-developers.com/showthread.php?p=12348102
However, i want to stress that its important that we get some device-specific feedback, so please post in this thread if you have issues,
this helps me keep track of bugs and requests better.
You can use the Lite version of the app - it has all the functionality of the full version apart from automatic updates (not really that important imo).
As I haven't got one of these phones in my pocket, I need some testers to track down problems. Please, use this thread to comment or
suggest features. It is my belief that addressing issues is best done individually by phone, so if something doesn't work, let me know and I will fix it ASAP.
Market link:
https://market.android.com/details?id=fahrbot.apps.ussd.widget.lite
Debugging:
Please use the "Write to developer" item in the Settings menu to send logs. Enable debugging, reproduce your error and then send the logs.
Make sure you include a description - the more detailed the description the better.
Screens:

1.3.3.0
Added full Russian translation
Fixed many small errors from user logs
Fixed rare radio restart issue on some ICS buils

Anything to report?

Related

[APP] App Stats (for developers)

App Stats is an Android developer tool which allows you to check application stats and comments from one place. App Stats keeps you informed by notifying you when new information is available such as a new rating or additional comments. The lite version allows you to monitor up to three applications and includes advertisements while the pro version allows for essentially unlimited monitoring and is of course ad free.
Update to Pro (v1.3.0)
Now has a desktop widget =)
Update to Pro (v1.2.0)
Some developers may have a lot of apps to manage stats on such as games with lots of addon content or maybe live wall paper apps, etc. To help alleviate scrolling through a long list of apps, we have added in the ability to label apps and filter the apps list with these labels.
Also, you will find that you can now set per application notification settings. This lets you control when an app update notification is fired so you can now choose specific items to be notified about.
Notes
On certain devices you may not be able to see all of your apps without having root on your device. It is also important to note that if you can not see your app in the market on your device there is no way this app can circumvent that.
If you have any questions, comments or bug reports please contact me here or via our developer email which can be found on the market. (toxicbakery at gmail)
To download, use the attached image or search 'App Stats' on the market and we should be the first two results for pro and lite versions.
Known Issues
- Certain languages may no be available in comments, if you find one please let me know
Upcoming Features
- More graphing options
- Backup search against an app database to find missing data
- Have a feature request? Let me know what you want!
Need another feature? Just ask =)
I love it. But I think that $5 is a bit too much for the full version. I would have gladly paid $2 or $3 even, but anything more takes it out of impulse buy for me.
Don't think I'm bashing your choice, as a dev I understand your need to make money from it, but sometimes the sales you lose from a higher price are worth more than the extra couple dollars you'll make from the higher price.
Thanks for the input! I would have to agree with you that currently $5 dollars is on the high end of price however with the additional features we are working on we feel that it will be a fair price very soon. Depending on what features we end up being able to incorporate we may adjust the pricing.
We almost have the plugin finished that will assist in grabbing your market android id from tcpdump and once we perfect that then it will be possible to search 2.2 apps and copy protected apps when using legit android devices that are rooted. Once this is complete we will have the only app on the market that I know which can essentially hands free get all the needed info to make a 'true' market request that lets you see all applications. This is how sites like androidzoom and like function. Without this additional parameter other apps are limited to 2.1 and less non copy protected applications by design of the market itself.
After that we will be working on letting you attach admob accounts to your apps and possibly google checkout however google checkout looks iffy due to its seeming lack of being able to pull useful information such as 'total sales' etc.
That said, thanks again for the input and if you need help please email me at our developer email for fastest response.
-Ian
One thing that's highly annoying for an application which is not a game, a navigation system, or a media application: Asking for the fullscreen window feature.
Please consider removing it... I don't really see any need for it, and it just breaks the transitions between activities anyway (when you're not making the design consistent). Thank you.
Anyway, once polished up and the bugs cleared up, looks like a useful app
Thank you for the input! We removed the full screen requests on the detailed view and graphs view.
I'm unfortunately out of town currently however either tonight or tomorrow we will be releasing an update that adds in the functionality to search 2.2 and copy protected apps if you have a rooted device. This should alleviate the complaints some people have had about it not finding their apps.
Unfortunately right now having a rooted phone is the only way get the market key we need to make these 'fully enabled' searches due to how the market works currently. The other option is having users use TCP dump to grab the needed packet and then proceed manually with decoding it and running it though protobuf to get the key out.
A few other fixes and tweaks have also been put in place and after we release the updates the Pro version will be available again as we removed it due to a major bug in the licensing we didn't catch before.
Please keep the comments coming! If you don't like something feel free to post it or email us and we will do whatever we can to improve it.
Thank you again to everyone that has voiced their opinion, every bit helps!
Finally got the new version released!
To see copy protected or 2.2 only applications you will need to have a root phone that can already see those apps on the market. For example a 2.1 phone can't see 2.2 applications no matter what you do and theres no way to code around this, sorry.
Once installed, hit menu from the main screen and select settings. Simply hit the "Load Key" Button at the very top and hopefully after a few seconds a Toast should show up saying that the operation was a success.
I know for a fact this wont work on all phones. We tested it to work on a Droid and it works on a G1 with Cyanogen 2.2 rom however it will not work on an Eris. That said I'm sure it will fail to work on other phones but I will be working on figuring out the fix asap. If you are one of the unlucky ones with a phone that doesn't work, please email me or message me here and I will do whatever I can to get you setup!
New version is now out and good news! It appears, on our end, that root is no longer necessary to get copy protected and 2.2 applications. This change is still too new to confirm it works on all devices so please send us feedback on if you can see all of your applications without using the root feature.
As always please feel free to leave feedback!
New version released that will hopefully allow more users to successfully find all of their apps with less hassle. Also a few misc bug fixes and FC issues have been resolved.
Update to pro version released, main post updated.
Released new versions of lite and pro, updated main post.
About App Stats and its development
I am from Mobile application Development company in Singapore. I would like share this stats, today more users are available in through mobile apps. and mobile developments also increasing day by day. So this growth of development is lead the business strategy. Know from our Mobile app development how its useful for business environment.

Swype Beta 3.25 and Swype connect

Im a fan of swype and have been for a long time.I saw there was a new beta version out so i went to check it out to see whats new. I saw something called Swype Connect which is basically a process which will allow swype to upload ur usage data to Swype.
Call me paranoid but im not sure i want anyone to have access to ANY data from my keyboard ( i had a keylogger incident long ago ). It even send your ESN as an identifier :S.
They do have a FAQ regarding swype connect
http://forum.swype.com/showthread.php?4356
But still i am wondering if anyone has anyway to disable that part of it? I dont like it when apps have to call home.
Yes, I've the same question...
Or at least anyone knows if its possible to block its internet access?
the new swype is supposed to notify you when a new beta update is availble hence the internet access i read this on an android website cant remember which 1 sorry
if you are rooted you can block internet with droidwall its on the android market
roccoadam32 I'm talking about this:
What is Swype Connect?
Swype Connect is a background service that allows Swype to communicate back and forth between the Swype application on a phone/tablet and Swype's servers. While it currently only consists of 3 segments - licensing, automatic updates, and measurement data - it has been designed to support more features in the future. With Swype Connect, we have more tools to continuously improve users’ experience with Swype on-the-fly by learning more about how Swype is used and where our current methods are falling short.
This first version of Swype Connect focuses on implementing the core systems necessary for ongoing development of this service. 1) Licensing allows us to uniquely identify each device that Swype is installed on, so that we can verify the authenticity of each installation, and learn more about the kinds of devices people are using Swype on. This is not new, all Swype Beta releases have previously collected this information using the Swype Installer. 2) Automatic updates allow us to notify users when there are new versions of Swype available, and deliver these new versions directly to your device over your data connection. 3) Measurement data tells us more about how Swype is actually being used on a daily basis, so that we can continue to improve Swype.
What information are you collecting?
For licensing we collect very basic device information such as make, model, screen resolution, cellular ESN, etc, to identify the device. None of the device information is personally identifiable. We will not share any of the device details we gather with third parties, except when required by law. For measurement data, we gather a number of statistics about how Swype is being used to make sure that it performs to our best standards. For this purpose, Swype may collect: Speed of text entry; language selection; how often words are added/removed from the Personal Dictionary. NOTE: Swype does not collect the actual words added/removed, nor any of the words you type, just how often words are added and removed in general. All of this is done in the background, with no noticeable impact on how you use Swype or your device. Additionally, the privacy of our users is incredibly important to us. Beta account information and usage data are stored separately, and are not associated with each other. When we analyze the data we collect, it is done in aggregate and users are completely anonymous. We also encrypt all data during transmission for additional security.
Can you link the usage data you collect back to me personally?
None of the usage data is personally identifiable, and is stored anonymously, so nobody can look at it and figure out who you are. Additionally, usage data and beta account information are stored in separate databases. The only piece of personally identifiable information we have - your email address - is not included in statistics collection, and is never associated with usage data.
What differences will I notice now that Swype Connect is on?
Absolutely none! In fact, you might even notice Swype working more reliably than before. Swype Connect is designed to run in the background, at low priority, and only activate rarely when it needs to check its license or submit gathered measurement data. The amount of information passed back to our servers is very small - usually less than 1kb - so you won't see any excessive data usage coming from Swype Connect. The measurement data collection itself takes place as part of Swype, so you won't notice any extra battery drain either.
Where can I get more information?
If you have more questions about Swype Connect, please get in touch with us! You can post on our forums, send us a tweet, or chat with us on IRC. We're happy to answer any questions you have. You can also read our complete privacy policy for more details.
Click to expand...
Click to collapse
http://forum.swype.com/showthread.php?4356-DETAILS-Swype-Connect-Statistics-Collection-and-Privacy
I'm going to investigate droidwall... thanks!

[NEW] New Android service: Get rss/atom notifications for App updates

Work-In-Progress
Domain is up
AppFeed.net
​
Coomon problem:
As many of you knows, there is no app or service for Android where users can request notifications of application updates, especially the price changes (mainly price drop), or updates for slow updating apps.
Solution:
My solution was to develop a website where users can add applications to a list, and get a unique RSS/Atom feed that notifies them whenever the apps gets updated (Price, Version, etc).
The feed can be added to any application that support it: Desktop Readers/notifiers (tested with Thunderbirds), Web-based readers (Tested with Google Reader).
I intended to add other forms of notifications, but later found that with the service if this then that I can create tasks that monitor my unique feed that do everything else: Email notifications, Twitter posts, or any other channel provided by the ifttt.com service.
Usage examples:
Some usage examples for such a service:
1) I like a paid app, but its cost is a bit high for me, so I add the app to my watch list to get notified if/when the app gets on sale, instead of having to check frequently or miss an opportunity to get the app during a great sale (happened to me few times already).
2) I like and played a game, and finished all levels, the developer promised extra levels, instead of leaving the game installed on my device and wait for updates, I can uninstall it and add it instead to my list and get notified when it's updated.
3) With Android Play Store auto update feature enabled, I miss most app updates, with notifications on selected apps I can see when those apps gets updated.
4) Other usages...
Status of the project
Currently this project is being developed and tested by just myself, and it seems to be working as expected. But to have a good service, I need some to extra help to test it better, to suggest features, etc.
What is mainly missing is some legal advice, such as a privacy policy and term of service, and on whether I can put up such a service (does Google allow this kind of service? knowing they do not provide API for the Google Play).
What is still missing the some text, I am not a native-English speaker so still trying to put things correctly.
Privacy
I take privacy issues very seriously.
To make this service work, I opted for using 3rd party sign-in (Google and Twitter), what is saved on the DB is a hash of the sso unique token, not even I can get the clear one. User name and email are required, and are saved encrypted in the DB (with AES), and get decrypted only during login to show your name on the top bar, nothing else.
Here is a screenshot of the main wishlist:
And here is what you get in the rss feed, through Google Reader:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Click to expand...
Click to collapse
My topic is more development than questions, maybe not an Android App but and Android service
Updated post #1.
project is going well, anybody is interested, please let me know (by leaving a comment), if I get enough feedback, I'll get a domain and host it somewhere, currently it is running on a personal domain.
Update:
Got a domain for my new service, and now it is up and running.
check the first post for link and info
Hi,
while using google for authentication, I am actually notified that your website wants to "manage your contacts".
What is the reason behind that?
Thanks a lot
ale
alanzed said:
Hi,
while using google for authentication, I am actually notified that your website wants to "manage your contacts".
What is the reason behind that?
Thanks a lot
ale
Click to expand...
Click to collapse
For the authentication I use the HybridAuth library, and this is the minimum that I can ask for from Google for use the OAuth authentication, if there is anything less, I'll do it, but I can't find how.
Twitter authentication has just Read Only access (Minimum available).
Update:
Found the solution, now it doesn't ask for Manage Contacts...

[APP][4.1.2+ with OpenPDroid or PDroid2.0] PDroid Manager ALPHA[2013-01-12 v0.2.9.8]

A quick note
If you've come from Google Play to get support, welcome! I'm glad you made it here.
Please do post a description of the problem you are having, but you may also want to read the section below labelled What should I do when it fails?, as this will make it much easier for me to provide support.
If you're having a problem, the place to post it is here, because if you do so on Google Play then I have no way of responding. Unfortunately, this has been the case where an issue has become apparent, and I have included a fix, but there is no way for me to notify those who had the problem.
In any case, back to our normal program...
What is it?
PDroid Manager is an alternative OpenPDroid/PDroid 2.0 Management App. It is currently the 'official' management app for OpenPDroid, and serves as an alternative to the PDroid 2.0 App for PDroid 2.0.
It is GPL licensed (with additional attribution conditions). Source can be obtained from my github.
What does it need?
First, this relies on either the OpenPDroid Core/Framework patches (recommended), or the PDroid 2.0 Core/Framework patches being present in the ROM. You need to have them installed, either by getting the patches (OpenPDroid, PDroid 2.0), patching and compiling a rom yourself; or using the excellent autopatcher tool by mateorod and pastime to patch an existing rom.
It also requires Android 4.1.2 or 4.2.1.
Status
This app is in a supremely alpha state. It does have bugs. It will crash if you run it without the PDroid core/framework patches. It does have a problem with the way notification icons display if you install multiple apps without configuring them. It will crash in a range of other situations I haven't thought of yet.
It will crash if you try to use it while you have the PDroid 2.0 App installed. (It's a permissions signature thing, and you can't have both installed unless you resign them both yourself: see here for how to do that.)
It has been tested on three devices a Galaxy Nexus running AOKP, and a B&N Nook (cheers to mateorod) and a Nexus 7 running AOSP.
Probably others too now, what with people using it, but I don't have a list for that =)
What is the difference between this and the PDroid 2.0 App
This is an ALPHA status tool, so it has more bugs.
This isn't complete - it is missing useful things like an 'about' box, the ability to check the PDroid core version, backup & restore, all of which are in the PDroid 2.0 App.
It can keep logs of application activities. There is currently no way to view these, though. Logs are now (I think?) supported in PDroid 2.0 App. I haven't tried them though.
You can filter the app list by whether it is a system or user app, and by the type of permissions used. Now also in PDroid 2.0 App.
You can filter apps by the 'type' of permission they use - e.g. 'messaging', 'calls', etc.
The source is available.
It can create and restore multiple (human-readable) backups on your SD card or 'external storage'.
It supports multiple languages, thanks to the contributions of others (languages and contributors are listed below) PDroid 2.0 App now supports German and English (but not Russian and French).
Did I mention it has more bugs?
What is the difference between this and Permissions Denied, and other permission-modifying apps
In brief: OpenPDroid and PDroid 2.0 do not actually change the permissions of apps; rather, they intervene when the apps try to use some of the features allowed by these permissions. For example, it doesn't remove permission for an app to use the camera - instead, it lets the app believe it is using the camera normally but then feeds back a fake image when a 'photo' is taken. Similarly, the app can try to request the phone number from the phone, but PDroid can return either a blank number, or a fake number, to the app. The main advantage of this is that rather than the app crashing, as often happens if it finds expected permissions have been removed, it continues to operate simply using incorrect data as its input.
The downside is that PDroid requires modifications to the ROM, which is difficult.
What should I do when it fails?
First, check if the problem you have discovered is a known issue, by looking at issues on my github. If if has already been lodged, but you have additional information to add, then ideally attach it to the issue in github. Otherwise, you can post it here but please clearly refer to the existing issue in github when doing so.
If it is not a known issue in the github:
You can open an issue on my github, providing a logcat: see how to get a logcat.
You can post on this thread, providing a logcat. I will try to monitor this thread, but if it starts getting out of control then I will probably try to run up a bug tracker somewhere else for people to use (and I will always fall back on the github issue tracker).
When will you stop telling me about the bugs and give me a link?
I have added PDroid Manager to the Play store, so you can obtain it from there (which means easier updating). If you do get it from the Play store, remember that support is provided via this thread, not via the Play store comments. I have only added the app to the Play store as a convenience so people can get updates without monitoring this thread.
Check the attachments to this post for the PDroid ALPHA releases. Make sure you read that ALPHA part.
Source at my github.
Requirements: Android API 16 (i.e. 4.1.2 - haven't tested in 4.2 yet).
What does it look like?
This:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did you build it?
The original PDroid app by Syvat, and the subsequent PDroid Addon/Extension/2.0 apps by CollegeDev didn't do everything I wanted them to do. I couldn't modify them because I didn't have the source. I'd never created an app before and I wanted to give it a shot.
Why does it need permission to access my SDCard?
I've added the ability to backup and restore your settings to the external storage. In order to do this, I need to be able to write to, and read from, the external storage. I will be adding a version at some point which doesn't require this permission, and cannot do backups.
Isn't doing backups to the external storage really insecure? Couldn't another program edit my backups?
In general, doing backups to the external storage would be insecure, in two ways: other apps could read your settings from the backup, and other apps could edit the backup so when you restore it your settings are wrong.
The ability for other apps to read your settings is a problem even ignoring backups. The Pdroid 2.0 Core (and the original PDroid Core) do not prevent applications from reading settings without any permissions whatsoever. Yes, any app can read your settings directly from the PDroid service. That is the way the PDroid core is built at present (and I don't much like it, but that's another story).
The second problem is one that I have attempted to address. Each installation of PDroid Manager will generate a 'digital signing key', and any backup you create will be signed with this key. When you attempt to restore the backup, the signature is checked to ensure the backup (or signature) has not been modified. If the signature doesn't match, you are warned and given the opportunity to restore anyway. You cannot export this signing key, because exporting that key to your external storage would make it accessible to other programs, and with it they could re-sign your backups to make it appear that they had not been modified. This means if you uninstall and reinstall PDroid Manager, you will get 'invalid signature' warnings on all the backups made from previous installations. If you don't want this to happen, I recommend downloading and using Titanium Backup - it will store the encryption key (although on external storage, which itself could be a security risk). Thus, unless you uninstall and reinstall your PDroid Manager installation, the app will verify that backups have valid signatures before restoring them. Mind you, a root app could steal the signing key. As is always stated, for root apps it is all up for grabs.
I have a great suggestion! How should I get it to you?
First, keep in mind that there are various degrees of detail which can be provided with suggestions, such as:
A suggestion of a feature which could be included
A description of how the feature should work (e.g. user cases: list XYZ, then user presses N, dialog P opens, etc.)
Storyboards or images of what the feature could look like (even if it just a box diagram done in Powerpoint or something).
A suggestion of an app which implements a similar behaviour that could be used as a reference for implementation
A bit of example code
Suggestions of new features are excellent, and some suggestions need less description than others - e.g. "add a help button to each setting" needs less description than "add the ability to filter by the 'trust' state of the app" (although in both cases, interface diagrams could be helpful: e.g. should the help button go to the left or right of the text label for the setting?)
You don't have to provide all of these details, and indeed even if you do provide some details I may not actually use them (e.g. if your suggested images were very inconsistent with the Android UI idioms, or the rest of the app). You can certainly make suggestions that are quite simple: e.g. I would like to be able to apply settings to multiple apps at once, or I would like to be able to filter by individual settings rather than groups of settings (although the latter would be a good candidate for interface suggestions too). If you are suggesting complex features, though, some suggestion of how the interface should work could be handy too - even if I don't use the suggestions as such, they can be very useful for giving me different perspectives.
If you have a suggestion then please describe clearly the suggested feature, interface or behaviour change, or whatever your suggestion it may be. If it requires a new UI screen, or a change to an existing one, descriptions of how it should work, drawings or imagery (or pointing to another app) are very welcome.
In order of 'most desirable' to 'least desirable' (from my perspective) I suggest:
Post the suggestion to my github
Post the suggestion on this thread
PM me (this is low on the list because if I get a flooded PM box it will be hard to find anything).
Finally, remember nothing says "I'd love this feature to be in the app" like a patch to implement it
Can I contribute a translation?
Absolutely! I welcome translations! The process for doing a translation will depend on whether you have a github account or not.
Currently we have translations being contributed for:
English
French (jpeg729 and patrickpr)
German (TamCore)
Hungarian: appelsson
Russian (Beasty)
If you have a Github account
You can fork the PDroid Manager project, and create a "values-xx" directory for the relevant language (e.g. values-de for German). Into that directory, you will need to copy:
Files containing text displayed to the user are:
access_notification_text.xml, which is the text for notification messages provided to the user when an app attempts to accesses a particular type of data.
arrays.xml, which currently contains the text of the drop-down lists used for filtering, and the 'Untrusted, Trusted, No Settings' text displayed.
settings_strings.xml, which contains the text descriptions of each setting, and the associated help text. (I have *just* pushed an update to github for this file, so if you want to translate it make sure you do a pull).
strings.xml, which contains the 'general' strings used in the app.
Once you have created those files, you can commit them, and then create a 'pull request' so I know they are ready to be integrated. I'll then integrate them.
If you don't have a github account
You will need to download the four files linked above, and translate the strings in them. Once you have done that, post to this thread with the files attached.
Remember:Keep in mind that if you have the files sitting around for a while in a partially translated state, they could change in development! When doing translations, make sure you have the latest version from the server. If you find that the strings etc have changed on the server, and you have done a partial translation, you can use a tool like WinMerge to merge the new changes into your file without a lot of work.
Also, if you are creating translation files, please include yourself as an @author in the header to the file, or nominate the details you would like to have recorded against your authorship. Also note that basically the entire app is under a GPL license, and I will only accept material which is licensed under a GPL or BSD license, to make sure that people are free to copy and edit the code as they see fit.
What do you have planned next?
Fix bugs
Add a 'preferences' and 'info' screen to check PDroid core/framework version, etc mostly done
Add help to the individual settings, so users can understand what they mean DONE!
Add the ability to view log and delete logs
Add the ability to create 'profiles' - i.e. pre-configured groups of settings, which can then be applied to an app
Add batch processing, so profiles can be applied to multiple apps in a single action Released in 0.9.3
Add filtering of apps by individual settings, not just by 'setting group'.
Add filtering of apps by setting state (i.e. trusted, untrusted, no settings)
If you want you can give it a go. Read the source. Have fun. Just don't complain that you haven't been warned about it being buggy.
2013-01-15 v0.2.9.9 ALPHA
Changes
Added support for 4.2.1 - not that it stopped you installing it anyway, but for Google Play it mattered =)
Added Spanish support, thanks to alceasan.
2013-01-12 v0.2.9.8 ALPHA
Changes
Fixed a force-close affecting everyone as a result of a corrupted APK. Sorry about that, all!
2013-01-12 v0.2.9.7 ALPHA
Changes
Added Hungarian language support thanks to appelsson.
Updated French language support thanks to jpeg729.
Fixed (I think) a bug in which the app crashed when an installed app does not have an icon.
2012-12-15 v0.2.9.5 ALPHA
Changes
Theoretically fixed a bug which I was unable to reproduce (but I think I know why) which caused a crash rather than a friendly message when a user attempted to run PDroid Manager without the PDroid core installed.
CHANGE LOG
2012-12-15: v0.2.9.4 ALPHA
Changes
Added detection of whether necessary permissions to write to the PDroid core were present, and provide a friendly message if they are not. (These permissions are absent if PDroid 2.0 App is installed before PDroid Manager, not uninstalled before PDroid Manager is installed, and the two packages have not been re-signed with the same key).
Otherwise, this version is identical to v.0.2.9.3. It was just added because I saw some crashes due to PDroid 2.0 App being installed with Google Play users.
2012-12-14: v0.2.9.3 ALPHA
Changes
The main stand-out of this release is batch processing: further details about that are after the list.
Instead of crashing if you don't have PDroid installed, it will now give you a message telling you that you need to install it.
Batch processing: you can now select a bunch of apps, and change their settings. Long-press on an app to enter selection mode, touch other apps to select or deselect them, then use the action bar options to choose what to do.
Added a 'purge settings' option to preferences. This deletes all settings for all apps.
Changing language now triggers a restart of the app (after prompting the user) to immediately switch language
Restructured the filtering interface to work better on smaller devices, and generally look nicer.
Info/help buttons for settings only appear on larger devices now (due to screen real-estate issues). Clicking on the name of the setting will display the help on smaller devices.
Performance improvements
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing). Still.
I think there is still something funny going on with the 'trust' indicator after you save an app, but that may be a new issue. Still.
App names in the application list don't get reloaded when the phone locale changes, which means they stay in the old language until manually refreshed. I'm no longer going to call this an issue, because it is handled by the OS.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
Key points about batch processing:
When you select some apps and choose 'custom settings', only the settings relevant to the apps will be displayed (unless you choose 25+ apps; then it was too slow to work out which ones were relevant).
Only those settings you select new values for will be changed. Those with no pressed buttons will be left alone.
You can 'deselect' a button in batch mode by pressing it again (effectively clearing that setting row, so it will not be changed).
Batch processing can be a bit slow, but unfortunately that is a consequence of the Privacy service to which PDroid Manager connects. I have modified this service to improve performance, but I'm still testing the changes so the app does not require those modifications.
You can't avoid overriding the 'logging' and 'notification' settings when doing batch processing at this stage. I will resolve this soon.
2012-12-07: v0.2.8 ALPHA
This is a minor update: It provides an updated German translation from TamCore, and
Changes
Updated German translation from TamCore,
fixes the Application List scrolling back to the top when you open details for an application, thus losing your place.
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing). Still.
The app will probably crash if PDroid is not installed. Still.
I think there is still something funny going on with the 'trust' indicator after you save an app, but that may be a new issue. Still.
App names in the application list don't get reloaded when the phone locale changes, which means they stay in the old language until manually refreshed. Still.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
2012-12-03: v0.2.7 ALPHA
A couple of new features in this one, and returning to just one version (rather than multilingual and English). The backup and restore features are shiny and new, and *should* work, but be cautious when using them. I've tried them out quite a bit, with custom settings etc, but there could be bugs there that will cook all your PDroid settings. If you find one, please, please report it (see the section on reporting bugs).
Changes
Added a 'preferences' screen, with 'About' box, 'Credits', and a link to this thread
Added language selection (i.e. overriding phone language), again in the preferences screen. Note that for the language to change, you need to force-close and restart PDroid Manager after switching languages. I'm looking at how to resolve this.
Added backup and restore of settings. This requires access to your external storage, hence the new permission. I will be adding supporting code at some stage to allow a separate version without backup and restore to be easily generated for those who are uncomfortable with SDcard access by the app. You can read more details about the backup approach in the Why does it need permission to access my SDCard? and Isn't doing backups to the external storage really insecure? Couldn't another program edit my backups? sections.
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing). Still.
The app will probably crash if PDroid is not installed. Still.
I think there is still something funny going on with the 'trust' indicator after you save an app, but that may be a new issue. Still.
App names in the application list don't get reloaded when the phone locale changes, which means they stay in the old language until manually refreshed. Still.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
2012-11-30: v0.2.6 ALPHA
This release has two versions: Forced English (PDroid_Manager_0.2.6_en) and multilingual (PDroid_Manager_0.2.6_multilingual). The multilingual will automatically use the language matching the phone where possible. The 'en' version uses the exact code I intend to apply to allow users to override the automatic language selection. Basically, this is the same as having a button to force the app to always use English, except the button isn't on the user interface and is always pressed. If you find this isn't always showing English, please let me know so I can fix it.
Changes
Incorporated updated help text (fine work by wbedard, to which I made minor edits. Thus, errors are probably mine not wbedards).
Added German translation (thanks to TamCore) and French translation (thanks to patrickpr on GitHub; note I removed a few words from the translations because the English help text changed, so may have introduced gramattical errors into patrick's French).
Added automatic language data re-loading. To optimise speed, some language-specific text is stored in the database. To make sure that stays up to date, the App will check if the language has changed, and regenerate that database data if it has. If this doesn't happen for you, and the interface stays in English when you switch your phone to German, etc, please report it..
Added different button sizes for 'large' vs 'non-large' devices. This means that buttons will appear larger on most 7-inch tablets (and maybe 10-inch tablets too; my 10-inch isn't working right now) than on phones.
Modified the code to use Android 'Fragments': hopefully, this will be invisible to users at this stage; however, in future it will allow easier development of a multi-panel tablet interface. This is a pretty major change, so may have introduced bugs. Sorry.
Updated notification bar icon to match Google's style guide.
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing). I will fix this soon, honestly.
The app will probably crash if PDroid is not installed.
I think there is still something funny going on with the 'trust' indicator after you save an app, but that may be a new issue.
App names in the application list don't get reloaded when the phone locale changes, which means they stay in the old language until manually refreshed. I'm undecided as to whether to I consider this a bug or not. Feedback (or patch to fix it) welcome.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
2012-11-25: v0.2.3 ALPHA
Changes
Added improved text for the access notifications
Added a help button for each setting with a summary of what the setting does (I know it is ugly, and I plan to fix that soon).
The application list status indicator should now work under all normal circumstances
Dialogs have been added when loading, saving etc. to avoid interactions that could cause crashes
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing).
The app will probably crash if PDroid is not installed.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
2012-11-19: v0.2.2 ALPHA
Changes
Re-added some debug logging (but still much less than was there originally).
Added the ability to delete privacy settings from an app, both in the application settings detail screen, and on the long-press menu on the application list.
The application list status indicator (i.e. trusted, untrusted, no settings) now updates after the long-press menu is used, or the settings are changes in the detail display
An 'all' option has been edited when filtering by the type of settings (e.g. messaging, media, etc).
Known bugs
The trusted/untrusted is sometimes incorrect - 'trusted' apps may appear as 'untrusted'.
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing).
The app will probably crash if PDroid is not installed.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
2012-11-16, later: v0.2.1 ALPHA
Removed writing to the device log (so logcat will not be hideously large)
Contribution to PDroid Manager acknowledgements (in alphabetical order):
mateorod: testing assistance, great ideas, building Autopatcher.
patrickpr: French translation
TamCore: contributing Android.mk, markdown for tables in README.md which were unreadable, German translation
wbedard: textual descriptions of the individual settings
Still playing with the 2e version. I like what you have done with this a lot. Having an open source version will keep us from being in-between working versions, like we were between gingerbread and the auto-patcher release.
An open source alternative like this keeps that from ever happening again.
I had noticed that CollegeDev had not added preloaded-classes to his PDroid2.0 build patches, a potential security leak. Without any access to the source or even version control with the patches I didn't have much recourse to correct the issue. I was left to suggest it in his thread and hope for the best. While he never brought it up again, I did finally see that the suggested change was integrated, but it struck me that having version control for the patches would be for the best as well.
In the spirit of having the entire process open AND available, I have pushed repos for the updated original PDroid patches, worked on by pastime1971 with some help from me, and the PDroid2.0 build patches (which I call PDroidCorePatches) by CollegeDev (which are already open-source, just not available with version control AFAIK) pushed as well.
If CollegeDev or you update the build patches for 4.2, we can either use those repos or start new ones, if necessary. But I am more than willing to add read/write to both of you. Wbedard has ported the PDroidCore patches to AOSP, but I will wait and see if he wants to put up a repo first before adding a new one (or possiibly a aosp-4.1.2 branch).
My hope is that the move towards complete open-source could galvanize all of us who work on PDroid to work together instead of splitting our efforts...we'll see how that goes.
Anyway, great job! I will eventually push the entire history (gingerbread to today) but for right now only 4.1.2 is up.
Original PDroid
PdroidCore
If anyone who has been working with us on Pdroid wants push access, pm me. Anyone who wants to contribute that I don't know yet, submit a pull request and we'll get to know you.
I think having the patches be attached to the same repo as the Auto-patcher and smali patches makes sense, but I am open to suggestion.
FFU5y said:
It is GPL licensed (with additional attribution conditions)
Click to expand...
Click to collapse
dear OP,
i was under the impression that GPL2 did not allow additional obligations (like attributions) being added to the burden of the receivers of the licensed code. however, i think GPL3 made special provisions for some extra obligations in other common permissive free software licenses (manly attributions) to make them compatible with GPL3, so there are some attribution provisions in GPL3 i think.
an example of GPL2 ban on additional restrictions: GPL3 enforces further obligations on receivers, such as non-tivoization, and thus is itself incompatible with GPL2 for the previously stated reason.
could you please clarify the method you chose to extend GPL with attributions in this case? thank you!
Lanchon said:
dear OP,
i was under the impression that GPL2 did not allow additional obligations (like attributions) being added to the burden of the receivers of the licensed code. however, i think GPL3 made special provisions for some extra obligations in other common permissive free software licenses (manly attributions) to make them compatible with GPL3, so there are some attribution provisions in GPL3 i think.
an example of GPL2 ban on additional restrictions: GPL3 enforces further obligations on receivers, such as non-tivoization, and thus is itself incompatible with GPL2 for the previously stated reason.
could you please clarify the method you chose to extend GPL with attributions in this case? thank you!
Click to expand...
Click to collapse
The code is GPL3 licensed, and the additional attribution (and differentiation) requirement are under GPL3 Section 7 (b) and (c).
If there are specific contexts in which people would like to use the app that are excluded by GPL3, they are welcome to contact me about alternative licensing arrangements. Of course, as soon as others contribute GPL3-licenced code then that will get a lot more difficult, but right now that is an option.
I hope that answers your question, but if not let me know.
This is so absolutely awesome, thanks a lot FFU5y!
The filtering options for user/system apps and permission type are exactly what I needed. Further ideas would be:
search app by name
advanced filtering for a single specific permission, e.g. "start on boot"
batch operations: e.g. block network & gps location permissions for all apps
dbx4 said:
This is so absolutely awesome, thanks a lot FFU5y!
The filtering options for user/system apps and permission type are exactly what I needed. Further ideas would be:
search app by name
advanced filtering for a single specific permission, e.g. "start on boot"
batch operations: e.g. block network & gps location permissions for all apps
Click to expand...
Click to collapse
Cheers dbx - glad you're finding it useful.
These are good ideas (and indeed, I started on 'searching app by name' but de-prioritised it for release). I'll add them to my github issues list as enhancements (so they are listed somewhere centrally).
I'm not really sure at this stage how I'd go about implementing the filtering for a single specific permission, mainly because I'm not sure how to represent it in the user interface without cluttering it up.
One way may be to have a specific view for filtering by setting, which shows a list of settings, and then upon choosing a setting shows only the apps to which that setting relates (e.g. choosing 'GPS location' from the list of settings shows only those apps which have that as a valid setting - i.e. those with permission to access the GPS).
I'm afraid those features will probably take a little bit of time to develop, but hopefully you'll find the app useful in the meantime while I'm working on them.
Version 0.2.3 ALPHA has been relased:
CHANGE LOG
2012-11-25: v0.2.3 ALPHA
Changes
Added improved text for the access notifications
Added a help button for each setting with a summary of what the setting does (I know it is ugly, and I plan to fix that soon).
The application list status indicator should now work under all normal circumstances
Dialogs have been added when loading, saving etc. to avoid interactions that could cause crashes
Known bugs
When multiple apps are installed one after the other, the notification to update settings of previous installations is replaced (rather than additional icons appearing).
The app will probably crash if PDroid is not installed.
Also see my github list: https://github.com/wsot/pdroid-manager/issues
Hi, PDroid is a very important app, and I wanted to thank you for making an open source alternative with much more features.
Wish I was a dev, so I could help you more, but I will gladly test it the moment the autopatcher supports 4.2.
Sent from my GT-I9000 using xda app-developers app
Dr.69 said:
Hi, PDroid is a very important app, and I wanted to thank you for making an open source alternative with much more features.
Wish I was a dev, so I could help you more, but I will gladly test it the moment the autopatcher supports 4.2.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Cheers =)
I'm eager to give it a run on 4.2 as well, but I am aware that CollegeDev is working on a new release of the PDroid 2.0 Core and App, so I'm not going to try to port the core to 4.2 until the update is released (otherwise there may be a lot of re-working needed, and if CollegeDev is porting it already then I'd just be duplicating work).
In the meantime, I'm going to try to get some fixes and new features into PDroid Manager which can then hopefully move smoothly to the 4.2 version.
Hello, i'm using Permission pro to remove rights i don't want from program, do your program works the same way, or rights are removed by an other way ?
Also, some Gameloft games have managed to get their start at boot rights back, with every programs i used, i was never able to kick them, so this is somewhat important to know, for me, if it will fail the same way.
Don't know if it's possible to do, but people not using Jelly Beans cannot block notification from a program, amybe we could get it with PDroid manager ?
Magissia said:
Hello, i'm using Permission pro to remove rights i don't want from program, do your program works the same way, or rights are removed by an other way ?
Also, some Gameloft games have managed to get their start at boot rights back, with every programs i used, i was never able to kick them, so this is somewhat important to know, for me, if it will fail the same way.
Don't know if it's possible to do, but people not using Jelly Beans cannot block notification from a program, amybe we could get it with PDroid manager ?
Click to expand...
Click to collapse
The quick answer: PDroid and PDroid Manager do not block notifications from programs. In new version of Android, there is a feature to limit which applications can create notifications. If there are a lot of 'marketing' notifications you should report the app to Google (I think you can report it at the Play store) because they are starting to move against that kind of activity.
Anyway, continuing...
PDroid 2.0 (and PDroid Manager) work quite differently to permissions pro. First, PDroid 2.0 (which is the Android modification that PDroid Manager configures) requires a modification to be made to the ROM on the device. This allows for the Privacy Service to limit the access apps have to private information, even when they have Android permissions to access the information. The PDroid Manager App (or the alternative, PDroid 2.0 App) allows you to choose what private information is provided to what app.
So, in order to use PDroid Manager, you need:
A ROM patched to add the Privacy Servire, which you can achieve by either patching the source code yourself using the patches in the PDroid 2.0 thread and compiling the rom, or potentially by using mateorod and pastime's excellent autopatcher
PDroid Manager (or the PDroid 2.0 App) to configure
The advantages of PDroid over Permission pro is that with PDroid, the app still has the same Android permissions, but when the app requests data from the Android operating system the privacy service provides back blank or incorrect data. This means that rather than the app crashing, as often happens when its permissions are changed, it keeps running.
The main disadvantages of PDroid compared to Permission pro is that it requires changes to the Android frameworks, which means you need to be willing and able to modify your ROM in order to use PDroid. It is not 'easy', and it also means there is a delay before new Android version are supported because the patches for the framework need to be modified to support the updated framework.
I hope that helps.
Hello, thanks for your answer, on the autopatcher page, it's not clearly written if it will work on OEM's rom (but it's clearly written it won't on samsung/htc one)
I'm currently usng ASUS' stock rom and guevor's kernel, any chance to have it working ?
If the service reply false information, it's still able to block an app at boot ? to make it unable to start itself at boot ?
Magissia said:
Hello, thanks for your answer, on the autopatcher page, it's not clearly written if it will work on OEM's rom (but it's clearly written it won't on samsung/htc one)
I'm currently usng ASUS' stock rom and guevor's kernel, any chance to have it working ?
If the service reply false information, it's still able to block an app at boot ? to make it unable to start itself at boot ?
Click to expand...
Click to collapse
Autopatcher will probably not work on an OEM ROM at this stage, unfortunately. That is something mateorod has been working on, but I believe it is still a work in progress. You can give autopatcher a try nonetheless, though. If it can't patch it, it will tell you. Also, if you search around the forums for your device, you may find someone has created special patches just for that device.
If you can get the ROM modded to include PDroid, then one of the features allows you to prevent an app being notified of when the device finishes booting. For those games, that means they would not be started when the device finished booting. However, it is possible that they may use a range of other ways to make sure they start which PDroid doesn't affect.
Probably the best way to deal with these types of problem apps is to use a tool that can 'freeze' the apps, and then just 'unfreeze' them when you want to use them. If they are giving you notification bar spam, you should definitely consider reporting them at the play store, too. Notification bar spam is against Google's current policies for the Play store.
Sorry I can't give you better news - patching of already-compiled OEM ROMs is not my focus area.
Hello, i already reported gameloft for their notification ads, and a video game doesn't need to be notified of system's start. Fact are they are "super dev" in play store and i doubt google will do anything.
PDroid seems more complete than Permission Pro, to make programs unable to acces data.
So, if i understand correctly, when i refuse a right to a program, the service will give blank information instaed of letting it see the real information. Does it have a big impact on the performances ?
I wouldn't mind switching rom, but it seems that no rom is able to install and keep all the data/configuration, means you have to use the custom rom since start or you're stuck if you want to keep things.
Edit : Seems Pdroid 2 is for 4.1.2+, my device use 4.0.3, will keep this thread bookmarked and will come back once i'll have enough courage to switch rom (since ASUS won't let us get the update anyway)
Hy!
enough if I flash in recovery the my ROM's update zip?
root required ? :fingers-crossed:
hmm
it looks like it works.
Thanks.
ROM:cm10 Flinny 129.
is possible into other languages translate?
acultr said:
is possible into other languages translate?
Click to expand...
Click to collapse
It's easy. Translate this file and open a pull request or attach it here.

[APP][4.0.3+] HasItChanged?

I wrote this app mainly for fun and to explore android, but I thought I would share it here in case anyone finds it useful.
HasItChanged is intended for personal use when a website you're interested in updates irregularly, but you still want to know when it changes. Instead of firing up your browser only to find nothing has changed, let your phone do it for you!
While the app does have the ability to keep track and notify you when a site goes down, it is not intended to be a professional uptime tracking tool. Please don't use for sensitive or critical purposes.
Features
Ability to specify individual update intervals
Utilizes Android's built-in sync mechanism to reduce battery usage [This requires the Identity Permission]
Doesn't just check to see if it's up (although you certainly can); only be notified when the website changes!
Utilize HTTP content caching technologies to reduce network usage
Control specifics such as connection timeouts and network usage
Supports HTTP/HTTPS/FTP connections
No ads. Open source. Feel free to contribute!
Please submit bug reports via Github. Feature requests welcome! As this is a purely hobby project, no support is guaranteed, although I'll certainly try to do my best!
Play Store
Bug report
The app doesn't work for many websites, for example mojang.com, YouTube channels or YouTube Playlists. Every check if the website changed gives a positive result, so I keep getting notifications for those sites. I tried with smart compare on and off and also cache on and off.

Categories

Resources