vodafone 945/zte joe

[Guest fguimas]

Hi,

Someone could try with a Blade stock 2.1 rom to change the boot.img file and put there the boot.img file of the VDF945 stock rom that isavailable here at modaco, and try to flash in VDF945. You need to change also in blade rom in system directory , the Build.prop file of the VDF945 stock rom, to match the resolution.

I dont have the phone in the moment so i couldt try but its no aproblem for sure, because the only difference between Blade and Joe its the Touchscreen (Type and resolution).

If it works With blade 2.1 rom , it will work with 2.2 and 2.3 roms.

Regards

[Guest skboy]

Wasn't there a ROM based on CM6 ZTE Blade that booted but touchscreen didn't work?

Can someone share a link for that? I can't find it in this huge thread...

[Guest skboy]

I tried to use 2.1 ROM r9_update_de-orangeated_blade_signed (by Sebastian404) with boot.img from VDF PT stock ROM and changed build.prop to lcd density 160 and replace all "blade" with "joe".

Results:

- after succesfull boot there's no image at all in the screen (sometimes something shows up coming from bottom right corner as there was some wrong offset around)

- if I, blindly, slide to unlock, I can see in logcat that it did unlock and I can see there are no errors coming up and all my touch events show up properly. I can even start Settings.apk as it is easy to know where to touch. But no image at all.

It's still better than when I did the same with r12-update-modacocustomrom-blade-kitchen-unsigned (froyo), that touchscreen will only reply to the first touch (which would be slide to unlock) and never again until system eventually crashes and restarts launcher, going back to lockscreen. And then I am "allowed" to touch once more.

In that ROM I could see the first touch would be properly detected and forwarded to OS, but the following ones always returned "Waiting for key", but at least they were detected.

There were a lot of errors booting (specially Unknown permission android.permission.something_something) so I'm guessing system eventually crashes waiting on those and touchscreen might be being affected by that.

[Guest skboy]

Some extra progress on a different issue:

Regarding ZTE kernel sources on their website, that are not the sources they used to compile our Vodafone 945 for sure as we can see by the (small) typos we had to fix to compile and the touchscreen not being so responsive.

I've fixed (in what I would call a terribly ugly way) the touchscreen so it does respond all the time now. But the blinking keys are still there.

The touchscreen fix was traced/solved like this, after uncommenting some printk instructions in drivers/input/touchscreen/synaptics_i2c_rmi.c:

- when the OS would react to the click, dmesg would show:

<4>[  951.233374] wly: finger=1, finger2=0, buf[1]=1

<4>[  951.233424] wly: gesture=0,flick_x=0,flick_y=0

<4>[  951.308263] wly: finger=1, finger2=0, buf[1]=1

<4>[  951.308288] wly: gesture=0,flick_x=0,flick_y=0

<4>[  951.345656] wly: finger=0, finger2=0, buf[1]=0

<4>[  951.345682] wly: gesture=0,flick_x=0,flick_y=0

- when the OS ignored the click, this would show:

<4>[  967.163833] wly: finger=1, finger2=0, buf[1]=1

<4>[  967.163883] wly: gesture=0,flick_x=0,flick_y=0

<4>[  967.188688] wly: finger=0, finger2=0, buf[1]=0

<4>[  967.188713] wly: gesture=8,flick_x=0,flick_y=0

<4>[  967.349951] wly: finger=0, finger2=0, buf[1]=0

<4>[  967.349975] wly: gesture=1,flick_x=0,flick_y=0

So I went into driver code and just added:

 #ifdef CONFIG_MACH_JOE//ZTE_TS_ZT_20100520_001

                    	y = 2787 - y;

                    	y2 = 2787 - y2;

                    	[i][b]//ugly fix

                    	if (buf[12] == 8) {

                            	buf[12] = 0;

                            	finger = 1;

                    	}[/b][/i]

 #endif

buf[12] is the gesture variable, so basically every time a gesture 8 came in, I'm assuming it's one of "those" clicks, so I force finger to 1.

It's really ugly, but it does work.

Though, this was tested with replacing the kernel in VDF PT stock ROM. From this to a ROM with 2.2 or 2.3 other issues have to fixed first.

And maybe kernel has to be updated...

[Guest harock]

here s blade kernel maybe help u

blade elclair 2.1. 2.6.29

www.mediafire.com/?yqz5xgkahao3d8q

blade froyo 2.2. 2.6.32

