Announcements

ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.

Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[ROMs] [gen1/gen2] Various 2.3.x roms for ZTE Racer

146 posts in this topic

latest mokee-mooncake worked wonderfully in my Mexican ZTE Racer, blazingly fast, but the camera is not working... what can I do? how can I make the camera work? Im an advanced linux user so don't fear to throw technical terms at me... I have adb working... should I use another mod? should I switch boot kernel? help please...

According to the notes from latest installation attempts, the last ROM I tried was an hybrid putting the kernel of cm7_2.3.7_Racer_full-257v2.zip inside thecm-7-20120819-NIGHTLY-mooncake.zip file. This rom was able to make the camera work, but it was very slow. I have a 3.2 megapixel camera.

Share this post

Link to post

Share on other sites

hmm.. some racer devices have different camera models, thats probably the issue.. also, some kernels have different configs so it might be that one kernel can load proper camera driver for your specific model and the other doesnt.. you should try just putting kernel you used in your hybrid rom in mokee to see if it would load your camera.. and also you should replace liboemcamera.so in your /lib folder with the one from the rom with working camera, that might work..

According to the notes from latest installation attempts, the last ROM I tried was an hybrid putting the kernel of cm7_2.3.7_Racer_full-257v2.zip inside thecm-7-20120819-NIGHTLY-mooncake.zip file. This rom was able to make the camera work, but it was very slow. I have a 3.2 megapixel camera.

did the kernel make your phone slow or camera? didnt really get that good.. but it still shouldnt mess up things, i dont know what kernel raceboy uses but i guess its vamshi's, pretty much the same thing i use.. maybe old release which would explain camera driver but again, shouldnt make anything slow

Share this post

Link to post

Share on other sites

Thank all you for your quick answers. Everything is kinda slow with that kernel (the one with camera working). By example, it takes like 3 or 4 trials to push the power button to make the locking slider to react correctly. When I exit an activity to the main icons screen, the icons take like 4 seconds to load. And so... When I tried the mokee-mooncake, it ran blazingly fast compared with the custom rom i had before.

I have both android sdk and ndk... and just minutes ago i tried compiling the cyanogenmod kernel with them, using a configuration i extracted from a backup of my original phone. Most options were missing, so the compiling failed. Should I use a patch or another sources? How can I compile a working kernel for the ZTE Racer given that I have the compilers and the original config file?

Share this post

Link to post

Share on other sites

I compiled the kernel using the aforementioned sources... It gave me an arch/arm/boot/zImage file. Then I tried to run it, with adb reboot bootloader and then sudo ./fastboot boot /path/to/zImage. And my ZTE Racer simply turned off. Didn't boot at all. Why? Any hints? I really want to be able to run my own kernels. I am using the compiler inside the toolchains/arm-linux-androideabi-4.4.3 of the official NDK... is that correct?

I compiled the kernel using the aforementioned sources... It gave me an arch/arm/boot/zImage file. Then I tried to run it, with adb reboot bootloader and then sudo ./fastboot boot /path/to/zImage. And my ZTE Racer simply turned off. Didn't boot at all. Why? Any hints? I really want to be able to run my own kernels. I am using the compiler inside the toolchains/arm-linux-androideabi-4.4.3 of the official NDK... is that correct?

Thanks in advance.

As far as I know, while fastboot the zImage directly is somewhat supported, in most cases you'll want (or even need) to create the boot.img and fastboot that (fastboot boot /path/to/boot.img), you can use tigex's racer_kitchen_v2 here on the forum to create the boot.img

Share this post

Link to post

Share on other sites

No matter which kernel I try, the result is the same... The ZTE Racer shuts itself down. Maybe I have not configured the udev thing? Because i have to run fastboot as root user, and when asked for the device name it says '?????????? fastboot'. When run as normal user, it says 'no permissions fastboot'.

No matter which kernel I try, the result is the same... The ZTE Racer shuts itself down. Maybe I have not configured the udev thing? Because i have to run fastboot as root user, and when asked for the device name it says '?????????? fastboot'. When run as normal user, it says 'no permissions fastboot'.

That are the contents of my android udev config file.
Thanks in advance.

Hmmm what linux is this?
The udev rules are ok, well, the first two are unncessesary unless you have asus and huawei products. After connecting the phone, what's the output of:

adb devices

??

I think I've had a similar problem for not having platform-tools in my $PATH, or maybe it was for using jdk7 instead of jdk6, I'm not sure. As for the "no permissions" as normal user, are you sure your current user (not root) is in the plugdev group?

Share this post

Link to post

Share on other sites

In the udev configuration file it was SUBSYSTEMS instead of SUBSYSTEM. And i had to add the idVendor of the phone in fastboot mode too.

