Any chance that a dev has investigated backporting AoD for A10?
Seeing how buggy 11 is right now, maybe we could see some action of AoD on 10 stock, modded?
Related
Do any of the Lollipop Roms for 1+1 have Nfc polling modes (Screen on unlocked/Screen on locked/Screen off)
I have checked changelogs but I couldnt find anything listed regarding nfc polling mode.
Some 4.x ROM's have the ability for NFC to work when the screen is locked or turned off.
Are there any Lollipop ROMS out there that can do this yet? Or a way to get it to work?
i understand Xposed doesn't work on Lollipop so that's not an option.
Most of the builds after 12/07 have it working. Just read the changelogs.
Canterbury said:
Some 4.x ROM's have the ability for NFC to work when the screen is locked or turned off.
Are there any Lollipop ROMS out there that can do this yet? Or a way to get it to work?
i understand Xposed doesn't work on Lollipop so that's not an option.
Click to expand...
Click to collapse
So far for the Builds I've tested, 3 now, NFC works between OnePlus to another android NFC abled phone, just not OnePlus to OnePlus.
Updated first post.
Wanting to know if any Lollipop Roms have Nfc polling modes
Any lollipop roms yet?
Still no lollipop roms with NFC polling for the 1+1?
I hope someone implements nfc polling soon - i have too many nfc tags to go without now.
Perhaps Pie has better performance and battery, but i still prefer Oreo because has better features to me like brightness, Wifi more stable, funcional Dolby, calls record, no disturbing alarm clock,etc..
What do you think?
I liked OOS Oreo because it was faithful to stock Android. With Pie, they changed the design of the phone, settings, etc. apps to a cheaper looking design. I really like the new transition animations and the notification management, but the design is inconsistent, the recent apps screen is buggy even in the final release. These small things end up irking me. It seems unfinished, unpolished while Oreo was buttery clean and smooth. I'll probably revert to it once I have some time to spare.
Ha
FAIL
For me, i like the added smoothness and the changed System UI, others could disagree with me (it's totally fine no hatred) but it's more prominent compared to oreo.
Personnaly i have battery problems compared to oreo , the pie battery seems much worse...
I would like to go back to oreo for that reason
Android Pie
pie bring so many change like typing magnifier, volume slider at the right position but the thing i love the most is the animation, its look so much better than oreo. Though it have some catch, pie recent panel like....nah
Dunno what everyone else's issues are with Pie. My phone is significantly improved as regards battery, auto brightness works (hint, you have to turn it on), no problems at all with it.
Then again, I upgraded from a freshly wiped phone, I didn't upgrade over a whole lot of junk apps.
I updated from latest Oreo rooted TWRP with ex kernel to Pie. Flashed in TWRP, flashed TWRP reboot to recovery and flashed 17.2 Magisk and all way fine. I wiped cache in phone and recovery and no battery issues at all. Slightly better then Oreo. Not really a fan of the new settings (gotta embrace change) other than that, Pie is a big time go!
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
UDPSendToFailed said:
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
Click to expand...
Click to collapse
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Mikxx said:
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Click to expand...
Click to collapse
Yea, I have Tab A 10.5 (2018), SM-T590.
Basically I installed TWRP from here: [RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597] | XDA Developers Forums (xda-developers.com)
Then I just downloaded some GSIs and flashed them to see which one works, with some changes to the original post. I may create an updated guide for installing GSI ROMs using MrHomebrew's TWRP without having to mess with SD cards, etc, but you can follow the original guide to have a mostly working system.
You can download ROMs from here: Generic System Image (GSI) list · phhusson/treble_experimentations Wiki · GitHub
I'm still not sure about how that A-only / AB thing works, if you have updated to Android 10 on stock system, AB ROMs with A64 binder will run.
Is there a way to disable the touch function of the fingerprint scanner? It drives me nuts. At first i thought it would be ghosting but then i figured out that when i tab the fingerprint scanner it selects stuff on my launcher and in system settings.
Using Arrow Os 12 beta right now and before i had Ancient OS with the same "error". Before that i had Miui Oneos and it didnt have that "function". Is it just a bug of Arrow OS 12? Why did Ancient OS 5.6 which is still android 11 also have the same problem?
Any insight on this issue?
You're more likely to receive help if you post in the respective ROM forum. This is for general questions and answers.
Hi there,
Ever since Google removed global immersive mode starting from A11, I've stuck to A10 to keep that feature. Since A10 is no longer supported by most maintainers, I've been living with all the bugs that came with the last supported version of my A10 ROM (crDroid). I know that Samsung still allows their phones to access something similar to disable the status bar, but every ROM I've looked at has lacked such a feature. Is there any ROMs that do something like that? Or a root-related method that allows me to hide/disable the status bar for the most part?
Thanks!