[Q] So the Nexus 6 is 32-bit, what are the actual implications? - Nexus 6 Q&A, Help & Troubleshooting

I've seen a handful of messages both here and on reddit lamenting the fact that the Nexus 6 is a 32-bit device. What all of these posts have in common is a lack of information: what does 32-bit vs 64-bit actually mean for day-to-day use and what are the practical implications?
Will the lack of 64-bit turn out to be a big deal within 2 years? How?

there's no way of telling. the first 64-bit Android device is the Nexus 9 and it's too new to tell any implications for the next year, let alone two.
as far as we know, it's schrodinger's cat... until there are 64-bit phones in the market, we'll neither know, nor not know, what we actually get.

It took apple a year (since the release of 64bit on the iPhone 5) to enforce 64bit code change for all apps... So likely you won't be hearing about 64 bit android apps probably until early 2016. Even then, the adoption rate will be gradual and slow until the majority of 32 bit handsets are phased out.

Related

why old processor?

why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
t3rm3y said:
why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
Click to expand...
Click to collapse
because Microsoft only support the "old" snapdragon .
why apple customers don't ask them the same question , they use the same GPU as what is in 3gs a year ago ,
a second thing wp7 is developed on the snapdragon which is more than enough for now with it's improved drivers and direct x 9 support , it will perform even 2x better than a DHD with 8255 processor
t3rm3y said:
but dont want to rush into buying this phone if something better is coming.
QUOTE]
Sorry I'm the one that had to break the news, but there is always something better coming...
Click to expand...
Click to collapse
hoss_n2 said:
why apple customers don't ask them the same question , they use the same GPU as what is in 3gs a year ago ,
a second thing wp7 is developed on the snapdragon which is more than enough for now with it's improved drivers and direct x 9 support , it will perform even 2x better than a DHD with 8255 processor
Click to expand...
Click to collapse
+1 and 10char
t3rm3y said:
why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
Click to expand...
Click to collapse
I have an HD7, it is lag free and very responsive, I think the processor will be up to the task as long as the coding is optimal.
Because having the next most powerful processor isn't important. It doesn't matter what kinda specs a device is running s long as the device runs well. Apple has proved that.
And from what I have seen, MP7 runs beautifully.
Lorddeff07 said:
Because having the next most powerful processor isn't important. It doesn't matter what kinda specs a device is running s long as the device runs well. Apple has proved that.
And from what I have seen, MP7 runs beautifully.
Click to expand...
Click to collapse
True that.
Old processor?
Maybe this is a bad news to you, but it's good to me cause of my hd2.
I probably would have been crying about the same thing, if technology was growing by leaps and bounds. But its not right now, technology is kinda stagnate as of lately. Yes, the HD7 has the same processor as its predecessor the HD2, but its not a bad thing. especially now that the new rom has came out for the HD2, it feels faster than ever (you can go on the HD2 and Leo boards to attest for yourself). Another thing to remember, is that the new Windows Phone 7, is not an OS that needs a 2Ghz processor to run buttery smooth. I think that we are used to the PC ideology that the next thing should have a higher number than the last, in order to be considered and respectable upgrade. But even those Intel and AMD processors, reached their, threshold for raw computing power (for now) and the companies are now refining their codes, and drivers, in order to utilize and maximize peak performance out of what they already have. (That's why 4Ghz desktop processors aren't mainstream yet)
Another thing is the WP7 is standardized with base set requirements for internal specs. I truly doubt that you'll find a noticeable difference between all the launch devices behavior with the OS, because of their processors. The mail screen might open up a little quicker on one device, but again, that could be a driver code magic for the display adapter in a particular phone, so the one that "wins" in our mind, should have been the "newer, speedier" processor but because of the refinement and more developed drivers, the one that displayed the inbox quicker was the "older" processor. (I hope you guys got that...lol)
So what I'm trying to say at the end of the day, is it really doesn't matter about the processor spec, because whats inside the HD7 is more than plenty to run the OS and its apps very very nicely.

Do Windows Phone 7 devices need to be multi-core?

