I'm using Franco's Kernel v15 + ZRAM with Mik's CM7 6.5.2. At first it was a dream, 1352 points on quadrant and 58.5fps on neocore @480/729Mhz Smartass. Everything running smooth and really fast.
About 6 hours of intense testing some apps (many, in fact) started crashing for no reason. Mostly google apps like Calendar and even Market. But also some widgets and running services.
I reflashed everything, even re-formatted (and re-partitioned) my sdcard and everything was fine again but after a reboot to install google applications (gapps-gb-20110325-signed.zip) the crashes started again. And I was running w/o overclocking at this time.
Searching for some info on the issue I saw a post stating that v15 kernel is for FROYO only so it's not compatible with CM7 but Franco always said that his Kernel was compatible with CM7 and there's no such info coming from Franco himself so I want to be sure of it before flashing a Froyo ROM.
Any thoughts on this issue? Any help is appreciated.
Edit:
Maybe it's worth noting that my phone is a O1 p500h, apart from the 3.2mp camera I don't really know if there's other differences in hardware that may cause problems.
That h is ur problem I think
I really hope not. I've been using Franco Kernel + CM7 for many versions and never had any problems with it (well, aside CM7's known bugs).
I'm from Brazil and CM7 is the only ROM I know that has Brazilian Portuguese (pt-BR) language support. All other ROMs I tried are strictly european and only have support for Portugal's Portuguese (pt-PT), which is kinda different and "sounds" quite annoying at some times.
And while I feel quite confortable using english, it's not the same thing as your mother tongue.
Its weird some users reported this kind of stuff.
I think its safer to use dookmatt kernel than franco kernel
Could a theme cause this kind of instability? I just remembered that on both times the crashes started I was experimenting with a XperiaArc theme for CM7.
Are you using app2sd or data2sd? These may cause such conflicts at time.
Vip_blast said:
Are you using app2sd or data2sd? These may cause such conflicts at time.
Click to expand...
Click to collapse
Nope, but I have an Ext4 partition on my SD-Card so I get more "internal" memory for installing apps.
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
doktornotor said:
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
The answer remains "no", I'm not using app2sd nor data2sd.
You missed the point. Whatever are you using for this can cause the instability. Apparently top secret stuff, so... go help yourself I guess.
Sent from my LG-P500 using XDA App
I am facing certain problems like you after flashing devoid.franco+kernel V15+ ZRAM.
I had following issues for the past 15 days.
1. changed the stock ROM to devoid Franco + V14
I agree the performance of the phone increased. Did OC using Set CPU. Score over the Quadrant was never over 650, not an issue with this as long as i can feel the diff in the performance.
One major change i saw was - as you all know the SMSes get threaded with a particular contact (both recd and sent msgs.). In my case if i receive sms from TD-I-mint, the message was shown as received from TD-Reylon, similar with all the SMSes, the actual sender was never possible to know when you see the list of msgs. Only after you open the msgs then you could find out the sender.
this is continuing still with Kernel 15.
2. same situation after flashing V14.1, V14.2, V14.2.2.
3. with Kernel V 15 + devoid.francoROM with little change. I wiped everything, SD was partitioned and upgraded to EXT 4. Flashed new ROM (05-06-2011), rebooted, flashed Kernel V15, rebooted, flashed ZRAM, rebooted, but phone never came to life, had to remove the battery and reboot, same result. Then wiped cache and dev cache, then flashed ZRAM, the phone was breathing.
Then tried to flash the system apps downloaded from first post of http://forum.xda-developers.com/showthread.php?t=1049518&page=1, the phone lost its life and had to re-do the whole process of flashing ROM....
With update of ROM + Kernel V15, i had to re-do the whole process for 5-6 times. I never had this problem with older kernels or flashing custom ROM.
One major issue is - msgs and other apps like TB (list of backups) some times display vertically. Today for the first time the SMS app was force closed.
Any-body facing issues like this or issues and you have the solution , I request you to post here.
I guess the best solution for me is to use the stock ROM with franco.kernel. This way I maintain my country's language (and, most important, GPS configuration) and still get some nice tweaks from Franco's.
By reading the comments on v15 kernel, it seems wise to wait for a new version before installing it. There are several users experiencing heavy battery drain. Or maybe install v14.2, but I don't have it anymore.
So, is it safe to use franco.kernel v14-v15 with LG stock ROM (mine came with v10A, android 2.2.1)? Or does it have any compatibility issues?
Thanks for your replies.
touch fix
hi, Does this kernel has the touch fix like Mik_os' kernel?
cas0404 said:
hi, Does this kernel has the touch fix like Mik_os' kernel?
Click to expand...
Click to collapse
Yes it does. Am running stock 2.2.2 with Franco's kernel v15 and its smooth as butter.
Running 2.2.1 stock ROM + franco.kernel v15 for about 10 hours now, so far no significant change on battery use.
But I miss mik's ROM performance... FPS on neocore dropped from 57fps to 36.5fps. And my old score on quadrant was 1350 and now is 615.
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
drakull said:
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
Click to expand...
Click to collapse
Wait for 2.3 to be released.
Related
Hy everybody. I just bought a Htc Hero and I`m wondering wich is the best rom to put on it? thanks
It depends what you're looking for really.
VillainROM 13 is like stock, has HTC Sense, but quick, like very quick!
My personal favourite is RCMix 2.2. It is a Sense ROM but has a few nice visual tweaks.
And there's Cyanogen. They've recently dropped support for the Hero, but the nightly releases aren't too bad.
Basically just try as many as possible and see how you get on with them.
I would like to know which one is the most stable, without any bugs, fastest etc.
I have installed Villainrom v13. It's really fast, but I think there is a bug, because my battery drains empty in 6-12 hours, when on my original ROM it held for 24-30 hours.
Hi
Hello I am wondering the same thing. I have installed a 2.3 version and I am not that happy although some things are better everytime I go to the home screen it has to load which never happened with my stock 2.1 Orange rom.
Anyone can recommend a ver stable and fast rom would be much appreciated?
snailydale said:
It depends what you're looking for really.
VillainROM 13 is like stock, has HTC Sense, but quick, like very quick!
My personal favourite is RCMix 2.2. It is a Sense ROM but has a few nice visual tweaks.
And there's Cyanogen. They've recently dropped support for the Hero, but the nightly releases aren't too bad.
Basically just try as many as possible and see how you get on with them.
Click to expand...
Click to collapse
Hi! I looked into the VillainROM 13 but its only Android 2.1 I really need 2.2 for app2sd and also sharepoint. Do you have a link to the other roms you recommended? And are they easy to install with rom manager and the recovery software that comeswith that?
Thanks mate
Yes, we are newbees on Android and we need your opinions.I have now on my phone Android version 2.3.2, tasty version gingerbread 2.0, kernel version 2.6.29.6-RaKern-200 [email protected] #14, Baseband version 63.18.55.06pu_6.35.15.11. IS THIS A GOOD ROM? What are his advantages and disadvantages? Thanks everybody in advance & sorry for my bad english
I've tried a few ROM's. I've got backups of Villain13, Elelinux 7, and Floyo.
At the moment, for daily use I'm on Floyo 1.2. I have been using Elelinux, and in general it's a nice ROM but the black screen bug that you have probably heard about is rather annoying. Hopefully with the discussions between Erasmux and Elelinux they will come up with an idea to get Cyanogen Hero dev back under-way.
But for day-to-day use I'd go Floyo 1.2. You can flash a gingerbread theme if you really have to. I find its rock solid and the kernel can be overclocked via flashing.
Also, Apps2SD is supported (old fashioned style). If you have a fast SD card, why bother with the Google version?
Good luck, and if there is any help I can offer....
Tbh if you want a fast stable driver, that you'll use daily then i'd use VR13. Froyo and Gingerbread have never been officially released for Hero so using Rom's based on these android versions means you will encounter a few bugs and some lag. If you really need App2SD then you could use dark tremor's script which will install it for you. I'm gonna post up my own 2.1 rom which will have App2SD enabled if you wanna try it. But from experience of nearly every hero rom available on xda, VR13 is the best.
Thanks JieHD, could you plese tell me were I can foun this rom, and a quick guide to intall it om my Hero? Thanks in advance
TBH i've never had lag on Floyo, or any other problem for that matter. The only thing is you don't get the HTC add-ons.
VR13 is good, but I do miss Friendstream. Been using the one out of Launcher Pro.... Each to their own.....
My advice, flash one, try it for a while. Do a full backup in Rom Manager. Then flash another.... But beware, you will become addicted to flashing (ROM's that is).
As I said earlier, I keep a few on my SD card. So easy to restore in Rom Manager...
Anybody could tell me how to install a new rom on my Hero and how to get rid of the old one?
tibbyke said:
Thanks JieHD, could you plese tell me were I can foun this rom, and a quick guide to intall it om my Hero? Thanks in advance
Click to expand...
Click to collapse
http://dl.dropbox.com/u/23463603/JieeHD's_Hero_Litev1.zip
should be up soon, to install:
1. Boot into rcovery
2. wipe data
3. wipe cache ( if you use it )
4. wipe dalvik-cache ( this is in advanced options if you use cwm )
5. install rom from sd card
6. reboot, should take about minutes
As a side note, just for a nicer user experience -- download spare parts+ frm market and set windows animation to fast and transition animations to fast. and tick fancy input animations
I will lose my apps and data on my phone? How can I backup them?
use titanium backup from the market
If you tried out my rom, tell me what you think
Sent from my HTC Hero using XDA App
Alucardas said:
I would like to know which one is the most stable, without any bugs, fastest etc.
I have installed Villainrom v13. It's really fast, but I think there is a bug, because my battery drains empty in 6-12 hours, when on my original ROM it held for 24-30 hours.
Click to expand...
Click to collapse
i was tested a lot of roms and finally my favourite rom is VILLAINROM V.13 because is soo STABLE (IMPORTANT),works fast...,and the most important for me: has sense widgets for drain battery i´m ussing flykernel 12a with O/C, SETCPU at 514 mhz conservative.(battery drains empty in 24 hours more or less)...
if there was some froyo rom with sense and working camera It would be brilliant because chocolate froyo for example works well
JieeHD said:
If you tried out my rom, tell me what you think
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Tried it this morning, was nice a smooth, just the icons were not to my taste, if I get some spare time over the weekend I'll knock up an alternative framework, being elderly I find the circle battery meters hard to read when they have numbers in the middle, or that could just be this mornings hangover
A 'Team Highly Medicated' Release:
Hello everyone,
As highly anticipated, here is my port of dumfuq's overclocking patches ported to 2.6.35.10.
If you test it and Android either doesn't boot or is very slow, then you are experiencing an incompatibility that cannot and will not be fixed. Please note, I do not know if this kernel is compatible with Android versions below Gingerbread (2.3) because the Interprocess Communication (IPC) agent version differs.
http://www.multiupload.com/CNKQEWXIUH
Notice (added 7/20/2011): It has been made apparent by users and myself that as your battery gets lower, the slower your phone will become despite it showing it is overclocked. This is most likely because 787MHz requires the max voltage and the phone is unable to maintain that voltage as the phone loses charge. While batteries are measured in mAH (milliamps), the voltage exerted from the battery progressively decreases with the loss of mAH. The reason it requires this voltage is because of FSB and CPU multipliers... it is otherwise impossible to obtain that clock-rate with lower voltages. I will investigate possible workarounds.
No need to disable perflock. Remember to use SetCPU to actually overclock! Interactive governor enabled by default - it's a beauty!
Version 3, UPDATE 6/22/2011 @ 8:18pm CST:
- dumfuq was very helpful and I have (hopefully) now fixed the instability issues present in version 2.
- Due to complications with how frequencies are stepped I am limiting the max frequency to 787MHz.
- Please note, this is a TEST version and I am seeking any feedback regarding stability.
Version 2, UPDATE 5/27/2011 @ 11:24pm CST:
- Fix wifi.
- Actually enable Interactive governor by default.
Like it? Click the "Thanks" button - or even better "Donate"!
Peace out.
Is this the kernel that was mentioned to be added to the Salsa Slide ROM?
Although I suppose that's more of a question for Ohgami.
Can I just use this with it anyways? Thanks nbetcher!
SefEXE said:
Is this the kernel that was mentioned to be added to the Salsa Slide ROM?
Although I suppose that's more of a question for Ohgami.
Can I just use this with it anyways? Thanks nbetcher!
Click to expand...
Click to collapse
Ohgami wanted to have me release it separately. So yes, you most certainly can use it with it anyways.
Thanks nbetcher
Sent from my T-Mobile myTouch 3G Slide using XDA App
Ah yes what we've been waiting for. I agree though this kernel is Damn snappy without oc. But I have to try it out right. I'm curious to know though, if you said this works with ext2/3/4, will darktremor a2sd work with this and salsa port?
Sent from my fingertips using Android.
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Wagedroid said:
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Click to expand...
Click to collapse
retry i was stuck for a little bit but it came around
EDIT: the kernel keeps freezing my phone on salsa rom
Force Close City. Running CM Nightly 76. Fixed permissions and I still get a bunch of FC popups.
Hi, great job!
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Thanks.
ogo2 said:
Hi, great job!
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Thanks.
Click to expand...
Click to collapse
From the O.P.
Apps2SD included: http://www.multiupload.com/9EVC6CL8FP (your ROM needs Apps2SD support though!)
Non-Apps2SD: http://www.multiupload.com/8N1JPBM4N0
(By "Apps2SD", I mean the old-school Ext2/3/4 separate partition on your SD card. Either of these zips support the crappy Froyo (or higher) "Move to SD" function.)
I removed Perflock from the kernel entirely, so no need to disable Perflock.
koolkidjay1321 said:
retry i was stuck for a little bit but it came around
EDIT: the kernel keeps freezing my phone on salsa rom
Click to expand...
Click to collapse
I'm sorry to hear it's freezing. It's most likely clocked too high. Please make sure to clock it down.
ogo2 said:
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Click to expand...
Click to collapse
No, it's been included by Kitchen via the init.rc. Kitchen batches the init.rc to add Apps2SD support.
Wagedroid said:
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Click to expand...
Click to collapse
Same here, using latest CM nightly.
this kernel freezes my legend
ogo2 said:
this kernel freezes my legend
Click to expand...
Click to collapse
Overclocking or at boot?... Try lowering your speed and don't set it to start at boot.
Sent from my fingertips using Android.
I have not set anything connected to overclocking.
The system just hangs on boot (after entering the pin code and before the sense is loaded).
ogo2 said:
I have not set anything connected to overclocking.
The system just hangs on boot (after entering the pin code and before the sense is loaded).
Click to expand...
Click to collapse
I don't know if the Legend has the same frequency/voltage/bus speeds as Latte, so I can't promise that this would work on another device like the Legend. I'm learning that although the Legend is similar to Latte, they do have some very different parts.
nbetcher said:
I don't know if the Legend has the same frequency/voltage/bus speeds as Latte, so I can't promise that this would work on another device like the Legend. I'm learning that although the Legend is similar to Latte, they do have some very different parts.
Click to expand...
Click to collapse
They are both based on the MSM7227 SoC, so there shouldn't be any dramatical difference between them.
i had to load the rom before loading the kernel
koolkidjay1321 said:
i had to load the rom before loading the kernel
Click to expand...
Click to collapse
Tried this, thank cwm for backups. Fail, stuck on splash.
Sent from my fingertips using Android.
Hello,
Yesterday I installed Wolf's package. Now I redid the whole thing with the new V3.5
My question:
Are speedfixes and tweaks included in the Wolf_GB_2.3_TW_V3.5.zip?
My problems:
-Neocore only gives me 30.7 fps
-Quadrant only gives my 1100 points
And I'm pretty sure I installed the package correctly.
kr1st0f1 said:
Hello,
Yesterday I installed Wolf's package. Now I redid the whole thing with the new V3.5
My question:
Are speedfixes and tweaks included in the Wolf_GB_2.3_TW_V3.5.zip?
My problems:
-Neocore only gives me 30.7 fps
-Quadrant only gives my 1100 points
And I'm pretty sure I installed the package correctly.
Click to expand...
Click to collapse
You should ask him on his thread.
But yes, they're included. There's a new version now.
http://forum.xda-developers.com/showthread.php?t=1192988
Yes but as I am a new member, I can't post in his thread because it is very likely that the question's answer is already in his thread.
OT: I wiped dalvik cache as someone mentionned in his thread, but that didn't help.
EDIT: Useless post again I think, after rebooting got 2200 points so it's fine
hey im a newbee here , and please don't get angry with me asking this
I have just installed wolf's GB 3.5 ,
Do i have to install speed tweak 3.2 following GB 3.5 installation
I went through the main OP but couldn't find mention like that on GB V3.5 post
Thank you so much
u need not install anything except wolfs' v3.5 everythin included except theme chooser!!!
thats all ...
even m using the same thing only
Hope it clears ur doubt !!
Thank me if it helps !!
Its really fast. Lol
Sent from my X10i using XDA App
trollertron22 said:
Its really fast. Lol
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I know right! I'm amazed with it
I would like to know about battery life, since everytime I switch stock to any custom firmware I get more speed but verry little battery life (I have tried freex10, cm6, cm7, miui, tripnmiui).
How's your battery life with that rom, if I may ask?
proyectomx said:
I would like to know about battery life, since everytime I switch stock to any custom firmware I get more speed but verry little battery life (I have tried freex10, cm6, cm7, miui, tripnmiui).
How's your battery life with that rom, if I may ask?
Click to expand...
Click to collapse
battery life is awesome, i switch wifi on all night and it drain only 4% ^^!
Im currently on the first WB and speedfix 008v4.
Do I need to completely reflash to get to 3.5, and then update to 3.6?
Whats the difference between all the different ROMS? Found like 6 on XDA? Which one is the most popular, WB?
Thanks
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Thats new bug you phased not anyone tell about and not im phasing any that thing
v2.2 and v2.3 are almost same just few things like odexed and some fix not much other thing
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
I got this too http://forum.xda-developers.com/showthread.php?t=1271268
I don't have that bug... did you flash the framework for v2.2 before flashing 2.3? maybe this dosn't afect to the touchscreen but just only to see what was your flashing process.
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
acesteady said:
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
Click to expand...
Click to collapse
moded framework allready gave in rom
touchscreen prob of keypad you tell is not happen atall in my phone
Im reply all things from my phone not from pc means not phasing that stuff yet
will try to solve for those phasing in new version
adeklipse said:
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
Click to expand...
Click to collapse
thanks for the quick reply nims, just info for you the bug that I found is just exactly the same as adeklipse said
acesteady said:
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Click to expand...
Click to collapse
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
icemanhi said:
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
Click to expand...
Click to collapse
And "#throwinag##"% fthus akernael wdill make it wsorks,h rigsht?
This is the text that I typed without any correctionss
And "throwing" thus kernel will make it work, right?
Sent from my GT-S5830
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
adeklipse said:
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
Click to expand...
Click to collapse
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
acesteady said:
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
Click to expand...
Click to collapse
Yep, I went with flashing the non-oc kernel as well. Underclocking will still leave you with the problem.
Sami-sami.
*ane orang Banjar nyasar ke Bandung, gan.
Sent from my GT-S5830
I use 800 MHz on oc kernel and not facing this problem.. maybe I'll try above 800..
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
adinq said:
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
Click to expand...
Click to collapse
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
I also have the same Problem.
It was all fine with froyo 2.2, when i switched to stock 2.3.3 kpe or 2.3.4 kph this problem occured. It stopped happening with 2.3.3 kpy and its perfectly fine with the 2.3.5 stock firmwares.
My big problem is, i cant use any custom roms, it happens with every single custom rom.
So it's not really a warranty issue when it happens with custom roms. Coz samsung could say it works fine with stcok firmware, 2.3.3 kpy for example.
I really don't know what the cause of the problem is, because my friends galaxy ace doesnt have these problems with the custom roms i tried.
I'm not sure but besides the kernel i kinda think it might be a battery issue, because it happens less frequently when its plugged to the charger.
adeklipse said:
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
Click to expand...
Click to collapse
may be this mod can help you..
http://forum.xda-developers.com/showthread.php?t=1365434
i OCed to 883MHz without problem on touchscreen
matur nuwun
aku wong solo bro...╋╋ム ╋╋ム ╋╋ム =)) ╋╋ム ╋╋ム ╋╋ム
pls press thanks button if you like this.
sorry for my bad english
I recently switchef back to tasks AOKP ROM after trying out shostock. I like AOKP the best because of the layout options beep encountering problems with the ROM. I know its no longer in development so I assume its stable and its just user error. I also don't know where else to ask these questions so I hope I am in the right place
First off, I can't access the settings (not AOKP settings) in the menu. It crashes every time. EVEN on a fresh install with nothing but the gaps.
Second, the ROM starts to slow down after only a little bit of use. I want to say this is bad memory managment but clearing the task manager doesn't help. The only thing that gets it up to speed is using the kernel tweaks app and setting the gov. to performance mode which really kills the battery.
Third, which type of kernel would I use to put on this ROM? With or without mic swap? Plus what is the difference between AOKP and AOSP?
Sorry for the nooby questions guys but I'm rusty on this stuff. Don't bash on me too hard
Probably best place to ask would be the thread already created for it. http://forum.xda-developers.com/showthread.php?t=2303484 I've ran this rom myself and can say I didn't experience any of these issues, a lot of the time it's user error or not doing a complete and total wipe before installing. Or a bad flash.
As far as I know, AJK v4.9 AOSP and STI v2.40EX14 would be the choices for a custom kernel. Use the AOSP version, not the swap or no swap versions.
AOSP = Android Open Source Project
AOKP = Android Open Kang Project
AOSP is a generic term for Google's code. AOKP and all the other rom names such as cyanogenmod, miui, carbon, etc. are names given by the developers.
Oh, and nobody around here bashes any more. All the high strung guys evidently have moved on to newer phones. Or they've mellowed with time, lol.
I installed ajk kernal and it gave me a huge speed boost. But I still get a ui crash when I go into settings=>kernel settings. Any ideas?
aspen1135 said:
I installed ajk kernal and it gave me a huge speed boost. But I still get a ui crash when I go into settings=>kernel settings. Any ideas?
Click to expand...
Click to collapse
Yes, don't use the kernel settings in the settings menu. It was meant for the custom kernel that originally came with that rom.
Instead, use STweaks to make any changes you desire; it was installed when you flashed AJK.
sent from the i777
SteveMurphy said:
Yes, don't use the kernel settings in the settings menu. It was meant for the custom kernel that originally came with that rom.
Instead, use STweaks to make any changes you desire; it was installed when you flashed AJK.
sent from the i777
Click to expand...
Click to collapse
Ah, TY dude. I tryed this kernal a long time ago when it was still in its early dev stages and there were some bugs. I remember STweaks but you had to install it via the play store. I kept searching for "st tweaks" not STweaks so it wasn't showing up. I was wondering what happened! haha