Related
Hi
Is there a way to run Linux on the Kaiser ??
I run PuTTY on it without any problems what so ever. Which I like, couse that gives me the ability to control my server at home.
Maybe with an emulator. You can't run it natively, though.
As of yet, Linux won't run on it, and the chances are not ery good that it will run Linux in the near future, because Qualcomm, who makes the processor/system on a chip that runs the PDA has not released the detailed specs for it. Ifyou want to run Linux on a PDA I suggest buying an old iPAQ, or even one of those Sharp Zauruses (Zauri?) that already come with Linux by default.
I think Linux would run great on it.. did a search on the net about the Kaisers system and found this.
This info is gathered from Qualcomm that supplied Kaisers with it's processor. Which means that it is possible to run linux on it.
MSM7200 Chipset Solution
Overview
The Convergence Platform fundamentally redefines wireless mobility with consumer electronic features, superior processing power and advanced applications that take mobile communications to a new level.
Ultra-sleek handsets powered by the MSM7200™ chipset for WCDMA (UMTS)/HSUPA and GSM/GPRS/EDGE (EGPRS) networks will become all-in-one devices, utilising next-generation wireless technology to offer consumers the in-demand features that can change the shape of their day-to-day lives.
Benefits
* Establish long-term customer loyalty with high-end devices that have the processing speeds to power the data-intensive applications consumers use every day
* Deliver easy-to-access premium content over high bandwidth WCDMA/HSUPA and EGPRS networks with integrated Launchpad™ solutions
* Reduce BOM and development costs with an integrated chipset that supports more features for stylishly chic handsets
* Cash in on the demand for multi-tasking devices that combine in-demand consumer electronic features and high-speed wireless
Technical features
* Supports WCDMA/HSUPA and EGPRS networks
* Multimedia Broadcasting Multicast Service (MBMS)
* Integrated ARM11™ applications processor and ARM9™ modem
* QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
* 528 MHz ARM11 Jazelle™ Java® hardware acceleration
* Support for BREW® and Java applications
* Qcamera™: Up to 6.0 megapixel digital images
* Qtv™: Playback at 30 fps VGA
* Qcamcorder™: Record at 30 fps VGA
* Q3Dimension™: Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
* gpsOne® position-location assisted-GPS (A-GPS) solution
* Support for Linux® and other third-party operating systems
* Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
* Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and WiFi support
For more details, please review the MSM7200 data sheet.
Click to expand...
Click to collapse
DOH!
DOH!!!!
http://fandroid.net/content/android-kernel-found-android-htc-kaiser-imminent
At least its a step in the right direction...
Bugger.
Oh well it doesn't mean that it aint possible to run linux on it... but it will probably take some time before it's released.
is that really possible?
wow, man i'm impressed with your data. i'm really looking forward that 1 day some device that can really runs on multiple OS(es). i can tell u that NASA and other coporate will sure fuk up with it. LoL...
Hi, I have new Diamond, and I want to ask, why is video playing so slow in GDI, Direct Draw and others. On my Intel PXA 270 520MHz video playback of the samo video was in TCPMP bench 132% on GDI, Direct Draw etc, but Diamond has barely 50%. Why is this?
PXA (Xscale) processors have Wireless MMX instructions to accelerate the video decoding, while MSM chipset inside Diamond does not. Therefore CPU-only decoding will perform very poorly there.
Hovewer, Diamond has a special video decoding accelerator (QTv), so you have to use CorePlayer with Diamond QTv support and obviously switch it to QTv output mode.
Ingvarr said:
PXA (Xscale) processors have Wireless MMX instructions to accelerate the video decoding, while MSM chipset inside Diamond does not. Therefore CPU-only decoding will perform very poorly there.
Hovewer, Diamond has a special video decoding accelerator (QTv), so you have to use CorePlayer with Diamond QTv support and obviously switch it to QTv output mode.
Click to expand...
Click to collapse
My movies (FLV and AVI) don't play in Coreplayer in QTv mode. Are you sure the Diamond has QTv support?
pietrucci said:
My movies (FLV and AVI) don't play in Coreplayer in QTv mode. Are you sure the Diamond has QTv support?
Click to expand...
Click to collapse
same here:
coreplayer/menu/tools/preferences/QTx Display--i have only one option "TyTNII driver mode" with on/off.
if unthick this only option i have no image
coreplayer v1.2.5 build 4506
OK, thanks, so basicly Xscale accelerate video in every mode, GDI, DirectDraw, because CPU recognize video. And Qualcom has something similiar to that Wireless MMX instructions but it is called QTv and you must have player that can use it, like on PC you must have Video Driver to use VGA card, specially for your GPU. Am I right? So, do you think that it makes Xscale bettter CPU? In other ways, are they simmiliar in performance to each other? Qualcomm and Xscale? I thought that Qualcomm i technically better, coue it is ARM11 but Xscale is lower version of ARM core.
I dont see how Wireless MMX alone makes XScale "better CPU" than MSM. Only because its older than QTv and so supported by older TCPMP, while for QTv you need newest CorePlayer?
This is just how it always happen with new technologies, you always have more software adoption for the older ones.
"TyTNII driver mode" is exactly the QTv support. In Coreplayer 1.2.5 its Diamond-compatible.
pietrucci said:
My movies (FLV and AVI) don't play in Coreplayer in QTv mode. Are you sure the Diamond has QTv support?
Click to expand...
Click to collapse
Yes, works great! You net latest version of coreplayer and trigger the TyTN II mode in QTv setting.
so I don´t neet to convert the files anymore
Flanders said:
Yes, works great! You net latest version of coreplayer and trigger the TyTN II mode in QTv setting.
so I don´t neet to convert the files anymore
Click to expand...
Click to collapse
Incorrect. Some flv files do not play with CorePlayer 1.25 or older versions.
Qtv does not trigger full enabeling mode for all extensions.
Correct that the same movies DO play better on TytnII with QTV support enabled vs. RAW- GDI mode on Diamond. sucks no?
Well, thanks, but in one way sale is better. H can accelerate video in every mode available on TCPMP, so the Xscale must recognize video, if he can accelerate it under every display drivers mod. In fact Diamond must have GDI, DirectDraw etc. But he dont accelerate video on them because he can´t recognize it himself, am I right? Has Xscale or Qualcomm support for accelerating FLV ? Or just Xvid DivX ?
Its not the problem of the MSM CPU, but the problem of TCPMP.
TCPMP have no support for MSM QTv, only for XScale Wireless MMX, thats why it performs poorly on MSM and better on XScale. Because development of TCPMP was basically stopped more than a year ago.
Use latest Coreplayer, it has the proper QTv support and delivers the good performance on Diamond.
Yes, i understand it. I am just saying that even with new CorePlayer you MUST set QTv, but with Xscale, you can set every driver mode you want, GDI, DD, etc. and Xscale can handle it, can recognize it at every driver-mode.
pokevitek said:
Yes, i understand it. I am just saying that even with new CorePlayer you MUST set QTv, but with Xscale, you can set every driver mode you want, GDI, DD, etc. and Xscale can handle it, can recognize it at every driver-mode.
Click to expand...
Click to collapse
Its because XScale Wireless MMX handles only decoding.
QTv handles both decoding & display, its more efficient this way (at least for video playback, especially at higher resolutions).
Now I am little confused. I was asking why Xscale can handle video decoding in every mode, GDI, DD etc. , but Qualcomm only in QTv. And you said that it is becouse of QTv helps displaying, so Xscale can better display images if withount displaying can play video in every mode?
So, I tried CorePlayer 1.2.5 4506 and unfortunelly I must say that Diamond is very slow device. Very! For example: Asus P535 Intel PXA 520MHz - same testing video sequences (704x480, 29FPS, 1,6 Mb/s) - Diamond - QTv mode - 66 %. P535 - DirectDraw - 109%. I want to cry.
You are not directly comparing VGA output with QVGA do you? In VGA case its 4x times more pixels to process. So actually Diamond is more than 2 times faster.
Ingvarr said:
You are not directly comparing VGA output with QVGA do you? In VGA case its 4x times more pixels to process. So actually Diamond is more than 2 times faster.
Click to expand...
Click to collapse
he does, the p535 only has 320x240 display.
Eh, I though you may ask for it, I was thinking this way: Video is first decoded (doesent depend on resolution) than image is scale for screen, in QVGA devices is scaled down, in VGA is normal or scaled up. I didnt see much influence of VGA display here, absolutelly no on decoding, which is most important part.
OK, I did some research and there is an idea: Dell Axim x50v - the 624 PXA CPU, VGA screen. I found that on beta player (practically same as the CorePlayer) a video was played on 92% (i remember just bitrate - 1.6Mb). Of course withount 2700G support. With this support it is 190!!!!!%. If is true, that the Wireless MMX is "QTv" (multimedia instruction set) than Diamond is as fast as 624MHZ Xscale CPU, but only in Axim. Loox 720 (again VGA) can play same file with 520MHZ Xscale on 116%, which is also very good. (Only if case that you can QTv consider as Wirelass MMX analogy). This is bad. Our device is 15% slower using special QTv mode than Xscale on same frequency. I read that ATI Imageon can play with ATI driver play same video at 142%, which is GREAT! On VGA device of course. Does Diamond have ATI Imageon chip? I think TyTN has one. Anyway, they wrote that it isnt just Imageon work, but also a Excelent HP drivers. So I think we can expect some noticable video playback improvement in never versions of CorePlayer, and maybe, just maybe with some new ROM, since Diamond has some drivers, HTC cannot say that they must pay some license, and they just optimalised drivers. If this failes too, there still remains "TyTN 2 driver", and maybe it will be usable on Diamond too.
All I wil say is that nothing works for me on QTv, I have to set it to GDI and only then do I get both video and audio. I have no problem with playback, it plays very smooth actually.
Just a bit confused as to why QTv doesnt work for me.
I'm using AVI files and I'm running Coreplayer version 1.2.2 build 3852
Regards
D.C
Simple answer - you just need Core Plyer 1.2.5. It is becouse of older version support QTv, but not on WM6. Newest version does.
Just because opengl es and D3DM work doesnt mean that the GPU is doing the work. I think all we have here is a software rasterizer that is using the CPU. There is no evidence that i am aware of that proves the graphics chip is active. Here is the evidence i collected that shows how the graphics are rendered.
1. In Touchflo 3d,if you go to the settings tab,and click about, there is a list of all the technology used to develop TF3D. Where it says opengl, there is a copyright 2004 Hans-Martin Will. Hans-Martin Will started the vincent3d opensource opengl es project, which is a SOFTWARE implementation. Basically what this means is,Touchflo 3d uses this graphics library to render graphics.
2.The D3Dmobile driver is only a wrapper around opengl ES. Why would we need a wrapper for D3DM if hardware drivers were present? What this means is that D3Dm is also rendered by software only. Notice how DirectDraw is also slow? Thats because there are no drivers.It wouldnt make sense for drivers to allow 3d acceleration only without support for 2d.
3.Samsung Omnia drivers work on the Diamond/Raphael. Huh? These two devices dont even have the same graphics chip. How can a driver for one graphics chip work on a completely different brand/model/type of graphics chip? It cant. The only explanation there could be is that the omnia driver is also a software rasterizer and thats why it works with the htc devices.
that sucks, because it makes sense..
most interesting...
i smell conspiracy...
so true.......................................
Play a very high quality MP4 (h.264) in software mode (with coreplayer for an example) and watch your diamond completely choke, then launch the same video with windows media player and see the difference!
That's one proof of hardware acceleration at least...
Also I highly doubt a game like Xtract would run as great as it does on the Diamond without any hardware acceleration, the graphics and framerate is way to good for the cpu to handle in only software mode, even if it was just drivers.
Aha, that is perhaps why iGo runs way better on my old tek S200 than on my fresh, new touch diamond.
mayby if you read the posts & topics
then you would see there is a 3d driver
just use de diamond ati 3d driver
my diamond goes from 0.2 fps in the hologram program to an stable 25 fps
Thats a hole inprovement
Ps sorry for my bad english
and i also included the driver in the attachment
Greetings Nossie
Hm, where did you find that? It didn't notice any differnce in the slowness of IGO really..Why isn't that installed by default?
disagree...
test the software and hardware versions of COD 2, THPS 2 and NFS Undercover. See the difference: 3D acceleration not only improves the texture and graphics in general, but the framerate. I think if it was just some kind of emulation 3d, improved graphics would worsen the framerate, but what you see is an increase in FPS! Therefore, I believe there is actually hardware acceleration.
I was just wondering has anybody come across a beta test of windows mobile 7 yet ????
if so where can i get it ?
i am just itching to get my hands on it
kevmass said:
I was just wondering has anybody come across a beta test of windows mobile 7 yet ????
if so where can i get it ?
i am just itching to get my hands on it
Click to expand...
Click to collapse
Even if someone did get their hands on it most likely the touch pro 2 would not even run it. It is not even close to the minimum requirements MS has listed for devices.
WM7 Chassis 1 Specification
Core requirements:
Processor: ARM v6+, L2 Cache, VFP, Open GL ES 2.0 graphics HW (QCOM 8k, Nvidia “Tegra” AP15/16* and TI 3430 all meet spec)
Memory: 256MB+ DRAM, 1G+ Flash (at least 512MB fast flash – 5MB/s unbuffered read @4K block size)
Display: WVGA (800×480) or FWVGA (854×480) 3.5” or greater diagonal
Touch: Multi-touch required
Battery: Sufficient to meet Days of Use LTK requirements.
Controls: Start, Back, Send and End are required (soft controls allowed as long as they are always present).
Peripherals:
Camera: 3MP+, flash optional, 2nd camera optional (VGA resolution sufficient)
GPS: aGPS required
Sensors required: Light Sensor, Compass (3 axis, 5 degrees, 100 Hz sample rate), Accelerometer (3 axis, 2mg resolution, 100 Hz sample rate)
USB: High speed required, 20 MB/s transfer rate.
BlueTooth: BT2.1 required, must run MSFT BT stack, CSR BlueCore6 or later recommended.
Wi-Fi: 802.11B/G required, must run MSFT Native Wi-Fi stack, Atheros 6002 or Broadcomm 4325 recommended.
Connectors: Micro USB and 3.5mm Audio required.
Options:
FM tuner: If tuner HW is present it will be detected and supported by the Media application.
Haptics
SD Card (Micro SD recommended)
DPAD, qwerty or 12/20 key keyboards all optional
Nope, and the latest speculation is on this thread : http://forum.xda-developers.com/showthread.php?t=554981
Ta
Dave
Lets start a hack-pack on the Galaxy S3!
We need a place to collect information as it becomes available. I've started these threads in the past here: http://forum.xda-developers.com/showthread.php?t=1111866 and here: http://forum.xda-developers.com/showthread.php?t=1316501 once this matures, we'll move this thread to the hardware hacking forum.
Why Hardware Hacking? The upcoming release is expected to be an "international variant". Generally Samsung designs their International variant which all carrier variants are designed upon. The various GalaxyS3 devices are expected to be generally similar across the board. Information which applies to one model can be applied to other models, with additional datasheets added into the hack-pack.
So far we know the processor is a S5E4412. I wrote an article about that here: http://www.xda-developers.com/android/the-galaxy-s-iii-s5e4412-processor-a-hackers-overview/
Here are the specs on this processor:
Code:
Overview
Exynos 4412 (S5E4412) is a 32-bit RISC cost-effective, low power, performance optimized and
Coretex-A9 Quad Core based micro-processor solution for smart phone applications. To provide
optimized hardware performance for the mobile telecommunication services and general
applications on smart phone, Exynos 4212 adopts 64-bit/128-bit internal bus architecture and
many powerful hardware accelerators for different tasks. These tasks, for example are, motion
video processing, Image Signal Processing, display control and scaling. Integrated Multi Format
Codec (MFC) supports encoding and decoding of MPEG-2/4, H.263, H.264 and decoding of VC1. This
hardware Encoder/Decoder supports real-time video conferencing and digital TV out.
The memory system has dedicated DRAM ports and Static Memory port. The dedicated DRAM ports
support LPDDR2 interface for high bandwidth. Static Memory Port supports NOR Flash and ROM type
external memory and components.
To reduce the total system cost and enhance the overall functionality, Exynos 4212 includes many
hardware peripherals, such as TFT 24-bit true color LCD controller, Camera Interface, MIPI DSI,
CSI-2, System Manager for power management, embedded GPS and GLONASS, MIPI slimbus interface,
MIPI HSI, four UARTs, 24-channel DMA, Timers, General I/O Ports, three I2S, S/PDIF, eight IIC-BUS
interface, three HS-SPI, USB Host 2.0, USB 2.0 Device operating at high speed (480Mbps), two USB
HSIC, four SD Host and high-speed Multimedia Card Interface, Chip to Chip interface, and four
PLLs for clock generation.
Package on Package (POP) option with MCP is available for small form factor applications.
Features of Exynos 4412
The features of Exynos 4412 (S5E4412) are:
ARM Cortex-A9 based Quad CPU Subsystem with NEON
32/32 KB I/D Cache, 1 MB L2 Cache
Operating frequency up to 800 MHz at 0.9 V, 1 GHz at 1.0 V, and 1.5 GHz at TBD V
128-bit/64-bit Multi-layer bus architecture
Core-D domain for ARM Cortex-A9 Quadl, CoreSight, and external memory interface
Operating frequency up to 200 MHz at 1.0 V
Global D- domain mainly for multimedia components and external storage interfaces
Operating frequency up to 100 MHz at 1.0 V
Core-P, Global-P domain mainly for other system component, such as system peripherals, peripheral
DMAs, connectivity IPs and Audio interfaces.
Operating frequency up to 100 MHz at 1.0 V
Audio domain for low power audio play
Advanced power management for mobile applications
64 KB ROM for secure booting and 256 KB RAM for security function
8-bit ITU 601/656 Camera Interface supports horizontal size up to 4224 pixels for scaled and 8192
pixels for un-scaled resolution
Multi Format Codec provides encoding and decoding of MPEG-4/H.263/H.264 up to [email protected] fps and
decoding of MPEG-2/VC1/Xvid video up to [email protected]
Image Signal Processing subsystem
JPEG encoder supports various format.
3D Graphics Acceleration with scalable Multicore GPU.
2D Graphics Acceleration support.
1/2/4/ 8bpp Palletized or 8/16/24bpp Non-Palletized Color TFT recommend up to SXGA resolution
HDMI interface support for NTSC and PAL mode with image enhancer
MIPI-DSI and MIPI-CSI interface support
One AC-97 audio codec interface and 3-channel PCM serial audio interface
Three 24-bit I2S interface support
One TX only S/PDIF interface support for digital audio
Eight I2C interface support
Three SPI support
Four UART supports three Mbps ports for Bluetooth 2.0
On-chip USB 2.0 Device supports high-speed (480 Mbps, on-chip transceiver)
On-chip USB 2.0 Host support
Two on-chip USB HSIC
Four SD/ SDIO/ HS-MMC interface support
32-channel DMA controller (16 channels for Memory-to-memory DMA, 16 channels for Peripheral DMA)
Supports 14 8 key matrix
Configurable GPIOs
Real time clock, PLL, timer with PWM, and watch dog timer
Multi-core timer support for accurate tick time in power down mode (except sleep mode)
Memory Subsystem
Asynchronous SRAM/ ROM/ NOR interface with x8 or x16 data bus
NAND interface with x8 data bus
LPDDR2 interface (800 Mbps/pin DDR)
Embedded GPS/AGPS/GLONASS.
We need to find a real datasheet on this Exynos processor, but I've yet to find one. Please post related datasheets in this thread.
The best way to collect a bulk amount of information on a new device is to install Elite Recognized Developer Supercurio's "Voodoo Report" from the android market https://play.google.com/store/apps/details?id=org.projectvoodoo.report. Once we have a Voodoo Report, we can extrapolate data and begin collecting information about the rest of the device.
If you happen to get ahold of a GalaxyS3, please run a voodoo report and send it to me at (my username)@gmail.com
Credits and thanks
None yet
This is a development thread. Please do not post in this thread unless you have something to contribute. It only makes the thread longer and the information gets spread out across multiple pages.
I already suggested to someone attending the event in London to install and extract a report here: http://www.reddit.com/r/Android/comments/sl81a/ill_be_at_samsungs_galaxy_s3_announcement/
Could you please +1 the comment so that it ends up in the top3 requests.
Hope it will work! Fingers crossed...
I think it's worth noting that anyone who has early access to this phone, also please take some high resolution internal pictures of the circuit board, and post links to them here, so that we can confirm the hardware used and search for undocumented chips etc. Also here is the Supercurio (?) live Google document for SGS3 internal specifications.
GT-I9300 Service Manual
So we got the Service Manual! Thanks to the user renierx in this post.
However, the manual pages were seriously messed up and in several files, so I repackaged them in the correct order.
Download Here!
[or here, 121 pages, sections 1-9, 7zip, ~7.7MB]
Issues/Features
Block-Diagram (p.27) is probably fake since its an exact copy of that in the GT-I9100 Service Manual (and thus not showing NFC etc.)
MHL (SiI9244BO) chip and schematics is missing (but can be found in the GT-I9100 Service Manual)
U500 (MAX77686 EWE+T) is very unclear (p.78,82) but pin out names can be clearly seen on p.89.
Samsung part descriptions have been correctly (?) left intact on both schematics and in the parts list. (Thanks Samsung!)
Some of the chips without pin outs and not shown on the schematics of the GT-I9100 Service Manual, can be found in this manual. Great cross reference! (I.e. U108/RF6590 p.94)
I have not been able to find the "Region Selector Jumpers" in the schematics (as shown in post #10 below)
So now...
WE NEED INTERNAL HIGH-RESOLUTION PICTURES!
(We now got some thanks to Chipworks and iFixit!)
...So that we can verify the Service Manual.
I will eventually produce a complete parts list with datasheets in the Hack-Pack...
So it does not differ any region,Telco or country we resides am I right?
^^ As long as your device is labelled as a "GT-I9300", only the firmware should differ.
EDIT: Actually the schematic doesn't seem to differ, but there are some solder jumpers as shown in Post#10 below, that determine region in some way, still unknown.
Not sure if anyone posted but here's the internal teardown from ifixit
http://www.ifixit.com/Teardown/Samsung-Galaxy-S-III-Teardown/9391/1#.T8k3btVYsuh
EDIT: More details from Chipworks
http://www.chipworks.com/en/technic...downs/2012/06/inside-the-samsung-galaxy-siii/
^^ I'm slightly disappointed with the fact that iFixit now just gets their pictures from Chipworks. Before, they actually made a good complement to each other. In addition I'm a bit dissappointed in the quality of those pictures as they are not as close to the PCB as is the SGS2 photo coverage. Thus we still need better closeups!
But I am grateful for any pictures at all and also thankful to those websites that attempt to provide us with useful details!
Thanks Chipworks!
Thanks iFixit!
Undocumented Region Related Solder Jumpers
So while having a first look at the i9300 mobo, the 3 region related jumpers, jumped out into my eyes like a glowing iron! AFAICT, they seem undocumented in the Service Manual, and elsewhere. I'd like to know more about these and what chip and pins they are connected to.
Obviously (?) the region codes refer to:
EU = Europe
AU = Australia
IN = India
This is how it looks:
{
"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"
}
Image Courtesy of Chipworks (cc) BY-NC-SA
E:V:A said:
So while having a first look at the i9300 mobo, the 3 region related jumpers, jumped out into my eyes like a glowing iron! AFAICT, they seem undocumented in the Service Manual, and elsewhere. I'd like to know more about these and what chip and pins they are connected to.
Obviosly (?) the region codes refer to:
EU = Europa
AU = Australia
IN = India
This is how it looks:
Image Courtesy of Chipworks (cc) BY-NC-SA
Click to expand...
Click to collapse
I saw that on the Ifixit teardown. I have no idea. Maybe they simply change the moniker of the model number or something.
Service Manual
E:V:A said:
Service Manual,
Click to expand...
Click to collapse
May I ask you where did you find the service manual ? Thanks
removed removed
http://bit.ly/KbGZGj
AdamOutler said:
Why Hardware Hacking? The upcoming release is expected to be an "international variant". Generally Samsung designs their International variant which all carrier variants are designed upon. The various GalaxyS3 devices are expected to be generally similar across the board. Information which applies to one model can be applied to other models, with additional datasheets added into the hack-pack.
Click to expand...
Click to collapse
This is unfortunately not true.
For example, it's absolutely confirmed that the internals of the AT&T and T-Mobile variant will be COMPLETELY different (Snapdragon S4).
VZW version unknown.
Samsung has routinely made carrier variants vastly different from the international variant over the past year. The SGH-I777 was the last carrier variant device to have any internal resemblance to its international sibling at all.
The SGH-I727 (Skyrocket) and SGH-T989 had zero commonality with the I9100/I777.
Same for the SGH-I717 (AT&T Note) vs. the GT-N7000 (international Note) - They share a name and external dimensions, but have almost no internal commonality.
E:V:A said:
So while having a first look at the i9300 mobo, the 3 region related jumpers, jumped out into my eyes like a glowing iron! AFAICT, they seem undocumented in the Service Manual, and elsewhere. I'd like to know more about these and what chip and pins they are connected to.
Obviously (?) the region codes refer to:
EU = Europe
AU = Australia
IN = India
Click to expand...
Click to collapse
Would these codes refer to the variants of the SGS3?
EG. Australia uses the 9300T version on two of it's networks, India use the 9300G version, and Europe use the international version.
The 'T' version is designed for specific 850 mhz networks that are used by two carriers in Australia and elsewhere in the world, but the international version works just the same on any network in Australia, so go figure
Just note on the US S3:
Yes, it will have a duel-core Snapdragon S4 and have 2gb of RAM available and will come in 16GB / 32GB variants from different carriers.
Hi adam, could you help in finding apx mode for nvidia tegra 3 .. Do u have access to TRM for it ?
via Flying Daggers.
tids2k said:
Hi adam, could you help in finding apx mode for nvidia tegra 3 .. Do u have access to TRM for it ?
Click to expand...
Click to collapse
I'm sure he doesn't have it. In addition I know there are some T3-TRM owners hoovering around here on XDA, but they are either incompetent to use and understand it themselves, while being too scared to share it! It's a very sad story, and the main blocker for helping people unlock, S-Off and UnBrickable mod their phones!
Thanks to my anonymous friend I now possess TRM ... eva do you need it ? Should I post it here.
Sent from my GT-I9300 using XDA Premium HD app
^^ We all need it! I can't give you advice on what you should do. Just follow your hart!