Right so here's the deal:
As of now, flashing a galaxy s rom boots up fine and gets me to the lockscreen...however, touchscreen doesn't work and so I can't test any of the other features (wifi, bluetooth, camera, etc.).
The aim of this thread/project is to create a "flash-pack" that will allow us to flash ICS Galaxy S AOSP/CM9 based roms (much like Hanthesolo's pack for GB roms)
Sooo, let's get to work:
Touchscreen
i know that files in /system/lib/hw and /system/usr/idc are necessary for it to work, but replacing them makes no difference. Ideas?
reserved just in case
theraf said:
Right so here's the deal:
As of now, flashing a galaxy s rom boots up fine and gets me to the lockscreen...however, touchscreen doesn't work and so I can't test any of the other features (wifi, bluetooth, camera, etc.).
The aim of this thread/project is to create a "flash-pack" that will allow us to use ICS Galaxy S AOSP roms (much like Hanthesolo's pack for GB roms)
Sooo, let's get to work:
Touchscreen
i know that files in /system/lib/hw and /system/usr/idc are necessary for it to work, but replacing them makes no difference. Ideas?
Click to expand...
Click to collapse
So it could only be a matter of finding how to get the touchscreen working to get all the galaxy s roms working if I understand? This is if every other thing work indeed. I've always aksed myself wath was so different between them that prevent us to be using their rom. Hope you get the touchscreen working so you can test if evrething works fine.
theraf said:
Right so here's the deal:
As of now, flashing a galaxy s rom boots up fine and gets me to the lockscreen...however, touchscreen doesn't work and so I can't test any of the other features (wifi, bluetooth, camera, etc.).
The aim of this thread/project is to create a "flash-pack" that will allow us to flash ICS Galaxy S AOSP/CM9 based roms (much like Hanthesolo's pack for GB roms)
Sooo, let's get to work:
Touchscreen
i know that files in /system/lib/hw and /system/usr/idc are necessary for it to work, but replacing them makes no difference. Ideas?
Click to expand...
Click to collapse
The touchscreen mostly don't work because the I9000 uses a different touchscreen drivers than us. The i9000 uses the mxt224 drivers and we use the qt600xxx (I don't remember the digits) drivers. We do however use the same touchscreen but only with a different driver. And I think the changes between those drivers can fix the US home button problem in the US players.
zaclimon said:
The touchscreen mostly don't work because the I9000 uses a different touchscreen drivers than us. The i9000 uses the mxt224 drivers and we use the qt600xxx (I don't remember the digits) drivers. We do however use the same touchscreen but only with a different driver. And I think the changes between those drivers can fix the US home button problem in the US players.
Click to expand...
Click to collapse
the drivers are in /system/usr/idc right?
theraf said:
the drivers are in /system/usr/idc right?
Click to expand...
Click to collapse
Not exactly. The drivers itself are in the kernel. the file in /system/usr/idc is the calibration file for the touchscreen. I think it indicates the kernel where the touchscreen should calibrate. The thing is I think the I9000 took the mxt224 drivers from crespo because I tried one day from our kernel source and it didin't work. (Maybe I didin't have the right calibration tool too.)
zaclimon said:
Not exactly. The drivers itself are in the kernel. the file in /system/usr/idc is the calibration file for the touchscreen. I think it indicates the kernel where the touchscreen should calibrate. The thing is I think the I9000 took the mxt224 drivers from crespo because I tried one day from our kernel source and it didin't work. (Maybe I didin't have the right calibration tool too.)
Click to expand...
Click to collapse
ok, but since i'm using the ypg1 kernel, all i need to do is swap the correct files from the galaxy s /system folder
Related
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
riddelln said:
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
Click to expand...
Click to collapse
I would suggest checking out Cyanogen's IRC. There are a number of people in there who could help you with this.
You need to run the extract-files script or the unzip-files scripts in devices/htc/passion before you can build. the product should be "full_passion"
After that step there are some things still not working such as camera and playing videos. Logcat says that the permissions in /dev are not correct and they cannot access the /dev/vdec and audio as well. I havnt got past that part yet using either 2.6.32 or 2.6.34 kernels.
This is a MIUI GB 2.3.xx rom ported from stock ZCPK9(China version) rom with miui patchrom.
---FLASH AT YOUR OWN RISK---
I'm now busy preparing for college entrance exam so I won't (perhaps) continue develop before I get into college
Not working:
GPS(Don't know why)
Not perfect:
Theme
DownloadProviderUI
SideKick
ClockPackage
Default language is Chinese.
App2SD(Cause reboot every time when you switch an App between SD and internal memory but actually it has operated successfully)
Ugly statusbar transparent.
Not proted now(All using stock one):
MIUI Settings
MIUI Camera
MIUI SoundRecorder
MIUI SuperUser
MIUI FileManager
MIUI Browser
MIUI Gallery3D
(And some other MIUI apps)
Features:
All MIUI features except that mentioned above (plus that I forgot and not find).
GUI installer by Aroma.
Optional Ad-hoc patch, Gapps, no keyboard light patch, USA keyboard patch.
Something wonderful:
Press home at lock screen to turn on torch.
Press home + back at same time to take screenshot.
Press menu + volum up to turn background light max(temporary).
Thanks to:
Myself , MIUI team and friends at XDA and Sdapk.
How to install:
1. Make sure you have rj's or Entropy512's installed. This rom does not contain kernel.
2. Download rom and place in your sdcard.
3. Reboot into recovery.
4. Wipe /data as well as anything else if you are first install this rom.IMPORTANT!
5. Choose install zip and this will start Aroma Installer.
6. Choose any patch you like in Aroma Installer and finish install it.
7. You will reboot automatically.
8. Be patient while first boot up.
9. Congratulations!
Screenshots:
Change log:
Code:
MIUI.2.3.xx.Noisyfox.01b
Fixed FC when headset plug in
Add USA keyboard patch
MIUI.2.3.xx.Noisyfox.01a
Fixed Settings Fail After Wipe /data
MIUI.2.3.xx.Noisyfox.01
Initial Release
Download:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0/downloads
Develop:
If you are interested in this project, you can get fully source code from here:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
anil_kilic said:
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
Click to expand...
Click to collapse
rj's is better.
pmdisawesome said:
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Click to expand...
Click to collapse
It works partly.
This is sweet, good job!!
I followed instructions to the letter. Seemed to flash fine but it is now sitting at the black Samsung screen screen for about 20 minutes. How long has it taken for 1st boot? Tried re-flashing, clearing cache, etc.
change your kernel to rj's kernel and flash again.
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
tsg2513 said:
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
Click to expand...
Click to collapse
Dont install . rj's kernel is for only INTL devices . Sorry i think your device is INTL and replied.
could you make a port for the 4 inch sgp?
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
mrjaredbeta said:
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
Click to expand...
Click to collapse
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
raishiro said:
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
Click to expand...
Click to collapse
Are you saying that after you re-flashed entropy's kernel the buttons work? Also, have you checked to see if the GPS works?
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
raishiro said:
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
Click to expand...
Click to collapse
Great! Can you please check if GPS works?
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
raishiro said:
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
Click to expand...
Click to collapse
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
tsg2513 said:
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
Click to expand...
Click to collapse
Anyone know how to get the GPS working?
So after a couple of hours searching the web, it may be that the GPS problem is inherent in MIUI 2.3.
Hi all,
Since i'm unable to start a thread in the android development forum I try here. Hopefully Arrrrgh won't get Arrrrgh'd at me for posting this..
I have a problem which I hopefully get support for. I have tried all Android roms for the touch pro2 which none will boot or get past the ACL bootlogo.
I've tried every imaginable way to get it working but all are resulting in a kernel panic. I tried the NAND versions and the SD versions but both options results in the same kernel panic.
First I thought it was the SD formatting problem but after trying 4 different sizes and brands I excluded this as a possible cause.
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
I'm able to pull logs i'm ready and willing to pass the logs for supporting this device. I've found a similar thread by Z!nk / Z1nk but he gave up on the device before the developers could get to it.
So hopefully there is a developer willing to add this version to the android roms.
Thanks for reading and hope to hear from anyone soon.
Cheers,
Alchedin
[edit] The device has security unlocked and is HSPL'd [/edit]
Alchedin said:
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
Click to expand...
Click to collapse
How can we correct you if you're wrong - you need to tell us what phone variant you have. There's a surefire way to know as well...
It's kind of the first question in the FAQ...
Either way, the fact that you can't boot either makes me think you have a clone. There was another fellow with a clone (perhaps the one you mentioned?) that was unable to boot XDAndroid because he didn't have the same hardware. If you run HaRET.exe with no startup.txt, what does it say?
Edit - Regardless, I would focus on one build and try to get that to work. FRX07.1 is probably the "simplest" from that perspective.
Edit2 - Also, you seem to indicate it's a kernel panic. Why no logs?
Dear Arrrghhh,
Thanks for replying.
Ok, looking at the faq it states my phone should be a Rhod100 (complete: NM8RHOD100) which seems, when googeling, to be some kind of T-Mobile version. At the moment i'm running a deepshining
I ran the rom without a startup.txt and it gave me the following message: Found machine Rhodium. Hope this is the info you needed?
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Will keep you informed since I'm not at home.
Alchedin said:
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Click to expand...
Click to collapse
Logs? How do you know it's a kernel panic? What kernels have you tried?
arrrghhh said:
Logs? How do you know it's a kernel panic? What kernels have you tried?
Click to expand...
Click to collapse
Hi Arrrghhh,
Attached are the adb logs, which I hope is the info you need. This is what I get when using FRX07.1 like you advised.
But I have three questions if i'm not too bold:
1. Did you advise this version because it's more thoroughly when it comes to finding a issue?
2. When looking at the logs, is there something wrong with sound or something?
3. I'm able to pull logs of NAND builds if you like? They seem to be more complete when it comes to information on boot.
Cheers,
Alchedin
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Alchedin said:
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Click to expand...
Click to collapse
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
arrrghhh said:
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
Click to expand...
Click to collapse
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
arrrghhh said:
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
Click to expand...
Click to collapse
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Alchedin said:
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Click to expand...
Click to collapse
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
wizardknight said:
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Click to expand...
Click to collapse
I used the same ts-calibration file that was created during the first boot of gbx0c. Like I stated earlier, I only replaced/removed the zimage, module and data.img file every time I switched kernel.
Should I also re-calibrate every time when switching kernels?
arrrghhh said:
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
Many thanks for your interest and pointers arrrghhh, I will look into kernel stuff and such, maybe i'll get some of it working :fingers-crossed:
I have little to no development/linux/android skills but I can at least try to learn it.
Cheers
P.S: In a earlier stage playing around with NAND builds I managed to use the boot.img of the CM9-ICS_X1_testbuild1 in combination with the CM7.2 of walter79 and got it running in landscape mode, if this worked for me I can go from there.
Bit by bit i'm getting a hang of it.
Alchedin said:
Should I also re-calibrate every time when switching kernels?
Click to expand...
Click to collapse
No, as I state in all my threads about calibration - once you get a good calibration file, save 15,000 copies of it and re-use it constantly. There's no need to constantly recalibrate.
Ok here we go, sorry for the big read..
I hope I can be as precise as possible. This is about the NAND builds i've tested.
I installed ICS like in my last post again and made a CWM backup of the whole phone.
After this I did a new task29 and reflashed everything till I got back into CWM.
This time I installed the OMGB stable release with the kernelpatch + gapps.(seems the most advised build) Factory reset/data/cache/etc just to be sure.
Rebooted the device and let OMGB do it's thing, thus resulting in a kernel panic - can not sync issue. This is clearly a default message on this phone which I am in peace with. (log1)
Now for the fun part, I had this ICS testbuild backup up earlier and only did a restore of the boot part. Cleared the data/cache/etc again and rebooted.
This time it just boots fine into OMGB... (log2) previous attempts resulted in a landscape layout which i wasn't able to adjust myself, but this time I got the portrait mode correct! The only part which isn't working is the keyboard and hardware buttons.
Seems the "default" startup process is hanging in the part of the AudioFlinger? I compared the 2 logs but I can't see anything really which normally would result in a kernel panic.
Attached are the logs for the default OMGB boot (log1.txt) and the ICS modified boot + OMGB system (log2.txt)
Is this still different from any other Rhod100 or just a small adjustment? If this is really unknown I will break the phone to pieces and give up on it :silly:
I'll keep this config on the phone a bit longer since data and phone is working.
Thanks for reading
Cheers
-No sound
[Update]
Made a finding myself, the problem for my phone lies within the libhtc_acoustic.so removing this file made NAND boot up for the first time on this phone. Now looking for a compatible acoustic replacement which generates sound.
Going to try copying/pushing the file from FRX0.7 to NAND CM7.2 and see what it does. Including replacing my csv's from WinMo in the /system/etc folder.
[Update2]
Installed CM7.2 2.6.27 version today and used the FRX0.7 aucoustic.so, which resulted in a perfectly working android without sound...
now going after the csv's, which I hope gets me sound.
arrrghhh said:
[snip]...
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Alchedin said:
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Click to expand...
Click to collapse
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
arrrghhh said:
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
Click to expand...
Click to collapse
The interesting parts were the updates I posted. I did copy the csv's from the WinMo earlier, which were instructed by you (using total commander and such), but can't remember if it did produced sound.
But then...
I switched over to NAND CM7.2 by Walter79 and replaced the csv's in the CM7.2 zip file at location /system/etc (audioparatable.csv etc.)
Also I used the libhtc_acoustic.so from here
And ADB pushed the .so into the /system/lib folder.
When running logcat I see that the csv's are used and the audio routing is ok, but still didn't produce sound. Thought there were some other locations were the csv's are stored which I will also replace with mine. But didn't get to that yet.
Just tinkering with files really.. that's as far as I can go since I'm no developer.
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Alchedin said:
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Click to expand...
Click to collapse
I don't know how else to phrase that...
Although, I might have misread your statement. I thought you said you replaced a lib from FRX07.1 - which wouldn't boot for you. GBX0C did boot, so it seems the new acoustic code actually helps your phone.
So now I'm not sure what the deal is. I know OMGB uses the new acoustic, and I was under the impression that the CM ROM did as well. Did you try GBX0*? Basically the NAND version of GBX0C.
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
dhruvraj said:
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
Click to expand...
Click to collapse
Flash stock firmware, i seriusly doubt that it can solve your problem, but give it a try..
dhruvraj said:
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
Click to expand...
Click to collapse
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
ideopath said:
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
Click to expand...
Click to collapse
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
dhruvraj said:
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
Click to expand...
Click to collapse
Its a pleasure @dhruvraj, i remember how good it felt when i fixed it, so HTH.
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
cosmacol said:
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
Click to expand...
Click to collapse
Actually the script didnt work for me either - i opened an adb shell, su'd to root and did this as a one-liner
Code:
cyttsp_fwloader -dev /sys/devices/platform/spi_qsd.0/spi0.0 -fw /system/etc/firmware/touch_smultron_sony.hex -verify_only
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
Click to expand...
Click to collapse
Thanks for the headsup, i was thinking this was a possibility if the problem comes back on a future rom!
how do u think about this?
my touch didnt work on bottom screen area (see attchment).
it happen when ive use phone for long time or when my phone become warmed.
yes, i sent from my phone using Xda Premium, so what?
I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance
Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.
i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.
When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD
Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?
It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.
I think im going to stick to the stock for the now. Camera is the best there
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.