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
Related
Has anyone seen this?
http://www.techradar.com/news/phone-and-communications/mobile-phones/htc-admits-some-androids-leak-wi-fi-passwords-1059847?src=rss&attr=all
It seems a pretty big bug. I am wondering if it affects people with custom ROMs?
I have CM7 and just curios if it would behave the same.
http://www.engadget.com/2012/02/03/htc-acknowledges-wifi-security-flaw-says-it-deliberately-kept-i/
HTC has released a fix Only a matter of time till we get it (PS - AOSP ROMs don't have it at all, if Sense ROMs do, it'll be fixed soon)
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
HI on my lg p500 I have some problems with multitouch in games there is a fix? I dont want to change my rom or kernel (maybe a kernel with fix)
so there is a fix something?
The multitouch problem on our phones is caused by our hardware, so a complete fix would be almost impossible. There are different touch screen drivers in different kernels which do affect multitouch, but none fix it. Also, there's an old kernel with a work-around that does a fairly good job fixing it, but I can't seem to find it, it also caused a lot of battery drain. There's an ice cream sandwich kernel which tries to fix it here:http://forum.xda-developers.com/showthread.php?t=1468792 in my opinion, it doesn't work very well though, and it is only for ice cream sandwich. If you try out different kernels, you may find one that you like better, but there is no way to completely fix it.
( on youtube I have watch a video with 80% fix for lg500
wolfuniqe said:
( on youtube I have watch a video with 80% fix for lg500
Click to expand...
Click to collapse
its true we have kernel with the touch fixes... n basicaly mostly all kernels are built with these fixes..... if the problem cannot go completely atleast it has been reduced..!!!! :cyclops: ... well... search over for kernels.... i can say... candied ice... perfect peso... roqthunder(these r some good kernels... which r used as defaults in roms).. so... check it out... download zip n flash..
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.
I was wondering that maybe I can help fix the bluetooth error on sense 4 roms for the htc amaze but before that i kinda want to know what has been tried and what most of the developers think the problem is. Dont worry i may seem as a noob but i know my way around the device. I am just tired waiting for a working sense 4 rom with bluetooth so i have decided to do it my self any help is greatly appreciated.
found a clue
So i have been looking around at other devicea and tampering with mine and found out that the major cause could be lack of bluetooth drivers for sense 4 , i believe that that was also the problem for other sense roms as well. I know most of the big shots of amaze may be able to fix this and create the drivers. This was the problwm in sensation i guess but they fixed it