im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
DonDizzurp said:
im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
Click to expand...
Click to collapse
Based on your signature, you're running OrDroid 7.1.0 .
At this point in time (IMHO) the Sense 4.0 ROMs just aren't mature enough to warrant using them as a daily driver. There's a lot of bugs that remain to be fixed or even discovered.
Remember, the Sense 4.0 ROMs are not originally made for our devices - they are a port from another device.
Probably best to stick with Sense 3.6 based ROMs.
OH, its because of sense 4.0? probably something kernel related im assuming?
yea our official ICS came with sense 3.6 but 4.0 is sooooo slick
well, at least i know its nothing wrong with my phones hardware .. ill try a 3.6 rom and see if i get the same issues. thanks
DonDizzurp said:
OH, its because of sense 4.0? probably something kernel related im assuming?
yea our official ICS came with sense 3.6 but 4.0 is sooooo slick
well, at least i know its nothing wrong with my phones hardware .. ill try a 3.6 rom and see if i get the same issues. thanks
Click to expand...
Click to collapse
Yes, I agree, it DOES look slick LOL! It's not Sense 4.0, but rather, the ROMs based on Sense 4.0. Again, they are ports from over devices - once all the kinks get ironed out they are going to kick butt! But for now, they are very young and "not quite ready for prime time".
JWhipple said:
Yes, I agree, it DOES look slick LOL! It's not Sense 4.0, but rather, the ROMs based on Sense 4.0. Again, they are ports from over devices - once all the kinks get ironed out they are going to kick butt! But for now, they are very young and "not quite ready for prime time".
Click to expand...
Click to collapse
ok, thanks
its all good, the devs here at XDA will figure things out in no time
DonDizzurp said:
im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
Click to expand...
Click to collapse
There is workaround for that.
Camera : Turn off face detection in camera settings, your camera will fly.
Capacitive Button : It's related usually with Kernel. Read Changelog of the kernel you have to see if there is a workaround.
Proximity Sensor is working correctly if you untick Automatic Brightness.
That should fix some of your problems. You can have a look at this thread too.
Lucky Thirteen said:
There is workaround for that.
Camera : Turn off face detection in camera settings, your camera will fly.
Capacitive Button : It's related usually with Kernel. Read Changelog of the kernel you have to see if there is a workaround.
Proximity Sensor is working correctly if you untick Automatic Brightness.
That should fix some of your problems. You can have a look at this thread too.
Click to expand...
Click to collapse
hmm, okay ill look into that..
auto brightness doesnt even work for me, and because of that.. the capacitive touch buttons dont light up (since they cant detect if its dark enough to be lit)
it worked on stock rom, and i went straight from stock to sense 4.0 without missing a beat im gonna try arhd sense 3.6 to see if these issues are nonexistent with sensation base roms
the proxy sensor works... when it wants to..
it seems this issue remains with sense 3.6 based ROMs
Related
Why is it on every sense 3.0/gb rom I try I run into the same issues... When I answer a call it is automatically on speakerphone.. random rings from the phone... when i plug/unplug the phone from a usb port on a computer it goes crazy playing a ringtone.. I am also not the only one who has this issue. I am formatting everything correctly and have the appropriate radio/ril.
earhog said:
Why is it on every sense 3.0/gb rom I try I run into the same issues... When I answer a call it is automatically on speakerphone.. random rings from the phone... when i plug/unplug the phone from a usb port on a computer it goes crazy playing a ringtone.. I am also not the only one who has this issue. I am formatting everything correctly and have the appropriate radio/ril.
Click to expand...
Click to collapse
Well, sense 3.0 wasnt specifically designed for this phone, so any ports are going to be just that...ports.
There may very well be bugs still present and unresolved.
I don't think it's gb-specific only, as I run a gb-sense 2.1-based ROM and have never experienced what you are describing.
I'm running Leedroid with the sense 3.0 patch and haven't experienced the issues you describe.
Sent from my Desire HD using XDA App
you might wanna add which roms and radios you have been trying, that might help solve your issue, also have you checked for known bugs of that rom?
Im running coredroid 6.8 and have the issue with the speakerphone automatically being on shen i answer a call. Any ideas?
Well, the fact is *every* rom I have tried has issues: sync issues or fc issues or gps issues or calendar issues or sound issues or battery issues and so on... There just is no perfect rom...
Sent from my Desire HD using XDA App
Four-Fifty-X said:
Well, the fact is *every* rom I have tried has issues: sync issues or fc issues or gps issues or calendar issues or sound issues or battery issues and so on... There just is no perfect rom...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you want something done right, you gotta do it yourself, I suppose, huh?
earhog said:
Why is it on every sense 3.0/gb rom I try I run into the same issues... When I answer a call it is automatically on speakerphone.. random rings from the phone... when i plug/unplug the phone from a usb port on a computer it goes crazy playing a ringtone.. I am also not the only one who has this issue. I am formatting everything correctly and have the appropriate radio/ril.
Click to expand...
Click to collapse
You may not be the only one, but I am experiencing none of these issues with Coredroid and stock AT&T radio. Nothing like that. It has been very stable for me.
I figured out the problem must have been HW related... starting having the problem on stock roms as well. So warranty one is on the way
Scott_S said:
If you want something done right, you gotta do it yourself, I suppose, huh?
Click to expand...
Click to collapse
Didn't mean it that way. It goes without saying that porting a rom is really complex...100s of hours or work. Because of the complexity, don't expect a custom rom to be completely clean.
Four-Fifty-X said:
Didn't mean it that way. It goes without saying that porting a rom is really complex...100s of hours or work. Because of the complexity, don't expect a custom rom to be completely clean.
Click to expand...
Click to collapse
I know you didn't, I was just being a turd, something at which I'm quite proficient...
ok so this is driving me nuts i fixed proximity sensor and then it goes out again so it seems that its a sense problem ??
i have flashed all roms and kernels and seems that every and all roms that are not sense work ugh
dont tell me to flash or do this or that i have done it all i fear its being over looked or a bug with base and may need to leave sense unless someone can tell me new info
bump
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
rpod83 said:
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
Click to expand...
Click to collapse
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
MagicalHobo said:
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
Click to expand...
Click to collapse
Thanks, MagicalHobo. Did you ever try a different ROM with success?
rpod83 said:
Thanks, MagicalHobo. Did you ever try a different ROM with success?
Click to expand...
Click to collapse
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
biglittlegato said:
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Click to expand...
Click to collapse
From my experience, GPS works perfectly on aospx.
on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
russian392 said:
on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
Click to expand...
Click to collapse
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
I'm trying the new MIUI pure view and the problem is horrible. Working g on a solution.
Sent from my LG-P506 using xda premium
sarus_b said:
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
Click to expand...
Click to collapse
anyway i think i found a fix if anyone has a black screen bug like that, or lets just say you cant run aokp.
http://forum.xda-developers.com/showthread.php?t=1227682
i would switch to rashed97's cm10 rom, its way more stable than all the other stuff, and it has a version for each optimus phone
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
gabo_lope said:
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
Click to expand...
Click to collapse
The kernels included multiple black screen bug fixes, I assumed the could work, but my thrive did not like them, my color was way off and stuff like that. Black screen persists but depends on ROM I think. Give it a go and don't forget, backup everything.
Sent from my LG-P506 using xda premium
i only had that problem on. cm9, try gingersnap 2.3, it doesnt has that problem
i would really like to use fundoozz's miui pureview rom, it has the issue, i doubt it is based of cm7 but it is GB, i have no freaking idea what the problem could be, but still looking, also plz help me, get a cm7 rom that has the issue and try finding a fix for it by testing.
Thanks,
Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.