Related
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
THE LATEST NIGHTLIES HAVE BEEN REMOVING VOLTAGE CONTROL STATS, SO PLEASE REMOVE ALL OVERCLOCKING BEFORE FLASHING A NIGHTLY OR AN UPDATE FROM HERE.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. To undervolt, use either Voltage Control, SetCPU, or Control Freak.
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to have feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/android_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not an error. Don't freak out. Let it boot.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.
CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz (Something for you to shoot for, Shaolin. )
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-Upsteam changes to modem_ctl
-Upstream tvout drivers (Totally untested on my end, so i dunno if they work)
-fsa usb switch suspend
-Overvolting cap
-add the kernel version (v5.2) to the kernel name.
v5.3[May 16]
-Upstream changes to initial flash/initramfs
-Upstream changes to battery calculation percentage
-Some other stuff, nothing really important. Its all upstream changes anyway.
NIGHTLIES/WHENEVERS:
#1[May 25]
+Working ril (data + service)
+working gps
+switched to mfloat=softfp as it gives slightly higher linpack scores
+Voodoo sound v9
+LZO compression for a faster boot up time.
Known bugs:
Rild crashes in areas with no service, causing a hard reboot. (Can anyone tell me if this happens on the stock kernel?)
#2[May 27]
+Actually working ril (no more reboots)
+Optimized for size
+Updated to 2.6.35.13 kernel (No, I dont have a changelog. There is one on the internet somewhere. Needless to say, its huge.)
+Probably some other stuff.
Known bugs:
Bln is finicky on this build, try reflashing/rebooting if it doesn't work at first.
#3 [May 29]
+States table in voltage control kinda works, but is buggy.
+disabled ext2
+re-added 1.6Ghz with a higher voltage (be careful guys).
+upped 1.55ghz by a few Mhz so it should be one or two above rather than below.
#4 [June 4]
+Disabled the states_enabled_table again, cause voltage control was really sketchy about keeping the states properly enabled. Hopefully the new rewrite will help.
+Fascinate support
#5[June 28] UNTESTED
+All upstream merges
+GPU bus clock speed modifiable using Control Freak
+Other stuff that I can't remember or have time for
#6[July 12]
+Upstream changes
+Fixed BLN (For whatever reason, it won't work after booting into recovery. Do a normal reboot, and it'll work).
+Reenabled the debugging, cause it was causing issues
This is nice!! Waiting for Voodoo fixes!
So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App
chipsa964 said:
So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?
born_fisherman said:
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?
Click to expand...
Click to collapse
There is, but it doesn't fix everything g that is necessary. You need the update zip.
Sent from my CM7 powered captivate
It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!
boardsportsrule said:
It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!
Click to expand...
Click to collapse
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.
Would these recent captivate cm7 voodoo kernel be helpful to integrating voodoo into your oc kernel?
http://kang.project-voodoo.org/
Voodoo sound is almost done, either tonight or tomorrow. Then, ill look at making this compatible with xan's UV app. Bln is probably going to be last, as it looks like the most work. There is currently no bln for any nexus s kernel, so ill have to see if it'll work.
Sent from my SGH-I897 using XDA App
Dlev7 said:
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.
Click to expand...
Click to collapse
Yeah, just flash it over top.
Sent from my SGH-I897 using XDA App
This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing
GGXtreme said:
This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing
Click to expand...
Click to collapse
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App
merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.
slifer315 said:
merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.
Click to expand...
Click to collapse
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App
TheEscapist said:
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
actually there aren't any issues. I've been using a kernel I built after the pull for several days now.
Sent from a phone, playing a phone, disguised as another phone.
TheEscapist said:
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Of course. MKV support is definitely not a primary feature of a kernel, but it sure would be nice. Also, I'm not talking about a codec, I'm talking more of a demuxer that simply streams the H.264 and audio streams as if they weren't inside the MKV so the hardware could play them like any MP4 (kind of like an Android equivalent of Haali Media Splitter).
I'm giving this a try...i really like the fact that I can choose how my cpu scales....hoping it helps battery life a little...also looking forward to you adding uv...
Sent from my Captivate using XDA App
Testing now. While I'm not particularly interested in the OC, the fact that you're using SetCPU and it's working makes me want to see if I can UC this. The default kernel doesn't play too well with this.
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
Hi,
Since I'm not yet able to post directly into the main thread, I'll post some opinions and experiences here.
The original Thread: http://forum.xda-developers.com/showthread.php?t=1364411
Current setup:
ROM: NEXUS MV 2.12.25
Kernel: GLaDOS 2.5 CFS - 3.0.8
So far, great ROM at all.
No reboots, no crashing apps...
But there are some things a bit annoying:
- On the NSTools, the "backlight dimmer" function only disables the capacitive buttons after the selected time, doesn't change anything in the display (I really don't know if it's a bug or not);
- Most of the times (not always) when I press the button to lock screen, after the animation the screen "flashes" and only after that I hear the "click" sound, but I think it's more a kernel issue than a ROM issue;
- The Assasin's Creed Revelations Game doesn't load the Main Menu completely, only the title appears and I can't select anything. I've reinstalled it and the problem still occurs, but I don't know if it's a ROM problem or some crazy incompatibility.
And also I'd like to send my suggestions:
- I've used another ROM (wich I really don't remember exactly what was) with a launcher where there was an option to prevent the apps menu to slide into the widgets, it would be nice to have it here too... (don't know if it can be implemented on ROM or only on the Launcher)
- I miss an option to enable/disable 3G data connection on the top menu of the slider, like CM7.
I can't think on any other thing to add for now...
The ROM is really fast and stable, thumbs up to MarkVis
Keep the good work!
I've noticed some serious problems after updated to NovaLauncher beta 7. Whatsapp hangs many times during use and system says "low RAM" when I try to send pictures via whatsapp.
I've changed back to beta 5 and still had some hangs and crashes.
I really don't know what's the relation between Nova Launcher and Whatsapp, but I'll try the new GLaDOS v.2.8 to see if I have any changes.
Sent from my Full Android on Crespo using XDA App
Following what was posted on the GLaDOS thread...
http://forum.xda-developers.com/showpost.php?p=20935218&postcount=1843
endursa said:
i recompiled the framework-res.apk with the mentioned bluetooth adapter quick switch set to false and now my deep idle status shows TOP=OFF usage
please be aware that i only tested this file on the OTA 4.0.3 IML74K Rom!
just Flash from recovery!
any other rom on the same base could work with this zip file, but i don't assist in repairing any other roms!
To get the original framework-res file from your Rom back just extract the framework-res.apk file from the original rom zip and replace the one in my uploaded package!
Click to expand...
Click to collapse
I've tried it with various versions of GLaDOS kernel and MV ROMs and it doesn't work, my phone hangs at initialization and keep on an infinite loop.
Also doesn't work with AOSP+ ROM, same infinite loop...
ledzpg said:
Hi,
Since I'm not yet able to post directly into the main thread, I'll post some opinions and experiences here.
The original Thread: http://forum.xda-developers.com/showthread.php?t=1364411
Current setup:
ROM: NEXUS MV 2.12.25
Kernel: GLaDOS 2.5 CFS - 3.0.8
So far, great ROM at all.
No reboots, no crashing apps...
But there are some things a bit annoying:
- On the NSTools, the "backlight dimmer" function only disables the capacitive buttons after the selected time, doesn't change anything in the display (I really don't know if it's a bug or not);
This is the intended functionality, to turn off the capacitive buttons LEDs off, not the backlight/SAMOLED for the whole display
- Most of the times (not always) when I press the button to lock screen, after the animation the screen "flashes" and only after that I hear the "click" sound, but I think it's more a kernel issue than a ROM issue;
Common problem with the brief flash while locking, most people have it and i'd imagine some a bit worse than others. The click and similar sounds on my Nexus S have always lagged to some extent, nothing has changed for me (though i turn all of this off anyway).
- The Assasin's Creed Revelations Game doesn't load the Main Menu completely, only the title appears and I can't select anything. I've reinstalled it and the problem still occurs, but I don't know if it's a ROM problem or some crazy incompatibility.
Lots of apps are still not updated (or won't be updated) for ICS, something which we may have little to no control over. This sounds like one such issue.
And also I'd like to send my suggestions:
- I've used another ROM (wich I really don't remember exactly what was) with a launcher where there was an option to prevent the apps menu to slide into the widgets, it would be nice to have it here too... (don't know if it can be implemented on ROM or only on the Launcher)
Pretty sure some launcher replacement apps can do that, and roms like CM9 alpha probably offer this.
- I miss an option to enable/disable 3G data connection on the top menu of the slider, like CM7.
Extended Controls and Widgetsoid provide this functionality in nearly the same way as CM7/CM9
I can't think on any other thing to add for now...
The ROM is really fast and stable, thumbs up to MarkVis
Keep the good work!
Click to expand...
Click to collapse
ledzpg said:
Following what was posted on the GLaDOS thread...
http://forum.xda-developers.com/showpost.php?p=20935218&postcount=1843
I've tried it with various versions of GLaDOS kernel and MV ROMs and it doesn't work, my phone hangs at initialization and keep on an infinite loop.
Also doesn't work with AOSP+ ROM, same infinite loop...
Guess those ROMs have some modifications which break that stock framework file, the same one works perfectly on my stock ICS. I'm sure the updated file will be added into some ROMs as standard soon.
Click to expand...
Click to collapse
I need to write this because answering within the quotes doesn't contribute to the 10 letter minimum
Harbb said:
I need to write this because answering within the quotes doesn't contribute to the 10 letter minimum
Click to expand...
Click to collapse
Yeah, I've noticed some things of your answer after a good time reading... hehehe
And at some part of the main threads (need to search again), somebody posted about how to end the screen flash after pressing the lock button, I've just didn't tested yet.
But thanks for the reply, I keep reading the threads and testing almost every new ROMs released to see if the deep idle correction is already implemented or not hehehe
That's just a bluetooth fix though, if you turn bluetooth off deepidle should work perfectly fine. This would only really be a problem for you if you use a bluetooth earpiece, headset or car loudspeaker.
I always keep bluetooth and gps disabled unless I need them, but even this way I only got the TOP=ON deep idle, not TOP=OFF.
That's why I was trying that fix
I'm starting to think that's the GTalk's camera thing...
{
"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"
}
[T]he [M]ost [C]lean
CyanogenMod 7.2.0
19.05.2013
Download:
http://code.google.com/p/forumber-projects-for-u8800/downloads/list
Changelog:
18022013 ----> 19052013
- Update WiFi power control changed by dzo
- Some fixes for SD Card detection changed by dzo
- CPU voltages are changed for more battery life
- Add force phone mic with headphones & fix speakerphone echo by ksatta
- GPU driver was using offical drivers. But now, The system uses CyanogenMod GPU drivers. The new drivers decode/encode videos better,more battery friendly. And also fixes some graphic bugs in some games (like Dead Trigger,Vector)
- X5 Settings is moved to Settings and removed some useless features.
- Camera drivers are changed. Auto focus improved in photo/video capture.Fixed the problem of blurring while capturing video.
- Updated Synaptics Touch Screen driver. It's more responsive now.
- Battery life is improved.
- ZRAM turned on by default.
- All native tethers (WiFi & USB) are working
29012013 ----> 18022013
- WiFi driver changed to genokolar's driver. It may slower but more stable than offical wlan driver
04012013 ----> 29012013
- "Phone sometimes going to bootloop on bootanimation" is really fixed now
- WiFi drivers are updated from offical GB by Huawei.
- Audio drivers are updated from lastest ICS drivers in kernel
- Atmel Touch Screen driver updated by me (increased feedback,fixed the lag). Now, as good as in 2.6.32.9
- Other updates
01012013 ----> 04012013
- Added SmartAssV2 governor
- Added & enabled bfq i/o schulder by default
- Keypad led brightness is reduced
- Added haptic feedback for soft keys support. You can enable this in X5 Settings
- some fixes for bluetooth problems
- Disabled second mic and voice quality is improved
- Added X5 Settings
- changed some voltages for system stability and battery life. also You can change voltage volues with Antutu CPU Master
- Lag on Atmel TS is fixed but I'm not sure,please give me a feedback about this
- Font changed to "Ubuntu" font
16122012 ----> 01012013
- Sensors are updated. All of sensors are working
- Compass fixed
- Added some tweaks for battery & stability
- This update will wipe dalvik-cache so the first boot after update may take longer than other
09122012 ----> 16122012
- "Phone sometimes going to bootloop on bootanimation" is fixed
- Disabled Beats Audio,Added DSPManager
- VSYNC turned on,battery will not draining
04082012 ----> 09122012
- Builded from lastest CyanogenMod source so base is fully changed
- Kernel Changed (with a lot of updates)
- Some libraries taken from LeWaOS
- Fixed a lot of updates
- etc
12072012 ----> 04082012
- Beats Audio added,DSP Manager deleted
- Bravia Engine updated
- Themes comes by default and ICS Theme is enabled by default.
- Revert to genokolar's CM7 and I fixed a lot of bug,so it runs more stable and faster.
- My preference, use auto task terminator for more RAM.
- FPS unlocked (up to 55 fps)
- ZRAM turned off
- Added Google Maps and Google Talk
First release ----> 12072012
- CyanogenMod base was changed to RC0
- Written host file blocking ads
- Nemus Launcher updated, will be less teasing.
- Written scripts against overheating.
- Shortened time connecting to Wifi
- Many tweaks for games.
Main Features:
- based on CyanogenMod 7.2.0 RC2
- Completely clean
- Bug free!
- CPU has stable frequencies up to 1.8 Ghz with modded kernel
- Incoming / outgoing sounds are clean - high
- Fully multilanguage
- FPS locked to 45 for prevent the fluctuation of the screen and improve battery performance. If you are prompted,you can unlock it.
- Media Profiles (video-camera settings) taken from Elite X1
- Experience lifelike colors on the screen with Bravia Engine.
- Wi-Fi drivers have been updated. Now, more than 15 Mbit download speed, even in the WPA
- Accelerometer works stable.
- Compass is working stable. (after calibrate)
- Light sensor reacts quickly.
- Additional theme support (by CM7)
- Stable even at 600 Mhz.
- USB Tether works. Use Barnacle Tether for Wifi Tether.
- Customized settings for the RAM (Thanks MosTERRA)
- Database IO performance is better with modded sqlite.
- If you select auto 3G/2G mobile settings, the device gives higly priority to 3G.
- ZRAM turned on by default.
- You can play Gameloft games without any need for correction of build.prop
- You can see internal and external storages at the same time in the PC and phone.
Screenshots:
so this is for wich version of the kernel? .32? .35? 3.0.8?
first impression: smooth, a lot of usable (!) features, but rom is still pretty smooth and fast even at 600mhz (like you said), MC3 runs at 1ghz as smooth as it should, nice animations and i also love other icons. I am verry impressed at speed of this rom
installation went well with cwm5.8
there is a common cm7 problem - error while searching for network. and another thing - primary language is turkish, but I mannaged to change it I just looked at icons
so far is this very good rom, i think i will stay at this one for a long while - i usually flash new one every week
didnt saw it... really sorry...
brdnacer said:
first impression: smooth, a lot of usable (!) features, but rom is still pretty smooth and fast even at 600mhz (like you said), MC3 runs at 1ghz as smooth as it should, nice animations and i also love other icons. I am verry impressed at speed of this rom
installation went well with cwm5.8
there is a common cm7 problem - error while searching for network. and another thing - primary language is turkish, but I mannaged to change it I just looked at icons
so far is this very good rom, i think i will stay at this one for a long while - i usually flash new one every week
Click to expand...
Click to collapse
oow,I forgot to write a note about "first boot lang is Turkish". I'm sorry.
Thanks for feedback!
could you give some instructions about installation? i am on kernel .32 now. do i need to install this after updating to official gingerbread?
forumber2, this, of course doesn't support force internal mic with headphones on, like every other .35 ROM, correct? I would love to try this, but the lack of that is a big problem for me
fjsferreira said:
forumber2, this, of course doesn't support force internal mic with headphones on, like every other .35 ROM, correct? I would love to try this, but the lack of that is a big problem for me
Click to expand...
Click to collapse
I didnt try it so I can not say anything about this,sorry
Experiences said:
could you give some instructions about installation? i am on kernel .32 now. do i need to install this after updating to official gingerbread?
Click to expand...
Click to collapse
You must install offical GB before install this ROM. If you want, I can send a PM about install this ROM?
Very nice Rom, I am loving it, I was missing CM
Is it possible to increase the painel frame rate to 53 with this script?
Code:
echo 31745 > /sys/devices/platform/mddi_nt35582_wvga.0/t2
This would make this Rom my main 4 some time for sure:fingers-crossed:
Experiences said:
could you give some instructions about installation? i am on kernel .32 now. do i need to install this after updating to official gingerbread?
Click to expand...
Click to collapse
if what u want to ask is if you need to install oficial .35 rom before installing this rom the answer is yes...
kaza said:
Very nice Rom, I am loving it, I was missing CM
Is it possible to increase the painel frame rate to 53 with this script?
Code:
echo 31745 > /sys/devices/platform/mddi_nt35582_wvga.0/t2
This would make this Rom my main 4 some time for sure:fingers-crossed:
Click to expand...
Click to collapse
You can unlock FPS to 55, but i think your method dont work on this ROM. You can do this method for unlock FPS to 55;
1-Open Root Explorer
2-find "system/etc/enhanced.conf"
3-Mount as RW
4-Open "enhanced.conf" with Text Editor
5-find "VSYNC=on" in "enhanced.conf"
6-change "VSYNC=on" to "VSYNC=off"
7-save it and reboot
enjoy :good:
forumber2 said:
You can unlock FPS to 55, but i think your method dont work on this ROM. You can do this method for unlock FPS to 55;
1-Open Root Explorer
2-find "system/etc/enhanced.conf"
3-Mount as RW
4-Open "enhanced.conf" with Text Editor
5-find "VSYNC=on" in "enhanced.conf"
6-change "VSYNC=on" to "VSYNC=off"
7-save it and reboot
enjoy :good:
Click to expand...
Click to collapse
This method works, but unfortunatly it causes some screen tearing on my device, at 53fps it works perfectly, anyway, thanks for your answer
I'll test. I'ma big fan of CM7.
Thank you.
im not a big fan of cm7 but im starting to be a huge fan of forumber2 work... just wanted to say that im not sticking with this rom i prefer crazy miui as they are both really good, but just cause i prefer miui style, cause as far as im concern this rom in 2 hours of use its working flawless and smoth...
im gonna stick with it till tomorrow to see how battery performs... to reply here...
thks forumber2 for another well done work...
inculto said:
im not a big fan of cm7 but im starting to be a huge fan of forumber2 work... just wanted to say that im not sticking with this rom i prefer crazy miui as they are both really good, but just cause i prefer miui style, cause as far as im concern this rom in 2 hours of use its working flawless and smoth...
im gonna stick with it till tomorrow to see how battery performs... to reply here...
thks forumber2 for another well done work...
Click to expand...
Click to collapse
Yeap,battery performance reports and more screen shots are being waited impatiently here.
---------- Post added at 02:31 AM ---------- Previous post was at 02:23 AM ----------
Guys,I wonder:
-Is volume rocker wake possible? I can't live without it anymore.
-What about sensors? Are photos rotating without lags besides proximity sensor?
Thanks.
volume rocker function is available...
and for now im a bit dissapointed with battery performance... 16% with no use and wifi on.... hum... maybe its draining a bit?
inculto said:
volume rocker function is available...
and for now im a bit dissapointed with battery performance... 16% with no use and wifi on.... hum... maybe its draining a bit?
Click to expand...
Click to collapse
Nooooooooo
It's too much cause it's nearly nothing even if wifi is on on most roms.
I'll install 30 min.later.we can compare.Be sure i'm very obsessed with battery drain.can interpret easily.
Edit:After 2 hours,battery seems normalat least,as good as an official rom.
Installed this, but there's something wrong with it. Wiped everything and no phone functionality / does not register battery.
-KJ
fjevel said:
Installed this, but there's something wrong with it. Wiped everything and no phone functionality / does not register battery.
-KJ
Click to expand...
Click to collapse
You must install B5xx before install this ROM :good:
forumber2 said:
You must install B5xx before install this ROM :good:
Click to expand...
Click to collapse
Hi fornumber2,
I am now on stock B528, just would like to see if I am eligible to install your ROM? Can't wait to give it a try... :cyclops:
Just to know if you guys want something for my rom
Battery Life. Even Underclocking isn't increasing battery life with BORETS24's kernel, do something that'll increase the SOT ! I don't get more than 3 hours of SOT with any ROM, Kernel.
Stable gps during using waze or other gps app....no more gps lost connection plz
i would expect a simple build, with no bloadware and of course stable even with a a501cg. iirc most problem are with that device.
list of expectations(mine and the others)
- stable
- no bloadware
- simple installing/autoinstaller (there is a simple-to-customize autoinstaller mentioned in this forum)
- possible to choose gapps installing by choice in one install process.
- gps
- led functional
- battery life
Simple Rom (like a pizza without any topping. User can select toppings )
Stability (GPS, wifi, data connection, bluetooth, and of course the device itself. Sudden restart is really terrible.)
DT2W/S
Battery life
LED with color (if possible)
I'd love to have another UI. To get the CM12.1 drop-down menu instead of Asus one.
Provide and alternative to borets' kernel: it has great features, but for me was and keeps to be more battery eating (I think due to the dt2w and overclock integration) than even a stock one.
dimdimdim said:
Provide and alternative to borets' kernel: it has great features, but for me was and keeps to be more battery eating (I think due to the dt2w and overclock integration) than even a stock one.
Click to expand...
Click to collapse
It will have the latest boret24 kernel without overclock
Installed CM12.1 your version found at windroidica website and found some bugs. Can't set contacts photos, it always says "No pictures on phone". Can't leave a comment on videos through youtube app and. No editor found in Gallery app? I need some help because I just flashed this rom yesterday.
if based on stock..
remove all bloatware..
pre rooted..
pre xposed..
g apps as separate package..
ota for future updates..
adb sideloadable..
the list is unlimited..