DHD proximity sensor - Summary - Desire HD Q&A, Help & Troubleshooting

This topic is meant to summarize all that was written about that diabolic DHD proximity sensor.
Let's gather everything you find, and try to solve this once for all, and please let's not spam dev forum section with such talks.
Scenarios:
1) The screen doesn't dim/shuts off when making a call.
Solution: First try a great app Proximity recalibrator, which can be found here (thank the guy, he did great job):
http://forum.xda-developers.com/showthread.php?p=11312762
Also, READ the whole thread before saying it doesn't work.
2) The screen dims fine (or eith some help of above app), but DOESN'T LOCK, or it turns ON when the call is answered/randomly during the call.
Solution: NONE found.
Let's assume that you've eliminated the "faulty sensor" option by:
- cleaning the sendor with cotton wab and alcohol
- trying some really different rom, like Sense.
As far as I know, sensor works with Sense roms, and problem happens with:
- aosp cfx 4.x.x (no matter the SR version)
- jellytime
So it might be something in cm10.
Or?
Write below what you know!
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified

My sensor works fine with 4/5 (LT/HT) values
Sent from my Desire HD using Tapatalk 2

Ok
Also, I think the country you bought it from (and whether it is a inspire/desire), the radio in use (and RUU) could be important factotrs.
Using a British Desire HD,
July 2012: Radio 12.69.60.29_26.17.14.11_M - AT&T Inspire 4G 3.20.502.52 (Latest)
Running CFX 4.2.2 SR15+banks gapps with no work arounds.
I have used Ice Cold sandwich, jellytime 4.1/4.2 trainwreck, CodefireX 4.1/4.2 and multiple sense Roms (2.3/4.0) in the past.
I am having NO issues (although on older release of CFX, SR8 I had some random reboots)
IDK what all the complaining is about
(I have had other issues on Alpha releases (and occasionally betas)of ROMs, but Alphas are expected to have issues.)

Great, detailed info to start from.
For me, only sense (stock gb, sabsa ICS, Viper ICS) worked fine. All JB cm10 failed, and screen just doesn't lock.
Didn't realize that radio has anything to do with sensor.
What do you mean by "country matters"?
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified

I have also had NO issues with the proximity sensor or the screen lock during calls, no fixes or calibrations made.
I've been using only JellyTime R6.1 for about a month now as my daily driver.
My DHD was bought from England. Using it now in Israel. All other info is in my signature.

broken hardware
Is there anyone that knows where the proximity sensor is actually located in the phone?
My guess would be the motherboard flex cable... :/
So my problem is, that i've dropped my DHD, and ever since then the proximity sensor/light sensor doesn't work (it is the same sensor), and I'm pretty sure that the hardware is broken.
Lately, I have been looking into the possibility of disassembling the phone, and replacing the broken part...
But as of now, i have no idea which part the proximity sensor is actually integrated onto.
Any ideas? I watched about a dozen disassembly videos on Youtube, but not one of them mention the proximity sensor.
Thanks in advance

This seems like HTC official dissassemble video:
https://www.youtube.com/watch?v=JfatoeWbMRk&feature=youtube_gdata_player
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified

iopetja said:
Great, detailed info to start from.
For me, only sense (stock gb, sabsa ICS, Viper ICS) worked fine. All JB cm10 failed, and screen just doesn't lock.
Didn't realize that radio has anything to do with sensor.
What do you mean by "country matters"?
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
Click to expand...
Click to collapse
The model sold in different countries (if it differs, I don't know) and the radio provided in different countries will make a difference.
(Sorry for late reply)
edit: The radio controls many of the phone's functions like the wireless and the cellular. It might control or affect the proximity sensor too.

Related

[Q] optical trackball problem - any way to disable the sensor?

After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner
I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.
There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977
@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?
@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:
OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper
Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel
No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper
i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k
hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?
hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source
huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!
ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper
Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye
Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] HTC Desire HD - Virtuous Quattro RC3 - Help

