Blue Sky Device ideas - Off-topic

Hey everybody, I wanted to see if some of the regulars here might wish to join me in a thought experiment.
I've been given an opportunity to give input on a new tablet that is being developed, with the two guiding principles being future-proofing and maximum user control. I am wondering, from a dev point of view, what options or features would you find desirable. I will give you some of the pre-pre-alpha specs (enough so my cohorts don't shank me for saying too much)
8.9" screen
x86 CPU (Skylake)
64-bit UEFI BIOS
64GB storage
SDXC (2TB support)
8GB LPDDR4E
USB 3.1-B x2
Bluetooth 5.0
WACOM active stylus
6000mah battery
Qualcomm Quick Charge 3.0
From what I know so far, it is going to involve some heavy customization on the package (mostly because of what I haven't yet mentioned, so they have 6-9 months of flexibility if we want to make changes. I am trying to talk them into open-sourcing the whole shebang (I'd kill for any device with a truly FOSS BIOS, so I can multi-boot and et cetera)
Any feedback is appreciated.

Related

[Q] HP Touchpad + Android or A1CS?

I'm looking at buying an Android tablet around the £100 mark, and think I've narrowed it down to either a HP Touchpad from ebay (dual boot with Android), or a A1CS Android tablet like this:
http://www.amazon.co.uk/A1CS-FUSION...1_8?s=computers&ie=UTF8&qid=1358246198&sr=1-8
I can't seem to find any decent comparisons for the Touchpad + Android up against dedicated Android tablets. Does anyone have any experience? Would I be better off going for the A1CS if Android is all I want, or does a rooted Touchpad + Android out perform them?
Touchpad is much better in my opinion.
Dual core CPU, double the ram (1GB is needed really), much more dev support, running Jellybean.
theronkinator said:
Touchpad is much better in my opinion.
Dual core CPU, double the ram (1GB is needed really), much more dev support, running Jellybean.
Click to expand...
Click to collapse
I agree agree completely. You'll have a unique dual boot tablet.
Ok thanks guys, sounds pretty conclusive!
I've been through 3 Android phones and another tablet, and the TouchPad with CM9 is the most stable experience I've ever had. It's shocking to see such a perfect Android experience from a device that was never intended to run it. The devs here are fantastic and so is the XDA community. And the wireless charging dock is awesome. Every time I need my tablet it's 100% charged... everyone who sees it is jealous.

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.

Your very own Mobile Internet Device

