text:
Are Exchange server policies permanent?
My company support Android on their Exchange server, but they have policies (lockout, and password policies) that get applied to my phone. Are these permanent, or can they be removed later if I stop using the service?

No, they are not. For as long as you have the account registered in your email app, the policies are applied, however, if you remove the email account then the policies will no-longer be enforced.
The app is given a "device administrator" status (you can see any apps which have this in "Security" in your settings), and you can revoke that at any time. Revoking it, will of course, cause your email to stop working.


text:
Google Nexus S USB Drivers for Windows 7 64Bit
Anyone knows how to get the Google Nexus S to be recognized by the Windows OS. The only option I could find was to download the Android SDK and then use the driver from there, but unfortunately, it is a very big download and I wish to find a faster way to connect and check the files and folders on my Nexus S

The USB Driver for Windows is available for download as an optional SDK component. You need the driver only if you are developing on Windows and want to connect an Android-powered device (ADP, Nexus One, or Nexus S) to your development environment over USB.
Are you going to develop android app or just want to browse the internal memory?
http://developer.android.com/sdk/win-usb.html

The problem with the link that you have provided is that, it requires the SDK to be downloaded and installed on your system. This is the thing which I wish to avoid for now.

The link on that page does seem to point to an 8.3MB USB driver which works fine on my system without downloading the SDK. Here's the direct link: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

source: Stack Exchange

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

sort: votes


text:
Prevent deletion of all data after 10 incorrect unlock attempts
"You've incorrectly attempted to unlock the phone 1 times. After 9 more unsuccessful attempts, this phone will be reset, which will delete all its data."
This is actually worse than just letting the attacker access my data, because now I can't get at it either.
As such, this lockscreen is actually worse than not having a lockscreen.
This phone is a (Tracfone) Alcatel (TCT) A577VL (supposedly a Pixi 5 HD), and it doesn't appear to be rootable easily.
1) How do I get rid of this feature, or replace the lockscreen application, without rooting?
2) The A577VL (Pixi 5?) does not appear to officially exist according to Alcatel; can I root it to fix this more easily?

Screenshot (click image for larger variant)

"This is actually worse than just letting the attacker access my data, because now I can't get at it either." – I disagree. This is security – and for the second part, you have a backup. Haven't you? // As for "getting rid": Do you want to disable the lock screen completely (which can easiliy be done via settings) – or just disable the deletion part (which might be achieved by disabling the integrated lock and using a 3rd party lock screen)?

"This is actually worse than just letting the attacker access my data, because now I can't get at it either." If an attacker gets hold of your phone, I assure you that you aren't going to get it back, nor will you be getting the data from it unless you have everything backed up somewhere.

@Izzy to answer your question, i've clarified the first point

@MichaelKohne i'm far more concerned about the case in which someone (a fellow student, or an unruly young family member,  for example) just sabotages my phone by abusing this feature -- they know they would get in more trouble for stealing it (or it would be inevitable that I get it back) than trying to unlock it, so they would just leave it where I left it, having succeeded in their harassment. alternatively, having factory reset the phone, now it is their device, freshly from the factory, and not my device, and there's nothing i can do to prove ownership short of the removable serial number

OK, valid points, @cat – take a look at my lockscreens app listing then. Personally, I'd avoid those with too many permissions (numbers in the square boxes next to the app name) – especially CM (Cheetah) and GO (both: ads, trackers: mouse-over the "monitor icons" in those lines for details). "C Locker" is a good one, though. Haven't tried the others.

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


text:
Find a malicious app
I have a Google Nexus 5.
Recently i had a problem about WI-FI, it just could not be turned on. I've found many suggestions how to fix that. None of them but turning on in safe mode solved the problem.
As i know, safe mode disables third party apps, which potentially can cause a problem.
I wonder how can i detect exactly which app caused wifi problem ?
What i think now is brute force approach, that is, to delete all the apps one by one and see what happens.

Can I ask how are you sure that WiFi problem is related to an app?

@SarpSTA I'm not sure. It is related to Safe Mode and as safe mode disables apps, i thought that it was related to app

You can begin with listing out all the apps which have the permission android.permission.CHANGE_WIFI_STATE. You may  use Izzy's answer to list those app in fewer steps or my command-line based answer.

Do a brute force approach, but not by uninstalling apps one by one. Do it  in the  permission control. First go to settings, then go to permission control, then go to wifi and then uncheck app one by one . This may be woks


text:
Android 6 Update Changed SD Card Name
I have a Motorola Moto G3 Smartphone and I installed the Android 6 update yesterday. After installing the update, I found out that all my playlists, App preferences and basically everything that relied on the external Sandisk 16 GB micro SD card is Messed up or damaged. I found out the cause of this is that the base name for the SD card has been changed from 'sdcard1' to '3835-3237'. I am unable to change the SD card name in Mobile (using ES file explorer) or externally via PC (no matter what I change it to, it still shows those numbers on my mobile). I have a heavily customized my phone and I would prefer not to root it just to change the SD card name. Could anyone please tell me a method to change the SD Card name without having to root the phone? Or any way I can do it externally?

Android 6.0 now uses the volume serial number of the formatted partition as a unique identifier to distinguish which SD card you might be using.
I guess this could be useful in case you have a device that could theoretically support multiple SD cards.

Is this based on opinion? If not, can you provide us  means to independently verify your claim in first paragraph?

Here's a screenshot on my device, showing how my SD card is called in /storage (77EB-1515 in my case)
(Solid Explorer)
If I run the command blkid (root needed) to see all the attributes of all block devices, you can see the SD card has that UUID
(Console)
You could do the same in Windows or any other operating systems using OS-specific commands.

And it could also be extremely counter-productive: imagine your heavily-customized phone references /storage/1234-5678 in lots and lots of apps,  and then you buy a faster SD card. Now what? Reconfigure everything?

You could change the volume UUID to match the previous card if you don't want to relink everything to the new volume.


text:
Absolutely cannot reset my Moto G 2nd gen tracfone
So I have had my phone sure Christmas and everything has been functioning properly. Now all of a sudden my phone has no bars anywhere I go, I cannot use the home button, notifications don't work, quick settings menu doesn't work, and my lock screen doesn't work.
After looking through multiple online threads I have decided to factory reset my phone, but one problem, my factory reset button is greyed out for some reason. When I try to hard reset my phone via the command prompt thing that, you can only get to by holding the buttons a certain way when it's starting, I go to "Factory" and it just starts up normally. Although if I go to recovery my phone shows an Android guy with a circle and a slash through its chest.
I have tried all 4 options I have under the command prompt thing with no avail.
I am running Android 6.0 if that helps.
Also my brother has the same exact phone and Android version but we can't figure out why his still works
Any suggestions?

I have the EXACT same situation (had it since Christmas, had all the same issues you listed when I updated to Marshmallow, and my mom has the same phone and factory reset hers with no problem). I just did this so I'm not sure if it's just a quick fix, but I got my notifications and lock screen back (home button still doesn't work though).
Go into settings and click "users"
Switch to your guest user (if you don't have one set up, you can probably set it up)
You should get any notifications that are for the whole phone (ie if there is WiFi available or if your storage is close to full; app notifications shouldn't come up)
Go back into settings>users and switch back to the owner account on the phone.
Your lock screen should return, along with any notifications you missed. The drop down settings menu is accessible as well.
Like I said, the home button is still unresponsive for me, and I'm not sure if this is a long term solution, but at least it's something!


text:
Nexus 5X no "Charging rapidly" on original (stock) charger
After 7 months LG Nexus 5X now doesn't show "Charging rapidly" but only "Charging".
Ampere app shows 1700 - 2100 mA max. Overall charging time now 50% longer than initially was.
In accordance to screenshots of Ampere I see the following wattage:
4.07V * 0.89A = 3.62W
or
4.26V * 1.79A = 7.62W
Both measurements are far from 15W declared by Nexus 5X specs.
I have checked my original 5X charger with Nexus 6P phone - it displays "Charging rapidly" on 6P from my charger. This makes me to believe the issue with the phone or its battery or QC IC (Quick Charge integrated circuit).
Update:

My charger is OK with Nexus 6P -> "Charging rapidly"
Nexus 6P charger doesn't detected on my 5X at all -> no charge, nothing
Switching cables on 6P charger with 6P phone -> 5X cable OK on 6P "Charging rapidly"

Conclusion: Phone Nexus 5X itself is suspected: battery or charger chip or system.

Somewhat related: Android phone “charging slowly”: How to make it faster

My question exactly about the issue with the stock (original) charger from LG and original cable for Nexus 5X. I did not play with any third party cables and chargers.

As Andrew clarified in his answer , it is the wattage that counts not just the current as measured by Ampere app (which appears to be fine).  You would need to measure the voltage also to see if the wattage (product of voltage and Ampere ) is fine.

In accordance to screenshots of Ampere I see the following wattage:
https://goo.gl/photos/EJSwT76mD3dmVDU9A
4.07V * 0.89A = 3.62W
or
4.26V * 1.79A = 7.62
Both are far from 15W declared by Nexus 5X spec.

So that means it could be a problem with charger and cable combo. One way to confirm this would be to try another original set if you can lay your hands on it or with different chargers. Alternatively, now that you know that wattage could be the issue take to service centre, device still being in warranty and post the outcome as a solution if it is solved, else edit question with inputs

Today a have checked my charger with Nexus 6P - it displays "Charging rapidly" from my charger. This makes me to believe the issue with the phone or its battery or QC IC.

The answer by @rajatpunkstaa seems to be correct by your own testing and summation. Did you try to reflash the firmware manually via fastboot?

@acejavelin not actually reflash with downloaded FW but full factory reset through recovery menu. Did you mean this one? Or should I download system image from Google and reflash it then?

@SergeySergeyev I would reflash image just to be sure

 I had the same issue with my Nexus 6P. Tried everything but nothing worked. Visited service centre and got it fixed. They told some hardware issues with the fast charging chip.
 I read somewhere that flashing the firmware again using Fastboot on the phone solves this issue for some users.I didn't worked for me. Might you wanna try. Good Luck!!


text:
How do i reinstall the android OS?
I accidentally wiped my tablets systems firmware in recovery mode which deleted Android it self. But what do I do now?
more info
Samsung Galaxy Tab 4 7.0
Android version: KitKat 4.4.2
TWRP recovery
That was my Stock Rom. I just need it so that i can revert to it if need be.

There are many things you can do.
But first you have to identify which tablet you are using, if its samsung then install kies and recovery will take you through the process.
Second check your model number xyz whatever.Download the rom to your pc and
Transfer the downloaded ROM from your computer to your device. You can use the USB cable to perform this task,leave the ROM ZIP file in the root of your phone's SD card; it will make it easier for you to find the file when you need it.
visit this link you will understand more.
http://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool


text:
Edit password.key then unlock phone
I just did a strange thing.I went to data/system, there was password.key file.It was consisted of almost two lines of text included more numeric and few alphabets.I just edited it and add "32" at the end of second line using ES file explorer.Then I locked my phone,now i am unable to unlock it. How can I unlock my android phone without factory reset?

Do you have a custom recovery installed?

ROM Manager app says your phone is not listed for custom Rom


text:
How to change input method on 5.1.1
I cannot see the "select input method" command in the pull down menu like in Android 4.
By experimenting, I discovered you can select the input method if you long-press the space bar in Samsung keyboard.
I used this to switch to Hacker's keyboard.
But that keyboard doesn't support the space bar long press convention.
So, I cannot change back.
Edit: the long press method is a feature of Google Japanese Input, not the Samsung Keyboard, sorry. I can change the input method via Settings/Language and input/Default Keyboard. That is far too inconvenient for regular use.
Edit: I remember seeing on some Android version a good mechanism for this: a little keyboard icon displayed while in input mode. I feel it must be somewhere; I'm just not looking in the right place.

Settings -> Language & input. What options do you see there? Is there an option named "Selector icon"?

@Firelord No such thing there.

Found it. Stupidly, you have to pull down, then scroll through the entire stack of notifications. "Select Keyboard" is buried at the bottom!

authors: عبدالكريم اعبو


text:
My IP address is wrong. How can I change it
I live in Iowa but my IP address is from another state. Why? I would like to change it to my area.

This is due to your cell carrier assigning random IP addresses to the phones connected on its network. It doesn't mean your IP address is wrong, it just means they don't have any available IP allocation available in your area.
The easiest thing you can do is connect to WiFi networks while browsing on the Internet, that will give websites a better idea of your location.
Installed Android apps do not care what your IP address is. If they need your location, they will use GPS to find your location (Google Maps does this). Websites won't use your GPS because that invades your privacy. They don't need to know your exact location, unless you want them to know (such as ordering off Amazon).
I hope this clears up the issue

Thank you very much for your help. I really appreciate it. Have a good day

@MelindaRohrer-Baldwin Glad to see Aaron was able to help you. If his answer solved your issue (which it IMHO did), please accept it (by ticking the little check-mark next to it). That way other users can recognize your question has a solution, even when seeing it in a list of questions. Thanks in advance!


text:
Is there an Android File Manager app that allows to browse rapidly through photos stored on a remote SMB share?
I have a desktop with Open Media Vault 6 installed, and I have set up a SMB 2 (also tested with 3) share on it so that my girlfriend and I can get access to our photos from any device via Tailscale VPN. When I connect to the share via my laptop connected to the VPN (I made sure to connect with the public IP addres of my OMV desktop and not through the local network), I can see my 4k photos loading quite fast in Windows Explorer, like 20 per second or so. However, if I connect to the share through an Android file explorer like Solid Explorer, File Manager Plus or MiXplorer the images a quite slow to load, like 1 or 2 per second. The only one that I found that was faster than the rest (loads around 5-10 pictures per second) is X-Plore, but it has no galery layout so browsing through photos is really not great.
To add more context, I have a Pixel 8 with Android 14 and my girlfriend has a Galaxy S22.
I don't know why nearly all File Manager apps are slow and I was wondering if some of you would have any guess and suggestions of things to try to improve the speed.
Thanks

Hi, please note that questions directly asking for app recommendations are off-topic. While the question body has reasonable scope, the current title is considered problematic. Otherwise, you might be interested in our sister site, Software Recommendations Stack Exchange instead.

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


text:
How do I get my device detected by ADB on Linux?
I just got my shiny new Wileyfox Swift – and before putting it to use I want to oem unlock and root it (as I usually do with new devices ;) Trouble is, though usb-debugging is enabled on the device, and a corresponding line in /etc/udev/rules.d/51-android.rules exists, the device is not seen by adb devices.
I know there are several answers scattered around this site, but they are either hard to find, just cover a specific device, or don't cover all steps I finally needed. So I take this as a chance for a canonical, device-independent question and give it a detailed answer below:
How can I get my Android device seen and used by adb on Linux?

Enable USB debugging on the device
This is done in Settings › Development. If you don't have that entry in your settings menu, go to Settings › About, scroll to the "Build number", and hammer it like a monkey until your device congratulates you having become a developer. Go back to the main page of the Settings menu, and close to the bottom you should see the "Development" (or "Developers") settings now. Enter it, and enable USB Debugging here.
Identify the device
First we need to know how the device identifies on the USB bus. For that, with the Android device NOT connected, grab a shell and run the command lsusb. Then connect the device and run the command again. Spot the new line. For the Wileyfox Swift this is a "nameless device":
Bus 004 Device 003: ID 2970:2282

Setting up the rules for ADB
We now need the numbers at the end of the above line: 2970:2282. These specify the vendor (2970) and the device itself (2282). Having those details, we need a root shell on our Linux machine to edit (or create, if it doesn't yet exist) the /etc/udev/rules.d/51-android.rules file. In there, add a line for your device. Following example line shows how it looks for the Wileyfox Swift:¹
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2970", ATTRS{idProduct}=="2282", MODE="0666", GROUP="androiddev", SYMLINK+="android%n"

If you have a different device, replace the vendor and product IDs with what you've found above when running lsusb. A short explanation of the line:

SUBSYSTEMS=="usb": obviously this rule is for USB only ;)
ATTRS{idVendor}=="2970": the vendor ID of the device this rule is for
ATTRS{idProduct}=="2282": the device ID
MODE="0666": permissions the device node shall get. 0666 is quite lax, giving every user on your system read and write permission – so if you're concerned, you might try replacing that with a 0660 (giving only owner and group read-write, and deny everything to others).
GROUP="androiddev": which group the device node should belong to. This should be a group the users intended to work with the device belong to.
SYMLINK+="android%n": just to give the node a nice name, so you can find it easier in /dev (in my case, it later showed up there as /dev/android5)

That rule entered in /etc/udev/rules.d/51-android.rules, we must tell udev to make use of it. Safest way (next to a reboot ;) is restarting the udev service. Depending on your Linux distro, this can be done either via sudo service udev restart or sudo /etc/init.d/udev restart.
Done that, leave the root shell. Disconnect and reconnect your Android device, try adb devices again. Most devices showed up now, but not the Wileyfox Swift – which obviously wants some extra cuddles. If you're in that situation, open (or create if it doesn't exist) the file ~/.android/adb_usb.ini and add a single line to it, naming the vendor you've found out with lsusb above; for the Swift that would be 0x2970 (yupp, here you need to prefix it by 0x to point out it's a hexadecimal number). Then restart the ADB server: adb kill-server && adb start-server. Disconnect and reconnect the device again. Now adb devices should see it.
Connecting the device
You might have noticed adb devices told you something like 0123456789ABCDEF  unauthorized. That's OK and for your (devices) safety: your computer must be authorized first to be able to access the device. So simply issue adb shell now – which will be quit with an error: device unauthorized. Please check the confirmation dialog on your device. Follow that advice (optionally mark the check-box to permanently authorize your computer), and you're done: Now you can use adb to access your device.

Updates:
¹ Note that in later Linux versions, syntax for the UDEV rules has slightly changed, as e.g. jcomeau_ictx pointed out in his comment. For the values we found above that would be:
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", ATTR{idProduct}=="2282", MODE="0666", GROUP="plugdev", SYMLINK+="android%n"

Two differences: it's now SUBSYSTEM (no plural), and the group has changed from androiddev to plugdev (the former does not exist on recent systems, the latter does and usually is assigned at least to the first user).
Additionally, you might need to add the vendorID to your ~/.android/adb_usb.ini (one ID per line, in hex notation):
# ANDROID 3RD PARTY USB VENDOR ID LIST
# 1 USB VENDOR ID PER LINE.
0x2970

the format for the udev rule was different on my Jessie system: `jcomeau@aspire:~$ tail -n 1 /etc/udev/rules.d/99-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="201d", MODE="0666", GROUP="plugdev", SYMLINK+="android%n"
jcomeau@aspire:~$ cat ~/.android/adb_usb.ini
ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
USE 'android update adb' TO GENERATE.
1 USB VENDOR ID PER LINE.
0x0e8d`
I had to ignore the advice to run android update adb and enter it manually as you stated.

@jcomeau_ictx thanks for the feedback! As far as I can see from your comment, it's just using a different user group (plugdev instead of androiddev). Not verified, but I'd say the important part here is that it's a group your user (which you want to use USB with) has as well.

also SUBSYSTEM instead of SUBSYSTEMS, ATTR instead of ATTRS, comma after MODE="0666"
not sure if all those changes were necessary, but that's what worked.

Oh – thanks, missed those small ones, @jcomeau_ictx – good point!

For Linux Non Savvy folks sudo wget -O /etc/udev/rules.d/51-android.rules from here worked for me for my Xiaomi Mi A1 . Of course it's better to learn but good to be lazy :)

On some distributions you restart udev with udevadm (see https://unix.stackexchange.com/questions/39370/how-to-reload-udev-rules-without-reboot).

Great answer. One thing to add: it is possible for higher-level udev rules which target the same vendor to override / conflict with lower-level rules. So if you have a rule targeting ATTR{idVendor}=="2970" in 51-android.rules and then another rule in 99-bad.rules targeting the same vendor id, the latter may make the former ineffective. Something to look out for.

@Andy I didn't dig that deep into udev. And as that's not limited to the Android rules, it might make a question better fitted at Unix & Linux, don't you think?

On Android 11, I see the rules group as plugdev, NOT androiddev, as previously mentioned. Not sure if it's related to Android or Linux Mint

@beeshyams you saw that that is mentioned with the update already? And it's got nothing to do with Android as it's the Linux part. Not even with Android-11, but with the "Linux version" – you see that update was already done in 10/2017 when not even Android-10 was released ;)

Stackexchange should be like reddit. I wanted to give away 50 points of my credit directly to upvote/award this answer. I lost days with this issue in internet searching and implementing so many voodoos that you see around. +50, why is that not possible?

Thanks @JoãoPimentelFerreira – glad I was able to help! Unfortunately not even a moderator has influence on the "minimum amount" of bounty credits. And I agree that 100 as a minimum is a bit high, especially if one has not much credits to give. 50 would be a good number. Maybe a corresponding question exists on Meta.SE with a reasoning or even the request to adjust…

@JoãoPimentelFerreira strange, according to this answer, you should be able to put a minimum of 50-rep bounty. I may refund your bounty if you want to try it again.

With mode 0666, the group will not matter, any user will get access regardless. You want mode 0660 instead. Gee.

A few comments from a newer Linux distribution. Fedora 29 with a Nexus 5X or the Nokia 7.1 (Android One) phone.
First disconnect the phone, if already connected.

Install android-tools which will supply ADB (sudo dnf install android-tools)
Copy udev rules (sudo cp /usr/share/doc/android-tools/51-android.rules /etc/udev/rules.d)
Reload udev rules (sudo udevadm control --reload-rules)
Restart ADB to be sure (sudo systemctl restart adb)

Now connect the phone and run adb devices from the command line. You will probably see a device listed with "no permissions". This is fine.
IF it is not listed, you will have to add your device to the udev rules file, but for me, the tested devices just worked with the pre-defined rules.
Run adb shell and hopefully you will get a security notification on the phone asking if you want to trust the computer, select yes.
IF instead your computer says "error:insufficient permissions for device", you need to make sure that on the phone you have set your USB port to "Transfer files" mode, and not "Charge this device". On Android 8.1 this is located in settings under "Connected devices" > "USB".
I have noticed that even if you have everything working today, that tomorrow it may suddenly break for no apparent reason. If that happens, first check the USB port setting on the device, which may have changed back to charging mode, and if that fails, revoke USB debugging authorisations on the device (in settings under Developer options), and you should hopefully get the pop-up again when you run adb shell.
With this, I am able to run Android Studio and run on the connected device.

I have played around with USB packet sniffing with Wireshark and had used the modprobe usbmon module. When this module is loaded adb does not work anymore. In this case rmmod usbmonand adb kill-server helps.

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


text:
What's com.superthomaslab.rootessentials?

What is com.superthomaslab.rootessentials? Having root access, no icons no name, just a package name. Please note that this app isn't installed on my devvice

You have lucky patcher ... Most luck patchers are malware now, unless it's actually from the original developer, i would guess it's something to do with a trojan ... just a guess.... Have you checked if it's a widget or if it can be launched from the settings menu ?

The app linked is developed by one of our community with same name. @SuperThomaslab

That app was installed at one point and granted root, then later uninstalled which is why the package name is showing up in SuperSU with no icon instead of the application name. You can test this with any app you've granted root access to. Uninstall it and the same thing will happen.


text:
Default ATI Path Change setting on Samsung Galaxy A20
I've just purchased my Samsung Galaxy A20 and was configuring my settings, and I'm unsure what this specific setting does.
ATI Path Change (Both)
[0] Physical UART path
[1] AP path
[2] Both ATI, No RmPC

I accidentally hit my screen and it chose an option. Now I'm unsure what the default setting was.
I've tried to look it up but no luck to help guide me on the right or default setting was.
I've chosen "Both ATI, No RmPC", but which one was the default setting?

The default is:
(2) Both ATI, No RmPC


text:
Installing LineageOS on Samsung Galaxy Tab S2 from Mac
I have a Samsung Galaxy Tab S2 stuck on Android 5.0.2. I wanted to upgrade the software to LineageOS. There is a lot of information out there, but nothing that can help me.
A few things first that I need to share. I'm using a Mac. I once unlocked my device and Knox is now void, so it must be unlocked. I can't tell if the bootloader is unlocked. I tried to check using an app, but came back with an error of "Sorry! root access is not properly installed on this device". The tablet is in developer mode, there is no OEM mode or anything like that, and USB debugging is turned on.
I have tried several things using Terminal but they didn't work with homebrew and ADB services. These are installed on my Mac. I got as far as trying to add fastboot devices, and it was denied on the terminal, but that probably makes sense if the bootloader is locked.
Most instructions imply that you know what to do and don't explain much. Can anyone please assist with step-by-step instructions so I can complete the process of installing LineageOS?

Have you looked at the instructions in the LineageOS wiki? They are pretty step-by-step, up to telling you which keys/buttons to press when to achieve what.

@Izzy: The right idea but the wrong link ;) This link should point to the correct device: https://wiki.lineageos.org/devices/espressowifi However the Tab S2 is no longer maintianed by LineageOS, hence you won't find any official LineageOS builds anymore.

you may still find old builds somewhere https://android.stackexchange.com/q/213272

@Robert Oh, I missed "tab". Wasn't InitCapped so I didn't recognize it as part of the name #D Apart from that: It's a Samsung device, so steps might be comparable. But maybe better check with one of the other tabs then which are close to that. I'm not a Samsung user, so I cannot really tell which ones that might be…

Thank you for all you advice. Ive tried looking on lineageOS couldnt find anything to help. I'm not sure what download mode is to check bootloader status. if Tab S2 is no longer maintained by LineageOS is there no hope, I want  an update as  near as possible for the tablet. 5.02 is very old

This picture provides a proof of a successful installation of LineageOS.

This guide explains how to install LineageOS (open source Android) 21 (based on Android 14) on Samsung Galaxy S10 from Debian or Ubuntu Linux.
The question of this thread was asking on MacOS Linux not Debian Linux. On macOS you will have to find a way to install adb, fastboot, and heimdall by searching on the internet. adb is installed easily with Android Studio or with a standalone download. For heimdall and fastboot, there are many answers on the internet. You should use fastboot and avoid heimdall for flashing all the .img. Fastboot cannot be used for everything. You need heimdall for the recovery.img that needs heimdall once to create a fastboot mode on the device, this mode is shipped with the lineageOS recovery.img. And the program I used on Debian is called fastboot, not fastbootd, so without an ending D.
This guide can work for other phone models. The combination of buttons to start fastboot mode or download mode may change.
The model I have does not have a fastboot mode at all but it has a download mode and a recovery mode from Samsung.
The download mode allows to flash a recovery from Lineage os that can run a fastboot mode and do other things like install non official binaries using adb sideload
Note on nice Lineage features:

Lineage allows to have security updates on devices that Samsung stopped to support for security updates.
Lineage allows to have a newer Android version.
Lineage is secure due to its open source nature (Like Linux kernel, or Debian). A few security companies support it.
LineageOS 21 (Android 14) when it starts, it allows to copy all settings from another Android using Bluetooth using a QR code that one phone takes with the camera (we do not have this at startup on the original Android 12 after a factory reset).
LineageOS allows to install old Androids for testing purpose.

1. Preparation and set OEM unlock

Back up all data so you do not risk losing data.
Enable debug mode in Android settings pressing 7 times build version
In developer mode set USB mode and set OEM unlock, that is the thing that protects flashing another Android.

Bootloader unlock and OEM unlock are 2 different things. And following the next steps of this guide, you will need 3 steps. OEM unlock in settings, bootloader unlock in the download mode screen, and then a trick to make OEM be grayed out in settings and really triggered.
Remember that pressing all buttons will shut down the phone if you are stuck
After later reboots, you will see OEM enable. And if something does not work later, go back to this step and check it.
Install adb heimdall-flash and fastboot
note: adb could be used from Android Studio
adb is to run commands on the device and to push files and to reboot in download mode
heimdall is to flash the recovery.img
fastboot is to flash all remaining .img after booting in recovery
sudo apt update && sudo apt install default-jdk
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
sudo apt install heimdall-flash

Download all the files for lineagesOS from the website, and pick the right device. All files are important.
Pick the latest Lineage version you can find.
Download gapps of the right android version. it is for goole mail apps, etc and recommended by guides.

Note: as a commenter said, the Android SDK is not mandatory. I used adb from the Android SDK because I had it already. But you can have adb via the apt install command above.
2. Enter Download mode
Download mode is a mode that allows using heimdall, a flash program for Linux
It depends on devices,
volume down + bixby + plug in USB cable that is connected to the computer, enter download mode
Another way to enter download mode is via adb reboot download when the device is in USB debug mode (an option in developer settings, and developer settigns is enabled by pressing 7 times the build number in software information in the settings on Android).
3. Unlock bootloader
It documents one the screens what you can do.
In download mode pressing volume up for a long time will unlock the bootloader, to allow installing and flashing
3. bis ensure OEM unlock is grayed out in the settings
Before you move to step 4, you must ensure that OEM unlock is present and grayed out in the Developer settings in a Android.
If it is not, you will not be able to flash any custom binary.
There is a combination of tricks to ensure that it is that way.
It was found on a tutorial that I give for curiosity, but I will sum it up.

Go in Android and put the time to a date older that 8 days ago.
Remove auto time update.
Search in settings there are several places with automatic updates, even security updates.
Reboot Android.
Now go in the Settings and find the reset, to factory reset Android.

