Barcode scanner - T-Mobile LG G2x

OK I tried using barcode scanner to scan one of those fingerprint looking barcodes and would not work just kept aitofocusing. It did scan a regular barcode. Wondering if anyone else has this issue or maybe just a bad code
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.

tackleberry said:
OK I tried using barcode scanner to scan one of those fingerprint looking barcodes and would not work just kept aitofocusing. It did scan a regular barcode. Wondering if anyone else has this issue or maybe just a bad code
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.
Click to expand...
Click to collapse
what exactly were you trying to scan? you need to hold the phone still and fill the camera screen with the barcode.

crazythunder said:
what exactly were you trying to scan? you need to hold the phone still and fill the camera screen with the barcode.
Click to expand...
Click to collapse
I know how to use it. Just wondering if anyone else had issues on the g2x with it. Qc code I think is the right name for it.
It was a code on the side of a tacobell cup. It kept pinpointing it but then started over.
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.

Related

[Q] i9020a BLN

Anybody have this working on their phone yet?
tested on my i9020a and doesnt work either for me anyone?
Seems to work fine on mine.
slobba said:
Seems to work fine on mine.
Click to expand...
Click to collapse
thats odd i tested it using the free version and the BLN test didnt even work. Tried calling a few times and missing the call as well as texting my phone and leaving the message unread and still nothing. Wonder if this is the case with only the rogers/fido/telus/bell i9020as as some of us had to root via the i9023 CWM recovery.
Yeh, I got caught with the problems of flashing the i9020 CWM instead of the i9023 version but the BLN is working for me both with the free non-blinking test and pro blinking test.
The NSCollab ROM I'm using includes the latest Netarchy 1.3.0.3 CFS kernel. Maybe that's the reason it's working for me??
really thats interesting, the kernel i tested one was the 1.3.0.3 netarchy kernel i guess i'll have to test it using the paid version and see wat happens
edit: tested using the paid version and it seems like its the i9023 root method thats screwing things up a little.
imisky said:
really thats interesting, the kernel i tested one was the 1.3.0.3 netarchy kernel i guess i'll have to test it using the paid version and see wat happens
edit: tested using the paid version and it seems like its the i9023 root method thats screwing things up a little.
Click to expand...
Click to collapse
That's what I was kinda wondering about the i9023 recovery, I guess that is what is doing it. I have the paid version of BLN as well, and it didn't make any difference.
did a bit more testing and it seems that BLN does work, but only for SMS and not for missed called even with the LED notification on for missed called.
Took mine back to 2.3.3 stock, installed Netarchy latest 1.3.0.3 kernel and now I'm getting the same behaviour: BLN test doesn't work, LED notification on missed calls not working but LED notification on new email is working.
Might try flashing the NSCollab ROM again to see what happens.
Tried running fix permissions on the stock ROM but this didn't seem to fix BLN notifications.
Reflashed NSCollab ROM. Tested BLN and initially still not working but after a reboot it's all working properly again.
so it might just be a stock rom + BLN kernel issue has any of the kernel devs looked into this?
I tried it out a few hours ago on my 9020a with CM7 and the Trinity UV kernel and so far BLN free version works great, not that I have much use for it, never used it on my Galaxy s but will see.
I too am having issues with it working on calls. emails/txts it works without fail.
EDIT:seems i found the issue. its the good old BFS choose a kernel that doesn't use it and it works fine. Seems bfs doesnt really like the 9020a's.
themapleboy said:
I too am having issues with it working on calls. emails/txts it works without fail.
EDIT:seems i found the issue. its the good old BFS choose a kernel that doesn't use it and it works fine. Seems bfs doesnt really like the 9020a's.
Click to expand...
Click to collapse
im using it with netarchy 1.3.0.3 CFS so im not sure if the BFS is the sole cause of this
Hi,
I'm just wondering if anyone got BLN working on the Jame Bond kernel ?
I've read in that thread that it supports Voodoo and BLN and I'm using the Sabai dee kernel but BLN doesn't seem to work for me ?
To be honest, I'm not too sure how to run the test. I click on it and it says press the power button to test it, which I do, but then my screen just turns off and nothing happens....am I doing something wrong ?
I also brought the pro version, and tried calling myself and sending myself an email and nothing happened.
Any suggestions ?
Cheers in advance
I'm running SupeAosp 6.2 Rom and BLN works perfectly for with, this includes missed calls and notifications. The Kernel that I'm using is 2.6.35.12-SuperAosp-S-1400. Apparently the next upgrade is going to be compiled with the UV which I am planning to test out as soon as its released. Furthermore as a bandage solution people can use NoLED without any mods at all, I found the app quite useful as I was not experienced enough to recompile with BLN included.
I forgot to mention, I am using an i9020A.
Chibsz said:
Hi,
I'm just wondering if anyone got BLN working on the Jame Bond kernel ?
I've read in that thread that it supports Voodoo and BLN and I'm using the Sabai dee kernel but BLN doesn't seem to work for me ?
To be honest, I'm not too sure how to run the test. I click on it and it says press the power button to test it, which I do, but then my screen just turns off and nothing happens....am I doing something wrong ?
I also brought the pro version, and tried calling myself and sending myself an email and nothing happened.
Any suggestions ?
Cheers in advance
Click to expand...
Click to collapse
first of all make sure all your settings are correct in the bln app...
bln works for the 9020a, but I forget if the missed call works or not...everything else seems to. with that being said, the issues with stock and the missed call not working will be sorted shortly...when the 9023 gets working...its not the 9023 recovery causing the problem

