Database Develop

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.

Performance of last year WP devices?

Considering the availability of snapdragon 800 devices (such as Lumia 1520), is a device like Lumia 920 (or HTC 8x) still powerful enough to handle all games and apps?
I'm thinking of getting a secondary windows phone. I wonder how last year's devices perform these days.

Right now? Easily. The high-end launch devices (Lumia 92x, HTC 8X, Samsung ATIV S) are still plenty powerful for all apps on the market. The newest high-end phones are definitely more powerful, but aside from maybe a short reduction in loading times and faster bootup, plus of course better performance in JavaScript and so on, it shouldn't be a problem. Apps are pretty much required to run well even on 1GHz dual-core CPUs, like the mid-to-low-range phones have; 1.5GHz dual-core (like the high-end launch phones) is plenty.
Now, eventually that will no longer be the case, and the launch phones will go obsolete before the new ones. But the high-end launch phones will probably last longer than the low-end ones of the new generation anyhow, and the low-end launch ones will be the first to go. Microsoft will want to avoid that happening for as long as possible, so you should be good for a while.

GoodDayToDie said:
Right now? Easily. The high-end launch devices (Lumia 92x, HTC 8X, Samsung ATIV S) are still plenty powerful for all apps on the market. The newest high-end phones are definitely more powerful, but aside from maybe a short reduction in loading times and faster bootup, plus of course better performance in JavaScript and so on, it shouldn't be a problem. Apps are pretty much required to run well even on 1GHz dual-core CPUs, like the mid-to-low-range phones have; 1.5GHz dual-core (like the high-end launch phones) is plenty.
Now, eventually that will no longer be the case, and the launch phones will go obsolete before the new ones. But the high-end launch phones will probably last longer than the low-end ones of the new generation anyhow, and the low-end launch ones will be the first to go. Microsoft will want to avoid that happening for as long as possible, so you should be good for a while.
Click to expand...
Click to collapse
Thanks for such a detailed and helpful response. Much appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app

You're welcome! There's other concerns besides the raw CPU power to consider, of course, such as the 1520 having a 1920x1080 resolution screen and BT 4.0 with low-energy mode, and newer phones will probably have more RAM and Flash storage as prices per gigabyte for such things continue to fall. Still, I've been very happy with my ATIV S (SGH-T899M) even though it's missing a few things that the newer phones have.
Oh, and while I appreciate the post, there *is* a Thanks button too... Much quicker!

GoodDayToDie said:
You're welcome! There's other concerns besides the raw CPU power to consider, of course, such as the 1520 having a 1920x1080 resolution screen and BT 4.0 with low-energy mode, and newer phones will probably have more RAM and Flash storage as prices per gigabyte for such things continue to fall. Still, I've been very happy with my ATIV S (SGH-T899M) even though it's missing a few things that the newer phones have.
Oh, and while I appreciate the post, there *is* a Thanks button too... Much quicker!
Click to expand...
Click to collapse
Important things to consider. thanks again! (Thanks button clicked) I have one last question. Do you see any advantages in owning a Phablet Windows Phone device over a Phone?
Does it have any extra functionalities, or anything unique that makes it special aside from having more tiles on the home screen? That's something that I'm really curious about

I don't own one myself, but the only thing that comes to mind is the ability to get a bunch more tiles on the Start screen (three "normal" columns, plus each tile is shorter as well - they're still square, after all - so you get more of them vertically at once). That's a nice feature, one which I enabled (via registry hack) on my ATIV S (at 4.8", it's just below the 5" cutoff for that feature to happen automatically) as soon as I got GDR3. Aside from that, and the phenomenal resolution of the 1520, though, I'm not aware of anything much.

