Related
Hi all,
I frequently charge my X1i through USB. There are 2 problems with this method, however.
1) The device goes into USB drive mode, disabling my SD card apps (I keep them on SD card AT ALL TIMES due to frequent backups/restores)
2) Screen does not turn off! while connected to computer! The screen only dims, but does not turn off.
WITHOUT resorting to a) plugging into wall outlet b) connecting to Activesync, is there any to fix these behaviors?
Thanks!
just let it go into activesync mode, that way you can still access your files on your phone and micro sd card from both your pc and phone. And if you dont like the screen not turning off, they just change the settings or just press the power button, to shut off the display.
I know about the power setting, but when your computer is connected to the computer via USB, it refuses to turn off the screen (only dims it)
what? one simple button press and the screen is off. the device is still visible to the pc. I do it all the time - r3a generic uk rom.
in power options u can set after what time it disables screen... default is never
what? one simple button press and the screen is off. the device is still visible to the pc. I do it all the time - r3a generic uk rom.
Click to expand...
Click to collapse
Weird. When I'm connected to Pc, it dims the screen, it does not shut it off. Also, it does NOT auto-shut of screen after the 2 minutes specific in the Power options
You can also use "safely remove devices" to disconnect the data connection from the phone, it'll still charge.
There's nothing we can do AUTO. But like said before, a simple pression on the power button will do it, or you can use My Mobiler and press F11 on your PC.
stisev said:
Weird. When I'm connected to Pc, it dims the screen, it does not shut it off. Also, it does NOT auto-shut of screen after the 2 minutes specific in the Power options
Click to expand...
Click to collapse
Yep, I've had 5 different WinMo devices since '05 and they all worked as expected except the X1. I like to use it as an MP3 player at night, Pocket Player has a sleep timer built in so I just like to leave it running as I drift off most nights. But if I do anything, change the volume, rewind, anything at all the screen comes back on and stays on until I hit some other button to turn it back off. All my other devices obeyed the settings you set in the Power tab, but not the X1...
I'd very much like the screen to auto-off if I tell it to while on USB power. It's not only wasting power, but it wakes me up and gets me fumbling for the tiny power button at 2 in the morning. Any fix would be greatly appreciated.
Thanks,
Peter
I bumped up thread: http://forum.xda-developers.com/showthread.php?t=561832 Since it has a better title and shows the exact same unresolved issue...
Reg Fix
Adding this potential fix here as well so anyone subscribed to this thread sees it.
Ok, I think I have a fix for this. I googled around some more and found that this might be an HTC problem more than an SE one. There were various registry keys people suggested to try to fix the 'backlight problem' - which may or may not be related. None of those suggestions seemed to work, but I kept changing keys myself and eventually found this seemed to do the trick.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\ACUserIdle: 120
I confirmed that changing this value affects the amount of time before my X1's screen turns off - but my MP3s still play with the screen off and my phone wakes on receipt of a new call. This value is the # of seconds before the screen turns itself off (in this case 2 minutes). You do need to soft reset for the change to take effect.
This doesn't seem to be posted anywhere else that I've found doing this to fix this issue issue - I changed a few other registry keys as well that might be enabling this fix. So anyone with this problem, please do give this a try and if it doesn't work I'll post the other keys I changed as well - and if it does then post to say so and we're good
Peter
Update: I tested it also while hooked up to the computer and it does work with the phone accessible through active sync with the screen off and the battery charging (faster now that it isn't competing with the screen for power, except for the 2 minutes before it times out). If I want to use it I just click a button and the screen stays on till I leave it alone for 2 mins and it remains off. Get a call or a message and the screen goes on for 2 minutes and then off - Exact same behaviour on AC and USB - exactly the behaviour I wanted .
I pasted this in Google's official forum but no reply. Can anyone one here please reply to this?
******************************
Here it goes:
The phone is perfect. Works very well. With a small annoying issue.
Sometimes after calling some someone when I hang up and keep it aside, the screen times out (which is normal).
But later when i try to wake the phone by pressing power button it does not do anything. No matter which button i press the phone lies dead.
Take out the battery and the phone starts working great as if nothing happened.
I have experienced this issue atleast 5 times. I tried factory reset just to make sure any random application is not doing this. But, after couple of weeks the issue came again.
I am not sure if HTC is the only one that can help because I am basically scared that they might screw other areas of phone which are working just fine.
Can this be solved by Froyo? Should I wait for it come OTA?
Also, there can be an application which wakes up phone via trackball but would that help?if no button is responding.
Please help guys!!
Always include:
Carrier:Singtel
Country / Language:Singapore
OS / Browser / build number (if applicable):2.1-update 1 (Unrooted, waiting for Froyo OTA)
Try calling your phone from another line first. That would happen to me on my HD2 (a really awesome phone if it didn't suck ass so bad) and, sometimes calling it from another line would cause it to wake up.
OK
Will try to call from another phone once the issue re-occurs.
Should get Froyo by this week as per google so lets see if that can eliminate the issue.
Just now this issue reappeared. I tried calling my phone with other phone but it just kept ringing, no response on N1.
I tried connecting charger and usb but again phone lies dead.
Pull-push battery and now I am typing this message with same phone.
Still wating for froyo ota.
Guys, pls suggest if someone is facing same issue.
I know Leo Laporte had this problem with his N1. Because the power botton is used for unlocking the phone it is more prone to having issues. Everything on his phone was fine, then the power/wake button stopped working. He pulled the battery and could never get it to boot up again, since the power button didn't work. He called up HTC customer service and they sent him out a new phone minus the battery and back cover. That may be the easiest solution to your problem.
I had that problem at one point, although not so severely. Froyo put an end to it but I have a strong feeling the problem will return since I am starting to notice a ~1/2 second lag between pressing the button and the phone waking up.
I think the problem lies in the hardware/software interaction for the button. Can you try something:
-Plug in your phone to your computer
-Start logCat* on your computer
-Keep messing around with your phone while its still connected (logCat will keep scrolling by itself, displaying the system log - if it doesn't, scroll to the bottom of the log and it should begin auto-scroll)
-Wait for the problem to come back
-Press the power button ONCE and see if ANYTHING shows up in logCat that coincides with you pressing the button.
The reason I say this is that I tried this with my phone (i'm a dev so I had it plugged in at the time already) and when I clicked the power button, although the screen would not turn on, logCat would indicate that the Android system registered the click.
Post the results for everyone, if you would be so kind.
*logCat is part of Android-SDK and can be downloaded from the Android Developer's Resources.
it's most likely a hardware issue with the button itself. 3 weeks ago I had a very similar problem where the button was working 1 out maybe 5 times. I called up HTC and they sent me a new one (well technically they're refurbished but I honestly couldn't tell the difference). I was rooted and everything, but they still didn't charge me for it. New phone is still working just fine.
So give them a try.
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
MSigler said:
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
Click to expand...
Click to collapse
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
maniacx21 said:
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
Click to expand...
Click to collapse
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
musashiken said:
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
Click to expand...
Click to collapse
Ahh. I believe you misunderstand my intention;
The logcat output won't explicitly say that the sleep/wake button was pressed, rather you would see some indication of background [system] activities reacting to the press (you would see 'x many' log entries appear RIGHT when you clicked the power button). There would be no way to tell for sure if you see it after the fact. You would essentially be clicking the button with your finger while staring at the logcat output on your computer. You could not do that with alogcat (from the market) as the [device's] display would be off at the time.
*I bolded alogcat to differentiate it from logcat.
For those unfamiliar, the Android system (and activities spawned by applications) send 'messages' to a sub-system in the Android-OS called logcat. The logcat is used by developers to find out at what part of the program an error occurred while debugging as they can output detailed error logs to it from their app. Logcat also outputs things such as results from OTA checkins so Google can debug the OTA system to make sure it is pulling the correct download paths, ect. This was put in place by Google devs (and led to the public finding out the google server addresses of the Froyo 'test' builds).
On average, there are 2-3 logcat entries added per second when the device is being used, and about 0.1 logcat entries per second when the device is in standby mode. What we are looking for in this case is whether there is a sudden surge of entries when the button is pressed, indicating that SOME part of the Android system recognized the press. The entries wouldn't have anything to do with the button itself, but if the same [few] entries come up EVERY time you press the power button and nothing happens visually, you know something was triggered.
Logcat is a software that runs on your computer (what we want in this case) that lets you view log entries in real time. Alogcat on the other hand, is a software that RUNS ON YOUR PHONE that allows you view log entries in real time.
Let me know if you have any questions!
Do you use a taskiller? Ever since I got burned by a taskiller, I've been wary about them. Not wary enough to uninstall them though.
Not a fix:
But a workaround would be using Trackball Wake to circumvent having to use the power button to wake your device. Especially since you are not running on Froyo.
I am tired of sending my N1 back to HTC to have the power button repaired.
At the moment it's very hard to press so I am using custom apps to power off the phone with a widget (or long press on Search) and power on with the Vol Up key.
That works fine but means I can't have a PIN lock on the phone and means I can't connect to my work's Exchange server.
Is there a custom ROM out there or something that requires ROOT access to the phone that allows you to power on the phone with a different key but retain PIN number access? Somebody mentioned on another thread that this was no possible with a stock phone and it had to be rooted but I can't find an application that has this functionality.
Thanks
You are referring to waking up the phone correct? cause powering on is a totally different thing and I don't think you can power on with any other buttons if the phone is completely off.
If you can flash CM7, you can have trackball wake than unlock via pin code or pattern.
Sorry I meant waking the phone up not power it on which can't be done with software of course.
When I get my phone repaired I will look in CM7. I would prefer something else than the trackball to wake the phone since it's easily pressed. I do like vol up that one tool provides.
Yes, as baseballfanz mentioned, CyanogenMod has the ability to wake up the phone with the trackball (I also believe they recently added in the ability to wake it by the volume buttons). And it is built into the ROM, so there aren't any additional apps necessary for that.
They also include a notification widget to turn off the screen (it shows up in the notification drop down along with other buttons - similar to the power control widget). I also got an app called Lock Screen which allows me to place an icon in my main dock (or anywhere else for that matter).
EDIT: I just checked, and I do have the volume wake option on my phone. I am running nightly #151. I am pretty sure it is not in the stable 7.0.3, but it might've been put in before 7.1 RC1. If not, it will definitely be in RC2.
bassmadrigal said:
Yes, as baseballfanz mentioned, CyanogenMod has the ability to wake up the phone with the trackball (I also believe they recently added in the ability to wake it by the volume buttons). And it is built into the ROM, so there aren't any additional apps necessary for that.
They also include a notification widget to turn off the screen (it shows up in the notification drop down along with other buttons - similar to the power control widget). I also got an app called Lock Screen which allows me to place an icon in my main dock (or anywhere else for that matter).
EDIT: I just checked, and I do have the volume wake option on my phone. I am running nightly #151. I am pretty sure it is not in the stable 7.0.3, but it might've been put in before 7.1 RC1. If not, it will definitely be in RC2.
Click to expand...
Click to collapse
Sounds good. What I want is to be able to unlock the phone with the power button (I press the trackball too easily) and when that button is pressed, I am presented with the standard unlock screen with PIN number entry.
At the moment I have a free app from the market that unlocks the phone with Vol Up but then it's completely unlocked with no PIN entry. Putting in a PIN number disables the app.
Hopefully with CM7 I can have both going?
Yes, the volume wake is just that. It wakes up the phone, but doesn't unlock it. And I thought the same thing with it being too easy to turn on, but I've only ran into the issue a few times when it has turned on in my pocket, but the screen has a relatively short timeout before it turns off (I think it is 5 seconds), so it hasn't ever really been an issue.
But either way, it does have the volume wake (and not volume unlock).
If your phone's power button is in a 'pressed' state, like mine, (turns on automatically when battery is inserted), it is a hardware issue.
Here is a hassle free alternative to turn on the phone when it is in sleep mode, without relying on the power key!! Takes a minute or two only!!
1. Get 'Go launcher' from the app market (play)
2. Get 'Go Locker'
3. Now Enable Go Locker on your device. And you are done!!
When the screen goes black again, Just press the volume button, The screen wakes up!!
Using this method you don't lose the normal functionality of the volume rocker!!
I recalled that I used to have Go Locker on my phone, and that when I pressed the Volume key the screen turned on!!
At that time I found it a little annoying, But now it has turned out to be such a gift!!
* For this method to work, your phone has to be rooted.
The power button is not going to work until the hardware is repaired, I prefer to use this method, because it is a safe and quick method!!
Believe me I looked around the internet and this forum for a fix, The usual method: editing the system files on the phone, and after which the volume button cannot be used to control the volume.
For those looking for a quick fix, just follow my method!
Cheers!
There are also several roms out there that have the volume rocker wake built into the rom without making it completely useless for it intended purpose. As well as several that offer a go to sleep toggle in the notification window so you can lock your phone again.
so this is a hardware issue ? i had been using the go locker i been using but the power button is annoying cus it keep showing the power button options . and killing my battery.
only fix is samsung?
Pretty much every version of cm for cappy has volume rocker wake as an option, because of this common problem. I use app called turn off screen as well.
Natureboyhcg said:
so this is a hardware issue? only fix is samsung?
Click to expand...
Click to collapse
I had the exact same problem with my Epic Touch 4G. Thought it was the ROM, the overclock, etc. I flashed back to (almost) stock, went back to original clock speeds. I couldn't figure out what it the world was causing the issue, until it got worse. Then, I noticed that even brushing past the power button would wake the screen, and about 10 seconds later the phone would reboot.
Long story short, I bought a replacement power switch, soldered it in place, and have had zero problems since!
Several eBay sellers offer the proper replacement switch you'll need.
(They don't include the required skills to properly desolder/solder it, however. It's a tiny switch - about 4mm x 2mm x 1.5mm, and you'll need a good quality fine-tipped soldering iron.)
Factory Settings
Factory Settings
Accessed using code 126
Application
Hardware related settings (eg. canbus, dvd, tv)
Radio Band
Select radio band that works in your country
Car Logo
Change startup logo
Audio
Set default audio levels
Other
RDS: Display Radio Data System info for radio stations that support it
Front camera: Activate front camera (usb for inbuilt recording)
Wheel3: (possibly a poor transcription of freewheel) Affects the operation of the volume knob. If this is incorrectly set, the volume control will not work properly. Likely related to the type of rotary optical encoder used.
RGB LED: Button lights
Rudder: Lets HU know if car is left or right hand drive (eg. for displaying which car door is open)
Disable app install: Don't allow apps to be installed
Key light: Keys lit always or with illumination wire.
No wheelstudy:
Keymap option:
Touchmap options:
Reversing brightness: Change in screen brightness when reverse camera is activated
Why is this here? It's already in the Wiki.
mike.s said:
Why is this here? It's already in the Wiki.
Click to expand...
Click to collapse
Both this and mcu codes are in the wiki, this is just for others to comment on (more info/discussion) and also so it will appear in search
All of the MCU codes were not in the Wiki (they are now, because I added them).
What's there to discuss? If people want to add more detail to the Wiki, they can. For discussion of individual settings, a thread started with a copy/paste from the Wiki isn't a good beginning, and certainly doesn't add any new information. Adding yet another location to find the same information hurts, not helps, search.
Finally, the Wiki can be updated by anyone and doesn't require any individual to update their post as more info/knowledge is gained, and provides a single location users can refer to for common knowledge.
Can someone please explain what the Keymap option and Touchmap option actually do? Is this keyboard layouts etc? I've changed the options (only had unit 1 week so limited about of trying) but it didn't seem to do much?
Mr Bigglesworth said:
Can someone please explain what the Keymap option and Touchmap option actually do? Is this keyboard layouts etc? I've changed the options (only had unit 1 week so limited about of trying) but it didn't seem to do much?
Click to expand...
Click to collapse
I don't think anyone knows. Nothing seems to change haha
Would assume it changes the layout of hardware keys (button or touch)
Brendo said:
I don't think anyone knows. Nothing seems to change haha
Would assume it changes the layout of hardware keys (button or touch)
Click to expand...
Click to collapse
Glad it wasn't just me!
Mr Bigglesworth said:
Can someone please explain what the Keymap option and Touchmap option actually do? Is this keyboard layouts etc? I've changed the options (only had unit 1 week so limited about of trying) but it didn't seem to do much?
Click to expand...
Click to collapse
I know what keymap function does.
Option 1: If you open an app like radio and press home button it will close the app.
option 2: When you press the home button, it does not close the app anymore.
The rest of options I haven't tried!
Touchmap function .. I don't find any diferences beetwen the options. Maybe it's for units who don't have buttons?
Any update on exploring the keymap options? I'm not convinced that the above description is universal, as when I have option 1 set and press the home button it does not close the app.
I've been trying different options (1 - 10) however don't have any really good information, except to comment that it's impossible to turn on Wi-Fi when set to option 3.
Option 2 seems to really slow down performance of the machine.
I've really only had a chance to explore 1 - 3 but will continue through all 10. Please post if you have any particular experiences with various options.
In my unit in the button keymap you can set different functions to a hardware button, by pressing the required button twice.
i.e.
The SCR button opens av player by default.
I don't use it and want to start the music app.
So press SCR button twice and in that menu you can choose the Music icon.
Then it will start the music app with the SCR button.
Now you have to be really careful NOT to use the touch button option!!!!
This recallibrates the touch screen, and if you touch the screen then..... it totally screws up everything...
Only solution then is a reset and you can start all over again.
---------- Post added at 11:33 AM ---------- Previous post was at 11:19 AM ----------
Next thing NOT to do is in "others" tab.
There was some "power" option which default i think was "on".
Options there are "on" "of" and "remember last status" .
In my opinion the radio turned off to quickly, even when power down was set on 5 minutes (in android settings).
So i first saved this "power" thing in factory settings to "on".
Off course the radio stayed On after turning off ignition.
So i waited 5 -10 minutes, but it stayed on.
Then i made the biggest and most stupid mistake in my life and tried "off", and guess what.
It does not turn on anymore.... ****** (I should have guessed that).
According to the helpdesk, the radio should start in recovery when holding reset for 3-5 seconds.
But the button backlight (red colour) only blinks once when you release reset, and that is it.
Holding the power button for 10 seconds turns on button backlight as long as you hold the button.
I did receive their latest firmware so i could flash it in recovery, but then it has to boot first...
Now i am waiting for the next answer from the helpdesk, but for now my unit is dead.
I hope this message helps others to prevent making the same mistake.
oh thanks i was wondering how to access that !
Hi, can you fix the problem?
lottumeb said:
In my unit in the button keymap you can set different functions to a hardware button, by pressing the required button twice.
i.e.
The SCR button opens av player by default.
I don't use it and want to start the music app.
So press SCR button twice and in that menu you can choose the Music icon.
Then it will start the music app with the SCR button.
Now you have to be really careful NOT to use the touch button option!!!!
This recallibrates the touch screen, and if you touch the screen then..... it totally screws up everything...
Only solution then is a reset and you can start all over again.
---------- Post added at 11:33 AM ---------- Previous post was at 11:19 AM ----------
Next thing NOT to do is in "others" tab.
There was some "power" option which default i think was "on".
Options there are "on" "of" and "remember last status" .
In my opinion the radio turned off to quickly, even when power down was set on 5 minutes (in android settings).
So i first saved this "power" thing in factory settings to "on".
Off course the radio stayed On after turning off ignition.
So i waited 5 -10 minutes, but it stayed on.
Then i made the biggest and most stupid mistake in my life and tried "off", and guess what.
It does not turn on anymore.... ****** (I should have guessed that).
According to the helpdesk, the radio should start in recovery when holding reset for 3-5 seconds.
But the button backlight (red colour) only blinks once when you release reset, and that is it.
Holding the power button for 10 seconds turns on button backlight as long as you hold the button.
I did receive their latest firmware so i could flash it in recovery, but then it has to boot first...
Now i am waiting for the next answer from the helpdesk, but for now my unit is dead.
I hope this message helps others to prevent making the same mistake.
Click to expand...
Click to collapse
Hi, can you fix the problem?
I think the same thing happened to me, I tried to restart in all the ways and I do not get anything, always the black screen.
If you managed to fix it, could you tell me how you did it?
Thank you and receive a warm greeting.
AbelEvelio said:
Hi, can you fix the problem?
I think the same thing happened to me, I tried to restart in all the ways and I do not get anything, always the black screen.
If you managed to fix it, could you tell me how you did it?
Thank you and receive a warm greeting.
Click to expand...
Click to collapse
oh, I do same stupid thing, have any solution?
thank for advance help....
jonesweng said:
oh, I do same stupid thing, have any solution?
thank for advance help....
Click to expand...
Click to collapse
I did the same. However, I inserted a pin into the reset (RST) hole of my unit and it came back up fortuntately....
Anyone knows how to change the led color buttons?
jonesweng said:
oh, I do same stupid thing, have any solution?
thank for advance help....
Click to expand...
Click to collapse
i'm too, any solution ?
can anybody help to fix the problem ?
lottumeb said:
In my unit in the button keymap you can set different functions to a hardware button, by pressing the required button twice.
i.e.
The SCR button opens av player by default.
I don't use it and want to start the music app.
So press SCR button twice and in that menu you can choose the Music icon.
Then it will start the music app with the SCR button.
Now you have to be really careful NOT to use the touch button option!!!!
This recallibrates the touch screen, and if you touch the screen then..... it totally screws up everything...
Only solution then is a reset and you can start all over again.
---------- Post added at 11:33 AM ---------- Previous post was at 11:19 AM ----------
Next thing NOT to do is in "others" tab.
There was some "power" option which default i think was "on".
Options there are "on" "of" and "remember last status" .
In my opinion the radio turned off to quickly, even when power down was set on 5 minutes (in android settings).
So i first saved this "power" thing in factory settings to "on".
Off course the radio stayed On after turning off ignition.
So i waited 5 -10 minutes, but it stayed on.
Then i made the biggest and most stupid mistake in my life and tried "off", and guess what.
It does not turn on anymore.... ****** (I should have guessed that).
According to the helpdesk, the radio should start in recovery when holding reset for 3-5 seconds.
But the button backlight (red colour) only blinks once when you release reset, and that is it.
Holding the power button for 10 seconds turns on button backlight as long as you hold the button.
I did receive their latest firmware so i could flash it in recovery, but then it has to boot first...
Now i am waiting for the next answer from the helpdesk, but for now my unit is dead.
I hope this message helps others to prevent making the same mistake.
Click to expand...
Click to collapse
I was find a solution:
HU can't start, because in the config file there is mistaken option with power service turned off.
You need to find a MCU file (DMCU.IMG) and MCU CONFIG (DMCU.CFG) file and make an HU update in the recovery. mode.
Put these files on the SD card and flash MCU.
Link to the MCU CONFIG file:
https://forum.xda-developers.com/and...-mcus-t3624724
Link do the MCU file:
https://forum.xda-developers.com/and...essor-t3834657
REMEMBER - YOU MUST GET FILES TO YOUR HEAD UNIT - but you can try different, your HU is dead now anyway...
Oh Crap
--------------------------Then i made the biggest and most stupid mistake in my life and tried "off", and guess what.
It does not turn on anymore.... ****** (I should have guessed that).-------------------
Did you ever get it working again? Unfortunately i just made the same mistake and really hoping its not a paper weight :crying:
Updated my MCU KLD v3.01 on my PX5 and there is now an option for a carplay dongle. I have one so I checked the box. Have no idea what is changed because everything was already working but I am hoping someone smarter then me will tell me.
KAOS313 said:
Updated my MCU KLD v3.01 on my PX5 and there is now an option for a carplay dongle. I have one so I checked the box. Have no idea what is changed because everything was already working but I am hoping someone smarter then me will tell me.
Click to expand...
Click to collapse
Awesomes, but just wondering what this has to do with MTCB units?