Database Develop

Barcode Scanner Force close when scan complete

Hi,
I have version 3.51 of the Barcode Scanner (zxing). I used it in the past and it worked but now when the qr code scan is complete, I get force close dialog.

This has been happening to me also since I rooted my wildfire...idk what's wrong with it
Till then using google goggles for qr codes....
Sent from my HTC Wildfire using Tapatalk

Yes it force closes on Wildfire, its old news. It has something to do with the latest update.
Be smart and just download the earlier version?
http://zxing.googlecode.com/files/BarcodeScanner3.4.apk

I thought it was a problem that had no connection with the app being the last version. 3.4 works. Thanks!

got the same problem since i'm on openfire ..

Lol..never tried to figure out he problem thanks..
Sent from my HTC Wildfire using Tapatalk

Barcode Scanner released a new version which fixes FCs on QVGA devices (cf. changelog)
Just update to latest

Sympnotic said:
Barcode Scanner released a new version which fixes FCs on QVGA devices (cf. changelog)
Just update to latest
Click to expand...
Click to collapse
Why bother? Barcode scanner will always be barcode scanner. It is not going to scan new kind of codes, or become any faster... not yet at least. So it doesn't matter which version you have, barcode scanner is the same.

Infinitum said:
Why bother? Barcode scanner will always be barcode scanner. It is not going to scan new kind of codes, or become any faster... not yet at least. So it doesn't matter which version you have, barcode scanner is the same.
Click to expand...
Click to collapse
Actually I was only saying this because it's on the market, which is a lot simplier than grabbing an old apk, putting it on your SD, then installing it...
But I guess something called "bugfixes" and "code enhancements" is both two good reasons to keep our apps up to date.

[Q] Built a custom AOSP ROM, sound + video does not work

