- - OnePlus 2 Original Android Development

Closed

THANKS FOR POSTING! About to try it out now. ALSO, I'm a noob when it comes to development, but how could this rom be pure AOSP if the kernel is based on CM?

OmegaBlaze said:
THANKS FOR POSTING! About to try it out now. ALSO, I'm a noob when it comes to development, but how could this rom be pure AOSP if the kernel is based on CM?
Click to expand...
Click to collapse
It's not pure AOSP. There is no such thing as pure AOSP except whatever is built from Google's source for the Nexus devices.

LiquidSolstice said:
It's not pure AOSP. There is no such thing as pure AOSP except whatever is built from Google's source for the Nexus devices.
Click to expand...
Click to collapse
Facts!
And at the end of the day, damn ROM won't even boot up. Back to Oxygen.

OmegaBlaze said:
Facts!
And at the end of the day, damn ROM won't even boot up. Back to Oxygen.
Click to expand...
Click to collapse
Please, be a bit more constructive, this isn't a way to support rom development.
Any data wipes? or kinda info that can allow to devs know where is the problem..

OmegaBlaze said:
Facts!
And at the end of the day, damn ROM won't even boot up. Back to Oxygen.
Click to expand...
Click to collapse
Your CM kernel doesn't build by default in an AOSP build engine so a lot of it I constructed by hand.
It seemed to build without error; maybe I was wrong here
Edit: Some things I KANG'd from CM but does it really matter? If you're really a developer and have looked at kernel code you should know it's all mostly generic anyway the same way android code is so I don't entirely understand you

LiquidSolstice said:
It's not pure AOSP. There is no such thing as pure AOSP except whatever is built from Google's source for the Nexus devices.
Click to expand...
Click to collapse
Pure AOSP is defined as Android code without any aftermarket changes like what is found in CyanogenMod 12 (t-mobile theme engine etc)
If Google uses an AOSP code-base to build for Nexus and decides for w/ reason to build for a Motorola device (It was owned by Google so not that far out of reality) does that mean the Moto device does not have AOSP even if it was generated from the same code?

Henxu said:
Please, be a bit more constructive, this isn't a way to support rom development.
Any data wipes? or kinda info that can allow to devs know where is the problem..
Click to expand...
Click to collapse
I don't even know that he's just not dumb and did something wrong; honestly

@Monoliths
I wiped data, system, dalvik cache, and cache (TWRP 2.8.7.0). Flashed the ROM BY ITSELF and also flashed it with GAPPS.
Neither booted up. The Bootanimation just kept going and going.

OmegaBlaze said:
@Monoliths
I wiped data, system, dalvik cache, and cache (TWRP 2.8.7.0). Flashed the ROM BY ITSELF and also flashed it with GAPPS.
Neither booted up. The Bootanimation just kept going and going.
Click to expand...
Click to collapse
Okok, I'll close this topic. If you can't provide ADB or if it doesn't work this is a fruitless endeavor

Cant understand with ppl who is demanding so much for free service.
Sent from my ONE A2001 using Tapatalk

Thread Closed....

Related

[ROM] PMDroid AOSP Gingerbread 2.3.3 (Version 0.2)

