Database Info

Polaris camera Problem

I think i'm very unlucky regarding this device. Besides my BT problem (see the link in my signature) i have a Camera problem also. See this picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did someone else also had this problem ?
What can it be?
I have to mention it happend a while ago from time to time, now seems to be permanent; Also i've installed the hot fix for the camera from HTC and nothing
PS: Sry for my english

hi..
i have the BT problem too and i have this screen problem too:
http://forum.xda-developers.com/showthread.php?t=385195
i think we have winning a defective unit...
but my problem is that im in brazil and i cannot send my cruise to eua or UK because when it cames to brazil i didnt payed the customs fees and now if i send to outside i will pay a penalty because i dont declared before...

i've the same annoyingly camera problem. sometimes it works but in most cases i see this multicolor buggy pictures. i'll not send it to htc because i've no replacement and i'm sure it will last 3 weeks or more

I have developed the same camera problem now... so my Polaris only takes strange technicolor pictures. I have tried to change ROMs, Radio, Re-cooking camera app but it´s still the same. So it looks like I´ll have to send it back Well I must admit I have been holding off for a while because I have a list of "problems" which need sorting out...
1. Loose screen. Top left and right of the screen (windows and x button) make a clicking noise after long use, like the screen isn´t stuck down properly
2. Scroll wheel is loose
3. D pad makes a double rebound click on pressing down or left
4. SD card lid doesn´t close properly
and now this
It´s incredible this thing cost me a small fortune and the build quality is really really sh*t. Which is a shame because I think it´s a great device. No such problems with my Kaiser.

today main camera stopped working. just a black screen when camera app is started. then i installed Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab and camera had problems with it BUT after deinstalling Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab the camera works normal!!!! maybe its luck or the problem is only solved temporary ... time will show. can somebody confirm this on his device?

About my Polaris, everytime I press the capture key, something strange happens: a pixel-like black/white preview of the picture magically appears on the screen over the normal image from the center to the left side of the display, what should be?
Any suggest? Thnx

"Preview Picture Magially Appears"
a pixel-like black/white preview of the picture magically appears on the screen over the normal image from the center to the left side of the display
Click to expand...
Click to collapse
It sounds like your in Panoramic Capture Mode.
Go to camera and look in top left corner, if you see three rectangles in a box it means your in Panoramic mode, just press the right arrow next to the box three times to return to normal capute mode.

You're right
Thank you very much

I have the same camera trouble.
Do you have some news from HTC about those stranges colors ?
I've tried the "Nadavi" trick , but it didn't worked.

christonge said:
I have developed the same camera problem now... so my Polaris only takes strange technicolor pictures. I have tried to change ROMs, Radio, Re-cooking camera app but it´s still the same. So it looks like I´ll have to send it back Well I must admit I have been holding off for a while because I have a list of "problems" which need sorting out...
1. Loose screen. Top left and right of the screen (windows and x button) make a clicking noise after long use, like the screen isn´t stuck down properly
2. Scroll wheel is loose
3. D pad makes a double rebound click on pressing down or left
4. SD card lid doesn´t close properly
and now this
It´s incredible this thing cost me a small fortune and the build quality is really really sh*t. Which is a shame because I think it´s a great device. No such problems with my Kaiser.
Click to expand...
Click to collapse
Chris,
nub remark here: This picture of yours seems to look like one of the picture modes that the camera supports.
I can make those pictures as well by choosing picture type "Inverse".... or is your cam stuck in this mode indefinetly?

Hi,
Do you mean in effects? I know there's a "negative" option which gives a similar look but this is a multicoloured mess and it always there regardless of effect or mode. The front camera works fine but the main camera has this problem.
I'm not sure that this Is a hardware problem but it's a major problem. I suspect that the radio has caused this problem because as we can see from the Kaiser forum the camera & radio generally work hand in hand.
As you have said on other threads it's best to stick to original radios until we get to the bottom of this. I fried my Hermes using a test radio so you live and learn!! or not in my case...

I had the same problem as you. When I pressed the lower right button, in camera mode, the problem was fixed :s. If this isn't your solution then you can try to play with all the options in camera mode to solve this problem.

Low quality of reduced pic size
My problem is slightly different. Pictures are OK, but if you reduce the size of the jpg (for emailing for example) the quality is appalling. I thought the if you reduce picture SIZE, quality should go up, not down?

radem205 said:
I had the same problem as you. When I pressed the lower right button, in camera mode, the problem was fixed :s. If this isn't your solution then you can try to play with all the options in camera mode to solve this problem.
Click to expand...
Click to collapse
Which button are you talking about?? The setting button in camera mode? I tried everything in settings but that didn´t change a thing. As you can see from the quality of picture attached it´s not a mode you can select. I have flashed my device many many times and the camera has never started up in anything other than normal mode.

my touch cruise has this troubles again
i think our club is daily becoming more and more members. is it a hardware fault or problem with some ROM versions?
ROM: 1.25.407.1 GER
RADIO: 1.58.21.23
ps: the small front camera is always working.

O2 Xda Orbit 2 Working 100%
Hello I am using a xda orbit 2 and seems that the problem is with htc touch cruise only not xda. I know that they are same but just different names, but still I think that the problem is only on htc sim free version.
I am using BEPE 0.67 PREMIUM with 1.64.08.21 radio and never had problems with bluetooth or camera.

sumitescp said:
I know that they are same but just different names
Click to expand...
Click to collapse
no.... they are different!

.ForumUser said:
no.... they are different!
Click to expand...
Click to collapse
How is that please can someone explain to me? I think that they are the same with didfferent names and looks. Correct me if I am wrong.

I have the same camera trouble.
Did anybody fix it?

CompleteIdiot said:
My problem is slightly different. Pictures are OK, but if you reduce the size of the jpg (for emailing for example) the quality is appalling. I thought the if you reduce picture SIZE, quality should go up, not down?
Click to expand...
Click to collapse
No this is correct and happens any time you reduce the file size of an image.
To make the file smaller it has to make the data size of the photo less. To do this it has to get ride of information which makes the image smaller.

Touch Pro Screen problem

Hi all
just wondering how many people have experienced an issue with their htc touch pro's
when using pocketxpdf or any program which has a grey/brown background, on the bottom edge of the screen there is a band about 7mm in height where the screen flickers. and then when the handset is flipped into landscape mode, you can see a ghosted image of the bottom bar again on the left edge
how many people have this issue?
when i have my camera in my hands tomorrow i will post a picture up to show what i mean

About the landscape issue.. I've started a topic some time ago.
http://forum.xda-developers.com/showthread.php?t=443466
videos included.
poor video drivers.. who knows..

Exact same issue
I have this same issue. I noticed it after I flashed NATF's v1.2 Rom and applied the HTC Black v.1.93 1.1b theme using the Diamond Configurator, it seems to want to be grey and the HTC Black wants it to be black, not sure if this is what makes the bottom bar flash only.
I then tried to install the Sprint theme using Diamond configurator and the flicker lessened but stil noticeable probably due to the all black background. As soon as I turn to landscape it ghosts and lines begin to flicker on the far right.
Not sure if I should reflash the Rom...or if theres some other way to address this.

