text:
Persistently or aggressively enabling Battery Saver
I love the Battery Saver feature. When I'm travelling or in other situations where reliable communication is more important than user experience, I want to always have it enabled, sometimes for days at a time.
However, Android automatically turns it off after the phone has been charged, requiring me to remember to go in and re-enable it after unplugging my phone. I occasionally forget.
Is there any way (including via third-party apps, excluding via rooting or jailbreaking the device) for me to automatically or persistently enable the Battery Saver, aside from the system's built-in options to enable it at 15% or 5% charge remaining? Alternatively, is there a way to leave it on indefinitely, or a way to have it automatically activate earlier (such as at 50% charge), or a way to activate it based on a schedule?
If there's no user-accessible way to do this yet, I would also be interested in knowing if there are any mechanisms in the operating system (URL schemes, framework APIs, relevant permission settings) that could potentially be used to control Battery Saver.

Corresponding question for iOS (I use both), if anybody is curious.

Quick thought: check our automation tag-wiki. One of those apps might be capable of it. My first check would be if Tasker can do that. The trigger is clear (when you disconnect the charger). Just not sure whether there's a plugin to deal with the battery saver.

@izzy: Yes, thanks. When I wrote earlier comment ( now deleted), this feature wasn't there  .Set myself a reminder on the app to check possibility and it reminded me today !

@beeshyams, nice workaround but as Izzy had suggested, with Tasker you could define the specific battery saving features  (e.g turning off gps, dimming light, disabling vibration etc) as a task then the profiles as battery level and disconnection from charger

@xavier_fakerat: me no Tasker :). Found it difficult to learn and switched to Macrodroid every since. I haven't yet needed to look for alternatives. You could add an alternative using Tasker, if it works for non rooted devices

@beeshyams, nowadays its not as tough as it was on first day of using it. Made use of online tutorials, now I realize the power locked inside Tasker and made very intersting projects and apps too with tasker. The useguide its pretty easy to learn trust me. One day you will see. :). However macrodroid is very user friendly and very time saving so its a big nod !

automation is the preferred option. Many apps are available. I prefer using MacroDroid , since it is free (upto 5 macros) and easy to learn.
Macrodroid along with other applications like Wakelock Detector have made this possible for non rooted device using adb to grant WRITE_SECURE_SETTINGS permission to the app
Following actions are possible (quoting developer's post in the forums, accessible from within the app (10/01/17)

Battery Saver
Location Mode
NFC Enable/Disable

You need to set up adb on your laptop
Once you have a working adb connection, you need to run the following command from the command line/terminal on your computer:
adb shell pm grant com.arlosoft.macrodroid android.permission.WRITE_SECURE_SETTINGS

Your macro would look like this
Macro : Toggle Battery Saver (name of macro as example)
Trigger: Empty Trigger
Action: Battery Saver  → Toggle
Constraints: Leave blank
Once you save the macro, go to widget drawer of Macrodroid and drag the shortcut widget to your home screen, and assign to the widget the macro you have created. Press  widget to toggle Battery Saver manually
Coming to your other requirement of activating Battery Saver at user defined percentage or on full charge, create another macro
Macro :  Battery Saver on full charge or when I want (name of macro as example)
Trigger:

Battery Level → increases to 100 % ( full charge )

Battery Level → decreases to 50 % ( user defined limit )

Action: Battery Saver → on
Constraints: Leave blank
My device is rooted, so can't verify adb command but from user response it works and I had used similar command for Wake Lock Detector when my device was not rooted

In the second macro, you could add trigger of Power disconnected also if you wish.  Triggers work in logical OR. Though with the on demand toggle of first macro and controlled activation in second macro, one is pretty much covered


text:
Nexus 7: does ruining the bootloader hard-brick the device? Or is there still a chance to recover?
So, I've got a Nexus 7 and would like to start expirementing with images, etc (primary goal being installing Ubuntu in multiboot with Android, probably loading from a flash drive over an OTG cable).
My main concern (and hence the question) is:
I've heard, that rooting, unlocking the bootloader and flashing ROMs involve some dangeorus operations (like "fastboot erase boot loader") that can render the Nexus 7 unbootable if something goes wrong (i.e. the bootloader ends up in a messed state or erased).
Is there always a strong guarantee (not "99 out of 100, I'd say, if you're lucky") I can get the Nexus 7 to boot an OS with software-only means (i.e. USB cable, PC, and my hands pressing the hardware buttons on the tablet) if the above-described scenario takes place (i.e. the bootloader is ruined and the device refuses to boot)?
I've discovered that there exist different opinions on that matter, with some (obviously quite experienced) people telling one should not really worry about possible problems during image flashing and alike operations, and still others seem to struggle with what appears to be a Nexus 7 hard-bricked after an unsuccessful flash attempt.
For example:

This thread is a story of several Nexus 7 devices (hard) bricked with essentially a wrong sequence of fastboot (or alike) commands.
This fresh thread bears an example of "a knowldgeble guy" telling everything can be fixed.

Please note: this question is specifically about Nexus 7, and not about unbricking in general!

This is more likely to get vote closed as its not a constructive question eliciting arguments from both sides of the camp, which is ... off-topic ... unless you edit the question in such a way you will get a definitive answer! And a question in relation to bricking has been answered before! this and this, and here

BTW, the most reliable way of killing the device, this was true for Samsung using download mode, have the battery at < 5%, flash a ROM with Kies (known for bricking) or fastboot, either, two scenarios, battery goes flat during download of ROM flashing, or pull the cable during flashing, good luck with that! :) Then its JTAG time baby!! :)

@t0mm13b - but still recoverable.

@RyanConrad recoverable? You mean via JTAG, which is outside of the common average Joe user?, if yes, then yes its recoverable, but comes with a cost!

@t0mm13b The reason the both sides are even mentioned is that there's only one answer (to a perfectly reasonable, and vital -- at least for the devices themselves, if not the owners) question, hence the question format, as there are quite different opinions on the topic.

"Not a real question?" Really, guys? :)

OP: If you notice how wildly varying each and everyone's opinions are within the comments/answer, its too broad and bordering on rhetorical question.. hence "Not a real question"

@t0mm13b the fact that the answers vary does not make the question too broad, as it already quite precise.

Sorry OP, you've edited the question a few times, and the initial question was too broad then deleted bits out of it each time... it shows and telling thats the case.

@t0mm13b I've edited the question for the wording to better match the site's rules as you guys see them, but the essence of the question and 95+% of the wording is the same; besides I deleted things only once -- per your request not to ask for a specific ("Yes"/"No") answer fromat, not multiple times :)

If you can get the device to boot to fastboot then you can "fix" a brick.
I have "soft bricked" my devices many times.
Samsung has "Download Mode", basically their version of fastboot. If you have an image that you can flash, you can recover. The same goes for the Nexus 7. If you have an image, which google provides because they are "developer" devices (as well as consumer).
The term "brick" is used very loosely and doesn't mean what it meant back in the WinMo days. When you bricked your WinMo phone it was as useful as a paperweight.
The only true bricks I have ever seen is when something fails in the hardware. Anything else that I have seen there is still a way to get to recovery, fastboot, download mode, etc. If you can get in to any of those you are golden.

Heh! Still have that Dell Axim v51 with WinMob 6.5, but never powered it on, and was very dicey in flashing a newer WinMob ROM on it (Originally WinMob 6.0), far too dicey IIRC, it would fail if the big SDCard had a dodgy filesystem on it! :D

Thanks, but what about specifically doing what the guys from one of my links did: "fastboot erase boot; ..."? Those who did it have perfect access to the stock images, but still are out of luck (due to the state of their devices -- no boot code, as I get it, and the lack of special tools (i.e. nvram) support for Nexus 7, unlike for example ASUS TF101).

In short, it is still perfectly possible  (with a wrong sequence of actions and commands, but not physically damaging the device in any way) to make oneself not able to get to fastboot and thus hard-brick Nexus 7, right?

@mlvljr: unless it involves hardware failures like the driver instructing to put excessive voltages AND the hardware protection failed, I don't know of any way to permanently brick a device such that it cannot be recovered by someone with the right knowledge with the right tools. Many people gives up too early because they cannot find or didn't understand the fixing instruction or that they think the fix is not worth the effort. Many people draws a line that if it requires JTAG to fix, then it's hard bricked because it's not worth it to get the tools to fix it.

@LieRyan Ok, precisely: if one issues fastboot erase bootloader and then reboots, how can he make Nexus 7 boot whatever OS/image at all without JTAG (and alike means)? (note: there's no known way currently to use nvflash to flash a bootloader to Nexus 7 gone to APX mode, or smth like that (and thus essentially hard-bricked)).

@mlvljr If you wipe the bootloader from the storage and then wipe it from RAM with a reboot, you will need JTAG / a jig to reload the bootloader.

@MatthewRead Ok, thanks, but google is almost silent on doing things this way with Nexus 7, so it looks like something one is not likely to succed with at home :)

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/

sort: votes


text:
Rooting Micromax A87 to make it faster
What is the best way to root my Micromax A87?
My phone RAM shows only 160MB, but I only access about 120MB.
I want my phone to run faster.
Or is there any common method for rooting my phone.
Kindly help me.

Just by rooting you will not make your phone run faster. You may have to do a lot like throttle CPU speed, manage memory etc to achieve it. Of course, for all these you have to root your phone.

I added a link to your question on our rooting index. You might want to have a look over there, maybe one of the described "general methods" applies to your device. If you succeeded, don't forget to update that fact here -- you might even answer your own question, describing the steps involved, if nobody else did that here ;)

Just realized now that Micromax devices are already rooted! Yep, this is true at least for Micromax Funbook Tablet and Micromax A110 phone. Install and run Root Checker which will reveal whether your device is already rooted.

@Narayanan I have checked but my Micromax A87 not rooted.

A XDA thread speaks about rooting MicroMax A87 Ninja which seems to be quite easy and broken into following easy steps:

Preparation of computer which includes downloading JDK, SDK, ADB driver and One click tool to root.
Connect the phone and run the root tool.

I am skipping on rest of the details as the XDA thread enumerates its details.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/


text:
Battery draining fast because of Android System
I'm on a HTC Droid DNA with 4.4.2, not rooted. My battery is going down really fast. When I look in power settings it shows that the main offender is Android System with 92% of power usage. I know that android system is a collection of apps, so how do I figure out which ones are doing this?
It's only been bad like this for the last few weeks. Before that I usually had no problem making it through the day.
I'm hoping there is a way to find the culprit without having to guess.
Since it may be more than one sub system at fault, and since there isn't an easy way to determine battery usage outside of controlled conditions, I don't want to have to shut off a system, wait a day to see if it seems like things have gotten better, and then move on to the next one, hoping to divine the correct sequence by chance, while taking normal usage into account.
I'd try Better Battery Stats, but I don't think it will work right since I'm not rooted.

turn off the location and under 'Location' in the Settings you can use 'Power savings Mode' for the GPS, and also turn off the Google Reporting and Location..

@Lucky I can do that, but when I go into location settings it shows power usage for recent location requests. I have Google App 1%, Google Services 9%, and HTC Services 1%. I'm sure going into power saving mode will help, but I am wondering if there is a way to pinpoint the real problem without just guessing.

Disabling some system apps can help your cause..disable google+ photos backup and try to disable some system apps(bloatware)..and disable app data sync in background

