Database Develop

nexus 7 art runtime please complain here

http://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=62375

Having tried it on my Nexus 5 i cant see what all the fuss is about, yeah stuff opens a little quicker but its hardly life shattering.

wtf??
im using ART on my 2012 nexus 7 without issue. sure, a few apps donr work on ART(like pandora) but the device seems like it took a dose of speed. its fast without ART, but faster with. ART isnt available on the nexus 7(2012) stock img, but it is available for the nexus 7 on aosp builds.

MrBelter said:
Having tried it on my Nexus 5 i cant see what all the fuss is about, yeah stuff opens a little quicker but its hardly life shattering.
Click to expand...
Click to collapse
I know that the reason it is not on here is because of I\O wear out on the flash memory.(Crappy chip)
This device can't handle the strain of ART.
I'm just a little irritated that google won't put it in the DEVELOPER!!!! options in there stock build.

simms22 said:
wtf??
im using ART on my 2012 nexus 7 without issue. sure, a few apps donr work on ART(like pandora) but the device seems like it took a dose of speed. its fast without ART, but faster with. ART isnt available on the nexus 7(2012) stock img, but it is available for the nexus 7 on aosp builds.
Click to expand...
Click to collapse
I love that kernel
And thanks for the second link in your sig.
I dont want to load up another build though.
And geez. I would figure that google would put it in the for crying out loud developer options.
I like it completely stock.
I start from the ground up with modifying the build to my liking.
Thats why I'm a huge fan of Xposed Framework and the Arch Linux model.
Rant^

Why complain here? is anyone significant going read it.?

I think an explanation is what we need. Obviously it was a technical issue, but like every technical issue, Google leaves us in the dark and leaves us to speculate. I'd also like to know why we can't get a kernal higher than 3.1 when nvidia actually makes a 3.4 kernal too.
Sent from my Nexus 7 using Tapatalk 4

Cor-master said:
I think an explanation is what we need. Obviously it was a technical issue, but like every technical issue, Google leaves us in the dark and leaves us to speculate. I'd also like to know why we can't get a kernal higher than 3.1 when nvidia actually makes a 3.4 kernal too.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Then why post here? a developers forum of all places. if a problem if being had with google, go email em

-PiLoT- said:
Then why post here? a developers forum of all places. if a problem if being had with google, go email em
Click to expand...
Click to collapse
I really don't care that much. As far as I'm concerned my nexus 7 feels more like an antique these days and art or a new Kernal isn't going to magically make it a tegra 4 or give it another gig of ram. I was just replying to the topic that's all, wasn't my creation
More or less agreeing with the op. But I think he meant click on the original link and post your complaints there, not here
Sent from my Nexus 4 using Tapatalk

About to go for a nexus 6 but some issues are keeping me from doing it

I've had pretty much every nexus device, but last year I decided to get myself an Iphone 6, but I really missed android, so I'm about to get the nexus 6 but some issues are keeping me from doing it, I've read quite a few reviews and I'm concerned about the following issues:
1. Why is the camera so slow to take pictures? You think it could improve in the future? That's probably the thing I like the most about the iphone 6, how good the pictures come and how the camera is blazing fast
2. Is it true that the device is slower than the nexus 5? Have updates improved this situation? My nexus 5 already stuttered with Lollipop, Ive read quite a few reports about the phone slowing down and lagging for no apparent reason (except for maybe the quadHD killing the cpu/gpu)
3. How true are the reports of screen burn in?
4. How do non google apps and icons look? I imagine pretty bad since facebook or instagram's icons haven't even been updated to take advantage of a 1080p screen
5. Is it true that the device has slow storage a step down from the nexus reading and writing speeds?
Thanks for your help

