Leaderboard

^^^ Just added something in the message : FLASH..! End-of-The-World scheduled in December 2012, has been postponed to 3012 due to Technical Problems. Please co-operate & continue with Life & same Wife till further notice !!!

You reading this post because you have an imported/foreign CDMA handset with you and its ESN/MEID is registered in Reliance database. If ESN/MEID is not registered then you can check this topic. Now you want this handset to be working on India's Largest and RIMweb's beloved CDMA network! Though this area is little tricky for n00b's, past knowledge of CDMA development plays a key role. But if you don't have anyone this post will help you (hopefully); fingers crossed! PLEASE NOTE THIS PROCESS CAN GET YOU VERY EXPENSIVE AND ULTRA MODERN PAPERWEIGHT. SO YOU SHOULD KNOW WHAT YOU DOING. IF YOU DON'T WANT THAT TO HAPPEN THEN GET IT DONE WITH THE HELP SOMEONE AS MENTIONED IN THE FAQ TOPIC. Prerequisites 1) CDMA 800 Mhz handset (Which ofcourse you have) with its data cable. 2) CDMA workshop v 2.7 (though there are more softwares to do it, this is used commonly) - Use Google to find 2a) There is a possibility that your handset isn't supported by CDMA Workshop v 2.7. In that case you need QPST - Use Google to find 3) Knowledge of how to put your particular handset in DIAGNOSTIC mode along with its driver. You can Google that out. 3a) Though I have personally done 100's of different handset models, keeping track of each handset model is difficult. So I am mentioning the most common DIAG mode enabler below: HTC Handsets: ##3424# or ##3424+Call button. Palm/HP: ##8727277# Samsung: ##8778# and select modem. BlackBerry DIAG behaves on virtual port created by installing BlackBerry DM. This list will be huge if i keep writing. So I'll suggest if your handset isn't mentioned in this list then please ask on this topic and I will try to reply with your enabling DIAG solution. 4) Diagnostic Driver for your device. (There are so many handsets and usually there are different drivers for each devices, so this is something you have to request here, commonly used DIAG Drivers - Google for it) 5) Windows PC with XP or Win 7 32 bit. (Its very difficult to find 64 bit drivers so I'll keep and support this tutorial for 32 bit only) 6) Carrier specific NAM PRL or Preferred Roaming list file. (Check the pinned topics in Technical forum) 7) A-key or Authorization key. (will be provided by ESN/MEID Registrar or handset seller) 8) Your handset's SPC (check your handset cover box or ask your handset seller). How to / Step by Step: Note - There are many handsets/models and each time process is little different. But basic changes to latch your phone to Reliance network is mentioned here. I am using HTC DEVICE to do it for Tutorial. 1) Pick your phone and enable Diagnostic mode in it. ( I am using HTC HERO and so i punch: ##3424#). Please find your phone DIAG enabler in prerequisites above. 2) Connect your Phone to PC using Data cable and let the Driver search process begin. (mostly Driver installation failed and you have to do it manually) See pic or video. 3) Now open CDMA workshop (You might have to disable your antivirus, as the crack for CDMA workshop uses Trojan pattern) 4) Open Device manager and expand Ports (COM & LPT) there u see which COM PORT assigned for your device. In my case its Com PORT 7 5) Select that comport on CDMA workshop and press connect. and press read. 6) Go to security Tab and enter SPC and press SEND button. return message should be SPC COrrect Phone unlocked See pic. 7) Now go to Nam Tab and press load and select Reliance.nam and press write. 8) Go to CAVE and enter your akey and press write. (You might have to calculate akey, see pic for details on calculation) 9) Go to Other tab and press write under PRL select Reliance.PRL file return message should be success. 10) Now your phone is flashed on Reliance CDMA network. :thumbup: :thumbup: Note - Now after this process you need to visit Reliance webworld to transfer ur number from existing handset/RUIM to this phone. U can also use HCC (Handset Change Card) if its available and work in ur city/state. Hope you enjoy flashing your phone. Thanks. EVDO Activation & Configuration For questions related to generating the NV dump file with EVDO parameters and submitting EVDO activation request, please check the FAQ topic. If you have the NV dump file from your handset seller or MEID/ESN registrar, you can follow these steps to upload the NV dump file to start using EVDO: 1) Go to "Security" tab in CDMA Workshop and Send the SPC as explained earlier in this topic. 2) Once it showed that the phone has been unlocked, go to the "Memory" tab and click "Write" under "NV Items" 3) Clik OK when it shows that you have to send the SPC and then you will be able to select the NV dump file. Browse and select the file. Sample file name is like "MEIDnumber@hrpd.rcom.co.in-net-NVItem-Script-PPP-HDR-27.txt" 4) Submit the file and it will show that the NV items have been written successfully. Now restart the handset and EVDO should work fine if the EVDO activation has been done already at Reliance.