The debate is raging and is splitting the community in 2...
So I thought lets have a poll.
Let's be honest, even with a single core, WP7 devices DON'T lag. But just because having multi-core becoming a fashion statement, do WE need it?
Only spec whores care about dual core and overclocking...I've had this since December 2010, I don't get lags..WP doesn't need it...yet.
Sent from The Syndicate using XDA Windows Phone 7 App
i believe, in fact, that is a consumer gimmick.
consumers are 'bred' to think, "the bigger, the better."
and a dual-core is better than a single-core.
just isn't necessary for WP7 like it is with the fragmented Android.
so, yeah, it is all about the specs.
sh4d0w86 said:
i believe, in fact, that is a consumer gimmick.
consumers are 'bred' to think, "the bigger, the better."
and a dual-core is better than a single-core.
just isn't necessary for WP7 like it is with the fragmented Android.
so, yeah, it is all about the specs.
Click to expand...
Click to collapse
I agree...the fact about dual core processors is this - a dual core processor is just half the job done. You applications need to RECOGNIZE the other damn processor and make use of it. (1 example is the Safari for iPhone 4S that recognizes the dual core chipset and makes optimum use of it.)
Windows phone don't need dual core to run apps casue thats how its built.
Microsoft is very good with support for old hardware like you can run windows 7 on an old pentium 4 pc which is good that unlike android almost all windows phones will get newer updates as they are rolled out.
Also remember Nokia is aiming for the budget phone customers as It admitted long ago that the Higher end phone market has too much competition for it while the lower end is still a strong point for nokia, hence their partnership with MS makes sense.
And keeping costs low will help both Nokia and MS to crack the phone market a bit more
Please remember the famous Bill Gates quote...
"who would ever need more than 256kb of RAM?" ( not a direct quote, blame my memory )
The OS in the current state doesn't need that obviously, it works flawlessly. But dual-core gives us space for improvement - both in the OS and apps. So...it's not necessary, but i wouldn't go as far as to say it's not needed.
But still, we don't need to put dual-core chips in every Windows Phone. A wide range of prices, equipment etc. is definitely a perk.
What's to debate?
Do current Windows phones have multiple cores? No.
Do they work? Yes.
Case closed. On to the next thread...
My answer, Why not!? If it can be done without negatively affecting functionality, the technology should push forward leading to more opportunities for developers.
DoogieDC said:
What's to debate?
Do current Windows phones have multiple cores? No.
Do they work? Yes.
Case closed. On to the next thread...
Click to expand...
Click to collapse
No. Case is not closed. Right now, even Mango phones do not support dual core processors. That is the main reason why HTC is still using single core processor in its flagship windows phone (Titan / Ultimate).
Multi core support will come with Apollo update.

how to buy a Samsung Galaxy Tab S 10.5 with 64 bits CPU?

