Related
HTC home theme is old news, and manila is slowly heading that way too.
how about making a new rom based on the Vtocco theme ?
Its classy, great looking, and i bet it would work great with the jamin/Prophet.
there is already a project that has created the theme for windows mobile users, the thread can be found here : http://forum.xda-developers.com/showthread.php?t=430190
The source code is availible as well so whoever wants to add anything to the theme can.
might be great if it can be integrated into a rom.
anyway, its just an idea.
How about something new?
I am pleased to present, three years after the device's release...
AOSP 4.2.2 r1.2 for Nook Color
For this first release, I wanted to keep this as close to straight AOSP as I could. The device and kernel tree are identical to the the one in the CM10.1 release. There is a three year history of maintainance and improvement from the NookieDevs. Without that group of gentlemen, we would all be using ManualNooter, so be thankful. This project, and AOSPA as well, are not possible without them.
This is a straight a port to AOSP as a device with our boot parameters could hope for. Let me know what you think. The deviations from stock AOSP are minimal and almost wholly hardware related...a list is on a following post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: these are random Google image results, not screenshots. I have not enabled native screenshots yet, and have no intention of buying an app to do it now. It's AOSP, you guys are familiar.
The only thing I added to this build that wasn't necessary or direct from AOSP was that I embedded Superuser, because ROOT! (and things just work more smoothly if it ships with the SU stuff handled.)
I think the performance is actually really nice, let me know.
Bug List
Nothing jumps out at me. Let me know. (Please check if you are reporting a bug with this build, or one from AOSP upstream. Google helps.)
Downloads
Rom is here.
Gapps are here.
I may decide to enable update notifications from Goo Manager...I haven't decided. I don't expect to update this as often as PA, not until 4.3 drops anyhow. But an update or two is for sure coming.
The Future
We can add some common-sense extras to this rom...but I do not want to spend a bunch of time and effort skirting the line between this and CyanogenMod. We already have CyanogenMod...it's awesome. Having said that, I am willing to add some basic extras. Post your thoughts about this issue in the thread...the more we add, the further from AOSP we go. Options include:
Performance Settings
MTP/PTP
Screenshots
Power menu (reboot etc.)
Requests may be considered (no promises...my plate is already pretty full. But contributions from the community are treasured...see the next post for source code info)
Thanks
NookieDevs (fat_tire, nemith, eyeballer and steven676 especially)
TeamWin for the vast amount of free hosting they provide me (and so many others)
inportb, koush
Leapinlar and RedneckReg for the replacement device.
Scroll down for build guide
Technical info for source code enthusiasts.
https://github.com/mateor/android/tree/aosp-4.2
CM projects used:
build
system/extras
vold
The above are all related to either the Nook's unique boot (having a uboot and MLO) or the partitioning scheme in the emmc. I intend to change to using the AOSP versions of those projects with the needed changes cherry-picked. Almost all of the commits we need were written by our own nemith and dalingrin.
hardware/ti/*
frameworks/av
frameworks/native
I have not decided what I will do with frameworks/av(whether I will pull out the OMAP stuff from that project or leave it as is), but the other hardware/ti handling will likely remain as the CM versions. I will peek at a diff, but the odds are high that we will stick with CM version there.
android_device_bn_encore
android_kernel_bn_encore
These two will 100% closely mirror the CM versions. I had to make some no-brainer changes to device before building...that will likely be the end. Thanks and credit to NookieDevs, especially Steven676 for 4.2.2.
Omap aside, my experience showed me that we only needed 15-20 changes to AOSP to port. So we will try and dial it back to just the barest changes necessary as an intellectual exercise.
Contributions from the community are welcome...the branch naming is all over the map right now...look at the manifest linked above for definitive answers about the source code used.
Thanks.
Build Guide (perfect for first-timers. Support can be requested in the thread)
These instructions are for 64 bit Linux environments, try VirtualBox if you don't use Linux normally.
Take 15 minutes and follow the beginning of this guide. if you don't have ADB set-up, it will take longer, but that is just for downloading the SDK.
If you need help installing the JDK on Ubuntu (or another system with apt-get) do this (the absolute easiest way)
Code:
cd ~/
wget https://github.com/flexiondotorg/oab-java6/raw/0.2.7/oab-java.sh -O oab-java.sh
chmod +x oab-java.sh
sudo ./oab-java.sh
sudo apt-get install sun-java6-jdk
When it gets to the step to intialize the repo (repo init -u ETC.) STOP, and come back here, You are done with that guide, forever. Those steps only need to be done once.
Enter:
Code:
[FONT="Courier New"]repo init -u git://github.com/mateor/android.git -b aosp-4.2[/FONT]
[FONT="Courier New"]repo sync[/FONT]
If you experience fetch errors during the repo sync, change the command to repo sync -j4 -f. If they still occur, then repo sync -j1 -f.
This will take a long time, do it before bed, or family time, or go eat.
When the sync is done
Code:
. build/envsetup.sh
lunch full_encore-userdebug
make otapackage
You're done!
When it is done compiling, your ROM will be waiting for you at out/target/product/encore.
Fat-tire says building your on rom makes you an Android ninja, so you know it must be true. That means that if you don't try, you are admitting you don't want to be a ninja. Which reveals you to be the geek you already are but with loser rubbed all over you. Why else are you on XDA if not to learn?
Wow! Amazing work mateorod! I know we personally have discussed this project many many times and I'm glad you were able to dedicate some time to pulling it off, sorry I haven't been around as much lately.. life in the way but will definitely give this a look
Congrats!
badass!!!!!
coulkd you add the option to edit quiccktoggles
Wow! Awesome stuff mateorod! Looks like you've been pretty busy here. Gonna give this a go for sure!
Thank you for keeping our little device still alive, kicking and fresh!
Intriguing.
Not only am I checking this out, but the goo.im link wasn't working so I'm building a rom from source for the first time
Would an AOSP base be good for a AOKP port, or would Cyanogenmod be better?
Sent from my NookColor using xda app-developers app
AgentCherryColla said:
Would an AOSP base be good for a AOKP port, or would Cyanogenmod be better?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
Use AOSP, for sure. AOKP is AOSP-based now, except for the hardware implementation (I.e. the hard stuff) done by CM and their device maintainers. But definitely use my aosp-4.2 manifest as your base. All the changes are very specific...you must use my forks of those CM projects not simply the CM-10.1 versions. (that probably goes for the device tree as well).
A good example is vold. CM-10.1 vold is not backwards compatible with the AOSP repos...there is some undocumented dependency in another project. I could go on and on...deviate from my choices at your peril.
However, swapping out the AOSP repos (I.e. anything straight from aosp) with AOKP repos should work fine. Krylon stalled out on an AOKP build for the Nook...I think this manifest will allow you to be successful. Ask any questions you like...if I can answer I will.
PA Halo goes Open Source!
Hi mateord,
may be you didn't know about that: Paranoid - Halo goes Open Source now.
Please have a look here:
Code:
HALO goes open source
Non PA users
Make sure to tell your developer to take a look at these two links:
1. [URL="https://github.com/ParanoidAndroid/android_frameworks_base/commit/518c329e8c67fa96b8a8fc22e1962ddb8497c333"]https://github.com/ParanoidAndroid/a...962ddb8497c333[/URL]
2. [URL="https://github.com/ParanoidAndroid/android_packages_apps_Settings/commit/7c739a86e7a02451a63615d71f1b6c846caacdc6"]https://github.com/ParanoidAndroid/a...1b6c846caacdc6[/URL]
Commits are streamlined and squashed, should be merged in a few minutes easily. HALO is still in beta since support for TabletUI and PIE is unfinished, among other minor things, but it's good enough for a release.
As for the feature itself, I can honestly say it's been the most exciting Android project I've been involved in. I can think of absolutely zero reasons why anyone would dislike it in its current state. I sincerely hope you enjoy it, whatever rom you run.
Facebook
Again, we would like to thank Facebooks clever engineers for this idea. We've had a blast bringing it to new levels and making it entirely and creatively our own. This ain't
just a random carbon copy, we've tried hard to make it adapt Android as best as we can, starting by extending the basic functionality to all apps of course and ending with that sort of integration which you would expect from any native feature.
Google
As for threats to Androids eco system, until now apps react nicely to our changes. Apps adapt, they simply assume a smaller screensize. We do have some remaining issues to clear but this should be safe when we are done. Should any doubt come up as to our integrity, we are prepared to do whatever we can to lessen negative impact. We have created white & blackliststs, we have flagged this feature beta and instructed our users of their responsibility to respect app developers should any issue arise.
We earn nothing from our feature and do this solely because we enjoy Android and the Nexus/AOSP platform. Our goal is not to spread and hack, we simply want to demonstrate that the AOSP platform and its compliant devices are already the creative breeding ground that anyone could wish for.
PA users
There seem to be no crashes or spontaneous reboots that we know of and we have observed and measured it long enough to know it poses no danger for your battery and performance. Therefore the code has been merged into our main branch. You'll get all the features and changes that happened outside of HALO's scope.
I will try to sum up what i see on Git:
- HALO has white & blacklists now. Blacklists can prevent apps from pinging through HALO, whitlists do the same but only allow pinging when you explicetly allow it for single apps, everything is silenced
- dismissal of notifications has been improved
- PA Wallpapers has been taken out of the rom and can be downloaded for free on Google Play: [url]https://play.google.com/store/apps/d...oid.wallpapers[/url]
- DCHSPA+ symbols
- Dirk Rettschlag's Quick unlock
- PIE option for emptyangle (the start gap)
- Birthness dialog updates
- Statusbar date/time layout changes
- Option to use volume keys to control media volume anytime
- Launcher does not need to be started when you go in and out of fullscreen (no more black flicker)
Oh, we took out GooManager since we will soon replace it with a custom solution that will make updating as easy as possible, with full context awareness of course (hybrid props, backups, kernel updates, PA-gapps, etc.).
Enjoy!
regards and thanx for your hard work...
bitstra
All this is really missing is battery percentage, and performance settings. I like built in performance settings, I feel it take up less ram (vs setcpu).
::-::-::-::-::-::-::-::-::-::-::-::-::-::
Okay, I have to ask. Any guides on flashing this to emmc? I was running CM7 on emmc (Got stale), went back to stock 1.4.3, tried rooting but could never get full market, Then saw this and it looks awesome and would love to go for a spin on it. I have the zip files ready to go and a CWM sd card, but I need to know how to get it installed on emmc.
I am on pure stock 1.4.3
Thanks
Geeve
geeve420 said:
Okay, I have to ask. Any guides on flashing this to emmc? I was running CM7 on emmc (Got stale), went back to stock 1.4.3, tried rooting but could never get full market, Then saw this and it looks awesome and would love to go for a spin on it. I have the zip files ready to go and a CWM sd card, but I need to know how to get it installed on emmc.
I am on pure stock 1.4.3
Thanks
Geeve
Click to expand...
Click to collapse
If you have everything on a CWM sd card then just flash it
You can follow my (slightly outdated but mostly valid) guide over here: http://forum.xda-developers.com/showthread.php?t=1030227 Just replace the CM stuff with the stuff from this thread.
Thanks! Gonna give it a go when I get home...
Geeve
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I gave it a try with a clean install. It is actually very impressive. it has smaller foot print, boot up quicker, runs smoother and faster. I think it is perfect for such old device compared to CM10.1, I would have it for daily usage after try it for few days.
I installed it in SD card (EMMC has CM10.1 RC5), and I don't see upgrading android even when I boot from this ROM to CM10.1 (not sure why).
One thing might need some attention is the storage in settings crashes. Again, not sure if it is due to installed in SD card or not. However, it is not a big deal to me.
Another couple of things noticed, it has color band, and youtube won't play HD videos. I really don't care that much compared to the speed of this rom.
Thanks a lot for this great ROM. it is a better choice for my Nook Color.
Not just you. Have it installed on emmc and storage crashes in settings for me as well. I have the color bands too. Haven't tested YouTube yet though....
Great ROM so far! Good job devs! Fast, stable, and runs great!
Thanks
Geeve
Edit: I have the same YouTube problem. Could it be the kernel not using the display correctly? I am by no means a Dev, it just leads me to believe with the color bands and lack of HD that either the driver or kernel isn't doing its thing. Just a thought. Are there any other kernels we can flash to test?
Sent from my NookColor using xda app-developers app
The installation was a breeze, excellent ROM!
I can confirm the crash on Storage settings.
The performance is horrible though. Could it be because of the SD card? I have a 16G SanDIsk, should I go with class 4-10?
Thanks for the heads up on the settings crash...I just grabbed a log cat from it myself. I haven't looked into it, but it shouldn't be too hard. The banding that you mention, that is the background in holo dark, correct? That is actually an upstream AOSP issue. I don't understand how it has lingered so long...it certainly hasn't made it's way to the stock production builds. CM already fixed it back in ICS...http://review.cyanogenmod.org/#/c/14945/. I will add it here as well.
We don't have HD YouTube for PA either. Is that working on CM10.1? I thought not but I have spent very little time on CM10.1 for the Nook (due to my development commitments only...CM is the best.)
I have also been really pleased with the performance of this ROM. I will probably add in CM performance settings, just to make it easy to add our standard 200mhz over clock. There are a couple other small things I will cherry-pick in from other ROMs to make things a little easier. But I don't want to add too much. Like I said in the OP, I want to try and keep this as close to stock AOSP as is reasonable. We already have CM10.1 for this device...no reason to mimic all of it's features. I also think the small footprint is inemof this ROM's best features.
Performance settings, gradient fix for sure. Quick toggles editing has been requested and will be considered. Anything else?
yes, HD Youtube is working on CM10.1. I don't care if it plays HD videos or not, even it plays, it is not perfectly smooth. However, HQ videos have HD video as ads in the front, so most of time, it can't play HQ videos without playing the HD ads ahead.
I totally agree that we shouldn't have all of CM10.1 features, and keep it small footprint. Currently in my opinion, it is better than CM10.1 on Nook color (due to hardware limits). I feel less laggy compared to CM10.1. A full feature ROM like CM10.1 maybe better for new hardwares. for nook color, this rom is almost perfect. It will be perfect after the minor issues fixed.
thanks a lot for your excellent work!
mateorod said:
Thanks for the heads up on the settings crash...I just grabbed a log cat from it myself. I haven't looked into it, but it shouldn't be too hard.
Click to expand...
Click to collapse
Via the AOSP 4.2 port for the Nexus S:
https://github.com/diclusial/platfo...mmit/16edc0f2b53c6713952e297c941ec2aeae1b9adb
steven676 said:
Via the AOSP 4.2 port for the Nexus S:
https://github.com/diclusial/platfo...mmit/16edc0f2b53c6713952e297c941ec2aeae1b9adb
Click to expand...
Click to collapse
Thanks steven! I would guess that you have the actual attribution correct from your find...I am building with an identical commit but with different authorship from the CM project.
https://github.com/CyanogenMod/andr...viceinfo/StorageVolumePreferenceCategory.java
That has pretty much been the method for all bugs here and at AOSPA...how did CM solve it (usually back in cm7, by nemith or dal). Thanks a bunch for the tip.
Welcome to Starship Nexus. A Cyanogen based Rom designed to be lite-weight, simple, fast and efficient like any good Starship should.
THANKS
All praise goes to the CM Team and the Nexus 5 development community.
I had honestly never intended on posting this and was more a project for setting up my phone the way I like it. I have been developing in the past for the most part as part of different organizations who's initial purposes was to just bring Cyanogen to different devices.
https://github.com/Chairshot215
Up until the Nexus 5 I have never owned a supported device so as mentioned have worked with different teams to get CM up and running on mainly Sprint or VM devices. Also being the Art School Dropout that I am have also spent the past few years starting with CM-7 creating alternate themes for each device I have worked on and have released different versions of the starship theme for Sense, Touchwiz and other devices and have created a stockpile of images over the years to work with for each variant all sharing a common design. Unfortunately all those images are HDPI and will not work with the higher resolution of the Nexus 5 but what can I say developing has been a big part of my life over the years and although the Nexus 5 has no shortage more experienced developers it just feels strange not actively working on a Rom so have decided to go ahead and post what I have as I work on theming and adding different options and customizations.
Features Include
Now Launcher as the default Launcher.
G-Camera
Heavily Themed
Bare-bones app selection.
GCC 4.7 Compiled.
many minor modifications to numerous and insignificant to all be listed but includes things like customized text for example changing instances of generic terms like device to be more specific and allowing non market app installation as the default for those of us who may have owned a Kindle and either purchased or installed enough free apps of the day through Amazon that installing the Amazon App Store is a first after flashing. Otherwise would be a lengthy list of changes I don't think would make or brake anyone’s decision on installing the Rom.
Kernel Version is 3..4.41 which is nothing compared to other Kernels. With that said the Kernel is based on the current CM Kernel that although has incorporated many back ports from higher kernel patches starting this late in the game it is not easy to apply other patches even if already done so by other developers because other kernel patches had been made at earlier times so it is not as easy as just cherry picking entire patches as after confirming the CM team has not already incorporated each individual change each change must be tested individually. So anyhow that’s what’s going on with the kernel. Have also incorporated a few other changes not included in the version patches or by the CM Team from other Kernels like Omnirom for example. I would otherwise like to thank all the Nexus 5 Kernel devs as the patches are based on those found in other kernels like UBER and LiquidSmooth taking common commits between many different kernels to form each patch. Otherwise I plan to continue improving the Kernel as I work on the Theme. Kind of excited as for the most part working with other teams have always been the vendor blob guy and looking foreword to learning more about the kernel. The Kernel has not been tested on all CM11 Roms but is compatible with current Official CM-11 builds so probably will work with most CM-11 Roms built from the current source so will include the Kernel only as a separate download.
Each individual change made as part of the Linux Version Patches are explained in detail under the cm-11.0_testing branch. The Version Patch commits are grouped together under the primary cm-11,0 branch without individual explanation for an easy view of what changes or commits made to the Kernel are made outside of the Linux Version Patches. The testing branch link below shows all changes tested before added to the Starship Kernel as well as the individual commits for each change made as part of a Linux Version Patch.
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/cm-11.0_testing
Kernel Source & Change Log
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/cm-11.0
Downloads
Starship Rom (12.25.2014)
Starship_Nexus-20141225-Hammerhead_Class.zip - 302.93 MB
Starship Rom (11.13.2014)
Starship_Nexus-20141113-Hammerhead_Class.zip - 301.79 MB
Core Engine - Kernel 3.4.41 (11.22.2014) - Current
Starship_Hammerhead_Kernel_Engine_3.4.41.zip - 7.68 MB
Core Engine - Kernel 3.4.36 (11.13.2014)
Starship_Hammerhead_Kernel_Engine_3.4.36.zip - 7.68 MB
Core Engine - Kernel 3.4.27 (previous)
Starship_Hammerhead_Kernel_Engine_3.4.27.zip - 7.68 MB
Gapps 20140606 (Not Included)
http://wiki.cyanogenmod.org/w/Google_Apps
Source Repositorys
https://github.com/Starship-Android
I am not responsible for your device or property, in other words use at your own risk!
Thank you for sharing. I'm DL now and will get back with some thoughts and feedback.
Bert
bertcarv said:
Thank you for sharing. I'm DL now and will get back with some thoughts and feedback.
Bert
Click to expand...
Click to collapse
Yeah it is definitly at this point bare to the bones and will post a few screenshots in a bit. Ultimitly I would like to base the theme somthing like the original incarnation of the Rom from what I had done with the Motorola Triumph. Posting a link to the thread for the screenshots to give an idea of what to expect in the future.
http://forum.xda-developers.com/showthread.php?p=27847911&postcount=4
Hmmmm thank you. Trying it now
Screens???
Holy $hit, long time no see, will give it a whirl
Nice seeing you again
Sent from my Nexus 5 using xda app-developers app
Oh new ROM..... downloading..... :silly:
I luv naked ROMs. Thanks for this
Sent from my Nexus 5 using XDA Premium 4 mobile app
Any alternative link?
Dropbox link not working.
Sent from my Nexus 5 using XDA Free mobile app
Love that it is very slim
Sent from my Nexus 5 using xda app-developers app
Sorry had just recently reinstalled Ubuntu over the weekend and had not yet set FTP back up. I added a Mediafire link that will hopefully do the job until I finish work and get a chance to set up FTP again.
In download. Why zip is 284 MB?
yanner2012 said:
In download. Why zip is 284 MB?
Click to expand...
Click to collapse
There is a script that runs the first time the Rom boots that removes allot and moves the necessary files for the now launcher to work correctly from a staging directory to ware they need to be placed in the system & data partitions.
HTTP://github.com/StarshipNexus/android_device_nexus_starship-common/blob/cm-11.0/app-update
After this script has run a second script cleans everything up including the staging directory.
https://github.com/StarshipNexus/android_device_nexus_starship-common/blob/cm-11.0/cleanup
Is done this way to prevent needing a specialized Gapps package for every update as the Now Launcher requires newer libs for Google Search than what is found in the Gapps zip that would be replaced when the Gapps zip is flashed. So in short for multiple reasons the zip is large but by the time it starts installing apps the first time the Rom boots it has been slimmed down pretty well.
Very slim. Now I test it.
I have updated a few new thing. I have first been testing out new Bootanimations and default Wallpapers. Nothing set in stone although kind of dig the new Wallpaper. The Bootanimation is from the G2 as I have also been working on porting the G3 Stock Rom ported to the G2 so is more a port of a port. Anyhow decided to give the Boot animation a try. The G3 is also the source of a few of the new Icons mixed in with a few Blur and other images. Most notably are the buttons and settings divider line. I have also applied patches for the 3.4.16, 17 and 3.4.18 Kernel version patches along with different Audio and a few video Enhancements.
Posted an update, mainly because I found a few parts of the theme hideous. Is definitely getting there though and starting to see glimpses of my pre xxhdmi resolution Starship Roms. Looking at the last updated screenshots definitely need to hit up some text colors for next time. Otherwise happy how things are coming along and posting is definitely motivating my Ars. Think are not yet downloads so going ahead with aditional text color. Just in case will add a b version in a few.
Filename is 20140930 not version b
Made more changes for next time with the Teal blue taking up the right side of the Statusbar leaving the left using the OG White. Doing this because some user intalled apps will add images on the left and think it looks silly mixed up between the two so each side of the Statusbar will have its own color. Using the darker Teal in place of the lighter Teal / Blue coloring I have used since Froyo after reading an article about how certain colors help reduce battery usage from the display depending on the display type of the device. I have been desighning the Rom in a way that it can be built for any device with a CM port official or otherwise with most of the changes being aplied through a Starship Device directory so far requiring only 2 lines added into the device directory importing the Starship directory like shown in the below link to the commit for the Nexus 5. With that said Im going to end up changing the name as I built what has been completed up to this point for a friends Moto as simple as adding the Starship directory and adding two lines into the device directory.
https://github.com/StarshipNexus/an...mmit/45e6b9d410c1cccfcc79562b83d0575db64aabb4
https://github.com/StarshipNexus/android_device_nexus_starship-common
Anyway posting these things in advance because I havnt seen many opinions or feedback on the current look and feel but can see a steady number of downloads so if anyone has an opinion or idea for improvment let me know. The current incarnation or reboot is still very young and as some may have noticed things are changing pretty drasticly version to version so could still use any help anyone is willing to offer.
Instead of reboot think Im going with reimagined, seems to be the new term going around.
Ok. This rom is rock. Do you will its development?
Wallpaper
Anyone got a separate link for the wallpaper please?
TIA
My favorite tweak from cyanogenmod was always the status bar brightness slide control.
I couldn't find any decent way to make that happen in ics stock evo-ware.
Want stereocam and 3d or I'd just run LS 4.4
I googled a bunch on xposed statusbar brightness and found a short reddit thread with the idea of using a bit of gravitybox to do it.
Their source excision was missing a few critical bits.
I got the original jb gravitybox modstatusbar.java, chopped it down, added different initialization process for standalone use.
Source, although very messy, is attached as a zip.
I'll share later when it's cleaned up, in the appropriate forum for xposed modules. This is my very first foray into the world of xposed module creation.
for now, evo users win first.
I had to use a gimmick from another xda thread to build working xposed modules with aide
since all development I've done this calendar year has been strictly on my evo.
At least partly because of that I wanted to toss the finished xposed module apk I built out there in the evo forum before posting anything in the xposed areas of xda.
Slide right/left across statusbar to change brightness or long press it.
temporarily overrides automatic brightness if on. Turn that off for full control.
Thanks to the gravitybox developers for sharing and their fine work!
and that reddit post for pointing me that way.
Reserved against the possibility of future development
Nice app squid, as you know, I've been messing with Liquid and that's been implemented. Does it work with stock based?
PiggyFlooper said:
Nice app squid, as you know, I've been messing with Liquid and that's been implemented. Does it work with stock based?
Click to expand...
Click to collapse
I've only tested it on stock. Dunno if it'd even work on cm-derived stuff. Maybe cm9 but not sure.
It works with Liquid Smooth- is that cm 11?
PiggyFlooper said:
It works with Liquid Smooth- is that cm 11?
Click to expand...
Click to collapse
Cm11 based anyway, there's lots of cm in the LS manifest.
good to know it works on later android versions than 4.0 anyway.
thanks for testing!
It is working on MIUI 8.
akshyapatil said:
It is working on MIUI 8.
Click to expand...
Click to collapse
How did u install it?
Working on FlyMe 6 where GravityBox does not. Thank you!
Hey dev, could you add support for oreo?
maxs8007 said:
Hey dev, could you add support for oreo?
Click to expand...
Click to collapse
The only device booting Oreo I've got to test it on is my evo 3d, and I'm not sure if that build will even run xposed for testing.
Not tons of time to play around, either.
Source code is posted though, if you know someone else who can mod it. Code's mostly from gravitybox with some patchwork to run standalone.
bigsupersquid said:
The only device booting Oreo I've got to test it on is my evo 3d, and I'm not sure if that build will even run xposed for testing.
Not tons of time to play around, either.
Source code is posted though, if you know someone else who can mod it. Code's mostly from gravitybox with some patchwork to run standalone.
Click to expand...
Click to collapse
wow, you still have your evo 3D running, that's amazing. Mine started destroying batteries, I'm jealous
I like a simple OP so ...
Just like the title says this IS and WILL be a CLEAN AOSP rom built from source, I really just build for myself but I don't mind sharing with the community.
You ask why share a basic AOSP rom?, well there are some people here that like a AOSP rom but don't have the time or the resources to build, also at one point I felt that Android in its infancy needed a lot of customization, but now its a lot better, plus with the invention of Xposed there's not enough reason to code in features when you can just download them.
This does not come with Google Apps installed you will have to install the ones you desire just make sure they're compatible with Android 6.0, and also this rom is not rooted so you will need a compatible root solution if you need root.
There is no screen shots since the is a non-themed AOSP rom, which will look like any other AOSP rom so please do not ask, and please be friendly to one another, and also please report anything broken I will try to fix it as I can.
DOWNLOAD:
https://www.androidfilehost.com/?fid=24052804347835456
MD5:
2c1191564a694d53aca3cfdae65ad6f7
Nice!
ooo im first( NOPE 2ND) thanks for the upload ill give it a spin :good:
Finally, thank you so much.
Is it RRO ready?
puertorecon said:
Is it RRO ready?
Click to expand...
Click to collapse
I've been away from the developing scene for awhile you will have to tell me what rro is but its bare no mods except to get stuff working.
I will download and check myself.
puertorecon said:
Is it RRO ready?
Click to expand...
Click to collapse
6.0 has RRO compatibility built into the source.
All that is needed is Root and BusyBox.
Running Layers as we speak on a factory ROM.
I thought Xposed was broke on 6.0?
gr33nd3vil said:
I thought Xposed was broke on 6.0?
Click to expand...
Click to collapse
Yeah but since it will be compatible in the near future, there is no point in adding any flashy features that are xposed-specific into the ROM.
Peylix said:
6.0 has RRO compatibility built into the source. All that is needed is Root and BusyBox. Running Layers as we speak on a factory ROM.
Click to expand...
Click to collapse
The layers now available are for previous versions.
But there is enough working to create a dark interface. The trick is to use layer combinations.
Suggestion for dark: InversionUi, CommuteUi, Scarlett, Blackish
Start with layers for 'framework', 'systemui', 'settings' and 'velvet' only.
Existing layers(not updated) for keyboard, contacts, calendar etc, will not work or text is not readable.
In the play store is a layer manager available. I prefer to extract them manually and transfer the layer-apk's manually to /system/vendor/overlay. After a reboot the layers are active and copied to vendor/overlay.
NLBeev said:
The layers now available are for previous versions.
But there is enough working to create a dark interface. The trick is to use layer combinations.
Suggestion for dark: InversionUi, CommuteUi, Scarlett, Blackish
Start with layers for 'framework', 'systemui', 'settings' and 'velvet' only.
Existing layers(not updated) for keyboard, contacts, calendar etc, will not work or text is not readable.
In the play store is a layer manager available. I prefer to extract them manually and transfer the layer-apk's manually to /system/vendor/overlay. After a reboot the layers are active and copied to vendor/overlay.
Click to expand...
Click to collapse
Many have been updated for 6.0.
Right now I am using Evolve and it's partner CommuteUI. Applied through the Layers Manager app (working on 6.0) and the themes stick on reboot.
I understand if you want to bake this in to a ROM, but I'm just passing along the info that Layers works out of the box with stock factory images of 6.0 with root and busybox installed. No need to rely on AOSP or Custom Roms for Layers now. (My point basically and to answer the initial question I quoted)
Peylix said:
Many have been updated for 6.0.
Click to expand...
Click to collapse
There are still things not touched, like Google contacts. But I keep watching[emoji1]
I understand if you want to bake this in to a ROM,
Click to expand...
Click to collapse
No I just suggested a different approach. A layer manager is not needed. There are a lot of nice layers on 'afh'. I download/extract on the PC (add .zip at the name) and delete the layer-apk's I don't use. Transfer to 'system/vendor/overlay' and reboot is enough. So I use root explorer, but layer manager is also good.
The main point is that the device involved needs Root acces. And when you have Root there are alternative. Just sharing it with the community.
NLBeev said:
There are still things not touched, like Google contacts. But I keep watching[emoji1]
No I just suggested a different approach. A layer manager is not needed. There are a lot of nice layers on 'afh'. I download/extract on the PC (add .zip at the name) and delete the layer-apk's I don't use. Transfer to 'system/vendor/overlay' and reboot is enough. So I use root explorer, but layer manager is also good.
The main point is that the device involved needs Root acces. And when you have Root there are alternative. Just sharing it with the community.
Click to expand...
Click to collapse
Touche.
I don't use Contacts. Just unhid it from Nova and checked. You're right.
Man, I'm spoiled with touch-less interface haha. I RARELY if ever use the phone/contacts app. I just say who I want to call or speak the number. Works better with Tasker cooked in w/ Autovoice.
I also figured you were just listing another way of doing it. It's good to have multiple ways.
Hi.
Thanks for sharing.
Is AOSP SMS application include ?
If yes, is it possible to have an extract of the apk please ?
Cheers
Envoyé de mon Nexus 6
Just a heads up to whoever is using this, there is going to be another release shortly that is much "cleaner" it won't have any of the debugging tools added nor will it have anything that can be found in the PlayStore. This next release is pretty much just barebones and you will need to get a internet browser, camera, gallery app, music app, well you will see whats not there. At any rate I feel that this gives the user more freedom on what they want installed, so this is the new format for this rom and it is complete, the only thing that will happen now is updates to make it better. Also I will be releasing my source for this too if anybody wants to rebuild and add their own spin on it or contribute to the pre-existing rom.
SirOch said:
Hi.
Thanks for sharing.
Is AOSP SMS application include ?
If yes, is it possible to have an extract of the apk please ?
Cheers
Envoyé de mon Nexus 6
Click to expand...
Click to collapse
I don't think there is an AOSP messaging app available.
ANDR01DN00B said:
I don't think there is an AOSP messaging app available.
Click to expand...
Click to collapse
Yeah it is you can just pull it from your phone or extract it out of the update zip.
However its just the same as the Google Messenger app just green instead of blue and doesn't have the extra Google added crap.
jakdillard said:
Yeah it is you can just pull it from your phone or extract it out of the update zip.
However its just the same as the Google Messenger app just green instead of blue and doesn't have the extra Google added crap.
Click to expand...
Click to collapse
But does it have quick reply? And does the action bar color change with the contact that you send the message to?
Thanks!
ANDR01DN00B said:
But does it have quick reply? And does the action bar color change with the contact that you send the message to?
Thanks!
Click to expand...
Click to collapse
You know what it does not. I didn't notice that, it looks like they just gave it a facelift.
Hmmm it might not make the next version either.