I want to buy a phone that has proper CM10.1 support. The SGS2 Exynos chip has very poor support and CM does not even want to develop it anymore because of Samsung's lack of support. CM10.1 is very laggy. The OMAP version on the other hand is well supported by CM10.1.
Is the Tegra 3 the same as the Exynos or is it well supported?
Related
So everybody, Which next "Nexus" Chipset do you think will be most developed for? In terms of custom ROMs etc.
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
Ok, I am kind of lost, I am not a Developer, However to me Personally doesn't seem to difficult to be able to take a:laugh: Stock or even Custom Rom already running Great from the Galaxy Tab 3 T311 and have it run the same or even better on the Galaxy Tab 3 T211, I do Understand that theres much more things that should be considered besides the 1" size difference, but other than that both devices run 3g, can someone please enlighten us non kmowers, lol, cause our T211 section is like a GHOST town and would love to see it lite up like 42nd st in Manhattan on Christmas.. Thanks Muchhhhhh....
[email protected] said:
Ok, I am kind of lost, I am not a Developer, However to me Personally doesn't seem to difficult to be able to take a:laugh: Stock or even Custom Rom already running Great from the Galaxy Tab 3 T311 and have it run the same or even better on the Galaxy Tab 3 T211, I do Understand that theres much more things that should be considered besides the 1" size difference, but other than that both devices run 3g, can someone please enlighten us non kmowers, lol, cause our T211 section is like a GHOST town and would love to see it lite up like 42nd st in Manhattan on Christmas.. Thanks Muchhhhhh....
Click to expand...
Click to collapse
It is much more than just the size difference, the Tab3 range all use completely different CPUs and GPUs
Samsung Galaxy Tab 3 7.0
Processor: Marvell Technology Group PXA986
Graphics Adapter: Vivante GC1000+ Dual-Core
Samsung Galaxy Tab 3 8.0
Processor: Samsung Exynos 4212 1.5 GHz
Graphics Adapter: ARM Mali-400 MP4
Samsung Galaxy Tab 3 10.1
Processor: Intel Atom Z2560
Graphics Adapter: PowerVR SGX544
I Know its MUCH more than a size diffrence
I do understand that its more than just a size difference, I Know it has to do with Partitions, Kernels, DPI, CPU, GPU, However these other devices that have had totally different Roms for totally different devices ported into them. from what i have been reading in this forum is that theres a problem porting the Kernel, again i could be wrong. I cant Wait to flash something soon, cause this stock Rom SUCKSS..
lee_w said:
It is much more than just the size difference, the Tab3 range all use completely different CPUs and GPUs
Samsung Galaxy Tab 3 7.0
Processor: Marvell Technology Group PXA986
Graphics Adapter: Vivante GC1000+ Dual-Core
Samsung Galaxy Tab 3 8.0
Processor: Samsung Exynos 4212 1.5 GHz
Graphics Adapter: ARM Mali-400 MP4
Samsung Galaxy Tab 3 10.1
Processor: Intel Atom Z2560
Graphics Adapter: PowerVR SGX544
Click to expand...
Click to collapse
As discussed in an other thread I start here a new topic regarding the overall performance of Android 4.x on Snapdragon S1 MSM7227A SoC design based Samsung devices. This refers for example to the following Samsung phone models:
GT-S7560M
GT-S7560
GT-S7562
GT-S6500
Note, this contains NOT the GT-I8160 (Galaxy Ace 2) phone which is build around an NovaThor SoC design.
Galaxy Mini 2 GT-S6500, CyanogenMod 10.1 (Android 4.2.2 @ kernel 2.6.38.6) build from 20150902
AnTuTu v5.7.3 performance score: 5538, second round 5784, third round 5826
This seems to be 8 to 10 times slower then newest high end class smart phones. Nevertheless the performance of CM10.1 at my Galaxy Mini 2 is absolute adequate. It runs stable, fluid, and has no laggs in normal daily used apps. :good:
Galaxy Trend GT-S7560M
ROM : CyanogenMod 11
Android version : 4.4.4
Build : 11-20141114-UNOFFICIAL-kylessopen
Kernel : 3.0.79
AnTuTu Benchmark v5.7.1 :
6671
7427
7399
Thanks breversa! As expected the GT-S7560M is faster than the GT-S6500, - although not so much as I thought. The difference goes most likely back to the higher CPU clock and the more amount of RAM.
Well, the question is now how many of these AnTuTu points are needed to run run CyanogenMod 11 fluid, adequate and without lags. It can be that the GT-S6500 is just below this limit.
You're welcome.
Why don't you flash CM11 on your device then give back the results of the test ?
breversa said:
You're welcome.
Why don't you flash CM11 on your device then give back the results of the test ?
Click to expand...
Click to collapse
Well, I tried this several times. But with newest ClockworkMod v6.0.5.1, which fixes a grave internal / external storage error, the installation crashes shorty after starting it.
Furthermore, CM11 for the Galaxy Mini 2 is no longer developed, - the original dev leave the project longer time ago. An other dev also quite his CM11 M12 build after he changed the phone. Regarding the Galaxy Mini 2 I think the challenge is just too hard. The problem starts at fundamental things like bad kernel 3.x and driver performance. (These are much less optimized then in older kernel 2.6 versions.)
And, because there exist an awesome CyanogenMod 10.1 build there is no real need for CM11. Really everything is working, including NFC, Camera and Camcorder. The latest release also fixed the Android Stagefright exploit. The only feature that I will miss may be Google Wallet. That requires KitKat 4.4 so far I know.
These are good enough reasons.
Glad I could be of assistance !
Samsung says memory limitations. hmm, why a3 2015 has lollipop ? A3 HAS 1GB RAM. 2 cores not has problems to run lollipop.
Why I'm say worse ? Samsung's all devices, only S4 mini and s3 neo has Snapgragon 400. but s3 neo has 720p display, s4 mini has 540p display.
Yea, great developer edit s3 neo lollipop port rom to had compatible qHD display. but s3 neo has cortex a7, s4 mini has krait 300
But I don't know who is succesfully ported 5.1 to s3 neo. note 3 neo has 720p but has exynos ???
Next device is A3 2015 but it has 64-bit cpu. blablabla...
Possible ?
ets2_volvo said:
Samsung says memory limitations. hmm, why a3 2015 has lollipop ? A3 HAS 1GB RAM. 2 cores not has problems to run lollipop.
Why I'm say worse ? Samsung's all devices, only S4 mini and s3 neo has Snapgragon 400. but s3 neo has 720p display, s4 mini has 540p display.
Yea, great developer edit s3 neo lollipop port rom to had compatible qHD display. but s3 neo has cortex a7, s4 mini has krait 300
But I don't know who is succesfully ported 5.1 to s3 neo. note 3 neo has 720p but has exynos ???
Next device is A3 2015 but it has 64-bit cpu. blablabla...
Possible ?
Click to expand...
Click to collapse
i'm unable to understand devs here in s4 mini section , they dont even try , and not even respond when its about it !
there must be a way to do it , do you know any turo on how to port lollipop to kitkat devices ?
Maybe the only way to do that will be creating from cm sources with an existing ROM with another skin. Time ago, when I got my galaxy ace I tried a ROM that was a jellybean port, that was far from TW 2.X look and feel.
http://forum.xda-developers.com/showpost.php?p=64033422&postcount=225
http://forum.xda-developers.com/showpost.php?p=64035364&postcount=229
http://forum.xda-developers.com/showpost.php?p=64059624&postcount=236
adityapal(adizmayazal) tried it but as far as I know unfortunately he got too many force closes, issues
J2 is worse device than s4 mini. Than J2 has exynos 3. I don't know
http://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-aryamod-port-s7edge-portv6-0-t3416461 everything is possible s4 i9506 with TW 6.01M for us may be dependent on developers
huawei92 said:
http://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-aryamod-port-s7edge-portv6-0-t3416461 everything is possible s4 i9506 with TW 6.01M for us may be dependent on developers
Click to expand...
Click to collapse
I think another good dev port s3 neo's lollipop port cos very similar chipset but comes different gpu blabla...
ets2_volvo said:
I think another good dev port s3 neo's lollipop port cos very similar chipset but comes different gpu blabla...
Click to expand...
Click to collapse
the system of the Samsung TouchWiz and wonderful it would be really nice if by cm code could pull off a 6.0 tw must recreate a kernel using cm code and the operative part of a s5 32bit taking just enough like the Samsung app panel tiles the dialer contacts the settings panel the music player and the gallery would be fantastic removing the fingerprint sensor and all the other things that a stock s4 not has a beautiful rom would come and certainly turned better than KitKat well optimized with marshmallow
huawei92 said:
the system of the Samsung TouchWiz and wonderful it would be really nice if by cm code could pull off a 6.0 tw must recreate a kernel using cm code and the operative part of a s5 32bit taking just enough like the Samsung app panel tiles the dialer contacts the settings panel the music player and the gallery would be fantastic removing the fingerprint sensor and all the other things that a stock s4 not has a beautiful rom would come and certainly turned better than KitKat well optimized with marshmallow
Click to expand...
Click to collapse
Cm sources not usable because touchwiz freamwork very different to aosp. S4 kernel's I think work
ets2_volvo said:
Cm sources not usable because touchwiz freamwork very different to aosp. S4 kernel's I think work
Click to expand...
Click to collapse
you can not take the base of s5 and developing an area compatible with our new cyanogen mod comes out when you do not take the google code and spread to most of the devices can not do the same with TouchWiz from a new kernel
huawei92 said:
you can not take the base of s5 and developing an area compatible with our new cyanogen mod comes out when you do not take the google code and spread to most of the devices can not do the same with TouchWiz from a new kernel
Click to expand...
Click to collapse
I think very best base is s3 neo cos msm8228 and msm8230