Develop Bugs

After digging found a aokp rom

After digging and google searching i found a aokp rom.its pretty sweet not sure why its not posted in the forums.for anyone who wants to try here is the link.
https://androidfilehost.com/?w=files&flid=130222

gillim74 said:
After digging and google searching i found a aokp rom.its pretty sweet not sure why its not posted in the forums.for anyone who wants to try here is the link.
https://androidfilehost.com/?w=files&flid=130222
Click to expand...
Click to collapse
It's a test build with an unknown status, I couldn't find an OP anywhere.
http://www.cyanogenmods.org/forums/topic/htc-10-aokp-marshmallow-rom/
Considering the state CM has been for a long while, what works and what doesn't? What model do you have? What carrier?

Ariac Konrel said:
It's a test build with an unknown status, I couldn't find an OP anywhere.
http://www.cyanogenmods.org/forums/topic/htc-10-aokp-marshmallow-rom/
Considering the state CM has been for a long while, what works and what doesn't? What model do you have? What carrier?
Click to expand...
Click to collapse
I have been running it and its pretty solid.htc 10 verizon.it was last updated the 19th

gillim74 said:
I have been running it and its pretty solid.htc 10 verizon.it was last updated the 19th
Click to expand...
Click to collapse
Does Verizon carrier show as 3107?

krazie1 said:
Does Verizon carrier show as 3107?
Click to expand...
Click to collapse
Not on mine

gillim74 said:
I have been running it and its pretty solid.htc 10 verizon.it was last updated the 19th
Click to expand...
Click to collapse
traced it down to this member: PippoX3
http://forum.xda-developers.com/htc...evelopment-t3376014/post68823357#post68823357

tkacer said:
traced it down to this member: PippoX3
http://forum.xda-developers.com/htc...evelopment-t3376014/post68823357#post68823357
Click to expand...
Click to collapse
Nice i just sent him a message asking if hes gonna update it.its fast and super smooth

I like it so far, I still have to do some tests.
Also, for Verizon USA people:
Set your preferred network type to LTE and your APN to VZWINTERNET.
It shows up as Verizon Wireless instead of 3107 and has LTE instead of roaming as the data type. This is ****ing lit, I'mma do some more tests.
And that causes SMS not to work for me. Back to the drawing board, I think some build.prop edits should help.
Edit: CDMA+EVDO/CDMA mode works like a charm minus the 3107 label and the fact that is says roaming. Oh well. SMS/MMS/Data/Calls work fine.

Ariac Konrel said:
I like it so far, I still have to do some tests.
Also, for Verizon USA people:
Set your preferred network type to LTE and your APN to VZWINTERNET.
It shows up as Verizon Wireless instead of 3107 and has LTE instead of roaming as the data type. This is ****ing lit, I'mma do some more tests.
And that causes SMS not to work for me. Back to the drawing board, I think some build.prop edits should help.
Edit: CDMA+EVDO/CDMA mode works like a charm minus the 3107 label and the fact that is says roaming. Oh well. SMS/MMS/Data/Calls work fine.
Click to expand...
Click to collapse
Set it too cdma/lte/evdo and youll have lte and everything else keep the same apn the carrier might not say verizon but that dont make a difference to me.

Just to clarify, this only works with the firmware voodoo, right?
Sent from my HTC6545LVW using XDA-Developers mobile app

jtommyj said:
Just to clarify, this only works with the firmware voodoo, right?
Sent from my HTC6545LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Lol as far as i know

This is my setup.

Talked to the maintaner of this rom and he said he will keep it updated and it will go public soon.

gillim74 said:
Talked to the maintaner of this rom and he said he will keep it updated and it will go public soon.
Click to expand...
Click to collapse
much like all CM based roms, this also has no sound making/receiving calls with earbuds....hope they fix soon!

That and Verizon showing as 3107 is getting annoying, lol

andybones said:
That and Verizon showing as 3107 is getting annoying, lol
Click to expand...
Click to collapse
Lol mine says sprint

tkacer said:
much like all CM based roms, this also has no sound making/receiving calls with earbuds....hope they fix soon!
Click to expand...
Click to collapse
This is what's holding me back from CM/AOSP ROMS.

gillim74 said:
after digging and google searching i found a aokp rom.its pretty sweet not sure why its not posted in the forums.for anyone who wants to try here is the link.
https://androidfilehost.com/?w=files&flid=95228
Click to expand...
Click to collapse
new 2017 n builds !

tkacer said:
new 2017 n builds !
Click to expand...
Click to collapse
I have a op3 now

You could follow on Google+

Thinq does not have advanced messaging option

I bought 2 US thinqs from t-mobile the other day. Both have the same base version. Security version. I've compared every setting I can think of. But one of the phones does not show Advanced messaging options in settings. No alias settings. My. Phone shows a click able menu called "advanced messaging" but the other phone does not. Anybody know anything about this?

