yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] dali rami:
Requirements: ANDROID 2.1 +

Overview: Customizable Fingerprint Lock that actually locks your phone!

Customizable Fingerprint Lock that actually locks your phone!

Get the only fingerprint scanner lock that actually works as a lock screen and uses your own wallpaper! Simply run the app and your normal lock screen will be disabled until you exit the app.

This app includes large, visible time and date and Customizable Features, including Themes and Fonts.

Your own wallpaper will be shown behind the lock screen, even Live Wallpapers!

Invalid identity scans will be denied access to prevent intruders. However when you scan your own thumb print, you will be granted access quickly and easily.

Access the settings menu to customize and personalize the Fingerprint Lock screen to your liking, including options to disable sounds, vibration, show or hide the date and/or help button, to change themes, or to change the font of the time and date.

- Actually locks your phone!

- No notification bar and button presses are disabled! (including Home and Back buttons)

- Large, easy to read Clock and Date!

- Many fonts and themes to customize your own personal lock screen!

- Shows your own personal wallpaper, including Live Wallpapers!

Note! - This app does not actually scan your fingerprint. That is impossible. It works great as a lock screen, but is great for pranks, jokes, and fooling people. There is a hidden button that will toggle access to the phone. After toggling access to allow entry, you can either scan and be granted access, or you can enter the settings menu. This is all explained in the app by clicking the "Help" button. I am not liable for any actions involving the use of this app and can not guarantee that no one will be able to access your device while using this app.

download from here click here
[Android Apps and Games] mariosraptor:
Mirror please.
[Android Apps and Games] sirholm:
Bad link
[Android Apps and Games] Markuzy:
I suspect OP is attempting to distribute malware.

His post description is copy pasted from here:

https://play.google.com/store/apps/details?id=com.nb.fingerprint.lock.free&hl=en

This is a free app from the Play Store.

No need for suspicious 3rd party links.
[Android Apps and Games] Dayfid:
The zip contained two links:

https://play.google.com/store/apps/details?id=com.nb.fingerprint.lock

http://depositfiles.com/files/7awa7kh4h

I assumed he didn't post them due to not reaching the required post limit to be allowed to post links so there they are.
[Android Apps and Games] dali rami:
thank's guys for posts
[Samsung Epic 4G Touch] Aganar:
You'd think I would have figured this out by now, but having been a CM9 loyalist since day one I never bothered to learn what any of the others constitute beyond looking at what their acronyms stood for.

So my questions are as follows:

1) What exactly is the difference between Android Open Source, Android Open Kang, and CyanogenMod? My initial understanding (and this was when I followed the stuff more closely on the HP Touchpad) was that AOSP was built directly from the source Google released, CM9 took it and tweaked it for the specific device, and AOKP piggybacked off that to further tweak. I'm not so sure anymore.

2) Who's developing what? I thought the three branches were distinct but then I see sbrissen and chris seemingly making commits to both CM and AOSP, so I'm a little confused by this.

3) What's receiving the most development right now? I was on CM9 Alpha 6 for the longest time. I was debating from moving to a CM9 nightly or a CM10 beta, but the separate thread for AOSP Jellybean made me wonder what exactly that offered vs CM10. I was tempted to stay on CM9 just because it's been around longer but I haven't seen any "official" updates in awhile (i.e. ones on the e4gt.blogspot.com site--I'm sure the nightlies are official in some sense). Is it still even being worked on by the CM team anymore or have they all jumped ship to CM10 development?

As of right now I just flashed the FH13 ICS Stock onto my phone to see how that works out. When the other roms reach a better level of stability I'll probably move back to one of the CM's, but I wanted some idea of what I'm flashing before I do.

Thanks in advance.
[Samsung Epic 4G Touch] GiantJay:
Aosp is pure android like on a nexus.
[Samsung Epic 4G Touch] Aganar:
Okay...half-answered one of my three questions...and I kind already knew that.

