Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/bionic e2c1351dea669ca2fc49164d386373390aa242d9..f5185cc4f1a0eba96b6fc6dc73c429e5c7dfbb89
- commit f5185cc4f1a0eba96b6fc6dc73c429e5c7dfbb89
- Author: Dirk Rettschlag <[email protected]>
- Date: Tue Feb 11 15:23:42 2014 +0100
- libm: use neon optimized sin/cos/pow/sqrt/sqrtf
- This enables the optimized functions for all devices that
- support the NEON instruction set.
- benchmark iterations Normal ns/op NEON ns/op
- BM_math_sin 10000000 126 109
- BM_math_cos 10000000 112 114
- BM_math_pow 5000000 375 328
- BM_math_sqrt 50000000 496 38
- BM_math_sqrtf 100000000 136 25
- Change-Id: I2b2ee9ab1769c994edac4a5e56eee2fafa4a37a7
- Signed-off-by: Dirk Rettschlag <[email protected]>
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/build 038b7b47a43412c2942c3b316ca130465007bcb1..2c165e5e893828bf1a1fc83c2e6e228cfe93dd90
- commit 2c165e5e893828bf1a1fc83c2e6e228cfe93dd90
- Author: dhacker29 <[email protected]>
- Date: Tue Jan 28 15:51:51 2014 -0600
- Allow devices to specify certain ro. props via TARGET_UNIFIED_DEVICE
- This modifies buildinfo.sh to not set model, name, description, and
- fingerprint in build.prop. These can then be set via custom init
- lib.
- This also fixes ota_from_target_files to function without these
- props being preset.
- Change-Id: I945b2c38e60b207d2d0f82b34f4f230ac21b0657
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/frameworks/av 0f4d10e7ea9aa431542a10d73fea372ca081e5c1..c6791bd67e0740c02adfcc3b75f6a22f33ed4d9d
- commit c6791bd67e0740c02adfcc3b75f6a22f33ed4d9d
- Author: Haynes Mathew George <[email protected]>
- Date: Mon Jan 27 11:11:19 2014 -0800
- audio: Use composition instead of multiple inheritance
- - AudioTrack is derived from BnDirectTrackClient along
- with RefBase to receive the notifications from
- AudioFlinger in tunnel/LPA mode. This is breaking
- binary compatibility for the clients which use native
- AudioTrack directly instead of Java based AudioTrack
- API
- - Fix is to use composition here instead of inheritance
- Change-Id: I9fd2c61cff5629924e3b08f63559679e0263bcfd
- commit a50273c732d068fd91438c0b3348f0944517e947
- Author: Pavan Chikkala <[email protected]>
- Date: Wed Dec 18 15:06:43 2013 +0530
- audio: Check the return code of MediaWriter::start
- - Return code of MediaWriter::start method is not checked
- in startRawAudioRecording. Due to this, sound recorder
- application is not receiving the error whenever there is
- an error in starting of the recording
- - Fix is to check the error and return it back to
- the client accordingly
- Change-Id: I15916211da7a2eb0f27fbf9d4151410a8bdfdd42
- CRs-Fixed: 591788
- commit 616521f189409a5d5c7cbd8e2fc822f09b45fc98
- Author: Naresh Tanniru <[email protected]>
- Date: Mon Dec 16 21:21:10 2013 +0530
- Audio: Tunnel Exception for ER AAC ELD profile format
- - some m4a clips are not working properly
- - ADSP audio decoders don't support ER AAC ELD support
- - Added tunnel exception for ER AAC ELD format.
- Added AACProfile metadata support for MKVExtractor
- Change-Id: I2f6fe721b05377dfe0f24ea0ad1f6c4a885d576d
- commit 7be41518c3b60399cade17783497784f65268fb9
- Author: Nitesh Bhardwaj <[email protected]>
- Date: Fri Dec 13 11:24:37 2013 +0530
- audioflinger: Add Null pointer check while enabling effects for LPA
- - MediaServer is crashing when disabling effects after mediaplayer
- object is released.
- - EffectChain pointer is de-referenced without NULL check, hence
- leading to a mediaserver crash.
- - Adding a NULL pointer check before using EffectChain object.
- Change-Id: If5ff469445246028046ba65e5ddf3300180318c2
- CRs-Fixed: 583305
- commit 5668f2403e055feadb8a89b5277bb1c6ae5d85f5
- Author: Phani Kumar Allada <[email protected]>
- Date: Thu Sep 27 18:21:54 2012 +0530
- framework/av: Fix for frame drop in video playback
- - Breaks in video playback seen in video clips having audio content
- with sampling rates less than 16kHz.
- - While extrapolating real time with system time, the real time is wrongly
- caped.
- - Fix this issue by limiting the extrapolated real time only when EOS
- is reached.
- Change-Id: I95b6a8f7f1f1fd561c92955cf52151ae2890c9a7
- CRs-Fixed: 400398
- commit 8bcbb487b7de4c2aaae95d461a39b64f0ea9f590
- Author: wjiang <[email protected]>
- Date: Tue Oct 29 22:22:16 2013 +0800
- audio: Supress redundant effect config events in short duration
- Distortion sound persists for the whole song when re-enabling effect in
- LPA playback mode till switch to next song. And pop noise is quite obvious
- when enable/disable effects in LPA.
- As the design of LPA, EffectsThreadEntry() loop is used to handle effect
- config changes through applying effects with new config on dsp pcm buffers.
- However, it can't handle too many config change events in a short time,
- and effect with new configuration will be applied on part of dsp buffers.
- Filter out redundant effect config events that come too closely to avoid
- applying effect on dsp buffer in vain.
- Change-Id: If8915b1d068724d5976e1519ec57e3c08cf89c9d
- CRs-Fixed: 562806, 563418
- commit 9fc34ac64181a9c1745c6a392bb02285f2a6a047
- Author: Sharad Sangle <[email protected]>
- Date: Tue Nov 5 18:08:24 2013 +0530
- audioflinger: SRS effects are not working for LPA
- -Issue: If SRS effects are applied on LPA playback,
- in ARM side there is a delay of 4-5 seconds for effects
- application
- -Root cause: In applyEffects SRS effects are applied first and
- then Android effects are applied.
- In case of active android effects, SRS effects are called
- first and then android effects are called, so buffer with
- SRS effects is getting overwritten with buffer with
- android effects.
- If there are no android effects applied then all
- the SRS effects are overwritten with decoded data.
- So until next write call, SRS effects are not applied and hence delay
- of 4-5 seconds
- -Fix: In applyEffects first apply android effects and then
- apply SRS effects
- Change-Id: I36b2133256d168f06b13c3d4a2bad00312d571ac
- CRs-Fixed: 566278
- commit 1b37c78b7709e6958885e3d2fdeaab45ba64d6dd
- Author: Eric Laurent <[email protected]>
- Date: Fri Nov 15 12:02:28 2013 -0800
- audioflinger: do not use raw pointer for tracks
- Commit 9da3d95 surfaced a problem caused by the use of a raw
- pointer to a track in offload thread implementation.
- Pointers to tracks should always be weak or strong pointers.
- Bug: 11708529.
- Change-Id: Ic48632532d186c9be8261f73cefdf824b9fbbd2b
- commit 2d844ce6dc3b3558dabe67bd0607042eb0685bb8
- Author: Shashank Mittal <[email protected]>
- Date: Tue Sep 3 10:58:10 2013 -0700
- media: Add Ops check before starting audio recording.
- Confirm user permission before starting audio recording.
- Change-Id: Ia4e6d8fb6986d4e73fb656ba0efaf42c210e92af
- commit 4dfe626b6f3e4b80e71c01fc39d9e3c9b16b0ef0
- Author: wjiang <[email protected]>
- Date: Wed Oct 16 14:41:54 2013 +0800
- framework/av: Check for NULL pointer of mCblk and zero division error
- latency calculation happens in two places: AudioTrack::latency() and
- AudioTrack::dump(). Need to add null pointer and zero division check on
- both of these places.
- Change-Id: I9cbe8c1c00a390cd626bdbf202124f27e60eb3e3
- Fixed-CRs: 548514
- commit af8b665c1ab2eeb1d0e964684043590522082f3d
- Author: Divya Narayanan Poojary <[email protected]>
- Date: Fri Nov 15 15:16:48 2013 +0530
- frameworks/av: Mediacodec initialization check in QCUtils
- - Mediaserver crash is observed while playing wma10pro clips
- on MM stability stress
- - 8x10 device is not supporting wma10pro format from openmax
- which is resulting component creation fail.
- However in this case multiaac decoder component is creating
- which is resulting crash
- - On QCUtils::helper_addMediaCodec without intialzing the codec
- we are trying to add codec capabilities which is resulting wrong
- codec capabilities to assign for multiaac decoder
- Added initializarion & flags check to fix the issue
- Change-Id: I8a61d658bcbebf53a59a30bd6d812b4dafec46c6
- CRs-Fixed: 552817
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/frameworks/base d6a6cd6c6fb8ed5fa2c5363881f72a907ce2109c..5127fbb6e37377e121814df20eb5f3ab3f55cda8
- commit 5127fbb6e37377e121814df20eb5f3ab3f55cda8
- Author: Daniele Di Conza <[email protected]>
- Date: Thu Jan 16 10:37:41 2014 +0100
- SUPL early data connection fix
- if GPS started before data connection is alive, SUPL will be broken for entire power cycle.
- Change-Id: I0486ac5e62a2d4a7da14506e3dd8e78da42f405d
- commit 9f5f243b433010d6d9910dcf52c396d7e5bad7d3
- Author: Nilesh Poddar <[email protected]>
- Date: Fri Jan 17 11:13:17 2014 -0800
- Release wakelocks acquired by SyncManager
- Release the wakelocks internally acquired by SyncManager to improve
- power performance.
- Change-Id: I6d9663292cb4471d92ed9132beb7ed1ba2e8128f
- CRs-Fixed: 585825
- commit b8db689c03949b67b5760263606f7bd53c526531
- Author: Guntawee Tiwapong <[email protected]>
- Date: Thu Dec 12 12:29:23 2013 -0800
- server: Handle broadcast intent and receiver
- Ensure the receivers of broadcast intent is not launched before boot
- completion by adding an intent flag, since connectivity events can
- happen before boot has completed.
- Change-Id: Id6fc9e34c89d947d768def38e5c5bb0df54a3a7b
- commit d3132b3227030f614f3f1cdcad3fe54976a75e74
- Author: Jorge Ruesga <[email protected]>
- Date: Wed Feb 12 02:05:08 2014 +0100
- base: fix battery stats
- * Fix IBatteryStats.aidl posititions. BatteryService.cpp from hardware sensors uses a position token
- from the binder. The dock battery patch broke this order, causing sensor stats to be send to
- wakelock stats, causing a breakage in the partial wakelock counter.
- * Create a separate dock stats implementation to avoid collision in the internal statics variables
- of the normal stats implementation.
- Change-Id: I22c92d5941804449668530715bf5381b00164593
- JIRA: CYAN-3127
- Issue: https://jira.cyanogenmod.org/browse/CYAN-3127
- Signed-off-by: Jorge Ruesga <[email protected]>
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/hardware/libhardware_legacy 107fcb3eeb34b5d4c4a7216dc712a107623533ab..7a133590ff567fe09b7f415371c78480d39a83e7
- commit 7a133590ff567fe09b7f415371c78480d39a83e7
- Author: Steve Kondik <[email protected]>
- Date: Sat Jan 25 22:12:58 2014 -0800
- audio: Fix check for sonification on digital docks
- Change-Id: If077bc6336ce57256dd078d0cbe80c3b5e3a0b6e
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/hardware/ril 6ca77e7b9c8c306ab80e574d6d6bacb341760b71..681cd4de0b999eee8fc8d9c52c69ee46c810168d
- commit 681cd4de0b999eee8fc8d9c52c69ee46c810168d
- Author: Alex Yakavenka <[email protected]>
- Date: Wed Dec 4 13:54:37 2013 -0800
- Send unsol_sim_status on radio_state change
- Sim status changes based on radio state.
- Need to notify new sim state whenever radio state changes
- Change-Id: I8fef3a6ddf601647107e3059f2b2eb89a67242cf
- commit 6e803ab428b72f0ad61272b12d9e6104e39dbdf5
- Author: Colin Cross <[email protected]>
- Date: Fri Jan 24 17:02:19 2014 -0800
- Set USE_NP based on HAVE_PTHREAD_COND_TIMEDWAIT_RELATIVE
- 64 bit bionic does not define pthread_cond_timeout_np, use
- HAVE_PTHREAD_COND_TIMEDWAIT_RELATIVE to determine whether or
- not to use it.
- Change-Id: Ia94dd76f7ea4b0268f07049c127342a8bd016ec0
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/hardware/ti/wlan 352b51297be9bcf268f9f66eaf5c323cc11327b7..cb0a5534c1cb95772cbd770849198fa68e21c7f3
- commit cb0a5534c1cb95772cbd770849198fa68e21c7f3
- Author: Michael Bestas <[email protected]>
- Date: Wed Nov 20 08:22:06 2013 +0200
- Use AOSP version of wpa_supplicant_lib
- Squashed commit of the following changes:
- Update make file for new location of libnl
- Change-Id: If93aea9913cfa263fb228feb27137ac16b78cf0a
- Signed-off-by: Mike Lockwood <[email protected]>
- wpa_supplicant_lib: Use common file from hardware_legacy
- Change-Id: Ibbf60918848ab02dbc1b985005f986ab63d4dc52
- Signed-off-by: Dmitry Shmidt <[email protected]>
- wpa_supplicant_lib: Clean the code and fix the build
- Change-Id: I6a916c2f9306a49951dbba7bda5793d389899f91
- Signed-off-by: Dmitry Shmidt <[email protected]>
- Also cleans up the files to bring them inline with AOSP
- Change-Id: I4a1dc7b25abda0254c18677e7e9a6651a920b05f
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/kernel/archos/archos_g9 eb25864ce086ac67dc3e8fb72b9350baed6b7bb3..39bf0849c05d6093897e1b079e2ca0c47dc0bd54
- commit 39bf0849c05d6093897e1b079e2ca0c47dc0bd54
- Author: Michael Gernoth <[email protected]>
- Date: Wed Jan 22 00:01:14 2014 +0100
- sync struct wl12xx_platform_data to hardware/ti/wlan
- this stops the wlan-driver from accesing memory outside
- of its platform-data
- Change-Id: I6e0f1920d3f8528cef3528d4989c9626507aa422
- commit 45634ec9230e9a16790e5c1a8702e785c38cf81f
- Author: Matt Wagantall <[email protected]>
- Date: Wed Jul 17 06:53:08 2013 +0000
- net: flow: Prevent bringing up new CPUs during per-CPU initialization
- In a rare race-condition, it's possible that a CPU will be brought
- online between when the for_each_online_cpu() loop executes to
- call flow_cache_cpu_prepare(), and when the hotplug notifier for
- calling this same function is registered. If this happens,
- flow_cache_cpu_prepare() will never be called for the new CPU,
- resulting in crashes due to uninitialized per-cpu data.
- Fix this by preventing CPUs from being added or removed during
- this small but sensitive window.
- Change-Id: Iafbbaa8a50e5c527392d130561874313720849d0
- Signed-off-by: Matt Wagantall <[email protected]>
- Conflicts:
- net/core/flow.c
- commit 43bb6f26e71347c6cd4d5e832b9ba2b6d7ce0ebf
- Author: Junxiao Bi <[email protected]>
- Date: Wed Sep 11 14:23:04 2013 -0700
- writeback: fix race that cause writeback hung
- There is a race between mark inode dirty and writeback thread, see the
- following scenario. In this case, writeback thread will not run though
- there is dirty_io.
- __mark_inode_dirty() bdi_writeback_workfn()
- ... ...
- spin_lock(&inode->i_lock);
- ...
- if (bdi_cap_writeback_dirty(bdi)) {
- <<< assume wb has dirty_io, so wakeup_bdi is false.
- <<< the following inode_dirty also have wakeup_bdi false.
- if (!wb_has_dirty_io(&bdi->wb))
- wakeup_bdi = true;
- }
- spin_unlock(&inode->i_lock);
- <<< assume last dirty_io is removed here.
- pages_written = wb_do_writeback(wb);
- ...
- <<< work_list empty and wb has no dirty_io,
- <<< delayed_work will not be queued.
- if (!list_empty(&bdi->work_list) ||
- (wb_has_dirty_io(wb) && dirty_writeback_interval))
- queue_delayed_work(bdi_wq, &wb->dwork,
- msecs_to_jiffies(dirty_writeback_interval * 10));
- spin_lock(&bdi->wb.list_lock);
- inode->dirtied_when = jiffies;
- <<< new dirty_io is added.
- list_move(&inode->i_wb_list, &bdi->wb.b_dirty);
- spin_unlock(&bdi->wb.list_lock);
- <<< though there is dirty_io, but wakeup_bdi is false,
- <<< so writeback thread will not be waked up and
- <<< the new dirty_io will not be flushed.
- if (wakeup_bdi)
- bdi_wakeup_thread_delayed(bdi);
- Writeback will run until there is a new flush work queued. This may cause
- a lot of dirty pages stay in memory for a long time.
- Signed-off-by: Junxiao Bi <[email protected]>
- Reviewed-by: Jan Kara <[email protected]>
- Cc: Fengguang Wu <[email protected]>
- Signed-off-by: Andrew Morton <[email protected]>
- Signed-off-by: Linus Torvalds <[email protected]>
- Signed-off-by: Francisco Franco <[email protected]>
- Change-Id: I973fcba5381881a003a035ffff48f64348660079
- Signed-off-by: Quallenauge <[email protected]>
- Conflicts:
- fs/fs-writeback.c
- commit 48c726a266853d47454a7f963410d2cc53ae6861
- Author: Felix Fietkau <[email protected]>
- Date: Fri May 4 21:08:33 2012 -0700
- timer: optimize apply_slack()
- __fls(mask) is equivalent to find_last_bit(&mask, BITS_PER_LONG), but cheaper.
- find_last_bit was showing up high on the list when I was profiling for stalls
- on icache misses on a system with very small cache size (MIPS).
- Signed-off-by: Felix Fietkau <[email protected]>
- Signed-off-by: edoko <[email protected]>
- Change-Id: I8a5021a2fb2936c00ffd456663a76cb1b23e3100
- commit 8260d44edd59ee04445d20405dc45c3ae28128f9
- Author: Jan Kara <[email protected]>
- Date: Fri Jul 12 17:30:07 2013 +0200
- writeback: Fix occasional slow sync(1)
- In case when system contains no dirty pages, wakeup_flusher_threads()
- will submit WB_SYNC_NONE writeback for 0 pages so wb_writeback() exits
- immediately without doing anything. Thus sync(1) will write all the
- dirty inodes from a WB_SYNC_ALL writeback pass which is slow.
- Fix the problem by using get_nr_dirty_pages() in
- wakeup_flusher_threads() instead of calculating number of dirty pages
- manually. That function also takes number of dirty inodes into account.
- Change-Id: I458027ae08d9a5a93202a7b97ace1f8da7a18a07
- Reported-by: Paul Taysom <[email protected]>
- Signed-off-by: Jan Kara <[email protected]>
- Signed-off-by: Quallenauge <[email protected]>
- commit 3ddc205c9aa0c3c19e26611923f516aee8e6cfc7
- Author: Namjae Jeon <[email protected]>
- Date: Wed Jan 2 20:00:40 2013 -0600
- writeback: fix writeback cache thrashing
- From: Namjae Jeon <[email protected]>
- Consider Process A: huge I/O on sda
- doing heavy write operation - dirty memory becomes more
- than dirty_background_ratio
- on HDD - flusher thread flush-8:0
- Consider Process B: small I/O on sdb
- doing while [1]; read 1024K + rewrite 1024K + sleep 2sec
- on Flash device - flusher thread flush-8:16
- As Process A is a heavy dirtier, dirty memory becomes more
- than dirty_background_thresh. Due to this, below check becomes
- true(checking global_page_state in over_bground_thresh)
- for all bdi devices(even for very small dirtied bdi - sdb):
- In this case, even small cached data on 'sdb' is forced to flush
- and writeback cache thrashing happens.
- When we added debug prints inside above 'if' condition and ran
- above Process A(heavy dirtier on bdi with flush-8:0) and
- Process B(1024K frequent read/rewrite on bdi with flush-8:16)
- we got below prints:
- [Test setup: ARM dual core CPU, 512 MB RAM]
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 56064 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 56704 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84720 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 94720 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 384 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 960 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 64 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92160 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 256 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 768 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 64 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 256 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 320 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 0 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92032 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 91968 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 192 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 1024 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 64 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 192 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 576 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 0 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84352 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 192 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 512 KB
- [over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE = 0 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92608 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92544 KB
- As mentioned in above log, when global dirty memory > global background_thresh
- small cached data is also forced to flush by flush-8:16.
- If removing global background_thresh checking code, we can reduce cache
- thrashing of frequently used small data.
- And It will be great if we can reserve a portion of writeback cache using
- min_ratio.
- After applying patch:
- $ echo 5 > /sys/block/sdb/bdi/min_ratio
- $ cat /sys/block/sdb/bdi/min_ratio
- 5
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 56064 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 56704 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84160 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 96960 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 94080 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 93120 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 93120 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 91520 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 89600 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 93696 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 93696 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 72960 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 90624 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 90624 KB
- [over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 90688 KB
- As mentioned in the above logs, once cache is reserved for Process B,
- and patch is applied there is less writeback cache thrashing on sdb
- by frequent forced writeback by flush-8:16 in over_bground_thresh.
- After all, small cached data will be flushed by periodic writeback
- once every dirty_writeback_interval.
- Change-Id: I678b30a5a28ed99bed0e782e38926ba4626b86ee
- Suggested-by: Wanpeng Li <[email protected]>
- Signed-off-by: Namjae Jeon <[email protected]>
- Signed-off-by: Vivek Trivedi <[email protected]>
- Signed-off-by: Quallenauge <[email protected]>
- Conflicts:
- fs/fs-writeback.c
- commit 25d434fb1ef7f64dde1de297f36eef680a364d7e
- Author: Quallenauge <[email protected]>
- Date: Tue Feb 11 23:59:13 2014 +0100
- Let the twl driver know, that there is a specific archos battery driver available.
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/packages/apps/Camera2 42067bbce2203088e09039169b0262691dd07e97..33a19d784bc8b051ccef05ce56a85d7ca1088b9c
- commit 33a19d784bc8b051ccef05ce56a85d7ca1088b9c
- Author: Lars Greiss <[email protected]>
- Date: Sun Feb 2 03:09:22 2014 +0100
- Camera2: tweak volume key zoom and cleanup
- - cleanup unused code
- - cleanup codestyle
- - add more zoom steps for smother zooming
- - show zoom circle indicator during zoom
- Change-Id: I5214fc2620a0c5167bfdc8e85f7115966c3b8bcf
- commit 942890667aa08cc3c1305d7ba64c1340df1219db
- Author: Lars Greiss <[email protected]>
- Date: Sat Feb 1 05:16:28 2014 +0100
- Camera2: add option to prevend autofocus cancel if preview stopped
- There are camera HALs which cannot handle the autofocus cancel call if the preview
- stopped in startPreview(). Add an option for this HAL's to do not cancel autofocus in this cases.
- Change-Id: I0767cc7279405d17afc0b00120cb43e5bb309220
- commit 8c66953d26640d205a974d1f100a1cea98057326
- Author: Lars Greiss <[email protected]>
- Date: Wed Jan 15 05:08:26 2014 +0100
- Camera2: fix possible NPE on configurationchange
- Step to reproduce:
- - open camera from lockscreen
- - during it opens turn your phone
- - result: crash
- Due that the camera is in middle of the initialization mParameters
- is null at this point. Just check against null to prevend the crash.
- The correct resizing happens so or so during the ongoing initialization
- Thanks TJKV from xda for the report
- Change-Id: I0aab385172d7ff571adf525004305fd3b34d499c
- commit 2fae069ed775750fde89f6556dedac8a1bfe3df9
- Author: Lars Greiss <[email protected]>
- Date: Sat Jan 4 15:30:19 2014 +0100
- Camera2: actually fix ArrayAdapter on MoreSettingsPopup
- Like CAF already discovered googles attempt to handle the
- ArrayAdapter listview does not work as expected if the scroll view
- is larger then the screen. CAF tried to fix it with this commit on landscape
- view
- https://github.com/SlimRoms/packages_apps_Camera2/commit/c5b0bfcf2340f02ca65ad3d8c08b5c7d74776ea1
- which is only a dirty workaround fix for the actual root cause and only works
- on landscape partly and if the complete layout is loaded new completly not.
- Whatever to fix it we need to override and set getItemViewType(int)
- and getViewTypeCount() to actually allow to handle propper two row
- layouts like it is needed in MoreSettingsPopup (either checkbox layout
- or menu layout). The actual detection which type of preference
- we need is handled in getItemViewType.
- Change-Id: I6b48ca83daa5f10a7783dfa29c63e9c0bc562167
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/packages/apps/Contacts 8310831e5de6894ebc1b3176c211ab593cd4b618..74bbd34794b6a455d9a4b4f27f67dfed10c08bd6
- commit 74bbd34794b6a455d9a4b4f27f67dfed10c08bd6
- Author: Jorge Ruesga <[email protected]>
- Date: Sun Feb 9 03:25:06 2014 +0100
- contacts: Add support for import contacts to local phone storage
- This change allow to select the local storage account to add/import contacts
- when others cloud/corporate accounts exists. If one or more account exists just
- ask the user to select the destination account
- Depends on: http://review.cyanogenmod.org/#/c/59353/
- Change-Id: Ic055bdb09d037c2f2cdff06cd9a0159df87e2896
- JIRA: CYAN-391
- Issue: https://jira.cyanogenmod.org/browse/CYAN-391
- Signed-off-by: Jorge Ruesga <[email protected]>
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/packages/apps/ContactsCommon 65994eb578d656252c749aaa86b3198a23022b0b..162a1345f14753648063bdb76fc335f321e9bdd7
- commit 162a1345f14753648063bdb76fc335f321e9bdd7
- Author: Jorge Ruesga <[email protected]>
- Date: Sun Feb 9 03:23:42 2014 +0100
- contacts-common: Add support for import contacts to local phone storage
- This change allow to select the local storage account to add/import contacts
- when others cloud/corporate accounts exists. If one or more account exists just
- ask the user to select the destination account
- Depends on: http://review.cyanogenmod.org/#/c/59352/
- Change-Id: I0120861479a4dcced11a430803513fc21a2e130b
- JIRA: CYAN-391
- Issue: https://jira.cyanogenmod.org/browse/CYAN-391
- Signed-off-by: Jorge Ruesga <[email protected]>
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/packages/apps/Settings ae175cfe7f198d544b424a9e43cf21c97be93e44..651bd3bc65294f85e023068a7664c3f411e678ef
- commit 651bd3bc65294f85e023068a7664c3f411e678ef
- Author: Jorge Ruesga <[email protected]>
- Date: Wed Feb 12 01:04:24 2014 +0100
- settings: fix battery stats
- * Use the new dock stats parcelable creator
- Change-Id: I4f1ac0b2b7181f0c9c023795acf1671f7b9e9820
- JIRA: CYAN-3127
- Issue: https://jira.cyanogenmod.org/browse/CYAN-3127
- Signed-off-by: Jorge Ruesga <[email protected]>
- -----------------------------------------------------------------
- /storage1/Android/cyanogen_mod_bundle11.0/cm-11.0/vendor/cm ae9bff6bc2d5bd698c06414b0677158370cf64d4..ed80aaf56f3f0bae7743f96b98ad0854df29a6b1
- commit ed80aaf56f3f0bae7743f96b98ad0854df29a6b1
- Author: Arne Coucheron <[email protected]>
- Date: Sun Feb 9 04:31:46 2014 +0100
- Cleanup and consolidate APNs for providers using Telenor NO network
- * Remove "Telenor MMS" - Was merged into "Telenor" in a previous patch
- * Rename Ludo to Ventelo - Ludo doesn't exist anymore
- * Merge "Mobitalk Internet" and "Mobitalk MMS" into a single APN
- Change-Id: I77ff06d6c8d6021cd1887468bbeb7ac9315e68bb
Advertisement
Add Comment
Please, Sign In to add comment