Database Info

Some ICS 4.0 bugs and quirks

NOTE: This is a list of bugs for STOCK (NON-MODDED) ICS 4.0.3 & 4.0.4 (LC4, LD2, and LE2) (Most bugs from the initial LC4 leak fixed after the two major version leak updates) from DesignGears.
If you have flashed to ANY OTHER CUSTOM ICS 4.0 ROM, PLEASE WRITE IN THE DEVELOPERS' / ROM thread.
1 - 03/26/2012: When selecting "Contacts to Display" and selecting CUSTOMIZE LIST > Selecting ONLY Google Contacts (EXCLUDE G+).
Then you start typing someone's name, it returns contacts in SIM card and on Google contacts.
2 - 03/26/2012: Autocorrect on the included "Android Keyboard" doesn't work by pressing spacebar.....like it had been in previous 2.3.6. Even when changing setting to VERY AGGRESSIVE. FIXED IN UCLD2 LEAK
3 - 03/26/2012 [CONFIRMED] When deleting a message thread, the phone will freeze and turn into a blank screen (except notification bar) then the messaging app will close. FIXED IN UCLD2 LEAK
4 - 03/26/2012: [CONFIRMED] When using the "PHONE" icon to bring up dialer, contacts tab is no longer associated in it.
5 - 03/27/2012: 50/50 Users report more sensitivity on the touch screen, some report lack of sensitivity of touch.
6 - 03/27/2012: HOW TO take screen shot: Press AND HOLD ... VOL DOWN + POWER BUTTON for at LEAST 1-2 SECONDS. You will then be prompted to view the screenshot in notification bar / indicator.
METHOD #2 of taking screenshots: Press and HOLD Power button + HOME key.
7 - 03/29/2012: Some users report when tapping "RESTART" or "SHUTDOWN" on STOCK Power-button option, the phone will freeze. Either you have it or you don't. FIXED IN UCLD2 LEAK
7 - 04/02/2012: Users report echoing or unable to hear other party on an INCOMING call. This is a "hit or miss" bug.
8 - 04/02/2012: [CONFIRMED]Bluetooth stack in the new kernel has resolved a LOT of vehicle-to-android phone issue (static, drops, functions, etc.).
10 - 04/04/2012: [CONFIRMED BIG ISSUE] When creating a new contact in phone and setting it to GOOGLE CONTACTs; forcing a sync or auto-sync option will NOT push the contact to google servers for backup purposes. However, deleting or creating a contact while logged in on a full web browser will push it back to the phone via sync. FIXED IN UCLD2 LEAK
11 - 04/09/2012: [CONFIRMED] There are known issues with stock email app. Syncing unread/read e-mails will not push back to exchange server email client. Also emails me not completely send and stays "stuck" in outgoing box.
FIX (Thanks dixit):
This google thread shows the official issue and show that it was fixed officially in 4.0.4.
https://code.google.com/p/android/is...etail?id=23534
If you scroll down to post 51 you will see there is a link where someone put the two 4.0.4 APKs from a Spring Nexus S 4G which fixes this issue as explained above. So just go to that link, download the two Email/Exchange APKs, put them in System/App, correct permissions, remove your two Samsung Native Email APKs, and that will fix the issue of emails being stuck in the outbox.
Here is the direct link to those two APKs off Post 51
http://files.devphone.org/404mail/
11 - 04/15/2012: [CONFIRMED] When adjusting ringtone level in SETTINGS > SOUNDS, the ringtone level will not lower or raise; it stays at one level.
FIX: Adjust via volume rocker while in any other system screen (Home, MMS, etc) BUT NOT IN-APP. *Thanks petrochemicals!*

Here's what I found and posted in another thread...
So far so good except a few things:
1) I hate the fact that "contacts" are no longer visible in the dialer. Now I need another icon that I rarely use. The only option appears to hit menu and select contacts from there.
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
3) Can't use built in hotspot tethering anymore. This is something that I use with my tablet often. Any solutions other than a 3rd party app? If not, what app is everyone using for hotspot tethering?
4) Why in the world don't the signal bars turn green once fully connected? It's driving me crazy because normally that means its not connected to your Google account. This is the first time I've seen this (of MANY different Android phones). - This appears to be an ATT thing as other carriers and phones change the signal bars color when its connected to your google account (as it always should be).

