• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      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.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      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.

Racer 2.6.32 kernel

95 posts in this topic

Posted (edited)

It uses a modified source. Blade + mooncake files. That's the source that I need, it makes the touchscreen work also.

sebastian404 made one similar to that

https://github.com/sebastian404/blade-kernel

but touchscreen won't work like all the others. I bet that msm_ts.c needs to be modified

If they had respected the GPL, we wouldn't be having this trouble right now...

i'm using this config right now, touchscreen doesnt work (check attachment)

test1.config.txt

Edited by TigTex
0

Share this post


Link to post
Share on other sites

Posted (edited)

I wrote a simple script to compare configs. I think many will be useful.

And i found how to make the touchscreen work without editing msm_ts. If possible, lay out the sources later.

A tool for comparing configs by deadlink

Upd: updated link

Edited by deadlink
0

Share this post


Link to post
Share on other sites

Posted

I wrote a simple script to compare configs. I think many will be useful.

And i found how to make the touchscreen work without editing msm_ts. If possible, lay out the sources later.

A tool for comparing configs by deadlink

hi could you upload your build kernel so we can test it for you

0

Share this post


Link to post
Share on other sites

Posted

hi could you upload your build kernel so we can test it for you

Camera doesn't work. And touchscreen have some bugs. I fix msm_ts yesterday, but today i found another way to fix touchscreen without changing msm_ts driver. If possible with a touchscreen, maybe upload it tonight

0

Share this post


Link to post
Share on other sites

Posted

New experimental kernel

based on zte blade 2.6.32.9

improved touchscreen calibration

improved system performance

Known issues:

- camera doesn't work on any racer

This is still very experimental code!! Try at your own risk!

test_kernel.zip

0

Share this post


Link to post
Share on other sites

Posted

New experimental kernel

based on zte blade 2.6.32.9

improved touchscreen calibration

improved system performance

Known issues:

- camera doesn't work on any racer

This is still very experimental code!! Try at your own risk!

test_kernel.zip

Just tried it... noticeable improvement with touchscreen n performance:d camera no go:-Pas u mentioned it

0

Share this post


Link to post
Share on other sites

Posted

@deadlink i tryed your kernel its the best so far but i still find the touchscreen still no good when typing

will you be able to fix the home home,menu,back without having touch_to_key?

0

Share this post


Link to post
Share on other sites

Posted

Camera doesn't work. And touchscreen have some bugs. I fix msm_ts yesterday, but today i found another way to fix touchscreen without changing msm_ts driver. If possible with a touchscreen, maybe upload it tonight

you care to share the changes you made? so others might improve on your work?

0

Share this post


Link to post
Share on other sites

Posted

will you be able to fix the home home,menu,back without having touch_to_key?

I can rewrite the driver, but do not think it reasonable. Touch_to_key is a good decision. Maybe I'll do this later.

you care to share the changes you made? so others might improve on your work?

Of course I share the sources. Can you add them to your repository?

sources.zip

0

Share this post


Link to post
Share on other sites

Posted

Of course I share the sources. Can you add them to your repository?

Ok, I have added the changes.... commit

0

Share this post


Link to post
Share on other sites

Posted (edited)

