Develop Bugs

Phone.apk with call recording..

Edit:
Not working yet.
The phone app will crash when your record is stopped.
Created .3gp files are empty.
See page 2 for logs.
This is "our" Phone.apk modified, not the asian one.
Also tried with the asian libs, but they seem to be the same.
Btw: Who added [Hack] to the title ._. ..

Cool, thanks for your effort. I'll wait for someone to check it out

Fr4gg0r said:
I extracted the Phone.apk from Asian Firmware from samfirmware.com..
and I think it supports the sound recoring we know the asian firmwares have.
Click to expand...
Click to collapse
I too so thought.. but imho that's record videocall

thanks for the effort

I did the same thing with the korean phone.apk (deodex and replace original files). it didn't work either, just FCs.

I still believe the Korean phones have the hardware needed to record phone audio. Until someone gets this to work

According to this thread :
http://forum.xda-developers.com/showpost.php?p=9088397&postcount=32
call recording is allowed by hardware. If there's a developer to a find a solution for it, he'll be taking some of the bounty supercurio was looking for in his months-old thread about sound tweaks, that seems not supported now.
Call recording is a must feature for quite few of us.

I dont believe its disabled in hardware. (expensive solution)
I think its disabled in kernel code. (cheap one)

xan said:
I dont believe its disabled in hardware. (expensive solution)
I think its disabled in kernel code. (cheap one)
Click to expand...
Click to collapse
+1
cheap phones have this function is standard
and 500 € phone, could`t cause harware issue

half of samsungs code consists of appending strings for logging.

need this functions too

Don't want to promise anything, but I'm quite excited at the moment...
At the moment it crashes when saving the record.
Saved .3gp files empty.

continue m8,we do not hurry

maybe the interaction with native driver fails, not sure about it. Hoping it's not.

Posting your log might help.
Heck even dmesg might.

I am willing to donate for this feature if we could get it to work.

Daneshm90 said:
Posting your log might help.
Click to expand...
Click to collapse
yup.
http://pastebin.com/qWwVieX3
It obviously already crashes before hitting "stop":
11-30 14:28:35.801: WARN/audio_input(2821): numOfBytes (0) <= 0.
11-30 14:28:35.801: VERBOSE/AudioRecord(2821): stop
11-30 14:28:35.805: DEBUG/AudioHardwareALSA(2821): Entering AudioStreamInALSA::standby
11-30 14:28:35.813: VERBOSE/AudioRecord(2821): stop
11-30 14:28:39.933: ERROR/imdg81(3109): IsShutDownStarted()
11-30 14:28:39.933: INFO/KeyInputQueue(3109): Input event
11-30 14:28:39.941: DEBUG/InCallScreen(16029): simService - SMS Services
11-30 14:28:39.941: DEBUG/PhoneNumberUtils(16029): ril.ecclist0 112/0,112,911
11-30 14:28:39.941: VERBOSE/WindowManager(3109): Dsptch to Window{48f22dd8 com.android.phone/com.android.phone.InCallScreen paused=false}
Click to expand...
Click to collapse
Edit: Seems to be a native or even hardware problem, so I'm out at this point.
Btw: Samsung called setAudioEncoder and passed 3, whereas the docs only specify 0 and 1, tried both but did not help.
I've attached the apk.

push
asdf

Hi!
call recording on sgh-m100s works different. as you can see in the wm8994 initialization code (wm8994-aries.c).
see: hxxp://forum.xda-developers.com/showthread.php?t=842740
you won't be able to record through the means you specified.
i was able to change the wm8994 code in jpm firmware (latest available on opensource.samsung.com) to the sgh-m100s one to record but video call recording was broken. so that is not the way i prefer.
another interesting class is inside libaudio.so. it's called voicecallrecorder which seems to record through the svnet0 interface (ipc to radio).
it could be an option to write the necessary jni classes for that.
kr
David

Any news yet? It's a good idea if it can be made to work.

[Q] HTC Wimax Manager - ndssGetScanResults() ?

Hi all-
I am relatively new to android development, and the current project I've picked out for myself has proven to be more difficult than I thought it would be.
My goal is to create an app that will tell me about wimax network(s) my phone sees with more detail than you get from the settings application or something. Looking at the WifiManager class in developer.android, it looks like I am looking for the Wimax equivalent to getScanResults() - something that returns the list of networks seen in the last scan.
So after some digging online I found references to a Toggle4G widget that does getSystemService("wimax") to get a WimaxManager object, and uses reflection to get the getWimaxState() and setWimaxState(bool) methods. I used getMethods() on the WimaxManager object, and got a list similar to this one I found on pastebin:
EDIT: new user = unable to post links? Well, here's the pastebin code so you can find it
pastebin: 8ktAtcpm
The method of interest at the moment is ndssGetScanResults(), excerpt from pastebin below:
Code:
I/System.out( 1972): Method Name: ndssGetScanResults
I/System.out( 1972): Parameter Type = [Lcom.sqn.dcc.ScanResult;
Unlike the WifiManager though, it looks like this one takes an array of this ScanResult class instead of returning a list of networks. Not exactly sure how this works. I used java.lang.reflect.array to create an array of ScanResults and invoked the ndssGetScanResults() method, but I dont appear to be getting anything - even when I'm already connected on wimax! Can anyone please explain how to call this method correctly so that it will return what networks the phone sees?
I've searched these forums for ndssGetScanResults and other methods that seemed applicable, but I haven't found anything that appears to answer this question. Any help would be appreciated. Thanks!

[APP][IR][ALPHA] TvTerminator [Testers needed!]

Hi @ all
As already mentioned in the "3rd party ir app" thread, I'm working on a TV-B-GONE like app for the HTC One.
The app should be capable to:
• Sync tv-off-codes with an online database
• Send all known (in database) codes out through IR blaster
• Learn an off code and upload to database for other users
All these features maybe already work, but I can't test it as I don’t have my HTC ONE yet!
So if you wanna try, download it from and here and give me some feedback in the thread
• There is a good chance that the app doesn’t even start – I can't test any of the IR blaster related functions! – That’s why I need you until I get my phone :laugh:
• The app sends bug reports to me using bugsense – you can disable this feature in the options if you don't want to send reports! If you disable and get an force close -> please send me the logcat
• The database view is not fully implemented, you can list vendors and search for models but if you click on vendor / model nothing will happen
• Database sync on startup can be disabled in settings
• The Database is EMPTY now(except of one vendor), so don’t wonder if nothings getting synced
Used permissions:
• INTERNET -> For online syncing
• ACCESS_NETWORK_STATE -> To pre-check if sync is possible (not in flight mode)
Future:
• Making the app fully work.
• Making a universal remote app with database sync. So any user can scan his codes (not only power off codes), tag them, create remote layouts, upload schemes for a device, etc. Usable for any IR device (tv, hifi, Roomba, etc)
Changelog
(04.05.2013) Version 0.5:
• old IR blaster control
• send code when click on model name in model search box
(03.05.2013) Version 0.5:
• debug toasts
• new IR blaster control
• send all codes on main thread
(03.05.2013) Version 0.4:
• Bugfix where local recorded codes were not sent out
• Removed test buttons
• Learn-Timeout can be adjust in app settings
(03.05.2013) Version 0.3:
• New Send command used, maybe works now with "all off"
• Some test buttons to debug
(02.05.2013) Version 0.2:
• New Code format (sorry, had to purge the whole database). Old Version will not work anymore.
• Some Bugfixes
• Update check on startup
Download link of version 0.6
http://goo.gl/sjXzi

I'll take the plunge
Will let you know how it goes.

Theres already a new entry for a "dreambox" so recording codes (can) work.
Thx for trying!

antifish said:
Theres already a new entry for a "dreambox" so recording codes (can) work.
Thx for trying!
Click to expand...
Click to collapse
Ok. So given her a spin.
nothing happened lol.
installed fine. I have a LG tv and a virgin TiVo digital box (made by Cisco)
when you go to the search box, enter just moves down to the next line. it doesn't "enter" if that makes sense.
See attached pics anyway.
Hope it helps.

Thanks for the info.
That was excepted - you see vendors "sony" (dummy vendor by me) and vendor "" (empty, ill catch that in the next version) which someone who uploaded a code for a dreambox. As mentioned before, database view is not fully implemeted, you only see vendors ("Sony" and "") and models("dreambox") which other ussrr uploaded until now. Please try recording an offcode for one of your devices

Cool.
Sorry, I must of originally miss understood. Thought you had just added Dreambox to the list of others.
Ill keep an eye out for when you add LG on there
Keep up the good work though. What exactly is the end purpose of the app?
From what I can see, it would be a perfect app for me to prank friends and family whilst at home messing with the TV "quickly" instead of going through setting up the tv first.
:victory:

Downloaded.
Was going to try with the TV at my office but its LG also.
Ill test at home with a Samsung and a Panny.

Hi and thanks for this app, i was able to learn 2 codes, it turned off my TVs when using "Test Code (ir)" button before uploading, but once uploaded (the Panasonic one and a Samsung one are mines) i can't use "all off!" command, i'm still stuck at "Sending codes : 4/10" and then it FC ...
Maybe you could add a tool to try code from database (when pushing on a brand name, sending all codes for this brand) and to avoid duplicates ...
ps : sorry for my english

snowblind2142 said:
Cool.
Sorry, I must of originally miss understood. Thought you had just added Dreambox to the list of others.
Ill keep an eye out for when you add LG on there
Keep up the good work though. What exactly is the end purpose of the app?
From what I can see, it would be a perfect app for me to prank friends and family whilst at home messing with the TV "quickly" instead of going through setting up the tv first.
:victory:
Click to expand...
Click to collapse
michael.s.under said:
Downloaded.
Was going to try with the TV at my office but its LG also.
Ill test at home with a Samsung and a Panny.
Click to expand...
Click to collapse
scarabe17 said:
Hi and thanks for this app, i was able to learn 2 codes, it turned off my TVs when using "Test Code (ir)" button before uploading, but once uploaded (the Panasonic one and a Samsung one are mines) i can't use "all off!" command, i'm still stuck at "Sending codes : 4/10" and then it FC ...
Maybe you could add a tool to try code from database (when pushing on a brand name, sending all codes for this brand) and to avoid duplicates ...
ps : sorry for my english
Click to expand...
Click to collapse
Thanks guys for downloading and testing.
I think there is a little misunderstanding here -> i dont add vendors or devices or codes (at least not until i get my HTC ONE finally).
Its you, the useres, which upload codes. If you enter a model or a vendor which is unknown for the database, it will be created and then usable for everybody else.
@scarabe17
Thanks for the feedback. The force closes is becasue there are some wrong ir codes (data is invalid) in the database from failed uploads. will be fixed in the next version.
I have a lot of ideas what to implement in the app, and as mentioned before, the "tv-b-gone" functionalty (send all known off-codes) will be only a "special function".
The end purpose is an universal IR remote app, with community driven code uploads for all kind of devices and codes (not only power off).
There will be a "layout editor" where you can create your own layout with custom buttoms mapped to custom functions, and you will can share that with other users.
regards
antifish

This will be something cool

Please note, there is version 0.2 now!
Dont use 0.1 anymore, new codes will not work and upload will not be possible!
I had to purge the whole database (sorry to you who already uploaded a code) the format in database was a bad choice.
(details: i used java objectwriterstream to serialize the IR data, and if HTC will change something in that class it cant be serialized back without some trouble, so i changed to a json format)
also there should (hopefully) be less force closses.
and there is a check for updates, so you will notice when i upload the next version

uploaded my panasoic tv model
would be nice here to keep an update of model list cause apps, only show sony.
Also you should add a Vol + button cause at the end its more annoying in shops to set volume to the max than turn tv off

nocomp said:
uploaded my panasoic tv model
would be nice here to keep an update of model list cause apps, only show sony.
Also you should add a Vol + button cause at the end its more annoying in shops to set volume to the max than turn tv off
Click to expand...
Click to collapse
Thanks for the upload!
Can you please sync the database (with the sync icon in the actionbar). At least the Panasonic should apper now, as you uploaded it!
(Sony + Pansonic are the only two venors in the database now)

db synced, model showing, but not working.
you should apply for htc ir api for get codes, cause if you fill the db only with ppl having a htc one member of xda, i doubt you ll reach 50 models

Tried to learn my LG Remote. Got 3 different error-messages.
"Out of Frequ"
"Timeout"
and something with "Pulse"

nocomp said:
db synced, model showing, but not working.
you should apply for htc ir api for get codes, cause if you fill the db only with ppl having a htc one member of xda, i doubt you ll reach 50 models
Click to expand...
Click to collapse
what do you mean with "not working"? The database view actually does nothing when clicking on a model or vendor, thats not integrated yet. The only thing which should happen is that when you press "all off" it should turn off your tv :fingers-crossed:
I have the HTC IR API but it does not provide access to the integrated code database (or i don't know how). I'll decompile a ROM to look after the codes when i have time, maybe i find something! Its no easy to try these things as i dont have a HTC ONE at the moment (still waiting)...
I hope that the next HTC models will all have the IR blaster integrated! And when the app is ready i hope that it gets more response and codes in the play store.
When i got time and be in the mood i'll have a look at the galaxy S4, as it have an IR blaster integrated too, and it would be nice to have an app that support every pontetial model.

s60mike said:
Tried to learn my LG Remote. Got 3 different error-messages.
"Out of Frequ"
"Timeout"
and something with "Pulse"
Click to expand...
Click to collapse
how often did you tried to learn the code?
I'll make the timeout variable in the next version.
Maybe it works better in a darker room?

Ola, lemme know if i can help
When i say not working, it means my tv doesnt turn off
Envoyé depuis mon HTC One avec Tapatalk

nocomp said:
Ola, lemme know if i can help
When i say not working, it means my tv doesnt turn off
Envoyé depuis mon HTC One avec Tapatalk
Click to expand...
Click to collapse
Okay, maybe the data is corrupt (in the database), the scanning of the IR code is not as good on the ONE
as desired, or there is a bug in sending the codes.
Can you please learn the code 2..3 times again? I'll can compare the data then and see if the scanned data is
always the same

Oki i ll try
Envoyé depuis mon HTC One avec Tapatalk

[Q] Tap triggers swipe (aka sensitive screen)

Some people over at the fairphone.com forum reported a "sensitive" screen. They try to tap on a button (or link) and instead of triggering the button the fairphone starts scrolling. My fairphone also shows this behavior and I tried to find out why. Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
So I enabled the "pointer position" option within the developer tools and shot two screen shots. In the first screenshot I tap for round about 500ms whereas in the second screenshot I tried to tap as short a possible. Like you would click with mouse. It show the error pretty obvious. Any ideas how to adjust that?

Hello
I noticed exactly this behaviour on my Fairphone, too.
That's why I started a thread on the official Fairphone website 22 days ago.
I'm not allowed to post direct links here, so I can give you only the head line here:
"Hyper-sensitive-touchscreen"
And on german Fairphone Freunde forum there's also a thread about this problem
Key-Word:
"Empfindlichkeit-des-Touchscreen"
So far, there is not very much response on these threads, but it seems that not all the handsets are affected, because not all of the answers confirmed the problems. One of the guys on fairphone website sent a request to the support team, a few days ago. Maybe he can forward the answer he gets... I'll ask him in his own fairphone thread - "Sensibility-and-reboots"
Unfortunately my phone broke after just one day, so I'm waiting for a replacement now and can't really offer a solution here...
But during the few hours, my phone worked, I entered the engineering mode (by typing *#*#3646633#*#* in the standard dialler app) and there were many options to manipulate the tuochscreen.
Maybe the more experienced guys here in the forum can work out a solution to solve the problem?!
Thank you in advance!

I have the same "hypersensitive screen" issue
Before I was used to briefly and lightly tapping/touching the screen, but with my Fairphone that often gives a scroll signal.
My developer crosshair option shows short lines, the touchpanel behaves as if I first tapped a few centimers away and then a split second later it registers where I actually touched the screen.
I had to learn to firmly tap and hold, otherwise I couldn't select anything on the screen.
It seems a sofware patch for the touchpanel is needed.
-----------------------------------------------
Fairphone FP1
Caju (v.1.1)

Touchscreen settings
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.

boondiordna said:
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.
Click to expand...
Click to collapse
I already put a link on fairphone.com to this XDA thread. Thanks for telling! Well, my settings looks identical to yours. I also played around with them. I have no idea if touch screens nowadays need deboucing or sth like that. So I changed these settings a bit...without improvement though. I am also wondering what tpd_em_log is. It is put to 0. I put it to 1 hoping there is some log written somewhere....but i could not find where unfortunately.

Hey there,
I have the same problem and no solution. But here is my input on that issue. Maybe it helps Fairphone when they investigate that issue, maybe not.
hanzano said:
Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
Click to expand...
Click to collapse
I realized the same thing. BUT in addition, I figured out that it has also something to do with how soft you touch. If I try and touch my screen very very gently, I can reconstruct that behaviour every time. If I press a bit harder, it works better.
I attached a screenshot where I did soft touches, and you see a lot of wiggeling especially in the botom row

Yesterday I was annoyed by this issue. I was a bit in a hurry and the Fairphone touchscreen did not react properly
So I just debugged in Android Studio and this is what I logged:
Code:
12:07:48.874 MotionEvent.ACTION_DOWN: 300.44363, 485.4943
12:07:48.886 MotionEvent.ACTION_MOVE: 293.13342, 499.09888
12:07:48.901 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
...
12:07:49.168 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
12:07:49.183 MotionEvent.ACTION_MOVE: 291.2037, 497.48178
12:07:49.198 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
...
12:07:49.403 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
12:07:49.406 MotionEvent.ACTION_UP: 290.46213, 497.48178
12:07:49.406 event.getDownTime: 566
I tapped for 566ms. Pretty obvious that from ACTION_DOWN to the first ACTION_MOVE there is a big delta of ~14px (is it really pixel?) in y-direction.

Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.

I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.

Hyst said:
Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.
Click to expand...
Click to collapse
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
laufersteppenwolf said:
I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.
Click to expand...
Click to collapse
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.

hanzano said:
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.
Click to expand...
Click to collapse
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?

hanzano said:
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
Click to expand...
Click to collapse
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.

Hyst said:
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.
Click to expand...
Click to collapse
That looks much better than beforehand. I believe the red lines are not of interest. These just seem to be estimations. I had a look into Android source code com.android.internal.widget.PointerLocationView. The VelocityTracker has an Estimator which is drawn in light red. The MediaTek development tool seems to do it similar. So I would only count the green lines.
But I still think that this is not perfect either. I checked with my old Samsung Galaxy Ace and the Android location pointer which really gives points, no line at all when tapping shortly.

laufersteppenwolf said:
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?
Click to expand...
Click to collapse
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.

hanzano said:
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.
Click to expand...
Click to collapse
Sorry for the late answer, haven't seen you post
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers. in there are several drivers, you then need to find the correct one (in my case it's THIS file). In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned

laufersteppenwolf said:
Sorry for the late answer, haven't seen you post
Click to expand...
Click to collapse
No prob
laufersteppenwolf said:
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers.
Click to expand...
Click to collapse
Ah ok, got it. In folder alps >> kernel >> drivers >> input >> touchscreen there are 68 files.
laufersteppenwolf said:
in there are several drivers, you then need to find the correct one (in my case it's THIS file).
Click to expand...
Click to collapse
Did you forget the link on "THIS" probably?
laufersteppenwolf said:
In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned
Click to expand...
Click to collapse
Vielen Dank! Helps a lot

hanzano said:
Did you forget the link on "THIS" probably?
Click to expand...
Click to collapse
Ooops yeah, I did So HERE you go

Hello @Hyst
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
But, as I'm working abroad, its not that easy for me, to send it soon.
That's why I suggested, they should ask you, to get the IMEI of your old device - as you offered in the general thread.
Unfortunately Rick de Groot (the support guy) asked me again, to ask you for this number...
A little bit strange, but this is what I want to do now
Can you please send your old IMEI number and the RMA (repair form number) to this email:
<[email protected]>
That would be really great!
PS:
My Name is Florian W. if you want to quote me in your email.
Maybe this helps them to relate your email to my support request.
Thank you in advance!
Holzwurm86

Hi @Holzwurm86
sure thing. I've just send them an email.

Holzwurm86 said:
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
Click to expand...
Click to collapse
Good to see that there is still progress. The list of phones being affected gets bigger at the fairphone.com forum. If the engineers from Kwamecorp or Changhong need help like debugging or logging touches I am willing to help of course.

Where is the Samsung FM Radio App called "Radio"?

Hi everyone,
I just bought this phone and tried it out in Staples (Canada) and even tested the FM Radio app called "Radio" from Samsung.
Sure enough, after buying it, there is no native Samsung Radio App. I called Samsung and did the online chat, and they said they haven't released it, but clearly, they deploy it when the put the phones in "Demo Retail Mode" in the stores, but not when you are using the phone!
I tried downloading many version from https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-radio/ but all say "Can't install App" when trying to install the APK.
Does anybody know how to get this app? NextRadio works, but their app keeps losing features and won't let me auto-scan.
Thank you!!

whatever69 said:
Hi everyone,
I just bought this phone and tried it out in Staples (Canada) and even tested the FM Radio app called "Radio" from Samsung.
Sure enough, after buying it, there is no native Samsung Radio App. I called Samsung and did the online chat, and they said they haven't released it, but clearly, they deploy it when the put the phones in "Demo Retail Mode" in the stores, but not when you are using the phone!
I tried downloading many version from https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-radio/ but all say "Can't install App" when trying to install the APK.
Does anybody know how to get this app? NextRadio works, but their app keeps losing features and won't let me auto-scan.
Thank you!!
Click to expand...
Click to collapse
The specific error I get from adb is:
a50:/ $ pm install -r --user 0 /data/local/tmp/radio/radio.apk
Failure [-3001]
I've tried so many combinations and it always comes back with that Failure [-3001] error

Radio App is available in A50 indian version out of box.see attachment

:good:

Looks like they removed it from the North American version. Can any of you upload the apk?

Have you ever thought about that the North American SKU doesn't have hardware to make it work?

madd0g said:
Have you ever thought about that the North American SKU doesn't have hardware to make it work?
Click to expand...
Click to collapse
The hardware is there. I can install NextRadio and listen to FM. It's just that the only app I can get is NextRadio, and it's missing RDS and auto scan, which the Samsung Radio app has.
I contacted Samsung by chat and they said they are not releasing it, even though I have FM on the phone, and the store that had the demo phone that I used had it! Talk about bait and switch.

Ugh. I think you're onto something @madd0g
Just got this reply from Samsung:
Alexa at 20:18, Aug 23:
Samsung always considers customers feedback while releasing further updates.
Alexa at 20:19, Aug 23:
For any Samsung Canadian devices, the FM option is not available.
Alexa at 20:19, Aug 23:
Hope you understand.
But I can actually still use the FM radio. Samsung is not being nice here!

So it looks like a signing thing. Probably need root to install it:
08-23 20:42:06.293 4453 4527 D PackageManager: START INSTALL PACKAGE: observer{17944267}
08-23 20:42:06.293 4453 4527 D PackageManager: stagedDir{/data/app/vmdl911232079.tmp}
08-23 20:42:06.293 4453 4527 D PackageManager: stagedCid{null}
08-23 20:42:06.293 4453 4527 D PackageManager: Request from{null}
08-23 20:42:06.293 4453 4527 D PackageManager: VerificationInfo{,originatingUid=-1,installerUid=2000}
08-23 20:42:06.652 4453 4499 D PackageManager: EAS IT Policy com.sec.android.app.fm isPackageSignedByPlatform = false
08-23 20:42:06.657 4453 4499 I PackageManager: EAS IT Policy AllowList = ,,
08-23 20:42:06.657 4453 4499 I PackageManager: isAppBlockedByDPM?? = false
08-23 20:42:06.880 4453 4499 D PackageManager: sendBroadcastAsUser. PACKAGE_INSTALL_STARTED
08-23 20:42:06.883 4453 4499 D PackageManager: EAS IT Policy com.sec.android.app.fm isPackageSignedByPlatform = false
08-23 20:42:06.905 4453 4499 W PackageManager: verifying app can be installed or not
08-23 20:42:07.558 4453 4499 D PackageManager: result of install: -3001{17944267}

Yeah, it might be that the hardware could be there, but they deliberately blocked it from just sideloading it, probably because they need to pay some special royalties or **** like that.

In Slovakia (Central Europe) also without radio.

My European A50 (Dutch - A505FNXXU2ASH1) also has the Radio app.

Czech Republic A505FNXXU2ASH1 item Radio is present and working.

Radio apk from my A505F

Download NextRadio and it should work!!!
Hey guys and gals, I registered after reading this thread. The FM radio hardware is in fact present even though Samsung says its not. I have a Canadian Galaxy A50 purchased from staples, model SM-A505W. There is no pre-installed radio app on the phone. Even though I can not install the Samsung Radio APK attached in this thread, I was able to use NextRadio (free on the app store), and tune into my local stations directly without the internet. So don't listen to Samsung, go ahead and download NextRadio, you will be happy you did. I'm sure there is other FM tuner apps out there, but NextRadio was simple to use, and you can even output the radio to the phone speaker while the headphones are connected, so you can all listen. This will be so useful on canoe trips.
Hope this helps!

Thanks it works well without data or wifi on.

yamen_tn said:
Radio apk from my A505F
Click to expand...
Click to collapse
!WARNING!
DON'T click on the above '[Click for QR Code]' separate link to the right of the separate 'HybridRadio_P.apk' link posted above by 'yamen_tn' in Post #14 because it first displays a QR Code that when you scan the QR Code with your phone it takes you to a website that asks you to create a new account and then says that it needs your credit card information for verification purposes and says it won't charge your credit card, but then the company/website makes a fraudulent charge to your credit card!!! NOT COOL!!!
XDA Developer website Moderator please remove this link ASAP!

tech_dude said:
!WARNING!
DON'T click on the above '[Click for QR Code]' separate link to the right of the separate 'HybridRadio_P.apk' link posted above by 'yamen_tn' in Post #14 because it first displays a QR Code that when you scan the QR Code with your phone it takes you to a website that asks you to create a new account and then says that it needs your credit card information for verification purposes and says it won't charge your credit card, but then the company/website makes a fraudulent charge to your credit card!!! NOT COOL!!!
XDA Developer website Moderator please remove this link ASAP!
Click to expand...
Click to collapse
the file is an attachment so its uploaded to xda servers and it was safely downloaded more then 500 times. the problem is just in your side. try using an other browser

A505FN (Poland) radio app is present.

Any solutions yet?
still can't install the official sumsang radio app,
Snapdragon US version Galaxy S10 plus.
Does anybody have a solution?...not a third party app.