Develop Bugs

[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][WIP][5.0]Android L System Dump Port

Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me

+1 For quick start on this! I currently use toro so it is much appreciated. Just say if you need anything. :highfive:

KShion619 said:
Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me
Click to expand...
Click to collapse
hello can we flash this now?plus it says in build prop that its for maguro

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
I'm sorry, but did you even READ the post you quoted? it says "currently will reboot back to recovery"
so it's not really USABLE, but it's a START towards logs and figuring out what needs to be changed IF it can get to the point of boot& run

its awesome that you got it this far i tried to but it did what you said it rebooted into recovery thank you

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
Its stated as maguro for comparability with apps Verizon blocks, forgot I did that until now technically you can test it til it boots really on any Galaxy Nexus, you just won't gave data

What I've Deducted as of far
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting

^its possible but you need a skilled kernel dev. What I'm thinking (but I'm no dev) would be to decompile the n5 (android L) kernel, compare it to the n5 (kk) kernel, and apply similar changes to the gnex source and compile the kernel.
Just my 2 cents.

http://forum.xda-developers.com/galaxy-nexus/general/porting-android-l-lpv81b-to-tuna-help-t2796203/page3

wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?

KShion619 said:
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting
Click to expand...
Click to collapse
Why not just copy over some of the apps that make up the ui of L and edit the build prop so they act as if they are in an actual l installation?

dreamwave said:
wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?
Click to expand...
Click to collapse
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.

shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
good luck, it would be fantastic to at least get a bit of a port before the official launch so we know what to expect kind of. and are you sure you mean July? That's like a week
---------- Post added at 05:13 PM ---------- Previous post was at 04:56 PM ----------
shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
also if you tell me what the libs are I can try and make a couple decisions for you

Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
I could at least beta test so long as I am allowed to show it off to my friends
also, how is it coming so far? BTW I have the sprint galaxy nexus, so how hard is it to change it from verizon or gsm to sprint after you port them?

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
approximately how far are you two days of?

dreamwave said:
approximately how far are you two days of?
Click to expand...
Click to collapse
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.

I've been working on this as well, from what I can tell, there are unmet dependencies in libc.so, and there are some additional libraries that were added in KK AOSP that don't seem to be in any of the roms I've checked so far, libunwind.so is the major one.

shwise said:
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.
Click to expand...
Click to collapse
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?

dreamwave said:
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?
Click to expand...
Click to collapse
Any progress on this guys?

[DDK 1.9] OmniROM DDK 1.9 Test Version

Introduction
This is a test version of OmniROM with SGX DDK 1.9 graphics drivers, as well as many OMAP-related kernel updates. No, this isn't 3.4, but a LOT of TI updates were packed into the kernel. Currently, this is only for maguro, but anyone can build it for toro/toroplus with the sources.
Click to expand...
Click to collapse
Features
The ROM and the kernel has a stock feeling - no mods were added.
Most notable new features:
- SGX DDK [email protected]
- GPU governor
- Enabled 384 MHz GPU frequency (as a part of the OMAP updates)
- Tons of background changes for the kernel
Click to expand...
Click to collapse
Important notes
Camera and OMX is not working yet! This turned out to be a harder task for me to fix than implementing the new GPU drivers...
Other bugs are not known yet, but there may be some! Bug reports are welcome.
Thanks to everyone who helped me, especially Hashcode, as I used his repos as an example on how to set up things properly.
Click to expand...
Click to collapse
FAQ
How can I install this?
Just flash the ROM zip (and optionally GAPPS), and you're done.
Can I install this on top of Omni roms?
Yes, you should be able to do so without data loss.
Can I revert to non-1.9 Omni after this without data loss?
Yes.
Is this faster than the current ROMs/kernels?
As this is a stock-like ROM and kernel, not necessarily - there are no optimizations, etc added.
However, if one adds the optimizations used on current custom roms and kernels, this should be faster than them.
Can I install another kernel?
No, the new drivers require the ROM and the kernel side to match each other. Only this combination will work.
When will you fix camera?
I'm trying, but I don't have much success...
Can I help?
Sure, I appreciate any help, as I'm running out of ideas on how to fix camera and OMX.
Can I build this stuff myself?
Of course - everything needed is on my github. You'll need the following repos added to your Omni sources:
omni_android_device_samsung_tuna
omap (newpvr2 branch)
proprietary_vendor_samsung_tuna
Click to expand...
Click to collapse
XDA:DevDB Information
OmniROM DDK 1.9 Test, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: OmniROM
Version Information
Status: Testing
Created 2014-07-13
Last Updated 2014-07-13

Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk

aliesz said:
Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Click on the downloads button above the thread title

If you're on tapatalk you'll need to go to Web view..
To see the download
Sent from the "DOG" pound

Yes I found it just seconds ago
Sent from my Galaxy Nexus using Tapatalk

Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound

cujo6801 said:
Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound
Click to expand...
Click to collapse
Thanks for the suggestion, added it to the introduction text.

Amazing! I will try out tommorow

I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work

Nice work! Seems a lot more responsive although it may be placebo effect.

Thanks for posting this, I'm going to try building for toroplus, since we seem to get left out of the excitement so often. My internet connection is slow and so is my computer, so you will probably have everything fixed before I get a chance to even look for bugs.

Great work! I hope you manage to get camera working soon.

Amazing work bro, wishing u best of luck !!
I'm on F2Fs otherwise would have tested this asap...

Awesome work!

Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?

matoushybl said:
I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work
Click to expand...
Click to collapse
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
apollo07 said:
Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?
Click to expand...
Click to collapse
Not yet, I'm focusing on camera for now

Ziyan said:
The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
Click to expand...
Click to collapse
How about using SurfaceFlinger's Sync framwork now?
https://github.com/omnirom/android_...mmit/d677ae87b2466b03a6ca1cda6ee532c6ba407f8c

@Ziyan https://gerrit.omnirom.org/#/c/8141/
https://gerrit.omnirom.org/#/c/8156/ cherypick those and recompile

Ziyan said:
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
Not yet, I'm focusing on camera for now
Click to expand...
Click to collapse
Ziyan, thanks for the awesome work

It 's possible to have some screenshots?

(WIP) ChamelonOS 4.4*

Optimus G Owners,
I am working on my first build from source. I noticed we didn't have an updated build of ChameleonOS 4.4 of this forum. I am fairly new to this and have a fully capable pc to build it from scratch. Problem is I need some help with building and some testers. So if your interested in a collaboration with this build please leave a comment or leave me a message.
I have in installed Python, Git and the Sdk and am working on Forks and Repos. If you know of any good sources or suggestion please feel free to leave the below .

Repo is in progress
should be a couple hours to finish downloading and about an hour to build will try first build on my phone to see if it boots. if so I will post a download link to try it out.

Rmontoya83 said:
Optimus G Owners,
I am working on my first build from source. I noticed we didn't have an updated build of ChameleonOS 4.4 of this forum. I am fairly new to this and have a fully capable pc to build it from scratch. Problem is I need some help with building and some testers. So if your interested in a collaboration with this build please leave a comment or leave me a message.
I have in installed Python, Git and the Sdk and am working on Forks and Repos. If you know of any good sources or suggestion please feel free to leave the below .
Click to expand...
Click to collapse
I'm up for testing. I use multiRom. That could either be a benefit to your testing or a downfall. I usually like to know and inform others that use Multi what any issues are.

i tried to use multirom
dopy25 said:
I'm up for testing. I use multiRom. That could either be a benefit to your testing or a downfall. I usually like to know and inform others that use Multi what any issues are.
Click to expand...
Click to collapse
on my ls970 it stated it was not supported. hmm that's weird.

Rmontoya83 said:
on my ls970 it stated it was not supported. hmm that's weird.
Click to expand...
Click to collapse
Multi ROm? Yes, the app is not supported on our device, nor is the official recovery. If you are interested, I will link you to the xda thread.
http://forum.xda-developers.com/showthread.php?t=2734551
Follow this and if you have any questions ask them in that thread. I will help if you need. Just don't want to clutter your thread with questions about that one.

nice i never knew that was there.
dopy25 said:
Multi ROm? Yes, the app is not supported on our device, nor is the official recovery. If you are interested, I will link you to the xda thread.
http://forum.xda-developers.com/showthread.php?t=2734551
Follow this and if you have any questions ask them in that thread. I will help if you need. Just don't want to clutter your thread with questions about that one.
Click to expand...
Click to collapse
well back to work, I hope I can get this Chameleon OS up and running I hope I will have it done by this evening.

Failure
First build was a failure. Trying for round two tonight need to figure out what's missing. Will check my sources tonight hopefully I can get this working. If not I will ask some question from the pros =)

Rmontoya83 said:
First build was a failure. Trying for round two tonight need to figure out what's missing. Will check my sources tonight hopefully I can get this working. If not I will ask some question from the pros =)
Click to expand...
Click to collapse
The build failed, or the rom failed to boot?

build failed i think i figured out why
Think i was missing sources or added to many to my sync folder . Trying to clean up my build folder and make lunch.

Never heard of chameleon os, but I'd love to test

[ROM] CyanogenMod CM-13.0 jgcaap's builds [EXT4/F2FS Compability]

Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So I've started with angler! After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.9.0.2
Optimized SQL code for faster Read/Write
CM Super User (for now is the most stable one)
Kernel with F2FS support
Improved Code of frameworks
Optimized Build with custom toolchain on ROM and Kernel
Optimizations for our chip
Improved sound with speex resampler
Improved bionic with many optimized libraries (faster rom)
Improved Art with upstream patches
Optimized native frameworks for our device
LZMA updated to the latest
Proguard 5.2.1
Google Webview
F2FS ready for data and cache
Immersive mode
Expanded Notifications
CAF Task Manager
Snapdragon Camera
Network Monitor
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
​
As you might know, all credits go to CyanogenMod Team.
Source Code
If you like my work, please consider a donation.

