Why so many updates for Android apps? - Xiaomi Mi A1 Questions & Answers

Ok, first off, I DID do a search for this, and did not find any pertinent information, so please don't jump my case about using search.
I have often wondered why so many apps get so many updates from the Play Store, some getting updates 3 or 4 times in one week! Is there really that much behind the scenes development going on? Are they just changing the ads or something? Is Play Store updates broken so you get the same update multiple times? It does not seem to be just the free apps though. I have a number of paid apps that do the same thing. If any of you devs could shed some light on this, I would appreciate it. It bothers me when I see an app getting so many updates so quickly, as I wonder what is going on with it that requires those constant changes.
Regards,
--KB

KB_Thailand said:
Ok, first off, I DID do a search for this, and did not find any pertinent information, so please don't jump my case about using search.
I have often wondered why so many apps get so many updates from the Play Store, some getting updates 3 or 4 times in one week! Is there really that much behind the scenes development going on? Are they just changing the ads or something? Is Play Store updates broken so you get the same update multiple times? It does not seem to be just the free apps though. I have a number of paid apps that do the same thing. If any of you devs could shed some light on this, I would appreciate it. It bothers me when I see an app getting so many updates so quickly, as I wonder what is going on with it that requires those constant changes.
Regards,
--KB
Click to expand...
Click to collapse
In short, one of the reason are manufacturers, apps have sometimes problems and bugs with specific phones, for example App 1 works good on Xiaomi, but has bugs on Samsung, developer fix some problem for Samsung but breaks something on HTC phones, and so on, it's sometimes endless loop. And sometimes the same app can be working excellent on Samsung A, but buggy on Samsung B, or App FC when you have some other app installed, but works good if you don't have that other app for example.
Second is that there is 0 app that hasn't got some kind of bug.

Thanks Nitro. As a retired software engineer it just disturbed me that the apps seemed to be so unstable. I guess it makes sense though as they do run on a large number of different devices, with a large number of different iterations of the base software. I also would think that with the shear number of devices out there, actual testing on the various devices would be pretty hard unless you were a rich man. That is where the guidelines from Google come in I guess. You write to the guidelines and hope the manufacturers didn't mess with that portion of the base Android system. Heck of a way to make a living.
In any event, thanks again for the reply, and thanks to the devs that try to make usable apps in a chaotic system! :good:
--KB

Related

What is going on...?

