Hello guys. I'm a noob and i want to learn xD
I guess this is what XDA is all about
Would Someone explain what a kernel really is?
I know its the backend of the phone that processes.
The question is what do the custom kernels do?
What's different than the stock kernel ?
Waiting for an answer
Thanks
Sent from my GT-S5360 using xda app-developers app
Kernel is the commander of phone..
Btw stock kernel is limited it has deafult features like- 2 cpu frequency,no i/o scheduler some governors.
And in other hands custom kernel has lot more features like many cpu frequency to chose,many cpu governors,i/o scheduler,init.d support for using tweak. They are bettery saver.. There is some custom kernel which can also overclock your cpu.. Like merruk 2.5 kernel is 1.25 GHZ!!!!
there is more fetures in a custom kernel than stock kernel..
custom kernel has too many benifits btw...
some custom kernels-
White kernel
Merruk kernel
Savie kernel
Kuro kernel
Hells_fusion
Repencis kernel
So that means if i install a custom kernel it will overclock my processor....?
Sent from my GT-S5360 using xda app-developers app
as of now only merruk can overclock ur proccessor...
U..Y U NO PRESS THAT THANKS BUTTON IF I HELPED U >.<
prashantj95 said:
So that means if i install a custom kernel it will overclock my processor....?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Not really we don't have true over clock yet - but you can try merruk !
Customs Kernels are lot more than being able to change min and max frequencies the thing is i don't have much know how so I'll leave it to any other knowledgeable person reading this thread to answer you precisely
By the way you could have found all that you wanted and even more by spending a minute or two searching no offense
a plus b the whole square is equal to a square plus two ab plus b square
nikufellow said:
Not really we don't have true over clock yet - but you can try merruk !
Customs Kernels are lot more than being able to change min and max frequencies the thing is i don't have much know how so I'll leave it to any other knowledgeable person reading this thread to answer you precisely
By the way you could have found all that you wanted and even more by spending a minute or two searching no offense
a plus b the whole square is equal to a square plus two ab plus b square
Click to expand...
Click to collapse
This XDA app isn't very user friendly
X(
Search doesn't work for me.
Sent from my GT-S5360 using xda app-developers app
Xda is about open-source knowledge sharing,
Basically a kernel is the one that tells your device what to do and what are process needed to execute it
--------------------------------------------------------------
By staring at this post you have waived your right to privacy
Complaints will be trolled accordingly
prashantj95 said:
This XDA app isn't very user friendly
X(
Search doesn't work for me.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
No problem i was just saying
a plus b the whole square is equal to a square plus two ab plus b square
u want tol learn xda...
then learn the first thing..
when someone helps u...
press thanx button...
**rooting is new for me...and i am noob to root...**
nikufellow said:
Not really we don't have true over clock yet - but you can try merruk !
Click to expand...
Click to collapse
Overclock works. Not perfectly but works obviously.. Even the 900mhz overclocked kernel by merruk works for me.. U can feel it when your phone become warmer..
prashantj95 said:
So that means if i install a custom kernel it will overclock my processor....?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Just put Samsung galaxy y s5360 in front of all your searches
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
Basically if i would have to explain what kernel is all about..
Den i would say,
If ur smartfone is a Mercedes then ur kernel is engine.!
Lol
Sent from my GT-S6102 using xda premium
What is a kernel? If you spend any
time reading Android forums,
blogs, how-to posts or online
discussion you'll soon hear people
talking about the kernel. A kernel
isn't something unique to Android
-- iOS and MacOS have one,
Windows has one, BlackBerry's
QNX has one, in fact all high level
operating systems have one. The
one we're interested in is Linux, as
it's the one Android uses. Let's try
to break down what it is and what
it does.
Android devices use the Linux
kernel, but it's not the exact same
kernel other Linux-based
operating systems use. There's a
lot of Android specific code built
in, and Google's Android kernel
maintainers have their work cut
out for them. OEMs have to
contribute as well, because they
need to develop hardware drivers
for the parts they're using for the
kernel version they're using. This
is why it takes a while for
independent Android developers
and hackers to port new versions
to older devices and get
everything working. Drivers
written to work with the
Gingerbread kernel on a phone
won't necessarily work with the Ice
Cream Sandwich kernel. And
that's important, because one of
the kernel's main functions is to
control the hardware. It's a whole
lot of source code, with more
options while building it than you
can imagine, but in the end it's
just the intermediary between the
hardware and the software.
When software needs the
hardware to do anything, it sends
a request to the kernel. And when
we say anything , we mean anything.
From the brightness of the
screen, to the volume level, to
initiating a call through the radio,
even what's drawn on the display
is ultimately controlled by the
kernel. For example -- when you
tap the search button on your
phone, you tell the software to
open the search application. What
happens is that you touched a
certain point on the digitizer,
which tells the software that
you've touched the screen at
those coordinates. The software
knows that when that particular
spot is touched, the search dialog
is supposed to open. The kernel
is what tells the digitizer to look
(or listen, events are "listened"
for) for touches, helps figure out
where you touched, and tells the
system you touched it. In turn,
when the system receives a touch
event at a specific point from the
kernel (through the driver) it
knows what to draw on your
screen. Both the hardware and
the software communicate both
ways with the kernel, and that's
how your phone knows when to do
something. Input from one side is
sent as output to the other,
whether it's you playing Angry
Birds, or connecting to your car's
Bluetooth.
It sounds complicated, and it is.
But it's also pretty standard
computer logic -- there's an action
of some sort generated for every
event. Without the kernel to
accept and send information,
developers would have to write
code for every single event for
every single piece of hardware in
your device. With the kernel, all
they have to do is communicate
with it through the Android system
API's, and hardware developers
only have to make the device
hardware communicate with the
kernel. The good thing is that you
don't need to know exactly how or
why the kernel does what it does,
just understanding that it's the
go-between from software to
hardware gives you a pretty good
grasp of what's happening under
the glass. Sort of gives a whole
new outlook towards those fellows
who stay up all night to work on
kernels for your phone, doesn't
it?
:screwy:
Sent from my GT-S5360 using xda app-developers app
Cool.yash17 said:
What is a kernel? If you spend any
time reading Android forums,
blogs, how-to posts or online
discussion you'll soon hear people
talking about the kernel. A kernel
isn't something unique to Android
-- iOS and MacOS have one,
Windows has one, BlackBerry's
QNX has one, in fact all high level
operating systems have one. The
one we're interested in is Linux, as
it's the one Android uses. Let's try
to break down what it is and what
it does.
Android devices use the Linux
kernel, but it's not the exact same
kernel other Linux-based
operating systems use. There's a
lot of Android specific code built
in, and Google's Android kernel
maintainers have their work cut
out for them. OEMs have to
contribute as well, because they
need to develop hardware drivers
for the parts they're using for the
kernel version they're using. This
is why it takes a while for
independent Android developers
and hackers to port new versions
to older devices and get
everything working. Drivers
written to work with the
Gingerbread kernel on a phone
won't necessarily work with the Ice
Cream Sandwich kernel. And
that's important, because one of
the kernel's main functions is to
control the hardware. It's a whole
lot of source code, with more
options while building it than you
can imagine, but in the end it's
just the intermediary between the
hardware and the software.
When software needs the
hardware to do anything, it sends
a request to the kernel. And when
we say anything , we mean anything.
From the brightness of the
screen, to the volume level, to
initiating a call through the radio,
even what's drawn on the display
is ultimately controlled by the
kernel. For example -- when you
tap the search button on your
phone, you tell the software to
open the search application. What
happens is that you touched a
certain point on the digitizer,
which tells the software that
you've touched the screen at
those coordinates. The software
knows that when that particular
spot is touched, the search dialog
is supposed to open. The kernel
is what tells the digitizer to look
(or listen, events are "listened"
for) for touches, helps figure out
where you touched, and tells the
system you touched it. In turn,
when the system receives a touch
event at a specific point from the
kernel (through the driver) it
knows what to draw on your
screen. Both the hardware and
the software communicate both
ways with the kernel, and that's
how your phone knows when to do
something. Input from one side is
sent as output to the other,
whether it's you playing Angry
Birds, or connecting to your car's
Bluetooth.
It sounds complicated, and it is.
But it's also pretty standard
computer logic -- there's an action
of some sort generated for every
event. Without the kernel to
accept and send information,
developers would have to write
code for every single event for
every single piece of hardware in
your device. With the kernel, all
they have to do is communicate
with it through the Android system
API's, and hardware developers
only have to make the device
hardware communicate with the
kernel. The good thing is that you
don't need to know exactly how or
why the kernel does what it does,
just understanding that it's the
go-between from software to
hardware gives you a pretty good
grasp of what's happening under
the glass. Sort of gives a whole
new outlook towards those fellows
who stay up all night to work on
kernels for your phone, doesn't
it?
:screwy:
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
So it's basically divides the software developer and hardware developer's work.
One more question though.
If my hardware is limited., assuming OEMs made a driver for every hardware, what do these custom kernels offer, different from OEMs kernel.
Thanks for the help bro.
Sent from my GT-S5360 using xda app-developers app
Dude Custom kernels
Help You In Power Consumption
Overclocking .
More Perfomane Etc
Dont Forget To Press Thanks
Sent from my GT-S5360 using xda app-developers app
this is the best answer evah!
CLICK HERE
prashantj95 said:
So that means if i install a custom kernel it will overclock my processor....?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
means u can increase frequencies from 832mhz upto 1.2ghz but it will consume more battry
Related
*Disclaimer*
This is not my work and I am just posting it here in case some of you are interested. I take no responsibility for any problems on your phone. Don't expect any support from me.
**NOT TESTED BY MYSELF**
This kernel is for ICS, made in China.
Basically a 420MB RAM is the only difference from other kernel (although it's a big one).
Not working:
-Video recording
-HW decoding
-Camera FC when changing resolution (seems to be a problem on every ICS ROM)
Working:
Everything else
Original thread:
http://bbs.lidroid.com/forum.php?mod=viewthread&tid=102046
Downloads: http://code.google.com/p/all-roms/downloads/list
The original thread says that the developer tested it with CM9 and AOKP builds.
Have fun!!
Sent from my GT-I9000 using XDA
OMFG this kernel is AWESOME!!
Working great here!
EDIT:
Gameloft games don't work couse they use a HW decoded Gameloft logo movie at the beginning so the phone restarts.
What about building a new kernel like this one but... In english ?
My assumption that this would be:
The ramdisk or whatever it called has been modified, i have heard this before with my Nexus S, its so called : BIGMEM...
Sent from my Nexus S using Tapatalk 2 Beta-4
Is this based on platypus? Or did he only took the updater-script of it?
This should be placed in SGS development!
I won't post it in development as I didn't do any. (And I don't know how to!)
Just hoping that some devs see it and get interested?
Sent from my GT-I9000 using XDA
Not a lot of people come here... Hope they notice it? lol
nice
tried on Dark knight.
work very well. but camcorder fc.
interesting
Isn't part of the RAM required by the gpu? Maybe that's why it has hardware decoding issues??
We normally get 340Mb Ram with bigmem kernel (break HD record), he disable the MFC in http://pastebin.com/f5ytsipx so the kernel reclaim 70Mb from video HW decoding, so the kernel got 420Mb, but it's not the way to do things, probally will never get into out mainline kernel
Uuh, if there only was a way to keep HW decoding AND get 420 mb! My SGS sure could use extra 70mb, 330 is just NOT ENOUGH for Android.
Wow, I would love to try it if it were a gingerbread (stock) kernel .
If people want to use multiple kernels, it probably only takes a minute to flash an alternate kernel and reboot your device. that way you get the best of both worlds (but admittedly it is not the best solution).
I just went and read about the thread since I can read chinese lol
The dev there said he based his kernel on this guy https://github.com/ngiordano/ics_3.1.10
and Funnnny was correct, he disabled the MFC so that android can reclaim the reserved ram from that unit, which is about 70MB. But this breaks hardware video decoding and camcorder.....
But he made a compensation in the recovery so that when you need camcorder you can reboot and flash standard kernel, when you don't need it, you can flash back to the huge ram kernel....
dunno if that's useful....
Oh but can't play any games. Giving fc. I'm very interested! If you can override videos in game, you can play. Lets find a way to fix it. Think think rhink
Sent from my GT-I9000 using Tapatalk 2 Beta-4
Very interesting! How long have users complained "Where is our 512mb???" etc etc lol.
Is it just me or does dedicated RAM seem not necessary? Maybe it is possible to remap video/gpu/camera or whatever to shared RAM?
+1 oswade.
btw,which one to download??:there's one named i9000 and another t959 kernel panic fixed.
edit:well I downloaded the i9000 one. .it feels good to see 240 mb free ram on the info screen.
hope some developer further develops this idea.
oswade said:
Very interesting! How long have users complained "Where is our 512mb???" etc etc lol.
Is it just me or does dedicated RAM seem not necessary? Maybe it is possible to remap video/gpu/camera or whatever to shared RAM?
Click to expand...
Click to collapse
Dedicated RAM isn't necessary of course, but the Exynos SoC have MFC module that expect to use the Ram at a specific address, so the kernel can't touch it (known as reservation).
We can't just take the reserved Ram and use it, because next time when the module need it, it'll only use the Ram at the address it knows, and bang, the phone rebooted like the kernel in OP.
This is not just bad design at software level, maybe bad hardware design too, but I'm not system expert so I can't say anything here, but Exynos is a cool SoC and we should live on with this.
burakgon said:
Oh but can't play any games. Giving fc.
Click to expand...
Click to collapse
I've tried:
Dead Space
Andry Birds
Reckless Getaway
Hot Springs Story
They does work.
SPY mouse restarts the phone. I guess, it has a video in it.
Anyway, this kernel is rather interesting. I do hope that devs would find a way to trick SGS to play HD videos in software mode to avoid reboots. This way we'll have 70mb extra ram and won't lose anything - even if those videos would lag - who cares?
Also tried this kernel on ics slim and it feels good to have such ammount of free ram.
I also run dead space and reckless racing without any problems.Im assuming gameloft games wont run because they have always a video introducing the game.I just wish someone could break the video aceleration even if we had to loose lets say 20 mb of ram.Still would be very usefull.Ive posted in the stratosk kernel thread about this to see if he is interested on modify this kernel and make it even better
Some guys found a huge optimization for Linux kernel and Dalvik as well on ARM platforms. Actually it is not made by optimizing the code, but by the way GCC compiles, and it increased the performances from 30% to 100%. There is a little video of them running a benchmark on two Android development platforms, the two development platforms are the same. Here it is :
So the ROM used is the same used by the Galaxy Nexus, and Cyanogen Mod now uses it to gain these 30%~100%. What are your feelings about it ? Are you pessimistic, optimistic about the implementation for example for stock Atrix ROMs ? Or community ROMs maybe ? Also tell us if you have some news about it.
So this optimization was made mainly for the Linux kernel on ARM devices, which means it will be way more efficient on ARM computers/servers. This is a great step forward for Linux on embedded platforms. They also worked on Dalvik, so now even Android apps will run faster.
(Sorry for my grammar if I made some mistakes, just tell me I'll correct them.)
Very impressive performance increase. Looking forward to seeing these optimizations make there way into custom roms.
Can you post more info about how this works? Or a link to the original GCC discovery?
Linaro is a hot topic in the Samsung forums. Even the OG SGS (basically half the specs of the Atrix) users are begging support for it...
Sent from my MB860 using XDA Premium App
It will be implemented in the aokp #39 release.
Inviato dal mio Atrix con Tapatalk
AkaGrey said:
It will be implemented in the aokp #39 release.
Inviato dal mio Atrix con Tapatalk
Click to expand...
Click to collapse
how do you know that???
facuxt said:
how do you know that???
Click to expand...
Click to collapse
http://www.droid-life.com/2012/06/1...stem-performance-boosts-are-quite-noticeable/
Sent from my MB860 CM7.2 RC3 36p Radio
It seems it is not easy to get this to work on every CM device. Some people report issues with this patch: http://r.cyanogenmod.com/#/c/17535/
v.k said:
It seems it is not easy to get this to work on every CM device. Some people report issues with this patch: http://r.cyanogenmod.com/#/c/17535/
Click to expand...
Click to collapse
It may not be easy, but I got a feeling that many people from CM teams everywhere are gonna work round the clock to get this to work on their devices.
I'm definitely not a "benchmark guy", and generally shrug off those topics, but even I was blown away after watching this video...
Sent from my MB860 using XDA Premium App
Wow. Awesome!
Imagine that guy talking one on one with a girl though......
Sent from my MB860 using XDA
rancur3p1c said:
Can you post more info about how this works? Or a link to the original GCC discovery?
Click to expand...
Click to collapse
Well all is about the compilation, they didn't change the code but the way GCC compiles it, it is now optimized for the ARM instruction set. So, why wasn't it optimized before the "discover" ? Well I think they didn't take enough time on build optimization when they made GCC working with ARM. First it was made for x86, x64 etc. These are other instruction set, another list of commands the CPU is able to work with. Imagine the instruction sets like different languages. x64, the first one, has a rich vocabulary, and ARM the second one has a more restricted vocabulary but the two languages have the same syntax. The difference will be that you will need to use more words with ARM than with x64 to describe something complex, so now it has to be optimized to use the fewer words possible to be faster. And that's basically what the Linaro Team did.
So the optimization has been used for the Android System (Linux kernel + Dalvik, etc.) but it can also be used for any other ARM program. This is a great step forward also for ARM computers, and maybe ARM servers that will continue to use less energy for bigger tasks because of the optimization.
Slymayer said:
Well all is about the compilation, they didn't change the code but the way GCC compiles it, it is now optimized for the ARM instruction set. So, why wasn't it optimized before the "discover" ? Well I think they didn't take enough time on build optimization when they made GCC working with ARM. First it was made for x86, x64 etc. These are other instruction set, another list of commands the CPU is able to work with. Imagine the instruction sets like different languages. x64, the first one, has a rich vocabulary, and ARM the second one has a more restricted vocabulary but the two languages have the same syntax. The difference will be that you will need to use more words with ARM than with x64 to describe something complex, so now it has to be optimized to use the fewer words possible to be faster. And that's basically what the Linaro Team did.
So the optimization has been used for the Android System (Linux kernel + Dalvik, etc.) but it can also be used for any other ARM program. This is a great step forward also for ARM computers, and maybe ARM servers that will continue to use less energy for bigger tasks because of the optimization.
Click to expand...
Click to collapse
You lost me at compilation...lol
Sent from my MB860 using XDA
So they found a way to optimize compilation for arm architecture yielding massive performance boosts over current standards.. do want =D
These dudes rock.
Sent from my MB860 using XDA
michaelatrix said:
You lost me at compilation...lol
Sent from my MB860 using XDA
Click to expand...
Click to collapse
They found a way to talk to the system by saying less. Like if I would say to you, " hello, how are things in your life" but now I say, "how's things" and you understand both phrases mean the same thing. You get to the conclusion faster because you process less information but reached the same outcome. It takes less processing for the shorter phrase and improves overall response time.
Sent from my MB860 using xda premium
i don't think it'll be easy to use it for our beloved atrix, the linaro code uses a 3.2 kernel, and we're still stuck on the crappy froyo 2.6.32 kernel =/
So I've got some time at the moment to work on the vibrant again, so I figured I'd ask you guys a question.
What are you guys wanting out of the vibrant?
I'm not really one to go for the latest and greatest buzz word feature like "Linaro build" or "optimized build prop," etc.
lengthy posts are encouraged, tell me what you still want out of this device. What do you use it for? What do you want to use it for? Etc.
Like I said, not looking for "gimme 500MB ram" or " an updated 2.3 kernel", I wanna know what user experience your looking for.
Sent from my Galaxy Nexus using Tapatalk 2
No takers?
Sent from my Galaxy Nexus using Tapatalk 2
Now we have almost faultless ROMs and kernels, the only issue is GPS.
+1 on GPS
lorendroll said:
Now we have almost faultless ROMs and kernels, the only issue is GPS.
Click to expand...
Click to collapse
Point if the question was missed, it's not about faults. Also there are very talented individuals working on the GPS issues. I cannot test GPS as mine no longer works. I want to know not just for me but also the talented Devs working on the vibrant, what ideas do you guys have for improving the Android experience, just in this case I happen to be gearing it toward the vibrant as I won't be working in anything else myself. That doesn't mean it's faulty, there is always room for improvement.
Anyway...not monitoring this thread anymore....Idgaf anymore and people not gonna answer :3
Sent from my Galaxy Nexus using Tapatalk 2
ECOTOX,
Just in case you do monitor this thread Ill give you a request. Ive built a couple of Froyo ROMs now, and plan to stick with Froyo for some time (at least until the EU error fixed)
That said I usually package the Bali 18.8.UV kernel with them. My favorite Froyo kernel is the DMZ kernel.
http://rootzwiki.com/topic/633-kernel2213ghzdragonmodz-nightly3smartassscary8262011140pm/
What set your work apart is the fact it could stepclimp in 100mhz increments. My phone pukes at anything over 1100mhz. Its has the smartass governor (the one I want) that works perfectly. It is smooth, quick, and almost perfect for my needs. Ive only packaged it with one of my ROMs due to the lack to stepclimbing. Here is a request:
Ive tried up to 3 different overclock / volting programs. Tried to set it manually via init script, but the kernel has 2 stock settings: 500mhz / 1000mhz. If I I overclock to 1100mhz I only get three settings: 500/1000/1100. Is there any way you could get a 200mhz in there?
That said your git is available. I don't know how but I guess I could try and build my own based off your source / patches. You kinda sounded like you wanted to help/work some on the T959. With the EU error we have more folks coming back to Froyo every day. Froyo is not dead if I have anything to say about it -
Thanks for your time (I if read this)
+1 on GPS
Sent from my SGH-T959 using xda premium
GPS is primarily due to inadequate or faulty hardware design. We have pushed the limits of trying to fix it with software guys.
I personally would love more battery life. I truly cannot get more than 45 minutes of screen time in ICS.
Sent from my SGH-T959 using XDA
How about intergrating more RAM?
Sent from my SGH-T959 using xda premium
Moped_Ryder said:
ECOTOX,
Just in case you do monitor this thread Ill give you a request. Ive built a couple of Froyo ROMs now, and plan to stick with Froyo for some time (at least until the EU error fixed)
That said I usually package the Bali 18.8.UV kernel with them. My favorite Froyo kernel is the DMZ kernel.
http://rootzwiki.com/topic/633-kernel2213ghzdragonmodz-nightly3smartassscary8262011140pm/
What set your work apart is the fact it could stepclimp in 100mhz increments. My phone pukes at anything over 1100mhz. Its has the smartass governor (the one I want) that works perfectly. It is smooth, quick, and almost perfect for my needs. Ive only packaged it with one of my ROMs due to the lack to stepclimbing. Here is a request:
Ive tried up to 3 different overclock / volting programs. Tried to set it manually via init script, but the kernel has 2 stock settings: 500mhz / 1000mhz. If I I overclock to 1100mhz I only get three settings: 500/1000/1100. Is there any way you could get a 200mhz in there?
That said your git is available. I don't know how but I guess I could try and build my own based off your source / patches. You kinda sounded like you wanted to help/work some on the T959. With the EU error we have more folks coming back to Froyo every day. Froyo is not dead if I have anything to say about it -
Thanks for your time (I if read this)
Click to expand...
Click to collapse
Lol happened to be browsing the forum for info and saw you posted here.
I'll make you a kernel, but I'm not 100%sure I'm sticking with the 100mhz steps for my own release but I'll make you one specifically. I might, but I want to get voltage control working with 100mhz steps, I also gotta work on keeping the gpu clocks more stable.
Sent from my Galaxy Nexus using Tapatalk 2
I would be in your debt sir. Thanks for your time.
I just wanted to say thanks for the great work on DMZ, ECOTOX. It has surpassed Overstock as my kernel of choice, but I had one quick question/request. Is it an issue with the kernel or with a particular ROM for some functions to get a little quirky when you start to overclock into the 1.2Ghz range? Whenever I set the CPU ceiling to 1.2Ghz the long press functions on the haptic buttons of the Vibrant would become flakey. I read that's fairly common with overclocking, but was curious who the culprit might be.
Not knowing anything about how scalers/governers can be implemented, what would the chances be to get something like Smartass v2 or a few more options on a new Froyo kernel? I liked messing around with them when I was running Sub-Zero on ICZen to find that happy medium of battery life vs performance.
I say a Galaxy S III themed gingerbread ROM. Anyone?
Here is the best kernel for stock based x10 roms.
n5-1 http://www.mediafire.com/?z8voe760ok24doy
ALL THANKS TO THJAP
You don't know what you've been missing! This is for locked bootloaders so flash it with xrecovery. For unlocked bootloaders flash baseband .71 with flashtool first which also gives you the stock kernel. Then you can flash this kernel through recovery.
Sent from my X10i using xda premium
Features?
Farik335 said:
Features?
Click to expand...
Click to collapse
Im not even sure whats different about this one over others. All I know is its way better than any other I've tryed.
Sent from my X10i using xda premium
There is no such thing as a "Best kernel"! it grealty depends on what rom you're using, which settings you apply, ram, number of apps, cpu frequencies, governors and i/o scheduler. It also greatly differs per phone!!!!!
This one doesnt work on jaf rom!
It makes my phone to stuck at bootscreen!
And after flashing back to dooms kernel,everything is lagging,so i had to restore a backup!really a great kernel!
After flashing this My phone speed is like flashing the new Adreno ICS Driver its really slow
OK OK OK
I know benchmarks don't mean anything to you guys.
Sent from my X10i using xda premium
Deleted!!!
JeffreyPiket said:
Read this and weep!!!!!
Click to expand...
Click to collapse
Man. I thought that would spark a reaction.
Sent from my X10i using xda premium
tonyreimer said:
OK OK OK
I know benchmarks don't mean anything to you guys.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Read it and weep!!!!!
Dani897 said:
benchmarks are basically useless to the end user. fun to compare but dont think about it too much. a benchmark like quadrant can show a low score based on one area of poor performance but there is no guarantee that that will cause a bottleneck for data. it can also generate a high score based on one area and there is no proof that it is benificial. for instance we use voodoo lagfix that increases filesystem io according to the method quadrant usses to measure it by a fairly significant amount. it has never been proven to reduce hesitation of the phone outside of perception of the user, it is a good mod and i dont knock it im just trying to be objective. the thing is that data goes throught many componants and is held in ram and cached on the cpu, as long as the useage is light the file system performance is barely an issue because there are several systems that act as buffers, only when processing long sets of data uninterupted will the certain speeds become a bottleneck.
for a good analogy it is like drinking through a straw vs drinking through a hose vs drinking through a 1ft diameter pipe. the straw may slow the speed you can drink while the hose will not, but the pipe can supply much more water yet it is of no benifit to the person drinking because he can only drink so fast.
add cacheing into the analogy and it is like filling a glass through a straw a pipe and a hose. the glass can supply the person drinking as fast as they need it, but only holds so much liquid, it is enough in for on person but if several people want to drink (multi tasking or heavy usage) the staw will be a bottle neck, the hose will not and the pipe though overkill may make things marginally faster. now if there is alot of caheing it may be more like filling buckets and then the pipe may help but only when there is an enormous amount of data being used and in that case it needs to be processed just as fast, this is when the cpu can become a bottle neck.
it is very difficult to write a benchmark that can take this into account so it is hard to tell the usefullness of the data the benchmark gives you without reading the results of the individual tests it performs and making judgment calls.
we can increase our benchmark scores for filesystem by changing the filesystem to ext4, and even better by going with nilfs or nilfs2. we can increase sequencial reads by increasing readahead but that reduces random performance and waists resources. it all becomes a big balancing act and the end results can vary.
there are also ways to change the ram timing, the dalvik cache heap size, alter the ram disks, we can make the rom smaller and remove stock apps that are not needed, turn off background services that use resources, change polling frequencies to save resources, change governors to ramp up faster, alter and compile drivers for more efficient use of hardware, and a long list of other things. some work extremely well, some don't. some will make the phone snappier and have no effect on benchmarks, some will greatly increase benchmarks and not the feel of the phone.
Click to expand...
Click to collapse
:highfive:
Check out the 2d and 3d on the bottom of the top screen shot. I challenge you to get that good on both of them with any other kernel on our old x10.
Sent from my X10i using xda premium
tonyreimer said:
Check out the 2d and 3d on the bottom of the top screen shot. I challenge you to get that good on both of them with any other kernel on our old x10.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
No Comment... don't feel offended.. but
Did you read anything from the text Jeffrey posted?
You, well not you, but any good Dev can tweak a kernel and rom, to be good in Benchmarks.. while the general User Experience just plain sucks..
And to be honest, almost every ICS Rom with a somewhat decent optimized Kernel, has more 2D and 3D points than your screenshot.. i don't even need to post proof. it's a fact, even with the Xperia X10.
And there is no such thing as a best kernel...
Depending on the user, every Kernel has it dis-/advantages..
And thats why i think it's good for your ROM to support multiple Kernels, a thing many dev's are still missing, because when you have multiple Kernels, every user can use the Kernel best suited for his needs.
Tekkpriest said:
No Comment... don't feel offended.. but
Did you read anything from the text Jeffrey posted?
You, well not you, but any good Dev can tweak a kernel and rom, to be good in Benchmarks.. while the general User Experience just plain sucks..
And to be honest, almost every ICS Rom with a somewhat decent optimized Kernel, has more 2D and 3D points than your screenshot.. i don't even need to post proof. it's a fact, even with the Xperia X10.
And there is no such thing as a best kernel...
Depending on the user, every Kernel has it dis-/advantages..
And thats why i think it's good for your ROM to support multiple Kernels, a thing many dev's are still missing, because when you have multiple Kernels, every user can use the Kernel best suited for his needs.
Click to expand...
Click to collapse
Ya, I read it. I haven't tryed ics yet cause i use my phone as my internet connection. OK thats fine. I don't really care if not anyone else uses this kernel but as for me its the best one I've ever had. Peace
Sent from my X10i using xda premium
:silly: That's all!
etedeni fhall
JeffreyPiket said:
There is no such thing as a "Best kernel"! it grealty depends on what rom you're using, which settings you apply, ram, number of apps, cpu frequencies, governors and i/o scheduler. It also greatly differs per phone!!!!!
Click to expand...
Click to collapse
Totally agree with this post
Can any one guide me thru the best setting for smooth scrolling.
While using facebook for example, the scrolling up and down is not smooth.
It lags.
Currently on pacman powered by franco m3.
Sent from my Nexus 4
faddyie said:
Can any one guide me thru the best setting for smooth scrolling.
While using facebook for example, the scrolling up and down is not smooth.
It lags.
Currently on pacman powered by franco m3.
Sent from my Nexus 4
Click to expand...
Click to collapse
the facebook app just sucks.
try using the force gpu rendering option in developer options in the phones main settings.
Try Faux123's latest kernel. While there may be no true cure for stuttery apps like Facebook, it almost goes away.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
faddyie said:
Can any one guide me thru the best setting for smooth scrolling.
While using facebook for example, the scrolling up and down is not smooth.
It lags.
Currently on pacman powered by franco m3.
Sent from my Nexus 4
Click to expand...
Click to collapse
Just use the mobile facebook site. It is much better and its practically the FB app.
Just create a shortcut on your launcher to m.facebook.com
ShinnAsuka said:
Just use the mobile facebook site. It is much better and its practically the FB app.
Just create a shortcut on your launcher to m.facebook.com
Click to expand...
Click to collapse
truth
simms22 said:
the facebook app just sucks.
try using the force gpu rendering option in developer options in the phones main settings.
Click to expand...
Click to collapse
What exactly is force GPU rendering their for ?
Also does it effect battery or anything etc
Sent from my Nexus 4 using xda premium
myturbo1 said:
What exactly is force GPU rendering their for ?
Also does it effect battery or anything etc
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
some apps still use software rendering, this forces them to use the hardware to render. this generally will give you a better experience. more battery.. no, not really.
You can use another governor like "interactive" to get more smoothness.
While some apps aren't as well written as they should be, and Android isn't quite capable of perfectly fluid and hiccup-free performance just yet, use a kernel that doesn't do the ridiculous thing of disabling MPDecision, which is a part of project butter that many kernel developers pretentiously disable, thinking that they're more capable than google+qualcomm. Funny thing is, contrary to general belief, your phone will even heat up less.
SetiroN said:
While some apps aren't as well written as they should be, and Android isn't quite capable of perfectly fluid and hiccup-free performance just yet, use a kernel that doesn't do the ridiculous thing of disabling MPDecision, which is a part of project butter that many kernel developers pretentiously disable, thinking that they're more capable than google+qualcomm. Funny thing is, contrary to general belief, your phone will even heat up less.
Click to expand...
Click to collapse
That`s total BS! MPDecision= Little smoothness at high price! Hot-plugging is wayyyy better than MPDecision! Less heat!? MAybe if your phone is idling but not if you`re using it!
SetiroN said:
While some apps aren't as well written as they should be, and Android isn't quite capable of perfectly fluid and hiccup-free performance just yet, use a kernel that doesn't do the ridiculous thing of disabling MPDecision, which is a part of project butter that many kernel developers pretentiously disable, thinking that they're more capable than google+qualcomm. Funny thing is, contrary to general belief, your phone will even heat up less.
Click to expand...
Click to collapse
I am also inclined to believe the opposite here man.. mpdecition has been around and used before project butter and Jelly Bean
. It literally sets your min freq to over 1 gigahertz just on a touch. Creates a lot of heat when turned on. Devs like faux who have building kernels for multiple devices for multiple years do know what their doing.
Sent from my Nexus 4 using xda app-developers app
Yeah well, believe what you want to believe, it's not my job to change your mind.
I did my own testing rather than believing and came to my own conclusions; I could take 30 minutes to explain the actual behaviour of MPdecision compared to those hand written hotplug drivers, but I really have no interest in trying to convince anyone who's happy with their beliefs.
OP was asking for advice on how to make his device smoother (without even mentioning heat or power consumption) and I gave it to him. I'm happier with MPDecision, maybe he'll be as well; I don't really want to start a discussion with whom is already satisfied otherwise.
SetiroN said:
Yeah well, believe what you want to believe, it's not my job to change your mind.
I did my own testing rather than believing and came to my own conclusions; I could take 30 minutes to explain the actual behaviour of MPdecision compared to those hand written hotplug drivers, but I really have no interest in trying to convince anyone who's happy with their beliefs.
OP was asking for advice on how to make his device smoother (without even mentioning heat or power consumption) and I gave it to him. I'm happier with MPDecision, maybe he'll be as well; I don't really want to start a discussion with whom is already satisfied otherwise.
Click to expand...
Click to collapse
That was quite elaborative... I am also with mp decision might be... Coz on stock i dont know how but feel much smoothness rather than custom.
This might be might be coz i am not that much techy to tweak further the custom kernel. I run with default values of any custom kernel... Learning: wip. lolx
Sent from my Nexus 4
SetiroN said:
Yeah well, believe what you want to believe, it's not my job to change your mind.
I did my own testing rather than believing and came to my own conclusions; I could take 30 minutes to explain the actual behaviour of MPdecision compared to those hand written hotplug drivers, but I really have no interest in trying to convince anyone who's happy with their beliefs.
OP was asking for advice on how to make his device smoother (without even mentioning heat or power consumption) and I gave it to him. I'm happier with MPDecision, maybe he'll be as well; I don't really want to start a discussion with whom is already satisfied otherwise.
Click to expand...
Click to collapse
And yes im confident your testing and knowledge goes beyond devs who have been building longer than you've been on XDA.. :thumbup:
Sent from my Nexus 4 using xda app-developers app
Mokee os/sabermod + franko kernel linaro..
PJcastaldo said:
And yes im confident your testing and knowledge goes beyond devs who have been building longer than you've been on XDA.. :thumbup:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Not all devs dropped mpdecision.
PJcastaldo said:
And yes im confident your testing and knowledge goes beyond devs who have been building longer than you've been on XDA.. :thumbup:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Again, I really don't care what you think.
Confide in whatever you wish, you're free to trust people whoring for donations as much as you want.
I'll keep compiling and testing things myself without giving a crap.
SetiroN said:
Again, I really don't care what you think.
Confide in whatever you wish, you're free to trust people whoring for donations as much as you want.
I'll keep compiling and testing things myself without giving a crap.
Click to expand...
Click to collapse
i think "whoring" is overstepping. kernel devs such as franco and faux certainly aren't in it for the donations. they're just geeky enthusiasts like the rest of us, in it for the fun.
i think OP's problem is likely related (as others have mentioned) to poorly coded apps rather than rom/kernel.
namurt said:
i think OP's problem is likely related (as others have mentioned) to poorly coded apps rather than rom/kernel.
Click to expand...
Click to collapse
1. In scrolling is there a role of FPS?
2. What is sampling rate in a kernel. Increasing sampling rate in ondemand governer can make some resolve to this prob?
namurt said:
i think "whoring" is overstepping. kernel devs such as franco and faux certainly aren't in it for the donations. they're just geeky enthusiasts like the rest of us, in it for the fun.
i think OP's problem is likely related (as others have mentioned) to poorly coded apps rather than rom/kernel.
Click to expand...
Click to collapse
hahahahaha
you really don't know who faux is