www.mediafire.com/?35w0ugcdsno9gae

@skboy

u can find more question here

www.neopeek.com/viewtopic.php?f=24&t=6845

Edited September 13, 2011 by harock

[Guest fguimas]

Skboy said ,

Quote ,

"I tried to use 2.1 ROM r9_update_de-orangeated_blade_signed (by Sebastian404) with boot.img from VDF PT stock ROM and changed build.prop to lcd density 160 and replace all "blade" with "joe".

Results:

- after succesfull boot there's no image at all in the screen (sometimes something shows up coming from bottom right corner as there was some wrong offset around)

- if I, blindly, slide to unlock, I can see in logcat that it did unlock and I can see there are no errors coming up and all my touch events show up properly. I can even start Settings.apk as it is easy to know where to touch. But no image at all."

Skboy, i think you made something wrong maybe in build.prop (Joe use lcd-density=120 and not 160) , because you can see image correctly when you flash Blade roms in VDF945 (Touchscreen issue).

Cuttysark and others users already test it changing Build.prop. Please see cuttysark previous posts.

If you say the touchscreen works good with this solution , the image should be good too, because is not affected by boot.img file, and maybe we got our problem solved.

Thanks for your help.

Regards

Edited September 13, 2011 by fguimas

[Guest skboy]

Skboy, i think you made something wrong maybe in build.prop (Joe use lcd-density=120 and not 160) , because you can see image correctly when you flash Blade roms in VDF945 (Touchscreen issue).

Cuttysark and others users already test it changing Build.prop. Please see cuttysark previous posts.

Actually I didn't randomly try 160. It was based in vodafone stock ROM *and* cuttysark posts that does mention 160, not 120.

build.prop from VDF PT has density defined twice: first 120, then 160. Following the logic from a properties file in Java, the latest is the active one after file is loaded, so yes, it should be 160.

I've used 160 with every ROM I tried (including the 2.2 from blade where screen fits perfectly), this is the first something else did not work.

But I'll try to get the latest kernel (2.6.35) from ZTE Blade to work with Joe. I think the ROM with 2.2 I tried does require kernel to be at least 2.6.32.

If I get 2.6.35 working with stock system partition (2.1) it might be a good step.

[Guest skboy]

Has anyone tried to compile different blade kernels?

I've been trying with these two:

https://github.com/fopina/Zte-Blade-New-35-kernel (2.6.35)

and

https://github.com/fopina/ZTE-BLADE-2.6.32

and tweaking a little the Vodafone PT default config from 2.6.29, I get no more compilation errors, but I get a linkage error saying

LD      .tmp_vmlinux1

arm-linux-eabi-ld: no machine record defined

Googling for a while shows up a lot of people with these errors that never found out what was wrong with .config, they just replaced it with someone else's which is not an option in this case...

[Guest cuttysark76]

Great work Skboy!!!

I don't have any knowledge, only curious...

Don't forget the memory address issue from Blade. I believe it's easyer to use GEN 1 ROM's.

I can't find my previous ROM's (Blade) that I have used. I'm going to repeat all steps again and if I succeed I'll share the ROM.

Best regards

[Guest cuttysark76]

What about the CM7 kernel? Would it be easier to use?

Anyway here you can find the ZTE N700 (ZTE Joe CDMA) official update from ZTE site:

http://www.zte.com.cn/cndata/mobile/software/201106/P020110610463940851574.zip

The zip contains a BIN image, I can't use it but maybe someone does... It might be usefull since it has Android 2.2....

Here you can find SiKai Silicone case for ZTE N700 / Joe / vodafone 945:

http://www.ebay.co.uk/itm/SiKai-Silicone-case-ZTE-Vodafone-945-Joe-N700-case-/200641087314?pt=PDA_Accessories&hash=item2eb7240752

Best regards

[Guest skboy]

Non-ZTE kernels are even less useful..

The problem with the kernels I posted above is that ZTE did leave some JOE configuration behind but did not upgrade the actual drivers source code, just deleted them.

Tried with a few files, but there are a lot of small differences in structures and so on, so it would take quite some time.

As Froyo should be able to run with 2.6.29 I left kernel upgrade for now.

I've used r9_update_blade_deorangeated ROM (2.1 for blade, by Sebastian404) and did manage to get the screen showing up. I only had to replace libsurfaceflinger.so with the one from VPT 945 ROM.

Still, it's not really useful as for 2.2 the differences are a lot more.

