Hi everyone. I have been googling around for a way to extend my G Pad's battery life. On the way, I stumbled upon the Franco Kernel who many people consider the magical kernel to extend the device's battery life (some claiming even if you don't undervolt the CPU).
However, it appears that it is not working on the G Pad, atleast when I tried the franco installer on the playstore. I am using slimkat (which I believe is an AOSP... I have read somewhere that it works on AOSP devices, but though they didn't say which device, im leaning toward nexus only devices but im not sure).
Anyone tried and successfully installed this custom kernel? and on which ROM? Thanks
I thought Franco Kernel was exclusive to Nexus devices only? Where are you seeing that he has one for the G-Pad?
stevessvt said:
I thought Franco Kernel was exclusive to Nexus devices only? Where are you seeing that he has one for the G-Pad?
Click to expand...
Click to collapse
Not really. Actually on his installer application on google play the list of compatible devices are only the ones in the nexus line. But I do see in some threads for speeding up the android, franco often pops out. And since franco is compatible with AOSP custom ROMs, just figured, perhaps there might be a way to install this custom kernel on non-nexus devices with AOSP-based Custom ROM (i.e. Slimkat, or Pac-man ROM). But at the moment, im too scared to try it out on my own device because I just recently had it serviced for screwing up my partition table
Though I don't think custom kernels touch the existing partition table.
You need someone on here to port francos kernel over for our device.
But you can still use his app to alter certain settings, if his app is similar to fauxs and Trinitys.
Sent from my LG-V500 using XDA Premium HD app
whoamigriffiths said:
You need someone on here to port francos kernel over for our device.
But you can still use his app to alter certain settings, if his app is similar to fauxs and Trinitys.
Sent from my LG-V500 using XDA Premium HD app
Click to expand...
Click to collapse
I have heard of Faux's (his installer app in the playstore indicates that it unofficially supports other devices or something along those lines) but I had a keen interest in Franco's kernel because many has attested to its usefulness and that it saves quite a bit of battery life which the tablet could use.
Since there was a GPE version of the tablet, I was hoping they might port it aswell.
I guess kernels aren't like servers in the sense that, say for example in Linux, as it is based on x86, regardless of the CPU as long as its using the same x86 architecture, the kernel should be compatible. Following the same logic with Android which is essentially Linux which uses predominantly the ARM architecture, I was hoping that theoretically, the kernel will be compatible as they are using the same architecture... Although I can be wrong.
I would test it myself, but im afraid of bricking my device as I just hard-bricked it and lost quite a bit of my 9 lives... Dunno how many I have remaining
Hehe, it's not worth trying, as it wouldn't work. I'm not sure what would happen tbh. I don't think it would brick, I think it would just bootloop, but honestly it's not worth trying.
Have you looked at greenify?
It's great at what it does, but it is only saving battery during sleep. Mine is great in sleep, but it's not a vast saving of resources. Once you boot the tablet up you can literally watch the battery percentage ticking down
Sent from my LG-V500 using XDA Premium HD app
whoamigriffiths said:
Hehe, it's not worth trying, as it wouldn't work. I'm not sure what would happen tbh. I don't think it would brick, I think it would just bootloop, but honestly it's not worth trying.
Have you looked at greenify?
It's great at what it does, but it is only saving battery during sleep. Mine is great in sleep, but it's not a vast saving of resources. Once you boot the tablet up you can literally watch the battery percentage ticking down
Sent from my LG-V500 using XDA Premium HD app
Click to expand...
Click to collapse
hmm boot loop I can live with. I might just give it a try when I have the time and summoned enough courage. Yep I do have greenify and didn't do much in improving the battery life. But atleast I think it did something.
jarod004 said:
hmm boot loop I can live with. I might just give it a try when I have the time and summoned enough courage. Yep I do have greenify and didn't do much in improving the battery life. But atleast I think it did something.
Click to expand...
Click to collapse
in contrast to Linux distribution, our kernels are device specific as there are different drivers for different devices by different makers. On top of that, the ramdisk itself which is associated with the kernel to make a complete boot image, can have different mount points depending on the device.
You would think that all of this would be standard but of course with different makers of different phones, tablets, excetera, this just isn't the case.
Neither Franco's kernel, nor Faux kernel will work with the G pad. While I have done some work to port over different items from different kernels, I own the Google Play edition and not the stock LG tablet. Maybe one of the other kernel developers for the stock LG tablet would be open to porting over some of their work.
if you would like, you may also look in my signature for a guide on how to roll your own kernel for the G pad, and a couple of the other kernel developers have used it with success for your device. It is a complete guide start to finish, copy and paste style for anyone running Debian. check it out!
sleekmason said:
in contrast to Linux distribution, our kernels are device specific as there are different drivers for different devices by different makers. On top of that, the ramdisk itself which is associated with the kernel to make a complete boot image, can have different mount points depending on the device.
You would think that all of this would be standard but of course with different makers of different phones, tablets, excetera, this just isn't the case.
Neither Franco's kernel, nor Faux kernel will work with the G pad. While I have done some work to port over different items from different kernels, I own the Google Play edition and not the stock LG tablet. Maybe one of the other kernel developers for the stock LG tablet would be open to porting over some of their work.
if you would like, you may also look in my signature for a guide on how to roll your own kernel for the G pad, and a couple of the other kernel developers have used it with success for your device. It is a complete guide start to finish, copy and paste style for anyone running Debian. check it out!
Click to expand...
Click to collapse
Interesting stuff. Only little problem is I don't have a debian based machine currently (only using redhat based Linux ATM). Ill install Ubuntu on my "virtual lab" and see if I can try it when I have the time. Thanks a lot for your input.
jarod004 said:
Interesting stuff. Only little problem is I don't have a debian based machine currently (only using redhat based Linux ATM). Ill install Ubuntu on my "virtual lab" and see if I can try it when I have the time. Thanks a lot for your input.
Click to expand...
Click to collapse
No problem. I use AntiX, a Debian derivative and highly recommended it. You will find it far lighter, and with some really neat tools. Ubuntu is not all its cracked up to be...
sleekmason said:
No problem. I use AntiX, a Debian derivative and highly recommended it. You will find it far lighter, and with some really neat tools. Ubuntu is not all its cracked up to be...
Click to expand...
Click to collapse
its more like, its the debian distro I have lying around so I don't need to download anything else. fits the bill. Although I will take note of that AntiX
jarod004 said:
its more like, its the debian distro I have lying around so I don't need to download anything else. fits the bill. Although I will take note of that AntiX
Click to expand...
Click to collapse
If you use Ubuntu, you will have to adjust some of the dependencies, as they use their own packages. Unbuntu is a Debian derivative but is not compatible with the apt database. Let me know how it goes if you decide to do it!
sleekmason said:
If you use Ubuntu, you will have to adjust some of the dependencies, as they use their own packages. Unbuntu is a Debian derivative but is not compatible with the apt database. Let me know how it goes if you decide to do it!
Click to expand...
Click to collapse
I see. guess theres no harm in creating a new vm for this. Lemme google around for the installer and try it out when I get the time. Though I am quite loaded for this week and probably the next too
Related
I just wanted to start a discussion about kernels for our phone. Obviously the stock kernel for our phone is the .35 kernel. Before I traded in my EVO I was running the .38 kernel. I know that Linux was releasing new kernels every so often and the developers such as Toast would port them over and make them compatible with the EVO. I thought I read somewhere that Linux was not going to develop new kernels anymore, possibly someone could confirm that. So if thats the case what happens? Will android use the same kernels forever? What would be the possobility of our phones being able to use some of the newer kernel versions? As I write this Bybby323 is getting really close to having a fully functional AOSP kernel for our phones and I think development is really going to pick up. Maybe this will open the door for some different kernel versions for our phones.
All I know is that the Linux kernel isn't going to stop any time soon.
http://www.kernel.org/
Too many operating systems/devices (such as Android) use, or better yet, depend on the Linux kernel. Remember, it's an open source thing - not just one guy behind a desk. Many multi-million dollar companies use Linux for everything, from storing data to government websites and so on, they would be willing to invest if Linux needed money (this probably wouldn't happen, but you get me.)
In regards to ETAs, I have no clue. But just know that support for neither Android, or the Linux kernel isnt stopping anytime soon.
stangdriverdoug said:
I just wanted to start a discussion about kernels for our phone. Obviously the stock kernel for our phone is the .35 kernel. Before I traded in my EVO I was running the .38 kernel. I know that Linux was releasing new kernels every so often and the developers such as Toast would port them over and make them compatible with the EVO. I thought I read somewhere that Linux was not going to develop new kernels anymore, possibly someone could confirm that. So if thats the case what happens? Will android use the same kernels forever? What would be the possobility of our phones being able to use some of the newer kernel versions? As I write this Bybby323 is getting really close to having a fully functional AOSP kernel for our phones and I think development is really going to pick up. Maybe this will open the door for some different kernel versions for our phones.
Click to expand...
Click to collapse
the reason is Android 2.3 shipped with 2.6.35, similarly Android 2.1, 2.2, and 4.0 ship with 2.6.29,2.6.32,3.0 respectively.
I dont see the point in doing all of that work when ICS should ship on the GS2 soon with Linux 3.0
And no, Linux is far from dead
Sent from my SPH-D710 using xda premium
HI, i am new to this coming from iPhone..i have the AOKP rom for my atnt galaxy s3. I am wondering what is the deal with kernels? like what is the use of them? i am guessing the rom comes with it, but should i load the kernal like this one here:
http://forum.xda-developers.com/showthread.php?t=1756776
thanks
Kernals can change how the phone performs severely as well as add features. They can also affect battery life, speed, and how smooth your phone is.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thank you for asking, and thank you for answering. I was also wondering this and was about to start my search here.
ScudMuffin said:
Thank you for asking, and thank you for answering. I was also wondering this and was about to start my search here.
Click to expand...
Click to collapse
glad i am not the only one
crash822 said:
Kernals can change how the phone performs severely as well as add features. They can also affect battery life, speed, and how smooth your phone is.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
so for example since i am running the AOSP ICS rom, and there is AOSP kernel available for download, so i get that? and what is the order of installation? since i already have the rom installed and been using it
I suggest you stick to the kernel the rom's include until you understand fully what it is.
So to add to this, I learned many ROMs include a kernel. We don't always have to go out, install a ROM and a Kernel. In most cases it is if someone made some custom tweaks to a ROM kernel or stock kernel that you would reflash it. Please correct me if I'm wrong, still reading and learning.
To use a car analogy, I think of the phone hardware as the mechanical parts of the car, the ROM as the electrical system in a car and the kernel is the computer taking all the signals from the electrical system and telling the hardware what to do. Rooted ROMs can take advantage of connections already built into the phone but maybe turned off or disconnected in a stock ROM. Non-stock kernels can direct the traffic of electrical signals (like a stop light), change those signals, modify what hardware those signals control or even how the hardware behaves for a given signal. It may be a bit simplistic, but the best way I can explain it. A touch-wiz ROM and AOSP ROM will have different electrical connections, so they must have kernels made for those connections.
So far i've tried both faux and flar2's elementalx kernels on CM10.2 nightlies, and they both produce the same result. lag and screen tearing after playing a GPU intensive game such as Asphalt 7 and 8. I've mentioned this before, but apparently nobody else has had the issue. I'm starting to think my Nexus 7 is again having issues. If so it's going back for good.
It does not behave this way on the stock CM 10.2 kernel, so I'm not yet 100% sure it is a hardware issue. All settings are on stock with no overclocking as part of my test to see if I can figure out why.
You can see what it does in the video posted below: It was taken after playing Asphalt 7 for around 20 minutes.
https://dl.dropboxusercontent.com/u/17013328/N7screentearing.mp4
Can someone confirm this as a problem on their nexus 7 with custom kernels as well?
bump, i wanna know if there is a kernel that has vsync enabled... and how to enable it if it is off
You need to add voltage. Most kernels come undervolted. Some handle it better than others. Raise your CPU or possibly GPU voltage slightly and see if it gets better. Small increments. If you need to add too much voltage then it is something else. That is the first thing I'd try, especially since its on multiple kernels.
Sent from my AOSP on Flo using Tapatalk 4
CM drops frames playing something basic like super hexagon, for me. I haven't tried custom kernels yet but the stock CM one is crap. CM in general has just gone off the rails recently, stupid jss/jwr confusion and **** performance on nexus devices.
darkrom said:
You need to add voltage. Most kernels come undervolted. Some handle it better than others. Raise your CPU or possibly GPU voltage slightly and see if it gets better. Small increments. If you need to add too much voltage then it is something else. That is the first thing I'd try, especially since its on multiple kernels.
Sent from my AOSP on Flo using Tapatalk 4
Click to expand...
Click to collapse
Over-volting! it worked! i just added one step to all the clock speeds, no more screen tear!
but i want to know why it happens on the default voltages, i mean technically, why the tearing appears on low voltages?
EDIT: nope... screen tearing is still there... i added 2 steps to all of the clockspeeds, it's not solving the issue.
Sent from my Nexus 4
freeza said:
So far i've tried both faux and flar2's elementalx kernels on CM10.2 nightlies, and they both produce the same result. lag and screen tearing after playing a GPU intensive game such as Asphalt 7 and 8. I've mentioned this before, but apparently nobody else has had the issue. I'm starting to think my Nexus 7 is again having issues. If so it's going back for good.
It does not behave this way on the stock CM 10.2 kernel, so I'm not yet 100% sure it is a hardware issue. All settings are on stock with no overclocking as part of my test to see if I can figure out why.
You can see what it does in the video posted below: It was taken after playing Asphalt 7 for around 20 minutes.
https://dl.dropboxusercontent.com/u/17013328/N7screentearing.mp4
Can someone confirm this as a problem on their nexus 7 with custom kernels as well?
Click to expand...
Click to collapse
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Honestly CM doesn't play nice with anyone/anything any more. They do their own thing and want to be separate and "special" so nothing works well if you try to change anything. Their stock kernel sucks, and their compatibility with other kernels is slim to none. Best bet is finding a rom that is less restrictive.
just to be clear here, i'm on stock 4.3.
i was on stock kernel when the tearing happened, i moved to a custom one with vsync... same issue. overvolted, same... i also changed governors too, but the tearing is always there.
a temporary solution is to lower the graphics, but the nexus 4 supports the highest graphics, so i want to fix this on high
nrage23 said:
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
You nailed it. I figured that out a while ago but thanks for replying
just switched to stock JWR, and the screen tear disappeared!
So I'm going to get my Nexus 5 tomorrow...and my SGS3 will go up for sale. It was a great phone and the community here has been awesome. Big thanks to the CM developers and Ktoonsez for making my phone awesome!
I've been pondering something for a while about phones and custom roms, specifically AOSP roms on Samsung Touchwiz phones...
From my experience with laptops, if I load Linux on it, there is some hardware that just plain won't work or that doesn't work as well as it does when it has Windows on it. I've done every fix and loaded proprietary drivers and done just about everything I can do to make it work as well as possible, but it still falls short of Windows. This is plainly seen in battery life, with my best efforts I always lose 1-1.5 hours of battery life using Linux instead of Windows (not a knock on linux, I love to use Linux for certain things, I just have to use it with my power adapter).
I've been struggling to get good battery life with CM 10.2 on my SGS3 for some time now...I can barely get 8hrs with 2hrs screen on time with CM10.2 and Ktoonsez, undervolting and tweaking and all. I've done my research on wakelocks and energy usage and everything, but I just can't get it to go longer. So it the theory the same for the SGS3? Because it was designed for Touchwiz, it it practically impossible to get an AOSP rom to work as well/energy efficiently as a Touchwiz-based rom? And, as a curiosity, since the Nexus 5 is supposedly pure Android, will an AOSP based rom work just as well as the stock rom?
The difference would be that touchwiz is optimized by Samsung, and that Windows and Linux are totally different. The difference between touchwiz and aosp is more akin to say ubuntu and kubuntu or unity and kde. Also Samsung has all the drivers released for our hardware from what I understand cm has to take some generic stuff and tweak amd mod to get it to ruin on our devices. Hence the screen glitches you may see on some cm roms in some devices
Sent from my SGH-T999 using xda app-developers app
zander21510 said:
So I'm going to get my Nexus 5 tomorrow...and my SGS3 will go up for sale. It was a great phone and the community here has been awesome. Big thanks to the CM developers and Ktoonsez for making my phone awesome!
I've been pondering something for a while about phones and custom roms, specifically AOSP roms on Samsung Touchwiz phones...
From my experience with laptops, if I load Linux on it, there is some hardware that just plain won't work or that doesn't work as well as it does when it has Windows on it. I've done every fix and loaded proprietary drivers and done just about everything I can do to make it work as well as possible, but it still falls short of Windows. This is plainly seen in battery life, with my best efforts I always lose 1-1.5 hours of battery life using Linux instead of Windows (not a knock on linux, I love to use Linux for certain things, I just have to use it with my power adapter).
I've been struggling to get good battery life with CM 10.2 on my SGS3 for some time now...I can barely get 8hrs with 2hrs screen on time with CM10.2 and Ktoonsez, undervolting and tweaking and all. I've done my research on wakelocks and energy usage and everything, but I just can't get it to go longer. So it the theory the same for the SGS3? Because it was designed for Touchwiz, it it practically impossible to get an AOSP rom to work as well/energy efficiently as a Touchwiz-based rom? And, as a curiosity, since the Nexus 5 is supposedly pure Android, will an AOSP based rom work just as well as the stock rom?
Click to expand...
Click to collapse
It's is not true for everyone but maybe specific with your device as I am using mostly aosp / aokp roms and I am getting around 10 + hours time with 5+ hours screen on time
I too use kt with ktweeker setting with some undervolting and using greenify too
Sent from my SGH-T999 using Tapatalk
anil2653 said:
It's is not true for everyone but maybe specific with your device as I am using mostly aosp / aokp roms and I am getting around 10 + hours time with 5+ hours screen on time
I too use kt with ktweeker setting with some undervolting and using greenify too
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah...maybe it's just my battery going bad. Now that I think about it I was getting nerly 36hrs with 3hrs screen on time for a short time with CM 10.1.
So touchwiz is more akin to KDE or Gnome? That makes more sense...I thought maybe since there were so many differences it might have something to do with it.
Is anybody working on a custom ROM for the 510 yet? Kind of not necessary given there's no bloat and xposed works well. That being said, part of the reason I wanted to root my tablet is to play with different Roms/kernels.
I will say that mine is lightening fast, was easy to root using Linux, and has NO problems with the screen.
Any Update?
Any update on custom ROMs for the GPE V510?
bbubelis said:
Any update on custom ROMs for the GPE V510?
Click to expand...
Click to collapse
Why are you wanting a custom ROM? I ask because these days you can do many of the same things that were afforded by custom ROMs on the stock ROM using Xposed Framework modules, in particular GravityBox. There are very few options that I've seen in CM, AOKP, etc., that you can't do with those ROMs installed, and you get the benefits of the stock ROM, particularly with GPE.
Anyone who has used both a GPE and a rooted V500 running any AOSP ROM: is there any difference is responsiveness and speed at opening web pages?
cam30era said:
Anyone who has used both a GPE and a rooted V500 running any AOSP ROM: is there any difference is responsiveness and speed at opening web pages?
Click to expand...
Click to collapse
Yeah, that's been annoying. Think I have it fixed on latest kernel. At least my test run is working. It used to be forever waiting. Will upload sleekai5.1 soon. I'll check to see if XDA has their uploads fixed yet. Don't really like using github for that.
Sleekmason,
Really love the kernal mods. waiting for your next release with great anticipation.
sleekmason said:
Yeah, that's been annoying. Think I have it fixed on latest kernel. At least my test run is working. It used to be forever waiting. Will upload sleekai5.1 soon. I'll check to see if XDA has their uploads fixed yet. Don't really like using github for that.
Click to expand...
Click to collapse
So you are confirming that the V510 is more responsive and opens web pages faster than the V500?
cam30era said:
So you are confirming that the V510 is more responsive and opens web pages faster than the V500?
Click to expand...
Click to collapse
More responsive? Yeah, probably. Don't know about Roms. I scored 27474 on antutu for whatever that's worth. That's not with init.d set to lower CPU. Another user posted similar with madhi and the dyn kernel.
Web pages? You tell me.
sleekmason said:
More responsive? Yeah, probably. Don't know about Roms. I scored 27474 on antutu for whatever that's worth. That's not with init.d set to lower CPU. Another user posted similar with madhi and the dyn kernel.
Web pages? You tell me.
Click to expand...
Click to collapse
Well, I can't tell you.... at least not yet. I'm comtemplating buying a V510 and selling my V500. If someone with experience on both could post feedback.
And thanks for your info.
cam30era said:
Well, I can't tell you.... at least not yet. I'm comtemplating buying a V510 and selling my V500. If someone with experience on both could post feedback.
And thanks for your info.
Click to expand...
Click to collapse
No problem
I posted my latest kernel a few hours ago. Would love somebody to confirm better internet load times. If anybody has downloaded sleekai5.1, tell me if your connection seems better!
If you want a custom ROM, why did you spend too much money on the GPE?
Sent from my XT1060 using Tapatalk
popezaphod said:
If you want a custom ROM, why did you spend too much money on the GPE?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Because it sounds like fun. I later began tweaking the kernel instead, and adding other things like xposed. This thread is old. I wrote this when I first got the device and was looking for something different to work on. Because I wanted a clean device from which to work.
Other GPE devices can run custom Roms like their non gpe counterparts. This is the only device I'm aware of that actually has issues just loading any ROM you like. It's a shame.
sleekmason said:
More responsive? Yeah, probably. Don't know about Roms. I scored 27474 on antutu for whatever that's worth. That's not with init.d set to lower CPU. Another user posted similar with madhi and the dyn kernel.
Web pages? You tell me.
Click to expand...
Click to collapse
Now I can tell you. The V510 definately opens apps and web pages faster than a V500 (running CM11). Thanks for convincing me to buy one. Selling my V500.
gunnyman said:
Other GPE devices can run custom Roms like their non gpe counterparts. This is the only device I'm aware of that actually has issues just loading any ROM you like. It's a shame.
Click to expand...
Click to collapse
The issue is no one made a device tree yet for the v510. I have part of the device tree going thanks to @Drgravy and will be finishing it up when I can find the time.
Maybe @sleekmason can help with kernel
AndroidUser00110001 said:
The issue is no one made a device tree yet for the v510. I have part of the device tree going thanks to @Drgravy and will be finishing it up when I can find the time.
Maybe @sleekmason can help with kernel
Click to expand...
Click to collapse
Sure, let me know what you need!