Hi All,
I wanted to learn how to build an AOSP ROM for my Droid Incredible (original version), and I was finally able to get a working build today (i've been at it for more than a month on and off when I have time).
I downloaded gingerbread-release and used the CM overlay to get the vendor-specific stuff. The proprietary files were pulled from my working OMGB phone (which I understand borrows a lot from cyanogen; well-- the kernel at least).
My problem is that (1) I can't get any audio to play, (2) any time I try to play a video (like Youtube) I get a force close, and (3) the camera wont work.
I'm pretty sure (3) is a totally different problem, as I've seen lots of ROMs where the camera won't work.
Does anyone have any point that I could start on this? I've posted my logcat here: pastebin.com/GPqpD8N3
(sorry-- I'm not allowed to post links yet.)
I googled it but I'm having trouble finding anything pertinent.
Thanks in advance for any assistance you anyone can provide!!
EDIT: By the way, since this post I have changed my setup. All of my proprietary modules are from the CM nightly build now, instead of having modules from OMGB and and overlay from CM. I did this to make it more consistent in case I run in to any more problems.

Sorry -- additional detail that I meant to add in the post (but it won't let me re-edit for 5 minutes):
The bottom of the log shows me trying to play a song in the music player. From what I can tell, /system/bin/mediaserver is crashing and performing a stack dump; however I don't know why or how I can fix it.
It will not play any ringtones either, but the DTMF tones *do* sound when you press on the digits, and the phone/speakerphone work fine as well.

I just figured it out myself... in the logcat there is the line:
frameworks/base/media/libstagefright/omx/OMXMaster.cpp:90 err != OMX_ErrorNoMore
if you go to that file, in line 90:
CHECK_EQ(err, OMX_ErrorNoMore);
I just commented it out and sound works fine.
Now if I can get the camera working... any ideas?

Hmm I know the bugglas beast nightly's had the camera issue.
Sent from my ADR6300 using XDA App

Thanks, @Kiboe for the reply. I found the fix last night (right after I posted ) on xda-developers through Google Groups.
I implemented @dferreira's suggestion, and it compiled just fine. Now I have a working camera, but video still isn't working. (Also accelerometer isn't working, but I believe I have already found the answer for that).

[Update]Proximity Fix for Kexec Kernels! - All Sensors

First things first, I'd like to wish you all hello, as this is my first post here and to XDA in general.
That being said, after getting much out of XDA over the years I figured I would try to give something back while experimenting with android!
I give you..
Droid 3 Custom Sensors Module
This enables/fixes our proximity sensor on hashcode's awesome kexec kernel so the phone screen blanks during calls!
The issue is with the sensors.solana.so proprietary library that comes with our phones from motorola.
So I compiled for us a new sensors.solana.so to use which is compatible with Kexec kernels.
Note: This library only controls accerometer sensor, light/prox sensor and orientation/magnet sensor so theoretically it should work the same, just with proximity working. But without more use I can't be sure.
Also in theory this should work for any flavor of Kexec releases, but I can only confirm cm10 currently...
Update[12/13/12]:
-Akm module is now working (Magnetic Field sensor / compass)
-Why is this useful?
Google maps should work better in terms of orientation
Compass apps should work now, along with any others that use rotation vector
-This required a driver edit to get it pointing in the right direction, so v2 includes newest hashcode kernel with the edit. i sent the code to hashcode, so hopefully if he incorporates these changes then this will no longer be needed.
Installation:
1. Download Custom-SolanaModule-v2[Kexec].zip
2. Install it like any other zip in ss3
Removal:
2. Download Stock-SolanaModule [Kexec].zip
2. Install it like any other zip in ss3
More Notes:
Attached also is the source code I used. I cannot claim writing most of it, as its more of a collaboration of various files that I found online for our sensors with a couple various tweaks.
Edit[12/13/2012] For anyone looking to implement this, just unzip v2 source code into root directory of your repo, files should go where needed.
Obviously a big shoutout/thanks to Hashcode/dhacker/jonpry and everyone else that got our D3's to the place they are now. This is just one more step in the right direction hopefully.

Thanks dudeeeee!! Someone should pm this to hash! It's great!
Enviado desde mi DROID3 usando Tapatalk 2

Confirmed. Good work.
Sent from my XT862 using xda app-developers app

Nice, one step closer.
Who twittered Hash?

I tweetered.

Thank you Jarveson!
I'll get this into new builds w/ a credit to you for getting this together.

Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Also, Thanks Hash! I forgot to say that it would be awesome if you were able to incorporate this in your new builds, it was really late/early when I typed that up initially

jarveson said:
Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Click to expand...
Click to collapse
Orientation is already working not sure about magnet

DoubleYouPee said:
Orientation is already working not sure about magnet
Click to expand...
Click to collapse
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.

hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
djbolden said:
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.
Click to expand...
Click to collapse
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch

jarveson said:
hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch
Click to expand...
Click to collapse
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.

DoubleYouPee said:
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.
Click to expand...
Click to collapse
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?

jarveson said:
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?
Click to expand...
Click to collapse
Ye sometimes when I wake the screen it's in landscape. Or other way around when I open the keyboard it doesn't wake. If I then press a key it wakes but is still in portrait.
Btw, I also need to reapply auto brightness occasionally because it doesn't stick to my custom light sensor settings. But that might be some bug because the sensor itself works fine
Oh, thanks for the work btw. Only camera "sensor" left now

Ok, i can see the magnet works now in GPS toolbox, thanks!
I should've mentioned that I'm not using auto-rotate - so the problem I described is probably not related to these sensors.
It seems that sometimes, it doesn't recoqnize that the QWERTY keyboard got closed or got opened, and therefore it sticks the either landscape or portrait.
This doesn't happen in GB, so it's not a hardware fault on the slide mechanism.

What is libsensors? and do I need to install libsensors to use your custom proximity sensor?

Own Demon said:
What is libsensors? and do I need to install libsensors to use your custom proximity sensor?
Click to expand...
Click to collapse
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore

jarveson said:
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore
Click to expand...
Click to collapse
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).

Own Demon said:
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).
Click to expand...
Click to collapse
Coming after the 1/23 nightlies or do we know when?

Well actually i think nxt build well include this.
Sent from my XT862 using xda app-developers app

[Q] QR code scanner in 4.2.2 rom

does any one have a working qr code scanner on p970 4.2.2 roms ? i tried almost every app from market it just focuses on the barcode and does nothing. also face unlock does not work ! any reply would be appreciated.

gaurishmhatre said:
does any one have a working qr code scanner on p970 4.2.2 roms ? i tried almost every app from market it just focuses on the barcode and does nothing. also face unlock does not work ! any reply would be appreciated.
Click to expand...
Click to collapse
A) What ROM are you running?
B) Face Unlock is buggy in my experience.
C) Are there any other apps accessing the camera while your QR Code Scanner is running?

