yashsingh1/xdaforums huggingface dataset:
[Android Software Development] XabdullahX:
Hi

.. Since i think the progress of connecting phone, put apk file on sd card, disconnecting phone, browsing phones sd card for the apk file for then to install it is annoying ..

So I've made a quick batch file to quickly drag and drop files to install ;)

Lets get started.

1- Download the attached zip. Should look something like this:

2- Extract using your favourite extraction program or using windows explorer.

You should now have a folder like this one:

3- Thats actually it :)!

What you can do now is:

Put the apk file inside the folder "Android app installer" and run the "Drag and drop files here" file (remember the ".apk" suffix)

OR

the easier way is to right click on the "Drag and drop files here" file and choose Send to, then click Desktop (As shortcut). From there. you can, any time, just drag any apk file from any directory to the "Drag and drop files here" file. and it will install it directly.

BEFORE YOU GET STARTED YOU HAVE TO DO THIS:

1- Enable USB-Debugging on your phone

2- Connect your phone to your computer

Log:

-V 1.1 (Filename: "Android app installer v1.1.zip"):

Closes after you have installed file. doesnt ask for filename after installation.

-V 1.0 (Filename: "Android app installer.zip"):

Released
[Android Software Development] britoso:
I have several batch files associated with .apk files (windows).

As an example, Installing an apk is as simple as right-clicking on the apk and choosing "install" :)
[Android Software Development] XabdullahX:
Cool. But well, this is me, sharing my piece of the gingerbread :)
[Android Software Development] tridge:
Very cool! Thanks for the tip!
[Android Software Development] drajax:
Thanz mate was really looking for something like this! Am new to android :)
[Android Software Development] Djembebi:
Thanx! Was looking for something like this (newbie at Android). Excellent!
[Android Software Development] Rickmasta:
Thanks for this, What I do is put it in my dropbox, and install it from the dropbox app. :D
[Android Software Development] xSunny:
Instead of all that you can just use a app call Awesome Drop drop your apk onto the phone using a browser no wi-fi or usb connection needed just ur usual 3g connection and thats it boom you got you apk just on the app on the phone click on the apk nd install in seconds =]
[Android Software Development] basslover:
Yo, thank you very much for this guide, you just made my month!! I was looking a way to do that for a long long time. The internet is full of lausy bad guides. I owe you one :)
[Android Software Development] gueyenono:
Device not found

Hey guys,

How do I get my device to be found.

My phone shows that it is USB connected on debugging mode and all by the application doesn't seem to know that.

Anything I should do?

Thanks.
[Android Software Development] o0adam0o:
Nice! I missed WM6 because of this missing feature. thanks
[Android Software Development] XabdullahX:
The drivers are properly the problem
[Android Software Development] hellboyborn:
WOW man that is some work :)

Thanks
[Android Software Development] PhxkinMassacre:
Or you could just download it strait to your phone and click it in the notification bar to install it :P haha nice program tho.
[Android Software Development] Megdroid:
very usefull program! thanks mate!
[Android Software Development] alfajeff:
thanks its nice :cowboy:
[Android Software Development] Tekn010933:
Thank You OP :good:
[GT540 Optimus Android Development] joostvhoek:
Hello,

My battery indiacator does really weard. When my battery is low it says 20 %. A while later it says 14 %, another while later it says 4 %. Now comes the strange part, a while later it says 14% % and another while later it says 20 %. It continius like that until it shuts itself down because of the battery.

I use the Quarx Black Edition 2.1.

Joost
[GT540 Optimus Android Development] TopGunBG:
I don't know about this problem, i never leave my phone under 30%

You should report this bug to Quarx in 4pda ;)
[HD2 General] twizted786:
I've had my phone for about 6 months. It was working fine, but lately it's been acting really strange. It freezes on boot and get stuck on the "Stick together" screen.

I've tried a HR, Update and it still persists.

I've wanted to flash a custom rom, but the phone also freezes on the boot loader so i can't even get the flash to follow through.

The one time i got the tmobile's latest flash update to work. It rebooted the phone and then the problem was still there. With it getting stuck on the "Stick together" screen.

A few times when i tried booting the phone, the phone vibrated 7 times and then turned off.

