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.
Related
I'm using Sabsa Prime(ICS) and Movie app is still not open.. on my devices.
(Friends have Galaxy S3, S2, and Nexus downloaded that from Android Market without any obstacles)
https://play.google.com/store/apps/details?id=com.google.android.videos
forcibly open that link on DHD(on Search it doesn't appear), it still says incompatible.
it's weird.. Evo 4G+ user review exists. Nexus S user also does. but DHD.
However, that's fine. I got an apk. installed 2.1.9(October 3, 2012) to watch a movie I bought.
After allowing access to my Google Account, movies I bought listed on app.
I pushed play button loading a while then ended with crap; It just says "Couldn't fetch license. ( 43 )"
Googled there's a problem with rooted device so I unroot it.
Disabled Root SuperSU and reboot : "Couldn't fetch license. ( 43 )"
Clean Unroot and reboot : "Couldn't fetch license. ( 43 )"
Anybody watching videos Google Play Movie on DHD without problems?
=================================================================
AtomosVE said:
spoof my device as Galaxy S2,
Replaced some library files from Desire X 1.14. get it work. flash attachment.
But its temporary solution still Errors pops up sometimes might be by a ad-blocker. try much times it works.
also, not lost rt. Busybox 1.20.2-stericson
when activity turns out OR phone rings..
have to Uninstall Google Play Movies and install it from market again.
while it is playing
Plays VERY SMOOOOOOOTH and SOUND is NICE to watch in compact screen:laugh:
Click to expand...
Click to collapse
It is still marked as incompatible by Google so You have to spoof yours as Galaxy S2 to install app from market(have apk you'll be fine) and to open Movie category in Market.
There's one problem is you have to uninstall then re-install(from apk file, Market saying incompatible and.. Google Movie App doesn't have button "Clear Data" on App info) to watch movie.
Watch it from first is MUST. otherwise, "There was a problem while playing" or Error 31
Adblock? seems they aren't affected.
Try using Lucky Patcher and remove license checking from the app.
You need root for the app though.
- hit my thanks button if i helped you -
I have a way. I dunno this moderate way will work but I'll try it.
hukel56 said:
Try using Lucky Patcher and remove license checking from the app.
You need root for the app though.
- hit my thanks button if i helped you -
Click to expand...
Click to collapse
maybe an app's license problem..?
I have a way before lucky patcher.....getting help of friend by using their phone. I'll try it later.
did try it, but it won't work.
hukel56 said:
Try using Lucky Patcher and remove license checking from the app.
You need root for the app though.
- hit my thanks button if i helped you -
Click to expand...
Click to collapse
On Galaxy S2, working very fine AND can watch movie OR pin it.
On DHD, still error 43. Why this happens.??
Google Play Movie minimum requires is Froyo.
DHD have GingerBread officially, and have WVGA screen as SGS2!
+YouTube HQ works very fine. (no HD and it is same on SGS2).
also, found new user review from SGS1, says "Why could not get license."
from users have Galaxy Note 1, Optimus LTE 1 said the same.
seems Google Play Movie REALLY ONLY WORKS ON GalaxyNexus or newer Nexus or Galaxy S2, S3.
Try deleting data and cache for the app. Check the sd storage for folders beginning with a dot, example .android secure etc. And delete any that might be related to the issue, the app will recreate the folder after you delete it.
Sent from my HTC One X using xda app-developers app
still 43.
c5satellite2 said:
Try deleting data and cache for the app. Check the sd storage for folders beginning with a dot, example .android secure etc. And delete any that might be related to the issue, the app will recreate the folder after you delete it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
deleted /mnt/sdcard/Android/data/com.google.android.video and com.google.android.video. then I force closed it.
There was a button "Manage Spaces", instead "Delete Data". so I uninstalled it and installed it again.
It re-loads my purchased movies list and I allowed its access, but still 43.
-------------------------------------------------------------------
There is a Market button on Action Bar. However, it doesn't open "Movies",
just opens Market home after few 'loading's and gray-outs.
(Apps, Books, and Movies are available in my country. not music, magazines yet.)
I forgot, no Movies in Android Market home on my device. (both on 3.8.17 and 3.9.16)
Checking user reviews frequently,
found Wildfire S(positive user review) can watch Movies.
Evo 4G, Sensation 4G also reported not working.
I think this app and actions Google taken are just crap.
Missing, incomplete or broken drm files in custom roms seem to be the culprit. Rooted devices do work, google lifted the restriction earlier this year. Try disabling any adblockers and restore a real hosts file, should only contain 1 entry 127.0.0.1 localhost. Might be blocking the license server. If it is still broken then the rom is the issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
c5satellite2 said:
Missing, incomplete or broken drm files in custom roms seem to be the culprit. Rooted devices do work, google lifted the restriction earlier this year. Try disabling any adblockers and restore a real hosts file, should only contain 1 entry 127.0.0.1 localhost. Might be blocking the license server. If it is still broken then the rom is the issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
10 days ago from you replied to me, I have figured out with other conditions (including you recommended) concluded not to pay Google for Playable things.
(wrote in CAPS.. Sorry this makes me no way out)
NEITHER
Busybox 1.18.0 and 1.20.2-Stericson installed
ROOTed and UNrooted
WITH and withOUT Ad-Blocker (real host file with entry 127.0.0.1 localhost only)
on Sabsa Prime(4.0~8.0) and Stock Gingerbread ROM-3.13.1010.2
CAN PLAY MOVIE. It's just saying 43.
First of all, DHD has been set incompatible by Google on Android Market.
Maybe this is a Huge Point. I have no idea Why Google did this. even it's not 720p, 1080p. Same as Youtube HQ, 360p on mobile or 480p Web.
If your phone has root, you change change the string that identifies the phone to the identifier of another phone and try that. I think it is in the config file, but not 100% on that.
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
If your phone has root, you change change the string that identifies the phone to the identifier of another phone and try that. I think it is in the config file, but not 100% on that.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
changed and recognizes Samsung Galaxy S2.
Google Play Movie downloadable. & Movies category is OPEN on my device. :fingerscrossed:
Another Error came out:
Playback isn't supported on this device.
10-24 19:43:49.240: D/OpenGLRenderer(8549): Flushing caches (mode 0)
10-24 19:43:49.290: I/Adreno200-EGLSUB(8549): <ConfigWindowMatch:2078>: Format RGBA_8888.
10-24 19:43:49.330: D/OpenGLRenderer(8549): Flushing caches (mode 0)
10-24 19:43:49.330: D/memalloc(8549): /dev/pmem: Unmapping buffer base:0x54895000 size:6144000 offset:4608000
10-24 19:43:49.340: D/memalloc(8549): /dev/pmem: Unmapping buffer base:0x5704b000 size:13844480 offset:12308480
10-24 19:43:49.340: D/memalloc(8549): /dev/pmem: Unmapping buffer base:0x57e1a000 size:15380480 offset:13844480
10-24 19:43:49.440: I/dalvikvm(8549): Jit: resizing JitTable from 4096 to 8192
10-24 19:43:52.133: D/L(8549): youtube.core.player.SubtitleHelper.init:134 initializing to en
10-24 19:43:52.143: W/ApplicationContext(8549): Unable to create external files directory
10-24 19:43:52.143: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:395 infoType=3 mimeType=video/wvm
10-24 19:43:52.143: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVStreamIDKey=[OMITTED]
10-24 19:43:52.143: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVDRMServerKey=https://play.google.com/video/license/GetEMMs.cgi
10-24 19:43:52.153: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVPortalKey=YouTube
10-24 19:43:52.153: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVDeviceIDKey=[OMITTED]
10-24 19:43:52.153: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVAssetURIKey=[OMITTED]
10-24 19:43:52.153: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVLicenseTypeKey=[OMITTED]
10-24 19:43:52.153: I/L(8549): youtube.videos.drm.DrmManagerV12.logDrmInfoRequest:398 WVCAUserDataKey=[OMITTED]
10-24 19:43:52.984: W/ApplicationContext(8549): Unable to create external files directory
10-24 19:43:53.965: D/dalvikvm(8549): GC_CONCURRENT freed 1519K, 22% free 5828K/7459K, paused 3ms+11ms
10-24 19:43:56.127: E/OEMCrypto(1391): OEMCrypto_GetRandom(), Can't open device htcdrm
10-24 19:43:58.659: E/L(8549): youtube.videos.drm.DrmManagerV12.onError:321 DRM error PROCESS_DRM_INFO_FAILED 324 [OMITTED]
10-24 19:43:58.659: E/L(8549): youtube.videos.drm.DrmManagerV12.onError:321 DRM error PROCESS_DRM_INFO_FAILED 324
10-24 19:43:58.669: E/L(8549): youtube.videos.drm.DrmManagerV12.onError:326 DrmInfo missing from DrmEvent [email protected]
10-24 19:43:58.669: D/L(8549): youtube.core.client.DefaultAnalyticsClient.trackEvent:126 event [version=2.1.9, action=PlayErrorDrm, label=invalid license status INVALID_KEYBOX_SYSTEM_ID(44), value=-1]
Click to expand...
Click to collapse
might it's due to HTC's own DRM management? I can't use HTC Watch.(in my country)
Made it WORK!!!!!!
spoof my device as Galaxy S2,
Replaced some library files from Desire X 1.14. get it work. flash attachment.
But its temporary solution still Errors pops up sometimes might be by a ad-blocker. try much times it works.
also, not lost rt. Busybox 1.20.2-stericson
There was a Problem while playing. [31]
There was a Problem while playing.
Click to expand...
Click to collapse
when activity turns out OR phone rings..
have to Uninstall Google Play Movies and install it from market again.
while it is playing
Plays VERY SMOOOOOOOTH and SOUND is NICE to watch in compact screen:laugh:
-------------------------------------------------------
Is this safe from apk sharing restriction?
it's available for some devices and country but, it is basically FREE to install.
Hi all,
i've got an odd issue and wonder if somebody else has this.
I'm on pabx' AOSP ROM rc19.
When using Voice Search in Google Now it works the first time. After switching to another app and returning Voice Search fails with something like "Could not be understood". It fails immediately and doesn't even try to record anything.
PLUS: at this point voice recording fails in any app (e.g android voice input / swiftkey, what so ever).
when i force kill Google Search App, everything works again. so this somehow seems to block voice input.
maybe someone can reproduce this..
here's my logcat..
Code:
W/AudioFlinger( 193): findSuitableHwDev_l() loading well know audio hw modules
W/AudioFlinger( 193): loadHwModule() module primary already loaded
W/AudioFlinger( 193): loadHwModule() module a2dp already loaded
E/AudioFlinger( 193): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 193): loadHwModule() error -2 loading module usb
E/AudioRecord(10035): Could not get audio input for record source 6
E/AudioRecord-JNI(10035): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java(10035): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
D/dalvikvm(10035): GC_FOR_ALLOC freed 455K, 16% free 15471K/18248K, paused 28ms, total 28ms
I/dalvikvm-heap(10035): Grow heap (frag case) to 15.439MB for 320016-byte allocation
D/dalvikvm(10035): GC_FOR_ALLOC freed 7K, 16% free 15776K/18564K, paused 27ms, total 27ms
I/AudioService( 576): AudioFocus requestAudioFocus() from [email protected][email protected]
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(10035): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
I/VS.G3EngineManager(10035): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 3 ms
I/decoder (10035): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err(10035): java.io.IOException: AudioRecord failed to initialize.
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
W/System.err(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err(10035): at java.io.InputStream.read(InputStream.java:163)
W/System.err(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
D/dalvikvm(10035): threadid=49: thread exiting, not yet detached (count=0)
E/VS.G3EngineManager(10035): Error running recognition: 3
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/AudioService( 576): AudioFocus abandonAudioFocus() from [email protected][email protected]
E/UberRecognizerController(10035): onError
E/UberRecognizerController(10035): com.google.android.speech.exception.AudioRecognizeException: Audio error
E/UberRecognizerController(10035): at com.google.android.speech.embedded.Greco3Recognizer.read(Greco3Recognizer.java:98)
E/UberRecognizerController(10035): at dalvik.system.NativeStart.run(Native Method)
E/UberRecognizerController(10035): Caused by: java.io.IOException: AudioRecord failed to initialize.
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
E/UberRecognizerController(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
E/UberRecognizerController(10035): at java.io.InputStream.read(InputStream.java:163)
E/UberRecognizerController(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
E/UberRecognizerController(10035): Got error after recognizing []
I had exactly the same thing few weeks ago on a number of roms, couldn't get a fix so just settled on a rom that didn't have the issue
Sent from my HTC One X using xda premium
Thanks for your reply.
can you tell me on which roms you experienced the issue and on which it does not occur?
on AOKP it doesn't work either.
Sense ROMs seem to be working..
I also sent a feedback report to google but i don't think there will be any response.
It worked on sense ROMs but I don't like them, most aokp and aosp ROMs had the the problem but for some reason it works fine on xenonhd and slimbean. I like slim so I just stuck with it
Sent from my HTC One X using xda premium
I digged in a little bit deeper and it's really odd.
on the first launch google now initializes in my local language:
Code:
I/VS.G3EngineManager(23710): create_rm: m=ENDPOINTER_VOICESEARCH,l=de-DE
I/VS.G3EngineManager(23710): Brought up new g3 instance :/data/data/com.google.android.googlequicksearchbox/app_g3_models/de-DE/endpointer_voicesearch.config for: de-DEin: 34 ms
which works.
after returning it tries to bring up
Code:
I/VS.G3EngineManager(30287): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
W/Search.ConcurrentUtils(30287): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(30287): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 2 ms
I/decoder (30287): ERROR: Exception thrown from GoogleRecognizer.read()
which than fails.
when setting the system language to english it works all the time.
Do you still use a different language than EN_US on SlimBean (I suppose you did) ? or might that be the reason it is working on Slim ?
Phone and search are set to eng UK. Just tried changing to eng generic on Google now and the problem returns, changed back to eng UK and still problem then cleared app cache in system setting and all is fine again. So looks like you found something, good job
Sent from my HTC One X using xda premium
thanks for trying.
would be awesome if someone with a sense rom could try as well.
But i guess it will be an AOSP / 4.2.2 issue only.
maybe one of the dev's can have a look into it.. would be awesome to get this one figured out.
seems like the latest google search / now update solved the problem for me.
maybe you can confirm !?
Hello everybody,
Hope my thread finds you all well.
Since I do not find special place for HTC One M9+ SC, I am writing my question here. I recently bought HTC One M9+ Supreme Camera. The phone works well, but I can't manage to make the IR work. I was missing CIR Module and I installed it, but I get this message in the System log when I try to execute IR command within an application (it doesn't matter what app is it):
E/CIRControlService( 8844): CommandHandler: request 4 drop: 0 RID=6d188c3e-0333-4283-93a7-4c2dc3b14366
E/CIRControlService( 8844): CommandHandler: poll 1 drop:false id=6d188c3e-0333-4283-93a7-4c2dc3b14366
E/htcircontrol( 8844): loadAndSendIR: error 18
E/htcircontrol( 8844): loadAndSendIR: exit 0x12
The other thing I found that is this:
03-14 03:54:56.685 11906 11906 W CIR-HtcAccessory: onCreate: mCirExist: true, mAccessoryExist: false, mAccessorySupportCIR: false
03-14 03:54:56.685 11906 11906 W CIRControlService: Service Started
03-14 03:54:56.685 11906 11906 W CIRControlService: Received start id 1: Intent { cmp=com.htc.cirmodule/.CIRControlServiceOwner }
03-14 03:54:56.686 11906 11906 W CIRControlService: onBind
03-14 03:54:56.688 11906 11906 W CIRControlServiceClient: onServiceConnected , thread :main
03-14 03:54:56.853 11906 11906 W CIRControlServiceClient: sendMessageToService
03-14 03:54:56.853 11906 11906 W CIRControlServiceClient: sendMessageToService , thread :main
03-14 03:54:56.853 11906 11906 W CIRControlService: IncomingHandler: 1
03-14 03:54:56.853 11906 11906 W CIR-HtcAccessory: IncomingHandler: mCirExist: true, mAccessoryExist: false, mAccessorySupportCIR: false
03-14 03:54:56.857 11906 11906 W CIRControlService: Client { when=-2ms what=1 target=com.htc.cirmodule.CIRControlServiceOwner$IncomingHandler } registered.
Why are these "mAccessoryExist: false, mAccessorySupportCIR: false" set to false? I am happy if somebody can tell what's going on.
These are the versions:
Android 5.0.2
HTC Sence 7.0
Software number: 1.03.708.12
Kernel version: 3.10.61-g7421ec8 ([email protected]) (gcc version 4.9 20140514 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 9 22:30:29 CST 2015
Baseband version: 1.1506V24P59.2508.1008_HTW
Build number: 1.03.708.12 CL608897
Bootloader is unlocked and the phone is rooted.
Thank you all in advance.
more information
After a little bit of decompiling I found the meaning of this error:
CIR_TTY_READ_ERROR = 18;
The tty used for this operation is: /dev/ttyMT1. You can see that when you hexedit /system/lib64/libhtcirinterface_jni.so where the native calls are made from.
I still cannot understand what's wrong..
I've heard there unfortunately isn't an infrared port on the M9 SC edition , though I may be wrong ...
GrazzaD said:
I've heard there unfortunately isn't an infrared port on the M9 SC edition , though I may be wrong ...
Click to expand...
Click to collapse
You may be right, but there should be. The blaster can be seen on top of the phone. It's the same body as HTC One M9+. GSMarena confirms that there is infra red port, but HTC doesn't say anything in the phone specifications.
M9+ sc does have infra red. Have you tried the peel remote? Faulty ir ports are NOT unheard of.
Sent from my HTC One M9 using Tapatalk
I've just read on gsmarena comments that nobody who owns the m9+sce seems to have got ir working, that actually put me off buying it.
I've tried various remote control programs, but I've got the errors explained above.
I wonder why the phone came whitout HTC_CIR.apk preinstalled, but the shared libraries exist and are loaded. I checked them via /proc/<lib cir process id>/maps.
CIR firmware can be found in /system/etc/cir.img. I wasn't able to flash it using /system/bin/cir_fw_update.
I think the problem lies in the kernel missing support for it.
Can somebody give an idea how to check that? It's very hard without kernel .config.
Or how can I check what driver operates /dev/ttyMT1?
Yes, I own the same phone, and couldn't get the IR blaster working.
Zaki Gaima said:
Yes, I own the same phone, and couldn't get the IR blaster working.
Click to expand...
Click to collapse
I have contacted HTC Live support today and they confirmed that it has IR blaster and SHOULD work with Peel.
I still can't get it work and can't find the problem. I dumped my phone partitions and see what is there
Here is the SPEC for M9+ SC.
http://www.htc.com/hk-en/smartphones/htc-one-m9-plus-supreme-camera/
There was lack of "CIR" in the "Connectivity" section for M9+ SC.
Something loss.... maybe ?
yvtc75 said:
Here is the SPEC for M9+ SC.
http://www.htc.com/hk-en/smartphones/htc-one-m9-plus-supreme-camera/
There was lack of "CIR" in the "Connectivity" section for M9+ SC.
Something loss.... maybe ?
Click to expand...
Click to collapse
I read that couple of times and I still don't get it why the support guy did tell me that there is IR on this phone even though HTC_CIR was not installed and I told him that too. He confirmed the presence of IR couple of times. Everything looks very strange to me. Why did HTC leave ir dummy transmitter on a high-end phone?
I will continue to dig in this but I have to find а stock ROM first.
ivo1st said:
I have contacted HTC Live support today and they confirmed that it has IR blaster and SHOULD work with Peel.
I still can't get it work and can't find the problem. I dumped my phone partitions and see what is there
Click to expand...
Click to collapse
That sounds good, but I have never found a person on the web who claims that IR Blaster is working for their M9+
I have received my OnePlus 3 yesterday (updated today), and I have a weird bug in Google Chrome. My website (www.vry.sexy) has a Webkit CSS animated circle which you should be able to see as soon as you visit the site. Google Chrome on the OnePlus 3 does not display the circle, but Google Chrome on my Nexus 4 and Nexus 7 (2013) displays the circle just fine. Firefox on my OnePlus 3 also displays the circle. The issue was present before and after the latest update.
The code is on codepen.io if you wish to review it: http://codepen.io/badpixel/pen/GqNPzK
In the meantime I have also asked two friends with OnePlus 3's to test the website and they both experience the same issue.
I have also tested the site on a Samsung Galaxy Note II, Nexus 5X and Moto G 2nd Gen. It works as expected on everything else.
I have tried the usual clear data, install - uninstall.
I've contacted chat support which suggested a hard reset, which I have done to no avail. Another chat with chat support suggested I do an RMA but I cannot since the OnePlus site will not let me, as there is no way currently to contact support or start an RMA from their site. Their support must be swamped.
I have nevertheless emailed support, but I am not counting on a reply soon.
Does anyone have any idea regarding this issue? Do you experience the same issue?
Update July 14, 2016: OnePlus support contacted me and asked me to contact Google Support. I have made a thread to report the issue in the Google Chrome support forums and currently waiting. I have also asked OnePlus support how they wish I contact Google. They provided a phone number without a country code (it is not a local number for me) and I replied asking to which country the phone number is to, as I would not want to receive an inflated bill from international calls by the end of the month.
Try using an older version, if that doesn't help, wait for a new version. :/
_MartyMan_ said:
Try using an older version, if that doesn't help, wait for a new version. :/
Click to expand...
Click to collapse
Do you experience the same issue?
bad pixel said:
Do you experience the same issue?
Click to expand...
Click to collapse
Yes.
I have the same issue if it can help.
Also I had a look at the logcat and found a few interesting errors (they occur each time you reload the page).
I cannot assure you they are related to your issue but it could be.
Code:
07-14 17:16:43.334 5166 5178 E chromium: [ERROR:texture_manager.cc(2746)] [.CommandBufferContext.RenderCompositor-0xf50e8560]GL ERROR :GL_INVALID_OPERATION : glTexImage2D: <- error from previous GL command
07-14 17:16:43.388 5166 5178 E chromium: [ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0xf50e8640]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
07-14 17:16:43.397 5166 5178 E chromium: [ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0xf50e8640]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
If you try to debug, the circle is definitely there. It's just the blending option that does not work.
mix-blend-mode: multiply;
_Man0waR_ said:
I have the same issue if it can help.
Also I had a look at the logcat and found a few interesting errors (they occur each time you reload the page).
I cannot assure you they are related to your issue but it could be.
Code:
07-14 17:16:43.334 5166 5178 E chromium: [ERROR:texture_manager.cc(2746)] [.CommandBufferContext.RenderCompositor-0xf50e8560]GL ERROR :GL_INVALID_OPERATION : glTexImage2D: <- error from previous GL command
07-14 17:16:43.388 5166 5178 E chromium: [ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0xf50e8640]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
07-14 17:16:43.397 5166 5178 E chromium: [ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0xf50e8640]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
If you try to debug, the circle is definitely there. It's just the blending option that does not work.
mix-blend-mode: multiply;
Click to expand...
Click to collapse
Thank you so much for this. This is what I figured as well. The question is why does this not work on the 1+ 3 but works on every other phone I have tested.. I have posted in Google Webmaster and Chrome product forums but no replies from Google. 1+ support is just dodging the question of if they can replicate the error. I asked directly many times in my 1+ month old ticket with them and they always reply with something completely random.
using MyFiles, saw it in the main file directory.
GROWTH_TEST
was empty, deleted it.
anyone come across this?
Here also but the file is filled with connections blocked log.
raul6 said:
connections blocked log
Click to expand...
Click to collapse
interesting! what creates this log? is this system-related or a specific app?
Filled with following:
com.android.volley.NoConnectionError: java.net.ConnectException: Failed to connect to ureca.samsungapps.com
Me too. Info from Growth-Test Log Text.
com.android.volley.NoConnectionError: java.net.UnknownHostException: Unable to resolve host "ureca.samsungapps.com": No address associated with hostnamecom.android.volley.VolleyError: Network Disconnectedcom.android.volley.VolleyError: Network Disconnected
Sounds like it is a host. Could we be hacked? I have had issues since last august!
L .J.629 said:
Me too. Info from Growth-Test Log Text.
com.android.volley.NoConnectionError: java.net.UnknownHostException: Unable to resolve host "ureca.samsungapps.com": No address associated with hostnamecom.android.volley.VolleyError: Network Disconnectedcom.android.volley.VolleyError: Network Disconnected
Sounds like it is a host. Could we be hacked? I have had issues since last august!
Click to expand...
Click to collapse
It's apparent that it is a log file for an app on the phone.
Could your phone be hacked? if you truly were then you wouldn't see a log file. Let alone a log file saying that something couldn't connect to a samsung server.
If in doubt perform a full factory data reset and set the phone back up without using a backup. Do not install anything on the phone other then updates to what was on the phone originally. Use it like this for half a week to a week... if the log fle appears then it's probly from one of the apps on the phone.
Your issues are probably (80-90% likely until you make a proper new thread asking for help) entirely seperate from this.
Chances are either you have outdated firmware/software, hardware failures/problems, expectation/reality matters, or just need to do a factory data reset. If you choose to do the factory data reset then avoid using a backup to restore apps and settings (cuz if the issue was from an app or setting then the issue is most likely included with the backup).
I found some weird things in Hidden Sys apps as well: "Circular ver1.0" five instances of it 0.0B, "Filled" - also 5 instances, "Gestural Navigation Bar" - 10 times, "Rounded" x4 and some other 0.0 B apps., does anyone know what for are they and why they propagate in so many instances? Thanks in advance.
It was really bothering me that I couldn't find solid information on this. I went pretty deep down the rabbit hole this morning. So far, this is what I've found out:
Worth Noting;
-- If you crawl the subdomains for the logged domain samsungapps,com it's related to Samsung Galaxy Apps.
-- ureca subdomain was registered in 2009 (first Galaxy phone release)
-- "Growth" seems to be related to marketing via the Galaxy Store.
-- There seems to be Knox relations as well. I will speculate further down below.
After sorting through a ton of data, as if it couldn't be safely assumed by the domain, the ureca URL is embedded in the Samsung Apps, Theme Store, and Game Launcher, that I've found so far. Take a look at some interesting strings I found in the APKs;
Package Name
com.samsung.android.themestore
Internal Version
520110303
Displayed Version
5.2.01.10303
]https://ureca.samsungapps.com/collect/billing_usage_log
]https://ureca.samsungapps.com/collect/theme_sa_log
]https://cn-ureca.galaxyappstore.com/collect/theme_sa_log
Package Name
com.sec.android.app.samsungapps
Main Activity
com.sec.android.app.samsungapps.SamsungAppsMainActivity
Internal Version
450509140
Displayed Version
4.5.05.9
]https://ureca.samsungapps.com/collect/iap_usage_log
(There are also iap subdomains @ samsungapps too, fwiw)
BUT, I have no idea what devices these are coming off of. Some APKs are varying wildly. Some report spyware, trojans, etc, too. Most by only 1 AV vendor though. If anyone has more time than me, take a look. Not sure if Knox is the "backdoor", the 'diamond' and 'zirconia' subdomains looked interesting. Or if it's a false hit, the Chinese govt, or if the APKs are from a repo and they're malicious. Didn't look into it in the slightest.
VirusTotal
VirusTotal
www.virustotal.com
Or if anyone already discovered exactly the source of the "GROWTH_TEST" folder, please let me know so I don't revisit this. But I'm pretty sure it's Galaxy Store Market related stuff.
FWIW - Me
Galaxy S10+, OEM Unlocked.
June 1st security update. USA
My Growth Test folder contained 2 files,
appsUsageLog.txt: (1 "volley can't resolve ureca.samsungapps.com")
optin_trace.txt: (1 "volley network error")
You're probably over thinking this.
Pretty sure I've seen it before too.
If you're still running on Pie Karma Firewall will let you monitor and block internet connections.
Shows you which apks are busy sucking up bandwidth and battery.
Scan any questionable apks online with Virustotal.
AM Radio said:
using MyFiles, saw it in the main file directory.
GROWTH_TEST
was empty, deleted it.
anyone come across this?
Click to expand...
Click to collapse
Any updates to this? I too have the Growth_test folder with appGrowthLog.txt in it.
Edit: in the appGrowthLog.txt file says "com.android.volley.NetworkErrorcom.android.volley.VolleyError: Network Disconnected".