Chad_Petree said:
I've had pretty much every nexus device, but last year I decided to get myself an Iphone 6, but I really missed android, so I'm about to get the nexus 6 but some issues are keeping me from doing it, I've read quite a few reviews and I'm concerned about the following issues:
1. Why is the camera so slow to take pictures? You think it could improve in the future? That's probably the thing I like the most about the iphone 6, how good the pictures come and how the camera is blazing fast
Click to expand...
Click to collapse
The actual act of taking a picture is fast, its just focusing that is slow. If you focus manually or fixed, it will take pictures amazingly fast.
2. Is it true that the device is slower than the nexus 5? Have updates improved this situation? My nexus 5 already stuttered with Lollipop, Ive read quite a few reports about the phone slowing down and lagging for no apparent reason (except for maybe the quadHD killing the cpu/gpu)
Click to expand...
Click to collapse
Not at all true.
3. How true are the reports of screen burn in?
Click to expand...
Click to collapse
Completely imaginary.
4. How do non google apps and icons look? I imagine pretty bad since facebook or instagram's icons haven't even been updated to take advantage of a 1080p screen
Click to expand...
Click to collapse
Where are you coming up with these questions? The only icon I've seen that actually looks bad, is the one for my bank... and it looks bad on ANY screen. Screen resolution is not so tightly tied to "icons" -- bigger screen = more icons. Also, Nexus 5 was already a 1080p display. I also hardly consider this question to be meaningful. Who really cares what icons look like? The objective is to maximize USEFULNESS.
5. Is it true that the device has slow storage a step down from the nexus reading and writing speeds?
Click to expand...
Click to collapse
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.

doitright said:
The actual act of taking a picture is fast, its just focusing that is slow. If you focus manually or fixed, it will take pictures amazingly fast.
Click to expand...
Click to collapse
I see, we will see if it changes with the 5.1" update, I remember the first big update for the nexus 5 did wonders for the camera
doitright said:
Completely imaginary.
Click to expand...
Click to collapse
http://nexus5.wonderhowto.com/how-to/fix-screen-burns-your-nexus-6-other-amoled-device-0159397/
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
doitright said:
Where are you coming up with these questions? The only icon I've seen that actually looks bad, is the one for my bank... and it looks bad on ANY screen. Screen resolution is not so tightly tied to "icons" -- bigger screen = more icons. Also, Nexus 5 was already a 1080p display. I also hardly consider this question to be meaningful. Who really cares what icons look like? The objective is to maximize USEFULNESS.
Click to expand...
Click to collapse
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
doitright said:
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.
Click to expand...
Click to collapse

I'm in agreement with @doitright. I can say nothing but good about this device. I do not have any of those issues nor know of any that do. As with any device though there are always some bad ones that an unlucky few receive. It does not make all of them bad just those. My phone is a beast. It outperforms the N5 by miles. Screen looks amazing. Icons to me look great I haven't come across a bad looking icon except that of my bank.... I guess banks hire poor developers idk. Storage is incredibly fast. Camera is fantastic. Fastest signal acquisition I've seen on any phone including GPS.
Eh. Entirely up to you what you want to do. I don't trust any reviews. I rather go with my own opinions/feelings on anything. You should too.

Chad_Petree said:
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
Click to expand...
Click to collapse
App icons are controlled by the dev. I've never seen a fuzzy one.

doitright said:
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.
Click to expand...
Click to collapse
I'm awaiting this Thursday to grab one on VZ, coming from a Galaxy Nexus, anything I could get now would be a major update hardware wise, however the only exception I take is the last part of this, not trying so start anything, your other parts are spot on.
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html
2 - they tweak the software encryption, which if you check the threads, opinions really vary here. if you need to irk the absolute most out if it for read write, then undo it. But plenty of others have chimed in saying it wasn't that big an increase, i believe it to be what you may be using on the device that makes the difference, more intensive apps may cause the SW process to bog down, but in all, it is still fast.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Personally, if I grab the N6 this week, I plan on unlocking/rooting/removing VZ oem partition, but for the moment leaving encryption on, because 5.1 may drop in March, and then see how things are at that juncture.
It would be great if they could enable HW encryption, because we get that security and maintain read write offloaded from the CPU.
Lastly, I plan on trying to enjoy the thing, playing with it for at least an hour in store before taking it (you never know) because as most of us here are OC hehe, reading all the threads of issues before buying it is kinda a downer. I know I'm going to love it, having waited three years to update myself.

