Develop Bugs

[Q] missing pictures

Hi all, i have a odd issue im running fully updated STOCK rom with at&t.
The issue im having is, i have four i guess you call them folders in my gallery, all register x amount of pictures,,
Now the odd part when i open those albums/folders they are all black i get a "unable to load photo" prompt.
also i cannot delete either the photo nor the album i get no option for this. and i cannot locate via usb to computer to see if i can get rid of them from my computer,
can any one help or direct me to location to delete them i dont care what the pics were just anoying to have albums that show nothing!

chinefoo said:
Hi all, i have a odd issue im running fully updated STOCK rom with at&t.
The issue im having is, i have four i guess you call them folders in my gallery, all register x amount of pictures,,
Now the odd part when i open those albums/folders they are all black i get a "unable to load photo" prompt.
also i cannot delete either the photo nor the album i get no option for this. and i cannot locate via usb to computer to see if i can get rid of them from my computer,
can any one help or direct me to location to delete them i dont care what the pics were just anoying to have albums that show nothing!
Click to expand...
Click to collapse
bump

Hey I am getting the same thing did you figure it out?

lpstudio said:
Hey I am getting the same thing did you figure it out?
Click to expand...
Click to collapse
No i have not, im unrooted so i cannot search thru files in order to delete the root directory of these,
i should make a note on this as i think the cause was a app called ANDROID DEFRAG, <--- i recommend staying away from that app.
i tried loading a few of the pics via sharing / open with messaging app and a few showed.
all the details for the pics are there except for ORIENTATION which shows ZERO .
none of these pics show in connection to pc either cannot locate the files, like to edit them to try and make them appear but at this point a way to delete the files would suffice!

[REQUEST] Requesting a call recorder

Hi bros
I need a call recorder for my Samsung Galaxy Nexus running Android 4.2.1. I have tried lots of recording apps but those apps either didn't work or in case of working, had not satisfying quality. I want a call recorder that can record not only my voice but also the voice of my partner too. Some of apps i tried, acted as a voice recorder and recorded the sound of person sitting beside me which i don't like. please help me
Thanks in advance

aligh9 said:
Hi bros
I need a call recorder for my Samsung Galaxy Nexus running Android 4.2.1. I have tried lots of recording apps but those apps either didn't work or in case of working, had not satisfying quality. I want a call recorder that can record not only my voice but also the voice of my partner too. Some of apps i tried, acted as a voice recorder and recorded the sound of person sitting beside me which i don't like. please help me
Thanks in advance
Click to expand...
Click to collapse
Ok, I known exactly what you're saying... I tried TONS of "call recording" apps, that just didn't work as expected.
Today, I still use ICS "4.0.4", but the app is updated regularly, and I've seen some "JB support" in the updated, so it will probably work for you.
First, you NEED a rooted device. This is not a problem for you, right?
Second, you NEED the following apps:
1) AlsaMixer - You can get it free from Google Play.
I really don't understand what this program does, but this program is the key for two-way call recording in Galaxy Nexus.
I think it replaces some audio binaries.. So, open it and ALLOW it to replace your files. You don't need anything else from it, just keep it installed.
2) CallRecorder, from SKVALEX. You can buy it from Google Play, or download from the official XDA thread:
http://forum.xda-developers.com/showpost.php?p=21317161
* I bought it, as he was the ONLY developer who made it working. So, let's buy him a beer.
After you install both, make a call (or answer it).
All calls WILL be recorded by default.
You'll see a "recording" red icon in your screen during the call. You can click that to pause or resume recording.
If your voice, or the other-side voice is not being recorded, than you have to:
1) Open CallRecorder;
2) Click "Preferences" > "Record Calls From"
3) Try all the options. For me, only "Record calls from: ALSA" worked, but other may work for you, depending on your kernel.
After a while, I got a little problem when answering a call. The other side just couldn't hear me.
I fixed it by going to "Preferences > Advanced > Delay before start recording: 0.3 sec".
Let me know if it worked for you.

legalbrr2 said:
Ok, I known exactly what you're saying... I tried TONS of "call recording" apps, that just didn't work as expected.
Today, I still use ICS "4.0.4", but the app is updated regularly, and I've seen some "JB support" in the updated, so it will probably work for you.
First, you NEED a rooted device. This is not a problem for you, right?
Second, you NEED the following apps:
1) AlsaMixer - You can get it free from Google Play.
I really don't understand what this program does, but this program is the key for two-way call recording in Galaxy Nexus.
I think it replaces some audio binaries.. So, open it and ALLOW it to replace your files. You don't need anything else from it, just keep it installed.
2) CallRecorder, from SKVALEX. You can buy it from Google Play, or download from the official XDA thread:
http://forum.xda-developers.com/showpost.php?p=21317161
* I bought it, as he was the ONLY developer who made it working. So, let's buy him a beer.
After you install both, make a call (or answer it).
All calls WILL be recorded by default.
You'll see a "recording" red icon in your screen during the call. You can click that to pause or resume recording.
If your voice, or the other-side voice is not being recorded, than you have to:
1) Open CallRecorder;
2) Click "Preferences" > "Record Calls From"
3) Try all the options. For me, only "Record calls from: ALSA" worked, but other may work for you, depending on your kernel.
After a while, I got a little problem when answering a call. The other side just couldn't hear me.
I fixed it by going to "Preferences > Advanced > Delay before start recording: 0.3 sec".
Let me know if it worked for you.
Click to expand...
Click to collapse
thanks a lot, I'll check this out and post the result here
thanks once more

I use Call Recorder as well, and it works great. I have mine set so that I only record the calls I want, rather than every single one. Extremely handy for when someone is giving you directions and you don't have a pen/paper handy (or while your driving) amongst other uses

thanks dear legalbrr2. you are greatttttttttttttttttttt. it works like a clock!!!! i was looking for the apps like this and i was totally disappointed finding any solution, till today that i got your instructions. Again thanksssssss

Not working for me in 4.3. Rooted, busybox installed and alsa installed.
Keeps crashing. Any idea?

Nemesis_00 said:
Not working for me in 4.3. Rooted, busybox installed and alsa installed.
Keeps crashing. Any idea?
Click to expand...
Click to collapse
Is there any usefull and working tool to record both sides of a phone call?
My phone is still unrooted...

After reinstalling everything, it worked perfectly.
Sent from my HTC One using XDA Premium 4 mobile app

legalbrr2 said:
Ok, I known exactly what you're saying... I tried TONS of "call recording" apps, that just didn't work as expected.
Today, I still use ICS "4.0.4", but the app is updated regularly, and I've seen some "JB support" in the updated, so it will probably work for you.
First, you NEED a rooted device. This is not a problem for you, right?
Second, you NEED the following apps:
1) AlsaMixer - You can get it free from Google Play.
I really don't understand what this program does, but this program is the key for two-way call recording in Galaxy Nexus.
I think it replaces some audio binaries.. So, open it and ALLOW it to replace your files. You don't need anything else from it, just keep it installed.
2) CallRecorder, from SKVALEX. You can buy it from Google Play, or download from the official XDA thread:
http://forum.xda-developers.com/showpost.php?p=21317161
* I bought it, as he was the ONLY developer who made it working. So, let's buy him a beer.
After you install both, make a call (or answer it).
All calls WILL be recorded by default.
You'll see a "recording" red icon in your screen during the call. You can click that to pause or resume recording.
If your voice, or the other-side voice is not being recorded, than you have to:
1) Open CallRecorder;
2) Click "Preferences" > "Record Calls From"
3) Try all the options. For me, only "Record calls from: ALSA" worked, but other may work for you, depending on your kernel.
After a while, I got a little problem when answering a call. The other side just couldn't hear me.
I fixed it by going to "Preferences > Advanced > Delay before start recording: 0.3 sec".
Let me know if it worked for you.
Click to expand...
Click to collapse
Tried a lot of call recording softwares on google play and none of them did the trick for me. Your method gave me a flawless, crisp quality of my call. Thanks a ton!

