Thats true, there are only some workarounds (which are included in my kernel). Because of the hardware, there is no real fix possible as far as I know.
Thats true, there are only some workarounds (which are included in my kernel). Because of the hardware, there is no real fix possible as far as I know.
#43 only has someting more debug-stuff enabled.Has anyone else upgraded to the 43 kernel? Or, have you all moved on to sweetnsour? Can anyone compare DJNoXD's kernel with sweetnsour's?
cant find where 43 is stated in any of the DL locations. also dont know if it for the 505 or just 500.
The only thing changed in #44 was that I enabled the full kernel debugging.I tested wast build jenkins-44-candiedIce-kernel-p500 in cm 10.1rc0 but unfortunately wifi and BT didn't works . It is posible to fix it.
The only thing changed in #44 was that I enabled the full kernel debugging.
So if it doesn't work, you can maybe give me some log files.
- connect your phone to pc (adb must be installed)
- type: adb shell cat /proc/kmsg
if you like to pipe the output to a file type: adb shell cat /proc/kmsg > kmsg.txt
- is there anything reported about wifi / bluetooth errors while you are trying to use / enable?
Did you also experience this problem when using other kernels (e.g. 3.0), or older versions of mine?
Ok.I will try. I have problem with abd driver Is there another way to do this?
Its a gingerbread (cm7) rom, so please usehello can some one to tell me what version of this kernel will be the best for this rom p-miui ,i use over 70% calls ,,and other 20% for camera ....i use wifi only to update apps .or other small things...i love this rom but i have only one problem i have charge my phone to 60% and when i wake up phone was off....and battery 0% i think this is a bug ,becouse alll fuctions was off (sync ,data ,bt ...) and this is not first time when i get this ......if i charge battery 100% ...ofter 2 days of use i have over 20%or much more (when i dont make so much calls ) ......give me a suggestion please ...and sorry but i dont know english very well
Its a gingerbread (cm7) rom, so please use
v2.5.8-ta-vsync-20121129-signed.zip (maybe this is the best for you)
or
v2.5.8-ta-vsyncOff-20121129-signed.zip
from the first thread.
take a look at post 2: FAQ
vsyncOff
If you always want the highest possible frame rate, you should take this one.
(Disadvantage tearing)
vsync
No tearing, constant frame rate (60fps)
If the frame rate (60fps) isn't possible, the fps is divided by two (30fps -> 15fps and so on)
FirAmp said:The gpu libs I used were obtained from here http://xdaforums.com/show....php?t=1582243
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What I did was booted into my stock rom, used a root browser to get to build.prop and added the following lines to the bottom
After which I booted into recovery, and flashed this http://www.mediafire.com/?2go947rxb1anei1 (mirror) ( New Adreno Libs )Code:debug.performance.tuning=1 video.accelerate.hw=1 persist.sys.use_16bpp_alpha=1 persist.sampling_profiler=0 ro.lge.proximity.delay=25 mot.proximity.delay=25 ro.secure=0 ro.debuggable=1 persist.service.adb.enable=1 persist.sys.use_dithering=0 persist.sys.purgeable_assets=1 persist.sys.shutdown.mode=hibernate windowsmgr.support_rotation_270=true debug.composition.type=gpu windowsmgr.max_events_per_sec=400 dalvik.vm.verify-bytecode=false iro.min_pointer_dur=1
Then of course finally flashing your great kernel.
First boot went flawlessly!
FirAmp said:The gpu libs I used were obtained from here http://xdaforums.com/show....php?t=1582243
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What I did was booted into my stock rom, used a root browser to get to build.prop and added the following lines to the bottom
After which I booted into recovery, and flashed this http://www.mediafire.com/?2go947rxb1anei1 ( New Adreno Libs )Code:debug.performance.tuning=1 video.accelerate.hw=1 persist.sys.use_16bpp_alpha=1 persist.sampling_profiler=0 ro.lge.proximity.delay=25 mot.proximity.delay=25 ro.secure=0 ro.debuggable=1 persist.service.adb.enable=1 persist.sys.use_dithering=0 persist.sys.purgeable_assets=1 persist.sys.shutdown.mode=hibernate windowsmgr.support_rotation_270=true debug.composition.type=gpu windowsmgr.max_events_per_sec=400 dalvik.vm.verify-bytecode=false iro.min_pointer_dur=1
Then of course finally flashing your great kernel.
First boot went flawlessly!
- net: data usage now works
- Add more PMEM @rashed
- fs: aufs2.2 build in
- fs: some ext4 patches from later kernel sources
- cleanup: remove of unused driver
- CPU: CPUIDLE driver from kernel 3.7
- staging: framebuffer port from 3.0.8
- serveral patches from later kernel sources
- rtc: alarm: Update hrtimer if alarm at the head of the queue (@Arve Hjønnevåg)
- rtc alarm: fix bad index when canceling alarms (@JP Abgrall)
- video: msm: Block histogram requests with powered down panel (@Carl Vanderlip)
- Update ashmem to msm-3.4 (@androidmeda)
- better pmem fix (@jerpelea)
- Backport adsp_video_verify from .38 kernel (@gntcs)