Develop Bugs

Zip align

What does zip aligning apps accomplish? Been wondering this for awhile.
Sent from my Incredible 2 ReMix using XDA Premium App

could have googled this,it's compressing the apk which tries to increase it's performance

I don't see how compressing would increase performance unless its able to read the compressed data without decompressing? Strange

fridgid said:
I don't see how compressing would increase performance unless its able to read the compressed data without decompressing? Strange
Click to expand...
Click to collapse
It doesn't make sense because that's not what it does. What it does do, if my understanding is correct, is rearranges the .apk files so that they begin on the front side of blocks of storage space, rather than in the middle or end,where the OS would be forced to read through those blocks for the required data before execution. Android uses just-in-time compiling and this entails a certain delay before execution can begin. The dalvik cache is supposed to alleviate some of that delay, assuming executable code is available. Zipaligning together with correct memory management and a current dalvik cache, in theory, should provide a very fluid user experience. Tools such as aggressive garbage collection and task killers will destroy that. If you're running apps that are abusively using system resources, the better solution is finding a better app, not managing it's poor behavior.

Thanks for the replies, I pick loonatik. At least for now.
Sent from my Incredible 2 ReMix using XDA Premium App

trouble shooting slowness

Maybe someone already asked but I couldn't find it. I've had my rooted Inc for about 4 months and still trying Roms out. However whatever rom I use, except cm7, I get some lag. Some slow load times and such when I unlock or open a new app. I'm just curious if its an Inc problem, a sense problem, or maybe my hardware was ddamaged. I bought the phone refurbished from verizon
Sent from my ADR6300 using XDA App

infidelmatt said:
Maybe someone already asked but I couldn't find it. I've had my rooted Inc for about 4 months and still trying Roms out. However whatever rom I use, except cm7, I get some lag. Some slow load times and such when I unlock or open a new app. I'm just curious if its an Inc problem, a sense problem, or maybe my hardware was ddamaged. I bought the phone refurbished from verizon
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
If it was a hardware issue, even CM7 would show it. Sense ROMs have a lot going on, especially when you go to unlock the screen. Some kernels will switch governors to Performance as soon as the screen is turned on and until it's unlocked. Scripts can be written to accomplish this in most kernels.
Certain widgets, such as the SetCPU widget, will bring things to a grinding halt with the graphics. I can't tell you why, but I've used a few apps where the widget for it was whacky like that.
Newer Sense versions are also going to entail some lag as well. Overclocking will help a little, but the GPU in that device isn't real powerful and is easily overwhelmed by a Sense 3.0 environment. The limited memory is an issue as well.
If you can, create a swap file. That will free up some memory.
Do NOT use task killers. They slow everything down by killing apps that need to be restarted, thus taking up NAND bandwidth, eating power, and freeing up RAM that's there to allow for recently used apps to run faster.
Wipe your Dalvik cache with each new ROM/Kernel. A properly built Dalvik cache is there to minimize app launch lag. Basically, it's a cache of application byte code that's been pre-compiled so that it can be executed while the JIT compiler determines the most efficient compiling of the remaining application code.
On the dInc, my SCcard seemed to access files quicker than if stored on the internal eMMC. Moving your Dalvik cache to the SDcard could allow it to be accessed faster since it's not sharing bandwidth with the rest of the system trying to access OS and app data from eMMC. I don't know if there's a way to test that or not, but it might be worth a try.

Check number and frequency of items synched; quick hit on responsiveness. Task killer or antivirus installed? Uninstall to see whether they are the culprit.
Sent from my ADR6300 using XDA Premium App

[MOD/EXPERIMENTAL] almost double your RAM

So, it turns out the /preload partition is 500 megs of almost unused space, just to show us a video of Asphalt. So, how about turning it into swap space to almost double the effective amount of memory you have? To use this mod, you must be rooted, and have busybox installed. I recommend the stericson busybox installer https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I would like feedback on whether or not it actually speeds up the device, especially when running graphics-intensive games, and also effects on battery life.
How to install:
1.Be rooted.
2. Get busybox. If you don't already have it, you can get it here https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
3. You must have init.d support. This is built into my NardROM but you can also flash the file attached to this post.
4. Flash the script installer, attached below. NOTE: This will wipe your /preload partition. You can make a nandroid before you perform this step but CWMR doesn't back up /preload. Back up anyway
5. If it's successful, you will see something like the following screenshot when you open a terminal window and execute "free". Notice the swap being used. If you don't have swap enabled it will read 0 available.
To disable the mod:
1. Delete the script from /system/etc/init.d
2. Reflash your Asphalt video from a backup
To disable init.d:
1. Delete /system/etc/install-recovery.sh, /system/etc/init.d (entire folder), /system/bin/sysinit, and /system/xbin/run-parts
Disclaimers:
Using nand memory as a swap can significantly reduce its life. Your phone's internal memory will wear out in years rather than decades
A lot of people argue using Android swap works against the built in memory management of the Dalvik machine
http://forum.xda-developers.com/showthread.php?t=1504774

This is awesome, glad to see people spending time on this device
Tappin' Typin'

'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.

ludacris1 said:
'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.
Click to expand...
Click to collapse
I think it's device-specific info for face unlock to compensate for various things like the angle you're holding the phone at and the distance away from your face. And if you'll look a little more closely, you'll find /vendor is symlinked from /system/vendor, it's not actually a separate partition. You should probably put those files back if you want face unlock to work.

Technically I just downloaded some ram
Sent from my SGH-I927 using xda app-developers app On Ics

FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.

Same thing I was thinking. I have more than enough RAM but if by some miracle we get something past JB that uses a lot of RAM I'll do this. Nice work on it though!
sent from my captivate glide running ICS (NardROM 0.4 Rooted)

roothorick said:
FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.
Click to expand...
Click to collapse
Waiting for the comparison,then

mewatashiakumoi said:
Waiting for the comparison,then
Click to expand...
Click to collapse
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?

pm2gonzales said:
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?
Click to expand...
Click to collapse
1) this is not a hack, this is a simple tweak
2) swap file is ALWAYS has a performance decrease effect, no matter what (desktop PC, android phone). The only reason of use is when the device has no enough RAM, and the background processes shall be kept elsewhere
3) android has it's own RAM managing system and methods, simply stick to that as only that will gives you the best performance and user experience
4) "slowdown" occurs when the device runs out of free RAM and starts closing background applications to give everything to the foreground app. When you close the heavy resource use foreground app witch caused android to close every possible background apps, the phone reloads them (launcher, live wallpaper, app drawer, widgets, user apps, etc...) and this is what causes a temporary slowdown, and this is unavoidable, no matter if you use swap or not.

ART: ANDROID RunTime

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?

[Q] ART vs Dalvik

Under developer options, you can choose either ART or Dalvik as a runtime system. What are the differences here? I've heard that ART is supposed to be give smoother performance. The only difference I've noticed since switching to ART though is every time my phone restarts, it has to optimize 112 apps, which takes about 10-15 minutes and makes my phone blazing hot.
Sent from my SM-N910V using Xparent Blue Tapatalk 2

Till lollipop comes out stick with dalvik. Its more of a experimental on kitkat, it uses more space and has to optimize apps and some apps wont work under it.