Closed
Bug 1212078
Opened 10 years ago
Closed 10 years ago
No sound from a freshly flashed Flame
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ola, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20151001044230
Steps to reproduce:
Built, compiled, and flashed Firefox OS v2.5 to a Flame device (master branch).
The latest commit in my B2G git history is from 22nd Sep. git pull tells me "Already up-to-date."
When building I use the following options (in .userconfig):
PRODUCTION=1
VARIANT=userdebug
export NOFTU=1
export B2G_DEBUG=0
I also build with external Gecko, namely mozilla-central rev 265900.
Tried to flash two different Flame devices, both are unable to play sounds from any app. Everything else works fine, such as voice playback and vibration.
Actual results:
No sound from any app, including Music player, ringtone preview, tap sounds, etc.
There have been similar issues before, such as:
https://bugzilla.mozilla.org/show_bug.cgi?id=1091788
https://bugzilla.mozilla.org/show_bug.cgi?id=1091659
But I do not see any clear explanations or solutions.
Expected results:
Sound waves are expected.
Comment 2•10 years ago
|
||
I was unable to reproduce this issue using the Flame 2.5. Sounds are being played successfully. I attempted to Full flash (After rebasing) as well as shallow flashing. Reporter, which build were you using?
In the mean time I am leaving Qawanted tag on for others to attempt to find a proper STR if it does still exist on current builds.
Environmental Variables:
Device: Flame 2.5
BuildID: 20151006030203
Gaia: 60cdaa3d3424db3432dc903e7f9c6c8fa099c06d
Gecko: 3edc8d4a1e198314f5d7ebd2967b85842beef602
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ola)
Updated•10 years ago
|
Flags: needinfo?(jmercado)
Comment 3•10 years ago
|
||
Reporter, could you go into Settings > Sound, and check whether you have correct settings for different types of sounds?
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Yes, I have checked the sound settings, and they looks fine.
This is the output from the check_versions.py script (is that what you need?):
Build ID 20151004011424
Gaia Revision de66a9ce917bcf606216ac581c3b98bda8750545
Gaia Date 2015-10-03 12:05:46
Gecko Revision n/a
Gecko Version 44.0a1
Device Name flame
Firmware(Release) 4.3
Firmware(Incremental) eng.ola.20150827.153212
Firmware Date tor 27 aug 2015 15:32:27 CEST
Bootloader L1TC000118D0
Flags: needinfo?(ola)
Comment 5•10 years ago
|
||
It's odd that you are showing no gecko revision. We don't have access to the build you made but were unable to reproduce on builds made by buildbot around the same time yours was created. Does this also occur if you are using any other builds?
Flags: needinfo?(ola)
I'm making a new build now. It will take some time, so I'll get back once it's done.
Just to be transparent about what I do:
In mozilla-central:
> hg pull -u
> rm -rf objdir-gecko
(I just realized I havn't removed this folder previously, perhaps that's the problem?)
In B2G:
> git pull
> ./repo sync
> rm -rf out
> ./build.sh
> ./flash.sh
Everything should be vanilla, except .userconfig:
PRODUCTION=1
VARIANT=userdebug
export NOFTU=1
# Gecko settings
export B2G_DIR=${B2G_DIR:-$(cd $(dirname $0); pwd)}
echo "B2G_DIR = ${B2G_DIR}"
export GECKO_PATH=${B2G_DIR}/mozilla-central
echo "GECKO_PATH = ${GECKO_PATH}"
export B2G_DEBUG=0
echo "B2G_DEBUG = ${B2G_DEBUG}"
export GECKO_OBJDIR=${GECKO_PATH}/objdir-gecko
if [[ "${B2G_DEBUG}" != "0" ]]; then
export GECKO_OBJDIR=${GECKO_OBJDIR}-debug
fi
if [[ "${GECKO_PATH/*mozilla-inbound*/mozilla-inbound}" == "mozilla-inbound" ]]; then
export GECKO_OBJDIR=${GECKO_OBJDIR}-m-i
fi
echo "GECKO_OBJDIR = ${GECKO_OBJDIR}"
# Gaia settings
export GAIA_PATH=${GAIA_PATH:-$(cd gaia; pwd)}
export CUSTOM_SETTINGS="${GAIA_PATH}/build/config/custom-settings.json"
cat > "${CUSTOM_SETTINGS}.new" <<EOF
{"devtools.debugger.remote-enabled": true}
EOF
if [[ -f ${CUSTOM_SETTINGS} ]] && cmp "${CUSTOM_SETTINGS}" "${CUSTOM_SETTINGS}.new" >& /dev/null; then
rm "${CUSTOM_SETTINGS}.new"
else
mv "${CUSTOM_SETTINGS}.new" "${CUSTOM_SETTINGS}"
fi
Now I have flashed the phone again with a newly built system. The problem is still there.
I did exactly as in post 6, except for 'hg pull -u' since I realized I had to do:
> ./mach mercurial-setup
The output from check_versions.py:
Build ID 20151008072501
Gaia Revision dd9fe1df3f15991e5f7400b8a72f5b7bd2ee695a
Gaia Date 2015-10-07 18:16:05
Gecko Revision n/a
Gecko Version 44.0a1
Device Name flame
Firmware(Release) 4.3
Firmware(Incremental) eng.ola.20151008.065337
Firmware Date tor 8 okt 2015 06:54:00 CEST
Bootloader L1TC000118D0
Can it be related to firmware?
Is there any more information I can give?
Flags: needinfo?(ola)
Comment 8•10 years ago
|
||
NI Naoki since we're unsure whether reporter's flashing the device correctly.
Flags: needinfo?(nhirata.bugzilla)
I think I have found the source of the problem now. I decided to redo everything from scratch.
Everything worked fine until the backup state early in the build state. Somewhere during that process I got the following:
c/security/cacerts/6adf0799.0
pull: /system/etc/security/cacerts/69105f4f.0 -> ../../../backup-flame/system/etc/security/cacerts/69105f4f.0
pull: /system/etc/security/cacerts/67495436.0 -> ../../../backup-flame/system/etc/security/cacerts/67495436.0
Pulling files from ../../../backup-flame
cat: ../../../backup-flame/system/build.prop: No such file or directory
Pulling "libalsa-intf.so"
cp: cannot stat ‘../../../backup-flame/system/lib/libalsa-intf.so’: No such file or directory
Failed to pull libalsa-intf.so. Giving up.
> Build failed! <
I would think that this mean that somehow this file was lost when this was done previously. Therefore it was also missing in every build I made from my previous build tree. I haven't had time to fix this and test a new build yet, but the problem seems obvious.
In the future, as a lesson from this case, perhaps one could consider to include an extra check in the build script to make sure all (important) external system files are there?
Actually the problem is that your pull is old.
You need to resync your branch.
https://github.com/mozilla-b2g/device-flame/tree/kitkat-v2 doesn't use that lib file.
Please use:
./config.sh flame-kk
./repo sync --force-sync
or reclone the B2G directory again from scratch and the ./config flame-kk
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(nhirata.bugzilla)
Resolution: --- → INVALID
Updated•10 years ago
|
Flags: needinfo?(jmercado)
You need to log in
before you can comment on or make changes to this bug.
Description
•