text:
Nexus 5X vibrates despite disabling in app settings
My phone vibrates on all notifications despite turning off vibrate in the settings of each individual app that has the option. How can I block vibrating notifications for specific apps?
According to the Google support page and forums there is no way to disable vibrate globally without entering do-not-disturb mode, but it should work on an app by app basis. Turning it off within an app changes the vibration and they now all act the same. So it seems like the option is disabling the vibration that comes from the app but there is some system wide notification that always happens.
The phone is a new Nexus 5X that I just received after signing up with Project Fi. The phone vibrations are extremely grating and can't be changed or lowered. Not being able to limit them without putting the phone in DND mode is driving me nuts. Any help is much appreciated.

It works! I had not known about MacroDroid. Thanks for your help.

Your problem is similar to the question here Decrease default vibration length on notification?
Tweak that solution with following changes

Trigger - Notification received from all apps
Action-Volume change> system sounds slider value to zero


text:
To restore my newborn photoes: How to root LG G3 D852 (Canadian variant)?
I connected my LG D852 with MM to the LG software, I had a pop-up that there is an upgrade so clicked OK thinking that the data will not be wiped as long as I will be still on MM. That was wrong! ALL data are wiped including my newborn first photos which are priceless to me. I tried some apps like diskdigger and some software on the PC but all of them require root to perform. I tried all rooting methods that I am aware of, but nothing is working. I can't downgrade to LP since writing on the internal memory is not a wise move to restore my data. Any ideas how to root that without having to downgrade?

When rooting, you normally have to wipe all data again, so I think any data rescue program will be unsuccessful here.

@timoschwarzer that is not entirely true. (1) Apps like kingoroot can root most devices without wiping all data. (2) Wiping data doesn't mean it is gone or overwritten and that is exactly how recovery programs work.

source: Stack Exchange

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

sort: votes


text:
Google account login broke on old tablet/android
I have an old Galaxy Tab 8.9 (GT-P7300) tablet with Android 4.0.4 (Samsung original firmware update, not rooted). It mostly sits in the drawer and sees very infrequent use.
Today I booted it up and everything related to Google account on it is locked up (including Play Market), giving following error:

Google

That's an error.

The requested URL /o/oauth/GetOAuthToken was not found on this server. That's all we know.

If I click on Google logo I get dumped to the regular Google web search page, where I can login fine but which doesn't resolve the issue.
Had Google just abandoned older Android versions or something?

I went to accounts in settings and tried to force sync on Google account. It threw the same error multiple times, but must have shaken the issue out somehow — login suddenly worked after that.

Removing the account and adding it again solved the problem for me.

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


text:
how i update an app with my data connection in letv1s
I want to update apps with data connection in letv1s  they are waited for wifi but i want to update apps through my data connection

Open Google Play, then open the drawer. Tap on Settings > Auto-update apps. Set it to Auto-update apps at anytime. Data charges may apply

Screenshot (click to enlarge)


