[Q] Android L (5) - Nook HD, HD+ Q&A, Help & Troubleshooting

How soon do you guys think a ROM will be made for Nook HD/HD+ after Android L releases? Any guesses? Cyanogen have done a great job with 4.4

That's just going to be a lot of assumptions

sandsofmyst said:
That's just going to be a lot of assumptions
Click to expand...
Click to collapse
Probably why you were the only one to reply xD Thanks man

Just don't like to see 0 replies. That said, there's one now and then that I won't reply to. However, L is of much interest to me and some of the supposed improvements will hopefully be great. Plus L on the nooks would hopefully be even better. So I share your enthusiasm.
The release time could be shorter or longer depending on the amount of porting work to be done. There's other variables too. But someone else might also before cyanogenmod which would be fun.

Thanks for the reply, I agree on L being even better on the Nook varieties. Can't wait!

I was finally starting to look into bumping stock off og my HD9 and saw this... guess I can wait 4-6 months for this to all take shape... I wouldn't want to lose my progress in PvZ2 at this point anyhow

My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
With the nook being the nook... you could be right. The latest tech really makes android smooth, not android on the older tech.

OSs don't tend to get faster as they get fancier and the latest tablets and phones have much faster hardware (and more RAM).

Well I mean take a look at the iPhone 4S, it used to be able to run IOS 5 and now it's up to IOS 8 and it's still pretty fast. These companies need to focus as well on making the newer OS work well with older devices. I mean the HD/HD+ is only 2 years old...

Corkerman said:
the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
It might be 2 years old but the hardware was never really all that great as it wasn't a top-of-the-line tablet when it came out.
Anyway, that's why I'm hoping 5.0 does something to improve performance, but wouldn't expect miracles from it if anything at all. Android just does better on newer hardware.
_________________________
Looks like cm11 m12 improved responsiveness a noticeable amount and finally too. Still not the same amount newer hardware would cause but a welcome improvement.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster than 4.4.4_r2. With kitkat, art sped up menus and navigation, but not really much else. Lollipop is all art - no dalvik option - and not only are menus and navigation faster, but it seems to speed up apps as well, mainly the Chrome browser. I've been using Lollipop for a couple of weeks now, compiled 5.0.0_r2 with 4.4.4 blobs, and I've been pretty impressed. I just built 5.0.0_r5 from source yesterday with the new 5.0 blobs they released. I haven't had time to install it, but I would imagine the performance to be the same as 5.0.0_r2.
Unfortunately, the Nook HD depends heavily on CM source, and quite frankly, it's a little above my expertise. So I'll just have to wait for verygreen, bokbokan, and leapinlar to give us a lollipop build for the Nook HD and HD+.

cahrens said:
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster
Click to expand...
Click to collapse
That's great to hear it's indeed faster even though it's on a Nexus! Great job and hopefully the three guys can work some magic into the HD's

Corkerman said:
I mean the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
In consumer products, that's an eternity.

I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?

Jon Lee said:
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Click to expand...
Click to collapse
If it were me, I'd look here http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155 or here http://forum.xda-developers.com/kindle-fire/development/slimpop-otterx-t2957450 for some guidance.
Hashcode is a legend on XDA and he has almost single-handedly kept the very old, TI OMAP 4430 Kindle Fire alive. As for lovejoy777, currently, he has been the most active, hard working dev for that same KF. Hashcode has CM12 working and lovejoy777 has Slimpop.
Since our device is so similar to the KF and Hashcode has contributed to the Nook in the past, looks to be a good resource??? Then again, verygreen could also pop in sometime down the road.
Mike T

It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L

Jon Lee said:
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Click to expand...
Click to collapse
One of my first android devices was the 1st gen KF and Hashcode helped make an inexpensive E-reader a very viable android tablet. I would PM Hashcode and/or lovejoy777. Hashcode is usually very busy but he has always been helpful towards other devs, I know he gave some assistance to lovejoy777 with SlimPop.
As for lovejoy777, he's fairly new at development but seems to be very helpful. I think he also may have gotten some help/guidance from MwisBest who built a LP rom for the OMAP 4460 Galaxy Nexus. I mention this because I believe he knows the importance of cooperation among devs. As an aside, while reading his thread I think I read that he was in the process of "cleaning up" his github. So, he could be a good source.
Maybe also PM killersloth. He built quite a few nice roms for our Nooks last year and just recently expressed some interest in trying to get LP on our device. Maybe if you contact him, you guys can make something happen. I'm an old fashioned XDA'er that believes cooperation amongst devs and end users is essential in the community. Every little bit can help.
http://forum.xda-developers.com/showpost.php?p=57255968&postcount=14
Anyway, you seem to be a very sharp guy. I wish you luck in getting LP to the Nook. I wish I could contribute more but I'm more of a file swapper and modder of existing work than a dev. :laugh:
Mike T

Moving to Texas in three days, been hectic around here lol.
I had major issues with hwc, selinux, and our old configs. Hashcode must have plowed through it if its running on otter. I'd check his commit history for some tips.
We needed this for prebuilt boot image before
http://review.cyanogenmod.org/#/c/36813/1
I needed it a few weeks back when attempting to build. They might have brought up their own method since then.
I wish they would have called it SlimPop instead of SlimLP ??

A 5.0 build for hummingbird would be nice. Hopefully it won't be hard to modify an ovation build since all the devel appears to be on ovation.

Related

[Q] Ubuntu Touch for Galaxy S4 Active (i9295)

Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
TobiasFP said:
Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby
Click to expand...
Click to collapse
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!
Cederic said:
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!
Click to expand...
Click to collapse
Thanks for the pick me up
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?
TobiasFP said:
Thanks for the pick me up
Click to expand...
Click to collapse
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
TobiasFP said:
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?
Click to expand...
Click to collapse
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.
Cederic said:
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.
Click to expand...
Click to collapse
No, of course it is not easy, but what i was saying is, that when the i9505 gets going, which i believe it will, since they have been working on it for about a month now, i believe it could "easily" be converted to the i9295.
The i9505 is a lot more similar to the i9295 than the i537, they both share the same Krait processor, and the screen is already fully supported in the current CM build of the i9295, so i dont see that as a problem.
Of course it will take some time, but i believe (okay, a better word would be "hope") that when the i9505 has Ubuntu Touch ready, it will not take long for us.
See the development status here:
http://forum.xda-developers.com/showthread.php?t=2274387&page=4

No mention of KitKat yet?

In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!
rushless said:
In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!
Click to expand...
Click to collapse
Check the OP of the CARBON thread.
Unless a serious bug is identified, these early November builds will be the final updates for the 4.3 branch, as the Carbon Team has started working on 4.4
Click to expand...
Click to collapse
Be patient, it's coming!
Indeed, yes. It's true that KitKat will run on lower specification devices, however, that doesn't mean EOL devices will be resurrected. The lower specification "thing" is more of OEMs to consider, so they can push budget devices with the latest version of Android, KitKat; instead of still producing Gingerbread devices.
Of course, away from that subject. It should effectively mean, our devices currently on ICS/4.0.x+ should see an increase in performance, including our Nooks.
So when will we receive 4.4 KitKat on our Nooks? The general rule is never to ask for ETAs, but CyanogenMod has provided for us. CM10.1 is complete and finalised. They're trying to complete work on CM10.2, instead of jettisoning all of the current developers efforts. So they/CyanogenMod will be working on CM10.2 for some time, until they can finish it. That doesn't mean to say CM11 will come after CM10.2. No, you can expect CM11 nightly builds by the end of this month. And yes, it'll be called CM11, not CM10.3.
CM11 release date source.
Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app
psyberian said:
Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.
famewolf said:
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.
Click to expand...
Click to collapse
im so excited for 4.4 on our nooks!

Any new Developing Roms?

I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
royredman said:
I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
Click to expand...
Click to collapse
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
So you would teaching? [emoji56]
What do you want to know?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
I totally understand where you are going at. You are a great developer and I am not asking specifically you, just mainly other developers that haven't shown their awesome work for this tablet. And, do you know anywhere good to get a tutorial how to build a rom for this device?
Is building a rom for this device much harder than building a rom for another device, like the tf300t? Does the Tegra 4 chip really hard to work with when creating the ROMS for this tablet? Is there a way I can test the rom onto an emulator build of the tf701 on the computer so then I wont risk my tablet being bricked due to my ignorance? sorry for all the questions.

Thread Closed