Hi everyone!
I want to buy the tablet Samsung Galaxy Tab S 10.5 for its amazing screen, but the 64bits world is already here.
I checked that the only versions with a 64 bits cpu are just SM-T805S, SM-T805K, and SM-T805L with the Exynos 5433 in Korea.
Does anyone know where to buy it without going in person to Korea?
Or does anyone know if there is another version(s) with 64bits cpu and where to buy it?
Thanks!
Why do you want a 64 bit CPU?
codified said:
Why do you want a 64 bit CPU?
Click to expand...
Click to collapse
I'll bet he doesn't even know. Saying 64 "bits" tells me he isn't very knowledgeable with technology. He just heard it from somewhere.
bloodrain954 said:
I'll bet he doesn't even know. Saying 64 "bits" tells me he isn't very knowledgeable with technology. He just heard it from somewhere.
Click to expand...
Click to collapse
Or you can just be nice and explain to him why the 64 bit version won't garner him any real world benefits right now...:highfive:
wow!! how nice people are around here!!!
even if I dont have very high knowledge in technologies, you just have to write on google "64 bits android" to really know that 64 bits in android is not making any high difference now. So it doesnt really matter and whoever can know that. But at the same time, you can also see that there are some improvements and other "stuff" (typical word that some of my kind use) that will be useful soon while the rest of the techolopy (or technoloki... or how was the word? oh yes! = t-e-c-h-n-o-l-o-g-y ) is progressing.
I am not very advanced and thats why I am writing here, sorry that I didnt passed the test to write here.
Anyway, my only stupid reason why I want a 64 bits CPU is because of the money. Coz I dont have a lot. And I am the kind of person that tries to buy something that will last many years coz I cant afford to change deviced regularly. I bought my last laptop 10 years ago, it worked 7 years... and since then, there is no laptop. But my personal life is not the matter, and I am not asking about laptops or why I want a tablet now.
But I need a tablet that will last untill burns, and the "64bits world" is starting developing and in two years or so... I dont want to have a tablet that I cant use with something because 32 bits doesnt supported... but this is just an opinion anyway...
All 'new' tablets will last for a long time. 64 bit won't make a difference. If you feel it does, get the nexus 9. But even Google knows 32bit devices won't be going anywhere for a LONG time. Hence the reason the Nexus 6 is "only" using a 32bit processor. I'll be busy currently enjoying my brand new 32bit tablet
Just order online nuff said!
Sorry, didn't mean to make you feel stupid. I ask the question because a lot of people go blindly seeking the latest marketing term without realising what it means
64-bit processors are the new craze since Apple released one and had all the publicity about it
But it doesn't add much at all, and it won't future-proof your phone like you might think it would
This is a good article to read:
http://www.androidauthority.com/note-4-64-bit-32-bit-android-l-536280/
Anyway, the Exynos 5433 processor that you are talking about is technically 64 bit architecture but will only run in 32 bit mode, so you aren't really getting any of the advantages of 64 bit. You will have to wait for the Exynos 7420 for true 64-bit performance.
codified said:
Sorry, didn't mean to make you feel stupid. I ask the question because a lot of people go blindly seeking the latest marketing term without realising what it means
64-bit processors are the new craze since Apple released one and had all the publicity about it
But it doesn't add much at all, and it won't future-proof your phone like you might think it would
This is a good article to read:
http://www.androidauthority.com/note-4-64-bit-32-bit-android-l-536280/
Anyway, the Exynos 5433 processor that you are talking about is technically 64 bit architecture but will only run in 32 bit mode, so you aren't really getting any of the advantages of 64 bit. You will have to wait for the Exynos 7420 for true 64-bit performance.
Click to expand...
Click to collapse
You are right, 64-Bit processors are only really beneficial if you have the added memory to make good use of them, Apple's was only a gimmick when you consider they still only come with 1gb of RAM whereas most other devices not coming from Apple have 2gb or more.
lorinkundert said:
You are right, 64-Bit processors are only really beneficial if you have the added memory to make good use of them, Apple's was only a gimmick when you consider they still only come with 1gb of RAM whereas most other devices not coming from Apple have 2gb or more.
Click to expand...
Click to collapse
Thats not true. A 64-Bit processor have more registers and handle processing generally faster than the 32-Bit, even if you don't run any 64-Bit code on it.
caravana said:
Thats not true. A 64-Bit processor have more registers and handle processing generally faster than the 32-Bit, even if you don't run any 64-Bit code on it.
Click to expand...
Click to collapse
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
lorinkundert said:
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
Click to expand...
Click to collapse
RAM has nothing to do with the processors architecture, and with all due respect, your experience is not an argument. About the ARM 64-Bit architecture I can quote the AnandTech guys here:
Architecturally, the Cortex A57 is much like a tweaked Cortex A15 with 64-bit support. The CPU is still a 3-wide/3-issue machine with a 15+ stage pipeline. ARM has increased the width of NEON execution units in the Cortex A57 (128-bits wide now?) as well as enabled support for IEEE-754 DP FP. There have been some other minor pipeline enhancements as well. The end result is up to a 20 - 30% increase in performance over the Cortex A15 while running 32-bit code. Running 64-bit code you'll see an additional performance advantage as the 64-bit register file is far simplified compared to the 32-bit RF.
Click to expand...
Click to collapse
And here AnandTech does detailed arm 32bit vs 64bit performance comparison:
The conclusion? There are definitely reasons outside of needing more memory to go 64-bit.
Click to expand...
Click to collapse
So yes, the ARM 64-bit architecture is generally faster than the 32-bit counterpart, because of enhancements that does not depend on the amount of RAM available.
lorinkundert said:
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
Click to expand...
Click to collapse
I have a feeling you don't.
to take full advantage of a 64-bit processor you'd need an operating system that is also 64-bit as well, more than 4GB of ram (since 32-bit has a limitation of 4GB ram), and apps that are 64-bit.
For the pace of technology I'd say applications in the server-world (SQL and stuff) have fully taken advantage of 64-bit architecture for 10ish years, desktops maybe in the past 6 or 7 years.
It really depends on what type of programs you're using because certain things use the CPU, other's use the GPU. This being for games and such.
Apps like MX Player would take advantage of the CPU. ART in Android Lollipop will do us well. Bottom line- way too many factors but I don't think anything coming out on Android will make good use of a 64-bit architecture for a few more years. I mean, anything that would need 64-bits is really a battle with "is this a battery-friendly app or some intense app that should really be on a desktop?" or something. 64-bit just isn't needed right now. Personally, I like when developers focus on making programs that work best in a low power environment like a mobile device architecture.
You're buying an octacore tablet which is the most high-end device right now. I'd say Android and the hardware won't get much more fancier fancier for the next year or 2 and, TBH, this tablet won't start feeling sluggish for maybe 4 or 5 years as far as technology typically progresses.
Here's a video by Linus Tech tips detailing 64 bit vs 32 bit in a more layman term:
https://www.youtube.com/watch?v=IknbgnJLSRY
Thanks for your messages.
After reading all and watching videos... I see that 64bit is not a big difference now, but it won't be for a very long time either... so it will be a little bit like the current situation in deskpots: even if 64bits is generally seen in everything, everything (almost) is still compatible with 32 bits and companies still give support to 32 bits...
and, on top of everything, if the "highest" option with this tablet is the exynos 5433 64 bits but only runs in 32bits mode... it makes no sense.
so, according to this, my question would be: how this tablet is going to handle Android Lollipop with the exynos 5420? I mean, how does the exynos 5420 (32 bits) handle android lollipop (64bits)?
There is a 64 bit option on my kernel configuration file for Note Edge 5433 and if enabled + unlocked 64 bit bootloader + firmware = winner. The 5433 Tab S is the same and has been deliberately crippled by Samsung to keep it on par with the crappy Snapdragon 805 which won't be ready for 64 bit until mid-next year. Even then, SD performance and potential doesn't even come close to the Exynos.