Hi there, I think this is my first thread. Might be the wrong forum but I thought I'd give it a try.
The reason I'm posting is because I'm looking for some support concerning the Virtuous Quattro RC3 for DHD. I can't post in the "development" thread because I apparently am a noob. Anyway here goes.
First, my specs:
Phone: Desire HD
ROM: Virtuous Quattro RC3
Kernel: LorDmodUE ICS BFS 8.8 final
Radio: 26.14.04.28_M
Patches:
Camera fix
http://forum.xda-developers.com/showpost.php?p=21930178&postcount=2072
What I'm looking for are solutions for some of the issues I've encountered during the past few days. Here's what I've experienced:
* HW video, not working - No solution, I know. Same goes for youtube etc.
* Camera, works perfectly - Fixed via patch see post above.
---------------
* GPS can't get a fix on signal. Not working. Worked perfectly on ARHD
FIXED
Patch: http://forum.xda-developers.com/showpost.php?p=21962018&postcount=2464
* Apps don't close by themselves, are they running in the background or am I just imagining this? If I long-press the home button every app I've started seems to running
SEMI-FIXED
Just swipe to the left/right.
* Auto-brightness isn't working as well as it should be.
FIXED
Patch: http://forum.xda-developers.com/showpost.php?p=21970997&postcount=2473
* With Wifi on the phone doesn't switch to 3G automatically if I move outside the Wifi area. I have to turn on/off airplane mode and enter pin to get it to work again. Doesn't work to turn Data on/off.
* Can't read SIM-contacts. I had to move all my contacts to my google-account.
* Wifi signal seems to be weak as well, the bars on the icon go down one or two levels despite me being about 2-3 meters from the router.
* Dialer crashed once but I don't know the reason why.
------------------
Anyway, the issues I've listed seem to all be minor issues and they don't bother me too much to be honest. The battery doesn't drain too fast and it's great for normal use (calls, browsing, s/r texts, pics, viewing vids with mx).
But if there's a patch I'm missing or some other type of fix for the issues I've listed, I'd be glad if you could post it here.
Thanks in advance.
Regards
Master and Blaster.
Hi, I'm somewhat of a noob (here, anyway) as well, but I'll try to give some help. I'm running Virtuous Quattro RC3 on an Inspire 4G, but the answers should still help. Grain of salt.
Master-and-blaster said:
Hi there, I think this is my first thread. Might be the wrong forum but I thought I'd give it a try.
The reason I'm posting is because I'm looking for some support concerning the Virtuous Quattro RC3 for DHD. I can't post in the "development" thread because I apparently am a noob. Anyway here goes.
First, my specs:
Phone: Desire HD
ROM: Virtuous Quattro RC3
Kernel: LorDmodUE ICS BFS 8.8 final
Radio: 26.14.04.28_M
Patches:
Camera fix
http://forum.xda-developers.com/showpost.php?p=21930178&postcount=2072
What I'm looking for are solutions for some of the issues I've encountered during the past few days. Here's what I've experienced:
* HW video, not working - No solution, I know. Same goes for youtube etc.
* Camera, works perfectly - Fixed via patch see post above.
---------------
* GPS can't get a fix on signal. Not working. Worked perfectly on ARHD
Haven't had a problem, but one of the things I did was install the inspiremod patch, which supposedly fixes some GPS stuff (resetting for North America, etc.) Not sure if it could help you, but if you are willing to experiment...
* Apps don't close by themselves, are they running in the background or am I just imagining this? If I long-press the home button every app I've started seems to running.
Same here. In fact, it's something I've noticed even in GingerBread. But, if you have the list up with your long-press, swiping a task to the left closes it.
* Auto-brightness isn't working as well as it should be.
Here, auto-brightness works, but not sure about the "as well as it should be" part. Could you elaborate? I have noticed that, when I press Power button to "wake up" my Inspire, the screen is very dim. As I draw my passlock pattern, the screen brightens up a bit, but slowly.
* With Wifi on the phone doesn't switch to 3G automatically if I move outside the Wifi area. I have to turn on/off airplane mode and enter pin to get it to work again. Doesn't work to turn Data on/off.
Sorry, this works for me.
* Can't read SIM-contacts. I had to move all my contacts to my google-account.
I don't think I even use SIM-contacts any more.
* Wifi signal seems to be weak as well, the bars on the icon go down one or two levels despite me being about 2-3 meters from the router.
* Dialer crashed once but I don't know the reason why.
I have random lockups, as well.
------------------
Anyway, the issues I've listed seem to all be minor issues and they don't bother me too much to be honest. The battery doesn't drain too fast and it's great for normal use (calls, browsing, s/r texts, pics, viewing vids with mx).
But if there's a patch I'm missing or some other type of fix for the issues I've listed, I'd be glad if you could post it here.
Thanks in advance.
Regards
Master and Blaster.
Click to expand...
Click to collapse
There's an overwhelming amount of reading in the dev thread, especially when you have to wade through the off-topic garbage.
Thanks deeteroderdas.
I'll try the GPS fix you mentioned.
Regarding auto-brightness, It does work but I sometimes feel that it's not reacting to the environment quick enough if you know what I mean. Maybe I'm just imagining this. But I did manage to find a fix, I'll update the thread.
The Wifi issue could be due to the radio I'm using, it's a sense radio from ARHD.
Ahhh you swipe to the left to kill the app, "stupid me"....
Anyway, you've been great thanks.
Master-and-blaster said:
Thanks deeteroderdas.
I'll try the GPS fix you mentioned.
Regarding auto-brightness, It does work but I sometimes feel that it's not reacting to the environment quick enough if you know what I mean. Maybe I'm just imagining this. But I did manage to find a fix, I'll update the thread.
The Wifi issue could be due to the radio I'm using, it's a sense radio from ARHD.
Ahhh you swipe to the left to kill the app, "stupid me"....
Under settings, quattro control, general UI, there is also a toggle to "hold back arrow to exit app", near the bottom, if that interests you.
Anyway, you've been great thanks.
Click to expand...
Click to collapse
Sent from my HTC Inspire 4G using Tapatalk
I've seen that some are complaining about missing a direct link to the alarm clock.
Here's app that might help:
Nexus ICS Minimal Analog Clock
It's basically a clock widget starts the alarm settings when pressed.
Master-and-blaster said:
Hi there, I think this is my first thread. Might be the wrong forum but I thought I'd give it a try.
The reason I'm posting is because I'm looking for some support concerning the Virtuous Quattro RC3 for DHD. I can't post in the "development" thread because I apparently am a noob. Anyway here goes.
First, my specs:
Phone: Desire HD
ROM: Virtuous Quattro RC3
Kernel: LorDmodUE ICS BFS 8.8 final
Radio: 26.14.04.28_M
Patches:
Camera fix
http://forum.xda-developers.com/showpost.php?p=21930178&postcount=2072
What I'm looking for are solutions for some of the issues I've encountered during the past few days. Here's what I've experienced:
* HW video, not working - No solution, I know. Same goes for youtube etc.
* Camera, works perfectly - Fixed via patch see post above.
---------------
* GPS can't get a fix on signal. Not working. Worked perfectly on ARHD
FIXED
Patch: http://forum.xda-developers.com/showpost.php?p=21962018&postcount=2464
* Apps don't close by themselves, are they running in the background or am I just imagining this? If I long-press the home button every app I've started seems to running
SEMI-FIXED
Just swipe to the left/right.
* Auto-brightness isn't working as well as it should be.
FIXED
Patch: http://forum.xda-developers.com/showpost.php?p=21970997&postcount=2473
* With Wifi on the phone doesn't switch to 3G automatically if I move outside the Wifi area. I have to turn on/off airplane mode and enter pin to get it to work again. Doesn't work to turn Data on/off.
* Can't read SIM-contacts. I had to move all my contacts to my google-account.
* Wifi signal seems to be weak as well, the bars on the icon go down one or two levels despite me being about 2-3 meters from the router.
* Dialer crashed once but I don't know the reason why.
------------------
Anyway, the issues I've listed seem to all be minor issues and they don't bother me too much to be honest. The battery doesn't drain too fast and it's great for normal use (calls, browsing, s/r texts, pics, viewing vids with mx).
But if there's a patch I'm missing or some other type of fix for the issues I've listed, I'd be glad if you could post it here.
Thanks in advance.
Regards
Master and Blaster.
Click to expand...
Click to collapse
Thanks for this posting. I an noob to Virtuous Quattro RC3 so it's really helpful! I've got the fix for the camera (black screen). Anyone know if there is a fix for the video camera. Currently the camera stops responding if I try to switch to video mode..
I don't think there is a video fix right now. From what I have gathered through the ICS threads is that there are camera issues on all dhd/inspire ICS ports because ICS is very different from gb and our devs do not have some if the proper drivers yet.
Sent from my Inspire 4G using XDA App
nine zero one said:
I don't think there is a video fix right now. From what I have gathered through the ICS threads is that there are camera issues on all dhd/inspire ICS ports because ICS is very different from gb and our devs do not have some if the proper drivers yet.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Pretty much yes.
I gave up on Quattro and tried Affinity, not disappointed to tell you the truth.
ICS just felt incomplete I'd rather just wait for HTC to release an official ICS ROM.
AND THEY JUST ANNOUNCED IT!!!!!
Will be long time till we get an ics update,the ics roms are coming up good a I will say try once if you can live without your camera..
Sent from my MZ601 using Tapatalk
question
I asked a question before and no one answered so here it goes again,
I recently flashed this rom coming from another ICS rom, did the whole procedure, wiping then flashing.
The phone booted up alright and still works, but the camera when opened states
"Unfortunately, Camera has stopped." that is all what do I do???
Download Ucam...run at lowest resolution in settings and it works perfectly (on Inspire)...no glitches, good pic quality. No video though, don't think anyone does. Hope this helps.
Thanks for the update. Now that ice cream sandwich is going to officially be available for the Desire HD, this problem should be sorted sooner or later. It's because the official camera drivers are not yet available from HTC.
Sent from my DHD ARHD Touch of ICS using XDA app
Thank you so much, I might revert back to virtuous affinity for now

