text:
How to boot my Samsung Galaxy S4 mini when wall charger is plugged
I am Developing an Android Application, here i want my phone to start booting automatically when the phone is plugged into any power outlet without hitting any power button.I found many solutions and tried all but unfortunately nothing worked for me
I edited the file found in '/system/bin/playlpm' with the following custom script that will boot the phone:
Method #1
#!/system/bin/sh
/system/bin/reboot

Method #2
 #!/system/bin/sh/system/bin/reboot

Method #3
#!/system/bin/sh
su
/system/bin/reboot

but nothing worked for me. Please help me if somebody have any working solutions.

Did you set the permissions correctly? Also, you can make a script in your computer that launches it with adb when you connect the cable your phone to PC.


text:
Homemade update Sony Xperia to Android 6.0 Marshmallow and DRM restoration
I have a Xperia smartphone, Android 4.4.
Is it possible to upgrade my device with new Android 6.0 Marshmallow, and restore previously backed up DRM keys so Sony proprietary features can work as before? Or maybe the keys are bound to specific Android version?
I know about the tool Backup-TA and about the fact that Sony has recently released AOSP version for Xperias.
Please, if you can, give me answer which will be more than 'yes' or 'no', I always like to understand the way things are :)
PS. Sorry if this questions is unclear or could be a duplicate. Let me know about it please. I just could not find any information on the web about restoring DRM keys into new system version.

If you have a backup of your ta partition running a specific firmware it is for that specific firmware. Firmware in this case means the specific version of your firmware (e.g. build number). You cannot restore it.

Please explain your point more clearly. I cannot understand what you mean by "specific firmware". I do not know what firmware (if any) is run by TA partition, I am not an expert but I suppose that TA partition contains just some DRM keys (unique for each Sony device) and bootloader settings, like bootloader unlock flag etc. Also, if you can, please provide the link that supports your answer.

source: Stack Exchange

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

sort: votes


text:
Cyanogenmod LG G3 crashes and does not boot
I have recently rooted my LG G3 D855 and installed the latest stable Cyanogenmod release (Android 5.1.1 Cyanogenmod 12.1-20151117-SNAPSHOT-YOG7DAO1K8-d855).
Every few days it happens that the system crashes. So far it has only happened when I was not using my device (e.g. phone in my pocket). When I press the power button to turn on the screen nothing happens, even after several attempts and waiting between attempts. I believe that the phone is actually off during this phase as no phone calls go through.
Trying to press the power button for longer, hoping that the device will boot, proves to be unsuccessful as well. Trying the recovery buttons combination is inconclusive as well. When these issues occurred the battery was always almost full.
Luckily enough on this phone it's possible to remove the battery, and this is only thing that works. Once it boots up everything seems to be working fine. But obviously this is a really annoying issue and it's making my phone be unreliable.
Everything was working fine prior to installing the custom cyanogenmod ROM.
Is there anyway to find out what's causing the issue? And of course, are there any fixes for this?

@jis Your answer is not constructive. Why are you asking me a question if you already have the answer in my post? Also, in my post I stated that I am using a stable version of Cyanogenmod, and not an unstable one. Finally, you are suggesting something which is completely unrelated to my question.

It was a rhetorical question :)
I thought it well, why make more problems by installing CM when stock was ok... I have very bad personal experience with CM stability on my Samsung Galaxy phone and Nexus tablet, so I will never enter this bandwagon again.
Here are some useful posts for you:
http://android.stackexchange.com/questions/132218/new-lg-g3-randomly-crash
https://www.reddit.com/r/LGG3/comments/34xjyl/lg_g3_keeps_randomly_restarting/
http://forum.cyanogenmod.org/topic/118772-phone-crashes-and-another-bug/

I would recommend a hard reset in recovery. If you cannot boot into recovery, try using a computer to re-flash the system.

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


text:
Is it possible to install drivers for new hardware in Android OS?
I would like to know if it is possible  to install drivers for new hardware in Android OS. I know that Android images usually come only with the drivers for the particular device they're design for (to save space I guess). I have a Banana Pi M1 Chineese single board computer that runs Android 4.2. When I try to connect an Edimax wifi dongle to it or other generic Bluethooth dongle they don´t work. Does it make sense trying to look for drivers for these devices or is it worthless because if they existed they would already be installed there? This leads me to a broader question. Is it possible to manually install drivers in Android OS or this isn't supported as in for instance Windows or Linux OS?

I better aswer for my question is also in http://android.stackexchange.com/questions/6849/can-i-install-android-on-my-non-android-device


text:
Repair platform.xml
After upgrading to an experimental 6.0 build I've had some niggling issues. One of which was a bad WLAN config file, fixed with a delete. Second was SD Card being read only to some apps.
As a test I moved the platform.xml out to the SD and rebooted, to see if Android would generate its own (poor assumption), causing many apps to crash out, along with google play services.
I then moved it back, changed the perms to the normal for that directory, rebooted, but same issue. Cant find a way to restore the working state. Any suggestions how to fix it without a system wipe?

And it seems TWRP cant mount partitions now either, not good.


text:
Samsung Galaxy note 3 SM-N9005 cannot boot due to Power down
I have Samsung galaxy note 3 SM-N9005 and I wanted to make hard reset but I accidental did Power down. And now, my phone does not fully switch on. When I turn on the phone it stops at the Samsung sign. I waited for several minutes but nothing further happened.

Not sure if Galaxt note 3 comes with an unlocked bootloader by default, but try booting into Recovery, and doing something like a re-install (stock recovery should do in that case). You could technically go to download mode and install a custom recovery, but that voids warranty

when I switch on Adroid system recovery it offers me:
1.reboot system now
2.apply update from ADB
3.APPLY UPDATE FROM EXTERNAL SORAGE 4.apply update from cache 5.wipe data/factory reset 6.wipe cache partition 7.reboot to bootloader 8.Power down 9.voew recoveru logs 10.Enable cp logging 11.Disable cp logging

Did you mean you accidentally turned off the phone while doing hard reset?

I took the phone for repair and found out the  problem,they said that the need to reinstall the entire phone again.

The OP stated (in a comment),

I took the phone for repair and found out the problem, they said that they need to reinstall the entire phone again.

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


text:
How to access the browser history beyond the last 7 days of the default browser?
I know it's possible to view the entire browser history in other browsers. I can only see the last 7 days of my browsing history. How can I see which sites I visited beyond just the last week? Or are those getting deleted?
My phone: Android 5.0, Samsung Galaxy S5

Leaving this question up so that other people having the same issue may find help and in the case that someone knows a potentially better way to retrieve more of the browser-history.
I found something in:
/data/data/com.sec.android.app.sbrowser/files/ {1_tab123 files}

I know this is an older post but I thought an answer would be good for posterity.
The Samsung Internet browser is a Chromium based browser. As such it used to be you could use chrome commands from the address bar such as "chrome://history" and that would give access to the total history in the Samsung browser. Since the 2017 update to Samsung Internet 5.4 I have lost that functionality. It appears they have blocked it in the code.


text:
Blurry screen on Galaxy Note 8.0 (N5110) running CyanogenMod 12
I have installed CM12 on my Galaxy Note 8.0 (N5110), but now nothing is as sharp as it used to be with original Samsung ROM; all icons, text, etc. are not sharp.
How to fix this?

