yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] theGanymedes:
I already did that, and actually problem caused because of that : I used the an old file to change the scripts in the zips and this is why all the bootloop problems occurred :) I'm reuploading all the zips as soon as possible.

EDIT: FreeHosting servers are down at the moment. I'll upload as soon as they become online..
[Desire Android Development] Droidzone:
Servers still down? If the files are each under 50 MB, Box.net is a good solution. Or maybe dropbox for larger files?

Signing off for the night. Hope it's online tomorrow.
[Desire Android Development] theGanymedes:
Uploading in progress

Uploading as right now, half is online already... The problem isn't the server side, my sh*tty connection :)

Will be all up in half an hour...

EDIT: We're back online ;)
[Desire Android Development] theGanymedes:
Problem report

Please, everyone, I beg of you to give me those information in case you have problems with packages:

1- What kind of storage config do you use? (Apps2SD, Data2SD [ownhere's or sibere's ?], Stock)

2- What is the error are you getting (Application doesn't work/doesn't work correctly, Bootloop etc.)? (Please include the error message too)

3- Recovery flash log (if you used .zip package)

If you cannot supply these, spotting the problem is like a searching for a needle inside a barn for me.. As you said, this is a big project, and I need to know where it goes wrong so that I can fix it - simply saying "it doesn't work" is meaningless.

If you cannot supply the recovery log: it's ok if you reflash the package and obtain one then. Recoveries do have option of "copying log to SDcard" so you can use it to copy the log.

Thanks for your understanding..
[Desire Android Development] Droidzone:
Yes, it failed and got a boot loop. I couldn't get adb to communicate, and hence no kernel log/logcat.

on data2sd

recovery log https://www.box.net/shared/jdpt9g1dl7dkn7qeg3az

This log is where I flashed all packages one after the other, starting with glibc, but with glibc alone, the net result was the same-bootloop at kernel level
[Desire Android Development] theGanymedes:
Weird: it says that you don't have a data2sd configuration, but a2sd configuration - which might be causing problems ( make sure you have /sd-ext/system folderor link in place at recovery - it's how the system differentiates the setting from a2sd. Actually, this might be the reason for bootloop :/).

Another side note was "out of memory" error: do you have enough space in mnt-data partition? - Because glibc installs there..

Also, you're should use v 0.9.3 one, the old one's faulty.
[Desire Android Development] Droidzone:
Hey, the script is lying! :) I do have /data/system, or rather /sd-ext/system, only difference is on data2sd, we don't have	a sd-ext folder at boot.

Yes, I tried the latest one. Well, without glibc, I have only 35 MB on mtd5? Is this a issue? Why do to have to install anything on mtd5 anyway? It could just as well be done with soft links, couldn't it?
[Desire Android Development] Droidzone:
Btw..I just compiled a static bash worth 3 MB..As soon as bash loads, it execs .bashrc from /, So I've symlinked / to /data. So it now execs /data/.bashrc, which can contain export for envt vars, you could also add library links there. So why not just do away with modification of the ramdisk, and use .bashrc as the initializer? In the open source terminal emulator, as well as when adb is launched, .bashrc is executed. We could just as well move sh out, and symlink sh to bash.

Notice the var dz? That comes from bashrc
[Desire Android Development] theGanymedes:
* GlibC installs at MTD, because it needs to be available on system boot. SD-ext partitions are not, because they get mounted on init.d level - so if bash (or such) programs which run on boot are to run well (with Glibc dependency) GlibC must be at mtd.

* I don't know how much space is needed, but I think it should be around 50 MB.

* As I said, I'm already aware and did the solution you did (and be careful, linking file system root to /data may lead complications) in bash installation. However, if we want something persistent, at least one ramdisk modification is needed.

* The script just checks if there exists a /sd-ext/system at recovery:

if [ -e "/sd-ext/app"] && [ ! -e "/sd-ext/system" ]; then .....

and if this condition is true, you're having an a2sd solution - otherwise a data2sd (couldn't think of any other differentiation). However, this doesn't affect much - since you have /cache/log/data2sd.on file. I think your problem is either space, or this ramdisk modification issue - which I find weird because doesn't happen on my stock but data2sd device :S

EDIT: alternatively, we can have a 01variables which links .bashrc at (say) /data to rootfs at every boot, actually.. Hmm, let me think about this...

EDIT2: Above method doesn't work with stock bash, needs a "new" bash to run.
[Desire Android Development] theGanymedes:
Guys, if you manage to install successfully, but couldn't get any application running: apparently I found a bug in recovery scripts which was omitting the step of creation of symbolic links - it was because of that.

I fixed the bug, and now uploading. Please re-download and re-flash if you had issues after 1 hour. Thank you.

EDIT: You can download now, upload is finished.
[Desire Android Development] Droidzone:
I suppose it wont fix my issue. :)

If you need a static bash, I have the latest one with all patches
[Desire Android Development] theGanymedes:
I have the sources as well, but I didn't want to have a static bash in the system to distribute, because not every rom has 3 MB space at their /system partition - and I don't want to mess with that partition much - especially if you consider that "not-statically linked" one is only 650 KB :)
[Desire Android Development] rikmer:
@droidzone:

I will try again to install this awesome project on my Desire with Oxygen 2.3.2 and only wondered if the scripts for installing data2sd in this thread http://xdaforums.com/showpost.php?p=10692249&postcount=1299 are the most recent ones.
[Desire Android Development] Droidzone:
They were. However I doubt whether those files still exist on those servers. I dont even have a local copy of them. I moved to my own version of Sibere's scripts long ago, and havent bothered about those files for some time.
[Desire Android Development] theGanymedes:
Thank you everyone for your interest .. Right now, I'm working on APT frontent (DesirAPT I called it) - this is going to be a tad weirder than I expected, I should admit (AsyncTask's, Views, Layouts ... all is floating around :) )

So far I could only finish the part that lists available and installed packages on the system. Soon, I'll finish this part and will start writing the parts which it'll actually install/remove packages as well.

While designing, I've been in a dilemma about an issue: As you guess, packages has some flags attached to them: like priority, essentialness, category etc. To make application look more "alive" I decided to attach pictures to this states and show them in a corner of package info window. However, now the problem is: without a legend of what picture signifies what, it'll be a little non-trivial to identify what picture means.

So, should I just add a "legend" to the program for that, or would it be fine if I had prepared a help page online - like here or on my own host?

I'm trying to dig meaningful icons from Google but, well, cultural meanings are different after all (a sprocket feels right about an executable image, but briefcase for a library? Hmm...).

So, forgive me if I delay :)

ADDENDUM: I added some screenshots of what I've done so far:

Splash:

First window:

Package Information:

Well, as you see, all packages have this "red sign" now, it's because I didn't upload proper pictures to emulator yet, but with the application distributed, I'll start distributing proper images for packages as well - I already coded that part :)
[Desire Android Development] Droidzone:
Very nice. I'd say perfect, if I just stopped having bootloops while installing the packages..The requirements are rather stringent if one needs 50 MB in mtd5.
[Desire Android Development] MartiniMoe:
Hi there,

Im finally allowed to post in Development-Threads! :-)

At the moment I had no time to try the new ZIPs where you fixed the Data2SD-Bug but Im going to post results here when I found time to try it again.

Considering the symbols: Maybe you can add explanations to the symbols in the Popup that shows the description of the packages (the one in Screenshot 3)?

I think a nice symbol for librarys would be something like the WinRAR-Symbol. Three books bound to a package. What do you think?

Edit: I really like where all this is going. Youre doing great work! Maybe someday you can change the GUI of Desire-APT to look more like ICS-Applications? You can find the ICS-Design-Reference here:

http://developer.android.com/design/index.html
[Desire Android Development] theGanymedes:
Your case is quite weird.. may you please reflash you boot image completely first?

Also, the first zip might have corrupted some necessary files, maybe? Try to restore a known-to-work backup first, maybe?

Btw, it takes 22mb, I checked...
[Desire Android Development] theGanymedes:
Notice something with the GlibC today: the dev's definitely not using libc.so, libm.so and libpthread.so anymore - these files (which are causing a incompatibility with the Bionic) are keeping just simple redirection scripts; and another good thing is: the compiled applications (at least all the ones I compiled) doesn't show dependency to them!