MIUI.us 2.8.31

Does anybody use MIUI.us 2.8.31 ROM?
The ROM IS working To your phone good?
I flashed (MIUI.us 2.8.31.) to my phone yesterday. Earlier I used a MIUI.us 2.8.10
I’ve found some bugs:
• Usually I’ve got a black screen after unlock,
• The soft keys (home, menu, back, search) doesn’t light,
• I use a HTC headset. The headsets bottoms don’t function. I can’t pick up the phone.
Earlier ROM (2.8.10) doesn’t was these bugs.
Other: How can I use the FM radio. It’s doesn’t work any MIUI ROM for me?
Please help me!
Thanks:
Lacika888
Sorry for my English.
I've been using this ROM since 3 days. It looks great and it's been working well. Very smooth too. I haven't had the black screen on unlock bug at all yet, though I keep hearing about it. I do have an issue of backlight not going off after screen is locked, but that's a bug in the CM10 nightlies that this ROM uses as base. Soft keys not lighting up I confirm. They don't light up at all. I haven't tried the headset issue because my dog chewed up my headset lol.
I started with 2.8.31, so I don't know about 2.8.10. But from what I vaguely remember reading in the OP, is 2.8.10 ICS or JB? If it's ICS, then it is based on aospX by existz, which doesn't have any of these problems.
Sent from my Desire HD using xda premium
thanks
sashank said:
I've been using this ROM since 3 days. It looks great and it's been working well. Very smooth too. I haven't had the black screen on unlock bug at all yet, though I keep hearing about it. I do have an issue of backlight not going off after screen is locked, but that's a bug in the CM10 nightlies that this ROM uses as base. Soft keys not lighting up I confirm. They don't light up at all. I haven't tried the headset issue because my dog chewed up my headset lol.
I started with 2.8.31, so I don't know about 2.8.10. But from what I vaguely remember reading in the OP, is 2.8.10 ICS or JB? If it's ICS, then it is based on aospX by existz, which doesn't have any of these problems.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks four your answer.
Hello to all guys, I'm sorry for my English, I come straight to the point, I installed this rom 28.31 I found a lot of bugs, I had to go back and install the MIUI 2727 I have a big problem with youtube does not work, I know how to fix the problem I searched on google but could not find anything on the web site miui.us.Se someone could help me out, I'd be very grateful:. cried:
1.do a full wipe
2.dont restore system data/apps
3.try usign the rom with full whipe and slowly add the apps to reveal the culprit
I solved it by putting a vwersione old youtube, the new one does not digest well.