RW-1 said:
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Click to expand...
Click to collapse
That's what I was thinking about, would it be possible for them to get rid of the encryption with an OTA , I would think that one needs to factory reset your device

Chad_Petree said:
I see, we will see if it changes with the 5.1" update, I remember the first big update for the nexus 5 did wonders for the camera
Click to expand...
Click to collapse
Focus is a PHYSICAL MOVEMENT of the lens. No update will change the amount of time it takes to move the lens.
http://nexus5.wonderhowto.com/how-to/fix-screen-burns-your-nexus-6-other-amoled-device-0159397/
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
Click to expand...
Click to collapse
I congratulate you on finding a thread about an imaginary problem, and a "fix" for an imaginary problem.
There is a certain subset of people who will do anything, IMAGINE anything, to find a problem. Don't ask me why they are like that. Sucks to be them.
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
Click to expand...
Click to collapse
You can't do anything to increase the fuzzyness of an image, unless you actually stretch it larger. I.e., if it takes the same physical space on the screen, then increasing the DPI on the screen won't cause it to become more fuzzy -- it just won't increase in SHARPNESS with the display. Google has specifications regarding the dimensions of the icons, and these specifications have always included a "much larger" image than what will actually display on the screen. The icons actually get scaled down to fit. So really, don't worry about it. If you find an application with a ugly/fuzzy icon, complain to the application vendor, because they're the ones who made an ugly icon, not the platform.
I just can't stress enough, that this is a silly point to use to avoid a device.
---------- Post added at 06:03 PM ---------- Previous post was at 05:49 PM ----------
RW-1 said:
I'm awaiting this Thursday to grab one on VZ, coming from a Galaxy Nexus, anything I could get now would be a major update hardware wise, however the only exception I take is the last part of this, not trying so start anything, your other parts are spot on.
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
Click to expand...
Click to collapse
I *absolutely promise you* that they WILL NOT eliminate the encryption requirement. Those "android one" devices are... really really cheap. It is likely that they don't force encryption simply because they are not up to the task.
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
Click to expand...
Click to collapse
I CAN confirm that it does. There is no question at all. It is part of all snapdragon SoC's since about S4.
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html
Click to expand...
Click to collapse
There are two sides to the use of encryption hardware with qualcomm SoC's; the first is the "blobs", and the second is the integration with Android and the Linux kernel. Specifically, qualcomm's hardware crypto requires changes both to the kernel (which is under GPL), as well as VOLD (which is under APL).
Obviously, to include the kernel part, that kernel part MUST be provided as source. There is absolutely no option here.
VOLD is the part of Android responsible for mounting and managing disks. It is under the Apache license, which means that technically speaking, it can be distributed without including source, HOWEVER, this is a Nexus from Google, which means that they really can't ship a blob in place of VOLD. It has to be possible to build VOLD from AOSP.
So here is what was going on; at the time that Nexus 6 first shipped, Qualcomm HAD NOT made the source for Kernel or Vold available on CAF. That made it *impossible* for Google to include, since they would have to provide kernel code on request, and require that AOSP VOLD actually build and work.
QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!
And, in fact, there are a number of devices for which CM actually builds and includes hwcrypto *right now*.
2 - they tweak the software encryption, which if you check the threads, opinions really vary here. if you need to irk the absolute most out if it for read write, then undo it. But plenty of others have chimed in saying it wasn't that big an increase, i believe it to be what you may be using on the device that makes the difference, more intensive apps may cause the SW process to bog down, but in all, it is still fast.
Click to expand...
Click to collapse
This isn't even a half solution, because even though it may seem to improve storage performance to an acceptable level, it has to nail the CPU while doing so.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
Click to expand...
Click to collapse
Technically possible, but I *promise* you, it won't happen.
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Click to expand...
Click to collapse
Most definitely CAN be used. No question about it.
Personally, if I grab the N6 this week, I plan on unlocking/rooting/removing VZ oem partition, but for the moment leaving encryption on, because 5.1 may drop in March, and then see how things are at that juncture.
It would be great if they could enable HW encryption, because we get that security and maintain read write offloaded from the CPU.
Click to expand...
Click to collapse
You could disable crypto now, and let it encrypt when the update rolls around. Disabling forced-crypto does not prevent you from using crypto now or later.
Lastly, I plan on trying to enjoy the thing, playing with it for at least an hour in store before taking it (you never know) because as most of us here are OC hehe, reading all the threads of issues before buying it is kinda a downer. I know I'm going to love it, having waited three years to update myself.
Click to expand...
Click to collapse
Keep in mind that the test unit in the store gets abused.