PMDROID AOSP Gingerbread ROM​100% AOSP Android Gingerbread Build from Source.
Be sure that you're based on a Froyo FW! CRUCIAL.
2 Sdcards Mount on PC, new Kernel and Prerooted
Version 0.2 New Fixes
Version 0.1 Initial Release
What's working:
MTD
Radio
Audio
GPS
Wifi
Bluetooth
3D
HQ Video PLayback
internal SD-Card
external SD-Card
Most Sensors​
What's not working:
Polling problem on RIL (works after lock and unlock)
Compass (works not at 100%)
USB sharing of external SD-Card
commands: reboot recovery, reboot download (maybe not possible to implement)
FM-Radio
TV-Out
The same Like Cyanogenmod
1: Load these files:
2: Copy all files except:
speedmod-kernel-k13c-500hz.tar & cm7-galaxys-initial-kernel.tar
3: Flash speedmod-kernel-k13c-500hz.tar via Odin, wait for reboot and after that shutdown
4: Start via 3-button-combo in recovery mode and install galaxys-efsbackup.zip
5: Pull out battery and in again, start via 3-button-combo via download mode and flash cm7-galaxys-initial-kernel.tar via Odin BUT DON'T check repartition and auto reboot
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
7: Choose "mounts & storage" and format system, data, cache
8: Flash PMDroid AOSP Gingerbread.​
not to be an ass but maybe you should give credits to some people and upload your code to a github etc. rep since you are most likely using code of the cm7 project and google.
thx for your work gonna try it
it sounds so well men, great work!
Nice copy and paste from the MIUI thread nah it's cool, looks good but remember to give cred to all involved .
Sent from my GT-I9000 using XDA Premium App
[ROM] PMDroid AOSP Gingerbread 2.3.3
Click to expand...
Click to collapse
hm,
it's not even AOSP
it's modified AOSP thus CM7
any modifications you made to the kernel source ?
thanks !
It's Your Kernel and i will add it to the Op tomorrow
sorry for my Bad english
zacharias.maladroit said:
hm,
it's not even AOSP
it's modified AOSP thus CM7
any modifications you made to the kernel source ?
thanks !
Click to expand...
Click to collapse
Screenshots would be nice
It's so smooth!
This seems like a project heavily based off the work of the CM7 team and other kernel devs, only without the inherent benefits of CyanogenMod and the work the experienced developers have put into it. Exactly what is the benefit of this project?
Am I right in thinking you could take any nexus s rom and just slap this or bilboas kernel on it?
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
This seems like a project heavily based off the work of the CM7 team and other kernel devs, only without the inherent benefits of CyanogenMod and the work the experienced developers have put into it. Exactly what is the benefit of this project?
Click to expand...
Click to collapse
Some people consider cm to be bloated as it comes with excessive features not required by some users.
Bloat == less responsive. So w/e there's cm builds, u'll see aosp builds.
Why ? One simple reason, u get stock and nothing but stock.
Daneshm90 said:
Some people consider cm to be bloated as it comes with excessive features not required by some users.
Bloat == less responsive. So w/e there's cm builds, u'll see aosp builds.
Why ? One simple reason, u get stock and nothing but stock.
Click to expand...
Click to collapse
To be honest I don't think there is any measurable difference in performance between CM and AOSP on a device like the Galaxy S...IMO the features outweigh any preconceived ideas about slower performance that aren't really based reality. But if it's all about the clean AOSP "feeling" then go right ahead.
chambo622 said:
To be honest I don't think there is any measurable difference in performance between CM and AOSP on a device like the Galaxy S...IMO the features outweigh any preconceived ideas about slower performance that aren't really based reality. But if it's all about the clean AOSP "feeling" then go right ahead.
Click to expand...
Click to collapse
Yup i completely agree, especially on these high end devices.
This idea of having aosp clean builds originated however from previous generation devices such as g1,magic...etc where aosp builds seemed to be preferred by a lot.
Daneshm90 said:
Yup i completely agree, especially on these high end devices.
This idea of having aosp clean builds originated however from previous generation devices such as g1,magic...etc where aosp builds seemed to be preferred by a lot.
Click to expand...
Click to collapse
My brother uses a G1 and on their it's clear that in order for Froyo or Gingerbread to be usable it needs to be as light as possible. But this primarily pertains to memory usage...CM6/7 is pretty smooth, just apps don't stay open.
On Galaxy S I don't really think pure AOSP has any tangible benefits over CM7 which is quite obviously based on AOSP. For instance, MIUI, while it should feel more "bloated," feels 100% the same performance wise as CM7 which is great (they share kernel etc. so that makes sense)
Hey Guys,
I installed this on my cappy cause I wanted less bloat. Change the lib files for auto-rotation and flashed bilboas kernel. Working fine. Issue is this dosen't have root. How would I go about doing that? I tried super one click, but it freezes the app. Any help would be appreciated.
MAMBO04 said:
Nice copy and paste from the MIUI thread nah it's cool, looks good but remember to give cred to all involved .
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yeah... nice "description" there.
Anyway, good luck with the project then.
Sent from my GT-I9000 using XDA App
phoenix2217 said:
Hey Guys,
I installed this on my cappy cause I wanted less bloat. Change the lib files for auto-rotation and flashed bilboas kernel. Working fine. Issue is this dosen't have root. How would I go about doing that? I tried super one click, but it freezes the app. Any help would be appreciated.
Click to expand...
Click to collapse
On the zip file of the rom, copy the superuser apk onto /system/app
Then just reinstall the rom
Enviado desde mi GT-I9000 con android 2.3.3
awesome project, hopefully your project will soon overtake cm7 in terms of development speed. I have been waiting for a stable aosp like rom for almost a year now cm7 doesn't cut it for me, battery drain is crazy. Please keep at it and thank you very much
Sent from my GT-I9000 using XDA App
Nice !
I'll test it
schiphol said:
awesome project, hopefully your project will soon overtake cm7 in terms of development speed. I have been waiting for a stable aosp like rom for almost a year now cm7 doesn't cut it for me, battery drain is crazy. Please keep at it and thank you very much
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Have you done any reading? This project is entirely dependent on the work that codeworkx and the CM7 team has been doing. This project won't "overtake it"; I doubt this dev (no offense to OP) has anywhere near the experience or technical ability to troubleshoot problems with AOSP on Galaxy S like codeworkx, dumdidum, et all have been doing for months.
Battery drain on CM7 (and other ROMs that utilize its work like MIUI) is worse than Samsung based ROMs, sure. But it's not "crazy" at all and for my usage patterns isn't even a problem...I charge every night anyway. To me it's either one full day, or two full days, not in between. I've never had a ROM last me through two full days, therefore, I need to charge every night and it doesn't matter if I have 20% or 40% left.