[Q] g2x wont run any oc/uv kernels

I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!
facadewithin said:
I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!
Click to expand...
Click to collapse
Tom's...... Lol
Caucasian.... Lmao
More info...what rom you got?what kernel?what you trying to uv by?
G2X
facadewithin said:
I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!
Click to expand...
Click to collapse
umm just turn in your g2x to someone that is qualified to use it.
What is a Caucasian kernel?
That ladies and gentlemen, is signature worthy.
Edit: Forgot to even answer your question amidst all this racial kernel profiling. Your G2x can't handle the OC/UV kernel, nothing you can do about it.
dligon said:
umm just turn in your g2x to someone that is qualified to use it.
Click to expand...
Click to collapse
It's not that he's not qualified. A known issue is that some of the phone's can't support some of the features of other kernels so the phones won't boot. I started a thread about this and Faux chimed in affirming what I thought. It's a fault in the chip. Some can OC/UV, some can't.
Thanks hiko I thought I read something about that but what I don't get now is I flashed the Trinity kernel nd it sees the UV 1.1 in set CPU lol . Ill have to do more testing. As for the Caucasian kernel I blame racist correct lol
Sent from my LG-P999 using XDA App
hiko36 said:
It's not that he's not qualified. A known issue is that some of the phone's can't support some of the features of other kernels so the phones won't boot. I started a thread about this and Faux chimed in affirming what I thought. It's a fault in the chip. Some can OC/UV, some can't.
Click to expand...
Click to collapse
Yup. I have this problem. My broken G2x can run custom kernels on Stock. But my replacement G2x can't even get past the boot screen after flashing one. I can't run EB Froyo, and I can't flash faux's kernel unless it's on a Gingerbread ROM. It's pretty lame.
Sent from my LG-P999 using XDA App
darbear5610 said:
Yup. I have this problem. My broken G2x can run custom kernels on Stock. But my replacement G2x can't even get past the boot screen after flashing one. I can't run EB Froyo, and I can't flash faux's kernel unless it's on a Gingerbread ROM. It's pretty lame.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
yeah i wonder if getting another one would be any better though. im sure if i complain enough i could get a bvetter one, although the screen bleed on mine is actually pretty low compared to what ive seen so i might just hang on to it not sure
facadewithin said:
yeah i wonder if getting another one would be any better though. im sure if i complain enough i could get a bvetter one, although the screen bleed on mine is actually pretty low compared to what ive seen so i might just hang on to it not sure
Click to expand...
Click to collapse
If you get a replacement, nothing says you have to keep it. Feel free to send that one back.
Sent from my HTC Glacier
Dear OP. Wish I could help you. I do want to thank you for the laugh. Nothing personal. The typos made me spit out my coffee. It's been a long morning already, so I appreciate humor where I can find it.
As a couple have already said, not all phones are created equal. One of my phones would not OC and UV at the same time. I was able to hit 1300 stable on mine, but my wife, which has an identical setup, had issues at 1100. Faux released an overclock kernel without the undervolting. Have you tried that?
jcbofkc said:
Dear OP. Wish I could help you. I do want to thank you for the laugh. Nothing personal. The typos made me spit out my coffee. It's been a long morning already, so I appreciate humor where I can find it.
As a couple have already said, not all phones are created equal. One of my phones would not OC and UV at the same time. I was able to hit 1300 stable on mine, but my wife, which has an identical setup, had issues at 1100. Faux released an overclock kernel without the undervolting. Have you tried that?
Click to expand...
Click to collapse
I have not as the overclocking was not as big of an issue as undervolting was for me. I cant get a single of fauxs kernels to run etx/GB/FR thats does oc/uv but the stock one does it just fine thats goes 1.0sv/1.2oc. the whole reason why i am confused though is i flashed morfics trinity kernel thats oc/uv at the same rate 1.1uv/1.5oc and it loads perfectly fine on my phone. Setcpu sees the standard at 1.1ghz max on autodetect, howeer i have not tried overclocking to anything more than that as i do not have any experience with making the textfile for setcpu to overclock it manually. im going to work on this soon but im hoping someones already made and posted this elsewhere on xda =D
PS: im on a computer this time and ill say this is better than my blackberry who decided to autocorrect "heterosexual" in place of "hey" everytime i tried talking to one of my friends but glad its good for laughs lol
I've consistently gotten Morfic to work as well. Faux said that Morfic hasn't released his source so he can't compare notes and see what's causing the issue.
hiko36 said:
I've consistently gotten Morfic to work as well. Faux said that Morfic hasn't released his source so he can't compare notes and see what's causing the issue.
Click to expand...
Click to collapse
i hope he does soon as i would love to try fauxs kernel as i hear more about it than morfics. morfics for now works fanfriggintastic for me though. m g2x ocs to 1400 without any problems at all on morfics however has some stability issues randomly at 1500 and i undervolt it always under 1.1 by 75 and runs perfect. battery life is currently at 60% still after 30hrs of use even after phone calls texts and internet usage. no games or heavy downloads yet though. <3uv and juicedefender

