I have a P3113. After some reading, and seeing ROM availability, I'm gathering that the P3100 and P3113 are NOT the same, and a ROM for one is not a ROM for both. Need a specific P3113 ROM.
Or? I am also seeing that some ROMs specify they are for the P3110 - but will work on the P3113. So it appears the P3110/P3113 are in the same family. I'm not certain, as sometimes companies have the same hardware, but specify one model # for use in one country/continent, and another model # for use in another country/continent.
So - my question is - are ROMs for the P3110 also "good to go" for the P3113? Or are there still some differences that one should ALWAYS look for a specific ROM for the P3113?
tundrwd said:
I have a P3113. After some reading, and seeing ROM availability, I'm gathering that the P3100 and P3113 are NOT the same, and a ROM for one is not a ROM for both. Need a specific P3113 ROM.
Or? I am also seeing that some ROMs specify they are for the P3110 - but will work on the P3113. So it appears the P3110/P3113 are in the same family. I'm not certain, as sometimes companies have the same hardware, but specify one model # for use in one country/continent, and another model # for use in another country/continent.
So - my question is - are ROMs for the P3110 also "good to go" for the P3113? Or are there still some differences that one should ALWAYS look for a specific ROM for the P3113?
Click to expand...
Click to collapse
Before saying about the firmware compatability I am gonna introduce these 3 devices
P3100 - 3G +WIFI Version (has reciever to make phone calls + proximity sensor)
P3110 - WIFI only Version
P3113 - WIFI + IR BLASTER Version
firmware compitability:
P3100: only roms meant for 3100 will work on this beacause it is the only tab 2 7.0 device with sim slot and no other roms wouldn't suits it completely
P3110 : roms for p3100 (mic doesn't work properly ) and 3113 (think so ) will suits it
P3113 : roms with p3100( mic bug) and 3110( since no aosp roms has IR blaster support( but new cm 10.2 have IR support) will suits it and 3110 and 3113 has same cm roms
Hope tou understand this
P3100 has GSM
P3110/3 is wifi only. 3113 is IR. You can acutally use any ROM on any of the devices. Only problems are if you use a P3100 ROM on P3110/3 then the mic wont work. And vice versa.
Sent from my LG-P690b using Tapatalk 2
openmatrix said:
Before saying about the firmware compatability I am gonna introduce these 3 devices
P3100 - 3G +WIFI Version (has reciever to make phone calls + proximity sensor)
P3110 - WIFI only Version
P3113 - WIFI + IR BLASTER Version
firmware compitability:
P3100: only roms meant for 3100 will work on this beacause it is the only tab 2 7.0 device with sim slot and no other roms wouldn't suits it completely
P3110 : roms for p3100 (mic doesn't work properly ) and 3113 (think so ) will suits it
P3113 : roms with p3100( mic bug) and 3110( since no aosp roms has IR blaster support( but new cm 10.2 have IR support) will suits it and 3110 and 3113 has same cm roms
Hope tou understand this
Click to expand...
Click to collapse
Yup. What I find interesting is that while it's the same product "family", it isn't just the addition of features (GSM/IR/etc.) that differentiates them. I hadn't heard that a 3100 ROM would cause issues with the mic in a 311x series. And that's where the question comes in. There's no sticky/wiki/doc I have yet found that really states what the differences are - in terms of applying custom ROMs. I've seen many posts of those who jump into applying a 3100 ROM to a 311x, and then run into issues. So it's not clear if they are issues due to hardware differences, and the ROM support, or the person didn't do it correctly, or the fates simply caught up with you on the 1000th reflashing of a ROM.
It would be nice if some of the users/devs (WHO ACTUALLY KNOW SOMETHING) would set up a sticky for the device(s) they know - build that up to explain these issues, and a bit of why. That might reduce the number of "I installed ROM xxxxx, and I've bricked my unit", and the litany of "you didn't wipe cache/dalvik/whatever", and noobz having to jump in with "I fixed it by doing yyyyy", or "I installed ROM brand 'Z' and had no issue". Geez, wading through dozens/hundreds of posts to glean what really should be quite frankly put in a sticky/wiki would eliminate 2/3s of the unnecessary posts on this site, and probably 20-30% of the bricked units. I haven't even really found anything that really says what the differences are between stock/Cyanogen/AOSP/etc. for the same, basic version. I'd like to review a feature list, instead of playing Russian roulette installing ROMs and hoping and praying I don't brick a unit just trying to see what's in a ROM.
There's got to be some limit on how many times you can flash a ROM before it starts getting flaky. And how many have simply bricked their units because they flashed it one too many times? Would be nice if some of them would keep track of how many times they've flashed their ROM, and some idea could be built up of just how many times can you get away with before the unit decides to flake on you.
So, for the meantime, I'll stay stock, rooted, and with a recovery module that allows me to make backups, and gradually de-crappify my unit (of the vendor pre-installed junk), so I can hopefully avoid problems.
Related
Hi everybody, well, as many of you may know, here in Latin America (Brazil, Argentina, Chile) we have a specific Galaxy S model, the i9000B. Not too many changes from the T model, and Samsung just published the kernel diffs from the standard i9000 kernel source. Our problem is that we have no official ROM other than the old, slow and boring 2.1 Eclair. Well... there`s a leaked 2.2 ROM but what everybody here wants is to take advantage of all the great mods floating around but of course those can not be flashed in our B devices.
The question I would like to make is "WHY???". Of course the Kernel shipped on those ROMS might not be compatible, but as I said before we have access B sources so we could provide our own compiled kernels and mix them with the internation ROM which are of course binary compatible since the underlying harware is almost the same... but I guess that would not probe to be sufficient! What parts of the android platform could be device specific aside from kernel??? I heard something about the modem thing being specific to the geographic area...
Thnx in adv!
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
just test if reply is working.. because i wroth you a big tutorial and i submited get a frustation error msg
---------- Post added at 02:29 AM ---------- Previous post was at 02:02 AM ----------
iSuperAwesome said:
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
Click to expand...
Click to collapse
Sorry to not get this Tutorial as elaborated as I wroth before but I get flustered by getting a error when submit
-----------------------------------------------------------------------------------------------------------------------------------------
I use a windows software call SamFirm do download VERY FAST the lastest original firmware from Samsung servers.
Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Note 1: You need to specify the “Region/Country” of the Firmware. For that, you can look at some sites that have the same Firmware (Links below). But don’t download from this sites, because is VERY SLOW.
http://samsung-updates.com/device/?id=SM-T230NU
http://www.sammobile.com/firmwares/database/SM-T230NU/
http://www.androidayos.com/galaxy-tab-4-stock-firmware/
http://forum.xda-developers.com/tab-4/general/links-stock-galaxy-tab-4-firmware-t3013128
Note 2: The region “BNN” is for the Samsung galaxy Tab 4 7.0 Nook Edition
How to use SamFirm:
1 - Model = SM-T230NU <-----------------(Ex: Samsung Galaxy Tab 4 Nook 7.0" = SM-T230NU)
2 - Region = BNN <------------------------(Ex: “BNN” for Nook Edition)
3 - Auto = ON
4 - Click "Check Updates", if firmware for the particular region exist you see a msg in Log Window below
5 - Check CRC32 = ON <--------------------- Check is the file is intact
6 - Decrypt automatically = ON <----------- Decrypt file after download
7 - Click "Download” and choose the destination folder
8 – Extract the .md5 using 7-Zip (Nota: WinRAR get error sometimes)
9 – Done, now you can use Odin3 to upgrade you firmware
Cheers
iSuperAwesome said:
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
Click to expand...
Click to collapse
It sounds like you were asking about custom ROMs, as opposed to keeping official firmware up to date which is what BXA is talking about. For the record, instead of installing an extra app just to keep up to date on official firmware releases, you can always check my threads which I keep up to date on official firmware releases for all Tab 4 variants:
--Official Tab 4 KitKat Firmware thread
--Official Tab 4 Lollipop Firmware Thread
Assuming you were inquiring about custom ROMs, below is a list of the most popular and/or well-maintained ROMs that will work for your device (pro-tip, even if the ROM says it's only for the SM-T230, it will work on your device, but you probably will lose IR blaster functionality). Before you ask, there are no viable CyanogenMod-based or even AOSP-based ROMs for this device (or SM-T230). They tried to get CyanogenMod working for your device, but as of right now the available builds either don't boot entirely or boot but have bugs like Wi-Fi not working. I'll link to the thread with the relevant info and downloads, but don't expect much, certainly nothing stable enough for daily use. The list I promised you:
--Acheron ROM (well maintained, popular, great dev to interact with, and even though I don't own your device, my recommended starting point)
--Prism Barebones (unfortunately apparently no-longer maintained, but still a solid, popular ROM by a well-respected dev, a legit alternative to Acheron)
--TranchidaKat (seemed to be gaining in popularity, unfortunately the dev recently took a break from maintenance)
--T230 Smooth ROM (I don't really know much about this ROM, but from what I can tell it seems/seemed reasonably popular)
There are a couple more ROMs I feel reluctant even mentioning, and can't really recommend with any sort of confidence. The first had an OK dev (seemed to be in the up and coming, eager to learn but not experienced stage of being a ROM developer): Octagon ROM
The next ROMs I'm going to mention I can't recommend in good confidence not just they're now slightly out of date, but because they seemed to have a few bugs, but more so the developer doesn't do much to instill my confidence in their knowledge base when it comes to developing ROMs for android. Also they're not really custom ROMs more than they're just the stock ROM with themes and skins applied, as opposed to any real under-the-hood performance improvements: Everything Google ROM; the previous ROM with a Marshmallow skin; and Android 5.0 Lollipop Material Design -{theme}-
Finally the CyanogenMod thread I mentioned, even though as I said, you will be disappointed if you insist on downloading anything to try it out: http://forum.xda-developers.com/tab-4/general/dev-cm12-1-t230-nu-development-thread-t3190971
One last thing before I go, in case you haven't found the custom recovery you need, you have three (although the first two are more recommended) choices: an older version of TWRP which I can guarantee will work: http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Or a newer version of TWRP which should work for your device but I cannot personally guarantee that (click the link that says twrp-3.0.0.0-degas-160207-0212): http://forum.xda-developers.com/tab-4/development/recovery-twrp-2-8-1-0-samsung-galaxy-t2922795
Regarding that newer TWRP, I'm pretty sure I've seen posts confirming it works for your device but I can't recall for sure and I personally installed the first (older version) on a friend's SM-T230NU, so your call. If you have a strong personal preference for CWM as opposed to TWRP, you can try the following recovery, but it's not actively maintained any longer, so be warned. Although to be fair, it works fine as far as I can tell, so again your call: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
thisisapoorusernamechoice said:
It sounds like you were asking about custom ROMs, as opposed to keeping official firmware up to date which is what BXA is talking about. For the record, instead of installing an extra app just to keep up to date on official firmware releases, you can always check my threads which I keep up to date on official firmware releases for all Tab 4 variants:
--Official Tab 4 KitKat Firmware thread
--Official Tab 4 Lollipop Firmware Thread
Assuming you were inquiring about custom ROMs, below is a list of the most popular and/or well-maintained ROMs that will work for your device (pro-tip, even if the ROM says it's only for the SM-T230, it will work on your device, but you probably will lose IR blaster functionality). Before you ask, there are no viable CyanogenMod-based or even AOSP-based ROMs for this device (or SM-T230). They tried to get CyanogenMod working for your device, but as of right now the available builds either don't boot entirely or boot but have bugs like Wi-Fi not working. I'll link to the thread with the relevant info and downloads, but don't expect much, certainly nothing stable enough for daily use. The list I promised you:
--Acheron ROM (well maintained, popular, great dev to interact with, and even though I don't own your device, my recommended starting point)
--Prism Barebones (unfortunately apparently no-longer maintained, but still a solid, popular ROM by a well-respected dev, a legit alternative to Acheron)
--TranchidaKat (seemed to be gaining in popularity, unfortunately the dev recently took a break from maintenance)
--T230 Smooth ROM (I don't really know much about this ROM, but from what I can tell it seems/seemed reasonably popular)
There are a couple more ROMs I feel reluctant even mentioning, and can't really recommend with any sort of confidence. The first had an OK dev (seemed to be in the up and coming, eager to learn but not experienced stage of being a ROM developer): Octagon ROM
The next ROMs I'm going to mention I can't recommend in good confidence not just they're now slightly out of date, but because they seemed to have a few bugs, but more so the developer doesn't do much to instill my confidence in their knowledge base when it comes to developing ROMs for android. Also they're not really custom ROMs more than they're just the stock ROM with themes and skins applied, as opposed to any real under-the-hood performance improvements: Everything Google ROM; the previous ROM with a Marshmallow skin; and Android 5.0 Lollipop Material Design -{theme}-
Finally the CyanogenMod thread I mentioned, even though as I said, you will be disappointed if you insist on downloading anything to try it out: http://forum.xda-developers.com/tab-4/general/dev-cm12-1-t230-nu-development-thread-t3190971
One last thing before I go, in case you haven't found the custom recovery you need, you have three (although the first two are more recommended) choices: an older version of TWRP which I can guarantee will work: http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Or a newer version of TWRP which should work for your device but I cannot personally guarantee that (click the link that says twrp-3.0.0.0-degas-160207-0212): http://forum.xda-developers.com/tab-4/development/recovery-twrp-2-8-1-0-samsung-galaxy-t2922795
Regarding that newer TWRP, I'm pretty sure I've seen posts confirming it works for your device but I can't recall for sure and I personally installed the first (older version) on a friend's SM-T230NU, so your call. If you have a strong personal preference for CWM as opposed to TWRP, you can try the following recovery, but it's not actively maintained any longer, so be warned. Although to be fair, it works fine as far as I can tell, so again your call: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
Click to expand...
Click to collapse
Many thanks for the tips
Btw, your links are great.. and can be downloaded VERY FAST
have a nice day
First of all sorry for my english,and sorry if somebody already created a topic about this,but i cant find a solution.
Im currently running CM12.1 on my GS3 Neo (i9300i) and im experiencing battery drain.Every rom i installed had this issue (CM12,CM12.1 and ResurrectionRemix 5.5.9),i lose about 1% every 1~2 minutes and when charging sometimes it gets stuck at 70% and above,taking forever to charge,but if i remove the battery and put it back on it shows 100%.In stock rom i dont have those issues,is there anything i can do to fix it or is it normal?
Same problem (GT-I9301I) + Low voice while talking in phone with someone.
What version of rom you flashed? I read somewhere that NFC unnecessary files are draining battery, but that was fixed a long time ago with new builds.
cm-12.1-20151225, the latest version of CM12.1 for GS3 Neo,from here: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Also experiencing the low audio while audio recording or Facebook Messenger call,etc
That is not a last build, actually it's very old one.
Try out with last official one:
http://forum.xda-developers.com/galaxy-s3-neo/orig-development/kernel-n1kernel-t3208957
Battery life is not stellar but it's far from bad. Without playing games SOT is around 4.5h+. It changes properly but it's a bit slower than stock in it. It's certainly good enough for day to day usage. Result is with some streaming, lots of browsing, some downloads & cetera. It's a combination of WiFi and cellular usage but still mostly cellular (as it whose on a busy work day for me). So it should fairly represent typical usage scenario.
I was using the latest unofficial version because i didnt know that the official was compatible with my version of the GS3 Neo (i9300i)
I will try flashing the official rom and gonna test it
fernandomjs said:
I was using the latest unofficial version because i didnt know that the official was compatible with my version of the GS3 Neo (i9300i)
I will try flashing the official rom and gonna test it
Click to expand...
Click to collapse
It's a same rom (CM12.1) only build from newer sources along with polished kernel so the same patch for dual sim will work the same as on unofficial. On the CM 12.1 their is no difference between official & unofficial regarding a dual sim variant. Difference will be in the future releases with different, newer Android version's because dual sim variant then really won't be supported. Reason? Nikola doesn't have a GT-i9300i to do a testing & 3rd part tests simply don't qualify as desired quality ones. Hope this explains clearly enough the state how "GT-i9300i dual sim variant is not officially supported" & what that means in presence & in the future if situation doesn't change (eke he gets one as a present or rises enough fonds from donations to buy one).
Zola III said:
It's a same rom (CM12.1) only build from newer sources along with polished kernel so the same patch for dual sim will work the same as on unofficial. On the CM 12.1 their is no difference between official & unofficial regarding a dual sim variant. Difference will be in the future releases with different, newer Android version's because dual sim variant then really won't be supported. Reason? Nikola doesn't have a GT-i9300i to do a testing & 3rd part tests simply don't qualify as desired quality ones. Hope this explains clearly enough the state how "GT-i9300i dual sim variant is not officially supported" & what that means in presence & in the future if situation doesn't change (eke he gets one as a present or rises enough fonds from donations to buy one).
Click to expand...
Click to collapse
I flashed a nightly because on the download page it doesnt show any stable versions. I could not connect to wifi,i dont know if i flashed it wrong or the rom have a problem
It's just you so it's not rom problem. By the way CM12.1 is for the long time in stable, you just use nightly code when compiling it so that you can use very last one.
I dont know if its just my problem,i saw somewhere someone complaining about the wi-fi issue.Also,when i flashed the unofficial rom it had this issue,i could connect to wi-fi normally but sometimes it did not load any page,but turning the wi-fi on and off sometimes fixed it.
I will search more about those issues and try flashing the rom again to see if i can fix it.
Hi all,
I see sometimes that there are unofficial ROMs made of official ROMs such as Paranoid Android, that support devices such as our own before the original ROM creator does.
Now I know nothing about making ROMs, I'm guessing there of course is specific firmware and drivers for our phone as one example, unique to us.
Is it a support question, as in the official makers could support another phone (easily?!), but don't, because they don't have the device to confirm it works fine or may carry a brick risk etc?
How hard is it to make an "unofficial" ROM that supports specific devices features/hardware? Is it a case of merging differnt device firmware with another kernel and testing? (I'm sure some will be mad at my naivety)
Sorry for the newb question.