So i compiled the sources for gen1 kernel (when flashing my device it says its Gen1), and made an image based off the mokee one (split_bootimg.pl of the mokee gen1 img, then mkbootimg with the ramdisk of the mokee gen1 img and my recently compiled kernel). When trying to boot the phone with the generated image file, it doesn't boot, and doesn't even produces any logcat output. And if i try to flash it, it doesn't boot at all and I have to restore backup. Any hints?

Thanks in advance.

Update:

The reason my image files weren't booting was the kernel base address, Searching in google i found the base address 0x02e00000, Using that address i made the img again and it booted. I tried 2 images:

First I pulled the config from my phone (its the boot.img from cm7_2.3.7_Racer_full-257v2.zip). Using that config and the https://github.com/n...kernel-2.6.32.9 source tree, i built a first image. I flashed it, and both the camera and the orientation-changing animations looked green. Then, i cleaned my source dir, loaded the default configuration, built the kernel again, built the boot image, flashed it, and the camera didn't connected.

Any hints on how to make the camera work? The cm7_2.3.7_Racer_full-257v2.zip boot.img can make my camera work, but its slow.

Share on other sites

In the udev configuration file it was SUBSYSTEMS instead of SUBSYSTEM. And i had to add the idVendor of the phone in fastboot mode too.

Oh lol xD sorry, didn't pay much attention

The reason my image files weren't booting was the kernel base address, Searching in google i found the base address 0x02e00000, Using that address i made the img again and it booted.

That's one of the reasons I tell most people to use tiget's racer kitchen, it does that automatically, however, while 0x02e00000 works for some reason, the correct base address for gen1 phones is 0x02A00000, although I've also saw a zte released kernel with the address 0x02c00000 :-\ never tried that though, just 0x02A00000.

I tried 2 images:

First I pulled the config from my phone (its the boot.img from cm7_2.3.7_Racer_full-257v2.zip). Using that config and the https://github.com/n...kernel-2.6.32.9 source tree, i built a first image. I flashed it, and both the camera and the orientation-changing animations looked green. Then, i cleaned my source dir, loaded the default configuration, built the kernel again, built the boot image, flashed it, and the camera didn't connected.

Any hints on how to make the camera work? The cm7_2.3.7_Racer_full-257v2.zip boot.img can make my camera work, but its slow.

Thanks in advance. All you rock!!

The green thing could be either kernel, libraries or graphic drivers, beyond checking logcat I can't tell you much =/ given the different drivers zte used for camera (really zte, you suck T_T) is difficult to anyone beyond the phone owner to debug. Also, equilyim might help you out regarding libraries and graphic drivers since I think he have several versions of those and know much than me about it.

Meanwhile, what I could suggest is to take a rom where your camera works well by default and test your kernels with it, if you think is a kernel problem, compare the config of the kernel that works with the resulting config of a kernel you made or even better check the config of your stock kernel to see the camera driver used and compare that against your own kernel

Output from logcat when running the camera app from the hybrid rom made by inserting the boot.img from cm7_2.3.7_Racer_full-257v2.zip into the cm-7-20120819-NIGHTLY-mooncake.zip rom. As you can notice, the sensor is enlisted as mtd9d113. The source tree I am using doesnt have that option of camera device.

Where can I get that driver? How do I integrate it with the existing source tree?

Share this post

Link to post

Share on other sites

Output from logcat when running the camera app from the hybrid rom made by inserting the boot.img from cm7_2.3.7_Racer_full-257v2.zip into the cm-7-20120819-NIGHTLY-mooncake.zip rom. As you can notice, the sensor is enlisted as mtd9d113. The source tree I am using doesnt have that option of camera device.

Where can I get that driver? How do I integrate it with the existing source tree?

Thanks in advance...

can you please try one rom before going into this? just for my curiosity tho, sorry, could you download and try my zte-wbs rom, im not sure what i used to build it but people said they had a working camera on it..

as for mtd9d113 driver, best choice is google and github i guess, if you can find the driver, you can integrate it with ease in your tree, edit few files to load it and thats pretty much that

1

Share this post

Link to post

Share on other sites

Equiliym I want to deodex latest lewa rom for blade which is impossible with ultimatex..& Equiliym I also it in Ubuntu 10.10 but it is the problem of Java which is not available for 10.10 version...& can u give me download link for windows version of kitchen..thanks..

0

Share this post

Link to post

Share on other sites

Equiliym I want to deodex latest lewa rom for blade which is impossible with ultimatex..& Equiliym I also it in Ubuntu 10.10 but it is the problem of Java which is not available for 10.10 version...& can u give me download link for windows version of kitchen..thanks..

you need to add repo for java on ubuntu.. lemme just.. here, from android aosp site, they say you install java on ubuntu like this: