Related
Hi all,
Although I have tried to set it up to 30 seconds by using Advance Config 3.3; the keyboard light still goes dark after 10 seconds. And unfortunately the HD Tweak does not have this kind of setting.
It's annoying especially when trying to write something long at dark places, where sometimes you have to look at the screen and think before you write. The keyboard light goes off and you try to see the correct key, you write again and pause then same thing over and over.
Thanks in advance.
I have the same problem, It's really annoying, any solution???
there is another thread already dedicated to this an there is no solution yet
aegeuss said:
Hi all,
Although I have tried to set it up to 30 seconds by using Advance Config 3.3; the keyboard light still goes dark after 10 seconds. And unfortunately the HD Tweak does not have this kind of setting.
It's annoying especially when trying to write something long at dark places, where sometimes you have to look at the screen and think before you write. The keyboard light goes off and you try to see the correct key, you write again and pause then same thing over and over.
Thanks in advance.
Click to expand...
Click to collapse
It's not length btw, it's called duration.
mallman said:
there is another thread already dedicated to this an there is no solution yet
Click to expand...
Click to collapse
can you link us to this thread?
I've created an app that does what "socket84" was talking here on the forum ( http://forum.xda-developers.com/showthread.php?t=734151 ), which basically is a way to change the default home screen when the user presses the Home button. This works with a hidden setting from TouchWiz. I posted it on Market with the name "SGS Screen Changer".
NOTE: You'll ROOT and BusyBox for the app to be able to do it's work.
http://www.cyrket.com/p/android/com.pedronveloso.samsunghsc/
I've only tested it with the European, Samsung Galaxy S so far.
I've tested with various different firmwares ( JM2, JG5, JM6, JM7 and JM8 ) and it's working ok. Also I've coded a backup mechanism in case things don't work as expected, and later you can restore the file to it's initial state, from the the restore button within the app, or manually by issuing the command "cp /system/default.propBackup /system/default.prop", but verify first that you have the backup file.
> Doesn't work on Froyo yet! The configuration files have changed in those releases, and I've not fixed it yet.
Also, it would be great if people could post the contents of their "/system/default.prop" file in here, along with their firmware number, so I can fix it for different non functioning firmwares. Thanks
Let me know if you've any questions, and all feedback it's appreciated. Also remember this is the first public version, so don't expect it to look pretty, I've focused on functionality and correctness first.
Change-log:
Beta 2 ( 20-08-2010) :
* Bugfixes
* Fixed screen numbering as reported by Limality ( thanks )
Beta 1 ( 18-8-2010 ) : First release
IMPORTANT NOTE: Everyone who had installed the first beta should update it from the Market and set the screen to whichever they want, even if the app did work to them before. People who said it wasn't working, and the ones who said it didn't leave the 4th screen should update and select the screen they want and reboot. All those problems should be fixed in this release. I'll be waiting for further feedback on those ones to confirm if this solved their problems
pedrodh said:
I've created an app that does what "socket89" was talking here on the forum ( http://forum.xda-developers.com/showthread.php?t=734151 ), which basically is a way to change the default home screen when the user presses the Home button. This works with a hidden setting from TouchWiz. I posted it on Market with the name "SGS Screen Changer".
NOTE: You'll ROOT and BusyBox for the app to be able to do it's work.
http://www.cyrket.com/p/android/com.pedronveloso.samsunghsc/
I've only tested it with the European, Samsung Galaxy S so far, but I'm guessing it will work on the American version as well, but I would apreciate feedback on that.
I've tested with two different firmwares ( JM2 and JG5 ) and it's working ok, but I'll probably work for every new firmware out there. Also I've coded a backup mechanism in case things don't work as expected, and later you can restore the file to it's initial state, from the the restore button within the app.
Let me know if you've any questions, and all feedback it's appreciated. Also remember this is the first public version, so don't expect it to look pretty, I've focused on functionality and correctness first.
Click to expand...
Click to collapse
tested! working. great job. dont need any nice UI. this will do
tested with rooted JM5.
not configurable. always get me to screen 4 despite setting it to screen 3 or so on.
"Restore to original settings" doesn't work after reboot it's still screen 4.
Any ideas?
Note: screen 4 is only good for 7-screens SGS. since I've 5 screens I want to make default screen 3
thanks in advance!
Sweet, thanks for this, will give it a ry now
truemagic said:
tested with rooted JM5.
not configurable. always get me to screen 4 despite setting it to screen 3 or so on.
"Restore to original settings" doesn't work after reboot it's still screen 4.
Any ideas?
Note: screen 4 is only good for 7-screens SGS. since I've 5 screens I want to make default screen 3
thanks in advance!
Click to expand...
Click to collapse
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
etc...
Not working here on JG4 Aussie firmware
Limality said:
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
etc...
Click to expand...
Click to collapse
Regardless what I set (tried homescreen 1,2,3,4..) still when pressing "HOME" button it takes me to screen 4...
nice app!
might wanna just add 1 to all the screen numbers just so everyone gets it .
starting at 0 while the numbers shown in touchwiz are starting at 1, is kinda weird
\
so screen 0 = 1 and screen 1 = 2
edit: hmm not working here either on JM5 always gives the last screen as home screen, if i do it myself it works..
Not work with DXJG4
Maybe "One click lag fix 2.3" could be a cause ?
tommy34 said:
edit: hmm not working here either on JM5 always gives the last screen as home screen, if i do it myself it works..
Click to expand...
Click to collapse
cool....mind to share how did you "do it yourself"?
thanks~
truemagic said:
cool....mind to share how did you "do it yourself"?
thanks~
Click to expand...
Click to collapse
here : http://forum.xda-developers.com/showthread.php?t=734151
Thanks for everyone that tested it, your feedback it's apreciated .
Not work with DXJG4
Maybe "One click lag fix 2.3" could be a cause ?
Click to expand...
Click to collapse
No, I've lagfix myself and I'm using MoDaCo ROM and it worked. Did you reboot after setting it? You must reboot for changes to take effect.
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
Click to expand...
Click to collapse
That's easely fixed, I really though it was otherwise because on mine it worked. I'll retest. Humm..Could be that some fimrwares accept 1 as first and others as 0 ? Has more people post I'll find it out. Thanks for reporting that
"Restore to original settings" doesn't work after reboot it's still screen 4
Click to expand...
Click to collapse
The backup it's stored in /system/default.propBackup , you just have to do "cp default.propBackup default.prop" in some terminal as root in case to restore it manually, if the restore button fail's to do it's job.
work's perfectly on my JG5, thank you Pedrodh!
Sent from my GT-I9000 using XDA App
work's perfectly on my JG5, thank you Pedrodh!
Click to expand...
Click to collapse
Nice to know . By the way, you have BusyBox installed from the Market, or you had it bundled with your ROM ?
IIRC, some firmwares (i.e. DXJG4) have a different /system/default.prop and hence will not work.. Cant change manually either
I have installed busybox 1.17.0 when i put mimocan fix
IIRC, some firmwares (i.e. DXJG4) have a different /system/default.prop and hence will not work.. Cant change manually either
Click to expand...
Click to collapse
Would be useful to have the data regarding which firmwares work, and which doesn't. If I did I could check it while executing the app and notify the user properly. Also, I'm in doubt if people who install busybox from the market have a different setup from the ones who doesn't. I'm issuing the linux commands like "echo" , but if the busybox from the market doesn't update the system Path I'll have to pass the entire path when issuing the command. I'll be waiting for more feedback from the users and begin sorting this out.
So far it seems that everyone who has MoDaCo and/or JG5 has been able to use this.
OK, updated the app. I found out what was wrong, should now be fixed.
IMPORTANT NOTE: Everyone should update it from the Market and set the screen to whichever they want, even if the app did work to them before. People who said it wasn't working, and the ones who said it didn't leave the 4th screen should update and select the screen they want and reboot. All problems should be fixed in this release. I'll be waiting for further feedback on those ones to know if it solver their problems
Wish I could test it for you, but currently my phone is bricked.
Default screen is maybe the only option I am missing in TW.
However when I tried this hack in JPJG8 it didn't work, so if your app is just editing the /system/default.prop file, most chances are it won't work either.
Ok, I got a report that the fix did in fact work.
Pimp My Xoom .01
Todo:
- Bug reported Themes not applying.
- Straighten out the GVoice with a little more instruction.
- Add new Theme updates.
- Add new GVoice frameres hack update.
Please add any feature requests or bugs here
so I can hit the code hard on the weekend. You dont haffta but I might miss your request in the forum traffic.
Thanks.
Version Record:
.01 4/3 First.
.02 4/4 Fixed major bug in Sound managment utility. Redownload if you have .01.
Pimp My Xoom started as a utility to help me add and remove notification sounds from my Xoom easily from a massive library of sounds compiled by XDA developers from every Android phone ever.
Then it got ambitious. Pimp My Xoom now includes.
-Add/Remove/List/play installed notification sounds.
- Includes just the notifications from the Android Sounds library here on XDA.
-Add/Remove Bignadad's Themey type thing. Red and Blue
http://forum.xda-developers.com/showthread.php?t=1015434
-Add/Remove 3 boot animations. Attribution in app.
http://forum.xda-developers.com/showthread.php?t=998161
http://forum.xda-developers.com/showthread.php?t=991086
-Add/remoove GoogleVoice hack FOR 3GONLY
http://forum.xda-developers.com/showthread.php?t=1015857
-Add/Remove Keymapper mod.
http://forum.xda-developers.com/showthread.php?t=1016594&highlight=keylayout
-Add AdBlocker
http://forum.xda-developers.com/showthread.php?t=991082
TO Install and use:
1. YOU MUST BE ROOTED.
2. YOU MUST HAVE YOUR XOOM IN DEBUG and connected via USB.
3. Unzip PimpMyXoom and all it folders to a folder of your choice.
4. Run the PimpMyXoom_01.exe
5. Most buttons should be self explanatory.
YOU ACCEPT ALL RISK IN MODIFYING YOUR XOOM FROM STOCK.
Download PimpMyXoom
Reserved for future use.
Download failed. Will continue to try and download. Can't wait to try this! Thanks for the contribution!!
Instien said:
Download failed. Will continue to try and download. Can't wait to try this! Thanks for the contribution!!
Click to expand...
Click to collapse
Failed? Hmmm. lemme try.
Instien said:
Download failed. Will continue to try and download. Can't wait to try this! Thanks for the contribution!!
Click to expand...
Click to collapse
Your right. Mediafire blows up and says it cant. What the heck?
Edit: In a couple seconds I got the "Click to start download" and I clicked it and it started.
Password, really....and I get this how?
jmc2543 said:
Password, really....and I get this how?
Click to expand...
Click to collapse
Hang on. Stevenge just found a nasty bug. Reuploading... I passworded to freeze the downloads.
ah ok. makes sense.
All fixed. Carry on!
sorry im noob
sorry for the stupid ? but y will gvoice hack only work with xoom 3g was just wondering cuz i have wifi version
it works but...
it worked great but i did not get the full theme for the red or the blue my back home and apps on the bottom left hand corner did not theme also the same with my ariplane mode wifi etc...
moz90 said:
it worked great but i did not get the full theme for the red or the blue my back home and apps on the bottom left hand corner did not theme also the same with my ariplane mode wifi etc...
Click to expand...
Click to collapse
Not sure if it is just mine, however the reasonwhy the GVoice is listedthat way because on mine it tries to set up Gmail and when skip is hit it freezes. It will allow you to text, however only through contacts and will not let you read them for some reason.
Been looking into it all night.
stevenege said:
Not sure if it is just mine, however the reasonwhy the GVoice is listedthat way because on mine it tries to set up Gmail and when skip is hit it freezes. It will allow you to text, however only through contacts and will not let you read them for some reason.
Been looking into it all night.
Click to expand...
Click to collapse
Did yours fully theme?
Sent from my Xoom using Tapatalk
moz90 said:
Did yours fully theme?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
It looks like it may be broken for some reason. I am going to test a bit more and let JT know.
stevenege said:
It looks like it may be broken for some reason. I am going to test a bit more and let JT know.
Click to expand...
Click to collapse
Sounds good im going to donate on 15th to em this makes it so easy to theme I love it I hope gets fixed
Sounds cool, can't wait till I can give it a try during class tonight!
i have been talking to him, however when you theme does it make you sign into your account again when you go to the market or is this just me?
I went to extract the file and it notified me that there are duplicate files, name wise, in the \New folder\RedAndBlue\3g\stock area both labeled framework-res.apk. How exactly you got it to name two files the exact same i dont know, but this may be an issue that is causing troubles that some are having with the particular theme
Hmm found a bug I believe. In the sounds area when I click Get Installed Sounds it starts CMD , starts the daemon wityhout really doing anything aparant. If you try to click it again I get an error saying "Error; The same variable cannot be used for more than one control. The current thread will exit. Specifically vDevSounds Line#162: GUI,Add,ListBox, x600, y113, w260, h500 vDevSounds, %formated%"
Also the application is not work AT ALL for me. I have my Xoom in debug mode but whenever I click a button in pimp it flashes a few CMD windows real fast then sits there. I reboot and nothing has changed.
jmc2543 said:
Hmm found a bug I believe. In the sounds area when I click Get Installed Sounds it starts CMD , starts the daemon wityhout really doing anything aparant. If you try to click it again I get an error saying "Error; The same variable cannot be used for more than one control. The current thread will exit. Specifically vDevSounds Line#162: GUI,Add,ListBox, x600, y113, w260, h500 vDevSounds, %formated%"
Also the application is not work AT ALL for me. I have my Xoom in debug mode but whenever I click a button in pimp it flashes a few CMD windows real fast then sits there. I reboot and nothing has changed.
Click to expand...
Click to collapse
Hmmmmm, thievish odd. The siund thing is the bug I found too but was fixed with the update to the program.
Try deleting it and really downloading the program.
QUICK UPDATE:
Installing chainfire3d and using their "nvidia shader driver" fixes alot of games e.g. Angry Birds! (thanks to scottcom who sent me the tip via pm!)
This is a very simple ICS build using the Andromadus repo + Google AOSP code (rather than CM). This is just a quick update because we got the hw accel hack working
WORKING:
HW Accel (hack version i.e. not natively)
WiFi (TAKES TIME TOTURN ON)
Data
Calls
Superuser
Full Keyboard/Orientation
Audio
Basic ICS
Bluetooth
NOT WORKING:
GPS
Full Accel
etc.
NOT TESTED:
SD Card
FM Radio
most things
DOWNLOADS:
ROMS:
ALPHA II (by crowstar)
http://www.multiupload.com/5KGQH76YZN
ALPHA III CM (by Flinny)
http://www.multiupload.com/GESOB7P3JA
KERNEL:
http://www.mediafire.com/?2xbjvc1bk71xokx (OdiemanSAM's THANKS!)
!NEW! GAPPS:
http://www.multiupload.com/RQTF41Z1I2
THANKS:
To all involved! (Flinny, Ionic, guy who's name begins with an s who I forget)
I'll update the OP in the morning, need to go to bed
HOW TO BUILD ICS FOR YOURSELF!
Code:
mkdir android
cd android
repo init -u git://github.com/Andromadus/android.git
repo sync
then you can:
Code:
. build/envsetup.sh
lunch
5
make -j[NUM OF CORES x2] otapackage
I'll probably flash this ROM as a DD when it has 3G or real HW acceleration working, whichever comes first GJ so far though, I'll probably give it a whirl to see how it is later tonight, compare it to the port maybe in terms of speed and such
First off, here's how I flashed:
1. Superwipe
2. Flashed Rom
3. Flashed Odie kernel
4. Flashed gapps
5. fixed permissions
It booted really fast and looks absolutely clean. I immediately connected to data, but not wifi - even though the connection is strong here. My data says 3G, but could be HSPA, and I jumped on the browser just to double check. It worked.
Things I noticed:
Scrolling is choppy, but I know that's easily fixed.
The market would not download (as expected), so I ran the fix via adb. When I tried Market again, it froze the phone and I had to do a battery pull.
The home button is not working so well. Takes 3-4 pushes to get it to work, it's easier to just to use the back button.
Didn't get a chance to look at much else after the phone froze.
I really appreciate you posting this up. I know you've been working hard and probably waiting for something that can be played with, and you got that here. Thanks again, I 'll post more impressions in a bit.
enserio said:
First off, here's how I flashed:
1. Superwipe
2. Flashed Rom
3. Flashed Odie kernel
4. Flashed gapps
5. fixed permissions
It booted really fast and looks absolutely clean. I immediately connected to data, but not wifi - even though the connection is strong here. My data says 3G, but could be HSPA, and I jumped on the browser just to double check. It worked.
Things I noticed:
Scrolling is choppy, but I know that's easily fixed.
The market would not download (as expected), so I ran the fix via adb. When I tried Market again, it froze the phone and I had to do a battery pull.
The home button is not working so well. Takes 3-4 pushes to get it to work, it's easier to just to use the back button.
Didn't get a chance to look at much else after the phone froze.
I really appreciate you posting this up. I know you've been working hard and probably waiting for something that can be played with, and you got that here. Thanks again, I 'll post more impressions in a bit.
Click to expand...
Click to collapse
I'd suggest installing setCPU or something similar to check those lockups, as there was a known(ish) issue in the port with Odie's kernel clocking too low (at 122 mhz) so if you could bump that up and also see what the upper end is? I'll probably do it myself eventually, and since I'm super lazy ill just pack the apks for titanium and setCPU into the app folder of the ROM itself and give it a whirl haha
My wifi works but the icon doesn't show up so its as if I have no connection. My home button is also bugged.
Edit: Also the gallery apo doesn't work and the messaging app seems to be missing
Sent from my HTC Vision using XDA App
Is the camera working in this build? Its the last fix I'm looking for before going back to ics xD
ohshootrawr said:
Is the camera working in this build? Its the last fix I'm looking for before going back to ics xD
Click to expand...
Click to collapse
no it doesn't, that requires a new kernel which will be updated in the DHD section very soon
crowstar said:
no it doesn't, that requires a new kernel which will be updated in the DHD section very soon
Click to expand...
Click to collapse
Wewt, good news at last! Thanks for the reply
Rom runs good for an alpha
- The Homebutton ( i know this is known ) but it seems like its reacting like a back buttons sometimes.
- I often get a red border when tapping next in a menu or install in the market.
- SDcard works but no mass storage on pc
Edit 2: the : and ; are not located at the fn button but at the shift button.
So far i already like this better then de Desire S port
Edit: I have no messaging app, anybody else who hasn't?
Edit 3: I tried buttonremapper to try and remap the home button but no luck
johrie said:
Rom runs good for an alpha
- The Homebutton ( i know this is known ) but it seems like its reacting like a back buttons sometimes.
- I often get a red border when tapping next in a menu or install in the market.
- SDcard works but no mass storage on pc
Edit 2: the : and ; are not located at the fn button but at the shift button.
So far i already like this better then de Desire S port
Edit: I have no messaging app, anybody else who hasn't?
Edit 3: I tried buttonremapper to try and remap the home button but no luck
Click to expand...
Click to collapse
Your home button was acting like a back button? Mine was just being unresponsive until about the third press. Interesting.
aside from that, did you notice if your handset got warm while running this rom? Mine did, and I forgot to mention it in my post.
Hey the key layout and keychar file have move_home wrong
Sent from my HTC Vision using XDA App
I ran this rom for about 45 mins and had two lockups where I had to battery pull, first was upon signing into google and it goes to the wifi screen...locked up...rebooted signed in fine and played around for a bit...yea no messaging app and then I noticed it syncd emails and upon c hecking gmail from the notification bar it locked up in gmail..I then restored to cm7...data worked though tmobile usa
Sent from my HTC Vision using XDA App
enserio said:
Your home button was acting like a back button? Mine was just being unresponsive until about the third press. Interesting.
aside from that, did you notice if your handset got warm while running this rom? Mine did, and I forgot to mention it in my post.
Click to expand...
Click to collapse
No not having problems with it being to warm. Running it now since my post and still no problems except the usuals.
And about the homebutton, it also looks app related. For example in whatsapp it just does nothing, but in the browser it reacts as a back button.
Seems like someone in the desire s port thread fixed the home button. But i found something new with the hw kayboard. Capital d doesn't work.
Sent from my HTC Vision using XDA App
What particular files fix the software keyboard, allow hardware keyboard to rotate it and manage the keyboard lights??? Thanks
Sent from my HTC Vision using XDA App
Headphones not working properly: (
xT4Z1N4TRx said:
What particular files fix the software keyboard, allow hardware keyboard to rotate it and manage the keyboard lights??? Thanks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
the IDCs I think. But I'm not having these issues, try out some of the kernels by odiemanSAM. See which one works best
johrie said:
Headphones not working properly: (
Click to expand...
Click to collapse
That's to be expected. It's an alpha after all
bogdan5844 said:
That's to be expected. It's an alpha after all
Click to expand...
Click to collapse
I know but in Odies last kernel they worked perfectly.
Let me be more precise.
When i plug the headphones in they wil connect and work. Then i tried to skip a song and they dont work anymore and the phone speaker takes over.
Sent from my HTC Vision using XDA App
crowstar said:
This is a very simple ICS build using the Andromadus repo + Google AOSP code (rather than CM)...
Click to expand...
Click to collapse
Could you please write a short "how-to: compile ics for htc vision"?
I would like to build it on my machine but I don't know how...
Thank you!
g4rb4g3 said:
Could you please write a short "how-to: compile ics for htc vision"?
I would like to build it on my machine but I don't know how...
Thank you!
Click to expand...
Click to collapse
done! 10charcahrcahralsdfja;lsiht
Some time ago I ordered a px6 Max10 with 720p screen. The lcd screen somehow broke in the mail (I think they knowingly sent it to me broken... but that's just my opinion), and I sent them pictures of this. Dasaita sent me a new screen... or at least they were SUPPOSED to. A month and a half later (today) the WRONG part arrived in my mailbox. They sent me the outer glass instead of a new 720p screen. So here I am more than 2 months after I ordered this thing, it is STILL not in my vehicle. I am sooo friggin angry!
Anyway, I sent them an email but we're probably talking yet another 6 to 8 weeks... and that's if they get it right this time, which I doubt. I am fast coming to the conclusion these people are slightly less than honest.... but that's another thread.
I was thinking....
I do have a Dasaita px5 with a 1024x600 screen. Would it be possible just to take the screen off the px5 and stick it on the px6? This might be far easier than expecting much more from Dasaita at this point. After seeing what I saw today in the mail that they sent me, I don't think I am ever going to see a working 720p screen out of them. I have a feeling they are just going to jerk me around until I get tired of trying.
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
ojuniour said:
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
Click to expand...
Click to collapse
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Bob_Sanders said:
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Click to expand...
Click to collapse
Then just flash the 1024x600 update file (including the MCU if necessary )
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Noway
woggles said:
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Click to expand...
Click to collapse
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
HighWay7777 said:
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
Click to expand...
Click to collapse
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
Great post.
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Al Ferro said:
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Click to expand...
Click to collapse
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Bob_Sanders said:
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Click to expand...
Click to collapse
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
.
.
Al Ferro said:
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
Click to expand...
Click to collapse
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
sitealpha said:
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
Click to expand...
Click to collapse
Did you use one of the pre-made display fix files on the Russian yandisk repository?
HighWay7777 said:
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
Click to expand...
Click to collapse
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
From reading the forums and contributing, probably FFS.
marchnz said:
From reading the forums and contributing, probably FFS.
Click to expand...
Click to collapse
I tried to look for the right files but wasn't successful. But what do you mean by probably FFS??
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
I had the same issue and it took forever finding it. Just rename either dmcu.ext. I tried editing the other, the depository I used no longer existed and any Google search came here.
The new place were I got the dmcu.ext file.
Yandex
Finds everything
disk.yandex.com