Thanks anyway.
[Samsung Epic 4G Touch] GiantJay:
Google it. You will get your answers. Most pointing to the xda forums.
[Samsung Epic 4G Touch] Vash403:
Cm9 is still being worked on. Chris41g is working on making it officially supported. His nightlies are so much better than alpha 6. I'd recommend upgrading to a nightly if you are on a6. Sbrissens jb aosp is also amazing as well. For me the jump from his alpha 4 to 5 was a huge difference in terms of battery life. I haven't had any los on it or any other problems on it. Recently on one of the alphas (idr which one, probably the latest) he added the status bar toggles so that was a huge plus as well. It still doesn't have the customization of cm10 but it's still amazing.
[Samsung Epic 4G Touch] stank656:
cm10
[XPERIA X10 Q&A, Help & Troubleshooting] ratmkicksass:
So Ive been on M&M Miui Rom for the past 6 months with no problems. Just this morning tho, I received a call, and as soon as I hung up, phone froze. No biggie... Pulled out the battery, pop it back in, and it wouldn't boot. It gets stuck at the boot screen logo (i was on ckernel at the time) and in about 5 secs screen goes blank and and WLOD appears, and goes into a boot loop. I then flashed other kernels but with no luck (I have unlocked boot) I also tried to connect it back to PC Companion but wont read it. I also flashed the locked boot tft and pc companion still wont take it Any ideas on what I can do?!!?
[XPERIA X10 Q&A, Help & Troubleshooting] THeLogiC:
Why don't you try to get back to stock firmware by flashing it through flashtool.?

Sent from my X10
[XPERIA X10 Q&A, Help & Troubleshooting] Dzufa:
Or try to reflash Rom via Recovery or Flashtool.
[XPERIA X10 Q&A, Help & Troubleshooting] Toledo_JAB:
Please read up on recover from soft brick.

Normally flash 2.1 stock and go from there. If flashtool won't find phone, start flash process without connecting phone until prompted then remove battery and replace while holding the back button then connect to pc

~Jaramie

from my LT28at, rooted and eating an Ice Cream Sandwich :D
[Xoom Q&A, Help & Troubleshooting] Musicmaster:
Hello -- I recently flashed my Wifi Xoom to the latest 4.1.1 ROM using Clockwork 3.2

I did the wipe div / wipe cache and installed JellyBean.

In addition, I did the "factory reset" within ICS before formatting.

When going into storage options on my fresh xoom, it showing about 15GB being used and 16.xxGB free. Not to mention my files are still on the Xoom. How do I actually reset it??
[Xoom Q&A, Help & Troubleshooting] d3athsd00r:
fastboot -w
[Galaxy S II Themes and Apps] Phil3759:
FAQ / Updates

To be completed
[Galaxy S II Themes and Apps] Phil3759:
Done

Any feedback and ideas about the code is welcome
[Galaxy S II Themes and Apps] The-Droidster:
Thank you so much for ur work! Sorry I'm out of thnx today! will surely thank u 2morrow!:p

Been looking for this a long time!:victory:
[Galaxy S II Themes and Apps] Phil3759:
Please give feedback here after you try it
[Galaxy S II Themes and Apps] Phil3759:
Updated instructions for the beginners
[Galaxy S II Themes and Apps] vagsvag:
Tried, everything ok. Thanks

Sent from my GT-I9100
[Galaxy S II Themes and Apps] nayak.aj:
But why ?

I m sorry to question you on this, but why would one want to remove busybox ? given that there are 600+ symlinks .. but what is the benefit / effects of removing it or NOT removing it ?

Knowing this would educate people as to why people people should do this... its a solid noob question which should be added to the OP FAQ/ description if you ask me :) ... no offense :)
[Galaxy S II Themes and Apps] Phil3759:
When you install busybox in a folder, it creates about 328 symlinks in install folder (xbin often). Most cwm roms add to this a symlink for all commands to the bin folder.

Now, each busybox version comes with its active applets. You can end up with shortcuts installed by a previous version but that are not supported by the actual version.

At worst, some apps can have unpredictable behaviour. If link is removed, app will just end with a not found (also causing impredictable behaviour) . Actually, i never had any of these supposed issues, but why keep non working shortcuts in your system path?

This script is for people that tested so many web installers and busybox versions mainly. Flashing a full ROM in odin will clean it too.

Personally, when I change busybox version, i would use it to clean previous install. Why uninstall a program and leave hundreds of files?
[Galaxy S II Themes and Apps] karendar:
So to resume, this script exists just because it can be done and because someone, somewhere, somehow may someday need it. :D
[Galaxy S II Themes and Apps] ngagephone:
perfect example you install a Rom it comes with all applets installed you check the busybox version and its old so you wish to remove all applets then install new busybox.
[Galaxy S II Themes and Apps] Phil3759:
When I uninstall an app, I hate when it leaves folders and files around

