Related
This thread should serve as a general source of information for those patching and extending the kernel.
Anyone who does changes to the kernel should drop a note here (especially on those builds that go into FolioMod or TnT)
I'll also try to keep a list of patches and a current config file in the first post of this thread.
Just to make sure that anyone has a common base, the Folio 100 kernel source can be found at TegraMid wiki: http://tegramid.com/wiki/Main_Page
To upgrade to nvidia-10.9.8 apply the attached patch to the source tree.
Note that the zip file also contains a disabled folder, this contains 3 patches that were NOT applied as they prevent the folio from booting.
There were quite a few changes for handling audio devices, this may fix the issues with bluetooth headsets and sound coming from speaker and headphone (not tested though), also there was a change in some wakeup configuration structure for wlan, so this may also fix the wakeup issue.
Changes from DerArtem to support 3G Modems are not (yet) included in the kernel.
I also had two freezes when booting the system wuith this kernel (system_server not responding) however I could not reproduce them.
OK, I'm stupid!
Forget the patches above, I pushed the updated kernel images to the wrong directory (/sdcard instead of /sdcard/sdcard-disk0) So I was constantly flashing the last plain folio kernel on the device.
Damn you shell scripts!!!
Updated the patches above, the kernel should work and everyone should be able to recompile with the patch applied.
I've also attached a binary for users to test the kernel.
weeds2000 said:
Updated the patches above, the kernel should work and everyone should be able to recompile with the patch applied.
I've also attached a binary for users to test the kernel.
Click to expand...
Click to collapse
How do we install these files? Or do we better just wait for a new foliomod version?
killerbie said:
How do we install these files? Or do we better just wait for a new foliomod version?
Click to expand...
Click to collapse
If you look into update-nvidia-10.9.8.zip file, you could see that it is normal update file for kernel. So that I guess you rename update-nvidia-10.9.8.zip to update.zip and then update as any other update. But you should better always know what you are doing. If not, wait for full foliomod update.
To weeds2000: thanks for keeping kernel repository updated for the others.
weeds2000 said:
Updated the patches above, the kernel should work and everyone should be able to recompile with the patch applied.
I've also attached a binary for users to test the kernel.
Click to expand...
Click to collapse
Hedphones plus speakers issue seem solved, many thanks!
Foliowidget correctly report battery status and AP name but to set buttons light or display properties don't works.
Rom cooking
Most tools found to build Android ROM is for linux .Is there tools to build android ROM in WINDOWS environment?
Rom cooking
Most tools found to build Android ROM is for linux .Is there tools to build android ROM in WINDOWS environment?
This kernel is based on the stock Toshiba Kernel with modifiactions from DerArtem.
I've added UTF8 NLS support as required by the vold patch as well as the lag on wakeup fix.
Could someone please confirm that 3G support is still working with this build. As I don't have a 3G modem I cannot test this.
weeds2000 said:
This kernel is based on the stock Toshiba Kernel with modifiactions from DerArtem.
I've added UTF8 NLS support as required by the vold patch as well as the lag on wakeup fix.
Could someone please confirm that 3G support is still working with this build. As I don't have a 3G modem I cannot test this.
Click to expand...
Click to collapse
i can try install already on folionotion?? just for not reinstall the system..
I cannot guarantee that this works, but in case you cannot boot it should be enough to just flash the ROM again without making a Factory Reset.
Make sure you have an adb connection or some way to get an update.zip to your SD Card in case the device does not boot.
check out wifi drivers from here:
http://git.chromium.org/gitweb/?p=atheros.git;a=summary
is it possible to enable the tunnel support in the kernel?
Has anyone emailed toshiba to request the latest source? it took amout a month to arrive last time (on cd)
Could you please PM me the address you have writen the request to?
I searched the toshiba page yesterday, but couldn't find a developer page or something like that.
Or should I simply contact customer support?
weeds2000, can you attach the precompiled toolchain? i got smp compile error so maybe it is the toolchain im using.
what i did was:
1) download and extract the source
2) download and patch the tegra patch you attached in post 1
3) download the tegra config file you attached in post 1 and extract the config to .config to kernel directory
4) make ARCH=arm CROSS_COMPILE=/path_to_crosstoolchain/arm-eabi-
it was 2am when i did it so maybe i missed something.. lol
EDIT: Nevermind, found the toolchain from android.com.
PS. Anyone happens to have a copy of Tegra 250 technical datasheet?
Hmm.. Cannot get it to boot into OS.. The kernel booted and adb ran..
Also tried the binary you have attached in post #1 but also doesnt boot into OS. Did you get it to boot at your end?
Attached are dmesg and logcat
The image in post #1 should work with FolioMod 1.3. As the display/touchscreen driver seems to have changed it may not work with 1.4.
I'm not 100% sure, but this looks like a problem with the nvrm_daemon binary which is not started or has crashed.
please implemet tun.ko
Hi,
i need the tun.ko for the folio, so i can connect via vpnc to my fritzbox and make phonecalls for free over wlan hotspots. (like i do on my desire)
Please can you provide a tun.ko for this.
Cheers
xoom honeycomb source / git
Just got a note from MCLP on the honeycomb git.
so i downloaded it, and extracted the config.gz from xoom tablet (boot.img, that is) .
the kernel completely compiles without a single error, and no questions on the .config file i used, so the xoom config.gz matches the environment of the git (Koush said he also used it to compile the recovery kernel for xoom)
git is here
View attachment config.zip xoom edition.
now's the question if we can make it run on Folio
update:
removed(too many bugs) is the 2.6.36.3 with the Folio100 ODM_KIT included, i don't see any chance of making it work without, as i read the odmkit, its toshiba custom drivers + tegra for betelguese platform. this is NOT a working source, but inprogress.. but maybe someone else can assist?
Hey all, first time poster, long time reader here
So I've been tinkering with my Galaxt Tab 2 7.0 (gt-p3110), and I'd really like to get my 3g usb dongle working with it. I'm currently running AOKP Milestone 1, with the CM10 MaxOC kernel. As the kernel modules aren't available for those builds, I'm attempting to build my own (I've downloaded the source for the MacOC kernel).
However, there is no /proc/config.gz file on my device, and have no idea which options to enable/disable if using 'make mrproper' on the build.
If there another way to extract the kernel config for the currently running kernel ?
(i've also tried extracting it from the boot.img file, with no luck there either).
Thanks
(I know this really belong in the dev thread, but I don't have 10 posts yet !)
Check one of *.defconfig file in /arch/arm/config directory on your source tree, one of them is your config file.
Thanks heaps for that. I actually found the configs just before I saw your reply!
So I was able to build the kernel fine, but was unable to get it to boot. Not so sure why, but as I'm really after certain modules, I attempted to load them. I'm having trouble with the magic version number. I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
I'll revisit running the kernel another time. My eyes hurt!
lordvader1982 said:
I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
Click to expand...
Click to collapse
See this blog post http://stevechui.blogspot.com/2011/10/compiling-kernel-modules-tunko-for.html the step number 6 about editing scripts/setlocalvsersion
proudfoot said:
See this blog post ... the step number 6 about editing scripts/setlocalvsersion
Click to expand...
Click to collapse
Thanks for that ! I was atually using that post as a guide for building the modules. Kinda glanced over step 6 ...
I've since found prebuild 3g modules for my tablet on this forum, but I am trying to get nfs working, so it's all valuable info
location
lordvader1982 said:
Thanks heaps for that. I actually found the configs just before I saw your reply!
So I was able to build the kernel fine, but was unable to get it to boot. Not so sure why, but as I'm really after certain modules, I attempted to load them. I'm having trouble with the magic version number. I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
I'll revisit running the kernel another time. My eyes hurt!
Click to expand...
Click to collapse
can you please tell me where you found the config.gz file? I cannot find anywhere. thanks.
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
It's packaged as a complete rom to avoid kernel module difficulties. The rom is completely stock minus the boot animation, kernel and kernel modules. Thanks to everyone who has made this possible.
Both the kernel and PVR module have been compiled with linaro.
The kernel has numerous performance and stability enhancements over any other kernel to date.
Great Work. Thank you very much!
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
wahidx said:
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
Click to expand...
Click to collapse
I appreciate the last_kmsg. I apologize for using everyone as beta testers, but this demonstrates why it is a good idea- because I have been running OC5 for a few days without a single hiccup at all. I am actually surprised OC4 did so well for you. OC4 was also the first version to sport a new pvr module.
One thing I had been noticing before being able to compile my own pvr was that I could have one kernel play well with the stock pvr, and I could have a kernel right after that not play well with the pvr at all. This was my major motivation to be able to compile my own pvr so that it could match kernel space every time.
Ok, with that said, I compiled the pvr against OC4, and didn't bother updating it against any subsequent kernels. I probably should have known better, but it was working well enough for me.
Your error looks suspiciously like a missmatch between the pvr and kernel space. So if you want to try this update:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
and let me know if it works any better. I made sure to compile the pvr to specifically match the kernel.
Also, when I compiled the pvr before, I used PLATFORM_VERSION=4.1. I used this as an excuse to try
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.2.2
I don't know if it makes a difference or not.
Another thing I noticed you have slightly different hardware than I do. You have elpida ram versus samsung which is what I have.
I modified samsung ram timings to be slightly faster, but the other ram types were left at stock speeds. I may eventually try to clock the elpida ram the same as I have done with samsung, that may or may not make a difference. This may affect pvr performance as well. (It seems your pvr was a little slow bringing up power a few times). Then again, it could be my pvr source (although it works flawless for me, it may be hardware differences- I dunno.
thx for fast replay man,
i will try this release and give you feedbacks.
i have the bad feeling that something is wrong with my hardware. can be the only explanation, why my device reboot so often with CM10.2, CM11 and your OC6 release :/
//EDIT
actually i had just 1 reboot after some hour OC6 using, i will try OC6 for the next 2-3 days, maybe it was just a bad accident. after that i will try your OC7
regards
//EDIT #2
OC6 Test
after 2 days more, just 2 freez-->reboots (check last_kmsg) but still better than CM 10.2 and 11 on my device
Jon Lee said:
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
<snip>
The kernel has numerous performance and stability enhancements over any other kernel to date.
Click to expand...
Click to collapse
Hi Jon:
Hey, since we're asking for the moon, and since you're making THE oc kernel, any chance you can implement f2fs? I've got a Gal Tab 2 and an xda developer over there has a page about what he's done to get f2fs to work. Mostly it seems to require a .101 kernel. And he was kind to update TWRP so it would support f2fs. (I think to keep it from automatically formatting in ext4.) And he even wrote some zips to format /data, /system and /cache to f2fs.
My Tab 2 doesn't benchmark any faster but it sure is faster with f2fs. I image the HD+ would be faster too.
I'm new to flashing the Nook HD+. I was previously using the SDcard booting option for CM 10.1, but I would really like to get Nook off of this completely. Where do I start? I downloaded the ROM, and I have a boot IMG from another ROM on an SD card that takes me to recovery. Where do I put this ROM and how do I overwrite the actual Nook ROM?
install fails using verygreens internal recovery. is there a trick to installing this?
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
SynGamer said:
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
Click to expand...
Click to collapse
Yes, that means you still have stock recovery installed. You need to go to my HD/HD+ CWM thread linked in my signature and download and install the 6036 CWM from item 5 there.
Edit: but you know if you upgrade to CM10.2 you lose this kernel, right?
Sent from my BN NookHD+ using XDA Premium HD app
---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------
smatticus said:
install fails using verygreens internal recovery. is there a trick to installing this?
Click to expand...
Click to collapse
It depends on which verygreen internal recovery you are using. You need to have version 6036 or older to flash it. You can get one per my previous post.
Sent from my BN NookHD+ using XDA Premium HD app
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
i6941 said:
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
Click to expand...
Click to collapse
Does this work for CM11?
andtron said:
Does this work for CM11?
Click to expand...
Click to collapse
I think the answer is no, when you flash cm11 the OC kernel will be overwrite. But I didn't try this.
As the thread title indicates, this kernel is only for 10.1.3.
it says there is a new update from the option -- about menu...should I?
Jon Lee said:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
Click to expand...
Click to collapse
I couldn't find a tabletUI patch to match the final cm10.1.3 stable so here's one for anyone else downgrading like me.
Here's another experimental kernel update.
http://www.mediafire.com/download/1lkesmn6si6hd1e/ovation-kernel-cm10.1.3_v5.zip
I'm using it on OC7 pvr without issue (?).
1) reduced elpida and hynix ram timings.
2) updated vivante gc320 gcx 2d composition drivers to gitorious.org/gcx staging/alexei-dev. These are significantly different from original. (FWIW Staging/master branch threw memory map bverror 2 logs, but otherwise worked fine).
3) reduced dsp carveout memory. Increased system memory.
If needed, here is just the plain kernel for OC7, should anyone wish to revert back to that for any reason. (So as to not have to flash the entire ROM).
http://www.mediafire.com/download/z4r59n8dasxgz93/ovation-kernel-cm10.1.3_v4.zip
Kernel source for OC7
http://www.mediafire.com/download/6rngvee6x471cc3/android_kernel_bn_omap-cm-10.1_v3.tar.gz
So oc7 has been very unstable for me. I started with a completely clean slate, but it's frequently rebooting and not waking up from sleep. I may remember having these same problems when I was regularly using cm10.1 last year.
I've gone back to cm10.2.1. You should consider developing your kernel for that one.
Ya'know, I make these for me first and foremost. They reflect what I'm working on, trying to fix or improve the performance of my device.
Each one is different, some have worked better than others, but I notice an overall improvement from the original kernel. It is substantially different than any other nook kernel out there and works the best for me.
Here's the last. I think it works well. Made some additional changes to mmc/sdio to try and improve stability with wl12xx.
Source (which includes the vivante driver change from before):
http://www.mediafire.com/download/v4ihnr46eo9ap4d/android_kernel_bn_omap-cm-10.1_v4.tar.gz
Flashable kernel
http://www.mediafire.com/download/c9bsziswrf7y0e4/ovation-kernel-cm10.1.3_v6.zip
I like 10.3.1 but it has two downsides. 1) No automatic TRIM. 2) Unsafe manual TRIM because of Samsung MAG2GA EMMC bug.
Is it possible to implement the workaround used for 10.2.1 and later? Then manual TRIM by using console "fstrim" should be safe.
http://wiki.cyanogenmod.org/w/EMMC_Bugs
I assume the source for the 10.2.1 kernel would have the ported patch.
@zephiK , I installed the VomerTweaks on top of Mahdi rom and Franco kernel from your signature. I flashed it via TWRP , but dont know if its installed or is successfull etc. Can you let me know what exactly this tweak does and any way of finding if its active / installed ? Is there a option which appears in settings ? Thanks !
You didn't have to make a new thread for this.
To verify that the settings indeed have loaded, you need to use a kernel tweaker app (e.g. FKU, Trickster)... if you see that the maximum (fixed) CPU frequency is 1.2GHz then its loaded. A lot of the questions you asked are answered https://192.227.135.147/get/vomertweaks.txt (ignore the warning)
# What is it?
VomerTweaks is a tried and tested set of custom settings and power modes for your device!
The aim is to enable your device to have insane battery life without losing performance (all of us love da juice!)
We develop and test multiple configurations (for different "user types") & share them with the community.
Click to expand...
Click to collapse
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
shapethelola said:
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
Click to expand...
Click to collapse
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
zephiK said:
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
Click to expand...
Click to collapse
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
You need to reinstall Franco if it's supported yet that's all
dayanandgp said:
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
Click to expand...
Click to collapse
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
You need to reinstall Franco if it's supported yet that's all
Click to expand...
Click to collapse
No, flashing a newer/older version of Franco does not touch this script at all.
zephiK said:
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
No, flashing a newer/older version of Franco does not touch this script at all.
Click to expand...
Click to collapse
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
shapethelola said:
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
Click to expand...
Click to collapse
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
zephiK said:
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
Click to expand...
Click to collapse
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Check this post for download links:
http://forum.xda-developers.com/showthread.php?p=55150676
Sent from the One
dayanandgp said:
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Click to expand...
Click to collapse
I removed it since the links were just all over the place. Refer to nikzDHD's link above ^^.
To uninstall, just flash vt_uninstaller.zip
@zephiK sorry to ask this here, but is it possible for someone to build chroma rom for oneplus one? would be great right?
Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers(*) for our device. I'm on CM13 nightlies and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
(*) developer preview, does not meet customer release quality
dani_mola said:
Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers for our device. I'm on CM13 06-July nightly and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
Click to expand...
Click to collapse
Any insight as to drivers improvements?
gmlogan said:
Any insight as to drivers improvements?
Click to expand...
Click to collapse
Still testing. By now the most noticeable is the OpenGL 3.2 support (build.prop modify required, but I think the Adreno 418 of our SD808 is limited to 3.1) and by the moment I don't see any overheating nor graphics corruption at all.
I was hoping to see Vulkan libraries...
Unless "libllvm-glnext.so" is one of them, but I would expect to see libVulkan.so now.
quakeaz said:
I was hoping to see Vulkan libraries...
Unless "libllvm-glnext.so" is one of them, but I would expect to see libVulkan.so now.
Click to expand...
Click to collapse
I hope so, but Vulkan is natively supported only in the next android version 7.x unlike 6.x that need a 'fork' from the maker side. For example, Samsung made a Vulkan own driver version for their Galaxy 7 model supporting android MM, but I think that Motorola isn't in the work to develop a driver for the 2015 (nor 2016) models running android MM.
CM13 nightly moved to MOB30R branch (05-July) and the latest Adreno drivers are for MOB30M (01-June) so I hope an update from Qualcomm side...
dani_mola said:
Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers(*) for our device. I'm on CM13 nightlies and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
(*) developer preview, does not meet customer release quality
Click to expand...
Click to collapse
Can this be flashed on truepure? Rom based on stock?
unitz0mbie said:
Can this be flashed on truepure? Rom based on stock?
Click to expand...
Click to collapse
Yes...
@dani_mola I just flashed those drivers did the build prop edit and man. Thank you. I was getting the lines and weird static on the bottom part of my screen been looking at it for the lady couple months and hated it. Now, it's not prefect but the harsh stripping is gone and the glitchy fuzz is endurable is all I can think you call it. Should've taken a SS before but here's what I'm looking at now http://cloud.tapatalk.com/s/57ba27bab92e7/Screenshot_20160821-181254.png?[/URL]
Does this improves performance?
sooyong94 said:
Does this improves performance?
Click to expand...
Click to collapse
really havent notice much, but some ppl say its smoother. i guess it depends on optimized is your phone, runs different on everyone's phone