[wip][rom][aosp] ns2

Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...
Reserved for changelog, when hopefully it gets that far
Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App
O_OMG <3 :-!
Sent from my SPH-D710 using xda premium
Good luck! Looking forward to this.
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?
thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock
xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?
Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?
thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!
thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium
it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium

[ROM] [2012/07/18] AOKP Milestone 6 [unofficial]

Hi!
I wanted a 'stock' AOKP Build and couldn't find so I tried and built one...
Thanks to LorDClockaN (IceColdAOKP) for the device specific files and the vendor setup for AOKP.
So you get a pure AOKP synced with the latest AOKP changes with device specific fixes for the One X.
Changelog
same as AOKP - plus:
- Fixed Black-Screen on rotation
- Fixed button timeout (fix by tbalden)
2012/07/18
- Fixed some issues with Camera/Videorecording
I want to keep the main packages the same as in AOKP and just integrate device specific fixes - so no added features
Installation
Flash ROM
Flash GApps
Reboot into fastboot
Flash boot.img via fastboot (fastboot flash boot boot.img)
Reboot
Bonus: No wipe required when you are currently on IceColdAOKP ;-)
Downloads
Download (in sync with AOKP Milestone 6)
GApps can be found here
Sources and Changes/Commits can be found here
I recommend flashing the GPS tweak from here
thanks for your hard work.
it would be better to work with LorDClockaN ?
Tutorial.
But icedcold is pure aokp? What makes this different?
offenberg said:
But icedcold is pure aokp? What makes this different?
Click to expand...
Click to collapse
IceCold has some features added that are not (or at least not now) in AOKP - like profiles for example...
karoodee said:
IceCold has some features added that are not (or at least not now) in AOKP - like profiles for example...
Click to expand...
Click to collapse
Ok. But the issues list is exactly the same?
Should be mostly the Same, yes...
Which device and vendor trees is this built off?
EDIT: Nevermind, realised you've stated it in the OP.
Not being funny here and apologies if you think i am having a dig but you need to write abit more info on what you are sharing here...first you can give us even a tiny changelog please and if so as well few screenshots....
cause you are sharing something in the development section so as far as i know you can be sharing anything...so it is for the benefit of us the users who want to download this and also for the safety of your back so at least you showed the user what they are actually flashing on there phones...
and welcome it is always nice to have more roms but if you can add the above to the OP you will be good to go and hoping for more AOKP magic
Goku80 said:
Not being funny here and apologies if you think i am having a dig but you need to write abit more info on what you are sharing here...first you can give us even a tiny changelog please and if so as well few screenshots....
cause you are sharing something in the development section so as far as i know you can be sharing anything...so it is for the benefit of us the users who want to download this and also for the safety of your back so at least you showed the user what they are actually flashing on there phones...
and welcome it is always nice to have more roms but if you can add the above to the OP you will be good to go and hoping for more AOKP magic
Click to expand...
Click to collapse
Hey there!
Updated the Post and added more info. Are screenshots madatory? The ROM looks exactly like any other AOKP 0_o If I have to I will add some...
Not discouraging development but man, I really really wish people would work together and come up with - in the very least - an "official" AOSP/AOKP XDA ROM. Not CM9, not Trip's (no offense Trip) not any other variant.
Just get together and work on fixes together. These AOKP ROMs all over the place are confusing a lot of people.
karoodee said:
Hey there!
Updated the Post and added more info. Are screenshots madatory? The ROM looks exactly like any other AOKP 0_o If I have to I will add some...
Click to expand...
Click to collapse
No dude it's not mandatory but just check others thread and you see what I am talking about. Anyway thanks for changing it.
Sent from my HTC One X using Tapatalk 2
Quiksilver78 said:
Not discouraging development but man, I really really wish people would work together and come up with - in the very least - an "official" AOSP/AOKP XDA ROM. Not CM9, not Trip's (no offense Trip) not any other variant.
Just get together and work on fixes together. These AOKP ROMs all over the place are confusing a lot of people.
Click to expand...
Click to collapse
As there are lot of AOKP roms so are Sense ROMs like ARHD, Viper etc. Why dont you ask them to work together also instead of just singling out AOKP?
No offense just suggesting.
karoodee said:
Hi!
I wanted a 'stock' AOKP Build and couldn't find so I tried and built one...
Thanks to LorDClockaN (IceColdAOKP) for the device specific files and the vendor setup for AOKP.
So you get a pure AOKP synced with the latest AOKP changes with device specific fixes for the One X.
Changelog
same as AOKP - plus:
- Fixed Black-Screen on rotation
- Fixed button timeout (fix by tbalden)
I want to keep the main packages the same as in AOKP and just integrate device specific fixes - so no added features
Installation
Flash ROM
Flash GApps
Reboot into fastboot
Flash boot.img via fastboot (fastboot flash boot boot.img)
Reboot
Bonus: No wipe required when you are currently on IceColdAOKP ;-)
Downloads
Download (in sync with AOKP Milestone 6)
GApps can be found here
Sources and Changes/Commits can be found here
I recommend flashing the GPS tweak from here
Click to expand...
Click to collapse
First one to hit thanks Nice work, will try it out
Sent from my HTC One X
Is the default launcher in this modifiable? Or we need a custom one for that?
Sent from my HTC One X
theDroidfanatic said:
Is the default launcher in this modifiable? Or we need a custom one for that?
Click to expand...
Click to collapse
Launcher2 and NovaLauncher is included but you can install and use whichever you want
gani_d said:
As there are lot of AOKP roms so are Sense ROMs like ARHD, Viper etc. Why dont you ask them to work together also instead of just singling out AOKP?
No offense just suggesting.
Click to expand...
Click to collapse
He did, he said AOKP/AOSP, CM9 is covered under AOSP, and AOKP is just a derivative of CM9 anyway, building AOKP isn't any different than CM9 as the device specific stuff is the same.
The (seemingly) most efficient solution would be for everyone wishing to develop for an AOSP-based ROM to join tbalden and mdeejay in their TeamNDVRu organisation on GitHub.
gani_d said:
As there are lot of AOKP roms so are Sense ROMs like ARHD, Viper etc. Why dont you ask them to work together also instead of just singling out AOKP?
No offense just suggesting.
Click to expand...
Click to collapse
That wouldn't work, since they are in a way competing and all have different stuff, some are stock, but fast, some are based on leaked bases, some are totally customizable (LeeDrOiD and ViperX) etc., but CM9 is... well, CM9, so it actually makes *sense* (pun intended xP) to work on one rom
Sent from my HTC One X
whats the main diferences between IceCold and this rom ?
the profiles .. and .. ?
gani_d said:
As there are lot of AOKP roms so are Sense ROMs like ARHD, Viper etc. Why dont you ask them to work together also instead of just singling out AOKP?
No offense just suggesting.
Click to expand...
Click to collapse
Apples and Oranges.
Sense ROMs are based off HTC's official release. There is no such official release from Google for the HTC One X unfortunately. So until that happens, I just wish everyone could band together and release a pure AOSP ROM and THEN have developers apply their tweaks to their hearts' content, kanging the hell out of the AOSP build until they're blue in the face.
So far, these AOKP releases are like a virus. They all attach to one device tree, bugs and all, and virtually release the same (seemingly) ROM. When someone squashes a bug, they all copy it. It's just redundant work that could be channeled towards finishing one master build rather than having multiple ones floating around.
To give some food for thought, this is like having the CyanogenMod developers working individually to release their own version of CM9 or CM10.
Apologies for derailing this thread.

