Jump to content


Photo

ZTE V9 Tablet

* * * * * 2 votes

  • Please log in to reply
490 replies to this topic

#21
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404
The USB config did look quite odd... Does it work in the standard recovery?

  • 0

#22
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet

The USB config did look quite odd... Does it work in the standard recovery?


Don't worry, USB appears to be fine now - udev issue at my end.

I've unpacked your image and inserted a symlink from /system/bin/sh to /sbin/busybox. This has gotten 'adb shell' working. Still no further on the input issue yet, but the night is young :-)

  • 0

#23
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Don't worry, USB appears to be fine now - udev issue at my end.

I've unpacked your image and inserted a symlink from /system/bin/sh to /sbin/busybox. This has gotten 'adb shell' working. Still no further on the input issue yet, but the night is young :-)


It's seems zte screwed up the recovery, Adbd should point to /shin/sh but it looks like they included a regular version of adb ....

Can you try this version and see if its any better for you:

http://android.podtwo.com/light/

That keys file btw is the keys it uses to check the signed update files. Not the buttons on the device.

  • 0

#24
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet

It's seems zte screwed up the recovery, Adbd should point to /shin/sh but it looks like they included a regular version of adb ....

Can you try this version and see if its any better for you:


No, same error when trying to get a shell - looking for /system/bin/sh

So, I guess the next problem is the keys, and then, Froyo :-)

For the keys, I'm trying to compile kouch's bootable recovery from GIT but I'm having trouble getting busybox to compile. Am I on the right track ?

  • 0

#25
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

No, same error when trying to get a shell - looking for /system/bin/sh

So, I guess the next problem is the keys, and then, Froyo :-)

For the keys, I'm trying to compile kouch's bootable recovery from GIT but I'm having trouble getting busybox to compile. Am I on the right track ?


Sorry, I wasn't clear, the 2nd version has more keys added to it, can you select anything? If not we'll have to fond the values for they keys, tho now the shell is working that should not be too hard..


Sorry im traveling today so can't write too mixh

  • 0

#26
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet

Sorry, I wasn't clear, the 2nd version has more keys added to it, can you select anything? If not we'll have to fond the values for they keys, tho now the shell is working that should not be too hard..
Sorry im traveling today so can't write too mixh


Ah sorry. No, still nothing works as a select key.

M.

  • 0

#27
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404
Ok,

I've uploaded a 3rd version...

http://android.podtwo.com/light/

I've swapped VOL UP for Select... can you press the VOL DOWN 7 times to get to the 'Advanced' menu, then again 4 more times to get to 'Key Test', and try pressing all your buttons and give me the values of them?


I've also replaced ADBD with a built copy, so you should be able to get into a recovery shell

  • 0

#28
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

For the keys, I'm trying to compile kouch's bootable recovery from GIT but I'm having trouble getting busybox to compile. Am I on the right track ?



The way to do it........

There a number of tutorials around, and I'm not going to cover it all but this is what you need to do...


download the Android SDK & NDK

using the SDK download the 2.1-update2 & 2.2 SDK, emulator, etc, etc..

then you need to do download and build the standard vanilla Android source, try the boot/system.img you complied on the emulator to prove your enviroment is sane.


next you need to download the WHOLE CyanogenMod repository...

now you need to build a board config and its makefiles for your device...

and THEN.. you can build CyanogenMod and you'll have a (hopefully) working recovery in there....

  • 0

#29
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet

I've swapped VOL UP for Select... can you press the VOL DOWN 7 times to get to the 'Advanced' menu, then again 4 more times to get to 'Key Test', and try pressing all your buttons and give me the values of them?


Vol Up = 115
Vol Down = 114
Home = 330
Menu = 330
Back = 330
Power = 142

Considering all three keys on the front report 330 - I say we made select=330 :-)

I've also replaced ADBD with a built copy, so you should be able to get into a recovery shell


Thanks, this is working now.

And thanks for the quick overview - gives me something to play with incase I want to make changes myself.

  • 0

#30
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Vol Up = 115
Vol Down = 114
Home = 330
Menu = 330
Back = 330
Power = 142

Considering all three keys on the front report 330 - I say we made select=330 :-)
Thanks, this is working now.