I am happy to announce the project I have been working on. I do not know what direction it will take from here but I thought it was a good time to show it.
A MID, UMPC, tablet, smartphone - anything you want it to be. This is a kind of hybrid between phonebloks/project ara and the nokia n900 series
The wiki should guide you through step by step and answer most questions you may have. I have always thought one of the most important parts of this project is being able to teach others to do this and make it as accessible as possible.
As the wiki mentions, please raise a ticket on the issue tracker if you have a problem. But if you just want to talk about it this thread would be fine and I will try to get back to it from time to time.
Special thanks to people on this forum specifically who made all those Windows Mobile editing toolkits way back and helped me realize what was possible with pocketable devices and move on from there.
Link to SFS MID wiki
I thought I would provide an update here. The project is still ongoing with a mainboard transition from the Raspberry Pi to the Odroid C0 SBC.
The hardware and software has come a long way making for a pleasant experience to use but yet enough flexibility for most situations and users.
As always, you can post here or on the issue tracker if you have any questions or just want to talk about MID development. Thanks and good luck.
This is a 6 month update. The project continues with a switch to the Lattepanda x86 SBC.
More positives than negatives come with the new ecosystem and the future is bright. It is hoped that with the x86 technology the project will become relatable to more people and the architectural reliability will prove to be an advantage.
You can always post here or on the issue tracker if you have any problems, questions or speculation on the future of MID development. Thanks and good luck.
This is one more 6 month update. I am using the Lattepanda x86 SBC exclusively now.
The layout of the devices has been redesigned to be more like a smartphone and there is a new shell available for 3d printing. In addition, the software has undergone an update and there are new development notes including testing with some Raspberry Pi 4 prototypes which ended up being too hot and using too much power. Finally, there are 5 new scripts uploaded and one included with the MID software which deals with multitouch gaming.
It works well but I am hesitant to call the project finished so if you have suggestions let me know.
Hello and welcome to another update on this longrunning project.
The launch of the Raspberry Pi 4 came and went without offering any power savings so the project continued on without it using some alternative platforms. On the dual goal of being able to play PC games, it is only until recently that the 8GB Pi 4 had that potential. Unfortunately there is not enough overhead for Linux gaming even on most low end x86 PC platforms so there is little hope current Pi versions will make for a good PC gaming experience.
If you read the development notes you will see some experiments with portable PC stick hardware running games such as Kerbal Space Program on Linux but those devices were a dead end as far as power savings go. Both in terms of lack of power saving features and in idle and load power draw.
Currently there does not seem to be a small x86 device that has working suspend/sleep/standby mode in Linux which renders the dual goal of a Linux smartphone device that can play modern PC games unattainable.
The VIM3 SBC does have a working suspend mode as well as a wide 5-20v input. This allows for much more battery power and energy without the corresponding
wiring complexity and loss of efficiency that you would have in a device that required "stepping down" the voltage to 5V. "Stepping up" from traditional smartphone and tablet batteries comes with it's own challenges as well. Namely, the effective current limit, maximum available power and conversion inefficiency from such low voltage batteries.
On the gaming front all hope for portable gaming is not lost. I have uploaded a bonus version of Retroarch with VIM3 support to the releases area as well. This release is intended for and works well for the older console systems.
Maybe one day we can get a device with 8GB+ RAM that can play PC games and go to sleep. Until then keep building!
I thought I would slip in and give an update just short of a year. A few patches may be still to come anyway.
The goal of a PC gaming phone-like portable has been largely attained. The Lattepanda Alpha SBC specifically has 8GB RAM and can suspend to save power. With a MID based on it you can do the kinds of things you would do on a smartphone as well as play PC games with a gamepad on the go, keyboard/mouse while docked or perhaps even with the touchscreen. The Lattepanda Delta can suspend and has 4GB RAM and is a cheaper alternative. Recent PC games can be played successfully but I would recommend something like a Steam Deck for cutting edge games. If using Android apps is something you would require in a personal mobile device then the large RAM of the Alpha is something that should make emulation possible. When finished you can put the device to sleep and put it in your rather large pocket.
There is something to be said for a smaller more manageable mobile device that is more the size of a smartphone. Even if that means gaming capability is compromised. The VIM 3 is smaller than the Lattepanda Alpha/Delta and has different USB functionality making for a smaller and simpler overall MID. This is more of a device that you can put in your pocket and hopefully not have it break. You can put a plastic shell around it like a commercial device but you will find that one large enough to give good protection makes the MID too large. I do not consider this a big deal since one of the goals of the project is to put more control into the hands of the user and this includes the realm of repairability. In other words if it breaks you can fix it.
Thus 2 parallel ARM and x86 codebases are being maintained for now. Extensive troubleshooting has been undertaken to fix some long standing hardware
stability problems on both MID platforms as well. Addditionally, all main wiki pages have received an update. Finally, another bonus compiled version of the latest Retroarch source has been added that focuses on PS1 emulation.
A special message for XDA Developers users. Don't throw away your Android phones just yet. As inexpensive as cellular plans are you can keep your phone and tinker with something like this too. But remember that when the automobile was first developed it was considered worse than the horse. Over time it was refined and eventually surpassed the horse as a means of transportation. I think as computer parts become more commoditized ever time something similar will happen and nothing will be able to stop us from putting together a phone ourselves.
I am not sure where it is going to go from here but I look forward to using the devices now that the dream has come true.

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

Categories

Resources