Tragion said:
I bought 2 US thinqs from t-mobile the other day. Both have the same base version. Security version. I've compared every setting I can think of. But one of the phones does not show Advanced messaging options in settings. No alias settings. My. Phone shows a click able menu called "advanced messaging" but the other phone does not. Anybody know anything about this?
Click to expand...
Click to collapse
My silver T-Mobile G7 has advanced settings, and I'll get back on here after I check my wife's red one. What do you want from advanced settings, and what does alias do?
Sent from my LM-G710 using Tapatalk

Idon12no said:
My silver T-Mobile G7 has advanced settings, and I'll get back on here after I check my wife's red one. What do you want from advanced settings, and what does alias do?
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
I'm trying to figure out why I can't get delivered and read reports when my friend and I text each other. We don't have this problem with anybody else. Just each other. This seems to be the only setting that could be causing the issue. Delivery and read reports are working with mms between the two phones but not sms. Alias seems to just be another version of your personal profile on the phone. Not too concerned about that function but it seems to be connected to since she doesn't have that setting either

Hmmm, just got my silver T-Mobile G7 ThinQ Friday and I don't have advanced messaging on it either.

Lancerz said:
Hmmm, just got my silver T-Mobile G7 ThinQ Friday and I don't have advanced messaging on it either.
Click to expand...
Click to collapse
I think it was a bad installation of the update. Factory reset seems to have solved the problem

Tragion said:
I think it was a bad installation of the update. Factory reset seems to have solved the problem
Click to expand...
Click to collapse
Ok thanks, think I'll try that tomorrow then! Can you take a screenshot of the settings in your messages app please, thanks.

Tragion said:
I think it was a bad installation of the update. Factory reset seems to have solved the problem
Click to expand...
Click to collapse
Thanks that did it! I see some people don't know what advanced messaging is, but now I can see when my wife is typing or has read my text messages on her Galaxy S8.

Lancerz said:
Thanks that did it! I see some people don't know what advanced messaging is, but now I can see when my wife is typing or has read my text messages on her Galaxy S8.
Click to expand...
Click to collapse
Hooray, I'm useful!

Lancerz said:
Thanks that did it! I see some people don't know what advanced messaging is, but now I can see when my wife is typing or has read my text messages on her Galaxy S8.
Click to expand...
Click to collapse
Hi, do you have the LG Message app or thr Google Message app? Also, do you still have the wide angle camera of the front camera?

chakchak said:
Hi, do you have the LG Message app or thr Google Message app? Also, do you still have the wide angle camera of the front camera?
Click to expand...
Click to collapse
I don't think it ever had wide angle in the front. That's why there's two lenses on the back.

t1.8matt said:
I don't think it ever had wide angle in the front. That's why there's two lenses on the back.
Click to expand...
Click to collapse
I read the specs, and it shows that the front has it? And someone confirmed it was there before the update :laugh:

Question Updated To (13) Dev. Preview #2 & Lost Vo5G For Voice Calls!

Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es

evnStevn said:
Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es
Click to expand...
Click to collapse
Beta 1 should come out tomorrow, so I guess we will see what happens.

Doug8796 said:
Beta 1 should come out tomorrow, so I guess we will see what happens.
Click to expand...
Click to collapse
Where did you hear the 13 beta would drop tomorrow?

opz187 said:
Where did you hear the 13 beta would drop tomorrow?
Click to expand...
Click to collapse
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview

roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse
Gotcha, makes sense now

This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.

Well said, and as I said on reddit:
"The first build was released on 2nd Thursday, the 10th of February. The second build was released the 3rd Thursday, the 17th of March. Due to the dirty pipe exploit and taking an average of the two dates of the month (roughly 13.5 day of the month (rounds up)), the build will almost certainly come out tomorrow, April 14, 2022."
roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse

here you go, tell me if you need something more. es

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
a magenta fan too, I take it? was that what you were looking for? If you need something different just let me know. es

The modem in DP2 is older and less refined than the newer builds of Android 12+.

This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
LLStarks said:
This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.
Click to expand...
Click to collapse
Hey, I was just reading your comments, and yes, now, they are acknowledging the missing field. The first time I sent beta feedback on this issue was two weeks prior. They got everything from me, bug report, screen recordings from #1 & #2, as if "the before, and after" weight -loss ads! So a day or goes by, got the buginizer confirmation in my inbox, and I looked for the report filling in the beta feedback app grouped together with others I reported and the whole thing had been deleted, it wasn't anywhere! So I said fuc$ this shi#, I did the whole thing over again, even flashed back to DPB #1, to make sure Vo5G was still there! (lol) This time around, I made mention (several times) throughout my feedback report, that this first report seem to fall off of the radar, and could someone explain how & why, it had to be human error, blah, blah blah, & anyway this time around, it seems to be getting worked, but not vanishing into thin air. A friend of mine that I spoke to about this, got me in his mindset that this was maybe something that wasn't supposed to get out for public consumption until their Pixel 7 Series rollout, of course equipped with (stable) Android 13, and Vo5G Voice Calls included in their "Feature Blitz". To be honest, I'm still not so sure some of that isn't going on, as we all know both Google & Samsung been playing that shi# for years (because they can)!

LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse

hey, thanks for the hit. es

they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.

Beta 1 still doesn't include this.

NewDev4IOS said:
they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.
Click to expand...
Click to collapse
I heard it was omitted (not included) from DP#2 affecting only T-Mobile customers?! It may be just a rumor, others may be experiencing the same as us. I happy to learn we will see it again soon, next update or Android 13 Beta along with Face Unlock!

Doug8796 said:
The modem in DP2 is older and less refined than the newer builds of Android 12+.
Click to expand...
Click to collapse
how did that happen...another of Google's attempts to get all the teams back under one roof, post-covid 19 style-ish, by bringing back the ever popular, "Bring Your Medical Marijuana To Work" week?! lol

The QPR modems have generally been the newest.
But with respect to Vo5G in particular, I'm not really sure where the carrier settings are being read from. Overwriting the protobuf files for T-Mobile doesn't seem to help.

Question Block 13 update?

I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?

I assume if your phone rooted, automatically updating will fail

It doesn't, and I lose root, that's what I thought last security update— which is why i'm concerned

christiebunny said:
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
Click to expand...
Click to collapse
Yes tap build 7 times for Developer Settings and disable automatic updatea

You could unlock the bootloader (which would require a device wipe) and then reinstall your current build of Android manually. That would be one of the only ways to officially disable automatic updates as well as update notifications.

I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
You may be able to delay it some buy factory resetting and some other things, but it's a big "maybe", and ultimately I don't think there's any way for you to avoid it.
biggiesmalls657 said:
Yes tap build 7 times for Developer Settings and disable automatic updatea
Click to expand...
Click to collapse
The OP you quoted says:
christiebunny said:
I've already got 'automatic updates' turned off, but that isn't stopping it.
Click to expand...
Click to collapse

roirraW edor ehT said:
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
Click to expand...
Click to collapse
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Maybe it was even the same person mentioning it 3 times, lol. Not really sure.
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or just a fluke situation.