DIR,
Looked forward to your responses on my last post, and was not dissapointed, nice info there, especially "QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!"
so has anyone done a comparison between the hwcrypto'd CM versions and unencrypted yet?
Yeah, I know the store ones get abused, in the end it would be a N6 or a GS6 for me, and I just cannot go to touchwiz, no matter how toned down, I want pure android, and unlocking ability, etc. Kinda makes the choice or me hehehe.
Dammit VZ, if you just announce online ordering tomorrow ... grrr .....

doitright said:
Focus is a PHYSICAL MOVEMENT of the lens. No update will change the amount of time it takes to move the lens.
Click to expand...
Click to collapse
Oh oh well, nothing is perfect
doitright said:
You could disable crypto now, and let it encrypt when the update rolls around. Disabling forced-crypto does not prevent you from using crypto now or later.
Click to expand...
Click to collapse
What would be the point of deactivating to reactivate later?

Chad_Petree said:
Oh oh well, nothing is perfect
What would be the point of deactivating to reactivate later?
Click to expand...
Click to collapse
I would guess deactivate to gain read/write speed increase now, if the update enables HW encryption then you would let it.
Oh, and that is the point - nothing is perfect, not the N6, nor the units that will come after it hehehe....

RW-1 said:
DIR,
Looked forward to your responses on my last post, and was not dissapointed, nice info there, especially "QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!"
so has anyone done a comparison between the hwcrypto'd CM versions and unencrypted yet?
Click to expand...
Click to collapse
I said on *some* devices. I did not say that they were enabling it on Nexus 6.
Yeah, I know the store ones get abused, in the end it would be a N6 or a GS6 for me, and I just cannot go to touchwiz, no matter how toned down, I want pure android, and unlocking ability, etc. Kinda makes the choice or me hehehe.
Click to expand...
Click to collapse
Yep, I'm totally with you on that. My last phone was a samsuck.... NEVER again. I spent WAY too many hundreds of hours on kernel and device tree maintenance to get and keep that thing working adequately on CM... then Omnirom (omni is waaaaaay nicer than CM). After a year of ownership of that thing, got the wife a Hammerhead (nexus 5), and its been just so easy to maintain. Literally all I ever did with her phone was add root, busybox, and xposed (to kill a couple of the google services wakelocks). This time around, I wanted the thing to just freaking work already!!!! Only downside is that its a bit *larger* than I would have liked.
Dammit VZ, if you just announce online ordering tomorrow ... grrr .....
Click to expand...
Click to collapse
I don't think that you should buy from verizon, even if/when they sell it directly. It will likely be crippled and branded, at least to some extent. Buy it from tmobile or google play store, and all you need to do is throw your verizon sim card into it. I think I heard that sprint also does not molest it. Oh, it could also be purchased directly from motorola.
Just whatever you do, do NOT buy it from ATT. They DO molest and cripple it.
---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------
Chad_Petree said:
What would be the point of deactivating to reactivate later?
Click to expand...
Click to collapse
To gain RW performance NOW... DUH.

I'll be getting it from VZ, because I just don't have the spare $$$ to buy direct and place it on VZ.
ATT taught us that VZ will have to toss its bloat on the oem partition just like anyone else, so ... as far as branding, I think that may rub off like ATT's, but if not I plan on putting in a case anyway.
Now we have to wait another two weeks if the newest rumor is true ...

S6 Ram Management Discussion(Partial Fix)