Great advise
legalbrr2 said:
Ok, I known exactly what you're saying... I tried TONS of "call recording" apps, that just didn't work as expected.
Today, I still use ICS "4.0.4", but the app is updated regularly, and I've seen some "JB support" in the updated, so it will probably work for you.
First, you NEED a rooted device. This is not a problem for you, right?
Second, you NEED the following apps:
1) AlsaMixer - You can get it free from Google Play.
I really don't understand what this program does, but this program is the key for two-way call recording in Galaxy Nexus.
I think it replaces some audio binaries.. So, open it and ALLOW it to replace your files. You don't need anything else from it, just keep it installed.
2) CallRecorder, from SKVALEX. You can buy it from Google Play, or download from the official XDA thread:
http://forum.xda-developers.com/showpost.php?p=21317161
* I bought it, as he was the ONLY developer who made it working. So, let's buy him a beer.
After you install both, make a call (or answer it).
All calls WILL be recorded by default.
You'll see a "recording" red icon in your screen during the call. You can click that to pause or resume recording.
If your voice, or the other-side voice is not being recorded, than you have to:
1) Open CallRecorder;
2) Click "Preferences" > "Record Calls From"
3) Try all the options. For me, only "Record calls from: ALSA" worked, but other may work for you, depending on your kernel.
After a while, I got a little problem when answering a call. The other side just couldn't hear me.
I fixed it by going to "Preferences > Advanced > Delay before start recording: 0.3 sec".
Let me know if it worked for you.
Click to expand...
Click to collapse
Hello. I have a Samsung Galaxy Nexus I9250. All I can say: AlsaMixer and CallRecorder work perfectly together. Clear recorded sound. Good advise, man! Greetings from Romania!

Alexander pointed me to a flashable version of alsamixer that allowed me to install it on CM11:
http://callrecorder.skvalex.com/alsa_update.zip

Is it still working on Android 4.3?
I want to root my phone, if it's still working.

[How To For Sprint] Fix Persistent Voicemail Notification after Flashing New ROM

I recently upgraded to a 4.4 ROM on my Sprint SGS3. After flashing the new ROM and getting settled in to use it, I was unable to get rid of the annoying Sprint voicemail notification. It said I had 7 voicemails.
I've used Google Voice for my voicemail for several years, so I didn't believe that notification was true. But I decided to disable Google Voice and dial in to the Sprint system just to see if anything had ended up in there. It was empty.
Try as I might, nothing would eliminate the voicemail notification, and there was no way to "swipte it away."
Not finding anything related to the SGS3, I ran a site-wide search and came across this thread for the Nexus 5.
I've been a fan of Ghost Commander for a long time, so I used it instead of FX Explorer, which is what PaulB007 (the author of that thread) used. Ghost Commander has a "Root" mode built in, which was required in order for me to successfully navigate to the folder and file mentioned in that thread.
ROOT is required for this fix. But since it happened to me after flashing a new ROM, presumably that's obvious.
On my device, here's what I did:
Step 1. In Ghost Commander, from the "Home" menu, select "Root mode". If prompted, grant Ghost Commander "superuser" privileges (I did this for only 10 minutes to keep myself from bumping something during another session later).
Step 2. Make sure you've navigated to the root:/# location. Select the /data folder. Inside it, select the /data folder again. Ghost Commander should show your current folder as root:/data/data#
Step 3. Tap the "com.android.phone" folder, then find the "shared_prefs" folder. Find the file named "com.android.phone_preferences.xml" and long-press it. Ghost Commander's context menu that appears has an "edit" button which you can press to make edits to the file. That's what I did. If you want to be extra careful, you could "copy" that file and make yourself a backup, which would probably be wise. What can I say? I like to live on the edge sometimes.
Step 4. This is where what I did differed greatly from what PaulB007 did. The file on my device was fairly long, so rather than replace it's entire contents, I located the line that showed the voice mail count. It read:
Code:
<int name="vm_count_key_cdma" value="7" />
Ah ha! The 7 voicemails!
I changed it to read:
Code:
<int name="vm_count_key_cdma" value="0" />
Then I hit the menu button on my device, chose "Save" then hit the back button to return to the folder.
I skipped most of the other steps mentioned by PaulB007, but I did follow his 11th step:
Step 11: go into your notifications on the top of your screen and long press on the voicemail notification. Tap "App Info." Force stop your phone application so that the notification disappears up top.
Click to expand...
Click to collapse
That was as far as I needed to go... the notification disappeared after force stopping the phone app. It has not reappeared!!
A big thanks to PaulB007 for posting the fix on his Nexus 5 device.
As an aside, I don't know if it makes any difference, but the ROM I recently flashed is based on Cyanogenmod. Something similar has happened in the past with some other ROMs, but I've always been able to clear the voicemail notification with typical fixes (rebooting, reconfiguring Google Voice, etc.). This time, it obviously called for more extreme measures.

