Related
ThrillsKernel for the Acer Iconia TAB A510
version 2012-11-18, built from source
Here it is, the first ever non-stock kernel for the Acer Iconia TAB A510, dubbed the "ThrillsKernel"!
What's in this kernel:
Comes in two flavors: V2 for ICS ROMs and V3 for JB ROMs
Removed 'Samsung EMMC brick' bug: This prevents your internal memory from becoming corrupted.
CPU Governors: Interactive, conservative, ondemand, powersave, userspace, performance, SmartassV2 and lulzactive.
I/O schedulers: Noop, deadline, CFQ, Simple I/O, V/R and BFQ.
Removed Acer mount security: Now you can mount system as r/w.
NTFS, CIFS, and MD4 support
Tegra3 optimizations
Various other performance tweaks
Installation:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
If you don't have it already, install my CWM-Based Recovery.
Step 2:
Download the kernel from this post, extract the .RAR files and put the .ZIP file on your internal or external SD Card.
Step 3:
Start Recovery by powering down your device, holding the Volume down (**) button and turning it on again.
Step 4:
Make a Nandroid Backup. I can't stress this enough. Select backup and restore and choose one of the backup options.
Step 5:
Install this ROM by choosing install zip from sdcard and then choose zip from sdcard or choose zip from external sdcard.
Step 6:
Wait for the installation to finish (this takes a few minutes). Spend your time reading the text below these installation instructions!
Step 7:
Select wipe dalvik cache from the advanced menu, thenreboot system now, and enjoy!
Please read the following carefully before installing this kernel:
I am not responsible for anything you do to your tablet. Whatever you do, you do it at your own risk!
Which version should I install?
ThrillsKernel2 is built on the 2.6.39 linux kernel and intended for A510 tablets with a ICS ROM installed. That's Android version 4.0.0, 4.0.1, 4.0.2, 4.0.3 or 4.0.4.
ThrillsKernel3 is built on the 3.1.10 linux kernel and intended for A510 tablets with a JB ROM installed. That's Android version 4.1.0, 4.1.1 or 4.1.2. There is no support for 4.2+ yet.
FAQ:
Want to use ThrillsKernel in your own ROM? Go ahead, make my day.
Need ***** added to the kernel? Let me know, and I will try!
Want to remove the kernel from a NoThrills ROM? Although it's not recommended, it's possible. Check the instructions in the respective ROM thread.
Want to give me your first born baby? I'd rather not have that, but if you really want to give me something: Either click the 'Donate to me' button on the left, or simply hit the 'Thanks' button on this post.
Changelog:
The ThrillsKernel has the date as version number, e.g. version 20121118 is November 18th, 2012. You can check the status (or changelog, whatever you will) of the kernel by visiting the commit history of my github page:
Click here for updates to ThrillsKernel2
Click here for updates to ThrillsKernel3
Just check what the date of the ThrillsKernel is, and you can simply look at the dates of the commits to see if it's included in the kernel or not. Example: With the version from November 18th, any commit up untill that date is included in the kernel. With the 20120917 version, every commit up untill September 17th is included in the kernel.
Downloads:
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
NoThrills A510 WorldWide optimized Stock ROM
NoThrills A510 "Franken700" Stock ROM
NoThrills A510 Unofficial CyanogenMod 10
ThrillsKernel is included with these ROMs as of 2012/09/17. Developers, feel free to extract the kernel and use it in your own ROMs.
Great new!
NoThrills said:
[*]Removed Acer mount security: Now you can mount system as r/w.
Click to expand...
Click to collapse
So it was Acer who was messing with remounting system RW?
Suggestion- maybe switching to TinyRCU is a good idea? It has a lower memory footprint and performs faster
gen_scheisskopf said:
So it was Acer who was messing with remounting system RW?
Click to expand...
Click to collapse
yep, great catch by nothrills, i should have seen this one
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
It might be, never looked into it as I have used Screen Filter since forever
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I used to use rootdim on my thrive to get it so low I could use the tab as an alarm clock with the screen on and facing me all night.
But trying the same on this a510, the backlight just goes completely off if I try to set it any lower than default. So I wonder if it is a hardware limitation.
It would be nice though. This thing makes my eyes hurt in the morning on the bus to work.
Overclock possible please? Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I would absolutely love this feature. I dont like apps messing with my system...
Working A510 CIFS at last!!!
NoThrills said:
ThrillsKernel for the Acer Iconia TAB A510 version 2012-09-17, built from source
[*]NTFS, CIFS, and MD4 support
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
Click to expand...
Click to collapse
I'm currently quote happy with the stock ROM apart from the lack of CIFS so I took the modules from /system/lib/modules [NoThrills A510 WorldWide optimized Stock ROM] and copied them to my stock (but rooted) A510.
CIFS works perfectly!
Thanks!:good:
Feedback:
I've tried Smartass v2 and Lulzactive and they seem to eat up more juice.
I then checked System Tuner Pro for my CPU times, and I noticed that my CPU would only go from inactive to 1.3 or 1.4GHz. It doesn't use the values in between.
I then switched to Interactive, and I can see the CPU clocks like 400+ and 600+ used again.
Not sure if it's just me though, but I'm putting it out there for everyone to test. Nevertheless, I love this kernel, I love the optimized A510 that you released as it fixed my screen responsiveness issue entirely. Take that Acer!
Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?
salisbury_steak said:
Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?
Click to expand...
Click to collapse
I'd say NoFrills CPU Control- works fine on ICS/JB
Other one is SetCPU but last time I used it there were problems on ICS (January/February)
I've used SetCPU without problems myself. I do however have the purchased version, which is different from the free version that can be found on XDA. That one doesn't seem to be updated anymore.
I've posted about my touchscreen problems in some games in the Optimized ROM thread.. but no answers there. The problem is only there when I use the NoThrills kernel... the stock kernel works good. Have you got any idea what the problem can be?
I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%
meldrak said:
I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%
Click to expand...
Click to collapse
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?
salisbury_steak said:
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?
Click to expand...
Click to collapse
I didn't reboot just after being blocked at 99%
but between 2 charges I rebooted it and in both case blocking at 99
I came back to stock kernel so I can't test it again
Aaargh, I hate all this touch problems with this f#@$ tablet. Games only playable with the stock kernel, but a piano app is not usable because it doesn't always detect your fingers. Sometimes it's perfect, you can press up to 10 keys at the same time, and sometimes it doesn't recognize two fingers. So I probably need the custom kernel for this.. but I don't want to flash a different kernel for different apps.
This is really the worst device I've ever bought, I hate this piece of crap. I hope this annoying problem will be solved in some future kernels but untill now there isn't a perfect one out there which solves all the problems. No offence to anyone, I know it's all in your spare time, but it's a rant to Acer. A device of about €450 which is soo bad, that's some really bad engineering!
Maybe this new file format would be considerated (or not ) ?
http://www.muktware.com/4485/samsung-creates-new-file-system-f2fs-linux-good-news-android#.UHPclVFKSVh
How to implement
https://lkml.org/lkml/2012/10/5/205
some benchmark results post by the F2FS author : http://www.mail-archive.com/[email protected]/msg318439.html
1. iozone in Panda board
- ARM A9
- DRAM : 1GB
- Kernel: Linux 3.3
- Partition: 12GB (64GB Samsung eMMC)
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 30.753 | 17.066 | 5.06 | 4.15
- f2fs: 30.71 | 16.906 | 5.073 | 15.204
2. iozone in Galaxy Nexus
- DRAM : 1GB
- Android 4.0.4_r1.2
- Kernel omap 3.0.8
- Partition: /data, 12GB
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 29.88 | 12.83 | 11.43 | 0.56
- f2fs: 29.70 | 13.34 | 10.79 | 12.82
I was running Cromi 4.7 and upgraded to 5.3 today. I also switched over to Hund's 3.4 kernel.
Now, when I change the power setting to performance or eco, the tablet freezes and then restarts (in Balanced mode).
The options I picked during the install process are-
US hunds with experimental tweaks
Software rendering disabled
GPU OC
CPU OV
GPU UV
I can't figure out if I messed something up during the install or if I need to play with the settings in Hunds app. Any ideas?
vickker said:
I was running Cromi 4.7 and upgraded to 5.3 today. I also switched over to Hund's 3.4 kernel.
Now, when I change the power setting to performance or eco, the tablet freezes and then restarts (in Balanced mode).
The options I picked during the install process are-
US hunds with experimental tweaks
Software rendering disabled
GPU OC
CPU OV
GPU UV
I can't figure out if I messed something up during the install or if I need to play with the settings in Hunds app. Any ideas?
Click to expand...
Click to collapse
If you are using Hund v3.4.3 ET with the ET build.prop, you should NOT install the GPU OC, CPU OV, and GPU UV because the ET is already UV/OC for the kernel. Can you tell me what you have in your init folder? You can go here and find it: "/system/ect/init". It is a easy fix that I believe... One more question, did you do a clean installation with a data format?
Thanks,
LMK
LetMeKnow said:
If you are using Hund v3.4.3 ET with the ET build.prop, you should NOT install the GPU OC, CPU OV, and GPU UV because the ET is already UV/OC for the kernel. Can you tell me what you have in your init folder? You can go here and find it: "/system/ect/init". It is a easy fix that I believe... One more question, did you do a clean installation with a data format?
Thanks,
LMK
Click to expand...
Click to collapse
Thanks so much for helping me out with this.
I misunderstood the relationship between the kernel and the ROM. I thought the kernel made those options possible, but that I still needed to select them. So, simply using Hund v 3.4.3 ET enables these options automatically.
The init.d folder has the following files in it: 50CleanTWEAKS, 70B2R, 80Fsync, 89OV, 90 UV, 91GPUUV, and 99hundsapp.
Before I flashed the ROM I did a factory reset with TWRP.
vickker said:
Thanks so much for helping me out with this.
I misunderstood the relationship between the kernel and the ROM. I thought the kernel made those options possible, but that I still needed to select them. So, simply using Hund v 3.4.3 ET enables these options automatically.
The init.d folder has the following files in it: 50CleanTWEAKS, 70B2R, 80Fsync, 89OV, 90 UV, 91GPUUV, and 99hundsapp.
Before I flashed the ROM I did a factory reset with TWRP.
Click to expand...
Click to collapse
I think that your problem is that you under voltage too much which causes the kernel running unstable... So you could try this to see if you can fix your issues...
First, you may want to do a nandroid back from TWRP. Just in case you want to go back to your original state...
Second, delete these files from your init folder: "89OV, 90 UV, 91GPUUV".
Third, reboot your device and see if it is still rebooting when switching to performance mode....Good luck...:fingers-crossed:
Please report back what is happening when you delete those files, thanks..
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
azreal8 said:
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
Click to expand...
Click to collapse
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
berndblb said:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
Click to expand...
Click to collapse
azreal8 said:
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
Click to expand...
Click to collapse
That is really strange and unusual and certainly a PIA. But let's make sure we are on the same page:
Define what you mean by 'clean install'
Post your bootloader and recovery versions please.
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but is unusable when running a rom, stock or otherwise?
azreal8 said:
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but it unusable when running a rom, stock or otherwise?
Click to expand...
Click to collapse
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
berndblb said:
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
Click to expand...
Click to collapse
sbdags said:
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
Click to expand...
Click to collapse
all of a sudden the microSD slot doesnt work.
the slot on the keyboard however does. is that weird?
quite disappointing. also as i've unlocked, ive lost my warranty.
azreal8 said:
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
Click to expand...
Click to collapse
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
sbdags said:
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
Click to expand...
Click to collapse
Haha, you never get up to 7500... My average on the latest ET is around 7800ish and pass 8000+ on the high end.. BTW, if you would like to try out the new ET, please give the .9 a run because I am be able to have an extra one hour comparing to the .8 without performance loss. The average battery life on my daily usage on .8 is about 4+ hours and the .9 is about 5+ hours. Please give some feedback if you try it, thanks..
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
azreal8 said:
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
Click to expand...
Click to collapse
It should be under /system/ect/init.d..
If you flash my zip file, everything should set up properly for users to use...
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
azreal8 said:
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
Click to expand...
Click to collapse
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.8GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
LetMeKnow said:
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.7GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
Click to expand...
Click to collapse
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
azreal8 said:
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
Click to expand...
Click to collapse
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
LetMeKnow said:
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
Click to expand...
Click to collapse
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
azreal8 said:
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
Click to expand...
Click to collapse
What does the failed message say - it probably tells you what failed?
Also extract the recovery log from TWRP after.
[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F
Q&A for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
@Cl3Kener: Big thanks for your hard work. Installed your kernel yesterday, and can definately see some improvements.
@ramjet73: Big thanks to you too. I followed your posts/instructions and flashed rastapop+uber and am happy i finally took the plunge.
Now for my question: I have the tricksterMOD and I can't see any color profiles (except the default). How can I apply other profiles? I only see one.
Regards,
On LiquidSmooth LP 4.0 with UBER-L 3.4.105
Governer = optimax
Scheduler = zen
Read Ahead Buffer Size = 3072
Everything is running smooth and fast! Good battery life!
Low brightness after install
Hello, I gave a question... When I installed a last Uber kernel L v4.10 from 9 December of 2014... I have a very low brightness... How can I fix it...
Also I cannot make OC more than 2.7 or 2.8 ... Phone doesn't boot... And how I can fix it...
Thank you for a answer
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Are there any negative consequences for clocking the minimum frequency at 96MHz?
Usb-otg f2fs
I'm currently using the latest version of UBER-L kernel (01/01/15).
I have formatted my Micro USB to F2FS and would like to use it with my phone. TWRP recognises the USB and mounts it successfully, but the ROM (OptiPop) does not mount the USB. Both mount the USB fine when it is formatted to FAT32.
Is it possible for me to use F2FS using USB-OTG?
Thanks.
Edit: Got it working by using the 'Stickmount' app. ^_^
FloGatt said:
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Click to expand...
Click to collapse
I disabled trimming and I dont see a difference with f2fs. I would conclude that it isn't necessary with f2fs
Is there changelog of the new kernel version?
FloGatt said:
Is there changelog of the new kernel version?
Click to expand...
Click to collapse
Its all on github. The link is on the OP of the original thread. (The one with the download links)
GPU clock not going above 450MHz
Hey, I'm using this kernel (latest version as of now), on a clean flash of Optipop (also latest as of now - 11/01) with F2FS.
I set the max gpu clock to 650000000 in the uber_v1.3.cfg file in /etc
(also by terminal as in the 2nd post just to be sure) (echo "650000000" > the path and all)
Apps like System Monitor Lite and CPU-Z confirm that the max gpu clock is 650Mhz (Adreno 330 @ 650Mhz).
I have also set the performance governor (in the config file, and I tried via synapse + UKM 3.6.1 too) (I have set synapse not to apply settings on boot, so that should not be interfering with the init config of uber kernel until I set something in it.) I have no other kernel tweaking apps anyway.
However, the clock only goes up to 450MHz no matter what. It goes directly to 450 when touching the screen due to the performance governor, so I know settings are being applied.
However System Monitor, CPU-Z etc all show, current clock: 450MHz, Max Clock 650Mhz.
Even benchmarking with GFX bench gives results basically identical to the stock Nexus 5 with 450MHz, so there is no performance and FPS difference that should be there.
I searched the developer thread and found a few posts from many months ago that the gpu overclock was working properly for many people, with an appropriate improvement in FPS and benchmarks, with a couple of people also having my issue, that whatever of 650/533/450 max I apply, gpu doesn't go over 450MHz. However I couldn't find any solution.. it stopped working properly at some point between those builds when Chet introduced 533/650 and now?
I can't post in the dev thread (less than 10 posts).
This is reproducible, right after a clean boot, not a thermal issue (am not overclocking CPU, not running any CPU benchmarks, temp is less than 50C).
Hope someone can help. Thanks!
Installed Optipop back onto my N5 today. After a few hours of the phone being on the UI starts to act up then eventually needs a reboot to get back to being functional. I then flashed UberL kernel and now my screen is fuzzy and glitches out. Never had this problem in the past with Optipop or UberL. Please don't ask if I dirty flashed or deleted the android folder. I completely wipe my phone before I install a new ROM. I have been installing ROMs for a good minute now and have never seen this before. I have tried at least 5 other rom/kernel combos.....none have the same affect as UberL and Optipop. Yes I've tried F2FS ONLY Permissive Only and EXT4/F2FS Permissive and Enforcing with no luck.
Has the issue with the missing charging icon when the phone is turned off and plugged in reappeared? I have System, Data, and Cache formatted as F2FS and flashed F2FS-ONLY-Lollipop-Kernel-Cl3Kener-Kexec-Permissive.zip before flashing UBER, but I am still having this issue. Everything else appears to be running smoothly.
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
sirarduin said:
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
Click to expand...
Click to collapse
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
JayR_L said:
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
Click to expand...
Click to collapse
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
sirarduin said:
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
So you are saying that fixes the issue with the cfg file?
JayR_L said:
So you are saying that fixes the issue with the cfg file?
Click to expand...
Click to collapse
After 2 Benchmarks, i can say that doing this fixed MY problem. Uber/sabermod is now working realy well for the performance. Uses AnTuTU to check if its working. It upgraded a lot the performance for me.
Which governor gives me more performance?
[email protected] said:
Which governor gives me more performance?
Click to expand...
Click to collapse
performance ?! but it will drain your batterie a lot.
Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.
First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated
First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.
for me
another one for me
last one for me
Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!
How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!
Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know
flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere
I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..
I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....
Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,
Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks