since i cant post in dev section ...
i wanted to know if siyah kernel has any type of "upgraded" ram management .
i had problems with my alarm clock not going off a few times . tried to investigate whats causing this (no task killers of any kind installed) and i found that if a fill up the memory with lots of junk , the cashed clock process will be stopped eventually .
i tried to set an alarm , then open many apps until the cashed clock process will close - it did close , but the alarm stil went off somehow , strange.
as of now , i cant recriate the alarm not going off issue , so i'm just asking if the modified kernel has anything to do with it (i know the kernel has memory management of some kind)
tanx
Yo, I guess the Kernel can be blamed for stuff like this. My advice is to flash and see for yourself. Dont forget to clear cache/dalvik in cwm before you flash.Perhaps do a system clean-up by removing apps you really dont need
Sent from outer space by aliens on tapatalk using SGS2
That's almost impossible to say if the kernel was responsible for an event like that.
Personally speaking, I use an old (stable) build of Siyah (2.1) and find it really really good.
So far as "upgraded ram management" goes, I'll ask in the Siyah thread & post any reply(ies) I get in here. How's that ?
What Siyah does do is enable you to under/over volt/clock in order to improve performance or battery, depending on what you do.
I'll get back to you with an answer re: the ram thing if I get one
Edit - P.S: AJ's suggestion to try a few Siyah builds for yourself & see how they go was good advice :-D
hackinistrator said:
since i cant post in dev section ...
i wanted to know if siyah kernel has any type of "upgraded" ram management .
i had problems with my alarm clock not going off a few times . tried to investigate whats causing this (no task killers of any kind installed) and i found that if a fill up the memory with lots of junk , the cashed clock process will be stopped eventually .
i tried to set an alarm , then open many apps until the cashed clock process will close - it did close , but the alarm stil went off somehow , strange.
as of now , i cant recriate the alarm not going off issue , so i'm just asking if the modified kernel has anything to do with it (i know the kernel has memory management of some kind)
tanx
Click to expand...
Click to collapse
thanks guys.
i'm not sure if its the kernel to blame , as i know the alarm not going off issue is not new (searched google)
After installed siyah2. 3 my Device cannot detect external sd.. can solve this problem?
Sent from my GT-I9100 using xda premium
Ask in the Siyah thread ?
budi5555 said:
After installed siyah2. 3 my Device cannot detect external sd.. can solve this problem?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Quick question...
I'm currently using CheckRom RevoHD V4 & DK 2.4.3, however, I'm looking at DK 2.5.2 & Siyah 2.6_S99. My question is which is the best kernel to install if I want decent battery life combined with performance for running emulators etc?
Don't really understand all this governor business.
Cheers.
I asked that question re: RAM in the Siyah thread and got no response
Soooo...You're going to have to build your number of posts up & ask the question yourself
hackinistrator said:
thanks guys.
i'm not sure if its the kernel to blame , as i know the alarm not going off issue is not new (searched google)
Click to expand...
Click to collapse
no worries mate , 3 posts already
MistahBungle said:
Ask in the Siyah thread ?
Click to expand...
Click to collapse
i have already ask in siyah thread.. and no one can help fix this..
Related
hello every body....
this is first time to me in this forum and i'm new on android world
please i need your help
i have an official update 2.1 update1 at my mobile and i dont need any rom coz i tried many roms there is all have a bug i prefer to be at this firmware.
but the point that i need to have multi touch i cant play angrybird and what about overclock can i get it how ?!?!
please i need help with links and files
I feel so sad when i read things like this.........
freedompals said:
hello every body....
this is first time to me in this forum and i'm new on android world
please i need your help
i have an official update 2.1 update1 at my mobile and i dont need any rom coz i tried many roms there is all have a bug i prefer to be at this firmware.
but the point that i need to have multi touch i cant play angrybird and what about overclock can i get it how ?!?!
please i need help with links and files
Click to expand...
Click to collapse
Next time use search functions on forums before posting like these.
There are threads regarding multitouch development. As of now we don't have this feature yet.
When playing angry birds, I don't use two fingers to play. I can play with single touch with no problems though lol.
Overclocking, use ROMs developed neither by owain94, slade 87, D4rKn3sSyS. Not all custom ROMs have major bugs. The said developers created custom ROMs we can use daily.
or once again use the search function to search on how you can overclock your phone without installing custom ROMs.
Lastly, don't forget those people who created ROMs that you will be using
fictionworld said:
Next time use search functions on forums before posting like these.
There are threads regarding multitouch development. As of now we don't have this feature yet.
When playing angry birds, I don't use two fingers to play. I can play with single touch with no problems though lol.
Overclocking, use ROMs developed neither by owain94, slade 87, D4rKn3sSyS. Not all custom ROMs have major bugs. The said developers created custom ROMs we can use daily.
or once again use the search function to search on how you can overclock your phone without installing custom ROMs.
Lastly, don't forget those people who created ROMs that you will be using
Click to expand...
Click to collapse
sorry sir I did not mean to offend Programmer....i respect him
but really i tried a lot of rom's through i follow the instruction but i faced a lot of bugs and so many restart issue
about the post i wrote it coz there is many subject and you will lost in forum
sorry again
freedompals said:
sorry sir I did not mean to offend Programmer....i respect him
but really i tried a lot of rom's through i follow the instruction but i faced a lot of bugs and so many restart issue
about the post i wrote it coz there is many subject and you will lost in forum
sorry again
Click to expand...
Click to collapse
I'm just telling no need to say sorry lol. I'm just a regular user of their custom ROM too lol. XD
Hmm. Before we customize our ROM we need to know first what's the requirements. What ROMS did you use? And what are your kernel version, android version and build number? You said you're on stock ROMs at the moment right? please do correct me if I'm wrong. xD
ok man thats clear
i followed the instruction every once i install rom i tried
MiniCM6-1.0.0
xCyanogenMini 7
and others i didnt remeber
but alway have so many reboots
i have now
2.1 update 1
m76xx-tsncjolym-53404015
2.1.1.a.0.6
hmm call me noob but uhh, your phone's a mini pro?
MiniCM6-1.0.0
I think the problem is that you are using ROMs which is only made for xperia mini. That's why you're getting a lot of bugs.
Please do correct me if I'm wrong.
Currently I use slades87 work, and its xCyanogen6 for mini pro. It works perfectly for me. Why won't you try that? The infos you gave me suited it actually.
no sir my phone is x10 mini not pro
what's are the exact problems that you are experiencing?
did you do a factory reset before installing the rom?
-factory reset
-wipe stats wipe dalvik-cache
-wipe cache
then try installing custom rom.
do you still have xrecovery installed?
open the zip file of your rom you want to flash with winrar
browse to /system/lib/modules/
highlight x8oc.ko and hit delete
copy zip to your sd again
reflash
be happy
Why need to do this??
Can I do in running room?
slade87 said:
open the zip file of your rom you want to flash with winrar
browse to /system/lib/modules/
highlight x8oc.ko and hit delete
copy zip to your sd again
reflash
be happy
Click to expand...
Click to collapse
axpira said:
Why need to do this??
Can I do in running room?
Click to expand...
Click to collapse
This is only if you have reboots, cuz if you have still reboots on froyo rom, you SHOULD delete overclock module !
x8oc.ko - this module can overclocks Your phone. Overclocking means that it's CPU runs faster than it is for. It is working for someones and do not work for others (!). Could bring dangerous unstableness, reboots.
Wise advice to delete it, but I can't understand why overclock a modROM by default? (if this is the case)
.x.x.x.Peria said:
x8oc.ko - this module can overclocks Your phone. Overclocking means that it's CPU runs faster than it is for. It is working for someones and do not work for others (!). Could bring dangerous unstableness, reboots.
Wise advice to delete it, but I can't understand why overclock a modROM by default? (if this is the case)
Click to expand...
Click to collapse
i've installed a few roms for my mini pro, they came with the max clock at 600mhz, only the overclocked version of slade87 MiniCM came with the max clock at 710 mhz. i don't know any rom for mini (not pro), but i think it should be similar
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
Heyy xda ppl
i'm on miracle ROM right now and the problem i have is random reboots i have no idea why...their frequency is more right after a reboot
its a pain cuz the memory card has to read everytime and it takes ages
and somehow i feel the miracle ROM has a longer boot time than any of my previous ROMS....the random reboots is a pain pls help me out
cpu is smartassv2 800-245mhz
pls help me out here
Edit: all right the problem was the sd card partition. I have a class 2 sd card and I partitioned it so maybe the read speed was not fast enough for the apps and stuff hence reboots.
I got to know this because I had connected my phone to pc and ran the error checking in properties doing that something happened and partition started acting weird I think it's vanished now (magic ) so then without the partition the phone started working smoothly like hell smoothly
Thanks for all your help guys
Bump
----------------
Did I send this :O
hi,
have you overclocked your phone if yes then downclock it to the normal 800 MHz and if the problem still persists try reflashing the ROM
because as far s my experince goes MIRACLE rom is by far the best rom its ver stable !!! let me know if i helped !!
sent from planet earth through millions of miles of optical fibres !!
No no not overclock
----------------
Did I send this :O
That happens when the device runs out of ram so if it starts to lag this usauly happens to me when I have a lot of apps installed and my phone memory is full
u can try moving apps to sd
and scripts like slaidyboost
GOOD LUCK
Is there any autostart app? Change ur governor? Or did u change the kernel?
I used to date ALICE EVE but now, I'm going steady with MEGAN FOX
dude...its a miracle rom, so u get the miracle
encik_racun said:
dude...its a miracle rom, so u get the miracle
Click to expand...
Click to collapse
I don't find it funny
This was sent from a Galaxy Ace. Problem?
Account removal
Deleted
EmoBoiix3 said:
I don't find it funny
This was sent from a Galaxy Ace. Problem?
Click to expand...
Click to collapse
true its better than other cm7.2 roms out there !!
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
ANDROIDCUSTOMIZe said:
That happens when the device runs out of ram so if it starts to lag this usauly happens to me when I have a lot of apps installed and my phone memory is full
u can try moving apps to sd
and scripts like slaidyboost
GOOD LUCK
Click to expand...
Click to collapse
the rom already comes with adrenaline engine 3.0 i guess and in my experince it doesnt work with other scripts
i had once tried to falsh slaidy boost and adrenaline engine and the same problem happened with me !!
Hi everyone
I tried to search forum but i dunno if there exits already this thread but i will explain here my details
I have samsung galaxy s2 at&t sgh-i777 cyanogen mod 7
The problem is when i receiv as gift from my father (he did buy at china) the phone wasnt original stock but prolly the china did flash cm7 and some kernel and govern (i think maybe is active for now ondemand if i can understand).
But i cant know which kernel is current using? how i can to see this info?
Searching forum many use AOKP, Fluxxi, Shostock and so on but my phone how i could know which one is using this kernel at moment? is there an app that i can see all system there? I tried using with Z device test but the information android OS is not enough.
I have to flash cm9 soon but first i must know all the info before to start this.
For modems is easy to see i have to tap on info about device that ok...but i need a full information so will help me a lot.
Thank for support
Ummmm.... How about go to settings, scroll down and touch "about phone" then look under "Kernel version"
BROKKANIC said:
Ummmm.... How about go to settings, scroll down and touch "about phone" then look under "Kernel version"
Click to expand...
Click to collapse
Ya thought that but is just number not name kernel if that help lol
How i would figured it?
kernel current anyway is 2.6.35.7 [email protected]#1
If was a kernel for CM7 ok but using Fluxxi for example what is then? is based still cyanogen? or Fluxxi is just a name rom?
This give me a bit confuse..
I saw some topic talking about kernel for siyah but i still dont understand if was for cmw or is just a kernel different way to work with this phone.
For this i need understand what he did chinese update my phone and what current kernel..
EDIT= i found on site for AT&T http://downloadandroidrom.com/file/GalaxyS2ATT/kernels
So this mean there are only 3 kernels compatible on this SGH-I777 isnt?
If that so then i have to know which one of this 3 kernels is current on my phone hmmm someone could give me a hint please?
you are using the kernel that COMES PACKAGED WITH CM7
i dont know why you would go to some other website looking for info, when all you have to do is open up the dev section here and READ.
there are more than 3 kernels available to you, but not many options if you are staying on CM7. if you are staying on CM7, just leave the kernel alone...
you dont really need to know anything more about what you currently have on your phone, because its simple. you are running CM7 with the kernel that was packaged with the rom. any rom you flash will have a kernel with it...
you see kernel names and are confused, i get that, but if you open the dev section and read, you will see threads marked as [KERNEL] or [ROM]....pretty simple to distinguish the 2.
for CWM, with Samsung devices, all custom kernels have cwM packaged in them, you dont need to do anything else but flash the rom after following the instructions in the first post on the rom thread.
Alan2012 said:
I have to flash cm9 soon but first i must know all the info before to start this.
Click to expand...
Click to collapse
Take a snapshot of your "About phones" before and after flashing any custom ROM and you see the difference.
For more kernel detail, bring up "CPU Spy" and take a snapshot before and after, and compare.
"CPU Spy" is an app.
Pirateghost said:
you are using the kernel that COMES PACKAGED WITH CM7
i dont know why you would go to some other website looking for info, when all you have to do is open up the dev section here and READ.
there are more than 3 kernels available to you, but not many options if you are staying on CM7. if you are staying on CM7, just leave the kernel alone...
you dont really need to know anything more about what you currently have on your phone, because its simple. you are running CM7 with the kernel that was packaged with the rom. any rom you flash will have a kernel with it...
you see kernel names and are confused, i get that, but if you open the dev section and read, you will see threads marked as [KERNEL] or [ROM]....pretty simple to distinguish the 2.
for CWM, with Samsung devices, all custom kernels have cwM packaged in them, you dont need to do anything else but flash the rom after following the instructions in the first post on the rom thread.
Click to expand...
Click to collapse
Thank you for all the clear information then at this point i can flash Cm9 without worry to think kernel...
I vote you for "thank" anyway
votinh said:
Take a snapshot of your "About phones" before and after flashing any custom ROM and you see the difference.
For more kernel detail, bring up "CPU Spy" and take a snapshot before and after, and compare.
"CPU Spy" is an app.
Click to expand...
Click to collapse
Thank for tell me about app should be usefull in near future
Alan2012 said:
Thank you for all the clear information then at this point i can flash Cm9 without worry to think kernel...
I vote you for "thank" anyway
Click to expand...
Click to collapse
all roms come packaged with a kernel so as long as you have CWM (you do because you are on CM7), then you can flash to CM9 without thinking about changing any kernels.
Hey i wonderf why not all apps on market are avaiable on this device sgh-i777?
I belive i got a email here message:
Hello,
We are sorry for the inconvenience.
Do you use a ROM on your smartphone ? If yes, our app used an app
licensing offer by google and all version of android which modify or no
official on a smartphone, Akinator app will be not compatible with there
smartphone.
Regards,
---
Android Akinator Team
So what the point if ROM cant use instead one without MOD ? i still dont understand....just wonderf -_-'
Alan2012 said:
Hey i wonderf why not all apps on market are avaiable on this device sgh-i777?
I belive i got a email here message:
Hello,
We are sorry for the inconvenience.
Do you use a ROM on your smartphone ? If yes, our app used an app
licensing offer by google and all version of android which modify or no
official on a smartphone, Akinator app will be not compatible with there
smartphone.
Regards,
---
Android Akinator Team
So what the point if ROM cant use instead one without MOD ? i still dont understand....just wonderf -_-'
Click to expand...
Click to collapse
I didn't understand any of this lol. But are u trying to say an app developer told u that an app isn't compatible with your phone because of a custom ROM? If so that's crazy. And shouldn't affect anything. Normally when an app says its incompatible its because u changed the dpi. If u didn't, I would try clearing the data on Google framework and Google playstore.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
I didn't understand any of this lol. But are u trying to say an app developer told u that an app isn't compatible with your phone because of a custom ROM? If so that's crazy. And shouldn't affect anything. Normally when an app says its incompatible its because u changed the dpi. If u didn't, I would try clearing the data on Google framework and Google playstore.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Yes exactly that i try to say but what exactly mean dpi? I didn't know about it anyway and about clearing is there a thread about step to step for it? Thanks!
Alan2012 said:
Yes exactly that i try to say but what exactly mean dpi? I didn't know about it anyway and about clearing is there a thread about step to step for it? Thanks!
Click to expand...
Click to collapse
Yes. There are threads on both. Do a Google search for clearing google framework and do one for clearing playstore data. If u don't know what DPI is u probably didn't change it. DPI is the resolution size for the display on the phone. (How big or small things look on the phone) Stock DPI is 240 for our phones.
Sent from my SGH-I777 using Tapatalk 2
Hello, I am a new user & unable to post directly on the Ultima thread, can someone please recommend a kernel for this ROM & the relevant settings?
What I need from my phone & how I use it:
Would like better battery life
I play NO games on the phone
I don't use any of the dual window multi task options
Do a lot of browsing on dolphin
Constantly in & out of messages/WhatsApp/phone dialer
Want no lag when I go into & out of applications
Many thanks in advance.
What rom what kernel posts are not allowed .
Read the thread and decide for yourself .
JJEgan said:
What rom what kernel posts are not allowed .
Read the thread and decide for yourself .
Click to expand...
Click to collapse
Boeffla kernel is constantly mentioned in the thread, I just need someone to give me some guidance on the settings?
Bluebutter said:
Boeffla kernel is constantly mentioned in the thread, I just need someone to give me some guidance on the settings?
Click to expand...
Click to collapse
You decide what you want or leave at default .