Point Element

The MIUI ROM is heavy. I noticed severe slowing down in places. I did not use it for more than a few days though. So it could be that cleaning up the system a bit, might have helped. The MIUI looks great, is pleasure to use with great looks, features and a similarity everywhere. But its far too removed from the android experience. Sadly not my cup of tea right now! Link on needrom: http://www.needrom.com/download/miui-os-for-v889s-v807/

This ROM is fastest of the few I tried out. Its really slimmed down, is fast and pleasant to use. The two main problem I noticed were lack of 3G and broken battery charge monitor. The lack of 3G was not much hindrance for me, but the broken battery monitor meant I could not use this ROM. Link to ROM on needrom.com:  http://www.needrom.com/download/slimdroid-mod-v889sv807/

Edit: Links to software added VRoot 1.7.3.4863 (ENG)(6.9MB) TWRP Recovery (IMG)(5.8MB) Scatter file for ZTE Blade C (V807C) (382B) SP Flash Tool 3.1304.0.119 (6.7MB) Misc.: MTK Droid Tools 2.5.3 (11.9MB) ZTE Blade C Root and Recovery Folder (34.2MB) ZTE Blade C TWRP Recovery Flashing Video (Russian) (41.9MB)  My readme file with experience using the above russian video STOCK Rom ZTE Blade C (V807C) - Flashable by SP Flash Tool (280.1MB)   Wanted to flash TWRP recovery on my ZTE Blade C (v807c). After looking here n there, I stumbled onto a video by a Russian guy who showed how to do it. I got the idea of it all. And so I proceeded. Following the video, I got familiar with the process which is as follows: 1. Get the device rooted: using vroot the zte v807c was easily rooted. 2. Then install twrp recovery: In the video the operator performs following steps: a. Install the zte usb drivers from ZTE v807\Drivers for ZTE. b. Install the mtk drivers from ZTE v...

So far... I have installed RabbitMQ server on my development machine and using it to test my development code. I have STOMP_SEND working fine. Using the management web console for RabbitMQ I can see the messages being queued. Now I have to read the sent messages. And here I stumbled into a situation where libstomp's stomp_read function was failing. So now going ahead, I integrated the message sending code into the product. The requirement was simple. We had to send a fixed message to a queue with time stamp every two mins. So I put together a thread and put the message sending logic into it. After testing it, I started work on the read part. The requirement was simple. The product has to read some messages from a queue and display them to user. Thankfully one of the system guys fixed libstomp ( saving me some efforts :D ), and made the stomp_read working again. So after putting together a test application to read from the queue, I ended up with a no of problems. First o...