Grey bars, works for for me; turning green = same color as battery = confusion to some it is acting as a double icon of ur battery? lol
I don't get a freeze in the menu.... I'm assuming you're talking about the built-in menu not a modded one? I just use the one that came with the ICS.
Hotspot tethering, you'll have to wait for a dev to mod that unless you are wanting an app for it.

I can tell you that I got my portable hotspot to work. It gave me numerous error messages though when I first went to set it up and the screen freezes when I turn it on. I went back to home and back to the hotspot settings and the toggle remained on. I changed the default password to all 9s bc I was getting an invalid password error. After that, I connected my old iPhone to the Skyrocket wi-fi.
I used to use Barnicle Wi-fi tether but it doesn't work now. Is there a difference between the stock portable wi-fi hotspot program on the phone and Barnicle? Im just curious if Barnicle masked the fact that the user was tethering.
Sent from my SAMSUNG-SGH-I727 using XDA

Yes, I'm referring to the built in power menu. I fixed permissions in CWM and still no go. Any ideas???

I find the keyboard to be a bit slow on the responsive side. Anyone else running into that or am I just trying to type too fast?

Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.

good job guys, keep up the troubleshooting so hopefully some devs will cook up a nice rom

fongz27 said:
Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.
Click to expand...
Click to collapse
I'll give that a spin. I did that once already to fix my home button problem, so I'll try and do another. But yea I use to use the ICS keyboard from the market on GB, and that was quick enough for me.

stuff I notice so far
I did notice the contact tab missing from dialer. The menu selected one doesn't allow right and left swipe for call/text. In the contacts app, the swipe works ok.
the only real problem for me, thus far, is when deleting SMS threads; messaging force closes.
Anyone else have that?
BTW thanks for starting this thread, wasn't sure where to post bugs - I think this may be usefull to keep them all in one spot.

Getting some odd behavior from Rom Mngr
Aside from other errors I got, when I ask ROM Mngr. to perform a task, I get a bunch of errors like "Messaging has failed," "Internet has failed," "com.google.xx" has failed. But then it goes and performs the request.
However! Whereas on 2.3.6 UCLA3, when requesting a backup via ROM Mngr., it would go straight to the backup whereas now, it goes into CWM and I still have to select Backup from the option there.

Deleting threads freezes my messaging also.
Sent from my SAMSUNG-SGH-I727 using XDA

Noticed a new one.
Not getting pictures with messages now, too.
Nvm. Damn - I hate bug posts. They come, they go.

The only thing I've noticed so far is I don't seem to get LTE in my house anymore. Boo...

I'm having issues with audio files. I can't use either Google Play Music, Samsung Music Player or Doubletwist to play audio. It creates duplicates which I believe corrupt the file itself.
Sent from my SAMSUNG-SGH-I727 using XDA

jayrod88 said:
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
Click to expand...
Click to collapse
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.

rjohnstone said:
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.
Click to expand...
Click to collapse
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.

fongz27 said:
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.
Click to expand...
Click to collapse
Yep.
Face unlock does work... just not all the time.

have you done "improve facial recognition " if so how many additional pictures did you take?

Facial unlock is perfect for me. No problems whatsoever.
Sent from my SAMSUNG-SGH-I727 using XDA

Surely there's a solution

