I am finding a ROM that supports the feature of Suspend Execution for Cached Apps.
Only rom I've seen it on is nameless aosp, and I believe it's only for one plus devices
Related
I saw that many users had questions about the ksm module in the mildwild oxy topic.
This is what google tells me:
KSM: The Kernel SamePage Merging (KSM) module is used by the KVM hypervisor to allow KVM guests to share identical memory pages. The pages shared are usually common libraries or other identical, high-use data. KSM can increase the performance of certain guests by keeping these libraries in cache for various guests as well as increasing guest density.
Translated in to our android phone, what does this mean? What happens if i activate this module, and what will be the benefits ?
It will reduce the RAM used by the phone, so it can avoid you to use a swap partition.
Those who are still wondering what ART is....
Just watch this video
https://www.youtube.com/watch?v=U5oliXcOqxg&feature=youtube_gdata_player
I AM NOT POSTING THIS AS FOR PROMOTION OF ANY CHANNEL OR ORGANIZATION ....IT IS JUST FOR INFORMATION O
D5+/cm10.2/1.2GHz.
Sent from Tapatalk app
coolshahabaz said:
Those who are still wondering what ART is....
Just watch this video
https://www.youtube.com/watch?v=U5oliXcOqxg&feature=youtube_gdata_player
I AM NOT POSTING THIS AS FOR PROMOTION OF ANY CHANNEL OR ORGANIZATION ....IT IS JUST FOR INFORMATION O
D5+/cm10.2/1.2GHz.
Sent from Tapatalk app
Click to expand...
Click to collapse
In words,
Dalvik Runtime is being replaced with next generation ART (android runtime) in Android 5.x or later. Google has introduced it now so that developers can start testing their apps with it.
The older Dalvik uses what is called JIT runtime compiler which basically compiles java dex code to optimized native code (C binary) at the runtime.
The next gen ART uses AOT (Ahead of time) compiler which optimizes and converts java/dex code to Native during installation (ahead of time).
Both have their pros and cons, but overall AOT is faster than JIT. AOT is better at doing fast things really fast e.g. Scrolling a page in app (list, images, webview, etc) would be faster with AOT (used by ART), less often it would need to reclaim memory (GC -> garbage collector) vs. JIT.
JIT used by Dalvik has added advantages of being able to optimize java/dex code to native better, but it takes time to do so.
Overall ART should give faster launch times, smoother scrolling and better battery. Its still in alpha stage, we probably will see ART in Android 5.0 L-release doing wonders.
Enable ART on any Stock ROM
But hey, from what I've read, ART pre-compiles the apps, and thus they don't need to run on a VM anymore. Isn't that right? But one advantage of VM is that apps are seperated from each other and the system. Thus app crashes, malware and virusses don't affect the system. So... if you are using ART, will the system now become more vulnarable? Are we gonna need virus scanners for real now with ART?
hello guys,
i was watching this video : http://www.youtube.com/watch?feature=player_embedded&v=sONcojECWXs and that guy mentioned that android 4.4 (kitkat) will run as intended on "devices with as little as 512 ram".
i don't know much about android development, but is it possible we could have a ported AOSP 4.4 for one v ?
Edit:
I found this also. I think it looks awesome!
KItKaT 4.4 Specs
1.Screen Recording
2.Tap to Pay {Google Wallet for everyone}
3.NFC emulation for non nfc devices
4.14% less memory usage
5.Minimum Ram required is 512mb
6.chrome, youtube takes 12%less memory
7.cloud printing from Gallery {Print your photos directly to ur home Printer}
8.Webview is Now Chromium
9.Google Home is the new Launcher
10.New 'Google Home' works only with Google Search app installed
11.Core System Processes Trimmed
12.Apps are efficient and responsive on all devices
13.The all new 'procstats tool details' memory use
14.Payments without needing Secure Elements
15.Printer manufacturers can use new APIs to develop their own print services
16.A new storage access framework allows browse all document storage providers.
17.ART runtime compile support along with dalvik VM {faster runtime}
18.Dalvik JIT code cache tuning, kernel samepage merging (KSM), swap to zRAM
19.Use less heap,Aggressively protect system memory from apps
20.When multiple services start at once —Android now launches the services serially
21.hardware sensor batching
22.Step Detector and Step Counter
23.shared SMS provider and new APIs
24.Full-screen Immersive mode
25.Transitions framework for animating scenes {animate changes to your UI on the fly}
26.Translucent system UI styling
27.Enhanced notification access
28.seamless change in resolution during media playback
29.Common Encryption for protected content
30.HTTP Live Streaming
31.Audio Tunneling to DSP dramatically improve battery life
32.Nexus 5 offers a total off-network audio playback time of up to 60 hours
33.Audio monitoring peak and RMS levels of any currently playing audio
34.Loudness enhancer increase the loudness of spoken content
35.Audio timestamps for improved AV sync
36.Wi-Fi CERTIFIED Miracast
37.RenderScript Compute improves Ongoing performance
38.RenderScript in the Android NDK
39.GPU acceleration for any apps using render script
40.GLES2.0 SurfaceFlinger
41.New HWComposer 1.3 support for virtual displays
42.Bluetooth HID over GATT (HOGP) support
43.Bluetooth MAP support
44.built-in IR blasters, along with a new API and system service
46.Wi-Fi TDLS support seamless way to stream media in same wifi network
47.System-wide settings for closed captioning { appscan show captions}
48.SELinux (enforcing mode)
49.Improved cryptographic algorithms ECDSA
50.Designed to run fast, smooth, and responsively on a much broader range of devices than ever before
51.Phone dialer got local business detection
52.Smart caller ID
53.SMS support for Hangout
54.Emoji support on Google keyboard
55.Redigned Quickoffice
56.100gb Google drive Storage Coming soon
57.Updated Google Apps
58.Faster smoother,brilliant google voice search
59.swipe left for Google now on Google Home
60.Full Screen AlbumArt on lockscreen
I know that you're probably excited about this but it's already been discussed in several threads. Why start yet another one on the same topic?
Sent from my One V using xda app-developers app
mrcorey said:
I know that you're probably excited about this but it's already been discussed in several threads. Why start yet another one on the same topic?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
ehm, i searched on the forums and i did not find any post about this
http://forum.xda-developers.com/showthread.php?t=2505875
http://forum.xda-developers.com/showthread.php?t=2517974
And one of our devs is working on it for CDMA already:
http://forum.xda-developers.com/showthread.php?t=2536276
Sent from my One V using xda app-developers app
it is possible but not all features can be implemented. If only someone(like me who wants to bake) had a good internet plan to download those huge sources to bake the rom.
mrcorey said:
http://forum.xda-developers.com/showthread.php?t=2505875
http://forum.xda-developers.com/showthread.php?t=2517974
And one of our devs is working on it for CDMA already:
http://forum.xda-developers.com/showthread.php?t=2536276
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
sorry man, i did not find them, i guess i did not search well enough, i apolagise.
Just reading up on Samsungs DVFS implementation. If I run custom clock settings and guvnors, does the DVFS still take priority?
I'm currently going through a major refresh of my tablet and am trying to establish what I should and should not be including.
I'll be running Civ's flexbeam and SphereXtreme but couldn't see any reference to DVFS on those threads.
hertsjoatmon said:
Just reading up on Samsungs DVFS implementation. If I run custom clock settings and guvnors, does the DVFS still take priority?
I'm currently going through a major refresh of my tablet and am trying to establish what I should and should not be including.
I'll be running Civ's flexbeam and SphereXtreme but couldn't see any reference to DVFS on those threads.
Click to expand...
Click to collapse
I used the same setup... found stock with minimal mods to work just as good and have better capabilities with SD card and being OTA compliant for updates as well. I also had tested the DVFS disable with the the mods done in Civato's rom and kernel. No issues, both with his setup and my setup, and in stock rom as well.
Speed improvement was not too well missed.
I use the pro version of TweakterMod on the OEM ROM only to double the read ahead buffer for best speed with 633x SD cards.
Later on when developing gets better for a truly compatible Samsung kernel, I can use my pro version to its capabilities.
I have a few replies on battery consumption and workarounds along with a few threads as well for both SD and power battery issues.
Hi,
I have tried lot of custom roms such as 5.1.x AOSP based.
I noticed a major things. Original Samsungs rom's background process limit is very agressive, quickly kills unused app. When I tried to reopen backgrounded application it's starts to load again.
However 5.1.x AOSP based roms are not have this issue. Background process limit is responsive! They keep lot of application in background and result is when call backgrounded application, it is never load again! I'm still using Ironrom but this background procces limit is very teaser .
Is there any ways to increase background process limit?
You need to modify the OOM (Out of memory) settings. Apps are put into 6 groups of priority. The priority group a particular app is put in determines when an app will be killed.
For instance the launcher will be in group 1 or 2, group 1 being the last to be killed.
Doesn't Ironrom already let you do this with stweaks?
You can do it via terminal or scripts such as v6 supercharger.
Also there are xposed modules that can do it and apps such as 3c toolbox. Just have a look for memory management apps.