And busybox around installers can leave up to +600 of such files in just 2 folders, and you can install elsewhere too

Now, a clean approach is to install busybox in a custom folder and add it to path. No trash over the system. However, some apps look for it selectively in system folders and not in path
[Galaxy S II Themes and Apps] shoey63:
Why would anyone want to leave 600 files on their phone if they dont need them?

Plenty of people in plenty of places with issues arising from installing busybox from market many a day will need it;)
[Galaxy S II Themes and Apps] seitentaisei:
This will come handy in the future. Thanks for this!
[Galaxy S II Themes and Apps] Invalid_GR:
Hey congrats on your work.I have a problem if you can provide help:i flashed the uninstaller via stock recovery but after phone reboot wifi couldn't obtain ip adress.

Any help?
[Galaxy S II Themes and Apps] Phil3759:
Can you attach the file here

/sdcard/bb-uninstall/bb-uninstall.log

Also, under that folder you have a backup of each deleted file, so keep it so you can restore if needed

Sounds like some files in system/bin were removed wrongly, but I doubt my script would do it as I tested it fully and I even include the specific temporary busybox needed for the script

Post the log file so I can see
[Galaxy S II Themes and Apps] Invalid_GR:
First of all thanx for the quick responce.Here is the file you asked :

https://dl.dropbox.com/u/98804712/bb-uninstall.log

