Friday, August 29, 2014

NEW BUILD! PhilZ Touch Recovery for Galaxy Player 5

I spend some time making sure all the things that didn't work in the last build work on this one. AFAIK, everything is working.

  • Screen turns on and off properly now.
  • Touch functions working properly.
  • Virtual keys working properly.
  • Physical keys working properly.
  • Aroma file manager working.
  • Can flash this recovery in your current recovery.
  • Recovery persists even if you wipe cache.

Let me know if there are any issues.

Download in the download section as always

Thursday, August 28, 2014

Galaxy Player 5: Screen Recording Crashing after 60 sec[FIX]

A while back I noticed that I trouble creating screen captures that where more that 60 seconds long on the Galaxy Player 5. I like to take Screen Captures of the ROM to show case because  when I checkout a ROM I like to make sure it has the core features that I want. So when I create a ROM it's nice to show off the Settings area so people can see, before hand, if the ROM has a particular feature. During my testing I've notice that Screen Recording seems to crash after approximately 60 seconds and for the longest time I thought it was probably a "low memory" issue with this device. In the back of my mind though, I had a theory, that I always dismissed as unlikely but recently I tried it and it worked! This is how to get screen captures for more than 60 seconds:

The key is this line:
where it says "duration=60". This file is on the device @ /system/etc/media_profiles.xml.

To change it to say... 12 minutes ( Don't know if there is any upper limit???)

  1. Make sure that /system is remounted rw.
  2. Open the file : /system/etc/media_profiles.xml
  3. Change the line :

<EncoderProfile quality="480p" fileFormat="mp4" duration="60"> 
<EncoderProfile quality="480p" fileFormat="mp4" duration="720"> 
Save and reboot.

Now you should be able to do screen recordings up to 12 minutes. Possibly camera video recording up to 12 minutes as well!


Monday, August 25, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2e

I haven't had a clock freeze issue in a while but I've recently started to understand a little more about how the time system works in android so I put in a "Clock Freeze Monitor" to check for a potential issue that could cause the status bar clock to freeze.

  • Codinalte: added Clock Freeze Monitor
  • Carbon upstream changes.
  • Fixed apps to sd.
  • Lowered Font size of cLock widget so it doesn't look "cut off"
NOTE: From now on, builds will include the device's codename in the zip filename.

Download in the download section as always.

Sunday, August 17, 2014

EXPERIMENTAL BUILD:! Carbon for Galaxy Player 5

This is an experimental build because the magnetic sensor data is not correct. I just don't know enough about it to get it working properly.

  • Upstream updates from Carbon ( HOVER out Heads Up in)
  • Enabled lockscreen widgets.
  • Fixed CRT animations
  • Orientation sensor working.
  • Magnetic sensor is um... doing something.
  • Apps 2 sd enabled and working on external sdcard.

Tuesday, August 12, 2014

NEW BUILD!: Carbon for Hisense Sero 7 Pro

  • Upstream Carbon changes.
  • Restored cpu hotplug functionality.
Download in the download section as always.

Monday, August 11, 2014

NEW BUILD!: Carbon for Galaxy Exhibit / Ace 2 e

  • Just upstream changes from Carbon

Download in the download section as always.

EDIT: To fix "Apps to SD" download the following archive and put the 2 binaries in the "/system/bin" folder, replacing the existing ones

Sunday, August 3, 2014

Notes: Thinking About Codinalte Youtube Video Quality Issues

Quick personal note: I'm feeling much better these days but the long break has caused me to loose my development "mojo". I'm doing research as to how to get it back; apparently there was someone named Stella who lost her groove and she got that back. Then there is also Austin Powers; I guess someone took his mojo and he got it back as well... so need to watch/rewatch those I guess.

In the mean time, I've been thinking about a particular problem with Codinalte AKA: Galaxy Exhibit or Galaxy Ace2e. Well, this problem seems to exist across all codina/Galaxy S3 mini variants. In the official YouTube app, video quality is quite poor. No matter how you set the settings the quality settings the video just looks bad...

Now, Codinalte can play video in other contexts just fine. Video's look great in mx player and I think you can even use the browser and get better quality on the YouTube website so it does not seem to be a question of the device not being able to render good quality video; it obviously can and that leads me to believe that this is simply a misconfiguration somewhere.

Looking at the logs I found this:

E/YouTube (32655): Could not select a stream, defaulting to itag 36

Many of you may not know this but I worked on a video app a couple(?) years ago and at that time I was very familiar with how YouTube video's work. So when I saw the term "itag" I remembered that YouTube's web clients use to request a manifest of available qualities and encodings before selecting one to stream and each one had an "itag" number. Basically it's like this: The YouTube client would figure out what types of video's could be played i.e ( mp4, webm, mpeg, avi...). Then it would download a list of available encodings for a particular video. Then compare the list until there was a match and basically go with that. So, if the client could play mp4's and there is an mp4 available then we play that one. It was a little more sophisticated than that but you get the idea.

The above error seems to indicate that the YouTube app could not find a compatible stream in the list so it's defaulting to some "lowest common denominator"

ATM: I haven't found the spot where the android frameworks provide information to apps about what types of video can be decoded... Perhaps another dev will see this and get some insight...

EDIT: I have already tried to force Codinalte to use different decoders. With the recent inclusion of FFMPEG decoders, I thought this would be a good idea. I was able to verify that I was using different decoders but the result was still bad quality video. In all actuality no notice able change what so ever.

Comments welcome...