Aicks!.. duke_stix now I truely understand what you're talkin about. Today, I was listeing to radio. After a couple of hours I changed the volume and surprise, i've seen a gray band in the bottom area, near the black burned dots from the display edge (I've got 4 dots. 2 in the left , two on the right, both are parallel.. and they are visible on light/white images when looking at a different angle). Damn, it was so visible!.. I've restarted it and the band was still visible on the splashsreen.. I've pulled of the battery, restarted again.. still visible.. After a while it started to fade slowly.. right now I really can't notice the band..
duke_stix any updates on yours?
Here's how my "burned" dots are looking.. i hate 'em!

This time, badly. The margins had the previous image. The issue fixed by itself in about 1 hour.
It was looking something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(image posted by pierreye in this topic)

has anyone ascertained the cause and found some solution.
I just noticed the exact same thing today ..
i dont know if it is a previous problem i noticed today or it has been forever ..
the only thing that happened today b4 i noticed the issue was that the phone got hung on today screen .. completely unresponsive ... for about 1 hour .. i then removed battery to reset .. later i found this screen issue ...

Hi there,
Well guyz, since last night, I ve been analyzing the problem. I seem to have found a temporary solution, not something professional though.
Its not a permamnent damage (thats for sure).
I was seeing the shadow of the bottom bar of TF3D showing "Programs" and "Phone" ... however, i went to the weather menu and put my phone standby from there. After 5 min when i switched it on and went to volume screen I saw the shadow of bottom bar saying "5 Day" and "Menu".... Thats means that wherever you are at the point of standby, somehow, the bottom part of that screen is shadowed after power on ..
SO last night while going to sleep, I took a total black picture and went to alum and opened the picture in full screen mode. at that point i put the phone to standby . when i power it on in the morning no shadows are there, the screen is crystal clear.... and now i ve been using the phone for half a day and it has not emerged .. maybe if this procedure is followed every night, the screen will kinda reset all pixel memory. its too early to conclude, but a positive start though ... maybe u guyz can try it too and let me know the results ..

I have the same problem on my screen bottom 2x high area then the softbar .... annoying i thought RMA is the only solution.... but is not always visible.

ignore please

I had this problem on my first Fuze except it was happening at the bottom taskbar. I noticed it when I would go into apps like the camera... which you could still clearly read the softkey buttons WHICH WEREN'T there at all. lol
I ended up returning the Fuze for another and haven't had a problem since. I'm glad I caught it when I did or else I would be stuck with it.

I got the same problem
Hi all
I got HTC Pro for several days, when i played game in grey backgroud, and use screen test software, i found the same problem.
I will show pics as follow
Sorry for my poor english!

I have the same issue
My fuze does this as well, and a nothing i have tried cures it. Also, my home screen has an overlay of a person's silouette (presubably from contacts) that I cannot get rid of. Around the time that this showed up, my fuze stopped syncing too. I'll try to post a screenshot later to show this.

Hey guys there is nothing to do with the screen itself... is something related by grafics controller i gess reason why?
I got my screen broken a few days ago because i droped my tp and is landed on its face but i got the same screen problem before...
i bought a creen replacement online is just arrived yesterday 1.5 hous serious play with the new screen because the factory fitted screen glued together with the touchpanel. This came apart LCD+Digitalizer board
Now i still got the same problem i really hate that phone now i sent almost £500 on it top of that i got no warranty now and still got problem with my screen THX next time i buy cheap phone NK3300 maybe... i hope there just something to do with SPL so i just hope soon we see 5.05 or 5.08 SPL from olipro and cmonex

hi guys!
the screen flickers started to bother me
i see phone an program tabs on all the programs of the phone
is there anyone who found a solution?
thanx guys for cooperation

Hi all!
Have a same problem(((
Tryed to change ROM from 1.90.411.3 to 5.05.411.3 - it doesn't work.
Tryed to turn off TF3D as well - same result...
Does anyone know - is that an hardware problem or OS bug?
How it looks on my device:

ignore please

Same problem as above EXACTLY, my Touch Pro's serial # is: HT835K....

My phone is a stock, unmodified Vodafone UK model. ROM 1.90.161.5
I have the same problem exactly, just like in the screen shots
It only started a week ago and I've not added any software. Making me suspect it could be a deteriorating GFX chip/RAMDAC.
My serial is H837K00....
EDIT : Email sent to HTC, I'm not impressed with this, especially as they've fixed the same issue on the Touch HD.

ignore please

Response from HTC
Dear valued HTC customer, Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns. You recently wrote us about an issue that you have encountered with your Device This has not been a known fault to us at this time, XDA developers is a Worldwide based forum, thus meaning there may have only been a few instances where this has happened in the uk. at this time you are right there is no fix for this as there hasnt been a great deal of feedback on this issue, Im afraid that you wont be able to download the HD fix as its a different device and may cause more problems if done so. All i can do at this time is pass this on to the developer department as a request to be looked in to. so please keep checking the website for updates as we will post it on there if one becomes avalible. However you can try doing a hard reset to see if this fixes the issue, 9 times out of 10 it will but we can only try it to see. bare in mind that doing so you will need to update all data befor doing so. If the above steps do not resolve your issue, we invite you to visit the support area on our Web site. Please go to: http://www.htc.com/www/support.aspx Or you can go to: http://www.htc.com/select_country.htm, select your country and then click on the Support tab. You can also call our Call Center at: 08458900079 if you have further questions. Thank you once again for your continued patronage. Best regards, Europe customer support team HTC Corp. Global Service Division
Click to expand...
Click to collapse
My response
You say there is is no fix. So referring me onto your website and phone line is clearly an attempt to make me go away. I WILL NOT GO AWAY. You have acknowledged the exact same issue on the Touch HD, clearly there is a problem and clearly someone there knows how to fix this. There are a significant number of users with this exact problem and we demand that it is addressed urgently. Please pass this issue to the Technical Manager for escalation and be aware that the community will be seeing your responses. Best regards, Richard Griffiths
Click to expand...
Click to collapse

Hardware keyboard; unwanted key detection

I noticed that my Photon Q detects sometimes unwanted keys when I type fast.
i. e. "Hello, I am Loader009" can result in "Helloq, I am Loader009" or "Hello, I aam Loader009".
I never hit the q key but it is there.
I can understand the double character but I'm typing pretty fast so this actually shouldn't happen.
This happens randomly, I cannot replicate this.
Theoretically this can be an hardware-issue (the keyboard itself isn't really dirty).
Has someone else maybe noticed this on their Photon Q?

It's gotten worse but it seems to be a hardware issue.
My keys "O" and "K" are frequently failing or double-typing. The key "N" is also affected but not like the other two.
It seems that I have to open the phone and look for dust or something like that.

I have this issue on one of my Q phones also.
I get letters doubling up, or not registering, and it is when I type fast also, although not always. Thinking it might be a sticky key or something. I'll swap out the decal/sticker & see if that fixes it, & let you know.
This handset had issues with my 'A' key not registering every time, but I swapped the 'A' metal spring/disk with the 'sym' one under the sticker, and now they both work fine. Probably overworked the 'A' key a bit.
Sent from my SIM-modded Photon Q

Loader009 said:
It's gotten worse but it seems to be a hardware issue.
My keys "O" and "K" are frequently failing or double-typing. The key "N" is also affected but not like the other two.
It seems that I have to open the phone and look for dust or something like that.
Click to expand...
Click to collapse
Ok, I've changed the membrane/sticker for the keyboard, and now everything is sweet! I'm using the PQ that had the same issue as yours to type this, and there is no errors when typing, whereas before I couldn't get 2 words in without errors.
Not sure if you can clean up your own sticker, I have a couple of spare boards & swapped the sticker over.
Hope that helps you out.
Sent from my PHOTON Q using XDA Free mobile app

That's nice to read.
In a german forum there are also some persons with this problem.
In my case it looks like the letters "o", "k" and "n" are affected, sometimes the space key also.
Other keys works fine, at least I haven't noticed more of those symptoms.
(I rarely use numbers but I'm sure one of those number has to be affected too.)
I definitely will try to clean up my stickers and also open the phone and clean up with isopropyl alcohol the keyboard backside/connections.

Loader009 said:
That's nice to read.
In a german forum there are also some persons with this problem.
In my case it looks like the letters "o", "k" and "n" are affected, sometimes the space key also.
Other keys works fine, at least I haven't noticed more of those symptoms.
(I rarely use numbers but I'm sure one of those number has to be affected too.)
I definitely will try to clean up my stickers and also open the phone and clean up with isopropyl alcohol the keyboard backside/connections.
Click to expand...
Click to collapse
I'd try swapping the metal discs under the sticker with ones from barely used keys - could be the ones that are sticking have worn out a bit. I'd suggest cleaning the board contacts, and avoid washing the glue off the sticker.
Sent from my PHOTON Q using XDA Free mobile app

How was everybody doing with these symptoms? Cleaning out was successful? Should we order some parts for that? what do you think?

mh strange....
I would guess it's a cm11 software issue.
I've also got this problem for about 2-3 months now.
The frequency the problem appears differs from build to build.
let's say 50/50 ;D

Arguably, this would be a hardware issue. You can experience this with almost any year-old querty phone...
The question here is :
1. whether the dirt under the dome or on the pcb is causing this?
2. whether the loosened sticker above dome is causing this?
I doubt dome itself can be worn out...

I have two used PQ from the US. Both have had this issue in vanilla ROM. (Also in CM11.)
Not as extreme as mine (about 1 year and 10 month old) but the issue is there.
I suppose that this issue was the reason to not keep those devices

The input code hasn't changed for a year or so. Therefore seeing it as cm11 issue ("differs from build to build") is nonsense - just run stock firmware on your device for a while... It'll be the same.
It's clearly the hardware - the contacts wear off and produce more and more chaotic output at the moment when buttons are being pressed and released.
Regarding the software side - what we could do to help to overcome this issue is to increase the debounce time.
https://github.com/CyanogenMod/andr...1.0/arch/arm/mach-msm/board-mmi-keypad.c#L168
Currently it's set to 15ms. The max is 20ms (it has to be the power of 5, so increase to 20ms is the only easy option):
https://github.com/CyanogenMod/andr.../drivers/input/keyboard/pmic8xxx-keypad.c#L42
https://github.com/CyanogenMod/andr...drivers/input/keyboard/pmic8xxx-keypad.c#L586
There's also ghost key detection taking place in pmic8xxx-keypad.c, so theoretically we could try to improve it. But I don't hold my breath expecting anyone to come up with improved algorithm for it.
I'm open for suggestions, but nothing done on SW side can be compared to the results achieved with clean HW contacts that produce less signal bounces.

kabaldan said:
The input code hasn't changed for a year or so. Therefore seeing it as cm11 issue ("differs from build to build") is nonsense - just run stock firmware on your device for a while... It'll be the same.
It's clearly the hardware - the contacts wear off and produce more and more chaotic output at the moment when buttons are being pressed and released.
Regarding the software side - what we could do to help to overcome this issue is to increase the debounce time.
https://github.com/CyanogenMod/andr...1.0/arch/arm/mach-msm/board-mmi-keypad.c#L168
Currently it's set to 15ms. The max is 20ms (it has to be the power of 5, so increase to 20ms is the only easy option):
https://github.com/CyanogenMod/andr.../drivers/input/keyboard/pmic8xxx-keypad.c#L42
https://github.com/CyanogenMod/andr...drivers/input/keyboard/pmic8xxx-keypad.c#L586
There's also ghost key detection taking place in pmic8xxx-keypad.c, so theoretically we could try to improve it. But I don't hold my breath expecting anyone to come up with improved algorithm for it.
I'm open for suggestions, but nothing done on SW side can be compared to the results achieved with clean HW contacts that produce less signal bounces.
Click to expand...
Click to collapse
Thanks for the insight!
How can we, the average users who managed to keep up with nightly installs, try to apply this hack ? I don't think we can fork or recompile anything...

palmwangja said:
Thanks for the insight!
How can we, the average users who managed to keep up with nightly installs, try to apply this hack ? I don't think we can fork or recompile anything...
Click to expand...
Click to collapse
I've built a stock CM kernel with this value changed to 20.
See if it helps. Don't let the anykernel zip scare you, I assure you it's the CM kernel repacked with my anykernel edify scripts (I'm lazy.)
test-anyker.zip

palmwangja said:
How was everybody doing with these symptoms? Cleaning out was successful? Should we order some parts for that? what do you think?
Click to expand...
Click to collapse
Hi guys - I've had my notifications turned off, so only catching up with convo just now.
My key presses have had no issues since I cleaned the contacts on the pcb, I also swapped the disc out under the problematic key.
On my other Q I swapped the whole sticker inc discs, & it is also fine.
It def seemed to be a S/W issue, & I was getting frustrated with the ROMs, but in the end, it was H/W related.
If you are having issues, just try the clean. If you still have some trouble with certain keys, swap the disk with one from an un(barely)used key.
You may be pleasantly surprised.
Sent from my PHOTON Q using XDA Free mobile app

Before I flash a modified kernel, I've cleaned up (the metal pads and PCB).
atm it helps, the issue seems to be gone. But I think it won't last for a long time.
A bit OT: The keyboard technique used in the PQ is a bit complicated. Good for a flat device but hard to swap/repair. I would've used another PCB just for the keyboard... but I'm not an engineer.
Another thing: I found the reason for my random reboots. The ribbon cable is damaged and I replaced the screen-part. At least those random reboots should stop.

This is what I ended up yesterday...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I exchanged + shaped domes with o shaped domes I procured when I was using Xperia X1
The symptom was obviously cured, but who knows...

That's crazy, surely took an hour or so to do it nicely.
Lets wait and klick on the keys until the issue comes back!

looks like this sw fix was applied in the recent nightly! Thanks!

[Q] Issues after update 5.0.1

Im experiencing some issues with the display of some apps since the last update, first one is with floathing stickies https://docs.google.com/file/d/0B5liuSQRuRTSc3lJQlZTb3NNR28/edit?usp=docslist_api and the other is with Go SMS pro while I'm scrolling in the themes section, i couldn't get a screenshot of this but i guess everyone has that app and can check by theirselves. Its there anyone else having these issues and what other apps have you encounter affected?

Lollipop is ART, ART has inconsistencies... could just be a feature now. :/
I've seen similar floating issues when I used Picsay Pro recently... guessing some of the older top-tier apps haven't braced for the sudden change.

I have some rendering issues in some apps, like Puffin browser, now and then half of the screen is filled of flickering lines.
Battery life is dissapointing, not that it was very impressive before anyway.
Two times it has just charged a few percent overnight, it usually charges to 100 %.

All I can recommend is to keep sending ANR reports and always contact the devs with app issues. Make sure you say you're on 5.0.1.

Disable HW overlay in dev options and rendering is fine again, only problem is this introduces stuttering in animations/scrolling... (Went back to 4.4.2 myself because of all the bugs in lollipop)

I haven't had any rendering issues or floating icons, but what I'm having a serious problem with is bluetooth, before on kk i was able to hook up a ps3 controller via usb otg, and then after about a minute i could unplug the ps3 controller and it would sync with bt, now it works with otg but as soon as i unplug it the shield tells me that a ps3 controller is trying to pair with it but it asks me for a 4 digit pass code.
I did some research and found out that allot of people have this issue, actually everyone, A's no one can sync a ps3 control, i would use six axis, but i can't for two reasons, first reason is, i play a few games by Gamevil, and they have xignicod3 for security, so it detects six axis as a ts the game down, and second: if i don't hook up the controller natively, the gamepad mapper won't work, when i plug the controller in, it detects it as if it was an nVidia controller minus the nvidia button.
So i did some testing after, i tried to restore back to kk but now once bt detects the controller, i get a crash with an error saying "unfortunate bluetooth pair tool has stopped" every time without fail....wtf?
Any one have any suggestions?

dape16 said:
I have some rendering issues in some apps, like Puffin browser, now and then half of the screen is filled of flickering lines.
Battery life is dissapointing, not that it was very impressive before anyway.
Two times it has just charged a few percent overnight, it usually charges to 100 %.
Click to expand...
Click to collapse
You can try calibrating your battery, and also with the last update you can set the number of cores and the frecuency of them.

Ive gone threw 2 power cycles and my battery is showing 0% the whole time i use it. I installed Better Bat Stats and it shows the proper battery amount...I thought the OS would need to calibrate but it just cant figure it out. Still getting around 4-5 hours with movies and games and music.....I have experienced the floating banners keep flickering from different sizes very rapidly. Oh, and the stock charger cant keep up.
Has anyone noticed in the middle of doing something you hear a sharp electrical kinda CODE (dzzwirp) sounding?? Only happened a couple times, but kinda scary. Its diffidently channeled to threw the speakers when it made that noise.
Just stock not rooted/wifi

adjday said:
Ive gone threw 2 power cycles and my battery is showing 0% the whole time i use it. I installed Better Bat Stats and it shows the proper battery amount...I thought the OS would need to calibrate but it just cant figure it out. Still getting around 4-5 hours with movies and games and music.....I have experienced the floating banners keep flickering from different sizes very rapidly. Oh, and the stock charger cant keep up.
Has anyone noticed in the middle of doing something you hear a sharp electrical kinda CODE (dzzwirp) sounding?? Only happened a couple times, but kinda scary. Its diffidently channeled to threw the speakers when it made that noise.
Just stock not rooted/wifi
Click to expand...
Click to collapse
I have heard those wierd audio glitches too when watching videos mostly youtube.

Iams1002 said:
You can try calibrating your battery, and also with the last update you can set the number of cores and the frecuency of them.
Click to expand...
Click to collapse
Could you direct us to where those options are available? In 5.0.1 not rooted, I cant seam to locate any of those options. My battery (OS display) allways shows completely dead and the OS still wont show any amount that was put back in to it. I have ran the tablet down about 5 cycles and still wont calibrate. Ive placed an email to Nividia for help as well. If/when I get a response ill post up......thanks for any help.

dape16 said:
I have some rendering issues in some apps, like Puffin browser, now and then half of the screen is filled of flickering lines.
Battery life is dissapointing, not that it was very impressive before anyway.
Two times it has just charged a few percent overnight, it usually charges to 100 %.
Click to expand...
Click to collapse
I suggest you to install the full nvidia recovery image, i did that, i installed the 1.2 RoW(mine is US so bye bye ATT useless app and OTA delays), doing that solved battery issues, looks like updating via zip causes issues even after doing a factory reset. You can do that then an OTA update and i dont have anything to complain about 5.0.1 except the rendering issues, so im in Kitkat again. DON´T USE A CALIBRATING/REPAIRING BATTERY APPS SEVERAL TIMES OR IT WOULD DAMAGE YOUR BATTERY PERMANENTLY LOWERING YOUR BATTERY CAPACITY AND/OR MAKING IT SELFDISCHARGE(EVEN TURNED OFF) AND EVENTUALLY IT WILL BECOME COMPLETY UNUSABLE it sadly happended to my previous tab .
The rendering issues are a common Lollipop 5.0.1 problem not Nvidia. So we have to wait next OTA.
adjday said:
Could you direct us to where those options are available? In 5.0.1 not rooted, I cant seam to locate any of those options. My battery (OS display) allways shows completely dead and the OS still wont show any amount that was put back in to it. I have ran the tablet down about 5 cycles and still wont calibrate. Ive placed an email to Nividia for help as well. If/when I get a response ill post up......thanks for any help.
Click to expand...
Click to collapse
You will find the the cores and frec adjustments, in
Configuration----SHIELD Energy Managment----Processor Mode---- My energy mode----Customize My energy mode (not sure if those are the names in english my tab is in spanish hehe).
Changing the number of cores just gave me 10 min more of clash of clans gaming using 20% of the charge so i got around 1:10 of gaming. I recommed you to do the Nvidia recovery install.

MasterSe7en said:
So i did some testing after, i tried to restore back to kk but now once bt detects the controller, i get a crash with an error saying "unfortunate bluetooth pair tool has stopped" every time without fail....wtf?
Any one have any suggestions?
Click to expand...
Click to collapse
Did you install nvidia recovery image via adb? restoring a backup file from kitkat in lollipop seems to make system inconsistences, i did it and saw my tablet reboot twice with Android L splash screens letter and then the kitkat old android letters.

I get these weird graphical glitches on some apps, autodesk sketchbook pro, (which i've let the devs know) but also through google play games. Anytime it shows that I logged into a game or get an achievment the google games comes down from the top of the screen like its supposed to, but it has all these artifacts with it too, goes away after about a second and then all is golden, glad to see that it wasn't just my tablet though. I was not really up to the idea of RMA'ing my device since it's finally all "set up" and personalized like I like.
I've also tried to screenshot, and record it with an app, but it doesn't capture the errors in the video, it looks normal.
---------- Post added at 10:46 AM ---------- Previous post was at 10:35 AM ----------
Here's some shots taken from my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

contesauce said:
I get these weird graphical glitches on some apps, autodesk sketchbook pro, (which i've let the devs know) but also through google play games. Anytime it shows that I logged into a game or get an achievment the google games comes down from the top of the screen like its supposed to, but it has all these artifacts with it too, goes away after about a second and then all is golden, glad to see that it wasn't just my tablet though. I was not really up to the idea of RMA'ing my device since it's finally all "set up" and personalized like I like.
I've also tried to screenshot, and record it with an app, but it doesn't capture the errors in the video, it looks normal.
---------- Post added at 10:46 AM ---------- Previous post was at 10:35 AM ----------
Here's some shots taken from my phone
Click to expand...
Click to collapse
I get exactly the same graphically anomalies! I'm impressed with this release as it performs much better in speed and smoothness for me and I can use Facebook on it again. But the graphic anomalies really annoy me. I can also no longer return to kitkat as when I flash the system.IMG it fails with "couldn't allocate enough space on device" and fails to flash. I had to install the EU-LTE recovery from @twistedumbrellas kernel post to then flash the full nvidia lollipop .zip and lucky booted and checked storage etc. Back up and running and storage reporting everything is fine. But graphical anomalies are still present. Damn it. Lol. Well at least they are working faster than one plus one with their alpha release after three month's. Lol..

Yeah, I haven't tried the HW overlay thing in dev options but I may give that a go when I'm using my autodesk sketchbook and then just switch it back when I'm gaming. Other than those anomolies, (an some weird high pitched squelch thing that happens every once in a while) I love lollipop on this thing. I feel like chrome is in NO WAY optimized for this though, it's terribly slow, but I use it on my phone where it flies and I like being able to sync tabs and open pages/history etc.

Hi,
My post will probably spam, but I have the same graphics issues It started after upgrade to A5. I also tried to send issue message to developers, but seems the service is broken on my device. It fails to send message.

contesauce said:
I get these weird graphical glitches on some apps, autodesk sketchbook pro, (which i've let the devs know) but also through google play games. Anytime it shows that I logged into a game or get an achievment the google games comes down from the top of the screen like its supposed to, but it has all these artifacts with it too, goes away after about a second and then all is golden, glad to see that it wasn't just my tablet though. I was not really up to the idea of RMA'ing my device since it's finally all "set up" and personalized like I like.
I've also tried to screenshot, and record it with an app, but it doesn't capture the errors in the video, it looks normal.
---------- Post added at 10:46 AM ---------- Previous post was at 10:35 AM ----------
Here's some shots taken from my phone
Click to expand...
Click to collapse
Whoah, I get the same exact graphical glitching too! Glad to know I'm not alone, I just bought the Shield and almost RMA'd this thing thinking I had a defective unit (what between this bug and chrome crashing my tablet).
Anyhow, I had found a temporary fix that seems to make those artifacts go away. If you enable the developer options (if you don't know, go settings, tap about tablet, tab build number 7 times, unlocks developer options in settings menu) and enable "Force GPU rendering", it seems to make all the weirdness go away. It might kill your battery slightly faster, but you can always disable it again after you're done using the app. Kind of a PITA, but seems to work. Hope that helps.
Anyhow, I'm new to the Shield tablet scene, basically updated to lollipop right from the get go. So those graphical glitches didn't exist in kitkat? Was chrome always so slow? Man I hope this tablet gets it together soon, it will be awesome once it realizes its full potential.

Chrome is still a problem, wasn't such an issue with KitKat but I'm thinking it's an issue between the Nvidia kernel and lollipop. Once we have another update I'm hoping it'll be better compatibility.

suddenly, my Mate 9 restarts randomly

my phone restarts by it self randomly, 3 times so far, 2 today,
did it happen to any of you guys?

Even worse: yesterday, completely spontaneous factory reset when I was not using the phone. I sent a message to Huawei about this. L29, B126.

That's not good at all! I hope for the rest of us yours is an incident by itself...

May be an individual case mine is ok, thank GOD
Sent from my MHA-L29 using Tapatalk

i looked into battery info before i charge the phone, the phone lost about 7-9% in that restart, there's a gap in the battery diagram, and the phone kept getting empty a little quicker !!!

Hallo all,
I have the same kind of problem.
Automatic restart of the Mate 9. frequention about one time a week. After restart some settings were changed.
The setting for standard location for memory was SD card.
After restart each time it was set to Internal memory. It seems to be a smal structural problem.
I reported this to Huawei NL. Regards.

Not sure if that is the cause of your problems, but haven't seen it mentioned here: there's a scheduled restart of the phone that can be programmed in the settings (Smart Assistance/Scheduled Power on and off). Maybe you guys enabled it by mistake?
Sent from my MHA-L29 using XDA-Developers mobile app

Mine did the same too a few days back, was on B126.
It was rebooting every 5min. Got pissed off and exchanged it for a new unit.
It's my 3rd day on this one, no reboots so far, but still too soon.
Crossing fingers here ...

thbosch said:
Hallo all,
I have the same kind of problem.
Automatic restart of the Mate 9. frequention about one time a week. After restart some settings were changed.
The setting for standard location for memory was SD card.
After restart each time it was set to Internal memory. It seems to be a smal structural problem.
I reported this to Huawei NL. Regards.
Click to expand...
Click to collapse
I also checked the settings for scheduled start and or stop were disabled both.

Could it be a rogue app? I don't have this issue, though I am still on B110

Seifer1975 said:
Could it be a rogue app? I don't have this issue, though I am still on B110
Click to expand...
Click to collapse
I only noticed the issue on B126. I was on B110 for nearly 2 weeks and didnt encounter the issue, but then again it wasnt my daily driver so couldve happened without me noticing...
I doubt its a rogue app as I have the same apps on all my phones, except for "built-in" ones from different vendors. And I tend to remove/disable most bloat.
B126 felt like a step up from B110, but it's not yet polished, its more like a day one firmware that needs an update or two to work well. Some of us are still facing issues with touch response due to palm rejection, or delayed push notifications.
Crossing fingers for quick and solid updates here, I really like the phone and would love it with less bugs.

samxxx99 said:
I only noticed the issue on B126. I was on B110 for nearly 2 weeks and didnt encounter the issue, but then again it wasnt my daily driver so couldve happened without me noticing...
I doubt its a rogue app as I have the same apps on all my phones, except for "built-in" ones from different vendors. And I tend to remove/disable most bloat.
B126 felt like a step up from B110, but it's not yet polished, its more like a day one firmware that needs an update or two to work well. Some of us are still facing issues with touch response due to palm rejection, or delayed push notifications.
Crossing fingers for quick and solid updates here, I really like the phone and would love it with less bugs.
Click to expand...
Click to collapse
If you have the reboot and touch issue that means a hardware problem.
I was on b110 and now b126 without any of the problems above.
But true the software need lot of improvement to be more polished.

gm007 said:
If you have the reboot and touch issue that means a hardware problem.
I was on b110 and now b126 without any of the problems above.
But true the software need lot of improvement to be more polished.
Click to expand...
Click to collapse
I'm actually on my 3rd mate 9 so far, and only the second had the reboot issue.
But screen missing some touch was there on all 3. I'm. Pretty sure it's touch rejection issue as when I enable tap indication in Dev settings it shows all taps.

gm007 said:
If you have the reboot and touch issue that means a hardware problem.
Click to expand...
Click to collapse
You are jumping to conclusions without any justification for them.
The touch screen issue seems to be broad, there's a lot of complaints about that. I've you're not too picky you may not notice it but I am so I have noticed some responsiveness issues every now and than. I think that is a software issue where the area the finger touches the screen is perhaps not interpreted correctly (touch diameter too small).
And sudden reboots are well documented sw issues which are often fixed with a software release.
Sure, it could be hardware but it very well can be sw as well.

blackspp said:
You are jumping to conclusions without any justification for them.
The touch screen issue seems to be broad, there's a lot of complaints about that. I've you're not too picky you may not notice it but I am so I have noticed some responsiveness issues every now and than. I think that is a software issue where the area the finger touches the screen is perhaps not interpreted correctly (touch diameter too small).
And sudden reboots are well documented sw issues which are often fixed with a software release.
Sure, it could be hardware but it very well can be sw as well.
Click to expand...
Click to collapse
How to replicate the touch issue?

gm007 said:
How to replicate the touch issue?
Click to expand...
Click to collapse
An easy way for me is small objects in the top right corner , like when I try to tap the settings icon. It's either that the recognition area is too small or rejected. I noticed the issue is more prominent in built in software. Don't have this issue in apps from Google ...
Sent from my MHA-L29 using XDA-Developers mobile app

samxxx99 said:
An easy way for me is small objects in the top right corner , like when I try to tap the settings icon. It's either that the recognition area is too small or rejected. I noticed the issue is more prominent in built in software. Don't have this issue in apps from Google ...
Click to expand...
Click to collapse
So why I'm not having this issue? I tried clicking the settings maybe 50 times and all my touch are registered.
Do you have any screen protector on ur screen?

gm007 said:
So why I'm not having this issue? I tried clicking the settings maybe 50 times and all my touch are registered.
Do you have any screen protector on ur screen?
Click to expand...
Click to collapse
I attached a screenshot of the icon I tap in the battery section, can u try it out a couple of times ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MHA-L29 using XDA-Developers mobile app

samxxx99 said:
I attached a screenshot of the icon I tap in the battery section, can u try it out a couple of times ?
Click to expand...
Click to collapse
I just tried it and no problem, I can't remember how to use the screen recorder so i can upload for you my testing.

Also no problems here. I've tapped the icon countless times and it always registered. Also no random reboots to report. MHA-L29 running B126.