Status Update
No update yet.
Comments
sh...@gmail.com
Same problem here.
In config.ini, I have set:
sdcard.size=500 MiB
In hardware-qemu.ini, I have set:
hw.sdCard = true
In config.ini, I have set:
sdcard.size=500 MiB
In hardware-qemu.ini, I have set:
hw.sdCard = true
ni...@gmail.com
The issue is that the sdcard is not writable. You can workaround this by running:
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /mnt/sdcard
But those settings are lost once the emulator is closed.
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /mnt/sdcard
But those settings are lost once the emulator is closed.
hb...@gmail.com
I can confirm this an issue I am also having on Android Studio 2.3.
The second comment (https://code.google.com/p/android/issues/detail?id=240155#c2 ) of making the SD card writable, does work for me. The camera continues to say "Insert an SD card before using the camera"
The second comment (
ni...@gmail.com
API 15 galaxy nexus sd card not detected in storage settings
sh...@gmail.com
Is there a solution to this at this point of time?
Having the same issue.
Can't download anything nor take any pictures even the sd card writable workaround does not work for me (API 17).
Having the same issue.
Can't download anything nor take any pictures even the sd card writable workaround does not work for me (API 17).
ge...@gmail.com
For some reason the sdcard is *not* being mounted in the android system (API 16,17 only, 18 onwards WORKS AS EXPECTED) within the emulator.
adb shell
root@android:/ # df
Filesystem Size Used Free Blksize
/dev 757M 68K 757M 4096
/mnt/secure 757M 0K 757M 4096
/mnt/asec 757M 0K 757M 4096
/mnt/obb 757M 0K 757M 4096
/system 532M 349M 183M 4096
/cache 60M 40K 60M 4096
/data 1G 83M 1G 4096
The above is for a API 17 img, same thing happens with both "Studio Managed" sdcard as well as sdcard img file created both via the GUI and mksdcard.
No clues at all in the dmesg, in logcat there is only:
05-12 03:22:54.430 1154-1154/? D/Vold: Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
05-12 03:22:56.380 1486-1499/system_process D/MountService: got storage path: /mnt/sdcard description: USB storage primary: true removable: false emulated: false mtpReserve: 0 allowMassStorage: false maxFileSize: 0
05-12 03:22:56.380 1486-1499/system_process D/MountService: addVolumeLocked() StorageVolume [mStorageId=0 mPath=/mnt/sdcard mDescriptionId=17040615 mPrimary=true mRemovable=false mEmulated=false mMtpReserveSpace=0 mAllowMassStorage=false mMaxFileSize=0 mOwner=null]
05-12 03:22:56.390 1486-1522/system_process D/MountService: volume state changed for /mnt/sdcard (null -> removed)
05-12 03:22:56.400 1486-1522/system_process I/PackageManager: No secure containers on sdcard
05-12 03:22:58.180 1738-1957/android.process.media W/MediaScanner: Error opening directory '/mnt/sdcard/', skipping: Permission denied.
Just updated to Emulator 26.0.3 and still happening as above.
adb shell
root@android:/ # df
Filesystem Size Used Free Blksize
/dev 757M 68K 757M 4096
/mnt/secure 757M 0K 757M 4096
/mnt/asec 757M 0K 757M 4096
/mnt/obb 757M 0K 757M 4096
/system 532M 349M 183M 4096
/cache 60M 40K 60M 4096
/data 1G 83M 1G 4096
The above is for a API 17 img, same thing happens with both "Studio Managed" sdcard as well as sdcard img file created both via the GUI and mksdcard.
No clues at all in the dmesg, in logcat there is only:
05-12 03:22:54.430 1154-1154/? D/Vold: Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
05-12 03:22:56.380 1486-1499/system_process D/MountService: got storage path: /mnt/sdcard description: USB storage primary: true removable: false emulated: false mtpReserve: 0 allowMassStorage: false maxFileSize: 0
05-12 03:22:56.380 1486-1499/system_process D/MountService: addVolumeLocked() StorageVolume [mStorageId=0 mPath=/mnt/sdcard mDescriptionId=17040615 mPrimary=true mRemovable=false mEmulated=false mMtpReserveSpace=0 mAllowMassStorage=false mMaxFileSize=0 mOwner=null]
05-12 03:22:56.390 1486-1522/system_process D/MountService: volume state changed for /mnt/sdcard (null -> removed)
05-12 03:22:56.400 1486-1522/system_process I/PackageManager: No secure containers on sdcard
05-12 03:22:58.180 1738-1957/android.process.media W/MediaScanner: Error opening directory '/mnt/sdcard/', skipping: Permission denied.
Just updated to Emulator 26.0.3 and still happening as above.
ma...@gmail.com
Hello, I have the same problem. Anyone find a solution?
pa...@gmail.com
Unfortunately I had to go back to Android Studio 2.2 as I have to work with a SD card.
th...@gmail.com
Re: #8 and #9, please refrain from "me too" comments. Each new comment sends out an email to everyone who is subscribed to the defect (and my sincere apologies to everyone for the email that this comment generated!). Please just star the defect to let the devs know that you're interested in it and add a comment only if you have additional debugging/troubleshooting information to add.
sh...@gmail.com
Having same issue with API 15 emulator
br...@nealis.com
Have this problem with API 17 - but running with classic engine from command line works for me:
LD_PRELOAD='/usr/$LIB/libstdc++.so.6' ./emulator @Nexus_S_API_17 -verbose -engine classic
LD_PRELOAD='/usr/$LIB/libstdc++.so.6' ./emulator @Nexus_S_API_17 -verbose -engine classic
pp...@gmail.com
Thank you #12! I can confirm that emulators as far back as API 15 (my earliest supported API) work with that advice.
Specifically, if you need sdcard in the older APIs,
1- I have to use Android Studio (v3.1.4 for me) to create the AVD,
2- then I must boot it once via Android Studio or I will get an error about failed phone encryption, but the sdcard won't be mounted
3- then I may boot the standalone emulator from the command line using the classic engine. I did not need to do the LD_PRELOAD though (Ubuntu 18.04LTS, for me)
My command looked like this and returned this emulator version, working correctly with sdcard access:
$ANDROID_SDK_HOME/emulator/emulator @Nexus_4_API_15 -verbose -engine classic
emulator: Android emulator version 27.3.9.0 (build_id 4899998) (CL:e7b1c928a596dd490b990f4532055950f1409e49)
Specifically, if you need sdcard in the older APIs,
1- I have to use Android Studio (v3.1.4 for me) to create the AVD,
2- then I must boot it once via Android Studio or I will get an error about failed phone encryption, but the sdcard won't be mounted
3- then I may boot the standalone emulator from the command line using the classic engine. I did not need to do the LD_PRELOAD though (Ubuntu 18.04LTS, for me)
My command looked like this and returned this emulator version, working correctly with sdcard access:
$ANDROID_SDK_HOME/emulator/emulator @Nexus_4_API_15 -verbose -engine classic
emulator: Android emulator version 27.3.9.0 (build_id 4899998) (CL:e7b1c928a596dd490b990f4532055950f1409e49)
so...@gmail.com
Hi, I can't reproduce this with the canary emulator 29.2.3 with the latest revision of the API 16 x86 Google APIs image.
si...@hotmail.com
Thanks for checking, and that's good news - this was logged (and my comment with testing results added) prior to all the work on the emulators, and I've noticed several things in the area that did not work in the past are working now, so it's possible this was resolved as well. I'll re-check in a bit and post back results as my app supports API15+ at the moment and I need these to work. Cheers
bc...@gmail.com
I can no longer reproduce this with Android emulator version 29.2.3.0 (build_id 5916265) (CL:N/A) - on the API16 x86 non-Google APIs image
However, the API15 non-Google APIs image fails to boot completely
They may not have high enough user numbers to resurrect the emulation there but we do still have around a thousand users on API15 and below
So I think the original issue might be solved, but for very old APIs the images might need to be rebuilt by google to work on newer emulators? Or at least the documentation should be altered to note that no emulation is possible below API16?
However, the API15 non-Google APIs image fails to boot completely
They may not have high enough user numbers to resurrect the emulation there but we do still have around a thousand users on API15 and below
So I think the original issue might be solved, but for very old APIs the images might need to be rebuilt by google to work on newer emulators? Or at least the documentation should be altered to note that no emulation is possible below API16?
ch...@gmail.com
For API 15, the issue is that guest rendering is not supported anymore. However, in recent emulator canaries, we've forced those lower API levels to run with host side rendering.
ms...@gmail.com
Wow! With the current (as of today - Android qemu version 29.2.7.0 (build_id 5980645) (CL:N/A)) canary I can confirm API15 is working in Travis CI at least (ubuntu bionic linux image), with sdcard, even with hardware acceleration! Fantastic - we have every single play-store-accepted API except API26 (some orchestrator error, seems unrelated to emulator binary) working in CI now.
https://travis-ci.com/mikehardy/Anki-Android/jobs/253635737
The improvements in the emulator over the last year have been very helpful, thanks to the team.
The improvements in the emulator over the last year have been very helpful, thanks to the team.
bh...@gmail.com
Why is it North American companies are so obtuse in evaluating the need of people in other countries outside the United States. Patronizing users as if they do not know how to use a tool is wrong. This is equivalent to removing knifes from restaurants because some guest might attach another guest.
The bedrock of liberty is based on individuals deciding what to do. Google is not my parent, president, police or vigilante to take away a good feature, just because someone might not use it properly. It is very arrogant on Google to limit the users just because Google "knows best". Why not go to the extreme eradicating all phones and progress because these instruments might be used to plan something evil.
I have used recording abiding the law. The United States is not the world and its laws neither universal, in fact US laws break the law in many countries.
Please put back the recording capabilities in Pie.
The bedrock of liberty is based on individuals deciding what to do. Google is not my parent, president, police or vigilante to take away a good feature, just because someone might not use it properly. It is very arrogant on Google to limit the users just because Google "knows best". Why not go to the extreme eradicating all phones and progress because these instruments might be used to plan something evil.
I have used recording abiding the law. The United States is not the world and its laws neither universal, in fact US laws break the law in many countries.
Please put back the recording capabilities in Pie.
gl...@gmail.com
Hi Google! Call recording and even video are legal in my country if they concern my person. After upgrading to Android 9, the last opportunity to record my personal talks was blocked. Bring back the record. Or should I give up on Google phones?
ah...@gmail.com
Hi google we deal with many client and its useful tool to us
mu...@gmail.com
Google!!!, we need an official anounce!!!
an...@gmail.com
Day by Day Google Android doing bothering to valuable customer, call recording feature stop, can't provide video call by VoLTE (user video call by apps only), user can't delete multiple messages in single tread this problem exist from last Android 7.0 (Nougat) Android 8.0 - 8.1 (Oreo) and now going Android 9.0 (Pie) also.
ra...@gmail.com
Hi google let allowed call Recording its very much useful
le...@gmail.com
What can i say EVERYONE know that goverment is listening or beeing recorded. In my country its legal so why ban everyone from call recording when some country have banned it??
"I my country its legal" yes or no and owner is suid if something isnt!!!
"I my country its legal" yes or no and owner is suid if something isnt!!!
po...@gmail.com
Federal law permits one party consent unless I'm misinformed. Regardless I'd love to see some new development for people in lines of work that need recording capabilities, for conducting interviews for example. As a newspaper reporter, 90 percent of my interviews are over the phone and I take a lot of interviews over my cellphone while I'm on the go. I do not recommend a tone sounding every 15 seconds (because that would be extremely annoying) but perhaps something on initial start up to alert the other party that they are being recorded.
ch...@gmail.com
You are misinformed. As long as you are a party in the phone call (i.e. not an unknown spying on the call) you are legally allowed to record with only your own consent.
"Federal law permits recording telephone calls and in-person conversations with the consent of at least one of the parties. See 18 U.S.C. 2511(2)(d). This is called a "one-party consent" law. Under a one-party consent law, you can record a phone call or conversation so long as you are a party to the conversation."
"Federal law permits recording telephone calls and in-person conversations with the consent of at least one of the parties. See 18 U.S.C. 2511(2)(d). This is called a "one-party consent" law. Under a one-party consent law, you can record a phone call or conversation so long as you are a party to the conversation."
st...@gmail.com
Victim voices clear but victim 2 persons voice not clear
fo...@gmail.com
I'm downgrading to Android 6 on my Nexus 6P just to get this feature back..thanks google for messing with my life yet again, now I have to run a fairly insecure OS to get back functionality that never should have been removed in the first place? You are helping the criminals with this action not stopping them!
mp...@gmail.com
This is like disabling the camera because one might use it for purposes that are not legal. What a crazy move on the part of Google. Why not disable the phone functionality as well. I am sure many a crook has planned their next criminal act using an Android phone.
sa...@gmail.com
nice
ve...@gmail.com
Voice call not clear
10...@gmail.com
We all need voice recording to work to keep us safe. Looks like a move on to another device even Apple being considered if Google wants to control our lives with them deactivating the valued feature on Android phones. Please bring the features back.
sp...@gmail.com
Call is not recording.......pizza enable it...so call recording is not working........
ha...@gmail.com
Please unblock my audio callrecoding
lu...@gmail.com
lu...@gmail.com
sa...@gmail.com
Call recording not working plz help me vivo x.9
mj...@gmail.com
Kindly activate the call recording services,it's v v imp.
si...@gmail.com
Not call recording
pa...@gmail.com
Not all call recording properly
Description
- Below Android 6: Worked fine on phones that supported VOICE_CALL
- With Android 6: Getting "Thread requires android.permission.CAPTURE_AUDIO_OUTPUT" from AudioFlinger
- VOICE_CALL audio source was tied to RECORD_AUDIO permission. AudioFlinger should not throw permission error as there is no notification or documentation about this change
- This behavior can be observed on all Android 6 devices
Issue seem to be same with
VOICE_UPLINK
VOICE_DOWNLINK
But, does not affect
VOICE_COMMUNICATION
VOICE_RECOGNITION
Here is the log
4-12 22:46:25.855 5651-5651/? I/InCall: InCallUISystemDB - getSuppService: 0
04-12 22:46:25.855 5651-5651/? I/InCall: InCallUISystemDB - getTtySetting, setting: 0
04-12 22:46:25.865 550-550/CallRecorderService: mRecorder starting
04-12 22:46:25.865 5651-5651/? I/InCall: SecVoiceCallCardFragment - - needToShowMenu
04-12 22:46:25.865 5651-5651/? I/InCall: SecVoiceCallCardFragment - - showMenu: false
04-12 22:46:25.865 3158-15622/? I/APM::AudioPolicyManager: getInputForAttr() source 4, samplingRate 8000, format 1, channelMask 10,session 838, flags 0
04-12 22:46:25.865 3158-15622/? V/audio_hw_primary: adev_open_input_stream: request sample_rate:8000
04-12 22:46:25.865 3158-15622/? V/audio_hw_primary: in->requested_rate:8000, pcm_config_in.rate:48000 in->config.channels=2
04-12 22:46:25.865 3158-15622/? D/audio_hw_primary: adev_open_input_stream: call echoReference_init(12)
04-12 22:46:25.875 3158-15622/? V/echo_reference_processing: echoReference_init +
04-12 22:46:25.875 3158-15622/? I/audio_hw_primary: adev_open_input_stream: input is null, set new input stream
04-12 22:46:25.875 3158-5815/? I/AudioFlinger: AudioFlinger's thread 0xe9b80000 ready to run
04-12 22:46:25.885 3158-15622/? W/ServiceManager: Permission failure: android.permission.CAPTURE_AUDIO_OUTPUT from uid=10209 pid=550
04-12 22:46:25.885 3158-15622/? D/PermissionCache: checking android.permission.CAPTURE_AUDIO_OUTPUT for uid=10209 => denied (666 us)
[ 04-12 22:46:25.895 3158:15622 E/ ]
Request requires android.permission.CAPTURE_AUDIO_OUTPUT
04-12 22:46:25.895 3158-15622/? E/AudioPolicyIntefaceImpl: getInputForAttr() permission denied: capture not allowed
04-12 22:46:25.895 3158-15622/? V/audio_hw_primary: stop_voice_note_recording
04-12 22:46:25.895 3158-15622/? E/audio_hw_primary: adev_close_input_stream, set jack_in to null
04-12 22:46:25.905 3158-15622/? E/AudioRecord: Could not get audio input for record source 4, sample rate 8000, format 1, channel mask 0x10, session 838, flags 0
04-12 22:46:25.905 3158-15622/? E/StagefrightRecorder: audio source is not initialized
04-12 22:46:25.905 550-550/MediaRecorder: start failed: -2147483648