Database Users

[ROM][beta]ApHaSia~v1.0~{Non(¢'s)~

Nocoast's unofficial insomnia nonsense. I named it aphasia because i feel like I have brain damage! This is probably the most stable rom I've released, but Ive only had a night to test it
Preface:I got a clenener (CLNR) and was pretty blown away at how fast the interface was with everything stock, so im going to carefully pick through every app from the 605.5 pull every sense element that doesnt have anything but BASIC utility, then replace with fede launcher. Ev3rything is running smoothly. So far no FC's. Please make sure to update your SU binary.
This is NOT a team liquid release, this is just something I whipped up tonight while we wait for LGS to finish up..
so while we wait for the next liquid release to come out, i figured id make something very simple and stable for the nonsense platform.Again. this is not a team liquid release. (if it were it'd have cooler mods lol) This is a team im an insomniac release and jdk told me to do something on gtalk release. Big thanks to HTC for the 605.5 base, thanks android police for hosting it. (I originally built this off a debloat but i wanted to be a freak tonight,,)
The notion behind this rom is that you get a very stable, lean, clean slate with which you can do whatever you like (for those of you who like the stability of a stock rom but can't stand rosie launcher, this is for YOU!)
So the features of this rom are
-removed and as many htc apps/modules as possible, while still keeping it functional (note the personalize button probably wont work)
-Liquid modded fedelauncher -credit to liquid (thank you!)
-IMO's 5.1 Kernel (thanks)
-605.5 base debloated (thanks HTC for the base!)
-deodexed/zipalligned all apps
-custom android boot animation
-Taskiller modifications (customized by myself) done in the kitchen (I think they turned out well...)
-Your choice of stock HTC keyboard, stock gingerbread keyboard, and ics keyboard is included iirc (i havent slept) in order to activate the keyboard just go to input settings and click it on (Credit to TeamLiquid)
-removed, peep, htc facebook, friendstream, basically everything htc
-AOSP MMS APK -FINALLY GOT IT LINKED WITH HTC PEOPLE APP. That means you can click a contact in htc and start an sms and it will open the aosp mms.apk! (believe it or not I killed myself getting this to work in the past and i still had no luck) credit liquid for the aosp mms.apk)
-I forgot to update the superuser binary, should have (one of, if not the) newest superuser apk but youll have to update the binary from within the app (im sorry, hope its not too much of an inconvenience)
if you run into any issues with apps regarding root MAKE SURE you update the su binary
-tons more I've forgotten.
-Since market auto installs all of my prior apps, I dont quite remember if im missing any credits. Credit to the dude who made ICS keyboard if it did wind up in this build aswell as credits to jrummy for rom toolbox (again, that mighta auto installed im fried) and credit to ChainsDD for Superuser
As usual big thanks go to Liquid, perhaps after I brand this and add some liquid tweaks this can be an official liquid release. For now though its just a fun beta I did tonight just to switch the pace up
SCREENERS
{
"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"
}
DOWNLOAD LINKAGE
http://www.multiupload.com/SVQ8080RAP
The base began at about 470 megs, its down to 170. I could probably trim more fat and will but thats all I could get tonight, I rebuilt this thing quite a few times originally starting with DeTards' debloated base, but in the end I found it more stable to just use the stock and debloat myself...
please post any issues you guys have with this.
FINAL DISCLAIMERS, PERSONALIZE AND A FEW OTHER HTC LINKS ARE BROKEN, UNTIL I DECOMPILE SOME STUFF THOSE LINKS WILL REMAIN THERE, THEY DONT CAUSE FCS, THEY JUST LINK YOU BACK HOME.
Comic Sans MS TIME:heh now that ive got your attention please make sure you you dont brick your phone and blame it on me. BLAME IT ON VERIZON. Dont buy a galaxy nexus, I love this community!
DONATE TO LIQUID0624

FIRST!!!
Thanks for the ROM

I put stock messaging back in and this rom is insane with battery and speed. still needs extended power menu.

if you think its phat you should check liquidNonSense

Su binaries is outdated. Giving your Rom a whirl.
Sent from my ADR6400L using Tapatalk

Official one plus rom 5.0 alpha

https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/

thanks for posting, great suprise from OnePlus to 2015

Video
https://www.youtube.com/watch?feature=player_embedded&v=LWa-6yCFwTg

Does anyone know how to remove this logo?
{
"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"
}
It's a shame OnePlus and Cyanogen part ways, although Cyanogen seems to be the bad guy.. These guy originated from the custom rom community didn't they? When money enters the game...
The proposed Lollipop rom seems mostly vanilla 5.0 (and not 5.0.2), let's hope it's stable and OnePlus doesn't go the Oppo way...

nobody needs cm anyway.

Any new radio or firmware?
I'm sure some will dissect to find out.

To anyone thinking about flashing it
I flashed it and get no data and wont connect to wifi. Also the fastboot has been changed and is chinese now. So for me at least I am unable to use it at all on the 64gb international. Think im gonna push my recovery back onto the phone and go back to CM11s.
Edit: Manually put in APN's for ATT LTE and getting 4g icon but no LTE icon, didnt get GApps installed so dont have speedtest installed to verify speed. Still unable to get Wifi to work. however though which is a must for me.

Gigantic piece of crap ROM. You guys say no one needs CM but ask those lame developers from Oneplus where they got their build tree. They are building Cyanogen almost stock stripping out many features, and worst, the crappy rom messes up twrp and fastboot.
If Cyanogen stops providing support for the OPO the device will turn into crap.

lordneopt said:
Gigantic piece of crap ROM. You guys say no one needs CM but ask those lame ass developers from Oneplus where they got their build tree. They are building Cyanogen almost stock stripping out many features, and worst, the crappy rom messes up twrp and fastboot.
If Cyanogen stops providing support for the OPO the device will turn into crap.
Click to expand...
Click to collapse
Have you got any evidence for that?
This appears to be a pure aosp build using caf code.
The features aren't stripped out, it's aosp. Is how it comes, bear boned to be built upon.
Sent from my A0001 using Tapatalk

ToXicWinter said:
I flashed it and get no data and wont connect to wifi. Also the fastboot has been changed and is chinese now. So for me at least I am unable to use it at all on the 64gb international. Think im gonna push my recovery back onto the phone and go back to CM11s.
Edit: Manually put in APN's for ATT LTE and getting 4g icon but no LTE icon, didnt get GApps installed so dont have speedtest installed to verify speed. Still unable to get Wifi to work. however though which is a must for me.
Click to expand...
Click to collapse
Ha, same here. This rom destroyed my phone lol.
lordneopt said:
Gigantic piece of crap ROM. You guys say no one needs CM but ask those lame developers from Oneplus where they got their build tree. They are building Cyanogen almost stock stripping out many features, and worst, the crappy rom messes up twrp and fastboot.
If Cyanogen stops providing support for the OPO the device will turn into crap.
Click to expand...
Click to collapse
You are a bit extreme, but you're right. My fav feature of this phone was 11S out of the box.

[ROM] [NIGHTLY] [Shamu/Nexus6] Stock CM12.1 builds - everyday nightly builds

welcome to official nightly builds for Shamu(nexus6)
{
"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"
}
source CM website:
http://www.cyanogenmod.org/blog/the-l-is-for-lollipop
DOWNLOAD nightly ROM:
https://download.cyanogenmod.org/?device=shamu
DOWNLOAD GAPPS:
http://forum.xda-developers.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
With that, some words of wisdom:
1.This is an Android 5.1 Lollipop-based release - update your third party addons to ensure compatibility
2.The CM backupscript.sh in recovery will ignore and remove incompatible applications from your system partition (these are usually non-CM apps that users have opted to install). You must install a compatible app (or app pack) to regain that functionality
3.You can flash CM12.1 nightlies directly from CM11 M12 or CM 11 nightlies (no need to wipe), provided you read and followed items 1 and 2
4.Once on CM12.1 nightlies, you cannot downgrade back to CM11 without wiping – if you are thinking of just exploring the release, then take a backup of your existing installation if you want to go back to it.
5.You’ll need an L compatible recovery DOWNLOAD post #2 [TWRP - install]
6.For those which have problem with root acces - flashable superSU file via custom recovery.
6a.Check also on developer options is there root acces is "thick" for APPS+ADB
enjoy!

Any added features or stock?

eighty1 said:
Any added features or stock?
Click to expand...
Click to collapse
"We would like to note that at this point we consider ourselves 85% complete for our initial CM12 M release. We’ll spend the remainder of this month bringing up additional devices and finishing up the features you’ve come to love from CM11 – implementing them into the new Material UI.
At this point, the following large items are not implemented, but should be in the next few weeks. Some additional smaller tweaks are also missing, but left off this list:
Theme Engine
Quick Settings reorganization and customization
Quick Settings Ribbon mode
Navigation bar reorganization and customization
Sound panel customization
Lock-screen quick unlock"

Thank you for this!! Been waiting patiently! Gonna d/l and flash now.

Awesome! the wait is over!
Is encryption disabled?

Pliind said:
Awesome! the wait is over!
Is encryption disabled?
Click to expand...
Click to collapse
Unless they changed their policy, this was their stance on encryption for OFFICIAL releases as of 10/31. You can still flash a different kernel that supports unencrypted volumes though, or install an unofficial release that comes with a different kernel.
"Items not up for debate:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release."

hopefully the theme engine will be here soon just waiting for that before I flash.

Verizon LTE Support??
Does this support Verizon LTE or is it plagued by the ongoing issues found with some of the other CM-based ROMs for shamu?

you have to try your own couse it is avialible from couple of hours

dligon said:
hopefully the theme engine will be here soon just waiting for that before I flash.
Click to expand...
Click to collapse
Gotta ask..... any known bugs with any carriers?
Some of the other roms see issues like no data on certain carriers. I am running LS on sprint and it is working good except i have sms fail occasionally.
*EDIT*
Had the reply window open to long
aes512 said:
Does this support Verizon LTE or is it plagued by the ongoing issues found with some of the other CM-based ROMs for shamu?
Click to expand...
Click to collapse
Not the only one with these questions. I think i might try this with sprint but it will be a few hours before i do.

JasonJoel said:
Unless they changed their policy, this was their stance on encryption for OFFICIAL releases as of 10/31. You can still flash a different kernel that supports unencrypted volumes though, or install an unofficial release that comes with a different kernel.
"Items not up for debate:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release."
Click to expand...
Click to collapse
Alright, but flashing franco-kernel after should keep my unecrypted device decrypted? correct? I'm sure many other people reading this are wondering the same thing.

Pliind said:
Alright, but flashing franco-kernel after should keep my unecrypted device decrypted? correct? I'm sure many other people reading this are wondering the same thing.
Click to expand...
Click to collapse
Yes

Pliind said:
Alright, but flashing franco-kernel after should keep my unecrypted device decrypted? correct? I'm sure many other people reading this are wondering the same thing.
Click to expand...
Click to collapse
Yes..
Sent from my Nexus 6 using XDA Free mobile app

Shouldn't this be in Original Android development since this is the official thread?

I have install this build and first impression:
DIALER is much response compared to pure shamu rom + sensei kernel
no lag
no SOD
phone is not hot
during install this ROM phone being encrypted (it takes 30s)
it needs time to say more

Downloading now to see

one more thing so much important :
enough loud voice during a call without any modification! (out of the box)

what kernel would you guys recommend using to stay as close as possible to stock but with out encryption?

ROOT is a little different. Took me awhile to figure out that privacy guard has to be enabled on the app to recognize superuser access. Looks good other than the white background is killing me! cant wait for themes.

greenify seems to freeze the phone when using this first nightly. weird cuz it didnt happen with the unofficial builds.

[Clover-AOSP] 5.1.1 [cancro]

{
"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"
}
Overview
Pure AOSP for Cancro
Features
- No T-mobile theme engine or Layers, It is just stock AOSP.
- No .dat features
Download
Developer-Preview-1
Working
- Everything (unless I missed something, pretty sure I didn't)
Sources
My codebase is uploading.
GPL stuff:
Kernel used can be found here
Extended Information
I created this for firmware developers, It is for forking stock firmware such as MIUI.
If people choose to use this to port MIUI I obviously cannot stop them, but blah blah, beta software, blah.
This firmware uses the structure everyone loved in KitKat; I will not force anyone to deal with the .dat nonsense that we've all come to know and hate.
The codebase aligns very closely to what Xiaomi uses, and this code-base also aligns with many other vendor firmware.
Thx to: Datagutt, Heheda; co-maintainers :<
Thx to: Firmware developers, the source builders for this device

What is this exactly?

Works on mi4 ?

tendulkaradi said:
What is this exactly?
Click to expand...
Click to collapse
It's pure AOSP, and yes it's good to work on any device that idents as Cancro
It is designed specifically for use with porting firmware, recovery has been modded in source to allow for this more easily as well.
It is easy to build either CAF or deCAF firmware in this build engine, I designed it to be very easy like CyanogenMod and it does accept CM configs.
HOWEVER IT IS AOSP AND NOT SLIMROM OR CYANOGEN I can't stress this enough, It is AOSP

Will work for mi4.?

droidead said:
Will work for mi4.?
Click to expand...
Click to collapse
He already answered this question

@MonoIiths can you try building the Android M 6.0 (AOSP) with the same tree and blobs?

Link not working

contactwajeeh said:
@MonoIiths can you try building the Android M 6.0 (AOSP) with the same tree and blobs?
Click to expand...
Click to collapse
Ivan is already building android M. He will give a base rom which can be used for custom roms.

vishal24387 said:
Ivan is already building android M. He will give a base rom which can be used for custom roms.
Click to expand...
Click to collapse
My work is better
Edit: At least with source-build; his AOSP is not useful for porting ROM where mine actually is.
Android M will be the same in that case; when I decide to build it

Ir blaster an FM work in this rom?

camera quality, HDR?

hdr bug is still present, hdr mode click complete dark pictures, normal mode quality is fine. Can u manage to focus on camera quality .otherwise rom is good ,still haven't tested full

Source is still uploading?
Sent from my MI 3W using Tapatalk

Bitti09 said:
Source is still uploading?
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
Yes, my build engine is really huge and has multiple GCC forks depending on the firmware used :<

Neat clean stock ROM. Though meant to for porting and etc stuff. But as a user I like it, it's smoooth.
Everything is great except some minor stuff eg: long Wi-Fi turning on time, WCDMA Only mode reset after reboot, CPU frequency control not working proper with stock kernel.
These are minor stuff and I'm not complaining neither asking you to do anything about it.
PS if anybody has a solution for 3G Only reset would be glad.
Hope I can see a 6.0 ROM by you soon

Also, there's a lag between screen and capacitive keys becoming inactive.. say if I turn off screen and the very next second I touch capacitive keys the screen wakes up.

MonoIiths said:
My work is better
Edit: At least with source-build; his AOSP is not useful for porting ROM where mine actually is.
Android M will be the same in that case; when I decide to build it
Click to expand...
Click to collapse
We already Have @Bitti09 for this...we already have lots of lollipop ROMs...and u are late by a year ?
Sent from my MI 3W using Tapatalk

tendulkaradi said:
We already Have @Bitti09 for this...we already have lots of lollipop ROMs...and u are late by a year
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
But you still don't have 5.1.1 MIUI v7

MonoIiths said:
But you still don't have 5.1.1 MIUI v7
Click to expand...
Click to collapse
But we have bunch of official lollipop custom roms.

AOSP port to Note-4 trltexx,trltedt

Greeting Developers ,
I am new to this ROM building/porting process.
I want to install Vanilla Android on my note-4, so after questioning Google number of times, I came across official Android development guide on official Android website: https://source.android.com/source/downloading.html
I have downloaded the Android source locally and was following various Guides and tutorials from XDA-University & forums only for the development process. http://xda-university.com/as-a-devel...ng-source-code
I discovered that for downloading/configuring the build for a specific device(trltexx), we need to create a localmanifest file that contains device tree, vendor and kernel configuration links for repo syncing.
Now, I want your expertise to guide me forward from this point. Questions being:
1. Can I use CM or other projects (eg. AICP etc.) device configurations for this AOSP project.
2. Can I use these configurations for cross-version android build, say if I want to compile version 6.x, can 5.x configs can be used. (Manufacturer will take several months to release version update)
or Create new configurations using some guide/tutorial/book or something.
In XDA, I know I'm at the write place posting my questions and asking for expertised help.
Thanks!!

Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe

contramundi said:
Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe
Click to expand...
Click to collapse
Thanks for your reply @contramundi, I got N-910G which is a snapdragon version. I just want to know if I can use AOSP sources from google and device configurations from CM, AOSP rom can be built or I need to use specific device configurations for AOSP.

Why?
There's no need to start a whole thread for this as there are numerous threads to ask such a simple question. You didn't say which version of AOSP you were building, but regardless-- yes, you can try to start with CM device trees, but prepared to change quite a bit as there are quite a few dependencies on CM enhancements there.
If you want a truly "vanilla" experience, I"d use the Code Aurora sources, not AOSP's, as CA has all the latest Qualcomm support/bug fixes for MSM and APQ devices, which only may hit the AOSP tree when they do a new release. It is the repository where Samsung starts with their version of Android, and it's where CM also gets its qcom support/repositories.
Gekke, slahyer, and I have done the work to make the Note 4 build/work-- both for lollipop and now starting for 6.0 Marshmallow. And speaking of 6.0, before you even think of building that w/AOSP, you'd also need tons of patches for the Samsung kernel which I also have also already done.
Rather than just applying our work to vanilla AOSP though, you're welcome to join the community effort on CM 13, which has already been successfully built for tmo, eur/xx, spr, and edge so far) on the other thread. You'll need to read about the last two months of posts to catch up. I also posted a link to instructions on building CM-13 in my .sig below.
If you are insisting on straight AOSP by yourself, I would recommend you look at the shamu (Nexus 6) model. It is the same soc as the Note 4, albeit with different peripherals (screen, fingerprint reader, etc.). But it might be a place to start. My build instructions would need some slight tweaking for vanilla AOSP, but I'm sure you could figure it out.
ft

Compiling 8.1 oreo for note 4
Hi,I have been trying to compile aosp for note 4 snapdragon variant.I have downloaded the repo and the required files.I started the compilation and after 25% of the compilation is over,it shows some error and stops the process.Can anyone please help me.I have added the screenshots for reference.
{
"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"
}