text:
Nexus 5 stuck on OS loading animation, pressing Volume-/Power only shows fastboot for a second, adb shows nothing
This is the normal LineageOS loading screen, which I had until yesterday:

Problem: Since yesterday, only one circle is going from right to left, forever. In other words, it never reaches the 3 circles (even after 8 hours overnight), and my Nexus 5 has become useless.
After reading Nexus 5 stuck on "flying color dots lollipop" screen after Hard Factory Reset I tried pressing Power/Volume- at the same time for 30 seconds. Result: It makes the fastboot screen appear for less than a second (during that split second I can move the cursor with Volume+/-), then the screen turns black, then fastboot for a split second again, then this boot-loop:

white Google+unlocked lock on black background, for a few second
black screen
Vibration
Back to step 1

Pressing the same Volume-/Power during the earlier "white Google+unlocked lock on black background" screen results also results in the same boot-loop.
During all of these phases (animation, fastboot, boot-loop), running adb logcat from my connected computer only shows waiting for device.
I am performing all of this with the charger plugged in. I even changed the battery to make sure it was not a power problem. To check I managed to quickly push "Power off" in fastboot and it shows the battery level: 100%.
The computer/port/cable I am using are the ones that I have been using everyday for years to transfer files and debug apps over USB. I also tried a wall charger and new cable too to make sure, same result.
The Nexus 5 is unencrypted.
After plugging the phone into a Windows computer (instead of my usual Linux), fastboot miraculously stayed on, and I was able to get the following information:
Partitions
~ # cat /proc/partitions
major minor  #blocks  name

 179        0   30535680 mmcblk0
 179        1      65536 mmcblk0p1
 179        2       1024 mmcblk0p2
 179        3        512 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7       2048 mmcblk0p7
 179        8       1024 mmcblk0p8
 179        9        512 mmcblk0p9
 179       10        512 mmcblk0p10
 179       11        512 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13       3072 mmcblk0p13
 179       14        512 mmcblk0p14
 179       15      16384 mmcblk0p15
 179       16      16384 mmcblk0p16
 179       17       3072 mmcblk0p17
 179       18      22528 mmcblk0p18
 179       19      22528 mmcblk0p19
 179       20      22528 mmcblk0p20
 179       21       3072 mmcblk0p21
 179       22        512 mmcblk0p22
 179       23        512 mmcblk0p23
 179       24        512 mmcblk0p24
 179       25    1048576 mmcblk0p25
 179       26      30720 mmcblk0p26
 179       27     716800 mmcblk0p27
 179       28   28551146 mmcblk0p28
 179       29          5 mmcblk0p29
 179       32       4096 mmcblk0rpmb

Mount
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p25 on /system type ext4 (ro,seclabel,relatime,data=ordered)

Block names
~ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 abootb -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 crypto -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 imgdata -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 laf -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 rpmb -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sbl1b -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 system -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Jan  1 01:00 tzb -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Jan  1 01:00 userdata -> /dev/block/mmcblk0p28

Filesystem
~ # blkid /dev/block/mmcblk0p28
/dev/block/mmcblk0p28: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

Wiping cache
~ # twrp wipe cache
Formatting cache using make_ext4fs...
Failed to mount '/cache' (Invalid argument)
Done processing script file

~ # mke2fs -t ext4 /dev/block/mmcblk0p27
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
44832 inodes, 179200 blocks
8960 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

~ # twrp reboot
command is: 'reboot' and there is no value
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
E:a
Done processing script file

Doing that cache wipe did not solve the problem, unfortunately: The OS animation has been running for 3 hours already.
Question: How to at least get the content of my Nexus 5's /sdcard saved to a computer? Or maybe even fix the Nexus if possible?

Let us continue this discussion in chat.

I guess the problem is related to cache partition. you can try to fix it with
fastboot format:ext4 cache

or from twrp recovery with
adb shell twrp wipe cache

also formatting the cache partition will help
adb shell mke2fs -t ext4 /dev/block/mmcblk0p27

You can manually backup your data (sdcard) partition. if data is encrypted, mount it with
twrp decrypt <password> where you have to use your screen lock pin/password. if you use a screen lock pattern you must translate it to password (see https://blog.alxu.ca/unlocking-large-pattern-encryption-in-twrp.html)
GNU tar for android and external MicroSD Card or USB-OTG flash drive is required for this. The tar binary is included in open_gapps.zip, download and unpack it, copy the binary to MicroSD Card and rename it to "tar"
mkdir /data
mount -t ext4 -o ro,noexec,noload,noatime /dev/block/mmcblk0p28 /data
cp /external_sd/tar /tmp
chmod a+x /tmp/tar
/tmp/tar --selinux --xattrs --numeric-owner -vcpP /data | gzip | split -a 1 -b 1024m - /external_sd/data.ext4.tar.gz.

if partition is not mountable, you can copy the partition with dd
dd if=/dev/block/mmcblk0p28 of=/external_sd/data.img            bs=1024 count=28551146
dd if=/dev/block/dm-0       of=/external_sd/data_decrypted.img  bs=1024 count=28551146

edit: (thx @ Nicolas Raoul) if your phone neither has external MicroSD Card nor USB-OTG support, you can stream the partition over adb.
adb pull /dev/block/mmcblk0p28  C:\adb\data.img
adb pull /dev/block/dm-0        C:\adb\data_decrypted.img

Open the file with OSFMount or mount it from sudo (see above command). The sdcard folder is located /data/media/0. If you want to restore the apps later on encrypted data partition, it is recommended to create a tar archive (in addition to the above flags) with --exclude data/media this will reduce the backup size. the restoring command line is
cat /external_sd/data.ext4.tar.gz.* | gzip -d | /tmp/tar --selinux --xattrs -vxpPC /

For mount -t ext4 -w /dev/block/mmcblk0p28 /data I get mount: mounting /dev/block/mmcblk0p28 on /data failed: Invalid argument

The Nexus 5 is not encrypted. I guess I can run adb.exe pull /dev/block/mmcblk0p28 mmcblk0p28.img and then mount the image on Linux as ext4?


text:
Apps missing after sd card unmount
The core issue is in the title: the apps that were installed in the SD card seem to be not installed at all after I unmounted the SD card.
As additional information, these are the steps preceding the moment I have noticed this problem:

installed some apps (so, it's not an app-specific problem)
moved many of them to the SD card using App2SD - apps working properly
unmounted the SD card and detached from the phone (which is turned on)
no data were written on the sd card (only read operations)
put SD back in the phone (the same SD card)

At this point, I was, and currently am, not able to launch the applications previously moved in the SD card. The links are available on my home screen, but after tapping them I get an error message saying "error launching application".
They are not available in the app menu, neither are marked as "installed" in the play store.
Fortunately, the applications' data are still there, and installing some of the apps again they appeared the same as the last time I used them.
So, the question is twofold:

Is there a way to recover the apps, or do I have to manually reinstall them?
Is this a potential bug of App2SD?

Have you tried restarting the phone?

I did it several time (the phone has a strange behavior     since I reported the problem)

This sounds like a case of a vital hidden folder that you're missing - when apps are moved to the SD-Card, a hidden folder called .android_secure is created which is where the apps are stored in!
This is a common mistake to make, when replacing a SD-Card for a bigger one, so the moral is to ensure, when transferring to a bigger SD-Card, do not forget the hidden directories including .android_secure. Upon restart after inserting the bigger SD-Card, Android will re-scan the card and proceed to look in that specific hidden folder, for any apps that are moved to external storage and loads/caches the shortcuts for those respective apps.

That folder is called .android_secure :) Further your answer implies the OP switched cards -- the question doesn't indicate that: put SD back in the phone rather implies it was the same card. Apart from that: Good point!

@Izzy Gosh thanks for the heads up... will edit it accordingly! ;)

NP -- but you're still assuming the OP copied contents to a new card, which is not what the Q says (well, but it also doesn't deny it, so I'll give you a +1 nevertheless :)

Maybe I am in denial too... methinks the OP should clarify if that was the case? :)

@Izzy is right: I didn't change the SD card: it is the same. No data were written or changed while it was off the phone.

@AlessandroCuttin - Thanks for the clarification :) Ok... something is not quite right.. now forgive my ignorance, but when a card is unmounted, it does not mean to actually pull it out - am thinking aloud - ejected safely, unless you uncovered a bug with Apps2SD in that it failed to recognize the unmount and did not eject it.... just a thought...

...which should mean the same problem would occur when mounting the card via USB to a computer, wouldn't it? What would happen then? Is it unmounted locally or, as I read lately, simply gets its permissions reset to 000? Would /sdcard/.android_secure become unavailable in both cases (is it even handed to the computer this way?) But I guess that goes to far here :)

@Izzy, With windows, there's a very good reason for safe eject with regards to cards, the buffers holding the filesystem on card has to be flushed in a safe manner prior to ejecting, maybe the OP pulled it out with-out ejecting safely and that might have scrambled the dot directories (hidden directories)????

As a rule I generally un-mount the sdcard, power off the phone and can then remove it, I would not be 100% confident in pulling it out (despite being unmounted) when the phone is still on....

True about that -- but why should it have damaged only the hidden directories then (even more as the OP was unlikely to touch anythin in there)? Also, quoting: no data were written on the sd card (only read operations) So it shouldn't have mattered (but you're right: Who knows?)

I had the same problem, but we might have different phones. For me, the reason why I never see my apps moved by app2ds is because my sd card is partitioned so that app2sd would be able to see only that part of the card, and my computer cannot see the partitioned part. Whenever I unmount my sd card to switch it out with one I have music on, I just have to restart the whole phone afterwards is all.

source: Stack Exchange

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

sort: votes


