@g00ndu
The zImage is copied to a temporary boot.img file then written to the boot partition then deleted.
My bad. Didn't look hard enough@ the updater script. Thanks.
Sent from my GT-I9000
@g00ndu
The zImage is copied to a temporary boot.img file then written to the boot partition then deleted.
It seems like i have wifi error too no matter how many reboots i've done
On MIUI
Sent from my GT-I9000
@Mercury0660
Did you use an overclocked kernel before ? An if the answer is yes, did you delete the startup script to apply your overclock on boot ?
If it's not the case, try to wipe your cache through CWM.
Since latest MIUI is packed with Zach's kernel and scripts it seems clear to me that one or both scripts creates the problem.
Delete all files in system/etc/init.d folder then flash through CWM the file I linked to mosd on this post if you didn't already : http://xdaforums.com/showpost.php?p=13023742&postcount=22
Two i9000 with CM7 here and wifi works fine.
Do i need to reinstall the 3D driver update after flashing your Kernel?
Sure it's possible. It's not directly CPU frequency linked, but bus frequency linked.
I'll make a version B with overclocked GPU at lower frequencies then
1.4GHz should be stabler than on any other i9000 kernel though. I think some of you will find stability at higher frequencies compared to other kernels, especially Froyo ones since there's no other 1.4GHz+ kernel for CM7 ATM.
Probably related to Zach's scripts (the modules one maybe).
If you can delete them in system/etc/init.d and then flash the attachment, it should work
Many^^
In facts my kernel is closer to bilboa1's kernel than Zach's one. More barebone, less overhead.. Zach's one is starting to be heavy^^ From a user point of view, Zach's kernel will be slower at same frequency but probably less power hungry. With normal usage I can use my phone ~2 days before the battery dies on me, with 1.44GHz OC @ 1.375v and 3G always on. Don't know what you get with Zach's one.
zacharias.maladroit said:nice stability tweaks you added there !
you think it can be OC even to higher values ?
thanks !
zacharias.maladroit said:come on guys - don't blame everything on me
I'm not your scapegoat for WIFI, slowness, bloat, etc.
zacharias.maladroit said:not really, if you call upstream updates adding & removing stuff "heavy" then you're wrong
in that case you could also call 2.6.35.11 compared to 2.6.35 heavy
zacharias.maladroit said:the slower comes from direct tweaks in the cpu scheduler, cpuidle and other parts of the kernel
OF COURSE IT IS SLOWER if you compare APPLES TO ORANGES:
you can't compare conservative, e.g. with interactivate and other governors
zacharias.maladroit said:last time I fully discharged my battery I got around 90 hours so translated to the stock battery it also should be 2+ days ^^
Tk-Glitch what's your opinion on battery runtime from Froyo compared to Gingerbread, btw ?
Pretty hard to answer with my experience.. I think we can gain a bit, but maybe not significant. After some days running CM7, there's no real battery drain problem.zacharias.maladroit said:Do you also think that battery runtime is worse than it could be ?
zacharias.maladroit said:any link to your source repo or patches ?
all of this is GPLed stuff after all
working together and continually evolving stuff is the goal of all this
Thanks !
I took stuff from Morfic too and refined it by testing thoroughly some night with theescapist
but decided not to oc gpu differently / go above 1.3ghz because it's not that stable on most phones (also for other reasons) and don't really want people to start burning up their phones ^.^
if it proves stable at high freq at some point (and if the other reasons are fixed) i might run at higher freq too (i mean on my phone - i don't rly mind which kernel i use, doing my own usually because i didn't find what would satisfy me)
but it would need to be stable at like 1.6 or 1.7ghz to provide a real boost (and run n64 games smoothly ?! xD) which i'm not sure the cpu can handle in a stable fashion anyway ( at the hardware level)