Since we've been talking about this pretty extensively in a different thread I figured I would make a new thread for discussing, troubleshooting and attempting to improve the ram management issue on the S6.
Hopefully some good will come of this
So far this Is what we've got:
Should work on all variants including the edge and possible on other Samsung devices.
Thanks to @mikeyinid for finding these and @s.rapp for answering questions, and making the instructions easier to understand
And anyone else who I may have missed who helped contribute.
Prerequisites:
-A rooted device
-A root file explorer/manager app
-A backup of your original build.prop to be safe
Explanation: (From @mikeyinid )
Here is a quick rundown on how this came about, and what we actually know.
Since I purchased the S6 on release day, I've been messing with certain things, as you can see from the ROM I posted, Looper(shameless plug). Debloating Samsung apps really helped with battery life and I was pretty happy with the results. But like so many other people, I didn't understand why my S6 killed apps so aggressively. Initially I thought it might be the memory leak we all know so much about in 5.0. So, I did a little research and found the patch for that. While it did help keep the device stable over time, apps were still being killed with no prejudice. All this time I noticed really useless services running in the background, often stuff I'd never even opened. I studied LMK and started messing with those settings. After a month of trying everything I could find documented, I was ready to give up. Yesterday I was looking through the services.jar smali for the 37,875th time and realized the DHA referenced in there has to have something to do with memory management. I kept overlooking it because I hadn't seen mention of it anywhere else. I am no smali guru, as some of you know. But it was pretty obvious DHA was influencing memory management to some extent. Samsung, although leaving us in the dark on this, was kind enough to give us props to set the values for DHA. I pulled a few that seemed relevant, added them to my build.prop, and what do you know. For the first time in almost two months of tinkering, I saw an improvement in the way my device was managing memory.
The thing everyone needs to understand; I have no clue what DHA is. It overrides every aspect of Googles LMK and seems to do so in a way that makes more sense. I'm sure someone with more knowledge than myself will be able to tune this to the point the S6 will be the multi-tasking champ. There are several other props in the smali that are probably useful. I will try to get them all with their default values posted today. This has been pretty exciting for me, I spent way to much time trying to figure out the issue to not make some sort of progress. I hope you guys enjoy the tweaks, and I hope it helps sway those of you on the fence about keeping this device to stay. It's only gonna get better
Instructions:
First find your build.prop. This is located in /system. to get to /system you need to go to the root directory using a file explorer and then go to the system folder. The build.prop will be in there. You can also use and app such as build.prop tweaker but its a bit harder (imo)
In your build.prop scroll to the very bottom and paste this in:
Code:
# MultiTasking Tweaks
ro.config.dha_cached_max=15
ro.config.dha_cached_min=4
ro.config.dha_empty_max=36
ro.config.dha_empty_min=9
ro.config.dha_empty_init=36
ro.config.dha_lmk_scale=0.545
ro.config.dha_update_max_count=5
ro.config.dha_step=2
ro.config.dha_th_rate=1.4
ro.config.dha_defend_th_level=0
ro.config.64bit_lmk_enable=true
ro.config.sdha_apps_bg_max=70
ro.config.sdha_apps_bg_min=8
ro.config.dha_ils_enable=true
ro.config.dha_ils_dyna_lmk=true
ro.config.dha_ils_rate=1.5
Now you need to find and remove any duplicate build.prop lines which may cause an issue. So look through the build.prop and remove any lines that look like these(Not the ones you just added at the bottom!):
ro.config.dha_cached_max=
ro.config.dha_empty_max=
ro.config.dha_th_rate=
ro.config.dha_lmk_scale=
Finally reboot your device and report back here!
Video Tutorial (courtesy of @Thin_Bezel )
https://youtu.be/d-vaLXF0OxY
A note from @mrapp :
"The major addendum here seems to be that when using this build.prop apps like Chrome and and those calling webpages via Webview (Tinfoil for Facebook) still suck. The kernels being tested at the moment don't appear to have this issue, so if you're capable of flashing kernels I personally recommend checking out the Vindicator thread if you're on T-Mobile/W8 or UniKernel (universal) if you're on any other device. UniKernel tests may or may not be edge friendly, so always make a backup. Lots of people have gotten in to trouble today. Don't be one of them!"
Please note we are constantly experimenting with different values so these are subject to be updated rather frequently

