Samsung does this in the macloader service,
but this is the more appropriate place for
our platform.
Change-Id: I6335fea1d73d48f3c3f9938f33b536c5cda52acb
if a kernel device returns an I/O error, it is better not to chew
the CPU resources retrying I/O operation on a not ready device.
Fixes periodical 100%-core load in audioserver after a voice call
completion.
Change-Id: I2b66ffd18c85823a11e50598a6b4e3c0245a0083
The all_ranges structure has one entry less than MAX_TYPES because
semcove type is not defined there, but there's no check for NULL and if
the mac isn't found it segfaults.
Change-Id: Ie218ea0a82b03992085db0f2d1cfc7079e7415a0
On some devices, like SM-T805 (Galaxy Tab S 10.5 LTE), the RIL client
code produces errors "SendOemRequestHookRaw: No token" due to large
amount of tokens allocated by OEM messages requiring no response from
RIL daemon (like set call audio path, set call volume, set mite etc).
The indicator of an OEM message with no response expected is:
RegisterRequestCompleteHandler(client, REQ_XXX, NULL);
inside the RIL client message method. To prevent the token pool from
overflows, the proposed patch de-registers the token and frees its call
history if the handler for this message req_id is set to NULL.
Change-Id: Id414263bf471115797cae1a9ed628249734b9347
filiprrs: This fixes miracast, and possibly resolves issues with features
like chromecast, screen recording, wifi display etc.
Change-Id: I35f789a9ae29df0198b21c98dc866d8886799893
Seems that the fast blinking notification LEDs experienced on some
Samsung devices was due to the removal of these two lines that clean
the 'blink' array. Propose re-inserting to correct the fast blinking
LED issue.
Change-Id: I88ea828a50468aae494b1dd54290607308de543a
* Because we're using #ifdef in set_light_buttons(),
defining VAR_BUTTON_BRIGHTNESS to anything, including 0,
results in the button brightness code being enabled
* That results in broken touchkey backlight for devices
that don't override the samsung_lights header, or defined
this macro to 0 in their device's samsung_lights header
* Comment out the macro to correct this logic
Change-Id: Icf554b0deac975f729f1a70e517341dae74f3657
* Try to read the hardware revision from the
bootloader before parsing /proc/cpuinfo
* Set more properties to catch all recent device
needs as well
* Introduce a property to let other services (cbd)
know they can start
Change-Id: I50d8ec37921ec2559bdd7fe852d830f10fe1c12e
AOSP power hints can have a NULL data parameter,
only our custom hints are guaranteed to provide data.
Change-Id: Ibea874e75a7092b3f9c1c56dc5182cdf73f35532
The hispeed_freq value is read only in the inizialization process.
If we decide to change it later writing a new value to the node
this new value wont be taken into consideration by the power hal.
Lets update the hispeed_freq value in the power hal before using
it to limit the max cpu freq when we go into power save mode.
Change-Id: I4b8c7f67259750b2931b18c3871874022aa6054d
* As of now the code account only max_brightness > 255
-> Check if max_brightness != 255 and apply the scaling
even if the max_brightness is less then 255
Change-Id: I809ece5844c8ccf20ae6507f23d308fe3ddfe94b
Christopher N. Hesse