I've never really had problems with cam scanner before and I installed this rom by odining stock and then flashing bionix and i did this about 4 times to try to get this to work. I have installed the camera fix that they just posted and i still have this issue. Anyone willing to try and see if they have the same problem?
Me too
not only camscanner being forced closed, but also fxcamera on my Bionix-v 1.3
but there is no problem on Bionix-v 1.2.1
anyone can solve it? thanks.
Me three...camcard causes my phone to reboot.
Ditto, camscanner reboots the phone every time I snap a photo and then press the ok or cancel buttons. 1.3 with fix.
I have the same problem. I guess I have to go back to the previous version since I need to use the CamScanner. I hope some one will come up with a fix. Thank you.
IIRC, it's a problem with the kernel used. I never had camera issues, just mic and that was fixed with OverStock1.1. I believe if you update to the current one (OverStock1.3 now, I think), your camera should be fine after that.
Oniyuri said:
IIRC, it's a problem with the kernel used. I never had camera issues, just mic and that was fixed with OverStock1.1. I believe if you update to the current one (OverStock1.3 now, I think), your camera should be fine after that.
Click to expand...
Click to collapse
Have you personally tried? Ill test it out in a bit unless someone else has already tried this. Thanks for the suggestion
Nirmalspeed said:
Have you personally tried? Ill test it out in a bit unless someone else has already tried this. Thanks for the suggestion
Click to expand...
Click to collapse
Well, it seemed that the origin for the problems that appeared in the initial release was with the kernel (which was Overstock1.0). I never had any issues with my camera like some ppl had reported in the thread (Som did say that was a hit or a miss issue and I guess it missed me thankfully). My issue was with my mic not working with my headphones and that was solved by updating the kernel (like Som said before he posted the fix). Check out cmenard's OverStock thread in the dev section, I'm pretty sure a ton of ppl have already submitted lots of feedback on the newest kernel.
Yea the new kernel update fixed the problem. I believe both overstock and CWK have the fix working.
i tried it and it worked 4 me...
i am presently on bionix v 1.3 with the latest overstock 1.3 kernel and it has cleared up my camera problems!
trying bionix v 1.3.1 next but still checking out 1.3 for now...
Related
Hey,
I've tried almost all 2.2.1 ROMs now, frost, darky, atriarc, loki yet on none of these ROMs could I get the aGPS to work. It works flawlessly on 2.2 ROMs otherwise... What could be wrong?
I've tried faster fix, gingerbread.zip and sgps.zip from the forums, etc. already..
Sent from Bionix on Vibrant
then go back to 2.2... i don't see much change between 2.2 and 2.2.1 since we had voodoo on 2.2
but w/e
My gps was perfect when I was on Frost, after flashing sgps. Have you tried the hardware fix?
adyscorpius said:
Hey,
I've tried almost all 2.2.1 ROMs now, frost, darky, atriarc, loki yet on none of these ROMs could I get the aGPS to work. It works flawlessly on 2.2 ROMs otherwise... What could be wrong?
I've tried faster fix, gingerbread.zip and sgps.zip from the forums, etc. already..
Sent from Bionix on Vibrant
Click to expand...
Click to collapse
I have Simply Honey 2.5 with GPS fix plus there is another forum here:
http://forum.xda-developers.com/showthread.php?t=878970
This one has made my GPS best its ever been and probably best it will ever be considering it is Samsung..
Well, I did that immediately when I noticed that the 2.2.1 ROM isn't locking on... I had just replaced back the FFC mod camera and then I was planning to run 2.2.1 so that I can benefit from its camera firmware. So I thought maybe I screwed up the contact.
But that didn't happen. Once i flashed 2.2 back, i got a GPS lock in 15-17 seconds on every cold start.
Installed the sGPS.zip and Gingerbread.zip too, alternatively, and together, also done an ODIN and then fresh install, but none of it helps... Tried fasterfix too for India...
Anyone else facing this problem ???
Hey guys, bit of a weekend brain teaser for you guys...
My rotation function just stopped working completely a day or two ago. I dont know if its worth mentioning but I actually never use auto-rotation (I just personally dont like/need it much). However, certain programs; Youtube, games, have usually served their proper rotation function when in use.
I've been running SC 2.9.2 with jt's ec10 kernel for quite some time now without any flaws. No changes were made to the phone before the issue.
Kinda sucks not being able to watch Youtube in full screen...
Any ideas?
Interesting. Mine stopped working a couple of days ago as well, also using SC 2.9.2. I'm using jt's 4/7 kernel. I've tried reinstalling both the rom and kernel with no success. In addition to the rotation my compass also does not work, so both the accelerometer and magnetometer have failed. It happened while using Google Nav in walking mode, where the phone froze and became unresponsive. After about 10 minutes of no response I pulled the battery and afterward noticed the problem. I'm planning to revert to stock to see if it helps tonight.
whereas im relieved to know that someone else is on the same boat, i really hope that it doesnt come.down to doing a full back to stock wipe :/
it would be nice to know what caused the malfunction...
Sent from my SCH-I500 using XDA App
Mine's working again after going back to EB01 briefly before going to EC01. I was planning to try out EC01 anyway and the brief revert to EB01 is part of the procedure.
I have had VirusRom installed for about a week now. Overall I love it.
Here is my problem though. When I am making a call the screen will lock. I have to push the power button to bring back up the screen in order to hang up the call.
Shouldn't the proximity sensor know when I pull it away from my face so I can hang up the call? It did before I went to this rom, was still using stock rom at that point.
Anyone know of a way to fix this problem? I have tried to post this question on the VirusRom forum, Since I think it is a bug with the rom, but am not allowed. It says you need 10 posts to be able to do that, Still I get that too even though I am over ten posts. Oh well on that though.
This could be a deal breaker for me and VirusRom. As it is quite frustrating to me. If anyone has any thoughts on how to get around this I would be thankful.
It's due to the kernel Virus installed in teh rom. It's one of Ziggy's first kernels and it has a bug that prevents the screen from turning on after/during a call as you describe.
Fix: Install a new kernel.
There are several on here to use, or you can search PPCGeeks / Ziggy to find his new kernels, which he has now fixed the proximity sensor issue.
Thanks for the answer. I downloaded kernal manager from the market. Any specific recommendations for a kernel? Adrynalyne's seem to be the most stable, but maybe I should stick with a stock kernal.
You can't go wrong with one of Adry's kernels. You should start with one those.
Sent from my BAMF'd T-Bolt
I had the same problem. I installed the new radio which was supposed to fix it and it did. But Im having trouble with the data connection, so I flashed back to the stock radio.
Ziggy's new kernal upgrade has fixed this issue. Id suggest downloading that. It works great and super crisp and fast over the version that came with the ROM and the proximity issue is fixed, been testing it for myself and all is good.
Check the VirusRom thread for info.
Ok, So I flashed one of Adrynalyne's kernals and now I don't have 3g or 4g. Just 1x. So do I flash another kernal, maybe the stock one, and the problem is solved? That will put it back the way it was right?
nope that did not work, I flashed Adrynalyne's stock rom and still just 1x. What have I done? What do I need to do to put it back? SInce I keep rom backups everytime I flash a ROM, I am going to flash back to the previous version that did have 3g and 4g working. I hope that works. The kernal is part of the ROM, correct?
Now this is getting frustrating. Flashed back to the previous working virus rom the one I had before the kernel update, and it still is only 1x. Wouldn't the kernel be part of the rom? Why did this not work? What can I do now?
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Use Adrynalyne's kernel
http://forum.xda-developers.com/showthread.php?t=1024338
I use the 4.3 and it runs perfectly fine and the prox sensor works, his are in Kernel Manager also so it will be an easy fix.
oscar615 said:
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Click to expand...
Click to collapse
verizon 3g might still be down?
Small problem here, wondering if anyone else is having this issue.
Used the kernel with two different roms pwgb and tsm1.0, same result. The phone just restarts itself. Did a clean flash. Problem does not happen on the 9/28ish release of the kernel. Any suggestions?
Sent from my SCH-I500
mkuehl06 said:
Small problem here, wondering if anyone else is having this issue.
Used the kernel with two different roms pwgb and tsm1.0, same result. The phone just restarts itself. Did a clean flash. Problem does not happen on the 9/28ish release of the kernel. Any suggestions?
Sent from my SCH-I500
Click to expand...
Click to collapse
From what I've read recently the 10/18 build has some issues. I'm running TSM 1.0 with the 10/12 build and it's pretty stable.
I had my best results with the 9/28 and 10/5 tks kernal. The reboots started for me at 10/10 for me... for some reason disabling lagfix cured the reboot/lag for me, but I don't know how or why to be honest.
droidstyle said:
I had my best results with the 9/28 and 10/5 tks kernal. The reboots started for me at 10/10 for me... for some reason disabling lagfix cured the reboot/lag for me, but I don't know how or why to be honest.
Click to expand...
Click to collapse
There have been a lot of people saying they had to disable lagfix to stop the lag. I get lag regardless of whether it's enabled or not, but my quadrant score goes from the 940's to above 1500. Wish my performance matched the numbers...
hello new here i followed all the directions to a tee got everything install very easy as im not new to flashing roms. i have a rhod400 (sprint tp2) and i have the issue of no sound from the rear speaker when receiving phone calls or anything really. it all comes from the front earpiece speaker. is there a update to flash to fix this? or any easy way to get it working. ive tried numerous times thinking about a bad flash with no luck and yes i have task29'ed it after each to make sure. however the gbx0 3.3.x kernal works perfectly with sound but i like the normal omgb rom better personally for some reason the gbx0 nand rom on my phone seems much slower to respond and much slower going through menus etc for some reason and ive flashed it a few times to make sure
also im running the newest verizon .37 radio as well.
sorry for asking here and not in the thread i needed more posts and really hope someone can help with that. ill be posting more so hopefully will be able to ask there soon but i really wanted to get this fixed asap since i use this phone daily.
Never heard of that before, but I had to move the thread. Sorry.
Good luck & post logs. I doubt it's an issue with the ROM tho, as I run that same ROM myself. Same phone, same radio (assuming you're on the 2.37VZ radio), etc.
You're using the latest OMGB and the latest CWM recovery - not AOSP?
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
wizardknight said:
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
Click to expand...
Click to collapse
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
arrrghhh said:
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
Click to expand...
Click to collapse
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
wizardknight said:
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
Click to expand...
Click to collapse
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
arrrghhh said:
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
Click to expand...
Click to collapse
That is an odd issue. I have to agree with all your points.
wizardknight said:
That is an odd issue. I have to agree with all your points.
Click to expand...
Click to collapse
ive heard of this with really old sdcard builds... i seem to recall if you set the volume to one step below max the audio kinda worked the way its supposed to. let us know if your still having issues.
Me Too
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
NeoMatrixJR said:
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
Click to expand...
Click to collapse
Do you have this issue with the GBX Nand build?
wizardknight said:
Do you have this issue with the GBX Nand build?
Click to expand...
Click to collapse
Just got it installed. Ringer works fine on GBX0* + 3.3.6
NeoMatrixJR said:
Just got it installed. Ringer works fine on GBX0* + 3.3.6
Click to expand...
Click to collapse
Makes me think there's some acoustic patch that's missing in the OMGB .27 kernel...
That's a bummer. Strange only some experience the bug...