Can you provide the screenshot? Or, by "blur", is it the screen or camera? Lastly, if it's the screen, based on the same issue on LG Optimus, seems it's related to kernel issue (note: the kernel is for LG, not Samsung, so don't flash it).

well, its screen...

Seems there's transparent blur lock screen on CM. Are you using that? If not, is it always blurry (after unlocking, or when using any apps)?

no this is not the issue.. The thing is that all icons, fonts etc are not sharp anymore since CM12.. Looks like I bought a cheap china device, but its N5110 and ive used it for 2 yrs..

Okay, seems the issue is clear enough to be answered. However, I'm not using CM, so I'm not sure I can help (other than pointing that it's probably a kernel issue). Hopefully others can help you.


text:
CM12 + Titanium = How to recover Contact data?
I just installed CM12 on N5110, and I made Titanium backup of all apps before. Now whenever I try to get my contacts back, the Contact app of android stops with error "android.process.acore stopped...
How to get the contacts? cause I didnt take google based backup on my contacts.
Thanks

Do you've the backup of Contacts Storage or Contacts Provider app? That app keeps the contacts in the database named contacts2.db. As long as the database is not corrupted, clearing data of that  app, restoring data from Titanium and rebooting should work. If not, then extract database from backup, force stop the app, go to app's data directory and replace the database there. Reboot and see what happens.

thats what i did... restore from titanium.. but the thing is that now with CM12, I have Contact 5.1, and old was Contact 4.1.2. So thats possibly one issue I guess..

Here's how you can (try to) restore your contacts manually.  (NOTE: I'm assuming a little bit of Linux knowledge.  I've tried to cover the things that are hard to look up, but little else.)
First, enable USB debugging mode, and plug your phone into your computer. Then,

Find the folder that contains your backups. By default, I think this is something like /sdcard/TitaniumBackup. If you used a custom location (e.g., to store backups on an external SD card), then it should be easy to find.
There should be a gzipped tarball with a name similar to com.android.providers.contacts-<date>.tar.gz. Copy it to your computer with adb pull.
Untar the file you just pulled. There should now be a folder called data. Descend into data/data/com.android.providers.contacts/databases/. There you will find contacts2.db and profile.db. Use adb push to upload these to your phone. (Note: You will probably have to push them to a location that does not require root access.)

(For the next steps, you may want to reboot into recovery mode, to make sure that your phone is not using your contacts database.  You can do this easily using adb reboot recovery.)

Start a shell with adb again, and escalate to root using su. cd to /data/data/com.android.providers.contacts/databases/. Rename contacts2.db to contacts2.db.cm and profile.db to profile.db.cm.
Copy the files you pushed to /data/data/com.android.providers.contacts/databases/, so that they replace the ones you just renamed.
Make sure your new files have the same permissions as the old ones. Check the permissions of contacts2.db.cm and profile.db.cm with ls -l, and change the perms of your files with chown. Check the SELinux labels with ls -Z, and change them if needed with chcon <full label> <file>.
Reboot and see if it worked.

I hope this method works for you. I must admit, that when I tried it, CyanogenMod immediately reverted my changes (such that contacts2.db matched the original contacts2.db.cm). If this method does not work, and you really want to use CyanogenMod, then you can still recover the data from contacts2.db and try to add all of your contacts by hand.

Install sqlite3.
Run sqlite3 contacts2.db.
Your phone numbers are in the table named phone_lookup, and display names can be retrieved from the table named raw_contacts. You can see (at least some of) your contacts by running

select raw_contacts.display_name, phone_lookup.normalized_number from raw_contacts
    inner join phone_lookup on raw_contacts._id = phone_lookup.raw_contact_id;


text:
Is the rooted hack for Move to SD card better than the option built into the Android Phone OS?
What I have found recently: In order to save space on my device (Galaxy S5) I attempted to use the 'move to SD card' option. This has not really helped all that much. It seems that it uncompresses an application, making it a lot larger before moving a chunk of it to the SD card.
What I am asking is about the option that is available via a rooted phone. Does the rooted version offer a better solution, such as moving more of the app to the card? Or is it not worth the effort to root the phone for that choice?
My phone is I am certain long out of warranty so not really worried about that.
It is clear to me there also may be multiple different tools that do this. It would be helpful to find which may be the best choices. Thank you in advance.

The "Move to SD card" neither moves the app (APK file) nor the complete app data.
It just moves the additional media files and data (that doesn't pose any security risks upon revealing to user) like Images or Graphics or whatever.
(And all apps do not provide this option. It depends on the app developer.)
These moved data can be found in the Memory Card in a directory named Android/data .
And yes, the rooted solution moves the complete app and app data into your memory card, which completely lessens the burden.
But you have to create a separate EXT2/EXT3/EXT4 partition first in your memory card (using softwares like MiniTool Partition Wizard) and then use an app like Link2SD (as @Tamoghna said) or Mounts2SD.

Thank you for the elaboration and additions, partition solution as well. It makes sense. This looks like what I am needing.

Link2SD is a great root app that move the files 100%. I had it and saved a lot of space! but for now I don't need it. You will need to use a tool to edit the partitions on you SD card to make Link2SD work. I'm not sure if any of the tools running on Android will work correctly. There is a "Link2SD tutorial" available.
Just one bad thing about Link2SD : It is not free.

Sounds interesting, I will consider it - thank you for answering - for now I will accept this answer.


text:
Can we backup the stock recovery.img in any way?
Suppose I plan to flash my recovery with TWRP/CWM, but then later suppose I would like to move back to the stock recovery.
Is it possible to take a backup of stock recovery just like we can take a backup of our ROM?

Check this universal thread: Making Dump of Android Partitions. Just backup the recovery.img from there

Why do you you think it won't be possible? Rashr, Flashify and dd are always there to help as long as you've root access.

EXTRACTING BOOT.IMG FROM STOCK ROM or OTHER IMG LIKE RECOVERY ETC.
REQUIREMENT:
1. Download adb required tools.
2. PC
3. Phone Drivers (for other phones google it out)
          for spreadtrum phones: SCI-Usb-Jungo v4 (download here) or
                SCI-USB2Serial v1.5.6.1 (download here)
4. Android Phone + Usb cables
STEPS:
OPEN cmd window in adb folder
type the ff:
      adb devices
      adb shell
      su
      cat /proc/mtd

Now from your screen look at your files and you see mtd10 has your recovery.img
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd10: 00500000 00020000 "recovery"
mtd12: 00280000 00020000 "boot"
mtd13: 04380000 00020000 "system"
mtd14: 04380000 00020000 "cache"
mtd15: 04ac0000 00020000 "userdata"

Once u see it's LOCATION in which in this sample is in mtd10
type:
cat /dev/mtd/mtd10 > /sdcard/mtd10.img or
cat /dev/mtd/mtd10 > /sdcard/recovery.img
Source: http://howtorootcherrymobilesnap.weebly.com/adb/how-to-extract-img-files-via-adb-ex-bootimg

/proc/mtd is not universal. It's not there in all devices.. Change it :)

But works in many devices.

/proc/mtd is not there in my device (Yuphoria). It's empty in my mom's device (Android One).

And you conveniently didn't mention the original source. Please follow How to reference material written by others

/proc/mtd not found in my lenovo device. This may work  on certain devices only.

While /proc/mtd may not be valid for all devices how would anyone know trying to answer this question without first being provided what device model number/name is being worked on? This answer is good and until the question's author can provide specs I don't think I'd do any better than Vivek Ji already has. Also Firelord suggestions on dd will also work great for doing full backups over USB.

there is no /proc/mtd in samsung t-2111, please specify your device model to make this answer more clearly

The OP wanted to make a backup of the recovery partition BEFORE flashing a custom recovery partition. The custom recovery is needed to get root access su. So these commands will only work when the stock recovery partition is already gone.

Generic Backup/ Restore
If you are root you can backup/ restore all partitions (not only recovery) with native tools.
To list all mountable partitions and block devices use find and grep
adb shell
su
find /dev | grep by-name$

On my system I get /dev/block/platform/soc/1d84000.ufshc/by-name back (this is very device specific and yours may look different).
Now You can list ls this path to show all mountable partitions.
ls -al --color /dev/block/platform/soc/1d84000.ufshc/by-name/

Or all in one command
ls -al --color $(find /dev|grep by-name$)

Backup
Armed with this information you can, as root, backup all partitions. Just use the dd (part of every android toolboox/ toyboox e.g.:
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/recovery of=/sdcard/Download/recovery.img.dd

Restore

Warning
  Data lost possible! Don't use until You understand all dd parameter.

In many cases you can also restore with the dd tool, e.g:
dd if=/sdcard/Download/recovery.img.dd of=/dev/block/platform/soc/1d84000.ufshc/recovery

The key point is to boot a custom recovery partition such as TWRP without installing it. For instance with an HTC device you would use the platform adb tools and run this command from a terminal in Windows:
fastboot boot twrp.img

This remote-boots the custom recovery partition so you leave the stock recovery partition intact.
Now you root the phone.
Reboot the phone.
adb shell
su
Use dd command to copy the recovery partition.
If you have already flashed a recovery partition then it's too late. You will have to find a stock recovery partition for your phone somewhere on the interweb.


text:
partition on flash storage via ADB shell
I want to make a FAT 32 partition on unmontable flash because I did something wrong that I can get mount agaim the internal SD of my tablet. So I start with (in ubuntu environment)
adb shell
cd ./dev/block/vold

then with ls command I see as result
93:64
93:65

if I put
parted /dev/block/vold/93:64

I get the warning
/system/bin/sh: parted: not found

how can I make the parted command to work?. My further intention is to identify which of  93:64 or 93:65 is pointing to my flash storage and then I want to format this to FAT 32. Please, help.

Have you installed parted binary to begin with? First of all, does your Android have root access? Which device and Android version is it?

I have root acces because I see root@android:/ #, the Android version is 4.0.3   also, with the command # cat /proc/partitions I get:
93        0      16384 nanda
93        8      16384 nandb
93       16      32768 nandc
93       24     409600 nandd
93       32     524288 nande
93       40      16384 nandf
93       48      32768 nandg
93       56     262144 nandh
93       64    6470656 nandi
93       65    5421056 nandi1

The internal SD was unable to be mounted (indeed it was mounted but 0 bytes of memory) because it had errors made by me when I try to make a partition on it. I solve the problem easily, I got a external SD and I deleted its format in Gparted, then I put this in my device, a message popup showed if I want to repair it, click yes and Eureka !! my internal SD was repaired too. It seems that android device checked and repaired every SD card type in it and I get back my internal SD with its original 5 Gb !!!!.
Coool !!!


text:
Is it possible use a different bluetooth codec than SBC on Android Lollipop?
I've been having trouble with the sound quality of with my Motorola Roadster 2. Basically this is a bluetooth In-Car speakerphone that can stream incoming media audio to my FM radio, so I can enjoy listening to my music library in my car that has no 3.5mm jack.
I always thought that the sound quality was mediocre due to the FM remodulation, that is, until I connected an iPad to it and played some songs over it. The quality was absolutely better than that of my Android phone.
Apple has a different bluetooth stack for their devices obviously, so I've started looking into this. I've used this Stack Exchange answer to find out what codec my Samsung Galaxy S3 was using when streaming to the device. It seems that the Roadster 2 uses the A2DP profile and supports SBC as well as MPEG-1.2 codecs, but the phone chooses the inferior SBC after checking the capabilities for some obscure reason. Some research suggests that SBC is not recommended for music streaming because quality is not ideal, so my guess was to try using the MPEG-1.2 codec instead.
However, after some very thorough digging, I cannot, for the love of God, find any configuration to try and force the MPEG-1.2 codec with the Bluedroid Bluetooth Stack that is used with Android 4.2+ . The old BlueZ stack had an option in its configuration file (/system/etc/bluetooth/audio.conf) to enable a different codec, but it doesn't work anymore with the new Bluedroid stack. Is there a similar way to force a different codec than SBC?
I'm using Android 5.1 (Cyanogenmod 12.1 to be exact).

Looks like this question has already been answered:
How do I determine which A2DP codecs my phone supports/is currently using?
See the top most answer with a 3 score as of writing this answer.
Basically you can find out what codecs are available on your device as it comes down to what the hardware supports.  There are licensing and other fees so not every device has the capability to support every codec.

You referenced a post that MatLag already knows about... Click the link in his post. It's the same one you have so it's safe to assume that MatLag read through that.


text:
Use external mouse with Limbo
I'm using the Limbo PC Emulator on my Samsung I9305 running rooted stock 4.4.4.
If I plug in an external mouse through USB OTG or (I presume) Bluetooth, there are two cursors on the screen. Limbo's cursor, and the Android cursor. In order to move the Limbo cursor, I have to click and drag with the mouse just as I would have had to using the touch screen.
Is it possible to just have once cursor, that responds directly to the external mouse?

Yes, later versions add a feature that captures external mouse movement and actions and hides the android mouse.


text:
Different types of downloads on Cyanogen OS Website
** This question is for Cyanogen OS and not Cyanogen Mod.
On the Cyanogen OS download page, for my device (YU Yuphoria), I see 3 different downloads for my device, i.e.
cm-12.1-YOG4PAS47N-lettuce-signed-fastboot-5d674b9b61.zip
cm-12.1-YOG4PAS47N-lettuce-signed-806afa8c62.zip
cm-12.1-YOG4PAS47N-lettuce-boot-debuggable-c915697c50.img
It is clear that the first one is the firmware which is to be flashed over fastboot, but I'm skeptical about the second & the third one..
What do the 2nd & the 3rd link provide?

Signed fastboot zips:
  These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot.
Signed zips:
  Normal, stock or TWRP recovery flashable zips that won't overwrite your data partition.
Boot-debuggable images: (This is only for developers/testers)
  These are boot images (kernels) that enable adb root and the developer menu options. To be flashed via fastboot. (e.g.fastboot flash boot cm-12.1-YOG4PAS47N-lettuce-boot-debuggable-c915697c50.img)

Source: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746


text:
ADB bricked android doesn't connect to pc
I have a bricked android BLUBOO X2. I rooted it, changed build.prop to set some settings so that I could boot in Ubuntu Touch(which didn't work). And now I can't boot up anymore at all, it is in boot loop.
I tried booting in recovery and then selected "apply update from ADB". It then says: 'Now send the package you want to apply to the device with "adb sideload < filename>" ... '. I did this once and it showed an error, but the weird thing/problem is that I cannot sideload anything anymore: 'error: device not found'.
I (think I) know it is connected with my (Windows 10) PC because it made a connection and deconnecting sound when booting in recovery.
How can I get my android to be connected or how otherwise can I load a ROM or change the build.prop back?

Was ADB enabled in Developer Settings before it was bricked? What recovery do you have now? Is there a custom recovery available for your device?

I don't think I have enabled ADB before. I don't know how to respond to the question: " What" recovery do you have now?. And I wanted to install a custum ROM file, http://forum.xda-developers.com/google-nexus-5/development/rom-xtraslim-1-0-stock-odex-optimized-t2924150.

I mean, what is the name of the recovery? Is it the default (stock) recovery that came with the device? Or is it a custom recovery like TWRP ?

Just the stock recovery: if I hold power and vol-up I can choose recovery.

You don't have much options left at the table. If your device supports flashing from fastboot mode, then find a custom recovery for your device and flash or boot into it using fastboot mode. Then either correct the prop file or replace the ROM. If fastboot flashing is not supported, you must find the recovery flashable stock ROM zip for your device and use it to flash your device (you would lose existing data). Another alternative is to use SP Flash Tool.

Well, you've just messed with the system partition, so there's nothing much to panic.. Here's a stock ROM for your phone:
http://www.needrom.com/category/bluboo/x2-bluebo/ (Choose the ROM for the SAME android version you had before bricking).
The good news is you won't need to lose your data. Everything will be safe.
Download SP Flash Tools, load the scatter file from this ROM, uncheck all the partitions except ANDROID (SYSTEM) as this is the only partition you need to rectify. Click on Download and connect your device. Your device will be unbricked without having to lose any data.

Good that you found the ROM. Could you please link SP Flash Tools as well? If possible,  link the instructions for its usage as well.

The flash tool says its an invalid scatter file.

@Jeroentetje3 Be sure that you're targeting the MTxxxx_Android_Scatter.txt
This is the tutorial that worked perfectly fine for me when I was in the same condition as you: https://forum.hovatek.com/thread-159.html
Also, plz mention the flash tools version that you're using.

File: MT6592_Android_scatter.txt
Error:
" SP FLASH TOOL ERROR: (8417)
The load scatter file is invalid!
[HINT]:
Please check the scatter file and select again!"
This is both for 4.4.2 and 4.2.2. I downloaded the .rar from the site you send and unziped them and selected this file from there.
I use SP_Flash_Tool_v5.1532.00.000.zip = latest version. I also used 2 slightly older ones.

if you bricked your phone and the battery is non removable..
just open your back panel..
open screws and just cut off the power supply from the battery to phone..
for your reference i have posted a link of how to cut power supply from vivo xshot and restore it
https://moschino2015.wordpress.com/2015/09/18/exquisite-and-easy-to-disassemble-vivo-xshot-teardown-map-tour/
have fun!!
p.s who says battery arent removable??
note :- i am not responsible if u damage the internal circuits or void warranty of your phone!!
do it on ur own risk!
but it worked for me :)

When people say "removable", they refer to ones that are easily done, i.e. removable back cover and battery with bare hands. No risk of "damage the internal circuits or void warranty". Also, this isn't helpful to solving the brick problem OP is concerned with at all. -1


text:
Battery drains every time screen is turned on
I just bought a new phone, it is Android 4.4.2, but it seems that it has a problem with its battery. Every time I turn on the screen, the battery drops 1%. For example, the battery is 30%. then I close the screen and turn it on again after a minute, and then in few seconds,the battery becomes 29%. It only happens when I turn on the screen, but when im using it, the battery discharge is normal. How can I fix it?

the phone model is My25 (myphone) the battery usage says the cell standby drains 46% of the battery, i understand this because i always use data connection. Thanks for the reply @beeshyams

i've noticed that Phone idle is using 26% of the battery., while screen is using 17%

I've turned off the features. How to use safe mode?

i've used safe mode but the battery still drops

i've done that before, but the battery still drops. maybe it is a bug?

Based on our chat, things which were tried are:

Turning off "proximity sensor" and "Smart Stay" (to rule out malfunctioning causing battery drop h
Checking screen usage from inbuilt battery statistics (seemed to match usage)
Booting into safe mode and observing battery drop
Factory reset to rule out rogue app causing this

OP has confirmed that the Battery drop continues as stated in the question
Being a new phone, it could either be

ROM bug, which can be checked from user forums. If it is a reported bug add if the OEM rolls out a fix then the problem is solved
Defective piece, which being in warranty can be exchanged (Recommended course of action on my opinion)

(Flashing stock again is an option but do not advise it as rooting methods, flashing tools etc may not be readily available being a lesser known phone My25 (myphone). Flashing a custom ROM for the same reason and absence of developer support , is not recommended)

Have you been able to fix it? How?

There is a new thing in android called Smart Pixels. It is available in some custom roms like AOSP Extended (I don't think it is available on kitkat) or an android app called Pix Off
you can choose to disable a percentage of pixels on your screen to save battery :)


text:
Can I install cyanogenmod from an internal SD?
So far I am a regular user of Galaxy Ace 2, but I would like to upgrade it to CM 11. I found this page http://forum.xda-developers.com/showthread.php?t=2555021 with step saying "Install the zip from External Storage" (emphasis is mine). The problem is:

the (external) card is inserted
I alread copied CM and Open Gapps (pico version) there
yet when I reboot in the recovery mode I only have option of install from "internal sd card"

And when I browse internal sd card, there is no mount point for external card, so I assume it is not mounted at all.
Is it OK to copy the files to internal SD? Or what else should I do? Thank you for the help in advance.

Memory card will be listed as /microsd in recovery. Check it out :) BTW, yes, you can update from internal storage.

@GokulNC negative. It should be listed as either /external_sd or /extSdCard. It is safe to install from the internal storage though, as wiping /data in TWRP, CWM and Philz recovery does not implicitly wipe the internal storage unless you exclusively select it.

@GokulNC, no there is no such directory. Oddly, in main directory I can only see directories which names start with "." (dot) or capital letters.

@GiantTree Oops. Yeah.. I didn't remember that properly I guess ;)

@greenoldman What recovery is it? If it's a custom recovery like TWRP or CWM or Philz, check for an option named 'Mount' and mount the 'External SD' and 'Data' partitions in it.

@GokulNC, no, it is regular boot recovery from Samsung (stock one).


text:
Android 4.4 keep booting into recovery mode
I just bought this phone, DOOGEE LEO DG280, weeks later, it keep booting into recovery mode even though I restart the phone. I tried reboot system now, apply update from sdcard, wipe data/factory reset and wipe cache partition, but it doesn't work at all. I can't find solution on the internet that helps me. Any idea about this?


text:
How to use my Phone as a wifi camera for my TV
I've got a Sony Xperia Z3 phone.  I'd like to use the video camera function and live-stream to my TV in another room.  So far my best success was using 2 phones with video conferencing and an MHL cable, but I won't always have access to a second phone.
I tried using the miracast option, which allows me to cast the screen, but this didn't work with the video camera.
My TV is a fairly modern Samsung, and I also have a raspberry pi I could connect via hdmi.
Does anyone know of a way to do this without significant additional hardware?


text:
Nexus 4 3G not working
The phone is running AOSP Marshmallow, it is rooted and has Xposed installed. Mobile operator is Latvian Mobile Phone with working data plan. I can send and receive calls and texts and use WiFi.
So far I've tried:

Turning radio on and off - failed
Rebooting - failed
Rebooting in safe mode - failed
Going to lollipop stock image - failed
Going to jellybean stock image - failed
Flashing radios - failed
Checking APN at the service center - failed
Replacing the SIM card - failed
Doing all the stuff mentioned above with the new SIM card - failed


text:
Does Android Jelly Bean supports NTFS SD card formatting?
If I format my micro SD card as NTFS, will my phone see it? I need this because I want to transfer files larger than 4GB on my phone microSD card, but FAT32 allows just files up to 4GB.

Can you just check?..

Honestly speaking, It depends on the manufacturer. As far as I am aware, the company has to get some license from Microsoft to include NTFS support. Speaking from experience, most (high-end) Samsung and HTC phones do while custom roms typically do not.
The only sure-shot method to confirm is by trying it out with an extra sd card...

I've already found an similar issue: SD card supported by Android 4.2.2
Here you would find this answer:

I have looked into this issue before, and as it stands at the moment,
  native android does not support exFAT or NTFS.
Support for additional formatting types are included in some ROMs
  because they have been specifically coded to do so such as AFAIK which
  I believe supports NTFS.
I think you are stuck with FAT32 unless you wish to root and flash a
  ROM that supports alternative formats.

Shortly, it seems it doesn't depend on manufacturer or Android version. It seems to be every Android phone may some issues with NTFS-formatted SD card.

Could exFAT be an option? It allows large files and some Android devices support it. Worth a try?


text:
Bluetooth earpiece spontaneously disconnects and reconnects while talking
I have an Xperia Z3 Compact phone and a Plantronics Voyager Edge bluetooth earpiece. Recently the earpiece sometimes (usually once or twice a day) spontaneously disconnects from the phone and immediately reconnects (which causes the audio to halt for a couple of seconds). It might also be happening not only when I'm talking, I can't tell.
The problem is I don't know if the problem is with the phone or with the earpiece.
I upgraded the earpiece to the latest firmware but it didn't help.
I don't have any other bluetooth devices to check the phone with or another phone to check the earpiece with.
Is there any way I can check it?


text:
Joining a public WiFi made the owner able to send me a Facebook friend request. How?
I walked by a bar with free, unsecured WiFi. My device auto-joined it, and a minute later I had a friend request on Facebook from that very bar.
How did they get my Facebook identity just from joining their WiFi? It feels a bit intrusive for them to do that, and honestly it makes me a bit paranoid about how much information about me is made available to the owner of the bar so easily.

Public WiFis are often unsecured. Everyone can then sniff on anyone else's traffic and analyse it using simple tools. Use VPNs if you want to secure your private data when on a public WiFi.

Unsecured WiFi doesn't fully explain it. Facebook is all-HTTPS, at least in the US. Some other mechanism(s) is/are at work. One possibility is that some app has associated your device WiFi MAC address (publicly visible to anyone in range regardless of TLS, VPN, etc.) with your Facebook account, and the bar (or someone in it) had access to that association.

Not enough rep for comment, sadly - but my guess is that this could be Facebook beacon (not necessarily BT, they work with WiFi too).


text:
Micro SD Card Not Detecting
I am Using a Android phone Sony Z3 (5.0 - Lollipop), the Issue is My SD Card My Micro SD Card is not detecting in mobile and PC
Let me tell u clearly what i have done step by step?

Encryption (Phone & SD Card)
Factory Reset the Phone
Again Encryption but this time i didn't find the option of Encrypt SD Card. so only phone encrypt completed.

I tried to find the files in SD then i realize my SD is not detected then tried to put in pc its asking to format.
Please suggest i have backup in SD.

I am afraid your back up SD data cannot be read. Reasons

On doing factory reset your , encryption keys are lost. Which includes encryption of your external SD card and without this keys, possible to access contents.   Quoting from linked source (which incidentally advocates this method (encryption + Factory Reset ) as keeping information away from buyers, if you sell your phone)

Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.

Even assuming that you had an unencrypted SD card and wanted to fix the problem of not being able to read it, the very fact that neither your phone not PC can read it makes it nearly impossible to obtain data. You can still try to diagnose using this useful flowchart https://android.stackexchange.com/tags/external-sd/info. This is more for information and structured way of diagnosing SD card issues


text:
How to tell if phone's ROM is original or tampered?
I have bought a new phone which seems to be used. The manufacturer checked my IMEI and confirmed that the phone has been purchased/activated before.
The body looks new so I don't mind keeping it but I am worry about malicious software/apps. I know I can factory reset the phone, but is there any way to tell if the ROM is original?
FYI, the phone is a Moto G 2nd gen w/ 5.0.1 lollipop.

if your bootloader is unlocked by default, you can boot into download mode, and you will see KNOX warranty void: x on the top. Values are either 0 or 1 dependent on if it is tampered or not. Doing OTA updates SHOULD also switch to normal android OS, unless the hacker managed to make OTA updates download from his repository

It depends on what you meant by "tampered". Do you consider using custom ROM (e.g. CyanogenMod) as "tampered"? Or to put it simply, do you mean original ROM as "stock ROM" (the one from factory)?

Which phone? Model?

@AndrewT. Yes, I mean stock ROM/factory's ROM.

@beeshyams I had included that in the tags but it was removed, added it to the body now.

I am assuming your device is NOT rooted by you
You can

Factory reset your device (of course after taking back up of data )
Root your device, flash a custom recovery and take a complete back up of your device with TWRP
Generate MD5 check sum using TWRP or alternate apps like Hash Stamp MD5 & SHA1 generator
Download stock lollipop (assuming that your device variant matches with that mentioned and the ROM version on your device matches)
Generate and verify stock MD5 and SHA1 with TWRP nandroid back up
If it matches, it is confirmed both are same and no tampering took place
If not flash only kernel from TWRP, and generate MD5 and SHA1. Repeat with downloaded image and verify
Repeat above with /sys and /data
This should pinpoint the tampering that happened

It is a little tedious but IMO, worth the effort as it proves beyond doubt that either present ROM has not been tampered with or if tampered, in which portion (s) of the ROM it happened. This may not be a practical solution but is based on the premise that (near) fool proof validation is only possible when compared with original stock ROM. Other variations of this could be  see if OTA updates work or comparing partition sizes

The irony here is that if OP is already going to download stock ROM and flash TWRP, then why not simply flash the stock ROM and be at peace, because figuring out file integrity isn't worth anything at that point. Of course, there can be a possibility where the new owner would like to return the device, should the integrity be found compromised, but that doesn't appear to be the case here.

@Firelord..absolutely agree but from an academic perspective to my mind, this is the only sure way of  knowing, addressing the "how" portion of the question. I will wait with interest to see if there is an alternative way which gives equal assurance and unless OP declines this as not a viable option, it stays as an answer.  I have researched ways ever since this Q appeared as non-featured and saw nothing that gives full assurance (of course, I could have missed in not exploring alternatives). Explaining at length to address similar concerns from others

I don't think that the checksums would match even if the backed up ROM was backed up from a clean stock ROM as the files are completely different. The stock update file is probably of EXE type, while the backup is IMG or ZIP. The contents are also different internally because the OEM packs files diferently than a recovery, therefore it is probably impossible that a nandroid backup has the same hash value as an update file.

TheBro21's comment applies only if it's a KNOX enabled device.  For most Android devices, when you boot into downloading mode it will read a few lines in "SYSTEM STATUS: custom" or "Custom Binary Download YES (and the number of time here, if it hasn't be reset with triangle away)". If in bootloader mode it says Unlock state: true, it might be that the ROM is custom, but then again it may have been done by a stock flash.
You can also go into the settings and about and look at the system status, ROM, kernel, or base-band and if it has a weird name, google it, it's probably a custom ROM or kernel, if not, it probably isn't or close enough you'd never notice.
If you really are concerned and want a fresh device on official firmware, google how to flash your device with Odin, than download the latest stock firmware.

That's not enough. I would flash the stock bootloader and recovery if possible too

How to tell if phone's ROM is original or tampered?

This is how I would proceed. If the official stock ROM is available from trusted sources, you can download it and verify the integrity of the binaries on your phone by comparing it's MD5/SHA checksums with that of the one you downloaded.
But in your case, if the official ROM is available you could simply flash it and you can use your phone safely. But in case the ROM is not available(or even if it is available), the most safest option for you is to download the Official CyanogenMod ROM for your device and flash it. It will keep your phone free of "malicious software/apps."

To check if it is tampered - very hard. There are ways with calculating the checksum but I don't know will it work for sure. But, if you want to be 100% sure it was not tempered, I would suggest to manually download the official ROM and flash it. This does not void your warranty and AFAIK all phones can be manually flashed with official software.

This doesn't answer the question at all and "if you want to be 100% sure it was not tempered, I would suggest to manually download the official ROM and flash it." isn't making any sense. How would flashing the ROM would verify that previous was tampered with? You're simply wiping out all the evidence here.

Update file doesn't have the same checksum as the nandroid backup - not a valid check.

Root checkers and other indicators can be easily modified and set by other (maybe malicious) methods, making them also not good proofs.

My answer is no, there is NO WAY to be 100% sure that the ROM hasn't been tempered with. The only way is to download the update, compare checksums of the downloaded file with that on the website, and flash it.
Maybe my previous answer wasn't clear enough.

@Chapz I am a newbie. I searched the internet but I couldn't find the stock ROM on Motorola websites, I could only find it on third-party websites. is it possible to get it from the Motorola? also, would flashing it wipe the phone's memory clean?

Link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
You need to log in with your Google account or make a Motorola account, and you can download firmwares from their site. Flashing an entire ROM wipes it clean so do make a backup of your files.

Thanks @Chapz! how should I "full wipe" the phone and install the stock ROM? should I use a third-party flash tool, or is there one from Motorola or Google? also will I be able to get OTA updates normally after this?

Unfortunately, this goes beyond my knowledge, you can just google it as I would do it. The full wipe happens when you install the ROM, as it reinstalls all the partitions on your phone. OTA updates should not be a problem as the ROM is official, only difference is that you installed it in a different way.

I couldn't find Moto G's ROM on that link. what do you think about getting it from OTA's cache?

I don't have any knowledge on that one, sorry...


text:
Where is the "Episodes" button on Pandora's Android app?
In the "Serial" podcast on Pandora, welcome instructions are provided that tell people to press the Episodes button to be able to change episodes or seasons (e.g. to go back to Episode 1 when Pandora decides to start with Episode 2 for some strange reason).
I see the Episodes button when using the web app in a PC browser, but can't find it anywhere in the Android app (which does behave strangely in how it jumps around sometimes), though I still get the instructions to push the Episodes button.  Where is it in the Android app?


text:
All texts grouped under own phone number
I have android 4.4.4, using republic wireless.
For some reason, all of my texts are being grouped under my own phone number, and instead of being identified as my contacts, only the senders phone number is identified:

Usually each person's texts would come in under a tab with their own name, or just a phone # if they aren't a contact. Instead, all of the texts are under a tab that just shows my phone number, like they're being forwarded or something, and instead of showing the name of the person sending it just has their phone number.
I initially started having the problem when I was using hangouts as my text messaging service, although I was using it for a while that way without this problem. When it started happening, I tried downloading google's messenger app, but it is still doing the same thing.
Any idea why this is happening?


text:
one way sync gmail contacts to galaxy s6
Is there a way to do a one way sync of my Gmail contacts to my phone? I want changes to my Gmail contacts to update on the Galaxy S6 but I do not want the changes on the phone to edit my Gmail contacts. In the account settings I turn the sync option off, but then it wont get my updates from Google when they are made. Is it possible to set this up or is it stuck as a two way sink?


text:
How do I force reinstallation of an apk with different signature on rooted Android?
Normally I can reinstall (preserving application data) APK only when it's signature matches the previous one.
How do I force upgrading of the application signed with a different key (for example, from a distribution version to a self-compiled version, for example) without removal of the data (i.e. uninstallation) using root access?
Workaround is backup application's data + uninstall + install + restore data, but that is inconvenient and notifies other applications about [un]installation which is not intended.
Ideally this should be a one-off exception that I personally approve, not just disabling of the whole signature verification mechanism.

Patch the system to ignore the signature when installing an application. Apps like LuckyPatcher allow that.

What about replacing the APK in /data/app followed by a soft/full reboot?

A reboot is also inconvenient. I want seamless switching between development and repository versions.

In this case: Sign the development version with the same signature as your production version. Works like a charm.

I don't have the key for production, also F-Droid signs applications with it's own key. The workflow is: 1. Install app from F-Droid, 2. Want to contribute a fix/feature, so built from source; 3. Installed from source, tested, etc; 4. The fix is finally upstream. Self-built version is no longer needed; 5. Want to update app from F-Droid again.

You'll need to disable app signature verification. As @GiantTree said, Lucky Patcher is an app which allows this to be done.

Will it still warn on signature mismatch with this Lucky Patcher? I want it to be "Prompt" rather than "Always allow".

You can use an app called 'Lucky Patcher' witch contains many system tweaks, (root and busybox are required) then follow the following steps:

Go to 'Toolbox' tab in the buttom.
Select 'Patch to Android'.
Check 'Disable signature verification in the package manager'.
Press 'Apply' and wait for your phone to reboot.

and that's it. 'Lucky Patcher' also has an Xposed module to do the same task if Xposed is already installed in your system.

Use XInstaller, you need root.
you also need Xposed to activate XInstaller.
When all set up, go to XInstaller and choose installation, then choose Checking signatures. When you're done, always remember to enable checking signatures.
Here's download links:
Xposed installer and XInstaller

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


text:
Can't get adb on Macbook to see Pixel C
I'm trying to connect my 2014 Macbook pro to a Pixel C tablet. The tablet  has developer settings enabled, usb debugging enabled and unknown sources enabled. 'adb devices' shows nothing and there is no debug icon shown on the tablet.
I'm using a usb 3 type C connector that works Perfectly from my Macbook to my Nexus 5x
I've tried resetting the PRAM/NVRAM and the SMC to no avail.
The strangest thing is that we have 3 developers here with 2 ports per macbook. It does work on ONLY 1 port on one macbook, a 2015. We have a second exact same macbook bought on the same day that this tablet doesn't work on either.
Since it works on 1 port on one macbook, we know that the tablet is configured correctly for debugging. But why can't we connect it to the second port on the same machine or to another macbook??
We've never had any issues connecting any other Android device to any of these macbooks before.
Updates:

Got a different usb C cable and still have same issue.
Default USB Configuration (from Dev Options) is MTP, tried other USB config PTP and didn't help
After testing again on the 1 port that it worked in the past, trying 'adb devices' shows the Pixel C about 3 out of 5 times (in the span of 10 seconds). Trying to deploy to the device fails every time, presumably due to the flakey connection...

Is it plugged in to a USB 2.0 port? I have had issues similar to this when I plugged it into the Apple keyboard rather than the built-in ports of my MBP

@TheBro21, I checked and all the usb ports on the 2014 and 2015 macbook pros are usb 3.0

I am not a user of adb as much, but isn't there some sort of USB driver for your device? You might want to try to download it over an official site or if it came with adb. I used Heimdall to flash recovery and it had a kext to install so it detects my device.

@TheBro21, OS X doesn't require ADB drivers. Please refer Google's official documentation.

@Firelord , you very well understand what I mean. A computer can recognize and operate the ADB protocol with a  device if it has a driver for the device which exposes the ADB interface to the device over USB. That's what we refer to when we say ADB drivers. TheBro21 refers to Heimdall as requiring a kext (kernel extension, an OS X term for drivers, among other things), which is Samsung specific, and completely N/A for the OP who has a Pixel C (which was released in 2015,BTW) with Tegra X1 hardware, nothing Samsung specific at all, hence nothing Heimdall/ODIN-related is applicable here.

@TamoghnaChowdhury,  alright, so I'll be flushing out my comments in 60 seconds. Kinda realized that they don't add any value to the question. I request you to do the same for those directed to me. Thanks! Flag this for removal, in case I forget to remove.

To see if the mac actually maps the device: First unplug all devices except mouse (or keyboard). Then type ls /dev/ | grep usb into the command line. You should see no output. Upon plugging phone in, rerunning ls /dev/ | grep usb should return something like cu.usbmodemxxxxx, with possibly another one with tty instead of cu

@TheBro21, I don't get any output from the ls /dev/ | grep usb command you provided, either with or without the Pixel C connected. But... when I plug in the Nexus5x with a USB type C, even though adb devices shows it, the ls /dev/ | grep usb command given doesn't show any output either. I also tried it with only a Nexus 9 (standard usb) connected, and adb shows the device, but nothing from the ls command.

What brand USB-C cable are you using? We were having similar issues with our Macbooks (2013 and 2015). We just got some F-Color brand cables, and USB debugging popped up immediately. Maybe give those a shot?

@rare_exception, turned out that even though USB 3 is supported on both devices, only USB 2 currently works as far as I've seen.

I have tried a number of USB 3.0 cables with no luck but every high quality USB 2.0 cable I've tried has worked for me. This includes USB 2.0 cables that have a Type C connector (There are many of these on Amazon. I'm currently using an "iOrange" brand cord) as well as traditional micro-usb cables with a Type C adapter ("TechMatte USB-C to Micro USB Adapter").
I'd prefer faster charging and better speeds but this takes care of my debugging needs reliably.

Ok, I've got my order on the way from http://www.amazon.com/iOrange-E-Braided-Reversible-Connector-ChromeBook/dp/B010VFFU1W. I hope this works @goto10! Otherwise, if you're just trying to get me to order your product from Amazon... nicely played. Also, nice Google Glass picture Playa!

You're right! Tried 2 different USB 3 cables and they didn't work, (although they both work on my Nexus5x) but the USB 2 that you recommended worked perfectly! I wish I could have given you the bounty that I had on here a while back, it went unclaimed.

Unfortunately, I've found that rebooting the mac will cause the adb to recognize phones through the usb-c, even if I later unplug and plug it in again. Eventually, something happens and it stops working until I reboot.

This was my situation too. I have the cable mentioned in the other post, which has always seemed temperamental, but restarting solved it for me this time


text:
G4 - Bluetooth headset and multiple media player
I have LG G4, 5.1. It came with "Audio" player pre installed. however, I use Poweramp. It works fine 90% of the time. However, occasionally, when I have my BT headset on (LG HBS 750), and press play nothing will happen. At other times, the other media player will start playing. Is there a way to kill any other music players besides poweramp and have my BT send commands directly to poweramp only?


text:
What does this "N" icon represent (not NFC)

I haven't been able to find it in any icon lists, and the NFC icon drowns out other search results.
Galaxy S6, Android 5.1.1

Where does it show up in your S6? Give us the full screenshot.

@Firelordi just figured it out by checking my notifications area. Probably should have done that first, but I'm new to this android thing and still figuring it out. Anyway at least there's a Google-able answer available :)

I just figured out that it is the icon for "Netflix"


text:
Run a particular app on boot
I have a phone running Android 4.0 and I wish to know if it is possible to turn this phone into a dedicated calculator? When I say dedicated I mean - once the phone is turned on, it boots directly to a calculator GUI? Whereby the user can immediately starting using the calculator, just like any stock standard Android calculator app would look like.
I do not wish it to boot to a home screen in between, but directly to the calculator itself. I am using a very simple example here, in anycase, would this be possible?

This is surely possible. You could first flash a custom recovery like TWRP, then make a Big cut in the stock firmware, removing any unneeded features, and then making the Calculator boot. However I am not sure about how difficult it might be. After wiping System partition and flashing the complete zip file, then it should boot to calculator

I edited the title to reflect the issue, but if it's not correct, feel free to [edit] it again. The alternative is to launch calculator on boot using [tag:automation] apps like [tag:tasker]. It's certainly possible, but the phone still need to boot the Android and do the initialization (which may take some time depends on your phone and apps installed).

Tasker might be the way to go, but if you want the device to be a on-go calculator I think you'll have to look at a dedicated calculator. Android simply doesn't have that on-go boot process. It'll take some time to turn on

Use kiosk-mode. It would save you the trouble of booting into your typical home screen first and then to Calculator.

First, I'd like to point out that turning on is different than booting.  That said, I have a suggestion that will work if you are talking about turning the device on and off:
Use the Pin Screen feature of Android 5.0 (Lollipop). To do this, screen pinning must be enabled in Settings->Security. Once enabled, start Calculator (or any app) and then hit the "app switcher" button. This is done differently depending on what phone you have and tweaks you may have applied.  On my device, it's done by double-tapping the home key. When you are in app switcher view, touch the push pin icon on whatever app you want pinned.
Once pinned, Calculator will be the only app that can be used. If you turn the device off and on again, you will be right back at Calculator.
Note that the pin will not persist across reboots, hence the caveat.

OP is using Android 4.0 however.

Oops. Not sure how I missed that.

It is very much possible to turn an Android phone into a dedicated device, or kiosk, and allow access to only one application, e.g. a Calculator. There are many commercial applications available on google play like SureLock which provides lockdown solution.
Such a lockdown will ensure that the user cannot access any other applications, device settings, and even the hardware keys can be disabled.
Whenever the phone is turned on or restarted, it will boot directly to a calculator rather than the regular device home screen.


text:
Get other's WhatsApp chat history remotely
Is it possible to transfer the WhatsApp data of someone's phone without having access to their phone? Or alternatively, can I view their chat history remotely?

I removed the background because it's too private. Without access to their phone, you can't. If their WhatsApp is set to backup the chats, then you probably can access it from their Google Drive (but you need to know their account).

And what legitimate reason is here to do that?

This is not possible without breaking the law. Whats app uses a store and forward mechisnism, that means the messages are stored on the server then forwarded on to the client (i.e the persons phone you are talking to).
The only way to get access to the data on their phone or the whatsapp server is with a court order.
You will be able to see any conversation you have had with them on whatapps, but nothing more.

Find out where they have backed up their data, on the cloud or in their sd cards, then you'll have to retrieve the data and you are good to go.


text:
Retrieve WiFi password
How to get saved WiFi password from my android 5.1.1  without rooting?
I checked the path /data/misc/wifi/ using adb pull from terminal, but it's empty

You can't get the passwords without root access because shell (adb) is not privileged to access the file containing those passwords. As you would know, the file wpa_supplicant.conf contains all the saved Wi-Fi passwords. In order to even ascertain the existence of that file, you must have read or executable permission until wifi directory. It just happened that the permissions on that directory is drwxrwx---, is owned by user wifi and  group wifi. Executing id tells us that shell is not part of wifi group, so it ultimately would be considered others. As you can see, the permissions for others are blank --- i.e. no read/write/execute permission is available, hence, you can't enter that directory, let alone copy a particular file residing inside it.
Root the device if you want that file badly.
Related reading: File permissions and attributes

I have to say I am surprised that the answer to this is hidden so well on the internet.
It is a myth that retrieving the WiFi passwords from an unrooted device is impossible.
Prerequisites:

developer mode activated on android device
USB debugging (in activated developer options)
USB data cable
adb (on host computer)
java (on host computer)
an archiver such as winzip or 7zip (can be skipped on Unix systems)

These prerequisites may differ depending on operating system. android version and manufacturer. Answers on how to prepare these on your specific platform can be easily obtained with a search on your favourite search engine. Keep in mind that a USB cable that is good for charging your phone not necessarily provides a data connection. Use the cable that came with your phone if in doubt.
Steps:

Connect your phone to the host computer using the USB data cable
Backup your WiFi passwords with adb (from command line).
adb backup com.android.providers.settings

Enter a password for the file on your phone. The resulting file will be named "backup.ab" and appear in the directory where you executed adb.
Download and install Android Backup Extractor.
Convert the backup file into a TAR archive using the password that you entered earlier:
java -jar abe.jar unpack backup.ab backup.tar *password*

The archive will contain a file called "flattened-data". This file contains all networks that are saved on your phone. The psk entries are the passwords.

Notes:
It may be easier to move the backup file into the same directory as abe.jar before converting it.
Tested on Android 7 and Ubuntu, adb version 1.0.36, android-backup-extractor v20180521. If adb doesn't work, make sure you device is found using adb devices. On the same device, I tried to access the passwords directly using adb pull which didn't work (as was expected).

On which device did you test this?

@Firelord That would have been an LG G5 (H860N). I think the reason of doing so was to access a stored wifi password to use it on a laptop or it was to access a mifi-device that didn't have a reset button, probably the latter.

Hi @life-on-mars, when I unpack I got the tar file but it is empty. We have the same version of the extractor v20180521 and I copied the .ab file to the android-backup-extractor directory. What am I missing?

@Ralph my first guess would be compatibility problems with the adb or android version your tried this on. There is a github page for the extractor with a slightly newer version and additional info. Perhaps you can get answers there.

Reading memorized wifi passwords by device is only possible if you have a rooted device. There are two methods to do it.
1)You can do it manually by pulling file wpa_supplicant.conf
Or
2)By simply using applications like wifi password by farproc on play store. Install app, grant root permission and it will automatically show you all saved wifi passwords.