Unfortunately, the only way to jurasticly improve your battery life is by getting a new, more efficient phone. However, there are definitely compromises you can take to make it last longer.
One of the main killers is using 4G mobile data. Hence why turning on aeroplane mode uses like 3% an hour, so switch over to 3G when not needed, or turn off mobile data when connected to wifi (if you haven't already enabled in developer settings).
Another is location. Turn it off because chances are you won't need it most of the time.
Thirdly brightness ( obviously ). Huge killer. To see if this is the case, go into settings > Battery > 3 Dots top left > Battery Usage > Show full usage. You can then see in more detail what's draining the battery.
Another big consumer is Instagram, Snapchat. Try switching over to apps like Messenger lite or Facebook lite when possible. This uses far less mobile data and battery.
Use dark mode. Helps massively. Trust me.
Again if you're in need to message people, try use SMS if you already don't.
Or bring a powerpack, but we all know that's effort.

Thankfully I upgraded from that phone several years ago, but thanks for the answer. Hopefully it'll help someone else with the same problem.

mine had the same problem too. just turn off any connections. turn on airplane mode, disable location services, wifi, bluetooth, all kind of those. Reset your phone and let it be idle for a couple minutes and things should get back to normal.

What's the point in toggling the rest of the stuff if you are  ultimately going to reset the device? Makes me wonder what you meant by "Reset"?

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Android Marshmallow does not detect an SD card formatted as internal when inserting it
I have an el cheapo burner smartphone I bought due to my previous phone getting stolen, running Android 6.0. I formatted an external SD card for use as internal, and proceeded to spend the entire night downloading about 1 GB worth of apps and migrating them to the SD card. Then I rebooted my phone, and ran into a boot loop. To break it I started my phone without the SD card. It started properly, but now it won't detect my SD card when I insert it. Google didn't turn up any meaningful results for my issue. If I tell Android to forget that card, I'm going to have to spend another 4 hours downloading apps.
Is there any way I can get Android to manually try to mount the SD card again?

If it lost its encryption key (or scrambled it), chances are zero. Apart from that: Your title says "Nougat", but description and tags say "Marshmallow"; which one is it?

The same thing happened before the boot loop happened and I fixed it by just restarting the phone. I'm not sure if it's a problem with Android or with my phone's hardware, but it seems to only detect my SD card on system boot. And when my phone fails to start with the card inserted, that's where I'm in a pickle.

I've never used adoptable-storage. But considering it means the card is used as internal-storage, it makes absolutely sense it might have to be mounted during boot (and not after the system is fully up and running). // No further ideas, so someone else has to pick up here.


text:
Xiaomi screen turns black when under the sun
I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.

Maybe a 3rd party app is doing this? Try booting into safe mode and seeing if same happens.
You can also cover the camera, but that is a very temporary solution.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Can't root Galaxy 5830i
A year ago I bought a Galaxy ACE GT-5830i which came with Gingerbread 2.3.6, recently I wanted to root it, I tried following the instructions in Root,Unroot,CWM,and how to Flash Galaxy Ace S5830i, without success.
I wiped cache, Dalvik cache, rooted again, again and again but did not work.
After the root process I found the Superuser icon on the launcher, I checked for root and even tried to use link2sd and nothing. I tried to update the superuser app from Google play and ... nothing. How to root this device?

I tried to Root my Samsung galaxy s5830i. I followed the instruction on the xda developers and successfully rooted my S5830i without any problem and it works!.
Try this at your own risk.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=1552792
Using SD card as Internal memory:
http://forum.xda-developers.com/showthread.php?t=2142844

If you see the superuser icon then your phone is rooted. See this post to know what to do after root:I've rooted my phone.  Now what?  What do I gain from rooting?


text:
Unable to update Nexus 7 2012 32gb from 4.2.1 to 4.3
I bought my google Nexus 7 2012 32gb wifi only today. It has stock 4.2.1 and it is showing that an update to 4.3 is available but whenever i go there it always states that waiting to download-172.1MB.
I tried to restart it and see if it picks up the download but no use, its in the same way. Please can any one help me, i dont want to Root it or anything.

Check the WiFi connection you connected it to if it's working properly.
Go to settings>Apps>All>Google Services framework
and clear the data. Restart your Nexus 7 and see if the update downloads without hitch.

did that its the same.... :( thank you though

it happens to offer an option for search for updates and then after the moment it finds an update it immediately goes to the waiting for download.


text:
Keeping important apps alive even on overheat
I recently updated my Samsung Galaxy S4, and it came with some new features and also some new problems. Since the new update I have been getting warnings on my phone telling me it is overheating. The phone also has the ability to kill apps that are using a lot of processing power in order to get the phone to cool down. This has proven to be not only inconvenient, but actually dangerous. On several occasions the app that was closed (which, in truth, likely contributed to its overheating) was Waze. This usually happens on long trips, while i'm going 60mph, forcing me to pull over on the side of a highway just to let my phone cool down so that I can open the app again. I have not gotten into an auto accident yet, but I would much rather not be in that situation to being with. For others, there can be an even greater danger in just getting lost.
Is there a way to put certain apps, such as Waze, or any other navigation app, on a system whitelist so that they don't get shut down mid-use, potentially creating an extremely dangerous situation?

I don't know if this will work in your situation (and I can't test it myself) as in your situation it seems the killing of processes is done for safety reasons and not just to free up memory but it could be worth a try.
The app is called MinFreeManager (requires root) and there is a good guide here. Taken from the link to the guide, here is an overview of what the app will do;
ActivityManagerService.java looks at the 'importance' of running processes; foreground apps, services, content providers etc, and prioritises them for close order in an oom (out of memory) situation. Each process is assigned an oom_adj value. The lower the value, the less likely Android is to close the app when it starts to run out of memory.
These values are managed by Android at runtime so a processes oom value can and will change as it changes state, from foreground, to background to idle etc.
The app can adjust a processes oom_adj values to your own custom values so you can try and manipulate which apps Android will close first and at what stage of low memory on the device.
Like I said, this is just a very basic overview. Follow the link to the guide and you will find all the information you need to give it a go (Could go on for pages if I tried to explain in full detail).

I was hoping for something that didn't require root, but I guess if there is no option like that which comes stock, it has to be rooted.

I do not think it is the app the is using processing power and causing the phone to overheat. The most likely contributer to heat on the phone is the enabling of data, bluetooth and gps. These services require constant processing and 'pings' to maintain connectivity.
Waze and other gps based applications, use both data and location information, and at 60mph, they will be using even more of these, as the location is changing constantly and they need to refresh their maps and update their gps co-ordinates. If you are using a newer version of android (kitkat), you can change the level of GPS accuracy - device only should be fine for Waze, like so:
If your on an older android version (jellybean or below), you can play around with the settings, but I am not sure how that will affect battery. The settings look like this:

Obviously, you should try and remove all other services that are using battery, if possible, turn off bluetooth, data sync, lower display brightness, try not to constant charge the battery (this causes heat, you might only want to charge when battery drops below 15% and then take it off after 15 minutes) and so on. If all else fails, I would try and switch away from Waze. I suspect due to its social nature, it may be using the data connection for more than just sending map data. There are other mapping apps that can cache maps - therefore not requiring an active data connection - a huge battery saver!
If all this fails - I would suggest going to the manufacturer and ask for a new phone, as your battery or phone may be at fault. I use the maps on my phone (nexus 5), but other than slight heating (warm) on long journies - my phone does not shut down google maps or waze.


text:
Go Sms Pro: "Too many unsent multimedia messages" error
Every time I try to send a Multimedia message using Go Sms Pro, I get a
toast message saying: "Can't send message right now. There are too many unsent multimedia messages"

This doesn't happen when I send something through gomms (which is really only good for sending to other people with smartphones), and it doesn't happen when I use any other sms/mms client (like handcent or the default sms client). It only happens when trying to send an MMS message with Go SMS pro.
How can I get this to work? I would have thought that if this was a global bug issue, that it would have been fixed by now, so I am guessing that there is something I need to set/reset. What do I do to fix this?

I figured it out myself. Here's how I fixed it:
As it turns out, the message that says "Too many unsent multimedia messages" actually means that there are too many unset multimedia messages (who would have thought it!).
I went into the stock message client (the one that came with the phone), clicked the menu button, and selected the "unsent" menu tab. Then I clicked the menu button again, and selected the "delete" tab. Then I just deleted all of the unsent messages.
Now it works fine. Not sure why there was a limit on how many unsent messages there could be, and I'm still not sure why it worked with the stock client, and handcent, but not go sms, but, now it works!

This has happened to me at least once before. Very annoying. In my case I had to check every thread, and scroll up to look for failed mms messages in the thread(red !). Once one fails, apparently nothing else except regular txt will go through until the offender is deleted for some reason. I think I narrowed it down to a message I sent from my garage. With the doors shut and if I'm in the back, I get one signal bar if I don't move. I think I attached a pic, hit send, then stuck it in my pocket while it was trying to send. Why it doesn't send later when i get a better signal is beyond me. But, by checking all my threads, and deleteing each one the had a red ! eventually I was able to send the one I really needed to send. If it happens again, I'll update the post with more solid information.
Phone is G'zOne Commando, Android version 2.3.3 hope this helps someone.

This works for the Samsung Galaxy S8.

None of the explanations above worked for me with my LG G5, particularly because I was having trouble finding an app which allowed me to pull up my failed messages and drafts. Latest versions just seem to show the drafts inside the message threads.
Eventually I discovered that Handcent Next SMS comes with a delivery report showing failed messages and a button to pull up drafts. So I cleared all those out and everything is working nicely.

In GO SMS you can also:

Click the menu button
Click folders
Go the the outbox folder
Delete all the failed messages there

Worked for me - this was driving me crazy!

I have a note 3 and had the same issues.

Go in your settings and check to make sure sms is your default.
Under the sms program is a setting to make sms your default as well.
Your default notification on your phone system needs to be turned off so that you don't have multiple notifications.

Hope this helps.


text:
How does one enforce a secure lockscreen on Android mail clients?
Okay, the situation.  We have a Dovecot+Postfix based mail server with the SOGo groupware providing calendaring and contacts.
All three provide TLS-based services to the public Internet.  A few of us have been able to configure our devices to support accessing our emails and calendars from our phones.  Most of us are running some version of Android.  My phone is Android 4.1 (yes, ZTE live in the stone age, but that's another topic), others are v5.0 or above.  There are a few iOS devices also.
We would like to enforce (from the server end) that the user has a secure lockscreen so that if their phone goes AWOL, they don't give away the keys to the kingdom.
I've seen lots about how some Microsoft Exchange sites somehow enforce this, and lots of people asking how to defeat it.  Also lots on other services like Android Pay that enforce this.
I'm asking the opposite question, how does it enforce this from the server?  What do I need to tell Dovecot/Postfix in order for this to be requested by the client device when the user configures their device's mail client with our IMAP/SMTP server settings?
Note: A couple have suggested I install applications on the device.  I already know how to manually set up a secure lockscreen using a pin-code, password or pattern, however the user is then free to turn that back off again.  Clearly Microsoft Exchange is able to transmit something in that initial handshake between Android email client and server that tells the phone that it must use a secure lockscreen.  I wish to replicate that same hand-shake using the Dovecot/Postfix/SOGo mail stack.
If I have to install anything on the device, then that is the wrong solution.

https://support.google.com/a/users/answer/2364439?hl=en and https://static.googleusercontent.com/media/www.google.com/en//help/hc/images/android/MicrosoftExchangePoliciesinAndroid.pdf may be useful to you

Hi @MatthewRead, That seems to suggest it's an Exchange-only feature, correct?

Seems the answer is, "it can't be enforced", despite the non-answer that user157947 gave. (Seriously, did you actually read the question?  You certainly didn't read or respond to my follow-up queries.)
The closest one might come to this is to use custom CA certificates for signing the TLS key used by IMAP, as installing the requisite CA certificate (for server verification) in the phone more or less enforces the key lock.  Another option is to issue client certificates for each device to be connected via IMAP: this too enforces a secure screen lock.
Microsoft Exchange is able to enforce it by means of proprietary extensions in the protocols used it seems, it is not done over IMAP/SMTP.


text:
Uninstall via adb without root
I own an Asus Zenfone Go Z00VD running Android 5.1.  It came preinstalled with TrendMicro Dr. Safety, which I absolutely have no use for and do not want running at all.  This app starts itself periodically, and there is no option to uninstall nor disable it.  I'm not sure that it's a system app but I assume it is.
I've done some research and found the following options:

Root the phone and uninstall the app.  This is the most obvious solution, but this is a last resort.
Remove the app via adb without root.  Not sure if this is even possible, I've seen some claims that it is, and more claims that it is not.
Install an app manager to kill Dr. Safety processes as soon as they start.  From the answers on this Stack this seems like a bad idea.

This question is about option 2.  Is it possible?  Is it safe (little chance of bricking the phone and won't open security holes)?  If the answer to either is "no" are there other non-rooting options to disable the app?
I found instructions here:
http://hexgears.blogspot.com/2015/06/android-remove-system-apps-without-root.html
but I'm doubtful that they'll even work, let alone work safely.

Since it is Android Lollipop, you can setup adb in PC and execute this command:
adb shell pm hide PACKAGE

PACKAGE → package name of an app. To know the package name of an app, follow the answers to the question: View app's full package name?
If I'm correct, this app is exactly what came with your device and which you aim to get rid of. Although you should verify the package name through your own means, I find the package name as com.trendmicro.freetmms.gmobi from the linked URL, so your command would be:
adb shell pm hide com.trendmicro.freetmms.gmobi
adb reboot     # reboot the device

Note: Execute the command at your own risk. I cannot guarantee that it would not soft-brick the device but it would make sure the app do not run again until your unhide the package. To unhide the package, replace hide by unhide in the aforesaid command.
If something goes wrong, such as the Android ends up in a boot-loop  or with recurrent crash messages, then you should either unhide the package (provided that you can) or do a factory reset which means you should backup your data before hiding the package.
As for the instructions in the link, ignore them. The author doesn't know what they wrote. Let me simplify few things there. First, the device is rooted and the title is deceptive. They are using a kernel which is not stock. A stock kernel (production build) should never allow adb deamon to be restarted with root permissions but they were able to do so using adb root. If a kernel allows this, then it is considered an insecure kernel and unfit for consumer ready devices.
Also, the steps there about removing the system apps are risky. Huge risk. Only a re-flash of stock ROM or a backup of system partition would be able to fix the device.

Oh, I forgot to mention that you should not think of uninstalling a system app without root. It's just not possible! Related: Wondering if i can debloat some google apps from unrooted lg phone for my father?


text:
Cannot install any APK file due to "Out of Space" misleading error (plenty of space)
I know there are tons of questions about this, but I have tried many possible solutions to no avail. I believe the "Out of space" error is misleading...
I have a problem: I cannot install any .apk file no matter what I try... I can install apps using Play Store though.
When I tap on an APK file in any file explorer, Android Package Installer launches. I tap the INSTALL button but I always got the following error:

Out of space {AnyAPKApp} couldn't be installed. Free up some space and
  try again.

I have plenty of space, but even a tiny 248 KB APK won't install with the same argument...
This is the only problem I have with the ROM and it is very frustrating...
First, the details of my case:

Device: Samsung Galaxy Grand Prime+ SM-G532M, alias Galaxy J2 Prime (Xtreme detects my device as Model Number: SM-G950F)
Android: 6.0.1
ROM: Xtreme Ultimate V6.0 (15.07.2018)
TWRP: 3.0.2-0
Magisk: v17.1
Magisk Manager: 6.0.1 (151)
Storage: Adoptable
Internal storage: 7.02 GB used of 8.00 GB
SD card: 9.09 GB used of 14.70 GB
Root Essentials "View storage used": 9759/15787 MB (62%)
DiskUsage analysis: /system = 2.94 GiB; Free space 1.61 GiB

I've already done my homework and tried all of the following to no avail:

Move all movable apps to SD
Enable Adoptable storage
Wipe Dalvik / ART Cache and Cache partitions with TWRP
Full clean with SD Maid PRO
Force move apps to SD using SD Maid PRO
Uninstall Google Play Services and Google Play Store updates
Overcome unauthorized device issue while using ADB
Trying to install APK using ADB (e.g. adb install someApp.apk). I got: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
Delete /data/log contents as suggested here
Attempt to install in Safe Mode
Using Termux and the df command, I got the following output and there is free space in each partition:
Using pm install test.apk in a terminal emulator (Termux) I got [INSTALL_FAILED_INVALID_URI]. Using full path pm install /storage/emulated/0/Download/test.apk I got the same error: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]

The problem still remains. I think this is not really related to the full storage device error, I have plenty and the error seems misleading. It has to be something else...
I gave as much info as I thought it was useful. If more is needed, just tell me to share it.
I hope you can give me some advice to try to overcome this annoying issue.
P.S. I'll add more attempts to my list as I try them.

Curious if your SD card is partitioned?  Also with which file system format it has (ntfs, fat32, etc..)?

@CzarMatt If I understand correctly adb shell mount output, it is sdcardfs, right? /mnt/expand/d02821cc-6e14-4015-ae94-1bbd69368dce/media /mnt/runtime/default/emulated sdcardfs rw

@CzarMatt I followed the steps of Root Essentials to use my SD card as Adoptable Storage if that's meaningful.

What are the permissions on the directories where the software will be installed (and the directories leading up to the installation directory)?
Do the application(s) you are using to install the APK's have the install software right denied?  With LineageOS, this is handled by Privacy Guard.  I use X-plore: try installing it (from Play Store) and see if you can install with it.  With LineageOS, you would be prompted to allow X-plore to install software.  (It may request root privilege too.)  Perhaps you inadvertently denied the privilege earlier to your other programs (though you mention trying with adb)?
My suggestion is to backup and try reformatting the sdcard (or better yet use a new one) with the default filesystem using the built-in system utility.  On my phone, this is handled by System Preferences -> Storage (I believe).  Don't make any further changes, and try to install the APK's.

Thanks for your kind help. About the permissions, I download the APK files with Chrome browser to /storage/emulated/0/Download. According to SD Maid Pro, the permissions on the directory are rwxrwx--x (/0 as well. /emulated has rwx--x--x and /storage has rwxr-xr-x) which seems fine to me. All downloads including APK files have these permissions: rw-rw---- I even tried to set 777 permissions to an APK and install it with adb to test , but nothing. I'll add this to my attempt list. More comments to come about your answer/suggestions...

About the applications used to install, I've tried with the following (all with root privilegies): Root Essentials (Root Browser), SD Maid PRO (Explorer), Total Commander and now _X-plore_All of them launch Android's Package Installer. I've also tried with adb install test.apkand nothing... Using pm install test.apk in a terminal emulator (Termux) I got [INSTALL_FAILED_INVALID_URI]


text:
Does rooting require a custom ROM?
I've noticed that some apps say they require a rooted phone. Is it necessary to install a custom ROM in order to root a phone?
Edit: I should mention that I've seen this answer, but my phone isn't listed.

Apparently you can root the Flipside using z4root (http://forum.xda-developers.com/showthread.php?t=835627), if you do so feel free to add the Flipside to that answer!

Cool I think it worked, I've updated that answer.

Actually it's the other way around, you need rooting to load custom ROM! Happy to see you managed :-) There's an app to check if you're really rooted: https://market.android.com/details?id=com.joeykrim.rootcheck. Once you are permanently rooted you should see a "Superuser" icon among your apps.

No.  For the most part, custom ROMs are just cosmetic changes to official ROMs and may come pre-rooted, but nothing about rooting requires a custom ROM.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/2.5/


text:
USB reverse tethering - netcfg not found (marshmallow CM13)
I have been attempting to get reverse tethering working on my phone. I have a Galaxy S5 (g900t), running cyanogenmod 13 (marshmallow)...rooted, and with busybox.
*Edit: I've made some progress. I ran this on my ubuntu machine:
sudo ip addr flush dev eth0
sudo ip addr flush dev usb0
sudo brctl addbr br0
sudo brctl addif br0 eth0 usb0
sudo ip link set dev br0 up
sudo dhclient br0

And then I ran this in the adb shell:
dhcptool rndis0

After doing this, I seem to have internet.
I can do wget -s google.com. However, it only works as su.
root@klte:/ # wget -s google.com
Connecting to google.com (4.59.40.99:80)
Connecting to www.google.com (4.59.40.99:80)

2000@klte:/ $ wget -s google.com
wget: bad address 'google.com'

I verified that I can do wget as a regular user when I am connected through cell network or wifi.
So my question is:
Why would I be able to apparently access the internet as su, but not as a regular user? I've checked my ifconfig and route settings, and they all look the same either as su or regular user. Does anyone see what I'm doing wrong?

Config setting printouts
These settings are all the same, whether I run them as su or not.
Here is my ifconfig:
1|root@klte:/ # ifconfig rndis0
rndis0    Link encap:Ethernet  HWaddr 62:91:0C:85:FD:6B
          inet addr:192.168.22.6  Bcast:192.168.22.255  Mask:255.255.255.0
          inet6 addr: fe80::6091:cff:fe85:fd6b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:582 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:62495 (61.0 KiB)  TX bytes:15839 (15.4 KiB)

And here is my route table:
root@klte:/ # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.22.1    0.0.0.0         UG    0      0        0 rndis0
192.168.22.0    *               255.255.255.0   U     0      0        0 rndis0

And it appears that my DNS servers are set correctly:
root@klte:/ # cat /etc/resolv.conf
nameserver 8.8.4.4
nameserver 8.8.8.8

I cannot help you with all the command-line setup, but if you are willing to install an app, you could try my app ReverseTethering NoRoot: https://play.google.com/store/apps/details?id=com.floriandraschbacher.reversetethering.free

I just recently stumbled across what seems to me to be a much better (or at least easier) solution for reverse tethering: gnirehtet
It sets up a VPN on the android which redirects all traffic across an adb reverse port connection. Doesn't even require root at all.

I can just confirm that 'Android 6.0.1' has the same behavior.
USB reverse tethering is only working for user 'root'.
For the user 'shell' it does not work.

USB cable is plugin to PC with Window 7
Enabled 'USB tethering' on the phone
Window automatically installed 'Remote Ndis Driver'
Manually enable 'Internet Connection sharing' on my LAN Ndis(I get the internet from) for the 'USB Remote Ndis'. Doing so Windows assigns 'USB Remote Ndis' the IP 192.168.137.1
^ by this setup on the PC is complete

Now I use "adb.exe shell" to login to android
-> su
-> ifconfig rndis0 192.168.137.2 netmask 255.255.255.0
-> route add default gw 192.168.137.1 dev rndis0
Now test it:
shell@j5nlte:/ $ su
root@j5nlte:/ #
root@j5nlte:/ # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.137.1   0.0.0.0         UG    0      0        0 rndis0
192.168.137.0   *               255.255.255.0   U     0      0        0 rndis0

root@j5nlte:/ # wget --s google.com
wget --s google.com
Connecting to google.com (216.58.205.238:80)
Connecting to www.google.de (172.217.20.67:80)

root@j5nlte:/ # exit
shell@j5nlte:/ $ wget --s google.com
wget --s google.com

Here it just hang's wget gives no reply and after some time:
wget: bad address 'google.com'
Update:
In the registry change the ICS setting
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters
ScopeAddress  "192.168.137.1" => "192.168.42.1"
since android uses that as default as you can see here:
    shell@j5nlte:/ $ ifconfig rndis0
    rndis0    Link encap:Ethernet  HWaddr E6:D3:B6:BC:7B:D4
              inet addr:192.168.42.129  Bcast:192.168.42.255  Mask:255.255.255.0
now the only line that's left to enable USB reverse tethering for at least root is:
route add default gw 192.168.42.1 dev rndis0

Now I'm just experimenting with
    ip route
    ip route help
....

I know I'm answering an old question here, but I've run into the same problem with Android Nougat (LineageOS 14.1), and I might as well post the solution I found:
Run the following as root on the phone (through adb) after starting tethering:
dhcptool rndis0
ip rule add from all lookup main pref 99

(the commands to run on the computer aren't in question here; in my case, I had to modprobe usbnet and modprobe rndis-host to even see the usb0 interface, but that's a completely different problem).
The thing is, Android uses a fairly complex routing setup, with different routing tables (see below for a dump).  The dhcptool rndis0 command puts the appropriate routing lines in the standard main routing table, but the main table is only consulted under a rule that says uidrange 0-0 (that is, for root).  What the second line above does is force the use of the main routing table for everything.  This should be undone aftewards with
ip rule del pref 99

This seems to work for me, but I'm not sure how robust it is.  Maybe it subtly breaks something that I didn't realize it would.  Maybe there's a higher-level Android-specific command that's better and that I don't know about.
As a reminder, one can use ip rule show to display the current routing rules, and ip route show table wlan0 to show the content of table wlan0 (say).
For reference, here are the routing rules I found on my Android once tethering was set up:
0:      from all lookup local
10000:  from all fwmark 0xc0000/0xd0000 lookup legacy_system
10500:  from all oif wlan0 uidrange 0-0 lookup wlan0
10500:  from all oif rndis0 uidrange 0-0 lookup local_network
13000:  from all fwmark 0x10063/0x1ffff lookup local_network
13000:  from all fwmark 0x10064/0x1ffff lookup wlan0
14000:  from all oif wlan0 lookup wlan0
14000:  from all oif rndis0 lookup local_network
15000:  from all fwmark 0x0/0x10000 lookup legacy_system
16000:  from all fwmark 0x0/0x10000 lookup legacy_network
17000:  from all fwmark 0x0/0x10000 lookup local_network
18000:  from all iif rndis0 lookup wlan0
19000:  from all fwmark 0x64/0x1ffff lookup wlan0
22000:  from all fwmark 0x0/0xffff lookup wlan0
23000:  from all fwmark 0x0/0xffff uidrange 0-0 lookup main
32000:  from all unreachable


text:
Micromax Canvas 2 Restarting Problem. Show modem log on the way?
I got sick of this.
Whenever i restart my phone it shows "Modem log on the way". I don't know what type of log they are but it creates a folder in my internal storage named "mtklog" which contains some other folders like "mdlog","mobilelog" and "configlog".
The size of these folders are approx 1GB. It gets all over my internal storage. If i delete this folder or stop the process "Modem log on the way", my phone doesn't displaying any contacts and call logs.
And the most important thing after this so called "log" process gets over the contacts in my phone memory gets duplicated.
Please help if any one has solution.
Thank you.

Did u try disabling it from System UI Logger screen ?

yup if I disable the logging my contacts are not displying

Try this,
     formating your device that will solve your problem regarding to      restarting device sucessfully.
I hope above solution will help you.


text:
SMTP auth server settings
I'm using my own SMTP server with SMTP AUTH for sending mails. The greeting looks like:

250-[...fqdn...] Hello [...fqdn...] [...ip...], pleased to meet you
  250-ENHANCEDSTATUSCODES
  250-PIPELINING
  250-8BITMIME
  250-SIZE
  250-DSN
  250-AUTH CRAM-MD5 DIGEST-MD5
  250-DELIVERBY
  250 HELP

Unfortunately when configuring user name and password for SMTP (no TLS), Android 4.2 (the standard mail app of the Google/LG Nexus 4) does not seem to expect this: authentication methods aren't supported by server.
On the server, I see Android disconnecting after that greeting was sent.
What authentication methods are actually supported by Nexus 4's mail app?

I didn't look at the logs of my server for this, but I am using CRAM-MD5 myself with K9 mail. So it's definitely not the fault of Android, but rather of the mail app you're using. Maybe you could add information on your device, as different manufacturers might use different "stock email apps"?

@Izzy: It's the Google/LG Nexus 4. After your comment I tried K-9 and it is working. Thanks a lot. Adjusted question accordingly.

Glad the hint helped! So as suspected, it is a limitation of the pre-installed mail app of your device. Thanx for updating the details -- with some luck another GN4 user might be able to help on this.

Do you mind adding a few screenshots of your configuration window. In those, the text areas like username, password and server could left blank meanwhile keep other options as they were and take the screenshot.

@Murshid: It seems screenshots require rooting the phone which I did not do (yet?). However, the configuration for SMTP consists just of the following fields: server -- [...], port -- 587, security type -- none, require sign-in -- yes, username -- [...], password -- [...].

Did you give a try turning off require sign in?

@Murshid: Yes, then it just tries SMTP without authentication ... which is happily rejected by the server.

Well, it is kind of tough now. You have no problem with the port, since you are getting connected and you have no problem with android as well. So your server is rejecting the connection due to the authentication method. So your server isn't supporting CRAM-MD5 it seems. If you have an option to use PLAIN try it. You might have to install CRAM-MD5 authentication mechanism on your server.

The authentication is working on the server. It works with K-9 (with the same settings) and with different MTAs on PCs. It's just the stock email app which does not seem to play well.

Then it must be a bug in your stock app, as you have already doubted. We can't do much about it. I think you should try re-flashing the stock app

Probably a bit late to the party, but I'm recording this here for posterity.  My wife's Xperia Z5 Compact (Android 5.?), as well as my own Samsung S3 (4.3) suffer from this same problem.  I've pulled down the source code to the most recent email client, and it appears that the only authentication mechanisms that the native email client supports is PLAIN, LOGIN and XOAUTH2, otherwise the client comes up with the above error message.  As noted in the OP, the mail server is only offering CRAM-MD5 and DIGEST-MD5, which the client doesn't support.  I had to add PLAIN and LOGIN to my mail server (after enforcing TLS), at which point the stock mail client was happy.


text:
How can I take a screenshot on my Samsung Galaxy Fit?
I can't find how to take screen shot on my Samsung Galaxy Fit device. I noticed that it took some screenshots and I do not know how it happened. By installing third party app it works, but I do not want to do this because they run their services in the background.
Any help in this regard would be highly appreciated.

I've rolled back your edit because it served no obvious purpose. Proper nouns (such as "Samsung Galaxy Fit" and the pronoun "I") are capitalized in standard English. Your edit took a grammatically correct one and made it incorrect without adding anything.

Home + Power
--or--
Home + Back


text:
Relay SMS to a normal computer
Is anyone aware of a way to relay SMS messages back and forth to a PC/laptop?  As in, so you could deal with texting on the computer and leave the phone sitting around wherever on the same LAN.  Any target OS is fine.
I've searched myself for this but it turns out "SMS relay" refers to something slightly different.

The question "Is there an app..." will be closed because app recommendations are off-topic, and "How to write an app..." will also be closed because programming questions are off-topic. Your best hope here would be to focus on the problem you're trying to solve.

@onik Thx -- I'll rephrase this.  I'm actually not looking for programming help, that was kind of extraneous.

Android has no such native feature – but there are plenty of apps dealing with exactly this, see my collection to Send SMS remotely. The most famous candidates from that list are probably Pushbullet and MightyText.
If you want more, there are even apps to (almost) completely remote-control your Droid, see Manage your Android Device from your Computer. From this category, Airdroid is one of the favorites.

@goldilocks:Any target OS is fine, besides Airdroid as suggested by Izzy, you can try KDEconnect app but the functionality is  limited to Android 4.4.x and KDE(Linux). Other than that Webkey app from F-Droid works well like Airdroid but requires Rooted Device.

Look at mighty text. It let's you open a website on your computer and send/receive texts.

I use MySMS http://www.mysms.com/.  It works very well.

Google voice provides this capability along with many other useful features.


text:
"press" spacebar on website
I am using quite nice timer for measuring my Rubik's Cube solve time: http://mzrg.com/qqtimer/
I want to use it too on my Samsung Galaxy Ace 2, when I don't have access to computer. Problem is, that site wants you to press space to start and stop timer. Is there possibility to emulate pressing space in Android browser? If this needs to install some specific browser that's fine.
PS. I know there are some Cube timers in market, but I can't find one with all handy statistics that this site has.

Well, you could...press the space bar? There is one on the keyboard. If the keyboard is "invisible", it might help to long-press the menu button to bring it up (doesn't always work, but is always worth a try).

Long pressing menu button brings up virtual keyboard, but also "leaves" site and starts entering new site address. So it is not a solution to a problem.

Oh -- I wasn't aware of that (never used that feature with the web browser). OK, was worth a try though. So except for an external keyboard, I'm out of ideas then... (or maybe Tasker could be used to insert a keystroke? Tasker can do such things, according to its manual, but I never tried).

This is just html with javascript. Copy it to another site and modify the code (put a button in it).

@ott-- You mean - modify and store as offline page? That can work...

You can also use the greasemonkey plugin (in firefox) and simply add it online. The site owner will not be aware of it.


text:
How to add/restore the 'Apps' shortcut to the home screen of Apex Launcher
I'm using Apex Launcher. For some reason, I don't seem to have the 'Apps' button on the home screen (i.e. the button on the bottom-right of the default Touchwiz launcher that opens the list of apps).
I've tried to add it manually using QCustomShortcut but I don't know the package name.
Does anyone know how to get this button back or add it manually? Or if someone knows the name of the package or process name (of the 'Apps' process), I may be able to work it out from there.
This is the icon I'm referring to, as it appears in the default Touchwiz launcher: Samsung GS4 home-screen

Apex Launcher (com.anddoes.launcher) and Apex Launcher Pro (com.anddoes.launcher.pro). Also see View app's full package name?. If you clear data of Apex launcher from Settings app, you should be able to get what you want, albeit at the cost of lost customization.

It may be hidden under another icon. Try moving other icons and look for the APP drawer icon:)

The process name I was after is for the 'Apps' application.
Yeah, I tried resetting Apex launcher but it doesn't import that 'Apps' shortcut. Maybe this is the intended setting in Apex? I'm not sure as I've only been using it a few weeks. But then, the only way to launch an app would be by manually adding a shortcut to the home-screen for every application, which doesn't seem right.

Nevermind! The icon is indeed there when I reset Apex. I just mistook it for a separate shortcut. Thanks.


text:
Android TV box + Remote Control + Netflix
I use a mele Android TV box with a mele remote control. This works perfectly with Kodi and MXPlayer, but the netflix app is extremely uncomfortable. It only works, very temperamentally, with the mouse controls.
I am Primarily looking for Play vs Pause controls actually.. The rest sort of works, but pause is very conspicuously lacking. Is this actually expected or is there a way to get my play/pause button on my remote to work with the app?
To be clear I want a way for it to work with my remote control. Not for a way to use my phone as a remote control for netflix.

Is MX Player's play/pause working?

@SarpSTA yup! it works


text:
Advice to recover a bootlooped One plus One
Tldr: I now have a phone that works when it is plugged in but continuously reboots when it is not, shows the Oneplus logo and then reboots again. I am able to boot into TWRP or fastboot. I tried a wipe clean and flash Lineage 15.1 but still the same issue. Occasionally it gets a few seconds into the OS boot process, I start to see the lineage OS boot sequence and then it crashes again.
I had Lineage 15.1 on the phone, which I believe was flashed over 14.1 without a wipe (i dont remember). It was quite unstable, it used to crash and reboot couple times a day. And this particular time, it rebooted, then crashed again, and started the bootloop that it is in now. It was getting faster.. Initially it used to reboot to the lock screen, then crash in a second or 2. Then it used to come to the boot animation and then crash, and soon after just looping at the manufacturing logo. I did not flash or do any such tinkering recently. Yesterday, before I wiped, It was stable as long as it was plugged in to power, and then when I remove the power cable the boot loop would start. Now after I tried the wipe there is no such thing any more. It reboots whether it is connected or not. The only thing I did differently was use a cheap aliexpress cable that i bought recently and a old powerbank for a few minutes the day earlier, and given the behavior with it bootlooping on battery but not on AC, i was wondering if the battery pack or the cable fried my battery in some way.
Edit: Even after flashing a new rom I have the same behavior, works if it is plugged in, bootloop on battery.


text:
slow unusable nexus s
Samsung Nexus S, android 4.3.1, cyanogen 10.2.0-crespo, usable memory: 383MB

I have this mobile for three years now. The phone seemed to work okay until ICS and it started to get worse with Jelly bean. Now-a-days the phone is really slow and it is mostly unusable. It becomes more unusable when enabling data/wifi. I assume many apps are sent the broadcast message at the same time and they are all trying to perform updates at the same time.
I used to have Watchdog app and for quite a long time I have been monitoring cpu utilization and load average and found it to be high at most times. Until one day, I spotted the available memory was close to zero. Then i assumed the cpu is performing a lot of wasteful GC at most times. Later, I spotted more occurrences of memory plummeting to zero. I noticed that the garbage collection kicks in when I view 'My apps -> Running' and I am not sure whether it happens often enough to make the system performant.
In order to debug, I decided to reduce the number of apps and started uninstalling many of the apps including watchdog but that approach has not solved the problem. I have installed cyanogen updates and that has not solved the problem. I did notice the phone is much faster with the default apps from cyanogen. after installing gapps.zip, android installs more apps based on purchase history and the phone becomes slower. also the phone seems to be faster on restart and after a few days of uptime, it has less memory to work with. i believe there may be a memory leak and not enough memory to launch new apps and does wasteful GC work.
the ways I realize the phone to be slow are
1. when looking at running apps, android seem to be killing many non-foreground apps as I notice status 'restarting'
2. when i use the button on my microphone, the beep to the interrupt arrives either too late or it is completely missed.
3. if i come out of an app to the home screen, I can notice trebuchet initializing
guys, can you please offer some suggestions to debug the issue?
Thanks
Currently installed apps
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<AppListData>
  <App appname="Amazon" pname="uk.amazon.mShop.android" size="5316335" sizeString="5.07MB" date="23/04/2013" time="1366738427171" />
  <App appname="Amazon Kindle" pname="com.amazon.kindle" size="23581179" sizeString="22.49MB" date="21/04/2013" time="1366570897904" />
  <App appname="App List Backup" pname="com.brandao.applistbackup" size="2304027" sizeString="2.20MB" date="01/04/2014" time="1396383102282" />
  <App appname="App List Backup" pname="com.punsoftware.backup" size="378902" sizeString="370KB" date="01/04/2014" time="1396382887244" />
  <App appname="Barcode Scanner" pname="com.google.zxing.client.android" size="668224" sizeString="653KB" date="21/06/2013" time="1371836472245" />
  <App appname="BubbleUPnP" pname="com.bubblesoft.android.bubbleupnp" size="3957649" sizeString="3.77MB" date="13/03/2014" time="1394747887162" />
  <App appname="Bus Scout" pname="eu.asteryx.transportlocator" size="1681662" sizeString="1.60MB" date="26/10/2013" time="1382772788648" />
  <App appname="ColorNote" pname="com.socialnmobile.dictapps.notepad.color.note" size="859481" sizeString="839KB" date="27/04/2013" time="1367058968594" />
  <App appname="English" pname="livio.pack.lang.en_US" size="14437111" sizeString="13.77MB" date="26/04/2013" time="1366978486863" />
  <App appname="Facebook" pname="com.facebook.katana" size="17040328" sizeString="16.25MB" date="19/07/2013" time="1374218323740" />
  <App appname="Gmail" pname="com.google.android.gm" size="4253876" sizeString="4.06MB" date="21/04/2013" time="1366552277742" />
  <App appname="Google Play services" pname="com.google.android.gms" size="12235141" sizeString="11.67MB" date="21/04/2013" time="1366552139811" />
  <App appname="Google Play Store" pname="com.android.vending" size="6951714" sizeString="6.63MB" date="01/08/2008" time="1217592000000" />
  <App appname="Google Search" pname="com.google.android.googlequicksearchbox" size="15140947" sizeString="14.44MB" date="01/08/2008" time="1217592000000" />
  <App appname="Journey Pro" pname="com.navitime.journeypro" size="9248795" sizeString="8.82MB" date="21/04/2013" time="1366582802991" />
  <App appname="Klipsch Control" pname="com.outsidesource.klipschcontrol" size="1133885" sizeString="1.08MB" date="06/02/2014" time="1391648578499" />
  <App appname="Maps" pname="com.google.android.apps.maps" size="7231300" sizeString="6.90MB" date="21/04/2013" time="1366552318711" />
  <App appname="Music" pname="com.jrtstudio.music" size="1015725" sizeString="0.97MB" date="13/12/2013" time="1386910689644" />
  <App appname="Pink Floyd" pname="com.pinkfloyd" size="802578" sizeString="784KB" date="29/09/2013" time="1380469681247" />
  <App appname="Pink Floyd Lyrics" pname="com.burke.pinkfloydlyrics" size="789866" sizeString="771KB" date="29/09/2013" time="1380469799724" />
  <App appname="Planning Poker" pname="com.ubxd.poker" size="106737" sizeString="104KB" date="29/04/2013" time="1367230918208" />
  <App appname="Pulse" pname="com.alphonso.pulse" size="9143806" sizeString="8.72MB" date="21/04/2013" time="1366570526289" />
  <App appname="Silent Time" pname="com.QuiteHypnotic.SilentTime" size="83997" sizeString="82.03KB" date="22/04/2013" time="1366618039740" />
  <App appname="Skype" pname="com.skype.raider" size="17600039" sizeString="16.78MB" date="31/05/2013" time="1370024457835" />
  <App appname="Sound Sleep (MT)" pname="imoblife.mtsoundsleep" size="16695081" sizeString="15.92MB" date="02/06/2013" time="1370209484511" />
  <App appname="SwissArmyKnife" pname="com.digital_and_dreams.android.swiss_army_knife" size="761305" sizeString="743KB" date="22/04/2013" time="1366644512928" />
  <App appname="Titanium Backup" pname="com.keramidas.TitaniumBackup" size="6155960" sizeString="5.87MB" date="13/07/2013" time="1373670423283" />
  <App appname="YouTube" pname="com.google.android.youtube" size="7754318" sizeString="7.40MB" date="06/02/2014" time="1391648972286" />
</AppListData>

System information:
u0_a41@crespo:/ $ uname -a
Linux localhost 3.0.101-Cyanogenmod-g7421011 #1 PREEMPT Mon Dec 2 14:43:29
PST 2013 armv7l GNU/Linux

u0_a41@crespo:/ $ free -m
             total         used         free       shared      buffers
Mem:        392408       377584        14824            0         1180
-/+ buffers:             376404        16004
Swap:            0            0            0

u0_a41@crespo:/ $ ps
USER     PID   PPID  VSIZE  RSS     WCHAN    PC         NAME
root      1     0     584    448   ffffffff 00000000 S /init
root      2     0     0      0     ffffffff 00000000 S kthreadd
root      3     2     0      0     ffffffff 00000000 S ksoftirqd/0
root      6     2     0      0     ffffffff 00000000 S rcu_kthread
root      7     2     0      0     ffffffff 00000000 S khelper
root      8     2     0      0     ffffffff 00000000 S suspend
root      9     2     0      0     ffffffff 00000000 S sync_supers
root      10    2     0      0     ffffffff 00000000 S bdi-default
root      11    2     0      0     ffffffff 00000000 S kblockd
root      12    2     0      0     ffffffff 00000000 S khubd
root      14    2     0      0     ffffffff 00000000 S cfg80211
root      15    2     0      0     ffffffff 00000000 S cfinteractive
root      16    2     0      0     ffffffff 00000000 S rpciod
root      17    2     0      0     ffffffff 00000000 S khungtaskd
root      18    2     0      0     ffffffff 00000000 S kswapd0
root      19    2     0      0     ffffffff 00000000 S ksmd
root      20    2     0      0     ffffffff 00000000 S fsnotify_mark
root      21    2     0      0     ffffffff 00000000 S nfsiod
root      22    2     0      0     ffffffff 00000000 S crypto
root      37    2     0      0     ffffffff 00000000 S kapmd
root      38    2     0      0     ffffffff 00000000 S pvr_timer
root      39    2     0      0     ffffffff 00000000 S sec_jack_wq
root      40    2     0      0     ffffffff 00000000 S irq/38-sec_head
root      41    2     0      0     ffffffff 00000000 S irq/167-fsa9480
root      42    2     0      0     ffffffff 00000000 S mtdblock0
root      43    2     0      0     ffffffff 00000000 S mtdblock1
root      44    2     0      0     ffffffff 00000000 S mtdblock2
root      45    2     0      0     ffffffff 00000000 S mtdblock3
root      46    2     0      0     ffffffff 00000000 S mtdblock4
root      47    2     0      0     ffffffff 00000000 S mtdblock5
root      48    2     0      0     ffffffff 00000000 S mtdblock6
root      49    2     0      0     ffffffff 00000000 S spi_gpio.3
root      58    2     0      0     ffffffff 00000000 S f_mtp
root      59    2     0      0     ffffffff 00000000 S file-storage
root      60    2     0      0     ffffffff 00000000 S irq/308-mxt224_
root      61    2     0      0     ffffffff 00000000 S irq/173-k3g
root      62    2     0      0     ffffffff 00000000 S gp2a_wq
root      64    2     0      0     ffffffff 00000000 S irq/172-s3c-sdh
root      65    2     0      0     ffffffff 00000000 S binder
root      66    2     0      0     ffffffff 00000000 S krfcommd
root      67    2     0      0     ffffffff 00000000 S mmcqd/0
root      68    2     0      0     ffffffff 00000000 S mmcqd/0boot0
root      69    2     0      0     ffffffff 00000000 S mmcqd/0boot1
root      70    2     0      0     ffffffff 00000000 S dhd_cfg80211_ev
root      71    2     0      0     ffffffff 00000000 S dhd_watchdog
root      72    2     0      0     ffffffff 00000000 S dhd_dpc
root      73    2     0      0     ffffffff 00000000 S dhd_sysioc
root      74    2     0      0     ffffffff 00000000 S irq/334-cypress
root      75    2     0      0     ffffffff 00000000 S max8998-charger
root      76    2     0      0     ffffffff 00000000 S irq/39-max8998-
root      77    1     512    304   ffffffff 00000000 S /sbin/ueventd
root      78    2     0      0     ffffffff 00000000 S yaffs-bg-1
root      79    2     0      0     ffffffff 00000000 S yaffs-bg-1
root      81    2     0      0     ffffffff 00000000 S jbd2/mmcblk0p1-
root      82    2     0      0     ffffffff 00000000 S ext4-dio-unwrit
root      83    2     0      0     ffffffff 00000000 S jbd2/mmcblk0p2-
root      84    2     0      0     ffffffff 00000000 S ext4-dio-unwrit
system    86    1     924    220   ffffffff 00000000 S
/system/bin/servicemanager
root      87    1     4128   512   ffffffff 00000000 S /system/bin/vold
audit     90    1     976    296   ffffffff 00000000 S /system/bin/auditd
root      91    1     9916   904   ffffffff 00000000 S /system/bin/netd
root      92    1     960    244   ffffffff 00000000 S /system/bin/debuggerd
radio     93    1     7160   996   ffffffff 00000000 S /system/bin/rild
system    94    1     50844  34260 ffffffff 00000000 S
/system/bin/surfaceflinger
root      95    1     291036 12620 ffffffff 00000000 S zygote
drm       97    1     10404  952   ffffffff 00000000 S /system/bin/drmserver
media     98    1     38252  3228  ffffffff 00000000 S
/system/bin/mediaserver
install   99    1     952    316   ffffffff 00000000 S /system/bin/installd
keystore  100   1     3292   648   ffffffff 00000000 S /system/bin/keystore
gps       101   1     26124  1980  ffffffff 00000000 S
/system/vendor/bin/gpsd
shell     104   1     848    212   ffffffff 00000000 S /system/bin/sh
root      105   1     588    32    ffffffff 00000000 S /system/xbin/su
root      115   2     0      0     ffffffff 00000000 S kauditd
root      116   2     0      0     ffffffff 00000000 S pvr_workqueue
system    368   95    471676 107716 ffffffff 00000000 S system_server
u0_a39    446   95    369460 70424 ffffffff 00000000 S com.android.systemui
radio     564   95    351644 28920 ffffffff 00000000 S
com.android.phoneu0_a13    572   95    318548 16920 ffffffff 00000000 S
com.bel.android.dspmanager
nfc       580   95    321468 15204 ffffffff 00000000 S com.android.nfc
theme_man 589   95    314312 14152 ffffffff 00000000 S
com.tmobile.thememanager
root      677   2     0      0     ffffffff 00000000 S loop0
root      678   2     0      0     ffffffff 00000000 S kdmflush
root      690   2     0      0     ffffffff 00000000 S kcryptd_io
root      691   2     0      0     ffffffff 00000000 S kcryptd
root      692   2     0      0     ffffffff 00000000 S ext4-dio-unwrit
nfc       694   95    317504 13424 ffffffff 00000000 S
com.android.nfc:handover
u0_a48    788   95    314072 13252 ffffffff 00000000 S com.android.smspush
u0_a49    2181  95    361244 24236 ffffffff 00000000 S
com.google.process.gapps
u0_a49    2204  95    352248 17264 ffffffff 00000000 S
com.google.process.location
root      3158  2     0      0     ffffffff 00000000 S flush-179:0
u0_a1     3844  95    325584 19564 ffffffff 00000000 S android.process.acore
root      17538 2     0      0     ffffffff 00000000 S kworker/u:3
root      21485 2     0      0     ffffffff 00000000 S kworker/u:1
u0_a24    22634 95    321564 32460 ffffffff 00000000 R
com.android.inputmethod.latin
root      23014 2     0      0     ffffffff 00000000 S kworker/0:2
root      24625 2     0      0     ffffffff 00000000 S kworker/u:0
root      25153 2     0      0     ffffffff 00000000 S kworker/0:0
root      25948 2     0      0     ffffffff 00000000 S kworker/u:2
root      26130 2     0      0     ffffffff 00000000 S kworker/0:1
root      26146 2     0      0     ffffffff 00000000 S flush-31:4
root      26147 2     0      0     ffffffff 00000000 S flush-31:6
wifi      26386 1     3252   908   ffffffff 00000000 S
/system/bin/wpa_supplicant
dhcp      26418 1     952    440   ffffffff 00000000 S /system/bin/dhcpcd
u0_a66    27191 95    352376 50764 ffffffff 00000000 S com.facebook.katana
u0_a41    27231 95    310040 27240 ffffffff 4011f6f0 R jackpal.androidterm
u0_a41    27247 27231 848    468   c0040f64 4002fef8 S /system/bin/sh
u0_a67    27258 95    0      0     ffffffff 00000000 Z ogle.android.gm
u0_a49    27275 95    439248 26740 ffffffff 00000000 S
com.google.android.gms
u0_a17    27356 95    313376 24288 ffffffff 00000000 S android.process.media
u0_a41    27388 27247 1172   460   00000000 4004215c R ps
u0_a41@crespo:/ $ uptime
up time: 10 days, 21:42:08, idle time: 07:47:10, sleep time: 10 days,
07:34:03

u0_a41@crespo:/ $ df
Filesystem               Size     Used     Free   Blksize
/dev                   191.6M    64.0K   191.5M   4096
/mnt/secure            191.6M     0.0K   191.6M   4096
/mnt/asec              191.6M     0.0K   191.6M   4096
/mnt/obb               191.6M     0.0K   191.6M   4096
/mnt/fuse              191.6M     0.0K   191.6M   4096
/cache                 469.5M    89.6M   379.9M   4096
/efs                     6.8M     4.6M     2.2M   4096
/system                503.9M   380.8M   123.2M   4096
/data                 1007.9M   483.1M   524.8M   4096
/storage/sdcard0        13.3G     5.6G     7.7G   4096
/mnt/asec/imoblife.mtsoundsleep-1    17.0M    16.0M     1.0M   4096

u0_a41@crespo:/ $ cat /proc/interrupts
           CPU0
18:       4434  s3c-uart
22:       4434  s3c-uart
28:          7  s3c-uart
30:       5924  s3c-uart
33:    5651790  s5p_vic_eint  acc_int
34:        237  s5p_vic_eint  proximity_int
38:      88976  s5p_vic_eint  sec_headset_detect
39:         19  s5p_vic_eint  max8998-charger
43:     106060  s5p_vic_eint  modemctl_mbox
44:          0  s5p_vic_eint  pn544
47:          2  s5p_vic_eint  modemctl_bp
50:          0       VIC  s3c-pl330.0
51:          0       VIC  s3c-pl330.1
52:          0       VIC  s3c-pl330.2
58:        179       VIC  System timer
61:   16928706       VIC  rtc-tick
78:     341601       VIC  s3c2440-i2c.0
83:     535608       VIC  s3c2440-i2c.2
88:          0       VIC  s3c-udc
90:    8682840       VIC  mmc0
92:     354172       VIC  mmc1
95:    3416889       VIC  onenand
97:     247260       VIC  s3cfb, s3cfb
101:       3249       VIC  s3c-fimc0
102:          0       VIC  s3c-fimc1
103:          0       VIC  s3c-fimc2
104:          9       VIC  s3c-jpg
106:    1490590       VIC  pvrsrvkm
109:   45691172       VIC  s3c2440-i2c.1
110:          0       VIC  s3c-mfc
112:     854208       VIC
130:    1695299       VIC  mmc2
157:          0       VIC  debug-signal
164:     156714  s5p-eint  bcmsdh_sdmmc
165:          3  s5p-eint  bt_host_wake_irq_handler
166:       1912  s5p-eint  gpio_keys
167:         21  s5p-eint  fsa9480 micro USB
169:        197  s5p-eint  gpio_keys
170:        155  s5p-eint  gpio_keys
171:       3738  s5p-eint  akm_int
172:          0  s5p-eint  s3c-sdhci.2
173:       9764  s5p-eint  k3g
174:        105  s5p-eint
308:      41106  s5pv210-eint-group  mxt224_ts
334:       1347  s5pv210-eint-group  cypress-touchkey
FIQ:              fiq_glue
Err:          0
u0_a41@crespo:/ $ netstat -an
Proto Recv-Q Send-Q Local Address          Foreign Address        State
tcp6       0      0 ::ffff:192.168.0.6:48308 ::ffff:173.194.41.162:443TIME_WAIT
tcp6       0      0 ::ffff:192.168.0.6:52519 ::ffff:31.13.72.81:443ESTABLISHED
tcp6       0      0 ::ffff:192.168.0.6:41936
::ffff:173.194.66.188:5228ESTABLISHED
tcp6       0      0 ::ffff:192.168.0.6:48137
::ffff:173.194.41.142:443ESTABLISHED
tcp6       1      0 ::ffff:192.168.0.6:50009 ::ffff:173.194.41.132:80CLOSE_WAIT
tcp6       0      0 ::ffff:192.168.0.6:35612
::ffff:173.252.102.16:443ESTABLISHED
tcp6       0      0 ::ffff:192.168.0.6:52520 ::ffff:31.13.72.81:443ESTABLISHED

I have one of these phones as well, but I don't use it as my primary phone anymore. Honestly, the device has been over run by today's software. Apps keep evolving to make use of the more powerful hardware available and these older devices just can't keep up anymore. I still use my Nexus S as a play device for my kids. It has a very bare minimum installed and is still frequently low on or out of RAM. The 512 MB total RAM available isn't enough by today's standards. With the aggressive nature many apps have to keep themselves running, killing them doesn't do much good and even Android's memory management can't keep up.
I see you don't have a lot installed either as you've been removing things during your troubleshooting, but some of those apps that are left can be pretty weighty and run in the background most if not all the time. Check the Show Cached Processes as well as Running Apps and you'll likely see what else is hogging your memory.

i have upgraded to cyanogenmod version of kitkat for crespo. i have not installed gapps and i use amazon store for apps and occasionally try some .apk files. the phone is much faster and responsive and i have mostly around 100MB free. kitkat OS developers really have spent some time to be nice with old low-memory devices https://developer.android.com/training/articles/memory.html

There RAM usage seems a bit disturbing. I try to see to it that it has a min. of 15% - 30% free space.
There is a bit of a lag on our crespos. But, that relates to how many Apps are executed from Internal Memory and / or USB Storage.
Did you try moving Apps in and out of your Internal Storage. However, RAM is needed immaterial to your App's location.
Did you try any options, as yet?


text:
How to force built-in apps to update on a brand new android device?
I've just unpacked a new phone Moto G 2nd Gen and noticed that the Google Play My Apps is completely empty (it's for my wife, she didn't use android before).
So I updated several essential apps (chrome, gmail, maps) manually by searching them in play store manually and clicking "Update". Now they appeared in the list of apps.
But how can I ensure that all built in apps eventually update automatically as soon as they are not in the list?
It's painful to do that manually - some apps are not even in App Drawer (like Google Keyboard).
UPDATE:
Just to let you know: all the built in apps updated automatically and appeared in the list of "my apps"
PS: to be precise only some of them updated, others just appeared there waiting for granting more permissions

Open up the PlayStore, open menu and select settings.
Select second option from the top auto-update apps. Then chose if you want to update from just WiFi or incur data charges.
Sooner or later apps that have updates will want to update.
You can also go into the apps and select auto update if available.

The issue is that the list of "my applications" is empty since I haven't installed anything manually. Are you sure the built-in apps will eventually update even if they are not in the list?

If they have any updates they will show up, sometimes it takes awhile. But yes they will.

This should work, it has for me in the past. You could try clearing all the data from the Play Store and loading it again and see if that helps (it may make it worse). Settings > Applications > Google Play Store > Clear Data. They really should be there in the first place, but I have seen this on a few devices myself. I tended to go an add everything manually as it was a one off thing, but auto update did work for me. Each individual app has it's own 'auto update' option also... May make life a little easier.

This does work eventually, but I think the point of the question is how to make this happen "sooner" (ie, now) rather than "later".


text:
Arabic123 instea
I need to remove Hindy numbers off the Clock and date from the system of my nexus 7, when I have it in Arabic language.
I neeeeeeed numbers in this Format 1 2 3 4 5 6 7 8 9 0
Not in those middle eastern Format where
 Zero is a point and five is an o.
I know how to change Languages!!! My problem is with the format of the digits and numbers system wide.
So it is not a question that has been asked! Wake up guys.

Thank you to let us know! So do you have any question you want to have answered? Doing some guess-work: How do I add a new language?, Help getting Arabic on Android, Arabic support for my Android device

Just downloaded the Arabic language pack for SwiftKey and SwiftKey Tablet.
The numbers on it are standard 123, with the option of Arabic numbers. It does offer prediction, though apparently the Arabic language is still in beta for prediction.
I love this keyboard. I've had it since the day I got into android. It updates often. I don't even have a Tablet, but I bought both just to give the developers more money. It's currently on sale for half off, as they just released flow (their version of Swype with multiple word support.)
Good Luck. Remember why we love Android. Everything is an app, and can be changed. (:


text:
Some apps won't open anymore
I've got a problem on an LG G4 with android 5.0 : Some apps can't be openned anymore. Facebook and and supercell games like 'clash of clans' for instance.
Facebook close each time I try to open it and supercell games are locked on a black screen. That's why I didn't think it was the same issue but both happenned at the same time twice ... it has to be something they have in common...
It happenned a first time and the only way I could unlock it was to factory reset the phone.
It worked then for a few days but here I am with the same problem again and I'm looking for a way to fix this without factory reset each time ...
I don't have any clue... maybe someone here can help ?
Edit :
I tried to uninstall facebook, reboot, reinstall.   still crash at startup :(

Android's logs might give you a clue. Please check, then [edit] your post with your findings. Good luck!

I've found out that it occurs only when developpers options are enabled :/
As a developper, I need to enable those sometimes and the problem appear again.
So now I just disable them when I don't need it and it solve the issue.
If anyone can explain it I would be interrested.
Thx anyway


text:
Is it possible to change the Operating System of the K599 (chinese iPhone)

Possible Duplicate:
Can I install Android on my non-Android device?

I have an electronic device the model is K599 was built in China. The operating system of this device is a minimalist FreeBSD with java installed. I would like to know if is possible to change the operating system from Actual FreeBSD to Google Android.
Another doubt: Is it possible to install a new operating system inside the SD memory card?
I have been stuck on this for a long time.
Does someone have the same problem?
Please Help.

No.
Most chinese mobiles run on a processor like MTK62xx, which uses a MIPS instruction set. That's a possible hardware plattform for a Linux kernel to run on. Yet those phones are not equiped with enough memory to run Android. Android needs a lot more than the internal 90MB flash disk. And I assume the actual RAM is 32MB or less (judging from my last two and the remaining free Java mem.)
Your K599 does not run FreeBSD. That's a misinformation. The software and UI you see is a customized MTK/NucleuOS. There's no known way to run custom software, much less a complete foreign OS off the microSD.
There is the "Q8 / iRobot" chinese mobile, which runs a genuine Android 1.5 variant. But that was specifically designed for that, albeit I think it runs on a secondary MTKxxxx chip too. But all the other mobiles, specificall with dual sim/gsm modules are unlikely to ever will.

Thanks for your answer, it was everything I was in need to listen. Very good answer.

I have something very strange, when I use a network scan (like nessus) it find my device, and the operating system of it accuses to be FreeBSD.. it is very strange to me. or my scan is little bittle not well calibrated.. :-) anyway thank you very much, because I'm not to going waste my time trying to develop anything to this kind of chinese device. The best way to get some app to chinese device is JAVA.. yeah?

@FernandoCosta: It's very likely that all MTK phones actually use the TCP/IP networking stack from *BSD, so that might explain it being detected as FreeBSD. My OS fingerprinting tests with nmap -O were inconclusive. -- But you can run a couple of J2ME applications, yes. Opera Mini for example works well, but you'll have to be patient with both games and utility applications. -- Also btw, the "H6" or "A3000" are genuine chinese Android 2.1 mobiles.

nice tip, I learned one thing more about my chinese device. I have already opera mini and really work so well. Also I have skype working on my device, it is really funny but is true. But untill now I can't use the skype very well, sound like the program have a bug on calibration.. and I can't touch the functions..  anyway thanks again.

I don't see why it is not possible (ever heard Android running on iPhone?), as long as someone writes a driver for it. However, if your device is a niche device, then it might not have enough user support to attract an experienced driver developer to release an Android driver for it.

Thanks for the answer. This kind of device is very popular speacially in Asia, in south america is not so popular, but have a lot.. I ll give a try. Thanks again.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/2.5/


text:
AVG by DroidSecurity - legit? Useful?
Re-post from StackOverflow, when suggested this was a more appropriate forum. I originally posted this on Whirlpool as well - I am very interested to see what new input I can get from this community.
I was looking at AVG by DroidSecurity in the marketplace today and am a bit confused. On the free version there is recent feedback saying that AVG isn't affiliated with the app and other comments saying it is malware that slows the machine, deletes data and sends spam. But my Googling skills reveal articles saying AVG acquired DroidSecurity.
So, has anyone on this forum had experience with this app?
And... do I really need an anti-virus on my Android device? Is it so bad? Are we talking about bad things coming from .. what, apps, email or web pages? I am coloured by my experience with iPhone, nothing evil to worry about so far.
Also, if there's nothing to worry about, what are these AV apps doing? Scanning with an empty database?

This article about a new trojan should give you an idea of the current level of threats: http://www.androidcentral.com/security-firm-lookout-warns-against-geimini-trojan-hitting-android-china

I have no experience with this specific app, however here's my two cents on the second half of your question.
The Android security model is very well thought out. Android runs on the Linux kernel (a modified version) and sandboxes every app through a variety of measures, including running each under a different user account. The biggest legitimate threat you have is installing malicious apps. Most likely these will be trojans that ask for reasonable permissions (reading your SD card, communicating with the network) and use them for nefarious purposes.
If I remember correctly, the malware prevention portion of AVG works by scanning apps before you install them, much like desktop virus scans work. This is a reasonable way of protecting you, malicious apps can be added to a database and you are warned if anything you download (from either the internet or the Market) is known to be Bad. The only catch is that Google usually removes illegal and malicious app from the Play Store within a few days of it becoming available. (I have nothing but anecdotal evidence to back that claim up though)
So if you're installing a lot of apps from sources other than the Play Store, or you don't trust Google to quickly catch malicious apps, installing an anti-virus is probably a good bet.

Nicely answer @num1; a good description of the issue in general and I thank you sincerely. Based upon your input, I am inclined to keep the app. I cannot say with any real degree of confidence that all apps I see on the marketplace are legit: there are enough spam and outright conflicting comments against some apps that I am not wholly convinced that reputation alone is a good guide (on my first trip to market I marked multiple comments as spam). Certainly I did NOT see this level of divisiveness on iTunes. Flame me if you like; it is simply how I see it.

So, now I wonder if anyone has experience with AVG by DroidSecurity...

I found this article a few minutes ago, You might find it interesting. http://blog.mylookout.com/2010/12/geinimi_trojan/

Truth is, scanning consumes CPU cycles, which in turn consumes battery juice...

Also, if there's nothing to worry about, what are these AV apps doing? Scanning with an empty database?

That's why it should be avoided at all costs and ignore the so-called anti-virus products as that's fear-mongering into scaring you psychologically and likely,  end up "paying for their product" so that you'd feel 'safer' and lulling you into a false sense of security!
Ultimately it boils down to a bit of common-sense and double-check on the reviews and weigh it up carefully, users are not likely to bother reading what sort of permissions there are, the reviews, and so on, especially, from countries where buying an app is impossible due to legalities and restrictions within that country's jurisdiction and laws!
In relation to permissions, that is why developers post explicitly on the Overview page on the Play Store, what sort of permissions there are and explain it, around the top of the page, due to the fact end-users themselves are not bothering to click on the 'Permissions' tab page!
Henceforth, for some users, who do not want to buy, they ultimately end up being the victim and also for users from these countries, which end up resorting to downloading from unknown and dodgy websites, so don't be downloading from dodgy warez websites either!
Pro-tip If you happen to be in one of those countries or that you don't want to buy, email the developer of the app personally and ask them if some sort of agreement can be made, it can be done, perhaps by using paypal or similar... developers are not "out to get you", in fact, they are friendly! :)

YES to be blunt, Android apps can easily, be modified by someone who has knowledge of the code, due to their nature, and quite likely, to have some malicious code (read not virus.. but a trojan!) that fools the user, into thinking the app is "all-good" when in fact behind the scenes, it is sending out some logs/emails etc... that is often the reason why there should be a firewall in place to block unknown apps for a few days and monitor it. The sad truth, is, no-one gives a damn or care about that and end up posting "why is my phone bill so high?" or "Why is my battery getting sucked down very quickly?"
It is those clues that are the dead-giveaway of something quirky going on and should set off alarm bells in the head as in "Oh, that's funny, ever since I installed X app, this started appearing" but are the end-users going to care.. and carry on in denial...?

That is where the so called Anti-virus software vendors kick in... hence a vicious circle ensues...
Not to be an alarmist, remember this much: Android is not equal to Windows where viruses and malware are more commonly seen and prevalent!