The phone will restart, and like all new you must pick the language, etc. You do not need to enter your Google Account. Do the minimum setup since you will override it later by LineageOS, but it is important that you connect to a working WiFi, with the WiFi password. And you must perform the update.
After the phone starts, go in the settings and enable the developer options (it shows up with tap 7 times on the row Build number in Sofwware information). And in the Developer options, chevk that OEM unlock is grayed out in the list. If it is you have succeeded.
Enable the USB debugging in the Developer settings.
4. Use the adb command to start in a better version of download mode with less text
~/Android/Sdk/platform-tools/adb devices

if adb devices does not look good, you need to unplug the USB-C cable and plug it again, to trigger a reconnection. It is important that USB debugging is activated in the Developer options
~/Android/Sdk/platform-tools/adb reboot download

There are two different download mode: the adb way and the bixby + volume down and plug in power cable. It is recommended to use the adb reboot download to flash heimdall.
For later: To enter Recovery mode, restart from volume mode that allows volume up + bixby + power for a long time and it enters the recovery mode
lineageos has a recovery you can flash
heimdall can be installed on Debian
it is heimdall that can flash the recovery
be sure to have OEM unlock in debug options of android, then in download mode boot, unlock bootloader
then if your reboot enough and wipe data then heimdall will have no error and can flash
use "adb reboot download"
to enter a good mode for the download mode so you can flash with heimdall
If the command below results with a red line of error (only official binaries...) on the phone's screen, you miss the step 4. bis above.
heimdall flash --RECOVERY recovery.img --no-reboot

The --no-reboot is important so you have time to leave the download mode and immediately press the right buttons for the recovery mode.
If you are not fast enough, it will erase what you have just flashed when rebooting. This trick was found on link 2 at the end.
For me, heimdall had an error "ERROR: Failed to receive session end confirmation!"
and on the phone screen it said only official binaries are allowed.
So I missed the step 3.bis above.
Then I could make it work without error.
For this kind of error, it is important to reboot in download mode using adb
adb reboot download, and this may need to be down after a standard android startup.
So I erased data in the samsung recovery mode, and I check OEM unlock is well set.
It is important you do not skip the bootloader unlock above.
5. trick to enter recovery mode
At this step you are in download mode and just flashed with heimdall a recovery.img from lineage
press volume down + bixby
it will leave the download mode and reboot
as soon as the screen change, press very fast volume up + bixby + power, and keep pressing for 20 seconds until the phone enters recovery mode
If you fail, you cant press all button to shutdown everything. Put the phone in rest. and later enter again the download mode using one of 2 ways (adb from a started Android, or volume down + bixby and then insert power cable when phone is shutdown).
Recovery mode is much easier to enter by holding pressed very fast the right buttons when leaving download mode using 2 buttons. You cannot just start the phone and enter recovery mode that easily.
6. In recovery mode if you have reached it, it will say recovery at the top in a very special screen
you will have the lineage logo on top if you have the good recovery mode.
If it says Samsung at the top, then you had an error in the heimdall command and need to go back to step 3.bis and check the bootloader is unlocked.
Important: you can navigate inside  recovery mode using volume up and down to move the cursor, and power button to select an option.
If ever you need adb, note that the recovery mode has an option to enable adb, but you should not enable it if you do not need it since it can affect the sideload installation mode which is another adb mode

Wipe all data, it is safe.
Then enter fastboot in the menu.
It takes a long time to boot it.

