Guest fear_factory84 Posted May 17, 2011 Report Posted May 17, 2011 is it better then ritchen`s kernel? what`s the difference between this kernels? With this kernel you have full source tree, you can modify it, review it, do what you want. It's on github. Ritchen's kernel it's very similar, based on thepasto chocolate kernel like this, but he didn't share its source tree, so you have only a precompiled kernel. I cannot tell you what changes since we haven't its sources. I tried to ask him many times. Fortunately he shares its fixes with thepasto (like mic issue), so we also can get them.
Guest Dario93 Posted May 17, 2011 Report Posted May 17, 2011 Hey man,thanks for your guide+kernel :) I will make a sticky request if you agree :unsure:
Guest gnufabio Posted May 17, 2011 Report Posted May 17, 2011 Hey man,thanks for your guide+kernel :) I will make a sticky request if you agree :unsure: Obviously i agree, thanks :P
Guest groverkai Posted May 18, 2011 Report Posted May 18, 2011 (edited) I have a BOOTLOOP problem when using USB connection. I don't know what the differences are between my rom and others. I have tried: 4.008.08.EMEA.VFIT + LeoGingerBreadV5.0 --> BOOTLOOP 4.008.08.EMEA.VFIT + fear_4.008.08.EMEA.VFIT + gnufabio's kernel --> BOOTLOOP 4.008.08.EMEA.VFIT + fear_4.008.08.EMEA.VFIT + rithchen's kernel --> it's fine but battery temp is too high :) 4.008.08.EMEA.VFIT + t&l_Gingerbread_Edition.08 + gnufabio's kernel --> BOOTLOOP 4.008.08.EMEA.VFIT + t&l_Gingerbread_Edition.08 + rithchen's kernel --> It's fine. 4.002.14.EMEA.GEN1_A22F_A + fear_4.008.08.EMEA.VFIT + gnufabio's kernel --> BOOTLOOP 4.002.14.EMEA.GEN1_A22F_A + fear_4.008.08.EMEA.VFIT + rithchen's kernel --> it's fine. 4.002.14.EMEA.GEN1_A22F_A + LeoGingerBreadV5.0 --> I forgot to test it. :P As I know there are some ppl have this issue too. Sorry I am not a dev so I can't help you to check where the problem is exactly. :unsure: BTW, my device is Liquid E. Thanks anyway. Edited May 18, 2011 by groverkai
Guest gnufabio Posted May 18, 2011 Report Posted May 18, 2011 I have a BOOTLOOP problem when using USB connection. I don't know what the differences are between my rom and others. I have tried: 4.008.08.EMEA.VFIT + LeoGingerBreadV5.0 --> BOOTLOOP 4.008.08.EMEA.VFIT + fear_4.008.08.EMEA.VFIT + gnufabio's kernel --> BOOTLOOP 4.008.08.EMEA.VFIT + fear_4.008.08.EMEA.VFIT + rithchen's kernel --> it's fine but battery temp is too high :) 4.008.08.EMEA.VFIT + t&l_Gingerbread_Edition.08 + gnufabio's kernel --> BOOTLOOP 4.008.08.EMEA.VFIT + t&l_Gingerbread_Edition.08 + rithchen's kernel --> It's fine. 4.002.14.EMEA.GEN1_A22F_A + fear_4.008.08.EMEA.VFIT + gnufabio's kernel --> BOOTLOOP 4.002.14.EMEA.GEN1_A22F_A + fear_4.008.08.EMEA.VFIT + rithchen's kernel --> it's fine. 4.002.14.EMEA.GEN1_A22F_A + LeoGingerBreadV5.0 --> I forgot to test it. :P As I know there are some ppl have this issue too. Sorry I am not a dev so I can't help you to check where the problem is exactly. :unsure: BTW, my device is Liquid E. Thanks anyway. Can you post the logcat?
Guest gnufabio Posted May 18, 2011 Report Posted May 18, 2011 Updated kacer script http://goo.gl/0EVAj
Guest groverkai Posted May 18, 2011 Report Posted May 18, 2011 Can you post the logcat? No logcat because it reboots before adb connect to the device. I only got the message "waiting for device". I've tried using " adb logcat > log.txt " but it's useless. I'll try to make a short movie and upload it to show you how. Sorry for my poor Engilsh. :unsure: Thanks again!
Guest gnufabio Posted May 18, 2011 Report Posted May 18, 2011 No logcat because it reboots before adb connect to the device. I only got the message "waiting for device". I've tried using " adb logcat > log.txt " but it's useless. I'll try to make a short movie and upload it to show you how. Sorry for my poor Engilsh. :unsure: Thanks again! Uhm...to strange. fear rom + choco kernel works great for me...try to reflash the rom and wipe all data if you don't resolve the problem
Guest groverkai Posted May 18, 2011 Report Posted May 18, 2011 (edited) Uhm...to strange. fear rom + choco kernel works great for me...try to reflash the rom and wipe all data if you don't resolve the problem Is it possbile the device differences? ( Liquid and Liquid E) Will it help if I upload both logcat (two kernels with/without USB connect)? I have tried all the options(reflash, wipe all , wipe one by one) therefore you can see the post #29 :P Edited May 18, 2011 by groverkai
Guest thepasto Posted May 18, 2011 Report Posted May 18, 2011 Is it possbile the device differences? ( Liquid and Liquid E) Will it help if I upload both logcat (two kernels with/without USB connect)? I have tried all the options(reflash, wipe all , wipe one by one) therefore you can see the post #29 :rolleyes: It would be nice to have kernel panic log about that.. to get it you need apanic support in kenrel. then you can find it in /data/dontpanic/apanic_console. -turn on your phone -when boot is finished insert usb cable -after reboot remove usb cable -waiting for boot completed -put on pastebin.com or somewhere the apanic_console content -give us the link Thanks :P
Guest gnufabio Posted May 18, 2011 Report Posted May 18, 2011 Yeah but it's a bit strange, you're the first with this problem..
Guest groverkai Posted May 18, 2011 Report Posted May 18, 2011 It would be nice to have kernel panic log about that.. to get it you need apanic support in kenrel. then you can find it in /data/dontpanic/apanic_console. -turn on your phone -when boot is finished insert usb cable -after reboot remove usb cable -waiting for boot completed -put on pastebin.com or somewhere the apanic_console content -give us the link Thanks :P I can't find any files in that folder, it's empty. Does the apanic support file have some constant name format?(like "apanic_yyyymmdd....txt") I found some files similar in SDcard. Thanks for your help thepasto!
Guest thepasto Posted May 18, 2011 Report Posted May 18, 2011 I can't find any files in that folder, it's empty. Does the apanic support file have some constant name format?(like "apanic_yyyymmdd....txt") I found some files similar in SDcard. Thanks for your help thepasto! yeah you're right.. these files are ok.. when you have time you can upload them thanks to you :P
Guest groverkai Posted May 18, 2011 Report Posted May 18, 2011 yeah you're right.. these files are ok.. when you have time you can upload them thanks to you :P Okay, here is pastebin link: apanic_20110519 And I upload the txt file here too.apanic_201105190110.txt
Guest gnufabio Posted May 18, 2011 Report Posted May 18, 2011 (edited) Great news, thepasto fixed the problem. I'm compiling a new kernel right now. Download: http://www.multiupload.com/R5USTQFUEZ Edited May 18, 2011 by gnufabio
Guest thepasto Posted May 18, 2011 Report Posted May 18, 2011 Great news, thepasto fixed the problem. I'm compiling a new kernel right now. Download: http://www.multiupload.com/R5USTQFUEZ I hope it is solved :rolleyes: i can't test it because i don't have this problem... Anyway for now only a bad workaround not really a solution :P
Guest rithchen Posted May 19, 2011 Report Posted May 19, 2011 Okay, here is pastebin link: apanic_20110519 And I upload the txt file here too. What clock rate are you use? And did you use my fix2 kerenl to compare? I raise the voltage to 1300mv at 883mhz. If your crash situation(gunfabio's kernel) was above 768mhz, change the speed to 768mhz, and try again. BTW, i still working on the voice issue on skype, and it's not about mic, it's about audio encoding in qualcomm's dsp.
Guest groverkai Posted May 19, 2011 Report Posted May 19, 2011 (edited) I hope it is solved :D i can't test it because i don't have this problem... Anyway for now only a bad workaround not really a solution :rolleyes: It works! Thank you gnufabio and thepasto <_< What clock rate are you use? And did you use my fix2 kerenl to compare? I raise the voltage to 1300mv at 883mhz. If your crash situation(gunfabio's kernel) was above 768mhz, change the speed to 768mhz, and try again. BTW, i still working on the voice issue on skype, and it's not about mic, it's about audio encoding in qualcomm's dsp. I use OC 998mhz because it is stable to me since 2.1 eclair. :D I've tried your kernel (v1fix repacked by PhoenixWright) with fear_custom rom, and your kernel (v2fix) with T&L .08 rom. Your kernel won't reboot but gnufabio's will. It only reboots when connecting to PC, so I think OC is not the problem.....I guess :D And rithchen your kernel is very great , besdies the temperature. I just tried to set the speed to 768mhz but it still reboots. :P It works now with the newset patch. There is another discussion about Liquid reboot. HERE Maybe some other roms also have this problem though there are fewer users have this situation. Hope my questions can help you to make our Liquid better :( Edited May 19, 2011 by groverkai
Guest gnufabio Posted May 19, 2011 Report Posted May 19, 2011 It works! Thank you gnufabio and thepasto :P It works now with the newset patch. Great :rolleyes:
Guest ahyim Posted May 20, 2011 Report Posted May 20, 2011 I hope it is solved :rolleyes: i can't test it because i don't have this problem... Anyway for now only a bad workaround not really a solution :P Thank you for great kernel, but I install your kernel all work fine except the buletooth cannot be turning on. Will you try to test it?
Guest gnufabio Posted May 20, 2011 Report Posted May 20, 2011 Thank you for great kernel, but I install your kernel all work fine except the buletooth cannot be turning on. Will you try to test it? Do you mean on acer stock roms?
Guest ahyim Posted May 20, 2011 Report Posted May 20, 2011 Do you mean on acer stock roms? I try on this rom 4.005.05.AAP.GEN2_A22F_A_256mb_bbs.gfan.com
Guest gnufabio Posted May 20, 2011 Report Posted May 20, 2011 I try on this rom 4.005.05.AAP.GEN2_A22F_A_256mb_bbs.gfan.com Uhm, i didn't tested bluetooth, have anyone the same problem?
Guest ahyim Posted May 21, 2011 Report Posted May 21, 2011 Thanks gnufabio, The bluetooth is ok on 4.002.14.EMEA.GEN1_A22F_A_256.
Guest gnufabio Posted May 21, 2011 Report Posted May 21, 2011 Thanks gnufabio, The bluetooth is ok on 4.002.14.EMEA.GEN1_A22F_A_256. So it worked? Great :P
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now