Jump to content

deksman2

Members
  • Content Count

    162
  • Joined

  • Last visited

Community Reputation

12 Good

About deksman2

  • Rank
    Enthusiast
  1. In all honesty, MM update is definitely better than nothing... however, I would have preferred Nougat considering that they are putting the time and effort into updating the OS anyway. This lack of jumping to Nougat could easily be connected to several reasons: 1. They want to encourage sales of newest phones that come with Nougat 2. Possible issues of being unable to directly upgrade from 5.1.1 to 7 I got this phone for my flatmate as I thought it was excellent in terms of overall specs and price (I would have gotten one for myself too, but I went with Zenfone 2 (ZE551ML) due to it having better community support. Lack of being able to root the Ultra 6 however (to install Adaway at least and remove annoying ads) is disappointing. I tried every proposed option to root the phone and it's just not working.
  2. Guys... I also did an unlock by using an ebay. However, even after inputting the code correctly and the phone saying its now unlocked... another Vodafone app activated immediately (Message+ I think) and said that a non-vodafone sim card was detected and 'blocked' or that it just won't work. I've used Giffgaff sim-card and followed instructions to the letter, but the sim card is still not working - I can only get emergency calls.
  3. Hey guys. I got myself the THL W200 in late January. I repartitioned the internal space and everything is working fine on my end. No issues with SIM card reading or whatnot. Software works good, and I also learned that MediaTek apparently released the source-code for out MT6589T months ago, which means that Cyanogen will probably follow suit pretty soon. But, if I'm not mistaken, THL stated (or was at least hinting) that they will release the KitKat update for our W200. I kinda wish I waited a bit to get the octa-core version (THL W200s), but I didn't know it was in the works back when I ordered it... and at any rate, this will be more than enough for my needs. Battery capacity on the other hand is not something I'm too happy with (THL got stingy on this one - should have been at least 2000 mAh, or 2500 mAh), but they stated that they might release a bigger capacity version (I guess we shall see)... still, the phone is capable of making it through about a day or two with relatively moderate usage (if you are not gaming of course). Any news on Cyanogen options for this phone? I've been searching info on it and there are some indications of it probably coming soon, but nothing substantial to be honest.
  4. Hello everyone. I'm in a bit of a pickle. I got the THL W200 phone on Friday and its working great thus far. I wanted to clean up my ZTE Blade and give it to my nephew. Trouble is, the phone seems to refuse to ready any and all SD cards. Last week I successfully managed to get the sd-ext partition to work on the Blade (and expanding the internal storage in the process), but then, days later, the phone suddenly lost ALL of the data on the sd-ext partition and effectively rebooted itself into a clean slate. I looked at the internal memory and it was no longer at about 620MB (with the sd-ext), but 220MB as it was originally (before sd-ext). I tried everything I could think of on the SD card, but alas, to no avail. And just today, when I decided to clean up the phone from CWM and give it a fresh install, cleaning up everything in the process (except the SD card) and when it was time to install the ROM and GAPPs, the phone refused to read the SD card (2GB sd card that originally came with it nearly 3 years ago). I tried another SD card (4GB from micronis) and its the same thing. The Sd card reader on my laptop reads both cards just fine - it writes and removes files from them with ease, but the phone refuses to read the cards. I should note, the Blade decided to stop reading higher capacity SD card (16GB) I had previously (months ago) almost suddenly, but the 2GB SD card I had put in as a replacement worked fine. Some creative work on modifying the partitions of the 16GB card managed to get the card recognized on the Blade until I copied data to it (at which point it became unreadable again). And now, I have no ROM installed, and no extra sd cards lying around to try out. I downloaded ADB SDK developer tools in an attempt to install the ROM onto the phone without CWM, but alas, I got a strange error message after pushing the ROM to the phone - which made it impossible to complete the process and install the rom. If someone could provide assistance, I'd appreciate it. P.S. The 2GB card was formatted and tested formatted to FAT partition as well as FAT32. Neither seems to be affecting the Blade to recognize/mount the sd card anymore.
  5. Too expensive. I was looking for a phone up to $200 really. Besides, the THL W200 I picked is just fine and will probably do great. :-)
  6. Coming from KonstaT's ROM Android 4.2, I can definitely say that I noticed this ROM being more responsive. The virtual keyboard is more responsive to my inputs and there seems to be less of a lag in general. Then again, I noticed that versions past 4.1 (such as 4.2) have been increasingly taxing on the Blade. If KonstaT or someone else comes out with KitKat (or 4.4) for the Blade, there's a chance it will behave a lot better because that OS revision seems to have been tailored to function well for low end devices with 512 MB RAM. The OS in general should be capable of doing more with less as time goes on - but we do live in a system where the goal is to garner profits, therefore, releasing a more taxing OS in general promotes sales of newer hardware - when it shouldn't be about the OS requiring larger hardware, but being small and capable of USING the hardware its on efficiently.
  7. Nevermind. I picked THL W200. I also thought about getting the NO. 1 N3 smartphone which has a much higher capacity battery, larger screen (which doesn't seem to present any issues), as well as better cameras and motion sensor - but it costs the same as THL W200 ($180) - but at the time I mistakenly thought it might have been too large. Oh well, the THL W200 is still pretty sweet overall - mostly same specs except for the cameras and battery. My only beef with these 5" phones is that they seem a bit too long. They should have offered those 5" screens in a bit wider format.
  8. I went with the THL W200 because of the 5" screen and slightly faster CPU, though to be honest, I was also eyeing the NO. 1 N3 smartphone which has a 5.7" screen, but at the time decided it might be too big (later realized it actually wouldn't be, so right now I'm slightly regretting it because the NO 1. N3 also has better cameras, motion sensor and a much larger battery of 2800mAh - all for the same price of the THL W200). At any rate, the THL W100 seems to be exactly the same like the W200, except that it has a slightly lower screen resolution, a slightly slower CPU (thought the MTK 6598T is nothing more than overclocked MTK 6598) and a smaller screen. Other than that, they are comparable. Hardware-wise, the THL W100 definitely seems like a great phone for a cheap price.
  9. As the thread title suggests... I'm looking to get myself a new affordable smartphone which will last a while. Up until now I've been using ZTE Blade (the first one), and I still do (its 2 years and 10 months old now), but the little guy is showing its age I'm afraid what with the keyboard being relatively slow, etc. Most of the slowness is easily attributed to using 4.2 Android on it, but other than that, the device itself works ok (except of course the battery also isn't that durable anymore) and I liked the premise I could accelerate apps UI with the GPU... but granted, I think its time for a change because even that is not fluid. At any rate, I was looking at ZTE V967s and Zopo ZP820. Generally they both seem to be pretty much the same, except I'm a bit iffy on certain things. Namely, both seem to use the same CPU, except that the ZP820 essentially has an overclocked version of it (by about 20% - which is what AnTutu benchmarks reflects). Other than that, I am also puzzled by the GPU's. On one end, people seemingly suggest that the PowerVR SGX 544MP is better than Mali-400 MP, while of course others will say differently. I tried looking for comparisons, but the results were sketchy at best, and some websites seem to suggest the SGX 544MP is better, while others seem to indicate Mali-400 MP is better. Other than than that, I'm not too concerned about 20% difference in CPU speeds because its not a big deal. What I'm thinking about more are the differences in camera qualities. Again, some people say the ZTE is better, while others claim Zopo is better. Furthermore, I was unable to find any moded ROM's for Zopo, while the support for V967s seems to be a lot better in that area. One other thing... the screen sizes. Both devices seem to have 5" screens, and yet the ZP820 seems to be a bit wider than V967s (though I think this is more of an optical illusion created by the external design casing). P.S. I'm looking at the respective devices on PandaWill and AliExpress. PandaWill seems to have lower prices and both deliver for free to Croatia (which is where I'm at). Thoughts?
  10. I tried the full wipe with no apps installed. The newest ROM version seems to work fine, except for the home button (which was non functional for me). I made sure I did a complete wipe and all, so nothing could interfere... but the only difference was that I installed gapps from KonstanT's thread instead of the ones provided in the first post of this thread because they are newer if I'm not mistaken (but I don't see how those would break home button functionality).
  11. I think the ROM would benefit from a better GPU utilization optimization (if thats possible) in UI rendering (including APPS, etc.) so that it basically behaves all the time like it does in the Gallery (which is buttery smooth). Aside from that... the only real problem with this ROM is essentially the keyboard which is painfully slow. Even Swiftkey has slowdown problems and takes some time before the letters are entered after pressing (not sure what causes these delays though) at certain times. I realize the keyboard behaves a lot better/smoother under Gingerbread and Froyo, but short of going back to those old ROM's, is there any way the keyboard could be optimized?
  12. Ok... here's an update: I used the MicroSD adapter with that 16GB MicroSDHC card on my laptop and ran the following command in command prompt: chkdsk f: /r (f: being the drive letter for the MicroSD adapter). After I ran that and transferred files to it, I put it into the Blade and the card mounted fine. However... after about a minute or so it again dismounted on its own, mounted, dismounted... and on and on and on. I don't get it. The card is operational. It works fine on my laptop with the MicroSD adapter, but it refuses to work in the Blade... and the chkdsk command seems to make it functional only temporarily on the Blade with files on it... if the card is empty, it mounts just fine, but start writing data on it and the Blade goes bonkers. CWM can still install the ROM zip and gapps from that card... but incidentally, refuses to mount the card (reports an error). It looks as if I will have to RMA the card seeing how its useless and request a different one.
  13. Hey guys... I've posted this in KontanT's thread for JB 4.2.2 ROM but I might as well do it as a new thread. The ROM works great for me... however, I'm experiencing a problem with my ADATA MicroSDHC 16GB card (class 4). Namely, my old card (which had same specs) apparently somehow got damaged (wouldn't mount anymore and apparently became corrupted in a good portion since neither formatting or error correction worked) and I got a replacement. I tried the new card in my laptop. Formatted fine (FAT32 - just like the old one), checked for errors (came up clean), copied over the newest ROM and some personal files (pics, etc,) to the card. I was even able to install the ROM and gapps in CWM from that card... which means CWM registers it just fine, and I also initiated USB mounting from there and accessed the card from the laptop (again everything worked great). But... after the ROM and gapps were installed, the OS kept seeing the MicroSD card as being connected, then disconnected/removed, then connected again, disconnected/removed again... and so on and on and on endlessly (the OS simply couldn't read it). I tried it again in CWM... it reads the card just fine. I tried it in the laptop... works just fine. Boot up the ROM with the 16GB MicroSD inside, and the OS goes bonkers on the card (it keeps up with the removed/connected endless loop). Anyone has any idea what's happening? My 2GB MicroSD that came with the Blade works fine in the OS (so I'm using that for the moment)... but to me it seems as if the OS cannot work with this new 16GB card. Suggestions would be appreciated. P.S. Upon further experimentation, the ADATA 16GB MicroSDHC Class4 card in question seems to mount just fine when its completely empty. The moment I put ANYTHING on it, it would appear that the Blade refuses to mount the card. CWM behaves the same - but the strange part is, CWM still seems to want to install a new ROM whose zip file is located on that card - but try to mount the card, and it says it encountered an error. The card itself seems to be fine... I can manipulate it to no end on a laptop with data on (which is readable), just not on a mobile - the moment the card has any data on it, the Blade refuses to mount it.
  14. This ROM works great for me... however, I'm experiencing a problem with my ADATA MicroSDHC 16GB card (class 4). Namely, my old card (which had same specs) apparently somehow got damaged (wouldn't mount anymore and apparently became corrupted in a good portion since neither formatting or error correction worked) and I got a replacement. I tried the new card in my laptop. Formatted fine (FAT32 - just like the old one), checked for errors (came up clean), copied over the newest ROM and some personal files (pics, etc,) to the card. I was even able to install the ROM and gapps in CWM from that card... which means CWM registers it just fine, and I also initiated USB mounting from there and accessed the card from the laptop (again everything worked great). But... after the ROM and gapps were installed, the OS kept seeing the MicroSD card as being connected, then disconnected/removed, then connected again, disconnected/removed again... and so on and on and on endlessly (the OS simply couldn't read it). I tried it again in CWM... it reads the card just fine. I tried it in the laptop... works just fine. Boot up the ROM with the 16GB MicroSD inside, and the OS goes bonkers on the card (it keeps up with the removed/connected endless loop). Anyone has any idea what's happening? My 2GB MicroSD that came with the Blade works fine in the OS (so I'm using that for the moment)... but to me it seems as if the OS cannot work with this new 16GB card. Suggestions would be appreciated.
  15. Seeing how I personally don't have the money to spend just yet... I will continue to use my San Francisco for a while more. Besides, more powerful hardware is 'trickling down' in terms of cost, so I might end up getting something in the summer or by the end of the year. Either way, if I can find something with substantially more powerful hardware that doesn't cost I don't know how much, it 'should' theoretically be enough to last for about 3 or 4 years down the line (but my main priority will be a new laptop :D ).
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.