text:
Twitter app: Is it possible to switch accounts while viewing a tweet?
I have the Twitter app for Android, and I use 2 accounts. Both are configured in the app.
How can I switch accounts while viewing a single tweet (if, for instance, I'm viewing a tweet in account A but want to retweet it from account B).
I used to be able to do it, but they seem to have removed it a few updates ago.

As of current version (Version 8.25.1-release.0 on Dec 20, 2019), it is not possible to switch accounts while viewing a tweet on the official Twitter app.
The only way to switch account is from the sidebar, and it is currently only accessible from the main screen.
Instead, to "retweet from another account", the native workaround is by sending a direct message to that account:

From a specific tweet, tap the "Share Tweet"
Choose "Send via Direct Message" and choose the target account
Go back to the main screen, then switch to another account
Navigate to "Messages" (mail icon on the bottom navigation bar), then open the conversation with another account
Open the tweet, then retweet.

(Note: to reduce the switching, it is recommended to bulk send the tweets first before switching)

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


text:
How to see ip addresses of game servers
I want to see the ip address which the specific game connected to specific servers that i played. My Goal is to add a QOS on my router for specific game.
iv tried doing a packet capture on my android but it has alot of other none related ip addresses seen.

See my answer here. You might also wish to check the questions in the "linked" section there.

Alternatively, you can issue netstat -np from a terminal and grep for the relevant package name.

Does this answer your question? Listen which URLs an app tries to connect


text:
Can I use Tasker to simulate Page Up / Page Down without root access?
I've read people doing it using adb without root access. I've also read that people can do it using Tasker and several other methods, but with root access.
Is it possible to do the same with Tasker (or other methods without involving devices other than the phone itself), but without root access? If not, why so?


text:
Where is Android boot animation saved?
When you start an Android device, there is an animation showed, usually "Android", but sometimes the manufacturer's logo.
Where is this animation stored? I have looked in the boot.img, but can't see it there.

The boot animation is normally located in /system/media under the name bootanimation.zip. This is a zip file containing one or more directories named part0, part1, part2, and so on, and a text file named desc.txt. The directories each contain a number of still images, JPEG or PNG, sequentially numbered, for example, 0001.png, 0002.png, 0003.png, and so on. The text file is a simple description of the properties, such as how many times to loop each directory, the pixel size of the images, and the framerate. Like this:
width height framerate
p loop pause directory

For example:
1080 1920 20
p 1 0 part0
p 0 0 part1

0 for loop means that it loops until the boot process is complete, and the pause is specified in number of frames, so with a framerate of 20, a pause of 1 would mean 0.05 seconds pause before moving on to the next loop or the next part.
Some manufacturers may use a proprietary file format, which may or may not have a different name than bootanimation.zip, so make sure that your current file uses the above format before replacing it with a custom one. If the boot animation is corrupted, the phone may boot loop or simply ignore the animation.
The file should be owned by root:root and have permissions set to 644 (rw-r--r--). It must not be compressed.

The boot animation is located at
/(Home directory) > System > Media > ... (for me it's bootanimation.zip)

And of course you need a file explorer and a rooted phone I guess.

You don't need a rooted device to reach it

A root is required to perform this task.
Use any file explorer application such as ES File Explorer, with root access.
Go to the root directory of internal / system / media. You can see a file named bootanimation.zip, which is the one that loaded during boot.

Extracting the zip may display multiple folders named as part0, part1, part2,.. and desc.txt.

You don't need a rooted device to reach it

If you have a computer with Android Debug Bridge (ADB) available, you can run this command to find its location:
$ adb shell
# find . -iname "bootanimation.zip" 2>/dev/null
On one of my devices it was stored in /oem/media/bootanimation.zip and on the other device it was stored in /product/media/bootanimation.zip

For me, on Pixel 6 with Android 13, it's actually on:
/system/product/media/bootanimation-dark.zip

/system/product/media/bootanimation.zip

It appears you can override the boot animation on a device. Create a boot animation file, as described in the other answers, and copy it to /data/local, which is writable by adb without rooting:
adb push bootanimation.zip /data/local

Source: Emteria article on boot animations. I have not tried this yet.

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


text:
How to find out which app is providing adverts (without reverting to process of elimination)
I'm on Android 6 (P8 if it matters) and I am getting very annoying adverts.
Screen shots show it all:

Screenshots (click images for larger variants)
This icon shown on the right of the first screenshot with the word WIN persists on my "desktop" or "home" screen too. If I click on it, I get what's shown in the second screenshot – as pops up enough to be annoying but it doesn't pop up daily.
My question is, how do I know what is causing this so I can remove it.
The only option I know of is to start removing apps and use the power of elimination but that is not ideal!
The other option I know of is to click on it - sometimes an advert  is part of the app installed (in this image, it takes me to the buy plug ins from the Keyboard app I use) which probably suggests that this app is causing it (but not guaranteed).
Regardless of those 2, I'm still keen to know how to tell, be it via logs or anything else.

With that annoying popup open, what does the multi-tasking-list show (press the right-most navigation item, showing as a square in both screenshots)? It might show the application name along.

@Izzy, sadly I don't have it open but, I will return to this when it occurs again. Than you for the advice

Have you tried the solutions mentioned here?

@Izzy, sadly, when I see the small image (shown in the first image, with the word "win") and hit the square (to show the multi-tasking-list) it doesn't appear. When I click on the image to show the "gambling machine" and press the square, the gambling machine closes first. As such, it never appears.

I'm pretty sure that your keyboard is cause of ads showing (I guess this isn't stock one, is it?) try finding settings of that keyboard and see if there is option to turn off ads (I guess there isn't but still worth of try) however if you don't find option to turn off ads than simply uninstall some reliable keyboard (G BOARD and such)

It was the keyboard... So a different keyboard resolved it, but that was via trial and error. Thank you

Addons Detector is designed specifically for this purpose.


text:
Stay awake while charging - why not?
I am new to Android 7.1, and I would like my phone to be always on while charging. Is there any disadvantage? Are there any system processes running only in sleep mode?
Related:
Stay awake while charging, bad for battery?

Activate Developer options ( Go to Settings->About Phone->tap on build number multiple times, and it shows a message You have enabled Developer options after completed) , Inside developer options, check whether Stay awake is ON or not, if ON turn off by sliding left.

@RahulGopi OP didn't ask how to achieve that, but if that has any disadvantage. I'd say OP is completely capable of enabling it :)

There are no issues with background processes, you can go ahead.

@Izzy Ok, I understood.


text:
Stopping busybox's `httpd`
I just found that busybox has httpd. I started it, and now I don't know how to stop it without rebooting. My busybox version is Stephen Ericson, 1.26.2
Any help is appreciated.
EDIT
Here is the output of ps
angler:/ $ su
angler:/ # ps
USER      PID   PPID  VSIZE  RSS   WCHAN              PC  NAME
root      1     0     11092  1424  SyS_epoll_ 00005134e0 S /init
root      2     0     0      0       kthreadd 0000000000 S kthreadd
root      3     2     0      0     smpboot_th 0000000000 S ksoftirqd/0
root      5     2     0      0     worker_thr 0000000000 S kworker/0:0H
root      6     2     0      0     msm_mpm_wo 0000000000 D kworker/u16:0
root      7     2     0      0     smpboot_th 0000000000 S migration/0
root      8     2     0      0     rcu_gp_kth 0000000000 S rcu_preempt
root      9     2     0      0     rcu_gp_kth 0000000000 S rcu_bh
root      10    2     0      0     rcu_gp_kth 0000000000 S rcu_schedroot      11    2     0      0     smpboot_th 0000000000 S migration/1
root      12    2     0      0     smpboot_th 0000000000 S ksoftirqd/1
root      14    2     0      0     worker_thr 0000000000 S kworker/1:0H
root      15    2     0      0     smpboot_th 0000000000 S migration/2
root      16    2     0      0     smpboot_th 0000000000 S ksoftirqd/2
root      18    2     0      0     worker_thr 0000000000 S kworker/2:0H
root      19    2     0      0     smpboot_th 0000000000 S migration/3
root      20    2     0      0     smpboot_th 0000000000 S ksoftirqd/3
root      22    2     0      0     worker_thr 0000000000 S kworker/3:0H
root      23    2     0      0     rescuer_th 0000000000 S khelper
root      24    2     0      0     rescuer_th 0000000000 S netns
root      25    2     0      0     rescuer_th 0000000000 S perf
root      30    2     0      0     worker_thr 0000000000 S kworker/1:1H
root      31    2     0      0     rescuer_th 0000000000 S smd_channel_clo
root      32    2     0      0     rescuer_th 0000000000 S smsm_cb_wq
root      34    2     0      0     rescuer_th 0000000000 S deferwq
root      35    2     0      0     msm_rpm_sm 0000000000 D kworker/u17:0
root      36    2     0      0     rescuer_th 0000000000 S rpm-smd
root      38    2     0      0     irq_thread 0000000000 S irq/48-cpr
root      39    2     0      0     irq_thread 0000000000 S irq/51-cpr
root      40    2     0      0     smpboot_th 0000000000 S migration/4
root      41    2     0      0     smpboot_th 0000000000 S ksoftirqd/4
root      42    2     0      0     worker_thr 0000000000 S kworker/4:0
root      43    2     0      0     worker_thr 0000000000 S kworker/4:0H
root      44    2     0      0     rescuer_th 0000000000 S mpm
root      46    2     0      0     rescuer_th 0000000000 S writebackroot      47    2     0      0     rescuer_th 0000000000 S bioset
root      48    2     0      0     rescuer_th 0000000000 S crypto
root      49    2     0      0     rescuer_th 0000000000 S kblockd
root      50    2     0      0     hub_thread 0000000000 S khubd
root      51    2     0      0     ion_heap_d 0000000000 S system
root      52    2     0      0     rescuer_th 0000000000 S ipa_power_mgmt
root      53    2     0      0     rescuer_th 0000000000 S sps_ipa_power_m
root      54    2     0      0     rescuer_th 0000000000 S ipawq14
root      55    2     0      0     rescuer_th 0000000000 S iparepwq14
root      56    2     0      0     rescuer_th 0000000000 S ipawq43
root      57    2     0      0     rescuer_th 0000000000 S iparepwq43
root      58    2     0      0     rescuer_th 0000000000 S ipawq13
root      59    2     0      0     rescuer_th 0000000000 S iparepwq13
root      60    2     0      0     rescuer_th 0000000000 S ipa_rm_wqroot      61    2     0      0     rescuer_th 0000000000 S ipa_interrupt_w
root      62    2     0      0     worker_thr 0000000000 S kworker/4:1H
root      64    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      65    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      66    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      67    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      68    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      69    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      70    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      71    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      72    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      73    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      74    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      75    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      76    2     0      0     irq_thread 0000000000 S irq/261-msm_iom
root      77    2     0      0     irq_thread 0000000000 S irq/263-msm_iom
root      78    2     0      0     irq_thread 0000000000 S irq/102-msm_iom
root      79    2     0      0     irq_thread 0000000000 S irq/102-msm_iom
root      80    2     0      0     irq_thread 0000000000 S irq/102-msm_iom
root      81    2     0      0     irq_thread 0000000000 S irq/102-msm_iom
root      82    2     0      0     irq_thread 0000000000 S irq/74-msm_iomm
root      83    2     0      0     irq_thread 0000000000 S irq/75-msm_iomm
root      84    2     0      0     irq_thread 0000000000 S irq/75-msm_iomm
root      85    2     0      0     irq_thread 0000000000 S irq/75-msm_iomm
root      86    2     0      0     irq_thread 0000000000 S irq/75-msm_iomm
root      87    2     0      0     irq_thread 0000000000 S irq/273-msm_iom
root      88    2     0      0     irq_thread 0000000000 S irq/273-msm_iom
root      89    2     0      0     irq_thread 0000000000 S irq/272-msm_iom
root      90    2     0      0     irq_thread 0000000000 S irq/97-msm_iomm
root      91    2     0      0     irq_thread 0000000000 S irq/97-msm_iomm
root      92    2     0      0     irq_thread 0000000000 S irq/97-msm_iomm
root      93    2     0      0     irq_thread 0000000000 S irq/350-msm_iom
root      94    2     0      0     irq_thread 0000000000 S irq/350-msm_iom
root      95    2     0      0     irq_thread 0000000000 S irq/350-msm_iom
root      96    2     0      0     irq_thread 0000000000 S irq/298-msm_iom
root      97    2     0      0     irq_thread 0000000000 S irq/298-msm_iom
root      98    2     0      0     irq_thread 0000000000 S irq/298-msm_iom
root      99    2     0      0     irq_thread 0000000000 S irq/79-msm_iomm
root      100   2     0      0     irq_thread 0000000000 S irq/78-msm_iomm
root      101   2     0      0     irq_thread 0000000000 S irq/78-msm_iomm
root      102   2     0      0     rescuer_th 0000000000 S devfreq_wq
root      103   2     0      0     rescuer_th 0000000000 S cfg80211
root      104   2     0      0     irq_thread 0000000000 S irq/15-bcl_vbat
root      105   2     0      0     irq_thread 0000000000 S irq/460-bcl_iba
root      106   2     0      0     rescuer_th 0000000000 S rpciod
root      129   2     0      0         kswapd 0000000000 S kswapd0
root      130   2     0      0     ksm_scan_t 0000000000 S ksmd
root      131   2     0      0     fsnotify_m 0000000000 S fsnotify_mark
root      132   2     0      0     rescuer_th 0000000000 S nfsiod
root      152   2     0      0     rescuer_th 0000000000 S ad_calc_wq
root      153   2     0      0     rescuer_th 0000000000 S rot_commit_work
root      154   2     0      0     dsi_event_ 0000000000 D mdss_dsi_event
root      155   2     0      0     kthread_wo 0000000000 S vsync_retire_wo
root      156   2     0      0     rescuer_th 0000000000 S apr_driver
root      157   2     0      0     rescuer_th 0000000000 S pil_vote_wq
root      158   2     0      0     rescuer_th 0000000000 S shm_svc
root      159   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      160   2     0      0     rescuer_th 0000000000 S msm_ipc_router
root      161   2     0      0     rescuer_th 0000000000 S k_hsuart
root      162   2     0      0     kthread_wo 0000000000 S msm_serial_hs_0
root      163   2     0      0     kthread_wo 0000000000 S msm_serial_hs_0
root      164   2     0      0     add_hwgene 0000000000 S hwrng
root      165   2     0      0     rescuer_th 0000000000 S diag_real_time_
root      166   2     0      0     rescuer_th 0000000000 S diag_modem_data
root      167   2     0      0     rescuer_th 0000000000 S diag_lpass_data
root      168   2     0      0     rescuer_th 0000000000 S diag_wcnss_data
root      169   2     0      0     rescuer_th 0000000000 S diag_sensors_da
root      170   2     0      0     rescuer_th 0000000000 S diag_wq
root      171   2     0      0     rescuer_th 0000000000 S DIAG_USB_diag
root      172   2     0      0     rescuer_th 0000000000 S diag_cntl_wq
root      173   2     0      0     rescuer_th 0000000000 S diag_dci_wq
root      174   2     0      0     kthread_wo 0000000000 S kgsl_worker_thr
root      175   2     0      0     rescuer_th 0000000000 S kgsl-3d0
root      176   2     0      0     rescuer_th 0000000000 S kgsl-events
root      177   2     0      0     rescuer_th 0000000000 S governor_msm_ad
root      178   2     0      0     rescuer_th 0000000000 S kgsl_devfreq_wq
root      199   2     0      0     kthread_wo 0000000000 S spi5
root      200   2     0      0     rescuer_th 0000000000 S usbnet
root      201   2     0      0     rescuer_th 0000000000 S sharedmem_qmi_w
root      202   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      204   2     0      0     irq_thread 0000000000 S irq/212-msm_dwc
root      205   2     0      0     rescuer_th 0000000000 S k_gserialroot      206   2     0      0     rescuer_th 0000000000 S uether
root      209   2     0      0     rescuer_th 0000000000 S dsx_rebuild_wor
root      210   2     0      0     rescuer_th 0000000000 S dsx_exp_workque
root      211   2     0      0     rescuer_th 0000000000 S s2wiwq
root      212   2     0      0     rescuer_th 0000000000 S dt2wiwq
root      213   2     0      0     irq_thread 0000000000 S irq/502-fpc1020
root      216   2     0      0     rescuer_th 0000000000 S fwu_workqueue
root      217   2     0      0     rescuer_th 0000000000 S msm_cpp_workque
root      219   2     0      0     irq_thread 0000000000 S irq/495-batt-mi
root      220   2     0      0     irq_thread 0000000000 S irq/504-synapti
root      245   2     0      0     rescuer_th 0000000000 S dm_bufio_cache
root      246   2     0      0     cpufreq_in 0000000000 S cfinteractive
root      247   2     0      0     irq_thread 0000000000 S irq/170-f982490
root      249   2     0      0     irq_thread 0000000000 S irq/253-f98a490
root      251   2     0      0     irq_thread 0000000000 S irq/499-qpnp_wl
root      252   2     0      0     rescuer_th 0000000000 S binder
root      253   2     0      0     irq_thread 0000000000 S irq/603-nanohub
root      254   2     0      0     nanohub_kt 0000000000 S nanohub
root      255   2     0      0     mmc_queue_ 0000000000 S mmcqd/0
root      256   2     0      0     mmc_queue_ 0000000000 S mmcqd/0rpmb
root      257   2     0      0     rescuer_th 0000000000 S usb_bam_wq
root      258   2     0      0     irq_thread 0000000000 S irq/500-qpnp_sc
root      259   2     0      0     irq_thread 0000000000 S irq/224-spdm_bw
root      260   2     0      0     rfcomm_run 0000000000 S krfcommd
root      261   2     0      0     irq_thread 0000000000 S irq/609-adsp
root      262   2     0      0     irq_thread 0000000000 S irq/641-modem
root      264   2     0      0     rescuer_th 0000000000 S msm_vidc_worker
root      265   2     0      0     rescuer_th 0000000000 S pm_workerq_venu
root      267   2     0      0     irq_thread 0000000000 S irq/464-chg-err
root      268   2     0      0     irq_thread 0000000000 S irq/9-chg-taper
root      269   2     0      0     irq_thread 0000000000 S irq/10-chg-tcc-
root      270   2     0      0     irq_thread 0000000000 S irq/8-chg-rechg
root      271   2     0      0     irq_thread 0000000000 S irq/468-chg-p2f
root      272   2     0      0     irq_thread 0000000000 S irq/469-batt-ho
root      273   2     0      0     irq_thread 0000000000 S irq/11-batt-war
root      274   2     0      0     irq_thread 0000000000 S irq/13-batt-coo
root      275   2     0      0     irq_thread 0000000000 S irq/12-batt-col
root      276   2     0      0     irq_thread 0000000000 S irq/7-batt-miss
root      277   2     0      0     irq_thread 0000000000 S irq/470-batt-lo
root      278   2     0      0     irq_thread 0000000000 S irq/1-usbin-uv
root      279   2     0      0     irq_thread 0000000000 S irq/2-usbin-ov
root      280   2     0      0     irq_thread 0000000000 S irq/3-usbin-src
root      281   2     0      0     irq_thread 0000000000 S irq/4-otg-fail
root      282   2     0      0     irq_thread 0000000000 S irq/5-otg-oc
root      283   2     0      0     irq_thread 0000000000 S irq/6-aicl-done
root      284   2     0      0     irq_thread 0000000000 S irq/473-dcin-uv
root      285   2     0      0     irq_thread 0000000000 S irq/475-power-o
root      286   2     0      0     irq_thread 0000000000 S irq/476-temp-sh
root      287   2     0      0     irq_thread 0000000000 S irq/477-safety-
root      293   2     0      0     rescuer_th 0000000000 S rq_stats
root      294   2     0      0     events_not 0000000000 S msm_perf:events
root      295   2     0      0     rescuer_th 0000000000 S sb-1
root      296   2     0      0     ngd_slim_r 0000000000 D ngd_rx_thread1
root      297   2     0      0     ngd_notify 0000000000 D ngd_notify_sl1
root      298   2     0      0     rescuer_th 0000000000 S k_bam_data
root      299   2     0      0     rescuer_th 0000000000 S f_mtp
root      300   2     0      0     sleep_thre 0000000000 S file-storage
root      301   2     0      0     do_samplin 0000000000 D msm-core:sampli
root      302   2     0      0     do_hotplug 0000000000 S msm_thermal:hot
root      303   2     0      0     do_freq_mi 0000000000 S msm_thermal:fre
root      304   2     0      0     do_thermal 0000000000 S msm_thermal:the
root      314   2     0      0     boost_mig_ 0000000000 S boost_sync/0
root      315   2     0      0     boost_mig_ 0000000000 S boost_sync/1
root      316   2     0      0     boost_mig_ 0000000000 S boost_sync/2
root      317   2     0      0     boost_mig_ 0000000000 S boost_sync/3
root      318   2     0      0     boost_mig_ 0000000000 S boost_sync/4
root      319   2     0      0     boost_mig_ 0000000000 S boost_sync/5
root      320   2     0      0     boost_mig_ 0000000000 S boost_sync/6
root      321   2     0      0     boost_mig_ 0000000000 S boost_sync/7
root      322   2     0      0     rescuer_th 0000000000 S ipa_A7_svc
root      323   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      324   2     0      0     rescuer_th 0000000000 S clnt_req
root      326   2     0      0     rescuer_th 0000000000 S clnt_resproot      327   2     0      0     rescuer_th 0000000000 S clnt_req
root      328   2     0      0     down_inter 0000000000 S wl_event_handle
root      329   2     0      0     down_inter 0000000000 S dhd_watchdog_th
root      330   1     6340   1116  do_sys_pol 0000513510 S /sbin/ueventd
root      333   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p43
root      334   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      335   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p37
root      336   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      337   2     0      0     worker_thr 0000000000 S kworker/0:1H
root      341   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p38
root      342   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      343   2     0      0     kjournald2 0000000000 S jbd2/mmcblk0p32
root      344   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      351   2     0      0     kauditd_th 0000000000 S kauditd
root      364   1     5428   984   skb_recv_d 00f056571c S /system/bin/debuggerd
root      365   1     10788  1120  skb_recv_d 7b07f85cf4 S /system/bin/debuggerd64
root      366   1     52052  1932  hrtimer_na 7e546be744 S /system/bin/vold
root      368   365   10532  12    __skb_recv 7b07f8684c S debuggerd64:signaller
root      369   364   5172   8     __skb_recv 00f0566950 S debuggerd:signaller
root      388   2     0      0     rescuer_th 0000000000 S IPCRTR
root      389   2     0      0     rescuer_th 0000000000 S adsp_IPCRTR
root      392   1     51644  648   SyS_epoll_ 00004a6e78 S /sbin/healthd
root      393   1     18940  1264  do_sigtime 7a6f6bef34 S /vendor/bin/pm-service
root      395   1     9380   1412  do_sys_pol 7ac0c16e74 S /vendor/bin/msm_irqbalance
root      396   1     9428   1508  SyS_epoll_ 71c561ad54 S /system/bin/lmkd
root      406   2     0      0     kthread_wo 0000000000 S msm_slim_qmi_cl
root      407   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      419   2     0      0     irq_thread 0000000000 S irq/449-wcd9xxx
root      439   2     0      0     smpboot_th 0000000000 S migration/5
root      440   2     0      0     smpboot_th 0000000000 S ksoftirqd/5
root      441   2     0      0     worker_thr 0000000000 S kworker/5:0
root      442   2     0      0     worker_thr 0000000000 S kworker/5:0H
root      443   2     0      0     smpboot_th 0000000000 S migration/6
root      444   2     0      0     smpboot_th 0000000000 S ksoftirqd/6
root      445   2     0      0     worker_thr 0000000000 S kworker/6:0
root      446   2     0      0     worker_thr 0000000000 S kworker/6:0H
root      447   2     0      0     smpboot_th 0000000000 S migration/7
root      448   2     0      0     smpboot_th 0000000000 S ksoftirqd/7
root      450   2     0      0     worker_thr 0000000000 S kworker/7:0H
root      451   2     0      0     msm_rpm_wa 0000000000 D irq/215-fc38800
root      455   1     16132  1248  hrtimer_na 7da6c9b744 S /vendor/bin/pm-proxy
root      459   1     8040   1096  skb_recv_d 7ced8d4cf4 S /system/xbin/su
root      470   2     0      0     worker_thr 0000000000 S kworker/7:1
root      493   2     0      0     rescuer_th 0000000000 S kdmflush
root      497   2     0      0     rescuer_th 0000000000 S bioset
root      498   2     0      0     rescuer_th 0000000000 S kcryptd_io
root      499   2     0      0     rescuer_th 0000000000 S kcryptd
root      500   2     0      0     dmcrypt_wr 0000000000 S dmcrypt_write
root      501   2     0      0     rescuer_th 0000000000 S bioset
root      503   2     0      0     rescuer_th 0000000000 S IPCRTR
root      504   2     0      0     rescuer_th 0000000000 S modem_IPCRTR
root      514   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      521   2     0      0     rescuer_th 0000000000 S qmi_hndl0000000
root      526   2     0      0     worker_thr 0000000000 S kworker/2:1H
root      527   2     0      0     worker_thr 0000000000 S kworker/u17:10
root      530   2     0      0     kjournald2 0000000000 S jbd2/dm-0-8
root      531   2     0      0     rescuer_th 0000000000 S ext4-rsv-conver
root      540   1     76440  1348  SyS_rt_sig 78d3793f1c S /vendor/bin/thermal-engine
root      542   1     18652  964   futex_wait 73a270fe70 S /vendor/bin/perfd
root      547   1     14208  1304  futex_wait 7a60484e70 S /vendor/bin/oem_qmi_server
root      549   1     2158852 45060 do_sys_pol 72f4d60e74 S zygote64root      550   1     1592584 36712 do_sys_pol 00ef9c39a8 S zygote
drm       553   1     15168  2148  binder_thr 00f0fe1900 S /system/bin/drmserver
root      554   1     10336  1864  unix_strea 71e8db884c S /system/bin/installd
root      562   1     34456  4608  binder_thr 7f1ae08e44 S /system/bin/netd
root      564   2     0      0     worker_thr 0000000000 S kworker/3:1H
gps       566   1     9168   1120  SyS_rt_sig 7ae9892f1c S /vendor/bin/loc_launcher
camera    567   1     120240 10980  do_select 00f4b30a00 S /vendor/bin/mm-qcamera-daemon
root      581   2     0      0     notify_use 0000000000 S wrkld_notify
gps       594   566   78224  2740  do_sys_pol 7955f17e74 S /vendor/bin/slim_daemon
root      769   2     0      0     worker_thr 0000000000 S kworker/0:2
root      897   2     0      0     worker_thr 0000000000 S kworker/u17:1
root      980   2     0      0     worker_thr 0000000000 S kworker/3:2
root      986   2     0      0     rescuer_th 0000000000 S ipawq44
root      987   2     0      0     rescuer_th 0000000000 S iparepwq44
root      1052  2     0      0     worker_thr 0000000000 S kworker/1:0
root      1118  2     0      0     worker_thr 0000000000 S kworker/u17:3
root      1119  2     0      0     worker_thr 0000000000 S kworker/u17:5
root      1173  2     0      0     worker_thr 0000000000 S kworker/2:2
root      1175  2     0      0     worker_thr 0000000000 S kworker/0:0
root      1228  2     0      0     worker_thr 0000000000 S kworker/3:4
root      1240  2     0      0     worker_thr 0000000000 S kworker/1:2
root      1259  2     0      0     worker_thr 0000000000 S kworker/u16:2
root      1266  2     0      0     __mdss_fb_ 0000000000 D mdss_fb0
shell     1284  1     17772  704   do_sys_pol 00004e0dc0 S /sbin/adbd
shell     1345  1284  8180   1476  SyS_rt_sig 79643c0f1c S /system/bin/sh
shell     1349  1345  8180   1480  SyS_rt_sig 7b9f819f1c S sh
shell     1351  1349  1478840 53496 SyS_epoll_ 00f4cbe7bc S /system/bin/app_process32
u0_a197   1381  550   1103676 70324 SyS_epoll_ 00ef9c37bc S com.koushikdutta.vysor
root      1437  2     0      0     worker_thr 0000000000 S kworker/u16:3
root      1465  2     0      0     worker_thr 0000000000 S kworker/5:1
root      1468  2     0      0     worker_thr 0000000000 S kworker/6:2
root      1609  2     0      0     worker_thr 0000000000 S kworker/1:3
u0_a64    1633  549   1578580 31596 SyS_epoll_ 72f4d60d54 S com.android.terminal
u0_a48    1655  549   2257900 48508 SyS_epoll_ 72f4d60d54 S com.wifikill.techbrain
u0_a0     1768  549   1587532 44324 SyS_epoll_ 72f4d60d54 S android.process.acore
u0_a132   1792  550   1099944 57348          0 00ef9c3eb4 R yarolegovich.materialterminal
u0_a132   1818  1792  8180   1660  SyS_rt_sig 70d8a05f1c S /system/bin/sh
u0_a132   1856  1818  8040   1432     do_wait 7dc6007e4c S su
u0_a132   1857  1856  10360  560   n_tty_read 7dc600784c R su
root      1859  1     8296   260      do_wait 7ced8d5e4c S /system/xbin/su
root      1862  1859  8296   280      do_wait 7ced8d5e4c S /system/xbin/su
root      1863  1862  9312   488      do_wait 7ced8d5e4c S /system/xbin/su
root      1864  1863  8180   1712  SyS_rt_sig 757c9f7f1c S sh
root      1870  1864  9696   1704           0 7e85e2384c R ps
wifi      3073  1     14020  3108   do_select 725b791e8c S /system/bin/wpa_supplicant
u0_a69    3076  549   1655992 76788 SyS_epoll_ 72f4d60d54 S com.android.inputmethod.latin
u0_a36    3085  549   1768496 125072 SyS_epoll_ 72f4d60d54 S com.android.systemui
media_rw  3103  366   0      0        do_exit 0000000000 Z sdcard
u0_a1     3248  549   1577216 32608 SyS_epoll_ 72f4d60d54 S org.cyanogenmod.cmaudio.service
radio     3326  549   1631248 56140 SyS_epoll_ 72f4d60d54 S com.android.phone
u0_a81    5046  549   1577692 34208 SyS_epoll_ 72f4d60d54 S com.google.android.ext.services
u0_a225   5090  549   1589780 44324 SyS_epoll_ 72f4d60d54 S de.markusfisch.android.shadereditor
u0_a72    5127  549   1708852 109780 SyS_epoll_ 72f4d60d54 S com.google.android.gms.persistent
u0_a85    5168  549   2294788 42772 SyS_epoll_ 72f4d60d54 S com.google.android.googlequicksearchbox:interactor
u0_a33    5183  549   1577104 32704 SyS_epoll_ 72f4d60d54 S org.cyanogenmod.weatherservice
system    5197  549   1585304 37168 SyS_epoll_ 72f4d60d54 S com.quicinc.cne.CNEService
u0_a20    5209  549   1576540 32076 SyS_epoll_ 72f4d60d54 S org.omnirom.omniswitch
nfc       5224  549   1607496 47612 SyS_epoll_ 72f4d60d54 S com.android.nfc
u0_a65    5265  549   1576524 31808 SyS_epoll_ 72f4d60d54 S com.android.smspush
u0_a58    5377  549   1679712 148664 SyS_epoll_ 72f4d60d54 S com.cyanogenport.trebuchet
clat      5497  562   50404  43536 hrtimer_na 7912113744 S clatd-rmnet_data7
u0_a72    6259  549   2530608 180712 SyS_epoll_ 72f4d60d54 S com.google.android.gms
u0_a114   6335  550   1776976 67848 SyS_epoll_ 00ef9c37bc S com.lbe.parallel.intl:mdserver
u0_a59    6718  549   1576640 33124 SyS_epoll_ 72f4d60d54 S org.cyanogenmod.profiles
u0_a114   6937  6335  228    4     inotify_re 0000009a4c S parallel.monitor
u0_a188   7145  549   1591428 41296 SyS_epoll_ 72f4d60d54 S com.android.email
u0_a85    7719  549   2424232 109752 SyS_epoll_ 72f4d60d54 S com.google.android.googlequicksearchbox:search
radio     8054  549   1577588 32740 SyS_epoll_ 72f4d60d54 S com.qualcomm.qcrilmsgtunnel
u0_a185   8091  549   1592720 59112 SyS_epoll_ 72f4d60d54 S me.twrp.twrpapp
root      8508  2     0      0     worker_thr 0000000000 S kworker/7:1H
root      8550  2     0      0     worker_thr 0000000000 S kworker/5:1H
u0_a232   8611  549   2239816 37316 SyS_epoll_ 72f4d60d54 S com.pace.octaproccesorbooster
root      9152  2     0      0     worker_thr 0000000000 S kworker/6:1H
u0_a210   10197 550   1706604 43096 SyS_epoll_ 00ef9c37bc S io.rong.push
u0_a210   10259 550   1739448 60852 SyS_epoll_ 00ef9c37bc S com.groundhog.multiplayermaster:Jpush
u0_a128   11118 549   1605876 49956 SyS_epoll_ 72f4d60d54 S org.kustom.widget.service
u0_a210   14239 550   1738424 51476 SyS_epoll_ 00ef9c37bc S com.groundhog.multiplayermaster
u0_a210   14313 550   1712160 44940 SyS_epoll_ 00ef9c37bc S com.groundhog.multiplayermaster:ipc
u0_a72    14670 549   1588524 39548 SyS_epoll_ 72f4d60d54 S com.google.process.gapps
u0_a161   15263 550   1411620 115856 SyS_epoll_ 00ef9c37bc S org.chromium.chrome
root      15684 2     0      0     worker_thr 0000000000 S kworker/3:3
u0_a161   16086 550   1118540 54232 SyS_epoll_ 00ef9c37bc S org.chromium.chrome:privileged_process0
root      27050 2     0      0     irq_thread 0000000000 S irq/606-f98a490
u0_a147   27122 550   1033376 39388 SyS_epoll_ 00ef9c37bc S com.estrongs.android.pop.pro
u0_a147   27168 27122 4496   972   skb_recv_d 00efbe671c S /data/user/0/com.estrongs.android.pop.pro/files/libestool2.so
u0_a78    27382 549   1664212 57492 SyS_epoll_ 72f4d60d54 S com.android.vending
u0_a112   28797 549   2307352 75680 SyS_epoll_ 72f4d60d54 S com.google.android.apps.photos
root      30709 2     0      0     worker_thr 0000000000 S kworker/2:1
root      31145 2     0      0     worker_thr 0000000000 R kworker/u16:1
root      31801 2     0      0     worker_thr 0000000000 S kworker/1:1
root      32058 2     0      0     worker_thr 0000000000 S kworker/6:1
root      32061 2     0      0     worker_thr 0000000000 S kworker/4:1
root      32071 2     0      0     worker_thr 0000000000 S kworker/5:2
root      32111 2     0      0     worker_thr 0000000000 S kworker/7:0
root      32123 1     1336   20    inet_csk_a 00000f018c S httpd
root      32395 2     0      0     worker_thr 0000000000 S kworker/3:1
u0_a112   32501 549   2264712 45432 SyS_epoll_ 72f4d60d54 S com.google.android.apps.photos:CameraShortcut
u0_a10    32521 549   1582132 38392 SyS_epoll_ 72f4d60d54 S android.process.media
root      32542 2     0      0     worker_thr 0000000000 S kworker/u17:2
root      32701 2     0      0     worker_thr 0000000000 S kworker/u16:5
root      32708 2     0      0     worker_thr 0000000000 S kworker/3:0
angler:/ #

can you run ps and show the output?

@MarkYisri I can't post it all. The output is too long. I will try to cut out what seems unimportant.

root      32123 1     1336   20    inet_csk_a 00000f018c S httpd

That second column is the process ID.  Run this:
kill -9 32123

For future use, or for other people, get the processes PID with:
pidof httpd


text:
TWRP not recognize my sdcard
I've ported a twrp 3.0.2 to my device (kitkat 4.4), all works nice, but when I try press backup, and select store, only shows the internal store...
Device description: Azumi a50c+ with rom Kitkat 4.4. Its a MT6582
NOTE: this works fine in twrp 2.7 but then try change to 3.0.2 the sdcard cant be select in the options
My partition is:
=================
Phone store: 8GB, divide in:
    Internal store >> 4.2GB
    ext sd card (this is a internal partition of phone store) >> 2.33
    System rom.....

=================

    =================
SDCARD: 16 GB

THIS IS THE PROBLEM, In the recovery sdcard 16gb is detected in this partition in mmcblk1p1 but cant see the sdcard in "select store" option of   twrp 3.0.2.

=================

What files of ramdisk should I modify?  check the images...

What is the best way to fix bug of my TWRP 3.0.2? Thank you very much

Which device? I guess you done something wrong or missed in fstab so it doesn't handling it well. That happens when you port. The best way is to find device tree and modify it to fit twrp needs and compile it from source. Question will probably be locked due it more fits developement questions. So feel free to contact me if you need help i'm not expert but maybe I can help.

@ЈеднорукиКрстивоје Thank you very much dude, I've solved it, the problem was in fstab and one line of init.rc... Greetings! :D

@ЈеднорукиКрстивоје hey dude, can you help me with this: https://android.stackexchange.com/questions/169120/format-preloader-and-reflash-mtk6582-sp-flashtools Thank you

I've solved it
Note: this process requiere extract files of recovery.img, you can use "CarlivImageKitchen"

add this line and flags to the /etc/recovery.fstab files, and chage /sdcard to /external_sd example:
The mmcblk1p1 is the block of my sdcard:
 # Extructure is:
 # Mountpoint #type  #partition block     # block             #flags

/external_sd  vfat  /dev/block/mmcblk1p1  /dev/block/mmcblk1  flags=display="Micro SDcard";storage;wipeingui;removable

Problem Solved!

authors: Једноруки Крстивоје


text:
locked out with system lock screen on swipe
I have an lg rebel lte from tracfone with android  5.1. I install a custom locker and then somehow set the system lock to swipe. Now when i try to unlock the phone it says systemUI has stopped and touch input fails. Tried reboot and and cant boot recovery mode. Please help!

You will need to do a factory reset to gain access to your phone. If factory reset don't solve the issue, you'll need to flash a stock firmware.

First,  turn the phone off.
Press and hold the following keys at the same time: Volume Down Key  + Power/Lock Key.
Release the Power/Lock Key  only when the LG logo is displayed, then immediately press and hold the Power/Lock Key again.
Release all keys when the Factory hard reset screen is displayed.
Press the Power/Lock Key to continue or either of the Volume Keys  to cancel.
Press the Power/Lock Key once more to confirm or either of the Volume Keys to cancel.

WARNING!
Performing a hard reset deletes all of your user data, which includes pictures, videos, and music saved to your internal memory.


text:
how to back up contacts from oneplus one to google account
how do I backup my contacts from my oneplus one to google account or make a vcf file? i have tried to sync with setting>accounts>google>contacs(sync) on my phone but it doesn't save the contacts to google account. please help.

Have you tried the contacts/people app? Menu › Export/Import › Export to card? That would ump all contacts into a single .vcf file on the SD card.

Yiou have to move your contacts from SIM card or Phone storage to the Gmail

Go to the contacts app and in the menu ( 3 dots in top right corner ) there is Import/Export.
Select Import from SIM.
Now mark all contacts you want to move, there is button to Select all
Click Ok and select to move them to Google account
Now wait till it sync your contacts into Gmail, they will be visible at Google contacts


text:
What file systems can I use for a 128GB sdcard on Android 7.1, used as portable storage
I can't find an answer to this on StackExchange. I have a phone running beta LineageOS 14.1 (Android 7.1), and a 128GB SDXC card which I want to use as portable/shared storage between devices.
I know that the built in Settings -> Storage -> "format SDcard" chooses a default file system (FAT32 with large clusters or exFAT?), but if I wanted to, could I manually format the card via Terminal to use a proper journalling file system for better data safety?
If so, what file systems could I use and what would the appropriate commands be? Would there be any other benefits or disadvantages? Would it still be portable or would I have to do something to stop ACLs/permissions being set up by default that would prevent it being swapped to other devices?
Update
Regarding comments below, it sounds like more context would help.
I'm not looking at NTFS/apple NFS as other file systems. My main "other devices" for portability would be other Android 5.1+ devices and Windows 8.1/10 (via microSD USB adapter). I'm comfortable that Windows would need an ext2/3/4/other driver or to host a Linux VM in order to read or write a microSD card that isn't in FAT* format. (I'm much more comfortable about adding ext* handling to a Windows machine than to add NTFS capability to Android, and its also simpler and less likely to give me problems because Windows would only need to access it for file management/copying, not via multiple apps of various generations on Android)
The point underlying the question is that portable storage uses FAT32/exFAT by default, without offering alternatives, and these don't have any especial data integrity provisions such as journalling, that would be integral to (and included by) several other file systems.
So its a natural question whether, by using a different file system from the default - which would of course require manual formatting and perhaps manual permissions setup - I can get the effect of universal read/writeability and portability (as with FAT*), but also gain in addition, enhanced integrity via journalling in case of crash or other data issue, which FAT* doesn't provide.

