Database Info

Android N

Hey did anyone install android N preview 1? I haven't installed it cause it only released a preview 1, Maybe i'll installed it when preview 5 is released.
I'll link a source down below if anyone is wanting to install it
http://www.extremetech.com/mobile/224457-how-to-install-the-android-n-developer-preview-on-your-device-right-now

This is only for nexus devices
Enviado desde mi XT1563 mediante Tapatalk

as its name suggests, it is only for developer, for testing their apps etc. if you're not a developer, it is better to wait for a final release. unless you like living with bugs, crashes and other possible instability issues.

How likely will the MXP get an official N release from Motorola?

Holoryn said:
How likely will the MXP get an official N release from Motorola?
Click to expand...
Click to collapse
I don't think they will, i mean, yes MXP has 5.5 inches and 1080p screen but the RAM and processor is kinda weak for android N :/. but what do i know, I maybe a bit good at tech but i'm not a tech guy, but let's keep our hopes up that Lenovo will release android N for MXP

I have been wondering about this too but its too early. It is a preview of N and the android development platform for android N or whatever it will be called called is not yet released - after google I/O in may .....may be . In six months or more (alot more ) there something like cm 14 or other rom. Be patient

HerySean said:
I don't think they will, i mean, yes MXP has 5.5 inches and 1080p screen but the RAM and processor is kinda weak for android N :/. but what do i know, I maybe a bit good at tech but i'm not a tech guy, but let's keep our hopes up that Lenovo will release android N for MXP
Click to expand...
Click to collapse
I'm fairly confident Motorola will provide an N upgrade for lux. In any case, you'll get it with custom ROMs (after the final N build is ready). The CPU and GPU are perfectly fine for the purpose and I expect it have zero difficulties with it. I plan to continue supporting this device till at least 2018.

squid2 said:
I'm fairly confident Motorola will provide an N upgrade for lux. In any case, you'll get it with custom ROMs (after the final N build is ready). The CPU and GPU are perfectly fine for the purpose and I expect it have zero difficulties with it. I plan to continue supporting this device till at least 2018.
Click to expand...
Click to collapse
Yay!! :highfive:

The host of this thread wanted to get someone try it and let him know what it is possible or not/
right?

I hope it's 64bit

bablu048 said:
I hope it's 64bit
Click to expand...
Click to collapse
Nope, it will stay 32 bit. There will be no performance difference either way. I also will support the X Play until it can't anymore

GtrCraft said:
Nope, it will stay 32 bit. There will be no performance difference either way. I also will support the X Play until it can't anymore
Click to expand...
Click to collapse
yeah, i know 32-64 bit doesn't change the performance much. 64 bit just supports more RAM and has more address lines.
i hope to do the same, but building from scratch is very confusing when you are a beginner. still trying though.

bablu048 said:
yeah, i know 32-64 bit doesn't change the performance much. 64 bit just supports more RAM and has more address lines.
i hope to do the same, but building from scratch is very confusing when you are a beginner. still trying though.
Click to expand...
Click to collapse
PM if you need help. Would like to help

Not so quick question:
When Google releases a AOSP -source code ect - for android N or any other version CM team make a basic CM version - a core of the OS so to speak - so that people who maintain a given device like MXP can adapt it to work. And that takes time....I over simplified the whole process - which surely includes lots of coding and magic - but all in all is this how it it's made ?

Chaotick said:
Not so quick question:
When Google releases a AOSP -source code ect - for android N or any other version CM team make a basic CM version - a core of the OS so to speak - so that people who maintain a given device like MXP can adapt it to work. And that takes time....I over simplified the whole process - which surely includes lots of coding and magic - but all in all is this how it it's made ?
Click to expand...
Click to collapse
We need a final N and caf being updated. Then when a rom updates to that we can try building it for Lux (Code name Moto X Play) and fixing everything. Then Motorola will update it so we can use the blobs and kernel to make it even more stable.

You can look on motorola upgrade support page, there is info fo several models and android versions. We cant be sure if N will come to MXP, but Im sure, Motorola has great support and its normal, that phones gets two major upgrades. So MXP started on L, moved to M and N is very likely.

