Official Asus stock value is 160! But the official Asus kernel doesn't allow 160 and boots to 240 so who knows what the play store sees. My rom uses a multi dpi hack play store so doubt changhing dpinwill fix anything. 213 is not the default for sure. It is the default on the nexus 7.

If you search for wild blood it is not found in the play store list. What ROM were you on when you purchased them? Do you not keep tibu backups?

Hmm weird.. So guess it's probably a no go then... Honestly I'm not sure which device I purchased them on lol... I have several

Official Asus stock value is 160! But the official Asus kernel doesn't allow 160 and boots to 240 so who knows what the play store sees. My rom uses a multi dpi hack play store so doubt changhing dpinwill fix anything. 213 is not the default for sure. It is the default on the nexus 7.

If you search for wild blood it is not found in the play store list. What ROM were you on when you purchased them? Do you not keep tibu backups?

Could we using an app like build.prop or system tuner pro to change the dpi from 213 to 160 so as to download some games and then use them to change the dpi back to 213?

Command line prompts are not accessible to most. They are deemed old fashioned, cludgy and archaic.

Call it "chatting with the computer", doesn't that sound very modern and much more fun than silently pointing to things with the mouse?

Quote:

Originally Posted by sbdags

But for beginners its the only way for some to get a foot in the door. Surely you can see that?

When I was a beginner, I had to learn how the command line works - simply because there was no GUI. Today, the barrier for using computers is much lower, which is generally good. But for people who don't even want to learn basics about using a command line interface, there is another popular mobile OS much more suitable for them; they should not try to root Android devices and install custom ROMs. Just my opinion.

Hiding the (minimal) complexity of adb behind another layer of more complexity in a GUI only makes the whole system more complex, and if something does not work as intended, makes finding the problem even harder. I saw that already with the batch files to automate fastboot, and most people having trouble with adb on Windows seem to have driver problems, which are not solved at all by a GUI.

Anyway, feel free to disagree with me. I don't have to support that thing anyway.

Call it "chatting with the computer", doesn't that sound very modern and much more fun than silently pointing to things with the mouse?

When I was a beginner, I had to learn how the command line works - simply because there was no GUI. Today, the barrier for using computers is much lower, which is generally good. But for people who don't even want to learn basics about using a command line interface, there is another popular mobile OS much more suitable for them; they should not try to root Android devices and install custom ROMs. Just my opinion.

Hiding the (minimal) complexity of adb behind another layer of more complexity in a GUI only makes the whole system more complex, and if something does not work as intended, makes finding the problem even harder. I saw that already with the batch files to automate fastboot, and most people having trouble with adb on Windows seem to have driver problems, which are not solved at all by a GUI.

Anyway, feel free to disagree with me. I don't have to support that thing anyway.

No I agree with you 100% People are lazy, they don't want to have to learn, remember and type long syntax strings out to do stuff. So I'm all for tools that allows them to do it safely without having to struggle. Although I get your point that the only way to learn is to do and once you do it's not that difficult.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?