(sorry xda didn't allow me to upload a log file so dropbox it is)
[Galaxy S II Themes and Apps] Invalid_GR:
Once again thanx for your help.Yeah i used a market bustbox installer..Before i try anything could you please make clear what exactly i must do in the last step when you say "open terminal" sorry if it's noob level question..
[Galaxy S II Themes and Apps] Phil3759:
Download this application from market and install it:

https://play.google.com/store/apps/details?id=jackpal.androidterm

Then, open it (it is the terminal)

Then, you type the 2 commands line in code I told you

Do not forget to mount /system as rw in root explorer and set file permissions like described above
[Galaxy S II Themes and Apps] Phil3759:
Please do not ask support requests over PM, that way others can benefit from it.

If I do not answer in thread, you can always remind me by PM

for a free mount solution:

in terminal, type

su
toolbox mount -o remount,rw /system

Then follow steps above, root will stay of course

Reboot phone when done to remount ro without further commands in terminal

Please give a feedback later if it is fixed for you
[Galaxy S II Themes and Apps] Invalid_GR:
Ok you are right my bad..Once again thanx i'll give feedback as soon as possible.
[Galaxy S II Themes and Apps] meatlover:
Is it possible to describe. For what this program mean to be? But Thank you for creating such an app
[Galaxy S II Themes and Apps] Phil3759:
Page 1...
[Galaxy S II Themes and Apps] Invalid_GR:
I tried it but when in terminal i get a no such a tool message after i type the second line

"toolbox sh /system/bin/toolbox_fix.sh"
[Galaxy S II Themes and Apps] Phil3759:
My error

su
sh /system/bin/toolbox_fix.sh
[Galaxy S II Themes and Apps] Invalid_GR:
Ok done and rebooted without any problems.

One question before i use the uninstaller i am on stock rom but i use your kernel (PHhilZ-cmw6).Will this be a problem?
[Galaxy S II Themes and Apps] Phil3759:
Many thanks for the confirmation. So, now your wifi is back?

If yes, I will edit the uninstaller to preserve toolbox symlinks when they were hijacked by some busybox installers

About my kernel and also my root scripts: no risks at all, I do not symlink busybox to /system/bin
[Galaxy S II Themes and Apps] Invalid_GR:
Yep everything works fine many thanks for your help!
[Galaxy S II Themes and Apps] rocketero:
I was looking for an installer of the busybox symlinks, and this thread made that purpose, thanks @Phil3759

I haven't tried yet but for @Invalid_GR input seems it's the right script. I won't be using the zip but just the bb-uninstaller.sh script as I have is a generic tablet with ics 4.0
[Galaxy S II Themes and Apps] appagom:
Nice,

I used to do it with this:

adb shell
su
mount -o remount,rw -t /system
busybox ls -al /system/bin /system/xbin |busybox grep -e "^l.*->.*[ /]busybox$" | busybox awk -F" " '{print "/system/bin/"$9}'| busybox xargs busybox ls

Posted originally in shw-m110s thread.

Change the final ls to an rm when you're satisified.

Of course I don't do any backup or checks(other than using the ls). Just a quick one liner that takes care of it.

Edit: I say "used to" because mostly I don't ever make the symlinks anymore.

Edit: I undid my cleanup and just added a check for a link. " ->" to help a little.

There are potential pathologies with filanames that link to busybox AND contain a space as Phil3759 pointed out below.

Use the ls first to check results.
[Galaxy S II Themes and Apps] Phil3759:
good one :good:

But you'd better use find -type l

ls is a bad thing to proceed file names, if you ever get spaces...
[Galaxy S II Themes and Apps] appagom:
It's not highly sanitized. However, it only process lines that contain "busybox" so the only possible corner cases are files named like "Phil3759_busybox_uninstaller" or as you say files linking to busybox that have a space in them.

The failure mode in the first case is I think to delete Phil3759_busybox_uninstaller (oops, but I didn't need it anyway ;) ) and in the latter would be to do nothing in all but extremely pathological cases, but what busybox applet has a space in its name? Simply adding "-> busybox" (edit better yet -w) to the grep should solve the first problem (which I always knew about but didn't care, but I should edit it) and also guards against a pathological case not worth describing for the latter problem. I don't believe the space problem is ever a problem actually. Busybox and its applets are a core linux tools and spaces violate core linux file naming traditions, but yes sanitizing around that is harder, probably requires find, and probably requires looping.

There are still (with the -w) potential crazy cases like if you have files linked TO a file named "Phil3759 busybox" with a space in it. Or if you have two files

like "fake busybox" and just "fake".. then "fake" might get deleted. I worry about that stuff in scripts I write to routinely process whole hard drives where I find all kinds of crazy corner cases, but it doesn't really bother me here. As a quick one-liner with a way to test it first, this gets the job done fine.

---------- Post added at 01:43 PM ---------- Previous post was at 12:54 PM ----------

By the way busybox tools are not full featured as you know. The real find can do the whole thing all by itself very easily especially with use of -lname. Without the use of -printf though there's probably no way to replace ls with find here either. Now that I think about it, that was the frustration I had when I came up with that line resorting to awking ls.
[Galaxy S II Themes and Apps] Phil3759:
yeh, find is very limited in busybox, but it works well in my script if you look at it, that -type l is of

Also, a last case where your script (mine too as I did not add a fix for exceptions) is some market installers hack the toolbox shortcuts to link them to busybox

Once you delete them, people loose wifi access and some system vital parts

My script doing a backup has some room, but for a noob it is complicated to restore from them
[Galaxy S II Themes and Apps] appagom:
I'm sure your script is great including its use of find (which is almost always preferable to ls). Using find in a one liner is hard with its limitations though. Looping over find -type l results and applying readlink and conditionals, and well writing a real script allows all kinds of great checks.

I've kind of wondered if some installers wouldn't do exactly what you say they do with toolbox links. That's among the reasons I never used the market installers and tend to use the the command line and brain oversight instead. I like that in most of your work you place a good bit of emphasis on proliferating information over just handing out candy. It's far from always the case here.

I would think you'd need to do the backup BEFORE the market installer hacks the toolbox shortcuts and that responsibility seems to me rest solely with those market app developers. If you actually manage to clean up after that mess somehow, that's great.
[Galaxy S II Themes and Apps] Phil3759:
I posted a workaround a few pages back since a user had the issue after cleaning with my script, coming from a Market Installer

I never found time to add it to my script, it is easy, just a few lines to skip these links and restore them to toolbox
[Galaxy S II Themes and Apps] appagom:
yeah, ok.. just relinking the list of them works sure. It's unlikely any ROM changes it and the list is useful.

Just for kicks I fixed the regex up right. Now I think the only corner case is the one you mentioned, applet names with spaces in them. It's probably as safe to assume those don't exist as it is to assume the list of toolbox links.
[Galaxy S II Themes and Apps] SnarfSnarf:
ifconfig missing

How do I get ifconfig to show up in busybox.

I tried the uninstaller.zip on the first post and then stericson busybox apk to update. Cleared cache at recovey mode. It just gets written over by the kernel or something at every reboot. Keeps going back to busybox v1.20.2-jb with no ifconfig applet. (Using the latest Neatrom 4.1.2)
[Galaxy S II Themes and Apps] appagom:
Re: Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]

