P30 pro .162 update - Huawei P30 Pro Guides, News, & Discussion

Just received the .162 update. Chinese phone in the US
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you do any testing on the camera after the update? If so, did you notice any improvements in this regard?

I am interest on this also.
Maher.k22 said:
Did you do any testing on the camera after the update? If so, did you notice any improvements in this regard?
Click to expand...
Click to collapse

Are they fix orange color(some shade) issue for RYYB lens?

Nice! Of course it'll take a month or something like that before 95% of us gets the update, but at least it's something to look forward to.

Aznbadboixx said:
Just received the .162 update. Chinese phone in the US
Click to expand...
Click to collapse
Lol, he said "chinese phone in the us" ....

I hope it really fixed that front camera video issue.

Maher.k22 said:
Did you do any testing on the camera after the update? If so, did you notice any improvements in this regard?
Click to expand...
Click to collapse
I was getting ready for bed so didn't think to take a before and after pictures

So it does live wallpapers on the lockscreen now? Nice but would've been better they reworked the camera app.

Can you post a video from the front facing camera to see how much is it fixed?

162 test from man who use China model in Thailand FB group
Orange-Red still problem. Mate30 should throw RYYB sensor away. lul

hi, i am also on 162 but i don't have any problems

salemsayed said:
I hope it really fixed that front camera video issue.
Click to expand...
Click to collapse
Yeah, that is ridiculous, when you fast move the phone while filming with front camera its like a cartoon..

https://forum.xda-developers.com/showpost.php?p=79544797&postcount=679

Anybody out of China started receiving that update?

Found this chinese thread with a photo of before and after 162
https://club.huawei.com/thread-20357527-1-7.html

I got the update like 2 nights ago. Chinese Version also VOG AL00

I guess the .162 would be the last one now that Google has also restricted them access to further security patches and updates. Next ota might the phone being upgraded to huawei's own OS

JJay666 said:
I guess the .162 would be the last one now that Google has also restricted them access to further security patches and updates. Next ota might the phone being upgraded to huawei's own OS
Click to expand...
Click to collapse
There's a Google statement about that. They said that phone certification will not be lost in the phone already in the market and they are trying to find a solution to support all the phone already sold.
We will see in the next days.

drcldrcl said:
Yeah, that is ridiculous, when you fast move the phone while filming with front camera its like a cartoon..
Click to expand...
Click to collapse
The selfie cam? Just tried it on .153 and looks fine here! Smooth panning etc.

Related

Camera switch problem

Hi
I have a Galaxy S3 white 16gb.
One of the first first things a did when first turning on my new phone was to try the camera. I switched from the back to the front camera and then back again and now the camera app wont even open. After about 20 seconds after opening the camera app I get ' Unfortunately, Camera has stopped.'.
I thought if I turned the phone off and on again this may fix the problem but no. I then removed the battery for a few seconds but this again, this did not fix the problem.
The only way I could get the camera to work again was to do a factor reset. I just have to open up the camera app and switch from back to front and back again and the same problem occurs.
Is it only me?
Thanks
Me too
Hi,
No it's not just you I have this issue too! Not a happy bunny
I'm thinking it maybe a software release error. My device settings are
Android 4.0.4
kernek 3.0.15-611327
Cas
Cas8968 said:
Hi,
No it's not just you I have this issue too! Not a happy bunny
I'm thinking it maybe a software release error. My device settings are
Android 4.0.4
kernek 3.0.15-611327
Cas
Click to expand...
Click to collapse
I'm glad its not just me, seems like a software bug.
Are you going to keep yours?
theboss4 said:
I'm glad its not just me, seems like a software bug.
Are you going to keep yours?
Click to expand...
Click to collapse
Which firmware version are you using?
ronj1986 said:
Which firmware version are you using?
Click to expand...
Click to collapse
Kernel version
3.0.15-554505-user
Is that what you mean?
I got it from Vodafone UK.
Sending Back
Hi,
No I'm not keeping mine. I also contacted samsung and they have said to return it to the supplier.
As for the firmware I connected mine to Kies and Kies informed me that my phone was not compatabile for a firmware upgrade via Kies. I can only guess that there is no firmware upgrade available.
Cas
I have been chatting in the Vodafone UK eforum.
I have spoken to Vodafone and they said it is not a known issue so seems like a hardware problem with my device. They are arranging for a new one to be sent to me Thursday so I can swap.
Other than that is seems like a great device.
theboss4 said:
I'm glad its not just me, seems like a software bug.
Are you going to keep yours?
Click to expand...
Click to collapse
I just tried what you said - took a pic with the front camera, switched to the back and took another, then closed and restarted the camera - and it worked fine for me.
Although I did spot that you're on a later revision than I am (my phone's SIM-free)
{
"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"
}
Yes I know that "well it works for me" isn't that helpful. That said, maybe you can use this as "evidence" that you've got a busted phone? HTH

[Q] Why does my Xperia Z2 Tablet not get Lollipop?

Weeks ago I was on their website and saw, that it is already available for a long time. Buddy who has a Z3 Tablet mentioned last month he got his update, but my Tablet and the PC Companion software tell me everytime that my Tablet is up to date!
Last time I thought I had a great idea, I went for the kinda repair-y option you can choose in PC Companion, where the software downloads the current Android system, wipes your device and installs the newest Android. Of course I backed up my apps before that with PC Companion.
What was the result?!
I still got Build 230.1.A4.30
And thanks to that experiment I had a lot of things to reconfigure, that I configured perfectly to my needs over the months. If my Tablet was rooted, I would have just used TitaniumBackup or the likes and not trusted the PC Companion...
What gives?!? Do I now only have the option to finally root my Tablet and use only custom roms? And that after not even a year of owning it?!
Have a look at my screenshot, please:
{
"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"
}
As discussed on Android-Hilfe, LP is still in the distribution. You will just have to wait,or follow the instructions to update manually.
According to XperiFirm, for SGP512 model (32GB/WIFI), Lollipop is deployed about everywhere in the world except Japan and one group of European countries (FR/DE/... etc.) which are excluded for unknown reasons (does anybody knows why???)
Personally, I installed manually the UK firmware for now using FlashTool (but I'm waiting Japanese update...).
yep i also have the same problem...i purchased the tablet from germany and i am still stucka at 4.4... i hope i get lollipop soon. I also have a display problem...i noticed a little dots when i use black backgrounds...anyone seen this yet?
Got this problem too..it sucks. @masasume would there be a tutorial available for install manually??
me too, i did a downgrade, make it root, and flash a version from outside GER like UK, now my tab has lollipop
tommaazz said:
yep i also have the same problem...i purchased the tablet from germany and i am still stucka at 4.4... i hope i get lollipop soon. I also have a display problem...i noticed a little dots when i use black backgrounds...anyone seen this yet?
Click to expand...
Click to collapse
Updates are usually released according to regional areas.
You need to wait until Sony uploads the latest firmware and make available for you in your region.
There can be difference of a month or two between other phones update and yours.
The spots on your screen can be dead pixels OR it can be dust particles. Using AnTuTu benchmark take a screen test and check for dead pixels. Play store link is below;
https://play.google.com/store/apps/details?id=com.antutu.ABenchMark&hl=en
Regards,
hitman-xda
hitman-xda said:
Using AnTuTu benchmark take a screen test and check for dead pixels. Play store link is below;
https://play.google.com/store/apps/details?id=com.antutu.ABenchMark&hl=en
Regards,
hitman-xda
Click to expand...
Click to collapse
Faulty pixels never show in screenshots, for obvious reasons.
I think they are stuck pixels. I have a bicycle GPS and after a drop, a few pixels on the screen always stayed the same color. Funny enough when I gave the GPS a good "spanking", the pixels went back to normal.
degraaff said:
Faulty pixels never show in screenshots, for obvious reasons.
I think they are stuck pixels. I have a bicycle GPS and after a drop, a few pixels on the screen always stayed the same color. Funny enough when I gave the GPS a good "spanking", the pixels went back to normal.
Click to expand...
Click to collapse
That picture isn't screenshot.
hitman-xda said:
That picture isn't screenshot.
Click to expand...
Click to collapse
Oh never mind, seems I somehow read "screen test" as "screen shot"

Lollipop is looking likely!

After some rigorous googling last night, I stumbled on a Vietnamese website and found some screenshots someone had posted teasing Lollipop ...
{
"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 don't know about you guys, but that looks like the legitimate, real deal to me. Oddly enough, I went to the site that the photos are watermarked with and couldn't find a trace of these photos, mention of lollipop, anything... Even though they were posted on that Vietnamese forum I stumbled on just a few days ago.
Notice the new baseband... I wonder if it has included VOLTE!
This is really nice, but why Vietnam? I thought VZW only sales Z3V here in the US… maybe there're some Vietnamese developers working on this phone just for us, and that will be sooo nice!
Fingers crossed
Kfc. said:
This is really nice, but why Vietnam? I thought VZW only sales Z3V here in the US… maybe there're some Vietnamese developers working on this phone just for us, and that will be sooo nice!
Fingers crossed
Click to expand...
Click to collapse
Well actually it says ROM in the link I'll show you... But having a new baseband and kernel version? No way anyone developed that but Sony.. Especially on these locked bootloaders...I'm guessing they mean ROM as in FTF... I wish there was a download link and not just screens... It's so mean to just tease it lol. Link
He said he replied to your PM. What did he say?
brandodoubleg said:
He said he replied to your PM. What did he say?
Click to expand...
Click to collapse
He sent me an ftf of the .44 firmware and this is what I said back im waiting for him to reply.
zachariahpope said:
He sent me an ftf of the .44 firmware and this is what I said back im waiting for him to reply.
View attachment 3481633
View attachment 3481634
Click to expand...
Click to collapse
Looks like from the information he gave you, the build number will look something like 23.1.D.0.485. I've done mad searching around for any of the unique numbers or information he gave in screenshots and I could find absolutely NOTHING, so definitely not on the internet somewhere. Fact that he's connected to and HSPA network in Vietnam is curious, too. Didn't know the Z3v had that type of capability.
Yes, I have tried z3v with H+ connection in Taiwan last time I stopped for business
brandodoubleg said:
Looks like from the information he gave you, the build number will look something like 23.1.D.0.485. I've done mad searching around for any of the unique numbers or information he gave in screenshots and I could find absolutely NOTHING, so definitely not on the internet somewhere. Fact that he's connected to and HSPA network in Vietnam is curious, too. Didn't know the Z3v had that type of capability.
Click to expand...
Click to collapse
Verizon phones nowadays can go global. I went to Thailand and had HSPA+ connected.
23.1.D.0.485 fw its for prototype phones
mohkam84 said:
23.1.D.0.485 fw its for prototype phones
Click to expand...
Click to collapse
Sony has a 23.1.A.1.28 firmware for the first few releases of Lollipop 5.0.2.
Here is a tft of lollipop but for the Z3, Z3 com, http://www.gizmobolt.com/tag/23-1-a-1-28-firmware/ , looks like "A" is final release.

About Poco F1 Closed Beta 8.11.23

Some people on XDA are saying that touch issues are fixed in 8.11.23 closed beta.
I am sorry for writing this, but people are really going out and saying stupid stuff like these and whoever tried flashing the update in question got numerous bugs, first of all the touch issue is still not solved on any closed beta, secondly the update in question was pulled back due to major bugs.
Please don't believe the liars it will probably lead to more damage,
Source:
https://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=4687147&pid=32796920
{
"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"
}
What's the major bug are you talking about? ?
I'm on 8.11.23 and no bug at all
They suspend betas for Poco all the time but I never had any major bugs on them... As for touch, yes, it was fixed for the most part. The lag on the edges is 80% gone. The thing is that they screwed up the top and bottom of the display at the same time and latency in these areas is horrible. But typing and scrolling finally feels normal again. It's not a lie; .23 was the first update to bring a new optimised kernel which fixes touch. Did you even try the update? People have been lying in the past about the fix but this time it's for real. They need to work on it a bit more though because it's far from perfect.
mario123m said:
They suspend betas for Poco all the time but I never had any major bugs on them... As for touch, yes, it was fixed for the most part. The lag on the edges is 80% gone. The thing is that they screwed up the top and bottom of the display at the same time and latency in these areas is horrible. But typing and scrolling finally feels normal again. It's not a lie; .23 was the first update to bring a new optimised kernel which fixes touch. Did you even try the update? People have been lying in the past about the fix but this time it's for real. They need to work on it a bit more though because it's far from perfect.
Click to expand...
Click to collapse
Oh Snap! That was painful to watch. ?
And to answer the question, no the OP doesn't even have POCO F1 as he sold it like 2 months ago. But always comes back to check on POCO forums from time to time. Sad.
Touch on bottom and top of the screen is horrendous to say the least. So they fix touch for PUBG and screw up 90% of non-gamers?
I am on closed beta for Poco F1, and each build after .15 has been a pain. They pushed .27 earlier today and it is still the same.
I don't think .29 will bring in changes either.
sayHello21 said:
Oh Snap! That was painful to watch.
And to answer the question, no the OP doesn't even have POCO F1 as he sold it like 2 months ago. But always comes back to check on POCO forums from time to time. Sad.
Click to expand...
Click to collapse
Yea, I just come back to see how much Xiaomi fulfilled. If they fulfill their promises, they win my trust again and I will buy and suggest their phones. Right now, I only like their Android One series and despise all Redmi and Mi (non AOne) series phones.

Galaxy S9+ February Front-Facing Camera Bug

Guys, have you heard about SGS9+ Selfie Camera bug, that formed after the February firmware update?
I'm talking about auto-focus of the front camera at the very close range. The phone simply does not want to focus on the object when it is too close to the camera. Its a bug (and not only on my side, i've asked plenty of peoples that confirmed the bug), because phone could do it before the February update. Here is some of mine photo examples of the front camera shots, fuzzy image - Galaxy S9+, sharp image - Galaxy S8.
{
"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"
}
Same thing here
Dieexe said:
Same thing here
Click to expand...
Click to collapse
As far as i know, March update (that currently LIVE on German Galaxy S9) - WON'T fix this issue. The same fuzzy images at the close range still.
We have to somehow let Samsung Support know about this issue.
Just call Samsung support and report your findings
Sent from my SM-G965U using Tapatalk
tdevaughn said:
Just call Samsung support and report your findings
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
Already, but all they said to me - do wipe cache \ hard reset and go to the Service Store for warranty issue, our Support does not want to admit the problem, they said they don't have this issue. But its not true.
I think we have to somehow together report to Samsung Support so they really pay attention to this issue.
It actually happens at no matter which distance. Even when I move my face further away and try manually focusing on it, it ends up blurry. But auto focus works even when on close distance. This is a bug for sure, since the camera actually CAN focus the object on auto focus.
I wrote to samsung on samsung members app for a different bug regarding the navigation gestures, and first they said the same just to make a factory reset. After that I told them that I am a long - term samsung user and I know how to use my phone, explained that I already did a factory reset, explained the issue again and also attached a screen recording of the problem, and after that they said that they will make sure it reaches the development department.
So - just tell them that you already did everything that you as a user can do, and send proof that it actually is a bug.
I'll write to them.
Lets unite, people!
Seems like fixed now, right? April security patch
Do you use google camera apk for your S9?
I still have this problem. Hard reset and other things didn't work

Categories

Resources