Related
Hello All,
I just upgraded to the last WM6 (really cool OS btw)
I've been going through the treads but I can't find a solution for my stupid problem.
I can't set up my old ringtone, before I just needed to past the in the "\Application Data\Sounds" directory and I could select them as ringtones or custom ringtones.
But since the WM6 they don't appear anymore in the options.
I copied them everywhere
- root directory of storage card,
- \My Documents\My Ringtones\
- \Storage Card\My Documents
But they still don't appear what am i doing wrong?
I have 2 MP3 files that worked fine on my WM5
Thanks in advance.
Frem
Which WM6 ROM are you using?
But then, I am able to select custom MP3 ringtone for all builds of WM6
Version :
OS 5.2.318 (Build 15341.0.0.1)
Are they Mp3 format and what is the directory where you put them?
I just put some .WMA custom windows ringtones in the "\Application Data\Sounds" and they appear ! Is it that .mp3 are not recognized under WM6?
I converted my .MP3 to .WMA they now appear, but they sound TERRIBLE. How can I make the mp3 version recognized ?
Just put your ringtones to root of your storage card.
Have you tried sticking them in \windows\rings?
well I did put them in all those folders. But the mp3 versions don't appear.
The .wma do appear though.
For some unknown reason the phone doesn't see the mp3 versions.
Who's ROM are you using? Phil or Andot ?
I'm not sure I used the one from that tutorial:
http://karhoe.byethost33.com/index.php?option=com_content&task=view&id=21
In the About I have Version:
OS 5.2.318 (Build 15341.0.0.1)
Radio Version 4.1.13.28_06.61.01
RIL Version 2.002
Rom update versions 5.2.318.15341
I don't know if it's Phil's or Andot's.
Can you figure out which version I have from the info I gave you? And what is the best version?
Lol I just realized the tutorial I used is the same one as your signature . I guess you have the answer then.
Your guide is really good, I did the upgrade yesterday, and it took me 50 minutes to get everything set up on my Qtek 8310.
Very good job.
I'm still dealing with this mp3 file ringtone issues though .
Probably Andot's. I have the same problem and I'm using Andot's. Thanks for the fix.
I'll dig around in the registry and search for "\Application Data\Sounds" and see if it got mucked up some how...
Yeah my work-around with the .WMA convertion works.
I was able to get a decent sound with a .WMA version of my .MP3 version so I'll survive .
But still I like when things are perfect and are like they used to be, and even better.
So far this WM6 as make everything faster, easier, better, software more stable and some didn't work before or made the phone crash like PMrecorder, now it works perfectly.
I feel like having a new phone even if it's like 2 years old hehe.
Ok very weird I put an other MP3 which is 217K, it's smaller than the other mp3s I tried (496kb and 398kb) And this one appear!!!
It could be size related. We could do some checkup is the registry and test in that area.
frem said:
Ok very weird I put an other MP3 which is 217K, it's smaller than the other mp3s I tried (496kb and 398kb) And this one appear!!!
It could be size related. We could do some checkup is the registry and test in that area.
Click to expand...
Click to collapse
Strange. I'm test right now - tried mp3 file 863 KB and its OK. May be bit rate?
I'm use 128 kbps.
The two that don't appear have those settings :
-----------------------------
Size: 406802 bytes
Length: 25 seconds
MPEG 1.0 layer 3
128kbit, 975 frames
44100Hz Joint Stereo
-----------------------------
Size: 507112 bytes
Length: 32 seconds
MPEG 1.0 layer 3
128kbit, 1216 frames
44100Hz Joint Stereo
-----------------------------
The one that appear has this setting :
-----------------------------
Size: 223184 bytes
Length: 56 seconds
MPEG 2.0 layer 3
32kbit, 2146 frames
22050Hz Mono
-----------------------------
So the diffrence between the files are
- MPEG 2.0 layer 3 / MPEG 1.0 layer 3
- 32kbit / 128kbit
- 44100Hz / 22050Hz
- Mono / stereo
The problem is related to one of those parameters.
If i understand your last post you said that your 128kbit version appeared so we can remove that parameter. Is your 128kbit file that appear encoded in
- MPEG 2.0 layer 3 or MPEG 1.0 layer 3 (the info appear in winamp file info)
- Is it mono or stereo?
- What is the Hz on that file that appear?
We will get to the bottom of this !
OK. First file:
Payload Size: 879804 bytes
Header found at: 4096 bytes
Length: 55 seconds
MPEG-1 layer 3
128kbit, approx. 263 frames
44100Hz Mono
CRC: No, Copyrighted: No
Original: Yes, Emphasis: None
Second:
Payload Size: 883672 bytes
Header found at: 417 bytes
Encoder Delay: 576, Zero Padding: 1728
Length: 52 seconds
MPEG-1 layer 3
136kbit (VBR), 1994 frames
44100Hz Joint Stereo
CRC: No, Copyrighted: No
Original: Yes, Emphasis: None
Third:
Payload Size: 2975869 bytes
Header found at: 0 bytes
Length: 186 seconds
MPEG-1 layer 3
128kbit, approx. 889 frames
44100Hz Joint Stereo
CRC: Yes, Copyrighted: Yes
Original: Yes, Emphasis: None
And two small files:
Payload Size: 484075 bytes
Header found at: 4258 bytes
Length: 30 seconds
MPEG-1 layer 3
128kbit, approx. 144 frames
44100Hz Mono
CRC: Yes, Copyrighted: No
Original: No, Emphasis: None
Payload Size: 323848 bytes
Header found at: 0 bytes
Length: 20 seconds
MPEG-1 layer 3
128kbit, approx. 96 frames
44100Hz Mono
CRC: Yes, Copyrighted: No
Original: No, Emphasis: None
All this files works fine! I can assign all of them like ring tone.
I'm using Andot last (V6) ROM.
Exitao said:
Probably Andot's. I have the same problem and I'm using Andot's. Thanks for the fix.
I'll dig around in the registry and search for "\Application Data\Sounds" and see if it got mucked up some how...
Click to expand...
Click to collapse
Well like Exitao said i'm probably using Andot's as well i used the ROM from karhoe's tutorial :
http://karhoe.byethost33.com/index.php?option=com_weblinks&task=view&catid=20&id=29
I tried some high quality mp3s files as well and they appeared
Size: 5405593 bytes
Header found at: 0 bytes
Length: 225 seconds
MPEG 1.0 layer 3
192kbit, 8635 frames
44100Hz Stereo
CRCs: No
Copyrighted: No
Original: Yes
Emphasis: None
So the only files that didn't appear have those settings:
----------------------------------
Size: 507112 bytes
Header found at: 0 bytes
Length: 32 seconds
MPEG 1.0 layer 3
128kbit, 1216 frames
44100Hz Joint Stereo
CRCs: No
Copyrighted: No
Original: Yes
Emphasis: None
----------------------------------
Size: 406802 bytes
Header found at: 0 bytes
Length: 25 seconds
MPEG 1.0 layer 3
128kbit, 975 frames
44100Hz Joint Stereo
CRCs: No
Copyrighted: No
Original: Yes
Emphasis: None
------------------------------------
I just did a test on the second one (25 sec) that wasn't working. I re-encoded it with those settings:
Size: 509516 bytes
Header found at: 0 bytes
Length: 25 seconds
MPEG 1.0 layer 3
160kbit, 976 frames
44100Hz Joint Stereo
CRCs: No
Copyrighted: No
Original: Yes
Emphasis: None
And now it works it appear!
And if we check all the settings it makes absolutely no sense . Ho well one of those mystery bug .
I guess if it happens to someone else we can only advice him to re-encode his file and that will fix it.
Thank you for your help.
Frem
OK. Good to see what all working!
Got to let Phil now, hopefully he can fix this up
Why Phil? I thought i had Andot's ROM from your tutorial?
Andot is not really developing Tornado nowadays, but his wife's Typhoon
Nvidia lists the following specs on their website for the Tegra2 :
Video decode
H.264
VC-1 AP
MPEG2
MPEG-4
DivX 4/5
XviD HT
H.263
Theora
VP8
WMV
Sorenson Spark
Real Video
VP6
Audio decode
AAC-LC
AAC+
eAAC+
MP3
MP3 VBR
WAV/PCM
AMR-NB
AMR-WB
BSAC
MPEG-2 Audio
Vorbis
WMA 9
WMA Lossless
WMA Pro
Can anyone confirm that the xoom can decode these?
Can the Xoom/honeycomb media player read subtitles (in) .mkv or .srt, sub/idx files?
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
I am not sure what is out there on torrents, but I have some MKVs that I encoded and they have a bitrate of around 3mbit. According to this general tips section:
http://forum.xda-developers.com/showthread.php?t=969029&highlight=720p
The Xoom is supposed to be able to play video as long as the bitrate is under 20Mbit. The post references this:
https://supportforums.motorola.com/message/330326#330326
which says that realistically as long as the bitrate is under 4Mbit you should be fine.
The MKVs that I am trying to play, which are well under 20mbit and under 4mbit, skips like crazy and is unwatchable.
If I look at vmstat (via adb shell) while I am playing a movie using rock player in software decoding mode, the CPU goes to 100% (presumably in the kernel that android is using each core gets 100%, so there is a total of 200% available -- half ends up in system and half in user land):
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 74440 58584 254928 30112 158 1005 0 99 0 30 99 0 0
1 0 74564 58588 255036 30124 466 2263 0 99 0 22 99 0 0
1 0 68392 58880 261072 30128 367 2742 0 99 0 32 99 0 0
1 0 67136 58968 262216 30180 684 3604 0 99 0 32 99 0 0
2 0 67004 58976 262456 30180 224 1635 0 99 0 13 99 0 0
3 0 66632 58912 262756 30180 272 1721 0 99 0 10 99 0 0
3 0 60564 59724 266896 30160 414 2212 3 99 0 19 99 1 0
3 0 25136 60136 294812 30196 603 3372 0 99 0 76 9 0 0
4 0 25012 60128 294512 30184 472 2458 0 99 0 88 6 0 0
5 0 25020 60128 294448 30184 390 2121 0 99 0 99 3 0 0
3 0 24540 60128 294440 30164 265 1631 0 99 0 99 1 0 0
4 0 24416 60128 294576 30164 353 1768 0 99 0 93 6 0 0
4 0 24912 60128 293108 30140 332 1747 0 99 0 99 5 0 0
3 0 24788 60128 293076 30140 300 1604 0 99 0 99 3 0 0
While looking at hardware decoding mode, the system usage drops way down:
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 54116 58928 262524 30140 170 933 0 99 0 10 99 0 0
3 1 63780 58932 262520 30276 1119 4809 0 99 0 24 99 6 0
7 0 50184 59544 264332 31072 3493 19967 6 99 0 99 98 14 0
4 0 5620 59852 311776 31124 455 4765 2 99 0 61 18 0 0
3 0 5124 59868 311872 31064 368 4590 0 99 0 33 23 0 0
4 0 5124 59860 313024 30952 322 4625 0 99 0 39 44 0 0
3 0 4760 59860 313060 30936 390 5172 0 99 0 45 25 0 0
3 0 5256 59860 313032 30900 358 5475 0 99 0 38 30 0 0
3 0 4884 59868 312992 30876 336 5202 0 99 0 31 35 0 0
4 0 4636 59868 312856 30816 307 5036 0 99 0 34 36 0 0
3 0 5504 59904 312876 30816 378 5095 0 99 0 36 37 0 0
4 0 5504 59912 312884 30664 363 5046 0 99 0 33 44 0 0
3 0 4512 59924 312808 30656 288 4796 0 99 0 27 29 0 0
4 0 5256 59928 312908 30408 287 4927 0 99 0 32 38 2 0
3 0 5008 59928 312808 30404 367 5779 0 99 0 44 28 0 0
1 0 5132 59944 312820 30224 490 3432 0 99 0 36 74 0 0
But the playback remains fairly choppy. So all we need is the great devs at Rockplayer to stick the right code in for hardware decoding.
Presumably the native player uses hardware decoding which is why it is able to play video with framerates around 4mbit.
http://mediainfo.sourceforge.net/en
Download that and after installing, open it up and drag your mkv file into the window. Bet you that those videos are high profile h.264 which is the reason for the choppiness.
The reasons your processor max out in software mode is that its using the CPU to play the file. It drops down using hardware acceleration because its the GPU playing the file.
I used mediainfo to get the bitrate, which is under 4Mbit, which is under the limit that is quoted on the Motorola website. The fact that they may be a specific "media profile" in whatever converter you are using makes no difference -- only the bitrate is important.
Also, as mentioned in my post, I understand that the CPU drop is due to the use of hardware rendering. We still have to wait for either specific Xoom GPU support in Rockplayer or optimized code changes in Rockplayer.
Also, it appears that the native movies app is able to play my MKV files. It plays them much smoother, but they are still too choppy and the sound doesn't come through. The audio track on this is an AC-3 48KHz, 384Kbps audio stream.
No. You dont understand. The profile is everything. Bitrate means nothing. Tegra 2 is not capable of playing high profile hd h.264. The video you are trying to play is probably a high profile h.264 mkv file. There are various profiles for h.264 video. The Tegra 2 can play baseline profile. Almost all media is in high profile.
Do this for me, drag the media file you are trying to play into MediaInfo, and then go to View>Text. Then select the entire Video section and copy it and then paste it in here.
Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?
kmd1970 said:
Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?
Click to expand...
Click to collapse
software, honeycomb is buggy, its hardly optimized. no one really knows what the tegra 2 is capable of yet.
the facts are simple, there no tegra 2 device capable of playing high profile h264 right now.
tegra 2 devices are just now making it to market and its new untested unproven hardware.
secondly there are only two devices released or pseudo released(in the case of the adam) that even use this hardware. not alot of info to go on here.
at this point ask anyone here and they can't give you any 100% accurate answer, because we simply don't know. its ALL speculation at this point.
you have two camps on this issue. one camp, the hardware people claim that because both the adam and xoom use tegra 2 and can't play h264 high profile that its a hardware limitation.
the second camp takes the side that because this is new hardware, it needs proper software and drivers to handle the decoding and that this is the reason for the poor playback. this camp believes it will be fixed down the line with an update.
the second camp is the more feasible scenario. anyone that knows anything about hardware and software understands that hardware is worthless without good software.
let me give a prime example everyone knows video encoding takes time. if you want to encode a 20 minute video lets say you use handbrake and encode the video using your cpu in 14 minutes. but wait, whats this? you have a $500 nvidia graphics card in your system? its a big arse paper weight right now ain't it?
lets fix that, lets get the proper software and drivers and encode that same 20 min video by offloading to this powerful gpu. done in 5 minutes.(*actually times vary based off settings and actually hardware)
get the picture?
however, this does NOT mean that the tegra 2 is without fault. it could be the hardware and its simply not capable of high profile and never will be. we simply don't know, because we don't have any good information from nvidia or motorola or notion ink. we don't know what its true capabilities are.
all we know is that the tegra 2 with the current available devices and software cannot play high profile h264.
all the rest is speculation.
..........
From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
Tegra2 can't hw decode h264 [email protected] or above. I know because I have one (Tegra2 dev kit). That really limits the video content to SD. Too bad, it's a nice chip except for that.
Click to expand...
Click to collapse
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s
... with the amount of Tegra2 for the next month,
i think we could download all videos in tegra2 useable formats (720p/1080p) and nvidea will also adress this topic, so i am not worried about ...
muyoso said:
From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s
Click to expand...
Click to collapse
take his with a grain of salt. all he said was i have a tegra 2 dev kit and tegra 2 can't do the high profile h264.
whats this even mean? is there something in this dev kit that actually lists what the tegra 2 is capable of hardware wise? whats in this dev kit, whats the real reason it won't play.
ill take him for his word when pigs fly out of his ass.
http://developer.nvidia.com/tegra/tegra-devkit-features
its just hardware, no magical software to be had there. which means what? hes got the same software we do.
also id like to point out that there is a VAST difference between making android support another codec so it can play a video and making android offload to the gpu using drivers. key word there folks, drivers.
back to the cuda example, two things are needed to tango. first you need the proper nvidia drivers. and secondly, you need an application designed to work with those drivers in order to have it successfully utilize the gpu. xbmc can only proved the app to interface with what exists, they can't do anything else.
ps:
al gore invented the internet.
Is there like a cut off date for peoples denial about tegra 2's shortcomings? Like a year from now when it still can't play video [email protected] h.264, will people still be claiming its a lack of software?
Davilla did massive testing of the tegra 2. You think there were drivers from apple for the ipad? No.
Look, there may be a software solution if the tegra 2's cpu is powerful enough to decode hd h.264, but there is massive evidence that it will never hardware decode that video. I think its an important enough shortcoming to inform people about and not lead them on with some promise of future software.
Sent from my SPH-D700 using XDA App
Any official info from NVidia about this H.264 high profile hardware decoding capability?
Anyone reached NVidia?
e.mote said:
Most Honeycomb tablets announced will have a Tegra2 in it, and video playback is an important component, so I'm confident the issue will be addressed, if not from Nvidia, then from a 3rd-party commercial media player like Coreplayer.
Click to expand...
Click to collapse
Please, not that Coreplayer for Android rumor again. (I've been waiting for too long)
It's not really CoreCodec's fault. Android has been a pretty fast moving target, and my guess is that Nvidia hasn't been exactly timely with software support for the Tegra2, else the VS G-Tab would've had decent playback by now.
My reading of the tea leaves is that we'll probably see CP either around the Honeycomb mass launch or a bit after. Anyway, it'll come when it'll come.
Now, VLC, I think will be a fair bit longer in coming,
http://ivoire.dinauz.org/blog/index.php?post/2011/02/02/VLC-on-Android
muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
From Xoom office website, we know that Xoom supports AAC, H.263, H.264, MP3, MPEG-4, ACC+ Enhanced, OGG, MIDI, AMR NB, AAC+. If u want to play video on Xoom, the video format and video coding must be correct.
So I suggest u convert your MKV files to Mp4 H.264 1280*720 for playing.
I did a test, and I can't find any diffirence between 1080P and 720P, SO I recomend convert video to 720P, and the converted file size is small. therefore, u can transfer more video to Xoom.
For those use HandBrake, attachment is the [email protected] preset for playback in Tegra2
muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
MKV is a container format, which supports holding unlimited number of video, audio, picture or subtitle tracks inside a single file, can’t be played on the Motorola Xoom. only the video format and video encoding are right, Xoom can be play it.
So, not because Xoom can't play 720P high profile h.264 video, but the video format is wrong. I suggest u convert MKV 720p h.264 video to MP4 720P H.264 for playing on Xoom.
Asking for help from anyone who has a 5.1 audio setup to his/her PC.
At issue is ffmpeg's bug in incorrectly mapping channel order from AC3 (and perhaps other formats) to AAC. Before, you had to remap the channels using an intermediate app like sox. But my current testing (on a 2-speaker setup) shows that there isn't an issue. Confirmation from a 5.1 setup is needed.
Attached below are 4 audio test clips: 5.1 WMA, 5.1 AC3, 5.1 AAC (from WMA clip), 5.1 AAC (from AC3 clip). The clips tell you which channel the sound is supposed to come out of, eg "front left".."front right"..etc. The LFE channel will be a mumbling sound coming out of the subwoofer.
I would appreciate it if someone with a 5.1 audio setup would test all 4 clips, and tell me if the channel orders are correct for all four. The clips are only 9 secs long apiece. Thanks in advance.
They all play correct for me.
I appreciate the assist.
I still get wrong order when converting 5.1 AAC to 5.1 AC3.
which ffmpeg version are u using?
Mapped fine here, too.
Someone sent me a PM asking which build of ffmpeg I'm using (for the correct AC3->AAC mapping). Not sure if I sent a reply, so I'm cc'ing a copy here.
I'm using the Zeranoe build. This is from AC3 to AAC. I didn't test the other way. (If one way comes out OK, the other should as well, but you never know.)
http://ffmpeg.zeranoe.com/builds
ffmpeg version N-31031-gf211d9d, Copyright (c) 2000-2011 the FFmpeg developers
built on Jun 26 2011 22:50:39 with gcc 4.5.3
configuration: --enable-gpl --enable-version3 --enable-memalign-hack --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
libavutil 51. 10. 0 / 51. 10. 0
libavcodec 53. 7. 0 / 53. 7. 0
libavformat 53. 4. 0 / 53. 4. 0
libavdevice 53. 1. 1 / 53. 1. 1
libavfilter 2. 24. 0 / 2. 24. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
The AAC was created by converting the AC3 to 6-channel WAV, then piped to NeroAACEnc external encoder.
ffmpeg -i inputfile -vn -acodec pcm_s16le -ac 6 -f wav - -map 0.1 | neroAACEnc -q 0.4 -ignorelength -if - -of out.m4a
A Guide To Support My Other Thread On How To Create Boot animations So It Is Easier For People To Understand And Grasp The Concept.
so they will ask less questions XD
Hit thnxx if u like this guide friends !
CONTENTS
The Basics
Inside the bootanimation.zip file
Featured Boot Animations
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Basics :
The Android boot animation is contained within a an uncompressed zip file called bootanimation.zip that can be found in the media folder of the system partition i.e. /system/media on the internal memory of the device. This single file contains all the information required to play the boot animation, and is loaded automatically when the device boots. Thus, customizing or changing the boot animation is simply the process of editing or replacing this file.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Inside The Bootanimation.Zip File
This section is for those interested in finding out how the Android boot animation works. If you just want to install one without bothering yourself about what’s in the file, feel free to move on to the next section, as this one will get a little technical. Though it should be easy and simple enough for anyone to grasp.
While the Android boot animation might appear to be in a video format during playback, it is in fact a little different. If you extract the contents of the bootanimation.zip file to your computer, you will see:
A desc.txt file
A part0 folder (Contains PNG images named in incremental numbers)
More part1, part2 etc. folders (May or may not be present)
As you can see, bootanimation.zip merely contains one text file and one or more folders with PNG images. The animation is played simply by displaying the images in a sequence, and the text file defines how they are to be played. In essence, first the PNG files in the part0 folder are displayed one after the other and afterwards, those in the part1 file – if it exists – are displayed, again one after the other, and so on. All of this is defined in the desc.txt file.
Let’s see how it works in a little detail by taking a closer look at the contents of the file.
The folders
These contain PNG images named in numbers, starting from something like 0000.jpg or 00001.jpg and proceeding with increments of 1. There has to be at least one folder, and there is no known upper limit to the number of folders.
The desc.txt file
This file defines how the images in the folder(s) are displayed during the boot animation, in the following format:
Width Height Frame-rate
p Loop Pause Folder1
p Loop Pause Folder2
An example of a desc.txt file is:
320 480 30
p 1 0 part0
p 0 0 part1
As you can see, in the first line, 320 and 480 define the width and height of the boot animation in pixels for this example. This must be the same as the screen resolution of your device for the boot animation to properly play in full screen. 30 is the frame rate in fps (frames per second) i.e. number of images to display per second.
The second and third lines have a same format, start with p, which stands for a part of the animation and end in part0 or part1, which denotes the folder in which the images for that part are present.
The number after ‘p’ defines how many times this part will loop (repeat playback) before switching to the next part (if present). Specifying 0 would make the part loop indefinitely till the phone has fully booted.
The next number is for the pause, and is expressed in the number of frames, which can be translated into time by dividing it by the frame rate. A pause of 15 for example, would mean pausing for the time it takes 15 frames to play and since the frame rate is 30 frames per second, 15 frames would take half a second.
Translating all of this in case of the above example, the boot animation will play at a resolution of 320 by 480 pixels, at a frame rate of 30 fps, starting with the contents of part0 folder and after playing them in one loop, switching to contents of part1 folder and playing them continuously till the device fully boots.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE :
A note on resolution: Most high-end Android devices with large screens have a resolution of 480 x 800 pixels, and are referred to as HDPI. Some mid-range devices have a resolution of 320 x 480 pixels and are called MDPI. Lastly, the screen resolution of some low-end devices is 340 x 320 pixels and these are called LDPI, though these are either the really old Android phones or the cheapest Chinese models.
As a rule, a boot animation made for a lower resolution device will run fine on a high resolution one but it will be centered on the screen, with the extra screen space around it not being used. Using a high resolution boot animation on a low resolution device will result in the boot animation not fully displaying on the screen, with its outer parts being cut off due to being outside the screen’s bounds.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Featured Boot Animations
Link for some boot animations for MDPI Models i.e (320 x 480) screen resolution : http://forum.xda-developers.com/showthread.php?t=2197483 [/FONT]
Nice write up. Thanks for taking the time. Will use this to start a collection.
If you find the time please do a sound one too
E4GT Rom-a-holic!!!
Nice....:good::good:
Hello everyone!
I have been trying to compile a cyanogenmod kernel and rom for a cheap chinese tablet: yftech-me12. A clone of that tablet is Arnova 7h G3.
Tablet specs:
Capacity • Flash memory: 4 GB*
• Expandable via micro SDHC Slot up to 32 GB
Operating system • ANDROID™ 4.0 “Ice Cream Sandwich”
Processor • ARM Cortex A8 @ 1 GHz
RAM • 512 MB
Display characteristics • 7 inch - Capacitive points MultiTouch Screen 16 million colors
• 800 x 480 screen resolution
Video Playback1 • H.264, MPEG-42 up to 1080p resolution
With the above codecs, the device can play video files with the following extensions: .avi .mp4 and mkv
Audio Playback1 • MP3, WAV, APE, OGG, FLAC
Photo viewer3 • JPEG, BMP, GIF, PNG
Interfaces • Micro USB slave 2.0
• Audio Jack 3.5mm
• Micro SD slot
Communication protocols • WiFi
Miscellaneous • Front camera
• Built-in speaker
• Microphone
• G-sensor
I have downloaded the kernel source code from arnova.. Compiled the stock kernel to make sure it works and it does..
My problem is that i cannot compile a cyanogenmod kernel for my device! errors i cannot even understand!!
I've tried to install cyanogenmod for allwinner a13 tablets from here: http://forum.xda-developers.com/showthread.php?p=43072957
but the kernel will not boot! Plus i had to delete a few apks because my system partition is approx. 260mb and it would not copy the /system since there was not enough free space!
some other details about my device such as lsmod output:
8188eu 621096 0 - Live 0xbf103000
YFdecrypt 22118 0 - Live 0xbf0f8000
kt080x 5983 0 - Live 0xbf0f3000
mc32x0 7726 0 - Live 0xbf0ed000
dmt0567 10125 0 - Live 0xbf0e6000
bma250 7521 0 - Live 0xbf0e0000
byd693x_ts 9491 0 - Live 0xbf0d9000
pixcir_jc 13381 0 - Live 0xbf0d1000
sitronix_ts 23687 0 - Live 0xbf0c6000
goodix_gt82x 21242 0 - Live 0xbf0bc000
rtl8150 10305 0 - Live 0xbf0ab000
mcs7830 7589 0 - Live 0xbf0a5000
qf9700 9152 0 - Live 0xbf09e000
asix 24601 0 - Live 0xbf092000
usbnet 26253 3 mcs7830,qf9700,asix, Live 0xbf085000
sun5i_csi0 33604 0 - Live 0xbf077000
hi704 19664 1 - Live 0xbf06e000
hi253 21036 0 - Live 0xbf064000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf05f000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf055000
cedarx 9479 0 - Live 0xbf04e000
mali 151198 10 - Live 0xbf01c000
ump 48898 19 mali, Live 0xbf009000
sw_ts 18329 0 - Live 0xbf000000
cat /proc/partitions output:
ajor minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 261120 nandh
93 64 1024 nandi
93 72 2232320 nandj
93 73 2231296 nandj1
179 0 3872256 mmcblk0
179 1 3122070 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 249007 mmcblk0p3
dumps of my partitions /system /boot etc. : http://www69.zippyshare.com/v/97403369/file.html
Could someone PLEASE help me out.. I used a13_nuclear_defconfig from my stock kernel's source code to compile cm kernel and i get errors that it can not find certain files in the /drivers section.. copied files from stock source code and then some other errors occured.. so it fails..
Could someone give me some pointers? How do you guys start porting a rom to a new device without ANY previous support? Do you rewrite the modules source code to fit the cm kernel? how do you configure/find ramdisks to pack with your zlimage? can i use stock ramdisk with cyanogenmods lzimage to boot my device?
I'm not a developer and i just started learning about compiling kernels and modules etc..
STOCK ICS 4.03 is VERY SLOW even with nothing installed..
I hoped that Cyanogenmod 10 would run better on my device that's why i started all this but i'm seriously stuck...
Thanks in advance!!