[ROM][SUBSTRATUM][N9] Krexus 7.1.1 [OFFICIAL] [03.09.2017]

krexus_7.1.1-170309-flounder.zip - https://www.androidfilehost.com/?w=files&flid=144667 March security updates & Rootless Substratum
THINGS TO READ BEFORE ASKING:
Use N4F26T Vendor Image for 03/09.2017 build.
Stock kernel does not force encryption.
Not prerooted.
Built for the Nexus 9 Wifi (but it works on Nexus 9 LTE too. Flash latest volantisg vendor IMG and manually set APN)
Originally Posted by @KreAch3R
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Click to expand...
Click to collapse
Google+ Community
PushBullet Channel
DOWNLOAD LINKS:
KREXUS on AndroidFileHost
Previous Builds
CHANGELOG
Source Code: https://github.com/krexus
When @KreAch3R started building this ROM for shamu in 2015, I jumped on board right away. I've got Krexus running on every Nexus in my family: mako, hammerhead, shamu, grouper, and NOW flounder.
It runs beautifully on flounder and I hope you enjoy it too.
I am extremely grateful to @KreAch3R for all of his help and support.
IMPORTANT POINTS:
You have to flash GApps (Open or BaNks recommended)
ROM is not rooted, flash stable SuperSu for root
Busybox is included
Included kernel is stock no-force-encrypt
Flash newest factory vendor.img (I had Layers issues with stock selinux enforcing kernel on an older vendor version. Newest vendor.img works perfectly with stock kernel enforcing and layers)
F.A.Q.
a.k.a questions you shouldn't repost
Check the always updated F.A.Q.:
https://plus.google.com/+GeorgeGian/posts/f9m7zmi42Gy
OR
https://docs.google.com/document/d/1hMX-lQ2iUiNsrhszMIlp0Wwj1tSHWvsaEQ_yT4pD_eE/edit?usp=sharing?
BELIEVE ME, THE QUESTION YOU HAVE IS PROBABLY ANSWERED THERE.
Thank you for supporting the building for flounder, @buffal0b1ll!
For the next build, I will try to make Layers work with the default google kernel, and fix the processor info.
I want to specifically thank @BeansTown106, which device trees and blobs I used for this bringup.
Enjoy Krexus!
Another more conspicuous link for the Krexus G+ community.
https://plus.google.com/communities/117603046007221302455/
You will want to join this community if you like Krexus. It's very beneficial to hear user and developer advice/feedback and experiences across all supported devices.
Firsties!
Sent from my Motorola Nexus 6 using XDA Labs
Finally, we are starting to get some more quality ROM builds for this device. This is just awesome.
KreAch3R said:
For the next build, I will try to make Layers work with the default google kernel
Click to expand...
Click to collapse
Layers actually works fine with the default kernel and SELinux enforcing. An up to date vendor.img flash was all I needed to fix that.
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
Try the purenexus version of fire & ice
Sent from my Nexus 9 using XDA-Developers mobile app
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
I'm still using fire-ice 10.2.2 and haven't noticed slow charging. In 18 minutes I went from 27 to 35% just now. Ampere has me charging at 1460 mAh
Thanks for a great rom! Will it work with LTE version?
maelfilk said:
Thanks for a great rom! Will it work with LTE version?
Click to expand...
Click to collapse
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
KreAch3R said:
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
Click to expand...
Click to collapse
Will try it out on the weekend and report
Works great with LTE version!:good:
maelfilk said:
Works great with LTE version!:good:
Click to expand...
Click to collapse
That's awesome! Any hoops you had to jump thru?
buffal0b1ll said:
That's awesome! Any hoops you had to jump thru?
Click to expand...
Click to collapse
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
maelfilk said:
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
Click to expand...
Click to collapse
Sweet. Not even a vendor fingerprint mismatch?
buffal0b1ll said:
Sweet. Not even a vendor fingerprint mismatch?
Click to expand...
Click to collapse
I always flash vendorfix in twrp to 100% avoid this error so can't tell
maelfilk said:
I always flash vendorfix in twrp to 100% avoid this error so can't tell
Click to expand...
Click to collapse
Got it. FYI I'd been manually vendor fixing the fingerprint since December on the Wi-Fi flounder and had layers issues on the stock enforcing kernel. Fire ice made it work with the old hacked vendor partition. To make layers work with stock kernel i updated to may factory vendor.img

