Old in-call overlay, CID broken, can't find it to remove! - Samsung Galaxy S8 Themes, Apps, and Mods

So this is a silly problem, but I need some help. Back when I first got my s8 active, I went through and blacked everything out. A couple of days ago, an AT&T update left me with no names for caller ID, just numbers, even though they're listed in contacts. So in troubleshooting, I booted to safe mode, the in-call screen goes back to white, and the CID works as expected. I've removed every app and customization I can think of, but I can't affect the in-call screen, which is where the problem is. I believe I remember manually placing files back then, as substratrum wasn't available yet and it wasn't as easy as installing an APK. Can someone tell me what filename/location I should be looking for, and where to get the stock version If necessary? I just don't remember unfortunately. I'm also very open to any other suggestions anyone might have. Thanks in advance.

Related

[Q] Trying to remove lockscreen...

Before I discovered all of these ROMs on this forum that were somewhat debloated already, I spent a lot of time going through and debloating it myself to get it exactly how I want it and make it as vanilla as possible.
Along that train of thought, I'm having a heck of a time with the lockscreen. It's easy to rename or remove htclockscreen.apk, same as the Inc2 and TBolt. However, upon doing that, while the phone does revert back to the stock Android lockscreen, you can't answer an incoming call while locked. You have to unlock it, and then it appears as though you're already in the call - therefore all you can do is "end call" and call back.
For a period, Widget Locker seemed to remedy this, but it was inconsistent, at best. I've also messed with some of the idlescreen apk's (related to the Sense 3.0 "apps" within the lockscreen), to no avail. What am I missing?
TIA...
I think you have to select the option 'Hide Incoming Calls' in WidgetLocker settings for calls to work properly. You still have to unlock before answering, though. Unfortunately, that happens when you disable the lockscreen completely. I got used to it now. After unlocking I see the incoming call and have the option to answer or decline.
Definitely better than not being able to answer at all... thanks for that - I'll give that a shot.
That definitely did the trick... honestly that's not a bad feature anyway - decreases the chance of a pocket answer, and an extra swipe is no big deal to me.
What's weird is, in my testing, the other way worked fine as well... i.e. it came up normal before enabling "hide incoming calls". Who knows...

Incoming call - lower half of the screen black

hi there!
just wanted to let you know that, for the last 2 days now, I'm experiencing this weird issue:
http://forums.androidcentral.com/google-nexus-5/334621-problem-half-blank-screen-incoming-calls.html
the lower half of the screen, when I receive an incoming call, is black (this wasn't so in the first 1-2 days). even if the caller has a contact photo, it's shown only like 1/3, the rest is black. this appeared like 2-3 days ago and didn't change after the small update I've succesfully applied.
the device is an 8GB version, bought from Amazon.de.
any1 has this issue? is there a fix to it?
THX!
I have fixed it.
http://forum.xda-developers.com/showthread.php?t=2562126
shaftenberg said:
I have fixed it.
http://forum.xda-developers.com/showthread.php?t=2562126
Click to expand...
Click to collapse
thanks, but I wouldn't want to root my Moto G yet. especially since I'm kinda waiting for the KitKat update.
so, is this a bug, or is it a new "feature" of the later Android versions? because if it's the latter, it kinda sucks bigtime! the example in your other thread (where only the hat can be seen from the contact picture) is a good one for how stupid this is if it's really intended like this.
btw, this changed after 1-2 days of proper usage, I remember the incoming call screen to show the complete contact picture at the beginning, I guess it changed later. would it change if I'd reset the phone, for example?
did a factory reset and unchecked the option to restore settings and apps from the previous phone -- unfortunately, this didn't fix the issue. still, when there's an incoming call, i can only see like 1/3 of the contact picture. the rest of the screen is black...grrrreat!
Man, this is a bug in Phone.apk of Android 4.3 and I fixed it. You need root though if you want to change the apk.
eXelero said:
did a factory reset and unchecked the option to restore settings and apps from the previous phone -- unfortunately, this didn't fix the issue. still, when there's an incoming call, i can only see like 1/3 of the contact picture. the rest of the screen is black...grrrreat!
Click to expand...
Click to collapse
I have just got a Moto G (4.3) myself and noticed for the first time, this new "feature" of having have black or blank screen during an incoming call.
somewhere else I even read someone's reply rationalizing why it was necessary to have a 2/3 black screen, so that the green and red buttons can be easily visible !!
couldn't the designers just added a small black background to the red and green buttons? that would show them clearly !!
anyway,
I installed this HD caller ID app, so now a nice big picture of the contact is seen.
it does run as a service, and though I don't like this, its still better than having to see the hair of my contacts calling me !!
it has many reviews, ratings and downloads, though u might check other similar apps too. or perhaps another dialer app.
https://play.google.com/store/apps/details?id=tw.nicky.HDCallerID
works good enough for me, has some themes where u can change how the green and red buttons show up.

[Q] Lillipop Issues on AT&T Edge

I just received the upgrade to Lollipop last night on my At&t Edge. So far it seems ok for the most part but I found the following issues:
1. UCCW Widgets are disproportionate. They appear to have expanded and now go beyond the borders of the widget. Also the font has changed and is not fixable.
2. I have the LED notification turned off in settings, however it continues to blink blue when new notifications arrive... NOT playing nice with my OCD!!! How can I ensure this stays off???
3. Most annoying- I cannot change the ringtone or notification sounds. When I go to settings>device>sound and notifications>ringtones it brings me to the following path:
/storage/emulated/0/media/audio/notifications. Problem is I have nothing saved in that location and I cannot navigate to where any ringtones are stored.
Any help on how to accomplish this would be greatly appreciated- AT&T firefly is NOT the sound I want coming from my phone!!
UPDATE:
I was able to use ES File Explorer to navigate into my Systems folder and find the ringtones and notifications. I then copies them to the emulated/0/media folder and I can now change the tone. that is annoying, but a work around solution!
Still need to have the stupid LED light turn off!!!
Bluecham said:
I just received the upgrade to Lollipop last night on my At&t Edge. So far it seems ok for the most part but I found the following issues:
1. UCCW Widgets are disproportionate. They appear to have expanded and now go beyond the borders of the widget. Also the font has changed and is not fixable.
2. I have the LED notification turned off in settings, however it continues to blink blue when new notifications arrive... NOT playing nice with my OCD!!! How can I ensure this stays off???
3. Most annoying- I cannot change the ringtone or notification sounds. When I go to settings>device>sound and notifications>ringtones it brings me to the following path:
/storage/emulated/0/media/audio/notifications. Problem is I have nothing saved in that location and I cannot navigate to where any ringtones are stored.
Any help on how to accomplish this would be greatly appreciated- AT&T firefly is NOT the sound I want coming from my phone!!
Click to expand...
Click to collapse
I don't have any direct solution, but since the Note Edge just received the update last night I would suggest seeing if any Note 4 users had the same issue as you. I know a LOT of them are expriencing wild bugs. Unfortunately, it led a lot of people to doing a factory reset, which for many worked and for some it didn't.
In truth, it's not a bad idea to plan for a factory reset when a major Android version is rolled out. So just a thought. Hope someone has a solution for you, or else we'll see Android 5.1 on our device in the next 12 months!
I just got the lollipop update as well. Did a factory reset after backing everything up because I've seen too many people with problems not doing a factory reset. Everything works perfect though for me haven't had any issues so far.
Inkless said:
I just got the lollipop update as well. Did a factory reset after backing everything up because I've seen too many people with problems not doing a factory reset. Everything works perfect though for me haven't had any issues so far.
Click to expand...
Click to collapse
same here. no issues found. just wish they hadn't messed with the way lollipop does the sound. I prefer lollipops priority notifications over Samsung. I see why they did it though. some people can't bother to understand the new system and just want silent, vibrate and ring modes
Just noticed that. What's the difference between the previous silent mode and mute?
Inkless said:
I just got the lollipop update as well. Did a factory reset after backing everything up because I've seen too many people with problems not doing a factory reset. Everything works perfect though for me haven't had any issues so far.
Click to expand...
Click to collapse
All I did was let it boot up the first time, dealt with a few ANR's, and wiped cache from stock recovery. After Google Play Services finally updated, I haven't had a single issue since. I have to say, other than the odd choice of lots of white since we have AMOLED, I am enjoying this update so far :good:
Backed up the phone through Kies and did a factory reset. then restored through Kies. This fixed the ringtone issue. LED still blinks despite being turned off in settings. I am currently going through all my apps to see if one is overriding.
Only other thing I found is the "Briefings" panel is no longer accepting my weather settings and continuously prompts me to "tap to add weather info".
So far I am liking the update and will work through the issues I find! a few odd choices of color, though!
Was finally able to resolve the weather issue on my briefings panel. I had to open the Samsung weather widget and set it to my current location. Once I did that the panel connected and displayed the correct temp.
Bluecham said:
3. Most annoying- I cannot change the ringtone or notification sounds. When I go to settings>device>sound and notifications>ringtones it brings me to the following path:
/storage/emulated/0/media/audio/notifications. Problem is I have nothing saved in that location and I cannot navigate to where any ringtones are stored.
Any help on how to accomplish this would be greatly appreciated- AT&T firefly is NOT the sound I want coming from my phone!!
Click to expand...
Click to collapse
Are you sure you don't have another app controlling this? Check your defaults. Also, /storage/emulated/0/media/audio/notifications is where user notification sounds should go. Ringtones should be in /storage/emulated/0/media/audio/ringtones for user and /system/media/audio/ringtones for system.
jooniloh said:
Are you sure you don't have another app controlling this? Check your defaults. Also, /storage/emulated/0/media/audio/notifications is where user notification sounds should go. Ringtones should be in /storage/emulated/0/media/audio/ringtones for user and /system/media/audio/ringtones for system.
Click to expand...
Click to collapse
Thanks. This was resolved after a factory reset.

Random Notification Sounds?

Maybe someone else can help me with this.
Every so often during the day I keep getting a random notification sound with no visual as to what it is. The sound is 5 tones going in a descending pattern and sounds metallic. I do not have NFC turned on nor the facebook app. I checked all my apps and sounds. I even read a lot of threads else where and tried everyone's suggestion. Still does it. I searched my phone for *.ogg and *.wav files. Nothing.
I do have a wallet case but since NFC is off its not that. I've never heard this sound before. It only started a few days ago and I've have this phone for over a month. FYI I'm running the Hola launcher and omni swipe if that helps. Any suggestions?
I am thinking to uninstall ALL my apps and see if it still does it, but I really dont want to have to do that if I can avoid it.:silly:
Bump
Anyone?
Maybe it's the louncher. .. trai with the touchwiz
Sent from my SM-N915F using XDA Free mobile app
It's not the launcher. It doesn't matter.
This is why I hardly ask anything here. No one cares.
If your not a popular member you never get a reply.
I'll just ask my questions elsewhere where people actually care about you.
Are you using googles smartlock feature? When I first started using it I was receiving this weird notification which sounds like what you're talking about. It don't do it no more for some reason but man was it so annoying not knowing what the heck your phone is trying to tell you.
Sent from my SM-N915P using XDA Free mobile app
Hey there.
I have been checking back on this topic for a while because my wife's Note Edge is having the same exact problem. I even reached out to Samsung Mobile Support and they can't even figure out what it is. All they did was tinker with the sound settings and asked me if it was fixed. I have tried disabling all possible notifications from all possible apps. The only thing left is to do a factory reset it seems. Any luck on your end?
VGMStudios said:
It's not the launcher. It doesn't matter.
This is why I hardly ask anything here. No one cares.
If your not a popular member you never get a reply.
I'll just ask my questions elsewhere where people actually care about you.
Click to expand...
Click to collapse
Well that's not a pessimistic attitude or anything whatsoever! lol. Here's the thing... It might help to try and remember that nobody is on here getting paid to spend their time answering your questions all day long, so unfortunately it's inevitable that there will be times when people might just have to figure their problems out on their own or just be forced to wait until someone responds.. no matter how "popular" they might be.
This entire community wouldn't exist if weren't for all of the people on here who have been and are willing to spend their own free time sharing their knowledge with and helping others, so it's pretty ridiculous to sit there and act like it's a personal assault whenever nobody answers your question right away! From my experience on here people (including myself) are always more than willing to help out whenever they can (as long as the people are willing to help themselves too), but since nobody is getting paid people need to realize that it's more of a "self help" type of community than anything.
There are literally mountains of freely available information for people to search through to try to find their answers with, and with enough determination and persistence 99% of the time people could answer their own questions without ever even having to ask. So I'm definitely not trying to be rude or anything but it's just all in how you look at it.. because when people come here expecting to be handed all of the answers then they're most likely going to be disappointed and upset, but when you come here looking to help yourself instead you'd be surprised how much of a difference it makes and how rarely you'll have to ask any questions.
Anyway I'll try helping with some suggestions below since they're having the same problem too..
Mercodious said:
Hey there.
I have been checking back on this topic for a while because my wife's Note Edge is having the same exact problem. I even reached out to Samsung Mobile Support and they can't even figure out what it is. All they did was tinker with the sound settings and asked me if it was fixed. I have tried disabling all possible notifications from all possible apps. The only thing left is to do a factory reset it seems. Any luck on your end?
Click to expand...
Click to collapse
Ok I've actually had a similar problem in the past and I can't guarantee anything but hopefully this might help..
In my situation it turned out being "profiles" that I didn't realize were turned on, and they were causing rogue and unknown sounds to happen because they were overriding my ringer and media volume settings based on the time of day it was. So all I had to do was turn off the profiles and it solved the problem, but it depends on the rom that you're on as to whether or not profiles like that are even an option.
If not another thing I'd recommend doing (and I'm obviously not sure what all you've tried so I'm just trying to cover the bases just in case) is to get a root explorer (as long as you're rooted.. if not I'm honestly not sure what to tell ya) and navigate to the root folder .. then go to "system/media", and inside there should be a folders called ui, notification, and ringtones.. and this where all of the default notification sounds are located. I would go through and listen to each one of them (they should be .ogg files) and see if you can find a match to the one you're hearing, and if you do then you can just rename that file .bak instead of .ogg and that should stop it from playing randomly (basically a bandaid type fix).
If it's not any of the system sounds then you've basically narrowed it down to where it's most likely an app that's making the sound. If that's the case then what I'd do is go into Titanium Backup and filter it to only show "user apps" and then have it sort them by the date which they were installed, and then I'd just start going down the list looking for apps I've installed that could possibly be making the sound.. that way even if you have a general idea around when the problem started happening you can match that time frame up with apps that were installed around that time to narrow down your search (if that makes sense anyway).
Anyway that's what I would do to start at least and hopefully it helps!
Sent from a ridiculously modified ColecoVision
heh. I have an idea. You know those crappy applications on the edge? Some of them are games. I remember i used to have this issue with the memory one. Remove them from the edge. No root required. Just remove the panels from the panel configurator.
VGMStudios said:
Maybe someone else can help me with this.
Every so often during the day I keep getting a random notification sound with no visual as to what it is. The sound is 5 tones going in a descending pattern and sounds metallic. I do not have NFC turned on nor the facebook app. I checked all my apps and sounds. I even read a lot of threads else where and tried everyone's suggestion. Still does it. I searched my phone for *.ogg and *.wav files. Nothing.
I do have a wallet case but since NFC is off its not that. I've never heard this sound before. It only started a few days ago and I've have this phone for over a month. FYI I'm running the Hola launcher and omni swipe if that helps. Any suggestions?
I am thinking to uninstall ALL my apps and see if it still does it, but I really dont want to have to do that if I can avoid it.:silly:
Click to expand...
Click to collapse
Not sure if this is gonna help you or not. But yesterday I started to getbthe same metallic noises, I only recall 1 change to my settings and that was installing the live wallpaper on the lock screen to show me pictures based in weather and such. And since then every hour or so it makes the sound. Try to find out if you did the same thing.
Random notification sound
I am having a similar problem which has been widely reported but none of the suggested fixes are working for me. The notification tone keeps sounding in a seemingly random way. There is no notification to match the tone. This is not just a beep or random noise. It is the default notification tone. (Skyline for completeness). This happens maybe 5 or 6 times in 24 hours. It has been happening for about 10 days.
I am running Android 8.0.0 (Samsung Experience version 9) on a Galaxy S8. The phone is not rooted.
I have turned off all notifications individually.
I have turned off notifications for the phone.
I have turned off notification reminders (it was never on).
I have turned off NFC and bluetooth.
I have checked under Accessibility settings.
I have uninstalled every app installed in the last 3 weeks.
I can reproduce the NFC and credit card issue but that is a single beep and not what I am talking about.
I have installed 3 different notification log readers (NS Notification, Notif log notification history and Notification Log). None of them show any activity at the times when I am getting the spurious tone.
When I re-enable notifications for Texts, Messenger and WhatsApp, I still receive these as normal.
I recently got a new dual band router and thought maybe the tone was the phone jumping from 2.4 to the 5 Ghz band or vice-versa. It wasn't. I thought it might be the phone jumping from telecoms provider to WiFi. Tested that too and that's not it.
Next step is a factory reset which I am trying to avoid.
I know this is bringing problems to the table, not solutions but this is really bugging me. Any help would be greatly appreciated.

