Related
DEVELOPMENT DISCONTINUED
Disclaimer:
You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
_motley kernel:
Current version features:
OC support (overclock) - frequencies: 1.200, 1.400, 1.504, or 1.600Ghz (recommend 1.4 or 1.5GHz). Default clock speed is [email protected]
UV support (under-volting)
I/O schedulers: optimized deadline (default) and noop
Governors: optimized interactive, on demand, conservative, and performance
vfp, vfp3, vfpv3d16, thumb, thumbee, swp, fastmult, edsp, half
USB charging enabled
JRCU implemented - RCU for SMP with a single CPU garbage collector
Auto-group scheduling
Built in cifs, NTFS, Xbox controller, tun, PS3, joystick, mouse support
Encryption features CONFIG_DM_CRYPT, CONFIG_BLK_DEV_CRYPTOLOOP, and CONFIG_KEYS
Stock hardware/software is all working with no known issues (Camera, GPS, WiFi, sound, headphones, sensors, market, video/youtube etc.)
Prerequisites:
ROM must be based on the stock Galaxy Tab 8.9 with TouchWiz (stock and Overcome ROMs have been tested)
ROM must be rooted and have CWM installed.
Make sure you backup your boot.img so you can flash your stock kernel back. You should have a full CWM backup anyhow.
An app like SetCPU if you want to overclock(OC) or under volt (UV). I recommend only overclocking up to 1.4 or 1.5 GHz. Try 1.4 GHz first and see if it works for your tab.
Make sure you download the correct version for WiFi or 3G (3G only supported on Android 3.2).
Make sure you download the correct version for Android 3.1 or 3.2.
Android Honeycomb 3.2
Version v2d for Android HC 3.2
Add "autogroup" scheduling (for some background see: http://www.linuxfordevices.com)
Add support for LUKS and other file encryption utilities (CONFIG_BLK_DEV_CRYPTOLOOP=y and CONFIG_KEYS=y). Ext2 formatted loop devices should work now, but still no luck FAT12 8.3 volumes. Let me know how it works! (thanks ZeroPDA)
Misc merges\bug fixes from Nvidia repo (tegra\video\hdmi fixes, ext4 memory leak fix, interactive gov div\0 fix etc.)
v2d (7310 WiFi) View attachment motley_v2d.zip MD5 640af1d30eff11124f17b7fcb4c6201e
v2d (7300 3G) View attachment motley_v2d_3G.zip MD5 640af1d30eff11124f17b7fcb4c6201e
Version v2c for Android HC 3.2
WiFi only feature addition - added CONFIG_IP_ADVANCED_ROUTER=y to properly support Cisco VPN (VPNC Widget). This was not required for 3G as it already has this kernel feature. Thanks to questionmark for providing the info and testing the change for us.
UV bug fix - v2a introduced a UV issue where it was no longer subtracting the UV values even though they were set properly in sysfs by SetCPU etc. Thanks to Crashdown12 for reporting.
Important - I recommend removing the option to set UV on boot before installing this new version, just in case you were down to unstable voltages.
v2c (7310 WiFi) View attachment motley_v2c.zip MD5 cbfdee00b5ce514bef88e4230f7d0694
v2c (7300 3G) View attachment motley_v2c_3G.zip MD5 bce4881b2716f410b2903f96fe347271
Version v2b for Android HC 3.2
USB charging is now enabled like the GT10.1 (thanks pershoot, stefansaraev). See the following for usage: how-to (thanks dpakrr)
Performance: implemented JRCU, an RCU for SMP with a single CPU garbage collector so that each and every CPU doesn't periodically participate in RCU garbage collection. This is popular in the Android kernel space since dual CPUs have come about (thanks Joe Korty).
Performance: added optimized deadline i/o scheduler which is now the default since it is great for SSD (thanks morfic)
Added switch to turn off TouchWiz at the kernel level (not really relevant until someone tries to build a vanilla ROM)(thanks pershoot)
v2b (7310 WiFi) View attachment motley_v2b.zip MD5 3446574b2024897e41bad69f7c699aca
v2b (7300 3G) View attachment motley_v2b_3G.zip MD5 d299579a1de0d1469bfcb99ed6afc1d4
Version v2a for Android HC 3.2
Same features as v1i kernel, but now works for HC 3.2
Now a version for P7300 3G
v2a (7310 WiFi) View attachment motley_2a.zip MD5 59bfb8b8f213517676e06b6d69f35080
v2a (7300 3G) View attachment motley_2a_3G.zip- MD5 b5b6ab4f3dffe29dce5a83f32dd7eba6
Android Honeycomb 3.1
Version 1.0i changes (current for Android 3.1):
Governor default changed to OnDemand, but only so we can properly set back to the preferred interactive governor on boot using SetCPU and other tools (let me know!).
I/O schedulers: NOOP now the default (minor read/write improvements), CFQ still available, Deadline removed for now.
Starting voltages increased for 1.504 GHz and above due to some instability issues reported. I recommend you UV 25mV or so if you already achieved stability as it was increased by 50mV. Higher than 1.5GHz is still experimental and not recommended. I have been able to run at 1.6GHz for the first time in this build.
v1i - View attachment motley_v1i.zip - MD5 ea77e46967aa4c917e8dd8c429dca724 (current for Android 3.1)
Version 1.0h changes (beta 1):
Touchscreen lag fixed. Firmware downgrades prevented within Melfas touchscreen driver.
UV bug fix, no known issues.
Governor fixes, SetCPU seems to set properly on boot now (edit: still some issues setting on boot depending on SetCPU configuration)
Version 1.0g changes (alpha 2):
Overclock to 1.504GHz+ (only 1.5 is stable, over is experimental only)
UV (undervolt) support (experimental, still in testing)
NTFS and Xbox now built-in. No longer need to mess with loading modules.
Applied some upstream kernel patches.
Version 1.0c (alpha 1/first release):
Based on Samsung open source kernel from opensource.samsung.com
Overclock to 1.2GHz or 1.4GHz (a future version will likely be able to clock to 1.504Ghz)
Installation Instructions
Backup with CWM
Put the zip on your sdcard
Flash zip file from CWM
Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.
Optional: if you need or want to restore your original kernel, restore ONLY your boot.img from the CWM advanced recovery option.
Thanks go to:
pershoot for all his hard work on the 10.1 kernel. I used his kernel as a working guide and used his delivery method (Anykernel)
alterbridge86\Overcome for CWM.
Koush for the Anykernel delivery method.
Samsung for releasing the source like they should
Tiamat team, RichardTrip\roggin and NVidia for their open source git repositories.
All the testers!
Let me know if I forgot somebody!
Git repository:
https://github.com/motley-git
FAQ
Q: What is a kernel and why would I need it? How is it different from a ROM?
A: The kernel is the lower level of the operating system, or the engine so to speak. It is a bridge between applications and the actual data processing done at the hardware level. The Android OS utilizes a custom Linux kernel. The stock kernel provided by Samsung limits the CPU clock speed (i.e. CPU frequency) and other functionality that the upper level operating system can request (like mounting NTFS hard disks, undervolting, encrption, using certain joystick controllers, mounting network shares etc.).
A kernel is different from a custom ROM. A ROM is a customized version of the Android Honeycomb OS and will also come with a kernel. Most ROMs will come with the stock kernel, they should designate which kernel they use. In other words, most ROMs provide a customized version of the upper level of the operating system including base services and applications.
Q: What do I have to wipe before I flash?
A: For kernel only flashes, like this one, you don't have to wipe anything.
Q: What does the zip file do when I flash?
A: When the zip is applied in CWM, it does the following things using Koush's AnyKernel method:
Unpacks your boot.img from into a temp folder (into ramdisk and zImage components)
Replaces your zImage, i.e. the kernel binary
Updates the ramdisk default.prop (sets ro.secure=0 for adb root shell and removes init.p3.rc lines that set frequencies and governor during boot)
Repacks the new boot image and flashes back to /dev/block/mmcblk0p3
Updates two kernel modules in the stock location /lib/modules
Q: Will I lose any customizations to my ramdisk provided by a custom ROM?
A: No, your should not due to the use of the AnyKernel method described above.
Q: Will other overclocking apps besides SetCPU work OK?
A: Yes, they should work, but just keep in mind that not all apps are able to under-volt. I will typically be using SetCPU for all my testing, so keep this in mind if you have problems.
Q: Will overclocking use more battery?
A: Yes, higher voltages equals more current draw (I=VR). It will depend upon your setup and individual usage scenarios to how much runtime you will lose.
Using the interactive governor, your tablet will scale down to lower frequencies when the highest clock speed is not necessary. At the lower frequencies, the tablet will not use more power than it does stock.
Q: What OC frequencies are safe?
A: From research thus far, 1.5GHz is the top end for every day use stablity for most tablets. However, due factory tolerances 1.5GHz still may not be stable for everyone. You may need to use 1.4GHz or even 1.2GHz. Many choose to run 1.4GHz since it still gives a great performance bump over stock, but less heat is generated, and it will chew up a little less battery.
Q: I set my OC frequency to X, but I don't think it is working. How do I test to know that it is working?
A: For 1.4-1.5GHz using the interactive governor, you should be able to see a Linpack score between 70-87 depending on what else is running on the tablet.
The ad-free version of Linpack is better because the ads can lower your scores unless you hit test at the right time when the ad is already loaded. If you keep hitting test at 1.5Ghz, your consistent higher scores should be around 78-85.
Verify the clock speed by using Linpack scores
Verify in SetCPU that the different clock speeds are being used periodically, most particularly the highest clock speed.
It is kind of finicky sometimes until you get it set right and sometimes after a new version is installed it will get finicky. After you get it set right, then it stays put on reboot and you should have any issues from there. I am still wondering if there isn't something I can do about it to force it honor any changes SetCPU requests to sysfs no matter what. This is the reason why I eventually set the default governor to On Demand and then suggest that you configure it to be Interactive in SetCPU (the recommended governor). This seemed to help trigger the proper acceptance from SetCPU on boot. Pershoot (the 10.1 kernel guru) suggested that it might be falling to conservative at the default frequency like when it goes to sleep, but not coming back. However,when it goes to sleep and I turn it back on, it always goes back to my 1.5GHz just fine. And when it's set and happy, it never has this issue on boot either. Maybe a second boot is all that it takes, but I would sure like to pin it down and understand it better. Let me know if anyone has any ideas.
If your Linpack scores suggest OC is not working, I recommend that you do the following:
Uncheck the SetCPU setting to "set on boot" for OC and UV settings. Don't set this for boot until you are sure you are good to go with your clock speed and UV settings.
Upgrade to the latest kernel version for your tablet if you haven't already (Choose, HC 3.1 or HC 3.2, then 7300 3G or 7310 WiFi)
Boot up and use SetCPU to set your desired OC frequency AND then setp to use the "interactive" governor.
Verify your linpack scores to make sure they are higher than stock (~50-55). See above reference scores and notes about ads slowing down the scores.
Q: How do I setup under-volting (UV)? What values should I use for each frequency?
A: Not all tablets are created equal at the factory. What works on anothers tablet may not work on yours.
Uncheck the SetCPU setting to "set on boot" for UV settings. Don't set this for boot until you are sure you are good to go with your modified UV settings.
Once the clock speed is verified (see previous question), run some bench marks (Linpack, AnTuTu, and Quadrant are good) and do some multiple-tab browsing sessions to make sure your tablet is stable. Watch some vids or whatever you like to do, this is the key.
If you are stable, step down your voltage at the highest clock speed by -25mV. Repeat the benchmarks and usage scenarios. If it fails (locks the tab), hold down the power key until it reboots and step back up +10mV and repeat until it is stable.
Repeat the UV calibration for the next lower clock speed and so forth. I don't typically mess with anything below GHz since those are stock values.
Q: So, what OC and UV settings do you use?
A: I typically run @1.5GHz -50mV and leave the rest of the frequencies as-is. For my usage, I don't find the CPU spending a lot of time anywhere else besides 216, 312, 1000, and 1504. Every other frequency is typically less than 1% of time in state. If folks can UV further and keep it stable, that is great. I don't worry about battery too much since I am mostly around the house and don't mind charging every 2-3 days.
Q: I noticed that the stock tablet does charge using a normal PC USB port. The tab say discharging with a red x but it seems to be charging. So do I really need to use the usb charging script?
A: I grabbed this fix from the 10.1 kernel base. I was wondering the same thing when I went forward with the code change.
Here is what I know so far. The change in the kernel allows the tablet to properly report the charging state properly back to the OS. After the fix, the USB charging seems to be much faster, but it may just be the reporting mechanism. Before, it would take forever to trickle up 1%. Now it really seems be a viable charging source, but still slower than plugging in to the wall of course. I have not however done any tests to prove this, but I think the mod is definitely worthwhile. Samsung should have done it like this stock, but I think they did not want to deal with support calls to troubleshoot charging via USB as it is not as fast and reliable.
That said, the option is there and folks have a choice on whether to activate it or not. Others, please report back on your experience on this topic.
Any chance this would work on the 3g version?
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
What is meant by "PS3" support?
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Hurrian said:
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Click to expand...
Click to collapse
I highly doubt that. Maybe it supports it over USB.
+1 on this feature added to OC... I feel the stock ROM is too slow...
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Jade Eyed Wolf said:
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Click to expand...
Click to collapse
Because ps3 uses a proprietary bluetooth protocol.
Android 3.1 has built in USB controller support, so ps3 controller should work over USB. If Samsung hasn't messed something up.
Def a long delay on wake up otherwise everything is running fine, thanks!
Def looking forward to a faster OC, would be nice to be able to test up to 1.7 like the Tiamat kernel. A GPU overclock option would be welcome too. Let me know if you need any testers.
Sixaxis app works fine on the 8.9, I use my controller via Bluetooth with my tab just fine. Guess it is good to know there is USB support, too.
alishankiti said:
Any chance this would work on the 3g version?
Click to expand...
Click to collapse
Sorry, but I don't think it has the right kernel options at the moment. Samsung has a separate source download for the GT-P7300 and I have not studied it to see if it is the same source. It may be possible to easily make it happen by using a different configdef to setup the kernel. We'll see about adding support in the future, however I don't have 3G (or even a 3G dongle) to give it a try so others would need to test it. Some of the 10.1 guys might be able to help determine whether this is a mountain or mole hill. If it is the latter, I am happy to give it a try at some point.
CanEpia said:
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Click to expand...
Click to collapse
Thanks for the update, you may be the second person to run this kernel
Hurrian said:
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
Click to expand...
Click to collapse
Yes, voltage control is definitely high on the list after all hardware and annoying glitches are addressed.
vfp and vfp3 are baked in already. I believe they were in the stock kernel already. As far as compiler optimization, I haven't done much playing with that. I tried to use the code sourcery toolchains, but I could never get the damn kernel to boot. I am currently using the Android NDK to compile. I even had to back off a version on these toolchains because it broke WiFi without any other coding changes. It's a very sensitive beast. If anyone has any known and proven compiler optimization for Tegra2 and ARM toolchains, I am happy to give it a try. I know that the toolchains are what do most of the magic for our CPU, so we would have to stick to whatever is supported in the toolchains.
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
This is for supported the PlayStation 3 controller via USB (kernel option CONFIG_HID_SONY). Kernel option CONFIG_INPUT_JOYDEV is also built-in for supporting other generic joystick devices. I am not an avid gamer, so you guys will need to help out with the testing with this stuff.
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
randomb said:
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
Click to expand...
Click to collapse
Thanks for testing from Denmark Good thing I posted it last night before bed!
Your lockscreen seems to be much worse than I am experiencing. I get the same 2-3 sec behavior no matter what my cpu speed is. Not sure this why this is different for you. Even if my lockscreen is turned "off", I still get the 3 sec delay on wake. I like a good sleep, but this is a bit more like a drunken coma.
poolguy said:
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Good to hear poolguy, thanks.
Kernel is running nicely, as stated earlier it is about a 2-3 second wait time on the lock screen. The only issue I had is that the CPU was pinned at 1 ghz, this issue was solved by switching governors and then back to interactive. Now scaling nicely. Thanks for this.
Sent from my GT-P7310 using Tapatalk
This is all guide with bug fixing on minicm7 2.1.X
Screen Cut:
Only in CWM/CWR
NMEAListener:
I think NMEAListener is GPS
I found that gps.conf is europe settings
since that i have no problem with it
for non-europe residence Here Patch
Compass:
Wait till nAa fix
Video Recording Lag:
did you experience this
use this file Download
Auto Brightness:
use this tutorial
Code:
1. disable auto brightness first in display
2. go to cm settings --> display --> automatic backlight --> choose use custom and allow light decrease
3. tick edit other level
4. set number of levels to 13
5. look at this pic [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874309&stc=1&d=1327627892"]Here[/URL] And [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874311&stc=1&d=1327627892"]Here[/URL]
6. enable auto brightness in settings (not cm)
7. restart
8. enjoy
Android market app won't show up:
clear data on app settings
Just use recommended tweak:
Non-Recommended tweak make ur phone less stable
Recommended:
SuperCharger
Ram Manager / PRO
Juwe Ram's script
Etc...
Non-Recommended
Build.prop tweak
init.d tweak
IPV4/IPV6
Etc...
End of first post continued in 2nd post
Guide for Minicm7
Notice ADW launcher Lag use this settings:
Code:
1) Screen Preferences - Desktop scrolling speed - set to something low-ish like 150-200, default settings are just plain moronic here. Desktop overshoot should be fine at 30 or 40.
2) Drawer Settings - Horizontal Drawer definite on (this is far superior to the scrolling drawer if you have more than a few apps, and feels much smoother).
3) Drawer Settings - Zoom effect speed - 400 is a decent setting, default was way too high.
4) Drawer Settings - Columns/Rows - 4x4 is a nice setting for portrait, if you don't like a crammed screen.
5) System Preferences - Wallpaper Hack - check this. If you have issues, change wallpapers to something of a sane size.
6) System Preferences - Use Screen Cache - check this.
7) System Preferences - Scrollable Widget support - you should start with this unchecked. Only check it if you have issues with some
Make ur phone fast without tweaks?
here my perfomance settings
Go to CyanogenMod Settings --> perfomance settings
Code:
1.) Set compcache ram usage to 18%
2.) Enable use jit
3.) Disable Surface Dithering (optional)
4.) Enable 16bit transparency
5.) Enable Allow purging of assets
6.) VM heap size 48mb
7.)
SDcard cache size 1024kb Class 1,2
SDcard cache size 2048kb Class 3,4
SDcard cache size 3072kb Class 4,5,6,7,8
SDcard cache size 4096kb Class 9,10
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 245mhz
3.) Max Cpu frequency 691mhz+ (optional)
4.) Set on Boot
Make minicm7 more battery save?
here my battery save settings
Note: this settings overwrite "Make ur phone fast without tweaks"
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 19mhz
3.) Undervolt
4.) Set on Boot
final step: Delete Unused App
Extra Section
Coming Soon
End Of My Post
LtHuNTer_StepheN said:
Don't use any tweaks:
tweaks make your phone fast but less stable
and don't use xloud and mobile bravia
they are fake
Click to expand...
Click to collapse
+1 10char..
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
hixvolnutt said:
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
Click to expand...
Click to collapse
For Perfomance it's better set 48mb
this help app memory management
this heap size is usefull for HD games
Oh i forgot
i will edit it
for that tweak is already tested
what i say is
Code:
build.prop tweak
mobile bravia engine
and useless tweak
for that tweak it may increase stability
i will edit so people understand
Post Updated
Thanks
Is there any way to fix compass?the compass is somehow inverse
for auto brightness setting, how many level are you using? Ultra brightness enable or not?
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Post Updated
LtHuNTer_StepheN said:
Post Updated
Click to expand...
Click to collapse
Oops, i'm still using nAa 08...maybe because of that...0_x
Sent from my E15i using Tapatalk
bayumahendra24 said:
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
i think screen cut happen with smartass v2
D E V I L said:
i think screen cut happen with smartass v2
Click to expand...
Click to collapse
Flash the new nAa-08b kerner. This fix the problem
Hi!! I have just one question. The tethering wifi always disconnects when screen turns off. I tried wi-fi settings, advanced, never sleep but does not work. Do you have other solutions? Thanks
still score highly!!!
plus avent updated kernel and rarely get screen cuts!!
so id say great rom plus kernel!!
flegga92 said:
Flash the new nAa-08b kerner. This fix the problem
Click to expand...
Click to collapse
Still using nAa 08 (havent change kernel because what i see on the changelog, the difference between nAa 08 and 08b only the screen cuts fix) with:
- Cpu freq 19-600mhz
- smartassv2 on
- undervolt on
- bootanimation enabled
No more screen cuts since my prev post.
Screen cuts SOMETIMES only appear when i'm in cwm req...thats good enough for me..
For the video lag fix,does it work with other rom which have the same problem?flash with xrec or cwm?
Hello to everyone and excuse me if my question is probably going to be dumb (for sure it's an OT so please forgive me about that) but I'm quite clueless about the issue I'm experiencing and I hope to find an advice here.
I own and X10 mini with MiniCM 2.1.6 and 2.6.29.6-nAa-08 kernel. Everyhing's fine, really a great piece of work that has put new life into my beloved X10 Mini but I'm experiencing the 'screen cut' issue that's discussed here too: it happens only with some apps (Labyrinth for example) but it happens and I'd like to get rid of this.
I don't know if it could be an issue related to the apps not being designed for Gingerbread but I don't think so because I expect something different should this be the case.
I've read that the kernel nAa-08b is intended to solve this issue but it seems (maybe I'm wrong) that it isn't suitable for my X10 mini (I've made some digging around and the latest kernel version for my mini seems the one that I've already installed while the 08b seems to be intended for the X8). I'm sure that the reply is already around here but I couldn't succeed in finding it though I've read a lot (really a lot!) of posts here and there, especially on the official thread:
http://forum.xda-developers.com/showthread.php?t=1068553
where unfortunately I couldn't post because I'm a new member with less than ten posts. Some advices? Thanks anyway!
very good guide
thanks you very mach!
post updated
sorry im busy lately
OK as Fluxi XX kernel is becoming more and more popular it seems a perfect time to split the chit chat going on in the Development thread.
Please use this thread for all your non-development chat and sharing settings, battery life screenshots etc. If you're unsure about where to post your questions then please post them here and you'll get lots of other users who are willing to help you.
The original German forum for myfluxi can be found here: http://www.android-hilfe.de/kernel-fuer-samsung-galaxy-s2/236546-aosp-aokp-kernel-04-05-12-fluxi-xx-kernel-ics-xxtweaker-app-xxtouch-recovery.html
The new development thread is here: [AOSP/AOKP-KERNEL] Fluxi XX Kernel ICS [wakelock and drain-free slide2wake for SGS2]
Downloads for latest version:
Kernel CWM download: fluxi-kernel-sgs2-XX.03_s2w_b3.zip
xxTweaker apk download: fluxi-xxTweaker-0.4.0_beta1.apk
Slide to wake is currently beta and enabled by default but to disable it do the following in ADB, terminal emulator or a script (if you can get it working):
echo "0" > /sys/devices/virtual/sec/sec_touchscreen/tsp_slide2wake
If you're going to post bugs please do not just post "My phone is slow", "xxTweaker is not working". Remember if you have issues you need to help myfluxi/others help you so post logs to help diagnose your issue. Here's how to get the logs using xxTweaker:
1) Open xxTweaker
2) Scroll down to xxTweaker option (last in list)
3) Scroll down to "DEBUG AND REPAIR" section
4) Select "Debug system logfiles"
5) This will place a file in /sdcard/xxTweaker/logs
6) Attach this file to your post detailing exactly what's happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to post as much detail as you can along with your attached logs describing the issue you have and if possible how to reproduce it something along the lines of:
Issue experienced: e.g. SOD, freeze, lockscreen unresponsive, slow mo bug etc
What were you doing: Brief explanation of what you were doing when it happened (not applicable to SOD)
Your setup: Are you running stock settings, overclock/underclock/undervolting, governor/scheduler etc
Can it be reproduced: Is it consistent or was it a one-off and if it can how?
If you're new to the kernel then this is the best place to ask any of your Fluxi related questions.
If you have any ideas about how to improve this thread then please post your ideas or if you have any useful how-to's etc related to using the kernel/xxTweaker app then also post these and I can quote your posts in the 2nd post.
Thanks for helping keep the development thread on topic.
This is quoted from the other thread to help readers: (Thanks to xator91 for writing it)
xator91 said:
FAQ
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep.
Q: I have setted below maximum Suspend 500 MHz, 800 MHz is also used as the step. Why is this so?
A: "The device" wakes ALWAYS at 800MHz and goes to sleep as well, regardless of which settings are made. The hardware selected 800Mhz to ensure stable operation - change by software impossible.
Q: I need the "intermediate steps", ex. 300 or 700MHz, the CPU frequency table is not. Can I change this?
A: In theory: Nope! In practice: The option of individual frequency steps is a nice gimmick but virtually unnecessary as intelligent as governor select ondemand, conservative, or the interactive dynamic frequency target. The driver provides the steps of the governor decides. Future versions of the SoC Exynos therefore also use 100MHz steps.
Q: The xxTweaker remembers any settings, what is going on?
A: If only some Tweaker settings are not applied, I made a mistake (because I forgot to add them). If no settings are applied, there is something wrong with the permissions. Either missing from the root and the tweaker or directory /data/data/net.fluxi.xxTweaker/shared_prefs chmod'ed is wrong. The latter does the installer script at startup, if you like, it can also manually delete them.
Q: When is the superuser request every action, you can turn that off?
A: Simply update the su binary file: app drawer/superuser/Preferences/ "Press to check for updates" / Important "update anyway" / "Allow"
Q: I can not download, I just get a file "download.php".
A: The Android browser does not understand the PHP script on the server. Either 1 Rename the file and provided with the correct extension, eg "download.zip" or try another browser (Opera, Chrome) or use the PC.
Q: When the device wakes up from sleep or change the lighting conditions, the display is usually too bright / dark. It then takes a few long seconds to realize it, how bright it really is and then it adjusts the brightness. Is there a fix?
A: Yes and no. First, this is completely independent of the kernel. Basically, this is a source CM9/Open Source/Samsung-****ing-and-hold-consorts-important-things-to-lock problem. The HAL is the light sensor from Samsung is not documented and can not read CM reasonable values. Use the open-source sensor HAL (xxTweaker | System | Exynos sensor HAL) and the CM settings for automatic brightness (CM | System Settings | Display | Automatic Brightness | Step Customize | Editing levels). However, there is the possibility that thereafter the compass haywire.
Q: Help, BLN works in applications X and Y but not Z!
A: The poor kernel is innocent. BLN is as follows: The Android app generates a notification event, it triggers the liblight module, which writes to the sysfs kernel, liblight kernel module and have to rely on the information from the user space, so the ROM. In other words, from the perspective of the kernel, either always or not working.
Click to expand...
Click to collapse
Moved from the other thread:
Screenshots:
Settings:
System
I/O - Noop
CPUIdle Mode - AFTR or LPA
SCHED_MC - Disabled
Display
Brightness -5
Movement Hysteresis 2
Touch Preset - Gingerbread
CPU
100-900Mhz
CPU Voltages
900 - 1025
800 - 1000
700 - 1000
600 - 950
500 - 950
400 - 925
300 - 900
200 - 875
100 - 850
Max Suspend 500Mhz
Min Suspend 200Mhz
Governor
Conservative
Governor Settings:
Ram3n Tweaks from here:http://forum.xda-developers.com/showthread.php?t=1691129
Hotplug
Up - 90
Down 30
Dynamic Hotplug
Bus Frequency
30 Up
23 Down
Voltage Table: 1050,950,950
GPU
67Mhz - 825
100Mhz - 875
200Mhz - 950
BLN & LED
Both Off
Modem
LPX
Apps Used:
Opera
Texts messages
Wi-Fi
Boid
Friendcaster
Market
Other Apps too...
Much better this way
superleeds27 said:
Moved from the other thread:
Screenshots:
Settings:
System
I/O - Noop
CPUIdle Mode - AFTR or LPA
SCHED_MC - Disabled
Display
Brightness -5
Movement Hysteresis 2
Touch Preset - Gingerbread
CPU
100-900Mhz
CPU Voltages
900 - 1025
800 - 1000
700 - 1000
600 - 950
500 - 950
400 - 925
300 - 900
200 - 875
100 - 850
Governor
Conservative
Governor Settings:
Ram3n Tweaks from here:http://forum.xda-developers.com/showthread.php?t=1691129
Hotplug
Up - 90
Down 30
Dynamic Hotplug
Bus Frequency
30 Up
23 Down
Voltage Table: 1050,950,950
GPU
67Mhz - 825
100Mhz - 875
200Mhz - 950
BLN & LED - Both Off
Modem: LPX
Apps Used:
Opera
Texts messages
Wi-Fi
Boid
Friendcaster
Market
Other Apps too...
Click to expand...
Click to collapse
Which rrom are you using? Also which kernel version? Also is that with stock battery or extended?
Sent from my GT-I9100 using Tapatalk 2
awaisuk said:
Which rrom are you using? Also which kernel version? Also is that with stock battery or extended?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
See my Sig. Extended Battery too
superleeds27 said:
See my Sig. Extended Battery too
Click to expand...
Click to collapse
Really off topic: what's your theme? Heheheeh.
marcellocord said:
Really off topic: what's your theme? Heheheeh.
Click to expand...
Click to collapse
Flow Theme for AOKP/CM9. Available on the Play Store
Guys, not sure if this is the right thread but.. I've got a 46-minute wakelock with the latest kernel.. Anyone know what to do to get rid of this?
Attached logs..
My phone doesen't sleep very well..
The screen is off during the night but the phone is active and i lost about 10% battery..why?
Sent from my GT-I9100 using Tapatalk 2
Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
---------- Post added at 02:52 PM ---------- Previous post was at 02:21 PM ----------
francesco.cordella said:
My phone doesen't sleep very well..
The screen is off during the night but the phone is active and i lost about 10% battery..why?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Post your BBS.. Then we may have some clue of whats going on..
Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2
francesco.cordella said:
Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Keep in mind that wifi also consumes some battery I wouldn't let my phone on while i'm sleeping. At least I would kill the open apps and turn off wifi.
Sent from my GT-I9100 using Tapatalk 2
LogeshMenon said:
Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
---------- Post added at 02:52 PM ---------- Previous post was at 02:21 PM ----------
Post your BBS.. Then we may have some clue of whats going on..
Click to expand...
Click to collapse
Well SlimICS is CM9 with cherry picked bits of AOKP. Saying that though. I still got better battery life with the proper CM9
LogeshMenon said:
Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
Click to expand...
Click to collapse
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too. I personally leave everything stock clock and voltage wise and just use my phone as I see fit. Remember the less you monitor and worry about the battery the better it will be Battery life should never choose your ROM, whether or not it's useful to you and what you like should
francesco.cordella said:
Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It's never best practice to judge battery life on the first cycle, just use it, drain it, charge it, then after a few days try monitoring your battery to see what it's doing, but if it's lasting you a day then shouldn't be a problem, or have I just not got as high expectations as everyone else?
superleeds27 said:
Well SlimICS is CM9 with cherry picked bits of AOKP. Saying that though. I still got better battery life with the proper CM9
Click to expand...
Click to collapse
Slight correction it's not CM9 it's AOSP from Google sources with cherry picks from CM9 and AOKP
AvRS said:
Slight correction it's not CM9 it's AOSP from Google sources with cherry picks from CM9 and AOKP
Click to expand...
Click to collapse
There's only two types of ROMs: Samsung Stock and CM9. Every other ROM is a modified ROM from those two. Well, there's b2g also, but no one uses it.
AvRS said:
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too. I personally leave everything stock clock and voltage wise and just use my phone as I see fit. Remember the less you monitor and worry about the battery the better it will be Battery life should never choose your ROM, whether or not it's useful to you and what you like should
Click to expand...
Click to collapse
I find it strange that the battery life I get on CM9, i have never achieved on any other ROM.
SlimICS
Several AOKP Rom's
When I've used the Roms I've always used Fluxi and the same kernel settings, plus, given it chance to settle too.
CM9 for some reason seems to consume less battery when the screen is on!
AvRS said:
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too......
Click to expand...
Click to collapse
Bro, I've freezed about a total of 18 system apps from slim, extreme UV, UC 100 ~ 800, tweaked governor settings, gpu max step is 160, gpu UV more extreme than superleeds, only absolutely necessary apps, only inverted apps, and full black settings, no fancy color themes, autostart disabled of some services, sync only required apps and tons of other cherry picked tweaks, and i never get past 13 hours, and with screen of 2 hours. Anymore tweaks, and i rather sell off my S2 and get a nokia 3310..
The only thing i may be off the battery saving method is i'm using floating image live wallpaper, as i like to see my wife and daughters photo on my screen.. And even made sure that floating image does not misbehave, process usage and wakelock by FI, is very minimal.
My aim, is to have a minimal of 20 hours with screen usage of 4 hours.:fingers-crossed::fingers-crossed:
This is due to me sometimes being on the road and especially when i'm out on the boat fishing (hobby) for a few days...
I have no qualms when i'm in office or at home, i'm in front of my laptop almost 90% of my wake time.
I think that don't need setCPU (or CPU master Pro)
Because I installed cpu spy, it show cpu working at 312MHz is 80% and 832MHz is 11%
May be it's enough smart to exchange between frequency chip max and min.
First of all.... Please dont create question threads in dev section..
Read this thread Questions should not go here
To answer your question... set cpu and cpu spy are apps made for 2 different purposes.. cpu spy gives statistics or info on whats going on cpu... that too on software side..
Set cpu is an app to "set" governors/io schedulers/ cpu freq etc... also it provides info and info is related to hardware side..
So back to thread title.. yes set cpu or any other app which might do same actions as set cpu is needed for any device including duos only when you have a custom kernel which has many features to apply..
I hope this answers your question.. please do create threads in Q & A section for this.. i will request The-Captain to move this thread..
hit thanks button! If above post helps you..
Sent from my GT-S6102
First, thank to nitubhaskar!
Sorry for this,
I've never install setCPU or CPU master,
I only install CPU spy and it's show me that performance. I think my phone auto exchange it (don't need install other app to overclock CPU)
Or maybe that app is installed in kernel?
windows112009 said:
First, thank to nitubhaskar!
Sorry for this,
I've never install setCPU or CPU master,
I only install CPU spy and it's show me that performance. I think my phone auto exchange it (don't need install other app to overclock CPU)
Or maybe that app is installed in kernel?
Click to expand...
Click to collapse
No apps are installed on kernel...
If you use no frills cpu (free) or set cpu(paid) from play store.. you will get options to use full features of custom kernel.. but without these apps also you can use custom kernel. You wont be use full features.. thats all... so its your choice.. i suggest install no frill cpu then use it and see..
hit thanks button! If above post helps you..
Sent from my GT-S6102
Hi everyone,
I just download the OTA of Lollipop on my Shield Tablet. Here the results of many benchs. Lollipop update work great, but has less options than Kitkat. Unfortunately, Power management disappear. I hope Nvidia reintegrated it later. I had a bug in Riptide GP2, the jet ski leans to the left , you can not recalibrate. Wifi seem to be stronger than KitKat.
Edit : Power management Shield found, it's hidden in battery menu, bouton option=>Power management Shield. But it's much less complete than Kitkat(No framelimite, no personnal profil)
Edit 2 : Orientation Fixed after a calibration with Gps status & toolbox.
Antutu : + (+1000~1500 points)
CF Bench : +(1000 points and % much higher)
Quadrant : +(Too much x) )
Sunspider : - (between 30ms to 70 ms)
Geek Bench 3 : =
3D Mark : =
Gfx bench : + (driver overhead +11%), - (fillrate -6,4%)
Vellamo : ? (Can't compare)
Android : + (JVM - ~300 ms)
Add Vellamo and Android Bench
Antutu score here:
Snah001 said:
Antutu score here:
Click to expand...
Click to collapse
32 Gb version seems to have better scores
Faster 32Gb emmc memory than the Wifi version!
The old power management options are still there, but are even more hidden than the ones you found.
Create a Settings Shortcut widget, choose Power saving, and you'll find all the old options there under Shield power control.
Lte version with Lollipop.
Shield 16Go Wifi, no root, no tweak, CPU set to Nvidia Optimized mode. Pcmark result :
Same test with CPU set to max performance :
debunk said:
The old power management options are still there, but are even more hidden than the ones you found.
Create a Settings Shortcut widget, choose Power saving, and you'll find all the old options there under Shield power control.
Click to expand...
Click to collapse
I think it's hidden for some reason. A no power-user can't find this. Hope this option come back in settings in next update.
Thanks everyone for your report
Root needed for this?