Having been burned in the past by lack of drivers & resources for different devices, I started to wonder about the future of our Nook tablets.
I don't know anything about software and/or Android development so have no idea what is required to develop these ROMs.
Since the stock ROM runs on ICS and current development is on JB, are the drivers compatible?
Also, what about Android 4.3 (Key Lime Pie) and Android 5.0? When it is release by Google, would lack of stock ROMs be a hindrance to aftermarket development?
What exactly is needed by developers to create a (mostly) stable ROM for our Nook HD tablets & Android devices in general?
I hope someone with more knowledge than I possess can answer some of these queries.
Thanks.
IMO, my HD+ is pretty dang stable right now. I think the fact that the stock ROM is ICS-based helps a lot. Going forward, who knows? Hard to speculate, but with a solid kernel and that handles the devices capabilities, i think we should be good for a while.
Related
Is There a Rom for us sprint gt people running 3.0. Seems like 2.3 is becoming obsolete for all the good things. Please reply if you know anything about this.thank you much
Sent from my SPH-P100 using XDA App
From what I have seem we won't be getting that anytime soon. It took such a long time just to get the stable roms we have now.
Sent from my PC36100 using XDA App
there is an unofficial port of 4.0 (ice cream sandwich) being worked on HARD by volunteers in the SGT dev forum. it's booting but it's very early alpha and most things (wifi, gsm, etc.) don't work... if you give them a little time to polish it, from the progress made, i'd expect a stable version ready for beta testing inside of a month.
as for official upgrade, samsung hasn't said that it's NOT comming, however, I wouldn't hold my breath as these devices are now over a year old and the tablet / phone market goes so fast that I don't think that they are going to be releasing any updates to devices as old as the sgt. luckily, it's more or less a well documented platform with lots of great community support, and the dev guys on xda are pretty amazing hackers so there are currently quite a few aftermarket unofficial gingerbread-based roms which add many additional features, additional stability, and i find a few of them (overcome, cyanogen) actually operate far better than the samsung official roms. I would expect that the normal community development teams will be working to bring us fully working ice cream sandwich roms in the near future, so sit tight, it's coming
The fact that you're running 3.0 at all is probably about as far as ROM development is going to go on that front. As for an official upgrade, Samsung have said there will *not* be an ICS upgrade for the original Galaxy Tab. Every other member of the Tab line will get the upgrade but the original was deemed too old and too underpowered for official upgrades.
With the release of the S-PEN SDK, does that mean AOSP based roms will become a reality? I'm sure any AOSP based roms may not work properly for the GNote because of the S-PEN, so does the SDK solve this?
Much more interesting is the question, if the S-Pen or generally the pen implementation Samsung has gone for is compatible with the Ice Cream Sandwich implementation and therefore future proof or if they went their completely own way and ICS wont bring anything good to the Note except equipped with Sammys proprietary tools...
Jeez, is this really one single huge sentence? I'm afraid it is.
Sent from my GT-N7000
I was really wondering the same thing, but in a different way.
The current Touchwiz builds all have issues with playing music in A2DP stereo.
This is caused by low bitpool settings, which are compiled into their proprietary bluetooth stack.
This could all be fixed by using an AOSP-based kernel (and thus bluetooth stack).
I'll be honest, I would prefer vanilla ICS, but I would be happy to skin Touchwiz ICS, provided they at least fixed the BT issue.
Another way of asking a similar question is if cyanogenmod plans on integrating the S-pen into CM9 for the Gnote.
The current answer seems- maybe after Touchwiz ICS is released... maybe
The currently existing very early build of CM9 seems to be supporting the pen. Of course no proprietary Samsung software like S-Memo and such is integrated, but the hardware works, I once read in the thread. I didn't follow the thread though and I believe it's rather quickly growing
schaggo said:
The currently existing very early build of CM9 seems to be supporting the pen. Of course no proprietary Samsung software like S-Memo and such is integrated, but the hardware works, I once read in the thread. I didn't follow the thread though and I believe it's rather quickly growing
Click to expand...
Click to collapse
Have you tried it personally? I seem to remember it being stated that CM9 would categorically not support it, however ICS natively supports pen input.
I also heard that if it did support, would not be pressure-sensitive without the Spen SDK
No I didnt try it personally but I still strongly believe an overview was given and the S-Pen functionality was mentioned working.
I'll check the thread out though once I find time to do so, I'm quite interested to know, really.
#Tapatalk #Galaxy Note
I'm thinking of buying the X3c but have loved the vanilla version of the Nexus 4 and getting regular updates.
I'm very new to the whole unlocking community and wanted to know if its possible to install a vanilla version of Lollipop on it and install future update. If so, would this affect any functionality? I read that the camera in low light will be affected.
Thanks in advance!
The closest you'll get to AOSP on this phone -- and it's very close -- is through Cyanogenmod and derivative ROMs. I've read that losing Sony's DRM keys results in a few changes (see thread). The big question is will you lose and miss those features. Secondly, will Cyanogenmod ever release a stable version for this model. Currently,
I love AOSP for its speed, efficiency, and UI but I'm bummed to lose stability and camera quality. That's the tradeoff will almost all the Android phones right now though. Those Nexus phones have a great update policy.
Keep an eye on the development section to see when Android 5.0 ROMs are available and read the threads to see how well they're working: http://forum.xda-developers.com/z3-compact/development.
Thanks jayarmstrong will keep a lookout for those ROMs. Appreciate it
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.
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Hello jcole20
That would be awesome if some devs started doing something with the RP2! If I had the knowledge, I would!! I've had the RP2 since June of this year. I had some issues with it at first but they have been worked out. I really like the phone and it would be cool to see some devs show the RP2 some love lol. Hopefully you can get something started! Take care!
Dennis
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
I am sure people would love to see some device specific development. I have read that since the release of project treble most people just flash the system image from other roms. I specifically would love to see a stockish rom so I don't loose chroma but still get updated security patches.
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Krazy_Calvin said:
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Click to expand...
Click to collapse
Most functionalities work on Pie GSIs out-of-box (you need to manually install ims.apk in order to receive SMS while on LTE, see relevant threads here, or look for it on some GSI threads such as Havoc 2.9). exFAT also works on supported GSI (with arter97's kernel), while it's not supported on stock. The only problems I have so far are bluetooth-related, and also the inability to set SELinux to permissive (not sure which might be the real cause as arter97 stated the SELinux could be permissive).
Bluetooth media audio doesn't work at all on GSI, partly due to the crippling overlays (which prevents aptX from working, and probably some other limitations). Phone calls work with a bluetooth headset, but for some reasons I couldn't properly route phone calls to my Huawei Watch 2 (which means I always have to take the call from my phone directly).
Given the mostly positive result with numerous GSIs (and that some users are happy with stock ROM, or stock-based ROM modifications), active ROM developments for the device itself doesn't seem to be at a high priority (as some might be able to contribute patches for this device to their favorite GSI instead)...
I'm currently working on my own build of LOS. I haven't seen to much active development either I'm new to rom building but looks like we could use all the help we can get!
I think the only active dev we have for this phone is Arter97's kernel and people tinkering with GSIs to get them working as they should. I wish there was more being done with the stock ROM because I like a lot of it's features, but am having a hard time dealing with it's overall instability. I'd be happy to help develop or test in whatever way I can, though.
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
Yeah, it’s definitely just total lack of interest from other devs. We even have a guy with a prototype Razer Phone 2 with an intact DRM partition and unlocked bootloader (Allowing Netflix HD and Vudu HDX) but we couldn’t even pay anyone to try to port it.
I think if we had a fully working AOSP tree that it would possibly bring other devs into the scene. Who knows though, it has never been a popular device despite how great it is.
LSS4181 said:
Most functionalities work on Pie GSIs out-of-box.
Click to expand...
Click to collapse
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
EMJI79 said:
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
Click to expand...
Click to collapse
A stock Android 10 (which means a stock vendor image for Android 10) is not necessarily required to have a usable Android 10 ROM (though it may speed up the development to some extent, if it does have one), but for GSI, having a stock Android 10 vendor image can be better (currently it's a hit-or-miss on existing Android 10 GSIs).
Another device that I have, Google Pixel C, never had stock Android 9 (so never had stock vendor images for Android 9, only for up to Android 8.1), but custom Android 9 ROMs are already available (thanks to followmsi's efforts) and are working well. For Android 9 ROMs, the build system builds new vendor images along with system image.
It's just whether we're going to see our device's trees being made possible, so we can start from there to develop our own custom ROMs. The existing materials might be a good starting point in making trees.
- Working with proprietary blobs (from Lineage)
- arter97's kernel (can be useful for making a kernel tree, though one can also consider using stock kernel source as a base)
- Razer factory images and kernel sources (for studying stock ROM/kernel details, and extracting necessary system and vendor blobs)
If you can port LineageOS to this device, great!
I don't understand why people aren't flocking to this device. I came from the LG G6 that probably will be stuck on Oreo forever that is way more popular. The RP2 is cheap, has killer specs + a micro SD card slot + a newer version of Android. Should be a developers dream, you would think. *shrug*
Not sure if anyone's active on this device at present. With RP2's 9.0 MR2 available on the official factory images page the latest proprietary blobs (as well as stock kernel source) are now publicly accessible.
Actually arter97 once mentioned that his RP2 kernel is almost inline with his OP6 kernel (which is also sdm845 and shares some similarities), so it's possible that OP6 (enchilada) trees may be a good starting point, but I'm not sure if any configurations are needed to keep 120Hz working as high refresh rate is relatively uncommon.
My time is very limited so I won't be able to dedicate too much time to experiment on this. At present most functionalities work fine with GSI (including Bluetooth, although tricky and aptX still not working).
IDK how relevant this is anymore but as a new razor phone 2 user to be soon I have been keeping up and it seems that @f(x)THaxxorX could be a possible candidate of what you're looking for I've been keeping up with development on the phone seems like he is doing pretty well even if we get patched gsi which properly work is better than nothing.