If the other devices support it, EXT4 would be your best choice. Keep in mind that, as you thought, permissions will be messy at best, so you would have to edit them to be world readable-writeable-executable quite often (bad practice and security flaw). If you want to play it safe, go for FAT32, but mind that the maximum file size would be 4GB-1. Lastly, if you are brave and believe that all your devices might support it, you could give NTFS a try.

No easy option to get a journalling FS without permissions chaos or a lot of work, then?

@DeathMaskSalesman Are you sure to recommend FAT32 for so large a storage? FAT32 is a quite bad idea for volumes of 32GB or up in size. Instead I recommend exFAT because any system that supports volumes larger than 32GB must also support exFAT as well.

@iBug Well, if exFAT is supported by many devices, then why not? Do you plan to add it as an answer?

@DeathMaskSalesman I have no idea of adding an answer. The OP didn't tell us what devices he'd like to share data among. There's so much to discuss that I think it's unnecessary.

To clarify (as OP), I asked what I needed to know. I dont need to ask about other device compatibility, the question is purely about filing systems able to be used, and permissions implications/other pros and cons... given that I can narrow down other device compatibility separately if relevant.

@Stilez Windows has the best compatibility with other things so it's best to fit others' requirements first. If OP's sharing between Win & Linux, then ext4. If Win & Mac (despite being off-topic), then HFS+. If Linux & Mac, I'll give up and recommend exFAT.

