Related
The Nexus 9 uses the F2FS (flash-friendly) filesystem as default, instead of EXT4! (see attached screenshot)
Also notice the 508 MB Swap partition in the screenshot...
edgarf28 said:
The Nexus 9 uses the F2FS (flash-friendly) filesystem as default, instead of EXT4! (see attached screenshot)
Also notice the 508 MB Swap partition in the screenshot...
Click to expand...
Click to collapse
Can you do a androbench benchmark please i want to know the storage performance
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
edgarf28 said:
The Nexus 9 uses the F2FS (flash-friendly) filesystem as default, instead of EXT4! (see attached screenshot)
Also notice the 508 MB Swap partition in the screenshot...
Click to expand...
Click to collapse
What is the swap file used for, is it for the cpu, does it use the ram?
The thing has the fastest set up it should be the most smoothest device ever made.
64 bit tegra k1 with geekbench single core performance of 2000 almost double that snapdragon 801.
Fastest internal storage chip. 15MB random write and 38MB random read.
Android lollipop
F2fs filesystem
2gb ram
---------- Post added at 06:40 PM ---------- Previous post was at 06:03 PM ----------
bushgreen said:
Can you do a androbench benchmark please i want to know the storage performance
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
What is the swap file used for, is it for the cpu, does it use the ram?
The thing has the fastest set up it should be the most smoothest device ever made.
64 bit tegra k1 with geekbench single core performance of 2000 almost double that snapdragon 801.
Fastest internal storage chip. 15MB random write and 38MB random read.
Android lollipop
F2fs filesystem
2gb ram
Click to expand...
Click to collapse
.
..
bushgreen said:
Can you do a androbench benchmark please i want to know the storage performance
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
What is the swap file used for, is it for the cpu, does it use the ram?
The thing has the fastest set up it should be the most smoothest device ever made.
64 bit tegra k1 with geekbench single core performance of 2000 almost double that snapdragon 801.
Fastest internal storage chip. 15MB random write and 38MB random read.
Android lollipop
F2fs filesystem
2gb ram
---------- Post added at 06:40 PM ---------- Previous post was at 06:03 PM ----------
.
..
Click to expand...
Click to collapse
The 508 MB Swap partition do not use any RAM, I think it's just an partition on the internal memory to extent the RAM with 508 MB (so basically you have 1.8 Gb RAM + 508 MB Swap)
And see attached screenshot for the AndroBench results.
it is just plain stupid putting only 2GB ram on a 64Bit device and then helping out with 500MB swap. They could have easily add 3GB ram without any significant costs..
Funny thing is that the nexus 6 has 3GB ram and has a variant with 64GB disk.
Looks like f2fs is only used on the encrypted /data partition, /system and /cache still use ext4.
Also, the Nexus 9 actually has zram enabled, which explains the swap "partition". Having 2GB of memory with 0.5GB of zram is an interesting alternative to just using 3GB of memory instead.
farmerbb said:
Looks like f2fs is only used on the encrypted /data partition, /system and /cache still use ext4.
Also, the Nexus 9 actually has zram enabled, which explains the swap "partition". Having 2GB of memory with 0.5GB of zram is an interesting alternative to just using 3GB of memory instead.
Click to expand...
Click to collapse
no, it is not an interesting alternative, it is a stupid one in every way. the nexus 9 is already quite expensive. 1GB ram just costs a couple of dollars and room is more than enough within. and considering it is 64Bit it will bloat up ram usage anyway, not to forget that this high screen resolution eats up a lot of ram, too.
a user said:
no, it is not an interesting alternative, it is a stupid one in every way. the nexus 9 is already quite expensive. 1GB ram just costs a couple of dollars and room is more than enough within. and considering it is 64Bit it will bloat up ram usage anyway, not to forget that this high screen resolution eats up a lot of ram, too.
Click to expand...
Click to collapse
It's stupid until you realize how channeling works. The option to user zram is a very interesting one and it might be a better solution. So far benchmarks of the tablet agree with HTC/Google.
EDIT: also, in a serialized "queue" architecture like the this 64bit K1 with 2 cores, multitasking is not the priority. 2GB + zRam or 3GB should not make much difference.
Google opted for this kind of CPU in the N9 to make it as fast as an ipad air2 on your active task. You don't have multiple windows, you won't do true multitasking in this tablet. This is an ipad alternative, and even these architectural details show it.
FrankBullitt said:
It's stupid until you realize how channeling works. The option to user zram is a very interesting one and it might be a better solution. So far benchmarks of the tablet agree with HTC/Google.
EDIT: also, in a serialized "queue" architecture like the this 64bit K1 with 2 cores, multitasking is not the priority. 2GB + zRam or 3GB should not make much difference.
Google opted for this kind of CPU in the N9 to make it as fast as an ipad air2 on your active task. You don't have multiple windows, you won't do true multitasking in this tablet. This is an ipad alternative, and even these architectural details show it.
Click to expand...
Click to collapse
a lot of unrelated stuff in your post. there is no need for zram or swap (regarding the first posts its swap and not compressed ram, but i do not know myself what it is) if you get an extra 1GB of ram. 1 GB of ram is ALWAYS better than zram or swap. zram is a nice option when you cannot extend the memory for various reasons and swap may be used for heigh memory use cases when you have some not too slow alternate memory. n9 internal memory is still damn slow for swapping (if it is indeed a swap faile on disk at all).
but actually there seems to be no good reason to not add an extra GB as we can see the nexus 6 has it, the nexus 9 ha definetly room for it (it is not like pc dram module) and it is damn cheap also.
secondly, i'm not talking about multitasking when i pointed out 64bit, so why the hell are you bringing this in? beside of that on a tablet multitasking it meanwhile not so uncommen. the point is that a 64 bit os has a MUCH larger memory footprint. also such high screen resolutions add a decent amount of memory either. and finally, your argument about benchmarks proving anything related to my comment is unrelated at best. it doesn't prove anything related to my statement.
there is aboluelty no reason to prefere zram or swap over an extra GB of ram, and it seems that there is nothing that would made it difficult for htc to add it. i can only assume that they added this just collect some experience on it and nothing more.
i really don't get it. what's the purpose of your statement? showing of your lack of knowledge or celebrating fanboyship "oh cool, they skipped a 5$ GB ram but gave us zram hurayyyyy".
sounds totally sound to give a smartphone 1GB ram more, same high resoltion on a smaller screen and twice as much disk space
EDIT: but please finally tell us WHAT exactly is so "interessting" adding zram or swap instead of one GB ram? you post has no information except this little claim. one might find this decision interesting of course due to its stupidity but it doesn't look that this is the source of your interest.
Any conjecture or theoretical analysis is ultimately pretty meaningless. Just let the performance speak for itself.
@mkygod hallelujah !! ??
a user said:
a lot of unrelated stuff in your post. there is no need for zram or swap (regarding the first posts its swap and not compressed ram, but i do not know myself what it is) if you get an extra 1GB of ram. 1 GB of ram is ALWAYS better than zram or swap. zram is a nice option when you cannot extend the memory for various reasons and swap may be used for heigh memory use cases when you have some not too slow alternate memory. n9 internal memory is still damn slow for swapping (if it is indeed a swap faile on disk at all).
but actually there seems to be no good reason to not add an extra GB as we can see the nexus 6 has it, the nexus 9 ha definetly room for it (it is not like pc dram module) and it is damn cheap also.
secondly, i'm not talking about multitasking when i pointed out 64bit, so why the hell are you bringing this in? beside of that on a tablet multitasking it meanwhile not so uncommen. the point is that a 64 bit os has a MUCH larger memory footprint. also such high screen resolutions add a decent amount of memory either. and finally, your argument about benchmarks proving anything related to my comment is unrelated at best. it doesn't prove anything related to my statement.
there is aboluelty no reason to prefere zram or swap over an extra GB of ram, and it seems that there is nothing that would made it difficult for htc to add it. i can only assume that they added this just collect some experience on it and nothing more.
i really don't get it. what's the purpose of your statement? showing of your lack of knowledge or celebrating fanboyship "oh cool, they skipped a 5$ GB ram but gave us zram hurayyyyy".
sounds totally sound to give a smartphone 1GB ram more, same high resoltion on a smaller screen and twice as much disk space
EDIT: but please finally tell us WHAT exactly is so "interessting" adding zram or swap instead of one GB ram? you post has no information except this little claim. one might find this decision interesting of course due to its stupidity but it doesn't look that this is the source of your interest.
Click to expand...
Click to collapse
No...you would understand what he was talking about if you understood what he meant by "architecture". The Tegra K1 chip employed by the N9, aka Project Denver, is the first in order execution CPU since...like, 1990.......This device was never designed to multitask, as the CPU itself was designed to finish tasks in order, and be damn fast at that.
Here, read up on this: http://hothardware.com/News/Nvidias-64bit-Tegra-K1-The-Ghost-of-Transmeta-Rides-Again/
Adding 1GB of RAM is useless, since 64bit really needs 4 & up to shine, it doesn't make a difference whether or not you tack on another GB.....
UAL4588 said:
No...you would understand what he was talking about if you understood what he meant by "architecture". The Tegra K1 chip employed by the N9, aka Project Denver, is the first in order execution CPU since...like, 1990.......This device was never designed to multitask, as the CPU itself was designed to finish tasks in order, and be damn fast at that.
Here, read up on this: http://hothardware.com/News/Nvidias-64bit-Tegra-K1-The-Ghost-of-Transmeta-Rides-Again/
Click to expand...
Click to collapse
i know very well how denver works and it still has nothing to do with what i said.
Adding 1GB of RAM is useless, since 64bit really needs 4 & up to shine, it doesn't make a difference whether or not you tack on another GB.....
Click to expand...
Click to collapse
that's simply not true! 64bit does not shine more orn 4GB ram or on 12GB. you need 64bit for 4GB+ ram (while 4GB actually works on 32bit with PAE). but i am not talking about when 64bit is needed to allow for more memory. i am talking about the double sized memory pointers, the bigger size ints and longs, due to 64bit! this caused all native code to consume far more memory. but as ia already said multiple times, not only the 64bit os itself eats a lot of memory it also the high resolution graphics but also the meanwhile increased resolution assets of android.
i don't say that it is actually needed to install more memory. but if they decided to add zram it seems they actually needed more memory. the point is that it is stupid to extend the memory with zram instead of just simply adding 1GB ram.
i can't say it more clearly. the stupidity is to NOT INSTALL 1GB MORE RAM BUT INSTEAD USE ZRAM TO MAKE UP FOR LACK OF MEMORY.
It doesnt need a swap file 2gb ram is enough
UAL4588 said:
No...you would understand what he was talking about if you understood what he meant by "architecture". The Tegra K1 chip employed by the N9, aka Project Denver, is the first in order execution CPU since...like, 1990.......This device was never designed to multitask, as the CPU itself was designed to finish tasks in order, and be damn fast at that.
Here, read up on this: http://hothardware.com/News/Nvidias-64bit-Tegra-K1-The-Ghost-of-Transmeta-Rides-Again/
Adding 1GB of RAM is useless, since 64bit really needs 4 & up to shine, it doesn't make a difference whether or not you tack on another GB.....
Click to expand...
Click to collapse
Arm chips didn't really start to use out of order instructions until the cortex a9, sometime around the Tegra 2 and the atrix. There were plenty, literally hundreds of android phones with cortex a7 and a8 cpu's with in order execution. (Think of the older snapdragons, the hummingbird, the omap's) Because this CPU happens to be an in order processor, doesn't mean its now a non multitasking tablet or OS. Multitasking performance should not be expected to get WORSE, with better hardware(I'm not saying it is, but it shouldn't be expected).
Yes 64 bit processors shine with above 4 gigs of ram(as far as mapping more memory), but 64 bit applications have a larger memory footprint than the same application compiled for 32 bit CPU's(uses more ram). So with the higher resolution and 64 bit OS, 2 gigs of ram may be pushing it, and it is probably why they added the swap.
No matter how you slice it, ram is always better than swap. Ram is always gonna be faster memory than a large storage device. If they thought 2 gigs would not be enough ram, swap should not have even be a consideration, just make it 3. The nexus 10 was a prime example of this due to the screen resolution and the GPU needing too much ram. Most of the 10's issues were the CPU not having quite enough power and not enough ram. Chrome would refresh pages with just a few tabs open when switching between them.
I personally would not trust a young filesystem that was initiated by Samsung.
Both of the above sounds like my data is at risk
After playing with it for a few days , I observed reload of the launcher sometimes. I am not sure if Lollipop is not yet well optimized for N9 or whatever. I think that 3GB of ram should be better.
2gb Ram is plenty it does not need the swap file
I hope the swap file ain't causing any slow downs or lag because it is reading writing to it instead of using the main ram
edgarf28 said:
The 508 MB Swap partition do not use any RAM, I think it's just an partition on the internal memory to extent the RAM with 508 MB (so basically you have 1.8 Gb RAM + 508 MB Swap)
And see attached screenshot for the AndroBench results.
Click to expand...
Click to collapse
A swap partition is just that, it swaps memory to a file system when memory or other resources are gone. Some applications will do it by default.
I'm positive you don't have a grasp on linux or *inux systems. You should read up on 'em.
I beg to differ... I'm so sick and tired of all my apps getting booted out of memory the moment they're off-screen. Even the damn launcher vanishes way too quick and takes an eternity to reload. This tablet sucks for multi taking, even though the gorgeous screen is taylor-made for it.
a user said:
i know very well how denver works and it still has nothing to do with what i said.
that's simply not true! 64bit does not shine more orn 4GB ram or on 12GB. you need 64bit for 4GB+ ram (while 4GB actually works on 32bit with PAE). but i am not talking about when 64bit is needed to allow for more memory. i am talking about the double sized memory pointers, the bigger size ints and longs, due to 64bit! this caused all native code to consume far more memory. but as ia already said multiple times, not only the 64bit os itself eats a lot of memory it also the high resolution graphics but also the meanwhile increased resolution assets of android.
i don't say that it is actually needed to install more memory. but if they decided to add zram it seems they actually needed more memory. the point is that it is stupid to extend the memory with zram instead of just simply adding 1GB ram.
i can't say it more clearly. the stupidity is to NOT INSTALL 1GB MORE RAM BUT INSTEAD USE ZRAM TO MAKE UP FOR LACK OF MEMORY.
Click to expand...
Click to collapse
Totally agree with this, I'd be happy to pay $10-$20 more for and extra 1 to 2 Gb or ram.
Then they could have gone something like 4GB Ram + zram
Would have been better
And while denver may be an In order design, its 7 way Superscalar which should outweigh the benifits of a 3 way OoOE Design for multitasking
Anybody with some info about this screenshot?
32bit windows can max run 3gb ram, do andoid work the same way?
I see note 4 n910u have a 4gb ram module inside..
Never seen info about this, or never see any info about 3 or 4gb ram.
Greets from Holland.
No idea bout the ram module, but a 32bit OS can support 4GB!! The reality is that not all of that RAM is made available to the OS all the time as the system reserves portions
regards
escobar035 said:
Anybody with some info about this screenshot?
32bit windows can max run 3gb ram, do andoid work the same way?
I see note 4 n910u have a 4gb ram module inside..
Never seen info about this, or never see any info about 3 or 4gb ram.
Greets from Holland.
Click to expand...
Click to collapse
No it doesn't mean that.
Its telling you that the type of memory module being use is a 4 Gigabit, notice the lower case b, b = bit , upper case B = Byte.
Samsung is using 6x4Gigabit modules to give us 3GigaBytes of RAM. There is 8 Bits to a Byte.
And the usable amount is whats left over after they give a portion of it to the GPU for video processing.
Did you see the line "detection needs to be improved" in the bottom?
marleyb said:
No idea bout the ram module, but a 32bit OS can support 4GB!! The reality is that not all of that RAM is made available to the OS all the time as the system reserves portions
regards
Click to expand...
Click to collapse
A 32bit os can only address 3.75ish GB of RAM which most just round up to 4GB anyway
Sent from my fabulous Note 4 Exynos
Thanx
Thanx for clearing this up!!
I was thinking samsung make a mistake with my note haha!
Put a extra free 1gb..
Greets
dbzgod said:
No it doesn't mean that.
Its telling you that the type of memory module being use is a 4 Gigabit, notice the lower case b, b = bit , upper case B = Byte.
Samsung is using 6x4Gigabit modules to give us 3GigaBytes of RAM. There is 8 Bits to a Byte.
And the usable amount is whats left over after they give a portion of it to the GPU for video processing.
Click to expand...
Click to collapse
But it says usable ram 2833Mb.
Is it like a typo?
_mdssakthi_ said:
But it says usable ram 2833Mb.
Is it like a typo?
Click to expand...
Click to collapse
Hi,
no, that's because some RAM is used by system.
Asking for this because there is not a single thing like armv8a written in build.prop , So i guess we r using 32 bit android, also this is in build.prop
ro.product.cpu.abi=armeabi-v7a (not armv8)
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist64= (just empty)
ro.product.cpu.abilist32=armeabi-v7a,armeabi
JJSingh said:
Asking for this because there is not a single thing like armv8a written in build.prop , So i guess we r using 32 bit android, also this is in build.prop
ro.product.cpu.abi=armeabi-v7a (not armv8)
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist64= (just empty)
ro.product.cpu.abilist32=armeabi-v7a,armeabi
Click to expand...
Click to collapse
Yes bro its OS is 32 bit. Since its processor are based on armv7. And it won't be a trouble as the chip inside is not that powerful.
Ankit_29 said:
No bro. Common its 2017 almost every device is 64 bit.
Click to expand...
Click to collapse
al the latest moto G phones have 64 bit processor and 32 bit system... and the g5 plus is not an exception.
Then the software of both devices is 32 bit? That's a little disappointing
dhk.- said:
al the latest moto G phones have 64 bit processor and 32 bit system... and the g5 plus is not an exception.
Click to expand...
Click to collapse
Sorry I read it wrong. I thought he was talking about processor. Edited my post hope so this time I am correct.:silly:
dhk.- said:
al the latest moto G phones have 64 bit processor and 32 bit system... and the g5 plus is not an exception.
Click to expand...
Click to collapse
lol that is freking weird. but that matters? i mean upto how much extent. what if we had 64 bit os?
Thanks guys, i also did confirmed this myself ,os is 32 bit only although we have 64 bit compatible processor and even 4 gb ram . I donno whats wrong with motorola....
Ankit_29 said:
Yes bro its OS is 32 bit. Since its processor are based on armv7. And it won't be a trouble as the chip inside is not that powerful.
Click to expand...
Click to collapse
Bro snapdragon 625 is not a low end chip, it's powerful enough to run ur phone smooth, and it's based on armv8a and that makes it backward compatible to armv7....so this phone is supposed to run 64 bit os , but u knw moto
JJSingh said:
Thanks guys, i also did confirmed this myself ,os is 32 bit only although we have 64 bit compatible processor and even 4 gb ram . I donno whats wrong with motorola....
Click to expand...
Click to collapse
bcz i think to unify the system for all variants. g5 plus also has 2 and 3 gb ram varints. it must be something which moto has taken into account while pushing 32 bit. so i guess we are good here.lol
rayzen6 said:
bcz i think to unify the system for all variants. g5 plus also has 2 and 3 gb ram varints. it must be something which moto has taken into account while pushing 32 bit. so i guess we are good here.lol
Click to expand...
Click to collapse
Well i think u r right, 64 bit os would b heavy for 2 gb model... i hope we will get 64 bit lineage os sonn...
JJSingh said:
Bro snapdragon 625 is not a low end chip, it's powerful enough to run ur phone smooth, and it's based on armv8a and that makes it backward compatible to armv7....so this phone is supposed to run 64 bit os , but u knw moto
Click to expand...
Click to collapse
Please let me know where I have said SD625 a "low-end chipset". As far I know and own the device and went through several test it shows armv7 (SS attached).
Ankit_29 said:
Please let me know where I have said SD625 a "low-end chipset". As far I know and own the device and went through several test it shows armv7 (SS attached).
Click to expand...
Click to collapse
broo your imei.
@rayzen6
Thank you bro. I didn't noticed it.
I have changed it. Hope no one has downloaded the pic.
Ankit_29 said:
@rayzen6
Thank you bro. I didn't noticed it.
I have changed it. Hope no one has downloaded the pic.
Click to expand...
Click to collapse
:good:
JJSingh said:
Well i think u r right, 64 bit os would b heavy for 2 gb model... i hope we will get 64 bit lineage os sonn...
Click to expand...
Click to collapse
It is not software related. If the hardware is v7, you will not get 64 bit lineage
PunchUp said:
It is not software related. If the hardware is v7, you will not get 64 bit lineage
Click to expand...
Click to collapse
SD625 is 64-bit capable.
KapilFaujdar said:
SD625 is 64-bit capable.
Click to expand...
Click to collapse
You don't get the point. Even if it is a 64 bit SOC, rest of the hardware follows v7 architecture (as SD625 is backward compatible). So it impossible to run 64 bit OS on this device.
What about ram usability
Since we are running a 32 bit Android version 4 GB ram variant is good can Android OS utilise all the 4gb of ram?
ags34 said:
Since we are running a 32 bit Android version 4 GB ram variant is good can Android OS utilise all the 4gb of ram?
Click to expand...
Click to collapse
4 GB is the maximum a 32 bit architecture can support. So yes, it's fully utilised
PunchUp said:
4 GB is the maximum a 32 bit architecture can support. So yes, it's fully utilised
Click to expand...
Click to collapse
The physically addressable memory has not much to do with the "bitness" of the architecture. Most armv7a implementations support lpae (large physical address extension) and can thus address more than 4GB. Actually, I bet this extension is used on the 4GB variant as you also have I/O mapped into the physical address space and would be unable to utilize all of the RAM.
The 32 Bit architecture only confines the virtual address space *per process* to 4GB. Since some of that address space is used to map in shared objects (libraries), stack, kernel interfaces etc. you can usually only use 2-3 GB of RAM per process. This is hardly an issue for a phone (unless you run the Facebook app ). For servers (especially databases etc.) this limitation is an issue and the reason why 64 bit architectures are used there.
AArch64 has some other benefits, such as twice the amount of general purpose registers, 64 bit wide registers (obviously) which allow for 64 bit math, mandatory extensions (no need to check, compiler can just use NEON e.g.) etc. So it's sad that Motorola is not using the SoC's potential.
As for custom ROMs: You'd need a 64 bit kernel which supports the Moto's hardware, 64 bits gfx drivers. Not easy. And then you still need to hope that you can somehow convince the bootloader to boot your kernel in AArch64 state -- which may not be possible. Thus it is extremely unlikely that you get 64 bit support from the community.
Turns out Lenovo thought it would be a great idea to use 32bit for any reason.
realy? yet still this question?
LionLorena said:
Turns out Lenovo thought it would be a great idea to use 32bit for any reason.
Click to expand...
Click to collapse
Wrong area to post this. 64 bit? Get a nexus.
Sent from my Moto G4 using Tapatalk
Why is this so absurd to consider? The device have a 64 bit CPU.
Why not use 64bit Android.
LionLorena said:
Why is this so absurd to consider? The device have a 64 bit CPU.
Why not use 64bit Android.
Click to expand...
Click to collapse
If you had searched for a little bit, you would have found that the answer was already made many times and answered in detail.
LionLorena said:
Why is this so absurd to consider? The device have a 64 bit CPU.
Why not use 64bit Android.
Click to expand...
Click to collapse
Because there's effectively no point. The SD617 has a 32-bit width data bus- a 64-bit ROM would actually yield less performance.
Why do you want a 64-bit ROM anyway? There's absolutely nothing 32-bit Android has to offer over 64-bit Android absurdly high RAM amounts (which you'll never find in a budget phone).
Some software I wanna use is 64bit only.
And what would be "absurdly high"?
Because from what I know the advised ram for 64bit is 4gb.
LionLorena said:
Some software I wanna use is 64bit only.
And what would be "absurdly high"?
Because from what I know the advised ram for 64bit is 4gb.
Click to expand...
Click to collapse
No use of 64 bit unless RAM > 4 GB. Beyond 4GB is the point where 64 bit arch starts.
Moreover does moto even release 64 bit source? I heard something similar in the potter forum.
tywinlannister7 said:
No use of 64 bit unless RAM > 4 GB. Beyond 4GB is the point where 64 bit arch starts.
Moreover does moto even release 64 bit source? I heard something similar in the potter forum.
Click to expand...
Click to collapse
Actually 3.7gb (give it or take) is the limit of 32bit.
So any value over that is valid for 64bit
And to be fair the minimum ram for 64bit would be 2gb.
They say 4gb because is where it matters most.
Since 32 can only deal with 4gb.
1 for kernel and 3 for application.
RAM consumption is huge on 64 bits system, take a look to the Nexus 5X... For an Android device running a 64 bits system you need at least 3 GB of RAM, and also, why do you want a 64 bits system if a 32 bits system offers better performance? The 64 bits system just has new type of instructions that are only for more complex calculations that not even the average user will use
LionLorena said:
And to be fair the minimum ram for 64bit would be 2gb.
They say 4gb because is where it matters most.
Since 32 can only deal with 4gb.
1 for kernel and 3 for application.
Click to expand...
Click to collapse
What software do you need to run on Android that requires 64-bit?
joeeboogz said:
Wrong place to post
Click to expand...
Click to collapse
Oh, I'm deeply sorry, it sounded appropriate to post under its own device category.
Johann0109 said:
RAM consumption is huge on 64 bits system, take a look to the Nexus 5X... For an Android device running a 64 bits system you need at least 3 GB of RAM, and also, why do you want a 64 bits system if a 32 bits system offers better performance? The 64 bits system just has new type of instructions that are only for more complex calculations that not even the average user will use
Click to expand...
Click to collapse
I need it to run 64bit only software.
negusp said:
What software do you need to run on Android that requires 64-bit?
Click to expand...
Click to collapse
Dolphin
Nintendo GameCube / Wii Emulator
Thread cleaned of rather sad tripe.
Keep it civil please...
LenAsh said:
Thread cleaned of rather sad tripe.
Keep it civil please...
Click to expand...
Click to collapse
Thanks !
LionLorena said:
Dolphin
Nintendo GameCube / Wii Emulator
Click to expand...
Click to collapse
In all seriousness, even if a 64-bit ROM were ported to the G4 the SD617 inside would struggle heavily.
You need at least an SD801 to run Dolphin anywhere near smoothly.
negusp said:
In all seriousness, even if a 64-bit ROM were ported to the G4 the SD617 inside would struggle heavily.
You need at least an SD801 to run Dolphin anywhere near smoothly.
Click to expand...
Click to collapse
Hm I see.
Well, I've figured since it was to run some 2D title I would do fine.
Since I don't have a very powerful computer either (dual core i3 3217u) and it run said title at 60fps where other 3D games won't pass 10fps.
But that's expected I guess, I think it's time to move on.
I wonder if the Moto Z is 64bit since it is SD820
Didn't yu yureka have a 64 bit is?
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...