@Firelord is right but there's a file browser for Android that doesn't require root for some IO operations, and looking from the path for the saved passwords it should have full rights. It's called XPlorer, hope this helps

"looking from the path for the saved passwords it should have full rights." -- I take it as you've not verified your own answer. Please verify it because the app shouldn't be able to access the file or last-level directory per my answer. Hope this helps.

@Firelord works perfectly fine on my nexus testing phone on CyanogenMod 10 and my San Francisco phone on Lollipop.

I see. Can you verify that the permissions I explained in my answer for the relevant file and directory are the same in your devices? Furthermore, have you verified that the app in both CM10 and San Francisco phone doesn't have root access?

@Firelord Yup they are, and my CM12 phone has root access, but my SF phone doesn't (I keep a vanilla android phone for testing too)

I tried the app you mentioned on Nexus 5, Android 6 (stock, rooted), but I couldn't even access /data folder; it gave "permission denied". Could you clarify which location you get the saved passwords, and possibly also the permission?

The location is indeed /data/misc/wifi... What phone do you have? All I can think is that your phones manufacturers have blocked it.

@SyntaxBit All I can think of is that the provider of your San Francisco has messed up the ROM. That file shouldn't be accessible by any user app, as it would mean a serious security flaw. Would you use a password store for your personal passwords which is accessible for everyone in plain text? What sense do passwords make then?