[Q] ARC S with JB - proximity sensor issues (CM10 / AOKP / SlimBean / ETC)

Hello,
I have ARC S that runs very well with all Stock based kernels (Ultimate HD, JJ Hybrid, OptiMAX, and others)
I wish to upgrade to the JB, however on all kernels and roms (FXP, AOKP, Lupus) I have the following problem:
when I answer or make call -> the screen becomes black and no key is responding.
when the call ends -> the screen return to normal condition.
seems that the proximity sensor is making this problem (maybe the calibration is wrong with the JB kernels / roms)
how can I solve this case ?
BR,
From what I know, it is normal that screen turns off during call, if you put phone next to ear. Or did I misunderstand anything?
I'm referring to a problem I have:
In all versions of JellyBean when I answer a call the screen becomes black and nothing functions as if the phone thinks its close to the ear (as if the proximity is stuck on 0 distance).
I do not have this problem on ICS versions.
* all versions of JellyBean = cm10, aokp, aosp, slimbean,
I've tried multiple kernels for JB and with all I experience the same.
Anyone knows the reason why proximity sensor is not working properly on cm10 ?
Then it is because Sony hasn't made the libs open-source, so they could be made to work on JB. Due to incompability issues, these bugs occur. Nothing that developers could do at the moment.
Apparently I'm not the only one suffering from this proximity sensor issue.
the effect is huge:
when answering a call the screen does not response any more and I cannot disconnect calls.
I found:
http://forum.xda-developers.com/showthread.php?t=1985539&page=9
Originally Posted by f_zurzolo View Post
Yes the proximity sensor bug is the main reason why I am not using this ROM as well. But check back a few posts. . . the dev said he's gonna fix it. Thanks in advance n1kolaa
Click to expand...
Click to collapse
Since it happens with all JB ROMs, could it be a kernel issue?
Anyway thanks
Click to expand...
Click to collapse
Does anyone know how to solve proximity sensor on the JB roms ?
Does anyone ha any updates on this?
I'm having the same problem and it gets quite annoying.

[Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs

Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
Incredibly(^<Paranoid2.19.30Final Questions:
With my current flash of Incredibly(^<Paranoid2.19.30Final, I am not running any themes and installation should be basically standard (though I did have to flash the October GApps package over it because there was no way to set up a Google account).
1. Aroma: The Revised OP still talks about the Aroma installer (I know that there have been two versions of the ROM zip in the past). When I flashed 2.19.30, there was no Aroma installer. Bad download or mistake in OP? Answered in Post #4.
2. Camcorder: Regular camera and FFC are working correctly. The OP says that the camcorder has 720p enabled at this point. However, I do not see anywhere in the settings to change the quality of the camcorder, and the camcorder is currently recording at 480p. How do I change the camcorder to 720p? Answered by The Man himself in Post #14.
3. Bluetooth in Car: With the various AOSP ROMs, when connecting the phone to my car via Bluetooth (not A2DP, just a headset profile), I get sound but it is garbled beyond belief while ringing. For any music buffs, the sound is basically the first chord of "I Believe In a Thing Called Love" by The Darkness...as the sound of a phone ringing. Per Rushead's post #710, it appears that Bluetooth headsets and in-call voice are not functional, which is a known issue in AOSP ROMs under ICS and JB with no fix. Has this been resolved in this ROM since "everything" works but LED camera flash? Answered in Post #9 via OP for Incredibly(^<Paranoid Collection.
4. Status Bar Clock: I want to eliminate the clock in the status bar. I go in to the AOKP settings via Settings > ROM Control > Clock > Clock Style and select "No Clock". This removes the clock from the status bar. However, when the phone goes to sleep, and I come back through the lock screen, the clock is back. Going back in to the settings as referenced above, the "No Clock" option is still selected...and yet there is a clock there. If my memory serves me, in Aeroevan's CM10 the option would be under Settings > System > Status Bar, but there is no option for the clock there in Incredibly(^<Paranoid. Obviously not a huge deal, but just curious if anyone has a suggestion. Answered in Post #9; works fine in CM10 so who cares.
Any information or assistance would be greatly appreciated.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 helpfully suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Re: ViperInc headphones
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.[/SIZE]
Click to expand...
Click to collapse
great questions. i am in the same situation...a little experience but not enough forum-cred to post in dev.
i'm currently running ViperInc 1.3.1, just plugged in my el-cheapo RCA headphones and they work fine. sorry bro :-/
i'd love to see some answers to your 2.19.30 questions.
johannvonperfect said:
Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Click to expand...
Click to collapse
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Question number 1: that was a kind of op misunderstanding, a previous version included aroma, while the best one does not, your download was fine
Sent from my Incredible 2 using xda app-developers app
brymaster5000 said:
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Click to expand...
Click to collapse
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
This might sound odd. I've been on viper the longest. No lag. I installed super su n un installed their SU. Also got a busy box installer from the market n updated the phones busy box. I'm also running defensed but made sure I popped in rosie, but it's frozen n I'm running nova. Night n day I tell ya.
Sent from my forgotten by HTC Droid Incredible 2. Rooted and Rommed by great minds that haven't forgotten this phone.
johannvonperfect said:
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Click to expand...
Click to collapse
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
vikrantislav said:
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
Click to expand...
Click to collapse
Not that I'm aware of. As I mentioned above, I don't think it's a "hardware" issue, in the sense that even now I have no problems with CM 10, Incredibly(^<Paranoid2.19.30, etc. My best thought was that it may be something with the way the Sense 4 ROMs interact with the hardware, i.e. maybe the kernel on my particular phone? But I have no idea. At some point I will try flashing the "leak" kernel over the VenomINC install.
What I'm more interested in at this point is 720p recording on Incredibly(^<Paranoid2.19.30Final (And I am looking forward to Chilly throwing together a CM10 ROM).
If we keep going back and forth we can rack up enough posts to start posting at the grown-up table :good:
So the revised OP for what is now the Incredibly(^<Paranoid Collection answered a couple of the questions.
Bluetooth phone calls do not work in any of Chilly's ROMs.
I flashed his CM10, and the issue with the clock in the status bar is resolved. This leads me to believe it is an AOKP/PA issue; I am fine with CM10 anyway so no big deal there.
However, when I flashed CM10, the same issue exists with the camcorder. FFC and regular camera work great for photos; there is no option to change the camcorder to 720p.
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Only issues I have with Viper is it will not connect to my media server via the native apps. I also have been experiencing lag but I think it's mainly due to lack of ram as a reboot usually clears it up. Also if you toggle gps off it doesn't work unless you reboot.
johannvonperfect said:
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Click to expand...
Click to collapse
that reminds me, i also have the Sony XLoud disabled in ViperINC
vikrantislav said:
that reminds me, i also have the Sony XLoud disabled in ViperINC
Click to expand...
Click to collapse
I did not install XLoud in the Viper Installer, just went with Beats. As I said in the OP, I know that my issue was previously mentioned but it does not seem like anybody ever found out the cause.
Bluetooth phone calls are not a dealbreaker for me. At this point, if the 720p recording is actually working, I would be happy with CM10 as a daily driver (though I may check out Evervolv as well to see what 4.2 can do). I just can't find the setting...
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
johannvonperfect said:
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Click to expand...
Click to collapse
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
chillybean said:
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
That must have been what happened...I have kept up with the thread fairly regularly and thought I saw that 720p had been figured out, but as you said that must have been before it was pulled. I was confused why nobody was mentioning it in the thread considering it would have been big news.
Chilly, thanks for the response, and thanks for all the hard work you do to make the phone feel like new. We're lucky to have such talented devs keeping our device relevant. Keep doing what you do! :highfive:
To the Mods: that should wrap up this thread if you want to lock it. I do not believe there is an answer to my remaining question about ViperINC and audio through the headphone jack.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
I don't think it was mentioned, but did you try a reflash / redownload?
Probably not going to do anything, but worth a shot.
brymaster5000 said:
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
Click to expand...
Click to collapse
Sweet. I'm locked in my phone till November so I'll be like 1 outta 12 people left with the phone rocking ICS. Sounds exciting
Can usb tethering be done in cm10. I saw the WiFi app thread but nothing on usb.
Not to bump an old thread, but since I still can't post in the actual development thread: Chilly said in Post #1369 of his ROM thread that "No such thing as 100% but yes everything should work other then rotating hard keys bust out the champagne!"
Therefore my question is, once again: how do you change video recording quality to 720p in the camcorder? There still doesn't seem to be an option for it. Any info would be appreciated.

Categories

Resources