is the project dead?

no updates
diehard2013 said:
no updates
Click to expand...
Click to collapse
Becauase JIDE was dead.
come again
Totally dead. They already give official statement in their Facebook Page
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
JIDE is NOT dead - just targeting enterprises (not ordinary users)
diehard2013 said:
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
Click to expand...
Click to collapse
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
PGHammer said:
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
Click to expand...
Click to collapse
in vino veritas, acta non verba..
diehard2013 said:
in vino veritas, acta non verba..
Click to expand...
Click to collapse
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
CookyMonzta said:
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
Click to expand...
Click to collapse
It's not that anything necessarily is WRONG with RemixOS - nobody has said that (not me - or anyone else, for that matter) - it's simply overkill for what most users want. It's like the market for high-end GPUs (without the price factor); it's still a niche market. As good a graphical environment as RemixOS - and Marshmallow itself, for that matter - is, why have things moved north (on actual Android devices) and stayed south (on Windows-based Android emulators)?
As the default OS (as is the case with devices), unless you are talking the low and cheap end, N is the new JellyBean - not MM. (Note that instead of doing OTAs for the existing J3 - which is running MM - Samsung chose a hardware refresh instead; this is despite the J3 pre-refresh being barely two years old - and not even that in North America,) As an emulator core (alongside or within Windows), the tendency is STILL to prefer lightweight emulators - which still means KitKat or JellyBean - primarily so Windows (the core OS) can keep most of the resources itself. RemixOS Player didn't require vmWare OR Oracle VirtualBox - just like most of the KK or JB-based emulators; hence none of them are shackled to HAXM. I RAN RemixOS Player because I could take higher-end Android games to it - which wasn't - and still isn't - the case for most emulators - with OR without HAXM. However, gaining that S7 did away with my own need for a high-end emulator. (Remember, the S7 - while not shipping with N - instead, it shipped with MM - now can be blanked and factory-type N-ified using nothing more complicated than either Odin or Heimdall.)
What is further trouble for JIDE is that N is expanding at the low-end. I mentioned earlier Samsung's J3 refresh (which is now N-based - not the MM of the previous version); the same is true of Lenovo's Tab 3 Essential - a refresh of the earlier Tab 2 series of tablets and phablets. Unlike the Tab 2 (which started at KK and went only to L - with only the phablets going beyond L with community ROMs, and typically in languages OTHER than English), the Tab 3 Essential has changed SoCs from MediaTek (MTK) to Qualcomm - they also ship with N out of the box. Amazingly, the price tags went nowhere compared to the MTK predecessors - even the largest of the new line is BARELY $100 from Amazon - including shipping for non-Prime customers. With N for cheap, whither RemixOS? (Basically, RemixOS is being made moot by N on devices - not nice, but there it is.)
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
KingdomMan3 said:
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
Click to expand...
Click to collapse
You mean SW or HE'S?
anyone still usinng it?
hi guys. anyone still using it? is it stable enough? im thinking to install it on my pixel c tablet
These are project for which
---------- Post added at 02:56 AM ---------- Previous post was at 02:54 AM ----------
Give me a link pixel experience Android p for resume 4x
Hey guys,
I'm planning going back to Remix OS 3.0 (MM) on my Pixel C since AOSP really sucks for a lapotp like tablet like the Pixel C.
But I am worried about Security... Is it possible to use Antivir software like Avast to compensate the missing security updates?
If yes, can you recommend me an antivir app?

