anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add build flag for forcing single buffer mode	Ethan Yonker	2016-08-19	1	-0/+5
\| \| \| \| \| \|	RECOVERY_GRAPHICS_FORCE_SINGLE_BUFFER := true Change-Id: Id5144ea772c3b7ae382b064c41c23acdd0decb84
*	Black screen patch for some HiSilicon devices (FBIOPAN_DISPLAY)	Muhammad Fahad Baig	2016-06-09	1	-0/+6
\| \| \| \|	Change-Id: Ib114dcc7b48219142602a2fbc256e2a0258b26e0
*	Move force_rgb_565 up.	Aaron Kling	2016-05-26	1	-21/+29
\| \| \| \| \| \| \| \|	Changes to fb_var_screeninfo can cause changes to fb_fix_screeninfo. So, write back the force changes before fi is read. Change-Id: I721a960fa401ac5203ffc90bd3bfa2d7d0cfb292
*	minuitwrp: retry opening fb0 if it failed	that	2016-02-29	1	-6/+16
\| \| \| \| \| \| \|	On some devices TWRP tries to access the framebuffer before all device nodes have been created. Retry opening instead of crashing later. Change-Id: I189a8fe80a8906b46fb6cece53c0bf83c00c0e09
*	minuitwrp: fix and hopefully speed up fbdev screen flipping	that	2016-02-19	1	-7/+16
\| \| \| \| \| \| \|	Fix: use row_bytes instead of xres (should help on Shield tablet) Speed: Moving the calculations out of the inner loop Change-Id: Ie43ae5e94ae88822360900c7b4d852b7aab4379b
*	twrp: Add support for TW_SECONDARY_BRIGHTNESS_PATH	AdrianDC	2016-02-19	1	-0/+10
\| \| \| \| \| \|	* Required for devices like Sony Huashan (dual backlighting paths) Change-Id: I0f84623431aec91fafee6617c1d4c542e4566caf
*	Change some graphics build flags	Ethan Yonker	2016-02-03	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	While not all of these old build flags are active or implemented yet (and they may not ever be implemeted until we find a device that needs them), we need to make sure that the old build flags are only applied when actually needed. Since there are a lot of device trees that probably won't get updated due to lack of device maintainers, we will rename the build flags and fix up devices on a case by case basis. Also added some pixel format related build flags to the make file from AOSP so that AOSP devices should work in TWRP without additional build flags. Change-Id: I11ab475297d02b6aeffe89404fe50b4799a36be3
*	graphics: reintroduce flipped screens for fbdev	Ethan Yonker	2016-02-01	1	-11/+29
\| \| \| \|	Change-Id: Ide3510d2efc1c1b39c756691776938e42424b61d
*	twrp: default to GGL_PIXEL_FORMAT_BGRA_8888 if vi.red.offset == 16	Ziyan	2016-01-29	1	-1/+1
\| \| \| \|	Change-Id: I436bab6ef679168d3625d8e1837917077cf89908
*	Update minuitwrp graphics in line with latest minui	Ethan Yonker	2016-01-27	1	-0/+281
	Note: events.cpp is still old code renamed to cpp to make it easier to call functions like gr_fb_width(). I had to modify AOSP fbdev code to provide a separate memory surface for drawing to as drawing directly to the framebuffer resulted in rendering taking about 5 times longer. I also modified AOSP adf code to provide a separate memory surface for drawing for the same performance reasons. The Nexus 9 supports adf graphics. Overlay graphics work on at least one device. Overlay provides a separate memory buffer already so performance is good. I do not have a drm device yet that I know of. I made some attempt to update the drm code to determine the correct pixel format based on the drm graphics format, but what is available in pixel flinger and what is available in drm do not line up all that well. Reports are that the Pixel C is using drm graphics, but performance is slow, likely due to the use of a mmap instead of a memory buffyer. Change-Id: Ibd45bccca6ac2cb826037aa9b2aa5065cf683eed