Related
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.
Every day when I login to the forums I see either another AOSP/CM rom or nothing new. Being a long time Nexus fanboy, I find it really odd that this device doesn't have any ports of third party UIs. I mean, the Nexus 5 has MIUI, FlymeOS, Ubuntu Touch, SailFish, and more. I always thought that was the coolest thing about Nexus devices, we always got the latest and greatest Android software and the Devs would port over so many good UIs because of how easy it was to port to a Nexus device.
Are there any devs working on any ports at all?
Do you as N6 users want to see more ports, even if it's not a daily driver but for the fun of trying something different for a change?
Yeah I'd love some love from miui and flume.
Sent from my Nexus 6 using Tapatalk
Mr_S said:
Yeah I'd love some love from miui and flume.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Always wanted to try the latest MIUI V6 which was merged with Lollipop earlier this year, and Flyme OS which hit the Nexus 5 after I left the device. Honestly I just like to mix it up a bit even if the experience is not as grand as stock.
most nexus modders use nexus devices not for porting, as porting generally brings instability, but for the stability of using aosp. every other device has to "port" aoap over, which reduces the stability. nexus devices dont have to port it over. if you are so interested in running a port, why dont you port something over. you will realize that it is by far not easy work, and you will spend all your free time on it, without ever getting paid for your work. enjoy
simms22 said:
most nexus modders use nexus devices not for porting, as porting generally brings instability, but for the stability of using aosp. every other device has to "port" aoap over, which reduces the stability. nexus devices dont have to port it over. if you are so interested in running a port, why dont you port something over. you will realize that it is by far not easy work, and you will spend all your free time on it, without ever getting paid for your work. enjoy
Click to expand...
Click to collapse
Interesting, I'm not a Dev, but I always thought it was easier to port to Nexus devices since they are always running stock and not locked down like most other devices.
synergeticink said:
Interesting, I'm not a Dev, but I always thought it was easier to port to Nexus devices since they are always running stock and not locked down like most other devices.
Click to expand...
Click to collapse
port, to a device it doesnt belong on.. being a nexus has nothing to do with it. a nexus has an unlockable bootloader and is easy to root, thats it. drivers to get things running right on the n6 are not open source, they need to be written from scratch to get any os to work with our hardware and cpu.
simms22 said:
port, to a device it doesnt belong on.. being a nexus has nothing to do with it. a nexus has an unlockable bootloader and is easy to root, thats it. drivers to get things running right on the n6 are not open source, they need to be written from scratch to get any os to work with our hardware and cpu.
Click to expand...
Click to collapse
Would the drivers from the Nexus 5 help at all in that regard?
synergeticink said:
Would the drivers from the Nexus 5 help at all in that regard?
Click to expand...
Click to collapse
no. drivers arent for nexus devices, they are for our specific hardware. thats why a nexus 6 can not run kitkat, drivers for a nexus 6 for kitkat do not exist(actually they do, but never were released by google).
simms22 said:
no. drivers arent for nexus devices, they are for our specific hardware. thats why a nexus 6 can not run kitkat, drivers for a nexus 6 for kitkat do not exist(actually they do, but never were released by google).
Click to expand...
Click to collapse
Drivers were never brought over? Well that would be a problem. Cool, thanks for the feedback.
As @simms22 stated, parting correctly is very difficult from one device to another, regardless of which device you have. They generally need many dirty hacks and are seldom stable.
I think overall on nexus devices, interest in ports is waning, so there is little to encourage someone to do it.
As an idea of difficulty, the moto x pro, which is pretty similar to the nexus 6 still hasn't been ported, and they've been trying.
danarama said:
As @simms22 stated, parting correctly is very difficult from one device to another, regardless of which device you have. They generally need many dirty hacks and are seldom stable.
I think overall on nexus devices, interest in ports is waning, so there is little to encourage someone to do it.
As an idea of difficulty, the moto x pro, which is pretty similar to the nexus 6 still hasn't been ported, and they've been trying.
Click to expand...
Click to collapse
partially, at least :angel:
Just wondering what other developers have decided or shown interest in grabbing a OnePlus 3. I am thinking of getting one, but the cost is a bit steep to just support a device that I may not even use as a daily device. If there is a small amount of developers, I will be more likely to get one because I believe that users deserve to use their phone how they want, not how the OEM wants them to. This is more or less a roll call to see who will be supporting the device from a dev standpoint.
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Dinjesk said:
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Click to expand...
Click to collapse
Anyone kernel side?
DespairFactor said:
Anyone kernel side?
Click to expand...
Click to collapse
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Dinjesk said:
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Click to expand...
Click to collapse
I am considering it, I have plans to bring kexec hardboot to the device if I get it
DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
_PrEzi_ said:
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
Click to expand...
Click to collapse
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
DespairFactor said:
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
Click to expand...
Click to collapse
I can perfectly understand that. You - like me - do like to do things either perfectly or at least v. good or better leave them be if they are only 'ok'.
Nevertheless - please do consider. I am not promising anything but my guts tell me OP3 will have a larger userbase than the OP2.
And again - no promises - but I like beer and also like to send 'virtual beer/pizzas' to the devs I feel are putting big efforts to keep the users happy. Probably other humble users too :highfive:
Would be killer to have you onboard.
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
gururoop said:
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
derdjango said:
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
Click to expand...
Click to collapse
inzaghi75 said:
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
For right now I will blind build a kernel and try to get kexec working. If I somehow get the budget to grab one, I will. I hear there is a BrokenOS coming, but do not ask anyone about it, just wait for a release. I will not bring UBER ROMs to this device because we do not run CAF based sources.
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Taker18 said:
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Click to expand...
Click to collapse
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I agree, it is hard to maintain several projects at once for one device, let alone a few. IIRC, a lot of you come across from other OP devices too, not sure if you are dropping support on previous devices.
Well, I'm too working on a kernel for this phone (albeit don't have device)
Sent from my Moto X using Tapatalk
##W4TCH0UT## said:
Well, I'm too working on a kernel for this phone (albeit don't have device)
Click to expand...
Click to collapse
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
DespairFactor said:
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
Click to expand...
Click to collapse
I think you know me. Remember me from one group we created ? I think of you can get a device, do support it. Infact, in one way, people support of you support them. So, get a device, support the device and a lot chances are that people will support you and you might be able to overcome all expenditures on the device. And believe me, many devs told me this too. And I know your kernel from 6P. Will be great if you can support, and prolly you *might* have a surprise too (I am not saying anything, but, well) . We do need your support, but it will be best if you can support when you have a device too. It will generate people's trust upon you and also you won't need to get with wrong bug reports.
Sent from my OnePlus2 using XDA Labs
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.
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.