Reliance provides ADSL as well as Ethernet based broadband. May in your area it's Ethernet based so you're told to go for router without ADSL modem. 150N or 300N won't make any difference if you're going to use the router for internet sharing only. For large file copy between devices on your WiFi Network OR HD video streaming, 300N should give better throughput. Though this is true only for a limited area near to the router. As the range increases & signal weakens, the speed goes down in 300N also. 150 or 300 does not have much to do whether the router can cover a larger WiFi range area. 300N routers generally may have better range mainly because they tend to have dual/high dbi antenna compared to single/lower dbi antenna in most 150n routers. There is no definite prescription as to which router can cover your entire 2000 sq ft. area. Most (including 300N) consumer grade routers generally won't be able to give blanket coverage in every corner of your premise. The coverage depends on placement of the router (higher level/in center of premise should be better), wall obstructions, router antenna etc. Higher dbi/External/detachable antenna routers are preferred for better coverage. Would suggest to skip belkin. Netgear is also good. TP Link are currently the most selling/more bang for buck kind of routers. Range is between approx Rs 1,050 to Rs 2,800. 150N TP Link TL-WR740N - Rs 1,050 Netgear WGR614 - Rs 1,200/1,300 300N TP-Link TL-WR841N - Rs 1,800/1,900 TP-Link TL-MR3420 - Rs 2,600/2,700 If you want to keep future provision for using USB Dongle Data Cards also in addition to RCOM wireline broadband in a failsafe mode, TL-MR3420 can do that. If you don't need that functionality, probably go for a low cost one and keep a future provision of adding one more low cost router as range extender if the first one is unable to cover your entire house.

God postponed it because 1. he wants to see Manchester united vs real Madrid match 2. Rajnikant purchased new laptop which has 100 years warranty 3. God wants to see rimweb more famous than other forums..... sent from beast

Taptu >> https://play.google.com/store/apps/details?id=com.taptu.streams&feature This is a Flipboard competitor. Very nice news app. Main benefit? It has good number of indian news media sources also unlike flipboard which has none. Also has facebook, twitter, google integration.

I really fail to understand the OP's comparison where according to him a utterly 'dumb' phone like NOKIA can compare to the newer breeds of Smartphones like S2/S3/Note2.There is no comparison at all and the entire premise of this topic is 'flawed". And two devices in my pocket?? Not at all. After handling a 'phablet' like Note II for a few weeks, I could never go back to a dumb phone.

seems kinna late to the parteh mate !!!by and large all updated members on the forum are on JB infact a new leak is just out in FL04 just flashed it about an hour agao , not much change than FK23 , but some lesser bug fixes only . On my part i can say , i had many options to choose when i upgraded , but decided on Epic Touch the USPs i looked in it were 1.. best size , never had a phone which is so perfect to hold with right width and height , totally awesome to operate via one hand, 2.. the hardware is so solid of this phone 3.. the GPU and CPU both are advanced as compared to its contemporaries 4.. Yes the screen was a bit of a iffy thing , but JB has improved the screen and made it so damn crsip now , 5.. i never enjoyed touchwiz so much as much i am , on JB Love it , but then there are other phones as well that i love

