Related
==========================================================
News and updates in post #2.
==========================================================
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only! Any of the posters of software, or links to software on this thread take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
==========================================================
WIKI PAGE ABOUT DRIVER DEVELOPMENT FOR MSM720X DEVICES
==========================================================
image courtesy of tsalta. Thanks mate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, try GFXboost. It's cool to see the device CAN go beyond the normal speeds.
Installation: Disable Manila or Titanium before installing the cabfile. It's to make sure there are no files in use when copying the files. If you have an older version of the driverpack installed, best thing to do is a hard-reset. I know, it sucks. But believe me, it's best for your device.
MOD EDIT - Added NeoS, Magnif, Chainfire & topaz driver cabs
Updates and FAQ
Updates:
======================================
22-06-10: Benchmark added by tusuka: http://forum.xda-developers.com/attachment.php?attachmentid=347300&d=1277159324
18-04-10: The MSM chipset needs YOU! Please look at this post if you're interested in continuing driver development!
10-03-10: I retire from driver development for two reasons. 1.) http://forum.xda-developers.com/showpost.php?p=5842057&postcount=1861. and 2.) I've moved on to A Nexus One. Awesome device, twice as good as the Blackstone could ever be. (and not as retardedly big as the HD2 )
11-02-10: Added a signed driverpack to the first post. Hope it'll give improvement on Manila 2.5 roms and no lock-ups... I know my device runs perfectly fine and smooth(er) with the driver.
18-01-10: Benchmark of 4 driverpacks on a stock 6.1 rom. -Thanks FileFixer!
30-11-09: It's done. I officially stop doing anything driver related, until i get more time. I simply lack the time, knowledge and support to keep going on. If you feel like helping out coördinating, send me a pm.
24-09-09: Driverpack 3 released. Please report any bugs on the thread. Here's a benchmark:
21-09-09: GLbenchmark comparison with Driverpack 3 (in development)
16-09-09: Testing new driverpack on Touch HD. Shows improvement in Manila 2.5. Needs to be tweaked further.
26-07-09: New files seem to have shed a whole different light on our current drivers; we need to fully investigate what they do and how to get them working. Updates will be made once we have more info on this subject. Please, have patience!
30-06-09: DriverPack Beta 2 released. Bugfixes done. See here
23-06-09: Updated the F.A.Q. and bugfixing the current BETA pack.
19-06-09: Driver pack BETA released. Find it HERE.
14-06-09: Laurentius26 cooked our drivers in his latest rom and got amazing results: http://forum.xda-developers.com/showpost.php?p=3304864&postcount=4
01-06-09: Created a quick-to-install full cab package for the OpenGL & OpenVG driver combined. Currently being tested by the team.
06-05-09: Set up a Dev & Test team, inviting users with dev skills or something similar.
24-04-09: Finally fruits of labour; the new openVG driver gives improvement combined with a new Libgles_cm.dll.
See: http://forum.xda-developers.com/showpost.php?p=3685655&postcount=793
09-04-09: Testing with the OpenVG driver provided by Fards and itje
05-02-09: User Laurentius26 provided us with a zip containing display driver files from an LG Incite.
28-01-09: Thanks to user Chainfire the list of files on the wiki page is updated. Check it out for more info.
27-01-09: Wiki page started about driver development
13-01-09: User fards uploaded a signed HTCapi.dll for use with the driver, found here: http://forum.xda-developers.com/showpost.php?p=3159939&postcount=196
23-12-08: added minor explanation on what the 3D driver is and does, and how to see performance improvements:
http://forum.xda-developers.com/showpost.php?p=3076202&postcount=153
22-12-08: Added 3D driver link in 1st post.
17-12-08: User iRiKi tested the Libgles_cl wrapper (made by NuShrike, thx mate!) and confirmed it working. He also was so kind to post a video of Heretic_GLES now running on his Diamond.
http://www.youtube.com/watch?v=5t-JX2TSkJI And Cube too! http://www.youtube.com/watch?v=Sc3b9_CT2bw
16-12-08: We're currently looking into the possibility of making a libgles_cl.dll wrapper to support more programs and 3D applications, as well as making more tests work in GLbenchmark. Also, we've come to know that The Android porting team seems to have some fully working ports which might have some answers towards our graphics questions. (so if you're an Android devver, please join the conversation )
11-12-08: User Draxredd pointed out that the hotfix by HTC seems to update ddi.dll, disptools.dll, gxdma.dll and htcmdp.dll. 3 of those files are sure to be used for graphics. Glbenchmark results don't show much performance increase, but it does however fix the slowdowns the HD had.
11-12-08: user lukexda mentioned that the iPhone in this particular case only has a resolution of 480x320 and therefor is faster. Draxredd suggested we use WVGA fix (http://forum.xda-developers.com/showthread.php?t=455974) to correct screen resolution to VGA or lower to see if that makes any difference. An does it! The speed of some tests give a whopping DOUBLE SCORE! Now we know what makes our device sluggish. HTC gave us a device with a great looking screen at the cost of great performance.
However, we're not done in our quest to better the device's graphic performance. So please, keep contributing!
F.A.Q:
I've seen a few questions about this driver that come back each and everytime. So here's a small FAQ for you to read:
Q: What do these drivers do?
A: The original ATI drivers enable you to display 3D graphics on your MSM720X device. The OpenVG driver enables 2D Hardware acceleration on the OpenVG platform. That doesn't mean Windows Mobile's 2D interface will be hardware accelerated! HTC's TouchFlo3D heavily depends on this driver, and every update we bring will be aimed at performance.
Q: Are these solely for MSM720X devices?
A: Yes, since the files used only work with the MSM720X chipset. And not even ALL MSM720X chipsets.
Q: So, which devices are supported?
A: Currently only newer devices: the Kaiser, Polaris, Nike, won't work. This driver is only for Diamond and up. There MAY be more in the future though.
Q: How does one install this driverpack?
A: It's as simple as installing any other app or game, with one exception: You need to disable Touchflo3D/Sense or Titanium before running the installation.
Q: Why?
A: Just to make sure no files are in use when they're overwritten by the driverpack.
Q: Wait, you're overwriting files? How can this be uninstalled then?
A: Technically, it can't, unless you hard-reset or flash another ROM.
Q: Ok, but HOW do I disable and re-enable? TF3D/Sense/Titanium?
A: That's easy. Go to Start>Settings>Today. Then select the Items Tab. Deselect TF3D/Sense/Titanium and press OK. Use the same procedure to re-enable it.
Q: Does this driver improve performance in TomTom, IGO, Video's, Camera, etc?
A: Currently, all this driver does is 3D. TomTom, IGO, videos and such don't use the 3D engine. Most applications on your device are 2D currently, otherwise it wouldn't have worked before. But with the new OpenVG driver it could be possible to get 2D hardware rendering, if the app or game is written using OpenVG code.
Q: I've installed the drivers on my <insert device here>, but TF3D won't run anymore / Opera crashes the device after crashing.
A: This is a known issue with the driver. We're currently investigating on which files cause the issues and try to replace them. Somehow the driverpack doesn't work the same on different devices using the same MSM7201A chipset... <solved in Driverpack 3>
Please don't let me go crazy with that results...So do you mean it's poor in graphic performance???
It's... Average at best. Same as the Diamond and Pro. For now. I'm gonna try and see what i can do to improve it. And i hope some others will aid me in that.
I already got the lights working with Hardware rendering now, but that's too easy. Gonna do some SPB benches...
NeoS2007 said:
It's... Average at best. Same as the Diamond and Pro. For now. I'm gonna try and see what i can do to improve it. And i hope some others will aid me in that.
I already got the lights working with Hardware rendering now, but that's too easy. Gonna do some SPB benches...
Click to expand...
Click to collapse
is it a huge different talking about the screen?? I mean, watching a movie or something is totally different or it's kinda the same?
What about trying VSBenchmark ( Link to vsBenchmark )
danny_and_2 said:
What about trying VSBenchmark ( Link to vsBenchmark )
Click to expand...
Click to collapse
hmm. VSbenchmark won't run. No errors, but it just hangs.
Found an interesting registry setting:
HKLM\software\HTC\VelocityEngine\3D\Enable=0
I set it to 1. I don't see any big improvements or whatever. yet...
From what I've been reading HTC shipped the HD with the MS reference driver for the graphics.
Once the rom cookers get cracking I'm sure the driver update will be part of that.
With the Touch Cruise/Polaris, this made a gigantic difference in graphics performance and smoothnes of the interface.
I don't really get why the heck HTC won't install up to date and up to snuff drivers in new devices. It bites.
With a big screen like the HD, you need good graphics drivers.
I do have to say though that the performance of the HD is rather good compared to other HTC devices in the office. Especially for first release level firmwares
Well, I received my HD and display didn't impress me that much! Brightness is not impressive, Diamond and iPhone are better, colors and text seems to be faded. The white has a warm colour temperature...
Any one had the same impressions?
yes i wish there would be a way to increase brightness!!
It won't be easy to patch this driver for the HD. The Polaris and Kaiser driver were rev. 1 drivers. The Diamond and up are rev. 2. This means LOTS of low level coding and WAY more time consuming.
And the Polaris and Kaiser drivers themselves are still under development, so don't expect anything from the people who work on those drivers. (as far as i know, i'm the only one who got myself an HD)
The driver seems to work pretty similar to the Polaris (my old device) and as I said earler, i got Lights.exe to work on hardware rendering. But that's pretty much it. No improvements on speed or anything. I will however see how far i can push this myself.
...no! it looked to me gorgeous. what's your problem?
pzucchel said:
...no! it looked to me gorgeous. what's your problem?
Click to expand...
Click to collapse
If you refer to display...not so gorgeous...I remember the X7500 one more brightness than HD one.
asci said:
If you refer to display...not so gorgeous...I remember the X7500 one more brightness than HD one.
Click to expand...
Click to collapse
have you tried to manually set brightness ? it seem the lightsensor is'nt so efficent ...
Ciao Stesa...
Yes, I did, is the very first thing I do when I unbox all of them...At least from X7500
About the light sensor, it seems to work differently from the Diamond one, but I found it more reactive and the changes according to the ambient brightness value are more evident.
Thought I'd post this as a comparison with the SE X1
This was my glbench from this afternoon, it seems a bit worse than the HD, I'm not certain what's going on but from teh lights parallel down it starts to struggle in comparison.
GLBenchmark Pro Result Details
3D Rendering Quality: Bilinear Filter : 96% (Success)
3D Rendering Quality: Perspective Correction : 100% (Success)
3D Rendering Quality: Sub Pixel Precision : 95% (Success)
3D Rendering Quality: Trilinear Filter : 89% (Fail)
3D Rendering Quality: Z-buffer Precision : 99.1% (Success)
CPU Performance: Float : 781
CPU Performance: Integer : 8173
Fill Rate: Multi-Textured, 2x2 : 15206 kTexels/s
Fill Rate: Multi-textured, 4x2 : 17203 kTexels/s
Fill Rate: Single-textured, 4x1 : 20122 kTexels/s
GLBenchmark HD ES 1.0 : 542 Frames
GLBenchmark HD ES 1.1 : Failed / Not supported
GLBenchmark Pro ES 1.0 : 84 Frames
GLBenchmark Pro ES 1.1 : Failed / Not supported
Lights: Ambient x 1 : 113397 Triangles/s
Lights: Omni x 1 : 53123 Triangles/s
Lights: Parallel x 1 : 118505 Triangles/s
Lights: Parallel x 2 : 287069 Triangles/s
Lights: Parallel x 4 : 282983 Triangles/s
Lights: Parallel x 8 : 287069 Triangles/s
Lights: Spot x 1 : 50058 Triangles/s
Swapbuffer speed : 280
Texture Filter: LINEAR : 282983 Triangles/s
Texture Filter: LINEAR_MIPMAP_LINEAR : 285026 Triangles/s
Texture Filter: LINEAR_MIPMAP_NEAREST : 287069 Triangles/s
Texture Filter: NEAREST : 287069 Triangles/s
Texture Filter: NEAREST_MIPMAP_LINEAR : 287069 Triangles/s
Texture Filter: NEAREST_MIPMAP_NEAREST : 287069 Triangles/s
Texture Size: 1024x1024 : 287069 Triangles/s
Texture Size: 128x128 : 287069 Triangles/s
Texture Size: 256x256 : 280940 Triangles/s
Texture Size: 512x512 : 285026 Triangles/s
Texture Size: 64x64 : 287069 Triangles/s
Triangles: Flat Shaded + Color : 282983 Triangles/s
Triangles: Smooth Shaded + Color : 288091 Triangles/s
Triangles: Textured : 289112 Triangles/s
Triangles: Textured + Color : 289112 Triangles/s
OpenGL ES Environment Variables
GL_VENDOR QUALCOMM, Inc.
GL_VERSION OpenGL ES-CM 1.0
GL_RENDERER Q3Dimension MSM7500W 01.02.03 0 5.1.2
GL_EXTENSIONS GL_OES_byte_coordinates GL_OES_read_format GL_OES_fixed_point GL_OES_single_precision_commands GL_OES_compressed_paletted_texture GL_OES_matrix_palette GL_OES_point_sprite GL_OES_point_size_array GL_ARB_vertex_buffer_object GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 GL_ARB_texture_env_crossbar GL_ARB_texture_mirrored_repeat GL_EXT_stencil_wrap GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_blend_func_separate GL_EXT_blend_equation_separate GL_ATI_texture_compression_atitc GL_ATI_extended_texture_coordinate_data_formats GL_OES_draw_texture
GL_RED_BITS 5
GL_GREEN_BITS 6
GL_BLUE_BITS 5
GL_ALPHA_BITS 0
GL_DEPTH_BITS 16
GL_STENCIL_BITS 0
GL_SUBPIXEL_BITS 2
GL_MAX_LIGHTS 8
GL_IMPLEMENTATION_COLOR_READ_FORMAT_OES 6407
GL_IMPLEMENTATION_COLOR_READ_TYPE_OES 33635
GL_MAX_MODELVIEW_STACK_DEPTH 16
GL_MAX_TEXTURE_STACK_DEPTH 2
GL_MAX_PROJECTION_STACK_DEPTH 2
GL_MAX_TEXTURE_SIZE 1024
GL_MAX_TEXTURE_UNITS 2
GL_MAX_PALETTE_MATRICES_OES 48
GL_MAX_VERTEX_UNITS_OES 4
GL_MAX_VIEWPORT_WIDTH 640
GL_MAX_VIEWPORT_HEIGHT 480
GL_NUM_COMPRESSED_TEXTURE_FORMATS 10
GL_ALIASED_LINE_WIDTH_MIN 1
GL_ALIASED_LINE_WIDTH_MAX 1
GL_ALIASED_POINT_SIZE_MIN 1
GL_ALIASED_POINT_SIZE_MAX 32
GL_SMOOTH_LINE_WIDTH_MIN 1
GL_SMOOTH_LINE_WIDTH_MAX 1
GL_SMOOTH_POINT_SIZE_MIN 1
GL_SMOOTH_POINT_SIZE_MAX 32
EGL Native Platform Graphics Interface
EGL Vendor ATI Technologies, Inc.
EGL Version __EGLI__VERSION_MAJOR.__EGLI__VERSION_MINOR 2.07.050110.34681
EGL Extensions EGL_QUALCOMM_COLOR_BUFFER
EGL Selected Configuration
EGL_CONFIG_ID: 3
EGL_BUFFER_SIZE: 16
EGL_ALPHA_SIZE: 0
EGL_BLUE_SIZE: 5
EGL_GREEN_SIZE: 6
EGL_RED_SIZE: 5
EGL_DEPTH_SIZE: 16
EGL_STENCIL_SIZE: 0
EGL_CONFIG_CAVEAT: 12344
EGL_LEVEL: 0
EGL_MAX_PBUFFER_HEIGHT: 0
EGL_MAX_PBUFFER_PIXELS: 0
EGL_MAX_PBUFFER_WIDTH: 0
EGL_NATIVE_RENDERABLE: 0
EGL_NATIVE_VISUAL_ID: 0
EGL_NATIVE_VISUAL_TYPE: 12344
EGL_SAMPLES: 0
EGL_SAMPLE_BUFFERS: 0
EGL_SURFACE_TYPE: 5
EGL_TRANSPARENT_TYPE: 12344
EGL_TRANSPARENT_BLUE_VALUE: 0
EGL_TRANSPARENT_GREEN_VALUE: 0
EGL_TRANSPARENT_RED_VALUE: 0
Device Information
Device Name X1i
Device ID xxxxxxxxxxxxxxxxxx
Platform Name PocketPC
Platform ID 3
OS Windows Mobile
OS Build 19608
OS Version Major 5
OS Version Minor 2
CPU Vendor QUALCOMM
CPU Name
CPU Core MSM7200A-528MHz
CPU Instruction Set 0
CPU Type 2577
Reported CPU Architecture 5
Number of CPUs 1
Total Memory 210214912
Memory Page Size 4096
Screen size 480 x 800
System Color Bits 16
System Colors 65536
Nice! I see the performance of the X1 almost matches the HD. This could mean that a possible video driver could ALSO work on the Xperia.
I'm currently trying to see if the P3D driver can be of some use for the HD. I think it can, but it needs major alterations.
asci said:
Well, I received my HD and display didn't impress me that much! Brightness is not impressive, Diamond and iPhone are better, colors and text seems to be faded. The white has a warm colour temperature...
Any one had the same impressions?
Click to expand...
Click to collapse
No Sunny day today in Greece brightness just fine. maybe uncheck the autobrightnes??? a bit slow some times.
(sorry for my bad english)
I've doing some tests with the HTC-CA-Kaiser driver on the Blackstone.
I'am using the D3DM_ati.dll from this package. Lights.exe, D3DMdemo.exe and Triangle.exe running excellent.
Lights.exe tells me:
Hardware Rasterization: True
Hardware T&L: true
Triangles about 250-270 frames/sec.
Then i tested the Diamond Hologram. To make it running i've copy the HTCAPI.DLL into \WINDOWS\ folder.
It runs excellent!
TFLO3d also runs absolutly perfect!
But GLbenchmark won't run, even with original driver and the Omnia driver.
The first test ist running but the others not.
@NeoS2007
How have you managed to start glbenchmark?
i found these codes on the net and thought they were for my captivate. some work and some do not (on my captivate.) what kind of list is this?
ALL SAMSUNG UNLOCK CODE....
---------------------------
*2767*688# = Unlocking Code
*#8999*8378# = All in one Code
*#4777*8665# = GPSR Tool
*#8999*523# = LCD Brightness
*#8999*3825523# = External Display
*#8999*377# = Errors
#*5737425# = JAVA Something{I choose 2 and it chrashed}][/b]
*#2255# = Call List
#*536961# = Java Status Code
#*536962# = Java Status Code
#*536963# = Java Status Code
#*53696# = Java Status Code
#*1200# = AFC DAC Val
#*1300# = IMEI
#*1400# = IMSI
#*2562# = ??? White for 15 secs than restarts.
#*2565# = ChAeck Blocking
#*3353# = Check Code
#*3837# = ??? White for 15 secs than restarts.
#*3849# = ??? White for 15 secs than restarts.
#*3851# = ??? White for 15 secs than restarts.
#*3876# = ??? White for 15 secs than restarts.
#*7222# = Operation Typ (Class C GSM)
#*7224# = I Got !! ERROR !!
#*7252# = Oparation Typ (Class B GPRS)
#*7271# = Multi Slot (Class 1 GPRS)
#*7274# = Multi Slot (Class 4 GPRS)
#*7276# = Dunno
#*7337# = EEPROM Reset (Unlock and Resets Wap Settings)
#*2787# = CRTP ON/OFF
#*3737# = L1 Dbg data
#*5133# = L1 Dbg data
#*7288# = GPRS Attached
#*7287# = GPRS Detached
#*7666# = SrCell Data
#*7693# = Sleep Act/DeAct (Enable or Disable the Black screen after doing nothing for a while)
#*7284# = Class : B,C or GPRS
#*2256# = Calibration Info
#*2286# = Battery Data
#*2527# = GPRS Switching (set to: class 4, class 8, class 9 or class 10)
#*2679# = Copycat feature (Activate or Deactivate)
#*3940# = External loop test 9600 bps
#*4263# = Handsfree mode (Activate or Deactivate)
#*4700# = Half Rate (Activate or Deactivate)
#*7352# = BVMC Reg value
#*8462# = Sleeptime
#*2558# = Time ON
#*3370# = EFR (Activate or Deactivate)
#*3941# = External looptest 115200 bps
#*5176# = L1 Sleep
#*7462# = SIM phase
#*7983# = Voltage/Frequenci (Activate or Deactivate)
#*7986# = Voltage (Activate or Deactivate)
#*8466# = Old time
#*2255# = Call ???
#*5187# = L1C2G trace (Activate or Deactivate)
#*5376# = ??? White for 15 secs than restarts.
#*6837# = Official Software Version
#*7524# = KCGPRS
#*7562# = LOCI GPRS
#*7638# = RLC allways open ended TBF (Activate or Deactivate)
#*7632# = Sleep mode Debug
#*7673# = Sleep mode RESET
#*2337# = Permanent Registration Beep
#*2474# = ???
#*2834# = Audio Path
#*3270# = DCS support (Activate or Deactivate)
#*3282# = Data (Activate or Deactivate)
#*3476# = EGSM (Activate or Deactivate)
#*3676# = Flash volume formated
#*4760# = GSM (Activate or Deactivate)
#*4864# = Dunno doesn't work on newer versions
#*5171# = L1P1
#*5172# = L1P2
#*5173# = L1P3
#*7326# = Accessory (I got Vibrator)
#*7683# = Sleep variable (8)
#*7762# = SMS Brearer CS (Activate or Deactivate)
#*8465# = Time in L1
#*9795# = wtls key
#*2252# = Current CAL
#*2836# = AVDDSS Management (Activate or Deactivate)
#*3877# = Dump of SPY trace
#*7728# = RSAV done# (Everything went to standart but nothing was deleted)
#*2677# = ARM State (None or Full Rate)
*#8999*636# = Have no clue what it is, i see 20 lines
*#9999# = Software version
*#8999*8376263# = HW ver, SW ver and Build Date
*#8888# = HW version
*#8377466# = Same HW/SW version thing
*#7465625# = Check the locks
*7465625*638*Code# = Enables Network lock
#7465625*638*Code# = Disables Network lock
*7465625*782*Code# = Enables Subset lock
#7465625*782*Code# = Disables Subset lock
*7465625*77*Code# = Enables SP lock
#7465625*77*Code# = Disables SP lock
*7465625*27*Code# = Enables CP lock
#7465625*27*Code# = Disables CP lock
*7465625*746*Code# = Enables SIM lock
#7465625*746*Code# = Disables SIM lock
*7465625*228# = Activa lock ON
#7465625*228# = Activa lock OFF
*7465625*28638# = Auto Network lock ON
#7465625*28638# = Auto Network lock OFF
*7465625*28782# = Auto subset lock ON
#7465625*28782# = Auto subset lock OFF
*7465625*2877# = Auto SP lock ON
#7465625*2877# = Auto SP lock OFF
*7465625*2827# = Auto CP lock ON
#7465625*2827# = Auto CP lock OFF
*7465625*28746# = Auto SIM lock ON
#7465625*28746# = Auto SIM lock OFF
*2767*3855# = E2P Full Reset
*2767*2878# = E2P Custom Reset
*2767*927# = E2P Wap Reset
*2767*226372# = E2P Camera Reset
#*6420# = MIC Off
#*6421# = MIC On
#*6422# = MIC Data
#*6428# = MIC Measurement
#*3230# = Trace enable and DCD disable
#*3231# = Trace disable and DCD enable
#*3232# = Current Mode
#7263867# = RAM Dump (On or Off)
*2767*49927# = Germany WAP Settings
*2767*44927# = UK WAP Settings
*2767*31927# = Netherlands WAP Settings
*2767*420927# = Czech WAP Settings
*2767*43927# = Austria WAP Settings
*2767*39927# = Italy WAP Settings
*2767*33927# = France WAP Settings
*2767*351927# = Portugal WAP Settings
*2767*34927# = Spain WAP Settings
*2767*46927# = Sweden WAP Settings
*2767*380927# = Ukraine WAP Settings
*2767*7927# = Russia WAP Settings
*2767*30927# = GREECE WAP Settings
*2767*73738927# = WAP Settings Reset
*2767*49667# = Germany MMS Settings
*2767*44667# = UK MMS Settings
*2767*31667# = Netherlands MMS Settings
*2767*420667# = Czech MMS Settings
*2767*43667# = Austria MMS Settings
*2767*39667# = Italy MMS Settings
*2767*33667# = France MMS Settings
*2767*351667# = Portugal MMS Settings
*2767*34667# = Spain MMS Settings
*2767*46667# = Sweden MMS Settings
*2767*380667# = Ukraine MMS Settings
*2767*7667#. = Russia MMS Settings
*2767*30667# = GREECE MMS Settings
*335# = Delete all MMS Messages
*663867# = Dump Mm file
#*536961# = WAPSAR enable / HTTP disable
#*536962# = WAPSAR disable / HTTP enable
#*536963# = Serial eable / Others disable
#*53696# = Java Download Mode
#*5663351# = Wap Model ID [Your Model]
#*5663352# = Wap Model ID [SEC-SGHXXXX/1.0]
#*566335# = Wap Model ID [SEC-SGHXXXX/1.0]
*2767*66335# = Check on which model it is
*2767*7100# = SEC-SGHS100/1.0
*2767*8200# = SEC-SGHV200/1.0
*2767*7300# = SEC-SGHS300/1.0
*2767*7650# = Nokia7650/1.0
*2767*2877368# = Reset WAP Model ID to standart
i found this post on an european site and it was posted by .::kabir::.
sorry for such a long post. if any of this crap helps anyone please hit my thanks button.
Wow, I didn't know there were so many. I only knew maybe three or four of those.
i think this is an old list and maybe that is why only some work on my samsung. maybe a senior member will read this thread and tell us what the deal is with this list.
clarification: i understand how to use these codes and what they do. i just dont know if they are model specific or if they are supposed to work on all samsung phones.
Got a note from TRusselo and he told me this list was for several different samsung phones and the list was old. He said the best list for captivate codes are in the app sgs tool. it was excellent info. thanks tru.
I would really like ti know what that "dump of SPY trace" is ?? Kinda creepy sounding, but knowing android probably something that has nothing to do with what it sounds like.(lol)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
leezrd said:
I would really like ti know what that "dump of SPY trace" is ?? Kinda creepy sounding, but knowing android probably something that has nothing to do with what it sounds like.(lol)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
+1
10 chars
is it possible to get boot to gecko running on the droid
https://wiki.mozilla.org/B2G
https://wiki.mozilla.org/B2G/HardwareRequirements
Boot to Gecko Hardware Requirements
Minimum Required:
CPU: ARMv6
RAM: 256MB
Recommended:
CPU: Cortex A5 class or better, ARMv7a with NEON
GPU: Adreno 200 class or better
Connectivity: WiFi and 3g
Sensors:
Accelerometer
Proximity
Ambient light
A-GPS
with this being said it be nice to play with on the droid
FSTAB:
http://pastebin.com/LN75y6Jj
Build.Prop:
http://pastebin.com/ehgwGL8A
System Dump:
http://www.mediafire.com/download/ux9gg1661ojkao9/sprat-user_4.4W_KMV78N_SYSTEM_DUMP.zip
*Copyright owned by Samsung and Google
Getprop
http://pastebin.com/2mhPZhLV
Hardware Info
https://www.youtube.com/watch?v=NNtBzOiXLPw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENABLE ADB
- Tap on top right of watchface
- scroll down to Settings
- Scroll down and tap About
- Tap Build Number 5x's
- Go back to settings and Development Options should be available
- Enable ADB debugging
- Plug in the charger dock with a USB connected to the computer
- Authorize on your Phone for USB
RECOVERY MODE
FASTBOOT/BOOTLOADER Mode
Codename: SPRAT
Product: Gear Live
Key Specs:
- Qualcomm 400 chipset (Quadcore msm8226 - Same exact one as Moto G!)
- Adreno 305
- OpenGL 3.0 support
- 320x320 screen (hdpi)
Sensors / Parts:
- Invensence MPU6515 MEMs Gryo HERE
- AK8963c 3 Axis Compass and Hall effect sensor HERE (TOGETHER 1 +2 = InvenSense MP92M 9-axis Gyro + Accelerometer + Compass)
- Heart Rate Detector ( didn't see what the chipspec was).
- Samsung Driver abstracted "sensors" (just conglomerates info from the existing sensors).
- MAX77836—MUIC
- STMicroelectronics STM32F401 Cortex M4 microcontroller
- Qualcom PM8226 power management IC
- InvenSense ICS-43430 microphone
- Cypress Semiconductor CYTMA54 touchscreen controller
* holding for space *
Childofthehorn said:
.......
Click to expand...
Click to collapse
Sorry but app and priv-app and framework is complete or is not?
RevengeDevTeam said:
Sorry but app and priv-app and framework is complete or is not?
Click to expand...
Click to collapse
Its what I could get by doing a pull of /system. It should be complete.
Remember that the WEAR is a build type in Android.I don't quite get why they built so many of the components for Cellular into it though... probably just easier to have it be complete binaries.
Fastboot commands extracted from aboot:
Code:
continue
reboot
reboot-bootloader
preflash
flash
boot
oem lock
oem enable-console
oem disable-console
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge 0
oem off-mode charge 1
default settings:
Code:
[email protected]:~/Downloads$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: �������������������������������������������
You'll want disable-console, enable-charger-screen, and off-mode-charge 1 in order to get stock functionality with best battery life. For debugging, you can switch these options.
UART boot log: http://pastebin.com/M5ctEFtT
It was said that the Gear Live should only be running one processor. You can see in the UART log that there are 4 processors active. Here is /proc/cpuinfo which confirms this.
Code:
[email protected]:/proc $ cat cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
Hardware : Qualcomm MSM 8226 (Flattened Device Tree)
Revision : 0004
Serial : 0000000000000000
Recommendations for developers to increase battery life:
1. Remove useless drivers such as:
Code:
SCSI subsystem initialized
Code:
SCSI Media Changer driver v0.25
Code:
sdhci: Secure Digital Host Controller Interface driver
and many others
2. Disable unused processors, or offer a "power saving" mode to disable those additional processors
3. examine processor scaling
4. reduce use of SELinux. it's worthless.
4a. when device is near phone, phone security is off
4b. turning on ADB and accessing storage is easy as security is disabled on the phone
4c. because of the above reasons the device causes the phone to be insecure
4d. the device is wasting battery on its own security while reducing the security of the phone.
5. enable thermal max frequency
Code:
[ 4.700499] msm_thermal:disable_msm_thermal Max frequency reset for CPU1
[ 4.700509] msm_thermal:disable_msm_thermal Max frequency reset for CPU2
[ 4.700517] msm_thermal:disable_msm_thermal Max frequency reset for CPU3
6. above all: audit your logs.
We need a boot.img or at least a buildable kernel source to work with in order to go any further.
Anyone having this issue? Trying to unlock my Samsung Gear Live. ADB recognized device, Enabled communication through my phone, watch boots just fine using "ADB reboot bootloader" however, when entering "fastboot oem unlock" I get "waiting for device"?
Yes my watch is plugged in to my computer. I have tried several different ports. Any help?
I couldn't find the answer to this using the search function.
Thanks guys
*Edit*
I figured out the issue. If anyone is having this problem visit here:
http://stackoverflow.com/questions/24583354/adb-doesnt-recognize-samsung-gear-live-or-lg-g-watch
Follow the directions accpet one thing. Toward the bottom you will see a post telling you to install a "Samsung Device" instead of a generic "Android Device" Make sure you install the "Samsung device" if using a Gear Live.
UART Locations
This device charges VERY slowly, and on top of that, it's also picky about the charging port. In order to be sure you're always charging, you'll want to use a USB condom. This is important because many aftermarket chargers are unlabeled.
Here you can see it won't charge at all on an "Apple" charger
And it charges well on an "Android" charger with D+ and D- tied together.
The good news is that the charging rate is generally controlled by software, so if samsung would release kernel code, we could likely fix this.
AdamOutler said:
Recommendations for developers to increase battery life:
1. Remove useless drivers such as:
Code:
SCSI subsystem initialized
Code:
SCSI Media Changer driver v0.25
Code:
sdhci: Secure Digital Host Controller Interface driver
and many others
2. Disable unused processors, or offer a "power saving" mode to disable those additional processors
3. examine processor scaling
4. reduce use of SELinux. it's worthless.
4a. when device is near phone, phone security is off
4b. turning on ADB and accessing storage is easy as security is disabled on the phone
4c. because of the above reasons the device causes the phone to be insecure
4d. the device is wasting battery on its own security while reducing the security of the phone.
5. enable thermal max frequency
Code:
[ 4.700499] msm_thermal:disable_msm_thermal Max frequency reset for CPU1
[ 4.700509] msm_thermal:disable_msm_thermal Max frequency reset for CPU2
[ 4.700517] msm_thermal:disable_msm_thermal Max frequency reset for CPU3
6. above all: audit your logs.
Click to expand...
Click to collapse
Can I do that thru ADB? I am no developer at all btw!
Joe0113 said:
Can I do that thru ADB? I am no developer at all btw!
Click to expand...
Click to collapse
You probly don't want to be in this thread then.
Doesn't removing "sdhci" disable OTG functionality and possibly other USB devices, enumerated during DLOAD mode etc?
What is a USB condom?
And what is that nice USB-to-micro-USB thing you've got there? I see some useful pins... on it.
And yes, it is disturbing to see that a wrist watch has twice the number of processor cores than my daily phone!
EDIT: I just found answers here:
http://www.xda-developers.com/android/smartphone-chargers-xdatv/
http://www.amazon.com/Breett-Charger-Doctor-Current-Voltage/dp/B00JO73278/?tag=viglink20238-20
http://int3.cc/products/usbcondoms
Great! Will get at least one of each!
AdamOutler said:
This device charges VERY slowly, and on top of that, it's also picky about the charging port. In order to be sure you're always charging, you'll want to use a USB condom. This is important because many aftermarket chargers are unlabeled.
The good news is that the charging rate is generally controlled by software, so if samsung would release kernel code, we could likely fix this.
Click to expand...
Click to collapse
Adam, the issue with the charger is one which I filed early on the bug tracker and got to samsung.
Its a problem with the MAX77836- MUIC charger recognition code. Its a problem that I have encountered before with Samsung's custom kernel drivers for the MAX chipsets. You can get more in-depth charging info by just plugging a charger and running
"dmesg | grep max77 " , but we don't have root yet ( i haven't really spent any time on it).
I bet that if you change the ADC value on the ID pin of the MicroUSB connector you will get better results.
The MUIC general code is fantastic and then the individual function code classes are absolute junk.
Here is the values for the ADC and functions for most every Samsung Device:
ADC_DOCK_PREV_KEY = 0x04,
ADC_DOCK_NEXT_KEY = 0x07,
ADC_INCOMPATIBLE1_CHG = 0x08, /* 0x01000 10.0K ohm*/
ADC_DOCK_VOL_DN = 0x0a, /* 0x01010 14.46K ohm */
ADC_DOCK_VOL_UP = 0x0b, /* 0x01011 17.26K ohm */
ADC_DOCK_PLAY_PAUSE_KEY = 0x0d,
ADC_VZW_USB_DOCK = 0x0e, /* 0x01110 28.7K ohm VZW Dock */
ADC_SMARTDOCK = 0x10, /* 0x10000 40.2K ohm */
ADC_HMT = 0x11, /* 0x10001 49.9K ohm */
ADC_AUDIODOCK = 0x12, /* 0x10010 64.9K ohm */
ADC_CEA936ATYPE1_CHG = 0x17, /* 0x10111 200K ohm */
ADC_JIG_USB_OFF = 0x18, /* 0x11000 255K ohm */
ADC_JIG_USB_ON = 0x19, /* 0x11001 301K ohm */
ADC_DESKDOCK = 0x1a, /* 0x11010 365K ohm */
ADC_CEA936ATYPE2_CHG = 0x1b, /* 0x11011 442K ohm */
ADC_JIG_UART_OFF = 0x1c, /* 0x11100 523K ohm */
ADC_JIG_UART_ON = 0x1d, /* 0x11101 619K ohm */
ADC_CARDOCK = 0x1d, /* 0x11101 619K ohm */
As you can see, there is the UART deeper enable as well.
Childofthehorn said:
Adam, the issue with the charger is one which I filed early on the bug tracker and got to samsung.
Its a problem with the MAX77836- MUIC charger recognition code. Its a problem that I have encountered before with Samsung's custom kernel drivers for the MAX chipsets. You can get more in-depth charging info by just plugging a charger and running
"dmesg | grep max77 " , but we don't have root yet ( i haven't really spent any time on it).
I bet that if you change the ADC value on the ID pin of the MicroUSB connector you will get better results.
The MUIC general code is fantastic and then the individual function code classes are absolute junk.
Here is the values for the ADC and functions for most every Samsung Device:
ADC_DOCK_PREV_KEY = 0x04,
ADC_DOCK_NEXT_KEY = 0x07,
ADC_INCOMPATIBLE1_CHG = 0x08, /* 0x01000 10.0K ohm*/
ADC_DOCK_VOL_DN = 0x0a, /* 0x01010 14.46K ohm */
ADC_DOCK_VOL_UP = 0x0b, /* 0x01011 17.26K ohm */
ADC_DOCK_PLAY_PAUSE_KEY = 0x0d,
ADC_VZW_USB_DOCK = 0x0e, /* 0x01110 28.7K ohm VZW Dock */
ADC_SMARTDOCK = 0x10, /* 0x10000 40.2K ohm */
ADC_HMT = 0x11, /* 0x10001 49.9K ohm */
ADC_AUDIODOCK = 0x12, /* 0x10010 64.9K ohm */
ADC_CEA936ATYPE1_CHG = 0x17, /* 0x10111 200K ohm */
ADC_JIG_USB_OFF = 0x18, /* 0x11000 255K ohm */
ADC_JIG_USB_ON = 0x19, /* 0x11001 301K ohm */
ADC_DESKDOCK = 0x1a, /* 0x11010 365K ohm */
ADC_CEA936ATYPE2_CHG = 0x1b, /* 0x11011 442K ohm */
ADC_JIG_UART_OFF = 0x1c, /* 0x11100 523K ohm */
ADC_JIG_UART_ON = 0x1d, /* 0x11101 619K ohm */
ADC_CARDOCK = 0x1d, /* 0x11101 619K ohm */
As you can see, there is the UART deeper enable as well.
Click to expand...
Click to collapse
Those resistor values come from the Fairchild Semiconductors chip in the Samsung devices. I didn't find that chip in this device.
I posted the uart output which contains the dmesg output. I'm at work so i can't check the max77 in there.
Stock firmware images: http://goo.gl/UDVUh3
XDATV Video
Samsung Gear Live Unboxed the XDA Way:
http://youtu.be/xvY2Y21EYWo
4-hour hack hangout on air
Gear Live Teardown, Hacking, Filming For XDATV.:
http://youtu.be/0RJfBsWWQYo
@Dees_Troy released TWRP Recovery: http://goo.gl/49m8hl
[/thread]
[Thread]
Scratch that end of thread tag. I was overjoyed. There's still a lot of Linuxy stuff that needs to be done. Things like LED Brightness on the kernel and other standard hardware references which haven't been properly implemented. Standard Linux Device Tree stuff for command-line access is still needed.
The device is configured BT software to charge at .14A. In a stock kernel without the standard ramdisk I was able to pull a max of .45A. Which theoretically could charge the device in about 45minutes. Bumping up the charging rate should be examined as this device's 300mAh battery is far smaller than that of larger phones with the same battery materials, with 2000mAh batteries and charges in the same period of time.
AdamOutler said:
@Dees_Troy released TWRP Recovery: http://goo.gl/49m8hl
[/thread]
Click to expand...
Click to collapse
I wonder if is it possible to port Android Wear from Gear Live to Gear 2..
Thanks in advance
Hello!
I test a fake gyro on Unity 5, with C# and works on my Moto G XT1032
I wanna make a virtual gyroscope with the accelerometer values and the compass value
I've downloaded a gyroscope noise filter (XposedJitteryGyroFix) to replace the gyroscope values with fake gyro values, but this don't make a gyroscope on my phone, don't works, don't found a gyroscope on apps
Can Xposed make a fake gyroscope on android's system?
what did you download? I'm also interested
compass + accelerometer should make a so so gyro
cougarten said:
what did you download? I'm also interested
compass + accelerometer should make a so so gyro
Click to expand...
Click to collapse
I've download a XposedJitteryGyroFix, that filter the noise from Gyroscope and replace the real Gyroscope Values, but don't make a fake gyroscope on system, because that don't work on my phone
Fake Gyro Script
This code makes a fake gyro values, with (x,y,z)'s acceleration and compass input:
Code:
public float[] fakeGyro(float x, float y, float z, float compass)
{
float[] gyro = new float[3];
double xrot = Math.atan2(z, y);
double yzmag = Math.sqrt(Math.pow(y, 2) + Math.pow(z, 2));
double zrot = Math.atan2(x, yzmag);
double xangle = xrot * (180 / Math.PI) + 180;
double zangle = -zrot * (180 / Math.PI);
gyro[0] = (float)xangle;
gyro[1] = (float)zangle;
gyro[2] = compass;
return gyro;
}
This code convert the degree values to radians, because the gyroscope have values on radians:
Code:
public float degreeToRad(float degree)
{
return degree * 0.0174533f;
}
I've replace this from the filter gyro's project:
Code:
protected void beforeHookedMethod(MethodHookParam param) throws
Throwable {
Field field = param.thisObject.getClass().getEnclosingClass().getDeclaredField("sHandleToSensor");
field.setAccessible(true);
int handle = (Integer) param.args[0];
Sensor ss = ((SparseArray<Sensor>) field.get(0)).get(handle);
if (ss.getType() == Sensor.TYPE_GYROSCOPE || ss.getType() == Sensor.TYPE_GYROSCOPE_UNCALIBRATED) {
changeSensorEvent((float[]) param.args[1]);
}
}
To this:
Code:
protected void beforeHookedMethod(MethodHookParam param) throws
Throwable {
Field field = param.thisObject.getClass().getEnclosingClass().getDeclaredField("sHandleToSensor");
field.setAccessible(true);
int handle = (Integer) param.args[0];
Sensor ss = ((SparseArray<Sensor>) field.get(0)).get(handle);
// PUT VALUES HERE
float x = 0;
float y = 0;
float z = 0;
float compass = 0;
float[] val;
if(ss.getType() == Sensor.TYPE_ACCELEROMETER)
{
val = (float[])param.args[1];
x = degreeToRad(val[0])/9.81f;
y = degreeToRad(val[1])/9.81f;
z = degreeToRad(val[2])/9.81f;
/*x = val[0];
y = val[1];
z = val[2];*/
}
if(ss.getType() == Sensor.TYPE_ORIENTATION)
{
val = (float[])param.args[1];
compass = degreeToRad(val[0]);
}
float[] Gyro;
Gyro = fakeGyro(x,y,z,compass);
if (ss.getType() == Sensor.TYPE_GYROSCOPE || ss.getType() == Sensor.TYPE_GYROSCOPE_UNCALIBRATED) {
//changeSensorEvent((float[]) param.args[1]);
changeSensorEvent(Gyro);
}
}
how to use the Code?
Hey,
I have the same Problem..
I also need a fake gyroscope sensor on my Sony m5, lollipop 5.1
Could you please tell me how to use the Code above?
Thanks in Advance
Luis
GaussGEIST said:
Hey,
I have the same Problem..
I also need a fake gyroscope sensor on my Sony m5, lollipop 5.1
Could you please tell me how to use the Code above?
Thanks in Advance
Luis
Click to expand...
Click to collapse
The calculation of FakeGyro is using accelerometer X Y and Z, but these variables is between -1 and 1, but I don't know how is on Android Studio, I've made it for Unity 5 and works on game, not made a virtual gyro
That don't works because I don't know why, the apps don't recognize the fake gyro, and I don't know how make it works, I mind the filter only replace values of gyro, but don't make a virtual gyro with the values that try to replace
I don't know how can make a virtual gyroscope's sensor
I've download the source of XposedJitteryGyroFix and edit with:
Add the first and second code one line before of:
Code:
private static List<Object> antiJitterValues(boolean absolute_mode, float[] values, float[][] medianValues, float[] prevValues) {
The first code is for calculate fake gyro with Acceleration(X Y Z) and Compass
The second code is for convert degrees to rads
The third code it's for find to replace with the fourth code
any news?
kos25k said:
any news?
Click to expand...
Click to collapse
No, I don't know how to do that works, and I haven't got help of someone
nicolobos77 said:
No, I don't know how to do that works, and I haven't got help of someone
Click to expand...
Click to collapse
hello, i share your thread here : [XPOSED] VirtualSensor - Emulate a gyroscope from the accelerometer and compass
nicolobos77 said:
Hello!
I test a fake gyro on Unity 5, with C# and works on my Moto G XT1032
I wanna make a virtual gyroscope with the accelerometer values and the compass value
I've downloaded a gyroscope noise filter (XposedJitteryGyroFix) to replace the gyroscope values with fake gyro values, but this don't make a gyroscope on my phone, don't works, don't found a gyroscope on apps
Can Xposed make a fake gyroscope on android's system?
Click to expand...
Click to collapse
That's awesome dude, hope someone could help you soon!
Groso, espero que alguien te pueda ayudar!
josegon30 said:
That's awesome dude, hope someone could help you soon!
Groso, espero que alguien te pueda ayudar!
Click to expand...
Click to collapse
Someone have created a module and works on my Moto G
Alguien creo un modulo que funciona en mi Moto G
http://forum.xda-developers.com/xposed/modules/xposed-virtualsensor-emulate-gyroscope-t3424555