hello.
i having searching around and seeing that the flash problem is due to the newer kernels?
i have extracted the kernel from a build with working flash and replaced it with the one that has a bad flash but it still presists?
am i switching kernels wrong?
(system>lib>modules)
thanks in advance
did you replace zImage too?
justwonder said:
did you replace zImage too?
Click to expand...
Click to collapse
yeah i also replaced it
by the way does anyone know whats the lastest kernel that has working flash? thanks
S3BAZ10 said:
by the way does anyone know whats the lastest kernel that has working flash? thanks
Click to expand...
Click to collapse
All the Nexus One based kernels have working flash. Michy R11, Git, and probably Darkstone. All the Evo based kernels have the delayed flash.
buzz killington said:
All the Nexus One based kernels have working flash. Michy R11, Git, and probably Darkstone. All the Evo based kernels have the delayed flash.
Click to expand...
Click to collapse
That's not true. I have tried the newest Git and Michy's R11 and both had this issue. I think it's cause by the builds, not by a kernel.
What build are you using?
Related
I've tested many builds but almolst all of them have the same problem, that's why I would like to know if there are any Android sense builds without the premature flash issue, I've found that Core Droid V0.4R doesn't share this problem , but I don't like the custom skin it has. Do you know any others without that problem???
Darkstone HD2Froyo V2.1
.BetaBoy said:
Darkstone HD2Froyo V2.1
Click to expand...
Click to collapse
From what I see it is a nexus one build , I would prefer a Desire/EVO build because I like their appearance more...I am a want-them-all guy...
I thought only Evo builds/ Evo Kernels had that issue. My Froyostone 2.1 build is fine.
firebert said:
I thought only Evo builds/ Evo Kernels had that issue. My Froyostone 2.1 build is fine.
Click to expand...
Click to collapse
Really V3.1 that I tried had that problem...
What the f...k is it only me?
Just a question to all, is the cause of premature flash the build or the kernel?
I read through some posts on the Android development section that it's because of the kernel. If so, how come michy's evo kernel on core droid's build does not share this problem? Also, many said it's about the build. Then how come hastarin's kernel still produces premature flash on core droid's build?
On the other hand, many people keeps on building a lot of android builds from different base roms rather than fixing issues on their previous builds.
Its not build related but kernel related try michyprina r11 non evo kernel there s no prematurate flash on all roms i have tested
Sent from my Nexus One using XDA App
Premature flash seems to be present on any build based on the EVO kernel 9/28 or later.
asphaltkiller said:
Its not build related but kernel related try michyprina r11 non evo kernel there s no prematurate flash on all roms i have tested
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
will michy's r11 work on Desire HD builds of deejay?
I have made a quick patch for premature flash problem in evo kernels. I have tested it with hastarin source taken from his git repository.
This is a quick patch and somebody with more knowledge in android kernels can make a better solution.
The problem is not in premature flash but in missing flash. In desire kernels camera flash is activated twice (function msm_camera_flash in msm_camera.c) first time with low intensity (MSM_CAMERA_LED_LOW) and second time, while taking a picture, with high intensity (MSM_CAMERA_LED_HIGH). In evo kernels flash is activated only once with low intensity and because of that we only see the first activation of flash/led. Maybe someone knows from where the function msm_camera_flash is called and add a second call to that function with high intensity.
EDIT:
zImage with wifi modules on post:
h__p://forum.xda-developers.com/showpost.php?p=8635032&postcount=46
Congratulations on finding that. It makes sense a lot.
UPDATE: Everybody can now use hastarin 7.4 kernel since its updated with the code in this thread. Credit goes to mdebeljuh
http://forum.xda-developers.com/showthread.php?t=787588
Thank you very much mdebeljuh!
what we have to do with your file? can you provide how to steps?
How do i have to install this patch?
it's a kernel patch. if you don't know how to use it, you'll have to wait till one of the kernal-builders will implement it. hastarin and michyprima are very quick at adopting patches.
For testing
Ok, for testing purposes i have attached the latest hastarin kernel with patch included
mdebeljuh said:
Ok, for testing purposes i have attached the latest hastarin kernel with patch included
Click to expand...
Click to collapse
Thank you m8...will test it right now
@ Screemi
Thanks for explaining it so detailled...
Yes how do we use this patch file ?
First you need to know how to compile the kernel:
h__p://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel
Next you can apply the patch to the source you have downloaded from git and compile the kernel with, i hope, working flash.
You can use the patch with the next command (execute from your local git repository root directory)
patch -p1 < /path_to_patch/0001-Patch-for-premature-flash-missing-flash.patch
Thank you for your work
I can confirm, flash triggers as intended in a dark room.
Also I've let the developers know about it, Cass said he will do some tests as well.
Good work!
wow! its working! nice! thanks
please upload modules for this kernel
mdebeljuh said:
Ok, for testing purposes i have attached the latest hastarin kernel with patch included
Click to expand...
Click to collapse
Hi, thank you !
Is this based on hastarin 7.3 version?
Thanks
Sent from my HTC HD2 using XDA App
Yes it is based on hastarin sources from Friday October 15 2010
hi..
i tested this Zimage..
flash work.. but not work WIFI ..
i cant use in mdeejay froyo sense v.2.2 nextsense
mdebeljuh said:
Yes it is based on hastarin sources from Friday October 15 2010
Click to expand...
Click to collapse
OK, so I have to upgrade to 7.3 Wi-Fi module..
Thank you!
Sent from my HTC HD2 using XDA App
mannyy said:
hi..
i tested this Zimage..
flash work.. but not work WIFI ..
i cant use in mdeejay froyo sense v.2.2 nextsense
Click to expand...
Click to collapse
First you have to upgrade to version 7.3 modules..
Sent from my HTC HD2 using XDA App
iosub said:
First you have to upgrade to version 7.3 modules..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
modules for kernel without OC
mdebeljuh said:
Ok, for testing purposes i have attached the latest hastarin kernel with patch included
Click to expand...
Click to collapse
tested..work as it should be..
but we need .ko file error on wifi..
edit..
ups didn't see post above..so this is base on 7.3 no OC..
How should I go abount intalling intellikernel on cm7rc3 . I am a noob and do not really understand the importance of having a seperate kernel (incredikernel is supposed to be superior than the default CM7) .. would I have to do some tweaks after I flash this?
Do I need to wipe anything before I flahs this or any new kernel? is it stable?
kpdadroid said:
How should I go abount intalling intellikernel on cm7rc3 . I am a noob and do not really understand the importance of having a seperate kernel (incredikernel is supposed to be superior than the default CM7) .. would I have to do some tweaks after I flash this?
Do I need to wipe anything before I flahs this or any new kernel? is it stable?
Click to expand...
Click to collapse
Where did you get the "intellikernel" at. Is it supported for the Glacier?
neidlinger said:
Where did you get the "intellikernel" at. Is it supported for the Glacier?
Click to expand...
Click to collapse
Sorry I mean incredikernel.
I tried flashing right now over Cm7 RC3 (without wiping anything and it did not work)
kpdadroid said:
Sorry I mean incredikernel.
I tried flashing right now over Cm7 RC3 (without wiping anything and it did not work)
Click to expand...
Click to collapse
can you show me the link to this kernel?
Where can I find the list of supported kernels?
http://forum.xda-developers.com/showthread.php?t=848453
is the link
kpdadroid said:
Where can I find the list of supported kernels?
Click to expand...
Click to collapse
Development section.
kpdadroid said:
http://forum.xda-developers.com/showthread.php?t=848453
is the link
Click to expand...
Click to collapse
That is for the Droid Incredible.
That is why it will not work on our phone.
You can only flash 3rd party kernels related to your phone, and your skin design. meaning you cannot flash an AOSP kernel for Sense ROM, nor a DInc kernel to a OG Droid.
But I am running CM7 RC3 ... which is AOSP.... I am a little confused.
kpdadroid said:
But I am running CM7 RC3 ... which is AOSP.... I am a little confused.
Click to expand...
Click to collapse
But the Kernel you are looking at is for the Droid Incredible, not for the HTC Glacier. They are two different phones, with two different hardware packages. You must use AOSP kernels for the HTC Glacier.
Could you suggest one that you really like? and do I have to wipe anything before I flash any kernel?
kpdadroid said:
Could you suggest one that you really like? and do I have to wipe anything before I flash any kernel?
Click to expand...
Click to collapse
Personally i suggest running the stock kernel that came with your ROM. And i will only use the kernel that comes with the ROM. The developers have built the ROM to run around that kernel. So it should work the best. I know Faux123 has built some top notch kernels....but i cannot speak first hand.
kpdadroid said:
Could you suggest one that you really like? and do I have to wipe anything before I flash any kernel?
Click to expand...
Click to collapse
i personally like this one....
http://forum.xda-developers.com/showthread.php?t=876848
scroll down until you get to cm7 kernels and download the latest grandkin kernel! instructions are on the page =)
I use fauxs oc/uv just cause he's awesome and you can oc it to 1.8 ghz but you have to be careful when overclocking I'd suggest setting up the governers and profiles in setcpu after flashing the kernel. But no you don't need to wipe anything just boot into recovery and install
Sent from my HTC Glacier using XDA Premium App
Stuck on load
Hey y'all, I have CM7 on my Evo and tried to flash incredikernel http://forum.xda-developers.com/showthread.php?t=848453 using clockwordmod rom manager. Everything seemed to go fine but now it will not get past the white htc evo 4g boot screen. How shall I proceed? I was going to just reflash CM7 but wanted to see what the 'correct' thing to do is, help please!
SOLVED, I definitely learned something new today. Kernels are phone specific haha!
Do you feel the CM10 917+ Builds are less buttery or more choppy... It is due to a change in the CM source that removes VSYNC and replaces it with IOCTL that is much more power efficient.! Anyway if you want the smoothness over power until CM fixes it...
Flash this pack to revert the changes to the VSYNC.! [works with 917&918]
PS: Make sure you flash Either CM10 914 Kernel or Semaphore 2.1.0/2.1.0s or Devil before 917 , else you will have a black screen, after flashing the pack as they require kernel change.!
PS: New NOMUTEX Patch by pawitp. Download.! [Flash in Recovery. No need for kernel changes.]
ok, good to know there is a workaround for when the latest flashed cm10 is lagging, thx for that!
one question though: you only write cm10kernel or semaphore, is it not possible to use this with devil-kernel?
EDIT: 1.4.1 of DerTeufel's jellybean-kernel should work, too, shouldn't it?
it was made before the vsync-change and it is a kernel for cm10.
or is there any specific reason why devil-kernel not works for this?
EDIT2: ok, i just saw your edit right now, thx!
so everybody that wants to use cm10 WITHOUT the new vsync-change WITH devil-kernel should flash version 1.4.1 of it after flashing this mod.
greetz n thx,
sUsH
Is hellybean using VSYNC or IOCTL (knowing that devil kernel is vsync)
exadeci said:
Is hellybean using VSYNC or IOCTL (knowing that devil kernel is vsync)
Click to expand...
Click to collapse
Yes the latest version is.
yeah i experience the same problem
after flashing back to 9/14
all problem gone
I think there's bug in 17and 18 version
I read from the thread that the 918 build solves the problem... Don't quote me on this though.
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
greetz,
sUsH
Thanks nice that someone works on it!
Sent from my GT-I9000 using xda premium
sUsH667 said:
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
Click to expand...
Click to collapse
Nope kernel mod not required.
sUsH667 said:
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
greetz,
sUsH
Click to expand...
Click to collapse
mnazim said:
Nope kernel mod not required.
Click to expand...
Click to collapse
ah, ok, i get it, no kernel mod required cause there is a kernel included that gets flashed when using this zip...
so i better ask again:
can this new patch be used with other kernels?
and since there is a kernel included, the way would be
1. flash rom
2. flash patch
3. flash wished kernel
is that right?
EDIT: any idea what the patch.diff in the flashable is good for?
thx for clarification!
greetz,
sUsH
mnazim said:
Yes the latest version is.
Click to expand...
Click to collapse
What is IOCTL ?
sUsH667 said:
EDIT: any idea what the patch.diff in the flashable is good for?
Click to expand...
Click to collapse
I believe IOCTL will hold a lock on the framebuffer that is released only during the next vsync. this is the reason for microlags.
Read more Here.
AlwaysDroid said:
What is IOCTL ?
Click to expand...
Click to collapse
IOCTL is Input Output Control. It is a specific system call/api that does i/o operations in the system.
Read More.!
Hi guys, happy new year!
So, i'm testing the rom "Nexus 5 Experience (Kitkat 4.4.2)" and everything seems ok, i'm testing the version CAF Kernel. now i'm tryin install new kernels on this rom, but at every kernel I install i get the same error, after instal any kernel, I turn on my N4 and the screen seems very strange, colors flashing, sometimes when i start a game (or anything that forces the gpu) the screen is filled by one or two colors, but the touch is still working, is just a screen or gpu (i dont know) error.
I tryed to take some printscreens, but when i will check this on my pc, everything is ok, like if theres no error.
When i flash the rom again, everything works normally.
what i'm doing wrong ? I thought to change kernel is only flash him, is it wrong ?
i'm newbie, got my n4 yesterday but i have some experience in my old xperia..
sorry the bad english, im br
Thanks guys!!
Are you installing CM compatible kernels?
Try the AK kernel CM version
http://ak.hiddenbytes.org/old/cm//AK.309.CM11P.zip
goofball2k said:
Are you installing CM compatible kernels?
Try the AK kernel CM version
Click to expand...
Click to collapse
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
mendes1995 said:
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
Click to expand...
Click to collapse
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
goofball2k said:
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
Click to expand...
Click to collapse
yes, i'll try HellsCore.
thanks for the help, i appreciate it!