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 !
Related
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?
I have a SGT 3 GT-P5210 running Android 4.2.2 . But for some developing reasons I want to downgrade it to 4.0.3 ICS.
I have searched a lot on the web, but I couldn't find not even 1 ROM for 4.0.3 dedicated for my device.
I also have a look at this xda thread but nobody gives an answer in the end: http://forum.xda-developers.com/showthread.php?t=2582179
I am actually thinking that it is completely impossible to find a ROM for my purposes, due to many reasons.
Is this right? Or does anyone have a link at such a ROM?
The scenario of just trying to flash a ROM of SGT 2 won't work due to the Intel Atom Processor of GT 3...Not saying that it could work otherwise...
Thanks in advance.
If you every heard of porting then google how to port and there is a lot of guides, so that can help you make a rom for your own then if it works upload it and share it with community
Sent from my SM-T210R using Tapatalk
Ripshock said:
If you every heard of porting then google how to port and there is a lot of guides, so that can help you make a rom for your own then if it works upload it and share it with community
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
I googled for porting and I found some very interesting articles and guides. But it seems it is not possible for my purposes. The Port ROM has to be for the same processor type (Galaxy Tab 3 -> Intel Atom) and of the same manufacturer as of the Base ROM's (Samsung doesn't have an Intel tablet with Android ICS available..). In some guides I also read that the Android versions have to be of the same type, which is the opposite of what I want.
Porting from Galaxy Tab 2 will ,almost definitely, won't work since it has an ARM processor. But I will try it to ensure that it will fail.
Building from source is also impossible, because several vendor components will be needed, which are proprietary, and as a result, unavailable.
I will let you know when I brick my Tab 3 with Tab 2 ROM.
Nick_Pro said:
I googled for porting and I found some very interesting articles and guides. But it seems it is not possible for my purposes. The Port ROM has to be for the same processor type (Galaxy Tab 3 -> Intel Atom) and of the same manufacturer as of the Base ROM's (Samsung doesn't have an Intel tablet with Android ICS available..). In some guides I also read that the Android versions have to be of the same type, which is the opposite of what I want.
Porting from Galaxy Tab 2 will ,almost definitely, won't work since it has an ARM processor. But I will try it to ensure that it will fail.
Building from source is also impossible, because several vendor components will be needed, which are proprietary, and as a result, unavailable.
I will let you know when I brick my Tab 3 with Tab 2 ROM.
Click to expand...
Click to collapse
Why are you so n00b ???
Trying to flash a Tab 2 ROM on a Tab 3 ?
Architectures are VERY different,
Processor are different,
GPU are different,
RAM modules (DDR3L vs DDR2) are different,
Sound Cards are different,
So how could you port this ?
Have you already wondered WHY development of Tab 3 10.1 is too SLOW ?
Good luck with your port.
Btw, if you want the most smoothest ROM released for Tab 3 10.1, flash this http://forum.xda-developers.com/showthread.php?t=2693396 :good:
It's an awesome rom with many features like Multi-Window
Sent from my GT-P5210 running on amtrom hd
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
Any chance of getting Lineage 14 for the Galaxy Nexus or is the phone too slow and RAM memory too limited for this version of Android?
Any developer is allowed to build Lineage using the work done on Unlegacy. But this is hard work and everyone here is a volunteer. Unless you know someone who can help, the best you can do right now is running Unlegacy. I don't know if there is any developer who will take a donation from you as a bounty to get if working, but you could message them to ask.
This thread is technically off topic for the development forum
there is a lineage os rom for galaxy s2 i9100, maybe someone could port it to our device, galaxy nexus has similar amount odf ram and cpu compared to s2
MAD_psycho_Zz said:
there is a lineage os rom for galaxy s2 i9100, maybe someone could port it to our device, galaxy nexus has similar amount odf ram and cpu compared to s2
Click to expand...
Click to collapse
There is also Unlegacy 7.1.1 for our GNex (that ROM was, in fact, my introduction to N on ANY hardware). So why am I not running it now? Simple enough - PureNexus 7.1.1 includes both the Pixel Launcher AND Google Assistant (which can be run together or separately; I run them as a tag-team). At some point, I hope to ambush some unsuspecting Pixel or PixelXL owner with my GNEX.
PGHammer said:
There is also Unlegacy 7.1.1 for our GNex (that ROM was, in fact, my introduction to N on ANY hardware). So why am I not running it now? Simple enough - PureNexus 7.1.1 includes both the Pixel Launcher AND Google Assistant (which can be run together or separately; I run them as a tag-team). At some point, I hope to ambush some unsuspecting Pixel or PixelXL owner with my GNEX.
Click to expand...
Click to collapse
Does the Pixel Launcher work on the Marshmallow based PureNexus ROMs as well?
rahimali said:
Does the Pixel Launcher work on the Marshmallow based PureNexus ROMs as well?
Click to expand...
Click to collapse
No idea - it is included WITH the 7.1.x ROMs (both 7.1.0 and 7.1.1). There are ways to add it to 6.x (or even 5.x) - still, I like 7.1.x because it actually feels more *whole* with both PL and Google Assistant in place - which is why I am still hoping to find a Pixel/XL owner to ambush here in VZW turf.
PGHammer said:
There is also Unlegacy 7.1.1 for our GNex (that ROM was, in fact, my introduction to N on ANY hardware). So why am I not running it now? Simple enough - PureNexus 7.1.1 includes both the Pixel Launcher AND Google Assistant (which can be run together or separately; I run them as a tag-team). At some point, I hope to ambush some unsuspecting Pixel or PixelXL owner with my GNEX.
Click to expand...
Click to collapse
Where can I find the PureNexus 7.1.1 ROM? I saw that the only ROM in development section is Unlegacy ROM (by Ziyan)...but this Rom still has a sim bug
Here ya go
WoolTomb said:
Where can I find the PureNexus 7.1.1 ROM? I saw that the only ROM in development section is Unlegacy ROM (by Ziyan)...but this Rom still has a sim bug
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120698603
If you click on the name of the developer, there is a fresh build :laugh24 feb.):
https://www.androidfilehost.com/?fid=457095661767139794
Is it enough stable to use daily? Thx:angel:
He announces here. However, he is not good at English, so it may be difficult to communicate.lol
https://plus.google.com/+HatayamaYuuji
voidz777 said:
He announces here. However, he is not good at English, so it may be difficult to communicate.lol
https://plus.google.com/+HatayamaYuuji
Click to expand...
Click to collapse
Does he post here? Someone could make an official thread for him if he wants...
bamtan2 said:
Does he post here? Someone could make an official thread for him if he wants...
Click to expand...
Click to collapse
I think that it is better to have threads if people with various problems can help solve the problem.
He will be welcome if it is a thread for that.
If problem solving is possible, he will post for that.lol
Just remain patient.
The Samsung Galaxy Nexus (i9250, "maguro") is pretty similar to the Samsung Galaxy S3 (i9300), which already got LineageOS nightly. They're very similar phones when it comes to features and exterior. Both have 720p AMOLED screens, front-facing and rear-facing cameras, approximation sensors, light meter, earpiece, microphones, headphone jack in exactly the same places. Both feature 1 GB RAM and 16 GB eMMC. Both have HSPA+, but no LTE. They're also just half a year apart concerning their age (December 2011 vs. May 2012). They both feature an ARM Cortex A9 processor, though they utilize different SoCs (GNex = TI OMAP 4460, S3 = Samsung Exynos 4412).
The G-Nex seems to have a larger user base than the G-S3.
Lineage 14.1 for Galaxy Nexus
ZeeLog has built the Lineage for Galaxy Nexus. I don't know the status of the ROM but if anyone wanna try, then here is the link:
Galaxy Nexus Lineage OS 14.1
massima said:
If you click on the name of the developer, there is a fresh build :laugh24 feb.):
https://www.androidfilehost.com/?fid=457095661767139794
Is it enough stable to use daily? Thx:angel:
Click to expand...
Click to collapse
The 24 February build is, in fact, my daily driver.
shibaa987 said:
ZeeLog has built the Lineage for Galaxy Nexus. I don't know the status of the ROM but if anyone wanna try, then here is the link:
Galaxy Nexus Lineage OS 14.1
Click to expand...
Click to collapse
Do you try this rom? How much stable is?
Please see change log.
http://zeelogkang.blogspot.com
uji_sine said:
Please see change log.
http://zeelogkang.blogspot.com
Click to expand...
Click to collapse
Thanks a lot...but for me this ROM still has too much bugs for daily use...i'll wait
Hello, I just flashed ua_tuna-7.1.1-20170310 but my SIM card not works, not recognize, any suggestion? I done a full wipe
Vara83 said:
Hello, I just flashed ua_tuna-7.1.1-20170310 but my SIM card not works, not recognize, any suggestion? I done a full wipe
Click to expand...
Click to collapse
do what is explained in this post:
https://forum.xda-developers.com/showpost.php?p=71215509&postcount=1326
bye
yen
Seeing how even the Samsung Galaxy S II has gotten a port of LineageOS 12, I wondered if there's anything that would prevent the Galaxy Nexus from getting it as well.
A developer already told me privately that it would be theoretically possible and that it would probably be better off with Android Go settings, but I wondered if there could be anything else that might prevent it. Because I see little discussion about this phone and I've seen no Custom Roms that go beyond Android 7.1 Nougat.
As a smartphone of the Nexus line, shouldn't it be even easier to support than something like the Galaxy S II?
I just know that it'd be awesome to see newer Android versions on it, just as with several other older phones that already got them.
Are you serious??? There is no way Galaxy Nexus can run Android 12. Even when this phone run on Android 7.1.2 (latest custom rom) it run poor and gets hot quickly, so i don't think anyone will build any custom rom for this device.
alprtewwqfr said:
Are you serious??? There is no way Galaxy Nexus can run Android 12. Even when this phone run on Android 7.1.2 (latest custom rom) it run poor and gets hot quickly, so i don't think anyone will build any custom rom for this device.
Click to expand...
Click to collapse
I'm just curious whether it is possible or not. The Samsung Galaxy S II seems to be able to do it, even though it's still in an early phase.
"As a smartphone of the Nexus line, shouldn't it be even easier to support than something like the Galaxy S II?"
for ti Omap chipset it isnt really easy to port twrp or lineage 19.0
"A developer already told me privately that it would be theoretically possible and that it would probably be better off with Android Go settings,"
no, you don't bringup and you can't make android 12 for this device. remember TI OMAP processors are close source afaik. and android 7 on this device RUNS VERY POORLY. so it's impossible to port a12 on this device, unless you try to port LOS 15.0 first.
[ROM][AOSP][8.1 Oreo] Unlegacy Android (Unofficial)
Warranties: THIS GUIDE COMES WITH NO WARRANTY. I AM NOT RESPONSIBLE OF BREAKING YOUR PRECIOUS TABLET. PLEASE BACKUP YOUR DATA BEFORE CONTINUING, AS THIS GUIDE WILL WIPE YOUR DATA. Also, this guide assumes you have the following requirements...
forum.xda-developers.com
Oreo actually runs way better than Nougat, at least with the holy kernel 3.4.
Can someone port Lineage OS 15.1 for the Galaxy Nexus maguro?
Don't forget, Android 12 (as well as 11, possibly also 10) is 64 bit only.
siealex said:
Don't forget, Android 12 (as well as 11, possibly also 10) is 64 bit only.
Click to expand...
Click to collapse
That's not right, we are running A11, A12 and A13 on many other arm chipsets like the Samsung Galaxy S2, Samsung Galaxy S3 and also many others...
Yes, it can be compiled for these chipsets, but will it be compatible with new software?
siealex said:
Yes, it can be compiled for these chipsets, but will it be compatible with new software?
Click to expand...
Click to collapse
Yep, everything seems to work fine .
its theoretically possible, the omap 4460 is armv7 and has over a gig of ram, which are the bare minimum system requirements for running android 12.
however, it would be a major undertaking to port the crusty code over to android 12 AND it would run like garbage, unless someone were to try and speed up that code, which would be a whole other story.
if the community had continued like it had on the galaxy s2, this wouldve already happened, but it didnt for likely many reasons.
im guessing one of those is the lack of mainline linux support, which is because of the SGX540 in this phone.