OK...I've searched under terms: Joggr strip, Camera fix, volume adjust, etc, etc, and have found no definitive answer.
Just recently flashed my Dash to Ricky's Vanilla ROM...LOVE it! Except now the camera is unresponsive and the volume/JOGGR strip does not work. Worked fine with WM5. I've tried several different 6.1 ROMS and none of them make a difference. I've hard reset several times, no difference. Made sure the camera driver is "Enabled" in My Settings...still nothing.
1. Is there a fix for the camera that I'm unaware of?
2. The volume strip doesn't have to work...it's usually a bother anyway...BUT, is there at least a way to adjust call volume without using the strip? At this point I can't even do that, and THAT is a problem.
Current version of ROM is Ricky's V24 Vanilla
I'd be happy to search for the answer if someone could even direct me to the right search term, etc...
Thx for your help
*UPDATE/EDIT* OK, just decided to adjust clock speed up a bit (to 240)...rebooted and decided to hit the camera button for the 1000th time. Bam! Camera comes on but it looks like a digitized image in purple and black...not exactly a fix but it did get me closer. Any thoughts? STILL have no way to adjust call volume, royal pain in the arse.
still nothing?
No advice on this one?
Link to camera
a few people are having the same issue with the camera.
Not sure if there is a fix.
Jogger Bar link.
Read the threads. You might find something to help you out.
'preciate it...Those were the only two threads I could find in my previous searches.
Neither one had any solutions that seemed to apply. Just a bunch of repetitive posts on how to use the touch strip for scrolling/etc...mine simply won't respond. I even swapped out the entire board with an extra one from a previous Dash (with a broken LCD screen)...and that one did the same.
I'll check out HoFo and possibly look into different registry edits (the only thing I haven't tried with my Dash or my 8525, I guess now is a good time to learn.) If I could reassign the IN CALL volume control to a different button I'd be happy(er). The camera is hopeless as far as I can tell.
Just so you know, it's not the ROM
I would just let the thread die but since 50+ people took the time to read it, I figured I'd go ahead and update.
I opened up the phone again (had previously swapped out boards from an extra dash) and upon close examination found that the ribbon going from the jogger had a tiny tear in it. I took the jogger strip off of the old dash case (very simple, it's just "glued" on) and swapped it out...carefully this time.
It works!
Now I just have to figure out why the camera is not working...that, I suspect, is a software prob.
turn overclocking OFF and try the camera feature again.
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
As for #4: Not all programs have a landscape mode natively.
jlczl said:
As for #4: Not all programs have a landscape mode natively.
Click to expand...
Click to collapse
Thanks. I figured that she might be using an app that doesn't work in landscape since I haven't come across it yet.
Also, regarding #2, I should have mentioned that I have 4.48.25.20 as my current radio.
1) I use Jabra 2nd gen and mine is working great. A little crackling sound but nothing major.
2) Depend on the area you live and coverage, you might want to try different radio. I have stock radio and mine is working great. Better than my fuze was actually. I can get 1 or more bar than Fuze and call quality is super clear. No drop calls yet while I had like 2-3 drop calls with my fuze.
3) I am still running on stock rom and yes indeed it's slow and sluggish. I have to reset the phone physically sometimes. I am not too happy about moving the battery cover just to reset as well. With custom rom, the phone will be snappy since some people are running custom rom with their Tilt2 already. I am in the same boat as you. Waiting for the complete stock rom dump. Until then.
4) Not all the landscape work as you have already found out.
I use a BlueAnt and my BT reception is good.
I thought mine was slow at first but as I tweaked it a bit, turning off alerts and pop ups, it SEEMS to be more of what I expected.
Haven't had a dropped call issue.
But, I am thinking that I will flash the ROM when something comes along.
Thanks for the replies.
FWIW, my wife uses a Jawbone 2 and the crackling is noticable on both ends of the call. I use a first-gen Jawbone and have nocticed the crackling as well. It seems that it works better when the phone is on the same side of my body as the headset. I did not notice this crackling on my Dash and Blackjack 2 nor her Dash.
I think the dropped calls problem is definitely area related. My wife is currently out of town and it hasn't dropped her calls at all that I know of. And when I'm at home, it's no problem. It's just that on my regular commute, it drops 5-6 times where my previous Dash and Blackjack 2 only dropped once or twice occasionally. I've only made my commute once since I got the Tilt2, so maybe there were some coincidental network issues. That said, call quality has been very good.
I just turned off the new SMS notifications. I've also removed a couple of tabs that I know I'm never going to use (stocks, AT&T, and music) at that seems to have made things a little snappier too.
HAH! Not more than 1-2 minutes after I posted my last message (from my laptop), I went to use the internet connection on my Tilt2 and it locked up. A message appeared asking if I wanted to send error details to MS and then my phone turned off.
Another thing I've noticed is that Opera takes a *really* long time to switch from landscape to portrait. And it seems to be significantly slower than Opera Mini was on my Dash and Blackjack 2. Maybe because Opera Mini is Java-based on those platforms?
My wife is now reporting that her Tilt2 won't unlock unless she slides open the keyboard. Her Exchange connection requires the phone to automatically lock and require a PIN entry. I suggested tapping the power button but that doesn't wake it up, either.
Any suggestions? I'm thinking she might have a bum unit since mine isn't having nearly the trouble hers is.
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
SoapDoctor said:
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
e_dogg said:
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
Click to expand...
Click to collapse
Don't run to fast with my advice, I'm a complete noob but hard reset would be the first thing I would try. It is a microsoft product after all and I'm pretty dman lazy to run to the store first.
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
I can't really help you out too much, but I haven't been experiencing many of these problems at all, and I'm still on the stock rom, just cleaned it up a bit. Spend some time on the forums and you'll find some good quick hacks to try before you try a new rom.
superrrguy said:
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
Click to expand...
Click to collapse
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Linear2202 said:
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
Click to expand...
Click to collapse
Good info about your Jawbone issues. I have an old Plantronics headset that I'm not really using anymore. Maybe I'll give that one a try to see if it's just that Jawbones don't like these new versions of HTC phones (it worked great on her Dash).
As for the photos tab, it seems to work ok. Though the first "flip" through the pictures seems to be slower than subsequent flips.
I found that hiding tabs I won't be using like the "AT&T" tab seems to help speed things up. I think I have 3 or 4 hidden.
amurch said:
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
Click to expand...
Click to collapse
Thanks - good to hear of your sucess with the NRG ROM. That's the one I'm planning on trying since I really like the 6.5.1 changes.
redpoint73 said:
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Click to expand...
Click to collapse
Yeah, Touch FLO 3D sure is purty. And, now that I have the tabs sorted and hidden the way I like, it's very easy to use.
Just an update...the Energy ROM seems to have cured the dropped calls. With the stock AT&T ROM, calls dropped about 5-6 times on my regular commute. With the Energy ROM, not a single one!
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Linear2202 said:
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Click to expand...
Click to collapse
Yep - happened quite often with the stock AT&T ROM. I don't recall seeing it after switching to the Energy ROM.
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?