Remaining Good info About CPU Scheduler Source What is a scheduler? In a multitasking operating system, there must be an instance, the processes that want to run, CPU time and allocates it "goes to sleep" after the allotted time (timeslice) again. This instance is called the scheduler, such as opening and closing applications. that is, how fast they are open and how long they are kept in RAM. I / O scheduler can have many purposes like: To minimize time searching on the hard disk Set priorities for specific process requests To regulate a particular portion of the bandwidth of the data carrier to each running process To guarantee certain process requests within a certain time Which scheduler are available? CFQ Deadline VR Simple Noop Anticipatory BFQ Sio Anticipatory: Two important things here are indicative of that event: - Looking on the flash drive is very slow from Equip - Write operations while at any time are processed, however, be read operations preferred, ie, this scheduler returns the read operations a higher priority than the write operations. Benefits: - Requests of read accesses are never treated secondarily, that has equally good reading performance on flash drives like the noop Disadvantages: - Requests from process operations are not always available - Reduced write performance on high-performance hard drives CFQ: The CFQ - Completely Fair Queuing - similar to the Dead Line maintains a scalable continuous Prozess-I/O-Warteschlange, ie the available I / O bandwidth tried fairly and evenly to all I / O requests to distribute. He created a statistics between blocks and processes. With these statistics it can "guess" when the next block is requested by what process, ie each process queue contains requests of synchronous processes, which in turn is dependent upon the priority of the original process. There is a V2 and the CFQ has some fixes, such as were the I / O request, hunger, and some small search backward integrated to improve the responsiveness. Benefits: - Has the goal of a balanced I / O performance to deliver - The easiest way to set - Excellent on multiprocessor systems - Best performance of the database after the deadline Disadvantages: - Some reported user that the media scanning would take this very very long time and this by the very fair and even distribution of bandwidth on the I / O operations during the boot process is conditioned with the media scanning is not necessarily the highest should have priority - Jitter (worst case delay) can sometimes be very high because the number of competing with each other process tasks Deadline: This scheduler has the goal of reducing I / O wait time of a process of inquiry. This is done using the block numbers of the data on the drive. This also blocks an outlying block numbers are processed, each request receives a maximum delivery time. This is in addition to the Governor BFQ very popular and in many well known kernels, such as the Nexus S Netarchy. He was indeed better than the BFQ, but compared to the VR he will be weaker. Benefits: - Is nearly a real-time scheduler. - Characterized by reducing the waiting time of each process from - best scheduler for database access and queries. - Bandwidth requirements of a process, eg what percentage does a CPU is easy to calculate. - As the Governor-noop ideal for flash drives Disadvantages: - If the system is overloaded, can go a lost set of processes, and is not as easy to predict SIO: It aims to achieve with minimal effort at a low latency I / O requests. Not a priority to put in queue, instead simply merge the requests. This scheduler is a mix between the noop and deadline. With him there is no conversion or sorting of requests. Benefits: - It is simple and stable. - Minimized Starvations (starvation) for inquiries Disadvantages: - Slow random write speeds on flash drives as opposed to other schedulers. - Sequential read speeds on flash drives, not as good Noop: The noop scheduler is the simplest of them. He is best suited for storage devices that are not subject to mechanical movements, such as our flash drives in our SGSII's to use to access the data. The advantage is that flash drives do not require rearrangement of the I / O requests, unlike normal hard drives. ie the data that come first are written first. He's basically not a real scheduler, as it leaves the scheduling of the hardware. Benefits: - Adds all incoming I / O requests in a first-come-who-first-served queue and implements requests with the fewest number of CPU cycles, so also battery friendly - Is suitable for flash drives because there is no search errors - Good data throughput on db systems Disadvantages: - Reducing the number of CPU cycles corresponds to a simultaneous decline in performance VR: Unlike other scheduling software, synchronous and asynchronous requests are not handled separately, but it will impose a fair and balanced within this deadline requests, that the next request to be served is a function of distance from the last request. The VR is a very good scheduler with elements of the deadline scheduler. He will probably be the best for MTD Android devices. He is the one who can make the most of the benchmark points, but he is also an unstable schedulers, because his performance falter. Sometimes they fluctuate below the average, sometimes it fluctuates above the average, but if above, then he is the best. Benefits: - Is the best scheduler for benchmarks Disadvantages: - Performance variability can lead to different results - Very often unstable or unzverlässig Simple: As the name suggests, it is more of a simple or simple scheduler. Especially suitable for EMMC devices. He is reliable, maybe not as good as the VR, when this time has a good day, but he is despite all this very performance-based and does his best. At the moment it is the default scheduler in quasar kernel. Advantages: - not known Cons: - not known BFQ: Instead requests divided into time segments as the CFQ has, on the BFQ budget. The flash drive will be granted an active process until it has exhausted its budget (number of sectors on the flash drive). The awards BFQ high budget does not read tasks. Benefits: - Has a very good USB data transfer rate. - Be the best scheduler for playback of HD video recording and video streaming (due to less jitter than CFQ Scheduler, and others) - Regarded as a very precise working Scheduler - Delivers 30% more throughput than CFQ Disadvantages: - Not the best scheduler for benchmarks - higher budgets that were allocated to a process that can affect the interactivity and bring with it increased latency.

Swiftkey Flow Beta is here.. SwiftKey Flow Beta APK (smartphone) >> http://bit.ly/skflowbeta SwiftKey Flow Beta APK (tablet) >> http://bit.ly/skflowbetatab SwiftKey reveals 'Flow Through Space'