Related
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
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.
Reserved...
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
THATTON said:
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Click to expand...
Click to collapse
tkirton said:
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
Click to expand...
Click to collapse
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
THATTON said:
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
Click to expand...
Click to collapse
tkirton said:
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
Click to expand...
Click to collapse
Hey, that works for me! Thank you!
Add Apps2SD support in your Rom
I created a guide in my main thread on how to add Apps2SD into roms that don't have it.
http://forum.xda-developers.com/showthread.php?t=715116
Bump....New version 2.7.5 Preview Fix 4 is out (and there was a PF3, but it was only released to Desire users to try to work through the NAND protection on their device...their changes are part of PF4).
Has anyone tried this on the latest CM6 nightly build?
Chahk said:
Has anyone tried this on the latest CM6 nightly build?
Click to expand...
Click to collapse
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
djdarkknight96 said:
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
Click to expand...
Click to collapse
Cool, let us know here and in the CM thread. I would love to know as well.
THATTON said:
Cool, let us know here and in the CM thread. I would love to know as well.
Click to expand...
Click to collapse
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
I'll check it out and see what's going on.
EDIT: It's possible that Busybox Run-Parts won't process two files with the same name. Since I can't run it, can you run a logcat so I can see what's going on. Send it to [email protected] and I'll take a look at it.
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
It works on CM6. All you need to do is flash boot from Modaco's (Paul's) Froyo R21 with a2sd.
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Here's how Darktremor Apps2SD works:
1. First thing it does is transfer control to launcha2sd, which is ran by using bash instead of sh (bash seems to be more stable).
2. Once launcha2sd is running, it performs a quick test to see if you are asking for help (a2sd help). If so, it displays the contents of the help file and exits.
3. Next, it checks to see if the following properties are in the init.rc:
- cm.filesystem.ready or dc.filesystem.ready (only one has to be present)
If so, it can run the more advanced boota2sd. If not, it will run a basic version of Apps2SD (FYI, these properties actually are used to stop the init.rc until Apps2SD [and any other script the rom developer deems necessary to run] are complete. This prevents dalvikvm from interferring, preventing a race condition).
4. Next, it runs starta2sd unless you don't have the properties stated before, then it continues by moving the /data/app and /data/app-private to SD card (if needed and after attempting to mount the ext partition). Then it activates swap (if available) then it exits.
5. Under starta2sd, it checks to see if a command was requested (install, remove, cachesd, cachepart, jit, nojit, etc...). If so, it runs the appropriate commands for the command requested.
6. If no command was given, it checks to see if apps2sd is being ran for the first time. If so, it transfers control to boota2sd. If not, it displays a message stating you need to supply a command and promptly exits.
7. In boota2sd, it checks for the old flag files (from version 2.5 - 2.7) and moves them to the /data directory.
8. Next, boota2sd attempts to mount the ext partition. If that fails, it will engage Boot Loop Protection, which puts your /data/app, /data/app-private and /data/dalvik-cache (if it is stored on the SD card) back to internal storage and sets the No Apps2SD flag file. This can be reversed by executing a2sd install once the issue with the ext partition is fixed.
9. Next, it checks for flag files and whether the correct setup exists. If not (say you have the Dalvik to SD cache flag file active but your dalvik-cache is being stored on your internal storage), the program initiates auto-repair.
10. Once that is complete, it checks to see if it needs to move applications to the SD card and moves them, unless the No Apps2SD flag file is present.
11. Next, it looks to see if the user has activated ZipAlign on boot (a2sd zipalign) and, if so, will proceed to zipalign the /data/app and /data/app-private directories.
12. Next, it activates the swap partition, unless the swap partition isn't present or the No Swap flag file is set.
13. The program then ends.
This is the automated boot sequence. You can control the behavior of apps2sd by using commands (a2sd install, a2sd cachepart, a2sd align...)
System files are only modified if there is a need to (i.e. JIT) and only if the user activates the correct command (i.e. a2sd jit, a2sd nojit). In fact, the only time the /system partition is changed to a read-write state is during the JIT installation (and that is changed back to read-only when the setup is complete)...otherwise, the /system partition is read-only through the entire Apps2SD run.
mlevin said:
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Click to expand...
Click to collapse
tkirton said:
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Click to expand...
Click to collapse
Awesome! Thanks so much for the quick and detailed reply!
Just read through the code. Nice work!
I see that one of the options is to put dalvik-cache in /cache. Any reason apps can't be put into this partition as well? On a rooted device, /cache is mostly wasted space. Or does /cache get wiped on reboot like /tmp?
So... II am having a issue I can NOT find anyone else having. After upgrading from UBUNTU to LinuxMint GNOME 64Bit (Clean Install)... I CAN NOT get Android Kitchen to extract my ROMs. Never had a problem prior. When I choose to Setup my working folder and choose my ROM (which was built in Kitchen) i get "Error No system folder found".
Anybody have some insight?
Could it possibly have anything to do with switching from GNOME 3 to GNOME 2 or vice versa? Not sure what versions you're running. I've only dabbled around with Linux a little bit but I know it can be a real pain in ass getting some programs to work. I recently switched back to Ubuntu from windows 7 and then to bodhi Linux sense its a little easier on resources.
Sent from my DROID BIONIC using xda premium
Your AXIOM can't find? Like AXIOM very much!
:good::good::good::good::good:
DroidTh3ory said:
So... II am having a issue I can NOT find anyone else having. After upgrading from UBUNTU to LinuxMint GNOME 64Bit (Clean Install)... I CAN NOT get Android Kitchen to extract my ROMs. Never had a problem prior. When I choose to Setup my working folder and choose my ROM (which was built in Kitchen) i get "Error No system folder found".
Anybody have some insight?
Click to expand...
Click to collapse
The 2 main programs that the kitchen depends on is jdk and sdk,make sure that the paths are correct and linked to kitchen and that you have installed all the tools used for sdk and kitchen.
what steps do i take to know that the rom i made is going to work other than flashing it?
Gentlemen,
Lately I have found myself experimenting with Debian on my beloved Leo. It's very much WIP, but even right now it may be fun to play around for some. And most of the stuff that *doesn't* work, well, solutions are in the line of sight.
I won't have time to finish it anytime soon. So, partly in hope someone will join the effort, and partly to simply make sure I won't lose effects of my work in the darkest corners of my hard drive, I upload it as it is.
It's very much bare-bones Debian Unstable system. To install it, copy all three unpacked files (rootfs.ext4, zImage, initrd.gz) to "debian" directory on your SD card. Then, choose this directory in MAGLDR settings. Then boot from SD.
It boots directly into the desktop and allows you to connect to wifi and launch terminal (and install any software you want using apt-get/aptitude).
DOWNLOAD:
http://www.multiupload.nl/8D7ZS99UTX
http://d-h.st/Tx9 (thanks to Robbie P)
MD5: 9f5a9961d8ace10d38f7ea493a12ab4a
(mirrors appreciated)
Features:
*Touchscreen, UI works perfectly fine
*Wifi works perfectly fine too
*Sound kinda works (playback is too fast for me, please test)
*It's full Debian GNU/Linux - 15901141666 packages to apt-get!
Various technical info:
*Kernel based on linux_on_wince_htc from gitorious with some modifications:
-applied USB host patch by liiochen
-applied patch from tytung kernel that enables ALSA driver to be compiled as module (without that it wouldn't work at all)
-custom defconfig
*Rootfs size is 1GB. Filesystem is ext4 (to avoid data corruption).
*Window manager is E17, it's optimized for phones, very beautiful, and very impressive overall. Network manager is Wicd.
*Also installed: Xterm, SSH server.
*Default username is "htcleo". Default password for this account is "htcleo". Default root password is..."htcleo".
*As it is Debian Unstable, anything can break at any time and not much can be done about it. I also recommend using aptitude over apt-get (it is better at solving dependency problems).
Important To-Do:
*Phone functionality & suspend/resume (all of this should be supported! sadly, fso-deviced in Debian repositories is currently broken)
*Landscape mode (easy)
*Hardware buttons (easy)
*Bluetooth (at least partial support should be easy)
*??? to be continued
Wish-list (the less important stuff):
*Switch to armhf for performance gains (should be easy)
*At least partial hardware acceleration (should be possible thanks to xf86-video-msm driver)
*Bully someone into cooking newer kernel (2.6.32 is old)
*If the above doesn't work, backport brcmfmac wifi driver to current kernel
*Compass, GPS, camera, multitouch (aka the stuff not many really care about)
*??? to be continued
If you want to help me in the effort to make this port work perfectly, take a look at this:
http://www.multiupload.nl/BXNBMMECH0
It's a package with everything you need to reconstruct my rootfs on your own. There are some files and there is a dirty bash script ("createrootfs") that does everything that has to be done. Instructions are inside of it.
There is a lot of valuable information on htc-linux wiki (http://htc-linux.org). I'm available in this topic, on pm, and on #htc-linux freenode channel.
Big thanks to #htc-linux, Cotulla, liiochen, tytung, dcordes, many others I forgot about and will add later.
[EDIT 16.09.12]
Some people requested kernel sources, here they are:
http://www.multiupload.nl/IWL07GL78D
MD5: c698454af38ad7ed3dbec120eae84daa
Clever ones will notice ".git" subdirectory. There's full history and anyone's more than welcome to upload it onto github/gitorious/similar.
Please refer to this htc-linux wiki page for compiling: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel . Use htcleo-gnu_defconfig (it's in arch/arm/configs/ directory).
I would appreciate someone testing USB host functionality. It should work (proper patches were applied), but I don't have cables to check it out myself.
Won't load from magldr-stop on " 123fatal hit 3 "
Sent from my HTC HD2
USB host works, keyboard and mouse. Connected to wifi ok. But when I tried to take a screenshot, it just hung and had to press soft reset button. Will test more.
Excellent work bardzusny, BTW there are Ladies on this forum too
@ivicabrus, be sure to unzip the .tar.gz, the .tar and also the rootfs.zip
Edit; mirror- http://d-h.st/Tx9
In my debian folder...is it correct?
Sent from my HTC HD2
ivicabrus said:
In my debian folder...is it correct?
Sent from my HTC HD2
Click to expand...
Click to collapse
Looks good m8
Robbie P said:
Looks good m8
Click to expand...
Click to collapse
But won't load..
Sent from my HTC HD2 using xda premium
ivicabrus said:
But won't load..
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Robbie P said:
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Click to expand...
Click to collapse
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
ivicabrus said:
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Try 10.services>1.bootsettings>1.boot source>1.android from sd
Then the above
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Will test it
Sent from my HTC HD2
ivicabrus said:
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Click to expand...
Click to collapse
did you check md5 sum of download, else can't think why it isn't booting for you.
searching fatal hit 3 only brings up someone who dropped their phone
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
[zozi] said:
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Can you boot sd android builds?
It could be that any ext partition confuses matters IDK.
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
[zozi] said:
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
Click to expand...
Click to collapse
Check my post earlier you have to unzip the rootfs.zip too
There is no link on the download page.
Must register on this site to be able to see the download link?
Sorry, is the first time I come across this download site.
Thanks.
Your rootfs.ext4 seems destoryed.
Sent from my HTC HD2
I did some test on this build and performance is much better than ubu. Ui is very smooth and keybord is good as for smartphone. Tried to test sound but clicking mplayer does not give result. Wifi works but sometimes needs system restart to connect. Dont try screenshot option (just like above). Good work!
Sent from my HTC Sensation (HD2) using XDA
This build is ported from http://forum.xda-developers.com/showthread.php?t=1867986 using Portadroid forum.xda-developers.com/showthread.php?t=1094372 Credits and thanks to Rick_1995, boonbing for Portadroid, cyanogenmod, cmhtcleo team (arif-ali, milaq, charansingh and all other cm developers) for device tree, tytung for kernel, Darkstone1337 for SuperRAM concept, and any others we forgot.
Instructions:
Well you know just extract everything and put the build folder (the one with all the files in, for example ics, jelly) in the root of your sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to build folder using ad-sd dir and select build folder name then boot AD SD.
Please remember to REBOOT X 3.
Magldr users can get different sized blank data.ext4 from here forum.xda-developers.com/showpost.php?p=24930501&postcount=1353 edit; may get boot loops, please test. Magldr default=512Mb if you leave empty. edit2 here is blank 256mb one http://www.mediafire.com/?ey40c1wti77ni2w
Downloads
Barebone CM7 V3 -Latest SuperRAM build from Rick_1995 see this post http://forum.xda-developers.com/showpost.php?p=42007074&postcount=64
note that this is not a port from nand rom, but an exclusive SuperRAM build from Rick_1995
There is a problem for magldr users changing lcd density, a solution is posted here http://forum.xda-developers.com/showpost.php?p=47161712&postcount=78 (thanks to Calisto1986 for the heads up). HaRET users are unaffected and can edit startup.txt as usual
Barebone CM7 V2b SRAM
DEV-HOST LINK
Barebone CM7 V2 SRAM
DEV-HOST LINK
Barebone CM7 SRAM
DEV-HOST LINK
This is from parent thread by Rick_1995
Note: I compiled this rom for myself but figured sharing won't hurt, and hence I don't plan to provide much support though I'll see what i can if you find a bug.
What is the difference between this and the nightly ?
All libraries and native code is compiled in ARM mode (except for libwebkit which is still in thumb mode due to it's excessive size) and compiler side optimization is turned on (again, exception being libwebkit using -Os and sqllite using -fno-fast-math).
Important function calls and syscalls are aligned for faster response time.
I re-implemented some of the cpu atomic functions based on what I've learned so far, swp is used for atomic swap instead of ldrex/strex, register swapping of old value is done at success so if a context switch does occur, the loop will be aligned at the same boundary as the function. On best case, there shouldn't be any difference but can improve execution time for worst case of context switches.
Java libraries and bionic libc are compiled with NDEBUG, and the debug variable for java is also set to false.
Most crap (stuff that "I" do not use, has been removed ie. VPN, live wallpaper support etc..)
Fixed a few memory leaks in bionic, dalvik and ppp (also tether).
I've removed most locales except en_US and en_GB, though android still seems to be compiling strings from other languages in the build, so they might work but i can't guarantee anything with locales other than en_(US|GB). Arabic patch
Reverted the patch which auto closed notification bar when all notifications are canceled/removed. It was irritating me..
more stuff i don't remember.
For now the kernel is tytungs-r1 ics kernel patched for gingerbread, though I will be patching/updating and working on the cmhtcleo kernel once i have the build known to be bug free after some time.
Click to expand...
Click to collapse
One more............
thans wiss....very quick port ....
Touch selection sound does not work for me.... others looks good so far...
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
aion92 said:
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
Click to expand...
Click to collapse
Because you're not setting proper command line, if you're booting from magldr, you just can't do this. If you're booting from clk, while creating boot image, set the cmdline exactly as in startup.txt and modify the partition size then flash that to a secondary boot partition, now just boot on secondary boot partition for the SD rom. I think suspend wasn't working properly with clk on sd roms, have to see why.
If it's from haret (unlikely) just edit size in startup.txt
@wis, thanks for the port, might use it sometime in the future when i try the new WP builds
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Thanks Wis (although I think you should be concentrating on something outside xda!).
Any advice on how to get option for "Corporate" Accounts?
This could be my favourite
Cheers
Tom
Sent from my HTC HD2 using Tapatalk 2
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
aion92 said:
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
Click to expand...
Click to collapse
Hmm... I may be wrong here, but from my understanding...
The NativeSD method writes to partitions on an SDCard...
SuperRAM ROMS mount to RAM which is faster than both NAND and SDCard...
So I would assume by modifying this to use NativeSD would be more detrimental than good?
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
aion92 said:
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
Click to expand...
Click to collapse
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Version V2 please!This is great, thanks:good:
strikelight said:
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Click to expand...
Click to collapse
Ok, thanks, I`ll try expand my storage with "Toporesize" then.
Update: after some researching ive managed to have 4 gigs of storage even without toporesize - with MAGLDR startup.txt config of 4096 gb does nothig for me earlier, but with sboot + CLK it works great! My problem is solved, yay!
Update2: aaand... after 1 reboot the rom just doesnt boot at all ... ill try to install one more time then.
Barebone CM7 V2 SRAM
Barebone CM7 V2 SRAM is now on post 1:good:
So, every time when i make a reboot or shut down from working rom, the data.ext4 clean itself to 0 bytes. I use CLK + sboot \ sboot tools, 4096 mb automatic generated data file. Any ideas?
Strychnin said:
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Click to expand...
Click to collapse
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
ictimai said:
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
Click to expand...
Click to collapse
At the moment there is no surport for cm7 but i dont think it will be long
Sent from my HTC HD2 using Tapatalk 2
wis1152 said:
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
Click to expand...
Click to collapse
:laugh:
edit line in /bootsystem/build.prop ro_lcd_density=240 to whatever using a root browser, and reboot.