As I was saying before, Maybe someone can try compare Zenfone 2 services.jar with the one in samsung galaxy s6.
The Asus Zenfone 2 is knowed to had a great multitasking experience, it can keep a loot of apps even in his 2GB version, and remember that Zenfone is in Android 5.0 and don't have any problem with multitasking.
I already downloaded the firmware for Zenfone and decompiled his services.jar if someone like to try something, here is attached:

iFlasher said:
As I was saying before, Maybe someone can try compare Zenfone 2 services.jar with the one in samsung galaxy s6.
The Asus Zenfone 2 is knowed to had a great multitasking experience, it can keep a loot of apps even in his 2GB version, and remember that Zenfone is in Android 5.0 and don't have any problem with multitasking.
I already downloaded the firmware for Zenfone and decompiled his services.jar if someone like to try something, here is attached:
Click to expand...
Click to collapse
I'll take a look at it, but I've already gone through several different services.jar trying to find anything that might make a difference. Everything appears to be exactly how Google intended it to be.

mikeyinid said:
I'll take a look at it, but I've already gone through several different services.jar trying to find anything that might make a difference. Everything appears to be exactly how Google intended it to be.
Click to expand...
Click to collapse
I also noticed that Samsung uses the ramdisk to set VM memory settings and lmk settings rather than actually modifying the source for some reason. I tried removing all of these and letting the settings be stock google but that also made no difference
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
I also noticed that Samsung uses the ramdisk to set VM memory settings and lmk settings rather than actually modifying the source for some reason. I tried removing all of these and letting the settings be stock google but that also made no difference
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Right, all of that can be controlled with init.d scripts. i set the values ridiculously high and can see that that scripts actually work. Then going the other way no matter how low I set them or even disable them, there is no difference. Still can't have more than 5 or so apps open.

mikeyinid said:
Right, all of that can be controlled with init.d scripts. i set the values ridiculously high and can see that that scripts actually work. Then going the other way no matter how low I set them or even disable them, there is no difference. Still can't have more than 5 or so apps open.
Click to expand...
Click to collapse
What's a good test to see if memory management is improved? I've done some mods to lmk in my latest kernel and want to see if it helps any.
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
What's a good test to see if memory management is improved? I've done some mods to lmk in my latest kernel and want to see if it helps any.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
just open apps, never hit the back button, then switch between them using recents.

mikeyinid said:
just open apps, never hit the back button, then switch between them using recents.
Click to expand...
Click to collapse
Hmmm...idk still seems pretty mediocre :/ not sure if better or worse.
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
Hmmm...idk still seems pretty mediocre :/ not sure if better or worse.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Tried it on your latest kernel and it seems to be the same.

NJGSII said:
Tried it on your latest kernel and it seems to be the same.
Click to expand...
Click to collapse
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
Xileforce said:
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.

mikeyinid said:
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.
Click to expand...
Click to collapse
I meant I thought it may help with killing recents so soon. It had some tweaks to preserve favorites among other things
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
I meant I thought it may help with killing recents so soon. It had some tweaks to preserve favorites among other things
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
I was agreeing with you lol.

mikeyinid said:
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.
Click to expand...
Click to collapse
I have note 4 too and it has same problem with latest lollipop update, i switched to cm12.1 and now all the problem are gone, switching between apps it's really fast and apps stay in ram flawlessly.

CQ7 said:
I have note 4 too and it has same problem with latest lollipop update, i switched to cm12.1 and now all the problem are gone, switching between apps it's really fast and apps stay in ram flawlessly.
Click to expand...
Click to collapse
Interesting. This gives me hope! Ty for sharing. Im pretty sure its an issue on the ROM side rather than kernel.
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
Interesting. This gives me hope! Ty for sharing. Im pretty sure its an issue on the ROM side rather than kernel.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Right, but what on the ROM side could be causing this kind of behavior? I see myself as quite tech savvy, but I'm woefully uninitiated in the inner workings of Android you guys are unraveling here.
Even after removing just about all of Samsungs proprietary stuff, just leaving the bare basics, we're still seeing app genocide as soon as we're multitasking.
It'd sure be awesome of the community fixes this before Samsung does...

Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.