I think we can make them (Bionic and Glibc) work together ;)
[Desire Android Development] Droidzone:
Thanks a lot for the init syntax.. Wish I knew enough to help you. Don't worry about response to the problem. Very few people here are concerned about real development nowadays.. Most are interested in cloning roms ;)

I'd even posted a query about native c development for Android in the so called Recognized developer private forum. Nope, nil, nada. No response.

TouchPal-d from my Desire running Supernova Extreme Rom - 450 apps and counting. .
[Desire Android Development] theGanymedes:
Thanks a lot. Well, whatever, I love programming and did those just because I wanted anyway :)

Did init script work? I didn't test it myself - the phone was in recovery for so long time during testing, I thing it needs a time off too :P
[Desire Android Development] Droidzone:
Will try it later. For now, I've added a service in early init to see if it can do the same thing. I do need some

If_then logic, so bash has to come in..

TouchPal-d from my Desire running Supernova Extreme Rom - 450 apps and counting. .
[Desire Android Development] Chaosz-X:
Although I can´t help you guys with this project: I love the idea, and appreciate it much! Thanks a lot for projects like this, much better IMO than a bunch of Sense 3 ports :D
[Desire Android Development] theGanymedes:
@Droidzone, do you think I should compile GCC for Android as well? Would that be useful? Now we have GlibC, then we can compile some apps at Android as well :)

I'm already working on some applications (like shell itself). The problem is, the libraries are installed in sdcard ext[3|4] partition but this partition is not mounted till init.d level (which needs shell itself). I can mount at "init.rc" level; but we need some checks to do this correctly (and this is exactly when we need shell scripts).

I'm too tired right now to come with a solution. Please tell me if you can find a workaround.
[Desire Android Development] beidl:
Believe me theGanymedes, you're doing a great job here.

I've also considered "porting" glibc to Android but I've got a lot of other things to do.

Also, the reason this thread is more-or-less considered inactive is because most people usually lurking around here don't understand a word. ;)
[Desire Android Development] Droidzone:
Not entirely convinced that I want to compile apps from terminal emulator or adb.. :)

But it's a nice concept.. I'll be testing mounting ext from init section of init.rc (anyway, my version of Data2sd needs it).. If a service can be invoked for busybox at this stage, I think that solves the problem of invoking scripts..anyway normal runparts comes a bit later

TouchPal-d from my Desire running Supernova Extreme Rom - 450 apps and counting. .
[Desire Android Development] eXDee:
If it helps, i find this interesting and as far as i know getting something like this working would be a first for an android phone?
[Desire Android Development] Komadyret:
You have too much spare time on your hands! ;D

I'm following the progress, and will probably even try it at some time, as the concept is way cool. Sorry I'm not having the skills or time to help out in any way. But rest assured I find it interesting to follow this project.
[Desire Android Development] theGanymedes:
Well, I got spare time, alright :)

I gave 8 days (day and night) to create a nice toolchain and compile the library properly. The motive is: there is such a nice and small tools in Linux platform but apparently no one tried to port them to Android. I wanted make this possible... I even prepared ncurses library now, for instance..

I've seen some post at net too, but everyone was talking about what is missing; no one supplied it. I wanted to be the one who does that :) Thanks guys, I really appreciate your encouragements.

Well, let me put my hands on now then :)
[Desire Android Development] theGanymedes:
Added a few companion programs to the first page; check them ;)
[Desire Android Development] theGanymedes:
Vim is on the way guys :)

BTW; please tell me if you want a particular application compiled. I promise you to try that too (can't promise to deploy everytime tho, sorry :) )

I think I'm gonna try Emacs as well :)
[Desire Android Development] kfasheldon:
Thanks , be intresting to see what comes from this ...
[Desire Android Development] Komadyret:
Great progress.

Are there only "shell" apps you're compiling for now and testing? Or have you tried GUI apps too? Short jump from vim to lynx btw ;)
[Desire Android Development] theGanymedes:
So far only shell applications, because GUI applications require Xwindow system to be compiled. I'm going to try that as well, but not before I can master the process completely ;)

I also need to look for a "light" way to compile X, so it'll take some time - not even sure if I can make it coexist with Android platform
[Desire Android Development] theGanymedes:
Well, I realized today that except of compiling, preparation of the files for recovery is always the same. After compilation of promised applications, I'm going to start to prepare a small program that will automatize the process for me - ergo, the new application supply may slow ;)

Also, I'm planning to write a small (console based, because I'm not familiar with Android GUI programming yet) package manager for my programs, thus preventing user to go to recovery each time he/she wants to erase the package from his device. Might even try something that'll download and install! ;)

See you around guys ;)
[Desire Android Development] loedrus:
Someone did already just that, but I sadly forgot who did it. I also don't know if X could coexist with Android then, I googled the differences of Linux and Android then and came across that project.

So I think it's possible.
[Desire Android Development] theGanymedes:
I found it, it's going to be a little hard to compile it, but well, we'll see..

Sorry guys, btw, the links are going back and forth.. This is because I sometimes see small bugs and try to fix them right away. Going to upload all of them soon.
[Desire Android Development] theGanymedes:
Well, I started compiling X and it already has became 100MB or so :S I think it's going to be quite huge :)

Nice thing is, Android doesn't need X and if we're not to use any system programs that need X on boot (this is quite unlikely) we can use SD card to keep all libraries.

I think if we go on like this we're going to need our special sd partition (like data2ext) just for lib files :D - hmm, loved the idea :P

EDIT: Note that I didn't trim the library yet, for since I'm still experimenting on this, due to this all libraries (over 200, including font libraries, render extensions etc.). I think I'll trim them when I publish this.
[Desire Android Development] Droidzone:
Btw...my version of compiled binaries for ARM

https://sourceforge.net/projects/supernovakernel/files/linux-arm/
[Desire Android Development] loedrus:
now with the fixed glibc, I flashed all packages I found on the first page (no error given while flashing) with 4ext touch, but now apt-get update doesn't work. I suspect it's still the old busybox shell???

In any case, I can't change the shell to bash in the terminal emulator, too(Terminal emulator immediately fc's).

Screenshot of the terminal emulator attached.

Thanks,

loedrus
[Desire Android Development] Droidzone:
The last error message you received is interesting. it's the exact same one I have recently started receiving, not within the shell, but in Linux when I do an adb shell command.
[Desire Android Development] loedrus:
I get the same error in adb shell, too.
[Desire Android Development] theGanymedes:
It doesn't look like it's busybox shell - your prompt changed. Weird is it works on "shell mode" but not in "bash mode".. I'll try to see what's the problem - seems like some library issue to me...

EDIT: I made a small research and that problems seems like related to a GlibC - a bug with static binaries. Weird is, the shell I built is not static, so I can't really see why would be a problem. I'll test them all in my device once it has charged.

BTW: What ROM are you using, configuration of storage (data2sd etc. ) etc?

EDIT2: The second error message you're receiving is beyond my control: apparently it's a bug with GlibC itself with static binaries. I'll check if GlibC 2.14.1 still has the issue.

First message seems like my issue though, I'll check once my device is ready.

EDIT3: Issue (in second error) seems like fixed in GlibC 2.14.1.. I'll update it soon (will be in apt-repo)
[Desire Android Development] loedrus:
Unedited An-droid 2.1.0 ROM, which has, being a data++ ROM, parts of /system on /sd-ext, regular app2sd script otherwise. It also fits in oxygenr2 hboot, which I'm using now.
[Desire Android Development] theGanymedes:
OK, I don't know about that ROM at all - but I presume you're using the shell I distributed? That one also creates a "bash" link under /system/bin - so it should normally call "my bash" as well.

May you please put the outputs of

which bash

and

ls -l `which bash`

commands, too?

I'll work on the APT problem, once I fix that, I'll ask you to update the glibc and retry.

