[jcrutchvt2010]

Jcrutch: I flashed my modem bin via adb in the other thread (dual sim, was trying to get ims). I flashed it back...
Tho im not seeing the ota upgrade that seems to be out for my variant when I check via the upgrade app.
Could this flashing have messed up my ota upgrades?
Or do they just not roll out to everyone with the same variant sometimes?

Thanks!

Wouldn't think that would cause that but you can flash back the original modem if you like. I'm guessing you flashed NON-HLOS-usa.bin? If so, the original modem can be found here: https://www.androidfilehost.com/?fid=889964283620757998 If you flashed back to original, that wouldn't be the issue. You could try clearing the data from the updates app.

[jcrutchvt2010]

Universal Loader for AAP683 here. Should work for all but Sprint, ATT, China. Keep in mind this will wipe your data executed as is. Please let me know if you have issues with the loader script.

Sorry for confusion I uploaded 638 again.... The right 683 is uploading now should be done in 30 or so and will be titled 683UNIVERSALFINAL at my root folder here https://www.androidfilehost.com/?w=files&flid=204896

[mhw100]

Universal Loader for AAP638 here. Should work for all but Sprint, ATT, China. Keep in mind this will wipe your data executed as is. Please let me know if you have issues with the loader script.

https://www.androidfilehost.com/?fid=817906626617938787

Is this 638 or 683. I thought the first one was 638 and you were building 683 today?

[jcrutchvt2010]

Is this 638 or 683. I thought the first one was 638 and you were building 683 today?

Yep it's 683 sorry. Tired.

[thurask]

Wouldn't think that would cause that but you can flash back the original modem if you like. I'm guessing you flashed NON-HLOS-usa.bin? If so, the original modem can be found here: https://www.androidfilehost.com/?fid=889964283620757998 If you flashed back to original, that wouldn't be the issue. You could try clearing the data from the updates app.

Jcrutch: I flashed my modem bin via adb in the other thread (dual sim, was trying to get ims). I flashed it back...
Tho im not seeing the ota upgrade that seems to be out for my variant when I check via the upgrade app.
Could this flashing have messed up my ota upgrades?
Or do they just not roll out to everyone with the same variant sometimes?

Thanks!

Dual SIM KEYone (BBB100-7) is NON-HLOS-india.

[jcrutchvt2010]

Dual SIM KEYone (BBB100-7) is NON-HLOS-india.

Yeah link I posted should be to that one. Unless i mistyped again which is entirely possible. He flashed usa to test i believe and then back to the india version.

[mhw100]

Yep it's 683 sorry. Tired.

Thanks for all of your hard work.

[mhw100]

Universal Loader for AAP683 here. Should work for all but Sprint, ATT, China. Keep in mind this will wipe your data executed as is. Please let me know if you have issues with the loader script.

https://www.androidfilehost.com/?fid=817906626617938787

The download upload date is Oct 14 for file 638 and appears to be identical to the original file.

[jcrutchvt2010]

The download upload date is Oct 14 for file 638 and appears to be identical to the original file.

Universal Loader for AAP683 here. Should work for all but Sprint, ATT, China. Keep in mind this will wipe your data executed as is. Please let me know if you have issues with the loader script.

Sorry for confusion I uploaded 638 again.... The right 683 is uploading now should be done in 30 or so and will be titled 683UNIVERSALFINAL at my root folder here https://www.androidfilehost.com/?w=files&flid=204896

[jcrutchvt2010]

I'm downloading myself to make sure I only mistitled and didn't just attach the wrong zip. 99 percent sure I fixed the links to the ACTUAL 683 link. sorry for anyone who tried to DL using the old 638 link.

[gjh1978]

I'm downloading myself to make sure I only mistitled and didn't just attach the wrong zip. 99 percent sure I fixed the links to the ACTUAL 683 link. sorry for anyone who tried to DL using the old 638 link.

Did you happen to notice or hear of any differences between 638 and 683 other than model/region.

I have a unlocked 100-1 model and loaded 638, should I go back and flash 683 over it?

[jcrutchvt2010]

Did you happen to notice or hear of any differences between 638 and 683 other than model/region.

I have a unlocked 100-1 model and loaded 638, should I go back and flash 683 over it?

I'm using 683 for about 3 hours now and so far nothing different that I can tell. I'll let you know if I find anything.

[gjh1978]

I'm using 683 for about 3 hours now and so far nothing different that I can tell. I'll let you know if I find anything.

Thank you!

[jcrutchvt2010]

The download upload date is Oct 14 for file 638 and appears to be identical to the original file.

If you are downloading the new one and it appears the same, let me know and I'll re-upload the correct zip. Darn the numbers being so close. I'm uploading a new one now because I want to go to bed. It will just be called 683. It will be in the root folder of my KeyOne autoloaders folder within an hour.

[Al moon]

Thank you!

Did you wipe app data on o the update's app once i did it showed me 683 was available.

[jcrutchvt2010]

OK folks bungled the upload. new one is in progress and should be done within an hour. it will be in the root of my KeyOne autoloaders folder called "683UNIVERSALFINAL". root folder here:
https://www.androidfilehost.com/?w=files&flid=204896

[slagman5]

So if I understand your question, completely remove all icons from every "screen" and you should see no dots above the drawer launcher button? If so, I still see one dot above the drawer button even with nothing on any screen. I would expect that to be normal behavior though since a home "page" still exists. If I misunderstood the ask, let me know.

Negative, that is not normal behavior. It didn't do that until the August update. Why would you need a page dot if there are no pages? Also, long press on the home screen until the launcher settings show and press home. Or add an icon and remove it, you'll notice it has the animation for the dot to fade away. But it comes back when you do other things. But if the dot should always be there, there wouldn't be a fade animation at all...

[gjh1978]

Did you wipe app data on o the update's app once i did it showed me 683 was available.

Where would I do that in the update app?

[Al moon]

Where would I do that in the update app?

settings>app>scroll down to updates app>click on storage>clear data. Launch the app and check for update.

[gjh1978]

settings>app>scroll down to updates app>click on storage>clear data

Already did that. Don't think you understand. I flashed AAP638 which is October update for certain models, and I was curious if AAP683 is any different. If so, I would just wipe again and manually flash using autoloader.

[mhw100]

683 loaded great. Thank you jcrutchvt2010.

[fop518]

Wouldn't think that would cause that but you can flash back the original modem if you like. I'm guessing you flashed NON-HLOS-usa.bin? If so, the original modem can be found here: https://www.androidfilehost.com/?fid=889964283620757998 If you flashed back to original, that wouldn't be the issue. You could try clearing the data from the updates app.

Clearing cache data did the trick. Dling now. Thx!!!

[jcrutchvt2010]

Negative, that is not normal behavior. It didn't do that until the August update. Why would you need a page dot if there are no pages? Also, long press on the home screen until the launcher settings show and press home. Or add an icon and remove it, you'll notice it has the animation for the dot to fade away. But it comes back when you do other things. But if the dot should always be there, there wouldn't be a fade animation at all...

Yep I see what you mean I had just never used blank screens before.

[jcrutchvt2010]

683 loaded great. Thank you jcrutchvt2010.

Ok all, got the uploads sorted. OP updated with direct links to download universal loaders for EITHER 638 or 683. Please let me know if you have any issues. As always, no china, ATT, sprint, or BB10 devices. I kid. Too soon?

[jcrutchvt2010]

pointer mode appears to be broken I may have been the only one using that though...

Nvm had a typo in my setting it's back