text:
Google Play Store crashes on Amlogic Android TV
I have install Google Play Store (via flashing a GApps package through custom recovery) in an Amlogic Android TV device but after 2-3 reboots it keeps crashing.
Here are logs from adb logcat:
I/ActivityManager(  494): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.android.vending/com.google.android.finsky.activities.MainActivity} from pid 2306
I/ActivityManager(  494): start package name is com.android.vending, class name is com.google.android.finsky.activities.MainActivity, error code is 0
I/dalvikvm( 2306): Could not find method android.app.Activity.finishAfterTransition, referenced from method android.support.v4.app.FragmentActivity.onBackPressed
W/dalvikvm( 2306): VFY: unable to resolve virtual method 104: Landroid/app/Activity;.finishAfterTransition ()V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0012
W/dalvikvm( 2306): VFY: unable to find class referenced in signature (Landroid/view/SearchEvent;)
I/dalvikvm( 2306): Could not find method android.view.Window$Callback.onSearchRequested, referenced from method android.support.v7.internal.view.WindowCallbackWrapper.onSearchRequested
W/dalvikvm( 2306): VFY: unable to resolve interface method 9350: Landroid/view/Window$Callback;.onSearchRequested (Landroid/view/SearchEvent;)Z
D/dalvikvm( 2306): VFY: replacing opcode 0x72 at 0x0002
I/dalvikvm( 2306): Could not find method android.view.Window$Callback.onWindowStartingActionMode, referenced from method android.support.v7.internal.view.WindowCallbackWrapper.onWindowStartingActionMode
W/dalvikvm( 2306): VFY: unable to resolve interface method 9354: Landroid/view/Window$Callback;.onWindowStartingActionMode (Landroid/view/ActionMode$Callback;I)Landroid/view/ActionMode;
D/dalvikvm( 2306): VFY: replacing opcode 0x72 at 0x0002
I/dalvikvm( 2306): Failed resolving Lcom/google/android/play/drawer/PlayDrawerLayout$1; interface 1305 'Landroid/view/View$OnApplyWindowInsetsListener;'
W/dalvikvm( 2306): Link of class 'Lcom/google/android/play/drawer/PlayDrawerLayout$1;' failed
E/dalvikvm( 2306): Could not find class 'com.google.android.play.drawer.PlayDrawerLayout$1', referenced from method com.google.android.play.drawer.PlayDrawerLayout.onFinishInflate
W/dalvikvm( 2306): VFY: unable to resolve new-instance 6664 (Lcom/google/android/play/drawer/PlayDrawerLayout$1;) in Lcom/google/android/play/drawer/PlayDrawerLayout;
D/dalvikvm( 2306): VFY: replacing opcode 0x22 at 0x0030
I/dalvikvm( 2306): Failed resolving Lcom/google/android/play/drawer/PlayDrawerLayout$1; interface 1305 'Landroid/view/View$OnApplyWindowInsetsListener;'
W/dalvikvm( 2306): Link of class 'Lcom/google/android/play/drawer/PlayDrawerLayout$1;' failed
D/dalvikvm( 2306): DexOpt: unable to opt direct call 0x94c8 at 0x32 in Lcom/google/android/play/drawer/PlayDrawerLayout;.onFinishInflate
W/dalvikvm( 2306): VFY: unable to find class referenced in signature (Landroid/view/WindowInsets;)
I/dalvikvm( 2306): Could not find method android.view.WindowInsets.getSystemWindowInsetLeft, referenced from method com.google.android.finsky.layout.InsetsFrameLayout.onApplyWindowInsets
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9371: Landroid/view/WindowInsets;.getSystemWindowInsetLeft ()I
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0020
I/dalvikvm( 2306): Could not find method android.view.View.dispatchApplyWindowInsets, referenced from method com.google.android.finsky.layout.InsetsFrameLayout.onApplyWindowInsets
W/dalvikvm( 2306): VFY: unable to resolve virtual method 8973: Landroid/view/View;.dispatchApplyWindowInsets (Landroid/view/WindowInsets;)Landroid/view/WindowInsets;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0071
I/dalvikvm( 2306): Could not find method android.view.WindowInsets.consumeSystemWindowInsets, referenced from method com.google.android.finsky.layout.InsetsFrameLayout.onApplyWindowInsets
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9369: Landroid/view/WindowInsets;.consumeSystemWindowInsets ()Landroid/view/WindowInsets;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x007b
I/dalvikvm( 2306): Could not find method android.widget.FrameLayout.<init>, referenced from method com.google.android.finsky.layout.SpacerHeightAwareFrameLayout.<init>
W/dalvikvm( 2306): VFY: unable to resolve direct method 9808: Landroid/widget/FrameLayout;.<init> (Landroid/content/Context;Landroid/util/AttributeSet;II)V
D/dalvikvm( 2306): VFY: replacing opcode 0x70 at 0x0000
D/TextLayoutCache( 2306): Using debug level = 0 - Debug Enabled = 0
I/dalvikvm( 2306): Could not find method android.content.Context.getColor, referenced from method android.support.v4.content.ContextCompat.getColor
W/dalvikvm( 2306): VFY: unable to resolve virtual method 413: Landroid/content/Context;.getColor (I)I
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0006
I/dalvikvm( 2306): Could not find method android.content.Context.getDrawable, referenced from method android.support.v4.content.ContextCompat.getDrawable
W/dalvikvm( 2306): VFY: unable to resolve virtual method 417: Landroid/content/Context;.getDrawable (I)Landroid/graphics/drawable/Drawable;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0006
D/dalvikvm( 2306): GC_FOR_ALLOC freed 686K, 24% free 7774K/10188K, paused 45ms, total 45ms
I/dalvikvm-heap( 2306): Grow heap (frag case) to 7.884MB for 281896-byte allocation
D/dalvikvm( 2306): GC_FOR_ALLOC freed 2K, 24% free 8047K/10464K, paused 41ms, total 41ms
I/dalvikvm( 2306): Could not find method android.view.ViewAnimationUtils.createCircularReveal, referenced from method com.google.android.play.search.PlaySearch.onActionViewExpanded
W/dalvikvm( 2306): VFY: unable to resolve static method 9155: Landroid/view/ViewAnimationUtils;.createCircularReveal (Landroid/view/View;IIFF)Landroid/animation/Animator;
D/dalvikvm( 2306): VFY: replacing opcode 0x71 at 0x002d
E/HAL     ( 2642): load: module=/system/lib/hw/keystore.amlogic.so
E/HAL     ( 2642): dlopen failed: could not load library "libamlkeymaster.so" needed by "keystore.amlogic.so"; caused by library "libamlkeymaster.so" not found
E/keystore( 2642): could not find any keystore module
E/keystore( 2642): keystore keymaster could not be initialized; exiting
I/dalvikvm( 2306): Could not find method android.view.ViewAnimationUtils.createCircularReveal, referenced from method com.google.android.play.search.PlaySearchToolbar$2.onModeChanged
W/dalvikvm( 2306): VFY: unable to resolve static method 9155: Landroid/view/ViewAnimationUtils;.createCircularReveal (Landroid/view/View;IIFF)Landroid/animation/Animator;
D/dalvikvm( 2306): VFY: replacing opcode 0x71 at 0x0055
E/dalvikvm( 2306): Could not find class 'android.app.ActivityManager$TaskDescription', referenced from method com.google.android.finsky.layout.actionbar.ActionBarHelper.syncState
W/dalvikvm( 2306): VFY: unable to resolve new-instance 30 (Landroid/app/ActivityManager$TaskDescription;) in Lcom/google/android/finsky/layout/actionbar/ActionBarHelper;
D/dalvikvm( 2306): VFY: replacing opcode 0x22 at 0x00e4
I/dalvikvm( 2306): Could not find method android.view.Window.setStatusBarColor, referenced from method com.google.android.finsky.layout.actionbar.ActionBarHelper.syncState
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9368: Landroid/view/Window;.setStatusBarColor (I)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x01b8
D/dalvikvm( 2306): DexOpt: unable to opt direct call 0x009b at 0xfa in Lcom/google/android/finsky/layout/actionbar/ActionBarHelper;.syncState
D/Finsky  ( 2306): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80430500] >= Server Version [-1]
D/dalvikvm(  871): GC_CONCURRENT freed 643K, 23% free 2886K/3708K, paused 1ms+3ms, total 23ms
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
D/libEGL  ( 2306): loaded /system/lib/egl/libGLES_mali.so
D/OpenGLRenderer( 2306): Enabling debug mode 0
I/dalvikvm( 2306): Could not find method android.widget.ImageView.drawableHotspotChanged, referenced from method com.google.android.play.image.FifeImageView.drawableHotspotChanged
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9894: Landroid/widget/ImageView;.drawableHotspotChanged (FF)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6f at 0x0000
D/dalvikvm( 2306): GC_FOR_ALLOC freed 345K, 21% free 8331K/10464K, paused 37ms, total 37ms
I/qtaguid ( 2306): Failed write_ctrl(u 55) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 55 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(55) failed with errno -22
D/Finsky  ( 2306): [1] UpdateWidgetsReceiver.onReceive: Updated 0 MarketWidgetProvider widgets (com.google.android.finsky.action.TOC_SET)
D/Finsky  ( 2306): [1] UpdateWidgetsReceiver.onReceive: Updated 0 RecommendedWidgetProvider widgets (com.google.android.finsky.action.TOC_SET)
D/Finsky  ( 2306): [1] UpdateWidgetsReceiver.onReceive: Updated 0 NowPlayingWidgetProvider widgets (com.google.android.finsky.action.TOC_SET)
I/dalvikvm( 2306): Could not find method android.content.res.Resources.getDrawable, referenced from method android.support.v7.internal.widget.ResourcesWrapper.getDrawable
W/dalvikvm( 2306): VFY: unable to resolve virtual method 668: Landroid/content/res/Resources;.getDrawable (ILandroid/content/res/Resources$Theme;)Landroid/graphics/drawable/Drawable;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0002
I/dalvikvm( 2306): Could not find method android.content.res.Resources.getDrawableForDensity, referenced from method android.support.v7.internal.widget.ResourcesWrapper.getDrawableForDensity
W/dalvikvm( 2306): VFY: unable to resolve virtual method 670: Landroid/content/res/Resources;.getDrawableForDensity (IILandroid/content/res/Resources$Theme;)Landroid/graphics/drawable/Drawable;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0002
D/Finsky  ( 2306): [1] BaseWidgetProvider.onReceive: Received ACTION_APPWIDGET_UPDATE, updating 0 widgets.
D/Finsky  ( 2306): [1] InstallerImpl.kick: Installer kick - starting com.google.android.gms
I/ActivityManager(  494): Displayed com.android.vending/com.google.android.finsky.activities.MainActivity: +664ms (total +734ms)
W/Settings( 2306): Setting download_manager_max_bytes_over_mobile has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
D/Finsky  ( 2306): [1] GaiaRecoveryHelper.prefetchAndCacheGaiaAuthRecoveryIntent: Skipping fetching recovery intent -- gaia recovery disabled
W/dalvikvm( 2306): Unable to resolve superclass of Landroid/support/v4/app/FragmentTransitionCompat21$3; (1239)
W/dalvikvm( 2306): Link of class 'Landroid/support/v4/app/FragmentTransitionCompat21$3;' failed
E/dalvikvm( 2306): Could not find class 'android.support.v4.app.FragmentTransitionCompat21$3', referenced from method android.support.v4.app.BackStackRecord.configureTransitions
W/dalvikvm( 2306): VFY: unable to resolve new-instance 410 (Landroid/support/v4/app/FragmentTransitionCompat21$3;) in Landroid/support/v4/app/BackStackRecord;
D/dalvikvm( 2306): VFY: replacing opcode 0x22 at 0x01a4
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
I/dalvikvm( 2306): Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.BackStackRecord.setBackNameOverrides
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9032: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0020
I/dalvikvm( 2306): Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.BackStackRecord.setNameOverrides
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9032: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0013
I/dalvikvm( 2306): Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.BackStackRecord.addSharedElement
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9032: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0004
W/dalvikvm( 2306): Unable to resolve superclass of Landroid/support/v4/app/FragmentTransitionCompat21$3; (1239)
W/dalvikvm( 2306): Link of class 'Landroid/support/v4/app/FragmentTransitionCompat21$3;' failed
D/dalvikvm( 2306): DexOpt: unable to opt direct call 0x0890 at 0x1a6 in Landroid/support/v4/app/BackStackRecord;.configureTransitions
D/Finsky  ( 2306): [1] MainActivity.onReady: Optimistically fetching billing countries.
D/Finsky  ( 2306): [1] BaseWidgetProvider.onReceive: Received ACTION_APPWIDGET_UPDATE, updating 0 widgets.
I/dalvikvm( 2306): Could not find method android.view.ViewPropertyAnimator.z, referenced from method com.google.android.play.headerlist.PlayHeaderListLayout.setHeaderShadowVisible
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9321: Landroid/view/ViewPropertyAnimator;.z (F)Landroid/view/ViewPropertyAnimator;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0037
I/dalvikvm( 2306): Could not find method com.google.android.play.headerlist.PlayHeaderStatusBarUnderlay.setOutlineProvider, referenced from method com.google.android.play.headerlist.PlayHeaderListLayout.configure
W/dalvikvm( 2306): VFY: unable to resolve virtual method 38489: Lcom/google/android/play/headerlist/PlayHeaderStatusBarUnderlay;.setOutlineProvider (Landroid/view/ViewOutlineProvider;)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x01d5
W/dalvikvm( 2306): VFY: unable to find class referenced in signature (Landroid/view/WindowInsets;)
I/dalvikvm( 2306): Could not find method android.view.WindowInsets.getSystemWindowInsetTop, referenced from method com.google.android.play.headerlist.PlayHeaderListLayout.onApplyWindowInsets
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9373: Landroid/view/WindowInsets;.getSystemWindowInsetTop ()I
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0000
D/Finsky  ( 2306): [1] BaseWidgetProvider.onReceive: Received ACTION_APPWIDGET_UPDATE, updating 0 widgets.
I/qtaguid ( 2306): Failed write_ctrl(u 62) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 62 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(62) failed with errno -22
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
I/qtaguid ( 2306): Failed write_ctrl(u 55) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 55 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(55) failed with errno -22
D/Finsky  ( 2306): [1] DownloadImpl.setState: Duplicate state set for 'com.google.android.gms' (0). Already in that state
D/Finsky  ( 2306): [1] DownloadQueueImpl.add: Download com.google.android.gms added to DownloadQueue
D/Finsky  ( 2306): [1] DownloadImpl.setState: com.google.android.gms from 0 to 1.
I/installd(  136): free_cache(22795155) avail 5437329408
D/Finsky  ( 2306): [1] StartNextDownloadRunnable.run: Download com.google.android.gms starting
I/qtaguid ( 2306): Failed write_ctrl(u 62) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 62 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(62) failed with errno -22
D/Finsky  ( 2306): [152] DownloadQueueImpl$7.run: Enqueued com.google.android.gms as content://downloads/my_downloads/3
D/Finsky  ( 2306): [1] DownloadImpl.setState: com.google.android.gms from 1 to 2.
D/Finsky  ( 2306): [1] DownloadQueueImpl.onStart: com.google.android.gms: onStart
W/dalvikvm( 2306): Unable to resolve superclass of Lcom/google/android/finsky/layout/ControlsContainerBackgroundCoordinator$2; (1325)
W/dalvikvm( 2306): Link of class 'Lcom/google/android/finsky/layout/ControlsContainerBackgroundCoordinator$2;' failed
E/dalvikvm( 2306): Could not find class 'com.google.android.finsky.layout.ControlsContainerBackgroundCoordinator$2', referenced from method com.google.android.finsky.layout.FinskyTabStrip.onAttachedToWindow
W/dalvikvm( 2306): VFY: unable to resolve new-instance 3013 (Lcom/google/android/finsky/layout/ControlsContainerBackgroundCoordinator$2;) in Lcom/google/android/finsky/layout/FinskyTabStrip;
D/dalvikvm( 2306): VFY: replacing opcode 0x22 at 0x006b
W/dalvikvm( 2306): Unable to resolve superclass of Lcom/google/android/finsky/layout/ControlsContainerBackgroundCoordinator$2; (1325)
W/dalvikvm( 2306): Link of class 'Lcom/google/android/finsky/layout/ControlsContainerBackgroundCoordinator$2;' failed
D/dalvikvm( 2306): DexOpt: unable to opt direct call 0x502e at 0x6d in Lcom/google/android/finsky/layout/FinskyTabStrip;.onAttachedToWindow
W/dalvikvm( 2306): VFY: unable to resolve static field 4997 (BACKGROUND) in Landroid/view/ViewOutlineProvider;
D/dalvikvm( 2306): VFY: replacing opcode 0x62 at 0x000b
I/dalvikvm( 2306): Could not find method android.view.ViewGroup.invalidateOutline, referenced from method com.google.android.finsky.layout.ControlsContainerBackgroundCoordinator.updateBackgroundHeightAndFades
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9228: Landroid/view/ViewGroup;.invalidateOutline ()V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x003a
I/dalvikvm( 2306): Could not find method android.view.ViewPropertyAnimator.z, referenced from method com.google.android.play.animation.AnimationCompat.animateZ
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9321: Landroid/view/ViewPropertyAnimator;.z (F)Landroid/view/ViewPropertyAnimator;
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x000c
W/dalvikvm( 2306): VFY: unable to find class referenced in signature (Landroid/graphics/Outline;)
I/dalvikvm( 2306): Could not find method android.graphics.Outline.setRect, referenced from method com.google.android.play.headerlist.PlayHeaderListLayout$6.getOutline
W/dalvikvm( 2306): VFY: unable to resolve virtual method 914: Landroid/graphics/Outline;.setRect (Landroid/graphics/Rect;)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x0004
I/dalvikvm( 2306): Could not find method com.google.android.finsky.layout.play.PlayHighlightsBannerItemView.setElevation, referenced from method com.google.android.finsky.activities.HighlightsPagerAdapter$HighlightsTab.onCurrentBannerChanged
W/dalvikvm( 2306): VFY: unable to resolve virtual method 23519: Lcom/google/android/finsky/layout/play/PlayHighlightsBannerItemView;.setElevation (F)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x002c
I/dalvikvm( 2306): Could not find method com.google.android.finsky.layout.play.PlayHighlightsBannerItemView.setElevation, referenced from method com.google.android.finsky.activities.HighlightsPagerAdapter$HighlightsTab.onCurrentBannerChanged
W/dalvikvm( 2306): VFY: unable to resolve virtual method 23519: Lcom/google/android/finsky/layout/play/PlayHighlightsBannerItemView;.setElevation (F)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x003a
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
I/dalvikvm( 2306): Could not find method android.widget.FrameLayout.<init>, referenced from method com.google.android.finsky.layout.ControlsContainerBackground.<init>
W/dalvikvm( 2306): VFY: unable to resolve direct method 9808: Landroid/widget/FrameLayout;.<init> (Landroid/content/Context;Landroid/util/AttributeSet;II)V
D/dalvikvm( 2306): VFY: replacing opcode 0x70 at 0x0000
I/dalvikvm( 2306): Could not find method android.view.ViewAnimationUtils.createCircularReveal, referenced from method com.google.android.finsky.layout.ControlsContainerBackground.setBackgroundDrawable
W/dalvikvm( 2306): VFY: unable to resolve static method 9155: Landroid/view/ViewAnimationUtils;.createCircularReveal (Landroid/view/View;IIFF)Landroid/animation/Animator;
D/dalvikvm( 2306): VFY: replacing opcode 0x71 at 0x0087
D/Finsky  ( 2306): [1] DownloadQueueImpl.notifyProgress: com.google.android.gms: onProgress 0/-1 Status: 190.
I/dalvikvm( 2306): Could not find method com.google.android.finsky.layout.DocImageView.setTransitionName, referenced from method com.google.android.finsky.adapters.HighlightsContentBinder.bindChild
W/dalvikvm( 2306): VFY: unable to resolve virtual method 20813: Lcom/google/android/finsky/layout/DocImageView;.setTransitionName (Ljava/lang/String;)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6e at 0x00ac
I/dalvikvm( 2306): Could not find method android.widget.RelativeLayout.drawableHotspotChanged, referenced from method com.google.android.play.layout.ForegroundRelativeLayout.drawableHotspotChanged
W/dalvikvm( 2306): VFY: unable to resolve virtual method 10171: Landroid/widget/RelativeLayout;.drawableHotspotChanged (FF)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6f at 0x0000
I/DownloadManager(  754): Download 3 starting
W/ActivityThread(  754): ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
D/dalvikvm( 2306): GC_FOR_ALLOC freed 1394K, 15% free 9320K/10956K, paused 46ms, total 46ms
D/dalvikvm(  754): GC_CONCURRENT freed 431K, 24% free 1724K/2244K, paused 1ms+3ms, total 13ms
I/qtaguid ( 2306): Failed write_ctrl(u 62) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 62 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(62) failed with errno -22
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
E/RecyclerView( 2306): No adapter attached; skipping layout
D/Finsky  ( 2306): [1] DownloadQueueImpl.notifyProgress: com.google.android.gms: onProgress 0/-1 Status: 192.
I/qtaguid ( 2306): Failed write_ctrl(u 84) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 84 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(84) failed with errno -22
D/dalvikvm( 2306): GC_EXPLICIT freed 350K, 11% free 10748K/11984K, paused 9ms+6ms, total 86ms
I/dalvikvm( 2306): Could not find method android.widget.LinearLayout.drawableHotspotChanged, referenced from method com.google.android.finsky.layout.ForegroundLinearLayout.drawableHotspotChanged
W/dalvikvm( 2306): VFY: unable to resolve virtual method 9970: Landroid/widget/LinearLayout;.drawableHotspotChanged (FF)V
D/dalvikvm( 2306): VFY: replacing opcode 0x6f at 0x0000
I/qtaguid ( 2306): Failed write_ctrl(u 62) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 62 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(62) failed with errno -22
D/dalvikvm( 2306): GC_EXPLICIT freed 168K, 10% free 10855K/11984K, paused 2ms+6ms, total 85ms
D/dalvikvm(  754): GC_CONCURRENT freed 401K, 22% free 1773K/2252K, paused 3ms+1ms, total 16ms
D/dalvikvm( 2306): GC_EXPLICIT freed 171K, 9% free 12901K/14040K, paused 2ms+6ms, total 63ms
I/qtaguid ( 2306): Failed write_ctrl(u 91) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 91 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(91) failed with errno -22
I/qtaguid ( 2306): Failed write_ctrl(u 95) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 95 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(95) failed with errno -22
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
V/GLSActivity(  871): AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
I/qtaguid ( 2306): Failed write_ctrl(u 95) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 95 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(95) failed with errno -22
I/qtaguid ( 2306): Failed write_ctrl(u 84) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 84 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(84) failed with errno -22
I/qtaguid ( 2306): Failed write_ctrl(u 91) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 91 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(91) failed with errno -22
V/RenderScript( 2306): 0x6c7f3d28 Launching thread(s), CPUs 4
I/qtaguid ( 2306): Failed write_ctrl(u 95) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 95 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(95) failed with errno -22
D/PlayCommon( 2306): [1] BitmapLoader.access$200: http://lh3.googleusercontent.com/oWjDuhYth4eSUtoYC3LQOJnXNgu4NcF5As7CgZW07HZBpnO4Yd7_Y-wh94WSYaEQVNg=rw-w683-h448 is not cached
D/PlayCommon( 2306): [1] BitmapLoader.access$200: http://lh3.googleusercontent.com/RAgEBMk9GidYnxNMN8k8vKHi19XnGn17INA06_dVi01yUrxh-lGISyvl1lDKbifFm5ju=rw-w683-h448 is not cached
D/PlayCommon( 2306): [1] BitmapLoader.access$200: http://lh3.googleusercontent.com/_2y4wyOtvwASXzNaXjJ5uSABZ3tm1XnoRMLZf0UYVvJfqjut1NE4_cMWac84F7Z0LFA=rw-w683-h448 is not cached
I/qtaguid ( 2306): Failed write_ctrl(u 62) res=-1 errno=22
I/qtaguid ( 2306): Untagging socket 62 failed errno=-22
W/NetworkManagementSocketTagger( 2306): untagSocket(62) failed with errno -22
D/AndroidRuntime( 2306): Shutting down VM
W/dalvikvm( 2306): threadid=1: thread exiting with uncaught exception (group=0x41687ba8)
D/dalvikvm(  754): GC_CONCURRENT freed 278K, 17% free 1883K/2252K, paused 1ms+1ms, total 13ms
E/AndroidRuntime( 2306): FATAL EXCEPTION: main
E/AndroidRuntime( 2306): Process: com.android.vending, PID: 2306
E/AndroidRuntime( 2306): java.lang.ClassCastException: android.view.View cannot be cast to com.google.android.finsky.layout.play.PlayHighlightsBannerItemView
E/AndroidRuntime( 2306):    at com.google.android.finsky.layout.play.PlayClusterViewContentV2.getViewForItemPosition(PlayClusterViewContentV2.java:391)
E/AndroidRuntime( 2306):    at com.google.android.finsky.layout.play.PlayHighlightsBannerView.isItemLoaded(PlayHighlightsBannerView.java:99)
E/AndroidRuntime( 2306):    at com.google.android.finsky.activities.HighlightsPagerAdapter$HighlightsTab$1.run(HighlightsPagerAdapter.java:251)
E/AndroidRuntime( 2306):    at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 2306):    at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 2306):    at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2306):    at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 2306):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2306):    at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 2306):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:788)