HaveAnEpiphany said:
I recently upgraded to a 4.4 ROM on my Sprint SGS3. After flashing the new ROM and getting settled in to use it, I was unable to get rid of the annoying Sprint voicemail notification. It said I had 7 voicemails.
I've used Google Voice for my voicemail for several years, so I didn't believe that notification was true. But I decided to disable Google Voice and dial in to the Sprint system just to see if anything had ended up in there. It was empty.
Try as I might, nothing would eliminate the voicemail notification, and there was no way to "swipte it away."
Not finding anything related to the SGS3, I ran a site-wide search and came across this thread for the Nexus 5.
I've been a fan of Ghost Commander for a long time, so I used it instead of FX Explorer, which is what PaulB007 (the author of that thread) used. Ghost Commander has a "Root" mode built in, which was required in order for me to successfully navigate to the folder and file mentioned in that thread.
ROOT is required for this fix. But since it happened to me after flashing a new ROM, presumably that's obvious.
On my device, here's what I did:
Step 1. In Ghost Commander, from the "Home" menu, select "Root mode". If prompted, grant Ghost Commander "superuser" privileges (I did this for only 10 minutes to keep myself from bumping something during another session later).
Step 2. Make sure you've navigated to the root:/# location. Select the /data folder. Inside it, select the /data folder again. Ghost Commander should show your current folder as root:/data/data#
Step 3. Tap the "com.android.phone" folder, then find the "shared_prefs" folder. Find the file named "com.android.phone_preferences.xml" and long-press it. Ghost Commander's context menu that appears has an "edit" button which you can press to make edits to the file. That's what I did. If you want to be extra careful, you could "copy" that file and make yourself a backup, which would probably be wise. What can I say? I like to live on the edge sometimes.
Step 4. This is where what I did differed greatly from what PaulB007 did. The file on my device was fairly long, so rather than replace it's entire contents, I located the line that showed the voice mail count. It read:
Code:
<int name="vm_count_key_cdma" value="7" />
Ah ha! The 7 voicemails!
I changed it to read:
Code:
<int name="vm_count_key_cdma" value="0" />
Then I hit the menu button on my device, chose "Save" then hit the back button to return to the folder.
I skipped most of the other steps mentioned by PaulB007, but I did follow his 11th step:
That was as far as I needed to go... the notification disappeared after force stopping the phone app. It has not reappeared!!
A big thanks to PaulB007 for posting the fix on his Nexus 5 device.
As an aside, I don't know if it makes any difference, but the ROM I recently flashed is based on Cyanogenmod. Something similar has happened in the past with some other ROMs, but I've always been able to clear the voicemail notification with typical fixes (rebooting, reconfiguring Google Voice, etc.). This time, it obviously called for more extreme measures.
Click to expand...
Click to collapse
Hey man, are the settings sticking for you still? My success with this method seems to be ROM dependent and refuses to stick sometimes.

PaulB007 said:
Hey man, are the settings sticking for you still? My success with this method seems to be ROM dependent and refuses to stick sometimes.
Click to expand...
Click to collapse
Edit: seems the "<string name="vm_number_key_cdma">xxxxxxxxxxx</string>" lone is important for the nexus 5 at least. You'll have to let me know if it made any difference for this phone.

PaulB007 said:
Hey man, are the settings sticking for you still? My success with this method seems to be ROM dependent and refuses to stick sometimes.
Click to expand...
Click to collapse
Well... I'm not entirely sure.
Last night I drove out of range of Sprint's network and "hopped" to a roaming network and back. I happened to look at my phone and noticed the same notification: 7 voicemails. So... I checked the file and found that it still showed my edit:
Code:
<int name="vm_count_key_cdma" value="0" />
Weird. I was expecting to have to make that change again.
So I killed the phone app, and the notification cleared.
Drove back home... same drill (hopping to roaming and back). No new notification.
So it's too early to tell what's up. I haven't flashed a new ROM or anything (nor do I plan to for a while)... so I'm taking a "wait and see" approach. Would love to hear anything you might learn, though.

I tried it on CyanFox 4.4 and it didn't work.

Looks like this fix isn't working. The notification keeps returning when hopping to Roaming and on reboots. I had thought perhaps it wasn't related to the ROM, but I'm on CyanFox as well. Time to bring it up over there...
Sent from my SPH-L710 using xda app-developers app

