Related
i have tried some builds now, kernels etc. but i can't seem to get it to work, so my question is: is there someone here with an rhod-100 who got the camera to work. (with working i mean, are you able to make pictures without the camera crashing or freezing after 4-5 secs after u started the app >.<)
the newest 10/1 kernel made no difference and yes i tried the latest frx03 version (also some prev. versions) froyo x also did not worked for me. what should i do?
I can't get it working too....
Rhod100_de - Photos: yes - without crash hm - i think its related to autoexposure or whitebalance - as long as the image keeps somewhat static the app (Vignette from latest FroyoX in my case) works, if i change the image the screen gets distorted and the app or os crashes
I can make pictures in 1 out of 10 Android runs. But than it crashes after making 1-4 pics. So it works a little bit. Force Closes, freezes, crashes etc. are normal as for now on the rhod100 and it seems that there must be some debugging progress . But i think that will come along at some point! . I think it has to do with the stolen gpios that are used by the Keyboard (was it that or another module?) and are making more trouble on the rhod100's then the other rhod models.
Hope this will be fixed
same problem here... hope they'll find a way to fix it as soon as possible...
Geko90 said:
same problem here... hope they'll find a way to fix it as soon as possible...
Click to expand...
Click to collapse
Glad to see you're so committed to helping...
So Lets get it on. How can we/i/somebody help to get this working on rhod100 like it runs on the oder rhodiums?
Bieka said:
So Lets get it on. How can we/i/somebody help to get this working on rhod100 like it runs on the oder rhodiums?
Click to expand...
Click to collapse
Logs, as always. However, I don't think the RHOD100 camera is any worse off than the other RHOD's - my cam is far from perfect, I get FC's and the like as well.
The code is still very experimental - but the more logs that viruscrazy gets, the better - that's for sure.
As for the RHOD100 issues, those seem to all center around the panel - which hopefully WisTilt2 will resolve soon (haven't seen him in a week or so, but he said he'd be back around Sunday...)
Thanks ,
i thought camera is working better on all other rhodiums? All i read in the test thread (ok i didn't read EVERY Post ) was working, working, working. Only rhod100's had problems posted there i thougt. Good to know that it is that different . I will see if i can send him some logs. What you say about the hopefully soon solved panel problems sounds great.
cheers
Hello,
I have been trying out some GB roms lately and during the testing i saw that the compass was not showing north anymore.
If i turn the phone a little, the compass is swaying somewhere between NE and NW, but it never points north.
So i went back to FroYo roms, but now i have it there also.
I have been reading several messages fro different GB roms that people are having the same problem.
I also used the recommended radio's for the GB roms.
Since my AuraxTSense (FroYo) rom now also has this problem, it looks like a radio problem.
Can someone confirm this problem and tell me the solution or tell me the radio that is working?
Eric
Edit: See my post on page 2. There is a snq kernel fix for this problem.
Well, i have been testing some further.
Radios (old or new) make no difference.
Froyo rom (Aurax 8.4) and recalibrating the compass the old way, did make it work again.
Installing a new rom (GingerBread that is) and everything was wrong again. The radio version did not make any difference.
So i'm going back to Aurax and hope that i can recalibrate it again to let it work.
For other's with this problem:
Try the old way of calibrating the compass.
Make at least 2 figures 8, but do it slowly. It should take at least 2 seconds for every 8 you make.
Then turn the phone around 360 degrees along the length axe of the phone, also at least 2 times and 2 seconds per turn
Then turn 360 degrees along the sides axe (width), also at least 2 times and 2 seconds per turn.
If this did not work, repeat the last 2 ways of turning (length and width axe) but do it faster and about 6 to 8 times per direction.
This worked for me (and i hope it will work again in a few minutes).
Eric
Looks like North is up and South is down. The compass is now a "bubble" app.
MrXimi said:
Looks like North is up and South is down. The compass is now a "bubble" app.
Click to expand...
Click to collapse
I read a few days back that some Chinese Rom's had fixed it (HiAPK or something like that), but i just read that they also still have this problem.
So i will have to wait untill this is really fixed, because i need the compass for finding directions etc.
it seems to be a general gingerbread problem, other devices are affected too:
http://www.youtube.com/watch?v=l-9lehX8u2U
http://www.google.pn/support/forum/p/Google Mobile/thread?tid=07d4eaf9686b664e&hl=en
It is a general Ginger problem..we can nothing do about it but...waiting for fix
I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741
I added my comments also.
Sent from my HTC Desire using XDA App
supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092
godutch said:
supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092
Click to expand...
Click to collapse
In the RCmix S thread there was somebody who had tried it.
In GB most of the files are not found.
The fix is for Froyo and not GB.
The guy (i think) reported that it did not work at all.
We will have to wait for some other solution.
godutch said:
I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741
Click to expand...
Click to collapse
Confirmed
godutch said:
i opened a bug report on android's bug tracker, i encourage everyone who has this issue to confirm it so it will be fixed.
confirmed... Thnx
Click to expand...
Click to collapse
Compass fixed with new kernel
Since yesterday there is a fix for the Compass problem in the GB rom's
It is a new kernel from snq and works for (at least) most GB rom's and probably all GB rom's.
I have not had time to try it, but in most rom threads there are people who have tried it and it works!!!!!
The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1039004
If you want the flashable version, you can find it on the line with this text (on the previous page link):
download: zImage-v05 (flashable v04-to-v05 kernel image update package here)
Click to expand...
Click to collapse
or click on the link below:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1039004&v=1&libid=1306265553578&out=http%3A%2F%2Fdl.dropbox.com%2Fu%2F13432479%2Fmsm-2.6.35-bravo-GB%2Fg308ba26%2Fv04_to_v05-img-upd-flash.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D628%26order%3Ddesc%26page%3D2&title=%5BKERNEL%5D%5BGB%2FSENSE%5D%202.6.35.10%20%5Bv05%5D%20%7C%20OC1152%20%7C%20LZMA%20%7C%20COMPASS%20%7C%20fixes%20%2Baddtl%20modules%20-%20xda-developers&txt=here
Have fun with it. I will when i have time to flash it
Confirmed working btw, got it in my ROM and it's fine
Yeah, works for me too. Using latest leedroid.
sorry. wrong post.
~renzs
Working on Nexus S
Hello,
is this fix working on Nexus S, too?
So, is this fix going to be incorporated into the official Acer releases (prob not)?
I guess we have to root and flash after market roms to fix their fubars...
I'm running CM10 nightlies for a while now my camera has been failing. Everytime I try to take a picture, after a couple of seconds, it just freezes. Has anyone had this and tried fixing it?
So turns out that Smart Stay is causing the problem because it is trying to access the camera the same time I am trying to use it. So to fix it I just added any app that uses the camera to the exception list option in smart stay. Finally an end to this annoying problem. (or is it? ...I really hope it is.)
I had the same problem until I switched to jelly bean jellybomb rom instead. Try it, u will love it
Galaxy0523 said:
I had the same problem until I switched to jelly bean jellybomb rom instead. Try it, u will love it
Click to expand...
Click to collapse
I'll definitely give it a try, but what about if I still want to use cm10? Has anyone had any progress fixing this problem or at least finding the source of it?
In the changelog for cm10 it says the next nightly will introduce a "Fix Ignore Keyevents", maybe, just maybe, that will help!
Many people do not have this problem. Are you sure its not something you installed?
Sent from my SPH-L710 using xda app-developers app
pastert33 said:
Many people do not have this problem. Are you sure its not something you installed?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have odined back to stock, and wiped&&formatted everything possible. I did come across a thread (the link I have since lost) that mentioned something about possibly gapps causing the problem. Just know I had the idea that maybe because I am using JustinBean's inverted gapps there is a problem. I will investigate and see if that helps.
I can't believe I didn't think of this sooner. So even after the update, no change.. still freezing - GREAT! So then I started getting really aggrivated and started to uninstall apps that "Pimp My Rom" included, and I thought flash might be the culprit. And then it hit me, this is a camera problem right? Well then what app uses the camera? SMART STAY of course, and it made even more sense because it takes a sample at a certain interval and that explains that I am able to use the camera only for the short amount of time (always the same amount of time). So to fix the problem I just set in the exception list in smart stay an exception for any app that uses the camera. I really hope this is the fix I need. Thanks for your input guys!!
Hi,
I am having some GPS issues and I don't quite know how to fix them.
First of all, I have tried different ROMs starting with JellyKing, CM10.1, MarvellousCM10 and they all behave the same way.
The GPS simply does not get a fix, even when I let it sit outdoor for several minutes (I even left it 30 minutes).
There are times, however, where it gets the fix right away, it would work till I close the app that is using it (Endomondo, Runkeeper, for example) then it won't work again. I was not able to find any way to reproduce the "working" GPS.
The fact that it works, albeit rarely, makes me think it's not an HW issue, but I'm not so sure anymore.
What did I try already:
1) I followed this thread:
http://forum.xda-developers.com/showthread.php?t=1563226
The fix -supposedly- was tested with the Wildfire S.
Made no difference.
2) I installed FasterFix
The App simply did not work for me. Whichever server I picked, it said that an error had occurred
3) I installed FasterGPS
The app worked, in the sense that I selected a server and it updated the gps.conf file.
It made no effect though.
I have installed "GPS Status" to test it and I was (never) able to get a fix since I installed it.
All of the above was done with the rom from this thread (http://forum.xda-developers.com/showthread.php?t=1878031) but I had the same behavior with other roms ...
Any suggestion?
None of those patches will help you.It's just a placebo.
However, GPS is not working on cm ROMs as it works on sense based ROMs.
It does work, but it needs a lot more time to get a fix, especially the first one.It takes around 10-15 min, or even less if you're under the clear sky.
Nightshadow931 said:
None of those patches will help you.It's just a placebo.
However, GPS is not working on cm ROMs as it works on sense based ROMs.
It does work, but it needs a lot more time to get a fix, especially the first one.It takes around 10-15 min, or even less if you're under the clear sky.
Click to expand...
Click to collapse
Poh. I left it more than 30 minutes on the balcony. Clear sky, completely open. Nothing.
Are you saying this is an issue with the CM10* based roms?
So if I try one based on CM7* should it work?
I really would like to move to JB and stay away from Sense ...but I need the GPS to work.
Thanks for your help.
Well, as I said, it does work, but it's much faster on sense ROMs.Don't know why you can't get a fix, I'd suggest downloading GPS status from play store, there you can see exactly how much satellites your phone is catching.
I think it's that way on every CM based ROM.However, I've never tried cm7, so, can't really say for it.
Sent from my HTC Wildfire S A510e using xda premium
I'm using the first method and its working fine for me I get a GPS lock within 3 seconds
Sent from my Wildfire S A510e using xda premium
FAtfcK said:
I'm using the first method and its working fine for me I get a GPS lock within 3 seconds
Sent from my Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Hi FAtfcK,
how did you follow the 1st method, exactly?
I have installed ES File Explorer, then I downloaded the Google Specific, no SSL file and extracter gps.conf on the SD card.
Then with ES File explorer I copied the file in /etc (of the internal memory). It did ask me if I wanted to overwrite the existing gps.conf, so I figure it was the right location.
Rather than overwriting, I renamed the original one, then copied the new one.
I rebooted the phone (just in case) and waited ... and waited ... but no luck.
Did you do the same?
By the way, which Rom are you using?
yankeeDDL said:
By the way, which Rom are you using?
Click to expand...
Click to collapse
In my ROM, you can select your region (Europe, Asia, Africa, ...) and aroma will pick a gps. conf for you.
And yes, first GPS fix takes about 15 min, but it should work fine after that.
Gesendet von meinem HTC Wildfire™ S mit Tapatalk 4 BETA
djolivier said:
In my ROM, you can select your region (Europe, Asia, Africa, ...) and aroma will pick a gps. conf for you.
And yes, first GPS fix takes about 15 min, but it should work fine after that.
Gesendet von meinem HTC Wildfire™ S mit Tapatalk 4 BETA
Click to expand...
Click to collapse
DJolivier,
I'm sorry but that's not the case.
I flashed Marvellous CM7.2 and the GPS works perfectly. It gets a fix outdoor in 0.1s.
Even indoor it would get 4 or 5 satellites (not enough to get a fix), but it clearly showed that the GPS was working.
WIth any of the CM10* that I used the GPS was practically dead (did not see any satellite when outside): the GPS simply was not working.
I can't quite use CM7.2: I don't need many apps, but the few I do need don't support Gingerbread, apparently, which is a pity, because everything works in Marvellous 7.2 ...
Now that I know that the HW clearly works, I plan to re-flash a CM10 and try again the various options ...
Thoughts?
1) Take gps.conf from CM7 and implent it in any cm10 ROM
2) Try CM9. It's Android 4.0.4 ICS, I know that it works perfectly.
Gesendet von meinem HTC Wildfire™ S mit Tapatalk 4 BETA
You can't say that GPS is not working on cm10 ROMs, when it is.You don't need to touch gps.conf, or to do anything for it to work.It does work.
I got fix from 12 satellites once when I was outdoors.Indoors, I usually get 5-7.
yankeeDDL said:
Hi FAtfcK,
how did you follow the 1st method, exactly?
I have installed ES File Explorer, then I downloaded the Google Specific, no SSL file and extracter gps.conf on the SD card.
Then with ES File explorer I copied the file in /etc (of the internal memory). It did ask me if I wanted to overwrite the existing gps.conf, so I figure it was the right location.
Rather than overwriting, I renamed the original one, then copied the new one.
I rebooted the phone (just in case) and waited ... and waited ... but no luck.
Did you do the same?
Click to expand...
Click to collapse
Haha. Sorry late reply. I did all the same but..... I think you forgot to set the permissions that's why and you should overwrite it
Sent from my HTC Wildfire S using xda app-developers app
Nightshadow931 said:
You can't say that GPS is not working on cm10 ROMs, when it is.You don't need to touch gps.conf, or to do anything for it to work.It does work.
I got fix from 12 satellites once when I was outdoors.Indoors, I usually get 5-7.
Click to expand...
Click to collapse
Nightshadow931,
I am sorry but GPS with any CM10 I have tried so far is dead. I had some random luck which I cannot reproduce.
I am not claiming that gps is broken on CM10, but for sure it does not work for me. Infact, I was under the impression that this issue was only mine, however, apparently, it is not and there is a "known" issue with GPS in CM10.
I have installed this morning Thunderbolt 2v0 (based on AOPK 4.1.2) and it works like a charm.
I did not try Djolivier's suggestion of copying the gps.conf from CM7.2 to CM10: I read the suggestion too late.
For now I am going to stick to this rom.
Gps issue isn't in AOKP because it isn't cm based
Powered by my Thunderbolt (This isn't spam, this ia my signature)
I have a MarvelC and have been running CM10 alpha since January. I had been having issues with GPS in all the ROMs I tried - and was told that unless I was using a sense based ROM - GPS would not work for long if I ever got it working.
In the Play Store - I found this App - Navfree USA: Free Satnav. It works most of the time. There are times I do have a problem getting a connection, but I don't know if that's because of the ROM I'm using, or because of where I am at the time and there is no satellite to connect to.
For the US version, you do need to down load individual state "maps" to use - but that has not been an issue. They also have other country versions.
It may be a "fix" for someone - give it a try.
Mamadanz said:
I have a MarvelC and have been running CM10 alpha since January. I had been having issues with GPS in all the ROMs I tried - and was told that unless I was using a sense based ROM - GPS would not work for long if I ever got it working.
In the Play Store - I found this App - Navfree USA: Free Satnav. It works most of the time. There are times I do have a problem getting a connection, but I don't know if that's because of the ROM I'm using, or because of where I am at the time and there is no satellite to connect to.
For the US version, you do need to down load individual state "maps" to use - but that has not been an issue. They also have other country versions.
It may be a "fix" for someone - give it a try.
Click to expand...
Click to collapse
AOKP for MarvelC... All aokp haven't those issue but they have low brightness bug..
Powered by my Thunderbolt (This isn't spam, this ia my signature)
Mamadanz said:
I have a MarvelC and have been running CM10 alpha since January. I had been having issues with GPS in all the ROMs I tried - and was told that unless I was using a sense based ROM - GPS would not work for long if I ever got it working.
In the Play Store - I found this App - Navfree USA: Free Satnav. It works most of the time. There are times I do have a problem getting a connection, but I don't know if that's because of the ROM I'm using, or because of where I am at the time and there is no satellite to connect to.
For the US version, you do need to down load individual state "maps" to use - but that has not been an issue. They also have other country versions.
It may be a "fix" for someone - give it a try.
Click to expand...
Click to collapse
Mamadanz,
I think I tried all the CM10-based roms for WFS and I was never able to get the GPS to work consistently. I suppose it may depend on the App that you're using: the one I tried (Endomondo, Runkeeper) don't work.
Using the AOPK-based Thunderbolt 2v0 (which is JB 4.1.2, but not based on CM) I have no problems, whatsoever, with the GPS. It's been a few days so far and I have been using it extensively.
The rom, in general, is good. Some things are in a "different" place than what I'm used to, but you have all you need.
ScardracS said:
AOKP for MarvelC... All aokp haven't those issue but they have low brightness bug..
Powered by my Thunderbolt (This isn't spam, this ia my signature)
Click to expand...
Click to collapse
Thank you Scardac - I did download your ROM. Unfortunately, downloaded the wrong GAPPS yesterday and didn't realize until I flashed everything while away from home. DL's the correct GAPPS very late last night so am still playing with everything. But so far - everything looks very good. I'll keep you posted.
Thank you again.
removed
Mamadanz said:
Thank you Scardac - I did download your ROM. Unfortunately, downloaded the wrong GAPPS yesterday and didn't realize until I flashed everything while away from home. DL's the correct GAPPS very late last night so am still playing with everything. But so far - everything looks very good. I'll keep you posted.
Thank you again.
Click to expand...
Click to collapse
In my rom (for marvel) gapps are integrated, in this rom i think no
Powered by my Thunderbolt (This isn't spam, this ia my signature)
Hi!
in march i flashed PAC-ROM on my N1 and it works quite well... but after some time (can't recall when exactly) the motion sensor stopped working. compass is not moving (any app) and the app "Sensor Kinetics" shows a popup "All available sensors on this device are set off". Just flashed newest PAC and still not working. I found some other device-specific threads mentioning there could be problems with custom rom and sensor and some of them have provide fixes. Any one know if or how this could be fixed on N1?
Thanks - Any help much appreciated!
adding more info:
Kernel: 3.4.76-cyanogenmod-g7a996ec [email protected] #1 Sun May 11 03:23:14 EDT 2014
PAC version: 4.4Beta-1.0
AOKP version: n1_kitkat
Build number: CM-userdebug 4.4.2 KVT49L 84 test-keys
Is there any way to check if this is a hardware error (eg g-sensor broke)?
Any one else had this problem?
Again, any help/hint much appreciated!
[EDIT]
Solution: http://forum.xda-developers.com/showthread.php?t=2216224
Turn your device OFF - wait 5-10minutes - ? - PROFIT!
Cool App to check your sensors: "Elixir 2" - all up and running!
[EDIT2]
Problem reappears after some time and or reboot. sometimes my n1 does not recognize my sim-card and i also have to reboot... this is a game of luck to get sensor and sim working at the same time - any help/feedback very much appreciated!
same problems here.
hello, i am having the same problems as you do.
i also tried updating and rebooting a few times.
as you said, its a luck game..
i can live with sensor not working, but when it doesnt find my sim card, that defeats the point of having a phone..
im not sure if its the sim reader or the cell antenna thats the problem.
i would very much like a fix for this too.
hi! are you running PAC too? just wondering if this is rom-related (=PAC) or device/custom-rom-related (=any custom rom)? would try omni, but only if i know this fixes it
yes, i am running pac, i did not have these issues when using omni.
Are you guys running xposed?
@trialsrider1: i don't think so
funkymaster said:
@trialsrider1: i don't think so
Click to expand...
Click to collapse
I don't think ive ever had sensor problems. It works really well for me. I maintain and add features all the time but I do flash quite a bit so maybe I don't run builds long enough to see them...I wouldnt think time would kill them though...
Sent from my N1 using XDA Premium 4 mobile app
some more info on this
it seems to help to fix permissions in recovery when this happens.
i still get the problem, but its a much higher chance of it working when i fix permissions.
after 2 days normal use, i must say it got better with every nightly i tried (i'm still on PAC) ... with the latest i haven't had this problem :good: