MoDaCo is undergoing planned maintenance. Site functionality may be reduced - follow @modaco or @paulobrien on Twitter for updates.

  • Announcements

    • Reminder - MoDaCo position on illegal content

      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 software
      Nintendo 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 be hosted directly in topic via the MoDaCo attachment system
      ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)
      ROMs must give full credit to the original author
      This decision has been taken in light of the huge amount of interest in this area of device customisation within the community, and member feedback! Please note that custom ROM discussion should be kept in specific device sub-areas, (e.g. Kaiser.MoDaCo.com for Kaiser based devices). ISSUES If you have any issues with this policy, please contact me directly via PM. P
    • Support MoDaCo by signing up to a MoDaCo Silver or Gold membership

      To sign up to an annual MoDaCo Silver subscription which will eliminate all ads from the site (as well as giving you access to the MoDaCo Online Kitchens for Android) for only £9.99 using PayPal, Credit or Debit Card, ensure you are logged in to the site, and then click the link below, which will take you directly to the subscription store! You can also sign up to an annual MoDaCo Gold subscription for £29.99, which adds the benefits listed below! PURCHASE A MODACO SUBSCRIPTION - FREE Titanium Backup Mobile for Android worth $5.99! - FREE 1 year PrivateInternetAccess.com worth $39.95! - FREE 1 year LastPass Premium worth $12! - FREE CalcConvert for Pocket PC from Binaryfish worth $17.95! - FREE Calendar Bar for Pocket PC from OmegaOne worth $9.99! - FREE CamerAware for Pocket PC and Smartphone from MoDaCo worth £19.99 / $30! - FREE Chronos for Pocket PC from ActiveKitten worth $14.95! - FREE CodeWallet Pro for Smartphone and Pocket PC from DeveloperOne worth up to $24.95! - FREE Concentrix for Pocket PC from eSoft Interactive worth $9.95! - FREE FlexMail for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE FTouchSL for Pocket PC from Vekoff s.r.o. worth 10 euro / $12.50! - FREE Jewel Challenge for Pocket PC from eSoft Interactive worth $9.95! - FREE John Cody's Alerts Pro for Smartphone from Omnisoft worth $14.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Dutch for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> French for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> German for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Italian for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Spanish for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Dutch for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> French for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> German for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Russian for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Turkish for Smartphone from Lingvosoft worth $49.95! - FREE Note2Self for Pocket PC and Smartphone from WebIS worth up to $19.90! - FREE Opera 8.60 for Pocket PC and Smartphone from Opera Software worth up to $48! - FREE Pocket Informant for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE Pocket Launcher for Pocket PC and Smartphone from Conduits worth $9.95! - FREE PTab for Pocket PC and Smartphone from z4soft worth up to $60! - FREE Resco Explorer for Pocket PC and Smartphone from Resco worth up to $49.90! - FREE Safemode for Pocket PC from monocube worth $12.95 - FREE SplashPhoto for Pocket PC and Smartphone from SplashData worth up to $59.90! - FREE Sprite Backup for Pocket PC and Smartphone from Sprite Software worth $29.95! - FREE Teksoft Glyphs UI for Pocket PC and Smartphone from Teksoft €9.95! - FREE Teksoft HeadsetRemote for Pocket PC and Smartphone from Teksoft €4.95! - FREE Traffic Jam for Pocket PC from eSoft Interactive worth $9.95! - FREE unlock (1 per year) from imei-check.co.uk - DISCOUNT of 10% at MoDaCo FairDeal - DISCOUNT of 10% at Semsons.com - FORUM - AD FREE SITE - FORUM - custom rank / title - FORUM - double competition entries - FORUM - double post attachment space - FORUM - no search flood control - FORUM - priority event registration - FORUM - triple PM space
    • Reminder: Selling items on the forum directly is not allowed

      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 / suspensions / ban.

[maybe solved] Touchscreen does not react after flashing an new ROM

243 posts in this topic

Posted (edited) · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM.

Download: http://www.multiupload.com/93YKJDK5ZI

Edit: new link, since the old one can't work on Gen2 phones

kernel_patch.zip

Edited by leromarinvit
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

hi i just rooted today flashed froyo only to learn that my touchscreen stopped working, i flashed orange stock firmware unsigned version and then rebooted still nothing, left phone off and on charge for 30mins and then tryed booting and everything is working fine, then tried flashing again and again, screen is still working?? guess am lucky but it was kinda strange

ps. im using Swedish Spring RLS4b rom no other changes

Edited by ahac85
0

Share this post


Link to post
Share on other sites

Posted · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM.

Download: http://www.multiupload.com/93YKJDK5ZI

Edit: new link, since the old one can't work on Gen2 phones

What a happy morning for me :) I tried your modified image on my blade and it's seems to be working :)

You are the Hero of the Blade users who can't use Froyo still now :)

Thank you so much to share this!!!!!

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hey!

I've got the same problem (touchscreen doesnt work after installing Swedish Froyo thing or Gingerbread...)

How do i install the kernel patch?

//edit: And what is the "Swedish Spring RLS..." you've uploaded? It's only 6MB, while the original Swedish Spring ROM is more than 80MB... ?

Edited by Pidgey
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hey!

I've got the same problem (touchscreen doesnt work after installing Swedish Froyo thing or Gingerbread...)

How do i install the kernel patch?

//edit: And what is the "Swedish Spring RLS..." you've uploaded? It's only 6MB, while the original Swedish Spring ROM is more than 80MB... ?

Because this is just an update for RLS4

Download the original RLS4 and then do the same when you install a custom rom and after that install the uploaded update for RLS4

Edited by 3lackhawk
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Because this is just an update for RLS4

Download the original RLS4 and then do the same when you install a custom rom and after that install the uploaded update for RLS4

Ok, I've installed CyanoMod7 -> touchscreen doesnt work. If I try to install the 'kernel_patch', I get 'Installation aborted'

I'm going to try Swedish mod now :)

(P.S. I have Build B02)

//EDIT:

I have installed Swedish Spring AND the update leromarinvit has posted, and ............... it WORKS!!

Thanks a lot!! :) :P :)

Edited by Pidgey
0

Share this post


Link to post
Share on other sites

Posted · Report post

Ok, I've installed CyanoMod7 -> touchscreen doesnt work. If I try to install the 'kernel_patch', I get 'Installation aborted'

I'm going to try Swedish mod now :)

kernel_patch.zip isn't flashable, that's just the patch for the kernel source. 3lackhawk is correct, you have to install Swedish_Spring_RLS4b_B10_Test.zip as an update after the normal Swedish Spring install, since it contains just the kernel itself. I should have been clearer about that.

(P.S. I have Build B02)

Me too (Hofer/YESSS), so it should work.

0

Share this post


Link to post
Share on other sites

Posted · Report post

kernel_patch.zip isn't flashable, that's just the patch for the kernel source. 3lackhawk is correct, you have to install Swedish_Spring_RLS4b_B10_Test.zip as an update after the normal Swedish Spring install, since it contains just the kernel itself. I should have been clearer about that.

Me too (Hofer/YESSS), so it should work.

Yeyeyeyye It worked!^^

I have Swedish Spring now (Stable, I've rebooted 2 times and touchscreen keeps working^^)

Thanks a lot!^^

0

Share this post


Link to post
Share on other sites

Posted · Report post

I got a PM asking me how I did it, and thought I'd post it here in case other people are interested too:

The first clue was that whenever the touchscreen wasn't working, the X/Y range would be "unknown" in logcat. I tried manually setting it in the initialization routine, but that didn't work either: no matter what I wrote to these registers, they would always read back 0. So I tried to make sense of the Synaptics RMI4 documentation, and was quite annoyed that it doesn't contain a useful register map, only functional descriptions of the various registers.

As it turns out, that was actually quite helpful for getting me on the right track. Synaptics devices are logically organized in "functions", where each has an ID and its own register blocks. And there's a table which describes the available functions. Wanting to know the address ranges so I could poke around some more, I enumerated them - and saw that only the flash management function was active. From there on it was easy, I read up about this bootloader mode and how to reset the chip and tried it, and it worked. :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

I got a PM asking me how I did it, and thought I'd post it here in case other people are interested too:

The first clue was that whenever the touchscreen wasn't working, the X/Y range would be "unknown" in logcat. I tried manually setting it in the initialization routine, but that didn't work either: no matter what I wrote to these registers, they would always read back 0. So I tried to make sense of the Synaptics RMI4 documentation, and was quite annoyed that it doesn't contain a useful register map, only functional descriptions of the various registers.

As it turns out, that was actually quite helpful for getting me on the right track. Synaptics devices are logically organized in "functions", where each has an ID and its own register blocks. And there's a table which describes the available functions. Wanting to know the address ranges so I could poke around some more, I enumerated them - and saw that only the flash management function was active. From there on it was easy, I read up about this bootloader mode and how to reset the chip and tried it, and it worked. :)

You were in a very deep expert level :)

Thanks the explanation too !

0

Share this post


Link to post
Share on other sites

Posted · Report post

I got a PM asking me how I did it, and thought I'd post it here in case other people are interested too:

The first clue was that whenever the touchscreen wasn't working, the X/Y range would be "unknown" in logcat. I tried manually setting it in the initialization routine, but that didn't work either: no matter what I wrote to these registers, they would always read back 0. So I tried to make sense of the Synaptics RMI4 documentation, and was quite annoyed that it doesn't contain a useful register map, only functional descriptions of the various registers.

As it turns out, that was actually quite helpful for getting me on the right track. Synaptics devices are logically organized in "functions", where each has an ID and its own register blocks. And there's a table which describes the available functions. Wanting to know the address ranges so I could poke around some more, I enumerated them - and saw that only the flash management function was active. From there on it was easy, I read up about this bootloader mode and how to reset the chip and tried it, and it worked. :)

Any chance to made same patch/update for CM 7.0.0?.. (it is 2.3.3 Android). Have you considered contributing to the community to include your patch in CM 7?

While I'm using Linux I not so confident (and in fact I'm just afraid if I brick the phone while preparing custom firmware! It is mine first Android phone I'm learning about) in patching Android kernel (on desktop/server it more easier as you backed up by rescue boot, etc.)

And, yeah, thank you for your hard work!

0

Share this post


Link to post
Share on other sites

Posted · Report post

Works for me also. You rocks!

0

Share this post


Link to post
Share on other sites

Posted · Report post

I got a PM asking me how I did it, and thought I'd post it here in case other people are interested too:

...

easy, I read up about this bootloader mode and how to reset the chip and tried it, and it worked. :)

leromarinvit, Thanks a lot in deed for the progress made towards the issue resolution. Would you please advise FOR NON PROFESSIONALS, how you findings can used to make a touchscreen working say with MODACO Froyo 12 or CM 7.0 Stable.

Or shall I simply wait a bit till you results are validated and then incorporated in ROMs up-issues?

Thanks

0

Share this post


Link to post
Share on other sites

Posted · Report post

Because this is just an update for RLS4

Download the original RLS4 and then do the same when you install a custom rom and after that install the uploaded update for RLS4

Can this be made for CM7?

If so, you are my life saver

0

Share this post


Link to post
Share on other sites

Posted · Report post

Can this be made for CM7?

If so, you are my life saver

That would be great indeed^^

0

Share this post


Link to post
Share on other sites

Posted · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM.

Download: http://www.multiupload.com/93YKJDK5ZI

Edit: new link, since the old one can't work on Gen2 phones

:) Thanks!

i have test , very good!

0

Share this post


Link to post
Share on other sites

Posted · Report post

kernel_patch.zip isn't flashable, that's just the patch for the kernel source. 3lackhawk is correct, you have to install Swedish_Spring_RLS4b_B10_Test.zip as an update after the normal Swedish Spring install, since it contains just the kernel itself. I should have been clearer about that.

Me too (Hofer/YESSS), so it should work.

Magnificent work. I had 3 handsets all with non responsive touchscreens when flashed with anything other than original Orange UK B10 build ROM.

Well done - one very happy member.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

That would be great indeed^^

+1

We need that for CM7

Edited by rapidone
0

Share this post


Link to post
Share on other sites

Posted · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM.

Download: http://www.multiupload.com/93YKJDK5ZI

Edit: new link, since the old one can't work on Gen2 phones

Great work! You're doing ZTE's job for them! :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

Any chance to made same patch/update for CM 7.0.0?.. (it is 2.3.3 Android). Have you considered contributing to the community to include your patch in CM 7?

While I'm using Linux I not so confident (and in fact I'm just afraid if I brick the phone while preparing custom firmware! It is mine first Android phone I'm learning about) in patching Android kernel (on desktop/server it more easier as you backed up by rescue boot, etc.)

And, yeah, thank you for your hard work!

you can submit the patch request to the bug tracker. i'm sure somebody would see it. i also flagged it to one of the devs via twitter.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM.

Download: http://www.multiupload.com/93YKJDK5ZI

Edit: new link, since the old one can't work on Gen2 phones

So, does the touchscreen work with official ZTE kernel without this patch?

0

Share this post


Link to post
Share on other sites

Posted · Report post

Wow, thanks for all the great feedback!

Any chance to made same patch/update for CM 7.0.0?.. (it is 2.3.3 Android). Have you considered contributing to the community to include your patch in CM 7?

I'm quite sure it will work. The patch is obviously there for anybody who wants to use it. However, I'm not yet 100% convinced that this is the best way to fix the problem: The controller reports a configuration CRC mismatch, and ideally, it should be possible to dump the configuration data from a good device and flash it once on each affected device, so that the reset isn't needed any longer. Seems nicer than the sledgehammer method of resetting it "and to hell with configuration". Of course, this would still be done automatically. It's also possible that it won't work - we don't really know what's wrong. Maybe the chip can't be reliably configured for some reason, maybe ZTE just didn't bother. I'd like to at least try the nicer method before actively pushing the patch to anybody.

I'll try to build & upload a CM7 kernel later today to fix the immediate pressing issue of not having any working kernel though.

leromarinvit, Thanks a lot in deed for the progress made towards the issue resolution. Would you please advise FOR NON PROFESSIONALS, how you findings can used to make a touchscreen working say with MODACO Froyo 12 or CM 7.0 Stable.

Or shall I simply wait a bit till you results are validated and then incorporated in ROMs up-issues?

Thanks

Well, in theory it's pretty easy: you take the kernel source tree for your ROM, apply the patch and compile it. However, from a quick glance at the MCR thread, I didn't find any reference to the kernel source, so I guess Paul would have to incorporate the patch. For CM7, see above - give me a few hours. If you want to compile it yourself, you need a Linux system and an ARM cross compiler. This looks like a decent guide.

So, does the touchscreen work with official ZTE kernel without this patch?

Yes it does, but their kernel must contain some sort of fix for this. I don't know what they do exactly, since I haven't found the changes in the binary. Maybe they reset it, maybe they also configure it somehow.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.

...

I do confirm that this has solved touchscreen issue for me as well! Great work! (and patience to read controller func spec :))

Looking forward for incorporation of the patch into other ZTE kernals (and ROMs)

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Yes it does, but their kernel must contain some sort of fix for this. I don't know what they do exactly, since I haven't found the changes in the binary. Maybe they reset it, maybe they also configure it somehow.

I'm a bit confused. I thought the ZTE kernel source (link) when I said official ZTE kernel. Why did try to find fixes in the binary instead of source?

Edited by tlaci
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.