1. 15 Dec, 2015 1 commit
    • jbats's avatar
      not needed · 43088b4c
      jbats authored
      Change-Id: I1bebeada27c4fb4de283760ad0d50c5cf08ff632
      43088b4c
  2. 13 Dec, 2015 2 commits
  3. 08 Dec, 2015 1 commit
  4. 01 Dec, 2015 1 commit
  5. 29 Nov, 2015 1 commit
    • Michael Bestas's avatar
      qcom: cleanup packages · 13122e51
      Michael Bestas authored
      * Remove packages that are unused, already included in build or vendor
      
      Change-Id: I7861a8236f01712d347976827058dcb371b431ce
      13122e51
  6. 18 Nov, 2015 2 commits
  7. 12 Nov, 2015 1 commit
    • Dan Pasanen's avatar
      qcom: remove setup_fs · d4045318
      Dan Pasanen authored
      * fs_mgr can set up your filesystems for you by setting the
        formattable flag in fstab
      
      Change-Id: I5c786f710eae843ff2ea14bbdbbfb4878e8a60ba
      d4045318
  8. 08 Nov, 2015 1 commit
  9. 03 Nov, 2015 1 commit
  10. 02 Nov, 2015 1 commit
  11. 28 Oct, 2015 1 commit
  12. 23 Oct, 2015 2 commits
  13. 12 Oct, 2015 1 commit
  14. 02 Oct, 2015 1 commit
  15. 27 Sep, 2015 1 commit
  16. 24 Sep, 2015 1 commit
  17. 11 Sep, 2015 1 commit
  18. 08 Sep, 2015 1 commit
  19. 31 Aug, 2015 1 commit
  20. 21 Aug, 2015 1 commit
  21. 17 Aug, 2015 1 commit
  22. 06 Aug, 2015 1 commit
  23. 05 Aug, 2015 2 commits
    • Michael Bestas's avatar
      Automatic translation import · be1d5d01
      Michael Bestas authored
      Change-Id: I81d34abe156289f05466058b4a42bbb06e202970
      be1d5d01
    • Patrick Lower's avatar
      SamsungDozeService: properly fix future timestamp error · 64e6330b
      Patrick Lower authored
      Previously attempted fix at review.cyanogenmod.org/#/c/104083/
      The timestamp isn't in the future, that would be impossible.
      The real issue is the timestamp from the SensorEvent is a true
      timestamp, the System.nanoTime is nanoseconds since boot.
      So the previous patch would always return false and never pulse.
      I've simply changed it so that the wakeup call gets sent the current
      System.nanoTime in milliseconds since boot so it does not think the
      event came from the future since the wakeUp method expects
      uptimeMillis, not true world time.
      
      Change-Id: I78f5e9d61107caf9c3bf6c10fa7c5bb400082294
      64e6330b
  24. 04 Aug, 2015 1 commit
  25. 27 Jul, 2015 1 commit
  26. 25 Jul, 2015 1 commit
    • Brandon McAnsh's avatar
      SamsungDozeService: Prevent a pm wakeup with a timestamp in the future · 86e99675
      Brandon McAnsh authored
      
      Prevents:
      
      java.lang.IllegalArgumentException: event time must not be in the future
      at android.os.Parcel.readException(Parcel.java:1550)
              at android.os.Parcel.readException(Parcel.java:1499)
              at android.os.IPowerManager$Stub$Proxy.wakeUp(IPowerManager.java:550)
              at android.os.PowerManager.wakeUp(PowerManager.java:666)
              at com.cyanogenmod.settings.device.SamsungDozeService$SamsungProximitySensor.shouldPulse(SamsungDozeService.java:95)
              at com.cyanogenmod.settings.device.SamsungDozeService$SamsungProximitySensor.onSensorChanged(SamsungDozeService.java:75)
              at android.hardware.SystemSensorManager$SensorEventQueue.dispatchSensorEvent(SystemSensorManager.java:405)
              at android.os.MessageQueue.nativePollOnce(Native Method)
              at android.os.MessageQueue.next(MessageQueue.java:143)
              at android.os.Looper.loop(Looper.java:122)
              at android.app.ActivityThread.main(ActivityThread.java:5289)
              at java.lang.reflect.Method.invoke(Native Method)
              at java.lang.reflect.Method.invoke(Method.java:372)
              at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
              at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
      
      Change-Id: I8ed248271d67216e531b124bf27101fa538f1195
      Signed-off-by: default avatarBrandon McAnsh <brandon.mcansh@gmail.com>
      86e99675
  27. 19 Jul, 2015 1 commit
  28. 12 Jul, 2015 1 commit
  29. 04 Jul, 2015 1 commit
  30. 01 Jul, 2015 1 commit
  31. 22 Jun, 2015 1 commit
  32. 20 Jun, 2015 1 commit
  33. 13 Jun, 2015 1 commit
  34. 09 Jun, 2015 1 commit
  35. 31 May, 2015 1 commit
  36. 25 May, 2015 1 commit