Then use the fastboot command from Debian to flash all files (you may have more files downloaded from LineageOS's website)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash dtb dtb.img
fastboot flash super_empty super_empty.img
fastboot flash vbmeta vbmeta.img

The super_empty may fail, but it is not important
and the recovery you do not need it you already have it.
now reboot in recovery mode
7. Install programs
be sure the gapps has the corresponding android version number.
rename the lineageos zip in LINE.zip
and rename the gapps.zip in MIND.zip
it prevents bugs to have shorter paths it is recommended by all guides
TWRP, another recovery image, uses adb push to /sdcard, but TWRP does not work on Android 10+
With the recovery image from lineageOS, we use adb sideload
You need to select in the recovery mode menu:
Apply update
then go to adb Sideload and in sub-menus
you must go deep so that the sideload is activated
when you run adb devices it should say sideload.
adb devices can say unauthorized, recovery (if you do enable adb in the menu), or sideload
Now run sideload on the linage zip
do not check to reboot
~/Android/Sdk/platform-tools/adb sideload LINE.zip

You need to navigate the menu and pick deep in the menu apply update to
be able to have sideload access with adb. And you may need to move in the menu and pick yes.
Then install gapps
~/Android/Sdk/platform-tools/adb sideload MIND.zip

Then reboot.
And you will have to leave OEM unlocked and bootloader unlocked forever. If you disable it from the download mode, it will block the restart in a loop and it will be difficult (but possible) to shutdown and then to set it back from the step above (long press on volume button)
The first time it may ask to wipe data and to reboot.
Leave it time with the rotating logo.
Then Lineage starts well.
Be sure to check the right options and not not go too fast,
like the checkbox auto updating the recovery image when updating.
FINISHED.
the information below is just for extra help and information.
In the Trust settings (searching Android security patches), it says vendor patch is NOT up to date. It refers to the firmware from Samsung. There is a firmware provided by LineageOS for my device. But I decided NOT to flash the firmware. Because during 5 years owning the device, Samsung never made me update that firmware. And I am not 100% trusting for that LineageOS firmware. But I use my phone with low risk, not paying with it, etc.

Setup LineageOS to make it user friendly
I recommend moving one level up the text size just after the LineageOS installation is done and starts. it is on level 2, and I put in on 3.
To copy data from another device, you may need to pair manually the device in the Bluetooth menu (slide from top bar), and do it on both devices
On the source phone, open google app (installable in google play)
And type set up my device in the search bar.
To perform this operation from the destination device, you need to wait for a notification that says last step to set up device (slide top bar to see it in blue notification).
You can install missing things like Google Photos from the Play Store.
During the initial configuration, The fingerprint sensor may take 15 seconds to appear, just be patient on the black screen.
I use English as a system language. For the keyboard, I use a French (querty) with autocorrection that give suggestsions of words for the accents. Android keyboard (AOSP) has 2 entries in the settings, one called manage allows you to pick a language. There can be multiple already set up. If you pick just one, like French (Querty), it will be the only language for the keyboard, and also it applies to the spelling correction.

useful adb commands:
If ever you need adb, note that the recovery mode has an option to enable adb
~/Android/Sdk/platform-tools/adb devices
~/Android/Sdk/platform-tools/adb shell uname -m               (to know the Android version)
~/Android/Sdk/platform-tools/adb devices
~/Android/Sdk/platform-tools/adb reboot download

one can see all the partitions using this print command, but in download mode only
heimdall print-pit --no-reboot
one can set a device in root using "magisk" but it is not recommended to have root
NOTE:
Better use the recovery.img from Lineage's website than to use TWRP.
usual twrp on the internet that is more powerful to perform the installation
However twrp has a problem with dynamic partitions

archive of old versions of LineageOS

Links that I used:

for the Linux method, but I had to adapt it for my device:
to debug starting in recovery mode
the heimdall error about bad download mode not launched by adb as it should
the heimdall error about OEM
how to start download mode for Samsung Galaxy 10, it depends on the device

If you are on Windows, this guide explains how to use Odin windows program, and TWRP (but TWRP does not work for Android 10+, so use the standard recovery.img from LineageOS)
it worked on a galaxy S4, GT-19515, code jfvelte

main wiki
Install odin and install TWRT on the device (you must have a tar and use the app button only)
you can skip the Samsung kies USB drivers since its hard to install
The acat procedure in ODIN is here : and you need a tar
remove auto reboot or TWRT will not show up
then in twrt wipe 3 places and then reboot again in twrp

adb.exe is here: once Android stdio is installed and and SK is installed in SDK manager
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools\adb.exe devices
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools\adb.exe push .\lineage-18.1.zip /sdcard
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools\adb.exe push .\gapps11.zip /sdcard
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools\adb.exe shell rm /sdcard/gapps11.zip
C:\Users\thierry.vilmart\AppData\Local\Android\Sdk\platform-tools\adb.exe shell rm /sdcard/lineage-18.1.zip

Do not forget to remove those zip files to free space after setting up LineageOS, you need to enable debug mode (7 taps on build number in About phone)
and then in develop options you need to enable USB debugging
then the phone itself must allow always with a checkbox

you're probably talking about fastbootd. take note downloading sdk is not necessary as google provides standalone platform_tools

Thanks for the input. My model of Samsung Galaxy S10 does not have fastboot mode. I use download mode to flash the lineageOS recovery that ships in a fastboot mode.
Yes no need of android SDK. It is in my guide that adb can be installed via apt installed on Debian. I use the adb from my SDK because I already have it.

Samsung devices does not have fastboot mode, at least i am not aware of Samsung devices with Mediatek chipset
the bootloader lock status can be checked only from download mode screen
step by step instructions vary on device and android version. your android version 5.02 may not have OEM unlocking in developer options, you can skip this step
on the other hand be aware Samsung does improve security continuously and may roll-out new features even to old devices, which leads in non-working tutorials
also rooting apps like Magisk do silently change usage at will which may end up in data loss if tutorial isn't up to date

Magisk is advanced for root control and not necessary.
Samsung has download mode that must be launched with adb reboot download. And download mode allows to flaf a recovery mode  that is from lineage, and that installs a fastboot mode and also allows copying lineage with the sideload menu. you must go deep in the sideload menu for adb sideload to work with access.


text:
Removing white transparent space caused by Google Search Bar on the home screen after disabling Google app
I would like to know how to remove this artifact of the Google Search Bar after disabling the Google app.

Possibly there is a search bar toggle in settings somewhere?

Change the launcher app. Some stock launcher apps don't allow removing the Google search widget.

What happens if you long press on it?

think changing the launcher app may be key to removing this bar

That's the Google Search widget, but since you disabled it, it looks like a gray bar.
Just long press on it then you should be able to remove it as you would do with other widgets.
Check this video out on how to do it: https://youtu.be/Vn07c-5XcdM

this is not a normal widget because a long-press has no effect even after re-enabling the search function

I have never encountered such issue. I am not sure to be honest


text:
How can I dump UI hierarchy to a variable in Bash?
I want to dump the output of uiautomator dump to a variable and read it from there. How can I edit the below script so as to achieve that?
#!/system/bin/sh
while true ;
do uiautomator dump
sleep 1
done

Comments are not for extended discussion; this conversation has been moved to chat.


text:
Why downloaded videos by VidMate can only be played using PLAYit?
I have downloaded a video from YouTube using VidMate. The video is in 1080p and is in MP4 format.

When I tried to play it on mobile, it was not playing. I also tried it on PC using VLC Player, but it can't play the video too. Instead, the player shows this

I tried converting it, but no video converter is able to convert it.
I researched VidMate and found out that it says "use PLAYit player to play the video". When I download the app, it plays successfully.
Why can downloaded videos by VidMate only be played using PLAYit even though it is in MP4 format?

Looking from user reviews for 'PLAYit' and searching for 'VidMate', looks like videos downloaded using VidMate are now encoded/encrypted so that it can only be played using PLAYit. I haven't tried examining the downloaded video in detail, but it already looks shady enough...

yes i have tried things like converting but no converter in converting that encrypted video, and unfortunately there is no decrypter is available yet. but the solution is that use some old version of vidmat and never update it.


text:
"Package installer keeps stopping" error when trying to uninstall Zoom Android app
I have a Nokia 6.1 Plus running Android 10. I am unable to uninstall the Zoom Android app. When I try to uninstall, I receive an error message "Package installer keeps stopping".

I don't get the error while uninstalling/installing other downloaded apps.
How to uninstall this app?

Uninstall from Play store?

Uninstalling from play store worked for me !


text:
Will installing cyanogenmod7 on my Samsung Vibrant require me to wipe my phone first?
I'm interested in putting CyanogenMod on my Samsung Vibrant (Galaxy S).  The FAQ on Cyanogenmod says:

Q: Do I have to wipe my data before I install CyanogenMod?
A: Short answer: Maybe. Long answer: Maybe.

I understand there's a possibility if something goes wrong that I might have to wipe my phone.  However, in the Vibrant instructions right after booting into ClockworkMod Recovery it says to "wipe data/factory reset" and "wipe cache partition".  That seems to me to indicate that a factory reset is required, which I would think would wipe out everything on my phone.
Is it just that the Vibrant's instruction require a reset or am I not understanding something?  Thanks!

In my experience, yes.  I tried without wiping and CM7 failed to boot.

My experience, too. I tried once and I boot-looped. I tried a different time and it booted, but practically everything I opened force closed.


text:
Any android app capable of storing "unsent tweet" then send it out when internet connection is resumed?
As question, I have found something called offline twitter, but seems that it is broken in my HTC ChaCha, as I can't copy the "pin number" from twitter site back to offline twitter. Thanks.

A number of 3rd-party "social" apps have this feature.
Personally I use TweetDeck.  When Internet connection is not available, it will save my tweet, and throw a notification saying that it will be sent when connectivity is re-established.

Same for me with twicca.


text:
Double click word doesn't select it
I'd a Samsung Galaxy I5510 with stock rom, android 2.2. Whenever I double-clicked any word in an input field it got selected. Now I bought a Samsung Galaxy Ace I still have stock rom and andrond 2.3.4 and double-clicking a word does nothing. Is there any way I can get this functionality back? It was very useful to add words to swype after typing them.

Apparently this functionality lays on the keyboard. I'd and old version of Swype (which came installed). After rooting, I followed this instructions to update Swype and now I get this functionality back. Good luck to everyone!


text:
Blank Circle name in Google+
On my Google+ Android app (version 2.1.1.219805) there is a Circle with no name. There's no one in the Circle.
When I check Google+ on the web, this mystery Circle is not there. All of my Circles are as they should be.
I've already Force Stopped and cleared the data for the app.
What's going on or, at least, how do I get rid of it?

A new version of the app came out today (2.2.0.233662) with "numerous bug fixes" mentioned in the "What's New" text.
This apparently is one of the fixes. Everything is back to normal now.

This is not the resolution you are looking for, but I'd like to share that I have same problem with you.
The blank circle appeared a few days ago.
 There's no blank circle when I check Google+ web page, but there's a mysterious circle with no name (blank name) when I use Google+ android app.
I tried to uninstall and reinstall Google+ app, but it didn't resolve the problem.
Only a few people have reported this problem, and there's a post related to this on Google group too.
I hope it can be fixed soon.

Thanks for saving me from trying to re-install the app. Can you provide a link to that post?


text:
What are the differences between a system app and user app?
As I've played around with different ROMs and used Titanium Backup, I see that apps are categorized into system and user apps.  Several ROM developers state that Titanium Backup should only be used for user apps and not for system apps, and when I proceed to uninstall system apps, TiBu warns me that the ROM may not work correctly.
Other than the fact that user apps are downloadable via the Market or some other means, what are the key differences between the two?
What is it about the system apps that make them more integral to the OS itself?

/system is read-only without root so it prevents uninstalling applications from /system/app and /system/priv-app.  Applications that are critical are put there so that they can't be uninstalled.  Carrier bloatware that they don't want to let you remove is also put there.  The latter category of apps can be removed if you are rooted; the former, not so much.
/system/priv-app also allows apps installed there to use signatureOrSystem and other privileged permissions.  Stephen's answer has some examples.
As for why apps might be critical, that depends on the ROM.  HTC's Sense is heavily dependent on their built-in apps from what I hear, for example.  They simply didn't design their UI such that it would work natively with third party apps (or fail nicely if the system apps were missing).  Other apps are essentially part of the Android OS but Google coded them as apps/services (probably for encapsulation and reliability reasons).
Updates for some system apps can be downloaded via the Play Store, such as Google Maps.  If it didn't come preinstalled as a system app on your device then you can use Titanium to convert it from a user app to a system app.

does it also mean that a system app cant be killed by task killers?? or that they would auto start if killed??

@ashishsony System services are normally auto-started, yes, but (most?) apps/services can still be killed.  For example I can kill the Browser on my device.  (Insert usual advice about how task killers are bad.)

Correct, system apps on HTC Devices (even those like Dropbox, Facebook) are too deeply integrated with the Sense UI. One must refrain from removing them; also converting user apps to system apps should not be done unless very necessary as on some ROMs they might not terminate under low memory condition.

@all one programmatic difference is system(priv-app) application  receive a system broadcast even is force_stop from application settings, when  (user-app) non-system app can't receive the any broadcast if is force_stop from device settings.

The other answers are correct, but fail to point out a couple differences:
Permissions
System apps are granted the ability to request certain system-only permissions that are never available to user apps. This is not the same as root/sudo/su permissions.
One example that I know of and use daily is the ability to reset the missed call notification counter. I have Go Dialer, which is a replacement for the stock dialer and contact app (how you make phone calls). When I miss a call, android lets me know that with a notification. However, Go Dialer is not allowed to reset this counter, even though it asks for that permission when you install the app. Android 2.2 and earlier let user apps reset it, but made this permission a system-only accessible permission for android 2.3
By moving my Go Dialer app to the system partition, it is allowed to reset this counter. Root is not required for the app (except, of course, to actually move the app to the System partition).
Another system permission is the ability to set the current gps location. Now, Android does have a preference where you can allow mock locations, so any gps spoofing app you install can declare a gps location. But if the app is in the System partition, mock locations can be disabled while still letting the app spoof the gps location.
Updates
System apps can be updated just like user apps, but the update is never integrated into the original rom. That is, system apps have the unique ability to roll back to the version that existed when the rom was first installed.
Move to SD
Android lets users move user apps from internal memory to the sd card. System apps cannot be moved and always take up some internal space. Most (all?) devices, though, have internal user apps on a different partition, so uninstalling a system app would not give you any more user app space (other than the dalvik-cache being removed).
You will recover some space if you uninstall any updates to a system app. As noted, the updates are not integrated with the rom and are thus stored in user space. The updates are not allowed to move to the sd card either, but if removed, user space is recovered.
How it affects you
If you are a casual android user, you likely won't run into scenarios where system vs user app would make a difference. If you are an advanced user, you likely have root and can thus change a system app to user (and vice versa) if you ever run into one of these situations.

Did you mean "This is not the same as root/su permissions"? I seem to recall that sudo and su are not the same - at least in Unix and Linux.

You're right that su and sudo are different in *nix. But sudo is more applicable here, because sudo is asking for root privileges, whereas su is simply asking to Switch User. In order to use su, you only need to know the password of the account to which you are switching; if you don't specify an account, then you are asking to become root. In Android, however, there is no root password, nor any other accounts, so su is the command known by users to run in a terminal to gain root privileges.

At any rate, I'll update the answer to include su, since that is what some Android users equate to root.

System apps are apps that are included within the system. They are located in the /system/app folder.
The vast majority of them are required to make the device run. An example of some of these are the dialer, which sets up all the network connectivity, and browser, without which no in-app webviews would work.

The dialer sets up the network connectivity?

@MatthewRead Yes - It does! The actual 'Dialer' is a seperate activity located in the dialer application. The dialer.apk is the app that sets up the connectivity - if you want proof, freeze the dialer and dialer storage apps, the network wont work.

I would like to add something in the above answers. System apps cannot be deleted in a full factory reset, unlike user apps. So if you want to delete all your personal files but they are too many to be deleted conveniently that a factory reset is only the most convenient, and you have apps you want to keep, you can convert those apps to system apps so that they won't be erased during the factory reset.

Interesting tip! I want to move my music to system now lol

Another feature of system apps is that they use native libraries (libsomething.so files) from the common system libraries directory (typically /system/lib or /system/lib64), and not from the app-private libraries directory (e.g., /data/app/com.example.HelloJni/lib/arm). Before Android Nougat, user apps were free to load and use the system native libraries. Restrictions have been imposed later, see https://developer.android.com/about/versions/nougat/android-7.0-changes.html#ndk.

authors: Алена Назарцева


text:
How to solve "insufficent space on the device" error on Samsung Captivate
I have a Samsung Captivate, running the stock Froyo ROM, rooted.  When I try to install a large app from the Market, I get the error "insufficent space on the device", for apps of ~40 MB, with 700+MB free.  I first noticed it with "Jelly Defense" on Google's Christmas-week sale, but you can see it for yourself if you try the free "Reiner Knizia's Labyrinth" which is also quite large.
This is a common problem -- just Google it and you'll see dozens of posts around the Internet going back almost a year. From those posts, I've tried two free apps that are supposed to help, "Market Fix" and "Cache Fixer", but neither has done the trick yet.  As I understand it, both are supposed to re-mount /cache as a loopback file on the SD card.  I don't know why they don't work.  If anybody has fixed this specifically on the i9000 series (SGS1, Captivate, Fascinate, etc), please let me know how!

I had this on my Vibrant and now that I think about it I think it went away after I cleared the cache.  Interesting.

Always the way, innit?  5 minutes after I ask, I stumble across this.  It's not super elegant but its success is in its simplicity.  Simply replace the dedicated /cache partition with a link to the internal SD card, and Bob's your uncle.  Has to be repeated on reboot, so not perfect, but way better than not installing at all!

The reason you're getting that error is because your /datadata cache is filling up. The way I solved it on my phone was to get the MarketFix app from the market, and run that. It's a small app, so you shouldn't have any trouble downloading it. This probably does the same thing you found, but you only have to run it once.


text:
Phone says that it is "up-to-date" after a canceled update
I have canceled a Marshmallow update download by accident, and now when I got to check for updates, the phone says that the device software is up-to-date.  How can I fix this?
Phone: Moto G 3rd Generation
OS: Android 5.1.1
EDIT:  Unfortunately I cannot check solutions because recently the phone asked me to update to Marshmallow again, and this time I accepted.

You can try clearing data for the updater app under Settings -> Apps
Try checking for update after this.
I'm not sure whats the exact name of app in AOSP/Moto G rom.
For CM the name of app is cmupdater.
Hope this helps.

@Elena : Your update might be stored in cache partition.

@Firelord:  I cleared the cache partition, but it didn't work.  Thanks anyway.

You could either try to clear the whole cache of your phone via Settings > Storage & USB > Cache > Clear cacheor you could try to update through Motorola's desktop app.

OTAs (updates "over the air" to your device) are often distributed in waves to reduce server usage and affect fewer users with errors that could be found in an OTA. By cancelling the download, you may have missed your chance in this wave and the server will only tell your device that an update is available in a later wave. However, the PC companion app shouldn't be affected by this.

Unfortunately I cannot check your answer anymore, because recently the phone asked me to update to Marshmallow again, and this time I followed through.

good for you, I guess :)