Netarchy vs Matr1x

I did some searching and couldn't find a thread that compared these two kernels, so I hope there isn't one out there...
I've been using Netarchy CFS 1.3.9 (and 1.3.8), which has worked extermely well for me. It works well with over/under clocking, undervolting, BLN, voodoo, etc.
BUT, I often see that mathkid's Matr1x kernel is also getting a lot of positive reviews and feedback. So I was wondering if anyone has tried both and has any useful comments about each of them compared (things like performace, battery life - you know, the usual )
Thanks.
+1 for netarchy
Lol I knew you would say that pat....
Honestly your gonna all different answers for everyone. I would suggest you flash one to start, give to 2-4 days on your phone and see how you like it. Check battery life, responsiveness, speed, etc etc. Then flash the next kernel and do the same thing. It takes 10 seconds to flash and you get first hand experience with both as opposed to taking someones own experience which may not be the same as yours
infernosoft said:
I did some searching and couldn't find a thread that compared these two kernels, so I hope there isn't one out there...
I've been using Netarchy CFS 1.3.9 (and 1.3.8), which has worked extermely well for me. It works well with over/under clocking, undervolting, BLN, voodoo, etc.
Thanks.
Click to expand...
Click to collapse
You will get a lot of different replies because what works for one does not work for the other .. All kinds of roms are used, different model phones and even the same models will not behave the same .. But since you are so satisfied with Netarchy maybe you should remember this : If it is not broken , do not try to fix it !
really, youll have to try them out yourself. every phone is different, and reacts differently to each kernel. i only throw in that you should try trinity also, my phone likes it the best.
for me...trnity and matrix are the best...
netarchy I had got many reboot...with Oc or UV...
Matrix becasue he keeps FPS cap on
without cap 3d apps render slow
demo23019 said:
Matrix becasue he has FPS cap still
Click to expand...
Click to collapse
Sorry, but what exactly does this mean?