Lughnasadh said:
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Didn't go back to check the posts.
Click to expand...
Click to collapse
I think I've seen more than one person report this too, but wasn't sure, and as I always say, I keep forgetting the old stuff. What was I talking about?
Lughnasadh said:
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or something else is going on.
Click to expand...
Click to collapse
I suspect (but pretty obvious) that they have ways of force-pushing updates through despite the automatic update setting (or it's broken in typical Google fashion), but I think it's the former.
Then I believe they made a command decision that the vulnerability is too bad and that they felt they must force it on everyone. Again, given Google's reputation, this could've easily been an accident as well - "who pushed the red button!?!?!?"
And then the further command decision to push over top of modded, or at least simply rooted, devices as much as possible. I wonder what happens in the case someone has truly modified their software more aggressively at the root level. It wouldn't surprise me if it would've still overridden in those cases.
While, of course, those would be questionable actions for them to take (if these are actually true in the first place), I either partially or mostly agree with them, but just on principle, I can't wholeheartedly agree with them. Somewhere in the 40%-99% range.
If true, hopefully this is a very rare occurrence and not going to be how it is from now on. I will wait patiently to observe how things go.

What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!

Annil said:
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Click to expand...
Click to collapse
V4A, at least in my case. I'm not updating until its compatible, or I find a better alternative.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
Android 13 cannot be modified is one reason...

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
Could you explain your theory on this?

christiebunny said:
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Click to expand...
Click to collapse
Compatibility seems remarkably intact, magisk works as intended, and there is no evidence of any change in what control you have.

96carboard said:
Could you explain your theory on this?
Click to expand...
Click to collapse
Modified SystemUI bootloops.

Tulsadiver said:
Modified SystemUI bootloops.
Click to expand...
Click to collapse
Ok? How are you modifying it?

96carboard said:
Ok? How are you modifying it?
Click to expand...
Click to collapse
Same way I always have.

Tulsadiver said:
Same way I always have.
Click to expand...
Click to collapse
That answer really doesn't help anyone.

96carboard said:
That answer really doesn't help anyone.
Click to expand...
Click to collapse
Any like these:
Stand alone Clock, Navbargone, Battery Icon Gone, etc. Mods
For stock rooted only. For most part, these cannot be flashed together. These mods use the SystemUI Patcher Module Template by @Jai_08 By @cool_modules on telegram. After Installing this module, your screen will relock after every reboot of...
forum.xda-developers.com

Question Slower after Android 13/One UI 5 update. Anyone else?

It seems like the phone is ever-so-slightly-slower following the Android 13/One UI 5 update.
Splash screens of various apps consistently appear for a few split seconds longer than before. In fact, at least one app that used to launched instantly now shows a splash screen for a fraction of a second before launching.
Is this just my experience, or do others see the same thing as well?

xda-eh said:
It seems like the phone is ever-so-slightly-slower following the Android 13/One UI 5 update.
Splash screens of various apps consistently appear for a few split seconds longer than before. In fact, at least one app that used to launched instantly now shows a splash screen for a fraction of a second before launching.
Is this just my experience, or do others see the same thing as well?
Click to expand...
Click to collapse
Download good guardians from the galaxy store and over the app galaxy app booster. Ran it and look again

I found that upgrading from A12 to A13 slowed my phone down. Did a Factory reset and was so much better...

joke19 said:
Download good guardians from the galaxy store and over the app galaxy app booster. Ran it and look again
Click to expand...
Click to collapse
What does it do?

Galaxy app booster? Boost all app? Google?

Thank you.
But I'm trying to figure out if the small slowdown after Android 13 update is an anomaly or if most people experience it. Do you?

My phone came with Android 13/OneUI 5 preinstalled, but I later received an update with January security patch and I started facing issues after that update.
The scrolling works very bad, its like there are some ghost touches. When I scroll thru WhtasApp/Telegram chats, photos in gallary, webpages the scroll sometimes doesn't work, just like the screen didn't even register my touch. If I try to scroll fast, the scroll stops in between, just like a ghost touch or something.
I was also facing issue with fingerprint scanner when the phone screen is off for some time, but I got it resolved by removing existing finterprints. and registering new ones.
The scroll issue is a real bummer for me. I hope it get fixed with the next OneUI 5.1 update.

In Addition to what I listed above, I faced one more strange issue today. I received the January security patch AGAIN today. It's like before, the download size, update description, all is same.
The previous January security patch update I got was installed successfully, I could see it in the software section, I am not sure why I received same update again.

pank.dhnd said:
In Addition to what I listed above, I faced one more strange issue today. I received the January security patch AGAIN today. It's like before, the download size, update description, all is same.
The previous January security patch update I got was installed successfully, I could see it in the software section, I am not sure why I received same update again.
Click to expand...
Click to collapse
There was an issue with the first Jan Security Update. 2nd one should fix majority of the bugs

What region do you have and model ?

Billabomb75 said:
What region do you have and model ?
Click to expand...
Click to collapse
Region: India
Model: SM-G990E/DS

Can someone here please confirm if you are able to scroll faster? I mean, I have my old OnePlus 6 with me. If I do a simple test to scroll once in a telegram chat, OnePlus scroll backs to more number of chat messages compared to S21FE. The S21FE just scrolls to few lines.
Anyone observed same issue?

pank.dhnd said:
Can someone here please confirm if you are able to scroll faster? I mean, I have my old OnePlus 6 with me. If I do a simple test to scroll once in a telegram chat, OnePlus scroll backs to more number of chat messages compared to S21FE. The S21FE just scrolls to few lines.
Anyone observed same issue?
Click to expand...
Click to collapse
Yes. the scrolling on the S21 FE is much more stiff and "heavy" than my old J series Samsung phone. In addition, many screen taps aren't noticed by the phone, requiring me to tap again.
You should report it in the Samsung member app like I did. The more people who report these problems the bigger a chance that a patch will be issued.

joke19 said:
Galaxy app booster? Boost all app? Google?
Click to expand...
Click to collapse
The app you're referring to isn't available on my phone.

xda-eh said:
What does it do?
Click to expand...
Click to collapse
Look what you reply
xda-eh said:
The app you're referring to isn't available on my phone.
Click to expand...
Click to collapse
Galaxy store....

Did you format it after update?

joke19 said:
Galaxy store....
Click to expand...
Click to collapse
Is this the app you're referring to? Because the article you posted a screengrab of above said it's a Samsung lab.

MemurBey said:
Did you format it after update?
Click to expand...
Click to collapse
No. I'm not going to factory reset the phone after every update.

xda-eh said:
No. I'm not going to factory reset the phone after every update.
Click to expand...
Click to collapse
But you should. Do it and dont restore system options. Problem solved.
Btw you can use your phone without reset when its a small update but its a totally new android version so you must reset.

xda-eh said:
Is this the app you're referring to? Because the article you posted a screengrab of above said it's a Samsung lab.
Click to expand...
Click to collapse
Yes. I don't factory reset my phone and I bought it short after release.