Honor 6x BLN-24-cannot press "allow" for any app.

When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Do you have an special theme activated? Use the standard theme and try again
My 1st question to you is... when the window prompts, do you flag the option "don't ask to me again" or not? Because if yes, the only option avalaible becomes the "deny" one. This mechanism confused me too some time ago, when i wasn't understanding why it was blacked out; Android takes your flag as an "what a bore, just shut up and go **** ya' self leavin' me alone" answer, so it automatically deactivate the possibility to let it pass even one more time. If you didn't checked the flag, i have another question for you. Did you maybe recently made an update OTA, or with an update package found online? If the 2nd answer is what u've done, do a check for being sure that you have updated the phone with the correct package model. (BLN-21, BLN-22, ecc.) If neither this is your case, begin to tell us something more 'bout your phone configuration and start to think to backup your data and do a factory reset for eliminate this weird issue.
For the question of yours about the Nag screen (the splash one, for being clear) at the moment there is nothing that we can do to avoid it to pop out; just skip it pressing immediately the power button, is the best advice that i can do so far
I'll attempt to answer all these at once since I just got home from work. I wouldn't believe rooting the phone would cause this issue, but the problem happened before i unlocked the bootloader so I think that rules that out. I do not use a special theme, but I do use squarehome launcher for my phone, not the standard android launcher. Problem there is, the problem occurs with either launcher being active. And theme wise, I have a 3-d live aquarium for a background (which if turned off and just a static wallpaper, the same behavior occurs). As far as the phone update goes, it was an OTA update from 6 to 7, so still using stock, nothing sideloaded or flashed (yet). My data is all backed up via My backup pro, and doing a full backup with TWRP onto OTG is not a problem. I prefer not throwing in the towel, since setting up squarehome perfectly is a pain in the ass, but if it has to happen, it is better than manually setting permissions for every app that needs them. Not sure what a screenshot would do, think of any app asking for permission to use phone storage, both the allow button and the deny button visible (in white, nothing grey) and allow doesn't respond where deny responds fine. and then i have to go in manually and grant the permission after the fact. I suppose I could just root my phone and give that a whirl, seems some bloatware needs to be removed anyway, and i have the SU sitting on my hard drive already. Thanx for the responses, and let me know what you may have come up with before I just factory reset it which as mentioned, I am dreading doing.
Rommco05 said:
Hi, so you have unlocked bootloader but not rooted? This is maybe problem, you need to have rooted phone if you have unlocked bootloader for fully using phone. Can you post some screeshots?
Click to expand...
Click to collapse
Well, I didn't think that would be the answer, but you, sir were right. I rooted my phone and it seemed to have fixed the problem. I don't believe I made any other change whatsoever. Thank you very much. Glad I tried it anyway as you suggested even though I didn't think it would be the answer. I am not above saying thank you, and I was wrong. Kudos. Maybe this will help someone else. Good thing is, I planned on rooting it anyway, and you just kicked me in the pants to do it.
Rooted but allow button is still not activated
Hello guys,
I wanted to activate app twin so I rooted my phone BLN-L21 android 7.0
Allow button still deactivated.
Also the boot screen that asks to press power button still exist.
I noticed that if I activate whatsapp twin it won't work simultaneously .
I.e : when you open whatsapp you get all missed calles & messeges.
Also I was able to download themes through themes app ,but now it just views the local themes.
Note: superSu is installed.
Any help will be appreciated.
Thank you
Well, I think this is not related to OP (or at least partially), but when unlocking bootloader after setting up SD card as the default storage can break some things, like default themes.
Try to restore your firmware, and then unlock the bootloader.
If successful, you can now set up SD card as default storage.
jackmeat said:
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Click to expand...
Click to collapse
Its happened to me before i just wiped the phone. I even sometimes cant click install when installing an apk unless i lock and unlock the screen.

Categories

Resources