Database Info

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!

iNew V7 Owners' Thread

I recently bought this phone and am absolutely in love with it!
Superb camera, style, weight, speed, screen!
Anyone else bought this phone? Share your experiences, issues, finds, updates etc.

hows the gps
voiceferous said:
I recently bought this phone and am absolutely in love with it!
Superb camera, style, weight, speed, screen!
Anyone else bought this phone? Share your experiences, issues, finds, updates etc.
Click to expand...
Click to collapse
how is the gps working? can you share a signal strength screen capture?

voiceferous said:
I recently bought this phone and am absolutely in love with it!
Superb camera, style, weight, speed, screen!
Anyone else bought this phone? Share your experiences, issues, finds, updates etc.
Click to expand...
Click to collapse
I am very pleased with the phone too.
It feels very comfortable; the size is just right and is very lightweight and stylish.
Camera is very good, and the overall performance is excellent.
There are almost only pros for the phone: It is possible to use 3G with any of the sim cards; there is only one partition to install apps; it accepts 2 sim cards plus an sd card; It has 2 GB of RAM...
There is one concern, and that is the battery. I have only used it as a secondary phone for a few days, and I don't really know yet if the battery can last an entire day using it as my primary phone...
Another thing that bothers me is that the ring, notification and system volume are merged together, and you can't set different levels for each one...
sirpy said:
how is the gps working? can you share a signal strength screen capture?
Click to expand...
Click to collapse
I am using it in Portugal, and I have only made a satellite lock test. It works just fine, even indoors.

Got the iNew V7 about two weeks ago and it seems to be A-OK.
I use the phone as a mini-tablet. Bought, tracked and delivered (to USA) for $150.
Will be adding TWRP to do full backups and then will root it using the iroot instructions I found. Will report my findings on these efforts.
Must root phone to run xposed framework to run Bubbleupnp app in order to cast audio.
Put 32gig micro SD card in V7 but it does not recognize the SD card. Still working that issue. Geekbuying claimed max sd card size of 32gig.
Will report results and any phone foilbles.
Love the FM radio.

I purchased from POMP Mall Site, iNew V7 phone battery needs to be recharged every day.

I had this Phone for a week, and I am pleased . It has a nice battery life! Yesterday was an intense day of use, with data and wifi always active, GPS when needed , watsapp, facebook, 9gag . For more than 3 hours of screen time. Arrived at Night with 24 % battery still left .
And Really nice camera!
{
"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 concur, I've had this phone for about a month now and it's every bit fantastic. The word that best describes it - polished!
Everything is smooth, no bloatware, no hitches, no hiccups, no Chinese apps, no shoddy behaviour.
It's light, fast, superb screen and resolution, loads of RAM, fast CPU. The camera is excellent and GPS locks fast with great strength!
The battery? I use my phone for lots of calls and the occasional WIFI during the day. It lasts me 10 FULL days! I'd rate the battery 9.9/10!
I am very glad I paid slightly more for a higher-end device. It is worth every penny, and then some.
I think I'll be buying iNew from now on.

Hi there, got this handset delivered yesterday, and was extatic - everything about it was great, performance, battery, screen, looks... But today I'm thinking about selling it, because I encountered a problem that is a total deal breaker: touch screen. Today I discovered, that the phone is unusable due to constant "phantom" touches, that are happening when I'm typing text. Some happen on an adjacent buttons, but some on a buttons far from those I'm typing. Like, when I switch to the numeric keyboard and typing a lot of numbers, the phone just switches back to letters and so on. I entered a developers options and switched on options for showing touches and traces on screen, and was able to see, that sometimes when I make a brief tap on the screen, the trace of that tap is showing, that I made a line, and not a single dot. I tried to install several calibration programs, but none of them helped.
Did someone encountered the same problems? If so, how you managed to fix them?

Vindicator87 said:
Hi there, got this handset delivered yesterday, and was extatic - everything about it was great, performance, battery, screen, looks... But today I'm thinking about selling it, because I encountered a problem that is a total deal breaker: touch screen. Today I discovered, that the phone is unusable due to constant "phantom" touches, that are happening when I'm typing text. Some happen on an adjacent buttons, but some on a buttons far from those I'm typing. Like, when I switch to the numeric keyboard and typing a lot of numbers, the phone just switches back to letters and so on. I entered a developers options and switched on options for showing touches and traces on screen, and was able to see, that sometimes when I make a brief tap on the screen, the trace of that tap is showing, that I made a line, and not a single dot. I tried to install several calibration programs, but none of them helped.
Did someone encountered the same problems? If so, how you managed to fix them?
Click to expand...
Click to collapse
Hi, using the phone well over a month - I never experienced such problems at all. In fact, I think the touch screen is quite responsive and fluid, no "phantom" touches can be seen. I believe this could be a defect with your specific unit.

New official ROM http://www.needrom.com/download/inew-v7a/

pls help
hi i have a major problem with my inew v7.can someone make a backup with MtkDroidTools v2.5.3 and send it to me so i can restore mine.thanks

Second new official ROM INEW_V7A_4.4_v1.1.4: http://www.needrom.com/download/inew-v7a-2/
Download mirror links:
http://www.filedropper.com/inewv7a44v114part1
http://www.filedropper.com/inewv7a44v114part2
http://www.filedropper.com/inewv7a44v114part3

hi pleas help me my phone dead after flash , i flash thes :- http://www.needrom.com/download/inew-v7a-2/

pleas any one have a backup my phone stop work inew v7a

..
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
Vindicator87 said:
Hi there, got this handset delivered yesterday, and was extatic - everything about it was great, performance, battery, screen, looks... But today I'm thinking about selling it, because I encountered a problem that is a total deal breaker: touch screen. Today I discovered, that the phone is unusable due to constant "phantom" touches, that are happening when I'm typing text. Some happen on an adjacent buttons, but some on a buttons far from those I'm typing. Like, when I switch to the numeric keyboard and typing a lot of numbers, the phone just switches back to letters and so on. I entered a developers options and switched on options for showing touches and traces on screen, and was able to see, that sometimes when I make a brief tap on the screen, the trace of that tap is showing, that I made a line, and not a single dot. I tried to install several calibration programs, but none of them helped.
Did someone encountered the same problems? If so, how you managed to fix them?
Click to expand...
Click to collapse
Hi there, I have the same problem did you manage to resolve it by any chance?

Hi, U unfortunately flashed the v7am rom to my v7a phone and now bricked - can I solve this problem?

Sekypapa said:
Hi, U unfortunately flashed the v7am rom to my v7a phone and now bricked - can I solve this problem?
Click to expand...
Click to collapse
yes u can

i have ported cm12.1 for inew v7
everything is working excelent,better than stock
http://www.needrom.com/download/cm12-1-inew-v7/

Ok I'll try it. Will tell you soon how is going. If you can give us a guide for porting roms
Enviado desde mi V7 mediante Tapatalk
Edit: the post was deleted. there was no link even when the post was there.

jrodadoy said:
Ok I'll try it. Will tell you soon how is going. If you can give us a guide for porting roms
Enviado desde mi V7 mediante Tapatalk
Edit: the post was deleted. there was no link even when the post was there.
Click to expand...
Click to collapse
I removed rom,but in 1~3 back again

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.

Camera

Hi,
Motorola Droid Turbo. Ressurection Remix last version (7.x.x). I have problem with camera, "can't connect to camera". What I did? I try another app, restart phone, clear cache etc, hard reset, tried another ROM.
None of this things helped. I still have this problem....
What can I do?
Edit: flashlight is not working too. Camera app icon disapear

Here's my guess... You may have two camera apps installed (and possibly two galleries).
If you have two cameras there may be a conflict, and thus the one you are trying to use "can't connect". Also, in the past my flashlight didn't work when I had a camera conflict. The "flashlight" uses the camera's LED.
Use Titanium Backup to scroll down the list of your apps and freeze the camera app you do not wish to use.
Back when I was using CM12.1 a year ago, I had the CM camera/gallery installed as well as a Moto camera/gallery. I kept getting conflicts. So, I froze the CM camera, to use the Moto camera. But of the two galleries, I actually liked the CM gallery functionality over the Moto gallery, so I froze the Moto gallery. I mixed and matched the camera and gallery I wanted to use. It worked. After freezing the unwanted ones, there was no more "can't connect" error messages.
If you have two cameras (and/or two galleries), I would suggest FREEZING rather than removing, especially the one you are not using is a system app.
__________
If you don't have two cameras, then I suggests using a 2nd camera to see if that one works. You would of course want to freeze the "system" camera in Resurrection Remix when you install the 2nd camera, so you wouldn't have additional conflicts.
With Resurrection Remix 6.x, I now use this camera app. It's the G6 Moto camera ported:
Moto G5 camera for QUARK
https://forum.xda-developers.com/moto-maxx/themes-apps/moto-g5-camera-quark-t3575150
It installs as a "user app", not a system app. The camera that comes with Resurrection Remix, I have frozen.

What if it is hardware problem? I think maybe when the phone hit the ground, sth get loose.
Do you know I can fix it by myself?

$HaGraTH said:
What if it is hardware problem? I think maybe when the phone hit the ground, sth get loose.
Do you know I can fix it by myself?
Click to expand...
Click to collapse
$HaGraTH said:
Camera app icon disapear
Click to expand...
Click to collapse
Why don't we go through the software options first? Software fixes are free.
And no, I don't know how to fix any hardware problem. But your phone hitting the ground wouldn't cause a camera icon to disappear.

I flashed with this thread (https://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724) this version Verizon Stock Kitkat /// VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip and still my camera doesnt work... Now it says that the "camera is busy" but even if I try to open it in security mode still is the same...

Ok... I got a new problem with this phone. The microphone is really bad, people with who I talked told they don't hear me. The problem is with my phone, not theirs.

$HaGraTH said:
I flashed with this thread (https://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724) this version Verizon Stock Kitkat /// VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip and still my camera doesnt work... Now it says that the "camera is busy" but even if I try to open it in security mode still is the same...
Click to expand...
Click to collapse
Really, you went all the way back to Kitkat?

yes, someone in the other thread told me this might help but it didn't. Now I am running custom 7.1.2 ROM again... but still nothing
If you can PM me your email I will send you film with my apps to show you that nothing should colide with camera...

$HaGraTH said:
yes, someone in the other thread told me this might help but it didn't. Now I am running custom 7.1.2 ROM again... but still nothing
If you can PM me your email I will send you film with my apps to show you that nothing should colide with camera...
Click to expand...
Click to collapse
Just post screenshots here in this thread. That way others can help also. In Titanium Backup, show the section where camera is. I'll post mine right now, so you can see...
I have three cameras installed, but two are frozen.
{
"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"
}
Try installing that other camera above (ported Moto G5 camera). Now I'm curious what happens if you have two cameras?
You may have a hardware issue, and if so I cannot help you there.

As you can see I did it what you told me. I also have screen record but I can't post it here
The camera which is busy is the one which I downloaded (but when I tried used it the system camera was frozen)
the system camera have always "can't connect"
I did it on the "clean" ROM

You may have a hardware problem then.

Today I go to the place where the PC and phones are fixed. Someone told me about imei, radio and sth like that. He said that I should tried to install it again.
I don't know but I think that this things was done when I install factory image. Am I right?
I think this person didn't know what he is talking about... but maybe I am wrong

There was a user with a similar problem a year or so ago. He had to replace the FRONT camera and that fixed the problem with the rear camera. I know it sounds strange, but that was why the camera couldn't connect, because besides connecting to the camera, you should also have the ability to switch cameras from back to front. Since the front camera was messed up, the camera software couldn't even connect to the rear camera.
It does sound more and more like a hardware issue, but it may not even be your rear camera. Could be the front camera.

Hi! Turbo can't record 60fps at present day?

Unreal_man said:
Hi! Turbo can't record 60fps at present day?
Click to expand...
Click to collapse
What does the Moto Camera app say it can record? That's what it can record. We have updated app to give better quality but no new "features" have been added, that I know of.
https://forum.xda-developers.com/moto-maxx/themes-apps/moto-g5-camera-quark-t3575150

ChazzMatt said:
Here's my guess... You may have two camera apps installed (and possibly two galleries).
If you have two cameras there may be a conflict, and thus the one you are trying to use "can't connect". Also, in the past my flashlight didn't work when I had a camera conflict. The "flashlight" uses the camera's LED.
Use Titanium Backup to scroll down the list of your apps and freeze the camera app you do not wish to use.
Back when I was using CM12.1 a year ago, I had the CM camera/gallery installed as well as a Moto camera/gallery. I kept getting conflicts. So, I froze the CM camera, to use the Moto camera. But of the two galleries, I actually liked the CM gallery functionality over the Moto gallery, so I froze the Moto gallery. I mixed and matched the camera and gallery I wanted to use. It worked. After freezing the unwanted ones, there was no more "can't connect" error messages.
If you have two cameras (and/or two galleries), I would suggest FREEZING rather than removing, especially the one you are not using is a system app.
__________
If you don't have two cameras, then I suggests using a 2nd camera to see if that one works. You would of course want to freeze the "system" camera in Resurrection Remix when you install the 2nd camera, so you wouldn't have additional conflicts.
With Resurrection Remix 6.x, I now use this camera app. It's the G6 Moto camera ported:
Moto G5 camera for QUARK
https://forum.xda-developers.com/moto-maxx/themes-apps/moto-g5-camera-quark-t3575150
It installs as a "user app", not a system app. The camera that comes with Resurrection Remix, I have frozen.
Click to expand...
Click to collapse
thank you so much m8, this is what was really happening, just uninstalled any other camera and worked like a charm !!!