Hi guys. I have installed on my sgs2 the ressurection remix rom. It is fantastic as others roms but all this roms has a boring issue(if we can call it issue) when the screen is black and i unlook it, it gets up usually after 5 second or more. How can i increase the reaction. I searched to change something in Stweaks but i'm not expert. Can you help me? Thank you.
Hi,
did you flash the roms correctly with a full wipe? On all roms based 4.2 and 4.3 i didnt have this kind of problem.
Did you restore some apps with titanium backup, maybe there´s a problem.
Andi
andi2398 said:
Hi,
did you flash the roms correctly with a full wipe? On all roms based 4.2 and 4.3 i didnt have this kind of problem.
Did you restore some apps with titanium backup, maybe there´s a problem.
Andi
Click to expand...
Click to collapse
Yes i restored my app using another app but i don't think it can be a problem. I think it is related to the cpu speed when the screen if .
Are you using setcpu or similar apps to change the CPU frequency? Cause different governors during screen on and screen off may create such problems.
santhosh502 said:
Are you using setcpu or similar apps to change the CPU frequency? Cause different governors during screen on and screen off may create such problems.
Click to expand...
Click to collapse
Yes. You solve my problem thankyou.
Artificialkid47 said:
Yes. You solve my problem thankyou.
Click to expand...
Click to collapse
If you're using Stweaks (you mentioned that above) then there's no need whatsoever for SetCPU. In fact, the settings in Stweaks and in SetCPU may be clashing with each other. I'd say to get rid of SetCPU and use Stweaks as the kernel dev (I assume dorimanx) intended.
Sent from a galaxy far, far away
Related
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
Hi there~i'm new to xda so i cannot post in the development thread but only here.....
I'm using krabappel2548's KA rom, it really gd and fast and stable
i have two problems, when i use google+ hangouts, i see other's image ok and i see myself ok, but the other side (i.e. the ppl i'm talking to) told me that the color of my image is not correct......my face is blue; when i show him a blue object he saw orange;when i show him a pink object he saw blue.....anyone has similar problem?
the other is the map, the compass is not working. i read some threads in xda also stating similar problem, and it only happens in Google Maps 6.x but not 5.xx. Just want to know what is the origin of problem?
Hope it wont be too long...thanks so much!
just tried Skype, the situation is the same, just everything is green instead of blue......
Have tried to reflash the kernel? Sometimes it solves some problems..
Which kernel are you using?? Use NON OC kernel and test it..
Really strange Problem !
I just tried to reproduce it with my old X8, cause my only idea on this was that you installed a wrong localised Rom
(imo US Rom / Jap Rom instead of EU or something like this).
But didn´t get any similar display errors.
I would recommend starting up from the scratch, reinstalling Stock Kernel/rom.
drugbone said:
Have tried to reflash the kernel? Sometimes it solves some problems..
Click to expand...
Click to collapse
if i reflash the kernel again, will i erase everything on my phone?
protocol11 said:
Which kernel are you using?? Use NON OC kernel and test it..
Click to expand...
Click to collapse
i'm already using non oc kernel...
ymwca said:
if i reflash the kernel again, will i erase everything on my phone?
Click to expand...
Click to collapse
No just flashing the kernel doesn´t erase userdata
ymwca said:
if i reflash the kernel again, will i erase everything on my phone?
Click to expand...
Click to collapse
No, its just the kernel, so no apps or data will be losed
Sent from my fast & supercharged Neo V and a tiny keyboard xD
thanks!
i refreshed the kernel but it doesn't help.....anyway thanks!
Q&A for [KERNEL] [I9300] [Samsung JB] Boeffla-Kernel 5.3/6.0 (08-07-2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
No sound during call
This might be one of the best kernels for the 4.4 roms out there but it has just one problem in my device : there's no sound during calls. This happens only when I have Boeffla , as soon as I flash another kernel the sound fixes. I have tried uninstalling Boeffla Config and running the kernel without it but it's the same. How to solve this ? Thank you.
eb6 said:
This might be one of the best kernels for the 4.4 roms out there but it has just one problem in my device : there's no sound during calls. This happens only when I have Boeffla , as soon as I flash another kernel the sound fixes. I have tried uninstalling Boeffla Config and running the kernel without it but it's the same. How to solve this ? Thank you.
Click to expand...
Click to collapse
Hi,
make sure your init.d folder does not contain left overs of other kernels.
Especially when you were on Agni Pure before, this is a known issue as it overwrites Boeffla-Settings in an incompatible way.
Andi
eb6 said:
This might be one of the best kernels for the 4.4 roms out there but it has just one problem in my device : there's no sound during calls. This happens only when I have Boeffla , as soon as I flash another kernel the sound fixes. I have tried uninstalling Boeffla Config and running the kernel without it but it's the same. How to solve this ? Thank you.
Click to expand...
Click to collapse
Lord Boeffla said:
Hi,
make sure your init.d folder does not contain left overs of other kernels.
Especially when you were on Agni Pure before, this is a known issue as it overwrites Boeffla-Settings in an incompatible way.
Andi
Click to expand...
Click to collapse
I had similar problem with sound. Just before writting here I realized that I flashed again Boeffla after testing different kernel. After cleaning - see above - issue disapperared.
Wrong section, delete.
kernel issue
hi good night i install the kernel today with the rom back-to-n00t- and when boot i lose my sdcard (internal) i uset a cwm touch as well and have a issue with that, i have to remove the kernel for keep my internal sdcard, some can help me?
Cwm touch comes with it's own kernel, so this proves it is not a kernel problem.
Must be something else, maybe a defective sd card...
Lord Boeffla said:
Cwm touch comes with it's own kernel, so this proves it is not a kernel problem.
Must be something else, maybe a defective sd card...
Click to expand...
Click to collapse
im i mean with de internal storage, i dont have a sd card chip at this momento, when try to get in on the sd into cwm touch and intal zip, say sdcard/0/ seems the kernel put the "/0" to my phone. before flashing the new cwm touch i used a TWR and trying to flash get a error on this kernel. some help?
thx
Hi Andi,
triangle away will work on QS-kk rom?
mahe. said:
Hi Andi,
triangle away will work on QS-kk rom?
Click to expand...
Click to collapse
I never tried it. I am not very sure Triangle Away is compatible with any S3 kk rom.
I would be very cautious to not end up in a brick.
I recall I purposely did not put native TriangleAway support into my 6.x series kernel, to not open up any risk here.
Andi
Lord Boeffla said:
I never tried it. I am not very sure Triangle Away is compatible with any S3 kk rom.
I would be very cautious to not end up in a brick.
I recall I purposely did not put native TriangleAway support into my 6.x series kernel, to not open up any risk here.
Andi
Click to expand...
Click to collapse
Andi,
could you please add above mentioned suggestion in op if not done already? i think this very good piece of information.
Hello.
In NIK60 ROM v.3.0 (4.4.4) I installed Kernel Boeffla 6 Beta 6 with the latest Boeffla Config V2 with Boeffla Config change the values and to reset the phone's settings Governor, the Governor's profile and Internal memory back to their default values pegasusq, standard and CFQ. The other parameters I've changed if maintained.
Where can be the problem? I have proven to Beta 5 and with different versions of Boeffla Config and the result is the same.
Sorry for my bad English.
Thank you
xileftld said:
Hello.
In NIK60 ROM v.3.0 (4.4.4) I installed Kernel Boeffla 6 Beta 6 with the latest Boeffla Config V2 with Boeffla Config change the values and to reset the phone's settings Governor, the Governor's profile and Internal memory back to their default values pegasusq, standard and CFQ. The other parameters I've changed if maintained.
Where can be the problem? I have proven to Beta 5 and with different versions of Boeffla Config and the result is the same.
Sorry for my bad English.
Thank you
Click to expand...
Click to collapse
Must have something to do with the rom.
It seems like
- either you have scripts init.d that overwrite the settings
- you have another app that resets this stuff again
- the rom start takes extremely long (you can give additional startup delay in boeffla-configs settings for a try)
Unfortunately there is no way to do a better diagnose without having your phone in hands.
But... there are reasons why I recommend going on pretty clean roms like JustArchis Port. There these kind of things do not happen.
Andi
Lord Boeffla said:
Must have something to do with the rom.
It seems like
- either you have scripts init.d that overwrite the settings
- you have another app that resets this stuff again
- the rom start takes extremely long (you can give additional startup delay in boeffla-configs settings for a try)
Unfortunately there is no way to do a better diagnose without having your phone in hands.
But... there are reasons why I recommend going on pretty clean roms like JustArchis Port. There these kind of things do not happen.
Andi
Click to expand...
Click to collapse
Just try to Blekota ROM 8.1 and the result is the same, previously had Blekota 8.0 and had no problem.
The install has been fully cleaned, wiping up the internal sd.
Init.d folder only has 2 files and 99SuperSUDaemon 85sqlite
Thank you.
xileftld said:
Just try to Blekota ROM 8.1 and the result is the same, previously had Blekota 8.0 and had no problem.
The install has been fully cleaned, wiping up the internal sd.
Init.d folder only has 2 files and 99SuperSUDaemon 85sqlite
Thank you.
Click to expand...
Click to collapse
I am sorry, but I have no time to try all sort of roms. That's what you users need to do.
I officially do not support the roms you mentioned, only Archiport. So, if all works, fine. But if not, it is like it is.
Especially on the 6.x kernel series I do give only very limited support as it is kinda inofficial and experimental kernel only.
If it worked fine on Blekota 8.0 and not on 8.1 anymore, it is quite obvious something changed which broke some functionality. But as said, I cannot support all roms around as my day only has 24 hours
Thanks for understanding
Andi
Ok, let's start writing in this Boeffla Q&A thread
zRam...for needing multitasking if not working that good...but which values???
I'm on stock 1 device 300mb and 80 swappiness....any other super better setting???
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
PIRATA! said:
Ok, let's start writing in this Boeffla Q&A thread
zRam...for needing multitasking if not working that good...but which values???
I'm on stock 1 device 300mb....any other super better setting???
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
Click to expand...
Click to collapse
WHEN (!) I use zram, I use 600 MB total size with 4 devices.
But I almost never use it, I am a lean user, I always close my apps with back button. So zRam is not required for me.
Andi
installed on a fresh V5 coming from a V2, changed nothing in the settings, works flawlessly. Smooth and fast, thanks man!
SHV E210K
I 'm using S3 SHV E210K and my phone don't boot when i flash boeffla kernel.
Do boeffla kernel support my phone?
Lame question maybe. Should I turn the S3 power saving feature on while running a power saving profile or is it useless?
So today my OnePlus X came and I`m a little bit lost now. I want it to run without any stuttering in games and apps, but I know that the default cpu/gpu governors in this device are rubbish. So after doing some research I found blu spark`s kernel for opx, but in the comments I found out that the camera is slower (really important to me) and it has a delay in app loading. Maybe I can flash that kernel and change the governor myself for the personal best results? Or just leave it where it is? I just don`t know what to do with it, maybe someone could share their experience?
You could just change the governor of the stock kernel which will give you significant better gaming experience without losing camera quality and such (which I can not confirm or didn't noticed)
XqepX said:
You could just change the governor of the stock kernel which will give you significant better gaming experience without losing camera quality and such (which I can not confirm or didn't noticed)
Click to expand...
Click to collapse
*Noob question* - Could I just try flashing spark kernel and go back to default kernel if it won`t work well for me?
Should work Give it a shot
Hyper_X said:
*Noob question* - Could I just try flashing spark kernel and go back to default kernel if it won`t work well for me?
Click to expand...
Click to collapse
If you do a backup of system and boot partitions before flashing the custom kernel, you should be fine. Also a full backup is recommend before root so you could restore and take OTAs.
raulx222 said:
If you do a backup of system and boot partitions before flashing the custom kernel, you should be fine. Also a full backup is recommend before root so you could restore and take OTAs.
Click to expand...
Click to collapse
Ok, thanks now I done all possible backups and placed then in my pc for security reasons [emoji1] . Now I can test everything out myself.
Sent from my ONE E1003 using Tapatalk
So, i have installed the paranoid rom(link) WITHOUT having any black screens at all , but the camera simply does not work. I chose this ROM because it is the only one that allows cpu overclocking...
Do you know how to fix this anoying problem with the camera?Nobody is anwsering in the official thread. Also , do you know if there are any custom kernels for this phone ?
thank you in advance
panira said:
So, i have installed the paranoid rom(link) WITHOUT having any black screens at all , but the camera simply does not work. I chose this ROM because it is the only one that allows cpu overclocking...
Do you know how to fix this anoying problem with the camera?Nobody is anwsering in the official thread. Also , do you know if there are any custom kernels for this phone ?
thank you in advance
Click to expand...
Click to collapse
I thing there is an app that can fix your problem on cm11 based roms but i don't know if it is the solution for your problem, Please try to submit a cat log with your problem so it would be easier to help you. ^_^ (this app need root privilages) https://play.google.com/store/apps/details?id=com.billgbennett.camerafix