Repo will be offline for a while, since I'll be updating it.
[Desire Android Development] loedrus:
Screenshot attached:
[Desire Android Development] theGanymedes:
Oh, as I see, you also have a statically compiled "bash" binary which causes this issue. Hopefully, new glibc will solve that. Even if it doesn't solve, sadly I have to inform you that there is nothing I can do - this is an issue with Glibc and static binaries.

About the second issue, though; I apologize from everyone: I have made a syntax error in the script of Glibc at one of the regular expressions :) Uploading the fixed one as soon as possible :)

EDIT: Uploaded the new version.. Look omitting just a single " { " causes to us :)
[Desire Android Development] theGanymedes:
I specified this at the 4th post, but it's a good thing to remind here as well, I guess:

The packages don't have any specific order of installation: you can install them at any order you wish.

The only exception is APT - it should be installed after DPKG,

or otherwise your system will think you didn't install it
[Desire Android Development] loedrus:
I reflashed glibc, do I have to reflash the other packages, too?
[Desire Android Development] theGanymedes:
No, I already fixed the other ones before, but for some reason I skipped glibc..

Also, noticed that bash wasn't working because I was using an incomplete list of linkages to be made - fixed that one as well. To prevent any mishaps, I'm erasing and reuploading all of the zips tonight.
[Desire Android Development] theGanymedes:
ATTENTION FOR THOSE WHO INSTALLED GlibC 2.14.1 FROM APT REPOSITORY ( it stayed online for only one or two hours, but in case...)

Please erase "libdl.so" "libc.so" "libthread_db.so" and "libm.so" from your /data/lib and if existent from /system/data/lib and /mnt/asec/mtddata/lib folders - otherwise your system won't boot when you reboot.

it's called "library clash", because these libraries are also given by android itself - which causes programs to confuse which one to use.

For those who didn't install this: you're error free for since I already fixed that in 2.14-2 and it's the one in repo. (Old packages are free from this error as well)

Thank you
[Desire Android Development] theGanymedes:
Hooray!

I took my first donations for the project. Thank you very much! I'll keep posting the donors on the first page!

In the future, they'll have some privileges as well - after all we must cherish those who contribute to the project, right ;)
[Desire Android Development] rikmer:
Would this also work with AMARULLZ DATA TO SD-EXT? I read the description but was to dumb to figure it out myself.
[Desire Android Development] theGanymedes:
Sorry, I didn't know this solution when the packages created so, no, this algorithm is not supported. Why don't you use the package at the Cool AceS post itself - it also moves dalvik cache and system data to internal memory?
[Desire Android Development] rikmer:
I tried data2sd and data2ext and had some problems with those in the past ... lots of FCs with apps and less performance. As I understand the AD2SDX has better performance. Didn't test ist yet so I am not sure if this is true or if there are less FCs. I only wondered because my standard ROM MildWild which is based on Oxygen 2.3.2 (AOSP) upgraded to this solution in the last version and so it would be the most comfortable thing for me.

Is this solution not working because of the mounting points and therefore to less space for the packages or because your glibc install script is not able to handle it?

I only ask because if it is because of the second reason I could probably alter your script to also include this solution, if I find some time to do so.

I also wanted you to know again that I really appreciate your work and am really looking forward to finally get it up and running on the AOSP ROM that I use.

Also had some problems with bash not working resulting in FCs of the terminal emulator. As I understand this shouldn't be the case anymore.

Keep up the awesome work!
[Desire Android Development] Parastie:
Anyone tried this on the CM9 ICS build by dk?

http://xdaforums.com/showthread.php?t=1403113

I'm getting a bootloop on animation after installing the packages from the first post. :(

EDIT:

I'm reloading a backup that I have, wish I would have made a backup just before installing these files. LoL I'll have to try one at a time and see where things go wrong. My best guess is either the Linux util, or the ext space is filling up. DK uses a customized apps2sd solution that I have currently set to move apps and dalvik cache to ext. Since Market was recently complaining about low space, I'm guess I filled up somewhere.

I'll report back later today or tomorrow with more info, if I can get this stuff working again. I bet my wife is really mad that she can't call me at the moment. Hahahaha

EDIT2:

After flashing my backup I tried just installing glibc, only to have my wifi stop working on reboot. Which roms are working for this setup?