I hope that this helps some of you, and as I have yet to see this posted on any other Epix forum, I am almost certain I am the first to figure this password out. So, here it is:
(1) Open the Admin.exe program, either with a file explorer similar to Total Commander or Resco (file path is \Windows\Admin.exe), or by pressing the green phone button to access the phone program then dialing *#1546792*#
(2) Once the program is open, select option [3] Internal
(3) You will be prompted for a password, it is: *#0807#
Are any of the options in this menu useful for the average joe?
Im running SPB Mobile Shell 3.0 on my Epix and love it. It works great. The only downside was that some screen still were not "finger friendly," like SMS screens. I solved this by downloading ftouchsl.
This solved the problem, but made all SPB Shell screens non-finger friendly. They locked up and scrolling isn't possible.
If these two programs could co-exist, we could have an amazing phone. Is there a fix for this?
If some one call to me, one ring (in my epix) and end call. My Epix will show missed call, but can't show telephone number or name. Only show in missed list: Unknown
Im running SPB Mobile Shell 3.0 on my Epix and love it. It works great. The only downside was that some screen still were not "finger friendly," like SMS screens. I solved this by downloading ftouchsl.
This solved the problem, but made all SPB Shell screens non-finger friendly. They locked up and scrolling isn't possible.
If these two programs could co-exist, we could have an amazing phone. Is there a fix for this?
Add SPB Mobile to FTouchSL's exception list and that should fix the problem.
Im running SPB Mobile Shell 3.0 on my Epix and love it. It works great. The only downside was that some screen still were not "finger friendly," like SMS screens. I solved this by downloading ftouchsl.
This solved the problem, but made all SPB Shell screens non-finger friendly. They locked up and scrolling isn't possible.
If these two programs could co-exist, we could have an amazing phone. Is there a fix for this?
I am using both and I do not have that problem. Try re-installing them, that may help.
Which version of IGO8 you have tested ?
I've tried Ig0 8.0.0.88902 with no success. Failed on 160_160 resolution screen and Epix is 320_320 one.
Thanks
Michael
Which version of IGO8 you have tested ?
I've tried Ig0 8.0.0.88902 with no success. Failed on 160_160 resolution screen and Epix is 320_320 one.
Thanks
Michael
8.3.2.XXXXX, I've used several builds in this series. If you don't have the right resolutions you need a different data.zip and branding.zip probably, they contain the folders with the images for each resolution. I think I posted a sys.txt somewhere in this thread with my settings which might help.
make a file named mouse.mscr or whatever you want .mscr with the following text in it (or just download the attached .zip file):
Code:
sleep 12000
run \windows\mouseonoff.exe
sleep 100
run \windows\mouseonoff.exe
Then make a shortcut to the .mscr file in your windows/startup/ folder via total commander or what have you.
For some reason if you run mouseonoff.exe immediately the D-pad fails to work, 12000 ms (12 seconds) seems to be a good number to prevent that, if you have a problem with the d pad not working you can increase that number to say 15000. For the first 5-10 seconds you'll have the stupid mouse cursor box thing, then it disappears when it switches to mouse and back to dpad using the script. If I can find a program to kill the phone radio I'm going to experiment with fixing the device.exe problem. I think it's got something to do with the aGPS hanging, because device.exe goes back down to normal if you turn the phone off and on, I just need to find a command line program that can toggle the phone radio.
Last edited by big wheezy; 08-23-2009 at 04:41 AM.
FWIW, you may need to change the delay with certain versions of WM6.5, I was using trashcan's early build when I did the mouse fix, I had to change it up to 15000 ms when I switched to the 23028 build.
I am using the build and it works great. He had to post a new link because the old one got deleted. Just go to the last post. Here is a link to make it easier: http://forum.xda-developers.com/show...544101&page=31
Being a "newbie", does anyone know the different between the Epix 6.5.23037 10mb Page Pool file and the Epix 6.5.23037 15mb Page Pool file on the Win6.5 download page above? Do I use them both? Or just one of them?
Being a "newbie", does anyone know the different between the Epix 6.5.23037 10mb Page Pool file and the Epix 6.5.23037 15mb Page Pool file on the Win6.5 download page above? Do I use them both? Or just one of them?
Hey - you just use one. Each BIN file flashes your Epix's ROM, so you can only ever have one on your phone at a time.
I'd go with the 15MB since it allocates more memory for paging, which should make your Epix more responsive.
So I've been thinking if anyone still has their epix in the Rev. 0.3 version and be able to dump that. I am no phone programming expert, but I'm asking this is because that might provide some of us the possibility to somehow grab the files necessary to fix the device.exe for all the people who have upgraded to the Samsung ID1 "patch" . We all know that with that update, the gps is totally rendered useless due to spikes in the device.exe of upwards 60%, easily draining the juice of our large battery. I don't know if taking the device.exe files from the Rev 0.3 version of the phone will help fix the post ID1 gps issue, but I sure hope someone could think of doing that. Maybe put it as a .cab file? I don't know, but I'd love some experts giving me some opinion about it. To me, WinMo 6.5 roms are great and all, but I'm sure the gps issue will still be lurking around. Plus SPB mobile 3 on winmo 6.1 is great for my usages atm. *i've read through maybe 40 pages? starting from around May 2009 to present and we're still struggling w/Samsung's pathetic urgent update. Slog dumps would've been better*
Originally Posted by RichhEd
Reply With Quote
. We all know that with that update, the gps is totally rendered useless due to spikes in the device.exe of upwards 60%, easily draining the juice of our large battery. I don't know if taking the device.exe files from the Rev 0.3 version of the phone will help fix the post ID1 gps issue, but I sure hope someone could think of doing that. Maybe put it as a .cab file? I don't know, but I'd love some experts giving me some opinion about it. To me, WinMo 6.5 roms are great and all, but I'm sure the gps issue will still be lurking around. Plus SPB mobile 3 on winmo 6.1 is great for my usages atm. *i've read through maybe 40 pages? starting from around May 2009 to present and we're still struggling w/Samsung's pathetic urgent update. Slog dumps would've been better*
Bookmarks