I don't know about your busybox installation but if busybox is available at all in a reasonable place you can always use it like:

busybox ifconfig

Even if the ifconfig applet isn't linked or just

busybox

to get a full list of applets. Mine has ifconfig. If yours doesn't you should install a different one.

Ah... just understood maybe. As I recall some root kernels install busybox from the initramfs into /system... maybe writing over what you are trying to do. When I played with making a root kernel I made that behavior optional and one shot but I can't recall if that's standard, probably not. If that's happening... not much you can do. You can install in alternate location so it doesn't get written over but then you'll need to call it with the full path name or have a startup script copy it.. Or use a different kernel or ask the ROM dev for solutions.

---------- Post added at 02:30 PM ---------- Previous post was at 02:06 PM ----------

Actually here is another great idea. Install the busybox you want and then use chattr +i to make it immutable (even root cannot overwrite it without unsetting that first) before rebooting!
[Galaxy S II Themes and Apps] Phil3759:
because /sbin is in the path before /system/xbin and CWM has busybox integrated as entire part of recovery

Just set your sh path in script to the busybox binary you want
[Galaxy S II Themes and Apps] Phil3759:
Re: Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]

You do not have to mess with these and in anycase, they will be restored on boot. If you look at them, you will see that any part messing with busybox is commented out. These are dead code

Just search how to set your path and own scripts to use /sustem/xbin busybox of your choice
[Galaxy S II Themes and Apps] redemption024:
thank you so much. I've been looking for things like this to remove 'em busybox temporarily. I don't wanna do a full flash through odin or anything, too lazy, and that's where you comes in. thank you again.
[Galaxy S II Themes and Apps] elfaure:
Hello-

I have manually symlinked the busybox applet zcip to the wrong directory(/bin/busybox) which does not exist! How can I remove this symlink and recreate it to the right directory (/system/xbin)? I linked it with "ln -s /bin/busybox zcip ./zcip" and after mounting /system rw and cd /system/xbin when I try "ln -s /system/xbin zcip ./zcip" it fails with "Link failed, file exists". How can I fix this?
[Galaxy S II Themes and Apps] Phil3759:
unlink or rmdir
[Galaxy S II Themes and Apps] Phil3759:
Yes, if unlink is absent, you can use rm. End result is same for files, but for dirs, you would need rmdir
[Galaxy S II Themes and Apps] tiazek:
All right, good tip. Should I change anything in the toolbox fix script then? It worked fine fine to me. It seems that all those lines refer to files only, not any folders that I can see.

Also, thank you very much for this work!! I was tired yesterday and I forgot to thank you for this script because it was useful not only to fix the problem but also to understand the cause. :)
[Galaxy S II Themes and Apps] elfaure:
Well that only partially worked. Unlink worked to remove the existing symlink, but the file remained. Rmdir just removed the erronious symlink to the non-existant directory but not the file. I think rm is what I should have used to remove the file itself but I did it manually with root explorer.

My goal was to relink czip to the correct location. Your method did unlink it correcty, but would not allow me to relink it to a new location because "Link failed, file exists" error. I had to delete the czip file (created from the initial wrong link I made) from /system/xbin before I could resymlink it to the correct busybox location /system/xbin. FYI the file I deleted was size 0B (obviously a bad link file with no data). The OS should have never allowed this link to be created (to a non-existent directory) nor written this file (if it were written correctly with proper error handling)!
[Galaxy S II Themes and Apps] Phil3759:
you cannot link to an existing file/folder and you cannot remove a file with rmdir, but with rm

You said you linked to a folder, so I answered rmdir as rm will not remove a folder (unless -rf options). You have to be precise. Linux is precise...
[Galaxy S II Themes and Apps] elfaure:
Thanks for your reply. The folder (bin/busybox) I linked the busybox applet czip to did not exist so there was no folder to be removed. It was the file (czip) created by the ln command that had to be deleted from the /system/xbin folder (where busybox is installed) before the new link could be created and the new file written to the same location (/system/xbin/czip). The symlink I created was telling the applet czip to look for busybox in bin/busybox when busybox is really installed in system/xbin.

Long story short I deleted czip and recreated it with another ln command symlinked to the correct busybox location. That fixed the problem.
[Galaxy S II Themes and Apps] elfaure:
My busybox is trashed. None of the commands are working. So I ran your script and it did nothing on my device. All the symlinks are still in /system/xbin. How can I remove it so I can install a new copy?