[HomeBrews] Pixel 2: LineageOS/CarbonROM/DirtyUnicorns

Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pre-Disclaimer:
THIS IS AN UNOFFICIAL BUILD. The intent is to showcase what is coming up soon. I have been working hard on getting Walleye on a level I consider DD ready, especially from a security side of things.
Please keep any problems with those builds in this thread, I don't accept any bug reports for any other builds other than my HomeBrews.
Disclaimer:
While I make every effort to test these builds as much as possible, I am not responsible for anything that may happen to your device. I ask that you do your part to know your device and know how to recover from problems before you flash or post that you broke your phone!
Support:
I spend an astonishing amount of time developing this device. I can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Ask a question in this forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
Notice:
This build includes GApps for now. We're still working on ways to not prebundle it.
Before you flash, make sure you're on the latest 8.1 stock builds (and bootloader), then flash the ROM in TWRP.
Instructions :
Boot to TWRP
Format Data (If you didn't type YES, you did it wrong!)
adb sideload homebrews.zip
reboot system
(to gain root you must first boot homebrewsROM. Then reboot and to TWRP and install Magisk 1 6.0)
See below
Reporting Bugs:
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
What is your--
Build Date:
Did you--
wipe:
all data?
install gapps when you weren't suppose to?
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!
If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).
### RELEASES ###
https://drive.google.com/drive/folders/1NY1j-eH9demisz5Y05jeIPGXipENo5yK?usp=sharing
XDAevDB Information
LineageOS, ROM for the Google Pixel 2
CarbonROM, ROM for the Google Pixel 2
DirtyUnicorns, ROM for the Google Pixel 2
Contributors
Source Code: http://github.com/LineageOS
Source Code: http://github.com/CarbonROM
Source Code: http://github.com/DirtyUnicorns
Source Code: http://github.com/TresReinosDeLeche
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
### DONATE ###
paypal.me/JacobStermer
Created 2018-02-2
Last Updated 2018-03-Today
reserved
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
I for one am happy to see it.
iluvamk said:
I for one am happy to see it.
Click to expand...
Click to collapse
Me to ? do we need to flash twrp after the ROM like on pixel 1?
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
Archangel said:
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
Click to expand...
Click to collapse
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Let us know how it goes brother.
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
right now i am getting FC on Camera APP, X Google, Ok Google, and T Google something. My computer just crashed building the potential fix.
Ryche666 said:
boot to twrp.
wipe all data
adb push lineageos
reboot to bootloader
boot to twrp
adb push magisk
reboot to system.
right now i am getting FC on Camera APP, X Google, Ok Google, and T mobile something. My computer just crashed building the potential fix.
Click to expand...
Click to collapse
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
jasonsamms666 said:
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
Click to expand...
Click to collapse
Sorry, i got super anxious myself when i finally got playstore, phone, and text messaging working.
Thus the piss poor thread that i copy and pasted from taimen's lineage.
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Ryche666 said:
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Click to expand...
Click to collapse
FWIW this is what's been done with the Essential Phone.
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
I was the same way. A **** ton of reading and a lot of PMing. It is pretty simple when you get the hang of it. This early in the game you get to see the codes that attract you to certain roms or kernels.
Right now i just need to make sure it is stable before i work on the kernel or choose what rom i am gonna stick with.
NadavCE said:
FWIW this is what's been done with the Essential Phone.
Click to expand...
Click to collapse
That's what i heard. If i knew that last weekend we would have had that much sooner.
Awesome, glad to see some work
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Chronzy said:
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Click to expand...
Click to collapse
Can you share the complete steps and details on how you flashed it? Thank you!
infamousvincci said:
Can you share the complete steps and details on how you flashed it? Thank you!
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.

Categories

Resources