Hi,
Have not put Cyanogenmod on a device in some time and the Tab Pro 12 Wifi (SM-T900) device is new to me. Couple of questions, first - what is the correct codename for the device? I've seen Mondrianwifi in in the Cyanogenmod download device list but that appears to be the name for the 8.4, not this one. And when I look at /system/build.prop I see the value below.
ro.product.device=v2wifi
I thought that was supposed to be the codename per http://wiki.cyanogenmod.org/w/Doc:_porting_intro. The v2wifi value is not on the Cyanogenmod list and further, that name looks pretty generic. I realize Cyanogenmod may not yet have an official ROM ready for the device but was frustrated enough with the Samsung Touch-Wiz crap that I'm thinking of using another port if available. Having the right codename seems essential, needless to say.
While looking at the build.prop I noticed the ro.product.locale.region as GB rather than the expected US.
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
Does this mean the device I've got does not have a US ROM and does that present any problems? If so, is the process to rectify it as simple as downloading the right ROM from the manufacturer? Or are they still playing the lock-up and obscure routine? If having the GB rather than US version could give me issues later then it's time to return it right away while I can. The unit was bought on the special from Quickship Electronics on Ebay when the price was at $369.99 level (since gone up +40 or so) and time to return is short.
Any help on these issues and any recommendations for a good ROM to use as well as the best backup and install procedure would be much appreciated.
Thanks!
Robert C.
Update...
FWIIW to anyone reading this, I changed the launcher to the Google Now one and it's starting to look more familiar - used to running Nexus devices here.
Kies says I have current firmware/latest at PDA:ND4 / CSC:ND4 (XAR).
I do still wonder if I was sold a British tablet rather than an American one. So far it hasn't made any difference but when L comes out I'm sure Samsung will be months delivering an official ROM so that's when I'd probably be more serious about going Cyanogenmod (official).
Some more poking around via Google leads me to believe XAR does indicate US version.
So, just sit tight until Cyanogenmod official is out? Maybe until the L release?
Related
Has anyone purchased a Note 8 from Amazon with the Build JDQ39.N5110UEFMH3, the actual build is N5110UEFMH3, I'm not sure if the prefix is important? I got this at the end of September and some features are missing, the obvious is the keyboard functions (Qwerty, floating,split). Samsung reps seem to be perplexed about this build. I'm thinking others may have this build and may not know that some features are missing. I want to know how to upgrade to the right 4.2.2 version without rooting. Apparently the latest build is N5110UEFMI1. I just want my new tablet to have the right build in case future upgrades are sensitive to the old build. Samsung is still on the case but so far no resolution other than sending it in for service, which I don't want to do if it can be resolved remotely. I can live without the keyboard functions, I'm more concerned with future upgrades and having some unknown build number.
chuckr01 said:
Has anyone purchased a Note 8 from Amazon with the Build JDQ39.N5110UEFMH3, the actual build is N5110UEFMH3, I'm not sure if the prefix is important? I got this at the end of September and some features are missing, the obvious is the keyboard functions (Qwerty, floating,split). Samsung reps seem to be perplexed about this build. I'm thinking others may have this build and may not know that some features are missing. I want to know how to upgrade to the right 4.2.2 version without rooting. Apparently the latest build is N5110UEFMI1. I just want my new tablet to have the right build in case future upgrades are sensitive to the old build. Samsung is still on the case but so far no resolution other than sending it in for service, which I don't want to do if it can be resolved remotely. I can live without the keyboard functions, I'm more concerned with future upgrades and having some unknown build number.
Click to expand...
Click to collapse
I still don't have this resolved, hoping someone new may see this and chime in.
What model do you have?
What is your csc?
Frankly the build you have posted has a very strange build no, how certain are you that u got a genuine piece, and I would have it replaced if posible.
Your build suggests that it was done in august 2013, however The UEF part seems to be something very unlikely if we follow standard patterns. Like UE being Major Regional Part and F denoting The Major Os Build which is really strange as it's 2 generations ahead from anything that is latest available by samsung on this tab.
Sent from my GT-N5100 using Tapatalk
intelliriffer said:
What model do you have?
What is your csc?
Frankly the build you have posted has a very strange build no, how certain are you that u got a genuine piece, and I would have it replaced if posible.
Your build suggests that it was done in august 2013, however The UEF part seems to be something very unlikely if we follow standard patterns. Like UE being Major Regional Part and F denoting The Major Os Build which is really strange as it's 2 generations ahead from anything that is latest available by samsung on this tab.
Sent from my GT-N5100 using Tapatalk
Click to expand...
Click to collapse
I have a GT-N5110 that I bought from Amazon. It was in a sealed box. The Model # on the box is GT-N5110NKYXAR.
Getting it replaced was probably the wise move but I thought sending it back to Amazon for an exchange would have just resulted in another unit from the same shelf mine came from, out of the same batch of weird builds. I have gone round and round with Samsung so long the return/exchange is no longer an option.
I'm sorry, you asked what is my csc, I don't know what that is or where to find it. I appreciate your reply, don't know where to go from here, just wait for Samsung to get back to me I guess.
I purchased mine from Amazon just last week but it was actually sold by BigOutlet it also has the strange Build # JDQ39.N511OUEFMI1 Android Version 4.2.2 this is a black/brown refurbished Note 8 don't know if that makes any difference or not. I got like 3 OTA updates when I turned it on for the 1st time.
Mine has the Samsung keyboard and all it really has is Swiftkey like Flow, no split keyboard or anything like that. I didn't know it was suppose to have those.
gramps50 said:
I purchased mine from Amazon just last week but it was actually sold by BigOutlet it also has the strange Build # JDQ39.N511OUEFMI1 Android Version 4.2.2 this is a black/brown refurbished Note 8 don't know if that makes any difference or not. I got like 3 OTA updates when I turned it on for the 1st time.
Mine has the Samsung keyboard and all it really has is Swiftkey like Flow, no split keyboard or anything like that. I didn't know it was suppose to have those.
Click to expand...
Click to collapse
The build you have is the one I think I'm supposed to have, it is the one mentioned in all of the posts about the 4.2.2 upgrade. You should have the keyboard options. When you have the keyboard up long press on the key next to the spacebar and you should see the 3 keyboard options and the pen as choices. Check the tutorial under the Samsung keyboard settings. Mine shows how it should work in the tutorial but I don't get these options.
If I do that I do have the options you mentioned.
Mine had N511OUEDMD1 OUT OF BOX - 4.1.2
N511OUEEMF1 - 1st update
N511OUEEMF2 - 2nd udate
N511OUEEMI1 - 3rd update. - 4,2.2
That's the progression of the updates the last was the biggest and took awhile to download.
Hate to say this but did you do a factory reset then try checking for updstes?
Sent from my GT-N5110 using XDA Premium 4 mobile app
gramps50 said:
If I do that I do have the options you mentioned.
Mine had N511OUEDMD1 OUT OF BOX - 4.1.2
N511OUEEMF1 - 1st update
N511OUEEMF2 - 2nd udate
N511OUEEMI1 - 3rd update. - 4,2.2
That's the progression of the updates the last was the biggest and took awhile to download.
Hate to say this but did you do a factory reset then try checking for updstes?
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your help. Mine came like this from the factory, brand new. I did try the factory reset, unfortunately after setting it up one time and having to do it all again with no benefit. The problem is the build and the reset only reinstalled the same build, I didn't think it would help but did it anyway, just to be able to say I tried that already. Mine was obviously built with a build that was not the final product. Now I just want to figure out how to get updated to the right one so I can get future updates.
Glad you found the keyboard options.
Sorry I'm out of ideas other than root and a different ROM but that is pretty extreme.
How long have you had it? Amazon customer support is top notch with my dealings. Maybe the will send you another one. Something is definitly not right with yours. I can send you a screenshot if you need it to make your case.
Was yours brand new or a refurbished?
Sent from my GT-N5110 using XDA Premium 4 mobile app
gramps50 said:
Sorry I'm out of ideas other than root and a different ROM but that is pretty extreme.
How long have you had it? Amazon customer support is top notch with my dealings. Maybe the will send you another one. Something is definitly not right with yours. I can send you a screenshot if you need it to make your case.
Was yours brand new or a refurbished?
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine was brand new. I didn't return it to Amazon because I figured the replacement would probably come out of the same shipment this one came from and it would have been built the same. It's now past the 30 day return period, I'll have to wait for samsung to come up with a resolution. Thanks for your help.
Which version will get kitkat?
danierakes said:
Which version will get kitkat?
Click to expand...
Click to collapse
7,8,10.1 versions. samsung didn't specified it, so each version will get kit kat
danierakes said:
Which version will get kitkat?
Click to expand...
Click to collapse
I noticed this on Sprint's RDF feed for their devices:
Code:
<prf:SoftwareNumber>T217SVPUBNC9</prf:SoftwareNumber>
<prf: OSVersion>4.4.2</prf: OSVersion>
So it appears that the T217S will get 4.4 in the next couple of months.
I think only u.s version will get kitkat
Sent from my SM-T211 using XDA Premium 4 mobile app
For me it's been a while away from the non iphone scene, I happened to wonder if I could upgrade my Tab3 7" today and was reading plenty of news about it being available soon (from articles posted in February). A quick poke around and it seems that it's not released yet and I figure I may as well ask since I don't know.
What's the release schedule around these things usually like? IE how long from "announced" to actually available?
Is the firmware for Tab devices geo-specific? IE is the Australian launch different to the US etc?
(I understand for the phones it's likely to be very carrier dependant)
I think that's all for now.
The_Hawk said:
For me it's been a while away from the non iphone scene, I happened to wonder if I could upgrade my Tab3 7" today and was reading plenty of news about it being available soon (from articles posted in February). A quick poke around and it seems that it's not released yet and I figure I may as well ask since I don't know.
What's the release schedule around these things usually like? IE how long from "announced" to actually available?
Is the firmware for Tab devices geo-specific? IE is the Australian launch different to the US etc?
(I understand for the phones it's likely to be very carrier dependant)
I think that's all for now.
Click to expand...
Click to collapse
If you have a Sprint Tab 3 7.0, then expect an update somewhere between now and two months. That is just a guess but that is how firmware for my Galaxy S3 has worked. Sprint updates the RDF feed and then about two months later it gets released.
For other Tab 3's, no idea.
The_Hawk said:
For me it's been a while away from the non iphone scene, I happened to wonder if I could upgrade my Tab3 7" today and was reading plenty of news about it being available soon (from articles posted in February). A quick poke around and it seems that it's not released yet and I figure I may as well ask since I don't know.
What's the release schedule around these things usually like? IE how long from "announced" to actually available?
Is the firmware for Tab devices geo-specific? IE is the Australian launch different to the US etc?
(I understand for the phones it's likely to be very carrier dependant)
I think that's all for now.
Click to expand...
Click to collapse
Samsung is notorious for being one of the worst manufactures out there when it comes to updating their budget products. I wouldn't hold my breath on a April release, I expect the Tab 4 to be available for purchase before you'll see it. The Tab 3 7" will also probably be the last one to get it and will most likely be the last major update you will ever get, I would bet money on it. I'm actually surprised Samsung is even updating the Tab 3 7" as their track record for releasing new Android versions for their cheaper models is not good. Yes, the update is carrier specific for the LTE models and won't see the light of day for at least a month or two after the WiFi models are updated, if at all.
In the future I would stay away from Samsung's budget line, it's already been a year since version 4.3 was released without it ever reaching the Tab 3 line and now almost 6 months and counting for 4.4.2.
To be fair I only got this device to run torque pro in the car (which is does just fine). As an appliance it's great! Now I'm just tinkering because I'm bored
Although I'm also temped to trade in the iPhone for an android based phone and while I understand it's low powered this was going to be a taste of the new OS I'd be getting.
i bought tab 3 2100 since i needed a 7 inch tab with phone capability, my first choice was any google tab but there is no phone capability in them so therefore i bought it.. and i think Samsung wont give kitkat update unless they release tab 4 with kitkat ... this is their way of making money !
Do you think the tab 3 would get lollipop?
Officially? Doubt it for Tab 3, the Tab 4's might.
Unofficially? I hope so... fingers crossed...
they should
Samsung provides support fot devices two years after their release, tqb 3 was launched on july 2013, so we should be getting the update
KingUsman said:
Do you think the tab 3 would get lollipop?
Click to expand...
Click to collapse
Samsung probably won't release Lollipop for the Tab 3. They might, but based off of Samsung's history with devices -- especially lower end devices -- I would say probably not. I was actually surprised to see Samsung update the T210R to Android 4.4.2. I don't think they will do any more updates.
As for community porting, it is a possibility. However, it seems to be moving slowly. Your best bet here is to help that effort by testing or writing code or filling in random bits of information.
Speaking as someone who is trying to port Cyanogenmod to the Tab 3 (7.0), its a little harder than it looks. That said, I haven't spent time on it recently, so YMMV.
I think that Gr9nole has done a fair job with the porting work, but I haven't been able to get his stuff working with Cyanogenmod. It might be that I'm using an unsupported version of Java. Even with Lollipop, my version of java is not supported (Java 1.8). And I don't really feel like installing Java 1.7.
Nope unless some brave chap will build it from source. If we are lucky it might be on AOKP or Cyanogenmod
I have a TAB 3 10" stock, but I barely use it, since it is so laggy. Is there any ROM or MOD that could make it faster?
I really don't think anyone will build from source cm 11 development Is taking a while at least that should be ready for this tab. May not get lollipop
we can only hope. like was said i remember sammy saying two years was the update period. i would think companies like sprint and att and tmobile who are still giving these away for free might help us. they should want the newest os to help push them. tmobile on the 7in. got 4.4.4 i am on sprint 7in which is still on 4.4.2 but there was a small update recently. so hopefully development is still going.
Erm..... no I think lollipop won't be on Galaxy Tab 3 devices since they closed source unless someone do it by scratch.
Hello all, I decided to pick up a Pixel C and upgrade from my Nexus 10 since there was a developer sale today! I'm pretty excited and I came over to this section to see all the cool roms being made for the Pixel C and I must say I'm disappointed. Don't get me wrong, I appreciate the ROM developers (running Pure Nexus on my 6P) and I just thought I would see the same ROM support for the Pixel C.
Anyway, where is all the custom ROM support? Where is the official TWRP release? I went through and read the threads and I feel like I'm missing something and there is a reason there aren't any custom ROMs or official TWRP support.
vanydotk said:
Hello all, I decided to pick up a Pixel C and upgrade from my Nexus 10 since there was a developer sale today! I'm pretty excited and I came over to this section to see all the cool roms being made for the Pixel C and I must say I'm disappointed. Don't get me wrong, I appreciate the ROM developers (running Pure Nexus on my 6P) and I just thought I would see the same ROM support for the Pixel C.
Anyway, where is all the custom ROM support? Where is the official TWRP release? I went through and read the threads and I feel like I'm missing something and there is a reason there aren't any custom ROMs or official TWRP support.
Click to expand...
Click to collapse
I think there are a few reasons for this. One being (at least I believe) that this tablet doesn't appear to have been well received. The hefty price tag, along with the seemingly rushed (read: buggy) attempt at slapping Android OS onto a device meant to run ChromeOS from it's inception, may have affected sales. The other reason I believe relates to the previous sentence. The software on the Pixel C is some sort of amalgamation of Android and ChromeOS. From what I've gathered from the generous devs such as cheep5k8, this device is pretty much all ChromeOS up until it boots the actual OS, which is then Android. I would imagine that makes it a pain for devs to develop for it. Even chainfire said something to the effect of it wasn't worth his time because he would have to spend a lot of time adapting everything to be compatible with ChromeOS.
Now that being said, I picked one up today as well during the "developer sale" to replace my Nexus 10 just like you. However, I am perfectly content with the stock/rooted OS, as that's what I'm running on my 6P. I put "developer sale" in quotes because I'm not entirely sure the release of the Android N preview is the reason. Going back to my first speculation on why there aren't many devs, I don't believe they've moved as many units as they would've liked. So I kind of see this as an act of (for lack of a better term) desperation to move some units. But I'm okay with that. I've been waiting for Google to release another 10" tablet to replace my N10 for a good while now. With no other 10" tablet in sight from them (there is rumored to be another 7" unveiled at I/O) anytime soon, I figured now would be a great time to jump on this. I'm totally stoked that I was able to snag a 64GB version for $450 instead of $600. Can't wait for it to be delivered.
I as well was wondering this not because I want to use roms from other developers perse, but I like slimmed down roms over stock android.
I gave my son my ipad 2 and i needed a replacement for taking notes in class, work and then reading comics, books and watching movies in bed. Ordered the 32GB + Folio keyboard.
Im sure it is just a matter of time before the roms and official TWRP show up, like nearly all other devices. Especially now with the "dev sale". Might have a few more steps vs installing on a regular nexus though. We shall see. Til then im happy with stock android root.
Tablets never really have (m)any ROMs available, this one is specifically difficult since it's Android in a Chromebook's body.
Sent from my Pixel C using Tapatalk
I took the plunge last night after seeing the sale. I was surprised to actually get a code since I'm not a 'developer' by most standards. Anyways, I'm surprisingly leaning towards not using a ROM on this device and just running the kernel that's available, and doing the aesthetic and user-friendliness mods that I usually rely on ROMS for by way of Xposed. Seriously, the only reason I use a custom ROM on my Nexus 10 is to get the softkeys in a place where my thumbs can reach them, and since that's been handled natively in the Pixel C, I don't really see a need for a ROM.
Not that I wouldn't flash one if someone made something really impressive.
BaristaBot said:
I took the plunge last night after seeing the sale. I was surprised to actually get a code since I'm not a 'developer' by most standards. Anyways, I'm surprisingly leaning towards not using a ROM on this device and just running the kernel that's available, and doing the aesthetic and user-friendliness mods that I usually rely on ROMS for by way of Xposed. Seriously, the only reason I use a custom ROM on my Nexus 10 is to get the softkeys in a place where my thumbs can reach them, and since that's been handled natively in the Pixel C, I don't really see a need for a ROM.
Not that I wouldn't flash one if someone made something really impressive.
Click to expand...
Click to collapse
+1 Root access is the key element for me. While I like the customizations, I can find other ways to get them. For example, it would be nice to have the advanced boot features add to the power button, but I can easily get this with an app.
I think we just need good kernels
I've been given my brother's old phone, a Galaxy S4 Mini SCH-I435 Verizon running 4.2.2, and wanted to see if there was any development at all happening for this specific variant of the S4 Mini. it shares the same hardware as the serranoltexx variants, but I haven't found conclusive proof of this particular model having any sort of recovery or custom ROMs. I've rooted the phone and disabled KNOX just fine, I just need to know where I'm supposed to look from here.
I have a Moto Droid Razr as my daily running the LineageOS 20171110 14.1 build at the current. this sort of thing isn't new to me, I'm just reaching out for possible definitive answers to this plight I'm in. 4.4.2 is *not* acceptable to be using on a phone in this day and age. Has anyone ever actually gotten one of these to work properly with the serranoltexx ROMs? I know they share the same hardware, but I'm more worried about bricking the phone than I was doing it with the Razr since that has endless information about it out there, yet the I435 information, if any, is flooded by model name for the international LTE variant of the same base hardware.
Thanks in advance for any info anyone may know.
An edit: I've found actual proof that the bootloader is locked. the S4 from Verizon and AT&T also had this issue, and it turns out that the developer of Safestrap for my own daily-driver Razr, @Hashcode, also made one for the Verizon S4 non-mini. This excites me, yet pains me, as I don't think the two are hardware-compatible, meaning one would have to be made up somehow for this phone. Sadly, I think interest in the Verizon variant of this phone has dwindled to nothing. I'd love to have an AMOLED LineageOS device available to me that actually has more than a gig of RAM.
galaxy-s4-mini/general/confirmed-rom-sch-i435l-i435-to-i435l-t3548206
There are plenty r890/i435l boards on sale over at eBay. If you look hard, this mod costs 15 bucks +/-
Zz25 said:
galaxy-s4-mini/general/confirmed-rom-sch-i435l-i435-to-i435l-t3548206
There are plenty r890/i435l boards on sale over at eBay. If you look hard, this mod costs 15 bucks +/-
Click to expand...
Click to collapse
Could you explain this for me?
I too have a SCH-i425 that I've been using since it was released. For the last year or so I've been using it exclusively to accept Square payments but recently Square changed their app so it will not work on pre-android 5.0 versions. My phone is 4.4.2. I'm hoping to upgrade it to 5.0 so I can continue using it as I've been otherwise I have to buy a new phone which I really, really, do not want to do.
Thanks so much!