Ok first and foremost this is not just another post of someone complaining, in no way am i trying to offend or criticize this new device...these are simply observations made by a previous HTC owner (MDA/Herald/Wing) me...
I understand that the open source to "create" applications is fairly new not to mention all us G1 owners (ive had mine for lil more then a month). My concern is why are we seeing such "simple" programing in applications and things tht in reality none of us would ever use? Not to mention graphics what is going on...Look i have not created any nor have taken the time to even try to create applications, and if you or someone you know has, then my hats off to you, i envy you for knowing how and taking the time to...what im saying is why do all these new applications have so many bugs and in my opinion (cause that is all it is) are sub-par...i know its not really fair to compare to any other device on the market since it is the first of its kind, but im getting a little skeptical...am i alone in this? i find myself checking the android market every hour hoping for some sign to motivate me, but nothing so far aside from the obvious winners (youtube,maps,imeem,wheather channel etc...)...ill shut up now i sincerely was not trying to stir things up, and know/knew when i purcased the G1 it was the first of its kind and would probably take time to show its full potential, i just thought there were some things google had up its sleeve that were ready...does anyone have any insight or knowledge of better things to come...?
timace said:
Ok first and foremost this is not just another post of someone complaining, in no way am i trying to offend or criticize this new device...these are simply observations made by a previous HTC owner (MDA/Herald/Wing) me...
I understand that the open source to "create" applications is fairly new not to mention all us G1 owners (ive had mine for lil more then a month). My concern is why are we seeing such "simple" programing in applications and things tht in reality none of us would ever use? Not to mention graphics what is going on...Look i have not created any nor have taken the time to even try to create applications, and if you or someone you know has, then my hats off to you, i envy you for knowing how and taking the time to...what im saying is why do all these new applications have so many bugs and in my opinion (cause that is all it is) are sub-par...i know its not really fair to compare to any other device on the market since it is the first of its kind, but im getting a little skeptical...am i alone in this? i find myself checking the android market every hour hoping for some sign to motivate me, but nothing so far aside from the obvious winners (youtube,maps,imeem,wheather channel etc...)...ill shut up now i sincerely was not trying to stir things up, and know/knew when i purcased the G1 it was the first of its kind and would probably take time to show its full potential, i just thought there were some things google had up its sleeve that were ready...does anyone have any insight or knowledge of better things to come...?
Click to expand...
Click to collapse
Personally, I find the plethora of apps encouraging, yes, some are more useful than others but the wide range of effort is fan-flippin-tastic.
MY biggest observation is that the Market place needs some severe MODERATOR intervention... the one star "i is first u goons" and "this app suks (because I am too stupid to read the intro to figure out what it is for) really really really needs to be cleaned up/out. (A perfect example is the UTC clock... it does EXACTLY what it says, true, the numbers in the display look like they are from a missile silo, but hey, it is a tribute to the UTC heritage...anyway, people bag on it because they have no idea why, what, or anything else about it... morons)
[/rant]
--M
demontefixo said:
Personally, I find the plethora of apps encouraging, yes, some are more useful than others but the wide range of effort is fan-flippin-tastic.
MY biggest observation is that the Market place needs some severe MODERATOR intervention... the one star "i is first u goons" and "this app suks (because I am too stupid to read the intro to figure out what it is for) really really really needs to be cleaned up/out. (A perfect example is the UTC clock... it does EXACTLY what it says, true, the numbers in the display look like they are from a missile silo, but hey, it is a tribute to the UTC heritage...anyway, people bag on it because they have no idea why, what, or anything else about it... morons)
[/rant]
--M
Click to expand...
Click to collapse
i agree "first" comments are riduculous, and if you dont like the application from descrption then dont install it...positive criticism is more then welcome but "this sucks" is getting on my nerves...
timace said:
Ok first and foremost this is not just another post of someone complaining, in no way am i trying to offend or criticize this new device...these are simply observations made by a previous HTC owner (MDA/Herald/Wing) me...
I understand that the open source to "create" applications is fairly new not to mention all us G1 owners (ive had mine for lil more then a month). My concern is why are we seeing such "simple" programing in applications and things tht in reality none of us would ever use? Not to mention graphics what is going on...Look i have not created any nor have taken the time to even try to create applications, and if you or someone you know has, then my hats off to you, i envy you for knowing how and taking the time to...what im saying is why do all these new applications have so many bugs and in my opinion (cause that is all it is) are sub-par...i know its not really fair to compare to any other device on the market since it is the first of its kind, but im getting a little skeptical...am i alone in this? i find myself checking the android market every hour hoping for some sign to motivate me, but nothing so far aside from the obvious winners (youtube,maps,imeem,wheather channel etc...)...ill shut up now i sincerely was not trying to stir things up, and know/knew when i purcased the G1 it was the first of its kind and would probably take time to show its full potential, i just thought there were some things google had up its sleeve that were ready...does anyone have any insight or knowledge of better things to come...?
Click to expand...
Click to collapse
i agree with you; even though i love this phone there are a lot of things i dislike about it. the only advice i can give to you is to be patient. the phone has 'officially' been out for a little under a month and there is already so much improvements to it:
- 2 updates have already been rolled out,
- we have found a Root and a way to manually update it.
- we are beginning to see system folders moved to sdcard to save space(even though the phone should have came with more memory)
apps on the market are getting better i don't if you have seen the app "bubble". bubble is a basic bubble level that uses the accelerometer to see if something is level and changes as the phone changes orientation it may seem like a simple app but it shows that Google came come out with an update that uses the accelerometer to change orientation.
- first signs of on screen keyboards like akeyui, a7email and a7sms.
all of these improvements in about 3 weeks and tons more to come idk what anybody can complain about besides hardware issues
just wait come Jan 2009 the G1 isnt going to be anything like it is today.
demontefixo said:
Personally, I find the plethora of apps encouraging, yes, some are more useful than others but the wide range of effort is fan-flippin-tastic.
MY biggest observation is that the Market place needs some severe MODERATOR intervention... the one star "i is first u goons" and "this app suks (because I am too stupid to read the intro to figure out what it is for) really really really needs to be cleaned up/out. (A perfect example is the UTC clock... it does EXACTLY what it says, true, the numbers in the display look like they are from a missile silo, but hey, it is a tribute to the UTC heritage...anyway, people bag on it because they have no idea why, what, or anything else about it... morons)
[/rant]
--M
Click to expand...
Click to collapse
yeah there need to be some serious clean up in th commenting sections, some of these comments might discourage people from developing apps for the G1, i think comments should strictly about the apps and not about being 1st or 151st, or bashing other commenters, and people definitely should not comment on an app the don't know how to use.
however developers should include directions on how to use their apps so people do not have to rely on commenting to try and figure out what it does and how it does it.
The point is the development muscle that has been put in the device is minor.I feel like the market is made by kids or teenagers that stopped uploading on youtube and are writing apps using ready made lego kits (APIs). The apps in the market are all basic stuff. There is not even a Divx player for this device available but 5 Video players using the Google provided APIs to play mp4 which only play SOME mp4 files not all.
I love the sliding, bubble and Gmail on it but I cant name too many more things I love. Not even a Navi that works properly. I really cant think of anything else I love about it. No office, word, excel, PDF, flash, divx. The SMS system is grouped together. The actual phone keyboard is beyond basic with no options. There are simply too many bugs on the phone operation itself like bluetooth etc.
Time flies google, we need apps that have more than 10 man-hours of software programming spent on it. Lets stop the growth of many timers and alarms in the market and get some real stuff out there. Microsoft has probably put in millions of development hours into WM and it was not until now that I realized this.
brooklynite said:
The point is the development muscle that has been put in the device is minor.I feel like the market is made by kids or teenagers that stopped uploading on youtube and are writing apps using ready made lego kits (APIs). The apps in the market are all basic stuff. There is not even a Divx player for this device available but 5 Video players using the Google provided APIs to play mp4 which only play SOME mp4 files not all.
I love the sliding, bubble and Gmail on it but I cant name too many more things I love. Not even a Navi that works properly. I really cant think of anything else I love about it. No office, word, excel, PDF, flash, divx. The SMS system is grouped together. The actual phone keyboard is beyond basic with no options. There are simply too many bugs on the phone operation itself like bluetooth etc.
Time flies google, we need apps that have more than 10 man-hours of software programming spent on it. Lets stop the growth of many timers and alarms in the market and get some real stuff out there. Microsoft has probably put in millions of development hours into WM and it was not until now that I realized this.
Click to expand...
Click to collapse
muscle...DiVix...kids...office...flash...basic...bugs
words that stood out and i DEFINATELY agree
as i said before patience is the key here
the reason why there aren't many good programs out right know is because they are still in development, there are some apps that won google's app contest that are not on the market because they are still under development. developers take their to try and come out with a bug free app and you criticize them for taking to long however if they rush it and get it out with SOME bugs people crucify them. how long did you think it took for divx or flash to be developed for other phones?
why do people expect a phone thats been out for under a month to have the same capabilities as phones that been out for years?
how many phone do you know had divx support right out of the box or even one month after release? i estimate that divx support will be out before the end of the year.
i agree that apps on the market are going the the hole, especially with millions of the same type of apps, c'mon how many different weather apps do we need, how many background apps is necessary. but you got to admit out of the hundreds of apps on the market there are some good ones.
I'm waiting with great anticipation on the games for the g1. Sure i want cut copy and paste, document reader, full video player, full file manager and task manager as well as others but i'm dying to play nes games and others on this phone. The market is pretty lame in the games department but hey i got pacman, solitaire, and a few others free so i'm not gonna complain. I think the apps are very promising and there are a wide variety of them. Granted none of the crucial apps are out yet but i have quite a few on g1 that i love and got em all for free!!! We just have to be patient, i knew going in i would have to be.
All the apps are free. The hardware has only been in people's hands for a few weeks (at most). A serious developer, wanting to create the exact apps we're all hoping for, needs a heck of a lot more time. The SDK was fine, but any serious developer is going to want to log a lot of hours with a physical device (or several) to finalize the product.
And they're not going to do all that, for free.
This device has huge potential, and the reason we're seeing amaturish apps is because the only people who are willing to play around with creating apps for free are mostly hobbyists who want feedback to further their skills.
I predict that once the payment system is set up for the Market, the apps you're all stomping your feet about are going to show up.
The programs we're talking about are complex, writing them and testing them is time consuming, and I assume that they're going to be larger than the apps we're seeing now. It's entirely possible that some of these apps are almost finished, but are waiting for SD card loading to be added to the functionality before they can release them. Some may even be delayed by the announcement of the virtual keyboard -- they may want to integrate that for the launch of their apps.
I think two things need to happen before we're going to see the apps we all want.
-Pay system on Android Market
-The Ability for Apps to be installed and run from the SD card.
Until those two things happen, the App Store is going to be like it is. And it's also time you guys thought about something. The apps that are "missing" were never a secret, most of the complaints I see are about things that were known well before launch, or discovered the first week people had it in hand. If you didn't read up, that's your fault. If you read up and assumed things would be taken care of within one to two months (something no one promised you) that's also your fault.
I'll predict something for you right now, in light of the economy and everything else, it'll be 6 months to a year before HALF the apps we want are available and working. Now, that's just my estimate, but if that sounds "too long" to wait, then I'd invest in another phone rather than spending the next 6 months posting complaints like "why isn't _____ done yet? And where's the ______ app?!!"
Just my 2 cents
I have already heard many apps have been developed but the developers are waiting for the pay system which has already been annoucnced and is coming 3 months after launch.
I am similar to you... give it time and you will see the best things you have ever seen. I mean look at Linux... they have some awesome apps on most linux flavors that make me dual boot into linux just to have. I think this device will be the same as this was the entire purpose.
Google is updating features all the time in the git directory and it won't be long before they fix the main issues and then the developers will be looking at new things to give us.
So far the barcode readers alone seem like such a huge advantage as I haven't seen them on mobile devices before(at least none that worked)
brooklynite said:
The point is the development muscle that has been put in the device is minor.I feel like the market is made by kids or teenagers that stopped uploading on youtube and are writing apps using ready made lego kits (APIs). The apps in the market are all basic stuff. There is not even a Divx player for this device available but 5 Video players using the Google provided APIs to play mp4 which only play SOME mp4 files not all.
I love the sliding, bubble and Gmail on it but I cant name too many more things I love. Not even a Navi that works properly. I really cant think of anything else I love about it. No office, word, excel, PDF, flash, divx. The SMS system is grouped together. The actual phone keyboard is beyond basic with no options. There are simply too many bugs on the phone operation itself like bluetooth etc.
Time flies google, we need apps that have more than 10 man-hours of software programming spent on it. Lets stop the growth of many timers and alarms in the market and get some real stuff out there. Microsoft has probably put in millions of development hours into WM and it was not until now that I realized this.
Click to expand...
Click to collapse
Well you said my answer in your own post. The device has been out less than a month. That's nowhere near enough time to make those killer apps you're talking about. To google's credit they did put in things like street view with the compass mode and there are those apps you've talked about. It takes MONTHS to do real software developement so you're going to keep seeing more and more alarms and stuff until then.
seriously, does ANYBODY give a ratsass or even use streetview?
They should have made sure all the media stuff and the email was topnotcxh.
I agree 100% with the first post! Google should have prepaired Android better. There is a lot of competition out there and I would say by what I've seen so far they are light years behind. I did not expect that with all the money in the world Google couldn't release product that was better polished. I have put my G1 back in its box and I'm back to my unlocked Tilt, what sucks is going back to the old screen and Edge but its functinality that I need. I wish they made some kind of task aplication that I can put on the screen kind of likr thr picture frame that would display my tasks for the day. I have a Motorola ROKR E2 that runs Linux and there are more useful stuff for it out there. I desagree we have to wait untill we start paying for apliications, I believe Google can afford providing us with free functional software as more and more people will be using their services.
i love my g1, but i agree with these people that google didn't do enough...and i hope they're working to fix it.
i think that their whole "leave it in the hands of developers" approach was probably a mistake. they should have made all the basic applications like they did but also gone a step further to spice up the phone. i hope that google, in the new few updates, incorporates some more stuff, like OUTLOOK SYNC (i wuld love it if they changed the google calendar sync for windows into just google sync and have it sync everything with outlook....funambol right now sucks i have like 80 of each contact!)
they also should have made a GOOD video recorder / player, and even a better music player. they're trying to beat apple at multimedia, and are failing miserably.
they should add a decent on-screen keyboard and maybe even a task manager...or make it only have like 4 open tasks in the backgroudn...because i've noticed my g1 slowing down a lot after having a few apps open.
google should add a manual update button...i'm still on RC28 because i dont feel like installing the modified rc30 or plugging it in to update. have a freaking "UPDATE" button in the system info thing or something.
i think google needs more than 3 home screens...i've already filled all of mine up. they also should have added more widgets, like the guy above me said.
SELECTING TEXT SUCKS. i have to use the trackball to select a ltter of a word...on my windows mobile i could just tap on where i wanted it to be and at least it would get me within 1 or 2 letters...if i tap on a word on the g1 nothing happens!
we need to be able to install stuff to the sd card!
i think i'm missing a lot of things but i've only had the phone for 2 days and i've noticed all that...i hope developers DO step in if google is too stupid not to add more basic functionality.
/rant
Look at it this way currently there is no way to charge for apps that are developed. This is why we are seeing nothing but apps programed by independant programers some of which are good and some of which are useless. Once companies can charge for apps then it will make sence to put money into the development of better more porfessional apps. My suggestion is to just hold off on passing judgement untill the market is finished to where people that spend money in development can recoup those losses. I do think that the market place should have been finished before launch but what can you do.
coffeboy23 said:
Look at it this way currently there is no way to charge for apps that are developed. This is why we are seeing nothing but apps programed by independant programers some of which are good and some of which are useless. Once companies can charge for apps then it will make sence to put money into the development of better more porfessional apps. My suggestion is to just hold off on passing judgement untill the market is finished to where people that spend money in development can recoup those losses. I do think that the market place should have been finished before launch but what can you do.
Click to expand...
Click to collapse
Agaqin, super lame of google.
We can get a bunch of usless wank programs, but not proepr ones, becasue they don't have the pay market ready.
Also, I think that certain things like exchange and a proper email client shoudl have been included.
And remember most people are new to development, don't know how many "this is my first try" apps I have seen. When you get that one that charges 20 bucks for the app... you will get another developer who will release it free and just ask for donations... I suggest donating whatever you can to the one that gives it free.
Henchman said:
Agaqin, super lame of google.
We can get a bunch of usless wank programs, but not proepr ones, becasue they don't have the pay market ready.
Also, I think that certain things like exchange and a proper email client shoudl have been included.
Click to expand...
Click to collapse
google isnt the one entirely in charge of the market... tmobile is the one wanting money
neoobs said:
google isnt the one entirely in charge of the market... tmobile is the one wanting money
Click to expand...
Click to collapse
No, but it was google who shoudl ahve made sure that the basics were coveredf well.
The Camera I'm sure can take greta pics, but the controls suck.
The email is severly lacking.
No streaming video.
And they shoudl ahve elarnt form the iPhoen release, that push email fro MsExcahnge should have been there fromt he getgo.
Or the should have built a BB app, just like you can get for WinMo.
No, they focused on teenagers, not professionals.
neoobs said:
google isnt the one entirely in charge of the market... tmobile is the one wanting money
Click to expand...
Click to collapse
no....google is not taking any money but is giving 30% of all apps sold to the carriers...tmobile might be the one "wanting" money but they have no control over the app store at all.

