Related
Okay, I was using the camera flash from time to time as a torch and then the VJCandela app came along so I used that too. Usage maybe 2 or 3 times a week for 2-3 mins.
Now I have a very dim camera flash light, it actually looks like there is a black or brown spot in the center of the LED. I am pretty sure it is damaged, now and again it takes on a blue tinge if I test it again.
So I guess its back to O2 for warranty
regards
Vijay555 said:
This program is used to permit control of the flash light on various HTC Phones, to allow it to be used as a torch etc.
Note: this app may will cause permanent damage to your flash led over prolonged periods.
The app will disable itself after prolonged use, but still, use it at your own risk.
Click to expand...
Click to collapse
I know this is of little use after the fact, but there is a warning on the site.
This is the sort of thing that HTC should have thought about when including a flash LED on the device. Do they not do QA testing? Do they care that they are getting a lot of gear back for warranty repair?
I blame their close ties with Microsoft for this, after all, MS are the masters of rushing something to market and fixing the problems with it later, are they not?
I actually use VJCandela too, so I'll be back in this thread when my flash breaks to say "ME TOO!!!1!11one!" =)
PReDiToR said:
Do they not do QA testing? Do they care that they are getting a lot of gear back for warranty repair?
Click to expand...
Click to collapse
I highly agree. I guess having Billions of dollars at their disposal made them forget how hard it is to earn money. It would be nice for them to be poor before they die and experience life at the other end of the spectrum.
Guys, what kind of periods are you using it for? The latest release has a built in timer to switch itself off after 15 seconds, but even then, are you using it for long blasts or just the odd flash?
V
cktlcmd said:
PReDiToR said:
Do they not do QA testing? Do they care that they are getting a lot of gear back for warranty repair?
Click to expand...
Click to collapse
I highly agree. I guess having Billions of dollars at their disposal made them forget how hard it is to earn money. It would be nice for them to be poor before they die and experience life at the other end of the spectrum.
Click to expand...
Click to collapse
Hi Guys,
No disrespect meant here and really not at all knocking Vijay555, but if the flash is used in a way it was not designed to be used then yes, it'll probably fail! Vijay555 warned of this and you took the risk. And to amazingly come back to knock Microsoft about it..?!
The flash will have rating for continuous use and for pulsed use - if it's used continuously at it's pulsed rating, it will fail.
Again, not knocking anyone, but keep it in perspective guys!
bloney said:
And to amazingly come back to knock Microsoft about it..?!
!
Click to expand...
Click to collapse
I don't have a problem with vijay's app nor my flash as I don't use it that much. But my comment was directed not on the flash of the Universal, but to Microsoft as an entity, seems to me they just want to do what they want rather than consider also what the consumers want.
Same here... I didn't intend to hurt anyone's feelings.
you broke your own toy
My thoughts are with bloney on this one.
You broke your own toy, and now you want to blame someone else for it. The LED wasn't built for continuous illumination, but you ventured forth anyways. if it was actually meant for that, they probably would've included a free app for it anyways. not defending M$ or HTC, but try to use some common sense before you get over-enthusiastic about your expensive toys. It already does alot more than other expensive phones, without the gimmicky hacks, at a relatively good price (for me anyways). and because opportunities for good things to come cheaply for me is valuable, I try to treat it as such. You probably should too, instead of complaining here.
daryl425 - I don't think anyone's blaming anyone else here (I hope ), but IMHO there are two competing ways of looking at VJCandela and similar hacks:
1. They're all unsupported by the Manufacturer and OS designer. There may be a good reason for that, so play it safe, and don't risk your system with unsupported/unofficial products; or
2. Live on the edge, unlock, reflash, use and abuse your hardware to get the most out of it. There will be casualties of war - expect it.
I think most of us are wise enough to use our own common sense and live somewhere between the two extremes. If the Universal had cost me $1000, I wouldn't be using it as a $0.50 flash light, risking my hardware.
I wrote the app, for the fun of writing the app. I don't use my Universal as my main phone, so I can "afford" some minor damage to it in the pursuit of art. But, I strongly advise everyone else to use their own sense, and not sit on the flash for 30 minutes, or do anything else that might risk their precious hardware. Frankly, I hardly use the app at all. However, on the odd occassion that I do, it's come in handy. And it warms my geek heart every time :wink:
So, use caution. But remember, every single piece of software you use that isn't official (and a hell of a lot of those that are) could damage your system. Be careful!
But - don't forget to have fun as well. Think how much innovation has come out of this board and guys prepared to push their systems beyond the limit (ie Buzz et al. I don't consider myself within that heady band. I'm just a tinkling tinkerer).
V
hey guys,
its not such a big deal if you burn your flash! I just went to the local camera store (not the digital ones, the age old film based cams store) and found a flash led with almost the same size and rating. I opened up my device (just once again!), took the "dimmed out" led and replaced it. Of course, i got the connector pin from my previous flash led and used the same one. Now it works fine, and i guess the quality of this led is much better.
cheers,
San
To clear up:
I haven't blown my flash (yet). I rarely use it.
I mentioned MS in a disparaging manner because they have a history of releasing products without actually making sure they are ready to go to market (hence all the ServicePacks and patches), and this seems to be what HTC did with this LED. MS works very closely with HTC and I made a joke about the behaviour pattern being contagious.
Whilst I agree that this unofficial hack is intended to utilise the LED in a way that it was not designed for, which idiot sat in his/her lab at HTC and decided that nobody would ever send their PDA in for a warranty repair because of it? Surely this is the kind of thing that bean counters go nuts over? To put an LED that is a little more reliable would have added a penny to the manufacture, as opposed to spending pounds on postage, labour, parts, time, customer support and so forth.
If it can be done, it will be done. Surely this burning out will happen with normal usage too? How many people use the flash on their mobile to read with in bed, find something in the car, blind their friends as a joke? This is nothing to do with Vijay's app, it is a bad choice of materials, costing HTC money and reputation.
I hope this clears up my thoughts when I posted earlier in the thread, and if not, just put it down to too much Slashdot reading =)
PReDiToR - I entirely agree. Although, should a hypothetical guy on the Clapham Omnibus feel the need to trade in his Universal for a newer one, it might be a convenient way to make a warranty claim...
I've never known LEDs to blow unless wired incorrectly. Of course, as stated, it was only designed for bursts, but even so, as you say, LEDs costs pennies, the Universal doesn't. Hopefully, that won't be our loss, and get them to think about the economics of such components in future.
V
vijay555 said:
PReDiToR - I entirely agree. Although, should a hypothetical guy on the Clapham Omnibus feel the need to trade in his Universal for a newer one, it might be a convenient way to make a warranty claim...
I've never known LEDs to blow unless wired incorrectly. Of course, as stated, it was only designed for bursts, but even so, as you say, LEDs costs pennies, the Universal doesn't. Hopefully, that won't be our loss, and get them to think about the economics of such components in future.
V
Click to expand...
Click to collapse
Hello again Guys,
Not wanting to drag this on or to disagree with you Guys, but I've been looking at some LEDs at work (eg http://www.luxeon.com/pdfs/DS49.pdf) for use in a LED strobe and there's a whole load of LEDs out specifically designed for use as a flash.
So, assuming a purpose built flash LED is used in our HTC devices, it's not a matter of an inferior components being selected, but rather an entirely appropriate component that is designed for a very specific task.
From the data sheet, it states that for flash applications the maximum current (up to 1A) should be used. But for continuous operation 350mA max.
All LEDs have a finite lifetime and trebling the max rated current will obviously cause the component to fail pretty quickly!
Obviously the LED I've looked at probably isn't the one in the HTC units (could be though!), but hopefully shows that HTC might not have just been skimping on the flash!
Having said all that, I most commonly use my flash as a torch, so it's good to know it's replacable!
Hope this is of interest - it isn't meant to be not picking!
Bloney
I certainly wasn't complaining about Vijay's app
I was just pointing out my led is now knackered, lol
Keep up the good work Vijay.
Regards, Simon
No flaming of freeware and shareware
Hi Vijay.
I certainly don't remember a flashlight feature on any adverts for my MDA Pro. Once again, it's good to innovate, but users really can't blame you/HTC/MS/etc. only themselves for this. This is just like the classic CPU overclock situation, you can rev it up, but most people advise to watch out for any burning smoke if you push the pedal too hard
No one here is blaming you or your app, me certainly least of all. My point, just like bloney, is that before someone screams and shouts and cursing out other people, they should really take a look at themselves first. Although most shareware developers usually leave the standard "Use at your own risk" sign on their apps. Something else users should remember.
But then again, if they're screaming and shouting and cursing other people out, they might not be all that good to look at in the first place
Out of interest though??? I know you can leave the flash on whilst using the camera app, I used to use mine this way before. But does the flash timeout on it's own? Also is the flash actually brighter when using Vjcandela as opposed to the camera app? I never noticed it being any different?
Just wondering if I could have done exactly the same thing with just using the camera app over time? After all it does not work like a flash in a traditional sense.
As I said before, keep up the good work Vijay
Regards, Simon
Guys, I think I've said everything that needs to be said on this thread in terms of why we write and use "cutting edge" apps, and risk "bleeding"
Simon: the current version (on my website and XDA forums) has a 15 second timeout I think. This can be overridden, but the override also has a timeout, so it shouldn't be possible to sit on it for toooo long now :idea:
The flash is enabled at normal brightness as used in the Camera app. It can go even brighter, but in the circumstances, it's probably not advisable, eh?!
As bloney says, I think the LED is probably rated differently for burst vs sustained current, so hopefully the camera app wouldn't normally burn out the led. But I suppose we'll find out over time with those using the camera app a lot?
V
Hello.. I have been sinking my teeth into this realm for several weeks, and have noticed there seems to be a fairly important topic that is rather underdocumented.
People throw the word "ROM" around, but really with these devices there are several layers of software at work in this regard. I'm about to sound like the ultimate noob, so forgive me. But for example, users hear of a "splash screen ROM".. we read about SPL and its variants.. and of course the OS images everyone here loves.. somewhere in here there is a region accessed and manipulated by MTTY. So what it means to "flash a ROM" can vary wildly.
What I need (and many others would benefit from) is a link to a document that maps this out, describing each of the divisions of the device's low-level software, how they fit into the boot sequence and overall picture, and ideally, which of our tools they are connected to.
What happens once Windows loads is well documented, but what happens before this seems to be as crucial as it is undocumented (that I know if). Many people on these forums are quite technical, despite admitted ignorance of mobile device architecture. A better understanding of the playing field would eliminate much of the confusion users face. Many of the tools themselves are well documented in terms of usage, but their actual technical impact is a mystery to many.
Can anyone recommend any such reference(s) that might de-mystify the architectural aspect of our beloved phones and ROMs?
Hey guys very very important question , it's about the sar rating when we make calls . Sar represents radiation hazards to the brain and , most phones have predetermined valuethat is approved before they are sold for safety . Please can somebody do a test about this
htc hd2 running on winmo is safe but running on builds like the ones here we are not sure
i hope that the forum members and the developers for tons can find out and let us know.
Very very important !!!
im taking a guess here, but wouldn't it depend on your radio rom not the build?
can someone confirm or dispute this?
primaraly your looking at hardware such as antana and shielding. im doubtfull that diferent radio packages are going to boost things to unacceptable levels, otherwise mfg's wouldnt cook them up.
both winmo and android runs on the same radio regardless of wich one is booted.
does that make you feel more warm and fuzzy on the inside?...... or is it from to much radiation?
Once again, cell phone radiation poses absolutely no dangers to the tissues of your body.
You want to know why?
There is not enough energy in the radio waves.
There is less energy coming off of your cell phone's radio transmitter than there is coming off of your computer screen that you interpret as visible light.
Learn2highschoolphysics
enneract said:
Once again, cell phone radiation poses absolutely no dangers to the tissues of your body.
You want to know why?
There is not enough energy in the radio waves.
There is less energy coming off of your cell phone's radio transmitter than there is coming off of your computer screen that you interpret as visible light.
Learn2highschoolphysics
Click to expand...
Click to collapse
That's right
But if it does still, you won't die because of this radioation. It will only make you sterile if you carry your phone always near of your balls.
But then again if there are safety requirements about this than it is only
Logical to know that if a device exceeds a safe limit then it means
It could pose a health issue.
With that in mind , I hope that a test could be done to resolve the worry.
The radiation also has to with the antenna and battery consumption during
When the phone is searching for signal etc.
Thank you for the reply some of you have given.
ok, first, try educating your self before posting the same drivel in a bunch of diferent threads.
had you spent as much time searching how sar is tested as you did posting , you would have found that its tested @ the hardwares max output.
hmm... the software comes no wheres near pushing the hardware to the limit.
the radio software is the same in both WM mode and in Android mode
therefore this would lead to the conclusion that if it passed federal standards for sar emissions when run @ full hardware output, and we arnt driving it that hard, that we are at a level LOWER than what it was tested...
fariez44 said:
I hope that a test could be done to resolve the worry.
The radiation also has to with the antenna and battery consumption during
When the phone is searching for signal etc.
Thank you for the reply some of you have given.
Click to expand...
Click to collapse
please fwd me your bank info, and each specific condition you would like it tested.
its not cheep
http://www.metlabs.com/Services/Wir...ywgP2vhaUCFSBugwodfX3aOw.aspx?_kk=SAR+testing
http://www.ce-mag.com/archive/03/01/miller.html
http://www.rfexposurelab.com/
Well thanks for the information , I was looking for an explanation as such
It seems you resolved my doubts and thanks once again.[/B]
Need to take care of ourselves
I keep seeing people who claim to have headaches in the morning whenever they use specific builds. We also know some builds provide better cell signal and wifi capabilities. I strongly guess there is a difference between radiation levels of different builds.
If someone leads us to measure the SAR levels of builds under this forum to get an "XDA approval", we can surely all donate to her/him. Then we also can prefer the builds acording to their radiation levels.
Someone with knowledge please help us to determine:
- methods of measurement
- rules and standards of approving the builds
- safety classification according to SAR levels
Radiation is no joke. We are the only big enough developer community to provide this standardization to custom builds.
Radio waves are not ionizing, and thus do not carry enough energy to pose any danger whatsoever.
It is physically impossible.
enneract said:
Radio waves are not ionizing, and thus do not carry enough energy to pose any danger whatsoever.
It is physically impossible.
Click to expand...
Click to collapse
The effect of mobile phone radiation have been studied by a lot of scientists. There are thousands of articles about this topic. I agree that there are contradicting results but no single one claims as you said: "it is physically impossible" Or no scientist refused to do the research assuming that the high school physics is enough to finish the argument.
In fact a lot of researchers came into the conclusion that there is a corelation between cancer and mobile phone radiation.[1,2,3]
It has been basicly studied for the short and long term hazards. Long term hazards have not been completely studied yet due to the short history of word wide mobile phone usage. Short term hazards have been proven such as decrease in cognitive functions and prolonged response times. [4]
1. http://journals.lww.com/epidem/page...=2004&issue=11000&article=00003&type=abstract
2. http://oem.bmj.com/cgi/reprint/64/9/626.pdf
3. http://www.ncbi.nlm.nih.gov/pubmed/19285839
4. http://onlinelibrary.wiley.com/doi/...ionid=69BCBB4C4AC1B054C0B953A974547C77.d03t01
baybenbey said:
I keep seeing people who claim to have headaches in the morning whenever they use specific builds
Click to expand...
Click to collapse
Id bet that has wayyyy more to do with screen settings, size, brightness resolution refresh rate comparative brightness of the room( dark room more eye strain) than radiation.
Take two or three flights and you'll already have been exposed more than a small transmitter will give in its lifetime.
I have to admit I keep getting headaches with some phones when having long phonecalls. I'm sure it has nothing to do with the screen (always off during calls) or heating up of the phone (all about the same temperature while in use). In the past I would have laughed, but since I paid attention on when and where those headaches started, I'm pretty sure it has something to do with the phone radiation. Yes, the general radiation levels are pretty low, but still, they are concentrated at our heads and some of us might be more receptive than others.
First I noticed it with my old HTC Trinity. When I moved to an area with generally low reception, I kept getting headaches during phonecalls, while not having them in other areas where the reception was fine. Those headaches always started on the side of the head, where I held the phone. When switching to a bluetooth headset (which has much lower radiation levels) the headaches were gone.
Another example was the Nokia N73 which I had to use for a job I did. I never had a phone before and after which had such an excellent reception. Areas where I couldn't even get a signal with other phones, were no problem for the N73. I could make and receive phone calls without any problems (1-2 bars). For 3 days I had the phone around my neck with a lanyard. So it was resting on my chest all the time. And I can say for a fact that I got a weird feeling at exact that point. When removing the phone from the lanyard or replacing it with a dummy unit or switching it off, it stopped ...
There are various other phone where I can reproduce that. Unfortunatly.
I'm pretty sure too, that different builds have different radiation levels and the radio rom is not the only thing affecting those. When running WP7 on the HD2 I got headaches very fast (after 5 minutes) being on the phone. With Android (at least the ROM I use) and WM 6.5 those headaches only start after 1+ hour on the phone and even then much less. The radio rom might limit the maximum output, but the specific reception control still comes from within the OS.
So since I seem to be pretty sensitive on this, I'm cool with Android on the HD2. I don't get any more headaches than with Windows Mobile 6.5 (or other "low-SAR-phones"). However with WP7 on the HD2 I had serious problems having long conversations over the phone, comparable to my experience with the HTC Trinity in low reception areas. But I don't think that any of those levels are life threatening - it's just an inconvinience (at least for me). But being a gadget fan and geek that's a little bit of a letdown, having to admit that those things might actually be harmful in one way or another.
baybenbey said:
The effect of mobile phone radiation have been studied by a lot of scientists. There are thousands of articles about this topic. I agree that there are contradicting results but no single one claims as you said: "it is physically impossible" Or no scientist refused to do the research assuming that the high school physics is enough to finish the argument.
In fact a lot of researchers came into the conclusion that there is a corelation between cancer and mobile phone radiation.[1,2,3]
It has been basicly studied for the short and long term hazards. Long term hazards have not been completely studied yet due to the short history of word wide mobile phone usage. Short term hazards have been proven such as decrease in cognitive functions and prolonged response times. [4]
1. http://journals.lww.com/epidem/page...=2004&issue=11000&article=00003&type=abstract
2. http://oem.bmj.com/cgi/reprint/64/9/626.pdf
3. http://www.ncbi.nlm.nih.gov/pubmed/19285839
4. http://onlinelibrary.wiley.com/doi/...ionid=69BCBB4C4AC1B054C0B953A974547C77.d03t01
Click to expand...
Click to collapse
Yet, every study focusing on the overall cancer rate in comparison to cell phone adoption has found no correlation. There are numerous experimental problems with actually studying the supposed effect directly (in fact, there was a new york times article earlier this week written by an oncologist enumerating those problems, and why the research, either way, on this subject is fundamentally flawed).
However, the fact remains that if you are scared of this latest nonsensical boogeyman, you should also avoid exposure to all EM radiation of radio and higher energies - you know, radio waves, microwaves, infrared and visible light - goodluck!
I have to admit I keep getting headaches with some phones when having long phonecalls. I'm sure it has nothing to do with the screen (always off during calls) or heating up of the phone (all about the same temperature while in use). In the past I would have laughed, but since I paid attention on when and where those headaches started, I'm pretty sure it has something to do with the phone radiation. Yes, the general radiation levels are pretty low, but still, they are concentrated at our heads and some of us might be more receptive than others.
Click to expand...
Click to collapse
Obviously there is no way that you can get a headache from listening to a speaker placed a few millimeters from your ear for an extended period of time. Obviously, no bloody idiot would think that.
Re-read my post ;-) the speaker has nothing to do with the headaches...
Jeez this whole discussion sounds like one of those stupid news lead-ins like 'find out whats killing your kids... ...right after the break'
Surely there are worthier things to worry about than the radiation from cel phones. Just tune in to Fox News, you'll find plenty of ridiculous crap to worry about. Ask yourself this : if you know for sure that when you're 70 you'll have cancer from using cel phones all your life, will that be enough to make you stop using them now? I'll take the cancer over going back to pagers and pay-phones.
Sent from my HTC HD2 using XDA App
What's the problem discussing possible downsites of customizing our devices? It's not black and white, you know. We can discuss this stuff, and use phones accordingly to our findings and knowledge.
And as said before: It's not (only) about cancer (or any other long term damage this might cause). There are obviously short term effects for some people, why not try minimizing those?
I think it's no difference between WinMo or android builds radiation because the hardware it's the same whit its limitations....even if this wasn't true the livel of sar are not so high to damage our brain(it's possible some biological effect)...so take it easy...only God knows...perhaps
It is really weird that some people here, agrssively oppose individuals who are sharing their concerns by stating some scientific findings about the hazards of SAR. What is the purpose of trying to insult and silence people on the discussion of such a potential risk? Weird!
In the previous references I shared, more than one study of 10+ year of mobile phone usage statistics point out an increased incidence of brain cancer. There are many studies with this result.
And secondly, I found few articles which completely refuses the hazards and defends the safety of mobile phone radiation by agressively opposing(like some people here) the related scientific data. Most of them are suspiciously published from Finland(Country of Nokia). These articles are written in an ideologic and biased manner and falsify all the findings which prove the cancer corelation as nocebo effect or false positive. Or they study the effects of SAR on skin epitheliel cells(relatively resistant against radiation) instead of brain glial cells(sensitive to radiation) and -no surprise- in the end there is no serious harmfull effect... These articles urge to come into the conclusion that SAR is as lovely as blessing of God! Take a look at the discussion section of wikipedia on this topic. All editors complain biased and frequent editing of the page by someone who is adding suggestive sentences to defend the safety of SAR. Hmm...
According to some people here, by looking at the relative wavlength and frequency, microwaves are supposed to be less harmfull than visible light. In fact we can cook a chicken in a microwave oven but not in a sunny beach. SAR can not be found safe by comparing only wavelength/frequency. Who tries to do that obviously misses 3 major points which are:
- distance from source
- intensity of rays
- duration of exposure.
Anyway, even the fanatic SAR defenders in scientific community do not defend it by such a point of view.
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
This is a typical day for my app (pls embed for me): i.imgur.com/z0SlUal.png
last month: i.imgur.com/NDubFOO.png
ratios: i.imgur.com/GlPW2OP.png
countries: i.imgur.com/xmsB2mG.png
This is using AdMob: banners (a lot) & interstitials (a lot) & rewarded video (once a day), most users in the United States/Europe (but I got people all over the world), 30 second refresh rate.
Also running Facebook Audience Network native ads, which are even worse - about 1/3 of what AdMob earns me. Makes no sense cause those FAN ads are super pretty and there are more of them...
70-100k eyeballs a day and can't even afford a burrito, double meat + guac being completely out of the question.... This makes me really sad. Should I just get a job? :c
Would sincerely appreciate any advice!
meatyapp said:
This is a typical day for my app (pls embed for me):
i.imgur.com/z0SlUal.png
This is using AdMob: banners (a lot) & interstitials (a lot) & rewarded video (once a day), most users in the United States/Europe (but I got people all over the world), 30 second refresh rate.
Also running Facebook Audience Network native ads, which are even worse - about 1/3 of what AdMob earns me. Makes no sense cause those FAN ads are super pretty and there are more of them...
70-100k eyeballs a day and can't even afford a burrito, double meat + guac being completely out of the question.... This makes me really sad. Should I just get a job? :c
Would sincerely appreciate any advice!
Click to expand...
Click to collapse
Hi,
It means your approximate eCPM is 9/90 = 10 cents - quite low for those geos. This being it varies by the ad formats - I would suggest scaling with rewarded videos and video ads in general. Try the usual suspects - Adcolony, Vungle, Applovin. Hope it helps
These are terrible numbers. Even banners should be higher. My guess is you are getting very poor fill rates. Check your dashboards to see what eCPM is being reported. If it's like 90 cents or something like what habrcovi said, then that's it. But if it shows numbers like $1.50 or $3 or anything higher it just means really low fill rates.
Hey,
Thats really too low. You should definitely try other platforms.
Check the eCPM calculator to know the approx sum you may earn in these geos. You can find one on Clickky's website (monetize - self-serve)
This is definitely weird - it might be poor fill rates, but I doubt that. I have 60-70% fill rates for banner ads, but they still generate good money. Interstitials over 95%.
Country ratios are same as mine so no problems here. If you had most of your users from somewhere outside the US/Europe - that would have definitely be the case.
I'm thinking either your ads aren't correctly placed or are shown at the wrong moment. Or you're using the wrong ad for your game/app. It would help a lot if you could explain what's your app about and when and what type of ads are you showing.
I'm getting about 150$ for 100k impressions, my problem is that not many users download or use my apps. The amount of impressions you make in a day = my impressions in a month.
I would look into using an ad mediation network to find something that works well for you. You should be able to see which has better fill and ecpm.
It is difficult to say which networks will perform best for each developer, so mediation is a good start.
Using Enhance®, it has never been easier to integrate 3rd party services into your project or to keep them up to date. (Ads, Mediation, Analytics, Attribution, Crash Reporting and more) With little to NO coding at all, Enhance® will have you ready to roll in a matter of minutes. No more hours of coding! No more SDK integration!
We support “NETWORK” and many other top networks, and as mentioned earlier there are other 3rd party services that Enhance® supports and offers as well.
The days of coding SDKs are gone and we want to show everyone a simple life, a life without the hassle of integrating SDKs into your Android or iOS project.
For more information on the fastest way to implement and update SDKs, follow the link : https://goo.gl/kufiQQ
Good Luck!
It is important to not evaluate only eCPM or only fill rate. If you have a high fill rate at a .10 cent eCPM, or a high eCPM (1.5-3$) at a low fill rate, you will be dissatisfied with the results. I suggest that you troubleshoot and see if something is awry. Moreover, you would benefit from diversifying your portfolio. Try out some of your inventory with some other companies and see which performs best for you. I can suggest Tappx as a quality company .
There are a lot of SDK that allow you to earn money.
I prefer Luminati SDK (luminati.io/sdk), or MonkeySocks SDK (monkeysocks.net/sdk/) - with the last one i have working long time because it easy to get started.
meatyapp said:
This is a typical day for my app (pls embed for me): i.imgur.com/z0SlUal.png
70-100k eyeballs a day and can't even afford a burrito, double meat + guac being completely out of the question.... This makes me really sad. Should I just get a job? :c
Would sincerely appreciate any advice!
Click to expand...
Click to collapse
Still can't afford a double meat burrito?
Stats like this are not normal. Especially being over 10k. impressions.
Like other members here suggested, I'd say mediation is the way to go: Appodeal, IronSource, Apploving, etc.
meatyapp said:
This is a typical day for my app (pls embed for me): i.imgur.com/z0SlUal.png
last month: i.imgur.com/NDubFOO.png
ratios: i.imgur.com/GlPW2OP.png
countries: i.imgur.com/xmsB2mG.png
This is using AdMob: banners (a lot) & interstitials (a lot) & rewarded video (once a day), most users in the United States/Europe (but I got people all over the world), 30 second refresh rate.
Also running Facebook Audience Network native ads, which are even worse - about 1/3 of what AdMob earns me. Makes no sense cause those FAN ads are super pretty and there are more of them...
70-100k eyeballs a day and can't even afford a burrito, double meat + guac being completely out of the question.... This makes me really sad. Should I just get a job? :c
Would sincerely appreciate any advice!
Click to expand...
Click to collapse
I think that the issue is that you show too many ads to your audience. If you could give us some data on your daily active users (DAU), then, probably, we would find out that it is 10-20-30 times less than the number of your daily impressions.
And, as you probably know, the more impressions - not the better