text:
Phone stuck in bootloop even after flashing stock ROM
I currently have a phone named Symphony W17 (MT6572). I had flashed stock ROM using SP Flash Tool, but it's stuck in the boot loop. I tried clearing data and Dalvik cache from recovery but no luck.
fastboot getvar all
(bootloader)    partition-size:userdata: 32000000
(bootloader)    partition-type:userdata: ext4
(bootloader)    partition-size:cache: 17800000
(bootloader)    partition-type:cache: ext4
(bootloader)    partition-size:system: 28a00000
(bootloader)    partition-type:system: ext4
(bootloader)    partition-size:expdb: a00000
(bootloader)    partition-type:expdb: raw data
(bootloader)    partition-size:logo: 300000
(bootloader)    partition-type:logo: raw data
(bootloader)    partition-size:misc: 80000
(bootloader)    partition-type:misc: raw data
(bootloader)    partition-size:sec_ro: 40000
(bootloader)    partition-type:sec_ro: raw data
(bootloader)    partition-size:recovery: 600000
(bootloader)    partition-type:recovery: raw data
(bootloader)    partition-size:boot: 600000
(bootloader)    partition-type:boot: raw data
(bootloader)    partition-size:uboot: 60000
(bootloader)    partition-type:uboot: raw data
(bootloader)    partition-size:seccfg: 20000
(bootloader)    partition-type:seccfg: raw data
(bootloader)    partition-size:protect_s: a00000
(bootloader)    partition-type:protect_s: ext4
(bootloader)    partition-size:protect_f: a00000
(bootloader)    partition-type:protect_f: ext4
(bootloader)    partition-size:nvram: 500000
(bootloader)    partition-type:nvram: raw data
(bootloader)    partition-size:pro_info: 300000
(bootloader)    partition-type:pro_info: raw data
(bootloader)    partition-size:ebr1: 80000
(bootloader)    partition-type:ebr1: raw data
(bootloader)    partition-size:mbr: 80000
(bootloader)    partition-type:mbr: raw data
(bootloader)    partition-size:preloader: c00000
(bootloader)    partition-type:preloader: raw data
(bootloader)    kernel: lk
(bootloader)    product: UP11_ID_SYMPHONY_W17
(bootloader)    version: 0.5
all: Done!!
finished. total time: 0.078s

...................................................................

Firmware I flashed - https://www.mediafire.com/file/8csalmwtcxf0nme/Symphony_W17_V01.5_UP11.zip
SP flash tool version - 5.1516
Scatter - https://drive.google.com/file/d/12jhrdeM8bKjPU5Ej0KZVfEK4ZBg5DVzq/view?usp=sharing
MT6572_Android_scatter.txt
############################################################################################################
#
#  General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
  info:
    - config_version: V1.1.1
      platform: MT6572
      project: mtk_android
      storage: EMMC
      boot_channel: MSDC_0
      block_size: 0x20000
############################################################################################################
#
#  Layout Setting
#
############################################################################################################
- partition_index: SYS0
  partition_name: PRELOADER
  file_name: preloader.bin
  is_download: true
  type: SV5_BL_BIN
  linear_start_addr: 0x0
  physical_start_addr: 0x0
  partition_size: 0xC00000
  region: EMMC_BOOT_1
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: BOOTLOADER
  reserve: 0x00

- partition_index: SYS1
  partition_name: MBR
  file_name: MBR.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0xC00000
  physical_start_addr: 0x0
  partition_size: 0x80000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS2
  partition_name: EBR1
  file_name: EBR1.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0xC80000
  physical_start_addr: 0x0
  partition_size: 0x80000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS3
  partition_name: PRO_INFO
  file_name: NONE
  is_download: false
  type: NONE
  linear_start_addr: 0xD00000
  physical_start_addr: 0x0
  partition_size: 0x300000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: PROTECTED
  reserve: 0x00

- partition_index: SYS4
  partition_name: NVRAM
  file_name: nvram.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x1000000
  physical_start_addr: 0x0
  partition_size: 0x500000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS5
  partition_name: PROTECT_F
  file_name: protect_f.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x1500000
  physical_start_addr: 0x0
  partition_size: 0xA00000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS6
  partition_name: PROTECT_S
  file_name: protect_s.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x1F00000
  physical_start_addr: 0x0
  partition_size: 0xA00000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS7
  partition_name: SECCFG
  file_name: NONE
  is_download: false
  type: NONE
  linear_start_addr: 0x2900000
  physical_start_addr: 0x0
  partition_size: 0x20000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: INVISIBLE
  reserve: 0x00

- partition_index: SYS8
  partition_name: UBOOT
  file_name: uboot.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x2920000
  physical_start_addr: 0x0
  partition_size: 0x60000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS9
  partition_name: BOOTIMG
  file_name: bootimg.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x2980000
  physical_start_addr: 0x0
  partition_size: 0x600000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS10
  partition_name: RECOVERY
  file_name: recovery.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x2F80000
  physical_start_addr: 0x0
  partition_size: 0x600000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS11
  partition_name: SEC_RO
  file_name: secro.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x3580000
  physical_start_addr: 0x0
  partition_size: 0x40000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS12
  partition_name: MISC
  file_name: misc.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x35C0000
  physical_start_addr: 0x0
  partition_size: 0x80000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS13
  partition_name: LOGO
  file_name: logo.bin
  is_download: true
  type: NORMAL_ROM
  linear_start_addr: 0x3640000
  physical_start_addr: 0x0
  partition_size: 0x300000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS14
  partition_name: EXPDB
  file_name: NONE
  is_download: false
  type: NONE
  linear_start_addr: 0x3940000
  physical_start_addr: 0x0
  partition_size: 0xA00000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: INVISIBLE
  reserve: 0x00

- partition_index: SYS15
  partition_name: ANDROID
  file_name: system.bin
  is_download: true
  type: YAFFS_IMG
  linear_start_addr: 0x4340000
  physical_start_addr: 0x0
  partition_size: 0x28A00000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS16
  partition_name: CACHE
  file_name: cache.bin
  is_download: true
  type: YAFFS_IMG
  linear_start_addr: 0x2CD40000
  physical_start_addr: 0x0
  partition_size: 0x17800000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS17
  partition_name: USRDATA
  file_name: userdata.bin
  is_download: true
  type: YAFFS_IMG
  linear_start_addr: 0x44540000
  physical_start_addr: 0x0
  partition_size: 0x52C00000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS18
  partition_name: FAT
  file_name: fat.bin
  is_download: true
  type: YAFFS_IMG
  linear_start_addr: 0x97140000
  physical_start_addr: 0x0
  partition_size: 0x4E5E0000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: true
  is_reserved: false
  operation_type: UPDATE
  reserve: 0x00

- partition_index: SYS19
  partition_name: BMTPOOL
  file_name: NONE
  is_download: false
  type: NONE
  linear_start_addr: 0xFFFF00A8
  physical_start_addr: 0x0
  partition_size: 0x1500000
  region: EMMC_USER
  storage: HW_STORAGE_EMMC
  boundary_check: false
  is_reserved: true
  operation_type: RESERVED
  reserve: 0x00