Android Security: A neglected subject (long)

First of all: I'm an OSS advocate and love the idea of open source. Don't forget that while reading this.
Some 2 month ago, I got myself a Galaxy S. It's not exactly cheap, but on the other side, it's really good hardware. This thread is not about Samsung or the Galaxy S. It's about the missing parts of android security.
We all know it from our home computers: Software sometimes has bugs. Some just annoy us, others are potentially dangerous for our beloved data. Our data sometimes gets stolen or deleted due to viruses. Viruses enter our machines by exploiting bugs that allow for code execution or priviledge escalation. To stay patched, we regularly execute our "apt-get update;apt-get dist-upgrade" or use windows update. We do this to close security holes on our systems.
In the PC world, the software and OS manufacturers release security bulletins to inform users of potentially dangerous issues. They say how to work around them or provide a patch.
How do we stay informed about issues and keep our Android devices updated?
Here's what Google says:
We will publicly announce security bugs when the fixes are available via postings to the android-security-announce group on Google Groups.
Click to expand...
Click to collapse
Source: http://developer.android.com/guide/appendix/faq/security.html#informed
OK, that particular group is empty (except for a welcome post). Maybe there are no bugs in Android. Go check yourself and google a bit - they do exist.
"So why doesn't Google tell us?", you ask. I don't know. What I know is that the various components of Android (WebKit, kernel, ...) do have bugs. There's nothing wrong with that BTW, software is made by people - and people make mistakes and write buggy code all the time. Just read the changelogs or release notes.
"Wait", I head you say, "there are no changelogs or release notes for Android releases".
Oh - so let's sum up what we need to stay informed about security issues, bugs and workarounds:
* Security bulletins and
* Patches or Workaround information
What of these do we have? Right, nada, zilch, rien.
I'll leave it up to you to decide if that's good common practise.
"But why is this important anyway", you ask.
Well, remember my example above. You visit a website and suddenly find all your stored passwords floating around on the internet. Don't tell me that's not possible, there was a WebKit bug in 2.2 that did just that. Another scenario would be a drive-by download that breaks out of the sandbox and makes expensive phone calls. Or orders subscriptions for monthly new ringtones, raising your bill by orders of magnitute. Or shares your music on illegal download portals (shh, don't tell the RIAA that this is remotely possible).
The bug is probably fixed in 2.2.1 - but without changelogs we can't be sure.
But that's not all - there's a second problem. Not only are we unaware of security issues, we also don't have automated update mechanisms.
We only receive updates when our phone's manufacturers release new firmware. Sadly, not all manufacturers support their phones in the long run.
In the PC world, most Distros have a central package management - that Google forgot to implement in Android. Agreed, some phones can receive OTA updates, but that depends on the carrier. And because of the differences in Android versions it's not possible to have a central patch management either. So we do not know if our Android devices might have security issues. We also have no easy way to patch them.
Perhaps you knew this before, then I apologize for taking your time.
What do YOU - the computer literate and security aware XDA users - think about this? Do you think that's a problem? Or would you rather say that these are minor problems?
Very intresting, thanks! The update problem should be fixed with the next release, no more custom UIs and mods from phone manufacturers,at least google said that
Sent from my Nexus One using XDA App
Excellent post and quite agree with you. The other significant problem looming is the granularity (or rather, lack thereof) in app permissions which can cause problems you describe without bugs and exploits. I install an app that does something interesting with contacts and also has internet access to display ads. How do I know that my contacts are not encrypted, so making sniffing useless, and beamed back to mummy? Nothing other than blind trust!
I love Android but it's an accident waiting to happen unless the kind of changes you advocate are implemented and granularity of permissions significantly increased. I don't like much about Apple but their walled garden app store is something they did get right although IMHO, they also abuse that power to stifle competition. Bring out the feds!
simonta said:
The other significant problem looming is the granularity (or rather, lack thereof) in app permissions [...]
How do I know that my contacts are not encrypted, so making sniffing useless, and beamed back to mummy? Nothing other than blind trust!
Click to expand...
Click to collapse
I agree, although I'm not sure that less experienced users might have difficulties with such options.
simonta said:
I love Android but it's an accident waiting to happen
Click to expand...
Click to collapse
Sad but true. I'm just curious what Google will do when the first problems arise and the first users will have groundshaking bills.
If that happens to just a few users, it'll get a kind media coverage Google surely won't like.
I've seen quite a few android exploits posted on bugtraq over the years. It's a high-volume email list, but with some filtering of stuff you don't care about, it becomes manageable. It's been around forever and is a good resource if you want the latest security news on just about anything computer related.
http://www.securityfocus.com/archive/1/description
People are bashing a lot about the Android security model but the truth is you can never have 100% protection with ANY solution.
Apple is not allowing any app in their store. Fine. but mostly they are only filtering out apps that crash, violate some rules or they just don't like them or whatever. but they can never tell what an app is really doing. Therefore they would neeed to reverse-engineer every app they get etc. That's just impossible considering the amount of apps....
Speaking again of Android. I think the permission model is not bad. I mean, no other OS got such detailed description about what an app can do or not. But unfortunately it can only filter out very conspicuous apps, i.e. a Reversi game asking for your location and internet access. But then you never know... if the app is using ads it requires location and internet access, right? so what can you do?
RAMMANN said:
Apple is not allowing any app in their store. Fine. but mostly they are only filtering out apps that crash, violate some rules or they just don't like them or whatever. but they can never tell what an app is really doing. Therefore they would neeed to reverse-engineer every app they get etc. That's just impossible considering the amount of apps....
Click to expand...
Click to collapse
Not really, they do blackbox testing and let the apps run on emulated devices they then check if the app "behaves" as desired...
Of course you can't get 100% security and I don't think that's what we're saying, but there is a lot you can do.
Take for example internet access which is the biggest worry I have. The only reason most apps request internet access is to support ads. I now have a choice to make, don't use the app or trust it. That simple, no other choice.
If I installed an app that serves ads but did not have internet access, then the only way that app can get information off my phone is to use exploits and I'm a lot more comfortable knowing that some miscreant needs to understand that than the current situation where some script kiddy can hoover up my contacts.
However, if internet access and ad serving were separate permissions, you could in one hit address, taking a wild guess, 90% of the risk from the wild west that is Marketplace. With a bit more design and work, it would be possible to get the risk down to manageable and acceptable levels (at least for me).
I absolutely agree with you on Apple, one of the main reasons that I chose a Desire instead of an iPhone, but the Android approach is too far the other way IMHO.
Just my tuppence, in a hopeless cause of imagining someone at Google paying attention and thinking you know what, it is an accident waiting to happen.
marty1976 said:
Not really, they do blackbox testing and let the apps run on emulated devices they then check if the app "behaves" as desired...
Click to expand...
Click to collapse
Well, so why did a tethering app once make it into the appstore?
Also I think there are many possibilities for an app to behave normal, and just start some bad activity after some time. Wait a couple months until the app is spread around and then bang. Or remotely launch some action initiated through push notifications etc.
If there is interest, then there is always a way....
simonta said:
However, if internet access and ad serving were separate permissions, you could in one hit address, taking a wild guess, 90% of the risk from the wild west that is Marketplace. With a bit more design and work, it would be possible to get the risk down to manageable and acceptable levels (at least for me).
Click to expand...
Click to collapse
I agree that a seperate permission for ads would be a good thing.
But there are still many apps which need your location, contacts, internet access.... all the social media things nowadays. And this is where the whole thing will be going to so I think in the future it will be even harder to differenciate.
Getting back on topic: I just read that Windows 7 Phone will get updates and patches like desktop windows. That means patchday once a month plus when urgency is high...
simonta said:
However, if internet access and ad serving were separate permissions, you could in one hit address, taking a wild guess, 90% of the risk from the wild west that is Marketplace. With a bit more design and work, it would be possible to get the risk down to manageable and acceptable levels (at least for me).
Click to expand...
Click to collapse
But, how do you distinguish them? Today, (as a developer) I can use any ad-provider I want. In order to distinguish ads from general internet access, the OS would need one of:
A Google-defined ad interface, which stifles "creativity" in ad design. Developers would simply ignore it and do what they do now as soon as their preferred ad-provider didn't want to support the "official" ad system or provided some improvement by doing so.
An OS update to support every new ad-provider (yuck^2).
Every ad-provider would have to go through a Google whitelist that was looked up on the fly (increased traffic, and all ads are now "visible" to Google whether Google is involved in the transaction or not). This would also make ad-blocking apps harder to implement since Google's whitelisting API might not behave if the whitelist was unavailable. On the upside, it would make ad-blocking in custom ROMs be trivial.
Even if Google did one of these things, it still wouldn't provide any real increase in privacy or security. The "ad service" would still need to deliver a payload from the app to the service (in order to select ads) and another from the service to the app (the ad content). Such a mechanism could be trivially exploited to do anything that simple HTTP access could provide.
http://code.google.com/p/android/issues/list
issues submitted are reviewed by google employed techs... they tell you if you messed up and caused the issue or if the issue will be fixed in a future release or whatever info they find.
probably not the best way to handle it but its better then nothing.
twztdwyz said:
http://code.google.com/p/android/issues/list
Click to expand...
Click to collapse
Knew that bug tracker, but the free tagging aka labels isn't the best idea IMHO.
You can't search for a specific release, for example...
twztdwyz said:
probably not the best way to handle it but its better then nothing.
Click to expand...
Click to collapse
Ack, but I think Google can do _much_ better...
Two more things to have in mind:
1. I doubt that many Android users bother much about what permissions they give to an app.
2. Using Google to sync your contacts and calendar (and who knows what else), is a bad, bad idea.

Annoying Market Problem

Just wondering if anyone knows details on how market listings work. I know there are some apps that show or not to certain phones, but is that just a version issue, a special exception google makes?
At any rate, it's moot, because if google has a solution, they aren't making it very clear to lots of people.
Anyway, the problem:
As android ages, the phones age, and the apps mature. There are lots of apps that won't adequately run on older phones, but as far as I can tell, the only recourse devs have is to put a note in the description, which stops no one from actually downloading it, then clogging the reviews with 1 star "does not work on the ___" reviews.
While this was always a problem, now that we've reached the point in time where this is starting to happen to Droid 1 users, it's less an annoyance, and more a serious issue. Ratings almost mean nothing on those apps, and it's hard to use the reviews to see if there are actually any real issues.
(There are 10 billion droid users, and because it was true for quite a while they seem particularly locked in to the "I have one of the better phones out there" mentality )
Ok, rant over. Not sure anyone else even notices this.
Also, I'm not sure the solution is to restrict access, but an official way to list the phones that work or don't work needs to be in place, and then maybe another dev option to still allow access*
Then, if your phone isn't compatible, but the dev okays downloading anyway, you are given an extra screen to dismiss, explaining the app probably wont work for you, and you aren't allowed to leave reviews.
*Not all phones are equal, a stock phone, and a tricked out custom kerneled OC'd version, are very different, so a user might opt to give it a whirl anyway.
I have several apps on the market. In the manifest for the app you declare the minimum version of Android required for the app, and it's my understanding that phones that do not have at least that version of Android will not see the app.
Now, just because an app doesn't work on one person's phone, and they write a nasty review saying "doesn't work on the Epic!" doesn't actually mean that it doesn't work on the Epic, it just means that one person couldn't get it to work. Also, the developer may have made some hardcoding choices (like directories, etc.) that are not universal, and that may lead to incompatibilities that were un-anticipated. But, other than version of Android, I'm not sure what else is available to a developer to restrict access.
Yeah, I figured you could set the version. It's too bad there's no way to control it a bit finer.
I also realize that it's entirely possible someone is just being an idiot, but the fact remains we're past the days where you could necessarily infer anything about the phones from the version, or NEED the latest API version to do something useful/cool.
There are apps that legitimately don't run on some phones, and I feel like google needs to offer an official solution, rather than rely on dev comments that no one reads.
Obviously there are lots of ways to fake what your phone is, and whatnot, so nothing is going to be perfect, but there needs to be some way to officially denote "This app only requires 2.2, but your phone can't be one that shipped with Cupcake"
Edit: perhaps an easier approach is to have a market setting that only factors ratings/reviews of people that have the same phone.
I also don't mean to sound like I install every 5 star app, and wont even think about installing a 3 star app, no matter what I've heard. I've just noticed this in apps I was installing for one reason or another, and felt bad for the devs. It also gives a little less incentive to provide new/cool things for those of us with better phones.
I also suppose there's no "official" guidelines on what these stars are supposed to mean, but to me 1 starring an ap that says "this won't work for you" when it doesn't work for you is like telling people your dentist sucks because he wouldn't change your oil or make you a burger.
Hey guys, remember when the carriers blocked wireless tethering apps from the market for 'their phones'? I don't believe they ever REMOVED the apps from the market, just tagged them in such a way that they are not visible to any of the phones they provide service for. Just a thought, maybe devs could do the same kind of 'blacklisting' based on model number...
Sent from my pocket rocket

[Tools] Protecting and other tools to consider for your app.

I have gotten to the point in my project where I can actually see an end. I am sure there is a lot more left to do to wrap up my game, but I wanted to start thinking about the end game for this application(game).
Which brings me here, I was curious what tools/library's/methods indie dev's are using, and your reports on them. Hoping this section will help me decide what to include in my code, and help others too.
I've compiled a very short list. None of which has been tested personally by me. I will update with other people's great ideas. I am sure I have missed quite a few things,
Protecting your App
Obfuscate your code
Helps stop pirating to an extent, pretty easy to implement if articles are anything to go by.
Example:
http://developer.android.com/guide/developing/tools/proguard.html
License Verification Library
Also helps stop pirating, lets you refund people and be reasonably assured they aren't still using the product.
Example:
http://developer.android.com/guide/publishing/licensing.html (Android Licensing Library)
Secure Network communications
Needed if you are handling sensitive data in your app. Probably should be included anyways
Misc
Stat Tracking
Probably your number one way to get feedback from people actually using your app. Want to know if it was worth putting in a pause button that took 3 weeks to code? Record how many people are using it!
Examples:
http://www.flurry.com/ (Flurry)
http://code.google.com/mobile/analytics/docs/android/ (Google Analytics)
SaveToSD
I have not looked into this yet, but if comments on apps/games are anything to go by, this is requested quite often.
Here's another:
Crash reporting
I wouldn't rely on Android Market for crash reports because tools like BugSense and ACRA do a much better job. Personally I use BugSense because I prefer the UI but supposedly ACRA collects more data. If I wasn't using it I would never have known my app was crashing on older HTC models because Android Market just doesn't include that kind of info.
I'm just starting to put these in my app, and BugSense seems almost too good to be true. I'm in the process of testing it now, should help a lot in the coming months. Thanks.

[Q] Do you lose anything by rooting?

I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
DroidBois said:
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
SacGuru said:
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Rirere said:
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Click to expand...
Click to collapse
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Rirere said:
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Click to expand...
Click to collapse
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Click to expand...
Click to collapse
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Edit
SacGuru said:
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment).
Click to expand...
Click to collapse
I think we're reading the comment a little differently. This is why I brought up what I did.
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
Click to expand...
Click to collapse
Based on the questions being asked, I think it's reasonable to assume OP doesn't know anything about rooting or ROMs, so I'm being a little more liberal in looking at this comment than I would be otherwise. As such, I'd rather err on giving them information a little outside the original scope than too little.
Rirere said:
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Click to expand...
Click to collapse
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment). Somehow your answer seemed pretty similar to mine ('just about everything would be fine'), so I just wondered why you had to mention to me problems with apps like the google wallet which are easily fixed.
By now, I am sure both of us understand what the other is talking about. Also, the op has enough info to take a decision on his own. My only qualm is that the inclusion of some seemingly complex terminology might turn him off rooting his device
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
DroidBois said:
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
Click to expand...
Click to collapse
I've not had any problems with Google Play services and root, although most of my books are sideloaded after ripping DRM off of Amazon purchases (I don't really believe in the idea of a "perpetual lease"). As someone who has spent time working on that "employer junk" for corporate use, it may annoy the living **** out of you as a rooted user, but from a corporate standpoint it's actually pretty damn important.
Now, as far as MTP goes, don't quote me on this, but I remember seeing a setting in DriveDroid a while back (it's an app that lets you mount an ISO on your computer by connecting your device) that would let you change your USB connection mode to something other than MTP/PTP. I dont' remember the acronym, unfortunately, but it was a lot more in line with the way a "standard" USB device would connect (with the attendant issues of not using FUSE).

Categories

Resources