Related
I have a t-mobile us touch pro 2, stock rom, and for the life can't figure out how to enable single column mode in PIE.
Slightly related, if I go into zoom out mode in PIE, should the zoom bar do anything? I've spent a lot of time trying to determine if my zoom bar is broken or if it just doesn't actually do much.
--fg
having not heard anything, i'm going to have to believe one-column mode was removed in pie with wm6+
I have since upgraded to the stock wm6.5 rom and can say the zoom bar seems to be slightly more sensitive and definitely more integrated with pie, doing more than just changing the font size. Still not convinced it aint broken, but at least now i can see it working.
Ok I have seen a lot of confusion over the months regarding the LCD Panel fitted to the Kaiser, I will attempt to answer most of these issues here.
Hardware: The kaiser series is fitted with a 2.8 inch 240x320 TFT LCD panel, which means that it 240 pixels wide by 320 pixels deep, the optimum density of this LCD panel is 143 Pixels per Inch.
Resolution: This refers to the screen resolution that the Operating System will use to display on the LCD panel, the 3 most common being 240x320, 320x428 and 320x480, the reason this is possible is that the OS is capable of fooling the display into using the fixed 240x320 panel to display more pixels, ( it does not really have more pixels, it just looks like it).
DPI: DPI or Dots Per Inch, also known as Density, and correctly known as PPI or Pixels Per Inch, this refers to the number of pixels the screen displays in a One Inch Square on the screen. As I noted above, the actual PPI of the LCD panel is 143 PPI, this is fixed by the hardware, and cannot really be changed, however since the LCD is software driven, it can be persuaded to look as if it is displaying more or less pixels in that same area.
Panel Type: This refers to the actual LCD panel fitted to your device, there are 3 types fitted to the Kaiser series, one manufactured by Sony, the other two by Topoly. While the 3 different types of panel are functionally identical, they differ at the electronic level. On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, so the panel type must be set in the parameters passed to the kernel at boot time, either in default.txt when booting from SD, or hardcoded in the NBH when booting from Nand. Also there is no easy way of telling which panel type is fitted to any given Kaiser, since the panel type was chosen by HTC depending on price and availability and stock at the time of manufacture, so any model of Kaiser can have any of these types fitted.
The main problems encountered with the display are usually solved by changing the Panel Type, either by editing default.txt, or reflashing the correct NBH, ( note that you can also edit the kernel parameters of an NBH using a Hex Editor, however this would be a relatively advanced method, since an error could cause major issues).
Changing screen resolution and density: As noted above there are 3 main resolutions used, 240x320, 320x428 and 320x480. These easy to change either by editing default.txt, or flashing an NBH, depending on how you run Android, resolution is usually a personal choice. Density is not as easy to change, although Rogue Tools by Myn, (available in Market, and discussed here: http://forum.xda-developers.com/showthread.php?t=667581), is excellent for this purpose, there are various common PPI settings, and again mostly personal choice, a little experimentation with resolution and density will allow you to find what you prefer.
Hope this helps clear things up a little
Thanks for this, it helps alot!
vertical lines issue
just to add to the above: the vertical lines issue some have is related to choosing the wrong panel type. Chosing the correct one will solve the problem.
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Dark-Side said:
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Click to expand...
Click to collapse
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
zenity said:
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
Click to expand...
Click to collapse
I use panel 2... I go to use panel 3 to test this. panel 1 make for me pixel errors. I'll report here.
Thank you
EDIT: no difference between panel 2 or 3 on my kais130
Thanks! That helps a lot.
I havd a thought, which is to change a physical LCD panel for my kaiser, HVGA or VGA... Is that possible? I would look into some electronic files later...
i guess that our chip has max resolution only 320x240 so no higher resolution
but as I look in the pdadb.net there are some devices with higher resolution and same chipset as ours so perhaps it is possible
It is unlikely to be possible to use another panel, since there are a lot of differences with the interface, it's not just the chipset, but how it's wired, plus higher resolution panels may need extra address lines which are not present in our kaisers.
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
zenity said:
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
Click to expand...
Click to collapse
density 106 works very well with 240x320 if the build is designed for 320x480. I'm using that on the CyanogenMod port. Haven't tried it with other builds though. I did try 107 once with another build but that did not turn out very well.
106? that should really look a little blurry, but I think it depends on the resolution that the build was designed for, however I think I'd find it a little small personally, have you tried 100? it should look clearer than 106, although I have noticed that some people just prefer a certain density regardless of the actual mathematically 'correct' one.
zenity said:
...
Panel Type:....
.... On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, ...
Click to expand...
Click to collapse
So how do I detect which panel in winmo?
I don't like the idea of just stabbing blindly in the dark and hoping I get it right.
Basically? Stab in the dark, there is no way in wm or android to know which type is fitted, type 2 seems most common, and is usually a 'safe' default, if the graphics/colours are wrong, you probably have type 1, if you have issues waking from sleep then you probably have type 3. So try panel 2 first.
Sent from my HTC Dream using Tapatalk
I'm running Android on my HTC Tilt and am using panel 2. I tried panel 1 and the colors were off so Panel 2 seems good.
But the problem I am having is that when I open up the dialer, it doesn't fit correctly on the screen, the bar which shows which numbers you have entered covers up the numbers 1,2,3 and the sides are cropped.
Everything else seems to be fine why is the dialer messed up?
Should I try changing density its at default right now.
I personally like to use 110, but every time I open detail application on Market, it gave me force close. Facebook for Android does that too (I mean FC) whenever I open detail message or upload picture from gallery.. I've tried 106, 104 and 100 and still having the same problem.. it's not happening when I use 120 for density, everything seems work properly normal.. is that common or I have to do something to fix that problem?
Thats not normal behaviour for market, although it has been known to be a little flakey on some builds, however this is unlikely to be related to lcd density, since density only affects the visual appearance of the screen, not the OS itself.
Which Panel?2 or 3?
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
stajan said:
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
Click to expand...
Click to collapse
As previously stated, panel 2 is the most common of all.
As for the white flash and grainy display, this is due to the fact that we have to "fake v-sync" in order to display anything on our screens. Remember, Android was not designed for our Kaisers, but developers got it to run, piece by little piece, really well on our devices. There will always be drawbacks to this as the hardware doesn't really meet the requirements of what Android was developed for.
If you want to see whats going on when you have a white screen or snow, slide the keyboard open and press "Fn-left softkey". this brings up a screen that shows you what Android is doing.
To return to the main screen, press "Fn-right softkey".
Hope this helps...
So it has been mentioned throughout a lot of threads but I figured I would give a step by step and overview for the people who do not know about this or are unsure what it means and does. You must be rooted to use this.
When you compare our phones to a phone that has a qHD display you will see that the qHD display will have smaller text and will allow you to view more on the screen at one time then our WVGA screen allows. Well this is how you can even the playing field and view your phone like it was a qHD or even a 720p screen.
No more super large text like your phone was built for the blind. Also, a great feature if you use an alternate launcher you can set the screen to 5x5 or even 6x6 depending on the resolution you pick.
You will need the 2 apps from below.
First you need to install busybox. Download the app and then open it. From there it will ask you to install. Just choose okay for all the defaults and don't change anything.
https://market.android.com/details?...t=W251bGwsMSwxLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
Next app is lcd resolution. This is where you change the resolution.
https://market.android.com/details?...NvbS53ZW1vYnMuYW5kcm9pZC5sY2RyZXNvbHV0aW9uIl0.
There are 2 settings I use, 200 which is almost identical to qhd. qHD is 960x540 and the app allows you to set it at 960x576. You can also set it at 160 which is 720p. You can use all the settings in-between as well but I stick to these 2. You can do your own testing and see what works best for you. Make sure when testing that you do not click save on boot in case your Rom does not play nice with that resolution. I have found that 200 works almost everything but 160 can be a little more tricky, especially with certain themes. You top bar will be all blurry. A reset will put you back to stock if your Rom does not like the resolution as long as you did not click set on boot.
By doing this hack, TW launcher will not play nice so you must use an alternative. All other launchers will work. The stock dialer will also not work. You can use Go contacts, dialer one or Ex Dialer. They all look and function great. You will also need an alternate calendar and calculator app. Their are a ton to choose from.
When setting your system to 200, you might encounter an error message saying certain apps are not compatible with your phone in the market. This is because this setting while close to qhd is not exactly the same resolution so the market app does not think is is compatible as it is not a standard resolution. There are 2 ways around this. You can install the app through Amazon market as it does not know the resolution you are running on your phone or you can switch back to stock (240) then clear market data and you can download the app. Then switch back to 200. This won't happen with every app as a lot will still download when st to 200.
When running at 160 (720p) you will not have this issue in the market as this is a native resolution of Android and is recognized by every app.
I think that covers it all for now and I cannot imagine going back to a WVGA resolution as it looks sooooooo much better running at a near qhd res.
Below are 2 picks showing the difference. One is stock, one is set to 200 (qhd) and the other to 160 (720p).
Stock (240)
qHD (200)
720p (160)
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
bertm13 said:
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
Click to expand...
Click to collapse
Yeah TW theme built for 720p setting would be a keeper.
bertm13 said:
I like 720p. Also, you can edit your build.prop manually and modify:
ro.sf.lcd_density=240
Does anyone know how to modify a theme to make it work with this?
Click to expand...
Click to collapse
That works as well but the app makes it much quicker to jump between resolutions then having to edit the file.
When i changed it with LCD density the resolution changed but there was lots of space under the home screen # indicator, can you do a shot of your home screen and wallpaper to see what it looks like?
xlGmanlx said:
When i changed it with LCD density the resolution changed but there was lots of space under the home screen # indicator, can you do a shot of your home screen and wallpaper to see what it looks like?
Click to expand...
Click to collapse
you can't use Touchwiz. Need another launcher, and dialer. On some roms the camera and music apps break too if you go too low (like 720p), likely others.
I am confused, if the resolution can be improved via software, then how come the manufacturers are not doing it, what is the catch?
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I am confused, if the resolution can be improved via software, then how come the manufacturers are not doing it, what is the catch?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was going to take issue with OP's terminology but decided to not be 'that guy'...
...but here we are.
This doesn't actually change the resolution of the panel at all. You always have the same amount of pixels. Period. All this does is scale the UI. at a screen density of 160 our screen will display things at the size that a 720p screen of identical size would display them. However we lose detail on fonts whereas a 720p screen would have the same amount of detail at 160 as we would at 240....roughly. If you can live with smaller and slightly blocky fonts, go for it.
I can. It's awesome.
another confusing but interesting tidbit: LCD Pixels are made up of red green and blue subpixels. Our panel and the 720p Galaxy Nexus panel have an identical amount of subpixels. But the 720p panel achieves a higher resolution by using less subpixels for each pixel. That is why it is said to have a "pentile" display, as each pixel is composed an arrangement of 5 sub-pixels whereas we have 12 sub-pixels for each pixel. This also explains why 800x480 (WVGA) "pentile" panels look like crap...err...ahem...receive so much criticism. (See: motorola displays)
EDIT: Also, more sub-pixels per pixel means better 'sub-pixel hinting'...which is an effect used to enhance text on LCD panels. The fact that we have so many sub-pixels is probably the only reason why we can pull this off. Of course I'm assuming that android takes advantage of subpixels.
Just a reminder to everyone to nandroid before doing anything like this;
My phone won't boot after doing this. I can get into CWM, but anytime I try to reboot it gets stuck in a loop at the Sprint / 4g animation. I suspect it has something to do with busybox installation but who knows.
I did NOT have the "Set on Boot" selected in the LCD density app. I think I already had busybox support... maybe trying to install the market busybox app borked something.
Anyhoo... always do a nandroid, kids!
As Dan mentioned, it does not actually change the resolution in the true sense but for the purpose of this thread I didn't get into that detail.
I think our screens look 10x better then the Evo 3d and the photon screens when our screens are set to WVGA compared to their qhd display. This only makes it better. With a screen this large it only makes sense to shrink things down to get more on the screen.
Now the Galaxy Nexus screen, I am expecting that to be a killer screen.
Ok thanks, it was leaving like choke real estate under the page number on the screens, I actually like Touchwiz but thanks for the heads up
daneurysm said:
you can't use Touchwiz. Need another launcher, and dialer. On some roms the camera and music apps break too if you go too low (like 720p), likely others.
Click to expand...
Click to collapse
xlGmanlx said:
Ok thanks, it was leaving like choke real estate under the page number on the screens, I actually like Touchwiz but thanks for the heads up
Click to expand...
Click to collapse
I think if we could yank touchwiz off of a Galaxy Note it would do 720p (160) and if not whatever the density setting is on the Galaxy Note would make it fit perfectly.
As far as I've seen, touchwiz isn't ingrained in Android at all. I could be wrong, but, it seems like just a launcher. It's nothing like Sense which has it's big fat tentacles way up Android's ass.
...though I'm not a fan of Touchwiz, so, it really doesn't bother me at all. It's not that I hate touchwiz--I was actually astonished to find how nice it was after all of the Sense-o-philes bashed the crap out of it--I just love me some Launcher Pro and/or ADWex, depending on the time of day....though every now and then I throw on Launcher7 for giggles.
I think you are right on all accounts. I actually like its styling (well with ICS + ICS Twist) but the fact that the launcher is hardware accelerated is too much to give up
daneurysm said:
I think if we could yank touchwiz off of a Galaxy Note it would do 720p (160) and if not whatever the density setting is on the Galaxy Note would make it fit perfectly.
As far as I've seen, touchwiz isn't ingrained in Android at all. I could be wrong, but, it seems like just a launcher. It's nothing like Sense which has it's big fat tentacles way up Android's ass.
...though I'm not a fan of Touchwiz, so, it really doesn't bother me at all. It's not that I hate touchwiz--I was actually astonished to find how nice it was after all of the Sense-o-philes bashed the crap out of it--I just love me some Launcher Pro and/or ADWex, depending on the time of day....though every now and then I throw on Launcher7 for giggles.
Click to expand...
Click to collapse
xlGmanlx said:
I think you are right on all accounts. I actually like its styling (well with ICS + ICS Twist) but the fact that the launcher is hardware accelerated is too much to give up
Click to expand...
Click to collapse
Has this been verified? I stopped caring about it once I got LP/ADW up and running and it seems supernaturally smooth. Though I have to admit that the transition to the app drawer in TW is phenomenally smooth...aside from that, though, I don't really see it.
...and if only TW is hardware accelerated that must be via an API. Samsung proprietary? Considering the popularity of the SGS2 worldwide I'd imagine there would have to be another launcher that would take advantage of these hooks.
Honestly if we do, in fact, have hardware acceleration (and I believe we do) why wouldn't that be system wide? Once you go into settings you are out of the launcher and if anyone remembers Cupcake or Donut holy crap was that a painful experience for what was at the time super fast 528-800mhz phones (g1/hero and moment).
this is a great find I think, I really like the tight resolution, not too keen on having to change the type of launcher either
Has anyone noticed the jacked up notification on the notification bar?
And too bad there's not a way to make the dialer and home screens fit the screen now!
Thanks for the hint
Tried this at 160 using go launcher on starburst 1.9.8r with the beta ICS theme and it looked great except the status bar was screwed up. Do you think it might be the theme or rom?
psych2l said:
Tried this at 160 using go launcher on starburst 1.9.8r with the beta ICS theme and it looked great except the status bar was screwed up. Do you think it might be the theme or rom?
Click to expand...
Click to collapse
Was it a theme you added on to the Rom? If so, you can try it without the theme.
I am running Calk's 1.5a Rom and it works at 160 by itself, with the honey theme and the ICS mixup theme as well...
Tried it at 200 but didn't like how it screwed the dialer up and went back to 240.
tenaciousj said:
Tried it at 200 but didn't like how it screwed the dialer up and went back to 240.
Click to expand...
Click to collapse
Download GoContacts, it comes with GoDialer. Both better than stock apps and free and work at any density.
Sent from my SPH-D710 using XDA App
Anyone figure out a way to replicate a true qHD resolution? Being that it is a little off you get the apps not compatible message in the market. If you were able to replicate the exact res like 720p does you would not get that message.
Hey guys, I own my hox now for 2 weeks and updated it to the latest 1.29 version but I still notice some glitches so I just wanted to check if it's only with me or you all have them and they are a part of the software just not finished yet.
First of all I have set my screen brightness to automatic but every once and a while I notice the screen brightness going to maximum or some other value and when I access the menu I can see that automatic brightness is unchecked. Also when scrolling with live wallpaper the live wallpaper is freezing.
Anyway I think that this is not HTC style, releasing a product that is not ready yet, as I owned Desire and I was quite happy with it.
Thanks
dzdimov said:
Hey guys, I own my hox now for 2 weeks and updated it to the latest 1.29 version but I still notice some glitches so I just wanted to check if it's only with me or you all have them and they are a part of the software just not finished yet.
First of all I have set my screen brightness to automatic but every once and a while I notice the screen brightness going to maximum or some other value and when I access the menu I can see that automatic brightness is unchecked. Also when scrolling with live wallpaper the live wallpaper is freezing.
Anyway I think that this is not HTC style, releasing a product that is not ready yet, as I owned Desire and I was quite happy with it.
Thanks
Click to expand...
Click to collapse
About the autobrightness i am not sure, i dont have that issue.
But the live wallpaper is "normal", we have to wait for HTC to fix that (i hope with the next OTA).
P.S. you post this in the wrong place, this is for the Q/A thread
I have noticed this too when trying to disable delivery reports in messaging the option never saves.
Sent from my HTC One X using XDA
I also forgot to mention that sometimes my scene is mixing my icons i.e. I get different widgets on my home screen. This are very odd glitches and in my opinion very immature from htc, releasing this kind of undeveloped device
dzdimov said:
I also forgot to mention that sometimes my scene is mixing my icons i.e. I get different widgets on my home screen. This are very odd glitches and in my opinion very immature from htc, releasing this kind of undeveloped device
Click to expand...
Click to collapse
Hmmm, you probably need to perform a factory reset
Who else has noticed the screen burn in on the bottom bar location? I can notice the Windows icon in the center even once hidden. It is still faint. If the screen is the right color I can see the other icons also.
I absolutely hate this phone because of the OS. Windows 10 Mobile is too buggy for me. I cannot open my camera app half the time, the music app crashes, the browser resets occasionally, finger print scanner works half the time, sometimes the power button does not respond or the notification panel does not pull down.
The biggest concern for me is the phone powering off randomly. I've missed appointments and important things because my alarm doesn't go off, or my call doesn't come through. Why? Cause the phone shut itself off. Oh and the horrible heat this thing makes when browsing the web. Then it slows down until you have to manually shut it off and let it cool down.
Biggest POS I've owned. Now had they went with Android, it would be the best phone ever. The specs are amazing, the OS is total ****.
\rant
It seems you have a falty unit of this phone, contact HP support.
Howdy! I agree, sounds like a faulty phone or bad OS. I'm also using Elite x3 running Anniversary and pretty stable, not seeing the same behavior. Have you tried a phone reset and upgrade to 1607?
One thing, I also have screen burn-in after only a couple of months. Using the defaults for screensaver and sleep, so this isn't really acceptable. Also, the "durable" Gorilla Glass can and does scratch... I'm checking with support to see what options or if this is covered.
It's a bit strange, i have Lumia 930, 950,950xl and no one have burn-ins. I was wondering to buy an X3, but this topic, makes me change my opinion
It can happen...Had a lumia 950 that did that. So just as a fail safe I started enabling this reg key on my amoled w10m phones and it does not hurt anything to do it:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\NavigationBar\IsBurninProtectionEnabled dword:1
nate0 said:
It can happen...Had a lumia 950 that did that. So just as a fail safe I started enabling this reg key on my amoled w10m phones and it does not hurt anything to do it:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\NavigationBar\IsBurninProtectionEnabled dword:1
Click to expand...
Click to collapse
What has changed to the phone after you edited that reg key?
YoungAll said:
What has changed to the phone after you edited that reg key?
Click to expand...
Click to collapse
On the dark theme the nav bar after about 45s to 60s changes contrast so that it is not totally black and so that the nav bar back home and search are not totally white. Then if you touch the nav bar again it goes back to normal. I can try to take a screen shot of it if you'd like?
nate0 said:
The nav bar after about 45s to 60s changes contrast so that it is not totally black and so that the nav bar back home and search are not totally white. Then if you touch the nav bar again it goes back to normal. I can try to take a screen shot of it if you'd like?
Click to expand...
Click to collapse
Ok that would be nice.
Did you use interop tools to open access to registry option?
Yes interop tools method was used.
For some reason it is rendered funny after attaching. You might be able to download it and look at it on your phone to see the actual affect created.
Someone has also shared a link to another forum that helps explain more keys that could be of use for this scenario. I will paste the information from that site below...
Go to the path in the registry HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ NavigationBar and there add the necessary records and values (all entries are of type DWORD)
What we add:
1. IsBurnInProtectionEnabled
2. BurnInProtectionIdleTimerTimeout
3. BurnInProtectionMaskSwitchingInterval
4. BurnInProtectionIconsOpacity
5. BurnInProtectionBlackReplacementColor
The values of which are set accordingly
1. 1 on 2 off
2. Time before in seconds from 1 to ... (I put 1)
3. Time before in seconds from 1 to ... (I put 1)
4. The magnitude of the eclipse as a percentage of 0 (the whole panel will be black) to 100 (the buttons are brightly white) - I recommend 20
5. Replacement of black accent in percentage from 0 (remains black) to 100 (becomes color) - I recommend 0
This was all taken from a site shared to me here
Better to make a reg file to import with interoptool.
@augustinionut
i think its already in wptweaker
Good point :good:
But wptweaker only modify this value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Naviga tionBar\IsBurninProtectionEnabled dword:1
All other values are missing.
augustinionut said:
All other values are missing.
Click to expand...
Click to collapse
You can easily add missing values - WPTweaker especially designed for that purpose
By modifying tveaks.xml, i know, but i"m too lazy.
Ta daaaaa
Had it on the first x3 i got 4 years ago hp replaced it the 2nd one was used for 4 years still fine no burn in