Thread closed to avoid confusion.
Info.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother? In AOSP Nougat, the Snapdragon 800 and 801 chips using the Adreno 330 GPU are no longer supported as well. I guess my question is if it will it be possible to reverse engineer OMAP-4 drivers for Nougat that can support the new surface view texture renderer?
Sent from my Asus Nexus 7 (2013) using XDA Labs
Click to expand...
Click to collapse
I MIGHT be possible to support it, but would take a bit of work, offloading that stuff to the CPU (which is just what we need, right?) and all of which is above my skill level.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother?
Click to expand...
Click to collapse
The performance problems are probably a mix of slowish eMMC (have to load the precompiled ART files, and they're not exactly tiny), lack of main memory (ART has a bigger memory footprint), and an unsuitable CPU that was outdated when the phone was built, nevermind nowadays. The latter two are what seem to really kill us in CM13; if we're not stuck reclaiming memory, we're saturating the CPU : \
Having Motorola stroll in and develop some up-to-date, optimized drivers sure would be cool, though...hardware is hardware, but good firmware can make a lot out of little.
Nougat is apparently taking a step back and re-introducing JIT execution...so if our resident maintainer does somehow pull off yet another miracle and we get CM14 on here, I'd expect less I/O and memory pressure at the very least. The stock partitions would become viable again too, what with /data/ not being clogged by ART precompiles, and being able to run off them might also offer a (small) performance increase. /system/ is gonna be a tight fit, though...
But using drivers built in two previous, different eras of Android, most of which were for another device...seems like it's gonna take some serious work.
Sent from my Asus Nexus 7 (2013) using XDA Labs
Galaxy Nexus has Nougat!
MWisBest said:
Nougat build is up. No, I have not died, and neither has the Galaxy Nexus.
Decided to take an extra couple days to get this build stable rather than rushing out something that boots and does nothing else, sorry for the delay.
I can't verify the full functionality of the RIL since I don't have a SIM in my GNex these days, so let me know if there's any issues with that.
Everything else should be working well though.
No idea what to do for GApps at this time. I haven't tried them yet.
Download: aosp_n_tuna_2016-08-27.zip
As usual this was a team effort. @Ziyan helped, and @Hashcode (who I thought had died) helped as well.
Click to expand...
Click to collapse
Sent from my Asus Nexus 7 (2013) using XDA Labs
Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.
1f5 said:
Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.
Click to expand...
Click to collapse
Thanks! Maybe we should ask @stargo about it. Although, I know stargo likes to surprise people with a new Android version.
Sent from my Motorola XT912 using XDA Labs
Really hoping this old beast will get CM14 due to the coding magic of stargo or some other guys out there.
I recently aquired a completely new Droid 4 from a Verizon reseller in mint condition. Now I never want to live without a slider again!
It is a bit slow, gets hot sometimes and becomes pretty much unuseable with Google Play installed, but who needs that stuff anyways.
Can keep me warm in winter and after replacing stock apps with Naked Browser and Simple Music Player it runs well and fast.
Please don't let this slider die. The only alternative to this device is the Photon Q and this needs to be soldered due to the missing SIM slot.
Bro i think it will have a cm14 for the droid 4
Bro, there say that it is official for the droid 4 to get cm14 check on gammerson .com
Some new info from JooJooBee666.
u.b.o.o.t said:
Hi folks! I had some spare time to setup CM13 build tool chain and - maybe too late for @Septfox - I made a custom kernel with LMK accounting for swap memory, i.e. LMK does only consider memory pages as free which won't require swapping, now. In order to not spam this thread anymore with LMK issues and memory tuning, I created a new thread: http://forum.xda-developers.com/droid-4/development/wip-custom-kernel-lowmemorykiller-t3470411
Click to expand...
Click to collapse
JooJooBee666--
This is cool. I'll test these out here as well. If things look good I'll see about getting LMK changes added to the cm13 kernel and upcoming cm14 kernels (work just began).:good:
Bobcus Leper said:
CM14 confirmed?:fingers-crossed::good:
Click to expand...
Click to collapse
JooJooBee666 --
Not really confirmed (as in no promises it will ever be fully functional as of yet). Just started working on getting things compiling. After that, it's along ways a way from anything usable as there are some new hurdles to overcome thanks to additional lock-downs on SE Linux. So yeah, :fingers-crossed: is right.
Bobcus Leper said:
Thread closed to avoid confusion.
Click to expand...
Click to collapse
Please ask a Moderator to close your thread - otherwise it isn't actually closed....
I've closed it anyway.

Compiling Unofficial CyanogenMod 14.1 for Nexus 6

Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.

Categories

Resources