Just a normal man thinking in a high voice!
Ok so i had a touch screen failure of my HD2 during usage of Android build; maybe it's a coincidence maybe not! But what annoys me is that i was preserving it nearly intact: never fell, no water, no heat, no cold, no underclocking or overclocking (except that smartass governor dims cpu to minimum by default when screen is off)
Fixed it in the end and cost me nearly 1/4 the price of the phone (120$)!
So let's face it! HD2 was DESIGNED for Winmo 6.5 and not for android! And please nobody try to convince me that it doesn't have any side effects!
Well, it's like using diesel oil for a regular gasoline car! There has to be some disorders! Or using a BMW engine on a Peugeot! Maybe the chassis will handle it but not the cooling system or the clutch or the wheels or etc....
So let's begin with some of the concerns that i think of and excuse me if some questions look silly, i'm neither a technician nor a developer! (i know many of them have some basic answers, but here i'm questioning even these answers):
1-About touch screen:
Well HD2 screen is capable of 128k colors if i remember good while android GENERATES or produce 16M colors; couldn't that have affected the pixels of the screen itself?! Couldn't that be warming these pixels to higher rates than normal rates that this screen can withstand?! Maybe the system is obliging in a way or another the pixels to display those colors while they can't physically so the are failing at the end?!
(I simulate it to overclocking of the CPU: making the CPU run at higher speeds than the original ones that it was designed to work under will make it fail in the end after some time)
(and please don't tell me this has nothing to do with the OS, bcz let's not forget that the screen was limited to 65k colors in winmo while it is capable of 128k colors, so OS does matter)
2-About CPU/battery/cell temperature:
I couldn't separate those 3 characteristics coz they are highly related! (and even related to the screen )
If we overclock ==> cell temp increase
If we underclock ==> cell temp decrease
And both are bad logically for the phone, because simply those smart engineers at HTC that designed the phone knew what were they doing; that's why they kept CPU out of reach of children p us) because it will regulates the temp of the cell phone automatically to optimal values!
Anyway, who said that optimal values for normal HD2 (winmo) with it's 64or128k colors screen are the same optimal values for an android phone with it's 16M colors screen!?
So my touchscreen failed suddenly while in android, couldn't the smartass governor was the reason behind it bcz it dropped the cell phone temp to less than 26deg in idle and something in the screen failed/broke?!?
What about the cooling system/ventilation in the phone?!?!
Maybe because of its high power consumption (thus temperature) an android phone is designed to ventilate/cool the system in a manner that a winmo can't do like our beloved HD2!?! Maybe that's why our phones gets so hot during heavy use!?
Many other questions come to my mind...Just wanted to discuss some points, and evidently many other points that you will share to see if using android on our beloved HD2 is safe after all or not...
Cheers
I've read about your touchscreen failure in another thread, and while I'm very sorry for you, how can you be sure it's because of Android? I'm not saying it's not possible, but just running an OS during a failure doesn't mean the OS caused it, I can imagine some people have had touchscreen failures on WinMo too.
Just trying to keep things a little in perspective here.
1. The screen is capable of 16M colors (not 128k). WinMo only supports 65k, and I believe Android does at this point too. Pixels are unrelated to the touch sensitive part anyway.
2. Overclocking can indeed have serious consequences for your CPU (and possible surrounding parts too), and should *always* be done with caution (better to refrain from it at all actually, the small performance gain isn't worth it). I believe all kernel devs indicate the possible and imminent danger of overclocking.
Underclocking can't be a problem though, that's obvious. Extreme cooling can destroy parts, but heating it up less than usual is still not at all the same as cooling something down.
Again, I'm sorry for what happened to your phone, but I think you're somewhat overreacting.
Edit: a more likely explanation for an Android-related failure would be that your CPU somehow went insane and produced too high temperatures, breaking stuff down. This isn't typical behaviour though, and can almost always be prevented.
Life Engineer said:
Just a normal man thinking in a high voice!
Ok so i had a touch screen failure of my HD2 during usage of Android build; maybe it's a coincidence maybe not! But what annoys me is that i was preserving it nearly intact: never fell, no water, no heat, no cold, no underclocking or overclocking (except that smartass governor dims cpu to minimum by default when screen is off)
So let's face it! HD2 was DESIGNED for Winmo 6.5 and not for android! And please nobody try to convince me that it doesn't have any side effects!
Well, it's like using diesel oil for a regular gasoline car! There has to be some disorders! Or using a BMW engine on a Peugeot! Maybe the chassis will handle it but not the cooling system or the clutch or the wheels or etc....
So let's begin with some of the concerns that i think of and excuse me if some questions look silly, i'm neither a technician nor a developer! (i know many of them have some basic answers, but here i'm questioning even these answers):
1-About touch screen:
Well HD2 screen is capable of 128k colors if i remember good while android GENERATES or produce 16M colors; couldn't that have affected the pixels of the screen itself?! Couldn't that be warming these pixels to higher rates than normal rates that this screen can withstand?! Maybe the system is obliging in a way or another the pixels to display those colors while they can't physically so the are failing at the end?!
(I simulate it to overclocking of the CPU: making the CPU run at higher speeds than the original ones that it was designed to work under will make it fail in the end after some time)
(and please don't tell me this has nothing to do with the OS, bcz let's not forget that the screen was limited to 65k colors in winmo while it is capable of 128k colors, so OS does matter)
2-About CPU/battery/cell temperature:
I couldn't separate those 3 characteristics coz they are highly related! (and even related to the screen )
If we overclock ==> cell temp increase
If we underclock ==> cell temp decrease
And both are bad logically for the phone, because simply those smart engineers at HTC that designed the phone knew what were they doing; that's why they kept CPU out of reach of children p us) because it will regulates the temp of the cell phone automatically to optimal values!
Anyway, who said that optimal values for normal HD2 (winmo) with it's 64or128k colors screen are the same optimal values for an android phone with it's 16M colors screen!?
So my touchscreen failed suddenly while in android, couldn't the smartass governor was the reason behind it bcz it dropped the cell phone temp to less than 26deg in idle and something in the screen failed/broke?!?
What about the cooling system/ventilation in the phone?!?!
Maybe because of its high power consumption (thus temperature) an android phone is designed to ventilate/cool the system in a manner that a winmo can't do like our beloved HD2!?! Maybe that's why our phones gets so hot during heavy use!?
Many other questions come to my mind...Just wanted to discuss some points, and evidently many other points that you will share to see if using android on our beloved HD2 is safe after all or not...
Cheers
Click to expand...
Click to collapse
The "TOUCH SCREEN" has nothing to do with the CPU, therefore no amount of overclocking will damage your "touch screen".
Has your pc monitor ever got damaged by overclocking your pc's cpu? NO
Just because your screen stopped working in Android doesn't mean that it was caused by Android.
The GPU driver would limit Android or any other OS from forcing 16m colours on a 128k screen therefore no damage would be caused to the screen itself because it is limited by the driver. The driver tells Android (or any other OS) which resolution and colour depth is supported and will only support that. Just because Android is capable of 16m doesn't mean it will force that colour depth.
This was simply a manufacturing defect in your screen and could have happened at any time, it could have happened in WinMo but just happened to happen while your phone was booted into Android.
Also be aware that the screen is TFT, and there is a separate layer called the digitizer above the actual TFT screen which senses the touch. They are separate components, therefore the screen itself isn't a touch screen.
if devs or experience users can post wats the maximum temp and ma a hd2 device could take that would realy help us alot to see if a built is working normaly or pushing our hardware excessively..mayb juz a gauge like say over 36 degress is a risk or sumting like that..info like this will realy help us users
Stop overreacting, its just a hardware failure, just get it fixed and youre good to go.
derycklong said:
Stop overreacting, its just a hardware failure, just get it fixed and youre good to go.
Click to expand...
Click to collapse
Man no one is overreacting! I fixed it (maybe you didn't read the thread after all) and i am willing to use android again!!! However, if we shacked our brains a bit to see if android has any down effects on our cells, it wouldn't be such a bad thing!!! Nothing to loose, and maybe many things to win after all!
I wanted to put down a whole story on how stupid your comparison's are and how you should leave the thinking about this stuff to ppl who actually know what they are talking about.
Android wont destroy your hardware its a bare bone operating system with custom drivers to run on our HD2. Software imput cant realy damage your hardware unless your overclocking.
Take it from ppl who know what they are talking about seeing you seem to be clueless
shuntje said:
I wanted to put down a whole story on how stupid your comparison's are and how you should leave the thinking about this stuff to ppl who actually know what they are talking about.
Android wont destroy your hardware its a bare bone operating system with custom drivers to run on our HD2. Software imput cant realy damage your hardware unless your overclocking.
Take it from ppl who know what they are talking about seeing you seem to be clueless
Click to expand...
Click to collapse
No need to be rude! That's what i said in my post, i'm not a technician or a developer, i just have some concerns/questions and i need to be insured!
Besides, i am pretty sure that many others have many other concerns/questions!
That's why i titled it a "discussion"!
So if you are ready for a good discussion welcome; if you are not or think yourself much highly educated to discuss such silly ideas you can keep you mouth shut like many people did!
Regards
Software just doesn't work like that.
If any, the only side-effects that I can see is that we are using the Hardware Buttons more often, therefore they might fail earlier using Android instead of WinMobile.
The car comparison isnt really good.. Its more like when you buy a computer from the market with preinstalled windows os and put a linux on it. It wont kill your pc. It may not work as intended because of driver issues, but if set properly, there should be no problem. And as far as i know, its not that easy to overheat a cpu, because there is a hardware security built in, so your mobo knows what to do. It will just shut down. Sure,you can have bad luck and your cpu can die. I dont overclock my HD2 (only for benchmarking maybe), but i concider myself as a hardcore pc overclocker (like 15 years now), so i am aware of the potential risks and know what i am talking about
I agree with Greg on this one
Hardware is hardware on a computer..
If the correct software is written for it it will run.
I.e i run emulators on android and thats emulating the 68000 chip set no problems there.
But most damge you will cause to your phone is over clocking the CPU until it dies..
Reminds me when used to run windows 3.1 on my old AMiga
If this puts your mind at rest and stops people flaming.
No your touch screen failure was unrelated to Android. The cpu temps and screen res would not have been related. Had you had cpu or screen res/pixel related issues your symptoms would have different.
There are some risks to android, the worst of them being imho your battery going flat when your desperately trying to phone for a lift because the trains and buses have stopped and it's bloody cold outside (as I found out last week). However what I'd suggest is rather then non-devs making uneducated guesses we leave threads like this to the devs who can state specifically what the risks are.
Well, the worst that can happen, is killing the phone. happend to me. I started android, went outside the room for a minute and when I came back, the phone was dead and awfully hot. Fortunately htc repaired it ...
greg17477 said:
The car comparison isnt really good.. Its more like when you buy a computer from the market with preinstalled windows os and put a linux on it. It wont kill your pc. It may not work as intended because of driver issues, but if set properly, there should be no problem. And as far as i know, its not that easy to overheat a cpu, because there is a hardware security built in, so your mobo knows what to do. It will just shut down. Sure,you can have bad luck and your cpu can die. I dont overclock my HD2 (only for benchmarking maybe), but i concider myself as a hardcore pc overclocker (like 15 years now), so i am aware of the potential risks and know what i am talking about
Click to expand...
Click to collapse
Now that´s a nice comparison... but still, the operating system as a whole, means including hard- and software, is a highly complex entity.
Concerning LC displays, you can actually kill them if the power on sequence (eg. the voltage), which drives the display, is wrong. Depending on the display, there is a certain range of voltage which is fine, but below or higher still can produce problems or even permanent damage. Please don´t forget the complex structure of the LCD´s in our HD2´s.
To concur with some of the above posts, I have a computer that I have running Windows 7 on. I have also run XP and Vista on it.
Additionally I run Linux on it.
And if that were not enough, I am brave enough to admit I run OSX on it.
None of these affect any aspect of my hardware.
Now I do believe I do not have a large enough power supply to run my two hard drives, two optical, dual video cards and pro audio card. But that is a hardware issue, as the OP's issue clearly was hardware failure.
And yes, usage does affect computer/mobile life, no matter the OS it is running.
Life Engineer said:
No need to be rude! That's what i said in my post, i'm not a technician or a developer, i just have some concerns/questions and i need to be insured!
Besides, i am pretty sure that many others have many other concerns/questions!
That's why i titled it a "discussion"!
So if you are ready for a good discussion welcome; if you are not or think yourself much highly educated to discuss such silly ideas you can keep you mouth shut like many people did!
Regards
Click to expand...
Click to collapse
Again you stated in your first post dont try and convince me that it was not android that killed my toutch screen. So thats why i was rude ppl who say stuff like that in a opening post while saying you want a discussion is just useless.
winmobile screen failure
if this were any assurance to go by, here's my story: I had a screen failure of my hd2 back in the time when I was running it with windows mobile only - it simply would not respond to touch at all.. fortunately, htc has repaired it and I've been assured that such problems might happen to some handsets from the first months of production... my screen (or was it digitizer) was apparently replaced by a newer version/model... Since then everything has been running very smoothly on my hd2, and I've been testing all sorts of android versions available on this forum.. no problems with the screen or anything whatsoever...
Your concern are not logical to begin with. First of all: Android is a piece of software, that runs on top of Windows Mobile. It won't change anything. It is self containing. So it's like any other App you downloaded from the Windows Marketplace. Secondly: The gamut of Android or WinMo has nothing to do with what the LCD is really able to produce. If you turn down Windows 7 16bit Colordepth, you'll only get 16bit. If you crank it up to 32bit and your monitor is only able to handle 16bit, than you'll see 16bit colors. No pixel will overheat. And the last point: Underclocking won't damage you CPU. It will even increase the lifespan of it, because it does not have to process as many inputs and outputs within each second. If you just run Winmo, it is much colder than using an app.
It is just a hardwarefailure, nothing more. Happened to all of us at least once.
NessD said:
Android is a piece of software, that runs on top of Windows Mobile. It won't change anything. It is self containing. So it's like any other App you downloaded from the Windows Marketplace.
Click to expand...
Click to collapse
Wrong.
/Two cents,
My phone’s touchscreen broke while using Android. I eventually found my “Back” key is somehow interfering with the touch, and now when it happens I need to press the key many many times to stop it jamming the screen’s input. Very annoying but luckily not so serious to need replacing (yet).
As stated above, I think hardware-wise the biggest issue with Android is that you probably will use your buttons more, and as your device is likely to be over a year old, it’s possible you’ll see these give way more. But *shrug* what can you do? Every hardware has a shelf-life. And my hardware fault may well have occurred just as easily on Android.
//Edit: *On Windows Mobile
Related
Just FYI...
Reminiscent of my Diamond, when actively using the HD for a prolonged period, the battery area heats up almost as much as on the Diamond (plus I swear I just noticed a little screen dimming/flicker on it a short while ago - exactly as my Diamond does!)
It's not something that, on it's own, bothers me enough to attempt a re-flash (on the diamond anyway, given I'm not really very au fait with such things and really don't want to brick it...) but something I know was addressed in some of the cooked ROM's for that - so I guess you guys want to hear about issues with the HD/Blackstone as well.
This happened on my old Kaiser too, often if it was being used as a GPS for any prolonged period - it seems to be an issue with the Qualcomm chipset, and it's pretty shameful that it's still occuring on brand new devices. I don't think it's very healthy at all - overheating like this could easily shorten the lives of other electronic components even if the chip itself can take it, and it will be bad (potentially even dangerous) for the battery as well. There's some very poor hardware design going on here somewhere.
This also happens on my asus p750, so i think it is normal that devices get hot when you use gps or hsdpa.
OK
I agree this phenomen only occur using GPS.
But happens on all the hTC device with builtin GPS like Cruise,Dimond and now Blackstone.Don't know is this very healthy for the device.
Well I hate to say it, but my iPhone never runs hot, despite having a faster processor inside. It's not good enough to say "it's fast so of course it gets hot" - they could have put a Core 2 Duo in there and that'd be really fast, but it would also catch fire after a couple of minutes. The trick with mobile processors is to make them run fast enough, and cool enough, to do the job safely and well - and I think HTC (or perhaps Qualcomm) are pushing that margin too far, somewhere along the line.
Make no mistake, everytime it overheats like that, it's having a big knock on effect on your battery's health, and on the lifespan of various other components inside.
boba23 said:
Alright man, I can't judge it yet, since I won't get mine till tomorrow. But what you are saying here is simply .... well strange.
Click to expand...
Click to collapse
Not strange, just common sense. Every component has an operating temperature range, and the closer it gets to the top of that range, the more strain it's being put under.
You seriously think that HTC puts out devices, that they haven't tested for operating within a safe temperature range?
Click to expand...
Click to collapse
No, of course not, they have to gain FCC approval after all. They'll be within safe ranges, and there'll be a designed-in behaviours for when those ranges are exceeded (eg immediate shutdown), but that doesn't mean these are the best possible hardware designs or that these operating temperatures are particularly healthy for the device's longevity, it just means they aren't going to explode. Probably.
I really don't think unless the back of the device doesn't get REALLY HOT, that this will influence the device lifetime in any way.
Click to expand...
Click to collapse
"REALLY HOT" is a pretty subjective measurement - I'd say my Kaiser did get "REALLY HOT" on some occasions, and there was an immediate influence on the device's behaviour like apparent battery drain when this happened. I wasn't alone in experiencing it either. As far as its longer lifetime goes, then of course it has an effect. The battery chemistry in particular is very sensitive to temperature extremes.
I got a T60p notebook, which runs very warm under load. If you put your hand on its back you feel it's really, really warm there. That notebook runs absolutely fine for 3 years now. No problems what so ever.
Click to expand...
Click to collapse
That's a notebook - it has an active cooling system that draws cooler air over the surrounding components, and vents hotter air out the side. More than that it's also much larger with much more space in and around the components to allow the heat to dissipate. Phones like the Touch HD have none of that - not even a sidevent let alone a fan, and zero empty space inside - meaning pretty much 100% of that excess heat is being absorbed by all the other components. Not healthy, and not good hardware design - there's a reason why your T60p would never have been designed that way.
Boinng said:
Well I hate to say it, but my iPhone never runs hot, despite having a faster processor inside.
Click to expand...
Click to collapse
if you do a search online you will find out that apple downclocked a perfectly good 667MHz cpu to 400 MHz. On top of that, the reason it runs cool and seemingly running fast is because it's 400MHz for only one program (there is no multitasking, except core applications that came with apple). Also iphone's GPS doesn't update as fast I blieve 1Hz, instead of 5Hz.
ah yes - foolish apple for underclocking that chip and producing a phone which runs perfectly cool, and still faster than any WM device I've ever used. If only they used overstretched Qualcomm chips instead, eh ?)
Say what you like about the Iphone, but the Qualcomm processors HTC have wedded themselves to are junk, plain and simple.
As for the GPS and multitasking - well the GPS seems to be far more sensitive to movement than my old Tytn II was so I doubt what you say is true, but if it is then clearly HTC's hardware advantage is getting lost somewhere in poor software. Multitasking - well the iPhone multitasks as much as my kaiser ever did, given that I was always precious about closing background apps down anyway to save battery life and memory - the iPhone still does it's phone thing in the background of whatever I'm doing, still plays music while I write an email, all that kind of stuff - and it's still much, much faster at doing anything than the kaiser ever was, despite the "same" 400mhz processor.
Boinng said:
ah yes - foolish apple for underclocking that chip and producing a phone which runs perfectly cool, and still faster than any WM device I've ever used. If only they used overstretched Qualcomm chips instead, eh ?)
Click to expand...
Click to collapse
Didn't you read what he said? iPhone doesn't multitask anything like the HD or other WM devices for that matter.
elmarko99 said:
Didn't you read what he said? iPhone doesn't multitask anything like the HD or other WM devices for that matter.
Click to expand...
Click to collapse
I read every word. Maybe you should have read what I said?
boinng said:
Multitasking - well the iPhone multitasks as much as my kaiser ever did, given that I was always precious about closing background apps down anyway to save battery life and memory - the iPhone still does it's phone thing in the background of whatever I'm doing, still plays music while I write an email, all that kind of stuff - and it's still much, much faster at doing anything than the kaiser ever was, despite the "same" 400mhz processor.
Click to expand...
Click to collapse
Still i dont understand why you people worry about longivity, since is more likely you're gonna change the phone to the 2nd-3rd newer model availabe, if not the next one.
The devices get hot because they offer so many features (eg multitasking) and I am sure they would run within specs. So far I havent heard anyone saying that any HTC device caught fire.
btw iPhone sucks!!! Unless you want a toy, WM devices are mostly business oriented even though they do most of the things that iPhones do.
leftkats said:
Still i dont understand why you people worry about longivity, since is more likely you're gonna change the phone to the 2nd-3rd newer model availabe, if not the next one.
.
Click to expand...
Click to collapse
Plus htc give you a 2 year warranty.
from where to buy parts
hdwoiqhiodqo
You have a faulty device. Just send it back and ask for an exchange.
And no, it has nothing to do with the rom or the OS installed on it.
I have to say that my SHift , while installing Age of Beauty, had a blue screen of Death and never woke up again properly.
The fans acted strange and no boot, no Bios.
Of course, I also think it has nothing to do with the ROM , but it is curious...
guigqiugcdiuq
My god, I see a witch. We should burn her.
Just reinstall snapvue if you think it has somethink to do. And please try to invoke deamons to solve this.
I'm sure if we look very hard on this, we might find someone else who had this problem. or who knows someone who has.
And maybe I can start a museum for the survivors of the rom of dead. I'll start with my own device.
oh, and for the records, I think the shift has a design problem, and we get this error when the fan get screwed. It might happen after a year, or a bump. In any case, installing a rom and having a fan problem is a disociated event. Fan is dealt by the motherboard, and the bios. It has a small captor to say if it's doing it's round think well. If it doesn't, you get the bios error.
@ ThaiHugo, please don't be offended, I don't think you really are, are you?
I took some distance already saying the events most prolly aren't related.
But one has to react to those postings and tell similair stories, in the extremely rare case that something was overlooked
(I think about the EC frying something due to bad command)
Remember old C64 days, where smoke could be programmed to appear from the machine?
I should be getting my brand new shift back within the hour now, and first thing I'll do is install your Age ROM again.
-----------------------
Recap : There seem to be quite a few problems with the FANS and booting, and many people crack the vent cover as it's lame plastic.
I agree with you, and I'm just kidding the corellation between the fan problem and the rom.
I don't want people to start thinking for the bad reasons. The fan is probably a big device conception fault. I don't know if it's only happening on missuse, on heavy proc use, or after a while. But if we say it's comming from the roms, people will not presure htc on this topic, thinking "it's my fault, I used a custom rom on it".
IMO, the shift has multiple parts that can interfere with the fan:
The bios, the EC, the vista OS. The radio and the WM rom cannot. Just try this example: just turn off the shift, and play as long as you want with wm, the fan will NEVER start.
Programming a rom has multiple contact with the fan:
You use the vista OS to send it to WM.
You change the EC state during it
You reboot the computer, so the fan issue can be revealed at that time, even if it happenend a long time before. Also, the fan test at boot stress it to the max, so it will reveal any defect here.
So I'm ready to hear any story about Flashing a rom (any rom in fact), but actual rom use, or radio, is for nothing in this story.
Lucid, be assured that I consider your post with a high value, and that I'm ready to help as much as I can on this issue. My post wasn't really answering to you actually. But we must call a cat as a cat (so goes the saying) and exclude the actual use of a rom from the equation.
kjijqwopjdopqw
I understand your pain, specially when you are living in a country with no htc support. I hope you will get a proper repair at a good price. Good luck!
qhichoiowjp
First, let me say that age of reason is a better choice IMO. You should keep with it.
Now, let me explain you something:
The cpu in vista has absolutly no relation to the rom you flashed. There are two boards. The cpu you are monitoring is the intel one, used by vista. The Wm one, with qualcomm components, is using a different processor. You cannot see the processor use of WM from vista except if you install sofisticated programs for this task.
Now, what you are telling me looks more like a heavy cpu useage associated with a high ambient temperature. This will kill your fan.
I suggest running the shift from the coolest place you find, or at a cooler time, try to reduce CPU useage by reducing the programs you install and run at the same time. If you leave your shift without any program running, it must use less than 10% of your proc and show a flat line for the cpu. If you have spikes, it means you have bloated your install by some program that uses too much of your cpu.
Disabling aero might help you. Also, W7 seems to use less cpu than vista, so it could be a good upgrade for you.
Also, make sure you absolutly never cover the middle exhaust grid. Even by putting something closer than 10 cm in front of it. This one must be free as a bird. You should also leave the two side grids alone if you can. DOnt put the shift on your lap, on on the bed. Try leaving it on a flat surface and move it every half an hour to another spot.
While I'm writing this, my cpu is at 4%, peaking to 12% sometimes. This should be your case too.
Try all this and see if you have improvments.
@ Hykleif : Does this mean that your device is now "OK" again , that would be great ! It would however, be even more curious....
@ ThaiHugo, ok, we understand eachother - agree 100%
@ All : I just got my Shift back, it died on me, not booting up, not even showing BIOS, only weird Fan behaviour and sporadic access to windows Mobile.
They replaced the entire maiinboard and the keyboard, but left the (flashed Age of Beauty) Windows Mobile side intact. SO they can replace Vista without touching WinMo, as one would expect from the blueprints anyway.
(Thank you HTC repair guy, for not being a bully and tell your boss to charge me coz I flashed a better ROM than HTC provides. Thank you for real. Keep it up.
Then, the curious case of Mr. Hykleif. Flashes another ROM, get's rid of his problem. Curious !
I think Mr. Hykleif's shift has a too short lifespan to get any conclusion from that. Still think it's a heat problem.
hihoihvhvb
I totally agree with thaihugos advice re the fan exhaust port, gotta keep that 100% unobstructed. The Shift needs room to breath when it's working hard.
My Shift has been running the age of beauty rom for months, although I rarely use the winmo side. The intel side is in use several hours a day, and I've never seen a fan error message.
Whatever the anomaly causing your problem was, it wasn't thaihugos rom. You should be able to flash back to the age of beauty rom without problem.
The only difference between age of reason and age of beauty is a simple program (the today screen replacement).
I guess this is what doctors call the placebo effect.
bjkghojkp'[
Let's say it's happening exactly after flashing a new rom. If this is the case, then it's the flashing process that create the problem, and then flashing a new rom or the same rom another time would solve this issue.
But I still think this is mostly a exhaust cover problem. I'll wait for a new strange case before drawing any further conclusion.
First of all, thank you so much for your hard work and your noble strife to improve HTC HD2, a phone in much need of so.
Now to a more seriuos matters, I been testing out ROM´s now (around 15 different ones atm), and i get some striking matches that i want to ask about, all this on my HTC HD2.
Everybody wants to talk of Speed, 576mb, Clocked CPU, HD2 now super fast etc. And my question is the same as to HTC them selfs (boasting all this horsepower and falling so flat), why is menys and scrolling still lagging and showing .... in lack of words, Screen Tearing. Why on earth cant i in phone contacts, or file browsers, start meny, or any darn meny you like, scroll up or down and not feel like the phone is on a bumpy road? Dont know if any of you understand what i talk of, cause i havent seen any talk of it.
In some ways (Like through a non programer like me) it seems like hole darn windows is on some kind of grid, where the menys have to move through tiny bumps to move ahead. Anybody that can shine some light on this.
Im not new to phones, but im no hotshot also. So i want to make sure i made everything correct.
1. Install HSPL
2. Install ROM of liking
3. Hold your thumbs
As you may understand, i have in my own little world pretty humble visions. Fast everyday usage, ither in Windows or in Sense, does not matter. No lagg at all, pure speeeeeeeed. Is this really achivble? I must say im very dissepointed with the HD2´s performance.
Best Regards
Peder Nakazul Tjärnberg
Sweden HTC, Iphone, Motorola, Samsung User.
I understand what you mean..
Sometimes when flipping from the today in sense to view all 9 programs there is some kind of lag... the start menu also isnt that smooth..
Thats why MS started Windows Phone 7 development from Scratch! Now it will be much more fluid, smoother transistions rather than this messed up piece of code called WM6!
Tanmay® said:
Thats why MS started Windows Phone 7 development from Scratch! Now it will be much more fluid, smoother transistions rather than this messed up piece of code called WM6!
Click to expand...
Click to collapse
Thats so true...
But I'm still standing here with my 3 months old HD2..
And we have to wait until next month to hear if our devices is going to get the update or not..
My guess would be that they simply purposedly limited scrolling fps to save battery.
kilrah said:
My guess would be that they simply purposedly limited scrolling fps to save battery.
Click to expand...
Click to collapse
But since i must once again give you all programmers cudos, if it was a reduction by Microsoft, wouldnt you all have fixed that already?
Thnx for fast replyes btw. So its basiclly because Windows Mobile 6.5 builds on old programming then?
As you speak of screen tearing, that's also something quite common that you can get on a PC too, mostly noticeable when playing videos or games, and is due to non-synchronisation of screen refresh and image generation. The program creates a new image and sends it to the display buffer while the previous image is being sent to the display. Result is that the first half of the image that ends on the display is the previous frame, and the second half is the new one.
To prevent tearing the technique is to wait until the display finishes showing a full image before sending the new one.
A reason for the "slow" fps could simply be that the screen can't be refreshed faster due to hardware limits, which is totally possible with such a high resolution display.
Personally I don't find it "slow", of course when you put it side by side with an iphone it's definitely slower, but the iphone has a crap resolution... and I definitely prefer the HD2's screen resolution to slightly smoother srolling.
Kilrah, so you mean, basicly, if a better grahic driver could be created it could be solved? I mean do we even have any REAl graphic drivers, exept OpenGL and Chainfires 3d patch that are good, but not enough apperently?
have you toyed with the tweaks in THIS thread?
I have a noticably smoother sense sinse applying them.
Be warned thoughm, some of them will lock up the wrong phone. (I.e watch out for 576 mb tweaks on a non 576mb rom)
Maybe, maybe not. If it's hardware related, no way. Would need to know what the screen refresh frequency is, and anyhigher refresh obviously wouldn't be possible.
kilrah said:
As you speak of screen tearing, that's also something quite common that you can get on a PC too, mostly noticeable when playing videos or games, and is due to non-synchronisation of screen refresh and image generation. The program creates a new image and sends it to the display buffer while the previous image is being sent to the display. Result is that the first half of the image that ends on the display is the previous frame, and the second half is the new one.
To prevent tearing the technique is to wait until the display finishes showing a full image before sending the new one.
A reason for the "slow" fps could simply be that the screen can't be refreshed faster due to hardware limits, which is totally possible with such a high resolution display.
Personally I don't find it "slow", of course when you put it side by side with an iphone it's definitely slower, but the iphone has a crap resolution... and I definitely prefer the HD2's screen resolution to slightly smoother srolling.
Click to expand...
Click to collapse
In my opinion this cant be the reason. Have you ever scrolled in p.ex. TouchTwit1.6 ? It is 100% (!) fluid. So there is some Software around that shows us that it can be different...
I want to start a thread for hardware mods because of two compelling ideas that have arisen:
1) Swapping in the Super LCD of the HD7S into the HD2. Would it be possible to swap this improved screen into an HD2? I love the fact that I can dual boot android and WP7 in HD2 but that device really NEEDS a better screen. From what I can tell, the previous gen HD7 used the same hardware design as the HD2 including the exact same screen, so the HD7S seems like they just swapped in a better display. There are some guides on youtube that show how to replace the HD2 screen, so a modification like this isn't impossible but pretty difficult. Any comments?
2) NFC into the HD2. This didn't seem like a neccessary feature at first, but a post on engadget about using wireless NFC for android devices seems like a compelling option. I am not too sure about this mod though, don't know how hard it would be. I know somebody successfully created a wireless charging system for the Evo (I think) but an NFC system is a completely different ball game.
Post any thoughts or comments on these mods and propose your own mods as well. For the sake of intelligence try not to post mods without having some backup in terms of feasibility of the modification. What I mean is don't say stuff like "Lets put in a slide out keyboard, an SLR camera on the device and add playstation control buttons". Unless of course you legitimately found a way to do such a monstrous mod!!!! =P.
Well what you propose with the changing of the screen would be awesome, I have to say it would be one hell of an accomplishment. But you not only would have the actual physical hardware to contend with, but you have to ask is all other needed components in the HD2 compatible to work with the proposed adopted screen. Another thing will the actual size of the screen and digitizer for the HD7S as far as the thickness of them together. The questions and obstacles would no doubt be numerous if not to many to overcome or to large to overcome.
Then you have the fact that even if you did succeed in getting the screen installed you would have to modify the IPL of the bootloader to even be abale to use it. Plus probably a whole slew of other software related things would have to be modded. But this is XDA after all
Cheers
really cant see the point, the HD2 screen is already very good, well mine is anyway. That being said though I had a new screen fitted by HTC about a month ago and I am sure it is better than the original one.
hmm.
it won't be necessary to build the native NFC to HD2... they are coming with NFC SD cards, it will be pretty easy for us
Belovoj said:
it won't be necessary to build the native NFC to HD2... they are coming with NFC SD cards, it will be pretty easy for us
Click to expand...
Click to collapse
and nfc sims
http://www.theregister.co.uk/2011/11/16/nfc_sim_again/
Well about screen..
U may have measured the width and height. And may be same. But what about depth? And what about position of the flux cable?
Thats a hardware thing.what about software? And the display driver section? More/ less volts to backlight leds, display ram and the display itself? Any way give a try..
About nfc.. yap we got the software in every android os for it. Coz all or most of them are ports from phones having nfc( i think so)
But from the hardwre view.. its about making a radio module whith accelerometer support.. and its should be tiniy enough to put into the phone.. so its a realy hard thing..
The wireless charging dock is a simple one.. connecting both through the old technology.. mutual induction. Old wine in new bottle.+ unwanted losses too.+ dustortion to sensitive devices. Well that might be helpfull if u hav a 100% sealed device( water,dust... etc. Proof) and with out connectors which opens the inside world to the outside world!!! For charging a device like dat u can use wireless electricity. Or what else it may be usefull? Its a pure analog circuit. Every dude with a little electronics knowledge can rip a normal stepdown transformer and can make it.
But nfc is not that.. u may get the point..
send from my hd2 @ miui 1.12.2
Hello all, one of the main reasons why i chose the xperia z1 compact over a galaxy s5 by then was that i knew that z1 compact had much more power to spare for future gaming thanks to the low screen resolution, It was very hard for me to choose this time galaxy s6 over z5 compact for the same reason, but i succumbed to the bigger better oled screen this time around even though i was upset at the senseless screen resolution of 1440 x 2560 which made it clear that the phone would struggle with current high end games to keep 60fps let alone future games...
Well after playing Dead Trigger 2 with all gfx on max surprise surprise, the phone could not keep up with its absurd screen resolution a steady 60fps so i started thinking if there was a proper screen res changer tool this time around as i was a bit familiar with some of them in the past which done a poor job and many times left the phone unusuable thx to the resolution affecting the OS itself aswell.
Well guess what, Samsung woke up and presented galaxy s6 owners (and some other high end galaxy models) with a very nice solution.
Its called Game Tuner, officially made by Samsung and you can find it here:
https://play.google.com/store/apps/details?id=com.samsung.android.gametuner.thin&hl=pt_PT
What it does is exactly what all the games should have in the first place, options to choose resolution for your game without changing the resolution for your OS GUI, on top of that, you have a nice control panel profile system which allows you to setup different settings for different games installed in your phone, this apps benefits you with the following:
1)Lower graphics resolution for any games of your choosing,
2) It allows you to even force 3D games which are running at a lower resolution than your screen to actually run at highest resolution supported by your screen,
3)It also allows you to lock FPS to 30 instead of 60 if you would like to preserve some battery life.
4)Allows you some brightness control per game.
Here are the more confusing settings explained:
High (turns all games to the highest resolution of the phone screen) almost impossible to observe pixelization
Medium (turns all games to a tad lower res (i believe 1920*1080) difficult to observe pixelization
Low (turns all games to an even lower res( i believe 1270*720) pixelization visible but not too ugly
Extreme Low (turns all games to the lowest resolution possible (i believe 840*472) as i see alot of pixelization
Custom (Allows you to select each game with a specific profile (high, medium, low, extreme low).
Now you can fully enjoy that 2k screen without reprecussions!
Give it a try and have fun!
EDIT: If any questions feel free to ask and ill try to help as i can.
Wow, thanks for sharing. Works great. You can even specify the resolution, fps and brightness per game.
Verstuurd vanaf mijn SM-G920F met Tapatalk
NP, glad you like it, updated thread with more information and corrected some grammar issues.
You can already find this in the S6 themes and apps section. No need to post this here
Thanks, this is really cool. I wouldn't have seen it if you hadn't posted it here! I wish it would actually tell you what resolution each of the settings are. I tried taking a screenshot in game after I enabled it and then checking the "details" in gallery but it still said 2560*1440.
Now I'd like to know how I can completely disable it? It seems even after uninstall the settings remain. I'd like to now bypass the 60FPS limit.
lite426 said:
Thanks, this is really cool. I wouldn't have seen it if you hadn't posted it here! I wish it would actually tell you what resolution each of the settings are. I tried taking a screenshot in game after I enabled it and then checking the "details" in gallery but it still said 2560*1440.
Now I'd like to know how I can completely disable it? It seems even after uninstall the settings remain. I'd like to now bypass the 60FPS limit.
Click to expand...
Click to collapse
The settings wont remain after uninstalling, i say this because i tried it myself by setting a game to lowest resolution possible and after uninstalling it rolled back to normal, many people believe that, without modding, all games will run by default on the highest resolution supported by your screen, this is a false assumption, and you can easelly notice that with games such as Asphalt 8 and Real Racing 3.
Indeed it should specify resolution instead of "very low, low, med, high," thats why the thread settings are nothing more but assumptions.
Also setting it to MED is considered the default setting for said game in this app so maybe med is actually the default app resolution.
crzykiller said:
You can already find this in the S6 themes and apps section. No need to post this here
Click to expand...
Click to collapse
Well, i think it doesn't stress anybody, but the opposite: more users will know about it. It seems this app is not that popular, many users have no idea about it (i found it a couple of weeks ago by mistake in playstore).
The app should receive more coverage in media too. This will be a win-win situation for all, and maybe samsung will add a system-wide option for resolution change (yeah, keep dreaming)
I believe beying able to choose fullscreen resolution of your phone shouldve been a thing implemented by default, im Really happy that samsung thinked of this for my S6 as i can play games like dead effect 2 with extreme graphics but reduced resolution (almost imperceptible pixelization) and get a rock steady 60fps, the only strange thing it semms that it is happening is that after a level or two the game starts to loose performance, other users also reported this issue, samsung will hopefully fix it in the next app update.
TheWarKeeper said:
I believe beying able to choose fullscreen resolution of your phone shouldve been a thing implemented by default, im Really happy that samsung thinked of this for my S6 as i can play games like dead effect 2 with extreme graphics but reduced resolution (almost imperceptible pixelization) and get a rock steady 60fps, the only strange thing it semms that it is happening is that after a level or two the game starts to loose performance, other users also reported this issue, samsung will hopefully fix it in the next app update.
Click to expand...
Click to collapse
I think you should also disable DVFS for optimal performance gains.
vnvman said:
I think you should also disable DVFS for optimal performance gains.
Click to expand...
Click to collapse
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
TheWarKeeper said:
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
Click to expand...
Click to collapse
I may be wrong but I assume unless you game all day long it shouldn't make too much of a difference in terms of lifespan (assuming one swaps phone every 2 years or so), pretty much like OC/OV.
vnvman said:
I may be wrong but I assume unless you game all day long it shouldn't make too much of a difference in terms of lifespan (assuming one swaps phone every 2 years or so), pretty much like OC/OV.
Click to expand...
Click to collapse
Indeed OC reduces lifespan of said component but the problem is more serious than that, if you disable the throttle the GPU or CPU might overheat, it depends on the phone and the chips inside and also the heat dissipation quality which can range from different thermal pastes to different heatsinks and to where is that heat transfered after that, its a risk of hardware damage without knowing its internal chips temps.
But thats just me who knows maybe im wrong.
TheWarKeeper said:
Indeed OC reduces lifespan of said component but the problem is more serious than that, if you disable the throttle the GPU or CPU might overheat, it depends on the phone and the chips inside and also the heat dissipation quality which can range from different thermal pastes to different heatsinks and to where is that heat transfered after that, its a risk of hardware damage without knowing its internal chips temps.
But thats just me who knows maybe im wrong.
Click to expand...
Click to collapse
Well that would totally make sense, but at least as to OC+slight OV it has been tested that the possibility of making some actual damage will most likely be very slim untill around the 5 year mark or so of usage. As to DVFS, by disabling that you don't actually disable throttling completely, which is still managed by the kernel (as it should), but only Samsung's more aggressive throttling which is completely unnecessary because it's always trying to keep the phone "super cool" at the expense of performance, while some people who are into heavy games would use a device hot to the point that it causes mild discomfort (but still safe for the components), rather than a device that is slightly cooler but gets laggy after 2 minutes of actual gameplay.
I guess it's up to the user to decide whether to mess with this or not, maybe for most people it won't be worth even the slight risks but for people like me who happen to enjoy heavy games and swap phones every year and a half or so it's good to have the option.
vnvman said:
Well that would totally make sense, but at least as to OC+slight OV it has been tested that the possibility of making some actual damage will most likely be very slim untill around the 5 year mark or so of usage. As to DVFS, by disabling that you don't actually disable throttling completely, which is still managed by the kernel (as it should), but only Samsung's more aggressive throttling which is completely unnecessary because it's always trying to keep the phone "super cool" at the expense of performance, while some people who are into heavy games would use a device hot to the point that it causes mild discomfort (but still safe for the components), rather than a device that is slightly cooler but gets laggy after 2 minutes of actual gameplay.
I guess it's up to the user to decide whether to mess with this or not, maybe for most people it won't be worth even the slight risks but for people like me who happen to enjoy heavy games and swap phones every year and a half or so it's good to have the option.
Click to expand...
Click to collapse
I tought the DVFS disabled the throttle completely, its good to know it doesnt then and i agree, the samsung throttle is overreacting and prolly did better good with it off than on, thanks for your suggestion.
TheWarKeeper said:
Yes that would increase performance but its a heavy risk considering you might burn up ur cpu or gpu and void the warranty
Click to expand...
Click to collapse
I play with Samsung DVFS always off and I can play dead effect for 2 hours straight without performance degradation... CPU doesn't go over 75-80*C depending on the ambient temperature