-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After May 8th build, Samsung S2 will not boot up (Terminated ALSA PLAYBACK device hifi) #299
Comments
Hard to say how that build was created... They're by no means official builds. I suspect that Gonk-GB broke. We're moving to Gonk-ICS, so I suggest you upgrade to that. |
whoops, not sure why I had the IP in my Makefile. These builds are from http://b2gbuilds.org/ so I'll shoot them an email. Thanks for the clues. |
is there an official nightly build for samsung elsewhere? |
Nope. We don't distribute images for devices at all currently. |
@kumar303 This happens when you use |
I had the same issue with my own Gingerbread-based build from scratch (though slightly different log output http://pastebin.mozilla.org/1640169) but I can confirm that running "make install-gecko-only" fixed it. Is the fix for this bug to start using ICS builds? If it is, should we remove the gingerbread instructions from the README? If not, I guess this needs fixing. |
I'm having the same issue building against ICS. For the record, the guys from b2gbuilds.org where building against GB. |
I had the same problem. As peregrino said, just flashing with |
I met the same problem |
A little more detail. During ./flash.sh gecko, this occurs: push: b2g/components/binary.manifest -> system/b2g/components/binary.manifest The device actually starts working while it is copying libxul.so, so I assume the problem is with one of the files that gets copied before that. |
Bug 937679 - Add fastxul.sh for fast XUL recompile & flash. r=mwu
Using the May 8th build from http://83.212.96.171/galaxy-s2/latest/ , my Samsung S2 will not boot up. It seems to be stuck in a loop about the audio driver maybe? This is the loop that logcat shows:
The text was updated successfully, but these errors were encountered: