Related
Hi all,
If you are going to say we don't need Apps2SD on the N1, please leave the thread now . (Actually, read on) There are various reasons I can think of why we need Apps2SD on the N1, and one of the biggest is actually Games. I don't really play any games to begin with, but the last I checked, some games are as large as 19MB, possibly more. Isn't it kind of crappy that the N1, the superphone, can't hold more than 10 such games?
I started this thread with the intention of gathering more information, and hopefully some coders will do it (including myself, if I've the time). Package Manager (the thing in charge of installing, if I'm not wrong), is in the AOSP, under frameworks/base. In such a case, wouldn't it be possible for some programmer to mod it such that it will ask you whether to install to (SD/Phone) before each installation process?
The other issue is, looking at current implementation of A2SD, it seems all apps on Phone are moved to the SD card partition. If we can have an implementation that allows both to co-exist, in addition to the Package Manager mod, I'd say we'll have a pretty nice implementation.
Your thoughts/findings? I may be completely off, have yet to actually look at the AOSP source.
Update:
@ChrisSoyars has an early implementation of this in his SnackPack - http://forum.xda-developers.com/showthread.php?t=638301
I would also like to thank everyone else for their valuable input and support ! Keep them coming. Lastly, sorry I'm not doing much code-wise (not at all), school work's too much .
Would be nice!
....I've got the same problem. Some application are very big and so i have got only 10MB free space anymore...
ADB is god
See my attachment file
And...there is already a post about app2SD and this is not in the correct section...
lazinase said:
See my attachment file
And...there is already a post about app2SD and this is not in the correct section...
Click to expand...
Click to collapse
that doesnt work on roms like the desire by modaco. app2sd doesnt work, ive tried that method and it just hangs. true there is a thread already for app2sd, but its not going anywhere in terms of the newest desire release. i know its still early, but i only had like 50mb for apps and i have over 120 apps and i didnt feel like reinstalling. someone fix it please.
Apps to SD is of course necessary. The Nexus doesn't really have that much space for apps - about 190mb which is only the same as the Hero.
I have apps 2 SD working with CM 5.0.3 from the kitchen.
its also addable to a CM rom using the how to thread.
It WAS working ok with MoDaCo ROMS but for some reason has ceased to work and causes bootloops if you bake it in - shame...
I've no coding experience, but willing to test stuff out anytime.....
Dayz xx
i think what Wysie is trying to do is stimulate discussion about a different way to do A2SD.
He, and a lot of people believe (including myself) that running apps from the sd makes them slower, so what he wants is like WM where when you install an app it gives you an option to install it either onthe device or on the sd. So you can choose to install your most used and apps that require speed the most on your device...
And if this isnt thread development where the hell should he have posted it? It certainly is development if you ask me. he is thinking of ways to develop a better A2SD.
Seems like unionfs + some kind of app to manage which apps live where might work. This would require kernel support, however. You would set up /data/app and /data/app-private as union mounts of (say) /data/app-internal with /sdcard/app and /data/app-private-internal with /sdcard/app-private. You would then want a custom app management tool to move things to the appropriate places.
Nice initative Wysie.
My suggestions are as follows:
Use a different mount point, not inside any of the other file systems.
Like /apps2sd, this makes it alot easier to handle in the recovery realm (which is what I care about).
As for handling the specific apps installed in either /data/app or /apps2sd I suggest we have a look at something simple. Like symlinking individual apps.
Ext filesystem is mounted on /apps2sd on boot.
New installs of apps are done in /data/app like normally. /data/app is not symlinked to the apps2sd directory like it is today.
If a user want a app to be stored on apps2sd instead of in /data/app a management app can just move the .apk from /data/app to /apps2sd and set up a symlink it up into /data/app again.
Simple demonstration:
Initial state, two apps installed normally:
/data/app:
SomeApp.apk
SomeOtherApp.apk
/apps2sd
<empty>
Now the user moves SomeApp to apps2sd:
/data/app
SomeApp.apk -> /apps2sd/SomeApp.apk (symlink)
SomeOtherApp.apk
/apps2sd
SomeApp.apk
If this is possible, i.e. making sure that Android doesn't bork on symlinked apps (can't see why it would, but best to make sure). This is clean simple way handle it. It gives more control on what apps are stored where, better handling of ext stuff in recovery.
Also writing scripts/apps to facilitate this is trivial since it's so simple.
What do you think? Want input especially from ROM makers.
packetlss said:
As for handling the specific apps installed in either /data/app or /apps2sd I suggest we have a look at something simple. Like symlinking individual apps.
Click to expand...
Click to collapse
Okay, that's better than my idea, assuming it works. One disadvantage is that removing the SD card breaks all the links. You could conceivably swap cards with the unionfs approach, as long as you were not using any widgets or launcher icons which rely on APKs in the SD storage, and had a way to properly unmount the disk. Might not be worth the complexity, though.
I think the biggest issue is with regards to removal of SD card. You guys have made it way more complex than I thought, thanks for enlightening/sharing !
I thought it could be as simple as simply modifying the Apps2SD script to allow apps to exist on both the sdcard and the phone, and then modifying the Package Manager to prompt the user on where to install to. Keep those thoughts/opinions coming!
If it wasn't for my school work and lousy time management i'd definitely start doing something. For now, it's good enough if all the necessary knowledge is shared here, then some dev can actually start work and put it on github or something for the rest of the community to contribute!
i haven't looked deeply into android's files. but i've worked on hacking motorola phones to engineer a packet manager system. (EZX phones)
i believe the solution that we want isn't with the use of symlink or that sort. we should aim to find a clean, programmatic way of doing it - built to the heart of android.
any idea how android am manage the apps on the phone? is there an sqlite app db or something? how does it store the installed applications information?
arctu said:
i haven't looked deeply into android's files. but i've worked on hacking motorola phones to engineer a packet manager system. (EZX phones)
i believe the solution that we want isn't with the use of symlink or that sort. we should aim to find a clean, programmatic way of doing it - built to the heart of android.
any idea how android am manage the apps on the phone? is there an sqlite app db or something? how does it store the installed applications information?
Click to expand...
Click to collapse
Well, you have to remember that the solution should work on stuff that we do not have source access to, like people wanting to use on ported ROMs or a rooted stock ROM.
I tried to simlink apk's but for some reason it didn't work, simlink the app directory works.
I think the best way would be to add paths in the program that actually searches/launches the apps (my guess would be that's in framework.jar)
Currently it looks in /system/app, /data/app & /data/app-private there should not be any technical reason why it couldn't look in a forth directory. this way you can keep the imporant/most used apps in the flash and large/less used on the sdcard...
rj3005 said:
I think the best way would be to add paths in the program that actually searches/launches the apps (my guess would be that's in framework.jar)
Currently it looks in /system/app, /data/app & /data/app-private there should not be any technical reason why it couldn't look in a forth directory. this way you can keep the imporant/most used apps in the flash and large/less used on the sdcard...
Click to expand...
Click to collapse
packetlss said:
Well, you have to remember that the solution should work on stuff that we do not have source access to, like people wanting to use on ported ROMs or a rooted stock ROM.
Click to expand...
Click to collapse
Again, this is the problem. A general technique suitable for XDA-type applications must require only root or changes to GPL code. You can't touch the framework, which can (and does) have proprietary branches.
packetlss said:
Well, you have to remember that the solution should work on stuff that we do not have source access to, like people wanting to use on ported ROMs or a rooted stock ROM.
Click to expand...
Click to collapse
i would say that we have no choice but to implement it without considering those groups. however, i do suggest that we should make the implementation compatible, just that, on modded frameworks like cyan, it works to the fullest.
olearyp said:
unionfs
Click to expand...
Click to collapse
Everything old is new again. Oh well.
olearyp said:
Everything old is new again. Oh well.
Click to expand...
Click to collapse
Unionfs is not available for android devices without kernel sources.
Concerning ported rom, I am not sure the package installer get modified by vendors. So it may be possible to implement the changes done to aosp code using baksmali.
So my two cents are:
- modify AOSP sources to have android lookup at /sd/app for apps
- modify package installer to have it asks where to install apps
Sure the removing of sdcard problem is still there. I don't know how we can ever handle a straight manual remove of it. It implies big modifications to AOSP sources to have the system aware of missing applications that have existing home shortcuts or widgets, so it "hides" them until app is back...
Anyway we can start implementing the functionality and look after for that sdcard removal problem.
I've been thinking of doing this for a while, has any progress been made?
I like the idea of modifying pm to prompt for the install location, I was thinking of just writing an app to manage that (but probably would be a good idea to have both).
If progress has been made, great, if not, I may start a fork of CM5's vendor tree for this.
Lox_Dev said:
Unionfs is not available for android devices without kernel sources.
Click to expand...
Click to collapse
Kernel sources are the one thing you most assuredly do have on all devices, at least if they're sold where copyright law can be enforced. No one needs to risk a lawsuit by intentionally violating GPL.
olearyp said:
Kernel sources are the one thing you most assuredly do have on all devices, at least if they're sold where copyright law can be enforced. No one needs to risk a lawsuit by intentionally violating GPL.
Click to expand...
Click to collapse
Well.. it is not the case in real life.... For eg, acer Liquid kernel sources they acer provided is unusable.
Just a clue for aosp source modification:
services/java/com/android/server/PackageManagerService.java:frameworks/base/ Log.d(TAG, "Scanning app dir " + dir
can someone tell me if is possible port Android on this amazing device??
someone is working on this???
I wuold like a lot if someone port Andoid on oHD!!!
lukas_ita said:
can someone tell me if is possible port Android on this amazing device??
someone is working on this???
I wuold like a lot if someone port Andoid on oHD!!!
Click to expand...
Click to collapse
I was working on it for a long time. Unfortunately it is impossible, due to limited bootloader space (not enough for an android one) and no recovery partition. Also it would need a totally new partition layout (as it only has two accessable internal and one external drive, so no cache, recovery access, nor swap.
And also do not forget about the hardware incompatibility. Even if we manage to boot it, you will hardly be able to even make a phone call. Not to say use WiFi, or GPS, BT, or anything.
hi i joined because of some interest in this,
first of all let met tell you that i own a samsoung i8320 (vodafone h1).
this in some way helps because we now have a 'working' limo kernel, in my opinion it might help us out here.
the problem i have is that i never ever yet have been able to do 'any of the work here under' - the fact that i know howto doesn't make me capable of doing, (its like the fact that you know a plain fly's because of big wings and an engine, doesn't make you a pilot)
---------
the H1 uses a rather standard linux kernel as far as i can tell from the source could, though i havn't been able to run it inside quemu yet..
some guys allready interested in porting android say that they got android running but without functions like phone or wifi. this is because thay used an android kernel rather than the samsung one.
step 1:
so what if you would strip the samsung rom from all 'userland' software, keeping only the kernel, its drivers and busybox stuf.
creating a root shell only - you may even be able to make it mount as /boot rather than /
step 2:
now ad ad adtional filesystem on the internal phone memory or an external sdcard ... format it as you like (ext3 with noadtime could do, but other options are also availible).
this should now be where the remaining of the android rom should be. you could now always update most of your your android and apps exept for your linux kernel or drivers. without reflashing. this idea is largely based on apps-2-sd so we all know its been done before.
fonix232 said:
I was working on it for a long time. Unfortunately it is impossible, due to limited bootloader space (not enough for an android one) and no recovery partition. Also it would need a totally new partition layout (as it only has two accessable internal and one external drive, so no cache, recovery access, nor swap.
And also do not forget about the hardware incompatibility. Even if we manage to boot it, you will hardly be able to even make a phone call. Not to say use WiFi, or GPS, BT, or anything.
Click to expand...
Click to collapse
The i8910 community is great....this phone is great...a porting of android on this phone wuold mean a great number of donations!
cannot you use E\ (massmemory...8Gb or 16Gb) like partition?
Very Important Information For Beginners
/Introduction to Android for SD Cards
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~
I never tried S8500 Android, nor I have experience with Android handsets...
But I have stupid Questions.
Feel free to correct me, if I'm too stupid.
1.
I have never seen "optimized" aka custom ROMs...
Why?
Is it not possible to remove few Sounds, Pics... config files?
Maybe edit few settings...
2.
What is with such funny and normally easy tasks like this...
Some Logo or maybe start Animation or something like this:
http://forum.xda-developers.com/showthread.php?t=1396818
3.
Please read now carefully or ignore it.
Your choice.
Everyone is welcome to post something usefull...
if not usefull... who cares...
Free speech for everyone.
Best Regards
P.S.:
I'll start soon with Download files... and check few things...
As I am Android MEGANOOB.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
Click to expand...
Click to collapse
At the moment our Porting "Gods" not talk anymore with as stupid groupies...
I am not dumb enough to wait ... wait...
Why not use time to learn something.
I will starting now with lesson 1.
I will teach myself.
Attention. Lesson 1.
Downloading file from Internet... You need any space on HD and Browser...
Lesson 2.
After 10000 seconds I found this file:
ext2system.zip
Impossible task.
Zippo I know, but what is ZIP...
Sounds like .trip...
Oh, found something to decompress...
ZIP
WinRAR
Lesson 3.
New file ext2system.img
What I need to open this file...
Thanx in advance...
Best Regards
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
There is very useful page where You can check file formats and how to open it :
fileinfo . com/extension/img
Maybe you dont have to open img files.
http://forum.xda-developers.com/showthread.php?t=1212616
you can find all the files inside the img files in this thread hopefully. If the links still works.
adfree said:
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
Click to expand...
Click to collapse
You just have to mount it under linux (something like mount -t ext2 -o loop whatever.img /some_folder). It's an ext2 filesystem image.
But without the working kernel you can't do much... You can change the boot animation (it's stored in the system.img), or the boot logo with some tricks (you have to trick here as the bootlogo comes from the kernel, but it's pretty easy to change).
What do you want to acheive?
What do you want to acheive?
Click to expand...
Click to collapse
Good question...
I want to see files inside to analyze... learning.
This is what I do since 2006...
Playing with Firmware...
Maybe Android is cool...
NO idea yet. As no Android handset in use nor Linux on my PC...
But why not use time...
I am not smart enough to have enough Coding skills...
But my butt is fat enough... waiting for something is not really an option.
Best Regards
As Windows Fanboy maybe I'll try this...
http://www.howtoforge.com/access-linux-partitions-from-windows
Best Regards
My fault...
WinHex can extract files from ext2system.img
Later more...
Best Regards
as I've said many times, you can MOUNT the ext2system.img file from a Linux system using the following:
mount -o loop ext2system.img /some_dir
kind of same principle as here, except it's ext2 filesystem and not samsungs moronic rfs:
http://forum.xda-developers.com/showthread.php?t=751827
when working with android it's definitely preferable to do so on a Linux system, suggest you try installing Ubuntu on a Virtual machine.
I guess the reason a bunch of custom roms haven't popped up is because the lack of modem drive means they don't make it more useful, and we still have no idea how to solve problems like the sleep-power off or microphone crash.
If you want to have a go at modifying it however, the contents of the ext2system.img file are mostly from the I9000XXJPX firmware's "factory.rfs" file image, and many modifications that can be done to that (which is froyo 2.2 based) can possibly be made to work with this one.
note: do not attempt to use the recovery system for any of the "update.zip" packages available
I can see *.qmg Pics...
Are there any Viewer for Android?
I mean any Tool to see *.qmg on PC?
Interesting...
Around 1000 files in 50 folder...
biggest file is Swype.apk with 10 MB...
libicudata.so is with 6 MB biggest .so file in lib folder...
.so are ELFs...
Hmmm...
First I would remove Sounds...
Btw... few Fonts... in ttf...
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
adfree said:
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
Click to expand...
Click to collapse
But why do you want to remove stuffs from it? It's just storage space... I think you'd better install the SD based "release" on your Wave, it's easier to experiment with it. But I totally agree with nbates66: you will need Linux at some point to progress. I have Ubuntu in VirtualBox to tinker with Android.
the ".so" files are kernel module drivers(I am incorrect here, ".ko" files are kernel modules, ".so" files are some form of library), ".apk" files are android applications. The contents of .apk's can be extracted by using an archiver, I just checked using 7-zip.
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
you can also clearly see the shutdown animation stored as a set of .png files at /system/media/video/shutdown
the various audio files are all in the .ogg format in audio.
the 4 files inside "/system/firmware" are firmware files for a Galaxy i9000 camera NOT FOR A WAVE S8500 camera!!!
the bootsound and various settings are stored in "/system/etc"
"/system/bin" has various executable files used by the system, though they all are symlinked from "toolbox", this includes things like mv (move file), rm (remove file), and also executables for tasks during boot and handling wifi like "bootanimation" or "playlogo" and "dhcpcd"
if you really have to look at it from within windows, I believe Winimage can extract the contents of ext2system.img.
EDIT: wrong on ".so" files
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
Click to expand...
Click to collapse
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
the ".so" files are kernel module drivers,
Click to expand...
Click to collapse
Hmm. Maybe now more clear... if folder is named lib like library.
Then these are only parts... like DLL in Windows world...
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
But why do you want to remove stuffs from it? It's just storage space...
Click to expand...
Click to collapse
Why not... nobody will die or explode.
1.
Train my little brain
2.
Removing unnessary crap can help to free more RAM or other memory...
This is no secret.
3.
XDA is for sharing knowledge and to learn something usefull.
Not only download, without asking why...
Best Regards
adfree said:
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
Click to expand...
Click to collapse
well i'm afraid I don't know how to open the QMG's themselves, but all they contain are some sort of animation, the "playlogo" and "playlogos1" executables appear to be something non-standard Samsung created for their boot animations, to use custom animations I believe the workaround used is to rename the playlogos file to something else, and in it's place put a file that points to the android standard "bootanimation" executable, the bootanimation executable plays a boot animation from the "bootanimation.zip" file which is just a zip file with a set of images and a txt file that describes how it should play
here is some info regarding the bootanimation.zip: http://android.modaco.com/topic/338...nimationzip-futurama-bender-bootanimationzip/
adfree said:
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
Click to expand...
Click to collapse
well the QMG format I believe is some proprietary Qualcomm format (the modem in Wave phones which happens to be Qualcomm can be used for processing of various formats) but the (INCORRECT INFO).so file extension is used across a variety of systems for kernel driver extensions, and .so's are used in this case and for many android devices to allow manufacturers to install drivers without putting them into the Android kernel source (which apparently voids them the responsibility of publishing source codes) however .so's are NOT inter-compatible with different systems, IE bada .so files will likely fail if you attempt to use them on Linux kernel and vice versa, even Linux .so's for a slightly different Linux kernel version fail to load.(".ko" files are Linux kernel modules, ".so" files have been described as some form of software/native code libraries)
as for storage space on the "ext2system.img" file, it is generally mounted as read-only by the system and not modified unless your modding, the space in ext2system.img is normally not used for install of applications or for file/document/save storage of any kind.
sorry if this post doesn't make much sense, I in fact know very little about the inner workings of android, I mainly contributed slightly to modifications on init.rc:
http://code.google.com/p/badadroid/source/browse/trunk/nbates_files/xxjpxinitramloop030711/init.rc
EDIT: regarding the QMG format I just had a rethink and remembered that the Galaxy i9000 (from which this firmware came from) has a completely different modem configuration other than manufacturer (Qualcomm) yet the animation plays fine on Wave S8500, so possibly not the modem that is processing it in this case.
EDIT2: wrong about ".so" files
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?Can I upgrade os to android instead of bada?Please answer me I searched whole internet and didn't find any tread or post to say something about if this can be done or not.Thank you and have a good day.
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?
Click to expand...
Click to collapse
S5620...
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
This is Broadcom based...
...I searched whole internet...
Click to expand...
Click to collapse
Sure...
This is the reason why you think its easy to port to every device...
Your handset S5380 is also Broadcom based...
BUT this all on similarity with S5620 Monte....
S5380 NO known or confirmed Android solution yet...
Sorry.
If wrong answer.
Sorry.
Best Regards
I still hope that will appear something that can I upgrade from bada to android (
I still hope that will appear something that can I upgrade from bada to android...
Click to expand...
Click to collapse
Hope ever dies at last...
BUT why the hell you buy an bada handset, if you love Android?
Fastest working solution for your problem is.
Buy Android handset.
If you have time... much time.
Range between 0 and open end... (in years)
Then wait or maybe port self Android to your handset.
No joke...
There are several projects to port Android to unsupported handsets...
Why not start new project for S5380...
You need only NEW Devs... so you can recruit NEW Team members.
It makes sense ... user with S5380 or Broadcom knowledge like Monte team...
Again. For Broadcom I know only this:
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
Good luck.
Best Regards
Hi I wanted to see what you guys make of these apps. Does anyone know where I could get a reference guide specifically pertaining to such apps.
Even the "Performance control" feature found in most AOPK Custom Rom's have these weird terms.
Any help would be great.
Here's a picture for reference...sorta
WestxtseW said:
Hi I wanted to see what you guys make of these apps. Does anyone know where I could get a reference guide specifically pertaining to such apps.
Even the "Performance control" feature found in most AOPK Custom Rom's have these weird terms.
Any help would be great.
Here's a picture for reference...sorta
Click to expand...
Click to collapse
init.d -- a system that allows for running services at boot that are not run by the init.rc scripts
swap -- virtual memory. unlike ram, swap is stored on disk/flash storage, and as a result is slower but larger.
dirty -- memory that may need to be written to disk/flash. consider it used.
soft reboot -- a reboot that only restarts high-level system functions (essentially, the android part of android rather than the linux part)
couldn't tell you about the other options in android tweaker. see if it has a help file or similar.
hope it helps!
--ultraviolet
ultravioletnanokitty said:
init.d -- a system that allows for running services at boot that are not run by the init.rc scripts
swap -- virtual memory. unlike ram, swap is stored on disk/flash storage, and as a result is slower but larger.
dirty -- memory that may need to be written to disk/flash. consider it used.
soft reboot -- a reboot that only restarts high-level system functions (essentially, the android part of android rather than the linux part)
couldn't tell you about the other options in android tweaker. see if it has a help file or similar.
hope it helps!
--ultraviolet
Click to expand...
Click to collapse
Thanks! :good: that's pretty much what I'm looking for; leads that help me get my mind around it a bit more
iglo a109 problem
se.. all of those aren`t checked, when i tried to connect, in the photo, they are like that because it was i made a mistake when i created the print screen, so... i don't see how that's the problem, when i connect my phone and then after 2 sec it disconnects itself and starts charging