OptimusDan said:
A) What ROM are you running?
B) Face Unlock is buggy in my experience.
C) Are there any other apps accessing the camera while your QR Code Scanner is running?
Click to expand...
Click to collapse
A} i am currently running avatar rom 2.7b
B} Facelock is not much of a issue but what i really need the most is qr scanner working
C} no other other app is accessing camera.
i also have a problem in gps. it scans satellites quickly atleast 5 within seconds but never fixes i had this problem on all 4.2.2 jellybean roms

gaurishmhatre said:
A} i am currently running avatar rom 2.7b
B} Facelock is not much of a issue but what i really need the most is qr scanner working
C} no other other app is accessing camera.
i also have a problem in gps. it scans satellites quickly atleast 5 within seconds but never fixes i had this problem on all 4.2.2 jellybean roms
Click to expand...
Click to collapse
I must say I don't have any experience with Avatar but CM10.1 works great for me.
The Optimus Black doesn't have the best GPS out there but there are a couple of things you can do to help it... Pimp My ROM has some country specific settings that may help you can also look into some of the scripts.
Have you considered going back to a GB or ICS ROM?

gaurishmhatre said:
does any one have a working qr code scanner on p970 4.2.2 roms ? i tried almost every app from market it just focuses on the barcode and does nothing. also face unlock does not work ! any reply would be appreciated.
Click to expand...
Click to collapse
Same here. Using Mackay ROM and not a single QR scanner works. i've read somewhere it was a cm10 problem but i don't see many people talking about this, so i probably might be wrong. or not.
The cellphone itself can read a qr code, i mean, if i take a picture of it and tell the QR DROID to scan the picture, it works, BUT it seems not to be capable of do it "live", just poiting the camera to the code.
Gps working fine here w/ Mackay and no other app runing w/ camera while trying to scan a qr code.

ClarkPinheiro said:
Same here. Using Mackay ROM and not a single QR scanner works. i've read somewhere it was a cm10 problem but i don't see many people talking about this, so i probably might be wrong. or not.
The cellphone itself can read a qr code, i mean, if i take a picture of it and tell the QR DROID to scan the picture, it works, BUT it seems not to be capable of do it "live", just poiting the camera to the code.
Gps working fine here w/ Mackay and no other app runing w/ camera while trying to scan a qr code.
Click to expand...
Click to collapse
yea after taking a picture it works i wanted to check if i am only one facing problems of scanning it live.
also of gps my phones gets view of 5 to 6 satellites within a minute but never locks even after 10 mins. i have found no solution :crying:

[ROM][WIP][AOSP][4.4.4_r2] Google Edition for SGS4A (int'l) testing

This AOSP build by spegelius is rock solid and has been improving extremely fast in the last couple of weeks.
The only thing that needed some improvement is the back camera and the 0.96 dev build improved a lot.
Camera is responsive and just freezes a bit sometimes when it's focusing
Successfully scanned a document with Camscanner App
Instagram built-in camera loads but nothing happens when pressing the shutter, then crashes and restart is necessary
Instagram works OK when using the Google camera as default
Google Camera (the one you download) crashes when taking picture and restart is necessary
On Stock camera, moving to HDR mode worked fine but then freezes and crashes when going back to no HDR
On Stock camera, taking pictures works fine. Worked fine changing between flash modes (flash, auto, no flash)
Flashlight from Smart Tools app works fine
Spegelius, this is amazing. THANK YOU SO MUCH!!!!

Thanks for the report, I9295 camera is pain in the buttocks to understand, but getting there...

Hangout calls crashes probably due to front camera not working. Rebooted after switching to front but still no luck.
Going from front to back works OK.
Sent from my GT-I9295 using XDA Free mobile app

I've installed latest 0.9.7 this afternoon and so far everything seems to run smooth (including camera).

found a little bug(?). In this ROM the carrier names (at least for Germany) do not seem to be included. I just see the carrier codes (26201 for T-Mobile D, 26202 for Vodafone D, ... etc), it's probably just a little text file that needs to be updated to fix this?

jot82 said:
found a little bug(?). In this ROM the carrier names (at least for Germany) do not seem to be included. I just see the carrier codes (26201 for T-Mobile D, 26202 for Vodafone D, ... etc), it's probably just a little text file that needs to be updated to fix this?
Click to expand...
Click to collapse
Network name now appearing correctly after updating to 0.9.9-od1, thanks for fixing