I've compiled a new kernel, based on the current cyanogenmod blade kernel because sebastian404's kernel is incomplete (smartass for example, doesn't work, corrupts the boot).

Using this kernel

https://github.com/TomGiordano/kernel_zte_blade

And the mooncake files, I've made one optimized version, with PERFECT SCREEN CALIBRATION!.

1 problem that needs to be solved: camera still doesn't work. No more problems apart that one.

The config is almost equal to the blade's .config. So this is using the smartass cpu governor by default for best performance ever.

Attach below. feel free to test the kernel. Make sure you have the old kernel ready to reflash if you need it.

update.zip

Edited by TigTex
0

Share this post


Link to post
Share on other sites

Posted (edited)

I've compiled a new kernel, based on the current cyanogenmod blade kernel because sebastian404's kernel is incomplete (smartass for example, doesn't work, corrupts the boot).

Its not really 'my' kernel, its a fork from KK's... who is a Cyanogenmod developer...... I'd assume his was the same as TomG's

Using this kernel

https://github.com/TomGiordano/kernel_zte_blade

And the mooncake files, I've made one optimized version, with PERFECT SCREEN CALIBRATION!.

would you care to share what files you have modified from TomG's kernel?

Edited by Sebastian404
0

Share this post


Link to post
Share on other sites

Posted (edited)

Its not really 'my' kernel, its a fork from KK's...

would you care to share what files you have modified from TomG's kernel?

Just use the tomg's kernel + the zipped files and you get a perfect working kernel. No camera though.

config and files attached

kernel_mooncake.zip

config.txt

Edited by TigTex
0

Share this post


Link to post
Share on other sites

Posted

I've compiled a new kernel, based on the current cyanogenmod blade kernel because sebastian404's kernel is incomplete (smartass for example, doesn't work, corrupts the boot).

Using this kernel

https://github.com/TomGiordano/kernel_zte_blade

And the mooncake files, I've made one optimized version, with PERFECT SCREEN CALIBRATION!.

1 problem that needs to be solved: camera still doesn't work. No more problems apart that one.

The config is almost equal to the blade's .config. So this is using the smartass cpu governor by default for best performance ever.

Attach below. feel free to test the kernel. Make sure you have the old kernel ready to reflash if you need it.

Yep best performance:D

0

Share this post


Link to post
Share on other sites

Posted

Just use the tomg's kernel + the zipped files and you get a perfect working kernel. No camera though.

You use old mooncake-board :P In my fresh mooncake-board, which I have upload above, the camera works. There is a device /dev/msm_camera/. But I do not know why app not working. And i think that using smartass reduce battery life... ;)

0

Share this post


Link to post
Share on other sites

Posted (edited)

There is a device /dev/msm_camera/.

kernel with msm_camera in /dev/:

test_kernel.zip

Maybe something is wrong with init?

Edited by deadlink
0

Share this post


Link to post
Share on other sites

Posted

when opening the camera i get this from logcat

V/CameraHolder( 1040): open camera 0
D/QualcommCameraHardware( 135): createInstance: E
E/QualcommCameraHardware( 135): startCamera X: /dev/msm_camera/control0 open fa
iled: Unknown error: 0!
E/QualcommCameraHardware( 135): createInstance: startCamera failed!
D/QualcommCameraHardware( 135): ~QualcommCameraHardware E
D/QualcommCameraHardware( 135): ~QualcommCameraHardware X
E/CameraService( 135): Fail to open camera hardware (id=0)
E/CameraHolder( 1040): fail to connect Camera
E/CameraHolder( 1040): java.lang.RuntimeException: Fail to connect to camera ser
vice
E/CameraHolder( 1040): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1040): at android.hardware.Camera.<init>(Camera.java:258)
E/CameraHolder( 1040): at android.hardware.Camera.open(Camera.java:220)
E/CameraHolder( 1040): at com.android.camera.CameraHolder.open(CameraHolder.jav
a:124)
E/CameraHolder( 1040): at com.android.camera.Camera.ensureCameraDevice(Camera.j
ava:1794)
E/CameraHolder( 1040): at com.android.camera.Camera.startPreview(Camera.java:18
46)
E/CameraHolder( 1040): at com.android.camera.Camera.access$5900(Camera.java:94)

E/CameraHolder( 1040): at com.android.camera.Camera$3.run(Camera.java:938)
E/CameraHolder( 1040): at java.lang.Thread.run(Thread.java:1019)
I/ActivityManager( 213): Displayed com.android.camera/.Camera: +1s358ms (total[/code]

0

Share this post


Link to post
Share on other sites

Posted (edited)

Can you post a dmesg output here?

try to do "dmesg | grep camera > /sdcard/dmesg.log"

The error in the logcat is different than with my kernel (not found vs open failed).

deadlink, the smartass makes the phone run at lower speeds when the screen is off and always run at full speed when it's on (i read that somewhere, hope it's correct). That's why maybe the battery drains more when using. But you have better performance, that's what matters ;)