I've looked around the forum and searched for quite some time but haven't found anything. (It's a pretty big forum so i may have missed it). I will continue to keep looking but if anything has a fix or can help me please do.

Thanks!

(Glad to finally be part of this community)

-Raymon
[HD2 General] juggs:
Sounds silly but try these two things.

1. There are some pins on the battery that can be easily bent. Inspect them to make sure they're ok. There are usually other symptoms with this though, such as it won't take a charge or won't start at all, just thought I'd mention it.

2. Try it without the SD card in.
[HD2 General] twizted786:
Hey, thanks for the reply!

The phone charges fine with the usb cable. It's at full charge right now actually.

I took out the sim card and sd card when i did the HR and before i put those back in, the phone still froze on boot.

Really not sure what's going on, I'm going to try flashing it again when i get home. But last time i tried, it got stuck at 0% and then my phone froze, was scared it was going to brick, but i don't think it did.

Any other insight would be great, i really hope to resolve this issue.

If any other information is needed, please don't hesitate to ask. I can provide as much as possible to get to a conclusion.

Thanks,

-Raymon.
[HD2 General] KOCTA:
I got the same problem -- freezes and 7 vibrations before it. I made formatting with mtty (task 29 and task2a), it didn't help.

Anybody knows about 7 vibrations signal? Is there leodiag like blackdiag for HD?
[HD2 General] ashasaur:
That 7 vibrations HAS to mean something...but i'll be damned if I know what. People in both Leo sections keep saying that their phones vibrate 7 times then shut off, and I don't know what that really means....some investigation is in order!
[HD2 General] twizted786:
Just got done talking to t-mobile, my replacement is on it's way, still very weird.

Would love to know the solution to this.
[HD2 General] KOCTA:
Please tell me can I replace my faulty HD2 from T-Mobile? I bought it in Frys without contract and used it with another provider. I never had a T-Mobile contract.
[HD2 General] kotfarekot:
same here, bought the phone on Ebay and i live in Albania.

i have the 7 vibrations and then i have to take off the battery , leave the phone cool down so i can use it again for the next 10-20 minutes and then back to the vibrations
[HD2 General] abofihmi:
I have the same problem, mostly when i used GPS application, the phone reboot then vibrate one on th esplash screen then 7 times and freeze, the solution for this is to remove the battery for 10-20 minutes, pray and put it back, it is very annoying. I have this problem with ROM including the stock ROM.
[HD2 General] quwon:
hd2 freezes on BOOT!!!

try to take out the sim and leave the SD card in you will notice that it will work much better and get past the stick together screen ..mine does the same thing i think i may theSIM card but who know??
[HD2 General] KOCTA:
Nice suggestion, but totally useless.

I think these 7 vibrations means fault in NAND operation, but didn't find any approves.
[HD2 General] Pbeer:
I've this problem too.

7 vibration and freeze.

I've try update new radio, task29, new custom rom but nothing better.

Did anyone found any solutions, Please share.

Thank you.
[HD2 General] benjat:
mine got same problem.. i put the hd2 in freezer (without battery) for 3 minutes, then take it out.. put battery.. and my hd2 can start.. but after a while, when the cold is gone.. my hd2 will off it self.. hehehe
[HD2 General] hayyaan:
Any solutions?

I have the same symptoms, though the vibrations aren't that frequent, as much as stucking is..

I am not in a position to get a replacement, what do I need to fix?

This seems to be a heating problem, the freezer solution seems to work
[Galaxy S I9000 Q&A, Help & Troubleshooting] gil80:
Hi all.

Since I installed K7 kernel by hardcore (great job by the way), I seem to have lost the list of installed apps when I go to the download section in the Market app. I only have about three rather than 14 apps.

Is there a way to restore them or another way to view if these apps need update?

Thanks.
[Galaxy S I9000 Q&A, Help & Troubleshooting] snapper.fishes:
Do you use titanium backup? You can use that to reset market links.

Otherwise, try clearing your market cache in settings->Applications -> Manage applications
[Galaxy S I9000 Q&A, Help & Troubleshooting] gil80:
Thanks! Clearing the data solved the problem. Do you know why it happened in the first place?

p.s. - I don't use titanium backup.
[Fascinate General] Alexgsp:
I saw a tweet from jt1134 a few hours ago regarding voodoo5 working for the fascinate with cwm support. Can anyone lead me in the right direction to find this?
[Fascinate General] NKT:
http://webchat.freenode.net/

#samsung-fascinate
[Fascinate General] Alexgsp:
awesome, thank you
[Fascinate General] jadambpharm:
i recommend not installing it quite yet. just wait until some things are ironed out. from what i can gather, there were some people earlier on in irc with issues booting to cwm.
[Fascinate General] adrynalyne:
Cwm works on my voodoo5 hehe. It has since last night.
[Fascinate General] bL33d:
does it feel faster then stupidfast? i dont care about quadrant.
[Fascinate General] Daswolven:
This is pretty insane fast, and smooth.
[Fascinate General] Alexgsp:
Voodoo5 along with DJ05 and modem is like having a brand new phone. Very noticeable increase in speed. Not sure (nor do I care) about the quadrant scores. Highly recommended, but install with caution and always ALWAYS backup data. Voodoo is a pain to fix and you most of the time lose everything if it fails.
[Fascinate General] mexiken:
Battery life, thats the crucial part....

How is it on Voodoo5 ????
[Fascinate General] PhoenixPath:
Quadrant is getting high 1700's (1750-1790).

Seems rock solid as of build 1124 jt handed out tonight. CWM works...through the reboot mod (DJ05), but Rom Manager is being a little ***** about it.

No big, just flash directly from CWR....which is red now.\

So far, so good. This and DJ05 is pretty much all we needed. The phone is rock solid and smoother than ever now.
[Fascinate General] s44:
What changed between 1123 and 1124?
[Fascinate General] mexiken:
Check github if you're really that interested. Should be under the test folder, if memory serves me correctly....
[Fascinate General] shorto85:
Do you need to have DJ05 to update to the latest version of Voodoo?
[Fascinate General] tkdboi:
yes..............
[Galaxy S I9000 General] deathst:
supercurio has reported:

SpeedMod based (Doc's ROM and others) and every other Universal Lagfix corrupt badly /system

It means that as long as they don't restore a /system with Odin, they're stuck on kernels using broken mount options.

If you want to verify, try to boot a stock Samsung kernel. Depends on how much it is corrupt it will boot, or not, or with unexpected errors

Want proof?

http://bit.ly/bq2oXg

Highlighted line is using wrong and corruption mount points

lack of check=no which causes corruption. Every Samsung mount uses check=no

Second Issue:

Even with NO RFS Config selected... RFS is still used in /system mounts... means phone are slowly Dying of corruption..
[Galaxy S I9000 General] zacharias.maladroit:
please fix linky - I want to know more about this:

thanks !
[Galaxy S I9000 General] deathst:
Fixed XD Sorry for that
[Galaxy S I9000 General] RyanZA:
Not 100% sure on this, since I have not used or looked at sztupy's lagfix very much, but that line you are pointing out is not a problem.

If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.

The following line would then mount it correctly.

Basically, this seems to be totally false. More evidence please. :D

EDIT: Okay, OP was updated with better information. Lack of check=no means that the FAT32 check *may* be running on the /system, which would cause corruption.

Probably a good idea to confirm if the filesystem check is actually happening though!
[Galaxy S I9000 General] titooo7:
In case that supercurio is right (I hope he’s not for obvious reasons), I guess that it wont affect to users that are running harcore kernel without any lagfix applied, right?
[Galaxy S I9000 General] NetCopAD:
That is correct, however /system is not EXT4, but RFS.
[Galaxy S I9000 General] z4ziggy:
good catch.

but im sure sztupy can fix this with a small patch, although i agree the priority should be flagged 'critical'...

as always, good work supercurio :)
[Galaxy S I9000 General] RyanZA:
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.

It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!

If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
[Galaxy S I9000 General] Mopral:
Maybe I am wrong but there is no settings in sztupy's kernel which convert /system

Lagfix only convert /data, /cache and /dbdata
[Galaxy S I9000 General] deathst:
Yeah i just looking further system is still mounted as

/sbin/busybox mount -t rfs /dev/block/stl9 /system - Possible corruption happens here without check=no
[Galaxy S I9000 General] hardcore:
Yes this would affect the speedmod kernel as well, if it indeed is a problem. ULFK does not change /system in any lagfix scheme. So, its always mounted as rfs, apparently "wrongly".

I am testing an updated speedmod (shall we say, K9-pre) with the changed mount option. At the very least it should do no harm. And trying to get in touch with curio but over at IRC they say he's probably sleeping now after a coding binge! :p

Hmm and I found a minor 'bug' in the post-init.sh that was not properly setting /system to read-only after its done.... mainly because the logfile is being written to /system!
[Galaxy S I9000 General] RyanZA:
Method to test if this is a problem:

Replace your fsck_msdos (this is the only fat32 fsck in the filesystem) with a script file. Inside the script put the following:

echo "$?" > /somewhere

Then reboot your phone a lot of times. If the check is being called, then you will now get a log message instead of the check happening.

Will also affect checking of /sdcard though.

As far as I know though, fsck_msdos is only ever called by vold, and therefore check=no in /system may not have any effect, and this could be a false alarm. Anyway as hardcore says, can't hurt to fix it! :D

EDIT: Just wanted to add that running fsck_msdos even once on my /system (using the awesome pre-init scripts from z4mod!) made my phone immediately unbootable (damnit!). Not a big sample size, but I believe that if this was really a problem, we would be seeing many many reports of the sztupy kernel breaking devices! Since we don't have these reports, I'm gonna put this myth down as 'likely to be busted soon!' :)
[Galaxy S I9000 General] deathst:
Well the intention of this post is to show the issue for it to be fixed :D So let hope it does not do too much damage :S
[Galaxy S I9000 General] RyanZA:
Looks like this may have been a bit too sensationalist! ;)