It looks like clarification would help - see update to OP.

If 'journaling' is a requirement, then the EXT family (preferrably ext4) mighy be your only choice. Otherwise exFAT is the best. Just FYI, data safety depends more on your hardware rather than software (assume there's no malware), including filesystems. Any FS on a bad drive fails, and any FS on a good drive makes few differences.

It is definitely sure that if you format it to ext4, you'll have to frequently chmod -R 777 and chown -R 0.1028 (which is actually root:sdcard_r) to ensure apps work fine. Different apps have different UIDs & GIDs and upon creating a file, the owner groups are set as the app's U&G, while permissions are set according to the effective thread's umask.
Another notice is that Linux ACL is not supported by Android, whereas SELinux is, which can cause.
The FAT family is better for not having permission support, thus preventing "permission chaos" from happening. exFAT is my personal preference for shared storages. There's no regular maintenance required.
Since you're asking here, an Android community, I'm not going to discuss NTFS & Apple's HFS as they can hardly be recognized by a common Android device. Of course you can add the support for those by yourself, but it's mainly a concern of developers.

Stock android only supports mounting FAT32 drives as portable storage if mounted system-wide (r/w).
Supported partitions may vary depending on device to device.
Its dependent on manufacturer/customized Rom maker to provide system-level drivers for volumes of different formats.
As your are using lineage OS (cm fork) it might be provided. And in case it isn't can be easily configured (recommended-the busybox way).
I wouldn't have liked to go for journaling, permission-oriented filesystems.
For external SD, I focus on accidental deletions mostly on my media and documents, so TestDisk (free command line utility) works to "Undelete Files" from old index tree with ease. Very useful.
For the partitions, to keep it simple, I like to have the following partitions and configure on all my removable drives.
an FAT32 (~75% of size) (mountable on all - desktop, phone, tablet, smarttv, router, nas)
and exFAT(~25%) (on External HDDs I use TrueCrypt to encrypt this volume) (big files - mountable on PC's (Win/Lin/Mac) and Android (atleast in ES File Explorer (an app supporting exfat) and on my Sony AndroidTV (manufacturer-provided-drivers)) and rooted nexus 7 supports it)
You may allow android to create a partition as adopted storage depending on needs. See this link for mixed partition formats while using adopted storage (Semi-Adopted storage).
Apps can ask for access to storage and mount the external drives within their own context (mount point not shared with other apps). There are apps supporting ExFat, NTFS, AFS, HFS+, and even truecrypt/bitlocker encrypted partitions. All this is suitable for external connections, since an SD card would be required to mounted almost all time and accessible across.


text:
Is it possible to update OTA a rooted android device?
So my question is plain and simple, I have a Galaxy S6 with Android 6.0.1.
I want to root it but i was wondering whether this will stop me from receiving the upcoming Nougat update.

If your device is on Lollipop or newer, and you are rooted, have custom recovery, or other modifications to /system or /boot, an OTA update will likely (98% of the time) fail, the only time it wouldn't is if the OEM is dumb enough not to check for system modifications before the script runs. Attempting to update will likely put you in soft-brick condition stuck in recovery and requiring a cache wipe to get out of it. To take an OTA update you must 100% stock or it is likely to fail.

Well, why don't you root after the Nougat update?

@DeathMaskSalesman the update isn't out yet

@AmineBirouk Wait for the update and then root, or try your luck with the experimental systemless root.


text:
Sharing Android's Wi-Fi internet connection via... Wi-Fi. Not just extending!
Well.. basically what I'm trying to achieve is sharing android's internet connection by Wi-Fi. But Android is connected to internet by.. Wi-Fi. Also, I don't just want to extend the Wi-Fi, I want to share the internet connection because the Wi-Fi I'm connected to has a password you have to input at the Wi-Fi's login page, not in settings as usual. My Android phone is rooted, and I have couple of others if more than one is needed. All of them rooted. Thanks!

You need a phone with 2 sets of Wi-Fi hardware built-in, so that one can be used to connect to your original one and one can share. Unfortunately those are incredibly rare - the only ones I know of are Huawei D2 and Samsung's S7 family.
In your case where your network requires sign-in, consider using your phone as a proxy server and set other devices to use it. Probably works, probably not, but it's the only approach I can think of.

Is it possible to hook up two phones and use one as receiver and one as transmitter?

How do you expect these 2 phones to exchange data, then? WiFi? Same problem. Bluetooth? Way inferior bandwidth.


text:
Is my device infected/hacked?
Today on a normal navigation with firefox a fake popup said
"your firefox is infected with 2 virus"
then android ask me to give to firefox the "vibration access" of course i refuse.
And then firefox ask me to going to google-play to download antivirus.
I deinstall firefox and reinstall..and the page with advice disappear.
I download then the "free antivirus" from google-play(not the antivirus wich firefox want to force me to download) and do a scan..no virus found.
But now with linux I do a nmap on android device..and port 554(rstp) tcp
is open!
Why is open?Is my device infected or what else?

Never believe adds that pretend your phone has been infected!

Delete the browser cache and it probably will vanish as you discovered after re install. It does not mean that your device infected. You may like to run a scan using Malwarebytes app from play Store.

He said 0 malaware

it can be their as the websites can exploit stagefright bug and infect it and antivirus might not know it

554 or 5554 (port)?

554 sure,telnet 554 and nmap confirm

Solution found,there is something strange on my net because i see 554 port on every machine!
But if i did a telnet outside this machine..554 doesn't answer.
I investigate..meanwhile i'm happy my android is not infected,firefox probably take a fake virus.


text:
Lock Screen Wallpaper
I don't know how to have a lock screen wallpaper on my phone. I'm using an Android 5.1 Lollipop (Omega HD3, Cherry Mobile). Where can i find the setting to set my lock screen wallpaper on my device?

while setting wallpaper in android, it will ask whether to set both, or home screen , lock screen seperately .

If your default method doesn't work then you can try installing apps from PlayStore that changes your lock screen wallpapers.

Go to the gallery, find the picture you would like to set as Lockscreen wallpaper.
When u have the picture opened, in the menu ( 3 dots - usually) there is Set as..
Just click it and it will ask you for " Set as Homescreen wallpaper / Set as Homescreen wallpaper and lockscreen wallpaper  /  Set as lockscreen wallpaper"
Now select your option.


text:
Galaxy S7 edge - How do I use a sound downloaded as part of a theme?
I want to use the sounds I have downloaded as part of my theme (Blue Polygon) as my ringtone and alarm sound. However, it is not in the selection of sounds when I tried to change it.
Please advice. I have no root access.

@beeshyams Hey, the sounds might be stored in the theme folder I believe, which requires root access.

@beeshyams A theme is not an apk though.

Van you link the theme in your question?

@beeshyams http://www.samsung.com/global/themestore/index.html?appId=com.echovisuals.www.BluePolygon

I have asked the developers and found out that this is a bug caused by setting one or more of the sound settings (notification, ringtone and volume) to silent.
To fix it, follow these steps:

Start by going to Settings - Themes, select the theme named "Default", and then apply.
After this, go through all of your settings and make sure nothing is set to Silent.
Once this is verified, re-apply the theme and it should be working.


text:
This app will not install or uninstall on my phone
I am on android, Sony Xperia M C1904 model. There is an app called "SnapChat" that I cannot install or uninstall from my phone.
What happened earlier was that I didn't have enough storage and after i made enough storage, I tried to install it again, but it tells me I have it installed.
After lots of googling, cache clearing, and removing from my "Apps", this app still would not let me install.
I have tried to remove the listing on "My Apps" from my Google Play Store (it is gone now), and it still tells me i have it installed. I looked inside my phone's 'all apps" and it doesn't even list SnapChat. I had another app called "Sky Night" that I got rid of a while back and through this method I managed to properly "remove it". On the app store, it says I have it installed but it lets me install it again at least. But this one app would just not go away or get on my phone.
For reference I used techniques from here

Get the package ID of the app in question, then use adb uninstall to attempt to uninstall it properly. If it succeeds then it'll be a thorough uninstall; if it doesn't at least it will return a reason why it failed, which you can edit into your question and let us know.

@AndyYan, how do I get the package id...? I am not sure how to use the second step either...is it something I should open?

Play Store link contains the ID. If you don't know any one of these, just go look them up - basic for Android enthusiasts.

Or try it the other way around: adb install -r snapchat.apk should force a re-install (-r of an installed package – i.e. install the .apk over an already installed version of the same package.


text:
How to remove Android/PUP.Adware.SnowFox.a Adware?
There is a hidden adware installed in my android , which slides(Pops) a full screen  add on the screen by surprise when operating the touch screen and immediately gets a click and redirects to browser or google play store and begs to install a nonsense app.
I installed Malware bytes and it has detected a adware,

And when i hit uninstall , i get uninstall successful but there it again,
I installed root explorer and browsed to the location and tried to delete it and my OS says it is read only.
Is there any other meth0d to remove the adware.?
Android version 5.1.1
kernel version 3.10.49-perf-g2808008-00335-gacd81a9ccadmin@BUILD19 #1

I think factory resetting is the next step here...

@timoschwarzer factory reset doesn't touch /system. Instead, one neads to remount /system read-write: use adb shell to get a shell prompt, then su and mount -o remount,rw /system and rm /system/app/SnapdragonCamera/SnapdragonCamera.apk, and at last a reboot. Alternatively, use one of the system app uninstallers available :)

@lzzy you are right. For some reason I didn't notice/saw the picture in the question.

The device is rooted?

@MarkYisri It is not rooted .

No wonder Root Explorer shows read-only then.


text:
Can I use full disk encryption and unlock it with fingerprint on Android 6.0?
I would love to encrypt my phone. But I would only do it if I can unlock it after boot using my fingerprint.

Nope. After boot you need your PIN/Pattern/Password.

Android is open source. Maybe I should ask in XDA developers maybe there is a kernel patch or something I can use for this. I believe this setup can still provide enough security.


text:
LG G5: Nougat: Your device is corrupt. It cannot be trusted and will not boot
Stupidly locked boot loader and now device now won't boot.  I didn't realise I was running Nougat so now the verified boot checker prevents device from booting altogether, "Your device is corrupt. It cannot be trusted and will not boot".
All I can do is get get the devices to stock recovery which is pointless as it is not picked up in ADB and I can reset to factory here either.
I don't need to retain any data I just want to get the device working again.  Any tips? Help?
Thanks
xM

Unlock the bootloader again?

Why did you locked bootloader that won't bring back waranity because when you lock it for 'bootloader state' it says 'relocked'. Try unlocking bootloader again as owlswipe said.

Yeah I didn't realise that until now - noob mistake. as GPS is faulty on my phone so wanted to take it back the shop to replace and thought I'd lock the bootloader. I can't get the device to be recognised in ADB to unlock boot loader again... any ideas?

Try this:
Turn off your LG G5.
With your LG G5 connected by USB to your computer, push volume down and power button on your phone, then release power button keeping volume down pressed.
It should boot to bootloader directly.
In this state, you might unlock it with your personal unlock.bin file:
fastboot flash unlock unlock.bin

Then check if unlock is granted:
fastboot getvar unlocked

Also, you could flash TWRP recovery from here with:
fastboot flash recovery twrp-whicheverversionfits.img

If this works, please let us know :)

This worked a treat!  Only amendment is that I had to power down the phone (removed battery) then hold volume down for 5 seconds then plug in USB - it then boots to fast boot.  I then unlocked OEM as above!

authors: Једноруки Крстивоје


text:
Does TWRP recovery support encrypted /data/ partition?
I have a smartphone that is running Android 6.0 Marshmallow. I encrypted the device using the builtin mechanism. Unfortunately I forgot the password (intentionally). The only option to recover the phone is to Factory Reset the device, either from its recovery mode or using fastboot.
My smartphone has the TWRP recovery. When I wanted to Factory Reset the device using this mode, I simply couldn't do that because TWRP wasn't able to mount the /data/ partition:

So the question is simple: How to Factory Reset an encrypted device using the TWRP recovery? Is that even possible? Does TWRP recovery support this action?

Is your recovery ported or buold from source, maybe developer screwed recovery.fstab file. In theory twrp shouldn't have problems with /data encrypted. However if you can't wipe from twrp. Flash stock firmware it should handle things.

The TWRP recovery was ported from another device. I wrote the fstab file and wiping unencrypted /data/ partition works well. I added length=-16384 and encryptable=footer to the /data/ entry, but this did nothing (I know the key is at the end of this partition and not on a separate one). I also know that the stock recovery can fix this, but I just want to do it via TWRP.

You are probably doing some wrong with .fstab. Ask question on stack owerflow or xda, developing and programming questions are offtopic here

TWRP > “Wipe” > “Format data” to re-format and mount “/data”, which deletes all data.

I've managed to solve this issue. Apparently the ported TWRP image didn't have support for encryption. That's why it tried to mount the encrypted /data/ partition. I've build the image from source, and I've set the following flag:
TW_INCLUDE_CRYPTO := true

Now it can detect the encrypted partition:

The only problem is that it can't decrypt the data with the right password. Maybe something else is missing.

Can you elaborate on how you made TWRP recognize the partition?  I'm having the same problem but definitely not nearly as skilled as you in this department.  I'm finding it hard to believe that I can't save an encrypted partition; wipe the device; reinstall the same rooted stock OS I was using; add the data partition and use the same password to decrypt the data.  I'm probably very niave.

authors: Једноруки Крстивоје


text:
The emulator process for AVD Nexus_5X_API_22 was killed
I installed Android Studio with Android SDK from the offical web-site, created a new sample project, didn't change or delete even a line, but the project doesn't work anyway.
D:\AndSDK\tools\emulator.exe -netdelay none -netspeed full -avd Nexus_5X_API_22
Hax is enabled
init: Could not find wglGetExtensionsStringARB!
getGLES2ExtensionString: Could not find GLES 2.x config!
Hax ram_size 0x60000000
Failed to obtain GLES 2.x extensions string!
HAX is working and emulator runs in fast virt mode.
Could not initialize emulated framebuffer
audio: Failed to create voice `goldfish_audio_in'
qemu-system-i386.exe: warning: opening audio input failed
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
emulator: ERROR: Could not initialize OpenglES emulation, use '-gpu off' to disable it.

02/11 16:19:14: Launching app
Error while waiting for device: The emulator process for AVD Nexus_5X_API_22 was killed.

What can be wrong and how to fix it?

Go to:  Tools > Android > AVD Manager
Press the "edit" (pencil) icon next to your AVD
Change "Graphics" to "Software".

The options is there but disabled for me in Android Studio 4.0.1 with Android 10.0 x86 :(

How this solved the issue, can someone explain...?

Did not work for me.

emulator: ERROR: Could not initialize OpenglES emulation, use '-gpu off' to disable it.

The emulator wasn't able to use OpenGL ES emulation on your PC. As the message says, you can disable it using the command-line, or by turning off the "Use Host GPU" option in the emulator's settings dialog, but then the emulator will be very slow. It would be better to run your app on a real phone.

The same happened to me, in other places I read that is a problem with the library shipped with the SDK.
The following line worked for me
$ android-sdk/tools/emulator -avd Nexus_5_API_27 -use-system-libs

Now you can see the device from Android Studio and connect to it. Probably exists an option inside the AVD configuration to fix this.

However, I got a PANIC from the command line that I am missing the engine for 'arm' CPU.
PANIC: Missing emulator engine program for 'arm' CPU.

This is what worked for me:
Go to Tools> AVD Manager > Click on downward arrow beside your emulator > Wipe data
It will confirm if you want to wipe data, say yes in that case.

The-emulator-process-for-avd-nexus-5x-api-22-was-killed????
simple change "Nexus5XApi22" to "Nexus" problem solved.

I'm curious why changing the AVD name will fix the issue about OpenGL ES emulation?

I didn't know proper reasons but its working fine

Since the log also mentioned

audio: Failed to create voice 'goldfish_audio_in'

Check your Windows 10's Privacy settings > Microphone. If it is disabled, enable it.

Are you saying enabling microphone prevents Emulator process from being killed? How did you reach this conclusion?

i was referring to this. audio: Failed to create voice goldfish_audio_in'
I had the same error with this,.


text:
Problem while rooting : <OSM> All threads completed. (succeed 0 / failed 0)
I was trying to root my SM-G920F ,which is running Android 6.0.1, when i received the following message on Odin3.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)

the phone was in download mode (Odin) and the developer option is On as it is the case with USB debugging, also the reactivation lock is off.

Android version : 6.0.1
  Baseband version : G920FXXU4DPI9
  Kernel Version : 3.10.61-8821257 Sep 16 2016
  Build Number MMB29K.G920FXXU4DPIL
  KNOX Version : KNOX 2.6

ANY help will be appreciated.

I now it's very late. Buy maybe you didn't connect your phone before add the necessary files.


text:
MTP oddities on Windows 10
I had always used USB Mass Storage to transfer files from/to devices to my PC (currently Windows 10) but my new phone (LG X Power with Android 6) no longer supports it so I'm left with MTP, which appears to be significantly slower (but I don't know who to blame). Data transfer rate is acceptable but:

Creating an empty folder on the phone from Windows explorer can take up to a minute.
I can't move files within the phone (copy never ends, no matter file size).

This happened with whatever MTP drivers Windows 10 bundle. I downloaded the drivers provided by LG but nothing improved.
I asked LG and their reply was that «USB drivers do not support Windows 10» and I need to find a computer running «Windows XP SP3 ~ Windows 8.1».
My questions:

Is it true that current Windows version does not have first class drivers for MTP?
Is there some way to address those two issues I suffer?

MTP does not support simultaneous read/write, nor edit.  This has nothing to do with Windows 10.  (See: https://en.wikipedia.org/wiki/Media_Transfer_Protocol#History)
If you want to move files within the device, you will need to either (1) do so from within the device or (b) first copy the files to your PC, then copy them back to the new location on the phone.
The goal of MTP is to prevent data integrity issues by abstracting away the underlying filesystem and preventing simultaneous access; for this reason, it is strictly less powerful than USB Mass Storage.

Thank you. No wonder LG support guys have less idea than me. BTW, is the 1 minute delay to create empty folders something to expect?


text:
How to extract data from an .APK file?
I want to extract or copy every detail that .apk contain, like for example extracting data from whatsapp.apk or linked-in.apk or twitter.apk.
Please note that I dont want to extract my personal data from any installed app on my phone instead I want extract the data and images which the app developer had added while making the app.

An APK is the same as a JAR file which is the same as a ZIP file.
Rename the .APK to a .ZIP and then extract the .ZIP

As suggested earlier, Apktool is a good option,
Requirements:

Java Runtime Environment
Windows wrapper script (Right click, Save Link As apktool.bat)
Apktool.jar

(For Linux and Mac OS the files and installation instructions are also available:  Installation for Apktool)
Usage
Copy the apktool.bat and apktool.jar files to a folder preferably with no spaces eg inside the  C:\ directory. (e.g C:\Apktool)

Open command prompt by pressing shift and right click simultaneously.
In the command prompt type apktool d [apkname.apk] (e.g apktool d WhatsApp)
Find the extracted apk in the folder with the apk name (in this case (C:\Apktool\WhatsApp)
You can now browse through the folder to find all resources of the app e.g manifest.xml and PNG images in res folder or doing a search.

Acknowledgements:
Apktool a tool for reverse engineering


text:
My device is not locking
My android device is 4.4.2 with root access.
Mode of Screen Lock is Password.
Earlier, the screen got locked with password.
Now, the screen time out in a specific time but its not getting locked with password.
Please let me know, what I need to do to fix it?
Regards
InTech

Is it a custom rom on phone?

No. Its Stock ROM only with Xposed Amplify, Xposed BootManager, Xposed Greenify, Xposed Privacy, Startup Manager & Busy Box.

Hm, well then, does it lock with password when it's locked for some time eg 10 minutes? Maybe you turned on lock phone after x minutes sleeping..?

No, only screen goes off in 10 min. without password lock.

Well you said password stopped apearing after changing screen timeout time. So try to change it back on that value. Also try setting screenlock to swipe or none and than back to password.

I did same. I see same issue with swipe also. Sometimes swipe lock appears and sometimes it doesn’t appear. After this, I removed root access from my device, reset my device & rooted my device. Then I tried these locks; Swipe, Pattern & Password. I see similar issue in all i.e. sometimes lock screen appears sometimes it doesn’t appear.

Well then it could be rom releated bug. Does it work fine wothout root on phone?

I didn’t check without root. Please let me know, what I need to do in both scenarios, if same issue without root or if no issue without root?

If error is still there without root, than only thing that you can try is flashing stock firmware. And if there isn't error when phone is not rooted than you should try different way to root the phone maybe something is screewed in rooting process

I checked. Without root, Locking Screen is working fine. After rooting, I see same problem again. There are many apps for rooting android but from beginning (for more than one year) I have been using Kingo Root. Also depending upon scenario, I removed root access, reset device and re-root device multiple times. And I never had any issue with Kingo Root. I don’t want to use any other app. Please help me to fix issues with Kingo Root. Also I does support android 4.4.2.

Just try with other app and see if it still make you troubles, just to be sure is app causes troubles or root itself. Root phone via flashing super SU from recovery, you should avoid 'one click root' apps

From beginning I have been using rooting with PC. I don’t prefer one click root or root without PC. For last one-two days, I have been performing similar tasks multiple times like reset device, rooting device, un-rooting device. Because of these tasks sometimes I am suspicious of risk of device hardware and ROM. Device hardware is MT6592 and device board is ht1_107a_iball_mjk.

I tried other apps like farmaroot, z4root, TunesGo Root etc (with PC and Without PC). In almost all cases, there are some issues/errors in rooting process. Also in some apps, language is not English that’s why I didn’t prefer to proceed. TunesGo Root is paid app. Only Kingo Root with PC and Kingo Root without PC can root my device successfully. But after rooting device, I see same issue i.e. screen lock issue.

authors: Једноруки Крстивоје


text:
SD Internal make my Motorola X Play 3rd generation reboot and unmount sdcard
I bought the fastest 32 GB SDCard : Sandisk Extreme USH-I card ( Ultra HD )
Then, I formatted it as Internal Storage ( I have Android 6)
Now, my phone reboots sometimes, and also my sdcard is unmounted frequently.
So, a lot off apps doesn't work, because they need data on the sdcard.
The only way I found to fix it, each time, is to extract phisically the SD, and insert it again... this works for like 2 hours....
Is there anything I can do about it???

Check if card is not a fake one. Also does your phone support UHS  cards of not maybe that causes a trouble.?

It is not uncommon for this to occur if the write speed capabilities of the SD card are not sufficient, we have seen many examples of this with the Moto X Pure/Style and Moto G 2015 on XDA where a U1 card does not have fast enough sustained write speeds, and replacing it with a U3 rated card works beautifully. I am not personally familiar with your Moto X Play, but it is very similar to the G series hardware-wise.
This could also be an few other issues, like a poor connection to the cards contacts. Sometimes placing a couple layers of scotch tape on the back of the card can increase tension enough to keep the card in contact with the tension contacts in the microSD slot.
This could also be a fake or counterfeit card, you can use SD Insight to check it.
Not to count out it could just be a defective microSD card, or defective hardware, but you would have to eliminate and try the other issues above before moving to this conclusion.

authors: Једноруки Крстивоје


text:
What are the different rooting methods? and what are the differences between them?
I want to know what are the rooting methods that work on a a Galaxy S6 SM-G920F running Android 6.0.1, And when to use which ?
Android version : 6.0.1
Baseband version : G920FXXU4DPI9
Kernel Version : 3.10.61-8821257 Sep 16 2016
Build Number MMB29K.G920FXXU4DPIL
KNOX Version : KNOX 2.6
ANY help will be appreciated.

'When to use which' what's that supposed to mean? You use root method avalable and root. Try looking here for root methods.

Welcome to Android Enthusiasts! Have you already checked with our rooting tag-wiki? And followed up e.g. to How do I root my Android device? And there, checked for your device? 2 links for the S6 there.

I assume you mean systemless and traditional? Just about anything with Marshmallow or higher, like your device, requires systemless root on the stock ROM.

I'm not sure about your specific device, but here are the methods I know:

Exploit rooting - root via a loophole discovered for the device - an example is the Kobo Arc
Flash rooting - manually flashing an image for your device

Kingo Root is an excellent rooting application that works well on many models. It comes in both a PC version and an on-device version.

authors: Једноруки Крстивоје


text:
How to properly increase system partition on Moto G xt1033?
I tried parted like
unit MB
rm 34
rm 35
rm 36
mkpart 34 823 2400
mkpart 35 2401 2441
mkpart 36 2441 7818
name 34 system
name 35 kpan
name 36 userdata

and then
mke2fs -t ext4 /dev/block/mmcblk0p34
mke2fs -t /dev/block/mmcblk0p35
mke2fs -t /dev/block/mmcblk0p36

And after reboot nothing applyed.
I used
this guide this guide
What i'm doing wrong?
I need to install Mokee 7.1 but there is no space for gapps. This is a problem. Help me, please, i spent about 8 hours to trying solve it and nothing got( It's sad(
Update:
My question is "After i have had resized '/system' partition and after reboot - '/system' partition has the same size. What i'm doing wrong in my flow"
Update
"This guide" link fixed (typo)
Update
So finally what have i done:
I read guide described above completely. My device is Motorola Moto G xt1033 (codename 'falcon')
I wanted to install Mokee (android OS) and after installing Mokee there are no left free space for opengapps even for the most small pack (pico).
So i decided to increase 'system' partition. I did everything that was in guide mentioned above and i tried 2 or 3 times and each time after rebooting device 'system' partition remains the same size as before resizing.
The feature of this problem is that i did everything described above with my device XiaoMi RedMi 1s (C/W) (codename 'armani') and 'system' partition (in case of Xiaomi) has been increased (i used guide mentioned above).
So my question is - Why partition remains the same size as before resizing? How to prevent it? What did i miss? What i'm doing wrong? And finally - how to increase 'system' partition for my Motorola Moto G xt1033 (codename 'falcon')?

@MarkYisri , did you understand my question? My question is My question is "After i have had resized '/system' partition and after reboot - '/system' partition has the same size. What i'm doing wrong in my flow described in here?"

I think you misunderstood. You said that "I used this guide", but the link points to your own question.

@MarkYisri , sorry, my bad, i have fixed the link, please, take a look on this link

It is not possible.
Adopted storage works for marshmallow version and later. You may not use it on jellybean or even if you updated to lollipop.
I might have been wrong in understanding your situation, so please let us know of root status and latest rom or android version you have.
There is also more complexity when creating more than two partitions.
Try what has been discussed in https://android.stackexchange.com/a/145458/90095

My phone is already rooted. Is has TWRP 3.0 or upper (i don't remember). My currently OS is Mokee (android 6.0) with pico gapps package. I want to install Mokee (android 7.0) with any package i could install. But there is no free space for gapps with Mokee (android 7.0). Why are you talking that "It is not possible." when i already increas 'system' partition on my Xiaomi RedMi 1S (C/W)? I took a look on thread described by you above and there is one more thing: my device (Motorola Moto G xt1033 (codename 'falcon')) has no slots for SD card

Don't worry, now I think I understand your situation better. Please tell if you unmounted your storage fist and also if you did it in recovery mode or not (Since your guide mentions being in recovery mode as optional however still suggesting that) . Please have a look at this thread for cases targeting internal memory and follow the sequence of entering recovery mode and the unmounting, specified in steps 8 to 11.:https://forum.xda-developers.com/showthread.php?t=2720675 also you forgot filesystem type after -t, I think it is missed only in this post not on the real scenario you executed.

Well, i can't continue with this issue because i've installed android 7 on this phone and story ended at this point. Then, phone started lagging and i've sold it. I don't have this phone any more and i can't continue investigate. Thank you for all)


text:
Unable to get output buffers (err=-38) when attempting to screen-record emulator from ADB
I am attempting to capture a video of my emulator device screen using the screenrecord feature in ADB. When I run the command adb shell screenrecord --verbose /sdcard/demo/capture.mp4 I get the following response from ADB;

Main display is 1440x2560 @60.00fps (orientation=0)
Configuring recorder for 1440x2560 video/avc at 4.00Mbps
Content area is 1440x2560 at offset x=0 y=0
Unable to get output buffers (err=-38)
Encoder failed (err=-38)
Stopping encoder and muxer 218|root@generic_x86_64:/ #

Which version of Android?

@MarkYisri, I think 4.2 or 4.4 because I'm having a similar problem!

It's version 6.0

From ADB documentation :

"Some devices might not be able to record at their native display
  resolution. If you encounter problems with screen recording, try using
  a lower screen resolution."

Documentation link :
https://developer.android.com/studio/command-line/adb.html#screenrecord
Try to use the size option :

--size widthxheight
Sets the video size. The default value is the device's native display resolution (if supported), 1280x720 if
  not. For best results, use a size supported by your device's Advanced
  Video Coding (AVC) encoder.


text:
How do I switch between QWERTY and QWERTZ keyboard layouts of the Samsung Keyboard on Lollipop Galaxy Note 3?
I come from English background and strongly prefer QWERTY keyboards. I also write Czech often and have installed it (instead of just typing Czech with English keyboard) to get Czech autocompletion/correction but it comes with QWERTZ layout. Is there a way to switch it to QWERTY (for example it can be done easily on all major PC platforms) or to remove the Czech keyboard while keeping Czech autocompletion dictionary?

Ah, maybe try http://www.wikihow.tech/Change-the-Language-in-Android I can't verify for the autocomplete options, but this post here seems to back it up.
http://forums.androidcentral.com/google-nexus-4/251675-adding-second-dictionary-spell-check.html


text:
what is the advantage of using the GPU rendering options in Android?
Here is a screenshot:

Will it speed up my device to enable the two GPU options?

Force GPU rendering and Disable HW overlays are discussed in Can anyone explain all these Developer Options?, which see. The former basically makes no difference unless you have a very old phone, because all the 2D canvas rendering is done on the GPU on most phones anyway.
The latter won't make any difference in speed but will probably use more battery power if you turn it on. Many phones have a hardware overlay built into the display controller. This is a simpler piece of hardware than the GPU, but it can only do simpler operations. In the simple screen composition cases, the hardware overlay is used, and this uses less power than doing these simple operations on the GPU. Only in more complex cases (such as while window animations are happening) does the full power of the GPU need to be used. Turning this option on will make the phone use the GPU all the time, even in easy cases, which burns more battery power. It's only useful for system integrators to debug Android on their hardware.
Show GPU view updates and Profile GPU rendering are useful for app developers to learn how efficiently their apps are using the GPU. They make extra information available, which costs a little power (but probably not enough for you to notice). They won't make anything go faster.


text:
VM Android on host Ubuntu: no sound
I'm using Android in a virtual machine while the host is Ubuntu 16.10.
I've followed this tutorial here: http://www.linux.org/threads/android-4-4-kitkat-in-virtualbox.7175/
and everything is working great. Except I can't get any sound.
My config:

VirtualBox Version 5.1.6_Ubuntu r110634
Guest: android-x86-4.4-RC2 (KitKat)
Host: Ubuntu 16.10 64bits

Settings for the Virtual machine:

settings > audio > Host: ALSA Audio Driver
settings > audio > Audio Controller: SoundBlaster 16.

I've tried to use as settings in "Host":  PulseAudio, and in "Audio controller" Intel HD Audio or ICH AC97, but for the same result.

I found the solution by upgrading my config:

VirtualBox Version 5.1.14 r112924 (Qt5.6.1)
Android 6.0.1

with settings > audio:

ALSA Audio driver
ICH AC97


text:
Error while trying to stream TIDAL from Android to NVIDIA Shield
I just downloaded the TIDAL app on my android phone and tried casting it to my NVIDIA Shield. The TIDAL app has a build in functionality to do exactly that. So I open the app, start playing a song and select the cast to shield action. After that I can see the TIDAL logo on my TV screen, but the song stops playing and the app becomes inresponsive.

As you can see the app grays out everything on the screen.
I have absolutely no idea what is happening here, but maybe someone has experienced a similar issue?
Casting the screen works through other apps, so I'm pretty sure it's related to TIDAL.
I've reset my SHIELD and reinstalled the TIDAL app without any success.

I have exactly the same problem with the Tidal App on my Samsung S6 and my Ipad. The track shows up momentarily on the Shield then it cuts to a Tidal splash screen, with no sound. As you say, everything else casts OK so it's probably a Tidal bug! PS Have just found that the problem only exists if 'Hi Fi' is selected, lowering the quality to 'High' cures the problem but that's not the quality that I'm paying £20 a month for! This bug exists when casting to other hardware too !

Has this gotten any better? I was hoping to get a Chromecast audio for Tidal and saw there were many initial issues, but wasn't sure if things have improved recently.

@jon_wu Haven't tried it recently. I instead installed the tidal.apk directly on the shield, which works besides the Hifi streaming feature.


text:
How to change device model in build.prop?
The following is my build.prop file. I just can't find the device model option so I can modify it. I'm trying to change my device model to Pixel XL so I can run Google Assistant properly.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NMF26V
ro.build.display.id=lineage_titan-userdebug 7.1.1 NMF26V 399d12a5d9
ro.build.version.incremental=399d12a5d9
ro.build.version.sdk=25
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.1.1
ro.build.version.security_patch=2017-01-05
ro.build.version.base_os=
ro.build.date=Tue Jan 31 23:31:20 PST 2017
ro.build.date.utc=1485934280
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=phenom.zifnab.net
ro.build.tags=release-keys
ro.build.flavor=lineage_titan-userdebug
ro.product.brand=motorola
ro.product.name=lineage_titan
ro.product.board=MSM8226
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=motorola
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8226
ro.build.characteristics=default
ro.cm.device=Pixel XL
# end build

Update: I have further changed the manufacturer and brand to Google and the product to Pixel XL, but it still had no effect.

It was a pain putting your long block of build.prop into proper blockquote... I removed some irrelevant parts.

@Andy Appreciate it...

Instead of doing it manually, here's an app that does it for you: Get Assistant - Root. From app comments in Play and local markets, it's verified to work with multiple models even on LineageOS.

That app is not compatible for my device..I tried to use other build.prop editing tools..

@VickyShankar Says that on Play Store? Download it elsewhere e.g. APKPure.

It worked for me, I replaced every "motorola" reference in the build.prop to "google"(strictly lowercase) and changed device to Pixel XL..also make sure all permissions are given to Google App. Love my new Assistant.
Thanks @Andy you certainly helped.

Looks like your branding is set to Motorola. Not going to work. Replace with Google. (if that dose not work, try HTC, Google's contracted manufacturer)


text:
After upgrade to Nougat phone started forgetting recent apps
After my S7 Edge upgraded to Nougat, I noticed it only keeps a few apps in Recent Apps list, as opposed to before when it kept basically everything until I removed it. The amount of apps in the list changes over time, so maybe it only shows apps opened in last X hours, but I am not sure. I haven't been able to find anything relevant in Settings. The phone isn't rooted and isn't in Developer mode.
The strange thing is that I haven't seen anybody else mentioning this issue. Does it happen for anybody else? And any idea how it can be fixed?

I believe this is a feature, not a bug. http://www.androidpolice.com/2016/05/18/android-n-includes-tweak-of-recent-apps-ui-with-clear-all-button-at-top-only-7-apps-included-in-switcher-and-quick-switch-shortcut/
The article says that Google claims that "their user research showed that over 99% of users never accessed an app further back than 7 in the recent apps UI".
Unfortunately, for the thousands of 1%ers, this is an annoying change! I have yet to find a setting to modify it's behaviour, and it's possible that it's simply not configurable.


text:
Cannot flash Moto G3 2015 due to "Preflash validation failed" error
I have a Moto G3 XT1550 phone. I had to reset the phone as its UI was restarting on its own after 1-2 minutes of usage. After the phone booted, it asked me to enter the GMail and password the phone was registered with which I did, but the phone failed to recognize the Google account credentials.
I NEVER ACTIVATED USB DEBUGGING FROM DEVELOPER OPTIONS ON 'THIS' DEVICE AS I NEVER NEEDED TO.
I performed "Wipe data/factory reset" and "Wipe cache partition" from Recovery Mode expecting that the stored Google account would be removed. But it did not. Then I came to know that it is called "Factory Reset Protection (FRP)".
Since then, I have tried everything I could find over the Internet - Bypassing FRP, flash Stock ROM (100% sure downloaded a correct one), flash custom ROM, and flash TWRP. All to no use. Even tried unlocking the bootloader (got the unlock code from Motorola's website the same). Even that did not work, saying:
C:\MotoG3>fastboot oem unlock XCYJ4AZH542XAQWBJYFF
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options. FAILED (remote failure)
finished. total time: 0.016s

While flashing any image from fastboot, it keeps throwing a Preflash validation failed error.
C:\MotoG3>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [  0.018s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)

C:\Moto G3\Mfastboot>fastboot flash recovery twrp-osprey-2.8.7-test1.img
target reported max download size of 268435456 bytes
sending 'recovery' (11170 KB)...
OKAY [  0.400s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)

I've even tried an article that tells a trick to entering the phone's settings by long-pressing a word in the Privacy Policy of the phone and opening "Define". Long pressing on a word just makes the phone vibrate and not select it.
Even attaching an OTG drive with the hope to copy FRPBypass APK to the phone's memory work as nothing shows up on connecting the OTG drive (as against expected File Explorer opening up).
In a nutshell, I have kind-of soft-bricked my phone. Left with no other option. I don't even expect the Service Center guys to do anything that I haven't tried (expect to change the ROM chip, if ever possible).
Any help, please?

Preflash Validation Errors are because your device has a newer ROM or firmware than you are trying to install, downgrading is not supported. You cannot unlock the bootloader without enabling OEM Unlocking in Developer Options either. But your question isn't really about that is it? Flashing a new ROM will not remove FRP, there is currently no working bypass for FRP on any Moto G 2015 with a security update after about April-May of 2016.

The firmware ROM I am trying to flash is Marshmallow. And the firmware on my device is also Marshmallow. The difference might be in subversions. In that case, I am helpless. What about trying unofficial ROM's? Any ideas?

You have a locked bootloader, there is no way to flash custom recovery (required for custom ROMs) or any other package that is not digitally signed. Have you looked here for a newer factory image: https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 ?

After going through the link you provided, it seems like I MUST wait for OFFICIAL Android N firmware from Motorola /Lenovo.

Be aware, none of this will allow you bypass Factory Reset Protection. Flashing a new ROM will NOT bypass this at all. At this time there is no way around FRP on the Moto G 2015 unless you have a device on an older ROM (which you obviously do not). There is no known way to remove or bypass FRP on this device and a new ROM will not help.

I don't care about whether FRP can be bypassed or not. In short, knowing the fact that my device is having Android 6; and that no official or unofficial ROM above Android 6 is available for this very model, what options do I have?

I'm confused... I thought the end result was to get around the FRP and have a working phone? Patience will likely yield a new enough ROM image appearing on XDA, but that might take days, weeks, or even months, we never know how quickly they can be acquired from Moto, especially since being absorbed by Lenovo, but the FRP will still be there even if/when we get that factory image. Otherwise with a locked bootloader your options are limited to Moto service to repair/reflash the device (they have a different way of doing it than you or I do).

Thanks ace for being with me in the discussion. I'll check with Motorola Service, if they can do anything about it


text:
Decompile/Recompile Apk on Android device
So I am running Phoenix OS and I have installed Termux.
Is there a way to decompile and then recompile an apk inside of android.
I see this required for Apps here and there but I don't have a physical computer.

"I see this required for Apps here and there" - huh? Examples?

@AndyYan that's a fair question http://android.stackexchange.com/questions/25999/is-there-an-app-for-searching-installed-apps-dumb-search-alternative

Then keep in mind that APK-related tools on Android are often incomplete in function compared to their PC counterparts. Also, with the current complexity of Google App, I doubt whether it can still be decomp'd properly - last I did a decomp/recomp to it, it failed at recomp.

@AndyYan hmm that is said I like the web because everything is essentially open source to be viewed and edited.  I was hoping to get a similar experience on android.

@AndyYan where are you getting such information that apps can't be recompiled?  If I ask another question could you explain the current situation?

I had a similar occasion about a year ago where I had to decomp/recomp Google App to change some resources, but it failed on me, so I gave it up. I don't know about the current situation, though, so it's still worth your try.

@AndyYan What was the error?

@DeathMaskSalesman Can't remember precisely, it's been a while. I only knew it was a complaint thrown out by apktool.

@AndyYan Hmm. Did you run it from Windows?

@DeathMaskSalesman Sure. It could be anything that caused the failure though - I was using the command line back then and naturally it could introduce human errors.

@AndyYan It's just a guess, but I think that the error might've been related to the encoding. Once, I tried to recompile a particular APK, which failed due to ApkTool using ISO-8859-1 instead of UTF-8, whilst some resource folder sported a non-ASCII name. Recompiling on Linux succeeded, as did removing the oddly named resource.

There is the original APKTool by iBotPeaches & friends and there is a version modified by AndroBlack for use on Android directly. There are x86 compatible versions on AndroidFileHost linked to from the post there.

No, here is the official response from the developer here.
To quote

We leverage a couple of Java7 features that aren't completely in AOSP
  yet. Most of this being the java.nio2 library. Additionally our YAML
  library (SnakeYAML isn't compatible on top of Android).
Finally, our native binary (aapt) that has builds for Mac 64/32, Unix
  64/32 and Windows doesn't have an ARM build for AOSP. That is why.

What's that link supposed to be? Not working for me -- pops up as http://read%20speeds%20of%20550%20mb/s%20and%20write%20speeds%20of%20520%20MB/s and I definitely don't have that copied into my clipboard, lol.

@l3l_aze trying searching github.  That is where it likely came from.  Either that or the official website.  Sorry been a while since I have messed with this.


text:
How can I get the Samsung settings menu on a non Samsung Phone (Android)
Just got a new phone for work, the trouble is that I am finding it really difficult to use and navigate the Android 6.0 settings menu on it as I am used to the one from Samsung. Is there any way I get the Samsung version of the settings menu on my new work phone? (Blu R1 HD)

This is probably not possible, or at the very least rather difficult. TouchWiz, which is Samsung's custom Android UI "skin", is not available to download and install on the device of your choosing.
There might be a way to get it running on a rooted phone but I'm guessing that's not something you want to attempt, especially if it's a work phone.
The only other possibility is to look into 3rd party launchers such as Nova but I don't know which, if any, affect the settings drawer.


text:
How to disable in app notification counter in whatsapp?
Even after muting the chats, WhatsApp still highlights and counts the number of unread messages in an already muted chat.

As you can see, there are unread in app notifications still there even the chats are muted.
I have a rooted device running Lineage OS 14.1 (Motorola's Moto G4 Plus).
Please don't mark this answer as duplicate, as the other thread's answers are not working for me.
ShutApp is not working for me (Android 7.1.1). Someone on ShutApp's website pointed that it doesn't work on Marshmallow too.
This is ShutApp's link:-
https://github.com/eladnava/shutapp-android#usage

So, those answers are not working for you. Still doesn't deserve another question on the same topic. You can bring the original question to the further attention by upvoting, adding a bounty, editing to include your concerns, etc.

@wbogacz Okay sorry. Didn't know that.