I've searched here, google, etc... and the solution still escapes me
How in the world do I launch Google voice search (rather than S Voice) via bluetooth when the phone is locked? This is for bluetooth dialing and navigating (push and hold BT headset call button, say "CALL ......" or "NAVIGATE TO ......."
I don't want to flash a new ROM for this, but I'm willing to consider it IF:
- Above function works
- GPS locks are just as fast as stock
- Stability is top notch
- Battery life is as good or better than stock
- UI must be smooth
Stock ROM is great!!! I'd hate to deviate, but I hate even more not being able to use the BT dialing (S Voice SUCKS and rarely works!!!)
I have to have my phone locked (exchange server rules for my employer email)... it's a good policy anyway.
I am currently Stock Rooted, bootloader locked (I can unlock if necessary)
I've seen suggestions to use the Bluetotth launcher app, which works, but not when phone is locked.
The stock ICS has this feature. I hate the Samsung forced S Voice without giving us the alternative to go back to the google apps (which is MUCH better).

I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice

Sycobob said:
I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice
Click to expand...
Click to collapse
I've frozen S Voice with Titanium Backup. All that did was completely remove any ability for voice dialing through bluetooth.
The settings you refered to is a good suggestion, but only disables the home button (pressing it twice) from launching S Voice
Google Voice Search has no usable settings and I'm unable to use it as a default rather than S Voice

Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.

bobloblaw1 said:
Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.
Click to expand...
Click to collapse
Freezing in titanium is the same as disabling in the applications menu.
I feel like i read somewhere that synergyROM had this feature of google now replacing s-voice when you froze it. Ill try to find what im talking about for you. Thats the only solution i can think of.
Sent from my SCH-I535 using xda app-developers app

[Q] Odd classic voice dialer intermittently when using wired headset

Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3

bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.

joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3

take a screenshot of your classic looking dialer and post it here.

simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3

bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.

simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3

instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.

simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3

Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3

bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.

simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3

bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.

Sadly disappointed with various limitations and recurring issues :cry:

I received the phone and have been using it since 2/10. I have the 8/256gb version with the Chinese ROM. The phone is awesome with regards to build quality and so on, but I'm extremely frustrated with the issues that I'm seeing daily. I'm ready to ditch it and return to my Xiaomi Mi Mix.
Notifications are all turned off by default and every app notification must be turned on individually. So every new app needs this manual step.
Notifications, even if enabled correctly, lock screen, does not show up on the lock screen
Various apps do not receive new "data" such as emails until opened. (runs in background, just noticed the application freeze option, and turned that off)
Device Administrator removes MS Outlook as device admin regularly, used to be daily. (required by work)
When plugged into USB-C for Android Auto, must change setting to Transfer files, every time in order to activate Android Auto.
Resets Assistive Voice App nightly, removes Google Assistant and elects none, not even breeno voice.
Depending on task, it switches to use the Breeno Browser instead of Chrome as an intermediary and therefore does not fully like to the next task.
Swiping down on home screen brings up breeno search via breeno browser.
Cannot activate Location Sharing Services even if Location is turned on. I think this has to do w/ limitations on the "Region"
Things that I know does not work
Cannot use 3rd party messaging app. Once 3rd party app is set as default, it switches back to Oppo msgs app due to "security"
Cannot use another Launcher.
Cannot use Google Assistant wake up phrase
Can anyone else confirm if you're also experiencing the above? I'm willing to reset the phone but I think these are "defaults" and not like a choice I made during set-up to cause these issues. Thanks for reading.

The issues you mention are common and are part of the challenge of owning a phone with a Chinese rom. The trade-off is that you own a unique phone with awesome hardware.
I have been able to get all notifications to work though adjusting the notification options as you say, but you can also adjust the power saver and start-up options. You can also lock apps in the recent tasks screen.
You can also uninstall some of the built-in Chinese apps via adb. See the thread in the Find X forum. For example I have uninstalled the browser so it never comes up. I have not uninstalled the launcher as I am ok with the Oppo one.
Issues I have not been able to resolve: changing the default messaging and assistant apps for the long term.
For me, I know the experience of buying a phone with a Chinese rom is never going to be as smooth as a pixel or Samsung in terms of usability, but I love the fact that it is unique and appreciate the hardware (eg charging speed).

Unfortunately, the uniqueness of the phone does not overwhelm these limitations that causes daily resetting of certain defaults for me.
I'm ok w/ not using the Launcher and some other items like google assistant. However, other limitations really create barriers that can't be looked past for me.
I think I'll look for an opportunity to get the Xiaomi Mi 10 pro when possible and sell the Reno Ace.

Fighting the power! (management)

Is it just me or this phone (or at least the CN RMX2071 roms) are super aggressive in closing apps? I know it's a general theme with "custom" (non aosp) based ROMs and most vendor UI takes, but it feels really really broken in these phones.
I have to keep the phone in "high performance" mode and even then i have to re-run some apps every other day (Nova launcher's google companion app) and even re-add widgets (Google Calendar) for them to continue to function, presumably because the power management system keeps shutting them down.
I have every single app to OFF in the App Freeze screen, every app is allowed to run in background (not the smart option, plain always-let-this-run option) and allowed to launch other apps (otherwise more things are broken) and it still feels like things are quirky due to how aggressive the power management is.
Am i missing something? are there more options that i missed? is it better in the EU/IN ROMs?

The eu rom fixes this problem

So a trade off of functionality vs latest security patches etc. Might be worth a try of switching over and at least trying it for a short little bit to determine.
Does anyone know if there's a differnce in behavior for Android Auto between CN and EU ROMs? (though i imagine its also related to power management at the least)

[DELETED]

I am on EU ROM here in the UK (A.28) and ever since I got this phone. It loves to close apps in the background. Facebook used 1400mah when it was just running in the background. Disabled it running in background, notifications work but now it only uses 234mah roughly. There system is messed up. Other apps that I like to use in the background include Google Clock and Skip Track Settings.
These I have a Tasker to launch both apps, with a little pause between launch. I have "Exclude from recent apps" enabled and then after they've launched. I get it to go home automatically. Then with my usage, I have this task running on boot, 5am (whilst I'm asleep) and on secondary app open. I don't notice it, other than when it boots and you just gotta let it run. My clock then works 100% of the time for my alarms and works all day.
One thing to note is, if you click "clear all" in recents, you have to run the task (I do this with the secondary app) to reopen the apps. Thankfyully, with Tasker with auto start-up enabled, it just works and is obviously in realme's don't close in background list.
Thankfully, with Android 11, a promising change to the rules for OEMs is that they can't have list of preferable apps and have to give all app developers an equal chance to running and not being killed. So hopefully, with Android 11, realme will have to stop this annoying practise.
Hope I've explained that well enough and you can use Tasker as a bootleg option
- Josh

Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)

ransagy said:
Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)
Click to expand...
Click to collapse
Yes, apps that realme likes to kill in the background. I have them opened by Tasker whilst I'm sleeping and on boot as realme doesn't close Tasker in the background and then the apps work fine all day. I don't notice it open them other than on boot as otherwise my phone is in standby.
Alarms never triggered for me as realme killed Google Clock, that's why now when it just opens in the background as I sleep it isn't killed.
I don't use my phone intensely and because Tasker opens them as apps, realme can't close them because they're still technically open, even though they don't show in recents. That's why when you clear all apps in recents, you need to then reopen them (that's what my secondary Tasker app does).
As for Android Auto, I haven't had any issue with it. When I use it, my car isn't technical so it uses the screen. I plug my phone in, turn the car engine on and phone begins to charge. Then with a bluetooth to FM adapter, my phone auto connects to bluetooth, and as soon as my phone connects, Android Auto automatically opens (as I have it enabled in Auto's settings) and I get it to play music automatically.
For someone using the actual plug in display to the car, I don't know. Android Auto came pre-installed and all I had to do was install the version for "phone screens".
If you need help with Tasker, my insta is below. Feel free to reply to this or message me on there.
Hope this helps
- Josh

It does help, Thanks!

ransagy said:
Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)
Click to expand...
Click to collapse
Due to a similar issue I had in my corporate Outlook e-mail app, I searched for a solution for the error I got there like "Your organization has removed its data associated with this app" and I found an article from Microsoft proposing a resolution (url not include in this post because it is not allowed, however it is quite easy to find it).
I followed that resolution proposed and it worked for Google Clock app. The alarm finally rang this morning!
Basically, you should go to app list, choose Google Clock (or even any clock app) and configure it as follows:
-in "Power Saver", choose ""Run in Background"
-Set "Allow Notifications" to on
-Set "Auto Startup" to on
-Set "Allow other Apps or Services to Launch" to on
Hope it helps

Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!

