Hi!
I have a Galaxy S20+ with the newest One UI 3.0 update. Is it somehow possible to get the power menu from stock Android 11 on this phone?
Best,
Smirny
Was wondering this myself. Android 11 rolled out to my S20 Ultra this morning, but no change in the power menu, and I was really hoping to find a way to use the new Smart Home Control cards on my phone via the power menu. I even reverted back to using OneUI as my default, restarted and tried other variations and still no change. Hoping as more people get it, maybe someone will find that sort of stuff in places I haven't thought to look yet
Related
I'm using my Note 8.0 LTE as both tablet and phone. Headset and an Android Wear watch would be a perfect fit. However, changing to Android 4.4 seems to bring some serious problems. I created a list of pros and cons of changing from the original 4.1.2 OS I'm currently running, based on posts on this forum:
Advantages
Enables running Android Wear (this is the only major one, afaik)
Battery Life Improvements (seems to vary between devices, some are reporting worse battery life)
Performance Improvements (unclear which)
S Note with updated SDK 3
Record your screen without an app or root - using a PC via USB cable
UI changes (not all necessarily advantages, rather ought to be listed as changes)
Multi Window lines are smoother + instead of having an arrow on the screen, you just swipe your finger from the right
White Status Bar Icons
Changed icons
Driving Mode turned into "Hands-Free Mode"
GPS turned into Location.
Turning off and on your phone, theres a new effect
A few keyboard improvements (which?)
New Setting called "Default Applications" Below "Applications"
New apps - Music Hub,Video Hub (what are the others?)
Accessibility issue fixed (meaning?)
Recent Apps"(Long Press Home Button) Words are now bigger
Multiuser support (seems to be there on mine stock with 4.1.2, though)
Disadvantages
For those wanting to root, there's KNOX voiding your warranty (I'm running stock)
OS crashes and force reboots when you press alt+tab on external bluetooth keyboard - unclear if External Keyboard Helper Pro helps with this (this is a really disadvantage for my usage scenario)
No possibility to write to the SD card
S-pen offset worse than before (doesn't seem to happen to everyone)
Reading Mode in Auto Brightness is dark; UI is a bit darker
While updating to 4.4.2 all the apps in External SD are going to Force Close
Sometimes while charging instead of the real percent of how much battery you have, it turns it into 100% (e.g. you have 82% and then suddenly its 100%)
On some apps the new KitKat toast message is reverted back to the old Jellybean Toast Message.
KitKat update retains the input method force-switch to Samsung keyboard feature.
Also the layouts for external KBs are wrong
Overheating (unclear if it's only one user reporting)
KNOX isn't a biggie to me unless I have to root, which might be the case in the future. But forced rebooting will be catastrophic for external BT keyboard usage. Overall this is my evaluation of going 4.4
Big advantage: will enable Android Wear
Some nice to haves
Some really serious problems - a crashing OS when using an external BT keyboard being the major one; problems writing to SD card another
What is your experience with the disadvantages? Are there workarounds, not requiring root, overcoming them? Were the advantages worth going for 4.4 worth it to you? Which were the major improvements, to you?
@Gadgety
I have upgraded to 4.4.2 using odin and rooted and my knox is an +1 . The most advantage for me is the wearable, I am very happy with my gear 2 neo, I have full control and can install any program (after few tricks of course.
For the problems you have mentioned, I only faced the charging percentage problem, BTW, I did get sure about it only after your thread, yesterday while charging I see it about 80% and after a while not enough to reach 100 I found it 100%, but I didn't take attention, I thought that I didn't estimate the time correctly, but now I confirm this issue.
I have external Bluetooth keyboard, but didn't try yet with my note.
I think most of these problems could be solved with a clean hard reset after upgrade, starting from scratch as new phone, unfortunately I cannot do this unless know how to backup my gear sittings and software, I take a long time to set. I know that I can backup my watch via gear manger, but this to store the watch after its factory reset, but what about after phone reset? I don't know. May somebody tell us his experience about this?
Hello.
I have some problems after OTA update to Nougat on A320FD (dual sim from arab emirates). Samsung support did not come with any helpful advice besides the magical "do the factory reset", which i save for plan B. There was no problem during updates within Marshmallow versions.
- Performance seems to be decreased (app starting and switching). Is that just my subjective perception or is the hardware of A320 suffering under Nougat?
- When phone is in sleep, pressing the home button jumps to home screen instead of showing the last open app ( e.g. chat in messenger, turn screen off with power button, press home button, phone turns on at home screen, not in messenger (messenger is shown for a split second before jumping to home screen)). Is there a no-root way how to customize behavior of home button at wake up?
- And most annoying of all, after pressing any hard button, a pop up "keyCode: KEYCODE_xxx" shows for 3 seconds (xxx being eg. BACK, HOME,...). Is there a no-root way how turn these pop-ups off? I remember this option in Engineering mode in MTK phones, not sure how about Exynos.
Thank you.
hey, when i upgraded my a5 to nougat i also noticed a performance dropped and confirmed it when i compared geekbench scores. i made a thread and got some help but ultimately just factory reset my phone and performance became actually slightly better than MM. youre gonna have to back everything up and reset it. Hopes this helps
solved
Problems with buttons were caused by a key-mapper app. I forgot i have installed and it obviously wasnt compatible with nougat.
Do you by any chance know if this phone works on LTE in the United States?
AxlRose77 said:
Do you by any chance know if this phone works on LTE in the United States?
Click to expand...
Click to collapse
I have the united kingdom firmware but I have no volTE, well I don't even have 4G but whatever.
Hopefully somebody here can help me solve this problem I have, so here it is, I bought my LG V20 about a year and a half ago from Verizon as a VS995. Since then I did the Dirty Santa exploit to unlock the bootloader and root the device. I then tried out a couple of kernels. After I got all set up, about a month later my microphones used for making calls went out on me, this means that if I want to make phone calls I would either have to wear headphones or use speaker mode. Both of the aforementioned options yielded poor quality however, in addition to this my camera will not launch forward facing. When I switch the mode it hangs black for a second and then simply goes right back to rear facing but as a wide angle. I recently flashed a kdz in an attempt to get it back to stock firmware and non root which puts my software Version on US99610n , my Build number is NRD90M, my kernel version is 3.18.31 and Android version is 7.0. Now my power button / fingerprint scanner will not work. I have checked my settings and the fingerprint registration is gone as an option so I'm thinking this is a result of this firmware not supporting the scanner/power button combo. I am hoping to flash the VS995 back somehow but I do not know how as their is an incompatibility error for this while using LGUP/Uppercut. I'm thinking I might be able to spoof my config info to display my phone info as vs995 that way it will let me regardless but I'm not sure where these files are or how many I would have to change. Any ideas on how to accomplish going back to vs995? Please let me know if more information is needed, thanks.
*UPDATE* fingerprint scanner/power button is working again.
I am considering Putting Lineage OS on my S9+ but am unsure of a few things.
I have read many threads on the subject and see that there are a number of things that can go wrong. Unfortunately, the answers use many abbreviations which means I have no idea what they are talking about. Also they talk about flashing the stock firmware to get the camera working. This seems to be different to the OS.
I did successfully install CyanogenMod on my Galaxy S2 and was very happy with it. I'm particularly unhappy with the direction of Samsung's updates. Every new update seems to break something else I use regularly.
My alternative to installing Lineage OS is to downgrade to Android 9, but remembering how snappy and clean CyanogenMod was on my S2 I'd certainly prefer Lineage as long as key functions work.
With that in mind, here are my questions:
1/ Can the Bixby button be configured to operate the flashlight without unlocking the phone? I currently have an app that does that, although it's a little unreliable and sometimes takes 3 presses.
2/ If for some reason I don't like Lineage, is it reasonably easy to go back to a stock OS? (My phone is no longer under warranty.)
3/ I understand the camera does not work as well. Is this a problem with basic picture quality or is it just some of the more advance features that are missing?
4/ Is Lineage OS compatible with Google Daydream? Samsung removed Daydream support with the Android 10 update and this is the main reason I want to go to the effort of changing the OS on my phone.
5/ Is star2lite the correct version of Lineage for my phone, SM-G965F?
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
kurtn said:
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
Click to expand...
Click to collapse
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Mike Warren said:
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Click to expand...
Click to collapse
I'm sure the bootloader is mot locked in lineageOS 17.1
kurtn said:
I'm sure the bootloader is mot locked in lineageOS 17.1
Click to expand...
Click to collapse
I'm not having any luck with loading either a 9 image or a 10 image using Odin. Is there another way?
Every time I try the phone displays: SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 9. BINARY: 7
I've tried all kinds of stuff at this point, %100 know it's software, as I did the cache wipe and it worked for about 10 seconds during a call, then stops. Speaker phone works fine, but it's literally 0 audio otherwise. Tried even the google phone app as well thinking the samsung default phone app might be the issue, but I'm seeing this is happening to others in this thread:
https://r2.community.samsung.com/t5...android-11-update-in-galaxy-a10s/td-p/9197711
This started 2 days ago. This is a major headache for me.
Anyone have any ideas on a fix? or anyone else having these issues?
I wouldn't have upgraded to 11. Samsung uses specific little apks to navigate around Android 10's buggy OS. Over 100 were added to 10 aa compared to 9 to tame 10 down and make it usable. It's even more for 11, no doubt. It may be one of those added on apks that's the issue. Almost impossible to find unless you know which ones specifically to target. In 10 I was impressed by that little nightmare. Samsung is trying very hard, but they have a crapware Android 11's framework and Google's rules to navigate to do this.
Have you updated anything before this happened, if so go back to the factory load version.
Have you installed/uninstalled any apps?
Does it work in safe mode?
Try a network reset.
Try a factory reset if you get desperate, but it's likely to reoccur if you don't find the root cause.
You can use a package disabler to troubleshoot it by disabling apks one at a time, but there are literally hundreds. It will also completely clean apk data leaving no marks; clearing data in settings doesn't always and all it takes is one to screw up some system apps... been there, done that.
Unless you're in wuv with 11, I recommend rolling back to 10 if doable. It would probably save you a lot of time and trouble. Pie is for easier to troubleshoot than 10. I have two N10+'s, one running on 9, one on 10. They will never be upgraded to 11... that's how strongly I feel about it. I'm still getting to know the Android 10 variant's characteristics, so far no major issues.
The one running on 9 is fast and very stable, current load is over 1.5 years old.
blackhawk said:
I wouldn't have upgraded to 11. Samsung uses specific little apks to navigate around Android 10's buggy OS. Over 100 were added to 10 aa compared to 9 to tame 10 down and make it usable. It's even more for 11, no doubt. It may be one of those added on apks that's the issue. Almost impossible to find unless you know which ones specifically to target. In 10 I was impressed by that little nightmare. Samsung is trying very hard, but they have a crapware Android 11's framework and Google's rules to navigate to do this.
Click to expand...
Click to collapse
Well that sucks, I bought the phone used with 11 on it already I guess I need to figure out how to roll it back.
blackhawk said:
Have you updated anything before this happened, if so go back to the factory load version.
Have you installed/uninstalled any apps?
Does it work in safe mode?
Click to expand...
Click to collapse
I haven't installed anything for over a month when it started happening. Doesn't work in safe mode, only works for 1 call after I wipe the cache.
blackhawk said:
Try a network reset.
Click to expand...
Click to collapse
Well, this actually worked, hopefully I can just do the reset if it happens again. It's working on 2 test calls so far so, here's to hoping it lasts. Really appreciate this!
blackhawk said:
Try a factory reset if you get desperate, but it's likely to reoccur if you don't find the root cause.
You can use a package disabler to troubleshoot it by disabling apks one at a time, but there are literally hundreds. It will also completely clean apk data leaving no marks; clearing data in settings doesn't always and all it takes is one to screw up some system apps... been there, done that.
Unless you're in wuv with 11, I recommend rolling back to 10 if doable. It would probably save you a lot of time and trouble. Pie is for easier to troubleshoot than 10. I have two N10+'s, one running on 9, one on 10. They will never be upgraded to 11... that's how strongly I feel about it. I'm still getting to know the Android 10 variant's characteristics, so far no major issues.
The one running on 9 is fast and very stable, current load is over 1.5 years old.
Click to expand...
Click to collapse
The upgrade from 10 to 11 didn't make much a deal to me, they aren't so different that it matters. I do think I'll look into how to downgrade to 10 though.
Appreciate the help!
Yay!
It was just a hidden settings issue. That purge should keep for a while. Occasionally I need to do it for bt on mine as well but never for the phone. Just a semi annoying glitch but not a big deal once you know the trick.
Rollback is likely impossible if it's a factory load because of the bootloader version. Typical of Samsung; I can't roll back my Q variant to Pie.
It depends on the bootloader version vs the rom version. The significant digit is the 5th one from the end. If the rom's 5th digit is the same or higher, you can flash it. If lower than the bootloader's 5th significant digit, no go.
In my case the value is 2.
I'm curious what are your impressions of 11?
blackhawk said:
Yay!
It was just a hidden settings issue. That purge should keep for a while. Occasionally I need to do it for bt on mine as well but never for the phone. Just a semi annoying glitch but not a big deal once you know the trick.
Click to expand...
Click to collapse
Well now it works on and off, very weird.
blackhawk said:
Rollback is likely impossible if it's a factory load because of the bootloader version. Typical of Samsung; I can't roll back my Q variant to Pie.
Click to expand...
Click to collapse
Ugg, that's annoying.
blackhawk said:
It depends on the bootloader version vs the rom version. The significant digit is the 5th one from the end. If the rom's 5th digit is the same or higher, you can flash it. If lower than the bootloader's 5th significant digit, no go.
Click to expand...
Click to collapse
Hmm, mine is a 7, so if I want to rom it I need to get a rom with 7 or higher? This doesn't seem good.
blackhawk said:
In my case the value is 2.
I'm curious what are your impressions of 11?
Click to expand...
Click to collapse
11 is fine, this is my 2nd note, originally had the Note 4 and really loved it. Now this one, while I like the phone has a ton of bloat on it. This Bixby crap is just awful and now this speaker issue is really making me sour to it. I honestly wish I could go to a base build of 10/11 without all the crap added, I dont use any of it because it's just flashy bells with 0 function.
It's not as bad as it looks once you sort it out.
There seems to be around 80 apks I don't want running including lame bixby.
I use this package disabler to take out the trash.
Avoid using power management and the optimization options as they cause trouble... oh yeah is that turned on?!!!
If so, that's probably the cause.
In Device Care>battery, there are a bunch of options, only toggle on fast charging. Use medium power option.
Developer options>standby apps, all buckets should show as active otherwise power management is enabled! That power management enable/disable setting can't be changed here though. If enabled you can change individual bucket settings, but it doesn't work right. Uses more battery and will cause erratic behavior. Android will run fine without it once optimized.
It's not all bloatware, some is useful. Most just sits there and does nothing unless called on.
Some like digitalwell being, kid's whatever, FB, etc are just crapware. Gone.
Starting in 10 there are around at least 100 more smaller apks showing then in 9. These are essential to tone down 10 and 11. The Samsung version of 10/11 are much better than say Pixel's variant of those OS's. They only run when needed and don't seem to cause excessive battery usage.
All cloud crap including Google Backup Transport eat battery. Google play Services and Playstore I keep disabled unless needed. Google, app and carrier feedback, turn off.
Turn off Google Firebase unless you use it.
See if you can find a adb edit to kill scoped storage on your 11 if you want. I think it exist.