Hello all, after some extensive messing with the registry settings for the camera, my phone now seems to take photos in the correct orientation here's what i changed i think!!
HKLM\software\HTC\Camera\common\rotate set value to 0 (may already be 0)
HKLM\software\HTC\Camera\image\enableencodeportrait set value to 0
i know this is relevant to the main thread however its got too long and i fear many soloutionm may have been lost. it may also require a soft reset. i have extensively messed with the values for this and it kinda suddenly worked however i think this is what is required. i have not installed any rotation applications, nor have they been installed since a hard reset so that has no influence in my case.
i hope this helps, if not i will attempt to do a more thorough comparison with an unchanged regristry to get the definitive answer
regards
(all mods made at your own RISK!!)
Mat
this working at all?
Not for me . These were the default settings that I already had and I have the bug. I'm playing with other settings now and will report back if I find anything.
Related
Before you tell me to search; I have been for well over an hour. Screen lag, screen, lag, rotate, slow rotation, blah, blah, blah, blah, blah has turned up nothing for me yet. I am on an ATT Tilt, stock rom minus some bloatware, very clean almost nothing extraneous installed. When switching to landscape, it would take maybe a second to rotate. After playing a bit with KaiserTweak and MemMaid (no other changes) it can now take up to 4 seconds for initial rotation. Switch back to portrait is still very quick. Can't figure out what change may have done this, any thoughts?
You are experiencing the lack of acceleration for the video chipset on these units. There is a petition going for HTC to provide a DirectX compliant video driver a couple of stickies up.
Actually, I've been using this phone for 2 weeks now without this problem. I remember reading posts on here somewhere about this issue, but seeing as my rotation was almost instantaneous, I thought maybe this was only nitpicking. Now that I have played with the registry some, I have the same problem. My screen rotation was usually about 1 second. Problem is, I made many of the recommended changes for better performance, and I don't know which could have caused this.
Try setting all your KaiserTweak settings to the default, and see if it makes a difference. Then get back to us and tell us if it does .
Okay, had to leave things alone till I got back from work. The problem with just setting everything in kaisertweak back to default was that I had played a good deal with the registry before I ever installed it, so default was not going to get me back to my starting point anyways. I did try to go back to default though but that just screwed something else up. So after completely screwing up my registry, I did a hard reset, and lo and behold, quick rotation. My switch from portrait to landscape is about a one second, or less, delay again. I reinstalled all of my programs and checked it again, and it still works great. I really believe my delay was caused by something in the registry and not driver related because it works great now. Also, I am in no way blaming kaisertweak or any other program here. I simply believe one of the changes I had already made was somehow conflicting with one of these programs. For anyone that thinks this is simply driver related; maybe we should be looking a little harder at some of our registry values.
here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Lem0nHead said:
here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Click to expand...
Click to collapse
What rom are u using? Sometimes its good to make a hardreset.
Mikulec said:
What rom are u using? Sometimes its good to make a hardreset.
Click to expand...
Click to collapse
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Lem0nHead said:
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Click to expand...
Click to collapse
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Flying Kiwi said:
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Click to expand...
Click to collapse
I couldnt say it better. I flash and hardreset my phone very often, its a little bit painfull but u will get used to it.
Do not be afraid of the hardreset.
just letting you know I remembered in this same day I had the battery problem, I changed a setting on IP Dashboard (configuring it to keep max 500 KBs history)
I now removed IP Dashboard the problem stopped
will try some other program later, or the old config
thanks
All right, so a while ago say..few hours or a day ago, I dropped my phone. Nothing seemed wrong, everything was working fine. Until I decided to go play Abduction World Attack. It's a game where you tilt the G1 and the little character moves according to how you tilt it. Surprise Surprise I ran into my problem. The little avatar wouldn't move and it was just stuck there no matter how I turned my phone. I also just noticed that auto-rotate won't work. I believe it's because the accelerometer is broken...Anyone have any advice on how to fix this or calibrate it? I've tried calibrating inside apps that use the accelerometer. I've searched but to no avail. Help will be appreciated Thank-you.
[Edit]: A wipe has fixed this! =)
If your under warranty, you may want to try and get it exchanged. Let T-Mobile/HTC know that it just stopped working.
If you are out of warranty, you can attempt at looking for a solution by taking apart the phone. The official manual is here
The manual has all of the disassemble instructions. Hopefully that will lead you to a solution.
Sounds like it could be a hardware issue but no harm in testing to see if it is a software one. Tried rebooting the mobile? If so see if other programs like Bubble works. If not then a final resort would be a reflash to at least eliminate the software side of things.
If its no go then best to try and get it exchanged...
I've fixed it guys ^^ Seemed like a wipe would do it. I changed to the hero build for a second and then reflash CM after a wipe and accelerometer is fixed. Thanks for the suggestions though! Greatly appreciated
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
NeoBlade said:
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
Click to expand...
Click to collapse
Sure. OP and title has been updated!
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
whatchamccallum said:
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
Click to expand...
Click to collapse
Most likely a hardware problem then mate. You could try un-rooting and see if the accelerometer works.
If I install RC29 then the accelerometer works without issue. So that rules out hardware issue.
Here is another thread I found that goes in much more detail about what I am experiencing.
http://forum.xda-developers.com/showthread.php?t=533749
so far there isn't any movement on this thread. I'm surprised that this issue isn't more wide spread.
I just had the accelerometer on my HTC Sapphire go belly up.
Auto-rotate was broken, compass apps wouldn't initialize, tilting maze games would slowly move the ball to the top left side regardless of actual tilting, etc..
Reboot didn't fix it. However I did have a file under /data/misc/akmd_set.txt and most of the values in it were set to 0.
I renamed that file to akmd_set.txt, then killed akmd, per instructions in a neighboring thread.
akmd rose from its ashes, a new akmd_set.txt automagically appeared, with lots of different numbers for each value in it. All my accelerometer-depending features were happy again.
so yay, and all that.
As a side-note, I've been playing with some not insignificant magnets on my desk, and I'm wondering if abnormal magnetic fields around my phone might have caused the accelerometer miscalibration?
Good for my G1 too.
Kudos to the OP, this solution worked perfectly on my G1 with the same symptoms. Many Thanks!
I'm using a Z3 compact with CM12.1, that means unlocked bootloader and no more warranty. All of sudden, the main/back camera has stopped working. It is black, OSD still working, front camera still working, other camera apps don't make a difference.
I don't know if that is a problem of some recent CM nightly or something else. Browsing the web I get the idea that this symptom also appears on stock firmware, and it seems that nobody has yet found a solution (neither factory reset nor hardware replacement of camera help).
My question:
Has somebody else this problem, is it CM related?
Is there a solution other than complete phone replacement?
Is there some logfile I might consult to find out if the camera HW should be replaced? I don't want to disassemble the phone only to find out that the camera still does not work.
Thanks!
Must be a software problem related to the nightlies unstableness.
Try flashing a stock firmware to see if it gets fixed.
I'd rather avoid going back to stock. Reverting to a previous CM nightly (from a time when the camera definitely worked) did not help.
Do you have any reports of CM nightlies problems with the camera? I'd love to hear that, because it would mean that I don't have hardware problems. However, searching the web I only found many reports of the camera suddenly stopping to work, but nothing that this is related with recent CM nightlies.
But if it's a Hardware problem, there should be a logfile somewhere, or?
just did trial and error on the same problem with the black camera for 2h
i did however not install CM to cause this
I have a custom debloated rom, which worked fine.
I had to switch phones so i did a TW recovery backup.
Changed the filename on the new phone so it is found when restoring.
Restored. Everything works well, except the camera app.
When i wipe from the systems menu i lose all my data but the camera app works again.
But of course i need my data exactly the way i had it backed up.
Tried all kinds of things around the camera app, backing and restoring with and without kernel, always the same.
Back camera stays black.
This is similar to other reports I found in the web: The hardware works (which means replacing the sensor is of no use), but somehow it is no longer accessible. I tried different hw info apps, which all report the back camera with all specs and no problems, but no camera app is able to get it to work. I flashed several new CM nigthlies since, it doesn't help
I don't really know how to read logs (with 3CToolbox), however this line caught my attention. Maybe somebody here can interpret it:
07:45:48.427 caladbolg( 301)
9530027 cald_parammgr_generic.c (4299) 301 E [PRM] Fail: camera eeprom status
Since my Kernel debugging skills are also not existent i simply factory reset it and transferred my data with titanium backup.
Everything works fine now.
So my advise is to stop wasting your time with it too, just go back to working software
Unfortunately reverting to stock firmware did not repair my camera. Afraid I have some hardware defect
No resolution to this problem it seems
My problem is the phone will not auto rotate at all. I tried evry thing look all over on how to fix it and still with no luck at all. I'm on 4.4.2 dynamic 7.1. It's really starting to bother me. Do anybody know how to fix tthis issue?
Try this app:
https://play.google.com/store/apps/details?id=com.googlecode.eyesfree.setorientation&hl=en
I had the same problem, the app aj_vogtman posted sort of worked for me, it worked for manual rotation but the automatic setting still didn't work. Have you recently changed anything in /system? Never figured out exactly what caused that for me, but I think it started around when I was removing some apps, converting other system apps to user ones, integrating updates, stuff like that so I think it must have been a subset of one of those in my case. The manual rotation worked fine for my use case up until I accidentally bootlooped my phone, ended up finally upgrading to Lolipop and it started working again for me which confirms it wasn't hardware in my case at least. So I guess try reinstalling your ROM back to its base /system to see if that fixes it for you, and if it does document any changes you make so if it happens again you'll know what caused it?