text:
Using Google voice number without data
So I know similar questions have been asked, but I feel my situation is a bit unique to everything I've read.  So I transferred my old number that everyone knows to Google voice, then I got a new phone with a new number that only has calling and texting.  I took the SIM card out of that phone and put it into my android phone, effectively giving me an android that has calling and texting, but no data plan.  I set up google voice to recognize my new number and call forward and everything seems to work while I'm on wifi, but I don't seem to receive text messages when I am not on wifi.
Is there a way to tell google voice to send all text messages it receives on my gv number to my carriers text plan with my new number (even if I don't have access to data)?  Also can replying to these messages without being near wifi show my gv number instead of my new phones number?  I can call Google voice and have it call the number I want to have my old number always show up, but with texting I haven't seemed to find a way yet.  Anyone in a similar situation have a good solution?

I figured it out.  If you navigate to this page, and tick the receive text messages on this phone box all texts to Google voice will be forwarded to your phone via SMS.  This generates a new number for each of your contacts that will travel between Google voice before delivery, making it so you will always show as your Google voice number to friends, even if you are outside of wifi.  So just need to save the new number for each contact and be sure to text that instead of their actual number and it works perfect.  More info here.

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


text:
Clockwork: error: cannot load 'recovery-clockwork': No error
I am trying to flash a recovery-image file into my Nexus 7 but the flashing fails
know that I am working on windows and my image file is located in the same folder as adb and fastboot files are
here are the steps I am following:

start the tablet android system, and the device works fine
I restart the tablet into the bootloader using: adb reboot bootloader
browse to the Recovery Mode and then check if the adb sees the tablet: fastboot devices
adb is working fine and can detect the device and read its serial number
then when I flash: fastboot flash recovery recovery-clockwork.img: I get this error:
error: cannot load 'recovery-clockwork': No error

what am I doing wrong ?

Just to make sure: the file you are going to flash is named recovery-clockwork.img, and located within the same directory you are working from? Have you tried with a full path?

@Izzy: Yes, it is name is recovery-clockwork.img, I removed the version numbers and put it within the same directory I am working from .. but no, did not try the full path yet ..

@Izzy: yes it works.. the mistake was, after adding the adb path to my environment-settings, I keep opening the cmd and then run the fastboot flash command ..  so it was c:\User\User1 .. now, I change the working directory to the platform-tools folder ..c:\...\platform-tools .. and the flash command worked

OK, I did! Glad it was that easy :) In fact, I didn't expect that, as the error should have been something like "no such file" then...

@Izzy: me too, was excepting something more complicated, but, luckily, it was not  .. btw, it gives me the error "no such file" when I wrongly state the file name ..

Most common errors (and solutions to them) are:

different file name: make sure the file is really named recovery-clockwork.img, in your example, or adjust your command according to the file name
wrong path, e.g. your file resides in C:\Downloads, but you're executing fastboot flash recovery recovery-clockwork.img from C:\: Either first change to the directory the .img file is located in, move the .img to where you want to execute your command, or try specifying the file with its full path (e.g. C:\Downloads\recovery-clockwork.img)
sometimes adb/fastboot behaves strangely when executed from "somewhere else". In those cases it helps to first changing to the directory where the resp. executable is located, and run your command from there.


text:
Particular WiFi does not connect after trying to root Samsung Galaxy S10e with Magisk
I followed this tutorial: https://topjohnwu.github.io/Magisk/samsung
All went well until step 14 (so, right after flashing the ROM and rebooting).
At step 14, Magisk tried updating, but could not. I realized the problem was that Android can not connect to my company's WiFi. I mean, I can see the WiFi networks, but I can not log into my company's WiFi.
Notes:

The WiFi hotspot itself is OK, my desktop computer is using it right now to post this question.
Android was able to connect to that WiFi and use its Internet, up to step 5 at least.
Strangely, I can connect to another WiFi network (my friend's mobile tethering)
This thread suggests it might be caused by modules, and suggest removing the modules then rebooting, but I installed no modules.

How to fix the problem?
adb logcat
05-21 22:20:33.559  5207  5207 D WifiHAL : Start get packet fate command
05-21 22:20:33.559  5207  5207 D WifiHAL : createRequest Get Tx packet fate request
05-21 22:20:33.559  5207  5207 D WifiHAL : error code -95 mapped to -3
05-21 22:20:33.559  5207  5207 E WifiHAL : Failed to register get pkt fate response; result = -3
05-21 22:20:33.559  5608  5873 E WifiVendorHal: getTxPktFates(l.2241) failed {.code = ERROR_NOT_SUPPORTED, .description = }
05-21 22:20:33.560  5207  5207 D WifiHAL : Start get packet fate command
05-21 22:20:33.560  5207  5207 D WifiHAL : createRequest Get Rx packet fate request
05-21 22:20:33.560  5207  5207 D WifiHAL : error code -95 mapped to -3
05-21 22:20:33.560  5207  5207 E WifiHAL : Failed to register get pkt fate response; result = -3
05-21 22:20:33.560  5608  5873 E WifiVendorHal: getRxPktFates(l.2283) failed {.code = ERROR_NOT_SUPPORTED, .description = }

I also get:
WifiVendorHal: getRingBufferStatus(l.2059) failed {.code = ERROR_NOT_SUPPORTED,

Go to the WiFi networks activity.
Long-press the problematic WiFi network
Choose "Forget network"
Turn WiFi off and on, just to make sure
Tap the WiFi
You will be asked for the WiFi password again, enter it
Now you should be able to connect, at least that is what worked for me

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


text:
Reassign Bixby button on rooted S10
I never use Bixby on my rooted Galaxy S10e, so I would like to repurpose the Bixby button, for instance as camera shutter or to open an app of my choice.
Question: How to do that?
Note: I tried following https://www.theverge.com/2019/3/1/18246255/how-to-re-program-bixby-button-samsung-galaxy-s8-s9-s10-8-note-9 but at the first step, which is to open Bixby, I am told:

Bixby Voice isn't available in your country.

From Settings > Advanced features > Bixby key:

The Bixby key setting isn't available yet. Sign in to Bixby to start using the Bixby key.

Does useing a VPN work?

@helper: I just tried with a USA VPN server, it also says "Bixby Voice isn't available in your country".

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


text:
Error in unlocking bootloader in xperia ray with testpoint method
I was following guide to unlock my bootloader while preserving DRM data.
http://androidflip.com/unlock-xperia-phones-bootloader-without-losing-drm-data-track-id-working/
Everything went fine except the last one. Here is the log
I did all the steps in guide and receiving error for my xperia ray :crying:
Here is the log
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.

DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE

PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"

qcReceivePacket: can't get packet start.
Elapsed:24 secs.

Couldn't find a suitable answer in google. Any help?
Infos:
Boot loader unlock allowed : Yes
Build date 12W23
Can go to flash mode.

Currently xperia phones with newer EROM, bootloaders can't be unlocked via the above mentioned test point method.
Got the information from http://forum.xda-developers.com/showpost.php?p=30675295&postcount=108


text:
How to change the frequency of Google Play update checks?
Every day I get a notification on my Inc2 that there are app updates available in the market.  Is there a way to change the frequency of these update checks?  I see no reason to be prompted to update my apps on a daily basis and this is a little annoying.  I would like to be able to only have it check for updates weekly.

You can turn off automatic update checking by pressing menu and than settings in the play store. You can then manually go to my apps to update them. This will not greatly increase the work you have to do, because even if there is a notification once a week it would still require you to confirm the updates. There is no option however to change the frequency of the automatic updates.

If you go into Settings and check "Auto-update apps" it will download and install the updates without prompting you. If you're worried about data usage, also check "Update over Wi-FI only". I've had my phone set this way for a while now, as I too got tired of constantly having updates to accept.
As Dylan Yaga pointed out, if an apps update changes its permissions, you will still be prompted to update it manually, although this doesn't occur very often.

Side Note: Apps that change permissions must still be manually reviewed before updating using this method.

I like being in control of when my apps update.  Daily is far to often to review a list of updates.  I assume that if I auto-update I will still be notified of all of the updates that have occurred.  I have also found that quite a few of my apps update permissions frequently.

I finally gave in and went this route.  I still don't like apps autoupdating without telling me, but at least my monthly update all doesn't freeze up the device for an hour anymore.


text:
Boot loop after ROM write  in recovery
I have an HTC Sensation with ICS Android on it. How can I revert back to Gingerbread?
I have root and s-off. I tried to flash my Gingerbread ROM (??) in the recovery but am now stuck in a boot loop.

What do you mean "no effect"? What happened when you flashed the rom?

Just out of curiosity; why do you want to revert to Gingerbread? Also, can you try another ROM? Try reflashing /system if that is a part of the instructions. Also try a stock factory reset.

Did you wipe before flashing?

-I tried about 12 or 15 ICS roms but gingenbread is better to me.
-Yes, I've done a full wipe before flashing

Do this:

Boot into Recovery
Wipe cache
Wipe Dalvik cache
Wipe them again
Install your ROM

The first successful boot afterwards is going to take a while, as it is rebuilding Dalvik cache.
If you are not boot looping here, just let it go for a long while. If it boots a while and reboots, wait some more.


text:
ICS ROM with no Slovenian language
I bought HTC desire S in Slovenia and it has installed karnel ROM:
    RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068

This ROM do not offer Slovenian language. So i need help what to do to have Slovenian android version. It is not metter even if it is 2.3 version. Only that it has official android with Slovenian language.
Any idea how to use my device with Slovenian language?

I would recommend installing a custom ROM with support for the language you need. I think CyanogenMod might be a good try since it's usually very stable and close to "stock" ROMs of Android. You can find the stable CyanogenMod version for HTC Desire S here.
Rooting and flashing ROMs on your device might require some work on your device if it's not rooted, or if it's rooted it might be quite simple. Since you don't offer any information on whether you are rooted or not, here's some resources for you to look up:

Installing a custom ROM on the HTC Desire S [HD] Step-by-step tutorial
How to S-Off and Root the HTC Desire S, Sensation, Wildfire, Evo, Flyer HD - A step-by-step tutorial

All of this is of course assuming that your current Android version does not support changing the language. You might want to look in your menus just to make sure. If it's not there, you need to get another ROM.
If you have any questions, please comment on this answer and I'll try to expand on it accordingly.

Phone is S-On and not-routed. i have prevoius build number 2.10.401.8 CL156318 RELEASE KEYS if this gives any information. Otherwise rooting seems to complicated routing for me while I am not such phone expert and i do not want something goes wrong. This ROM do not offer Slovenian language. Is there any possibility to find official previous ROM??? and how can i install official ROM?
Thank you for your help in advance

You can always look at HTC's website or contact them to get some kind of update software.

Hi back,
I just found ROM that was previously installed on my HTC desires s and there is new question: How can i install now RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed so this ROM which has slovenian language will overwrite ROM that i have now? I hoe there is some easy way- and it is not need to root phone?

You probably need to root your phone and install a custom bootloader (CWM Recovery for example)

I found a solution for all languages issue: on google play is  app: MoreLocale2 which offer many languages. This app change language of your UI on Android phone.


text:
Neo V with 4.0 ICS update -- battery problem
My Sony Xperia Neo V battery performance has gone down very badly after upgrading to ICS.
It mainly happens when I have my mobile data/internet turned on. How can I improve the battery performance?

Well you can try managing battery life with JuiceDefender, which does a great job at disconnecting data connections when not needed and turning it back on when needed. I can personally attest to this fact although I use gingerbread on my Xperia Neo V. Give it a shot and see


text:
Installing Android using only fastboot on HTC Vision
I lost my system somehow. My phone turned off and reboots during starting up.
I'm only able to go to hboot (fastboot/recovery etc.) on my phone, and I'm unable to run Android system.
I have tried many possible solutions with help of #g2root on freenode:

First I downloaded the stock ROM and saved it to SD card (PC10IMG.zip).

It begins to load, and I see [1]-[12] positions.
When I agree to install, there's "- Updating" text near to "[1] Bootloader". Nothing else happens for more than 30 minutes.

Then we tried to get rom.zip from official HTC Unlocker for Desire Z, saving it to the SD card.

This time the only list item there was "[1] Bootloader" and also "Updating" text and nothing happens.

The last thing I tried was to run EXE file from HTC that is supposed to update my HBOOT.

It also doesn't work.

Here are my HBOOT params:

VISION PVT SHIP S-ON
  ?HBOOT-0.85.0013
  MICROP-0425
  RADIO-26.10.04.03_M
  eMMC-boot
  Apr 11 2011,23:36:27

Is there anything else I can try to recover my phone?

Have you tried running fastboot flash zip rom.zip from a connected pc?

Yes, and it also hangs.


text:
Force tablet UI on a non-tablet device?
I own a large screen phone and am wondering if I could make it recognize itself as a tablet, as in:

The navbar should stay at the bottom instead of rotating to the sides
Notification shade doesn't occupy the whole screen width in portrait / doesn't stay in the middle in landscape
Apps that support tablet layout will use it

AFAIK, a sufficiently small DPI (LCD density) value will trigger the change, but naturally I want the UI elements to stay at a visible, comfortable size. There's supposed to be a trigger (an if-else condition?) that calculates whether tablet UI should be activated based on device metrics and the above DPI value, however I don't know where the actual trigger is or how should I change it to make it always say "tablet". I've seen similar things done to Android versions below 5.0 via Xposed modules, but those are quite outdated by now.
The answer could be using Xposed (not preferred but still alright, since I still need to stay on Nougat for a while), modifying SystemUI, or even modifying the Android source code and building (I have the know-how for that) - one just have to tell me where and how.
Any ideas?

I've been told before that apps and web browsers detect the size of the screen in inches. If you can fool that then it should work. I'm posting this as a comment because I have no idea if this is true or how to even research how to do this. I'm very interested in this question so I'm leaving this for someone else to look into.

After some digging I am able to sort out a relatively easy solution for the first and most important requirement, that is, keeping the navbar at the bottom. Requires root (of course - to pull and push files) and basic skill of using apktool.
For pre-compiled ROMs:

Install apktool.
Install your framework-res.apk by executing apktool if /path/to/framework-res.apk.
Decompile your services.jar by executing apktool d /path/to/services.jar.
Go to the decompiled services.jar.out folder and open smali/com/android/server/policy/PhoneWindowManager.smali.
Search for 0x258 and replace the only occurrence of it with 0x0.
Rebuild services.jar (preserve its signature) by executing apktool b -c services.jar.out.
Decompile your SystemUI.apk by executing apktool d /path/to/SystemUI.apk.
Go to the decompiled SystemUI folder, then go to res/layout/.
Remove navigation_layout_rot90.xml.
Make a copy of navigation_layout.xml and rename it to navigation_layout_rot90.xml.
Rebuild SystemUI (preserve its signature) by executing apktool b -c SystemUI.
Push the finished services.jar and SystemUI.apk back to where they were using a method of your choice, set correct permissions, then reboot.

For ROM makers:

Open *build-folder*/frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java.
Search for shortSizeDp < 600 and replace the only occurrence of it with shortSizeDp < 0.
Find the SystemUI layout files in *build-folder*/frameworks/base/packages/SystemUI/res/layout/ and replace, similar to the method for pre-compiled ROMs.
Build the ROM.

Note that the default button layout doesn't look good under landscape mode, but one can always use the built-in navbar tuner in Android 7.0+ to tweak it to his desire.

As of Android 10, this has been simplified to a single boolean config config_navBarCanMove, which can either be set directly in the framework or separately in an overlay (recommended).

You could try changing the DPI via this method:
http://phandroid.com/2016/05/24/how-to-change-dpi-settings-on-android-n-nexus-no-root/

Open the Settings app
Scroll down to About phone
Tap Build number 7 times (you’ll see a prompt counting down taps to
  unlock)
Press back to go back into main Settings menu
Select Developer options which now appears at the bottom of Settings
Scroll down and select Smallest width (under the Drawing category)
Your current DPI setting will be displayed — write that down
  somewhere
Change the value to whatever you like (the bigger the number, the
  smaller the UI)

and then increasing the font/display size to compensate for the changed UI size. https://www.thurrott.com/mobile/android/77447/android-7-0-nougat-tip-customize-display-font-sizes
Settings > Display > Display size
Settings > Display > Font size

As I said, I want all the UI elements to stay at the size they should - that includes navbar buttons, various icons, etc. Increasing font size only introduces cutoff when the element can't fit the font.

Doesn't adjusting the 'display size' affect UI elements?

Didn't notice that, so I just tried it out - unfortunately any tweaks to the Display Size cancels out the Smallest Width filled in Developer Options (these two actually seems to be tied together). Also, same as setting the DPI alone, only a sufficiently small Smallest Width triggers Tablet UI.

You can download the Apex Launcher and in the settings set "Use tablet UI mode" to true. It is possible that this only applies to the homescreen and the like, but I don't know any app to test it, but you could give it a go.

That at best affects home screen (not even the navbar, which frankly is the most important requirement). I use it on a bunch of my old devices (Jelly Bean-era) since they have Tablet UI to match, but yeah this does not bring Tablet UI with it,

Ok my bad, sorry!


text:
Disable magnetic screen on/off *without* Xposed?
Long story short, looking for a way to either disable the behaviour of screen turning on/off in reaction to magnets, or disable the Hall sensor (the sensor responsible for the reaction) altogether. The flip cover I have in hand has a weak magnet and thus doesn't turn on/off the screen reliably, hence I want to simply disable the feature and take things into my own hands.
There are a bunch of Xposed modules that do just the job (example), but Android 7+ probably never will get Xposed from what it looks like right now, so a solution without using Xposed is required.
The device in question is a Samsung Galaxy Tab S2 (Qualcomm, Wi-Fi) with root access.
EDIT 1: after some poking around, it seems that /dev/input/event6 corresponds to the Hall sensor on this device - every time I open/close the magnetic lid, it shows an event there. Unfortunately, I still haven't found a way to disable a particular input device.
EDIT 2: I have tried a way to prevent the Hall sensor from reporting back its status, thus effectively disabling the sensor, and it works well. The problem is it requires me to modify the ROM's source code, and although I can handle that as a ROM compiler, I'm sure there are much more people who can't. So still, waiting for a more feasible solution.

I suppose it's possible by writing something to somewhere under /sys. Well, root required, of course.

Thinking of the same, and one can indeed do it that way on a Nexus 7 (2013), but different devices have different /sys structures, and that's the complication...

What's wrong with opening Settings and turning the thing off there?

@MatthiasUrlichs Most devices don't have such a setting. It's not a part of AOSP.

You can delete /dev/input/event6 directly. Then everything with the Hall sensor will stop working.
To make this happen automatically, you can write a simple script and let it auto-run at boot.
#!/system/bin/sh
exec rm -f /dev/input/event6

To restore without rebooting, examine it with ls -l before deleting (or you have to reboot)
Assume ls -l gave this result:
crw-rw---- root input 13, 68 1970-01-01 00:00 /dev/input/event6

Take note of the two numbers after owner/group, run this to recover
mknod /dev/input/event6 c 13 68

Your solution worked perfectly on my Galaxy A9 2018. I am wondering how to permanently disable this sensor without having something run at boot. Do you have any suggestions?

@Falcon Sorry, that's not easily possible (you have to modify the kernel or whatever)


text:
Is there method to send by not using SMS?
I tried to send a message. After that, it displays the following toast:

SMS is unable.

I can't use SMS. Is there a method to send messages by not using SMS?

Google Messenger is an SMS/MMS application. If you are not able to send SMS/MMS for some reason, you need to use a different messaging system and a different application. For example, you can use email, or a proprietary service like WhatsApp. If you need your message to arrive as an SMS, you can use a email-to-SMS gateway, though you need to know the carrier used by the recipient.

You can send messages without using SMS by using a messaging platform. These include
Google Allo,
Hangouts,
Skype,
Facebook Messenger,
Discord,
Kik,
and many more.
If you need your message to arrive as an SMS, you can use
Google Allo.
However, to solve your problem, you might want to try a factory reset.


text:
Google Pinyin Input (IME) keeps asking for Google account permission
Google Pinyin Input is an input method (IME) for Chinese.
It keeps asking me for Google account permission.
I deny it all the time, but it always comes back and asks again when I reboot (which is quite often). The IME works perfectly without that permission.
Question: How to deny the permission once for all?

I have a Nexus 5 with Android 7.1.2 / LineageOS 14.1-20170718.
It always pops up one request for each of the Google accounts I have configured in the Gmail app. I never use pinyin in Gmail.

I had this problem. I'd half installed Pinyin so continual prompting for a login account.
Go to Google play store and search for Google Pinyin Input. When that appeared there was an option to uninstall it (because it had already been installed).

So, what is the procedure to solve the problem? Uninstall and then install again? (I still want to use it) Thanks!

Uninstalling helped. I don't know how it had been installed to my device (I only installed Turkish lately), but I don't need it so removing was the best option. @NicolasRaoul I guess the app requires that access for something (probably to propose personalized word suggestions - I dunno) - so likely there's no way to just disable the permissions request forever.

I don't see why you would need it installed unless you can read Chinese.

Thanks!  This happened to me too.  It is very confusing to continually get these permission requests.  I did not install it and it has been a problem since getting the phone.


text:
LINE Letter Sealing - Unable to display message as it couldn't be decrypted
LINE is a chat application.
I recently reinstalled my OS, and restored my LINE chat history using this procedure.
Problem: Some of my chats appear like this:

It says:

Letter Sealing
  Unable to display message as it couldn't be decrypted. Please ask your friend to resend the message.

As you can see, my friend re-sending me the message does not solve the problem.
On the messages from July 6 to the day I reinstalled have this problem.
So I disabled Letter Sealing, and now I can read new messages sent to me (but I can still not read the existing problematic messages).
Questions:

How to make the problematic messages readable again? I still have the Titanium Backup from the former OS, if necessary.
Is there a way to re-enable Letter Sealing while making sure that encrypted messages will stay readable even after reinstalling my OS in the future?

Had the same problem. The second method on this page worked for me.
Steps:

Do a previous backup
copy /data/data/jp.naver.line.android/databases/naver_line to your PC and rename it to naver_line_old
Reinstall and do a fresh setup of LINE
copy the new naver_line to your PC and rename it to naver_line_new
In your PC, open and copy the chat_history table from naver_line_old(I used SQLiteStudio) and paste it on naver_line_new, having previously deleted chat_history from it
copy naver_line_new to /data/data/jp.naver.line.android/databases/naver_line(rename it as naver_line)
Restart your phone

Letter sealing should work OK now; unfortunately, I don't know how to make the problematic messages readable again.
I hope to have solved your problem.


text:
How can I free up internal memory space taken up by unmovable (to SD) and uninstallable apps?
I have a Samsung Galaxy Luna phone, running Android 6.0.1.  It only has 8 GB of total internal storage space, with about 3 of those GB taken by the Android OS itself, and about 2 more taken up with stock apps I don't use/want.  That leaves 3 GB for me to play around with, and as you can imagine, that doesn't allow many app installs.  Most of the apps I have installed have been moved to an external MicroSD card, but there are still those apps whose developers have forbidden the option to move to SD.  And on top of that, every time an app updates through Google Play, it moves it back to the internal storage, forcing me to uninstall some apps on the internal, update one app at a time, move it back to SD, then reinstall the apps I had to delete in order to perform the time-consuming process.
My ultimate goal is to free up space on my internal memory, all of which is taken by apps (anything else that I am able to put on the SD, such as files, is on the SD).  Things I have tried to accomplish this:

Rooting my phone:  Rooting my phone would allow me to uninstall the stock apps I don't use as well as use an app like Link2SD to move
the unmovable apps to SD; this would perhaps be the simplest
solution.  However, the Samsung Galaxy Luna is an uncommon phone and
it appears there is no way to root the phone (yet).

Adopting the MicroSD card as internal storage:  Another simple solution.  This would not allow me to uninstall stock apps, but hopefully enough space would be made free from internal storage by allowing another 32 GB space of "internal memory."  But because this is a Samsung device, there is no option to adopt the SD card as internal storage.

Using ADB to force enable the option to adopt the SD:  Another post on this site explains how to use ADB to force enable the option to adopt the SD card as internal storage on Samsung devices.  But even after multiple tries, this method just simply does not work with my phone model.

These were the only methods I could find on the subject.  It seems that I am out of luck with freeing up any more internal space than I have.  I could try converting an app I would like to force move to an APK and editing it to enable the option to move to SD, but then I would have to repeat that process every time I want to update the app, plus I want having to hack the app to be my absolute last resort.
Is there any way to free up the internal storage on my phone, by forcing uninstall of the stock apps without rooting, by forcing adoptable storage using another means that I have not tried, and/or by forcing apps to the portable SD card using another method I have not tried?  And a sub-question:  is there a way to force Google Play to install updated apps straight to the SD card?

Actually, it sounds to me like you just made a poor choice in devices in that you got one that doesn't have enough internal storage. Otherwise it seems like like you have tried all the normal ways of making more space and are out of options. Sorry.

Just a tip. You don't need a specific rooting procedure. You can just unlock bootloader, flash a custom recovery and then flash SuperSU zip package. It's a very general rooting method.

@acejavelin The phone is very obscure.  I would normally research this kind of stuff, but not many reviews exist, and the ones that do target a very general, non tech-savvy audience.  I once had an iPod Touch that only had 8 GB of storage, and I was able to install 40+ apps.  I had no idea I would be so limited with an 8 GB android.  But thank you for the tip, next time I will be much more conscious of that.

@iBug Thank you for the advice, but that's a bit too technical for me; I'm not THAT savvy.  I don't mind rooting if there's a step-by-step procedure, preferably in a video, for my specific device, but I would be afraid of bricking my device following that.  Plus the phone is very obscure, and I can hardly find any information on it as it is.

Apps that can't be uninstalled are called bloatware. You can search for a list of them to remove them manually (like this), a debloating script to flash via boot loader if you want to keep the OS/ROM (like this), or you can flash a custom ROM if you wish to start fresh.
If your phone can't use adb to partition the sd card, you may want to open a separated question regarding on this in detail.

One last thing to try would be a junk cleaner, try the one made by Norton (it's the only decent Norton software) and running it. It will clear any cache files and should not affect your device.

I actually have one and have been using it.  Currently using CleanMaster because it can move to the SD card and also can lock certain apps with a PIN.  If Norton can move to the SD card I may try it.  Would you say it works better than CM?


text:
Lost access to drawer icon for center button on CyanogenMod 7
I am running CyanogenMod 7 on my HTC Thunderbolt and somehow I inadvertently removed the function for the center button on my home screen between the phone and web browser icons.  This middle button used to bring me to the drawer where every installed application is listed, not just the ones on my home screen.
How can I restore the middle button functionality to get access to applications in my drawer?

Is the button still visible and non-functional, or is it missing from the action bar?

Missing from action bar, shows as Star icon and click gives message: No application defined yet, drop something here!.

It sounds like you just dragged the tray shortcut off the action bar accidentally. Try doing the following:

Long press on an empty space on any home screen
Select "Launcher Actions" from the menu that appears
Select "Open/Close App Drawer"
Drag the new shortcut back onto middle button of the Action Bar


text:
How do mobile companies change the boot animation?
I have been searching for an answer of how mobile companies and carriers get their branding like the bootanimation on a device. Do they do the same on every rom like go to /system/media folder and replace the bootanimation.zip file? How can they do this on a large scale? There must be another way also.

They don't have to change the ROM on every phone by hand. They have a relationship with the phone's manufacturer, so the carrier's customized ROM gets installed on the phones at the factory. This customized ROM might include their boot animation, bloatware, settings (e.g. APNs) for their network. These phones often also have slightly modified hardware: the outer shell badged with the carrier's logo, or in a different "exclusive" colour.

So how the manufacturer do it ? I need to know that if the bootanimation.zip file can be created after building the android source or it have to be copied manually.

Obviously they change it in the source as part of the build process.

Do you know how, or can point some tutorials on it..

I don't expect every company does it the same way. Since this isn't a programming site, and AFAIK nobody here works for a phone manufacturer, I don't think you'll get a more specific answer than that.

These carrier-specific modifications are committed to the source code and are automatically included during the build process through the build system to compile the source code and resources into a factory image (ROM as a flashable ZIP file or whatever format is used for distribution) or software update.
HTC released an infographic a few years ago illustrating why software updates took so long.

Google provides source code to HTC. HTC evaluates the new Android version's requirements.

So, Google releases the source code and the manufacturers evaluate which of their devices would be able to run the new software and how profitable it would be for the manufacturer to develop and ship the software update.

HTC assigns people and resources to support development of the new software version […]
HTC begins working with each carrier to define the scope of carrier modifications for that device including apps, services, and other requirements.
HTC incorporates carrier modifications into the code.

In point 6, manufacturers like HTC assign staff to work on different work items like device compatibility with the new software, but also developing new features. Which in HTC's case leads to a not very much AOSP-flavoured version of Android, but an HTC-flavoured Android.
At first, you would probably ask why a manufacturer would assign people from their staff to work with people from carriers in point 7. The manufacturer spends a lot of resources to create its own version of Android, but then someone else has a say? That's because to the manufacturer, a carrier is a customer with particular demands who is buying large quantities, and most manufacturers measure success by selling large quantities. So, assigning and paying a few more people to help carriers with branding devices to sell more devices through contracts to carriers (not to be confused with your carrier contract) suddenly makes sense from the perspective of a device manufacturer.
That's how different people from different companies like software engineers, quality assurance, network operations, and marketing staff come together to modify the source code.
The last bit here is to use overlays and similar mechanisms to maintain source code efficiently. So, you would have devices X and Y as well as carriers A and B, and changes/modifications are committed accordingly. You would just issue the build system to create builds for all possible combinations. This way, if people from the marketing of carrier A come up with a new bootanimation.zip and network operations of carrier B found a flaw in how device X behaves in the network, you would commit two changes but be able to build at least three new updated builds (if you didn't find that device Y is also affected). Of course, this is oversimplified.
You can download the source code of popular Android custom ROMs to your Linux box peek around and try it yourself. Here is the example for the Nexus 5 from the CyanogenMod Wiki, it's almost the same for all devices up until "Prepare the device-specific code". If you look into the shell scripts that follow after, you get a glimpse of what's going on.


text:
Where is the battery animation called?
I have a tablet from China, it's a Q8H Allwinner.
It is rooted, and I've browsed the internal storage for hours to find the battery animation, I found them at framework-res.apk...
Now I want to find the file who's calling the animation, so I can add a line with the code "/system/bin/reboot", so the tablet boot up on charging.
Does anyone have a clue on where can I find it?

The battery charging animation is usually a series of images, displayed in the status bar. Assuming that you are talking about them (the images in the status bar), they are animated when an event is broadcast.
Giving some more detail, whenever a charger is connected, an intent is broadcast, which is received by the SystemUI to animate the status bar's battery indicator image. When a charger is disconnected, another intent is broadcast so as to stop the SystemUI from animating the battery indicator images.
All of this is handled by the file BatteryService.java in frameworks/base of the android source.
The other charging animation that you are talking about, is when an image is displayed on the screen when the screen is turned off, but the charger is connected. This is usually known as off-mode charging, which takes over the framebuffer, and draws an image over it, according to two conditions:
1. charger is connected
2. display is turned off
Answering the second part of your question, the former method, BatteryService.java is in userspace, and you can not do much about it; as booting up the phone with only one service, and it showing the charging images. The latter, if exists on your device, would be when your phone is turned off, and connected to a charger, it usually boots up into the recovery, where it is 'checked' at boot time init whether the charger is present/not, and usually, shows the charging images.

The OP's intention is contradictory to your answer: he's looking for a way to boot up on charging.


text:
Pastel Colors in Phone/Dialer
I've got a Pixel 2 running Android 9 (Pie). The other day the colors for the contacts on the Phone/Dialer Favorites screen switched to what I can only describe as 'pastel'. They don't match the contact colors in the Messages App (though the used to). Switching a contact color in the Messages App has no effect on the new pastel color for the contact in the Phone/Dialer.
I don't think I fatfingered anything to cause this but I'm not going to swear to it. When I noticed it I had just picked up the phone and unlocked it to make a call.
Color Inversion (Accessibility) is not enabled. Dark Mode is not enabled. Phone is totally stock.
What caused this and how do I revert it?
Update 1
Co-worker with a Pixel 2 that recently upgraded to Pie noticed the same thing. It's quite possible the change happened at the same time for both of us (not at time of upgrade but a few days after). Is this something Google did? Something about Material Theming with the new Material Design they rolled out, pulled and rolled out again? Also, I've restarted and done a power off, so I don't think this is a transient glitch.
Update 2
Co-worker's Messages app has gone Pastel, mine has not so far, despite force stopping the Contacts App, the Phone/Dialer and Messages and doing a restart and power off. Phone is 23.0.208561757, Contacts is 3.0.6.209518734, Messages is 3.4.048 (Yehu_RC26_xxhdpi.arm64-v8a.phone).
Update 3
Yet another co-worker (Pixel 2 / Pie) has the same symptoms as me (Pastel Colors for contacts in Phone/Dialer only). So it seems this is definitely something to do with some kind of rollout of something by Google.

This question has been asked before and should be recognised as a duplicate. See this query for some guidance. Some have answers, some do not.

@wbogacz Related maybe, but I don't think duplicate.

@wbogacz I've got no Emergency Messages, I haven't synced contacts since I activated the phone and It's a Google device with the Google Phone/Dialer App, not a Samsung device (which has a different Phone/Dialer, right?).

Went to Settings->Apps & notifications->Phone->Settings->Uninstall updates (three dots) and ended up with 20.1.197612390. Colors are back to normal. Will see how long they stay this way and if they change the next time the Phone app is updated.
Update 1
The phone app was updated and the pastel colors returned. Downgraded again to get rid of them. It looks like this intentional on the part of Google.


text:
Pixel 9 Pro: Any way to record video with both wide-angle and normal lens? (both back-facing)
I want to produce two video files of the same scene, one taken with the wide-angle lens and one taken with the normal lens. Using a Pixel 9 Pro.
Is there any way to achieve that?
I am OK with rooting, and developing if really needed.
https://developer.android.com/reference/android/hardware/camera2/CameraManager#getConcurrentCameraIds() returns {{0, 1}} which makes me think it might be possible.

When I split the screen and use two third-party cameras, one stops showing live preview as soon as I start the other one.
Questions on this topic (1, 2, 3) conclude that it depends on the model, hence my model-specific question. Full info shown by Open Camera:
Open Camera v1.53.1
Code: 90
Package: net.sourceforge.opencamera
Android API version: 35
Device manufacturer: Google
Device model: Pixel 9 Pro
Display size: 960x1935
Display metrics: 960x1935
Current camera ID: 0
No. of cameras: 2
Multi-camera?: false
Camera API: Camera2 (Android L)
Camera orientation: 90
Photo mode: HDR
Min zoom factor: 0.51
Max zoom factor: 30.0
Preview resolutions: 1920x960, 1280x960, 1280x720, 1024x768, 1024x576, 800x600, 720x480, 640x480, 640x360, 352x288, 320x240, 176x144
Preview resolution: 1280x960
Photo resolutions: 4080x3072, 4032x3024, 4000x3000, 4032x2268, 3840x2160, 4000x2000, 3264x2448, 3264x1836, 2560x1920, 2688x1512, 1920x1920, 2560x1280, 2048x1536, 1920x1440, 1920x1080
Photo resolution: 4080x3072
Video qualities: 1, 6_r4000x2000, 6_r3264x1836, 6_r2560x1920, 6_r2688x1512, 6_r1920x1920, 6_r2560x1280, 6_r2048x1536, 6_r1920x1440, 6, 5_r1600x1200, 5_r1920x960, 5_r1792x1008, 5_r1440x1080, 5_r1344x1008, 5_r1280x960, 5_r1080x1080, 5, 4_r1024x768, 4_r1024x576, 4_r800x600, 4, 3_r640x480, 3_r640x360, 3, 7, 2
Video resolutions: 3840x2160, 4000x2000, 3264x1836, 2560x1920, 2688x1512, 1920x1920, 2560x1280, 2048x1536, 1920x1440, 1920x1080, 1600x1200, 1920x960, 1792x1008, 1440x1080, 1344x1008, 1280x960, 1080x1080, 1280x720, 1024x768, 1024x576, 800x600, 720x480, 640x480, 640x360, 352x288, 320x240, 176x144
Video quality: 6
Video frame width: 1920
Video frame height: 1080
Video bit rate: 33000000
Video frame rate: 60
Video capture rate: 60.0
Video high speed: false
Video capture rate factor: 1.0
Auto-level?: Available
Auto-level enabled?: false
Face detection?: Available
RAW?: Available
HDR?: Available
Panorama?: Available
Gyro sensors?: Available
Expo?: Available
Expo compensation?: Available
Exposure compensation range: -24 to 24
Manual ISO?: Available
ISO range: 22 to 11277
Manual exposure?: Available
Exposure range: 26345 to 500000000
Manual WB?: Available
WB temperature: 1000 to 15000
Optical stabilization?: Available
Optical stabilization enabled?: true
Video stabilization?: Available
Video stabilization enabled?: false
Tonemap curve?: Available
Tonemap max curve points: 65
Can disable shutter sound?: Available
Camera view angle: 70.71637 , 53.671764
Flash modes: flash_off, flash_auto, flash_on, flash_torch
Focus modes: focus_mode_auto, focus_mode_macro, focus_mode_locked, focus_mode_infinity, focus_mode_manual2, focus_mode_edof, focus_mode_continuous_picture, focus_mode_continuous_video
Color effects: None
Scene modes: auto, night, portrait
White balances: auto, manual, incandescent, fluorescent, warm-fluorescent, daylight, cloudy-daylight, twilight, shade
Magnetic accuracy?: 1
Using SAF?: false
Save Location: OpenCamera
Save Location SAF:
Parameters: None

To prevent "spy apps" I believe that only one app is allowed access to the camera APIs at a time. Recent version of Android do support multi-camera operation. You may want to install/run Open Camera from F-Droid In Open Camera, gear icon, scroll down to 'About' and then copy from clipboard the debug/device results into your question. There should be an entry called 'Multicamera?'

@MorrisonChang: Thanks! Pasted. It says Multi-camera?: false... is there any way to modify this?

Related StackOverflow: Opening Second Camera with Camera2 Multicamera API. After reading that to me Its unclear to me if a 'false' there just means just strictly sticking to the Camera2 APIs. You may want to try Camera2 API Probe but theSO link really points out the limitations that may exist in the camera pipeline.

@MorrisonChang I ran Camera2 API Probe, and in Available capabilities I see LOGICAL_MULTI_CAMERA.

If you read the docs, LOGICAL can be fusion of multiple physical cameras. I have a Pixel 6a which has a regular & wide camera on the back, that app reports similar. Hopefully someone has attempted what you are seeking and state what is possible. Should you wish to try, I would look at: https://github.com/ananthrajsingh/front-rear-simultaneous-camera as a starting project and then modify to use physical rear cameras (if possible).


text:
Why do I have to set lots of my settings again after a phone reboot?
For examples:

I have to set Input Method back to SwiftKey
I have to set what application I'd like to use when I clicked sms icon (I'm using ChompSMS)

All these happens after a phone reboot.

Do you have either app moved to the SD card (using Froyo)?
If yes, then you need to move then back.  The apps aren't loading when the phone boots, so the phone is reverting to what is currently available on boot  (stock SMS/keyboard).
You have to remember: with Cyanogenmod, it will let you move any app to SD card, regardless of whether the app is set to allow you or not.  I made a similar mistake with Swype.

It seems you're right, I've had exactly the same issue on Cyanogenmod 7, with SwiftKey and Twitter.  I think it might be a bug in the apps in question - I'm pretty sure it was happening with the Facebook app as well but that seems OK now, so possibly recent update fixed the issue.

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


text:
Disable application update notification
How can I disable certain application's update? I'm using Brut Google Map v4.6.0.4686. Since there is a new version in the market, the update notification will appear from time to time. How do I disable it?

I only receive notifications the first time an app has an update.  After that it just sits in the market's "My Apps" list with red text showing there's an update, even if the app is updated more times after that.

Try rebooting your phone, it'll reappear again

I reboot my phone lots.  What version of the Market do you have?

I think it's version 4. The one before Google changed the whole UI market. I'm using CM 6.1

I don't think there's a way to disable market update notifications for a single app right now.
In order to disable update notifications for all apps in the Market, open the market app, press the MENU button, choose SETTINGS.
In the Notification drop down, select DO NOT NOTIFY ME.

Thank you. Indeed I can disable market>menu button>settings>Notification checkbox.

I'm running cm 6.1 as well and I have a bug in my market that if you have, may solve your problem. My app updates get stuck sometimes and I've noticed if I cancel. An update the app no longer shows up as needs to be updated, or even installed, although it stays in my dl list. You could try starting the update then cancelling mid download. For me these apps in limbo don't give the update notification.

Seriously? I think I've had (sort of) similar experience, my internet connection had a problem during the update process, so, the app cannot be updated which causes the app to disappear from the list (I think Android uninstall the app before downloading the update).

Yeah, I'm serious.  It might just be a bug on my phone. The market is very wonky for me.  Every single time I update my apps, at least one gets hung up and I have to cancel it.  When I do it shows up as a new app, not installed even though it is still installed.  Strangely enough, even though it says it's not installed and stops giving me update notifications its still in my downloads list.  All I have to do to actually update it is to click on "install."

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


text:
How to change default PDF viewer on Nook Color?

I just upgraded my Nook Color to the
new 1.2 version that supports apps.
I purchased the ezPDF Reader app
which supports bookmarks and other
advanced features for PDFs which the
default Nook Color PDF viewer does
not support.

Is there a way to make the ezPDF Reader the default PDF Viewer?
(Currently when I click on a PDF the default viewer still opens)
To Clarify:
Currently I have to open the ezPDF Reader first and then open a PDF from within the app. If I simply click on a PDF on a book shelf or on the home screen then the default PDF viewer opens the PDF. I don't see any area in settings like on a regular Android phone to modify installed apps or app settings.

I didn't know the Nook ran Android.

Yes it does. The latest version is on Android OS 2.2/Froyo.

@KevinM Yep, I flashed CM7 on my a while back

The latest update of the Nook Color software  Version 1.4.1 allows you to change the default PDF reader. After the upgrade open a PDF and then a pop up box will appear allowing you to choose which application you want as the default PDF reader.

Find the app that took over the PDF intent in Menu -> Settings -> Applications -> Manage applications -> All, and then tap on Clear defaults button.  Next time you click on a PDF file, it should prompt you which app to use.  Check the Use by default for this action box, and tap on ezPDF Reader.
Alternatively, you can try uninstalling and re-installing the ezPDF Reader app.  It should re-register its own intent for handling PDFs, and prompt you for an app next time you try to view one.

This works on a Nook Color which is not rooted?

@KenB: it's a fairly standard way to clear defaults on Android phones, unless Nook was modified so this won't work for no reason this should work.

Yes, Nook Color is a custom / modified version of the Android OS. I don't believe you can access the application settings (as was described above) like you would on a standard Android device. Has anyone tried this on a Nook Color with the version 1.2 update?

I'm running CM7 on my NC, so I had no idea they disabled application management tools in stock firmware.  What about uninstalling/re-installing your PDF reader app? That should register its intent and allow you to select it as the default.

Nope, that doesn't seem to work. I still have to open the ezPDF Reader first and then open a PDF from within the app. If I simply click on a PDF on a book shelf or on the home screen then the default PDF viewer opens the PDF. I don't see any area in settings like on a regular Android phone to modify installed apps or app settings.

There is an app for that !! Try Default App Manager on the Android Market which can take care of both clearing and setting defaults for various categories like pictures, audio, video, pdf etc. Really makes life very easy.


text:
Root EVO 4G stock ROM?
I've got a Sprint HTC EVO 4G Wimax.  I want to get rid of the Sprint Apps to free up some space on the internal storage, but otherwise leave the phone stock for now.
I followed the instructions at the HTCdev website to unlock my bootloader and I installed Superuser from the Play Store.  If I can get an su binary installed, I can give root to Titanium backup and remove the Sprint Apps.  There is a zip file at androidsu.com that I think I can flash, but that's the bit I haven't figured out yet.
Since I've got an unlocked, but otherwise stock phone, I guess I don't have a recovery image, since if I boot into recovery mode, I get a red triangle with an exclaimation point.
What are my options for recovery images?  Is there anything besides ClockworkMod or Amon Ra?  If I go with either one, how do I get it installed?
Or is there a better way to get this done?
Update:
I Installed Amon Ra and used it to flash the su zip file.  I removed the apps that I could without breaking anything.  I didn't free up any space I could use at the moment, but I'm happy to have them gone.

I want to get rid of the Sprint Apps to free up some space on the internal storage - just to note, removing built-in apps won't give you more internal storage space. Uninstallable "bloatware" apps are on a separate partition from user-installed apps, and the space of one doesn't affect the other (unless you repartition your device entirely).

@eldarerathis  Sadly, it seems that you are correct.  Deleting a built in app does not free up any internal storage.

What are my options for recovery images? Is there anything besides ClockworkMod or Amon Ra?

A third popular option is TeamWin Recovery Project, usually referred to as TWRP.

If I go with either one, how do I get it installed?

Since your bootloader is unlocked, you can use fastboot to install a recovery if you download it in .img format. You do this by downloading the recovery image to your computer, plugging in your phone, and executing:
fastboot flash recovery /path/to/recovery.img

from a PC command prompt while your device is booted into fastboot mode.
Alternatively, ClockworkMod and TWRP can both be installed from apps on rooted devices. For ClockworkMod you can use ROM Manager and select the "Flash ClockworkMod Recovery" menu option. TWRP can be installed using GooManager by selecting the "Install OpenRecoveryScript" option in the app's settings menu.
A third option is to get a copy of the recovery you want in a bootloader-flashable zip file. For the EVO it will be a file named PC36IMG.zip. You put it on the root of your phone's SD card and then reboot into your bootloader and it should flash it for you. I know that Amon Ra has been distributed in this format, but I'm not sure about the others.


text:
Android device load process (preparing flashing)
Standard Android OS load process looks like (from docs):

BootROM (starts with 'on' button)
Bootloader
Kernel
init/mounting
Zygote+Dalvik VM
System services

But I have a difficulties understanding load process preparing flashing (how I met it flashing Galaxy Tab and MTK cellphone ROMs)
Could you help me to find a position for those tools on the list/diagram:

The code that show logo (or battery charge in percents when power cable is on) and respond to USB (when phone is off but battery is inside) ? Where it is ? It should be postioned before Boot ROM - but how you name it?

who are responsible for handle "on + volumne down" to switch to "bootload" menu ? BootRom or Bootloader?

"preloader" how it is positioned there? (I'm not sure that I understand what preloader is).

Twrp ? fastboot ? odin3  does they replace Dalvik or run over it? twrp by itself look like full OS.

Boot process of Android devices up to kernel stage is very vendor specific, device specific and contains mostly closed source code. You may see clear deviations of terminologies used and differences in their implementations. Here I'm giving a simple understanding.

When the charger is inserted, the device boots very similar to when the power button is pressed, except that a very limited OS is loaded.
Device boots normally up to init stage (given at point 4). init, instead of starting services from /system and /vendor partitions, starts a process: /sbin/charger* which is not a part of AOSP. Charger binary is usually closed source and varies for different devices. It may load some pictures / animations stored on some partitions specific for this purpose.
Also, some OEMs allow enabling / disabling off-mode-charge through fastboot to control the behavior i.e. whether the device should be switched on when power is plugged in or not. But it's also not a standard feature and varies for devices.

Bootloaders (SBL / ABOOT or equivalents) handle Power and Volume buttons pressed to start (Emergency) Download mode, SPL mode, fastboot mode etc. and recovery or normal kernel.

Preloader is a bootloader stage (SBL / SPL) before final bootloader (UBOOT / LK / ABOOT)

Here is the boot chain:

BootROM
Primary / Secondary BooLoader or PreLoader
Final bootloader (which provides odin / fastboot)
Kernel / Recovery (TWRP)
Init (first userspace process and in-charge of all other processes, also mounts filesystems)
Services or processes are started from /system and /vendor partitions by init (Zygote / Dalvik is one of those).

So odin (specific to Samsung) and fastboot are two independent protocols for communication with device through USB to format partitions, flash factory firmware, (un)lock bootloader etc. While TWRP is a minimal OS which is booted in place of normal boot.img (usually using same kernel) in case Android is unable to boot or needs OTA update or some modifications / maintenance.
None of them can be related to Dalvik, they are hardware specific and run at pre-kernel or kernel stage. While zygote - a part of AOSP - is a completely userspace process which forks a Dalvik Virtual Machine for every app.

For details: Boot Process: Android vs. Linux


text:
How the device (that is off) decide how to publish itself for USB: "MediaTek PreLoader USB VCOM port" or "MediaTek USB Port" device?
How the mobile phone (that is off) informs the Windows PC (with installed drivers "MediaTek PreLoader USB VCOM port" and "MediaTek USB Port") how to identify itself: as device
- "MediaTek PreLoader USB VCOM port" or as
- "MediaTek USB Port"?
When I plug the phone to USB, Windows PC connect it sometime through "preloader USB", sometimes through "just USB" ports, sometimes both  in sequence  (I see it from WMI events). I don’t see any pattern related to "time after next attempt" or "volume buttons pressed".
P.S This is "the phone off" state when battery is inside. What are correct names for those states (battery "in" and "outside")? When battery is extracted - device is not recognized as USB device by PC.

I can't see the question here ?
Are you asking what the driver is for ?
Please have a look at this video to understand what the preloader is, MTK Backup & Restore
The Mediatek Preloader is used for flashing new image's to your device.
Their is two different boot loaders on Mediatek device's..

MTK DA USB - For flashing the Preloader
MTK Preloader  - For flashing all other image's

How does it register as a device while it's off ?
This is so you can fix your device when it won't even turn on, it need's to be before the boot of your system.
I hope i somehow answered the question here.

Thank you. It is become more clear. But I still do not understand how the device decide that "at this moment I should be handled by MediaTek PreLoader USB VCOM port but next time as MediaTek USB Port" ? This is what I observe when plug the phone (that is off) to the USB. Sometimes it is connected through  “MediaTek USB Port” driver sometimes as for "MediaTek PreLoader USB VCOM port" driver... Answer could be "when you press the volume button it will be handled with PC preloader port driver" (but the problem is that I do not press any buttons and it is still get variety of results)

I have always had my MTK device's do this... It is because the Preloader only connects very shortly, it requires the PC to make a Handshake to hold the connection... If the PC doesn't make a Preloader Handshake, it'll drop the preloader and connect via Meditek USB Port ( CDC ) instead of Preloader... As fas as i can tell, it's just a fail safe

Also, i believe on some older models, you could hold volume down or up. and it'd hold the preloader connection open, for easier driver installation... It gets annoying using device manager because as your about to click on the port and install the driver, it disappears or change's, making driver installation really annoying.   I've always found it easier to manually install the drivers prior to connecting the device.

But that is not what I observe with my Alcatel Pixi 3. As I said - I observe totally random behavior: sometimes handshake for "just USB" sometimes for "preloader USB", sometimes (very rare) two in sequence as you said (but with different order: "just USB" first "preloader USB" second). I have tried buttons but they do not change anything.
Lets decide this is a kind of bug.
What kind of program (how you call it) propose handshakes?

I mean "What kind of program run on the phone when it is off (but battery is inside)?" Is it a "BootRom" - I have met this term several times..

One more question, what does it mean " click on the port " ?

When both devices are recognized by Windows computers, they're separated by Port Numbers ( MTK USB - Port 47 ) ( MTK Preloader - Port 48 ) ... This is to help the computer differentiate the two devices connected ( It seems weird but I'll explain ) ... The MTK Preloader & CDC Device's are a part of the CPU ( Mediatek ) firmware, it allows flashing like Fastboot for example... You use the drivers in the factory, The CDC Driver is for writing heavily secure parts like the IMEI numbers, The Preloader is used for writing to the storage for placing the system firmware.    Think of it like this...

On some device's these ( terminals ) are only accessible by pulling the back off your device and using a cut up USB cable and some paper clips to touch the right terminals ... MTK made it as simple as using the USB port for writing to the device... If that makes sense.


text:
No Turn-by-Turn Directions on Google Navigation
Google Maps gets fairly frequent updates (although I don't use it all that much). But, I have recently had to use it for some travel. I noticed that, where Google Maps used to give directions in this fashion...
"Turn left onto Main Street in 0.2 miles."
...ever since I did an update (no clue which update it was - as I said, I don't use directions THAT frequently) now all it says is...
"Left"
Needless to say, this makes it rather painful to use for direction purposes. What do I need to do to fix this? I Googled around, but didn't find anything. Would appreciate suggestions.

Is this Google Maps or Google Navigation?

@LieRyan - Technically, I suppose it is Google Navigation. (I'm browsing to the street address through Google Maps.)

This is a known issue with some versions of ICS: http://productforums.google.com/forum/#!msg/maps/FDKwbM5zMuU/TthydW9YLhoJ

@Zooks64 - Oog. That's a bummer. Well, I just got 4.0.4 (the OTA pushes have begun). Next time I'm out driving, I'll test it out to see if the problem has resolved itself.

@JasCav I just installed the 4.0.4 update yesterday but haven't had any reason to try out the turn by turn directions since then. I sure hope that it is resolved - I got spoiled with the street names.

Turns out the issue appeared to be specifically with a Google Maps update. I have received two updates over Google Play since then and the problem appears to have resolved.


text:
MadTeam's CyanogenMod 7 restarting itself randomly
I installed MadTeam's CyanogenMod 7 on my Galaxy 5 few weeks ago. First time I root and install a mod, but fairly uneventful process. My phone got way faster, and except for maybe getting a little slower to connect to the wifi and/or obtain an IP address, it is better in every possible aspect.
What is bugging me is that it is prone to restart itself randomly, possibly many times a day, except that I don't notice it most of the time. Just now I noticed because it was in front of my keyboard, and it vibrates when showing the boot animation. The boot itself is quite fast, so it really never posed any problem so far, and it never restarted mid-use, only when inside my pocket or laying on the table (ie. during standby). I just worry that it may become too common or happen during a call, while texting or something.
I fiddled a lot with the configs after installing it to discover what it had to offer, but I avoided changing anything that wasn't UI/usability-related. I took the performance settings warning seriously.
Any possible explanation? Or is this somehow normal, like a hard memory cleaning procedure? I did some seaching, but nothing about such issue.

Phone: Samsing GT-I5500 (Galaxy 5)
Mod: CyanogenMod-7-20120912-MADTEAM-galaxy5 (Android 2.3.7)

Updated mod to 20121001 version.
Got two unresponsive events (once unlocking screen and another one activating wifi) which caused phone restart seconds later, and according to phone uptime counter, an spontaneous reset 2AM last night. Within 48h.
Wifi got awfully bad after update (same baseband I5500LUYJPE), took dozens of tries to get an IP, but apparently it was solved by forgetting the network and typing the password again.
In short: wifi improved, random restarts remain.

Did you update the baseband as recommended to match your Galaxy 5? Some basebands are known to cause the sleep of death (I have one here!), boots up CM fine, then after a while, it goes to sleep and then completely dies which results in charging up the battery again.

@t0mm13b Yes, I changed it. After installing the mod, it was set to the stock ROM's baseband, I5500BVJJP7. I felt the wifi was bad (worse than now), so I followed the MadTeam devs suggestion and changed to I5500LUYJPE. The wifi improved somewhat, but I'm unsure if this baseband is responsible for this behavior, because I switched in less than an hour. I'll take a look about the SoD and see if it fits my case, and I might try the older baseband. Thanks!

Sometimes strange things happen when one forgets to wipe the Dalvik cache when first installing CM. As it doesn't hurt, you could try this (you should be able to do so from the recovery menu). That cleans up things, and the Dalvik cache will be rebuilt on the following boot (so don't wonder if that boot takes a bit longer than usual).

@Izzy Well, when installing I'm sure I did wiped the caches... twice. I could wipe it again, but I just found out that a new version of the mod was recently released, promising a SoD fix for some cases, plus better DHCP handling. I'll try it later today, and post whatever difference it makes. Thanks for your suggestion.

Could be good news. In case that solves your problem, I suggest you post the results as an answer. Crossing fingers!

So, to avoid a hanging question:
Using the new ROM for almost two months. Tried the original stock baseband I5500BVJJP7 but it felt overall worse, so I went back to I5500LUYJPE. Now any issue is rare... it's weeks since I last noticed a random restart, my phone reports over 160h uptime (not 100% reliable, I've seen it not restart after a crash), and wifi is most of the time fast to get in IP.
In the end, as things improved with a new ROM, I suppose the issues are due to small quirks of the ROM itself. Should improve over time.


text:
Why are there multiple versions of "Phone" installed under all apps in Android Lollipop?
Why are there multiple versions of "Phone" installed under ALL apps on my Android Lollipop 5.1.1 phone?
Menu = Settings → Apps → ALL
There are three versions of "Phone":

Phone - com.android.server.telecom
Phone - com.android.phone
Phone/Messaging Storage - com.android.providers.telephony

There was a mistake in my last (now deleted) comment. Sorry for wrong info.

not a problem - a little research suggests that com.android.server.telecom supercedes com.android.phone but they're both running concurrently on my phone (as "Phone"). com.android.phone is giving me a spurious voicemail message "New Voicemail (255)" everytime I start the phone. And runs as a separate process to the other - so I'd like to delete it, but am nervous over any side effects...

Do you have root access? A normal user cannot remove a system app and Disable option is greyed out for them.

I've managed to clear the phantom voicemail (just needed to leave another voicemail and delete). But I'm still interested in why there are two "Phone" apps running concurrently on the phone (notwithstanding that the packages aren't actually the same) - so I'll leave the Q open for a bit

Phone/Messaging Storage - com.android.providers.telephony
The Telephony provider contains data related to phone operation, specifically SMS and MMS messages and access to the APN list, including the MMSC to use.
Phone - com.android.server.telecom
Phone - com.android.phone
The package name has been changed from "com.android.phone" to "com.android.server.telecom" on some devices ( ex. Nexus 5 with Android 5.0 )
But for some reason you have both the packages. They are probably different apps and should not cause you any trouble.

The point is to find out what's that "some reason". OP already figured most of the stuff, see his comments. Thanks though, for posting the answer here.

@Firelord Most possibly due to an update. but it actually depends on the phone

These are not different versions, these are different apps. An app can have any name regardless of other apps' names. It is possible to have hundreds of apps with the same name on one phone because the name you see as a user has nothing to do with the name which sees Android (for example the system name for Shazam is com.shazam.android).
I have two "Camera" in my phone. One was pre-installed and the second is Google Camera whose visible name is also "Camera".


text:
Is there a widget for Twitter search?
I'd like to monitor Twitter for certain keywords.  I wonder if there is a widget which displays live search results on my home screen, which are automaticly updated at a certain interval. I've tried almost every app in the store, but none provides this simple functionality.

Have you tried Falcon Widget (for Twitter)? https://play.google.com/store/apps/details?id=com.jv.falcon

@IvanChau It misses that functionality

Since the anwer seems to be: "no there isn't", my workaround was to use an RSS-reader widget, and the following RSS URL: search.twitter.com/search.rss?q=keyword.
I think its strange I have to go through such hoops, since Twitter provides a HTML-widget for exactly this purpose.  I was expecting at least one Android app to mimic this functionality.

Unfortunately, this solution will stop working when Twitter will retire its old API on June 11, 2013.

There don't seem to be any widgets that let you monitor twitter for certain keywords, but here's a workaround that might do the trick.
Try an application like Meta widget. It can turn any webpage to a widget.

That's an original work-around, but not really what I'm after. I doubt it will have any transparency for example.

I don't think you can do something like that in a widget. However i allways wanted to test this app Falcon Pro (for Twitter), but i don't think you can have a widget, but you can make a search and save it for latter and do not have to retype every time.
Janetter for Twitter has this option of saving searches and notifies you about them, but it doesn't have a widget...

There is an official HTML widget from Twitter to display searches, so all somebody needs to do is put that code in a Android widget, doesnt seem like rocket-science.

Maybe u can try this (TweetCaster for Twitter)   https://play.google.com/store/apps/details?id=com.handmark.tweetcaster&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5oYW5kbWFyay50d2VldGNhc3RlciJd


text:
Use Voice Remote for Google TV with Android TV
I paired the Voice Remote for Google TV with an Android TV succesfully, and all functions work. Except for powering on the TV when it is off. This makes sense because I suspect that the Bluetooth chip is disabled when the TV is in standby.
Since the Voice Remote for Google TV is capable of sending infrared signals, this should be very easy to solve. But I can't figure out how.
Maybe I can pair the remote to somebody elses Google TV and setup the infrared function for the powerbutton? But I suspect that when pairing it back to the Android TV afterwards, it will also clear the infrared preference stored on the remote in the process.
Does anyone know a solution for this? Because there is no technical reason this cannot be done, it's just that Android TV doesnt provide the setup menu.

You lack clarity on what exactly you are doing. Is it that you have the Google Chromecast (the HDMI part) AND the remote? OR just the remote that you've paired through Bluetooth to the TV? The wake signals can only be sent through wifi or if the HDMI part of the Google Chromecast device is connected to the TV. The remote talks to that HDMI part which in turn turns on the TV.

No, I don't have a Chromecast. I have a TV with Googles Android TV OS (and ofcourse these have Chromecast build-in, so it would not make sense to connect an external HDMI dongle to it). I also have a Google Voice Remote (which have infra-red build-in). My only question is how to setup the infra-red on Android TV OS. Since that is very easy to do on Google TV OS, and as both OS'es are virtually the same under the hood, I expect there must be a way. There are also tricks to upgrade Android TV to Google TV, which will solve the problem. But as the TV is brand new I dont want to void the warranty.


text:
Is there a real time wifi traffic analyzer for Android?
I'm using SugarSync to sync files between my phone and my computer, but I'm not sure if things are actually working as they should.
It would be great to watch Android network traffic in real time.
Does anyone know of an app?

There is an app called 3G WatchDog.
It can monitor 3G data transfer and Wi-Fi traffic. A pretty neat application.

Click image for larger version

Isn't really an answer, but...
There is WiFi Analyzer which shows more information on the wireless networks your device can reach. It gives you more detail than the average user would require.
As far as I know, there is no application available on Android (yet?) that can "sniff packets".
Would be an interesting application to have in the pocket.

Cool app.  Thanks for pointing it out.  I use Tomato firmware on my router to do the same thing but Wifi Analyzer will make it much easier.

This isnt true now. If you have root access. There are a variety of Packet sniffing applications and some which even do session and cookie hijacking for you. Facesniff and Droidsheep are 2 prime examples.

You can view, sniff, and save actual network packets, however this requires root access.
Shark for Root app does this.

You don't need root to do this! Android apps can utilize the VpnService API to capture packets without root.
Here are some apps I found that do not require root:

Packet Capture
tPacketCapture

I use CoolTool to get current information about my phone. And with this you can monitor traffic data (ascending and descending).
The pro is that it displays as an overlay then you can monitor while using the app. Hope this will be helpful.

Internet Speed Meter Lite is an app which exactly does it.

Network Log is an app quite simple to use. It shows real time packets in a human-readable way as well as statistics. It takes it directly from iptables, hence you need a rooted device.


text:
How do I change the lock Pattern !!!! - Lenovo A7000
i have lenovo A7000, and i had recently had performed a reset, but, after setting the pattern, now i want to change the pattern as my brothers know the pattern. so, whenever i go to security settings and try to change it, the screen becomes repetitive and asks me to confirm the pattern infinite times, after giving the correct pattern too it again asks the same.... i cannot the change the lock as there is no screen to set it on the different modes like pin etc. what should i do ??? i tried clearing the certificates but it is grey and i dont want to hard reset or format the phone now.... pls tell me the correct way to go through it......


text:
Have I Killed My SAMSUNG TAB 2?
I couldnt update my tablet kept getting the message, "Cannot update as this device has been modified."
So I searched for advice on how to fix it. I was told to put in recovery mode by pressing power + volume down, which I did, but when it came on the message on screen was "WARNING DOWNLOADING NEW OS CAN FATALY DAMAGE YOUR DEVICE. Push volume up to continue volume down to cancel."
I pushed up before realizing what I had done. It then said , "Downloading do not turn off tablet." It was saying this for about half hour then went off. Now I cant get it to come on. Is it dead?

Was the tablet rooted or modded?

Hold the Power button until the device restarts. If it does not work, hold both Power and Volume Down.


text:
Using micro USB port as audio output
So, the audio output jack of my Samsung Note 5 just broke and it costs too much to get it fixed locally.
Would I be able to use the micro USB port as a replacement for my audio jack assuming I had a micro USB to AUX adaptor?
Phone Model SM-N9208
Android Ver. 7.0

B;uetooth might be your best bet.

As said in this XDA post,

Clearly the Note 5 supports USB audio, but it appears to not work properly.

So you can be sure it is, but also you should be aware of potential incompatibilities with your USB audio peripherals.

Source
This is true, in most cases, if you plug a USB to aux cable into your phone and connect it to your head unit. Some phones and MP3 players are designed to output audio signals via USB connection, like the original HTC Dream that used a single micro-USB connector for both power and audio output, but most phones and MP3 players come with a standard 3.5mm or 2.5mm TRRS headphone jack for a reason.
Many phones and MP3 players aren’t specifically designed to output sound via their USB connection. The USB connection is capable of transferring digital data back and forth, and can likely also be used to charge the device, but it usually won’t be designed to output an audio signal.
The only case where you would want, or need, to output audio from a phone’s USB connection to an aux input in your head unit is if the phone didn’t also include a headphone jack. Some phones, like the original G1/HTC Dream, omitted a headphone jack in favor of the ability to output sound via the USB connection.
Can't guarantee you for your specific device but you should try this product. Its easily available in local stores and online shopping sites too.


text:
How Device memory allocation happens
Under the Memory settings entry, there are several categories such as Apps and Documents.
What is considered as part of the Misc category? It's taking up a huge amount of my device's memory.

Everything not mentioned explicitly in the other sections. What exactly it is I cannot tell, but that would e.g. include logs (especially "tombstones").


text:
Can anyone identify the S notification icon
Someone please help me identify the S at the top left corner of my picture

Please  swipe down to list notifications and tap on notification to open it. check  settings, whether you have installed any launcher or app named with S.

I figured it out finally. It is Shopkick app.


text:
Failed to change my mac address by Android terminal Emulator
I followed all steps in this article trying to change my mac address. https://geekeasier.com/change-mac-address-in-android-devices-without-root/4792/#comments.
Then when I entered ip link set wlan0 address XX:XX:XX:YY:YY:YY ,it shows request send failed:permission denied.
I was using mac address generator and didn't change the address prefix,I tried turn wifi on and off all still didn't work, don't know where do I go wrong.
Is the wlan0 above should be something else?
Or there is something I have to do with phone first?

Which Android version and phone model? Also keep in mind the last paragraph of the article before the comments (it can work but does not have to and it may not work on newer Android versions).

Not working on Google Pixel with Pie update.

ifconfig wlan0 hw ether xx:xx.. doesn't work either.


text:
Sync Status Exchange Calendar
Due to inconsistence of the exchange calendar sync at work, Id  like to have some kind of widget or notification or whatever is easily doable, to see when the calendar was synchronised properly the last time. The IT guy seems not really interested in fixing the problem, considering its hard to find the problem probably, and I really don't like missing stuff.
I already searched for some time and haven't found any apps or widgets in the play store.
Do u guys know if there's a way to do this?
Thank you in advance for your help.