Freeze issue on Imnuts' 1/15 kernel

I'm having an annoying issue with my Charge. Whenever I try to record with the Camera the phone just freezes and reboots after about 10 seconds. Yes I'm undervolted, which is what I'm suspecting as the issue but I went into Voltage Control and set the voltages back to 0 and to no avail, it still just froze and rebooted. I tried overclocking to 1.2Ghz without undervolting that clock speed at all(1GHz and below were still all undervolted) and it still just froze and rebooted.
The weird thing is this happens on the stock undervolt settings that the kernel comes with. I'm going to assume Imnuts' just didn't have the time to test all the apps individually for stability issues when implementing his undervolt script. I know it's an issue with the kernel(almost positive it's from the undervolting itself because i had stability issues exactly like this back on EE4 when i would undervolt) because if I reboot and flash imoseyons 4.0.0 kernel recording is fixed.
edit: I just tried removing my Voltage Control boot settings so there shouldn't be any undervolting going on(aside from the stock undervolt script thats included with the kernel) and it still just freezes and reboots. I'm guessing it's either the undervolt script or the kernel itself. Anyone else have this issue? If so how'd you fix it? Thanks in advance.
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
mromblad said:
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
Click to expand...
Click to collapse
How long did you let it record? and was it on 1280/720? It usually freezes on me after about 10-20 seconds
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
adrenaline_rush said:
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
Click to expand...
Click to collapse
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Mine did the same thing and I am just using the kernel and the new eclipse
Sent from my SCH-I510 using xda premium
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Also getting freeze-up when trying to record HD vid.
Running Tweakstock 1.1 and PBJ 0115
edit: *UPDATE* - I just flashed Imoseyon's 4.0.0 kernel to test, and HD recording worked flawlessly. So it does seem to be the kernel which is causing the issue (in my case at least). Can anybody tell me how to pull a logcat so I can send it over to imnuts?
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
Where did you find the kernel? Everything works great except the video.
Does anyone know of a stock, rooted version?
Sent from my SCH-I510 using xda premium
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
I believe it's an issue with Imnuts' 1/15 kernel, not the ROM.
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
See anyone running Imos kernel doesn't have the issue so I don't believe that Eclipse is the problem, although it is still possible.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
Yeah I remember back when Gummy2.0 was released I had that issue. I know it's not the same thing though because whenever I would record it would give me an error message like "This SD card does not support HD video recording" or something like that and it would just close the camera app, it wouldnt just freeze and reboot.
shrike1978 said:
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
Click to expand...
Click to collapse
I'm positive it's not a problem with the SD card. I'm on Tweakstock so for now it's to be assumed that the kernel is the problem since cujo6801 already tested Eclipse with Imos kernel and had no problem, but adrenaline_rush tested Eclipse with Imnuts' kernel and it froze/rebooted. Pretty sure it's a kernel issue at this point.
jimc5423 said:
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Click to expand...
Click to collapse
Try your actual Camera and attempt to record video @ 1280/720, then tell me if it reboots.
I got the freeze and reboot every time with Eclipse and PBJ at 720p. Flashed Tweakstock with PBJ and it worked. Then tried Eclipse with the ep4d kernel and that worked too. I thought it might be the camera so I copied the one from from Tweakstock into Eclipse and 720p recording worked fine undervolted and oc'd to 1200.
Edit: Tried it again since reflashing updated Eclipse and it locked at 10 seconds. Guess I was lucky last time. Shot multiple 45 second plus videos ok.
Sent from my SCH-I510 using XDA App
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
kvswim said:
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Same config and instant, several attempts.
benb1974 said:
Same config and instant, several attempts.
Click to expand...
Click to collapse
Tweastock with PBJ freezes and reboots on mine too. Never froze on Tweakstock with included kernel
Checked the comments on Imnuts' kernel over at RootzWiki and i can confirm it's a problem with the kernel, in addition to that the HDMI port doesnt seem to work.
I have been getting froze screens and 1 reboot also, since running imnuts kernel. I thought it was maybe the ROM but doing a little research IM finding the kernel has an issue. I didn't try the camera with imnuts kernel but I've flashed imo 4.0 kernel and the recording does work w/o force closing on me.
Sent from my SCH-I510 using XDA App
Also be careful overclocking on PBJ, I set it to 1600 max on SetCPU, and after a few moments it froze and rebooted. When it rebooted, as soon as SetCPU was granted SU, there goes another freeze. I wasn't able to change the settings due to the freeze, and after a few reboots I was taken to the setup screen like you would see after a factory reset. But this came with random F/C errors and lots of non-functional apps. You can't do anything at this point but restart from stock+PIT and go up from there. Reflashing the ROM, kernel, restoring, even ODINing another ROM won't rid the F/C hell.
Same thing as this, when I tried to use the Voodoo screen tuner:
http://forum.xda-developers.com/showpost.php?p=21629058&postcount=176
Oh also people stated imyosen kernel was a battery drain, but it's been very good on battery so far.

CM7-A8.2 Camera glitch

I've successfully installed CM7.2-A8.2 on my phone with the ultra OC kernel, and I had no problems up until now. The thing that got me to register and eventually create a thread is that the camera - which I know is not fully functional - is a bit buggy. I can live with the messed up preview thing, but somehow 1/3rd of all my pictures are being taken later than other parts of the picture. That is a bit annoying, and I wonder if there is any solution to the problem. I tried to put the minimal core frequency up to 360, that didn't help.
Looks like I can't link a picture properly, so I'm gonna do it the ahrd way: bence .heilig .hu /IMG_20120801_221900.jpg
brenca said:
I've successfully installed CM7.2-A8.2 on my phone with the ultra OC kernel, and I had no problems up until now. The thing that got me to register and eventually create a thread is that the camera - which I know is not fully functional - is a bit buggy. I can live with the messed up preview thing, but somehow 1/3rd of all my pictures are being taken later than other parts of the picture. That is a bit annoying, and I wonder if there is any solution to the problem. I tried to put the minimal core frequency up to 360, that didn't help.
Looks like I can't link a picture properly, so I'm gonna do it the ahrd way: bence .heilig .hu /IMG_20120801_221900.jpg
Click to expand...
Click to collapse
Very strange indeed, did you instal another kernel to CM7.2-A8.2 or just the one that is with the ROM.
I have noticed that other kernel's can somethimes provide weird results.
dirkhuysmans said:
Very strange indeed, did you instal another kernel to CM7.2-A8.2 or just the one that is with the ROM.
I have noticed that other kernel's can somethimes provide weird results.
Click to expand...
Click to collapse
Actually the kernel I have is not for the A8.2 but for the A8.1a, but I have another phone with the same kernel/ROM (my father's) and the camera on it works just fine. As far as I know A8.2 has no kernel included.
Try g2mod 2.5 kernel, I had some strange bugs on CM7 before using that.
Have you tried different camera applications? Camera360 and Camera Illusion work quite nice with CM7.
martialaw said:
Try g2mod 2.5 kernel, I had some strange bugs on CM7 before using that.
Have you tried different camera applications? Camera360 and Camera Illusion work quite nice with CM7.
Click to expand...
Click to collapse
Thanks, the g3mod 2.5 kernel did the trick : )
any kernal can be used
brenca said:
Actually the kernel I have is not for the A8.2 but for the A8.1a, but I have another phone with the same kernel/ROM (my father's) and the camera on it works just fine. As far as I know A8.2 has no kernel included.
Click to expand...
Click to collapse
no any kernel of this device can be used......I use A8.3 ROM ND Alpha8's ultra oc kernal and it works fine.....just try flashing another kernal or just update Ur ROM to 8.3

Categories

Resources