Sorry for this noobish question, I've really only had an Incredible, a Rezound, and a B&N Nook Color, so this kind of fracture within a device was quite a surprise, and really made me a bit paranoid in making sure I had the right instructions for my device, the right recovery, and a ROM that would support my features (like the IR). Maybe this is more common than I'm aware of (like the GSM version of the Rezound, of which there's like 2 threads in the entire Rezound forum for, unlike the major fracturing here).
As someone who just bought this device on Boxing Day, I had no idea there was a P3100, P3110, P3113, SCH-i705... and apparently other models, until I came looking for a Jelly Bean update.
It would have been a lot easier for me to find that out, and get root instructions, a recovery, kernel, ROM, etc for my device had the dev forums been broken out accordingly. It's got to be harder on devs too making ROMs that work only for 3110, for instance, and people claiming bugs with the ROM when they have a different device.
So, I'm a bit curious since the kernels don't appear to work across models and they have different features, how come the forums aren't broken out? Was this a conscious decision? (Like assumptions that a single kernel would support all 4+ models?)
Good to see you over here as well quantum rabbit. I have seen you around the rezound forums, and the nook forums. I had the same problems as you when I first came here a week or two ago. Apparently, the only difference between all of these tab 2s is minor hardware. The p3100=cell radio, p3110=WiFi international, and the p3113=U.S. version. The p3110 is almost identical to the p3113 version, and most ROMs, and kernels work between the two.(at least that is my understanding) There are a couple of threads about this here already, and you are not alone in your thinking. If you need anything, give me a shout, we have been in the same forums since I got my Dinc. If you upgrade to the UK version of the JB ota, and then root, and install clockworkmod, you can maintain the it blaster, or jump into cm10.1. Any who, it is good to see you here:thumbup:
Sent from my Rezound using Tapatalk 2
JeramyEggs said:
Good to see you over here as well quantum rabbit. I have seen you around the rezound forums, and the nook forums. I had the same problems as you when I first came here a week or two ago. Apparently, the only difference between all of these tab 2s is minor hardware. The p3100=cell radio, p3110=WiFi international, and the p3113=U.S. version. The p3110 is almost identical to the p3113 version, and most ROMs, and kernels work between the two.(at least that is my understanding) There are a couple of threads about this here already, and you are not alone in your thinking. If you need anything, give me a shout, we have been in the same forums since I got my Dinc. If you upgrade to the UK version of the JB ota, and then root, and install clockworkmod, you can maintain the it blaster, or jump into cm10.1. Any who, it is good to see you here:thumbup:
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
Good to see you, too. I also noticed Scott is here for the SCH device (Verizon LTE one) and recognized him from the Rez.
I did find the difference thread earlier... thank god for acefsw here: [Q] Differences between models. So I get that the 3110 vs the 3113 is nearly identical, but apparently the p3100 and the SCHi705 are different from the 3113 enough such that all the kernels I find appear to be for the 4G enabled tabs (SCH models), like DoubleShot, Decaf, Scott's etc. (I also see CM9 and 10 kernels). For all I know, they'd work on my device, or they'd work but I'd lose features. I am unsure, yet.
On the Inc, there were single kernels that worked across Froyo, GB, and ICS... on the Rezound, seems like each android version and CM of each android version all have different kernels. Here, unless I'm misunderstanding it appears to be like the Rezound, only that there are also 2 or 3 or 4 hardware variants I may have to worry about to. Which really complicates the situation.
Here's how I see it.
All the P3xxx tabs are nearly identical.
The SCH-I705 is COMPLETELY different from the rest. The I705 is closest relative is the SCH-I535 (VZW GS3). If you or anyone else flashes a I705 kernel/rom/etc on a P3xxx, it will brick. Mount points are completely different, hardware is completely different. Why it's still mixed together with the P3xxx tabs is still a wonder. Though, there aren't many people with the I705 except for a couple of us.
MrHyde03 said:
Here's how I see it.
All the P3xxx tabs are nearly identical.
The SCH-I705 is COMPLETELY different from the rest. The I705 is closest relative is the SCH-I535 (VZW GS3). If you or anyone else flashes a I705 kernel/rom/etc on a P3xxx, it will brick. Mount points are completely different, hardware is completely different. Why it's still mixed together with the P3xxx tabs is still a wonder. Though, there aren't many people with the I705 except for a couple of us.
Click to expand...
Click to collapse
So seems like for Recoveries in particular, the SCH to P31XX is a definitive no go... that helps. Does that mean the 3100, 3110, and 3113 can all use the same recoveries at least, and maybe kernels and such?
I don't plan to play around too much, for now I'm on CWM 6.0.2.3 (May try for TWRP later) and kwbr Espresso, which I saw numerous posts of people on 3113 and how it works great including IR Blaster.
Related
I didn't post download link.
Because its for ME865 china ,but seems the last test version.
fastboot-p3_edison-edison-user-4.0.4--10273930-release-keys-ChinaRetail-CN_chn.tar.gz
Sent from my ME865 using xda premium
dickluo said:
I didn't post download link.
Because its for ME865 china ,but seems the last test version.
fastboot-p3_edison-edison-user-4.0.4--10273930-release-keys-ChinaRetail-CN_chn.tar.gz
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
please do link
Sent from my MB865 using xda premium
I second lkrasner. Any leak could potentially be beneficial, and we won't know until we check.
http://115.com/file/c25msn57#fastbo...273930-release-keys-ChinaRetail-CN-chn.tar.gz (hit the green button to download, it will be pretty slow)
It's an fxz (how they find these things I have no clue). Don't even think about flashing it though. If the international MB865 ICS leaks haven't helped us then I don't think this will be of any help either :\
So, since I'm essentially clueless on the actual coding and development aspects of this type of stuff - I'm no stranger to flashing ROMs and testing them out, been doing that for almost a decade now and still doing it between several devices (Axim X50v/X51v, HP iPAQs, Nexus S, Galaxy S, and now my Atrix 2) - but I don't understand what the actual problem is with this ROM with respect to the AT&T model of the Atrix 2.
I'm going to guess there's something going on with the Chinese/international leaked ROMs that will completely bork/hose/obliterate the AT&T model if I or anyone else attempts to install it, perhaps even permanently bricking it so...
Obviously I'm not about to try it myself, I'll leave that to the more talented folks around here already working on trying to get ICS for all of us. The Atrix 2 is such a damned nice device from the hardware perspective, and yes I'd love to get ICS on it (I know Motorola is working on it but as usual they're so tight-lipped about everything we're never going to know when it'll be available until it actually is, Cheesecake or not...), and now with having messed around with Jelly Bean on the Nexus S for a few hours - wasn't great but it was noticeably "butter" smooth as they're claiming - that gives me very high hopes that ICS will make an appearance on the Atrix 2 soon.
Come on, Motorola, if you can't get talented people to get this done, there's a bunch of people here on XDA that would do it practically for free just to get it done once and for all (not saying they wouldn't like to be compensated, obviously, maybe a free Droid RAZR MAXX or whatever for their efforts).
Yah, I know, Motorola could care less about this phone already, it's such a shame that this "disposable society" is what it is. Hell, I still use my Dell Axim X51v almost daily, and it's close to 7+ years old now, still running a custom Windows Mobile 6.5 from LennySH... I don't believe hardware is "useless" until the moment it actually doesn't work anymore, at all, totally hopelessly bricked or dead.
I'm impatient and I know it, so are most of you reading this.
If I thought a petition would help Motorola just skip ICS completely and jump right to Jelly Bean for the Atrix 2 I'd start one, but obviously that's just a waste of time. Sad we'll most likely never see Jelly Bean on the Atrix 2 officially 'cause it most certainly is a device that could manage it (minus a few aspects like NFC and whatever).
Bleh... just rambling, sorry. But I really would like to get some kind of basis for why the Chinese leaked ROMs are a no-no on the AT&T model, if anyone can spare a few minutes to explain, and be as thorough as you like as I'm all about details.
Thanks...
br0adband said:
So, since I'm essentially clueless on the actual coding and development aspects of this type of stuff - I'm no stranger to flashing ROMs and testing them out, been doing that for almost a decade now and still doing it between several devices (Axim X50v/X51v, HP iPAQs, Nexus S, Galaxy S, and now my Atrix 2) - but I don't understand what the actual problem is with this ROM with respect to the AT&T model of the Atrix 2.
I'm going to guess there's something going on with the Chinese/international leaked ROMs that will completely bork/hose/obliterate the AT&T model if I or anyone else attempts to install it, perhaps even permanently bricking it so...
Obviously I'm not about to try it myself, I'll leave that to the more talented folks around here already working on trying to get ICS for all of us. The Atrix 2 is such a damned nice device from the hardware perspective, and yes I'd love to get ICS on it (I know Motorola is working on it but as usual they're so tight-lipped about everything we're never going to know when it'll be available until it actually is, Cheesecake or not...), and now with having messed around with Jelly Bean on the Nexus S for a few hours - wasn't great but it was noticeably "butter" smooth as they're claiming - that gives me very high hopes that ICS will make an appearance on the Atrix 2 soon.
Come on, Motorola, if you can't get talented people to get this done, there's a bunch of people here on XDA that would do it practically for free just to get it done once and for all (not saying they wouldn't like to be compensated, obviously, maybe a free Droid RAZR MAXX or whatever for their efforts).
Yah, I know, Motorola could care less about this phone already, it's such a shame that this "disposable society" is what it is. Hell, I still use my Dell Axim X51v almost daily, and it's close to 7+ years old now, still running a custom Windows Mobile 6.5 from LennySH... I don't believe hardware is "useless" until the moment it actually doesn't work anymore, at all, totally hopelessly bricked or dead.
I'm impatient and I know it, so are most of you reading this.
If I thought a petition would help Motorola just skip ICS completely and jump right to Jelly Bean for the Atrix 2 I'd start one, but obviously that's just a waste of time. Sad we'll most likely never see Jelly Bean on the Atrix 2 officially 'cause it most certainly is a device that could manage it (minus a few aspects like NFC and whatever).
Bleh... just rambling, sorry. But I really would like to get some kind of basis for why the Chinese leaked ROMs are a no-no on the AT&T model, if anyone can spare a few minutes to explain, and be as thorough as you like as I'm all about details.
Thanks...
Click to expand...
Click to collapse
The ME865 (the Chinese version of the atrix2), has different hardware in it. There are also 3 slightly different versions of the MB865 (also the atrix2)... confused yet....
What it means is that the if you own a US AT&T version, you can not flash any of the international versions of the firmware, because there are slight hardware differences in all of the versions, and the AT&T US version has a whole different radio on top of the different wifi, gps, and GSM/GPRS/UMTA&S chipsets.
Well, that pretty much covers it.
I really do love this device, it's got an awesome form factor, feels fantastic in the hand, same screen size (diagonal) as my beloved HTC HD2 which I don't have anymore (but yes I'll get another one someday just 'cause it's the baddest portable device ever made for enthusiasts). Great cameras, there's really nothing to dislike about it so far, at least to me. Still on the lookout for a Lapdock as well (if my research has been accurate, I can use the original Atrix Lapdock with the Atrix 2 and a small mod of flipping the connectors on the Lapdock around - I hope I'm correct in that).
But ICS would definitely be nice to get, and soon. It's just a shame that Motorola Mobility is so far behind the curve with things. I had hoped that Google's acquisition of them might improve the situation but, with Google's announcement they were buying but leaving them alone to keep on doing what they've been doing, that basically nipped that hope right in the bud.
Anyway, thanks for the answer.
now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
tweeklulz said:
now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
Click to expand...
Click to collapse
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
yeah, and they released this iteration way too soon (<6 months i think) for devs to leave their primes
I think a lot of the devs have sent theirs back. I'm kind of wishing I had with mine. Pretty disappointed with the device so far.
One of the AOKP devs is working on a port to the tf700, and judging by his twitter the only major things holding him back from a release are issues with Bluetooth and some visual glitches. Once we have that, roms should follow since we'll have a working AOSP base.
His twitter account is here:
www.twitter.com/_mrbirdman_
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
and if you were in the e4gt forums from the beginning you will remember that it took several months for anything worth while to show up and how long for stable cm9? it took that forum quite a while to really get going.
legendary1022 said:
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
Click to expand...
Click to collapse
Well to each their own, but to me, it's in custom development that you really begin to use the device to it's full potential. For instance, the OG Xoom has been literally given new life with EOS Jellybean builds. Yes, the Xoom wifi did get the JB OTA update, but stock JB is nowhere near as great as the EOS nightlies. They have tweaked it to capacity. The same will happen with the TF700 in time, I hope.
I also have the Nexus 7 and it's true that development has exploded for it, but honestly, it's a really limited device. For that reason, devs are in a performance competition...pushing things to the max. The TF700 though needs to be able to work really well...we'll need to be able to find the balance between high performance and stability. The fact that it's not really skinned is in its favor. It's not a Nexus device though and so some devs will not be interested in working with it.
Part of the problem in developing custom roms - which I have been doing for the Galaxy S 2/3 - is that currently you cannot decompile/recompile the SystemUI.apk file for the TF700T. XDA user iBotPeaches has taken over development of the apktool (tool to decompile/recompile APKs) project and is aware of the problem I and others are having. He is working to fix it.
As soon as it is fixed, I will be releasing a custom rom for the TF700T, but I need to make changes to the SystemUI.apk file. I can decompile/recompile the framework-res.apk file (have added CRT OFF effect already - and it works better than on my Galaxy S3).
So please have a little patience while the development tools are fixed and improved.
One other point to consider is that the Jelly Bean update is right around the corner, so putting much effort into modifying the current ICS version or actually making Jelly Bean work on the tablet is a waste of time.
So given that Safestrap exists for this device, I've been researching just what it takes to port something like CyanogenMod over to a new device. I'm a long term user of Safestrap back in my Droid 3 / Droid 4 days and can confirm it is reliable and does exactly as claimed...
Now, we all know that the Xoom and the Xoom 2 are almost exactly the same hardware. Is there any particular reason that a Safestrap'd device couldn't have a Xoom ROM installed in a ROM-Slot?
I noticed that Hashcode took down the links to Safestrap 3.12 for the Xoom 2, however it is still available and if it works as it should (I haven't tested it yet due to not having any ROMs to test it with), does anybody know of any particular reason why a similar-spec (Wifi+3G for example) Xoom ROM would not be compatible with a Xoom 2?
Np xoom(tegra) rom will be compatible with a xyboard or xoom2(omap4). They have completely different chips inside. If the xoom 2 users are lucky, they'd get a ported rom out of xyboard 4.1.2 official from community.
Semseddin said:
Np xoom(tegra) rom will be compatible with a xyboard or xoom2(omap4). They have completely different chips inside. If the xoom 2 users are lucky, they'd get a ported rom out of xyboard 4.1.2 official from community.
Click to expand...
Click to collapse
Ahh my bad, I derped on that one. I missed the chipset change when comparing specs... d'oh. There's plenty of work on other OMAP4 devices from Motorola, although the amount of effort it would take to make software from a phone like the Droid 4 work on a Xoom 2 would be incredible. Though it would be worth it.
I haven't researched it fully myself but i hear the the Droid Razr XT910 shares a lot of hardware with the Xoom2/XYBoard. If someone was to attempt a port i imagine that would be the place to start.
I have been relatively happy running on Stock Rooted 4.1.2 on my (2012) Verizon GN 10.1 (SCH-i925) for a while now. This device, unfortunately didn't get much love due to the very few people that bought it. After having a couple of Verizon LTE tablets I've about decided it's not worth buying from Verizon since you get almost completely different hardware from the rest of the world. In any case I digress.
What I want to know with 4.3 or is it 4.4 for these tablets showing up is anyone working on a stock rom higher than 4.1.x? I like CM and all that for about anything except a Note tablet. Unless something's changed since last time I looked for this there is no way to get the samsung features and frameworks in there to do multi screen etc on the CM roms right? Anyone out there still wanting to breathe some more life into these VZW tablets now that the new ones are out?
ddickenson said:
I have been relatively happy running on Stock Rooted 4.1.2 on my (2012) Verizon GN 10.1 (SCH-i925) for a while now. This device, unfortunately didn't get much love due to the very few people that bought it. After having a couple of Verizon LTE tablets I've about decided it's not worth buying from Verizon since you get almost completely different hardware from the rest of the world. In any case I digress.
What I want to know with 4.3 or is it 4.4 for these tablets showing up is anyone working on a stock rom higher than 4.1.x? I like CM and all that for about anything except a Note tablet. Unless something's changed since last time I looked for this there is no way to get the samsung features and frameworks in there to do multi screen etc on the CM roms right? Anyone out there still wanting to breathe some more life into these VZW tablets now that the new ones are out?
Click to expand...
Click to collapse
Just curious, but how did you get it rooted? There is no known Root method on 4.1.2, at least that I know of.
It's been quite a while but if I'm not mistaken I was on an earlier version and then there was some upgrade path to keep root. Found it here on xda
NOTE: I have read the older threads HD2 vs Galaxy S, but they're from the very beginnings of the two and, while I still believe some of the comments are fair enough, they refer to other times.
Ok, so here's the background: I own a Galaxy S (GT-i9000) and I am not satisfied at all with it. Whatever Android version I'll flash on it, it does always strike back with some annoying bugs. Stock GB 2.3.6 works but many apps I have will not go along with it; CM9 (ICS 4.0.4) works, but hangs too often. CM10 (both JB 4.1.2 and 4.2.1) for some reason is so slow I can't even keep it for a day-to-day use, and it crashes frequently with no apparent reason. Finally I ended up using a CM11 nightly (KK 4.4.2), and seems to work, I'm still testing it.
But the point is I can't keep going on like this. It's more than a year that I don't have a stable configuration on the phone and I keep flashing ROMs and installing apps over and over every two weeks or so, every time going through all the settings again and again, restoring backing up and restoring... I'm just tired of it all!
Today, good news: A friend gifted me his HTC HD2 because he messed up with the software and the phone wasn't working anymore. I managed to flash the original WM6.5 OS and I found out that the touchscreen wouldn't respond to any kind of touches -> most probable cause, as discovered from searches, is the touchscreen controller which got broken. A touchscreen (only) would cost me around 25€ (around 35$ USD) excluded the costs of the actual replacing job. Not a very big deal, I may afford that.
I haven't tried an Android OS on the HD2 (even if wanted, I couldn't with a broken touch) but I see there are many custom ROMs available, and this is nice. Hardware differences seem to be not too big and honestly I like very much the HD2 design and the slightly heavy feel of it in my hand (off topic: what's all this thing about making phones light-weight? it's not like people would love to have a piece of paper in hand instead of a phone ). The Galaxy S is just awful from this point of view and as I said before, I am not satisfied at all with it.
The big question: is it worth spending money on the HD2, so I could replace my Galaxy S (possibly sell it)? Or should I keep the Galaxy S? When replying with your opinion on which should I keep, please add your reasons for suggesting such. And before you ask, yes, I have a whole life (apps) on android that I need so I would be using Android on the HD2. Thank you very much in advance!
Hello,
There are 3 threads devoted to discussions about devices, please repost your question in one of these three threads: The what should I buy thread or the The Device Suggestion Thread or the The Device Comparison Thread.
Thanks!