Related
Hi Dev Guys..
I was testing the CM7 build, but i need all camare resources working well.. Then, i was intended to rollback to stock froyo rom..
But, i like to play games like NOVA on milestone and, every know that multitouch is so worst on stock then CM7... I think is because the kernel used in this custom roms...
Then i ask... Can I use this kernel on my stock Rom? How Can i apply and find the necessary file??
My best Regarts to everyone that try to help me, i think this is help everybody...
May be this is what you are looking for..
http://forum.xda-developers.com/showthread.php?t=1167665
jorgebaruchi ,
Yes, the touchscreen in CM7 is much less sensitive, than on froyo, but less buggy also.
But as I know, CM7 is also built on 2.2 kernel, so, do not really think that you will have any benefit of CM7 kernel. Touchscreen response is hidden somewhere in hardware libs, so, it is very difficult to find and fix it.
Actually, i prefer a less sensitive touch but with a multitouch working fine..
Then, the point is... can i install that kernel or the gb leakek kernel on my stock rom?
Sent from my A953 using XDA App
jorgebaruchi said:
Actually, i prefer a less sensitive touch but with a multitouch working fine..
Then, the point is... can i install that kernel or the gb leakek kernel on my stock rom?
Sent from my A953 using XDA App
Click to expand...
Click to collapse
Multitouch is not provided by a modded kernel, but by a kernel module (posted above). You can load it with insmod or flash CM7/MIUI to apply it.
Sent from my Milestone 2 XDA App
dangpzanco said:
Multitouch is not provided by a modded kernel, but by a kernel module (posted above). You can load it with insmod or flash CM7/MIUI to apply it.
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Thanks Man!! Correct if i´m wrong.. If I apply this patch, that the propose is expand the multitouch limits, it will fix the multitouch issue in fps games, like NOVA ???
jorgebaruchi said:
Thanks Man!! Correct if i´m wrong.. If I apply this patch, that the propose is expand the multitouch limits, it will fix the multitouch issue in fps games, like NOVA ???
Click to expand...
Click to collapse
Yeps, it works fine for me.
ok,Tks man.. i will try this module again.. but, just for curiosit, how did u extract the kernel for on the CM7 ROM ?
Hmmm... I think this mod is not fixing the MT bug unfortunately. It lets you expand the limitation of MT points but the bug will still exist. I've been using this mod, so I know that. Or maybe I missed something? Anyway, it didn't fix this bug for me. And now I am using the ms2ginger which is totally free of it
mkmck said:
Hmmm... I think this mod is not fixing the MT bug unfortunately. It lets you expand the limitation of MT points but the bug will still exist. I've been using this mod, so I know that. Or maybe I missed something? Anyway, it didn't fix this bug for me. And now I am using the ms2ginger which is totally free of it
Click to expand...
Click to collapse
yeah, i had tested this module at the morning and nothing change in NOVA.. now i apply the CM7 1.5 RC and its so easiler to play...
lets contribute for the community.. =)
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
it was the same for me. nscollab was unusable since it was always freezing in two minutes after boot. changing the kernel did not help. so I decided to change the rom to Nexus MV 10.05. it works very stable (not a single reboot or freeze) and faster than nscollab.
mikkkg said:
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
Click to expand...
Click to collapse
Well, I found that custom kernels can work with stock ROM's. I'm using stock Google 2.3.6 on my 9023 + pete's kernel with Voodoo sound and BLN. Stable as ****, practically no issues, I'm happy with my NS as never before just because of the lack of constant flashing the **** around to "optimize". It just works flawlessly.
Here's the link to the kernel : http://www.peteralfonso.com/2011/08/download-nexus-s-263514-kernel.html
Had the no wake issue with cm7 216 and nscol 1.4.5. On nscol 1.4.6 and no problems yet. If it happens again it would seem to be a cm7 issue. While annoying devs are constantly hunting down and correcting problems, just the way it is and doesn't bother me.
Sent from my Nexus S using xda premium
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
The hole point for me is not using any other kernel but the stock one.. compile yourself a nexus s kernel (google it for how to) and be happy without any reboot, crash..
baterry? normally 1.5 days @ 1.0ghz..
You could do that as well
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
.45 with stock voltages caused the "pin asking" issue even with stock voltages(even with 5.5 cfs - maybe a cyanogen problem?), so that's why i am stuck at .42 with 5.5 cfs and did not even try .46.
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
If you see, in the thread of nscollab, there are also problems with the phone dying etc, even with the new stable cyanogenmod + matr1x kernel.
I only do tests in my mobile during the weekend, because i use it all week for my job. So stuck with matr1x 5.5 until i see a really stable matr1x kernel coming after 8.
madd0g said:
Here's the link to the kernel :
Click to expand...
Click to collapse
Thank you very much for posting this link. I did not know that kernel. I just found some time to flash nscollab .50 with this kernel and i only changed interactive governor with ondemand to be even closer to stock kernel.
I hope that it is as stable as it is for you.
After some hours with this new kernel, i am not sure about stability(although it seems stable) but nexus is running smoothier than ever.
I've used ondemand from the beginning I started using this kernel, then I tried interactive (default) just to try it out. Not really a difference, same stability/speed and I could get rid of NoFrillsCPU app setting the default governor at startup. So to wrap up, kernel runs beautiful from the start, no extra fiddling necessary.
I do not believe the issues described in the OP are kernel related. They persist in all custom kernels. I think it is from Dalvik VM crash but I have no proof.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Id say if you want stability, stay on stock, extra features like BLN and Voodoo sound are added via kernel anyway.
Sent from my Nexus S using Tapatalk
mikkkg said:
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Click to expand...
Click to collapse
Kalimocho found a kernel error and a missing vendor file in the CM kernel. It will be fixed in the next nightly. The hope is that this was the cause of the freezes/reboots/bootloops/dimscreen bootloops that people were seeing.
mikkkg said:
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
Click to expand...
Click to collapse
I use this, if it helps you.
Thread here.
mikkkg said:
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
Click to expand...
Click to collapse
lol i keep looking but i dont find anything
ahhhh
Thank you for opening this page.
My A953 is a Europe device, and the version i use is MIUI-X1.12.2X (kenerl version is 2.6.32.9).
The problem is that the touch screen isn't accurate, when i touch position A , the device thinks i touched B, which is over A(upper half screen) or uner A(under half sereen). But the distance between A and B is very short , i can only notice it when i search the contects by touching the first-letter.
And there is a place on the lower right screen, which can't responce any touching.
This two problems also worked on CM7 nightly version which i used. But i can fix them by disable the mulititouch(doesn't work on miui..).
Would someone please help me ? Thanks a lot !(I'm sorry for my terrible English...)
All the defy based roms has a bad multitouch compare to cm7 "original" for milestone2 (tezet rom).
Sent from my MotoA953 using xda premium
Thank you . I have flashed UK 2.3.4 and will "never" be able to use MIUI.
Sent from my A953 using XDA App
The kernel for the official gingerbread release still has the multitouch bug, are you experiencing this issue still?
Yes , because this issue is realated to the kernel, A2S is only a nandroid backup package.
With I experienced, if you put two finger on the screen with a short distance , MS2 will recognize them as one touch point(I notice this issue when i play Cut The Rope). But If you use froyo , you may not have this probelm
Yeah I know. Sucks to be you - I hope to never update to keep my options open. CH GB kernel all the way
My main touch problems were with FPS games, it'd switch between what touch point it thought was point "a" and point "b", so I'd end up getting stuck running against a wall until I'd pause and resume.
Hopefully when my phone is back from warranty repairs it'll still be on Froyo. They said it would be updated to the latest firmware, so for once being in the last thought of nation Australia will possibly pay off (we haven't gotten an update yet).
So, the only way to avoid touch bug is install the chiness gb sbf? I have tried almost all roms (endless cm7, tezet cm7, a2s, walter79 mod, miui) and all of them have touch bug.
My brother has a brand new razr, and it actually has the same touch bug (the same bug i experience with tezet cm, when playing games with two virtual sticks, after a minute or so touching the screen it goes a little funky, need to release the fingers or pause the game or turn off and on the screen.
Actually is a bit different than the old froyo touch bug, but a bug still.
Sent from my MotoA953 using XDA App
I'm pretty sure that the actual games themself have some coding issues and mess up on there own accord from time to time with touch screen input, but the multitouch bug certainly makes a mild problem much worse. (basing this on reviews you see ferom people with other devices saying stuff like "touch controls are glitchy" etc etc, alo I've experienced the occasional glitch on shadowgun playing on my Sony Tablet S)
If you have updated to official gingerbread, you are stuck on a non-downgradable kernel that has the multitouch bug.
If you are still on froyo the current roms using the CH GB kernel (the one that doesn't have multitouch bug) are CM9, CM7 defy port from endless7, Argen2Stone. (ms2ginger and blurless too possibly)
MIUI and CM7 use froyo kernels and have the bug.
DreadPirateDan said:
I'm pretty sure that the actual games themself have some coding issues and mess up on there own accord from time to time with touch screen input, but the multitouch bug certainly makes a mild problem much worse. (basing this on reviews you see ferom people with other devices saying stuff like "touch controls are glitchy" etc etc, alo I've experienced the occasional glitch on shadowgun playing on my Sony Tablet S)
If you have updated to official gingerbread, you are stuck on a non-downgradable kernel that has the multitouch bug.
If you are still on froyo the current roms using the CH GB kernel (the one that doesn't have multitouch bug) are CM9, CM7 defy port from endless7, Argen2Stone. (ms2ginger and blurless too possibly)
MIUI and CM7 use froyo kernels and have the bug.
Click to expand...
Click to collapse
It's possible to Switch the UK Kernel to CH Kernel?
---------- Post added at 11:21 PM ---------- Previous post was at 11:13 PM ----------
The brazilian 2.3.6 kernel don't have this bug. If you upgraded for the GB Official, you can try the 2.3.6 brazilian...
No， certenly not. Because UK GB kernel is based on NEW BOOTLOADER , if you flash old chinese gb kernel or old froyo kernel ,you will get a black screen so you must flash the kernel that based on new BL.
The new chinese kernel is based on the new BL,too.(4.5.1-5)(I can't remember it clearly, it seems like this)
But the brazil 2.3.6 is based on the NEWER BL than UK or chinese new gb kernel. so never flash it.
Now the cm7 , cm9 , argen2stone , mokee os works on the new gb kernel well.
Sent from my A953 using XDA App
mkyybx said:
No certenly not. Because UK GB kernel is based on NEW BOOTLOADER , if you flash old chinese gb kernel or old froyo kernel ,you will get a black screen so you must flash the kernel that based on new BL.
The new chinese kernel is based on the new BL,too.(4.5.1-5)(I can't remember it clearly, it seems like this)
But the brazil 2.3.6 is based on the NEWER BL than UK or chinese new gb kernel. so never flash it.
Now the cm7 , cm9 , argen2stone , mokee os works on the new gb kernel well.
Sent from my A953 using XDA App
Click to expand...
Click to collapse
Yes, i know this, but i have flashed the 2.3.6 brazilian sbf. After this, i have flashed the Uk 2.3.4 and works... Why? If the brazilian BL is newer than UK BL? Why i don't have the black screen?
I thought anyone could flash the newer boot loader? It came out before the official update. It's just the kernel can't be changed once your on the UK GB kernel. Or at least that's as far as I'm aware.
For example, I could update my boot loader but still use the UK froyo kernel no worries, is what I mean.
Pretty swish at that brazilian kernel though, I've never looked into it since I never updated. So would he just be able to flash the BR kernel and see how that goes right?
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
marcoahs said:
If the brazilian BL is newer than UK BL? Why i don't have the black screen?
Click to expand...
Click to collapse
This is basically what I meant.. it's not the boot loader, it's the kernels. And since it's once of the kernels from official gingerbread, it's all sweet
DreadPirateDan said:
I'm pretty sure that the actual games themself have some coding issues and mess up on there own accord from time to time with touch screen input, but the multitouch bug certainly makes a mild problem much worse. (basing this on reviews you see ferom people with other devices saying stuff like "touch controls are glitchy" etc etc, alo I've experienced the occasional glitch on shadowgun playing on my Sony Tablet S)
If you have updated to official gingerbread, you are stuck on a non-downgradable kernel that has the multitouch bug.
If you are still on froyo the current roms using the CH GB kernel (the one that doesn't have multitouch bug) are CM9, CM7 defy port from endless7, Argen2Stone. (ms2ginger and blurless too possibly)
MIUI and CM7 use froyo kernels and have the bug.
Click to expand...
Click to collapse
Actually im coming from endless defy port and has the same touch bug that im facing with tezet's rom. I dont know maybe is some kind of hardware failure, or touch screen drivers poorly coded by moto. Im testing this issue with this game: Cartoon Wars: Gunner+ from Zenonia.
Playing this game with a Samsung Galaxy S2 doesnt have this weird multitouch bug. As i said, it happens just after using the multitouch from some time (maybe one minute more or less).
Playing with a Moto Razr has this bug (another moto, coincidence?). Maybe is the way the game handle the multitouch that is one way or another not compatible with moto kernels.
My point is, that in all of the m2 roms there are multitouch bugs (annoying in some roms, less annoying in others) and that is not a rom failure, thats moto's fail.
As i have said, i have used almost all the custom roms ( i havent flashed yet any of the GB sbf so im still safe XD) and in all of the i have multitouch issues.
I guess we have to deal with it, thanks Moto XD
And sorry for my very poor english.
Sent from my MotoA953 using XDA App
Sorry for may terrible english again. I am sorry that i can't understand your word " My main touch problems were with FPS games, it'd switch between what touch point it thought was point "a" and point "b", so I'd end up getting stuck running against a wall until I'd pause and resume. " although i have used google translate.
Now i list the touching bugs i have found.(a bit angry, why the words will be all deleted if i press del key after shift or alt key?)
1. When charging(especially via usb or chargers which have little current output), if you touch the screen without your body touching with the metal on the ms2 , the touch point will "fly" to all the screen(i have tried to play Talking Tom at that time, it was funny and crazy...)(this issue is mostly on froyo. and will be better if you flash cm7)
2. After you slide out the keyboard, for me, i will put my two fingers on my left hands on the metal around the screen. Sometimes when i slide the webpages with my right hand's fingers, the webpages will be zoomed automaticly.(only on official gb rom whatever uk or ch)
3. As i said yesterday, ms2 won't recognize you when you put two fingers with a short distance.(uk 2.3.4 kernel i haven'5 tset on the new chinese gb kernel)
4. Sometimes when i play fruit naja ,the ms2 won't response to my touching. I have to retouch and then works normally. I don't know how and when this issue will happen ,but in the multi touch test, i don't get this issue.
5. When i play dragon hunter2, sometimes i both touch the vitrual d-pad and the attack button and the d-pad will turn to the attack button.(i only test it on ch froyo official rom)
6. The same as my post, if you flash the miui(i flash the one by DoubleX from gfan), there will be a little square on the right-down screen with none touching response. And the whole screen isn't accurate.
7. ...... to be continue....
I think the best touching experience is from froyo uk rom. And the bugs are mainly caused by the metal around the screnn(i didn't get these issues on the defy and the touching on the defy is very very very nice)
Sent from my A953 using XDA App
I didn't try it myself, i only heard it on Gfan. If you downgrade successfully, it means the chinese new gb kernel, the europe gb kernel and the brazil kernel are all bsed on BL=6
Sent from my A953 using XDA App
@rasecrmz
Perhaps this issue is more-so related to the OMAP SOC used in these devices. If you know anyone with a galaxy s (1), see if they have the same issue. Then we know whether it's specifically those games having the issue with the hardware + drivers (and not with moto) or if it's only while on a moto device
The galaxy s uses an sgx540 while MS2 use a sgx530 (as I recall anyway). So pretty similar hardware inside. RAZR also uses sgx540.
@ mkyybx
I mean: My left thumb will be pressing the left side of the screen. My right thumb will be pressing the right side of the screen. Somehow it thinks they swap around, although they do not. The controls of the game I'm playing then fail.
That's pretty vague but it will hopefully translate better .
It would be ok. To lock the BL stronger , moto have updated the bl version. Because the new bl will only apccept the sbf file that have moto official signed. I tried to push all the uk 2.3.4 rom files to the UK froyo official rom by the update.zip , but i failed because of the probem with the signature.
Chinese old gb kernel (4.5.3-77(109)) is based on old bl
Sent from my A953 using XDA App
mkyybx said:
I think the best touching experience is from froyo uk rom. And the bugs are mainly caused by the metal around the screnn(i didn't get these issues on the defy and the touching on the defy is very very very nice)
Sent from my A953 using XDA App
Click to expand...
Click to collapse
It's just paint though with plastic underneath though
DreadPirateDan said:
I thought anyone could flash the newer boot loader? It came out before the official update. It's just the kernel can't be changed once your on the UK GB kernel. Or at least that's as far as I'm aware.
For example, I could update my boot loader but still use the UK froyo kernel no worries, is what I mean.
Pretty swish at that brazilian kernel though, I've never looked into it since I never updated. So would he just be able to flash the BR kernel and see how that goes right?
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
This is basically what I meant.. it's not the boot loader, it's the kernels. And since it's once of the kernels from official gingerbread, it's all sweet
Click to expand...
Click to collapse
Yes, i think like you. I don't updated my BL. It's the same: 70.12. The kernel is the problem. But, if i sucessfully downgraded 2.3.6 Br to 2.3.4 UK, i can flash the CH 2.3.4, right?
You could try, but I'd be confident to make a wager it wouldn't work ;D
Just wanted to thank everyone on this forum for the knowledge they have contributed. Finally did my upgrade to b526 official so I can start playing with ICS roms. Went very smoothly and i should have done it a while ago. Running TMC cm7.2 currently and it is very fast and smooth. Only issue is no haptic feedback on the soft keys. This was the same as the stock rom so it is probably an atmel thing.
Thanks to all the people who have taken time out to post their knowledge and experience on this forum. Hopefully we can get a couple of stable ICS roms on this phone.
You have to know that .35 kernels having random reboots.
If you want start working on something will be good to start 3.x kernel from dzo or Blefish...More stable there..
demolition23 said:
You have to know that .35 kernels having random reboots.
If you want start working on something will be good to start 3.x kernel from dzo or Blefish...More stable there..
Click to expand...
Click to collapse
I used one of the kernels Forumber posted a while back right from the start and It was really smooth and fast, needed to swap it out because I have an atmel screen. Although I have had some issues with TMC cm7.2 missing calls I not had a reboot on .35 yet. Aurora works great too. really liking it a lot. Glad I made the step up to the new firmware.
Means I can start playing with ICS kernels too. Hopefully will have more success on that front than I have had so far. Have not produced a working kernel yet.
Hope to end up with something stable!
Sent from my U8800 using Tapatalk 2
hi everyone , i'm newbie , pls tell me about what is kernel? , i access website htc kernel , i see they don't support mytouch 4g anymore , i want to download new kernel for mytouch 4g , pls tell me where i can download , thanks so much , my english is not good
Kernels are very ROM type specific. We need to know what ROM you're on. Then we can help you.
i tested rom ViperTouch v1.0.1 | Sense 4.1 | 4.0.4 and yoshi 4.1, but i have a problem myscreen about 1-2 minute flash and go on ,i try fix but i can't , i don't know why and i think to up kernel , i don't know where download kernel mytouch 4g 4.1
If you're having the screen flickering problem, it is kernel related. However, it is across all of the kernels on this device. At least, as far as I know. Sorry
Use an old rom that uses 2.x kernel or switch to GB.
Sent from my Nexus 4 using Tapatalk 2
thanks everyone , i will try it
blue1231988 said:
thanks everyone , i will try it
Click to expand...
Click to collapse
I don't have screen flickering on CM 10.1 with the 3.0.57 kernel. You can try that if you want a newer version of Android.
Undiscovered said:
I don't have screen flickering on CM 10.1 with the 3.0.57 kernel. You can try that if you want a newer version of Android.
Click to expand...
Click to collapse
Some phones get flickering, some don't. Mine never did. Did yours flicker on other ROMs?
Undiscovered said:
I don't have screen flickering on CM 10.1 with the 3.0.57 kernel. You can try that if you want a newer version of Android.
Click to expand...
Click to collapse
i have screen flickering and camcorder problem on cm10.1 with 3.0.57 with mt4g. may be new kernel will fix this problem.
My never flicked with GB, but the moment I flash a ICS or JB, the flicker is on. Some said that it is in Sense framework and kernel, but I do not have Sense. With CM10 4.2.1 and .60 kernel, the flicker is on. Got to be patience. Some day, some one, will find solution.