More checking, less guessing is always good! (And I could learn a lot from that motto myself!! :) )
[Galaxy S I9000 General] deathst:
Well we could check it by running it on RFS and reboot alot of time and then flashing a original Kernel :P
[Galaxy S I9000 General] XxDrAg0nxX:
yeah when i saw that post my balls shrank.. thinking that by precious phone may be 'slowly dying of corruption' :rolleyes:

not like there is a repair file system tool to use :p
[Galaxy S I9000 General] hardcore:
/dev/block/stl9 /system rfs ro,noatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0

K8, u had a short life... looks like its time for K9

Important thing to note is that this is the way stock kernels mount /system: read-only, and we see the option log_off too.

The thing I noticed this way is that if u do a mount -o remount,rw /system and modify stuff... it may corrupt /system. All modifications to /system should then ideally be done via CWM or update.zip only.
[Galaxy S I9000 General] RyanZA:
Why would flashing an original kernel make a difference? Original kernel will mount /system in exactly the same way, so any corruption in /system would be seen on both the original kernel and on the sztupy kernel before the reflash.

Reflash or not has nothing to do with it.

Only method would be to reboot (or remount) enough times to hit the unclean filesystem check parameter (which rfs might not even have?), or wait long enough for the unclean check time to elapse. Not really sure how you would check what this parameter is - maybe tune2fs could be used? RFS is a bit of a black box! :D
[Galaxy S I9000 General] deathst:
It may mount correctly with Original Kernel..If it does quite a damage to the /system the phone might report errors even it is will not be able to boot.
[Galaxy S I9000 General] RyanZA:
No, that doesn't make sense. The difference between stock and sztupy is that sztupy's mount is telling the system to try and check the drive. If /system works fine in the sztupy kernel, it will still work fine in the stock kernel, because the only difference is that the stock kernel DOESN'T check. Well, testing so far seems to be showing that neither check, and the check option does nothing at all. :P
[Galaxy S I9000 General] Idan73:
I don't know if this is related but what is happening to me is that some videos and files in general disappear after reboot from external sd. Actually filename is still there but 0 size then sometimes even filename is gone. thought it was my memory card dying but could be related to this as well.
[Galaxy S I9000 General] kenkiller:
Can't be....how is /system linked to external sd?
[Galaxy S I9000 General] AnnihilatorSC:
A-ha! So that's why! (it's mounted rw instead of ro) :)

