UPDATE: The problem is my phone's screen won't turn on after pressing the power button several times. I discovered another issue with it is its time actually changed 6 hours later from my zone time. Hope you guys will give me tips to resolve this issue. PS- I tried to post a video link here but it won't let me at all because I need to post at least 10 times.
What version of AOKP are you running? I know Milestone 2 was supposed to fix a lot of issues.
brd23 said:
What version of AOKP are you running? I know Milestone 2 was supposed to fix a lot of issues.
Click to expand...
Click to collapse
I'm running the recent version of AKOP which is posted on their thread.
Related
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...
Is anyone else experience problem with the GPS lock with LPU.
I have installed WanamLite 12.4 few days ago and it takes more then 2 MIN to get a GPS lock.
YoramZa said:
Is anyone else experience problem with the GPS lock with LPU.
I have installed WanamLite 12.4 few days ago and it takes more then 2 MIN to get a GPS lock.
Click to expand...
Click to collapse
Yes, I have this problem with all 4.0.4 versions (starting from wanamlite 12.3). Seems to be the problem is with the samsung code.
No solution yet, so I am back to wanamlite 12.1
P.S. Few people do report to have a fast lock with LPU - not sure how, but maybe there is some difference in hardware...
polzovotel said:
Yes, I have this problem wit all 4.0.4 versions (starting from wanamlite 12.3). Seems to be the problem wirh the samsung code.
No solution yet, so I am back to wanamlite 12.1
P.S. Few people do report to have a fast lock with LPU - not sure how, but maybe there is some difference in hardware...
Click to expand...
Click to collapse
Thanks,I will wait ubtill the next version of WanamLite
YoramZa said:
Thanks,I will wait ubtill the next version of WanamLite
Click to expand...
Click to collapse
Next version will be based on XWLPX - that still has this problem (but working slightly better than previous one).
I am still wondering how some other users claim fast gps lock...
polzovotel said:
Next version will be based on XWLPX - that still has this problem (but working slightly better than previous one).
I am still wondering how some other users claim fast gps lock...
Click to expand...
Click to collapse
¸
With this solution I get a little bit faster GPS fix:
Setting > location services > Google location service:
enable --> disable and then enable.
polzovotel said:
Next version will be based on XWLPX - that still has this problem (but working slightly better than previous one).
I am still wondering how some other users claim fast gps lock...
Click to expand...
Click to collapse
New version for WanamLite 12.5
I going ti install it.
I will report later if it fixed the GPS bug.
YoramZa said:
New version for WanamLite 12.5
I going ti install it.
I will report later if it fixed the GPS bug.
Click to expand...
Click to collapse
The bug still exists on 12.5
The problem still there
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
The problem still there
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
So what should we do?
Wait till any update fix that
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
Wait till any update fix that
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
I guess we have no choice.
YoramZa said:
I guess we have no choice.
Click to expand...
Click to collapse
Is there some way to report this issue to Samsung ?
In the past, Nexus also had a GPS lock problem when 4.0.4 was released. Then Google fixed it.
Probably Samsung took this code and based there roms on it.
polzovotel said:
Is there some way to report this issue to Samsung ?
Click to expand...
Click to collapse
I don't know, i'm waiting for JB 4.1
YoramZa said:
I don't know, i'm waiting for JB 4.1
Click to expand...
Click to collapse
Well, it will take 2-3 month ....
polzovotel said:
Well, it will take 2-3 month ....
Click to expand...
Click to collapse
Wanam 12.6 - still the same problem.
Left - 12.6 (4.0.4) - see the satellites,
but do not lock (or lock after 1-2 minute):
Right - 12.1 (4.0.3) - see the satellites, lock in 1-3 sec:
polzovotel said:
Wanam 12.6 - still the same problem.
Left - 12.6 (4.0.4) - see the satellites,
but do not lock (or lock after 1-2 minute):
Right - 12.1 (4.0.3) - see the satellites, lock in 1-3 sec:
Click to expand...
Click to collapse
Two more months until November.
AJ88 said:
Wait till any update fix that
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Try this it works for me
http://forum.xda-developers.com/showthread.php?p=31783363#post31783363
Hi everybody. I have been reading many of the posts here over the past 6 months and trying to learn as much as I can about different ROMs and issues related to my particular phone which is the Samsung Epic 4G Touch.
Thanks Exit_Only for your helpful work in this thread: http://forum.xda-developers.com/showthread.php?t=1975379. In that thread Sydius 08 asked "How are the Stable 1 tweaks running for you guys? Running CM10 11/18 nightly" I would like to focus on one aspect of that.
First I am currently running cm-10-20121117-UNOFFICIAL-d710 with gapps-jb-20121011-signed. I had installed JellyBeanMod_Stable-One_EO in hopes that it would resolve my long-standing GPS issue. I have read so many threads and I do appreciate all of the comments and attempted fixes by this community. I also use GPS Status and GPS Essentials where I see zero satellites but saw eight or nine instantly with #3 below. Here are the three times when my GPS has worked:
1) When I first got it just over a year ago. It was running Gingerbread 2.3.x (don't remember the last number but think it was 1). It worked perfectly but stopped after about 2 months and worked on and off after that.
2) After the GPS completely stopped working I started learning all I could about using a custom ROM. I tried CyanogenMod 9 but it did not resolve the issue. There's more to the story and more ROMs and tips provided here that I tried but all failed. However, whenever I Odin back to StockCWM-EL26.tar it works perfectly. I followed the tip about getting a fix prior to putting an ICS or JB ROM on.
3) I installed this on 11/15 http://sbrissen.chris41g.org/sbrissen-ALPHA6.zip and my GPS worked perfectly. However, lots of other apps failed miserably and it kept freezing up.
So here I am with nowhere else to turn. This latest CM 10 works perfectly EXCEPT the GPS. I would appreciate any thoughts on this.
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
smoresrock said:
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
Click to expand...
Click to collapse
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Shlickwilly said:
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Click to expand...
Click to collapse
Thank you. I had actually tried that one and ran into a problem with flashing it but I think that's because I didn't go back to StockCWM-EL26.tar first. I might give it a try again. I do love CM 10 and it would be perfect if the GPS worked.
For those who may not know this guy, QBKing77, is one of the best at teaching how to do this. Here is one for the SGIII and the Blazer ROM which he considers one of his favorites. I had to remove the link because I'm such a newbie. Here is the YouTube description: Blazer Rom on the Samsung Galaxy S III [REVIEW]
allenp007 said:
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
Click to expand...
Click to collapse
yep. this is the same method i used to fix my friend's GPS issue on a jelly bean ROM. after seeing to it that i was getting a GPS lock on the stock ROM, i went back into recovery, and flashed the ROM she wanted (paranoid android i think it was)... since then, she's been a happy camper locking into 7-9 satellites indoors
Great news! I was able to resolve this issue by following Qbking's YouTube tutorial: "How to Temporary Boot Stock EL29 on the Samsung Epic 4G Touch." I was able to lock on to 9 satellites and get a fix on my exact location. It was literally showing me in front of the building where I was standing.
I hope this helps someone else who might be going through the same problem with their GPS on an E4GT. If someone could post this information and possibly the link to the thread I referenced earlier I would appreciate it.
Thank you everyone for your comments.
I just installed the May 2 build of CM10.1 on my Razr Maxx (XT912). My bluetoothe headset and obd2 dongle pair without problems.
My Polar H7 heart rate sensor, however, refuses to pair. (My Razr doesn't even see it.)
When running stock, I can pair it without problems. It also pairs easily with my laptop. So I'm pretty sure the device is okay.
According to Polar, this is a Bluetooth 4.0 device. They also mention it supports 'Bluetooth Smart', whatever that is.
I tried posting this in the CM10.1 development thread, but apparently I'm not allowed to post there. I also tried going to the CM10.1 bug tracker, but the page didn't load.
Is this a known issue with CM10.1? Or, does anyone know of a way to get the pairing to work? Thanks!!!
It could be a bad install try installing all over again fresh. Also you need 10 posts to post there so just hang around make some posts if you can and see if you can post again. I you can also read through the threads of cm 10 to see for a fix
Sent from my XT910 using Tapatalk 2
I believe cm10 still having some bugs including Bluetooth so try to flash different rom (full working ) that will resolve ya problem
Edit : i had the same problem with cm10 while it was ok with stock jellybean .
Read the cm10 op i think they have mentioned some issues around cm10.
So onwards try to flash full working custom ROM if ya don't wanna face this trouble in future
Thx
Hit the thx button if i helped ya in anyways
Thanks guys. I had already tried the suggestions from the CM10.1 thread, including clearing data for 'Bluetooth Share'. I agree that any of the ROMs based on the stock kernel probably have a better chance of success. Since the device does appear when I search for it when running the stock ROM.
I was just hoping maybe someone else ran into this and had a workaround. Or, at the very least, to let the developers know about the bug.
Thanks for taking the time to reply...
marksibert said:
Thanks guys. I had already tried the suggestions from the CM10.1 thread, including clearing data for 'Bluetooth Share'. I agree that any of the ROMs based on the stock kernel probably have a better chance of success. Since the device does appear when I search for it when running the stock ROM.
I was just hoping maybe someone else ran into this and had a workaround. Or, at the very least, to let the developers know about the bug.
Thanks for taking the time to reply...
Click to expand...
Click to collapse
Clearing data worked for me
BOSS__DAWG said:
Clearing data worked for me
Click to expand...
Click to collapse
Did you clear data for 'Bluetooth Share', or something else?
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.