GoodDayToDie said:
I don't own one myself, but the only thing that comes to mind is the ability to get a bunch more tiles on the Start screen (three "normal" columns, plus each tile is shorter as well - they're still square, after all - so you get more of them vertically at once). That's a nice feature, one which I enabled (via registry hack) on my ATIV S (at 4.8", it's just below the 5" cutoff for that feature to happen automatically) as soon as I got GDR3. Aside from that, and the phenomenal resolution of the 1520, though, I'm not aware of anything much.
Click to expand...
Click to collapse
That's interesting, i didn't know registry hacks for WP8 devices are possible. Can it be done for all devices with GDR3?
Sent from my Nexus 7 using XDA Premium 4 mobile app

Nope, I'm afraid they're still limited to Samsung's WP8 lineup. Check the interop-unlocks thread in my sig for more info.

GoodDayToDie said:
Nope, I'm afraid they're still limited to Samsung's WP8 lineup. Check the interop-unlocks thread in my sig for more info.
Click to expand...
Click to collapse
Then i may end up buying the Ativ S. Thanks man, I learned a lot from you. XDA needs more guys like you
Sent from my Nexus 7 using XDA Premium 4 mobile app

Well, we're still looking for unlocks in other lines (Lumias especially, given their popularity, but others too). You really can't give timelines on that kind of thing, though, and Samsung is already trying to break the one we have.

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?

I think we should have opened a discussion on some important points,

I think we should have opened a discussion on some important points,
1 adaptive storage, which I will draw on some specific model as our most has active others such as moto one, G6, and G7, motorcycle c, motorcycle and, we have to see if there is any limitation of hardware or software only thing, because this speech that Google does not support or that the cards do not have enough quality, not real, because every month we have models released with updated with this support.
2, dp vs dpi = 480 standard and high for this screen size, the base of android and 160, then it means that we have a base x3 of scale, this is legal for a worse point on the other, as this increases a lot more quality, the more the information displayed. You gain large, borderless icons plus loses in detail. Solution likely to set screen resolution lower than 540p, to have equibrio between size and quantity, or @ 1080p to have full amount of pixel there is screen, but if it is in stock has to activate a third party lacucher, because Motorola laucher does not support this pattern .
3, gpu is clock different from the specified, because it was to have maxima clock of 850mhz, more in the last version that I did read in the android with rom stock it was in setada the clock max 700mhz, more main problem was that even taking Max to 700mhz, in a good part of game and app it gets 450 MHz with low FPS content, even if it is not in the FPS limit of the game or application, it did not raise clock to its maximum .. probable solution for who has root, exchange governor gpu using kernel auditor, by order or by performance
4, this is less important and only one more doubt, mixed with indignation,. Because Samsung and some other privileged manufacturers can use 32bit android on their handset, which infinitely lighter and less consumer ram. What the 64bit, which Google has been forcing developer to use since the Android ..
It seems to prank some more Samsung with snapdragon 425 and 2gb of ram and HD + screen with 32bit android has usability, and multitasking better than our device that has 630 and 3gb of ram more with Android 64bit.
Mano has 5 years I see Google saying that there is no more Android 32bit, even so every year there is cell phone with input clip using Android 32bit fighting from equal to equal with Android intermediate with Android 64bit.
And I'm sorry if I said some nonsense, I do not understand much about development, but I had several devices and always made modifications, and always following the tropics and the developers

Ermes.mt/brasil said:
I think we should have opened a discussion on some important points,
And I'm sorry if I said some nonsense, I do not understand much about development, but I had several devices and always made modifications, and always following the tropics and the developers
Click to expand...
Click to collapse
So.... What are you trying to accomplish with this "discussion" that is probably already addressed in another thread??

jbaumert said:
So.... What are you trying to accomplish with this "discussion" that is probably already addressed in another thread??
Click to expand...
Click to collapse
yes and no, yes, because all the tropics in general seek 3 things (support, features or performance), and I'm approaching this three point, and yes! and discussion then everyone is welcome to try on a chair to have a coffee and speak their point of view .. #not much sound on this device and if we do not talk and we work together on it, we will not get a survival of it