cant seem to get this to work on 4.4.2 ROM Mokee.

Try leaving urself a voice mail from another phone. Then go bak and delete it. It should clear everything up.
Sent from my SPH-L900 using XDA Premium 4 mobile app

SGS3 with CM11
I have the same voicemail notification problem with my GS3 running CM11 and I cannot find the com.android.phone folder anywhere even while running a search with ghost commander or ES File Explorer.

Calling Out

I did a software update two days ago and I just found out this morning that I can no longer call out. What should I try? I Googled and have looked for a Call Barring setting, but I can't find it yet.

Do you get any type of error message? I use Googles's dialer app and the first call I made after the update I tried from contacts and got an error that I didn't have permission. I then opened up the dial pad and got the "allow permission" pop-up. Look at the phone app in Settings>apps and make sure the permissions are on and change system settings is allowed.

Tel864 said:
Do you get any type of error message? I use Googles's dialer app and the first call I made after the update I tried from contacts and got an error that I didn't have permission. I then opened up the dial pad and got the "allow permission" pop-up. Look at the phone app in Settings>apps and make sure the permissions are on and change system settings is allowed.
Click to expand...
Click to collapse
It took a while yesterday morning, but the problem has been solved.
It started with Total Wireless, who is my service provider. To their credit, they had me try some things, but when we got to the point of a complete hard reset. I decided to hold off on that.
I then used Samsung support chat. They eventually has me try the Safe Mode. I didn't even know about that. My S9 called out just fine on Safe Mode. So, I was advised it was being caused by one of my apps. I had just done an Android OS update two days earlier, but I didn't think I had added any new apps recently. I deleted a number of them until I got to Call Confirm. Then it hit me. The behavior of the phone was similar to Call Confirm, except it never asked me to push a Call Confirm button to place the call. I deleted Call Confirm and the problem was solved!
Thank you for the response!

[Bounty $500] My note 10+ was hacked with stalkerware

My phone was infected with stalkerware, they had access to my files, could view what was on my screen, listen into my mic, view my cameras remotely, everything! It's incredibly creepy! From what I can tell they somehow loaded q hacked version of Google Chrome and or android web viewer. After getting suspicious I downloaded Kaspersky and ran a scan, I found 2 versions of Google Chrome on my phone one of them had the dual messenger app icon on it. The other one said it wasn't a current version from the apps store. I Uninstallerd and downloaded the current version through the app store. I tried to see if a packet sniffer would lead me to them but I think I was too late by that point. I also pulled the Chrome app qnd decompiler it. There was some weird things in there like ignore playstore version but nothing that I could find that would lead me to who was watching me. Is there anything I can still do that will lead me to who did this? I have a strong idea of who it was but need evidence so I can prosecute them. Any help would be appreciated. Im putting up a 500 dollar bounty if anyone can help me get some solid evidence.

dangerruss said:
My phone was infected with stalkerware, they had access to my files, could view what was on my screen, listen into my mic, view my cameras remotely, everything! It's incredibly creepy! From what I can tell they somehow loaded q hacked version of Google Chrome and or android web viewer. After getting suspicious I downloaded Kaspersky and ran a scan, I found 2 versions of Google Chrome on my phone one of them had the dual messenger app icon on it. The other one said it wasn't a current version from the apps store. I Uninstallerd and downloaded the current version through the app store. I tried to see if a packet sniffer would lead me to them but I think I was too late by that point. I also pulled the Chrome app qnd decompiler it. There was some weird things in there like ignore playstore version but nothing that I could find that would lead me to who was watching me. Is there anything I can still do that will lead me to who did this? I have a strong idea of who it was but need evidence so I can prosecute them. Any help would be appreciated. Im putting up a 500 dollar bounty if anyone can help me get some solid evidence.
Click to expand...
Click to collapse
Try logging into your Google account from a computer. Look at what devices have access to your account. I looked at mine a couple of months ago and saw a phone I never owned on AT&T. Funny thing is I have NEVER had AT&T. I've always and still have Verizon. I immediately removed, blocked and reported the device.

HyperChick said:
Try logging into your Google account from a computer. Look at what devices have access to your account. I looked at mine a couple of months ago and saw a phone I never owned on AT&T. Funny thing is I have NEVER had AT&T. I've always and still have Verizon. I immediately removed, blocked and reported the device.
Click to expand...
Click to collapse
That was the first thing I tried. Didn't find anything unfortunately. These a holes are good.