Reverve

Frequently Asked Questions:
Q: What changes have you made between versions?
A: All changes made are the same as CyanogenMod ROM which can be found here: http://www.cmxlog.com/13/bacon/ and all manual changes will be also stated on 2nd post.
You can also check on Settings --> About where is all the changes .
Q: What is LZ4?
A: Read here about the project: https://github.com/Cyan4973/lz4
Q: Was latest build used LZ4?
A: This is still under testing and I'm working on it. It'll be on the test folder.
Q: What is the test folder?
A: Unstable, and test builds where I seek to study a new configuration to enhance user experience.
Q: Why don't you always share change logs?
A: Limited time. Sorry about it.
Q: Why do you many times ask for donations?
A: Well... This work is free, and as you know if you like it and on your own free will you think I deserve and currently wish to help me out as I am currently going to become unemployed and as also I study for my Masters in Finance , I believe is only fair. While you use, I'm testing and investing my time on it. Should be rewarded because of that right? Is only fair.
Q: Do you receive alot of donations?
A: Since last year until today I've received around 300 euro. But I've invested 1000 hours on these android builds. That gives a ratio of 30 cents an hour.
Q: Why do you still invest on android since it doesn't provide you any feasible income? I would have already quited!
A: Basically this forum makes me relax.
Q: Will you leave cm builds when exodus is released ?
A: I didn't plan on giving my cm builds, but if exodus prove to be superior why should i have double work right? Only time and users will tell.
Q: I'm confused. I have no clue which build is the latest!
A: You can always download again!
Q: Your site have ads why?
A: Need help on extra wealth to survive. Leave some clicks while you visit is only nice.
Q: I want more from the rom!
A: Me too!
Q: Why you sometimes ignore users?
A: I never ignore, just don't have time to answer all. Please help one another and also use search button. I think you prefer me learning to bring something nice than post all the time right? hehe
Q: I have so many questions to ask you!
A: I can provide many answers! Just ask!
Q: Can I PM you?
A: Only when is urgent!
Q: How to report bugs?
A: Our bugs are CM bugs. Report on JIRA: https://jira.cyanogenmod.org
Q: Are you CyanogenMod maitainer?
A: No, just an user which wants to have better builds possible. But would be nice to see CM adding me to the contributions list.
Q: Why Slim gaaps? Open Gaaps are so much cool!
A: Open Gaaps has provided many unstable issues which makes the phone unusable until a clean format. Slim gaaps have shown to be better on that.
Q: Why some buttons of UKM don't work?
A: Need time to improve that..
Q: I want an update app to auto update roms. To lazy to check the thread!
A: I understand, for now is not feasible to do it as I need time to analyse and understand best solution as I update tool-chains regularly and also is not my priority. Remember time is limited for me.

Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?

tibere86 said:
Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?
Click to expand...
Click to collapse
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz

Oh wow.. Ur ROM was the first custom ROM i had on OPO.. Nice to see you here

I have to admit I didn't check yet on cm source but I'll review.

yung40oz84 said:
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz
Click to expand...
Click to collapse
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?

Do we need to flash the correct vendor image from February's security patch?

Kookitza said:
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?
Click to expand...
Click to collapse
Will work both ways... But f2fs is very nice.

jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
But F2FS is not work on our device so....

jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
Yes, I have heard good things about it! So if I do not change /system to F2FS then I will be able to flash this ROM and other ROMS as normal correct? As long as they support F2FS of course for the other partitions I have converted. But some recommend system as F2FS as well, if I did that then what is the draw back? I would have to convert ROMS to be able to flash correct?
Sent from my Nexus 6P using Tapatalk

Kookitza said:
But F2FS is not work on our device so....
Click to expand...
Click to collapse
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.

jgcaap said:
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.
Click to expand...
Click to collapse
I don't know this for sure. I read that in one of the previous comments. Maybe someone can confirm this.. [emoji53]
Sent from my Nexus 6P using Tapatalk

When you say no bugs, did you fix the broken Bluetooth?

jclendineng said:
When you say no bugs, did you fix the broken Bluetooth?
Click to expand...
Click to collapse
Cm has also that bug?

Does this ROM force encryption?
Sent from my Nexus 6P using Tapatalk

Tomorow I'll answer all questions calmly as tomorow I have an exam. I want to deliver here what I delivered on bacon. Smooth experience.

Until then please test and let me know any bugs. Thanks!

Is anyone having issues with the camera?