I looked for a while, and found parts of the method, but no guide....
can someone give me a link as to where i can find it?
I'm not sure that all the ROM devs are using the same code, so:
"Use the force; read the source."
On my current ROM (Aloysius V12), a2sd is a shell script at /system/bin/a2sd - 453 lines long. At the beginning of that script are the comments
Code:
# A2SD version 3
# Edited By: TrevE @ xda for damagedrom
# Based on the modded Apps2SD by Robert Travis Kirton
# Automatic ZipAlign by Wes Garner
Not the easiest read in the world, but "what it does" is right there; you just need to decipher the script.
In the Aloysius version, it becomes apparent that it just "runs" automatically (started from /init.rc). It can be configured by toggles in
/data/data/com.damaged.DConfig/dc.conf -or-
/system/etc/dc.conf
It appears from examination of that version of the script that it tries to be reversible - that is, if you turn it off with a toggle in the configuration file, the next time it boots, it will move the apps back to /data. Don't quote me on that, though; YMMV.
Make sure you have backups and test thoroughly.
bftb0
There's not much of a guide for it, but I'll try to explain it as best as I can.
Apps2SD (or A2SD) is a script originally created by Cyanogen. The script, in its basic form, does one thing: moves your applications from the internal storage (/data/app and /data/app-private) to a linux-formatted (ext2, ext3 and sometimes ext4) partition created on your SD card. The way it does that is the following:
1. Creates /system/sd/app and /system/sd/app-private directories on the ext partition of your SD card
2. Moves the programs in /data/app and /data/app-private to /system/sd/app and /system/sd/app-private, respectively
3. Deletes the /data/app and /data/app-private directories
4. Recreates the /data/app and /data/app-private entries as symbolic links pointing to /system/sd/app and /system/sd/app-private, respectively.
Over time, developers such as myself has expanded on Cyanogen's basic script (even Cyanogen has improved the script quite a bit since the original version). The program has evolved to do the following (depending on developer):
1. Moving dalvik-cache to the SD card (and even to the Cache partition in Modaco's version)
2. Enabling JIT functionality (an enhanced Dalvikvm)
3. ZipAligning programs to make them load faster
4. Changing the Dalvik heap size to minimize dalvik-cache bottlenecks
5. Enabling swap partition
6. Diagnostic functions to check if your setup is correct
7. Automated repair function
Currently, there are three popular versions of Apps2SD: CyanogenMod's version by Cyanogen (commonly known as Apps2SD 1.x, though I know it has evolved as well), Darktremor A2SD by me (version 2.x), and DamageControl's version by TrevE (version 3.x). The version numbers really don't mean anything nowdays. When I created Darktremor A2SD, I based my code from CyanogenMod's first versions (1.x). TrevE based his code from my 2.5 code. At the time, TrevE's code was the most feature-rich, but over time Cyanogen's version and my version have evolved, so now all three are close to the same features.
The way each controls the various options is different. Both Cyanogen and TrevE uses custom properties (Cyanogen starts his custom properties with cm for CyanogenMod, while TrevE uses dc for DamageControl). I use a series of files stored on /system/sd (the root of the ext partition) that control which options are loaded.
Cyanogen and TrevE's versions have GUI interfaces while mine is all terminal based commands. Theirs is easier to program, but mine is more flexible with immediate feedback (designed for diagnostics). Also, whatever roms don't work with Treve's version will usually work with Cyanogen's version. Darktremor A2SD was designed to work with most roms (whether it does is another question, but that's why it's constantly evolving as well).
Trying to keep this from sounding like I'm trying to pitch my program.
I don't know what else there is to say...if you want to ask more questions, I will be happy to answer them to the best of my abilities.
adammsu said:
I looked for a while, and found parts of the method, but no guide....
can someone give me a link as to where i can find it?
Click to expand...
Click to collapse
excellent replies, thanks you very much, both of you. That definitely clears some things up.
if i were to take what i read (from this and other things) and try to make it practical for me:
1: partition SD (after backups and what not)
2: install rom that supports
3: use one of the 3 a2sd apps (depending on rom) to move the files and set up functionality
sounds about right?
adammsu said:
excellent replies, thanks you very much, both of you. That definitely clears some things up.
if i were to take what i read (from this and other things) and try to make it practical for me:
1: partition SD (after backups and what not)
2: install rom that supports
3: use one of the 3 a2sd apps (depending on rom) to move the files and set up functionality
sounds about right?
Click to expand...
Click to collapse
Steps #1 and #2 sound about right - a2sd is already set up in them, and merely detecting an ext2 (or ext3) partition on your SD card will kick it in place.
Wiring it into another ROM that doesn't already have it is a little bit more detailed, and - because you need to start up the mounting and symlinking pretty early in the boot, part of the fixups need to be done inside the boot image. (That means that you would have to unpack the boot image, edit it appropriately, repackage it, and then flash that boot.img back to the phone). A fair bit of work.
Thankfully, the ROM devs that have everything set up for you have already done this work for you... just do steps #1 and #2... and then afterwards, make sure you understand the implications of doing regular Nand backups versus Nand+ext backups.
bftb0
URGENT UPDATE: THIS KERNEL COULD BREAK YOUR ROM. It re-orders the mtd block order, this causes some custom scripts (e.g. in init.d) to break. Please don't use it for the moment unless the ROM is specifically updated to use it. You are free to test it, but be sure to backup first. Please report if the ROM works, and if possible check if there are any init.d/sh scripts with static mtdblock# mounting too (see post #13 for details).
Info For ROM Devs: To make your ROM compatible with this, any scripts you have that (re)mount partitions need to be updated. Please see post #13 for details.
If you use a ROM and want to use this kernel but it doesn't work, feel free to let me know and I'll see if I can make a patch to update it in case the original ROM builder doesn't for some reason.
----------------
Unlocked Bootloader only obviously, don't ask about locked bootloader support. I don't take any credit for this kernel. This is a mod of Championswimmer's kCernel v01 (the new 'test' ones, which are the best kernel yet IMO), I only started a new thread incase this kernel has issues whereas champs' original one doesn't (you can report them here). Additional credits go to DoomLorD (got some code from his old kernel for FXP, i.e. DoomKernel v05) and of course J and the FXP Team.
Hope you guys don't mind Championswimmer and DooMLorD, you are Gods :highfive:
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- CM7-FXP125 and later
- CosmicUI v0.6.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
v03
- Fixed gradual pixel shift bug in Aroma installer
- Changed handset max-gain to 600 (was 1000). I noticed no difference in volume, this also fixes distortion for some X10's
- Unlocked more mhz (1152, 1190, 1228). Be careful with the higher ones, though CM7/CosmicUI will revert to safe clock if it crashes.
- Compiled a second version with a different "safe" partition map for huge ROM's (system @ 285MB, userdata @ 608MB, cache @ 35MB)
- Optimized smartass governor for better sleep and wake (thanks to DooMLorD and FXP)
- Optimized smartassv2 governor for better sleep and wake (thanks to DooMLorD and FXP)
- Default governor changed to smartassv2 (bit more battery friendly than SavagedZen)
v02
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
v01
- Based on kCernel "test" v01
- Changed bootlogo to CosmicUI one with kCernel for FXP branding
- Removed Bootmanager (I don't use it) and replaced with Doom's Touch Recovery (more stable backup/restore than FXP Recovery)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
6) In my experience I've had to perform a Factory Reset and reinstall the ROM when switching from another kernel.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Download
v3 MaxMTD (/data = 730MB version) - recommended for CosmicUI
http://www.mediafire.com/?d4fenoosqeeryyk
v3 SafeMTD (/data = 608MB, /system = 285MB) - recommended for large ROM's
http://www.mediafire.com/?tuu7b07kptb32pb
Source
http://www.mediafire.com/download.php?nunrktw96q58eof
Detailed Info (for devs)
I am surprised how easy it was to create a custom partition map and I have no idea why nobody else has done this before. All I had to do was edit the default build config and edit the CONFIG_CMDLINE value:
Code:
CONFIG_CMDLINE="console=ttyMSM0 mtdparts=msm_nand:[email protected](boot),190m(system),730m(userdata),8m(cache),4m(appslog)"
...the other changes were taken from DoomKernel v05 in a basic tree-diff method.
Special thanks for Championswimmer and his guides, tips, kernels, etc. You are the best
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Prodigy said:
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Click to expand...
Click to collapse
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
CosmicDan said:
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
Click to expand...
Click to collapse
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Prodigy said:
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Click to expand...
Click to collapse
Hmm maybe it was xLoud that damaged the earpiece, who knows.
I checked out that post and crawled their GitHub, unfortunately they didn't use GitHub version management until a few months after adding the call-volume hack he mentions. So I won't be able to find it in that source =\
Guess the only thing to do is PM a veteran x10 kernel dev, but I'm not sure who. They all seem to have moved on since. If there is any other custom kernel (even for stock-based or locked bootloader) that you can find without any volume hacks, do let me know.
Although with the minimum-gain tweak I merged into this (which, as a mentioned, was from DoomKernel and not in original kCernel), I could compare the code from that to the stock kernel sources. But that will take a bit of time and I might not be able to find it, depends how much these custom kernels have changed from stock.
EDIT: Hang on, I just found an older repo from that thread "FreeKernel" (before it was 3Kernel). Maybe I'll find it.
EDIT2: Found it. https://github.com/tkymgr/semc-qsd8x50/commit/6c3c316b69ce7177cd08c73895406c94fd72db32 Yeah, I could have guessed that but now I'm sure so it's OK haha. If you look at that page you can see the ".min_gain = -900" which is what I changed to -400, but the max is changed here too.
OK, so the stock kernel (I think) has max set to 600, in this kernel, kCernel and DK though it's on 1000. I will create a version with 600.
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- FXP125 CM7 (official)
- CosmicUI v0.5.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
TAL333 said:
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Click to expand...
Click to collapse
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
CosmicDan said:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
Click to expand...
Click to collapse
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
TAL333 said:
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
Click to expand...
Click to collapse
OK, good call. I don't know why 35MB on cache will be needed with the download cache redirected to /data, but OK I'll do one with 285MB on system and 35MB on cache and that'll be marked as the "safest" mod. Then I might make one in-between if asks for it. But there will be a limit to how many I can maintain
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Prodigy said:
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Click to expand...
Click to collapse
No worries. Let me know if it helps though? Next version will keep it, as I already mentioned that my test showed that it was not quieter at all putting the gain back to 600.
Info for ROM makers
Code like this in any sh scripts (e.g. init.d, hw_config.sh, etc) will not work with this kernel...
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system;
...because it assumes a standard MTD map. This kernel has however modified the order. We could just change it to mtdblock1, but then that ROM would only work with this kernel. So, we use a function to parse the /dev/mtd file to find the correct mtd device to be mounted.
Add this helper function to the top of your script(s):
Code:
get_mtd() {
local DEV="$(grep "\"$1\"" /proc/mtd | awk -F: '{print $1}')"
local PATH=/dev/mtdblock
DEV="${DEV##mtd}"
echo "${DEV:+$PATH$DEV}"
}
...then later, when you need to assign the right mtdblock, do this...
Code:
mtd_system="$(get_mtd system)"
...changing 'system' to whatever you want to find. This will populate the variable with /dev/mtdblock1 in kCernel-CosmicMod, or in other kernels with /dev/mtdblock2. All good.
So then after that you can use it in a line like this...
Code:
mount -o rw,remount -t yaffs2 $mtd_system /system;
...and that's pretty much it.
...I realize that I could correct the kernel to use the "original" mtd map order, but this is a good habit for a developer to get in to. A developer should not tie themselves down with device-specific habits. Besides, my changes to the mtd order make more sense and other Android devices that I know of seem to follow this same order.
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
TheRuan said:
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
Click to expand...
Click to collapse
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
CosmicDan said:
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
Click to expand...
Click to collapse
No no, what i'm saying is that this doesn't work with the Kcernel, i couldn't try your modified one since i've been working a lot this week and didn't have the time to format the phone again, the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it, not sure about the swap partition, but pretty sure it would mount it too, but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Will try tonight to format the phone in the work, but can't promise anything since i've almost no tools here and also i'm very sick, shouldn't be working neither, hehehe, but I'm workaholic.
TheRuan said:
No no, what i'm saying is that this doesn't work with the Kcernel
Click to expand...
Click to collapse
Well you should probably ask in original kCernel thread or the thread for your ROM... what is the ROM you are using? I could take a look when I have time if you can't give me a logcat.
TheRuan said:
the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it
Click to expand...
Click to collapse
No, it doesn't have any function to mount sd-ext. You have to use a third-party method to get sd-ext access such as A2SD scripts (can be buggy) or the Link2SD app (recommended, most stable and more powerful).
TheRuan said:
but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Click to expand...
Click to collapse
Hmm all I can suggest is to reflash kernel with latest flashtool, factory reset, and reinstall the ROM. If no init.d scripts are running it must be a bad kernel flash, which happens fairly often with the X10.
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
TheRuan said:
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
Click to expand...
Click to collapse
Well I don't know what to say, init.d executes fine for FXP kernel, kCernel original and this kCernel mod. I find it hard to believe that init.d isn't working at all, because then sysctl wouldn't even be running. It's more likely that it's crashing out because of something you added or changed. You'll need to logcat it.
And sorry, I was wrong - the 05mountsd script handles sd-ext mounting. But that never did anything in my experience, it depends on your configuration. Link2SD works 100% for me and it creates an init.d script when you first run it and select your sd-ext partition type.
I noticed the undervolt thing and it's the only thing holding me off releasing the next version, I think I need to enable that sysfs interface somewhere. Changing clock voltages is done at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels - same as every other custom kernel for x10 that has it.
[email protected] said:
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
Click to expand...
Click to collapse
Try flashing stock gingerbread FTF, and please take those questions to the Questions forum - this has nothing to do with this kernel.
SleekAI kernel for the LG G Pad 8.3 V510 (GPE)
Updated 1-22-2015 CURRENT Sleekai8.1
Both kernels updated to Fsync off (again) and a couple of small changes to code. Also changed the versions to match numerically.
Also added a new 88sleektweaks file for init.d that has preset values for voltage control undervolting, See second post for instructions and zip file. Use Trickstermod if you want fsync on.
Both Lollipop And Kitkat Versions
(Lollipop version also works with CyanogenMod12)
Features:
Flash Through Recovery!
Interactive Governer as default
Row IO Scheduler as default
Wheatley Governer added as option (Lollipop only)
Knock_on enabled by default (Lollipop) or with
My app in the third post down (KitKat)
Sweep2Sleep enabled as an option
LCD screen control using Trickster Mod
Compiled using Linaro Toolchain cortex a15-4.9.3
o3 Compile optimizations
init.d support (zip align, etc...)
Faux Sound Control added
USB Fast Charge added
Frandom replacing Urandom
Fsync On/Off using Trickstermod
Tethering for bluetooth and usb
Exfat support for sdcards
User Space Voltage Control TricksterMod to change
Five new IO schedulers for Lollipop! Trickstermod to change
And more!
The kernel source and Commits that show the changes used for sleekai can be found here: Github
Prerequisites
Unlocked bootloader
Root
Install Busybox for init.d support
TricksterMod is recommended for changing settings
How does this work?
Start by making a backup of your boot in recovery, then:
Flash the latest version in Recovery . Proceed to the downloads below, download to your tablet, reboot into recovery and install the zip --That simple!
if you want to build your own kernel start to finish with complete instructions, you can follow my guide for rolling your own kernel HERE
Please hit "Thanks" to show your support!
DOWNLOAD HERE:
ATTACHED FILES
TO USE INIT.D SUPPORT ON YOUR DEVICE
Busybox must be installed for the init.d support file to work! (in the playstore)
You will need to add a folder named init.d to /system/etc/ in order to use this support
One example is to have your apps zip aligned on boot.
Another is to use my 88sleektweaks script to save battery
This includes undervolting values that you can adjust as neccesary, and a few WiFi tweaks.
Unzip the file to reveal the zip-align script. Then:
Copy the script to your /system/etc/init.d folder, change the permissions if needed, and reboot. Thats it!
You can tell you have it right by looking in /data for the zip align db files after you reboot.
You should change your permissions on any file in init.d to rwx r-x r-x (755)
Sleektoggle - For Knock_on and Sweep2Sleep
I made a small application using tasker that will enable Knock-on and Sweep2Sleep on devices using the kitkat kernel.
Knock-on is enabled by default in my Lollipop kernel - no app required.
The application works as a toggle, and will need to be "enabled" after every boot to use these features.
This is for your protection, as knock-on will freeze your device if enabled before or during boot.
This keeps you from having to enable these manually by adjusting the files yourself.
The knock-on feature should work on ANY 510 device, as it is native to the device.
To use:
Download and install the apk.
Put the icon from your apps somewhere on your home screen
after boot/reboot, press the icon, allow root privilages, and you are done!
You should only need to enable root the first time.
To use the features:
Simply knock twice in the center of the screen to wake up your device from standby
To put it to sleep, swipe from right to left on the lower portion of your screen.
Pressing the icon a second time does not disable the features. Restarting your device does!
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
edru said:
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
Click to expand...
Click to collapse
Excellent! You can expect the first reboot to be slow, as well as the first opening of some apk's as the kernel repopulates the files. Let me know!
A lone V510 dev emerges!!! Thank you!
Sent from my LG-V510 using Tapatalk
-Updated kernel for ability to pull the .config from the device, and shorter idle time before sleep.(battery saver). With this comes an updated name change to sleekai2.
--Update--
Kernel recompiled using the latest Linaro toolchain 4.9.3
Gamma corrected on the tablet with no further optimization needed
And the latest Antutu benchmark for the 510 with the latest Lollipop kernel: 31,526 See attachments.
going to give this a go right now.
---------- Post added at 01:57 PM ---------- Previous post was at 01:49 PM ----------
Gamma looks GREAT!
nice job sir. Thank you.
Just flashed on my V510. Thank you so much for your hard work!
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
this is awesome! It feels like a brand new device!
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
schalmers said:
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
Click to expand...
Click to collapse
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
kdog350 said:
this is awesome! It feels like a brand new device!
Click to expand...
Click to collapse
Excellent! Glad to hear it!
general_z said:
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
Click to expand...
Click to collapse
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
-Update-
Kernel Added
Changelog 22 Feb 14
general setup-perf-changed to sleekai3
compiled with -o2 for optimization of code/better battery life, maybe.
general setup-kernel log buffer size changed to 14
Note* sleekai3 is pretty much the same thing as sleekai2 except the specific use of the optimize flag for the gcc compiler. Does it really change anything? Don't know yet. Wouldn't worry about changing unless you just can't resist. If I see noticable battery savings I'll let ya know. Of course, changing is easy too . . ..
sleekmason said:
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
Click to expand...
Click to collapse
How thoughtful of you. In what file(s) is the gamma fix or where is the changelog that shows it?
I'm thinking that It may be quite easy to just to mod another kernel for the v500 and put it in (like dyn.Kernel v3).
sleekmason said:
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
Click to expand...
Click to collapse
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
schalmers said:
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
Click to expand...
Click to collapse
Yes, I did the fix as well. The sleekai3 is only the optimized sleekai2 (using flag -o2), so there really is not much difference.
SO, here we go, I looked up problems with the 64 bit card as I remembered reading something about them in a samsung forum. What I found this time I searched was here: http://forum.archosfans.com/viewtopic.php?f=84&t=66346 and here in our own forum: http://forum.xda-developers.com/showthread.php?t=2575043
Basically what "they" say is that the Sandisk 64 bit cards have issues with exfat. The solution is to format in fat32. you lose a gig or two with the different format, but it works. The above link also suggests ext4 as an option, but it will not work on our device, neither will ext2. At least not mine!
Long story short is to copy your files to your computer, reformat to fat32 and put them back!
The longer story is of more interest to me. As sleekai3 is based off the original kernel source for the 510, and because I have made no changes to areas that should/could effect the reading of your card, WHY does the stock kernel you have allow it? (yes, I switched it and am assuming it is unreadable by every kernel for the sake of argument.)
This is entirely a permissions issue as far as I know. frustrating. One thing I cannot do with my card is download a file, say a zip file, to my external sd card. I can copy it after it's downloaded, I can use link2sd with no problem, everything shows up well. This indicates the need for root access by Dolphin Browser.
I had thought to edit the fstab file and simply add "users" to the options but that doesn't work. I also tried many variations of the fix in the /permissions/platform.xml as well.
I'm going to have to study permissions for the device and see what I can do to fix it for everybody if I can. I'm afraid that adding the card to root could allow for an exploit. maybe.
Anyway, reformat to fat32 and let me know how it goes! regards, sleekmason