Samsung Mobile Devices
Samsung Mobile Devices
Introducing the Samsung Mobile Devices CONF.

This was also submitted in Github as well.
The DLNA/UPnP app used was: Skifta
(and will be my App of choice for testing too, as its DLNA certified software!!)
I welcome feedback.
Update (9/22/2013)
Once the h264 profile is ironed out, then i will update the code for Community testing!

This was also submitted in Github as well.
The DLNA/UPnP app used was: Skifta
(and will be my App of choice for testing too, as its DLNA certified software!!)
I welcome feedback.
Update (9/22/2013)
- Nightly Build (UMS Builder) has Icon now
- Working on H264 with SubJunk; this transcode package looks very promising with better video rendering, still audio issues.
- Need to collect a list of all Samsung Mobile Devices's User-Agents, Currently tested the below conf with the following devices:
SGH-T999 (T-Mobile S3)
SGH-I747 (Verizon S3)
SPH-L710 (Sprint S3)
SGH-I337 (At&t S4)
GT-N7000 (At&t Note)
SCH-I545 (Verizon S4) - Need to work with Optimus_prime to see if an additional line in the Samsung Allshare.conf; ADD IN "UserAgentAdditionalHeader=TV|X-AV-Client-Info" for a more specific identifier to "Samsung TV's" (i can't remember if we tried this or not.... ) viewtopic.php?f=5&t=757
- MKV's wont play. (mencoder fails) UPDATE: this now works in the latest UMS Build
- Android.conf is a conflicting CONF, to resolve that issue rename "Android.conf" to "Android.conf.disable"
- ChromeCast.conf shows potential for conflict.
Code: Select all
#-------------------------------------------------------------------------------------------
# Profile for Samsung Mobile Series - Galaxy S3, S4, Note, Note 2, and Note 3.
# See PS3.conf for a description of all possible configuration options.
# More Agent Searches could be used; Still need to Identify User-Agents.
#-------------------------------------------------------------------------------------------
RendererName=Samsung Mobile
RendererIcon=samsung-galaxy-s3.png
UserAgentSearch=SGH-T999|SGH-I747|SPH-L710|SGH-I337|GT-N7000|SCH-I545
UserAgentAdditionalHeader=Dalvik
UserAgentAdditionalHeaderSearch=SGH-T999|SGH-I747|SPH-L710|SGH-I337|GT-N7000|SCH-I545
Video=true
Audio=true
Image=true
SeekByTime=false
CustomMencoderOptions = -channels 2 -lavdopts debug=0:threads=4 \
-lavcopts autoaspect=1:vcodec=mpeg4:acodec=mp2:abitrate=192:\
threads=8:keyint=0:vqscale=5:vqmin=2:vrc_maxrate=10000:vrc_buf_size=10000 \
-vf softskip,expand=::::1:16\/9:4,scale=640:360 \
-ofps 30000/1001 \
-lavdopts fast \
-af lavcresample=48000 \
-srate 48000 \
-aid 0 \
-nosub \
-noautosub \
-mc 0.1 \
-o
Last edited by DeFlanko on Tue Sep 24, 2013 4:58 pm, edited 3 times in total.



Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
Re: Samsung Mobile Devices
Hello
I don't follow this thread but I spotted the wrong expand usage
Anyway why using expand? I suppose Android is not so "dumb" so you can control squeezed picture by changing AR manually (so SW player will add missing black bars automatically).
Why softskip/expand order is wrong and why :1: should be replaced with :0:
viewtopic.php?f=9&t=580
I don't follow this thread but I spotted the wrong expand usage

Anyway why using expand? I suppose Android is not so "dumb" so you can control squeezed picture by changing AR manually (so SW player will add missing black bars automatically).
Why softskip/expand order is wrong and why :1: should be replaced with :0:
viewtopic.php?f=9&t=580
Re: Samsung Mobile Devices
Haha, I copied from the ums.conf tbh...I can change it and see if its still the same. Ill try it tonight and let you know.
Either way it bulk of the custom section will be replaced hopfully with the new h264 thing subjunk is working on.
Either way it bulk of the custom section will be replaced hopfully with the new h264 thing subjunk is working on.



Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
-
- Posts: 6
- Joined: Fri Sep 20, 2013 12:34 pm
Re: Samsung Mobile Devices
GT-N7000 is international Galaxy note....for AT&T i believe it would be I717 and T879 for T-Mobile. Info are all on GSMArena.com 

Re: Samsung Mobile Devices
But i think think its sold here in America under At&t... unsure though i have T-Mobile. 
Ill add in the rigth devices as Members ask for them, and can assist in Testing.

Ill add in the rigth devices as Members ask for them, and can assist in Testing.



Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
-
- Posts: 6
- Joined: Fri Sep 20, 2013 12:34 pm
Re: Samsung Mobile Devices
I can comment about International Note only, not for other variant as im pretty sure it use different chipset/cpu. MKV work fine without re-encoding needed.
UMS ver 3 a5
Naruto anime eps. 319
Video :1920x1080 H264/MPEG-4 AVC/MPEG-4 part 10
audio : AAC 44.1Khz
Sub : embedded sub
Player : MX Player with additional codec installed
Dragon Lore curse of the shadow
Video :1920x1080 H264/MPEG-4 AVC/MPEG-4 part 10
audio : DCA (DTS Coherent Acoustic) / 5.1 channel / 1.5Mbit / 48000 KHz
Sub : embedded sub
Player : MX Player with additional codec installed
no AV OOS issue
UMS ver 3 a5
Naruto anime eps. 319
Video :1920x1080 H264/MPEG-4 AVC/MPEG-4 part 10
audio : AAC 44.1Khz
Sub : embedded sub
Player : MX Player with additional codec installed
Dragon Lore curse of the shadow
Video :1920x1080 H264/MPEG-4 AVC/MPEG-4 part 10
audio : DCA (DTS Coherent Acoustic) / 5.1 channel / 1.5Mbit / 48000 KHz
Sub : embedded sub
Player : MX Player with additional codec installed
no AV OOS issue
Re: Samsung Mobile Devices
You're using the MX player, i'm using the stock android player. Natively in ASOP (Android Open Source Project) MKV is not a recognized MIME type.
(which i think this is describing) also @Subjunk does this help?
http://developer.android.com/reference/ ... Codec.html

(which i think this is describing) also @Subjunk does this help?
http://developer.android.com/reference/ ... Codec.html
I know that Vplayer and MXPlayer using additional software codec's for rendering can do things, this normally results in extra CPU on the device to be used, and eventual more battery drain. My goal is to make UMS to do all the heavy lifting and present a usable video to the device. A majority of the users on here have very beefy machines mine included. Why not work those insteadpublic static MediaCodec createDecoderByType (String type)
Added in API level 16
Instantiate a decoder supporting input data of the given mime type. The following is a partial list of defined mime types and their semantics:
"video/x-vnd.on2.vp8" - VPX video (i.e. video in .webm)
"video/avc" - H.264/AVC video
"video/mp4v-es" - MPEG4 video
"video/3gpp" - H.263 video
"audio/3gpp" - AMR narrowband audio
"audio/amr-wb" - AMR wideband audio
"audio/mpeg" - MPEG1/2 audio layer III
"audio/mp4a-latm" - AAC audio
"audio/vorbis" - vorbis audio
"audio/g711-alaw" - G.711 alaw audio
"audio/g711-mlaw" - G.711 ulaw audio
Parameters
type The mime type of the input data.




Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
-
- Posts: 6
- Joined: Fri Sep 20, 2013 12:34 pm
Re: Samsung Mobile Devices


Re: Samsung Mobile Devices
Fair enoughsatanhead2003 wrote:my nas only sempron dual core with 2gb ram...ill stick with mx player




Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."