Related
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
zephiK said:
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
Click to expand...
Click to collapse
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now.
Having said that... I'm not going to build 4.4, because it is pointless.
---------- Post added at 06:49 PM ---------- Previous post was at 06:38 PM ----------
dustin4vn said:
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
Click to expand...
Click to collapse
What exactly do you mean by "aren't optimized"??? As a developer, I have to say that this statement is completely meaningless. There is nothing special that need be done from a software developer point of view to take account for ART, as long as you aren't doing weird and unsupported hacks (which very very very few people actually do).
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
What do you mean by "stutters"? Is there heavy I/O happening when it is "stuttering"? Do you realize the serious impact that forced encryption has on the device's I/O and CPU performance? Do you realize that the display on N6 has nearly TWICE as many pixels as your "old" S5? That means that it is GOING to take a lot more to keep things fluid on N6 than S5. Something that will be helped when software starts to take advantage of the newer OpenGL available on 5.0. NONE of this will be improved by downgrading to 4.4. In fact, because 4.4 will NOT be taking advantage of the newer OpenGL, doing this downgrade will make certain, even after software starts to make use of it, that you WON'T be able to benefit from it.
doitright said:
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now
Click to expand...
Click to collapse
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
i would have chimed in a while ago, but for certain reasons i didnt. normally, id say that it wont happen, since there arent any binaries for kitkat and the nexus 6. but guess what, there are! they arent anywhere where the public has access to them, but they do exist. as google had kitkat on the n6 before lollipop. and a very few people have even gotten their n6 with kitkat(when they just selling the n6). so, in the future, we might be able to see a kitkat build on our n6
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Click to expand...
Click to collapse
I'm not going to, because it is a waste of time and I have no interest in having a **** measuring contest with some random person on the internet.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Click to expand...
Click to collapse
That's hilarious. Especially since hardware wise, the only real difference between those phones I mentioned and Nexus 6 is the screen size. In fact, we know for a fact that those two devices very nearly WERE stamped "shamu" and sent out AS Nexus 6. Something happened between Google and Verizon that decided what size went under whose label. Also, you should see all the Sony blobs I used on my Samsung phone... also a bunch from LG.
But just to make things even more interesting, on what grounds do you claim that Android 4.4 won't run on blobs from 5.0? That same Samsung phone I referred to above running on Sony and LG blobs... is running 5.0 on such mishmash of blobs pulled out from 4.[0-4]. And perfectly happily at that. Blobs DO NOT HAVE an intrinsic "works with Android version X and nothing else" stamped on them.
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
THAT is essentially what I am saying. Not the "even if" (because it *IS* possible), or the dirty hack part, because though it may make you FEEL dirty to downgrade, it wouldn't actually be a hack. I'm saying that nobody WILL do it, because it is pointless and backwards.
dustin4vn said:
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Evo_Shift said:
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Click to expand...
Click to collapse
As far as bugs go, its no different than any previous version. They patched a bunch of bugs that were there before, and added a few new ones. I wonder though, what bugs you think you've spotted? List them, and tell me why you believe that they are bugs...
Just port android 1.5 cupcake and call it a day lol
md1008 said:
Just port android 1.5 cupcake and call it a day lol
Click to expand...
Click to collapse
haha, lol. Now that... might actually not be possible.
doitright said:
haha, lol. Now that... might actually not be possible.
Click to expand...
Click to collapse
Time to do a change petition from google to make official cupcake ROM lol
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
I am gonna go ahead and just attach it to your post. There is a port being worked on as I post this, yes there are people who want kit kat on the phone and there are other reasons than running cm, aosp or stock. Enough said and more will be revealed in the nexus 6 forums hopefully within the next week we will see how bad it really gets
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
simms22 said:
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
Click to expand...
Click to collapse
You may be right and I might be wasting time. Something to do though
jhr5474 said:
You may be right and I might be wasting time. Something to do though
Click to expand...
Click to collapse
i actually think you should keep trying, seriously. maybe it is possible to modify the lollipop drivers for kitkat, or modify the n5 drivers for kitkat for the n6. anyways, it woukd be neat to try kitkat on the n6
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
prdog1 said:
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
Click to expand...
Click to collapse
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
simms22 said:
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
Click to expand...
Click to collapse
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
prdog1 said:
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
Click to expand...
Click to collapse
i actually rooted it and flashed safeline recovery, first time ever! lol. i used kingsroot, a one click app to root. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
simms22 said:
i actually rooted it and flashed safeline recovery, first time ever! lol. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
Click to expand...
Click to collapse
Why can't use it on provider. He has used Verizon Rezound on TMO and S3 on ATT. Not perfect but they work. He bad about breaking **** and never buys insurance.
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.
Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
Oh, it is? Thats great. I have plenty of patience
I'm in the same exact boat, have rooted/de-bloated and installed trebuchet and other features, but really would like to see CM support.
jeffburg said:
Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff
Click to expand...
Click to collapse
ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?
contacted Blu and they told me that they are looking forward to working on updating as many devices as they can to the new platform as soon as possible!......righhtttt!!!
Once the dev. on the kernel is in line for a cm13 port , cm14 (which is already being worked on) hopefully might be a possibility.
Fullmetal99012 said:
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?
Click to expand...
Click to collapse
Me either, but I think it would be the drivers. I would suspect with CM13 they can use it's current drivers but with anything Android 7.0 they would need new drivers.
Blu has updated a few devices haven't they? They have to develop the drivers and then run it through the carriers approval I believe? I'm sure they are looking at how much money they expect to make from the R1 HD in 4-6 months. Some of this might depend on their plans of a new phone they plan to release. R1 HD is a big seller.... but what about in 6 months?
A device tree is very likely being compiled for this device now that the kernel source has been released. A CM 13 build I'd imagine is also in the works with other custom roms likely to follow. I would just sit back and keep your eye out. As soon as customs ROMs are released you should easily find them in R1 HD Forums on XDA. I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.
Jstame said:
I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.
Click to expand...
Click to collapse
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?
cmason37 said:
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?
Click to expand...
Click to collapse
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....
Jstame said:
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....
Click to expand...
Click to collapse
"Not a big name mainstream device"
Totally man. The number 1 selling phone on Amazon isn't a "big name, mainstream device." If anything this phone is proving how Android development is dwindling.
There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.
dba415 said:
There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.
Click to expand...
Click to collapse
They probably did say it, BLU has a history of promising upgrades, they rarely deliver. I don't know if the blame is theirs or their Chinese partners, not delivering. But even at that if BLU was smart they would hire a team of developers to actually develop roms instead of just simple branding tweaks on the manufacturer supplied firmware. BLU needs to tweak their sales routine, currently they sell flashy looking phones on the cheap, but if they would change their focus to selling entry to mid level phones with better support, they could really make a name for themselves.
Hi there XDA,
I just ordered a 3T, and saw that although the device clearly has the hardware specifications to support daydream it officially has no support for it.
Since I am still quite new to the whole development part of android, I wanted to ask you for the possibility of XDA to build something tot make de 3T compatible with daydream. Is there a chance this will happen, is the chance absent or is it not even a question and will daydream be implemented for sure? :good:
Thanks in advance for your responses. :highfive:
Greetings from Amsterdam.
update: Clarifying the question.
1asbak1 said:
Hi there XDA,
I just ordered a 3T, and saw that although the device clearly has the hardware specifications to support daydream it officially has no support for it.
Since I am still quite new to the whole development part of android, I wanted to ask you for the possibility of XDA to build something tot make de 3T compatible with daydream. Is there a chance this will happen, is the chance absent or is it not even a question and will daydream be implemented for sure? :good:
Thanks in advance for your responses. :highfive:
Greetings from Amsterdam.
update: Clarifying the question.
Click to expand...
Click to collapse
You're correct in that the OP3T has the correct hardware. At the moment, it isn't compatible due to it being on marshmallow, and not on nougat (yet). Once that occurs, it is a possibility based on what the oneplus team puts into it. I'm not aware of what needs to be done to make a phone daydream compatible aside from the OS version, but it might be possible in the future if this information is publicly available. I would sit tight and wait for nougat first as we may get nougat and it comes to us daydream ready.
nhshah7 said:
You're correct in that the OP3T has the correct hardware. At the moment, it isn't compatible due to it being on marshmallow, and not on nougat (yet). Once that occurs, it is a possibility based on what the oneplus team puts into it. I'm not aware of what needs to be done to make a phone daydream compatible aside from the OS version, but it might be possible in the future if this information is publicly available. I would sit tight and wait for nougat first as we may get nougat and it comes to us daydream ready.
Click to expand...
Click to collapse
Great answer! Thanks, Lets keep this thread open for further additions by the great XDA community. :highfive:
Somebody tried reguest support of some custom rom ? I try it right now.
najjannajS650 said:
Somebody tried reguest support of some custom rom ? I try it right now.
Click to expand...
Click to collapse
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.
kemoti said:
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.
Click to expand...
Click to collapse
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.
Causical said:
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.
Click to expand...
Click to collapse
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)
Dadud said:
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)
Click to expand...
Click to collapse
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?
Causical said:
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?
Click to expand...
Click to collapse
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.
Dadud said:
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.
Click to expand...
Click to collapse
Yeah, right...I meant like more system side like deeply modified frameworks and stuff and things that have been modded in the system like tweaks to things like active or "live display" or whatever. Other things like how notification LED functions and tweaks to the make camera actions snappier...I know there's more...I guess a better way to describe it is things that Xposed would do, but built into a ROM. Treble isn't enabling those things is it? Since it's just a software update that's entirely parallel to a phones hardware?
Thanks, that is what I want to hear ?
Good to know some of you were able to boot GSI's already. I maintain RR for another Moto device. Once I get the bootloader unlocked, I'll work towards getting us up and running with RR