Most of this article doesn't only apply to Telegram+ -- it just happens to be an example that got a lot of coverage elsewhere, with many authors or commentators putting the full blame on Google, Telegram, the Telegram+ developer or even WhatsApp Inc (eh?). In this article, we'll try to look at the different aspects to provide a clear view of what actually happened, and what can (and hopefully will) improve with regards to developers in general and the Play...
Two Methods to Fix Random Key Press Bug on Fascinate
Sometimes while engineering a device, a manufacturer misses a small problem. Here at XDA, we take these issues and make revisions to the hardware and the software. That’s one of the reasons why we have a whole forum dedicated to hardware hacking.
In this particular case, XDA Recognized Developer electric bill isolated a problem with a hardware interrupt on the the i500 Samsung Fascinate. The problem is a lack of capacitance on one of the physical buttons of the device. When the button is not pressed, random interference from both inside and outside of the device turns the button into an antenna. While there is a resistor that mostly takes care of the problem, it does not stop all issues from occuring. In the words of the hacker/developer himself:
The problem is that the touchkey chip is located right next to the 3G antenna. When the phone is accessing the 3G network the RF energy gets transferred to the interrupt and i2c clock and data lines causing false interrupts to occur. The processor responds to the interrupt by reading the key value from the cypress chip. The symptoms occur more frequently in low signal areas because the phone outputs a higher RF level in those situations which causes more RF interference on the interrupt line.
Electric bill came up with two solutions: both a software and a hardware filtering solution to this rather annoying problem. The software solution allows the device to ignore random key presses and continue on. This solution, while it works, is not ideal because the device is still reacting and wasting processor cycles every time it sees a change in the pin-state of the button in question. This means the user never sees it, but the hardware may slow down while reacting to and deciphering and filtering the key presses.
The hardware solution provides a filter at the hardware level. The hardware solution counters stray inductance by inserting a small capacitor into the circuit. This capacitor shunts randomness to ground, and provides somewhat of a hardware time-delay to the button press.
By far, the hardware solution is preferable. However, working with hardware means a risk of damage to the device. If you’re having a problem with your Samsung i500 Fascinate buttons, choose the method which is right for you. You can learn more by visiting the original thread.[Thanks to XDA Elite Recognized Developer Rebellos for the tip.]
Want something on the XDA Portal? Send us a tip!
Ever since custom recoveries and roms became popular, nandroid backups have been the fall back method for all android enthusiasts, irrespective of their confidence levels. They allow easy backup and restore in case things go wrong, which happens invariably when a modification is being tested. With that being said, how relevant are Nandroid Backups to this day? Back in 2011, when the world of Android was being awed by the likes of the Samsung Galaxy S2, a little modification made its appearance...
While HTC's latest flagship brings many new features, the aesthetic design of the device remains largely untouched in comparison to its predecessor. Many Android enthusiasts throughout the community were expecting a large redesign of one of the most beautiful handsets ever released, but what we got is something more along the lines of an 'HTC One M8S". So this begs the question, is the M9 worth the upgrade if you already own the M8? Current HTC One M8 users chime in and let us know your thoughts.