I dropped my phone earlier and decided to blame it on the flip cover. Why blame the poor cover?
Flip cover – The most useless of all
- Flip covers get easily damaged if you fold them opposite side.
- If you don’t fold them on the opposite side, i.e. if you keep them open, your grip on the phone is pretty bad and the phone can fall easily if you are walking briskly.
- The flip cover does nothing to save your phone if it falls. The sides are exposed. The back and the screen would be protected, however because of the bad grip the phone would fall on its screen side.
- It is difficult to take pictures with a flip cover as you need to keep holding the cover.
- You need to open the phone to see the notifications.
Case -I like the cases very much. Its perfect with a screen guard. Be careful while selecting cases.
- If the case is hard, it will put scratches on the sides of the phone.
- One nasty thing about cases is that because of the way cases are designed, they pluck the screen guard off.
- Can cause heating issues.
- If your phone has NFC, the case can hinder with it.
Bumper – I have never used one. The idea is a good one and it would protect your phone as long as the phone falls on a flat surface. If your phone falls on gravel and the depth of gravel is more than the height of bumper, it is useless. Also, it doesn’t help from dust.
How often does it happen that you know your password but cannot type it on a mobile. Happens to me a lot. I think, even if someone asked my password at gun point, I wouldn’t be able to tell them.
As explained in the previous post, I thought of writing a small program to allow me to type using adb shell.
I created a python single file application for this. Here is the code.
How to run:
This would open up the program which would display a message to select the adb
Click OK, which would display the Open dialog box where you would select the adb location
Finally, the message box will be displayed where you can type the message and send.
You can select adb later.
Here are the links I had open by the time I had completed the program:
Like I told in my previous post, my phone screen went completely black. I looked around the internet to find some software which would project my android screen onto my computer. I found this great software: Droid@Screen
Droid@Screen is a single jar application which means it works on Linux as well. It uses Android Debug Bridge (adb) to connect to phone and project android screen to one’s computer.
But sadly this required USB debugging to be turned on and I had that turned off. After several tries and taking several screenshots, downloading them using AirDroid, I remembered that I had installed App Lock and turned it on settings. I took nearly 50 screenshots to finally click select the USB debugging on. I attached some screenshots so that someone else may find it helpful sometime.
After turning the USB Debugging on, I connected the phone using the USB to my computer. But as I shared earlier the phone fell in water and since then the USB port didn’t work properly. I finally got the phone connected properly and got Droid@Screen working. The trick was to plug in the usb to the computer partially.
The trouble now was how to type. I found the following to send text to the phone using adb shell.
$ adb shell input text this-is-a-text
but this allowed sending word by word. Space required the below
$ adb shell input keyevent 62
So I thought of writing a small program to allow me to type.
I have started working on a greasemonkey script. I tried using jquery but sadly the page I was working on doesn’t include jquery. Found this link which allows you to use jquery.
Later found out, it wasn’t required on the newer versions of greasemonkey which allows loading external js/css using @require. The mistake I was doing was: the @require tags are required between
// @require http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js
This is cleanly mentioned at the greasespot wiki here. That’s why the say read the manual.
After using Ubuntu for about two years, I am moving away to Mint Linux. I am in the live boot from USB while the installation is proceeding in the background. That is the power of linux. However, it isn’t without glitches. Hit my snag first when trying to start with installation and it stuck at “detecting file system”. A quick search brought up this page, the problem seems to be with the partitioner in the installations software (Ubiquity).
I quickly fired the terminal. And went to root mode. (later realized this wasn’t needed.)
mint@mint ~ $ sudo su
then killed the ubiquity
mint mint # killall ubiquity
Then opened the gparted and formatted the partition I wanted and ran the installation again. And the installation was over before I finished this post.
P.S.: The terminal is amazing. See how when I was a normal user, the prompt color was green and once I became root, it became red. Simple but effective to tell you what you are – a dumb user or a root with the power to destroy.
Dropped my phone on steps. Initially, it displayed 90% black and about 10% of the display was OK. However now, the display is completely black. Sadly to fix this I need a new LCD display which costs about $100. Wasting such money on an old phone is useless. So planning for a new phone. However, if you want to fix a similar issue check these out.
Youtube video 1
Youtube video 2
Also check ebay out for “samsung s2 lcd”
P.S.: I can still use my phone, guessing where what is. I sometimes take screenshots and download them using Airdroid or my usb cable to see what page I am and where the option I need is. I am getting pretty good at using the phone without display. I wonder how visually impaired use their smartphones.
What’s funny is Nokia was against Android since the start. They partnered with Microsoft instead. Now Microsoft goes ahead and buys Nokia just to launch an Android version of Nokia. What does this say about Microsoft’s confidence in Windows Phones.
Read this to know about the Microsoft’s strategy.
Read this to know about why Nokia said NO to Android.