Please excuse me if this is a bit of a n00b question. But I have been reading up on F2FS and, whilst our phones (mine is an S9+) are already blazing fast, we could get even faster and more efficient results over a longer period of time by using F2FS? I also read that this is something that needs to be baked in to the kernel side of things?
Im just wondering if there is much call for this out on the XDA community and if any devs have given thought to implementing it to their kernels?
Samsung already uses F2FS on their phones, they have for years and they developed it in the first place for phones and other flash storage devices.
driverdis said:
Samsung already uses F2FS on their phones, they have for years and they developed it in the first place for phones and other flash storage devices.
Click to expand...
Click to collapse
Really? My device says it's using EXT4...
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
Guys, I’m sorry if this comes across as being a bit terse, but I’ve been very disappointed with my Epic Touch. While it packs a lot of great specs, coming from the HTC Evo nearly 9 months ago, I’m very disappointed with the overall stability of the roms available.
Please understand, this is in no way a complaint about the devs. I’ve been here long enough to fully understand and appreciate the amount of time and effort they put into these roms, and I’ve made a few donations along the way.
I’m hoping someone more knowledgeable might be able to explain some of the obsticles in developing for the E4GT. Most of the roms I’ve flashed have looked fantastic and offered great features, but I’m constantly seeing issues with kernels relating to battery life, LOS, GPS, bricking, etc. Are we not getting the kernel soruce from Samsung? The phone has been out for about a year now, and we still don’t have official CM9 builds. Heck, we were even the last (In the SII family) to get the official ICS updated. Again, I’m not complaining about the developers. It just feels like they may not have access to the resources they need in order to build more stable roms.
tl;dr Can anyone familiar with ROM development on the E4GT please explain why we see so many kernel related issues? I would greatly appreciate your input. Thanks!
The et4g is one of the only devices if not the only one that contains the recovery partition inside the kernel. That makes the kernel very different from other devices kernels and is one of the main reasons we aren't officially supported by CyanogenMod. We have the kernel source but for ICS its only been available for around a month, and came loaded with bugs that take time for the devs to locate and fix. GB had alot of bugs in the kernel source as well but 90% of the custom kernels for GB are relatively bug free, I say relatively cuz no software is ever 100% bug free it just the nature of the beast. Give it some more time and the ICS kernels will be just as stable as the GB kernels, the devs just need time to iron out the kinks Samsung was nice enough to pass along in the source
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Are device may not be the newest kid on the block but we just got ICS w/ source. For how long the source has been out the devs have been doing a great job and the word on the street is that we are going to be an official CM10 device which is better than just being a CM9 device if you ask me.
-EViL-KoNCEPTz- said:
The et4g is one of the only devices if not the only one that contains the recovery partition inside the kernel. That makes the kernel very different from other devices kernels and is one of the main reasons we aren't officially supported by CyanogenMod. We have the kernel source but for ICS its only been available for around a month, and came loaded with bugs that take time for the devs to locate and fix. GB had alot of bugs in the kernel source as well but 90% of the custom kernels for GB are relatively bug free, I say relatively cuz no software is ever 100% bug free it just the nature of the beast. Give it some more time and the ICS kernels will be just as stable as the GB kernels, the devs just need time to iron out the kinks Samsung was nice enough to pass along in the source
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Click to expand...
Click to collapse
That's exactly the type of info I was looking for, EViL! Thanks! Any idea why they designed the phone that way?
thaprinze said:
That's exactly the type of info I was looking for, EViL! Thanks! Any idea why they designed the phone that way?
Click to expand...
Click to collapse
Not a clue, I'm not sure if it has to do with hardware configuration forcing the software to be modified to function, if it was poor software engineering, or if they just wanted to try something new. I know it makes working with the kernel extremely difficult compared to other devices whose recovery partition is separate. Another major problem is the bugs included with source, they take time for our devs to find and fix in order for the builds to become more stable, I feel the major issue with that is Samsung made too many devices in the same family, gs2, all with different hardware configurations which require modifications to the kernel, making it hard for their developers to maintain the devics since they have to build a separate kernel for each device in the same family instead of one kernel that works on all gs2 variants with the exception of having to make minor changes for cdma, wimax, Lte, and GSM which would just require some driver changes and a little bit of minor code work. Instead they have to rewrite the entire kernel for CPU/gpu, network, display, ram, emmc, SoC etc for each variant of the gs2.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
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
I was wondering something, why there's no custom kernels for this device? (Not counting the ones made to fix the f2fs thing)
I mean, I came from Nexus devices and I remeber XDA being full of super custom kernels that would make my device four times faster, coulder, and battery friendly with CPU and GPU overclocks, optimized toolchains and a lot of buzzwords (I hope you see the irony here).
But really, just by curiosity, today there's no more interest in this kind of thing?
Maybe because stock is already very good but most probably because no developer interested to make it.
Sent from my XT1635-02 using Tapatalk
So I never really used "mainstream" or "flagship" & this is my first Samsung phone ever... & That being said the battery on this thing is s*** & I took the liberty of reading on here about the S7E battery hack, not knowing anything about modding or hacking phones. I took it to get the battery swapped, but my phone wouldn't boot, only showed the charging screen. So instead he put a S6E+ in my phone. The old battery was in it since 2015 (got it pre-owned through boost) so it's already better even without the phone recognizing the new capacity. I Rooted my phone for the first time, using ODIN, TWRP, & SuperSU, but I didn't make a backup first. I tried installing 2 different Kernels, Kiboi & SkyHigh. Kiboi had some kind of error before booting & said seandroid not enforcing on the Samsung screen and wouldn't go past that part. Removed that and tried SkyHigh kernel, it worked but got stuck on "Image Support Required" "Creating Image" so I took the original firmware from Samsung, wiped my entire phone and started over.
*UPDATE: I've switched from SuperSU to Magisk successfully & Synapse is working & SkyHigh didn't work because I installed v4 instead of v6*
So my main questions are these...
1: What Kernels for 920P will recognize a S7E battery.
2: What are a few things I should NOT do to avoid severely damaging my phone's OS/Software?
3: AccuBattery is reporting innacurate readings because it can't recognize it's not the original battery. How do I get my phone to recognize the new capacity in my settings & AccuBattery?
I am completely new to all of this, thanks in advance.
I figured a lot out. I've successful flashed BigDaddy ROM for Nougat, & SkyHigh v6.0.0 Kernel. Rooted with magisk. How do I make my phone recognise a S7 Edge battery?
(SM-920P) [Rooted] Custom ROM & Kernel combos for Nougat 7.0?
KingKRiggz said:
I figured a lot out. I've successful flashed BigDaddy ROM for Nougat, & SkyHigh v6.0.0 Kernel. Rooted with magisk. How do I make my phone recognise a S7 Edge battery?
Click to expand...
Click to collapse
The driver at that layer is not within then S6 base kernel. Send me the output of “ls -lR /sys”.
I intend to keep this kernel going well into the future, no plans to switch phones for as long as the battery keeps working but I can add support for other phones if there are testers.
Sent from my iPad using Tapatalk
tdhite said:
The driver at that layer is not within then S6 base kernel. Send me the output of “ls -lR /sys”.
I intend to keep this kernel going well into the future, no plans to switch phones for as long as the battery keeps working but I can add support for other phones if there are testers.
Click to expand...
Click to collapse
Output? How do I find that in the phone system? @tdhite
I intend to keep this kernel going well into the future, no plans to switch phones for as long as the battery keeps working but I can add support for other phones if there are testers.
Sent from my iPad using Tapatalk[/QUOTE]
This is fantastic news I just grabbed a new s6 from boost the other day for 100 bucks and was sad to see that there was little to nothing as far as development went for g920p but came across your kernel and I just love it..so many options in synapse it was overwhelming at first but now I want more I paired it with with the uni debloat mod floating around here that with some slight modification ended up working out quite well and was able to have 19gb of free space (and that's with an almost 8gb TWRP backup I have just in case I break something lol...so yes please keep up development of you would thanks alot
hammmersmashface said:
I intend to keep this kernel going well into the future, no plans to switch phones for as long as the battery keeps working but I can add support for other phones if there are testers.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
This is fantastic news I just grabbed a new s6 from boost the other day for 100 bucks and was sad to see that there was little to nothing as far as development went for g920p but came across your kernel and I just love it..so many options in synapse it was overwhelming at first but now I want more I paired it with with the uni debloat mod floating around here that with some slight modification ended up working out quite well and was able to have 19gb of free space (and that's with an almost 8gb TWRP backup I have just in case I break something lol...so yes please keep up development of you would thanks alot[/QUOTE]
Same here, that's how I got mine. Right now I'm on BigDaddy ROM for Nougat & SkyHigh v6 Kernel. I'd be willing to test if @tdhite adds support for the S7E battery mod, but I can't find the "driver layer output" or whatever it is he needs, I'm new to all of this I think I'm learning it all very fast but I'm still confused on a lot of the abbreviations, codes, lingo, ect. My only issue is I think the ROM uses way to much memory? I'll only have like 500-300mb left out of 3 gigs within an hour or so?
My only issue is I think the ROM uses way to much memory? I'll only have like 500-300mb left out of 3 gigs within an hour or so?
Click to expand...
Click to collapse
I have noticed that as well but I don't believe it is the ROM. It is the SWAP file from the Sky Kernel. When you go to Synapse and go to the Memory tab, mine is set at 2047mb. With 2698 total memory, that leaves 651 mb of available memory.
nhail47 said:
I have noticed that as well but I don't believe it is the ROM. It is the SWAP file from the Sky Kernel. When you go to Synapse and go to the Memory tab, mine is set at 2047mb. With 2698 total memory, that leaves 651 mb of available memory.
Click to expand...
Click to collapse
Okay thanks, that makes sense. The struggle is real here... I kept getting some weird problem where Magisk would randomly keep uninstalling and I couldn't access my Samsung Cloud. I reflashed the ROM (with S6 Launcher instead of S8) then the kernel. Haven't had the problem since.
NOW my issue is with Accubattery. I'm reading less than 2 hours of SOT!?!!!? My battery has the S6E+ installed and it's supposed to be 3,000mah, but I'm having worst battery life than I did before. I'm so confused I've tried calibrating it several times using Synapse & [ROOT] Battery Calibration Apps.