oxxshadow said:
Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.
Click to expand...
Click to collapse
The S6 isn't selling as well as Samsung had hoped. And the memory issue is probably a large part of it. I have a S4 also, and it doesn't have any issues multi tasking on lollipop. It's shameful that a 3 year old device can managed to run just about everything I throw at it with no problem.

oxxshadow said:
Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.
Click to expand...
Click to collapse
Samsung has acknowledged the ram issue and said they will fix it in an update. That's about as specific as they got. My guess would be 5.1.1 update though.
Sent from my SM-G920T using XDA Free mobile app

Xileforce said:
Samsung has acknowledged the ram issue and said they will fix it in an update. That's about as specific as they got. My guess would be 5.1.1 update though.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Sadly, Samsung has neither acknowledged the specific issue nor promised any updates. All the articles in the blogosphere regarding this (including the one from Forbes) cite a Facebook comment from a random Samsung employee giving an incredibly vague and generic response about future updates when asked a direct question about the memory issue by xda member johanbiff.
I'm baffled by the low level of journalism here.
EDIT: Typo.

Is Decryption Worth It?

Share your thoughts. Do you guys notice any difference in performance, that is worth decryption?

Most people will say they notice no difference. I think the more sensitive of you will though. It slows i/o on the flash memory when reading and writing and as it has to decrypt on the fly, it will add to CPU overhead.
I don't decrypt for performance reasons though. I just don't like encryption

I agree with the above from Dan. For myself, I haven't yet unlocked, rooted yet, just enjoying it coming from a GNex.
But to me coming from a Gnex - the N6 flies, and it is encrypted by default. In my case I don't think I would notice the improvement now, but eventually when I do decide to unlock and root, it will be unencrypted just for the heck of it.
It's really going to be a personal choice for you whether or not to do it, and if you see a difference, for the opinions out there vary wildly.

I got my n6 a couple weeks ago. Decrypted after a few days and noticed zero difference. accidentally encrypted again last week and yeah, I haven't noticed a difference at all. Up to you really.
Sent from my Nexus 6 using Tapatalk

For simple browsing it was fine for me encrypted. What killed me was downloading large files. In the same location i got 2mbps with my nexus 5 all of a sudden I'm getting 400k with the 6. Turns out it was the write speed of the software encryption not Tmobile. Decrypting solved it. Ymmv.

thionylx said:
For simple browsing it was fine for me encrypted. What killed me was downloading large files. In the same location i got 2mbps with my nexus 5 all of a sudden I'm getting 400k with the 6. Turns out it was the write speed of the software encryption not Tmobile. Decrypting solved it. Ymmv.
Click to expand...
Click to collapse
Yes that will do it.

No need to root.

This might be the first phone I leave stock. I do miss xposed on my htc, but aside from that. I don't see any reason to root. Am I the only one with similar feelings?
Sent from my SM-G920T using XDA Free mobile app

only 1 reason is ram management bug

adidas123 said:
only 1 reason is ram management bug
Click to expand...
Click to collapse
Glad that you mentioned this. Whenever I switch between apps and go back into chrome. The page I was viewing has to reload. How is this fixed via root?
Sent from my SM-G920T using XDA Free mobile app

So... you have to make changes to the build.xxx file? Are all phones affected by this ram issue? I haven't experienced any issues with apps crashing or lagging.
Sent from my SM-G920T using XDA Free mobile app

NYLUVBUG said:
So... you have to make changes to the build.xxx file? Are all phones affected by this ram issue? I haven't experienced any issues with apps crashing or lagging.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Honestly other than debloating, I could have left it stock as well.
I have incredibly itchy fingers though If I'm not messing with something that can turn my phone into a paperweight, I'm not having fun. Even the ram management stock wasn't noticeable to me. The Tmobile bloat is horrible, and I love loading ROMs and screwing with stuff I shouldn't be for the sake of the community.

