Hi, I'm new in this forum. I need help. I bought a Galaxy Note Pro 12.2 (SM-P900). I know it has two quadcores (one of 1.9 GHz and another of 1.3 GHz) but I think it only use one of them, because it lags a lot when I run games and another apps like chrome. Also when I run benchmarks, they only recognize the 1.9 GHz one. I tested Asphalt 8 and it runs at 20 fps or less. Also it lags when I pass pages in S Note. There's a way to speed up and take advantage of both CPUs? Thanks!
S Note always seems to lag (I don't use it, but others report it.) The app isn't optimized for 12.2". Try Lecture Notes.
Benchmarks see only one CPU because that's their limitation. They couldn't detect the second one even of it was running laps around the first.
Cores don't stack. So even if you have 4 1.9Ghz cores, it doesn't become 7.6Ghz. This is why the amount of Ghz matters so much for gaming and heavy apps. The Exynos is designed for multitasking, not heavy processing(games). That's what Snapdragon is for.
Next is the Mali GPU. It's weaker than the Adreno and doesn't handle 2K very well. Particularly in heavy games. Oh it does Candy Crush just fine , but it's like Intel HD vs Nvidia in terms of the more serious work.
If gaming was a priority, you should've gone for the P905 with the Snapdragon 800 & Adreno GPU.
You can try to get rid of most of the bloatware, that should at least speed it up a bit. Also replace the launcher with Nova or Apex, they use less system resources. (60MB RAM vs 800MB.) You can also try a factory reset, see if that helps.
Maybe someone else with a p900 can tell us if they, too, have the same framerate issue. (I've got the P905.)
The Note 3 N9005 and N900 editions have the same hardware as the P905 and P900 respectively. The N900 with the same Exynos/Mali has the same issues with lag in Gaming as the P900 does.
S Note can't be helped, that's Samsung's fault, bad coding.
Sent from my SM-N9005 using Tapatalk 2
Root it and pick one of the stock based roms because they are the only ones with kernel development. I'm on CM 11 because I love aosp but I'm living with the built in kernel. That's the best you're going to get as far as I can see, but there are a lot of really smart folks around here.
Thanks for replying. Your answers helped me
Asphalt 8 has graphics settings where you can change the level of detail. Change the settings to low (which still looks good) and play is completely smooth.
Regarding optimizing general performance, I'd stick with Samsung stock roms as the gpu driver is better than cm based roms. Change the kernel and overclock the cpu and gpu to 2GHz and 667MHz respectively. Use the synapse app to undervolt the cpu and gpu at the highest frequency steps, necessary to avoid thermal limits which drops the clock speeds. With these settings I get 41000 on Antutu and 996/3000+ on Geekbench 3. Very smooth performance for my tablet.
hi guys new to the forum hope you can help..im about to buy the wifi version but because of the lag im tempted with the lte now..my question is a do a lot of art work .sketching etc and recently artrage was released for android..would you say the snapdragon would be better than the exynos version for brush lag etc .I cant seem to get a good answer to this question ..the note 12.2 is a great size and much lighter than a laptop and reat battery life..
sorry wrong forum
Hello,
1- is it possible to compile moto x play kernel to arm x64 and use it?
2- Will it give any advantages over 32 bit kernel, eg. apps should run faster?
3- Why we have 32bit system when cpu supports ARM x64?
Thanks
Pararocker said:
Hello,
1- is it possible to compile moto x play kernel to arm x64 and use it?
2- Will it give any advantages over 32 bit kernel, eg. apps should run faster?
3- Why we have 32bit system when cpu supports ARM x64?
Thanks
Click to expand...
Click to collapse
This has already been told that the hardware isn't powerful enough to get the performance improvements with 64 bit software or kernel.
If the ram get ahead of 4gb, only then the real performance improvement of 64 bit can be seen.
Sent from my XT1562 using Tapatalk
K.khiladi said:
If the ram get ahead of 4gb, only then the real performance improvement of 64 bit can be seen.
Click to expand...
Click to collapse
benchmarks don't support this. At least on desktop pcs with less than 4GB of RAM 64bit systems mostly were faster:
https://www.phoronix.com/scan.php?page=article&item=ubuntu_x86_1304&num=1
Don't know about Android phones though
According to ARM the speed advantage is about 15-20% (see here). Of course the memory footprint is bigger. The Moto X Play has only 2GB RAM, so 64 bit may lose speed against 32 Bit if memory gets exhausted.
This is the same dimension like DroidFish would probably gain according to a mail from the author, which I asked some time ago:
Code:
[quote=tag]in a German Android forum someone insists that chess programs would be
much faster on 64 Bit Android. Do you agree? Would DroidFish for
instance make use of bigger data types, or do they exist already in 32
Bit Android?
[/quote]
The only functional difference in DroidFish when using 64 bit android is
that 6-men syzygy tablebases are supported. The DroidFish user interface
probably only get slightly faster by using 64-bit instructions. Chess
engines can gain quite a bit of speed by using 64-bit instructions though,
but how much they gain depends on the chess engine.
For the stockfish engine that is built into DroidFish I measured 16% speed
increase on my Nexus 6P when using 64-bit compared to 32-bit.
For my own chess engine texel the difference is much larger. The speed
increases about 68% when using 64-bit compared to 32-bit.
The difference can probably mostly be explained by the fact that stockfish
is heavily optimized both for 64-bit and 32-bit architectures, but texel
is only optimized for 64-bit architectures.
Pararocker said:
Hello,
1- is it possible to compile moto x play kernel to arm x64 and use it?
2- Will it give any advantages over 32 bit kernel, eg. apps should run faster?
3- Why we have 32bit system when cpu supports ARM x64?
Thanks
Click to expand...
Click to collapse
1. Maybe, if we can maintain binary compatible with 32-bit userspace blobs. It may be doable with CONFIG_COMPAT and some hackery, but I've never tried such a thing before. I've been contemplating building a 64-bit ROM for lux (using a blend of lux blobs and blobs from 64-bit MSM8939 devices) for quite a while, but I've been too busy to even try, and I have higher priority tasks to take care of when I do get time (such as Audio HAL issues on CM13).
2. Yes, expect a 15-20% speedup. 64-bit sucks with 1 GB RAM, but 2 GB is fine.
3. Motorola wanted to make surnia, osprey, merlin, and lux as similar as possible, so they chose the lowest common denominator.
@squid2 Did you manage to make a 64 bit kernel, buddy?
Hey guys,
Check out this video comparing the speeds of the devices and if the extra gig RAM really matters. https://youtu.be/j3J2DNHIbR4
Johnsmithson said:
Hey guys,
Check out this video comparing the speeds of the devices and if the extra gig RAM really matters.
Click to expand...
Click to collapse
Is the opx tweaked in any way?
its normal for the opx to open apps faster than the nexus, after all the 801 is still a good cpu clocked @ 2.3ghz vs the 808 which is a low powered quad core + more powerful dual core @ 1.8 ghz, thats why the opx is still a bit faster. But knowing what i know now, i would definitely go for the nexus 5x over the OPX
Unfortunately opening apps faster is not all that matters. Ram speed and other stuff is important too, as well as software updates
gavisharora said:
Is the opx tweaked in any way?
Click to expand...
Click to collapse
No, it's running stock OxygenOS 3.1.3 without any tweaks.
Synchronize the touches on both phone FFS. Total waste of 2:25
It seems ever since 64bit roms were possible for Athene, all maintainers are only building 64bit Oreo roms, rather than 32bit. But what is the real benefit of this? From what I've noticed, 64bit roms have more issues than 32bit roms. Correct me if I'm wrong, but this is the info I've gathered:
32bit rom bugs:
Camera
Torch
64bit ROM bugs:
Camera
Torch
GPS
System UI lags
Video recording
Not to mention 64bit roms have more ram consumption, which isn't good for those who have the 2GB version of Athene.
I think maintainers should continue building 32bit versions of their roms along with 64bit to give users more options. Just a thought.
There is absolutely no reason why a 64 bit Android should be on our devices. Will not add any performance, the memory is max 4GB (3.6GB available with 32 bit), 64 bit native apps take more space in memory, CPU is not fully equipped for 64 bit OS (32 bit memory bus)...
Skeptico said:
It seems ever since 64bit roms were possible for Athene, all maintainers are only building 64bit Oreo roms, rather than 32bit. But what is the real benefit of this? From what I've noticed, 64bit roms have more issues than 32bit roms. Correct me if I'm wrong, but this is the info I've gathered:
32bit rom bugs:
Camera
Torch
64bit ROM bugs:
Camera
Torch
GPS
System UI lags
Video recording
Not to mention 64bit roms have more ram consumption, which isn't good for those who have the 2GB version of Athene.
I think maintainers should continue building 32bit versions of their roms along with 64bit to give users more options. Just a thought.
Click to expand...
Click to collapse
The point is: most maintains uses one device tree for 64bit which will be developed.(correct me if I'm wrong).
So if the 32bit source won't be developed, you must switch to the other one.
ok, but 64bits mainteners are on the same stage: no progress.
lot of 64bits roms are compiled without any debugging.
murigny64 said:
ok, but 64bits mainteners are on the same stage: no progress.
lot of 64bits roms are compiled without any debugging.
Click to expand...
Click to collapse
That's what I wrote: they use the same device tree/source hence the bugs are present on nearly all 8.1 builds and. You need to fix the camera issues in the device source not the rom source as its a problem of not available drivers and you need to shim it.
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
SoNic67 said:
There is absolutely no reason why a 64 bit Android should be on our devices. Will not add any performance, the memory is max 4GB (3.6GB available with 32 bit), 64 bit native apps take more space in memory, CPU is not fully equipped for 64 bit OS (32 bit memory bus)...
Click to expand...
Click to collapse
People demand it permanently, that's the real reason for it.
strongst said:
People demand it permanently, that's the real reason for it.
Click to expand...
Click to collapse
This is the most vital reason. If perfected you get portrait mode which most people will be crazy about
64 (bit) is double the value of 32 (bit), so it must be far better, faster, sexier, whatever... :silly:
thorin0815 said:
64 (bit) is double the value of 32 (bit), so it must be far better, faster, sexier, whatever... :silly:
Click to expand...
Click to collapse
Yeah another reason.... Like Megapixel in case of quality....
You can use marshmallow. Bug free, 32 bit, torch works.
32bit was rather good since the only plus i see is Google camera which i don't really care. Bugs could be fixed on 64bit which isn't a issue. But the thing is 32BIT is dying, all oems are going through the trend of 64bit and the support for 32bit is slowly dead.
64bit is the way to go.
Orelse you guys should be on Nougat.
Just because marketing wise it's successful, it doesn't mean it will be better.
Especially when Moto doesn't develop 64 bit drivers.
But yes, stupidity always wins in the end because it's unrelenting.
That's because the ROM "builders" are not technically aware imho or maybe they just want to ignore the facts.
Fact is, this device houses a 32 bit bus. Busses are responsible for transferring data signals. When you are using a 32 bit system, the data is transported in one go but in the case of 64 bit roms, the data has to be transported in 2 turns ie the latency gets doubled. More the latency, lesser responsive your system. Yes you can reduce the latency by overclocking the bus, but doing that can only get you max to max 10% efficiency, overall the system is still lagging by 40%. This might not be noticeable on 3gb+ variants because of the obvious reasons but it gets pretty evident in the versions having 2gb ram.
We cannot get over this hardware limitation no matter what. It would be utterly stupid to shift to 64 bit roms for this device. A 32bit ROM should outperform any 64bit ROM easily. That's just my 2 cents tho, I would any day prefer a 32 bit ROM over any other.
hell_lock said:
That's because the ROM "builders" are not technically aware imho or maybe they just want to ignore the facts.
Fact is, this device houses a 32 bit bus. Busses are responsible for transferring data signals. When you are using a 32 bit system, the data is transported in one go but in the case of 64 bit roms, the data has to be transported in 2 turns ie the latency gets doubled. More the latency, lesser responsive your system. Yes you can reduce the latency by overclocking the bus, but doing that can only get you max to max 10% efficiency, overall the system is still lagging by 40%. This might not be noticeable on 3gb+ variants because of the obvious reasons but it gets pretty evident in the versions having 2gb ram.
We cannot get over this hardware limitation no matter what. It would be utterly stupid to shift to 64 bit roms for this device. A 32bit ROM should outperform any 64bit ROM easily. That's just my 2 cents tho, I would any day prefer a 32 bit ROM over any other.
Click to expand...
Click to collapse
Well hopefully most of the maintainers for our device read this, and then stop building 64bit ROMs. You've confirmed my suspicion that it's basically pointless.
Frostbite said:
You can use marshmallow. Bug free, 32 bit, torch works.
Click to expand...
Click to collapse
If there were security patches for it, I would love to do for sure!
You guys remember that discussion https://forum.xda-developers.com/moto-g4-plus/help/64bit-roms-t3634876 now it's known that there's no real benefit and more problems with 64bit :silly:
hell_lock said:
That's because the ROM "builders" are not technically aware imho or maybe they just want to ignore the facts.
Fact is, this device houses a 32 bit bus. Busses are responsible for transferring data signals. When you are using a 32 bit system, the data is transported in one go but in the case of 64 bit roms, the data has to be transported in 2 turns ie the latency gets doubled. More the latency, lesser responsive your system. Yes you can reduce the latency by overclocking the bus, but doing that can only get you max to max 10% efficiency, overall the system is still lagging by 40%. This might not be noticeable on 3gb+ variants because of the obvious reasons but it gets pretty evident in the versions having 2gb ram.
We cannot get over this hardware limitation no matter what. It would be utterly stupid to shift to 64 bit roms for this device. A 32bit ROM should outperform any 64bit ROM easily. That's just my 2 cents tho, I would any day prefer a 32 bit ROM over any other.
Click to expand...
Click to collapse
If you have the data greater than the 32bit system instruction set, you have to run the cycle twice.
64Bit doesn't mean you everytime have to run the cycle twice Imo.
When it's needed, it's done.
krypticallusion said:
If you have the data greater than the 32bit system instruction set, you have to run the cycle twice.
64Bit doesn't mean you everytime have to run the cycle twice Imo.
When it's needed, it's done.
Click to expand...
Click to collapse
It's not about the data. A 64bit system uses 64 bits for referencing the memory. So when you're running any app or anything, the cpu has to wait twice the normal time to get the next instruction.
hell_lock said:
It's not about the data. A 64bit system uses 64 bits for referencing the memory. So when you're running any app or anything, the cpu has to wait twice the normal time to get the next instruction.
Click to expand...
Click to collapse
Stay on N 32-bit and enjoy :')
Dreamstar said:
Stay on 32-bit and enjoy :')
Click to expand...
Click to collapse
But look at the title of the thread: that's exactly the problem.
All those 32 bit ROMs are stalled, no security updates or development anymore ..
(Of course everybody is free to compile himself, I know).
Dreamstar said:
Stay on 32-bit and enjoy :')
Click to expand...
Click to collapse
If you and other maintainers would continue building 32bit Oreo ROMs, then sure. But no one is anymore...
Could it be that if they carried the Redmi 7A MIUI, it wouldn't look better on Potter?
I have the variant with 2gb ram and had several performance issues with MIUI, especially in games, I really like MIUI, but so not to use, I play a lot, I realized that always carry the MIUI devices with more ram (usually 4gb ram ...), if you had one with less ram would not be better?
The improvement would be not only in the 2gb variant, but also in the 3gb and 4gb variant.
The Redmi 7A has a Snapdragon 439 and 2gb ram