dangerruss said:
That was the first thing I tried. Didn't find anything unfortunately. These a holes are good.
Click to expand...
Click to collapse
Did you run a log of your IP addresses?

HyperChick said:
Did you run a log of your IP addresses?
Click to expand...
Click to collapse
Not until after the connection was severed. My first thought was to run a virus scan. The only thing I found was an application was installed feb 1st and the clean version of chrome stopped uploading on Feb 1st.

Why are there two of these? And how did they use dual messenger to install doubles? I've disabled all of them.

dangerruss said:
Not until after the connection was severed. My first thought was to run a virus scan. The only thing I found was an application was installed feb 1st and the clean version of chrome stopped uploading on Feb 1st.
Click to expand...
Click to collapse
Did you delete the corrupt Chrome already? The IP history may be in there...
you wish to find your IP address Internet history, you can easily do so directly from your Internet browser.
Step 1
Open your Internet browser, and click on "Tools" located in the horizontal menu bar at the top of the window.
Step 2
Click on "Internet Options"
Step 3
Click on "Settings" located beneath the "Browsing History" subheading.
Step 4
Click on the "View Files" button to find your IP address Internet history.

If you post the chrome apk that you dumped or anything else that you have that was related to the "infected" files, they might be helpful in looking for clues.

These are the apk files that I suspect could have been infected. Unfortunately I didn't pull them until after they were updated. But I believe there is still a change log kind of manifest if you decompile them.

On mobile? Im not seeing those options
HyperChick said:
Did you delete the corrupt Chrome already? The IP history may be in there...
you wish to find your IP address Internet history, you can easily do so directly from your Internet browser.
Step 1
Open your Internet browser, and click on "Tools" located in the horizontal menu bar at the top of the window.
Step 2
Click on "Internet Options"
Step 3
Click on "Settings" located beneath the "Browsing History" subheading.
Step 4
Click on the "View Files" button to find your IP address Internet history.
Click to expand...
Click to collapse

From what I can see, those apks unfortunately appear to be normal un-tampered files. The manifest I believe you are referring to is a component of the apk that dictates things like permissions and interfaces, but it does not perform any sort of logging or historical record sadly, as the entire apk is replaced when an app is updated or installed over an existing installation.
I am not sure how much cleaning you have done of your device since it happened, but aside from clues or records which might be available from various services you use (finding connected accounts that aren't yours, history of any account activities that weren't initiated by you, etc), your next best bet would probably be to dig through the files on the device in search of anything that shouldn't be there. Hopefully there is still some artifact of the infection which could potentially point towards its origin. I will follow this thread, happy to dig through files in my spare time.

Does anyone know if android keeps a log of installs or qnything in the root folder perhaps?

Isn't there a relation between duplicate app instances and secure folder?

OnnoJ said:
Isn't there a relation between duplicate app instances and secure folder?
Click to expand...
Click to collapse
Yes but I've never set up secure folder. Never felt a need to.

First thing I do is a factory reset (and hope that gets it) and reset the Google password.
Keep that bloody device 100% isolated from your PC and data backup copies including the SD card*. Wipe the SD card in the device before the reload and again after the reload. Do NOT connect the card or phone to your PC before the new load is proven clean. Load data directly to SD card from the PC then to the 10+ just in case.
Try to piece together when and what did it but that is a secondary concern. Consider it a drill.
Better get while the gettings good... that level of being compromised means no time to lose ditching the OS. I most likely wipe the SD card too and use one of the clean data backups I keep for just such an event. Torch all data on the device.
If it gets into your backup data copies you're boned.
OSs are 100% expendable, critical data is not.
*you can scan it with everything on the planet and still miss trojans, tainted jpegs/pngs, etc if no definitions exist yet. Expect multiple hidden infections now and go full nuke.
Isolating the infection to that device is only priority. It's possible the infection(s) are already on one or more backups and/or your PC. That's why it's important to keep multiple time staggered backups on multiple electronically isolated hdds.
I keep a 3 tier backup and my PC is never internet connected.
Keep your head and limit the spread...

dangerruss said:
Why are there two of these? And how did they use dual messenger to install doubles? I've disabled all of them.
Click to expand...
Click to collapse
looks normal to me. Those are typical apps that run when dual account messenger service is used .