Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TheTwiddler

  • Rank

Profile Information

  • Your Current Device(s)
    Orange San Francisco
  1. TheTwiddler

    Worth the wait?

    Ordered a 16GB Nexus 4 from the Google Play Store late last night despite the site saying there was a 1 - 2 week wait. Got an email at 18:00 today saying it had been shipped! WoooHooo.
  2. TheTwiddler

    ZTE Skate - Confirmed Monte Carlo

    If it's 4.3 inches long, there's enough room to call it ZTE Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch ;)
  3. TheTwiddler

    google maps 5.0 rotation

    I'm running Flibblesans G2 R3a ROM (Froyo 2.2) on my OLED San Francisco and now that I have updated the /etc/permissions/android.hardware.touchscreen.multitouch.xml as above I can use two fingers to rotate a 3D view of the centre of Cardiff. Nice One.
  4. Found I had the same problem with the 2.2 ZTE full version after seing a post about it earlier in this forum, so I deleted the ZTE dialer (SmartDialler.apk) and instead loaded DialerOne from the Market. Also replaced the Launcher (Launcher2.apk) with LauncherPro from the Market, and replaced the messaging app (Mms.apk) with Handcent from the Market.
  5. Mine works OK using a 63 character password. Phone says that connection security is WPA/WPA2 PSK with a link speed of 48MBS. I am connected to a Virgin Media Cable Modem/Wireless Router (which is actually a Netgear Model VMDG280) and is set to WPA-PSK[TKIP] + WPA2-PSK[AES].
  6. Just thought I'd mention that there is no Mode10 (Sense) Live Wallpaper in either of the R3a ROMs, though it was present in the R3 ROM. I've tried copying the R3 apk into R3a and it doesn't seem to work. Is there something else I need to copy from R3 to R3a, or is this the reason for pulling it from the R3a ROM? Regards
  7. I've just converted from a variant of Pauls Modaco R4 ROM to the FLB R3 ROM and faced the same issue, namely non working Windows XP Drivers for Froyo 2.2. I can categorically state that the drivers from this sticky post Official ZTE USB Drivers work. The referenced post points here Official ZTE USB Drivers It's in 7Zip format (NOT Winzip), which you can download for free here 7Zip Download Use 7Zip to unpack the USB Drivers to a folder of your choice and double click the ZTE_Android_USB_Driver_1.2066.1.3.exe to install the drivers. DON'T do this with the phone connected to your PC.
  8. TheTwiddler

    32gb sd and SF

    Your SD card can only be seen by one machine at a time. If it's plugged in to your PC and appears as a drive letter in Windows Explorer, then it can't be seen by your phone.
  9. TheTwiddler

    Stuck on Green Android Logo

    Try also rebooting your (Windows?) PC just in case the Windows drivers have got confused. Once the PC reboots follow the instructions to: - Turn off the phone, take out the battery and SD card. Count to 30 and put the battery back (leave the SD card out for now) - Hold down Vol+ key and then press and hold power button, at which point you should shortly get the Android man on screen - Insert USB cable into phone and then PC. - The Bootloader driver should now load on PC. Check in Device Manager that there are no yellow exclamation marks. - Open a windows command window and cd to the directory where your fastboot (or fastboot-windows) executable lives - Try running fastboot reboot. The phone should now go through a reboot cycle. If that happens you still have the ability to flash the phone (ggod!), if not, you may well have bricked it (bad). Another thought. If you are trying to flash the R4 Modaco Custom ROM onto your phone, you need to first flash it with ClockworkMod Recovery. Be lucky!
  10. TheTwiddler

    Froyo Woe

    Just to check the obvious - you did put the SIM in the right way around - didn't you? (cutout facing the battery) It caught my mate out - so it did!
  11. Quick google and found this: ZTE Blade - Bouygues Telecon Enjoy
  12. TheTwiddler

    not recognised by adb?

    The following works for me on Ubuntu 10.10, with Eclipse 3.5.2, the ADT 0.9.9 plugin and SDK Tools R7 as described here Android ADT Plugin and here SDK Tools R7 This link Android Device Development says that you need to login as root and create a file named /etc/udev/rules.d/51-android.rules, which can be done as follows from a terminal window: $ sudo touch /etc/udev/rules.d/51-android.rules $ sudo chmod 644 /etc/udev/rules.d/51-android.rules The file should then have the following permissions (use ls -la /etc/udev/rules.d) -rw-r--r-- 1 root root 163 2010-10-27 00:18 51-android.rules Edit the above file in a text editor to contain the following two lines: SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="1354", MODE="0666" SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="d00d", MODE="0666" The first line matches the vendor/device Ids for the Adb interfaces that the SF presents when powered up normally and connected via USB. The second line matches the vendor/device Id for the fastboot interface that the SF presents when powered up with the VolumeUp button pressed, though I have not yet tried this for myself. Once done, I would recommend rebooting Ubuntu so that the above rules are activated. If I then power the SF up normally and connect it via USB, then cd to where I have the SDK Tools installed, I can launch an adb shell as follows without needing to become root or use sudo $ cd /home/android-sdk-linux_x86/tools $ ./adb shell # Hope this is enough to get you going. Edit: Fastboot does work with the above setup, but is isn't included in the SDK Tools. A bit of Googling and I found a copy here: Fastboot for Linux. Download it and copy/move it to the Android Tools directory where the adb executable lives and make it executable as follows: $ chmod 777 fastboot
  13. Mine arrived today also. Holder is a nice snug fit around the perimeter, but may need a sticky fixer or two if it rattles back and forth in situ. It came with a micro USB lead and definitely charges the 'Phone when connected up. However, the curly lead is only about 1M long when stretched, so isn't long enough to reach from the RH side window in front of the door to the Accessory socket in the console between the front seats on my Zafira. I'll have to have a rummage around under the RH dash over the weekend and see if I can safely rig up a supply or I'll have to look for a micro USB extension lead or a car charger with a much longer lead.
  14. TheTwiddler

    ClockworkMod Backup

    Thanks for the explanation. Happy bunny now.
  15. TheTwiddler

    ClockworkMod Backup

    Thanks for your reply. But can you tell me why you are so sure that the message doesn't matter? Would the data.img (or another) be missing if it did matter?

Important Information

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