Do you believe that the thread of oppo find 7 should separated in two: oppo find 7 and oppo find 7a? Do you believe that there will be need for this when the roms start to come out?
purplexed9 said:
Do you believe that the thread of oppo find 7 should separated in two: oppo find 7 and oppo find 7a? Do you believe that there will be need for this when the roms start to come out?
Click to expand...
Click to collapse
Makes sense to me.
I don't think there will be a need. It is sounding like the same rom will work for both and they come with the same software. Outside of screen calibration and impressions there is nothing much to make into a separate section as what applies to one applies to all. Unless of course future QHD owners aren't wanting to soil themselves by associating with the unfortunate vanilla 7A owners, that certainly calls for a new section. lol
No way will the same ROM work with all 4 versions of the F7. Just between the 7/7A there's 2 different processors. Maybe that could be settled with just a different kernel but I doubt it.
People are already using the same rom on two variants of the 7A and their tech guru is claiming the same rom with an auto detect could work for both the 7 and 7A. Tech guru is far from a word that would be used to describe me however. I'm sure entropy or one of the other guys will come along and set us (me) straight. Were it to be the case that different roms were required it would probably be a good idea to split the development section into two although that doesn't seem to be proof against people installing the wrong rom version as I've seen on many other phones.
About 90% of Oppo's deltas between 7 and 7A are handled at runtime by the kernel using a PCB version register.
Oppo's naming conventions are a bit confusing:
Find 7A = find7 (kernel defconfig)
Find 7 = find7wx (kernel defconfig) = Find 7S (kernel comments)
Find 7 OnePlus Edition = find7op (kernel source) = OnePlus One (what OnePlus calls it)
There are a few small things in the kernel that are handled by defconfigs instead of runtime - none of us have looked to see if these can be all switched to runtime because we don't have FHD 7 units yet.
Ideally there will be a common build. Worst case there will be a defconfig delta and 99% of the code will be common and (probably) the end result will be a common thread for omni (I hope...) Kind of like if I bothered to create a thread for galaxys2-family devices for Omni, I'd probably just create a unified one for I9100/I777/N7000 at this point. (maybe not N7000 but def. I777/I9100)
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Hellscythe said:
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Click to expand...
Click to collapse
Still, create a different f7 variant under the main f7 thread. As I have written, separate the devices of the thread, not create a completely new thread.
Sent from my P6-U06 using xda app-developers app
Hellscythe said:
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Click to expand...
Click to collapse
Um what? Every single carrier variant of the GS4 was given its own entire forum (not just an Exynos/Qcom split). (in retrospect probably a bad idea, but not surprising given Samsung's prior track record)
Also, "thread" is probably not the appropriate term for what the OP was asking.
Entropy512 said:
Find 7A = find7 (kernel defconfig)
Find 7 = find7wx (kernel defconfig) = Find 7S (kernel comments)
Find 7 OnePlus Edition = find7op (kernel source) = OnePlus One (what OnePlus calls it)
777/I9100)
Click to expand...
Click to collapse
Is the hardware in the OnePlus One and the Find 7 really that similar? Or was this said partly tongue-in-cheek?
bobbarker2 said:
Is the hardware in the OnePlus One and the Find 7 really that similar? Or was this said partly tongue-in-cheek?
Click to expand...
Click to collapse
It is.
Between OnePlus' relation with Oppo, the documented specifications, etc. - Pretty much every difference in the defconfigs/source for the two devices corresponds to the few documented differences in specs between the two devices.
The OnePlus One is a Find 7a with the following tweaks:
1) Nonremovable battery (kernel change: battery authentication disabled)
2) A PN65T instead of PN544 (kernel change: PN65 support in the NFC driver. The PN65 is pointless now that Google has sunsetted hardware SE support)
3) RGB LED instead of the blue-only Skyline (kernel change: different LED driver)
4) Left/right "mirror" reversal. (power button on right of OnePlus, left for F7a, etc.) Kernel change: none
5) MSM8974AC instead of MSM8974AB (kernel change: none, handled automatically at runtime)
farfromovin said:
No way will the same ROM work with all 4 versions of the F7. Just between the 7/7A there's 2 different processors. Maybe that could be settled with just a different kernel but I doubt it.
Click to expand...
Click to collapse
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
krabman said:
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
Click to expand...
Click to collapse
I saw that and stand corrected. You gotta cut me a little slack, coming from a Samsung background where every single variant, along with basebands, cause huge issues. Glad to see it done simple from Oppo.
krabman said:
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
Click to expand...
Click to collapse
could also be the software baseband compatible with both versions of the hardware modem
(nexus 5 US and int'l phones use the same software modem, though supporting different LTE bands)
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
Entropy512 said:
It is.
Between OnePlus' relation with Oppo, the documented specifications, etc. - Pretty much every difference in the defconfigs/source for the two devices corresponds to the few documented differences in specs between the two devices.
The OnePlus One is a Find 7a with the following tweaks:
1) Nonremovable battery (kernel change: battery authentication disabled)
2) A PN65T instead of PN544 (kernel change: PN65 support in the NFC driver. The PN65 is pointless now that Google has sunsetted hardware SE support)
3) RGB LED instead of the blue-only Skyline (kernel change: different LED driver)
4) Left/right "mirror" reversal. (power button on right of OnePlus, left for F7a, etc.) Kernel change: none
5) MSM8974AC instead of MSM8974AB (kernel change: none, handled automatically at runtime)
Click to expand...
Click to collapse
So after things get rolling: Find7, Find7a, and OPO owners should be able to flash roms for all devices, followed up by the correct kernel?
Yes. That's pretty much the expected outcome.
Sent from my X9006 using Tapatalk
farfromovin said:
So after things get rolling: Find7, Find7a, and OPO owners should be able to flash roms for all devices, followed up by the correct kernel?
Click to expand...
Click to collapse
If we can't do a unified kernel, we'll be doing separate complete builds for both. But you could expect in that case we'll have something similar to the Samsung Galaxy S2 family, where the I9100, I777, and N7000 all inherit a "common" device tree that contains 95%+ of the stuff for each device.
Related
www.muktware.com/2013/12/cyanogenmod-source-code-samsung-galaxy-note-3-now-available/18304
The sources are also available for various versions of Note 3. With similar hardware, would this make porting CM for our tablet any easier?
Srikar_NBK said:
www.muktware.com/2013/12/cyanogenmod-source-code-samsung-galaxy-note-3-now-available/18304
The sources are also available for various versions of Note 3. With similar hardware, would this make porting CM for our tablet any easier?
Click to expand...
Click to collapse
I'd love me some CM on this tablet.
Srikar_NBK said:
www.muktware.com/2013/12/cyanogenmod-source-code-samsung-galaxy-note-3-now-available/18304
The sources are also available for various versions of Note 3. With similar hardware, would this make porting CM for our tablet any easier?
Click to expand...
Click to collapse
I would imagine so, but isn't the note a snapdragon device? I know ours uses both depending on the model, but a lot of the devs hate exynos.
tkoreaper said:
I would imagine so, but isn't the note a snapdragon device? I know ours uses both depending on the model, but a lot of the devs hate exynos.
Click to expand...
Click to collapse
Note 3 international version uses Exynos 5420, the same as P600 and 601.
https://en.wikipedia.org/wiki/Exynos#List_of_Exynos_SoCs
And from the Muktware article, CM supports Note 3 International version
Plan to buy Oppo Find 7 but curious about custom rom. I couldn't find Find7 Rom so can we use the same custom rom? Thank you
none of the developers do have got a find7 from oppo.
as far as I know the available custom roms do not work on find7 due missing screen compatibility
Gesendet von meinem Find7a mit Tapatalk
Technically it is doable to have one ROM for both but other than color os no one supports it yet.
That will stay like that until one of the developers gets the time and the required device.
MrColdbird said:
Technically it is doable to have one ROM for both but other than color os no one supports it yet.
That will stay like that until one of the developers gets the time and the required device.
Click to expand...
Click to collapse
Yup. I would expect it to only take an evening or two worth of work for someone who knows what they're doing and actually has the device.
I'm not sure if I'll be receiving a QHD Find7 from Oppo, but someone who has the required skills most definitely will. It's primarily an issue of fixing up some things I chose to leave for later in my bringup efforts.
Specfically - https://github.com/omnirom/android_...mmit/59223a3e64565bcfa13bfd3b58fc676128d02ca7 fixed display initialization for the 7a but I did NOT do the same for the 7 because I didn't have one. That's the primary issue with the 7 currently.
Specifically you'll notice that nothing below the else{} case for dual DSI (Find 7S aka Find 7 QHD) was changed (near the bottom of the commit linked above)
I believe that developers had a difficult time now to support Quad HD smartphone because technically its a bit anew for them. Look to the Original Development of LG G3, there still no available rom or even custom recovery for that, same as Oppo Find 7. Just wait for the devs to learn new things and thanks them for their best efforts to support the android community.
Just out of curiosity, Why is their more rom options and development for the 7a than the 7? I am an owner of the us version find 7 and thought maybe their would be just as much development for the 7 if not more considering the higher specs.
Just curious
May be because of the higher price? Devs might not be able to afford the high-end version?
My 2 cents
also, 7a was on the market approx 2'months before 7
Also the qhd screen and not standard and many apps have problem working on it.
In fact there isn't really a lot more rom for the 7a than the qhd version since almost all of the rom are supported by both devices ! (maybe a few older ones)
It's just that the forum form isn't adapted for this kind of rom that goes on he find 7a and the find 7, so devellopers share their work in the find 7a development section.
It might seem like that, but I think there is a lack of ROMs for the Find7/7a period. However, most 7a ROMs will work on the 7
rgreene1971 said:
Just out of curiosity, Why is their more rom options and development for the 7a than the 7? I am an owner of the us version find 7 and thought maybe their would be just as much development for the 7 if not more considering the higher specs.
Just curious
Click to expand...
Click to collapse
Most of us don't want to maintain two separate threads for what is effectively the same device.
I am not aware of a single project that doesn't support 7a and 7s with a single build that works on both. I recommended that the moderators not split out the forums but they did it anyway. 7s took a bit longer since it was released 2-3 months later and dual-DSI is something no one had worked with before, but every project I know of has supported the 7s since mid-July. But none of us want to create a second thread in the 7s forum and just kept on using our threads in the 7a forums.
Hi,
I would be interested if we can expect Cyanogenmod for this device? Just asking, because I am very interested in it and could not find any hint.
Thank you!
Florian
+1 here, I think yes because hardware is very similar with the 8.4 inch edition !
haris-100 said:
+1 here, I think yes because hardware is very similar with the 8.4 inch edition !
Click to expand...
Click to collapse
It's NOT.
8.4 is the only recent Samsung Tab to have a Qualcomm Snapdragon 800, which makes it way more similar to other Qualcomm-equipped phones, including the Nexus 5. This makes development more or less easier.
Other Tabs, including the T520, use Samsung's Exynos, which is neither friendly to devs nor well documented. Development for any Exynos device usually takes much longer than Qualcomm.
Rest assured that CM13 currently still isn't complete, and even if you upgraded chances are you will find bugs and removed functions you aren't satisfied with.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
crpalmer, who we all owe for getting cm12 and12.1 onto our devices, has said he plans to do it when he gets time.
Just be patient, it's far more love than Samsung have shown.
b1g1an said:
crpalmer, who we all owe for getting cm12 and12.1 onto our devices, has said he plans to do it when he gets time.
Just be patient, it's far more love than Samsung have shown.
Click to expand...
Click to collapse
Right :good:
AndyYan said:
It's NOT.
8.4 is the only recent Samsung Tab to have a Qualcomm Snapdragon 800, which makes it way more similar to other Qualcomm-equipped phones, including the Nexus 5. This makes development more or less easier.
Other Tabs, including the T520, use Samsung's Exynos, which is neither friendly to devs nor well documented. Development for any Exynos device usually takes much longer than Qualcomm.
Rest assured that CM13 currently still isn't complete, and even if you upgraded chances are you will find bugs and removed functions you aren't satisfied with.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
Sorry, my mistake !
Is right
Very properly ! I agree with LOL...
[6.0.x|SM-T520|BETA] Unofficial CyanogenMod 13.0 for the Tab Pro 10.1 (picassowifi)
http://forum.xda-developers.com/gal...-xsm-t520beta-unofficial-cyanogenmod-t3372507
1.I am in searching of a new phone, and i stopped here on the oneplus 3 forum. I saw there are more models (a3000, a3003 dont really know more) around , so i dont know which one to buy?
And i just want to know if i can flash anycustom rom i want on any model of the Oneplus3.
2.Is worth the extra $ for oneplus 3t?
3.Which one has better rom development on xda ONEPLUS 3 or 3T ?
A3000 is American/Chinese, A3003 is EU/worldwide.
All ROMs can be flashed on all model numbers.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
A3 more000 is American/Chinese, A3003 is EU/worldwide.
All ROMs can be flashed on all model numbers.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
What about 2nd and 3rd questions. Any ideea?
RootNightmareX said:
What about 2nd and 3rd questions. Any ideea?
Click to expand...
Click to collapse
2. That comes down to personal choice. I'd say the original 3 has slightly better price/performance - 3T is indeed better on paper, but those differences are almost negligible in real life. That said, I may be a bit biased towards the 3 [emoji14]
Worth mentioning that 3 is not being produced any more so it may be hard to get now.
3. At the moment the OnePlus 3 has better dev support. But 3T is catching up. And in future they will probably have the same support - literally the same ROMs. We already know that kernels can be made to work on both models and AFAIK OnePlus is working on a unified ROM for both devices (which means that custom ROMs should also be able to work on both).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
2. That comes down to personal choice. I'd say the original 3 has slightly better price/performance - 3T is indeed better on paper, but those differences are almost negligible in real life. That said, I may be a bit biased towards the 3 [emoji14]
Worth mentioning that 3 is not being produced any more so it may be hard wto get now.
3. At the moment the OnePlus 3 has better dev support. But 3T is catching up. And in future they will probably have the same support - literally the same ROMs. We already know that kernels can be made to work on both models and AFAIK OnePlus is working on a unified ROM for both devices (which means that custom ROMs should also be able to work on both).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
How it is possible for a kernel/rom to work on 2 different chipsets 820/821
RootNightmareX said:
How it is possible for a kernel/rom to work on 2 different chipsets 820/821
Click to expand...
Click to collapse
I'm way too lazy to look into it ... better ask some developer [emoji1]
I guess it detects the chipset and selects the profile accordingly.
Probably not possible to do with completely different chipsets, but 820 and 821 are practically the same, just have different clocks (and probably voltages).
Check out blu_spark kernel by eng.stk in 3T development thread. That one works on Marshmallow ROMs on both devices.
Sent from my OnePlus 3 using Tapatalk
RootNightmareX said:
How it is possible for a kernel/rom to work on 2 different chipsets 820/821
Click to expand...
Click to collapse
https://www.xda-developers.com/sult...rom-approach-on-the-oneplus-3-and-oneplus-3t/
Here u go
It's simple.
If you want big development you choose 3. For 3t development it's small. I don't think many users/developers will get rid of 3 to buy 3t.
Update: we already have unified ROMs also (for example Resurrection Remix 5.8.0). So that proves that in the future both devices will share development.
Sent from my OnePlus 3 using Tapatalk
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
null0seven said:
It's simple.
If you want big development you choose 3. For 3t development it's small. I don't think many users/developers will get rid of 3 to buy 3t.
Click to expand...
Click to collapse
Check last few comments ... With unified ROMs and kernels the development is essentially the same.
Sent from my OnePlus 3 using Tapatalk