Wpbarreto said:
Due to a similar issue I had in my corporate Outlook e-mail app, I searched for a solution for the error I got there like "Your organization has removed its data associated with this app" and I found an article from Microsoft proposing a resolution (url not include in this post because it is not allowed, however it is quite easy to find it).
I followed that resolution proposed and it worked for Google Clock app. The alarm finally rang this morning!
Basically, you should go to app list, choose Google Clock (or even any clock app) and configure it as follows:
-in "Power Saver", choose ""Run in Background"
-Set "Allow Notifications" to on
-Set "Auto Startup" to on
-Set "Allow other Apps or Services to Launch" to on
Hope it helps
Click to expand...
Click to collapse
ransagy said:
Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!
Click to expand...
Click to collapse
I also enabled all of these settings (other than last one, can't find it) and had some days it worked, some days it didn't. So for the sake of my actual work, I used my Tasker method and works 100% of the time. Ultimately, realme kinda screwed us over. Ultimately, Android 11 should fix this with it's new guidelines so let's just work around it in the mean time.

Yeah, I'm yet to try your Tasker method, i definitely will though, it's basically the last ditch effort here. I just finished switching to the EU rom as well.

ransagy said:
Yeah, I'm yet to try your Tasker method, i definitely will though, it's basically the last ditch effort here. I just finished switching to the EU rom as well.
Click to expand...
Click to collapse
ransagy said:
Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!
Click to expand...
Click to collapse
On Startup Manager, for me on EU ROM A.30, and since I first got the phone. The limit on Startup Manager was and still is 20 not recommended startup apps. This is, in realme's words, "to ensure the hone will run smoothly", like bollocks. My old phone had 3GB of RAM and has the exact same apps and ran fine (other than only allowing 3 backgrounds apps to run before memory ran out). But with 8GB and SD865, it's just their way of saying, oh look we have this amount of screen on time. Judging by the list on A.30, the Google Clock is now recommended (I don't think it was before). Either way, realme is gonna get shunned with Android 11's new guidelines and it'll be a fair playing field.
Android Authority - Google Fighting Unfair Power Management Article (Just an interesting read):
www. androidauthority. com/ android-11-background-apps-1136794/
- Josh

Yeah, EU rom (A.20 as its the only one compatible with the chinese model right now) seems to have saner behavior, 20 startup apps instead of 5 and i don't think it has that "allow others to launch" option at all, so not blocking it even? We'll know soon. App Freeze doesn't seem to be automatically enabling on apps, either, also good.
Google Clock worked for me this morning (i duplicated the "system" clock alarms, just a couple mins later to be sure something triggers)
I'll check Android Auto today as well.
I AM always on High Performance mode though.
The thing is about Android 11's changes, that they seem to be worded a little on the easy side in the Google language - makes it seem to me that Google is just asking the vendors to be a little clearer on what they do when informing the users, not that they absolutely can't kill background apps. Here's hoping though.

ransagy said:
Yeah, EU rom (A.20 as its the only one compatible with the chinese model right now) seems to have saner behavior, 20 startup apps instead of 5 and i don't think it has that "allow others to launch" option at all, so not blocking it even? We'll know soon. App Freeze doesn't seem to be automatically enabling on apps, either, also good.
Google Clock worked for me this morning (i duplicated the "system" clock alarms, just a couple mins later to be sure something triggers)
I'll check Android Auto today as well.
I AM always on High Performance mode though.
The thing is about Android 11's changes, that they seem to be worded a little on the easy side in the Google language - makes it seem to me that Google is just asking the vendors to be a little clearer on what they do when informing the users, not that they absolutely can't kill background apps. Here's hoping though.
Click to expand...
Click to collapse
I keep my settings to standard and never do high performance stuff. I also use 60hz as although I love 90hz, I also love battery life and it isn't enough for me to justify the battery usage.

Yeah, I dropped down to normal and had no issues so far, without tasker of anything, just the EU A.20 ROM.
I am on 90Hz all the time though - As someone who is used to 144Hz monitors and gaming, i can sorely tell the difference between 60 and 90 and to me the battery life difference is somewhat negligible.
I haven't tried Android Auto, but we'll see soon enough. Android 11 also brings wireless Auto to everyone, so that might help there as well.