Personally I wouldn't mangle /system with log files, I'd rather toss them onto the sdcard.
[Galaxy S I9000 General] RyanZA:
Completely and utterly unrelated to this - don't worry. ;)

This is unfortunately normal behavior when pulling the battery out of the device - vold (the thing managing sdcard and external sd card) seems to have some serious issues imo. I have had this happen quite a lot too in my battery pulling tests. :(

When you start your device up, you will see 'scanning media' or whatever in the notification bar. If you pull out the battery or force reboot while this is happening, the file currently being scanned will often have 0 bytes on the next boot. Awful awful. Anyway don't pull the battery out of your phone! ;)
[Galaxy S I9000 General] sztupy:
Oh, forgot to fix that a month ago ... :)

for the others:

1. I don't know how severe this corruption is. Except from supercurio I didn't heard any problems about this.

2. the only real corruption I've found is when an rfs partition gets mounted as vfat (and mount -t auto will always mount an rfs parition as vfat).

3. there is no fsck.rfs, as it's included in samsung's init script (it gets exdecuted on the line exec apply_disk_policy)

4. samsung mounts /system as ro,check=no and after that it WRITES to the /system partition (wtf?)

From this, and if this corruption thing is actually true, I think that there are some strange things happening in the "exec apply_disk_policy" part, and that's where the corruption (might) happen. Or it can also be, that /system never gets checked on my setting as it's not actually mounted as "ro". (If _not_ mounting a filesystem as "ro,check=no" will corrupt it, then rfs is probably more flawed than anything else in the universe), or it can be that fsck.rfs gets run, but it corrupts /system as it's not mounted ro (fscking a device while it's mounted rw is bad for health). I don't know, never encountered this problem (mainly because I stick with ULTK).

