373 replies to this topic

[alves_369]

mikeioannina, on 07 November 2012 - 10:22 PM, said:

Be patient... now uploading Check first post for screenshots

woow nice work

[mikeioannina]

New Racer nightly & new CWM Recovery is up. Check first post for download links & changelog.
Please report if the bugs are solved or not

Edited by mikeioannina, 07 November 2012 - 11:10 PM.

[alves_369]

mikeioannina, on 07 November 2012 - 11:09 PM, said:

New Racer nightly & new CWM Recovery is up. Check first post for download links & changelog.
Please report if the bugs are solved or not

404 . file not found =(

[mikeioannina]

alves_369, on 07 November 2012 - 11:20 PM, said:

404 . file not found =(

I've tested the links and they work fine... Are you downloading the Racer nightly? Carl/Freddo is not available yet but you can use the Racer one with the bugs mentioned in the first post

Try refreshing the page

Edited by mikeioannina, 07 November 2012 - 11:46 PM.

[kimiamania]

mikeioannina, on 07 November 2012 - 11:46 PM, said:

I've tested the links and they work fine... Are you downloading the Racer nightly? Carl/Freddo is not available yet but you can use the Racer one with the bugs mentioned in the first post

Try refreshing the page

I already tried your cwm and its work on my zte carl/freddo
even faster than my previous cwm
right now im still using equilym cm7 nightlies
can i rename your build to update.zip and flash it ?
or i need to fresh install ?
sorry for dumb question

[mikeioannina]

kimiamania, on 08 November 2012 - 02:45 AM, said:

I already tried your cwm and its work on my zte carl/freddo
even faster than my previous cwm
right now im still using equilym cm7 nightlies
can i rename your build to update.zip and flash it ?
or i need to fresh install ?
sorry for dumb question

It's better to do a factory reset when you install my rom to avoid extra bugs... but you can install it without doing the factory reset. I haven't tested if it works, take a backup first

[kimiamania]

mikeioannina, on 08 November 2012 - 02:54 AM, said:

It's better to do a factory reset when you install my rom to avoid extra bugs... but you can install it without doing the factory reset. I haven't tested if it works, take a backup first

when I do backup, the CWM can't mount sd-ext, and skipping the backup for sd-ext
tried mounting it manually but it showing mounting error
is this a bug ?
never happened on previous CWM

[mikeioannina]

kimiamania, on 08 November 2012 - 03:20 AM, said:

when I do backup, the CWM can't mount sd-ext, and skipping the backup for sd-ext
tried mounting it manually but it showing mounting error
is this a bug ?
never happened on previous CWM

which filesystem do you use for the sd-ext partition? ext3 or ext4?

[dreluo]

I have tested the lasted rom . The link if fine! i have download it from phone. wifi LEDs call/end call keys work fine. The kernel is faster than 2.6.32 kernel.The available memory is more large! it is seem that all is fine on my RACER! Thanks your work! The last question. Can you port android 4.0.4  to racer with this kernel!

[green_hacker]

mikeioannina thanks for cook racerz. rom buut prob in touch, getting problem in touch....  I calibrated touch but not work..... mainly. problem in keyboards touch .....

[Glock24]

Hi,

I just installed the 20121107 on my Racer and everything seems fine, except for the keyboard, as it does not write numbers. If you type "1234567890" you get "l.adgjqx0" instead. This happens in most but not all apps.

As deluro says, there seems to be more free RAM compared to other ROMS; mine has 46MB free vs ~34MB before, I've got all apps I had installed before.

Even the camera works; it only worked with deadlink's kernel and not vamshi's.

It seems 3D is working, games don't feel any slower.

[mikeioannina]

dreluo, on 08 November 2012 - 09:43 AM, said:

I have tested the lasted rom . The link if fine! i have download it from phone. wifi LEDs call/end call keys work fine. The kernel is faster than 2.6.32 kernel.The available memory is more large! it is seem that all is fine on my RACER! Thanks your work! The last question. Can you port android 4.0.4  to racer with this kernel!

It could be possible but there are some things missing that need a lot of work to get fixed...

green_hacker, on 08 November 2012 - 12:06 PM, said:

mikeioannina thanks for cook racerz. rom buut prob in touch, getting problem in touch....  I calibrated touch but not work..... mainly. problem in keyboards touch .....

What problem do you have exactly?

Glock24, on 08 November 2012 - 02:17 PM, said:

Hi,

I just installed the 20121107 on my Racer and everything seems fine, except for the keyboard, as it does not write numbers. If you type "1234567890" you get "l.adgjqx0" instead. This happens in most but not all apps.

As deluro says, there seems to be more free RAM compared to other ROMS; mine has 46MB free vs ~34MB before, I've got all apps I had installed before.

Even the camera works; it only worked with deadlink's kernel and not vamshi's.

It seems 3D is working, games don't feel any slower.

I can confirm the keyboard bug... very weird

[Glock24]

Wifi sleep policy now works! Now it keeps the connection to a wifi network and does not disconnect when screen turns off or when locking the phone.

3D acceleration seems to work better than before. Enabling HW acceleration in "Air Traffic Control" resulted in garbage output or hard freeze, but now it works.

Great job!

[kimiamania]

mikeioannina, on 08 November 2012 - 06:14 AM, said:

which filesystem do you use for the sd-ext partition? ext3 or ext4?

still use ext2 xD

[noobzone]

I was just now going to report the keyboard bug. noticed it right when trying to set a google account (got my email and password with both letters and numbers) but the touchscreen has an awfull lot of ghost clicks. When trying to tipe a single letter I got every single one except that one. could it be because of the "multitouch" hack? if it was possible could you disable that in a test kernel so that we could rule that one out? didn't got to test anything else as I was in school and was short on battery  xD

[mikeioannina]

noobzone, on 08 November 2012 - 05:17 PM, said:

I was just now going to report the keyboard bug. noticed it right when trying to set a google account (got my email and password with both letters and numbers) but the touchscreen has an awfull lot of ghost clicks. When trying to tipe a single letter I got every single one except that one. could it be because of the "multitouch" hack? if it was possible could you disable that in a test kernel so that we could rule that one out? didn't got to test anything else as I was in school and was short on battery  xD

Try setting Gesture pressure & Gesture blindspot to disabled in Device settings... this should "disable" multitouch.

[noobzone]

mikeioannina, on 08 November 2012 - 05:36 PM, said:

Try setting Gesture pressure & Gesture blindspot to disabled in Device settings... this should "disable" multitouch.

done. but still. ghost clicks are on the menu today appart from that allI have to say is great job! the keyboard bug is from the keyboard apk itself and not from the kernel as I just tested with another keyboard and it worked fine.

Still the calibration that suits me the most, maybe because I'm more used to it is the one in vamshi's lattest kernel :S

[mikeioannina]

noobzone, on 08 November 2012 - 06:39 PM, said:

done. but still. ghost clicks are on the menu today appart from that allI have to say is great job! the keyboard bug is from the keyboard apk itself and not from the kernel as I just tested with another keyboard and it worked fine.

Still the calibration that suits me the most, maybe because I'm more used to it is the one in vamshi's lattest kernel :S

It's weird because I didn't make any changes related to keyboard... can you send me the keyboard apk that worked for you?
Unfortunately we can't disable dual touch completely, it's a limitation of the touchscreen driver and I don't have the knowledge to modify it. Vamshi never released his touchscreen driver sources so the best current option for 2.6.35 kernel is the driver we currently use

[noobzone]

mikeioannina, on 08 November 2012 - 07:16 PM, said:

It's weird because I didn't make any changes related to keyboard... can you send me the keyboard apk that worked for you?
Unfortunately we can't disable dual touch completely, it's a limitation of the touchscreen driver and I don't have the knowledge to modify it. Vamshi never released his touchscreen driver sources so the best current option for 2.6.35 kernel is the driver we currently use

oh well. One day I saw that the android keyboard was 11mb in space and I was like "that's to much" searched for another app and found "smart Keyboard" nice little keyboard with all the options I actually like and it was only 3-4mb so I searched a little bit if you know what I mean and that works perfectly

[GuyOverThere]

mikeioannina, on 08 November 2012 - 07:16 PM, said:

It's weird because I didn't make any changes related to keyboard... can you send me the keyboard apk that worked for you?
Unfortunately we can't disable dual touch completely, it's a limitation of the touchscreen driver and I don't have the knowledge to modify it. Vamshi never released his touchscreen driver sources so the best current option for 2.6.35 kernel is the driver we currently use

If it helps with anything, I use icecream sandwich keyboard from google play, more accurate than gingerbread's default.

I've also though about dual-touch being at least part responsible of ghosts clicks however, like mike I haven't been able to remove it completely, while I've been able to change MT_* reporting to simple ABS_X/Y things while still keeping the little calibration info we have every time it ends the same way: points stop being reported only when a second point is marked, meaning, say you marked point x:129,y:130, and then you marked x:200,y:190, well this will be translated as a line drawn between the two points, like you never upped the finger/tool form the screen after the first point you marked. Very annoying, it has to be related  to IRQ handling but I don't know how to change that :-\ or perhaps a check is needed like if (distance between first point and second > some number) { report new touch event; return IRQ_HANDLED; }

I've a sightly different msm_ts.c than mike in my github sources but still have ghost clicks and not a thing I can do about it so yeah, I concur with mike that for the momment there's nothing much to do than to deal with the msm driver we have =/