OS 32-bit or 64-bit

Can anybody please run a benchmark and confirm if the OS is 32 bit or 64 bit? I know Snapdragon 625 supports 64 bit OS. But Motorola put 32 bit OS previously on G5 plus. So just want to confirm.
jtrvk said:
Can anybody please run a benchmark and confirm if the OS is 32 bit or 64 bit? I know Snapdragon 625 supports 64 bit OS. But Motorola put 32 bit OS previously on G5 plus. So just want to confirm.
Click to expand...
Click to collapse
32-bit.
Way to disappointing that G5s plus got 32bit while it can run 64bit perfectly -.- Lenovo really sux at software handling for sure camera quality ain't as expected way to much yellow color in low light pics and way to much sharpness in day light photos no natural colors are to be found in pics -.- my Nexus 5 can do better than this one imo and lastly what disappointed me was that in LTE network sim 1 net is always turned on in background I checked developers option agressive data is turned off but net is always on which tolls on ür price if u don't have free data which I usually don't since I'm always surrounded by wifi 24/7 my over all impression about this device is that it's only good at performance and battery life
Yes, I just spent a fun morning trying to get the Adfree YouTube apk working before I discovered that 64 bit architecture was the wrong one to be using. Banging my head against a wall because the Snapdragon 625 is 64 bit so there was no logic as to why it'd be the wrong one.
Mind you, I did like the post above mine - all this phone has got going for it is performance and battery life. Well, as I couldn't really give two hoots about anything else other than performance and battery life, it looks as if I've made a good choice for my new phone...
With oreo being 64bit we should see the real full utilization of this CPU when we get the update. I just got my confirmation that my phone shipped and i cant wait to mess with it.
SynisterWolf said:
With oreo being 64bit we should see the real full utilization of this CPU when we get the update. I just got my confirmation that my phone shipped and i cant wait to mess with it.
Click to expand...
Click to collapse
what do you expect to happen with 64 bit? code is larger and you can access more than ~4 gigs of memory; handy on a 3gig phone.
Webern said:
what do you expect to happen with 64 bit? code is larger and you can access more than ~4 gigs of memory; handy on a 3gig phone.
Click to expand...
Click to collapse
Power efficiency and preformance. I also bought the 4gb ram version.
Sent from my Glade[emoji768] Plugins
SynisterWolf said:
With oreo being 64bit we should see the real full utilization of this CPU when we get the update. I just got my confirmation that my phone shipped and i cant wait to mess with it.
Click to expand...
Click to collapse
I thought Motorola has a put a hardware limitation by limiting the size of one of the buses to 32 bit or I could have totally misread something
Webern said:
what do you expect to happen with 64 bit? code is larger and you can access more than ~4 gigs of memory; handy on a 3gig phone.
Click to expand...
Click to collapse
64-bit required for Google camera HDR+ mod specifically
jtrvk said:
I thought Motorola has a put a hardware limitation by limiting the size of one of the buses to 32 bit or I could have totally misread something
Click to expand...
Click to collapse
I was under the impression that google will not support a 32bit Oreo and Motorola said this will be updated to Oreo. Do you remember where you saw the limitations?
Sent from my Glade[emoji768] Plugins
SynisterWolf said:
I was under the impression that google will not support a 32bit Oreo
Click to expand...
Click to collapse
That is incorrect. Android Oreo supports 32-bit devices just like always.
SynisterWolf said:
I was under the impression that google will not support a 32bit Oreo and Motorola said this will be updated to Oreo. Do you remember where you saw the limitations?
Sent from my Glade[emoji768] Plugins
Click to expand...
Click to collapse
Sorry mate, not able to find it now. Will update as soon as I find the link
As I thought, I had misread something. The decision to use 32 bit comes from G5 where 2 GB and 3 GB versions could not make use of 64 bit OS. So they decided to go with 32bit altogether for G5 series. Maybe that's the reason it's still 32 bit on G5s series as well? Business decision wise it makes sense :| and for that price we can't really complain
jtrvk said:
Sorry mate, not able to find it now. Will update as soon as I find the link
As I thought, I had misread something. The decision to use 32 bit comes from G5 where 2 GB and 3 GB versions could not make use of 64 bit OS. So they decided to go with 32bit altogether for G5 series. Maybe that's the reason it's still 32 bit on G5s series as well? Business decision wise it makes sense :| and for that price we can't really complain
Click to expand...
Click to collapse
Good to know. Thank you.
Sent from my Glade[emoji768] Plugins
SynisterWolf said:
With oreo being 64bit we should see the real full utilization of this CPU when we get the update. I just got my confirmation that my phone shipped and i cant wait to mess with it.
Click to expand...
Click to collapse
Do join our telegram development group. We have a couple test builds out too. Just text me @Manan44 on telegram.
After a lot of reading on 64bit vs 32bit on MSM8953 this SoC doesn't benefit to much while running a 64bit OS. This SoC was one of the earliest 64bit SoC that Qualcomm offered (for sale in Feb 2016). Comparing benchmarks (i know benchmarks arent the best way to compare devices, but i needed a repeatable source so that's what i used.) on both single core and multi core the overall efficiency was a minimal gain. like 1-3%.
It is smarter from a business stance that they would stick to 1 base for their G line and they picked 32bit. I was looking forward to having a 64bit device but it will have to wait.
Webern said:
what do you expect to happen with 64 bit? code is larger and you can access more than ~4 gigs of memory; handy on a 3gig phone.
Click to expand...
Click to collapse
Haha to be accurate 32Bit is more on side of saving battery and giving decent performance , 64Bit is about giving more performance and decent battery life , And last x86 is lot on performance and below avg with battery life
And I really wants 64Bit just to be able to run Google camera -.- and hope ported one to work well T~T
jtrvk said:
Can anybody please run a benchmark and confirm if the OS is 32 bit or 64 bit? I know Snapdragon 625 supports 64 bit OS. But Motorola put 32 bit OS previously on G5 plus. So just want to confirm.
Click to expand...
Click to collapse
is Android OS 32bit on 64bit CPU Arm, not is 64bit OS
but is support OS
clriboli said:
is Android OS 32bit on 64bit CPU Arm, not is 64bit OS
but is support OS
Click to expand...
Click to collapse
Yes that is the point. Even though the processor supports 64-bit OS, moto decided to put 32-bit OS (understandable business decision). I was just curious to know since Google Camera HDR+ currently works only on 64-bit OS.
Reson behind 32 bit os is as the architecture of cpu is 64 bit the 32 bit os will take 32 bit of thread space so 2 threads or two operations can run simultaneously boosting the device performance and battery whereas compared to 64 bit os will take 64 bit thread size and more ram and battery compared to 32 bit thats the reason behind 32 bit os but afterall dosent matter 4 gb ram and that snapdragon 625 processor can handle but battery can be a concern for heavy users.

Categories

Resources