you forgot to flash stock recovery (or disable dm-verity in case wanna keep TWRP)

I flashed stock recovery and firmware using sp flash tool but im stuck in bootloop. What should i do now ? Do you have telegram , discord or anything ? Please help me!!

Don't worry you will get help here. But please be descriptive - update your question with output of 'fastboot getvar all' (with IMEI + Serialno censored) and post link to stock ROM or scatter file used, and also partitions list selected for flashing, maybe there is a discrepancy

I colud not write not write it here. So I have written it on pastebin. Here is the link of the paste - https://pastebin.com/x6qsnTWQ   ...... Please help me!

there is discrepancy userdata partition 1.3 GB or 800 MB which partitions did you flash and what download mode selected?

I selected format all + download mode on sp flash tool. Userdata partiton was 1.3gb

you formatted whole eMMC so maybe some partitions got lost. you can try to fix with MTK tools

can you guide me ? please

This partitions probably got lost. This can partially restore some data, but I cannot guide you I never did. XDA is a better place to have such conversations, Android Enthusiasts is Q&A site only (1 Question, 1 Solution)

some notes regarding SP Flash Tool https://android.stackexchange.com/q/232584 https://android.stackexchange.com/q/209989 https://android.stackexchange.com/q/212931

Hey. I flashed another rom and it booted but when i try to erase storage from recovery it says unable to mount /data also i cannot install any apps. its saying that i dont have enough storage. here is link of scatter and firmware - Scatter - https://drive.google.com/file/d/1V4Ly5h8xQnIezIiKK6KrCbtROH90FHVX/view?usp=sharing
Firmware - https://androidfilehost.com/?fid=673956719939828710 . please help

i think its stuck in bootloop again. tried flashing again with that rom but still same

something is different this time. did you flash custom recovery?

i did nothing my phones battery died so i charged it and when i tried to start it its stuck in the starting logo

someone told me to repartition my phone's internal storage. do you know how to do it?

you did already with SP Flash Tool Format all, that's why your persist and nvram partitions are gone - bad advise. Let us continue discussion on xda

you are my only hope. none other replies to my questions


text:
screen mirroring from android tv box to smartphone
I want the opposite of screen mirroring, from android tv box to smartphone.
Reason I want remote control apps on android tv box with smartphone but avoid over the air streaming.
The android tv box is rooted and connected via ethernet LAN port to my home network.
Google TV and other screen cast apps require wifi enabled on tv box (which is disabled). I prefer solution over TCP/IP. scrcpy can control over adb which works on tcpip too, but it's for PC. Therefore I am fine with middle solution control PC from smartphone + control tv box from PC
What can I do?

If you just need to control your AndroidTV without viewing the screen on the smartphone you can use your phone as remote control: https://support.google.com/androidtv/answer/6122465?hl=en

tried com.ecloud.eshare.server it works but unfortunately touch input does not control tv (you can extract apk from Beelink S82 Plus TV Box firmware here)

gms is outdated and does not support android 7.1.1 tv box for some reason. therefore cannot use google tv

was able to install CetusPlay on set top box. it can share screen or remote control at least. unfortunately not simultaneously, that are two separate modes. maybe I should try teamviewer?

couldn't get teamviewer to work


text:
How to disable headphone jack in Android
I want to completely disable headphone jack in Android 10 without using 3rd party app.
I want to disable headphone jack and use headphones with USB Type-C to 3.5mm jack connector via usb instead.

i have edited your question, please feel free to revert if i got your goal wrong. it should be sufficient if you restrict google play services access, did you check android settings for headphone jack permissions? did you check usb settings when usb headphones connected? there is also some usb settings in developer options


text:
Galaxy Note 5 suddenly stopped booting up and in recovery mode has dm-verity and failed to mount errors?
All of sudden when I was trying to use my note 5 (unroot), I noticed that it was powered off and I couldn't power it on with power button. Can you please tell me if there is a way I can recover data on my phone without losing them? I also have Google Authenticator which is connected to many accounts online, If I lose data I will lose everything! Here is what I tried so far:
First thing I did was a soft reset ( power button + volume down) and the mobile turned on but unfortunately it kept looping on the Samsung logo screen. Then, I tried to go to recovery mode (power button + home button + volume up) and from there I tried "reboot system now", "wiping cache partition (which I hope it doesn't remove any data?)" and "Run graphics test: which failed with error no command and then wiping cached data" all of them without success. One thing I noticed in the bottom section of recovery mode there are these errors:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920C
CA_ TYPE: CA_2
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download : Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:5 K:0 S:1

Android Recovery
samsung/nobleltejv/noblelte
7.0/NRD90M/N920CXXS5CRH1
user/release-keys

No Support SINGLE-SKU
Supported API: 3
dm-verity error...
E: failed to mount /system (Invalid argument)

Comments are not for extended discussion; this conversation has been moved to chat.

Yeah, sorry about that. System automatically deletes a chat room when it meets some criteria for deletion. I have undeleted the chat room now. You should be able to access the chat room now. Try it again.

You could try to flash all partition images (except userdata.img) via heimdall command line
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --PARAM param.bin --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img

The above example command is created from partition list. This is how you get pit file

install heimdall, python and samloader

download and decrypt stock ROM for your region code
C:\Android\samloader>samloader -m SM-N920C -r AFR checkupdate
N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1