Updates:
When playstore update automatically to 6.0.0 version then its crashing all time older version of playstore working fine, so I found some work around from here check 3rd answer.
Above workaround stops playstore to updates itself and older playstore working fine.
Similar issue you can find here

What is your Android version? Are you using a ARM32 GApps package? Your system runs a Cortex A9 processor, which is very old and may not be properly supported by the latest Play Store versions for Android 4.4 and up.

Android 4.4.2,I'm using Amlogic s802 soc and ARM32 GApps

Searching on StackOverflow, there are errors related to Multidex related development with similar signatures. The reason being unresolved dependencies. Can you refer me to the guide you used for the procedure so that I can cross check?

I'm using this guide https://nosemaj.org/howto-build-android-kitkat-nexus-5 for adding google apps to aosp build, refer "Obtain the Google Proprietary Apps"

If you're using an Android TV device, which your chipset is meant for according to WikiPedia, a standard GApps package won't be compatible with your system, which is probably the problem.

Yes, I'm using for android TV device let me try with flashing gapps from recovery.

@RRD Did you solve your problem?

@Mr.Hyde: I didn't solve but found some workaround check in my updated question.

In our chat, and from the comments, I can identify your problem, but a solution is currently not feasible for you.
Problem:
The GApps don't work because you are using GApps meant for a Nexus 5 (source: your comment's link), a phone, on an Android TV. I'm actually not sure how it actually installed in the first place. It shouldn't have.
GApps are heavily device-specific. There are different versions by processor architecture, which isn't the problem, as both your TV and a Nexus 5 have ARMv7l based processors.
There are also different versions by screen DPI (display density), which are not necessarily intercompatible. 1st problem source.
Also, a phone running Android Kitkat and an Android TV running Android TV Kitkat do not expose the same set of APIs to applications, especially at the native level. GApps are heavily native, as illustrated above. 2nd problem source.
Just because the Android TV does not provide many of the API dependencies for a standard Android app, your GApps, meant for a phone, crash.
Possible solutions:
Use an ARMv7l (ARM) GApps package specifically for Android TV. This is easier said than done in your case, because, I, even after a very thorough search, couldn't locate a single applicable Android TV-specific ARM Kitkat GApps package. I did find such packages for Lollipop and Marshmallow, though.
This leaves us with not many options. The only feasible thing would be to upgrade to Lollipop or above, which, again, is easier said than done. I do not know of any Lollipop or Marshmallow custom ROMs for your device.
Links to Android TV GApps packages (Not trusted to remain available for long as there is no official host for Android TV (Leanback launcher) specific GApps):

Lollipop is here.
Marshmallow is here.

If there are any more anyone can find, feel free to edit them in.
Sorry to disappoint you, but you are probably stuck with whatever market app the OEM provided you.

@Firelord, very unreliable links have been added ;) (No official host for Leanback GApps)