If using the mount option ro,check=no solves this issue then only one question is remaining: WHY DOES SAMSUNG'S init.rc WRITE TO /system IF IT'S MOUNTED ro? (My script remounts /system ro after init has run, and not before running init, so init.rc can do it's modifying in /system)
[Galaxy S I9000 General] stuclark:
I don't know if what I've had is this /system corruption bug or not, but essentially I had a problem whereby newly installed apps wouldn't show up in TW launcher. I had to FC TW launcher or kill its data, to get apps to show up. (then the next app installed wouldn't show up and so on).

I also managed (with a fair few MMS) to end up with a subtly corrupt messaging database, which would cause the little red notification dot to either not show up at all when a new message was received, or to continue showing when all messaged had been read. (again, FCing TW launcher would fix the issue for that one time)

... does this sound like it could be related to the possible /system bug, or is it more likely it was related to using JFS based lagfix? (as I previously thought)
[Galaxy S I9000 General] RyanZA:
Thanks for the insight. Also you might not want to start off with assuming that it is corrupted - it really doesn't seem to be causing any corruption - seems to just be speculated at this point that leaving out check=no would cause corruption.

Tests I've done seem to indicate that doing a FAT32 fsck on /system will probably make the device immediately non-bootable - and I don't think that's happened to anybody using your kernel yet?

As far as the 'exec apply_disk_policy' goes - the 'exec' function in android init is a no-op - it doesn't do anything. So it's probably just something Samsung was trying to do without realizing it doesn't actually run. It's a bit counter-intuitive on android init's part. ;)

As far as the writing while read-only -- no idea. Must be some reason or trick involved, because trying to write to read-only RFS FS doesn't work, even when root.
[Galaxy S I9000 General] RyanZA:
Not /system related -- the issues you are specifying are /data or /dbdata related.

So it was probably JFS.
[Galaxy S I9000 General] stuclark:
...that's what I was thinking, but merely deleting /data and /dbdata didn't fix it; I had to do a reflash
[Galaxy S I9000 General] z4ziggy:
i couldn't find any write to /system in the init.rc. where does samsung 'writes' to /system ?
[Galaxy S I9000 General] jeebspawnshop:
I find it... odd... that recently supercurio has been making a lot of bold claims about how certain things are wrong, corrupt, and so forth.

I mean, my grandfather does the same thing when he's had too many whiskeys during a soccer game, but I don't think supercurio is my grandfather...

Anyway, he also doesn't back up any of his claims at all.

So I'm just writing this in the hopes that he might actually come and provide solid evidence for ANYTHING he says.