C:\Android\samloader>samloader -m SM-N920C -r AFR download -v N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1 -O .
downloading SM-N920C_1_20180820163853_vvggswhd8u_fac.zip.enc4
[################################] 38453/38453 - 00:06:20

C:\Android\samloader>samloader -m SM-N920C -r AFR decrypt -v N920CXXS5CRH1/N920COJV4CRB3/N920CXXU5CRH1/N920CXXS5CRH1 -V 4 -i SM-N920C_1_20180820163853_vvggswhd8u_fac.zip.enc4 -o SM-N920C_1_20180820163853_vvggswhd8u_fac.zip
[################################] 615247/615247 - 00:01:21

unpack files from zip
C:\Android\samloader>7z l SM-N920C_1_20180820163853_vvggswhd8u_fac.zip

7-Zip 18.01 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2018-01-28

Scanning the drive for archives:
1 file, 2520047837 bytes (2404 MiB)

Listing archive: SM-N920C_1_20180820163853_vvggswhd8u_fac.zip

--
Path = SM-N920C_1_20180820163853_vvggswhd8u_fac.zip
Type = zip
Physical Size = 2520047837
64-bit = +
Characteristics = Zip64

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2018-08-20 16:39:50 .....      5058737      1491256  BL_N920CXXS5CRH1_CL11762721_QB19211222_REV00_user_low_ship.tar.md5
2018-08-20 16:39:50 .....   4797583545   2248597336  AP_N920CXXS5CRH1_CL11762721_QB19211222_REV00_user_low_ship_meta.tar.md5
2018-08-20 16:44:16 .....     38092989     38093065  CP_N920CXXU5CRH1_CP10334463_CL11762721_QB19211222_REV00_user_low_ship.tar.md5
2018-08-20 16:44:18 .....    273756344    231865000  CSC_OJV_N920COJV4CRB3_CL11762721_QB16863364_REV00_user_low_ship.tar.md5
------------------- ----- ------------ ------------  ------------------------
2018-08-20 16:44:18         5114491615   2520046657  4 files

extract pit from CSC file
CSC_OJV_N920COJV4CRB3_CL11762721_QB16863364_REV00_user_low_ship.tar.md5

inspect NOBLELTE_EUR_OPEN_HIDDEN150M.pit pit file with PIT Magic or PIT Viewer

Comments are not for extended discussion; this conversation has been moved to chat.


text:
Can't restore backup - password unknown
I have a Google 6 Pro. I set up a "pattern" password (which I'll never do again - numbers and words are meant for my memory) and forgot the pattern.
After multiple tries, I decided to do a Factory Reset given I had saved all my contacts/apps/photos to Google.
After the factory reset, I was prompted to "set up phone with backup" - which I went do BUT THEN it asked me for the pattern password in order to set up using the backup which was my whole reason for doing a Factory Reset.
Is there a way to restore the backup (given I know the google mail account it's attached to and the password for that) without knowing the pattern?

most likely you can get your pictures from PC https://photos.google.com and contacts most likely bonded to google account, you probably won't lose it even when set up as fresh device


text:
Stuck on logo during Android-x86 boot
I'm trying to install Android-x86 on USB for my new HP laptop. I have followed the instructions on Android-x86.org. My issue is that after the initial install, it never boots again, it just gets stuck on the Android logo.
I have seen a few posts such as this answer:

when you change the internal frame where the UEFI firmware settings to the EFI framework setting change the boot order you have to make a small partition for grub go back and change it back otherwise it won't boot the second time

but unsure of how to do this.
I have also seen this answer:

In boot menu select Installation - Install Android-x86 to harddisk
In Choose Partition menu select Create/Modify partitions
In Do you want to use GPT question select No
cfdisk program will open
Select New and select Primary as partition type, set size to 100 MB and select Beginning
Select bootable. Now the Flags column should say Boot for the new partition
Select the free space and select New and select Primary as partition type, leave size as default to fill the remaining free space
Select Write and type yes and press Enter
Select Quit

but I'm stuck in the fact when I click on create/modify on this, I get cgdisk not cfdisk, and it's not as easy to use. I don't know why this is happening. Before I realised what to do, I was accessing cfdisk, but now it's only cgdisk.
I have purchased 4 premium USB sticks just in case the issue was due to a bad USB, but it's not the case and I'm just so frustrated.
Any help at all would really be appreciated.

Sometimes, it takes a long time until you boot through the Android logo screen
You can try adding
nomodeset xforcevesa

to the boot options according to this video.
The video is created by me as a part of our free video tutorials service on demand. That means anyone can ask us for instruction in a video and we will create the tutorial for free.
The instructions are as follows:

After starting Android, select the first boot option and don't press enter.
Select E.
Select E again.
Now move the cursor left, by pressing the left key until you reach the word quiet.
Replace quiet with nomodeset xforcevesa.
Press Enter.
Press B to boot this option.
Wait until Android loads, which may take a long time in some cases.

Please use the Auto installation option, if this is the only OS on your laptop.
Auto installation tutorial.
Instructions:

Thanks for getting back to me, i have tried auto installation before, straight to the usb but same thing happens, my laptop is remaining on windows, im just trying to make an android usb, and then can switch to which ever os i want.. in relation to above, how exactly to i add "nomodeset xfrocevesa" and where does it go.. thanks

Please provide a video or screenshots to exactly what you are doing. Its becomes harder to debug an issue remotely if we don't know the details.

ok so im really having issues, i have even tried a different rom, ie bliss os, but still same issues,  i install the image to usb, i have used rufus, as well as various others incase that didnt work, i then boot to uefi, and click to install to a 2nd usb.. i have tried to modify the usb stick 1st with cfdisk but for some reason this takes me to cgdisk which is not the same

I've found something that might help you. I recently installed androidx86-9.0-rc1 as a dual boot (unlike you), and I too faced this same problem that it booted for the first time just fine but gets stuck in subsequent boots.
So I tried uninstalling and reinstalling it to see what's wrong and what I found that when I am on Windows and if I try to switch to already-installed androidx86 [by choosing restart option in Windows/by entering BIOS from Windows and then booting to androidx86], it gets stuck [and gets stuck in subsequent times too, once you did such].
So for this, you must boot to androidx86 directly after you power on your PC when it's initially shut down.
Supposedly you're on Windows, and say you want to switch to androidx86 [newly re-installed, not the one that got stuck], so don't restart Windows; just shut down the PC and power it on to boot to androidx86. Just note that this is my observation only for the dual-boot case,


text:
Disable mouse acceleration on Android
I am using PrimeOS on my laptop. I have noticed that when I move a mouse slowly for about an inch, consider it travels some distance on screen line about 2 inches. But when I move the mouse rapidly for 1 inch as before, the distance traveled by the cursor is much more like about 3.5 inches.
I want to disable this mouse acceleration to get the same displacement of the pointer at both slow and fast speeds.

There's no API for that unfortunately, except on some of the latest SHIELD products that check for a com.nvidia.rawCursorInput manifest property.

Open Settings > General management > Mouse and trackpad
Change Enhance pointer precision from the default value of enabled to disabled.
This will disable mouse acceleration in both Android and Samsung Dex.

The setting is in Android so plus oned it. But I  don't know if its in PrimeOs

I don't have this option, only "Pointer speed", but the effects are less prominent with Faster speed as it tends to require less physical movement and therefore less acceleration.

Install SetEdit app, then on the System Table, find: Pointer Speed, then change its value from 1 to 0.

At least on samsung phones it seems like this might work.

The property in question accepts a wide range of values, at least [-5; 5], not just 0/1. Works exactly how you'd expect.


text:
Blocking toast pop-ups without Xposed
I'm currently running on a OnePlus 7Pro with OOS 10.3.2 (Android-10).
I've been using an Xposed module called "Untoaster Xposed" to selectively block toast popups based upon regex matches of the contained text. This works well, but now I am considering switching to Renovate Ice, which doesn't support Xposed or TaiChi, and I'm wondering if there is any non-Xposed-based method for selectively blocking toast popups in this or a similar manner.
I'm willing to write a custom app to do this, if it is the only alternative.
But is this even possible without Xposed?
Thank you in advance.

I think it would be best if you tell us whether you want to selectively block toasts from an app or do that in wholesale (that is, all toasts to be blocked from an app). If in wholesale, inbuilt appops can do this (for some apps).

Well, ideally, I'd like the same functionality as "Untoaster Xposed". It ignores the name of the app and just blocks by means of a regex match of the text within the toast. However, if that is not possible, blocking all toasts for a given app would be my second choice. I'll check out appops


text:
Battery level on Asus eee pad Transformer with dock
I'm wondering if anybody knows how the battery level is measured on the Transformer when the dock is connected.
I fully charged the other day, and after few hours of use the battery level was still 100%, so my first thought is that first uses the dock battery until this one is empty and the continues with the tablet's battery.
Can anyone confirm/deny my guess about the battery level measurement on this tablet?
Also, does it work the same when you charge the tablet though the dock, that is, starts charging the dock and when is fully charged continues with the tablet?

The Eee Pad Transformer will use the battery of the dock to both power and charge the tablet so long as it is connected. You can see this when docked and on battery because the tablet shows its battery as "charging". This gets the most use out of the tablet because when you undock it, it is most likely to have more charge than the dock.
When docked and on the charger, I am fairly sure that both charge at the same time. However, I haven't checked as my TF is docked most of the time.
Incidentally, if the dock's battery goes flat, it gets its power from the tablet (without trying to recharge its own battery).


text:
Receiving "Message board service started" randomly
Randomly on my Android Galaxy S2, I'm receiving a message nag "Message board service started".
It can happens in an application, in the app drawer or anywhere randomly.
I'm unable to find any sources talking about this message.
Do you have an idea?
Android 2.3.6

Found it ....

Message Board service started
BlueLocate service started

Here is the app causing theses messages : Connectdroid


text:
Does Android put wifi and other data networks to sleep when the display is turned off?
I was wondering if stock Android puts Wifi and other data networks to sleep when the display of the device is turned off. If not, what app can help me do the same ?

It depends, some Android devices have an advanced setting WiFi Sleep Policy under
Settings -> Wireless -> Wi-Fi Settings -> [Menu Button] Advanced -> Wi-Fi Sleep Policy
But I am not sure if this is a vanilla Android feature or an manufacturer modification. At least the Galaxy S series has this setting.
Data networks are usually fully active. But Apps like Tasker allow you to define certain profiles to improve battery life. For example: Only allow 2G when the display is off, because 2G requires less battery then 3G (UMTS).

That too on menu button... I wonder if there are any other settings with more options on menu buttons.

I don't think it turns the WiFi or Data networks off. You can try by downloading an app from market and while it is downloading, turn off the  screen. You can see that even after the screen is off, the download completes after some time. I am not sure exactly which app does this but you can try searching the market for such an app.

Whoever is down voting the answer, i would request to please provide a comment as to why the answer was downvoted.

Pretty cumbersome answer as there is setting built in Android for exactly what OP describes.

The WiFi sleep policy describes when to switch from WiFi to Mobile Data for my Samsung Galaxy S. Kiran is asking about whether WiFi or Mobile Data (connection to a network) gets lost or not. This is little bit different from WiFi Sleep Policy. Further, there is no such policy for Mobile Data.

I'd down vote this answer due to following statements presented in answer: 1) "you can try searching the market for such an app" --not helpful, if you know some of them, name it here 2) "you can design one yourself. This wouldn't be hard" --I really don't think so.

Removed the designing part. That would correct it somewhat.


text:
Why do I always lose this file?
I run a dual-booted HD2 from SDCard/HaRET with MIUI Android & stock WM6.5.
I keep a copy of this file in \Storage Card\My Documents for listening in CorePlayer and survive possible hard resets.
However, everytime, and I really mean every time I boot MIUI this file disappears from the SD card. I'm unable to locate it from Android and when I reboot into Windows I see no traces of it.
Why the hell (can I say hell?) does Android delete the file from SD on every single boot? Does it hate M3U files?

Most important, I never noticed any other file to be missing. I have lots, and I couldn't check one by one. But no other important file disappeared

Android scans your sd card. When it finds an MP3 playlist (m3u file) it looks for media files in the same path, if it does not find any, it deletes the playlist because it thinks it is empty.
To stop this from happening create a file in the folder with the m3u file called .nomedia. This will tell the media scanner to ignore the content in the folder.


text:
difference between ninesky and ninesky cn
Ninesky is a browser for android. What is the difference between Ninesky and Ninesky CN?

I would guess the latter is a special version for China.  It doesn't mention the links to US news sites like the main version, for example.

The screenshots of the CN version are all in Chinese, also the language code for Chinese Simplified is "CN".


text:
How to know if an app is ICS compatible?
I am thinking to upgrade my phone with Android 2.3.7 (Gingerbread) to 4.0.3 (Icre Cream Sandwich), but I would like to know first, if the applications I normally use are available and working on ICS.
Does exist a way to know it?

Android is written with backwards compatibility in mind. Apps written for older OSes should run fine on newer OSes (with a few exceptions here and there).

You can check the changelog and comments on the Market for information, quite many apps have recently been updated to be ICS compatible and there's usually a mention of this in the changelog. Also, if the app isn't compatible, there's usually a comment about this.
In my experience, almost all of the apps I use are compatible with ICS or have been updated. Some may not have all the compatibility features such as the new menu style, but ICS is backwards compatible with the old style too.
EDIT: Developers can also specify the parameter android:MaxSdkVersion in their AndroidManifest.xml which restricts the application from running (and AFAIK also from showing up in the market) on newer platforms. I haven't published any apps in the Market so I'm not sure if there are separate settings in there to restrict the apps from installing on higher version platforms.
You can try to check the AndroidManifest.xml of your apps by using android-apktool, but this requires you to know how to get the .apk files to your pc.

You could set up the android emulator with ICS, install the market on it, and try it for yourself.  Unfortunately all the instructions I've seen for installing the market on the emulator are for older versions of android, so I'm not sure if they'd work on ICS.  Here are a couple:
http://blog.varunkumar.me/2010/11/how-to-install-android-market-in-google.html
https://stackoverflow.com/a/4673964/399105
Edit:
This link seems to indicate it might be possible, using an android ICS VM instead of the official emulator:
http://vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838&limit=6&limitstart=84#8951

there is no such method to know whether all apps would work in ICS, I have seen some issues with hardware acceleration problem in old apps when running in ICS, it depends on application build, if any authentic applications like browsers mozilla chrome would update their application depending on OS which it has. no need to worry about applications which gets updated on time to time, still people are trying to fix all so should work on ICS,. let us C

Can you give example of some apps that you encountered HWA problem with?