[Q] Sensor fix (PAC-ROM)? - Oppo N1

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:

Related

Camera working normaly on rhod-100?

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

[Q] ICS BCM 0.3.2 - GPS Troubles - Runkeeper app

Hi,
I'm currently running dk_zero-cool's ICS BCM-Rom for Desire - which seems very stable and usable to me. I love being abke to run ICS on my old Desire.
I'm having trouble with the runkeeper app though and was hoping somebody can help me out here: For some reason, the app (which works fine under the most recent GingerVillain Rom) stops using the GPS to track my runs after about 1.85 miles/ 18, 19 minutes. I've had this happen three times in a row, so I don't think it's a coincidence (I was using 0.2.5, 0.2.6 and 0.3.2 versions of the ROM, resp.). The app still reports "good" GPS quality, it simply stops tracking.
I've been trying to use the "FasterFix" tool to stop this from happening, but without success.
I have not tried if this problems persists with a different running app. I will do this, but I'd really rather not switch apps.
Any ideas? Runkeeper seems to work under ICS in general (at least, I can't find any reports of problems).
Thanks for your help!
Or, if nobody knows anything, could somebody maybe post my question in the dev-thread, please? I still haven't got my 10 posts ...
saxelfur said:
Or, if nobody knows anything, could somebody maybe post my question in the dev-thread, please? I still haven't got my 10 posts ...
Click to expand...
Click to collapse
Or you could PM me
Try THIS. If that fixes it, I can add it to the ROM later.

Could someone please tell me the most stable 4.1.2 rom?

Need to know for a little experiment I wanna try.
Sent from my SGH-I927 using xda premium
Pacman or cm10 both by dman who is in fact da man !
Sent from my SGH-I927 using xda app-developers app
They seem like there's too many problems with them.
Sent from my SGH-I927 using xda premium
There's a thread reporting current bugs.
Those bugs are still important but I can say that these ROMs already work very good.
Thanks to dman for original work and, lately, to spyke555 and kick who are really doing an excellent job (development was almost dead before they committed and i'm very thankful to them for what they are doing).
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
spitfire2425 said:
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
He already answered your question, the 4.1.2 weren't ever completed, they were abandoned... hence why the issues in those roms are still present.
Install PACRom 18.2 and then apply the fixes for keyboard etc. I think the fixes are in the litekernel thread. Put on the latest litekernel for 4.1 keyboard fix, lights fix and you'll have the best working 4.1.2.
Note - skype and bluetooth headset still won't work, pretty sure the camera issue with rotation is still present. I ran pacrom 18.2 for MONTHS without any issue except those listed and the wake lag.
I was trying to port something, not use it as a rom.
Sent from my SGH-I927 using xda premium
GPS and other features
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
myxoh said:
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
Click to expand...
Click to collapse
Not for version 4.1.2 (jellybean)
Only ICS 4.0.xxx ...
****, somebody needs to make a sticky for the most current stable rom .. this question keeps coming up over and over and over in every forum and many threads.
myxoh said:
GPS Working (most important)
Click to expand...
Click to collapse
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
MUSIC Working
Click to expand...
Click to collapse
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype Working
Click to expand...
Click to collapse
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Camera Working
Click to expand...
Click to collapse
Current CM10.1 and derivatives have a fully working camera.
Google Now Working (this seems to be an issue from all custom Roms)
Click to expand...
Click to collapse
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Thanks for the reply
roothorick said:
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Current CM10.1 and derivatives have a fully working camera.
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Click to expand...
Click to collapse
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
myxoh said:
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
Click to expand...
Click to collapse
hi,
thread how to compile from source:
http://forum.xda-developers.com/showthread.php?t=2071542
AFAIK drivers are not open source if they were there wouldn't be so much problems with them. They are ported from other devices similar hw but with code for them.
any news about JB and bluetooth headset issue?
this is the only thing that's been holding me back so far
myxoh said:
Uhm is any STABLE release with:
(...)
Click to expand...
Click to collapse
Where to find this "Uhm"? It was not listed here: http://forum.xda-developers.com/showthread.php?t=1621350

[Q] Bluetooth broken on CM10.1 (+ any 4.2 ROM tried); Drop to CM10.0, or other?

Hi,
I've a few 4G's running Cyanogenmod 10.1-RC4.
Generally great, but ...
Bluetooth is unstable, and refuses to pair with many devices. That's old news -- LOTS of others on 4.2.x-based ROMs are reporting similar problems.
NONE of the fixes/workaround I've managed to find/try have helped. And, AFAICT, Google's "not talking".
My alternatives atm seem to be:
(1) stay on current 4.2 ROM and live without Bluetooth
(2) wait for 4.3, 5.0, or 'whenever' it gets magically fixed
(3) drop back to another version (<= 4.1 ? other) where bluetooth is known to work and be stable.
(1) isn't an option. (2) is plain foolish. (3) seems like a (possible) plan.
QUESTION: What's a recommended choice? I don't need flashy, I need functional -- rooted and without vendor bloatware.
Is CM 10.0 my "best" choice?
BT is imho the only pain point of 10.1/rc5. I too have read that none of the fixes work that corrected it on earlier versions.
Does anyone have a solution to the BT problems that is up to date with 10.1/rc5?
Good questions about cm op. Subscribing.
I'm considering cm for my epic due stock rom being a pos pita, but need bt. Same requirements, functional, not flashy, slim, fast and good battery. Please be sure to update and post here. I'm interested in what route you take.
Zaggy
Sent from a rooted candy bar
Bueller?
Anybody?
756, you figure out what your going to do? Is cm9 an option?
Sent from a rooted candy bar
Zagnutty said:
756, you figure out what your going to do? Is cm9 an option?
Click to expand...
Click to collapse
For getting bluetooth & wifi both working at the same time, CM 9.1 RELEASE is the only viable option in the CM product line. On any of my phones, anyway. Neither 10.0 or 10.1 work.
I switched after finding this bug
https://jira.cyanogenmod.org/browse/CYAN-878#comment-12632
which got no traction at all. Lots of references in there that make you wonder what Google, at least, is thinking.
Between all that, and the thin responses here, v9.1 will be good enoough until I eventually updgrade to other phones/ROMs.
Bluetooth temporary fix
Bluetooth issues are for almost all cm10.1 roms. The only solution is to force stop Bluetooth from applications and the toggle again. It works for me
Hit THANKS if I helped :laugh:
reshampanth said:
Bluetooth issues are for almost all cm10.1 roms. The only solution is to force stop Bluetooth from applications and the toggle again. It works for me ;
Hit THANKS if I helped :laugh:
Click to expand...
Click to collapse
Hi! Just want to know how to force stop bluetooth, I have cm 10.1 and having problem with bt. Thanks in advance
leo8259 said:
Hi! Just want to know how to force stop bluetooth, I have cm 10.1 and having problem with bt. Thanks in advance
Click to expand...
Click to collapse
Go to settings- applications - all applications - bluetooth share- force close
That's it. Toggle again and it shud work
Don't just say thanks, hit thanks

Known ROMs with working phone mic?

Are there any known 4.3 or 4.4 ROMs with working phone mic?
I've used CM 10.2 Stable (4.3) and Carbon Rom (4.4.2). Both work great, the only issue is that the headset is not usable for calls (low mic output). My solution for now is using the earbud/mic, but I'm curious to know if anyone has made progress on this. Aside from this, the various ROMs are near perfect for my needs.
I'm not very knowledgeable on the details of writing ROMs, but would any type of source code release from LG help developers solve this? Curious to know what the main hurdles are for the devs and what tools they need.
Thanks.
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Neroga said:
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
markusrussell225 said:
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
Click to expand...
Click to collapse
Still no luck on a solid working phone microphone (low volume on other end). And the search continues.
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
markusrussell225 said:
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
Click to expand...
Click to collapse
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
ja.andro said:
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ask because this is a problem has existed on all known roms since 4.3.1 for the E980 on ATT. Never been able to get a straight answer anywhere so I figure I would generically post it. I have reached out to some devs but not luck.
Any success on your searching?
thureos said:
Any success on your searching?
Click to expand...
Click to collapse
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
markusrussell225 said:
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
Click to expand...
Click to collapse
I saw that solution but I went back to rooted and debloated stock, I am very pleased with speed and stability.
Thanks
i've made the edits suggested on that post and still get the same issue...i dont remember having this issue before but i thnk youre right and the previous roms werent 4.4...oh well i live on the phone for work so back to stock for me. for now i guess...wanting a new phone anyways, hope we get the g pro 2 or g3 soon

Categories

Resources