Database Users

[RELEASE]HTC-BlueAngel 6.5 5.2.21176WWE2CX3.1 by sun_dream

Seems sun_dream found yet another build, hes saying is pretty fast, i cant wait till he releases it, heres the link to his blog post
edit:heres a mirror thx to homam_france

He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!

I hope the shell won't distort the OK and X Buttons anymore

egzthunder1 said:
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
Click to expand...
Click to collapse
Great, I just installed Xplode's R3. But i want to try it too.
egzthunder1 can i test it too?

i better get my BA fix up ASAP, the hardware buttons are not so responsive, it seems I am going to be busy flashing

Well,
Day 1 after flashing sun_dream's latest. So far, very fast and stable. Here are the main points (in my opinion anyways)
*Titanium seems a lot more responsive than before (I still don't like it though )
*The removal of windows and menus animations make the device respond faster overall.
*Unbelievably responsive kinetic scrolling.
*The honeycomb is actually usable now!!
*Settings were put back into categories (Personal, System, Communications).
*Battery life seems good, no major drainage.
*"OK and X" bug fixed and working fine!!
*Wifi nice and steady (still need to test PIE8 and Iris Browser).
*Transparent Top bar looks awfully nice! (too bad the programs replace it with the Black bar)
Things I did notice were as follows:
*The Wifi icon seems to be getting cut off from the bottom down. In other words, you can only see half of the icon.
*Power in the Power Settings doesn't show a percentage anymore.
I still need to do some further testing (e-mail setup, etc), but overall this rom is superb!
Will report back later.
Good Job Sun!!!!!

he sent me a beta too but got a big problem...my cradle ain't working anymore!

red_hanks said:
he sent me a beta too but got a big problem...my cradle ain't working anymore!
Click to expand...
Click to collapse
You can always use mtty and flash via SD.

hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....

red_hanks said:
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
Click to expand...
Click to collapse
I havent' had a chance to test xplode's R3, but sun's is a very nice rom (so far anyways). I still have to test BT (headset and GPS).
One thing I did notice also, is that it seems that data transfer via AS is a lot faster than in previous builds... I guess M$ finally did something right
You can read the rest of my review in my previoius post. Good luck with your craddle situation

A little further testing...
*I purposely soft reset the device and it took approximately 1 minute to wake up completely and loading PointUI Home 2. So, it has a very fast wake up time!!
*I set up my g-mail account with no problem.
*I don't use SMS, so I cannot test that.
*Lock application seems a bit faster and more responsive than in older builds.
*PIE is a bit faster, but I still have other browsers that I like to use. I will test YouTube later (with both PIE and Iris).
Left to do...
*Test BT connection with headset, and GPS (Pharos BT receiver).
*Test IR/BT data transfer... (I have to find another BT and another IR enabled device to do this)
*Must finish going through the settings to ensure that they all work.
Will do more later...

ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...

red_hanks said:
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
Click to expand...
Click to collapse
BT = Bluetooth?
if so, it's always a trouble-maker

i found strange issue with lockscreen, when you have locked your device and pressed power (entered standby) and recieve a call the answer lockscreen part does not show upon device resume, this bug does not happen when device is locked and not on standby - you may try the scenario yourself, i think that this bug is present in 21169 too (no matter sun or my roms)
tested various rom configurations, rebuilded about 20 times this rom, but this nasty bug stays

as of now I am very contented with wm6.1 v3.02 by sun_dream. I need to use my BA so I think I will just wait for a more stable build of wm6.5

Well, I tested (tried to pair really), my GPS receiver, but no dice... For some reason, the device either looses connection or just flat out does not recognize the pass-code. The BT headset, on the other hand hasn't given me too much trouble. It paired up nicely...
@xplode,
I'll give it a shot, but I don't normally use my BA as a phone (unless I am traveling)... which I will do on Monday, so I'll let you know then.
Still stable and no SR so far, except for one time when I was using wifi and my device went into power saving mode (turned off the screen) and afterwards, it would only have a black screen... had to SR there. I tried to recreate the situation on a few occasions with no luck... I guess it was a one time thing.
More reports to come..

well i had the same thing today, blackscreen - only fixed with hard reset
soft reset gets me back to the black screen

This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.

if we just talk about it, Microhell can't do something about it... now if we link to it here DIRECTLY, then xda-developers is in Trouble.

April 1 said:
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
Click to expand...
Click to collapse
@April 1,
The reason is rather simple. If you release something that has bugs and things (something you would consider a pre-release), you will have an enormous amount of people asking the same questions over and over and over and over.... and over again (kinda like it is right now but worse).
It is a lot easier to develop something when the beta testers are finding all the minor things and not hitting themselves on the face with major bugs that might require hard resets and stuff.
We are not trying to keep anyone in the dark (that is why we are reviewing this build), but sun_dream will release it when he deems it is ready for public use. So far, he has not made mistakes (at least not many) in his ability to judge when a rom is suitable for release.
Just be patient... this should be out soon

["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)

["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)
Firstly, I would like to give a big Thanks to "somebody" as well as the dev team at the behind of these roms for their efforts to bring ISC & JB as great things to our device.
Recently, I've tried both the ICSROM (known as the tune of leaked Rom under CWM flashable zip - Let's click Thanks for Upndwn4par) and "somebody's" CM10 (let's click Thanks for ticiano_arraes) and saw that they both have identical issues as reported by people such as the battery life, the deep sleep, the camera flash... including working fixes. But the fixes spread over the pages of threads caused inconveniences for us to track or update info. So I would like to open new thread just for purpose of collecting bug reports and the fixes from and for both users and our devs to get latest info on these roms quickly.
Admins please feel free to delete if this thread is already opened or if it's just not neccessary.
Belows are lists of great things of ICS/JB given by these roms that you can taste right now, and also the list of bugs/issues along with the best possible solutions that you can try for workaraound while waiting for the perfect release. The lists will be updated upon report from you guys. So please provide any thing from your experiences on these roms.
* Great things:
** For both roms:
+ Touch sensitivity is a big improvement in speed and accuracy (this might be inherited from Butter Project)
+ HDMI mirror works fine.
+ Others (pls share your experiences...)
** Individually for each rom:
ICSROM:
+ Webtop 3.0: work like a charm!
+ New Camera/Camcoder by Motorola with various valued upgrades such as Auto continuous (live) focus mode even for camcoder, full HD capture...
+ FingerPrint scanner @first steps of working (worked but not yet supported by original ICS/JB).
+ New valued apps added, such as Smart Actions (similar to Tasker, Locale but more intuitive/friendly/efficient), MotoPrint (valued add not only for business man but even for home usage), Battery Tracer (for battery monitoring with rich info)...
"Sombody" CM10::
+ All great things from CM10 as you experienced with such as Epinter's rom...
+ Camera/camcoder: worked.
+ 2D hardware accelerator: worked.
+ Data/GPS/Wifi/Bluetooth...: worked fine.
* Bugs/issues and workarounds (Newest update info are sized in big text, this helps you guys to track info more quickly):
1. Camera flash doesn't work properly: (Fixing is in progress...)
- Temporary solution: Turn on the torch while capturing in dark (shouldn't keep the flash on continuously over 5 min for safety of the LED flash light)
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing): CM10 23-Oct build FIXED. But some users reported that the bug is still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
If this problem still persists on your Atrix, try one of solutions belows:
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (Edited: seems not worked): Turn off any screen unlocker (Choose None in Screen Unlock Options)
- Solution 3 (needs more confirmation): Just reboot your phone once or serveral times after rom installation
- Solution 4 (provided by Pont91-unconfirmed):
+put all media files on internal SD;
+deleted all files created by any app on the external SD;
+set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
- Solution 5 (worked with many users): Set Never for Screen Timeout in Settings/Display, remember to press Power button to turn off the screen instead
3. Randomly reboot issue: (the phone suddenly reboots for unknown reason):
- Solution 1: (need more confirmations): Remove the SD card.
- Solution 2 ("Somebody's" CM10) : (need more confirmations): Turn off Wifi :cyclops: There are two guys who provided that:
+ Either turning off Wifi
+ Or set Wifi to NEVER SLEEP (Always on) by: Settings/Wireless & Networks/Wifi Settings/Advanced/Wifi sleep policy
can help stopping reboots. Not only for this problem, but even the issues of heat and deep sleep can also be improved. From their reports, it seems that there is some problem related to the Wifi driver with "those libs". So, try this solution at your own case and help our devs by confirming this way again. Tks.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be cleared when the fix for deep sleep is applied.
5. The battery life: So bad
Both ICSROM (known as the leaked ICS) and CM10 with "those libs" have an identical problem of battery life. As shown on my phone, the battery drains from 100% downto 50% just after a couple of hours in usual use, even if your phone is in idle state.
No fix yet for this issue But you can apply some of following improvements:
- Lock (freeze) unnecessary AT&T apps and services (ICSROM only)
- Turn off Auto Syn (Manually mode instead)
- Turn off or lock all tracking/reporting sevices you doubt
- Use static wallpaper instead of live one
6. Ram low or several other suggestions only for ICSROM: clike here
7. The I/O performance is a characteristic weakness of both roms which are using "those" libs. You can see this on the results report of Quadrant. Essentially, you can see that the data processing speed is significantly slower than the CM7.2 by using, for e.g, Call Log Backup & Restore, etc...
No yet improvement for this disadvantage of both roms
8. Blackscreen issue after a lock/unlock: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
9. Black incoming call screen and blackscreen issue after a call: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
...Other issues (please share and provide your own solution...)
Thanks for continuous reports from you guys!
(To be updated...)

flusshd said:
Firstly, I would like to give a big thanks to "somebody" as well as the dev team at the behind these this rom for the efforts to bring ISC & JB as great things to our device.
Recent days I've tried both the leaked Rom and "somebody's" CM10 and saw that they have the same identical issues as reported such as the battery life, the deep sleep, the camera flash... and some working fixes. But the fixes are spread over the pages of threads that cause inconveniences for us to track or update. So I would like to open new thread for collecting the bug reports and the fixes from and for people to provide quick update info on these roms.
Admins please feel free to delete if this thread is already opend or is not neccessary.
Belows are lists of great things and also the bug reports along with the possible or even just temporary fixes that you may should try to resolve. The lists will be updated upon report from you guys. Please provide any thing from your ecperiences on these roms.
* Great things:
+ Camera/camcoder worked.
+ 2D hardware accelerator worked.
+ Data/GPS/Wifi/Bluetooth... worked.
+ FingerPrint scanner @first steps of working.
+ Touch sensitivity is excellent (this might be inherited from Butter Project)
+ Others (pls share your experiences...)
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing):
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (unconfirmed): Turn off any screen unlocker (Choose None in Screen Unlock Options)
3. Reboots issue: No solution yet.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be clear when the fix for deep sleep is applied.
5. Other issues (please share and provide your own solution...)
Thanks in advance for continuous reports from you guys!
Click to expand...
Click to collapse
Thanks For your report!
My phone is an US AT&T. Installed ICSROM yesterday (WOW!!!) and confirm what you posted.
Biggest bug is the battery. It seems to consume 1% every minute! In an hour I was down to 40% after full charge and using Play Store on wifi. Webtop/Mirror mode works awesome! Watched some HD videos and listened to some music... all good. After using the HDMI connection, I confirm that you will not get black screen until you reboot the phone. Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Keep up the great work and thank you for your efforts! :highfive:

flusshd said:
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
Click to expand...
Click to collapse
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.

gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
Thanks for the suggestion !

gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
It works
Anyway, it seems i've stopped deep sleep reboot, with external SD inserted, in this way:
-put all media files on internal SD;
-deleted all files created by any app on the external SD;
-set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
Hope this can help you in some way
Sent from my beloved Atrix

Android03 said:
Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Click to expand...
Click to collapse
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?

First of all, thanks for the report.
Regarding the FP reader - what's really working and what isn't? Could someone enlighten me there?

As I'm back to cm7 right now, I would like that if you find any bug/fix, PM me. I will put it on the OP in the dev section.
Oh, btw, the flash workaround was my idea

I heard removing the SD card fixes the reboots.
Sounds like this might be similar to what pont 91 talking about.

Is there any fix for the upside down front camera in "somebody's" cm10?
Sent from my MB860 using xda app-developers app

Not sure if this is a bug with the roms (Somebody's 10/19), but I'm not longer able to track total data usage on my phone. Some apps will show the amount used by individual apps, but none will actually total it up (They all say 0 total data usage).

Woah where you getting October 22 from???

Fixed
flusshd said:
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
Click to expand...
Click to collapse
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip

israelborges said:
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
Click to expand...
Click to collapse
So, no more random reboots?

quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
Where is that link coming from?
Sent from my iPad using Tapatalk HD

Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
from here
http://forum.xda-developers.com/showthread.php?t=1934662

quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
I'm trying it right now. I'll let you know

Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.

quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Have you tried it? Can't stand black screen after call!!!
Sent from my iPad using Tapatalk HD

quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Yes, but it's not the first time he did this

Touchscreen issues solved after 05Q update

I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?

Nothing's changed for me :c
Sent via Telnet

I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?

alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..

my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain

alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!

I m also facing same issue
Any solutions to resolve this issue?

Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.

For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable

kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk

I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.

anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su

I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch

Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!

I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app

Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su

A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/

Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..

Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.

I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?

Will custom ROMs ever be sorted for this phone?

I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?

I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.

ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.

I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.

Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...

Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...

ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.

Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.

Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.

Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.

piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.

Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.

Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.

piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.

Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )

Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital

Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.

rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.

supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!

Screen sensitivity & recalibration

I received a Z17 a few days ago and have really struggled with it. The phone feels really good but I am finding operation really difficult - the screen seems excessively sensitive. Most of the time when I touch or sweep the screen it register multiple touches - I hear multiple ticks. More often than not the app just tapped on opens then immediately closes (not force closing just going into background). Operating the phone is near impossible.
Is there a way to re-calibrate the screen sensitivity?
Short video showing the problem - https://www.youtube.com/watch?v=qpP6t2C3xeM
Bee

I don't have that issue. My screen issue is that it's too dark. I have to put it over 75% brightness or higher. I have a Bluboo Maya Max that also have an LCD screen from JDI that is pretty bright at 25% level.

Brightness seems OK here - although I might not be the best person as I typically run my screens at minimum/very low brightness unless I am out in the sun.
The sensitivity issue is driving me nuts though.
Bee

Updated to latest software version (2.44) but this has not improved the situation.
I have noticed that this is worst when I pick up and use the phone after it has been sat for a while. Things settle down if I continue to use the screen for an extended period of time - it seems like the screen is hugely sensitive and is picking up static on my hands.
Hopefully there will be a way to recalibrate the screen, maybe once root, unlocked bootloader and custom roms all become possible.

Still surprised no one else has reported this issue. Really hoping to find a way to re-calibrate the screen sensitivity.
Here is a video showing the problem. Basically it is nearly impossible to use the phone when you first pick it up, it does seem to improve after continue use.
http://vid61.photobucket.com/albums/h62/boboskinsbee/VID_20170709_124811_zpsmm58kw6r.mp4
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Bee

i will receive my Z17 on Tuesday... then, for my part, i will answer again.
actually i have an off topic question: u can use google chrome?
if yes, how?
any other google apps?

loquenz said:
i will receive my Z17 on Tuesday... then, for my part, i will answer again.
actually i have an off topic question: u can use google chrome?
if yes, how?
any other google apps?
Click to expand...
Click to collapse
Yes - chrome works. You will need to get from apkmirror or similar.
Like others I tried installing google framework & play but this didn't work. Google music would run but unless you have local files you can't do anything with it.
I REALLY want to like this phone but so far it just isn't usable as a daily driver.
Bee

boboskins said:
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Click to expand...
Click to collapse
boboskins said:
Updated to latest software version (2.44) but this has not improved the situation.
I have noticed that this is worst when I pick up and use the phone after it has been sat for a while. Things settle down if I continue to use the screen for an extended period of time - it seems like the screen is hugely sensitive and is picking up static on my hands.
Click to expand...
Click to collapse
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
boboskins said:
Hopefully there will be a way to recalibrate the screen, maybe once root, unlocked bootloader and custom roms all become possible.
Click to expand...
Click to collapse
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental

Not just me!
Sort of pleased someone else has the same problem! Agree that it isn't fixed in RR. Hopefully there will eventually be a solution.
I tend to deal with it by holding the phone between my two palms (i.e. holding my palm fully across the screen) for a second or so when I pick the phone up after it has been sat for a while. This seems to reduce the sensitivity (or remove static build up?) and things work normally.
Of course this shouldn't be necessary and not something you want to do when trying to answer a call.
B
qwertius2 said:
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental
Click to expand...
Click to collapse

I have the same problem
qwertius2 said:
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental
Click to expand...
Click to collapse
Friend did you solve the problem with the resurrection remix? . I have seen a new update that says something about a bug I hope is the solution.
Daken.

boboskins said:
Still surprised no one else has reported this issue. Really hoping to find a way to re-calibrate the screen sensitivity.
Here is a video showing the problem. Basically it is nearly impossible to use the phone when you first pick it up, it does seem to improve after continue use.
http://vid61.photobucket.com/albums/h62/boboskinsbee/VID_20170709_124811_zpsmm58kw6r.mp4
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Bee
Click to expand...
Click to collapse
Hello Boboskins
Can't access to your video

Sadly still not found a solution. I have tried RR (up until about 10 days ago) and now using Mokee. Appreciate your comments on the recent updates - I will take a look at the log in case the latest RR updates solve anything.
EDIT: Ursus91, just took a look and Photobucket appears to have stopped allowing 3rd party views. I will upload somewhere else and update the link once I am done.

@boboskins : thanks, it should be helpful to understand the problem you encounter. I'm not sure to understand. And I'm still waiting to use the phone every day

I have the same problem

Same problème here ! When i use the phone it seems it close app or back like i hit the button. :/ Really annoying :s

Hello,
I have the same problem too. The sole solution from GeekB is to return the phone for repairing...
I have it sometimes on the left button (in the major cases), the middle button has actually no problems, the right, sometimes.
I use the middle button to come back to "the main view" (icons) and then, the left button seems going alive.
I'm not sure it is a hardware problem

Edge gestures issue
Greetings!
I've just started using Nubia Z17 Lite and found out that the specific edge gesture to control the brightness level doesn't work on my unit. Does anyone know if this is a bug that can be resolved by an update or did anyone have the same issue and has fixed it?
I'm quite sure the problem isn't with the hardware because other edge gestures seem to work fine.
Thanks ?

Nubia Z17 black screen
Good evening. I own a Nubia Z17 8gb ram 128gb rom and today had a problem. His screen is black and the LED on the menu button is on. It obeys no command. He did not fall, everything perfect. Could someone help me with this problem?