squid2 said:
I'm fairly confident Motorola will provide an N upgrade for lux. In any case, you'll get it with custom ROMs (after the final N build is ready). The CPU and GPU are perfectly fine for the purpose and I expect it have zero difficulties with it. I plan to continue supporting this device till at least 2018.
Click to expand...
Click to collapse
well i have to keep my moto x play as long as I can, maybe for 3-4 more years because I just bought it :/ and I really hope lenovo release android N for MXP.

HerySean said:
I don't think they will, i mean, yes MXP has 5.5 inches and 1080p screen but the RAM and processor is kinda weak for android N :/. but what do i know, I maybe a bit good at tech but i'm not a tech guy, but let's keep our hopes up that Lenovo will release android N for MXP
Click to expand...
Click to collapse
its obviusly mxp will get android n, its a 2015 smartphone ... general mobile (android one) its on beta program and only have a 410; as much as android Lollipop/Marshmallow/ N are very optimized, work flawless in practically "any device" with 1gb ram

Lineage OS

I've been under the impression that the Relay wasn't about to get Nougat support, because it's graphics chip was too old to do Vulkan. However these two sites indicate that Relay support is in the works. http://www.gizmoadvices.com/list-devices-supported-official-lineage-os/ http://lineageosdownload.com/devices-supported-by-lineage-os/
I'd not be prone to trust that, since they seem to essentially be the same list. (echo-chamber?) However this site http://www.theandroidsoul.com/download-lineage-os/ with download links shows some supported Samsung devices of similar vintage to the Relay, perhaps even older.
I plan to look into this more, but in the meantime, does anyone else know anything?
I also plan to upload my Dec 3 and Dec 29 images from last year to my google drive, and will make those known here, once I have. They're not fully tested - I did a bit more explicit testing of the Dec 3 image, but I'm currently running the Dec 29 image.
Edit - some content:
https://drive.google.com/open?id=0B_MKeoY9qBceVGlWV05fUlVObUU
https://drive.google.com/open?id=0B_MKeoY9qBceRDd5elpZbFZETVk
https://drive.google.com/open?id=0B_MKeoY9qBcecmxBR2xzV2N2cTQ
https://drive.google.com/open?id=0B_MKeoY9qBceVWJQSEUwaXpiNFk
(I fear I've lost track of which is which, but two are zips and two are checksums. Two are Dec 4 and two are Dec 29.)

Nice one! i've been running my relay on the stock OS for years. It's running slow as a dog. I really need to learn how to flash it with a nice new ROM.

That would be awesome if the Relay would get a second life.... i'm sooo close to drop it and buy the Nokia 6... hope HMD is living up to some customers expectations and is building a new communicator... love my old buddy E7.
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
by the way, the Relay is in basic the S III. But I'm quite astonished that they support the Relay ()

SinnedNima said:
That would be awesome if the Relay would get a second life.... i'm sooo close to drop it and buy the Nokia 6... hope HMD is living up to some customers expectations and is building a new communicator... love my old buddy E7.
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
by the way, the Relay is in basic the S III. But I'm quite astonished that they support the Relay ()
Click to expand...
Click to collapse
By "E7" you mean the Nokia E7, right? Oh, I have often fantasized about a device in an E7 chassis but with new internals and running Android... except for the weight, that was my favourite form factor ever, keyboard or not
---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------
BTW since my Relay is definitely not my daily driver, more than happy to give these builds a whirl...

so will there bea linage os for the relay 4g. if so I would be interested for afriend of mine . he loves the relay and so he is wondering if there will be development for linage for the relay 4g. please let me know.

I'm updating here the last CM recovery in case someone needs it.

mrk2815 said:
so will there bea linage os for the relay 4g. if so I would be interested for afriend of mine . he loves the relay and so he is wondering if there will be development for linage for the relay 4g. please let me know.
Click to expand...
Click to collapse
The leaks of the soon to be supported devices have the Relay on it. I can't believe it yet but why not? The Relay is the last Android QWERTY with decent hardware. As i stated before in another thread the S III is nearly identical to the Relay and the SoC is/was quite popular and built in many devices. The chances are high (to good to be true)

SinnedNima said:
The leaks of the soon to be supported devices have the Relay on it. I can't believe it yet but why not? The Relay is the last Android QWERTY with decent hardware. As i stated before in another thread the S III is nearly identical to the Relay and the SoC is/was quite popular and built in many devices. The chances are high (to good to be true)
Click to expand...
Click to collapse
I've done a bit of looking since, and see that Lineage OS is advertising both Marshmallow and Nougat support. I suspect that means that the Relay is going to get Marshmallow, not Nougat. My impression is that Nougat required Vulkan graphics, and the Relay's graphics chip wasn't capable of that. Still, Marshmallow will be newer and presumably more secure than KitKat.

phred14 said:
I've done a bit of looking since, and see that Lineage OS is advertising both Marshmallow and Nougat support. I suspect that means that the Relay is going to get Marshmallow, not Nougat. My impression is that Nougat required Vulkan graphics, and the Relay's graphics chip wasn't capable of that. Still, Marshmallow will be newer and presumably more secure than KitKat.
Click to expand...
Click to collapse
Even Marshmallow would be a welcome advance for the Relay venerable Relay.

I love my Relay so much that I want it keep it forever.
I bought a couple of extras, so I have some hardware for testing and I am eager to assist anyone who wishes to continue development for the Relay.
Please contact me if I can assist you and/or please direct me to someone whom I can assist.
thanks in advance,
- Soul Singin'

LineageOS released their list of officially supported devices and the Relay is not on it. I jumped onto the Lineage OS IRC channel to ask the devs what exactly they'd need to get the Relay officially supported. They said they need a working device tree + kernel. I emailed them the info they asked for and will let you guys know how it goes.
My Relay is my daily driver running CM11 and an more up to date rom would be amazing.

check out the development area here at xda, i'm sure there was a kernel over there. i do think that for someone like reventech from the validus project that task would be easy as a pie. don't they have the sources of cyanogenmod? the mirrors are down am i right? on that github should have been the source. i'm not able to build android yet. as an administrator my free time is quite limited

gerbilfat said:
LineageOS released their list of officially supported devices and the Relay is not on it. I jumped onto the Lineage OS IRC channel to ask the devs what exactly they'd need to get the Relay officially supported. They said they need a working device tree + kernel. I emailed them the info they asked for and will let you guys know how it goes.
My Relay is my daily driver running CM11 and an more up to date rom would be amazing.
Click to expand...
Click to collapse
Would you be willing to send me the device tree, as well. Or perhaps since I have the sources sitting around, I presume there's a device tree there. I've read about the device tree on Phoronix, but have never really walked through one.
Also, since I've got a source tree, I've also got a kernel in there. However will Marshmallow use the same kernel as KitKat? Oh, google was my friend: https://android.stackexchange.com/questions/51651/which-android-runs-which-linux-kernel
Android Version |API Level |Linux Kernel in AOSP
----------------------------------------------------
1.5 Cupcake |3 |2.6.27
1.6 Donut |4 |2.6.29
2.0/1 Eclair |5-7 |2.6.29
2.2.x Froyo |8 |2.6.32
2.3.x Gingerbread |9, 10 |2.6.35
3.x.x Honeycomb |11-13 |2.6.36
4.0.x Ice Cream San|14, 15 |3.0.1
4.1.x Jelly Bean |16 |3.0.31
4.2.x Jelly Bean |17 |3.4.0
4.3 Jelly Bean |18 |3.4.39
4.4 Kit Kat |19, 20 |3.10
5.x Lollipop |21, 22 |3.16.1
6.0 Marshmallow |23 |3.18.10
7.0 Nougat |24 |4.4.1
7.1 Nougat |25 |4.4.1 (To be updated)
So the problem is that we need a new kernel, and need to map the old config to the new. OK, I always save my kernel configs, and one of my home machines goes clear back to 3.7 and up to the present, except that while I have configs for 3.16 and 3.20, I'm missing everything in between. Another system has five different 3.18 kernel configs, but only goes back to 3.16.3. I know these configs are not usable for Android, but I'm hoping they can give me an indication of what changed between the relevant levels. Scratch that, one the first machine mentioned, I have a 3.18.8 kernel config laying around as well as 3.10.0, 3.10.9, and 3.10.10 configs. Sadly, there are 1570 lines of diff between the two. Haven't looked at any details yet.
This looks like a bit of a chicken-and-egg problem. I'm going to presume that I can't just stuff a 3.18.10 kernel into my CM11 build and expect it to work - though that's the way Linus would like it to be, and the two kernels aren't that far apart.
Pardon the rambling.
EDIT: I just checked my source tree, and I appear to have the kernel source there. Actually there seem to be two sources, "samsung/d2" and "samsung/t1". Neither appears to have been compiled, because I only see .c and .h files in there, nor is there a .config file. Luckily I just checked my Relay, and found "/proc/config.gz". Oh, and here's the other oddity: "uname -a" returns "3.4.104-cyanogenmod-g61tc527e", not the expected 3.10. I may have to grab a Validus image, if I can still find one.

phred14 said:
So the problem is that we need a new kernel, and need to map the old config to the new. OK, I always save my kernel configs,
Click to expand...
Click to collapse
Attached is my: /cm_repo/kernel/samsung/d2/arch/arm/configs/cyanogen_apexq_defconfig for CM 11, which uses kernel 3.4.95 and android 4.4.4
Does this help? If so or if not, please tell me how I can help.
And thank you for your help!
- Soul Singin'

would to know how it goes as well, any updates?

from what i've been told they have no plans for it either
https://www.facebook.com/LineageAndroid/posts/1499401083412550?comment_id=1499658536720138

any new news on any development for this device. i know that the s3 has gotten its linage os 14.1 rom and how come the relay whihc is based off of the s3 cant get a 14.1 rom. just wondering.

I know everyone hates a 'me too'. I have been a T699 user for about as long as it's been introduced. I also use a Stratosphere II and a Galaxy S5, but my Relay is still my favorite. I hope the developers at LineageOS will still consider supporting this phone. Thanks in advance.

Even though it's not my main phone anymore, I love pulling out my Relay now and then. In fact I'm using it as a music & podcast player since the SD card reader in my main phone died. The only thing that stops me from using it more is that the battery drops like a stone when it's got cellular signal/data going, to the point that it almost unusable day-to-day as a connected device. But it's got great standby life so I'm pretty sure it's the OS, not the battery. I would love it if a new OS actually fixed the battery drain...

It would be a dream to geht lineage OS in the relay 4g. Any advance Herr???

Android Oreo (Go Edition) + Motorola Droid 4 XT894 = ?

Greetings, fellow devs and fans. Hope that you are doing fine. I do hope that this would be the right place to ask anything, including what I have in mind right now.
I may have been ditching Android as my daily driver for Windows 10 Mobile for like two years now, but that didn't stop me from keeping tabs with the latest news about Google's mobile OS, and the latest news about the Go Edition of Android 8.0 Oreo do catch my attention. I would definitely love to see how Android Oreo Go stacks up against my current favourite mobile OS from Microsoft.
But that's not what I wanna talk about. I actually wanna talk about Motorola Droid 4 XT894 aka "maserati". I've been yearning to own what is undoubtedly the last ever Android - indeed, the last EVER smartphone with horizontal QWERTY keyboard. But that got me thinking: Since Android Oreo Go only needs 1GB of RAM and "maserati" is indeed only have 1GB of RAM, I wonder if there is(are) a way(s) of porting that particular Android into that Motorola?
Don't get me wrong - I'm not asking for tutorials or suggestions about steps on doing it, because I don't even know if someone else is thinking similar line as me. But who knows... in the future... maybe it is possible after all?
That's all for me. Would love to hear your thoughts.

fat8893 said:
Since Android Oreo Go only needs 1GB of RAM and "maserati" is indeed only have 1GB of RAM, I wonder if there is(are) a way(s) of porting that particular Android into that Motorola?
Click to expand...
Click to collapse
I would even be happy if the "normal" OREO 8.1 (Lineage 15.1) was released some day.
But here are some sad but unconfirmed news: https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338/page22#post76220740
Maybe you could ask the developer "stargo" https://forum.xda-developers.com/member.php?u=3457922 directly if he will publish an Oreo (Go) version for the XT894 maserati

Development of a ROM Android pie for the Huawei Y5 2018 or DRA-LX3

Who can develop an Android ROM 9.0 pie for the Huawei Y5 2018 or DRA-LX3 version of 1GB of RAM and 16 storage which comes with Android Go edition which I find very limited to my liking

i would love if someone make a custom rom for this device, i just got one as secondary device for work and i think is really good for the price(Screen is great, battery life is also great, looks ok) but my main problem are the GO apps (Gmail Go, YouTube Go, Maps Go, etc...) that get crash all the time and if a change to another app or if the device locks the apps always reset and is super annoying specially with the Maps app, before this i was using another Huawei with also 1gb of RAM and older android version and all those apps where running smoothly so i think is fault of the Go version of android oreo

I bought this phone a couple of weeks ago mostly for the price. The phone would be great, but the apps just close themselves, any app that is a little more demanding would close instantly. I contacted huawei, but they just told me to do a bunch of useless solutions to optimize the phone that obviously didn't work and they ignored me when i told them that the problem was the "Go" version of the Android Oreo. Anyway it would be awesome if someone would make a pie ROM for the huawei Y5 2018 or Dra-lx3, or another version that's not "Go". Is the only solution i think for this phone since an update solving the problem from huawei is unlikely to arrive any time soon.

Hi...
I experienced the same problem of @Jyroux and @NateXIII
... the apps just close themselves, any app that is a little more demanding would close instantly...
Click to expand...
Click to collapse
even, the apps close themselves suddenly!
I wish some improvement, looking for a naked versione of Android (Oreo or Pie...it doesn't really matter).
Have you any info?
Thanks a lot & CIAO!

Hi friends, I have the same problem.
Has someone managed to root the device?
Could you tell me how I do it please?

Raul1720 said:
Who can develop an Android ROM 9.0 pie for the Huawei Y5 2018 or DRA-LX3 version of 1GB of RAM and 16 storage which comes with Android Go edition which I find very limited to my liking
Click to expand...
Click to collapse
If a developer that had the ability to build a ROM owned one of these devices, they would already have built a ROM for it. Since there are no ROMs available, one can assume that no such developers own this device.
Building ROMs requires having one of the devices on hand to test what is built. If you want a developer here to build a ROM this device, you'll have to buy another device like this and donate it to the developer, otherwise, you can try learning to build the ROM yourself or you can give up on the whole idea.
You are much more likely to get a ROM for this device by learning to build it yourself, that will probably happen sooner than finding someone to do it for you. No one is going to take the time to build a ROM for a device they do not own or do not use, especially for free.
Sent from my SM-S767VL using Tapatalk

Raul1720 said:
Who can develop an Android ROM 9.0 pie for the Huawei Y5 2018 or DRA-LX3 version of 1GB of RAM and 16 storage which comes with Android Go edition which I find very limited to my liking
Click to expand...
Click to collapse

You can flash a GSI, which is kind of a generic rom, if you have bootloader unlocked.

Since we've had Linux boot on the Surface RT, will Android at some point?

Yeah most stuff doesn't work on Linux at the moment but maybe?

Today successfully booted up windows 10 arm on my surface rt.
I am so hasppy android ports are coming to this tablet

pedrofssf94 said:
Today successfully booted up windows 10 arm on my surface rt.
I am so hasppy android ports are coming to this tablet
Click to expand...
Click to collapse
well dang

FoxyDrew said:
Who told you android ports are coming to this tablet? lol glad your optimistic though
Click to expand...
Click to collapse
Actually yes, Android 5.1 is coming to this tablet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com

pguarache said:
Actually yes, Android 5.1 is coming to this tablet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com
Click to expand...
Click to collapse
You do know no one can see that because you would need to be in the discord server that we dont have an invite to lol

In theory It would work...
Older versions supported ARM32 pretty well and since Linux is already working It would not be harder to port Android to The surface RT and 2.
The problem is that these devices are almost 10 years old and few people care about them anymore.
Even with Android installed running apps with 2gb of very aged memory would prove to be a pretty bad experience...

Nicknackpaddywack101 said:
In theory It would work...
Older versions supported ARM32 pretty well and since Linux is already working It would not be harder to port Android to The surface RT and 2.
The problem is that these devices are almost 10 years old and few people care about them anymore.
Even with Android installed running apps with 2gb of very aged memory would prove to be a pretty bad experience...
Click to expand...
Click to collapse
Eh, I've run worse. I have a moto E LTE running android 9 (RR Custom Rom based on a GO version of android) and it runs fine (1gb of ram and a worse cpu than the RT) sure it would be nice to have more ram but it works.

WinDVD said:
Eh, I've run worse. I have a moto E LTE running android 9 (RR Custom Rom based on a GO version of android) and it runs fine (1gb of ram and a worse cpu than the RT) sure it would be nice to have more ram but it works.
Click to expand...
Click to collapse
Yes, I understand your point. But the fact is that it had Android to start with, with the surface RT you have to use loopholes and bugs to get Linux working in a inefficient way and even the currently working(sort of ) Raspbian based Linux system has a bunch of bugs and missing drivers etc. Power control lacks behind Windows RT (mentiond here:https://forum.xda-developers.com/t/porting-chromium-to-windows-rt.2095686/post-87719273. The sad fact that this device is already 10years old means that it is unlikely people would pay attention to it and use it to develop Android, and even with Android installed the experience would be very limited due to the ram. support would be almost non-existent similar to what happened to the windows phones that got unofficial CM versions. Developers are already moving away from ARM32 to newer ARM64 and a few years later most apps would have a minimum api equivalent to android 6.
There is still a silver lining though. RT devices are dirt cheap since they are almost or practically useless now and Android still has excellent backward compatibility. Anyone who really has interest and the time could pick up the pieces of the Linux project and move on with doing it, but it still would not be easy.
Maybe a crowdfunding project could give devs some incentive?

But for now you could try to run a vm in linux or simply run their linux equivalents. Chromium, firefox, WPS office etc. Raspbian is compatible wih the snap store too, so you could use it just like ubuntu.
I am not trying to pour cold water on your idea, and I really look forward to this project taking off. However, there ultimately is a reason why Windows RT and their RT devices failed to take off.

working with the progress made with opensurface-rt, we managed to get android 7.0 booting on the surface RT using the 3.4 kernel, got wifi working, but minor gpu bugs that make it an unstable setup. had a play about with 4.4 and 5.1 too. android 7.1.1 and above have critical gpu bugs which make it completely unusable. and probably unfixable. development into getting other devices such as sound, camera, bluetooth etc has yet to be done. so far we have, screen, touch screen, type/touch keyboard, 2d/3d gpu working. recorded a quick video of it running
maybe it would be possible to get all things sorted but it's quite the task.

jethro tarw said:
working with the progress made with opensurface-rt, we managed to get android 7.0 booting on the surface RT using the 3.4 kernel, got wifi working, but minor gpu bugs that make it an unstable setup. had a play about with 4.4 and 5.1 too. android 7.1.1 and above have critical gpu bugs which make it completely unusable. and probably unfixable. development into getting other devices such as sound, camera, bluetooth etc has yet to be done. so far we have, screen, touch screen, type/touch keyboard, 2d/3d gpu working. recorded a quick video of it running
maybe it would be possible to get all things sorted but it's quite the task.
Click to expand...
Click to collapse
Wow! Nice work! Would be interested to know the team behind this marvelous project. (since you mentioned 'we')
Also probably should embed the boot screen with your team's name...