For now, as touchscreen is working with ZTE Kernel sources now, I'll try to get Wireless Tether app to work in the stock ROM (with custom kernel) as I need that.

Then I'll go back to try to get 2.2 blade to stop crashing every minute...

What about the CM7 kernel? Would it be easier to use?

Anyway here you can find the ZTE N700 (ZTE Joe CDMA) official update from ZTE site:

http://www.zte.com.c...63940851574.zip

The zip contains a BIN image, I can't use it but maybe someone does... It might be usefull since it has Android 2.2....

Here you can find SiKai Silicone case for ZTE N700 / Joe / vodafone 945:

http://www.ebay.co.u...=item2eb7240752

Best regards

[Guest cuttysark76]

I use Barnacle Wifi Theter... Do you have Wfi with the custom kernel?

Edited September 16, 2011 by cuttysark76

[Guest skboy]

Which custom kernel?

With same config as stock, after the touchscreen fix everything worked great.

But enabling NAT did mess up something and wifi had issues that caused restarts actually. But I have only made a quick try, didn't check any error logs.

Does that one work well with stock kernel?

[Guest cuttysark76]

Which custom kernel?

With same config as stock, after the touchscreen fix everything worked great.

But enabling NAT did mess up something and wifi had issues that caused restarts actually. But I have only made a quick try, didn't check any error logs.

Does that one work well with stock kernel?

Perfect on stock 2.1

[Guest cuttysark76]

ZTE N700 (CDMA Joe) Update, new link

Again, the zip contains a BIN image, I can't use it but maybe someone can. It might be usefull since it has Android 2.2....

[Guest skboy]

When you said it would work with stock (that doesn't have NAT enabled) I thought it would be one of those crappy proxy solutions, but apparently it's full routing. I'll have to take a look at the source to see how it's done without iptables.

I believe using ZOE CDMA might end up being the same as using blade as the drivers are still different and It is probably using a newer kernel as well that does not include our Joe drivers.

And the 2.6.32 sources I downloaded have references to JOE_CDMA but it's missing some source files for it...

But tomorrow I'll take a look at that BIN and try to see.

[Guest cuttysark76]

Skboy,

I'm looking forward to your work. How can I help?

[Guest skboy]

I haven't done anything. I want to get AOSP working first, but android.git.kernel.org has been down (for quite some time now) and codeaurora mirror has issues in eclair branch.

After I get AOSP Eclair working I'll start playing around with AOSP Froyo.

I gave up on using these ROMs before I fully understand android file structure and dependencies, as my attempts with deorangeated blade 2.2 ROM have been frustrating (while trying to prevent system from restarting).

But let me know if you want to follow those lines yourself and play around with it.

[Guest sansuni]

skboy, did you try using "ZTE-U V871" or "ZTE-C N700" rom's? they are basicly same phone with different names...

[Guest skboy]

Actually they're quite different. N700 is CDMA which implies it uses completely different grmware at the very least.

Quick googling advises against those experiments.

It's the same as playIng around between gen1 and gen2 blades.

I won't be trying that until I fully understand it. I rather play with eclair.

[Guest sansuni]

they are different, but their drivers are the same and they use android 2.2 so you can use them for their components.. (they can't be that different right..)

[Guest skboy]

If you get a gen1 blade and run a gen2 rom after replacing the kernel, it won't work.

Same here.

You need to recompile the OS but there's no source.

That's why I'm waiting for git.kernel.org to come back online and I'll try AOSP builds.

[Guest sansuni]

If you get a gen1 blade and run a gen2 rom after replacing the kernel, it won't work.

Same here.

You need to recompile the OS but there's no source.

That's why I'm waiting for git.kernel.org to come back online and I'll try AOSP builds.

ok, if i can help you in any way, just ask..

(by the way, can you check this rom? a friend of mine send me this link and he says this rom works but when he installs this rom camera stops working)

Edited September 22, 2011 by sansuni

[Guest skboy]

by the way, can you check this rom? a friend of mine send me this link and he says this rom works but when he installs this rom camera stops working

same results as other blade 2.2 ROMs: system restarts.

I'll just wait for the GIT repository to come back online.

[Guest harock]

friends cingibi say this

I found something that might help

Touchscreen (ugly but working) fix

https://github.com/fopina/ZTE-Joe-Kernel-2.6.29/commit/b4aae8e05675c7126ed620361d96ce6eb01b3dd9