Hello,
I'been facing this problem since Froyobread v017. Problem is: I load the x8oc.ko module (modifying hw_config.sh) and set it to overclock at 740Mhz using this code on the hw_config.sh file:
Code:
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x26 > /proc/x8oc
Everything works fine. After reboot the overclock is working and I can see the processor running at 740Mhz and I can se the overclock module loaded using the command below:
Code:
dmesg | grep x8oc
The problem is that after around 30+ minutes if I check again the processor I see that it is not overclocked, so it is runnign at 600Mhz. Then if I check the module x8oc to see if it is loaded I found that is not loaded anymore.
I cannot find why the overclocking module is unloaded. I don't have any appkiller or something like that that could kill the module.
I already tried doing a full wipe and reinstalling the Froyobraed ROM from scratch with no success. There must be something killing the module but I cannot find what it is.
Any thoughts or advice about what could be the issue?
PD: I wanted to post this question under the Froyobread development post, but I think I am too noob to be able to post in there!
don't add the code in hwconfig, doixanh has already added it
he posted in froyobread thread this:
3. Anyone who needs overclock module can simply copy x8oc.ko to /system/lib/modules and reboot. No need to change hw_config.sh. It will be loaded automatically.
Thanks fifo171 for your advice.
I read that before troubleshoot the issue. Anyway the module IS NOT loaded automatically in doixanh's Froyobread. I tested it copying the x8oc.ko to /system/lib/modules and reboot. that is why I modified the hw_config.sh file.
for me it works, just copy x8oc.ko to /system/lib/modules, then reboot and set frequency with setcpu, it should work
edit: on which number did you look ??? on the big white or small green ???
I didn't wanted to use SetCPU, but if that is the only way to make the overclocking works I will try and let you now.
Thank you very much for your help.
PD: Is SetCPU a free app? I shearched in the Market but I found that it is a paid app... maybe I am looking at the wrong one.
on market is only donate version, free version is here
Great!!!
What do you refer with: on which number did you look ??? on the big white or small green ???
Do you refer to the CPU clock value informed?
i thought that you had setcpu and there are 3 numbers with frequency: current, max, min
Well it didn't work. I have x8oc.ko copied in the /system/lib/modules directory and I cleaned the hw.config.sh file
After reboot x8oc module is not loaded, and SetCPU only shows as maximum clock 600MHz.
I checked x8oc.ko permissions and it is Read/Write for user, group and other. Should it have also the Execute permission enabled? Maybe is a file permission issue.
patriciocs said:
Well it didn't work. I have x8oc.ko copied in the /system/lib/modules directory and I cleaned the hw.config.sh file
After reboot x8oc module is not loaded, and SetCPU only shows as maximum clock 600MHz.
I checked x8oc.ko permissions and it is Read/Write for user, group and other. Should it have also the Execute permission enabled? Maybe is a file permission issue.
Click to expand...
Click to collapse
try to check all permisions and reboot, maybe it will help
I did chmod 777 /system/lib/modules/x8oc.ko then rebooted.
No luck. Module is not loaded. Do you know where is the file with the code that uploads the oc module? Maybe I have something missed on that file.
i don't know, try to install froyobread update.zip, it will delete /system and reinstall the rom, it will preserve your data, but don't do factory reset, and then try installing x8oc.ko again. if this won't help, i don't know what's the problem
Great! the problem was solved with your last instructions. Maybe I broken something when I modified the hw_config file. Now the module is loaded on boot again. I will monitor now if it keeps the processor overclocked through the time.
Thanks for your help and time fifo171!
Related
Hi guys,
Since J001 I have used as lcd density 210 instead of 240. Now I have flashed J003 and forgot to change the lcd densitiy in the build.prop before flashing and recognized how much better the rom looks with 210, so I thought I should tell it to you.
J said anywhere that this lcd density will break some apps, but I weren't able to find any app that will be broken by using this lcd density instead of the normal one. So, could you try it please and report it back if you find any app that won't work/work right with this lcd density?
I'M NOT RESPONSIBLE IF YOU BREAK YOUR DEVICE OR DROP YOUR COFFE
Files:
Edited Build Prop Cm7.1 J002.zip
Edited Build Prop Cm7.1 J003.zip
back to original.zip
Cheers,
L
I don't know if it can be considered an app..but Arc launcher doesn't support different lcd density!!
is creating a new thread for this actually required?
in my opinion why dont u integrate all ur CM7 related threads into one "CM7 fixes / tweaks /etc" kinda thread? u can ask the mods for some help the can do such combining-thread-stuff...
it would be really helpful...
also there is an easier/more generic way to do this change in ANY build.prop:
just run this script (include it in update.zip) thru recovery:
Code:
#!/sbin/sh
# modify ro.sf.lcd_density=240
busybox sed -i 's/ro.sf.lcd_density=240/ro.sf.lcd_density=210/g' /system/build.prop
# modify qemu.sf.lcd_density=240
busybox sed -i 's/qemu.sf.lcd_density=240/qemu.sf.lcd_density=210/g' /system/build.prop
DooMLoRD said:
is creating a new thread for this actually required?
in my opinion why dont u integrate all ur CM7 related threads into one "CM7 fixes / tweaks /etc" kinda thread? u can ask the mods for some help the can do such combining-thread-stuff...
it would be really helpful...
also there is an easier/more generic way to do this change in ANY build.prop:
just run this script (include it in update.zip) thru recovery:
Code:
#!/sbin/sh
# modify ro.sf.lcd_density=240
busybox sed -i 's/ro.sf.lcd_density=240/ro.sf.lcd_density=210/g' /system/build.prop
# modify qemu.sf.lcd_density=240
busybox sed -i 's/qemu.sf.lcd_density=240/qemu.sf.lcd_density=210/g' /system/build.prop
Click to expand...
Click to collapse
simply copy your code into the updat-script?
9Lukas5 said:
simply copy your code into the updat-script?
Click to expand...
Click to collapse
no...
u will have to make a file (say "install_mod") in the root of the update.zip
and the update-script should be something like:
Code:
run_program PACKAGE:install_mod
now the contents of "install_mod" should be the ones i posted above...
u might have to also mount system before executing the script...
also do test it out... i am really tired today to sit and make these zips
will go to sleep now [not "deep sleep" ]
Delete
Sent from my X10 using XDA Premium App
hi, i hope i understand it right, with broken apps did you mean they didnt fit the screen?
i change always on any custom roms the lcd.density to 190, then some apps didnt fit the screen (some games or widgets)
to fix is easy with spare.parts
-open spare.parts
-navigate to spare.parts settings
-scroll down to compatibility mode
-uncheck and check again
-reboot
-after reboot
-again open spare.parts
-navigate to compatibility mode
-uncheck
-reboot
after that the apps they didnt fit the screen, works now fine
only problem is with stock dialer, numberfield is smaller, or arc launcher will not work with this trick
edit: here are example pictures(lcd 190), before and after the trick with spare.parts
you know you could just use the lcd density changer app...;o
Zocker Tko said:
hi, i hope i understand it right, with broken apps did you mean they didnt fit the screen?
i change always on any custom roms the lcd.density to 190, then some apps didnt fit the screen (some games or widgets)
to fix is easy with spare.parts
-open spare.parts
-navigate to spare.parts settings
-scroll down to compatibility mode
-uncheck and check again
-reboot
-after reboot
-again open spare.parts
-navigate to compatibility mode
-uncheck
-reboot
after that the apps they didnt fit the screen, works now fine
only problem is with stock dialer, numberfield is smaller, or arc launcher will not work with this trick
edit: here are example pictures(lcd 190), before and after the trick with spare.parts
Click to expand...
Click to collapse
Works fine, thanks.
Sent from my X10a using XDA App
I've been using 220 since CM6 first was released and I can't find any apps that don't work either
Here's the modified stock kernel from software ver 2.17.651.5, flashable through recovery, of course.
As of 1/13/12, CIQ back and front ends have been removed by HTC.
Includes init.d support.
Changelog:
8/21/11
On boot the following happens:
-Removes files from /data/system/dropbox
-Removes files from /data/system/appusagestats
-Removes files from /data/system/usagestats
-Removes files from /data/tombstones
-Modifies permissions on /data/system/dropbox to read-only
-Modifies permissions on /data/system/appusagestats to read-only
-Modifies permissions on /data/system/usagestats to read-only
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db-shm
-Removes permissions on /data/system/userbehavior.db-wal
-Removes permissions on /data/system/userbehavior.xml
8/30/11
Thank you to mike1986 of the awesome Sensation forum and the Android Revolution HD ROM for the initial idea, and smokin1337 for bringing it in mod form to the EVO 3D forums.
-DualCore support (my own twist). It sets the second core to run at half the speed of the first core as well as drops the minimum frequency to 192MHz on both cores.
-Compatible with scripts/apps that don't bother the second core.
-PowerSave script is not compatible or needed with this kernel.
-For Quadrant braggers, your scores will take a slight dip since Quadrant isn't optimized for dual cores. However, performance does increase.
8/31/11
-Minor ramdisk tweaks.
-Removed /system/etc/init.post_boot.sh from zip. No longer needed.
-A2SD support.
-594MHz second core now runs with a threshold of 40. (should be slightly better performing)
-Update4: 1.2GHz second core runs in sync with first core at 75 up-threshold.
9/1/11
-Fixed stuck-at-splash-screen.
-Removed A2SD for now.
9/6/11
Removed HTC IPC Server from ramdisk.
10/26/11
Updated kernels with HTC's ramdisk edits.
Added TrevE's ro.lb=unknown and ro.bootloader=unknown values to default.prop. TAKE THAT GOOGLE! Thanks TrevE!
Removed references to htc_ebdlogd
Set ANR (app not responding) history to 0
Set dirty_expire_centisecs to 100
Set capacitive lights to dim (2)
10/27/11
Added ScreenOff script
Added Uninstall ScreenOff script
1/13/12
Updated kernel
Added mpdecision (Thanks TrevE)
Removed insmod /system/lib/modules/qce.ko
3/12/12
Removed mpdecision and references to it in the kernel ramdisk
Updated unmodified and stock dual core kernels to include stock mpdecision so that users of the modified kernels can get mpdecision back when flashing unmodified kernels.
3/14/12
Changed loglevel to 0. Afterall, this is a stock kernel. The less logging the better.
Removed wimaxDumpKmsg
Removed wimaxDumpLastKmsg
Removed wimaxDumpLogcat
Removed bugreport
Removed loading and references to those files from the Kernel ramdisk. Don't worry, WiMax still works. If anything it will work just a bit better now that it doesn't need to worry about dumping any information to logcat and kmsg.
Updated unmodified kernel package to include missing files for those who want to go back to pure stock after flashing one of these.
Here are the changes from 2.08.651.3 ramdisk to 2.17.651.5:
Code:
init.rc
Removed:
mount debugfs /sys/kernel/debug /sys/kernel/debug
Added:
#set projector permissions
chown system system /sys/devices/platform/projector/interface/enable
Added:
on property:crypto.driver.load=1
insmod /system/lib/modules/qce.ko
Not exactly sure why insmod /system/lib/modules/qce.ko is in there. This file is not in the OTA or full ROM package. But it looks like it only gets called if crypto.driver.load=1, but even so, the file isn't there. Strange. Gonna go ahead and remove that.
HTC has made the following ramdisk edits with 2.08.651.3 but actual kernel version hasn't changed.
Here are the edits:
Code:
init.shooter.rc:
Added:
# to enable low charge current in voice call
chown radio radio /sys/class/power_supply/battery/charger_control
chmod 0660 /sys/class/power_supply/battery/charger_control
Removed:
# for vnc
service androidvncserver /system/bin/androidvncserver -a
disabled
oneshot
service usbnet /system/bin/usbnet on
disabled
oneshot
Removed (in bold):
on property:init.svc.bootanim=stopped
[b] start thermald[/b]
start mpdecision
Changed:
[b]FROM[/b]
service mpdecision /system/bin/mpdecision --Nw 5.4 --Ts 480 --no_sleep --avg_comp --single_core_while_panel_off
[b]TO[/b]
service mpdecision /system/bin/mpdecision --Nw 5.4 --Ts 350 --no_sleep --avg_comp --single_core_while_panel_off
Kernel information:
freEVO 3D-StockKernel 2.17.651.5.zip: Dual Cores active. 2nd core max frequency 1.2GHz, Up-threshold at 90 (Stock setting). Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5b.zip: Dual Cores active. 2nd core max frequency 1.2GHz, Up-threshold at 75. Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5c.zip: Dual Cores active. 2nd core max frequency 594MHz, Up-threshold at 90 (Stock setting). Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5d.zip: Dual Cores active. 2nd core max frequency 594MHz, Up-threshold at 75. Minimum freq at 192MHz.
Unmodified:
freEVO 3D-StockKernel 2.17.651.5ORIG.zip
Modified (dual cores left at stock settings):
freEVO 3D-StockKernel 2.17.651.5e.zip
Dual Core ScreenOff script:
freEVO-3D-DualCoreScreenOffscript.zip (1.2GHz version):
freEVO-3D-DualCoreScreenOffscript594.zip (594MHz version):
This will install the 70cputweak file in /system/etc/init.d/. To check whether or not it's working (and if your kernel supports init.d), with your phone connected to ADB, simply type or copy: "cat /sys/devices/system/cpu/cpu1/online" If it returns a 0 while the screen is off, that means it is working. You can also do "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" while the screen is off, and if it returns a 384000 then it is working. Keep in mind that you may also edit this file with root explorer or notepad++ to your liking, but you will need to reboot for it to take effect.
Uninstall ScreenOff script
freEVO-3D-UninstallScreenOffScript.zip: This will simply delete the 70cputweak file in /system/etc/init.d. You can accomplish the same thing from adb or root explorer.
NOTE: Please make sure that you don't have any other CPU controlling app such as SetCPU, virtuous OC/OC daemon, CPU Tuner/CPU Master, 98dualcore (from ziggy kernel/synergy) installed if you decide to use this, as they will most definitely interfere with this script and I haven't coded a failsafe to disable it in their presence. You can essentially accomplish what this script does if you use any of the above mentioned apps, but this is mainly for those who want to 'set it and forget it.' Also, SetCPU is most definitely not compatible with this method of dual cores, script or no script. It will return cpu1's online state to default and will render this script as well as the kernel useless.
NOTE 2: If you are going to install another kernel and would like to uninstall dual cores active always, you will need to flash either the unmodified or modified without dual cores kernel first with a reboot afterward, as the ramdisk method employed here will survive many kernel replacements that use Koush's anykernel updater. I've thought about using init.d scripts rather than ramdisk method but eventually decided on this way. Sorry for any inconvenience!
ENOUGH CHOICES?
HBOOT 1.5 users? or just want an easier way to flash things? Joeykrim has created a fantastic app that will allow you to flash kernels, among other things, directly from Android. Check it out here: http://forum.xda-developers.com/showthread.php?p=16129916
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Download: here
Click to expand...
Click to collapse
You are the man!
hTc Evo [3D]
Dang..
Awesome
Sent from my PG86100 using XDA App
Thank-you! I didn't even wait, downloaded it on my phone.
Sent from my s-off Shooter!
Can this kernel get the OC scripts?
I'm sure most of you know this, but since I made the mistake, ill share it. Don't flash the kernel unless your on a 2.3.4 rom. It will break the camera and wifi, among other things. If you did flash, just reflash the old one.
Thanx again and again
Sent from my PG86100 using XDA Premium App
will the silverneedle kernal flash over this succesfully
mjohnson4580 said:
will the silverneedle kernal flash over this succesfully
Click to expand...
Click to collapse
You can flash any kernel over another one......
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Pardon my ignorance but, A, what is cIQ and, B, will this work with Overclocking apps?
Thanks!
gksmithlcw said:
Pardon my ignorance but, A, what is cIQ and, B, will this work with Overclocking apps?
Thanks!
Click to expand...
Click to collapse
A: think of it as carrier spyware
B: No
[email protected] said:
You can flash any kernel over another one......
Click to expand...
Click to collapse
I don't think any other kernel will work on 2.3.4
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Good stuff man! Thanks!
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Thanks. Nice and fast without ciq running in the background.
lafester said:
I don't think any other kernel will work on 2.3.4
Click to expand...
Click to collapse
I believe you're right. I tried to flash the RCMix kernel and got bootloops until I reflashed the 2.3.4 rom again. I guess we'll have to wait until they release the kernel source for this rom before we see newer ones.
sonic41592 said:
I believe you're right. I tried to flash the RCMix kernel and got bootloops until I reflashed the 2.3.4 rom again. I guess we'll have to wait until they release the kernel source for this rom before we see newer ones.
Click to expand...
Click to collapse
that sux.. definitely gonna wait myself, on flashing any custom 2.3.4 ROMs right now.. will wait for AOSP/CM7/MIUI 2.3.5 gotta have my OC and Custom ROM..
Nice work on pulling the iQ BS out of it..
Freeza, what ROMs is this tested with? I tried it on my own build and on xhausx build and it wouldn't boot all the way. Screen goes blank and then nothing. Still responds to power because I see the buttons toggle on and off.
Do I need to have the other firmware updates (radio, etc) too?
Any thoughts?
I did the firmware updates and this modified kernel ran fine on Haus's stock.
Sent from my PG86100 using XDA App
Mexiking10 said:
I did the firmware updates and this modified kernel ran fine on Haus's stock.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Sweet! Thats what I wanted to know.
Thanks brother!!!!
scrosler said:
Freeza, what ROMs is this tested with? I tried it on my own build and on xhausx build and it wouldn't boot all the way. Screen goes blank and then nothing. Still responds to power because I see the buttons toggle on and off.
Do I need to have the other firmware updates (radio, etc) too?
Any thoughts?
Click to expand...
Click to collapse
i got the same thing going on on my end. i baked it in as well. just reboots.
For use with Streak Gingerbread Roms
Edit 12-7-11
This is the marked end of Gkernels project,
Gkernels 1.5 FINAL
but the marked beginning of Gxkernels!
Changes to 1.5 include:
Bumped the Dell source to 2.6.35.14 -Stable
Removed QoS in networking for reasons clear to my mind
Flashable zip here: http://db.tt/JuCSscC8
Developer tar.gz here: http://db.tt/pNkHIPRQ
Special thanks to you, the user of Gkernels!
-G
Edit 12-4-11
Gkernels1.4.3.1 now a flashable zip from your recovery, for easy installs!
lex parsimoniae
Special thanks going to _n0p_ for this method!
Download link here:http://db.tt/XrDJQ6Jv
to install:
copy the zip to sdcard, launch recovery in your streak, flash the zip file
for future releases, I will include the standard Gkernels tar.gz for rom developers, and also the flashable zip file, as two separate links for the community.
-Greg
Edit 12-3-11
GKERNELS1.4.3.1
Built with an older toolchain arm-eabi-4.3.1
Changes from 1.4.0.1 include:
<*> General filesystem local caching manager
<*> Filesystem caching on files
Wifi-
<*> Common routines for IEEE802.11 drivers
--- Bluetooth subsystem support
[*] L2CAP Extended Features support (EXPERIMENTAL)
networking options-
[*] IP: multicasting
[*] IP: ARP daemon support
Qos service changed-
<*> Hierarchical Fair Service Curve (HFSC)
---removed from 1.4.0.1 version---
adjust priority to speedup resume thread, (seems to help with wifi issue, special thanks DSC-Team)
Again, no overclocking;
Download Link here: http://db.tt/0vlfvlaI
Edit 11-27-11
1.4.0.1
changes since 1.3.3:
Suspend sleep mode (Power collapse suspend)
Control the low power modes of memory
Default Memory Low Power Mode during Idle (Memory in retention)
Default Memory Low Power Mode during Suspend (Memory in deep power down)
Enable standalone power collapse
Android RAM Console Enable error correction
Virtual Contiguous Memory (VCM) Layer
Download link: http://db.tt/ZnaqJ9qH
I am fairly certain wifi freeze issue is resolved. Further testing is needed to prove this;
Enjoy!
-Greg
Gkernels 1.3.3 still attached below
Gkernels 1.3.3
changes from Gkernels1.0
Enable WiFi control function abstraction
Preallocate memory for WiFi buffers
Enable KSM for page merging
Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)
I've got some under-volting going on with static voltage regulator
kernel switched to low resolution timer
Cross-Compiled using arm-eabi-4.4.3 from Dell 4.05 source, thanks given to Dj Steve for his tip with wifi practices. Thanks going out to kernel cross-compiling sources and books; thanks to all the rom chefs;
To me, Streak kernel work is more of an art than a science. Include Gkernels in your rom; do what you feel with it, all is permitted.
Installation Instructions
Method 1:Assumption is on a linux distro,
obtain a prebuilt fastboot and adb binary, and get them into your /bin folder, to use the commands from anywhere within your system
download Gkernels1.3 and extract, if you have not already done so.
attach streak to computer with usb cable;
from the extracted archive directory run this command in terminal:
sudo adb reboot bootloader
the streak will then boot into the fastboot mode
Then:
fastboot -i 0x413c flash boot boot.img
Then:
fastboot -i 0x413c reboot
then from same directory, run this command as phone is rebooting:
sudo adb push dhd.ko /system/lib/modules
I then recommend rebooting one more time.
Method 2: Any system
Re-substitute the boot.img and dhd.ko in the archive, by replacing same files, in your chosen rom's update zip;
transfer to the device
then flash as you would, the rom using your prior flashed recovery.
Thanks to Delirium77!
Method 3: Bypass for adb with root explorer/total commander app from the market
flash the boot.img with fastboot per method 1-
copy the dhd.ko file to your sd card, unplug your device, and using root explorer/total commander, navigate to the file on the sdcard, then move it to:
/system/lib/modules
ensure the dhd.ko file has correct permissions, then your wifi will function after a reboot.
-Greg
Thanks for your work!
can you build for your kernel few modules?
cifs.ko, slow-work.ko
for slow-work there is some kind of manual editing and preparing.
or if you give me your .config i will try this myself?
EDIT:
also you can statically compile CIFS filesystem into kernel
mind if i ask what advantage/s does this kernel have over Steve's gingerstreak kernel?
I can provide a .config file, sometime this evening, as I am away-
Gkernels is a project based on the 4.05 Dell source;
It is not better than another kernel in that regard, I am trying to get all I can out of it, without overclock. Changes to my knowledge, that differ from the Steve kernel, are listed above;
Thanks to _n0p_ 's tip 1.3.3 solves the RTC issue- Thanks _n0p_
I believe this was done by changing to the low resolution timer.
-Greg
.config
Sorry for the delay, I was detained-
attached is the .config for 1.3.3
Working with an attempt to solve the wifi issues-
one environment seemed to work during my testing, yet at a great sacrifice to battery life, by enabling:
control the low power modes of memory -->
Default Memory Low Power Mode during Idle (Memory active)
Default Memory Low Power Mode during Suspend (Memory active)
I am still uncertain-
before I release a 1.4, I will trial more of these modes
-Greg
Can this modes be switched by detecting if external power supplied?
--
I've also recieved some requests, saying that power (and maybe other) buttons sometimes "flickers". Is there any way to filter key events a little?
--
Thank you for your devotion,
Sergei
I will look into this.
Hi, there seems to be some screen tearing , I suspect that it has something to do with vsync. Could this be fixed with a new kernel update or is this ROM related?
Sharptv-
This may be kernel, rom or both related;
you may try and experiment with different roms and kernels-
This could also be screen density related, on my device there is minimal tearing on default density
I had some screen tearing on power rom but none on DSC....
Good work on the kernal
May bishnu grant you many donkeys and wives
@Roy
are u indian
Hi GSpecial!
I'd like to ask you to join forces with ltrifonov.
You both are advanced system builders, i think Streakers community would really benefit from your teamwork!
That's an awesome job you are doing. Never was able to crack more than 1500 upload until now!
Sent from the SuperStreak!
borijess said:
That's an awesome job you are doing. Never was able to crack more than 1500 upload until now!
Sent from the SuperStreak!
Click to expand...
Click to collapse
Is this considered a good score?? I just did the test and got 10ping, 15162kbps down and 8912kbps up
Sent from my Dell Streak using xda premium
Greg, your new kernel 1.4.0.1 (can say after a day of tests), is absolutely fantastic.
Fast, responsive even with conservative governor waking from 128Mhz - and WiFi is simply excellent!
Thank you!
Nop can you make a flashable zip plz???
You might pay attention to Downloads section for DSC ROM (not ad )
greekunit690 said:
Is this considered a good score?? I just did the test and got 10ping, 15162kbps down and 8912kbps up
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
I guess compared to u rs no but normally I was getting around 1000 up. So its 3 times as fast now for me.
Sent from the SuperStreak!
i am not sure if this mod works but you can try it.
i have not had screen death bug using this.
i have not made flashable zip, you have to apply this mod manually.
it will be very good if some one make it for me.
here is what you have to do.
1) download View attachment vsync.rar and extract 20-vsync file.
2) put this file to /system/etc/init.d/ and set permissions to rw-r--r-- (644)
3)open system/lib/egl, edit egl.cfg and delete first line i.e. 0 0 android
after that save and exit.
4)also delete libGLES_android.so from /system/lib/egl/
5)now download View attachment adreno_config.rar and extract adreno_config.txt
there are 3 files each 1) no MSAA (multisample antialising)
2) 2x MSAA
3) 4x MSAA
choose whichever you like, i would recommend 2x MSAA file.
6) put extracted adreno_config.txt to /system/etc and replace with old one. and set permissions to rw-r--r-- (644)
7) now reboot phone into recovery, clear cache and dalvik cache and reboot.
enjoy JB with less screen death.
please test and report...............
also you need to edit build.prop with
debug.sf.hw=1
debug.composition.type=gpu
if you are getting lags use
debug.composition.type=mdp
reserved
has anyone tried it yet??? please test and report...
This bug cannot be resolved with sole init.d files and libs..this bug is caused of low ram!
ya i know about that but still this mod decreases the frequency of bug.
you can say it is "near project butter implentation"
Working
Before I had flashed your fix, screen doesn't wake up.
After I had flashed your fix, screen always wakes up and I feel that my x8 is faster (placebo?).
Sorry for my bad English.
Confirmed...Working...now,it's not that hard to wake him up than before.. :thumbup:
E16i - android 4.1.2 jb
- MiniCM10 4.0.2
Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
ludogaut14 said:
Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
Click to expand...
Click to collapse
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
freaksamael said:
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
Click to expand...
Click to collapse
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
ludogaut14 said:
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
Click to expand...
Click to collapse
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
freaksamael said:
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
Click to expand...
Click to collapse
Hi, I did your advice but do not work. 00test init.d ok, 01disable_selinux not work, "getenforce" always "enforcing". I wait a good person makes a kernel with SELinux permissive and KNOX desactived. Thank you very much for your advice and excuse me for my english.