Battery consumption is okay I guess, 4% battery used in 2 hr 50 minutes of idling with WiFi on (sleep policy - never, 245/729 smartassV2).
Franco, Could you refer something useful from this kernel?
[KERNEL] Rome V.1.3.2 - Kernel 2.6.35.14 - CM7 6.6.x - Gingerbread - Phoenix | 11 nov
Use google to translate it if you don't understand italian.
i've been testing the kernel since this afternoon, no panics or random reboots... just one thing: data transfering from phone to pc is extremely slow (600KB/s) with class4 sdcard... not a bug i guess, but i'm reporting my experience...
Dude you have no apps?Battery consumption is okay I guess, 4% battery used in 2 hr 50 minutes of idling with WiFi on (sleep policy - never, 245/729 smartassV2).
Friendcaster and yahoo mail don't get any CPU, they use push, you can force stop them and still get notifications, that is why push saves battery...I do have a lot of apps actually, and they just LOOOVE using any form of network connectivity (think Foursquare, Friendcaster and Yahoo Mail).
---------- Post added at 11:56 AM ---------- Previous post was at 11:54 AM ----------
Ah by the way, I don't usually leave WiFi always on, I prefer using a Tasker script + profile I made to turn it on and off at certain intervals so that apps can fetch updates but the battery won't be drained too much.
If you have panics with smartass2 change to conservative and test with the same enviorment.. I suspect smartass2 is ****ed somewhere and causes panics.
Sent from my Nexus S using xda premium
on mine (class 10), its
PC to phone - 4-6mb per second
phone to PC - 16-19mb per second
using mik's 6.5.7 ROM file (84.7mb) as testing.
so i guess there isnt a slow transfer bug for me!
btw, last midnight I experienced a kernel panic at 710smartassv2 but in nofrills i remembered there were about 20% usage of 729mhz.
i dont know why but i am sure i checked 710 for the 1 hour stress test... maybe some mispress when the phone was initializing...
now im still using 710 to test while checking nofrills frequently, there are no 729 usage while no panics so far! will update my note and report back soon.
https://www.evernote.com/shard/s79/...19a3b0a260ae/2e9e5dc5b04f1cd475ea337ce76a2c66
on mine (class 10), its
PC to phone - 4-6mb per second
phone to PC - 16-19mb per second
using mik's 6.5.7 ROM file (84.7mb) as testing.
so i guess there isnt a slow transfer bug for me!
btw, last midnight I experienced a kernel panic at 710smartassv2 but in nofrills i remembered there were about 20% usage of 729mhz.
i dont know why but i am sure i checked 710 for the 1 hour stress test... maybe some mispress when the phone was initializing...
now im still using 710 to test while checking nofrills frequently, there are no 729 usage while no panics so far! will update my note and report back soon.
https://www.evernote.com/shard/s79/...19a3b0a260ae/2e9e5dc5b04f1cd475ea337ce76a2c66
mmmm i didn't understand: using 6.5.7 you got good transfer rates? Isn't this kernel for 6.6.x?
optimus one P500
clockworkmod recovery 5.0.2.0
mik_os cyanogenmod 6.6.1
franciscofranco kernel v1.1 02102011 smartass v2 480/729 MHz
Link2sd (from market) sd-ext4
Man, are you on the wrong rom? This kernel is only for 6.6.1. Rom and not 6.5.x. If so, this the cause for most of your problems. Read carefully first post.
hey franco.. are you jesus or what...? how did u find out the problem and when u say it, the problem happened on me
you replied to topic -> xda send email to me -> gmail notification -> i wake screen and unlock -> random shutdown
at 710 smartassv2 which i totally agree with your point!!!
sure man im changing to conservative and gonna launch stress test for 2 hours with 710! thank you so much franco
Not jesus but I have experience in this kind of ****, and I spend a good part of the day reading
Conservative shouldn't create panics in the normal OC values, I think smartass2 scaling tries to access not available CPU frequencies, thus the panics. I'm not 100% about it, but it's my guess. And because I tuned Conservative it became a viable governor.
Not jesus but I have experience in this kind of ****, and I spend a good part of the day reading
Conservative shouldn't create panics in the normal OC values, I think smartass2 scaling tries to access not available CPU frequencies, thus the panics. I'm not 100% about it, but it's my guess. And because I tuned Conservative it became a viable governor.
Any idea why the need to downclock one step from .32 to .35 tree kernel? And can or should this be fixed?
omg why didnt i think of this..! right what a tricky evil smartass2 lol... secretly ****ing my higher frequencies
so why dont i stress 729 again on conservative (729smartass2 failed before, maybe it thief used 748!)
btw do you have any brief description on ur brand new baby conservative? as i only use smartass1 as my favourite before
(its fine if u wanna explain everything after final release )
justnow my 710 conservative survived after 1 hour stress test and now im trying the 729! (as my .32 stable)
dont know whether the one step down is happening on both of us lets see my results...
I also used to do SETCPU stress tests, but i gave up cause i think its not accurate nor relevant as i got kernel panic although going through some succesfull test time. Best way to test freqs and govs fast is to use them in some apps, mostly games.
Any idea why the need to downclock one step from .32 to .35 tree kernel? And can or should this be fixed?
#4
* Added 652, 672, 691, 710 cpu frequencies
* Doubled busses frequencies - system will go faster but you'll possible lose some overclocking capabilities. Busses frequency OC > cpu OC.
* Added and tweaked Simple IO scheduler as it proved to be the fastest one for this device
* Added tun.ko and cifs.ko
* Added camera flicker bug fix
* Cleaned up some more debug ****
* One or two small tweaks
#3
* Completely rebased kernel
* No more blackscreen
* Based on CM's source
* All the tweaks and ****s you've been known about from me
* Franco magic?
* POWER
* BATTERY
* Well...I'll write a more detailed post later, too busy at the moment =)
08122011
- Touchscreen driver improved
- Same changes as the 27/11 release but now with wifi working
27112011
- Major speed up because fsyncs are not disabled
- SLUB memory allocator tweaked and made default
- Wifi Tethering fix attempt
- One or two other small tweaks and optimizations
- This release is labeled as a testing version
22112011
- Bye vsync toggle, it's not possible to change vsync without a kernel recompile
- Blackscreen bug fix attempt
- Touchscreen drivers optimized with the axis inversion workaround - changes by paolo, fserve, and me
12112011
- Vsync on/off toggle added. This is what I need be checked, I don't know if it's working: run this command via terminal or init.d script
Code:echo "0" > /sys/module/mddi_hitachi_hvga/parameters/vsync_on
Echoing 0 it will disable vsync, echoing 1 will enable it.
- FSB/BUS overclock is lower, it will lower benchmarks a bit, but you won't notice any difference during normal usage and it will increase stability
- Obviously all the changes from the latest testing version are included
- This release is labeled as a testing version
02102011
- Smartass2 tuning
- Ck2 patch - system more responsive and noticeably faster
- Compiled with the latest Linaro 4.5.4 2011.09 toolchain
- Fix camera flicker - thanks Turducken
- Add Simple I/O scheduler and made the default - should fix the slow USB transfer bug
- net: Reorder incoming packets in PPPoLAC and PPPoPNS
- Misc fixes
- Should provide some extra battery power
19092011
- A lot of reverts to increase overall stability
- Smartass2 improvements
- BFQ i/o scheduler added and made default. VR scheduler makes the USB transfers slow
- Wifi change to drain less battery
- Clear RAM feature in Andy's rom works now
- Add Jhash3
- vfs_cache from 100 to 25
- init/calibrate backported from 2.6.39
- Some other improvements that can be seen in my github
29082011
- Reducing VM_READAHEAD from 4096 to 512. Should fix the occasional music stutter
- Some .config changes from fserve to increase battery life
- Tweaks and code cleanups from CAF to increase stability, battery and performance
- Cleaned up some governors
- Add SmartassV2 added yesterday from the original Smartass creator
- Re-written InteractiveX
- Vsync enabled by popular demand
- dirty_writeback_interval = 1500 centisecs
- Some reverts that should fix the reboots or random crashes
- Thanks across for the testing
- This release is labeled as a testing version
24082011
- Strange behavior with ext3/ext4 fixed
- More ARM architecture specific code
- Internet/data speed majorly increased
- **** legacy drivers removed
- Dunno what else
- This release is labeled as a testing version
21082011
- Filesystem tweaks from Code Aurora. Mainly ext3 and ext4 improved code
- Power management tweaks from Code Aurora
- Two Power management patches from Arco's kernel
- A lot of ARM architecture specific tweaks and improved code
- Some other small ****s
- This release is labeled as a testing version
16082011
- Battery display bug is fixed
- Terminal ****ting itself when closing fixed
- Headset button should work now too
- Some reverts to provide some extra stability
03082011
- Patched with 2.6.35.14 from upstream
- Tweaks in the touchscreen driver
- Lots of reverts from backported code to improve stability
- USB should be fixed
- CFS scheduler updates
- Wi-fi should be finally fine (I hope because I haven't touched wi-fi **** code)
- Camera should work fine now too
01082011
This is a complete re-written kernel from scratch featuring all the performance and battery patches from the last version plus a lot of new code.
The changes are all in my github so I don't need to list them here. I need you guys to test the kernel and tell me what is working and what is not working, which bugs do you find, if the performance is good, if battery is good etc etc. I don't want posts like "BLUETOOH HANDS FREE DOESN'T WORK FIX PLX" or "WAHT IS THE BAST GOVERNOR AND OC HALP PLOX" I want informative posts about your conclusions, if it kernel paniced what is your environment, your OC, your governor... stupid and non helpful posts will be ignored. If you want a good kernel, do you job as an user and help me too.