Based on the updates shown at Sprint (Phone Carrier in the USA), the Android 5.0.1 update (15 December 2014) should be released today for the Nexus 5
Let us hope it will solve many of our issues since the Lollipop update.
Source : http://support.sprint.com/support/a...AndUpdateTheSoftwareVersionOnYourGoogleNexus5
Let's hope that's true!
They gave a clear shot at the date of 5.0. I hope they are right again.
F5 F5 F5 F5
https://developers.google.com/android/nexus/images
markp99 said:
F5 F5 F5 F5
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
This time I'll wait for the OTA. Configure everything again is something boring.
ReeSilva said:
This time I'll wait for the OTA. Configure everything again is something boring.
Click to expand...
Click to collapse
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
BRiANj64 said:
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
Click to expand...
Click to collapse
I've heard about, but always exists a fear that it don't works |smile|
BRiANj64 said:
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
Click to expand...
Click to collapse
FYI.. removed that -w when flashing my nexus 7.. did nothing, it wiped everything anyway
orthonovum said:
FYI.. removed that -w when flashing my nexus 7.. did nothing, it wiped everything anyway
Click to expand...
Click to collapse
This is what Im talking about.
Don't just remove -w
Open up the .zip and remove userdata.img from it.
Of course this only works if you leave your bootloader unlocked. I leave mine locked for security. Don't want someone getting my data if I lose my phone, force them to wipe to unlock it.
Flashing userdata wipes your sdcard ya noobs
ReeSilva said:
This time I'll wait for the OTA. Configure everything again is something boring.
Click to expand...
Click to collapse
Same here since it only took 2 days to get it on my nexus 7.
Pezmet said:
Same here since it only took 2 days to get it on my nexus 7.
Click to expand...
Click to collapse
Nexus 5 5.0.1 image not posted yet on the Google firmware page. Last years Moto G does have 5.0.1 though
Same here I'll wait for the OTA this time around rather flash the image, basically because i can't be bothered flashing
gee2012 said:
Nexus 5 5.0.1 image not posted yet on the Google firmware page. Last years Moto G does have 5.0.1 though
Click to expand...
Click to collapse
Yes the reasons of the delay are weird since it is the same build name, hence no later fixes should be there so the wait was kind of useless.
ixon2001 said:
Same here I'll wait for the OTA this time around rather flash the image, basically because i can't be bothered flashing
Click to expand...
Click to collapse
5.0.1 OTA for the Nexus 10 was only 8,4MB, so don`t expect too much.
I'll wait for the ota. I can't be bothered to flash again.
Pls pls just update the radio to powerhog on 4G
It takes less than a minute to Fastboot flash system, boot and radio(in case we get a new one). Not sure why all the drama.
Related
My Nexus 6 was bought here in Denmark and its a 64 version. However i would really like to update it before i go travelling, as i just want the improvements with the 5.1 updates.
I have tried the "check for updates" button for like 1000 times as i dont want to clean install it, and just want to upgrade it with my apps etc.
Am i still the only one waiting for 5.1?
Oniska said:
My Nexus 6 was bought here in Denmark and its a 64 version. However i would really like to update it before i go travelling, as i just want the improvements with the 5.1 updates.
I have tried the "check for updates" button for like 1000 times as i dont want to clean install it, and just want to upgrade it with my apps etc.
Am i still the only one waiting for 5.1?
Click to expand...
Click to collapse
First, mashing your check for updates button doesn't help your cause. Look here:
http://www.droid-life.com/2013/11/21/android-engineer-explains-why-mashing-check-for-updates-on-nexus-devices-isnt-helping-you/
Evolution_Freak said:
First, mashing your check for updates button doesn't help your cause. Look here:
http://www.droid-life.com/2013/11/2...or-updates-on-nexus-devices-isnt-helping-you/
Click to expand...
Click to collapse
Thanks for the article. However the image is available but not the OTA... Not logical
Oniska said:
Thanks for the article. However the image is available but not the OTA... Not logical
Click to expand...
Click to collapse
Are you still on 5.0.1? You can sideload update to 5.1 LMY47D.
Evolution_Freak said:
Are you still on 5.0.1? You can sideload update to 5.1 LMY47D.
Click to expand...
Click to collapse
Without Clean wipe? Really?
Oniska said:
Without Clean wipe? Really?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2906493
Evolution_Freak said:
Are you still on 5.0.1? You can sideload update to 5.1 LMY47D.
Click to expand...
Click to collapse
Evolution_Freak said:
http://forum.xda-developers.com/showthread.php?t=2906493
Click to expand...
Click to collapse
I think ill just wait for the official OTA, as i dont want to *uck up my radio again like i had before. However it would be great if there was like a "PC Suite" software from Google
Oniska said:
I think ill just wait for the official OTA, as i dont want to *uck up my radio again like i had before. However it would be great if there was like a "PC Suite" software from Google
Click to expand...
Click to collapse
Sideloading is really easy though. Just a few simple ADB commands and you're done. Your choice though, I understand. I don't use toolkits but if you wanted to go that route, you could look into it. They make an already simple process even simpler. If you do use toolkits though, it is wise to still have a basic understanding of fastboot and ADB if you get stuck. *end PSA* Good luck with your choice and your traveling.
Oniska said:
Without Clean wipe? Really?
Click to expand...
Click to collapse
You can also open the factory image and fastboot flash each image separately. Just skip the userdata.img. Will leave data partition alone.
Evolution_Freak said:
Sideloading is really easy though. Just a few simple ADB commands and you're done. Your choice though, I understand. I don't use toolkits but if you wanted to go that route, you could look into it. They make an already simple process even simpler. If you do use toolkits though, it is wise to still have a basic understanding of fastboot and ADB if you get stuck. *end PSA* Good luck with your choice and your traveling.
Click to expand...
Click to collapse
Do i need root to do the sideload?
Oniska said:
Do i need root to do the sideload?
Click to expand...
Click to collapse
No.
All,
I just got prompted by AT&T to install the 5.1 update and while I want it right now my phone is working near perfectly and I use a number of root needed applications. Before I do the upgrade I want to know if this will cause me to lose root and if so how easy it is to get it back? Right now I'd definitely pick root over 5.1
Searched but couldn't find an answer so sorry if I missed a thread on it already...
-Ross
rosscarlson said:
All,
I just got prompted by AT&T to install the 5.1 update and while I want it right now my phone is working near perfectly and I use a number of root needed applications. Before I do the upgrade I want to know if this will cause me to lose root and if so how easy it is to get it back? Right now I'd definitely pick root over 5.1
Searched but couldn't find an answer so sorry if I missed a thread on it already...
-Ross
Click to expand...
Click to collapse
you have root, you wont be able to update via ota. any kind of system file changes prevents you upating via ota.
simms22 said:
you have root, you wont be able to update via ota. any kind of system file changes prevents you upating via ota.
Click to expand...
Click to collapse
Ah, ok - so even if I'm being prompted you're saying that it will fail? I'm not running a custom ROM or anything just rooted. Just clarifying as it is prompting me to update.
So to update would I then need to go through the process manually? I'm sure there's a thread somewhere so I can find that, just making sure I understand...
-Ross
rosscarlson said:
Ah, ok - so even if I'm being prompted you're saying that it will fail? I'm not running a custom ROM or anything just rooted. Just clarifying as it is prompting me to update.
So to update would I then need to go through the process manually? I'm sure there's a thread somewhere so I can find that, just making sure I understand...
-Ross
Click to expand...
Click to collapse
yup, itll fail. and yes, manually. theres ways of doing it without losing data as well. yes, theres a thread for that
simms22 said:
yup, itll fail. and yes, manually. theres ways of doing it without losing data as well. yes, theres a thread for that
Click to expand...
Click to collapse
I can't find that thread
PunishedSnake said:
I can't find that thread
Click to expand...
Click to collapse
Loads of threads. Search "update losing data" or something.
But in short, just fastboot flash system.img and boot.img and not userdata.img
rootSU said:
Loads of threads. Search "update losing data" or something.
But in short, just fastboot flash system.img and boot.img and not userdata.img
Click to expand...
Click to collapse
Thats what I figured
And I went from D build to E back down to 5.0.1 then ota to M lol
I hope the release the wifi calling update as a system image
PunishedSnake said:
Thats what I figured
And I went from D build to E back down to 5.0.1 then ota to M lol
I hope the release the wifi calling update as a system image
Click to expand...
Click to collapse
If its m that's already out, I don't see a factory image coming
Got this OTA after doing an ODIN of EPF1 to my phone. Baseband is updated to match, unsure about bootloader but I doubt it. If someone wants a ROM dump and is willing to tell me how....
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
elroy253 said:
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
Click to expand...
Click to collapse
I didn't. I haven't tried downgrading but I flashed recovery after it updated. The one thing I have noticed is that wanam xposed/firefds kit has some functions that don't work or change anything...
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
EncryptedCurse said:
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
Click to expand...
Click to collapse
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Maqical said:
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Click to expand...
Click to collapse
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
I guess until further notice using Smart Switch as a lazy way to recover from my own stupidity is out
EncryptedCurse said:
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...l/how-to-flash-marshmallow-update-sm-t3362983
This guide will help you with all of it, just change the "the rom" part to whatever 6.0 rom you decide you want to use instead.
I'm downloading the complete TAR image from Sammobile, but due to finances I don't have the means to pay for the full speed..
So I'm downloading at the slow method.. If someone else has not uploaded the image, I will upload it by late tonite..
I'm still having issues with the damn Upload it gives me last second errors when I step away to do another task..
I'm making my final attempt to upload it onto my Android File Host... It should be up by morning if it uploads correctly.. Just Look For Zaphodspeaks in Android File Host if I haven't posted it yet..
I have many tasks to do this week ends.. Mainly upkeep the the old house and updating some of the old wiring while its getting cooler..
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Got my phone rooted, custom rom, and kernel that I was using before, no problem.
Last night (9/27) I got a firmware update for my factory USA unlocked 920T. Sammobile shows it was released on 9/26. It was a 50MB file that updated the Android secruity patch date to Sept. 1. No other changes. I noticed the Samsung Smart Manager app/widget shows I'm using 5% less memory now. I don't know if it's better RAM management or Samsung modified the app/widget to show different figures LOL. I suspect the t-mobile 920T will get the update soon.
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
Thanks!!
RFrancis said:
Thanks!!
Click to expand...
Click to collapse
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
JustZaphod said:
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
Click to expand...
Click to collapse
Only a month? Record time there...
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
thanks
Hortisimo said:
thanks
Click to expand...
Click to collapse
Thank me by hitting the Thanks Thumbs up!
JustZaphod said:
Thank me by hitting the Thanks Thumbs up!
Click to expand...
Click to collapse
already did
Was wondering if a kind person could deodex this new update? for some reason i cannot install ubuntu on my pc to get it done right.Thanks
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
Just manually updated to build QD1A.190821.014 Face Unlock was working fine before uodating now it won't let me Unlock for the life of me. I can still register my face just can't do the actual unlocking with it. It says Can't verify face Everytime.
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Falargi said:
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Click to expand...
Click to collapse
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
RLKirk said:
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
Click to expand...
Click to collapse
That's exactly what I did too. Let me know how it goes. I'll probably do the same.
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
This happened to me. The .007.A3 flash fixed it.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Falargi said:
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Click to expand...
Click to collapse
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
RLKirk said:
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
Click to expand...
Click to collapse
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
murphyjasonc said:
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
Click to expand...
Click to collapse
Cool thanks dude
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Falargi said:
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Click to expand...
Click to collapse
Glad I could help. :good:
I sent my Pixel 4 XL back in for a warranty replacement because of this issue. I wasn't sure if it was hardware related or not. Didn't want to take a chance on it being a hardware defect. I was on the November security update. I updated it as soon as I set up my phone so I didn't have a chance test it out on the October update.
murphyjasonc said:
Glad I could help. :good:
Click to expand...
Click to collapse
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
https://support.google.com/pixelphone/thread/21769134?hl=en/
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
murphyjasonc said:
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
Click to expand...
Click to collapse
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Falargi said:
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Click to expand...
Click to collapse
I think your best bet is to flash the 011 image. I would try flashing it first with the -W removed. You might get lucky and save yourself some time. If that doesn't work then flash November again and go from there.
Is this issue related to root? I had a fresh install with the latest December patches (qq1b.191205.011) that did not work with Face Unlock. However, that attempt was also rooted in the typical fashion with Magisk. After performing a full re-install of qq1b, I was able to use Fack Unlock normally. I'll re-apply root later today and let you know if that was the tipping point.