1. 09 Feb, 2012 1 commit
  2. 16 Nov, 2011 1 commit
  3. 09 Nov, 2011 2 commits
  4. 01 Nov, 2011 1 commit
  5. 26 Oct, 2011 1 commit
  6. 21 Oct, 2011 2 commits
  7. 18 Oct, 2011 4 commits
  8. 10 Oct, 2011 1 commit
  9. 03 Oct, 2011 1 commit
  10. 30 Sep, 2011 1 commit
  11. 22 Sep, 2011 1 commit
  12. 20 Sep, 2011 3 commits
  13. 16 Sep, 2011 2 commits
  14. 02 Sep, 2011 1 commit
  15. 26 Aug, 2011 1 commit
  16. 24 Aug, 2011 1 commit
  17. 22 Aug, 2011 1 commit
  18. 26 Jul, 2011 1 commit
  19. 15 Jul, 2011 1 commit
  20. 20 Jun, 2011 1 commit
  21. 26 May, 2011 1 commit
  22. 20 May, 2011 1 commit
  23. 03 May, 2011 3 commits
  24. 29 Apr, 2011 1 commit
  25. 27 Apr, 2011 4 commits
  26. 16 Apr, 2011 1 commit
    • Sahil Verma's avatar
      Added missing duration field to database record insertion. · 0508261c
      Sahil Verma authored
      
      This addresses AOSP Google Code Issue 15841.
      When an audio recording sample is saved to the media
      database, attributes like audio title are stored in a
      database record.  However, the duration of the sample
      was not being stored.  Therefore, an application that
      queried attributes for a sample would get an incorrect
      record; the record would contain a default duration of
      0 ms.  The fix was to add the recorded sample's length
      to the list of attributes put into the database record.
      Note that the sample's length is in seconds and had to
      be converted to milliseconds as described in the
      documentation for the duration audio column.
      
      This bug could have been prevented if the database
      schema for duration audio column required a non-null
      value with no default.
      
      Change-Id: I80e4f8feb7d9f1050baf1e7c44323123b9d6b6b0
      Signed-off-by: default avatarSahil Verma <vermasque@gmail.com>
      0508261c
  27. 01 Apr, 2011 1 commit