LMT pie, adaway, custom roms, alliance framework, volume warning removal, de bloating, viper4android, etc... Root is always necessary.

viper4android

You are not missing much by not rooting. Nothing out there anyways. Most bloat can be disabled. No fix for ram issues. Only samsung can fix it if they want.
Sent from my A0001

ambervals6 said:
You are not missing much by not rooting. Nothing out there anyways. Most bloat can be disabled. No fix for ram issues. Only samsung can fix it if they want.
Sent from my A0001
Click to expand...
Click to collapse
True, I have everything disabled and I haven't found the need to root.

NYLUVBUG said:
True, I have everything disabled and I haven't found the need to root.
Click to expand...
Click to collapse
Stock since April 10th ram management isn't a huge issue for me. First phone ever not rooted. I'm satisfied.
Launched from my?T-Mobile Galaxy S6 ? 5.1.1 ?

philliman said:
Stock since April 10th ram management isn't a huge issue for me. First phone ever not rooted. I'm satisfied.
Launched from myT-Mobile Galaxy S6 5.1.1
Click to expand...
Click to collapse
Agree, you won't miss much by not rooting. I have disabled most of the bloat which are allowed to be disabled. I can switch between apps without any issues. I got a replacement device last week because the previous one will just turn off itself even if the battery is charged. the "new" (Actually is seems refurbished) works well so far. I have repeated the same process on disabling the unwanted apps, turning off wifi calling and VoLTE, screen on auto brightness, all the usual stuff. Battery life is not great, but can last a working day with moderate usage. If you are on the road, and use camera, maps, then battery drains quickly. If t-mobile network is poor where you are( which is a not unusal), battery will drain even quicker.

T version has to many app from stock... Almost 1.5gb of trash stuff.

abachhan75 said:
Agree, you won't miss much by not rooting. I have disabled most of the bloat which are allowed to be disabled. I can switch between apps without any issues. I got a replacement device last week because the previous one will just turn off itself even if the battery is charged. the "new" (Actually is seems refurbished) works well so far. I have repeated the same process on disabling the unwanted apps, turning off wifi calling and VoLTE, screen on auto brightness, all the usual stuff. Battery life is not great, but can last a working day with moderate usage. If you are on the road, and use camera, maps, then battery drains quickly. If t-mobile network is poor where you are( which is a not unusal), battery will drain even quicker.
Click to expand...
Click to collapse
I have everything enabled. Disabled the apps that I don't use and my battery life is great for my needs. 15 hrs with moderate use. I'm not big on SOT because I'm not in my phone all day long. Lol people be wanting 10 hrs SOT. ? ? ?
Launched from my?T-Mobile Galaxy S6 ? 5.1.1 ?

viper4android!

I semi-bricked my phone and haven't been rooted since bringing it back to life. The only thing I truly miss is AdAway. It's been years since I had to browse the web without an ad blocker and I feel like they've turned up the onslaught ten fold.

Not bad at all.
Sent from my SM-G920T using XDA Free mobile app

I wouldn't root either, but I hate ads, ad-away is a must for me. Adguard and all those work when browsing but not in apps. Until then I will stick to 5.0.2 with root. If anyone knows of a alternative for ad blocking like ad-away does, please let me know.

I need root. Few reasons. Debloating, ViperFX and volume button skip mod (whenever we get one)
Also really really hoping official Cyanogenmod makes it to this phone. I miss AOSP with all my heart.

H3adru5H said:
I need root. Few reasons. Debloating, ViperFX and volume button skip mod (whenever we get one)
Also really really hoping official Cyanogenmod makes it to this phone. I miss AOSP with all my heart.
Click to expand...
Click to collapse
Why not get a nexus then
Sent from my A0001

ambervals6 said:
Why not get a nexus then
Sent from my A0001
Click to expand...
Click to collapse
It's too damn big lol plus I prefer Samsung software. The S4 was perfect because of Google's GPE program. But since that's dead the best I can hope for is that sooner or later CM will come to the S6.