also, did you made that new board-mooncake?

Edited by TigTex
0

Share this post


Link to post
Share on other sites

Posted

did you made that new board-mooncake?

I replaced some code of the 29 core from zte sources. If you read /proc/devices you will see msm_camera! Its mean that camera work... Does not it?

0

Share this post


Link to post
Share on other sites

Posted (edited)

I replaced some code of the 29 core from zte sources. If you read /proc/devices you will see msm_camera! Its mean that camera work... Does not it?

it means that the device is there, doesn't mean it works... see the "dmesg" output. There is something there related to the camera that might help you.

Also, i see you've deleted the sections related to the brasilian zte camera... we want their camera to work...

i think you need this code

#ifdef CONFIG_MSM_CAMERA

static uint32_t camera_off_gpio_table[] = {


#if 0 

	GPIO_CFG(0,  0, GPIO_INPUT, GPIO_PULL_DOWN, GPIO_2MA), /* DAT0 */

	GPIO_CFG(1,  0, GPIO_INPUT, GPIO_PULL_DOWN, GPIO_2MA), /* DAT1 */

	GPIO_CFG(2,  0, GPIO_INPUT, GPIO_PULL_DOWN, GPIO_2MA), /* DAT2 */

	GPIO_CFG(3,  0, GPIO_INPUT, GPIO_PULL_DOWN, GPIO_2MA), /* DAT3 */

Edited by TigTex
0

Share this post


Link to post
Share on other sites

Posted

Just use the tomg's kernel + the zipped files and you get a perfect working kernel. No camera though.

looking at the files, there is no real difference between TigTex's and Deadline's updates to my first commit, tho the TS_OFFSET_X & TS_OFFSET_Y in msm_ts.c seems to be different, the fix for the camera seems to be in the config....

# CONFIG_MT9D115 is not set
# CONFIG_MT9D113 is not set[/code] is now:
[code]CONFIG_MT9D115=y
CONFIG_MT9D115_QTECH_SUNNY_SOCKET=y
# CONFIG_MT9D115_QTECH_SUNNY_FPC is not set
CONFIG_MT9D113=y
CONFIG_MT9D113_QTECH_SUNNY_SOCKET=y
and
# CONFIG_SENSOR_ADAPTER is not set
is now
CONFIG_SENSOR_ADAPTER=y

I managed to loose my Racer a few weeks ago so I can really test this.....

0

Share this post


Link to post
Share on other sites

Posted

About the calibration, you can use msm_ts.c new offsets and also new values on my board-mooncake.c . I am sure it's perfectly calibrated.

About the config, the MT9D115 and MT9D113 are the 2 differences between my stock rom (tmn softstone) and the brazilian x850 (the camera doesnt work on 2.2/2.3 roms because the kernel doesn't have that modules enabled). I've been testing the camera with and without that modules. No change. So it's something that deadlink did on it's file that made this work (well, the msm_camera is in /dev). But he removed support for mt9d115, the main reason for me to make a custom kernel... also he's board-mooncake has wrong calibration values and battery voltages. This night I'll try to skype with deadlink and have a better look at all of this. Maybe tomorow we have a fully working kernel ;)

0

Share this post


Link to post
Share on other sites

Posted

@ Sebastian404 could you build a kernel ill be happy to test it

0

Share this post


Link to post
Share on other sites

Posted

Any chance of a complete update.zip to try?

Many Thanks

0

Share this post


Link to post
Share on other sites

Posted

I build kernel with working camera! ;)

Maybe kernel config not optimized, and touchscreen without tigtex offsets, but all work now =)

Tigtex, i don't know what is the difference in brazilian Racer. Try to fix it with my config and board.

test_kernel.zip

And config:

config_camera_work.txt

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.