And thanks for the quick overview - gives me something to play with incase I want to make changes myself.


Cool, I'll build another (final) version...

These buttons are they physical buttons?

the only reason I ask is that 330 is the same value I get from the Blade when you tap anywhere on the screen....

  • 0

#31
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet
They aren't physical no, they are printed just below the LCD screen.

Here is pretty good photo - http://www.greaterea...8c_zte-v9-1.jpg

They are down the far end.

  • 0

#32
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

They aren't physical no, they are printed just below the LCD screen.

Here is pretty good photo - http://www.greaterea...8c_zte-v9-1.jpg

They are down the far end.


ARGH! I wish you'd said that before :unsure:

also checking linux/input.h:

#define BTN_TOUCH 0x14a

(thats 330)

Hmm, the 'official' way to support devices without physical buttons in clockwork is to set a define, that will will cause the an extra 'back' option to appear on all menus, and then you get to press the POWER button to select an option

So I've enabled that, but I've also added TOUCH so any of the 'virtual' buttons (or tapping on the screen) should be select.


http://android.podtwo.com/light/


Let me know how that works

Edited by Sebastian404, 04 January 2011 - 10:01 PM.

  • 0

#33
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet
Probably be easier if we were doing this over IRC :-)

Up/down and tapping anywhere for select. The 'back' option is in the menu.

BUT, it appears the USB device ID changed and even after updating my udev config I cannot get adb to recognise the device. Anything change in that area ? It worked fine in b3

Edited by serialmonkey, 04 January 2011 - 10:16 PM.

  • 0

#34
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Probably be easier if we were doing this over IRC :-)

Up/down and tapping anywhere for select. The 'back' option is in the menu.

BUT, it appears the USB device ID changed and even after updating my udev config I cannot get adb to recognise the device. Anything change in that area ? It worked fine in b3


nope, not touched that part since b1 when I added the ro.product.device id...

sebastian@laverna:~/android/zte_light$ cat clockwork/ramdisk/usb.conf
ro.product.name=V9
ro.product.device=V9
usb.enable_switch=1
usb.linux_switch=1
usb.linux_pid=0x1350
usb.switch_pid=0x1354
usb.default.pid=0x83

vs the orignal:

sebastian@laverna:~/android/zte_light$ cat recovery/ramdisk/usb.conf
ro.product.name=V9
usb.enable_switch=1
usb.linux_switch=1
usb.linux_pid=0x1350
usb.switch_pid=0x1354
usb.default.pid=0x83

can you got back to b3 and double check its not something with your host?

  • 0

#35
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet
Must be something with my setup - I'm having trouble with b3 now. I can see the device in adb, but when I adb shell it doesn't work as expected. I get the prompt, but can't type anything.

I'll keep playing, thanks for all your help.

  • 0

#36
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Must be something with my setup - I'm having trouble with b3 now. I can see the device in adb, but when I adb shell it doesn't work as expected. I get the prompt, but can't type anything.

I'll keep playing, thanks for all your help.


can you still use ADB when your booted into the regular system?



oh btw, when you get time, can you post your romdump somewhere so I can take a look at it?

  • 0

#37
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet
Yep, works fine when booted normally.

Upload my romdump now, will post a link here when it's done.

  • 0

#38
serialmonkey

serialmonkey

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Newcastle, Australia
  • Devices:ZTE Light Tablet
Looks like its something we broke awhile ago - if I go back to your first image and fix up that /system/bin/sh symlink then adb shell works fine.

When testing adb shell on b3/b4 I must have been just seeing if I can access the shell, and not actually trying to use it. Doh !

  • 0

#39
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Looks like its something we broke awhile ago - if I go back to your first image and fix up that /system/bin/sh symlink then adb shell works fine.

When testing adb shell on b3/b4 I must have been just seeing if I can access the shell, and not actually trying to use it. Doh !


ah, ok... hmm well on b3 I replaced ADBD with one I built from source.... so that sort of figures

Hmm, its easy to 'fix' as you say with the symlink, but the OCD in me would prefer to use the recovery adbd...

I'll check out your dump, maybe it was just an oversight with the ZTE branded one..

  • 0

#40
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404
btw, can you give the other features a go, backup and restore are I guess the best ones to try...

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users