MOD EDIT:
Links removed.
MOD EDIT:
Links removed.
yeahh.downloading
Successful installs everyone
You claim HWC is fixed, but your device trees still have HWC disabled in your system.prop.
abtekk said:
You claim HWC is fixed, but your device trees still have HWC disabled in your system.prop.
Click to expand...
Click to collapse
Bad claim, they are not disabled. , check and download Rom / anyone feel free to do that
eduardo193 said:
Bad claim, they are not disabled. , check and download Rom / anyone feel free to do that
Click to expand...
Click to collapse
Then why are they disabled on Github?
HWC isn't even fixed lol.
abtekk said:
Then why is it disabled on Github?
---------- Post added at 10:22 AM ---------- Previous post was at 10:16 AM ----------
OP, this is in your system.prop. HWC is NOT fixed. Don't advertise as such.
Click to expand...
Click to collapse
jameseytickner said:
HWC isn't even fixed lol.
Click to expand...
Click to collapse
abtekk said:
Then why are they disabled on Github?
Click to expand...
Click to collapse
Some of the device tree i took from another person who allowed me to do it, i edited these files locally before compiliation, sorry peoples i have removed the complianted sources and please test my rom to see if hwc is working!! instead of viewing a sources!! TEST BEFORE SPEAKING!! SAME WITH BATTERY LIFE!! ALWAYS LOOK THEN OPEN YOUR MOUTH DONT DO MOUTH FIRST OKAY!!
From now on:
test my rom
verify hwc yes working
then apologize plz
eduardo193 said:
Some of the device tree i took from another person who allowed me to do it, i edited these files locally before compiliation, sorry peoples i have removed the complianted sources and please test my rom to see if hwc is working!! instead of viewing a sources!! TEST BEFORE SPEAKING!! SAME WITH BATTERY LIFE!! ALWAYS LOOK THEN OPEN YOUR MOUTH DONT DO MOUTH FIRST OKAY!!
From now on:
test my rom
verify hwc yes working
then apologize plz
Click to expand...
Click to collapse
Or, here's an idea, push your sources back to Github so that I can take a look and don't have to go through the motions of backing up all of my data, flashing your ROM, factory resetting, then restoring my backup.
abtekk said:
or, here's an idea, push your sources back to github so that i can take a look and don't have to go through the motions of backing up all of my data, flashing your rom, factory resetting, then restoring my backup.
Click to expand...
Click to collapse
all my suources back on github? Ok give me 1 minute
abtekk said:
Or, here's an idea, push your sources back to Github so that I can take a look and don't have to go through the motions of backing up all of my data, flashing your ROM, factory resetting, then restoring my backup.
Click to expand...
Click to collapse
CHECK AGAIN, ALL MY SOURCE HAVE BEEN ADDED BACK
SORRY EVERYONE!! i forked and didnt edit them with my fixes thats why my github sources were messed up i did the edits locally, well now i published everything to my github for all to see . dont worry hwc is completely fixed and try my build to test it out!! DONT SPEAK ABOUT IT WITHOUT TEST!!
eduardo193 said:
CHECK AGAIN, ALL MY SOURCE HAVE BEEN ADDED BACK
SORRY EVERYONE!! i forked and didnt edit them with my fixes thats why my github sources were messed up i did the edits locally, well now i published everything to my github for all to see . dont worry hwc is completely fixed and try my build to test it out!! DONT SPEAK ABOUT IT WITHOUT TEST!!
Click to expand...
Click to collapse
Thanks Augustin, I can see what you did now. Much better. Just an FYI, that HWC "fix" will knock the colours out of whack, you still need to patch the HWComposer to return the correct values to the system.
abtekk said:
Thanks Augustin, I can see what you did now. Much better. Just an FYI, that HWC "fix" will knock the colours out of whack, you still need to patch the HWComposer to return the correct values to the system.
Click to expand...
Click to collapse
Refer to previous post!!
"TEST BEFORE SPEAK!!!"
eduardo193 said:
Refer to previous post!!
"TEST BEFORE SPEAK!!!"
Click to expand...
Click to collapse
I was offering you further advice. Suit yourself.
abtekk said:
I was offering you further advice. Suit yourself.
Click to expand...
Click to collapse
Test ROM and speak after
Sent from my SM-G935F using Tapatalk
I will give it a shot and report back. Thanks for the work.
xchatter said:
I will give it a shot and report back. Thanks for the work.
Click to expand...
Click to collapse
enjoy ROM
Thanks, flashing it right away.
Either Augistines Italian accent is f'in perfect or eduardo is highly schizophrenic ?
Either way, come back to TG brottha, we miss you ?
Related
This kernel will be kept simple and inline with stock and free from buzzfree stuff..as the aim is a stable day-to-day use kernel..this kernel is NOT for those who want to break records..as i do not believe and rely on benchmarks..(its me..)
Disclaimer:
i nor xda would be at fault if something weird beyond my test results happen to your phone..also this is not a benchmark kernel..if you like crunching numbers and breaking records go use another kernel..this is meant to save juice and be efficient and stable as a daily driver for Samsung based ROMS..
Features:
- Based on i9205/i9195 source from Samsung OSRC(Thanks for the borked source)
- Fixed a few things left by Samsung to be broken
- Simple and no fancy stuff thats gonna bork your phones..more stuff does not guarantee it's better..
- User voltage control from faux123 for Krait CPU's..
- EXFat support(by Samsung OSRC..)
- OC(if already stable)
- will populate more as things get stable
- Selinux permission is set from enforcing to permissive via ramdisk
- insecure boot image
- Disabled Rooting security measures implemented by Samsung..
Pre-requisites
- Install busybox via CWM or via Playstore before installing my kernel..this is to make sure init.d and also some scripts work properly..
Downloads here: Test build 5(ML1 Ramdisk)
My git: source
Credits:
- noone in particular but thanks to ALL the wonderful devs here in XDA..
If you like the builds please help me get a Soda/pay bills..or the least is just hit the Thanks Button..
one more in case..
uploading..
please report/feedback on any issue you might encounter..please do provide logs(last_kmsg, logcats, dmesg...etc..) so that i can shoot things out..i do not own the device yet and surely things can go wacky along the way..
TIA
kindly someone report if the build boots up..
What do you mean with those features?
- Fixed a few things left by Samsung to be broken
- Removed most of the crappy and buggy stuff..
- GPU Idling fix..
Click to expand...
Click to collapse
I cannot see them on your sources
Grarak said:
What do you mean with those features?
I cannot see them on your sources
Click to expand...
Click to collapse
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
kairi_zeroblade said:
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
Click to expand...
Click to collapse
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Grarak said:
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok so if it bothers you then i will ninja edit it then..its just a general template i used on my previous OP..dont be so harsh on me..
update: edited it to "fit" your standards.. (what a way to welcome me here........now i can go to bed..and get my beauty sleep.. )
update: good morning guys!! any reports or comments if it boots up?? need feedbacks so i can start pushing more stuff..
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Silesh.Nair said:
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Click to expand...
Click to collapse
thanks will invetigate the logs provided..can you upload a stock image of the i9200 btw??so i can check if there are specific differences from the ramdisk of the i9200 from i9205..afaik aside from the LTE there should be other differences from them..
re: root it might have been because of the ramdisk i used..can you shift to Koush's superuser??chainfire's supersu has been finicky with my HTC 4.3 update but Koush's never had a glitch..
Thank you very much for the feedback!!
edit: get the SuperUser by Koush here
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Silesh.Nair said:
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Click to expand...
Click to collapse
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
kairi_zeroblade said:
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
Click to expand...
Click to collapse
Attached.
Silesh.Nair said:
Attached.
Click to expand...
Click to collapse
ok nailed down the culprit..will release a new test build in a few minutes thanks Silesh..it seems i was missing a few stuff..
kairi_zeroblade said:
update: new test build here OP updated as well
kindly test and provide feedback so i can push more stuff in..i have to do alot more maintaining also to my git..
Click to expand...
Click to collapse
I am testing my slimkat build. Will flash and let you know in an hour.
Silesh.Nair said:
I am testing my slimkat build. Will flash and let you know in an hour.
Click to expand...
Click to collapse
thank you it seems i made a minor derp..will fix it now..and upload a new kernel.
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Silesh.Nair said:
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Click to expand...
Click to collapse
update: get test build 3 here
kairi_zeroblade said:
update: get test build 3 here
Click to expand...
Click to collapse
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Silesh.Nair said:
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Click to expand...
Click to collapse
ok got it..will switch to the ML1 ramdisk you gave me..will post a new build in a few minutes..
edit: it seems i was messing with the UCNA2 update with SELINUX..thats why i was borking things..i am now using the ML1 ramdisk..
@silesh
new build up..here
Dirty Unicorns just updated sources to Marshmallow.
XDA: Dirty Unicorns ROM Updated to Marshmallow, Brings Lots of New Features.
http://www.xda-developers.com/dirty-unicorns-rom-updated-to-marshmallow-brings-lots-of-new-features/
Would be nice if someone could port and build for Onyx.
As far as I know, it's based on CM13.
Thanks
+1
I was literally just abut to make a thread about this
---------- Post added at 12:34 PM ---------- Previous post was at 12:34 PM ----------
Please devs
Officially I read that they had no plans to support it
I would look into maintaining it myself but my rig needs new parts. Otherwise with my laptop even compiling a kernel from source takes forever
RJDTWO said:
Officially I read that they had no plans to support it
I would look into maintaining it myself but my rig needs new parts. Otherwise with my laptop even compiling a kernel from source takes forever
Click to expand...
Click to collapse
If you intend to support it officially, they would probably let you use their build server to release builds.
Just guessing. If you're really interested in supporting DU, you can ask them
Sent from my OnePlus X using Tapatalk
Calvin2394 said:
If you intend to support it officially, they would probably let you use their build server to release builds.
Just guessing. If you're really interested in supporting DU, you can ask them
Sent from my OnePlus X using Tapatalk
Click to expand...
Click to collapse
I'll look into that and see what I can do then
@RJDTWO So what's up? Did you ask them if you can use their servers?
Calvin2394 said:
@RJDTWO So what's up? Did you ask them if you can use their servers?
Click to expand...
Click to collapse
Doesnt look like ill be able to unfortunately. However the dev working on Tamesek is working on an unofficial build.
RJDTWO said:
Doesnt look like ill be able to unfortunately. However the dev working on Tamesek is working on an unofficial build.
Click to expand...
Click to collapse
that would be @rohitporoli
Subhrajyoti Sen said:
that would be @rohitporoli
Click to expand...
Click to collapse
I've kept that aside for now! Having the same issue regarding server! :/
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Vatsal said:
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Click to expand...
Click to collapse
You´re awesome man! Thank you so much!
Vatsal said:
So well, I booted DU for onyx.
To my surprise, all basic functions are working. RIL is working flawless too.
What's broken :-
Selinux (Needs work)
Tristate keys (Will fix them)
Rest all is working as it should atleast in my case, I will make a thread and post the build when I fix the above two things.
Don't ask for links please. I won't post untill I fix the stuffs.
Click to expand...
Click to collapse
Oh sweet. Will they let you make this official? They wouldn't let me use their servers for releases
RJDTWO said:
Oh sweet. Will they let you make this official? They wouldn't let me use their servers for releases
Click to expand...
Click to collapse
No official sorry. I don't wish to apply for official.
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the source.
V4 Flashable ZIP: https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA
Obligatory screenshots: https://imgur.com/a/cXrnH
Working
As Shamu is a supported device, most things work well here:
Booting
Cellular (Calling, SMS and data)
Audio
Wi-Fi
Bluetooth
GApps (see below)
Easter egg
Not working (?)
Not working on Verizon, as reported here
There are probably more
GApps
This build has dm-verity enabled. With the stock kernel, GApps will not show up, or a warning is displayed when booting. To solve this, either use a custom kernel or use FED-Patcher.
After installing OpenGApps, you may encounter force closes during the Setup Wizard.
replica102 said:
You can just skip setup without editing the build.prop. Just tap on the four corners of the screen, starting from top left, clockwise. Do it right, and you'll get sent to home screen.
Click to expand...
Click to collapse
Afterwards, to get rid of the Play Services force closes, go to Settings > Apps > Three dot menu > Show system and find Google Play Services. Enter the Permissions menu and grant all the permission it needs.
If apps requiring WebView force close, try excluding "WebviewGoogle" using the gapps-config config file. Details are available here.
Sources
This build was compiled on a modified tree. See the changelog for details.
Vendor blobs are downloaded from https://developers.google.com/android/nexus/blobs-preview
Changelog
Code:
V4 - NRD90U - That's what I call "Useless"
Flashable ZIP: [url]https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA[/url]
- Updated to 7.0.0_r6/NRD90U. So you want the shiny new build number? Here you go!
V3 - NRD90S
Flashable ZIP: [url]https://mega.nz/#!35Zl0QyY!gUYM79Fs_I6tm2RdEJw1v5S30qQqJ2RA1B3EosKlSqk[/url]
- Updated to 7.0.0_r4/NRD90S, with September's security updates.
V2 - NRD90M - A proper build... and more!
Flashable ZIP: [url]https://mega.nz/#!f4wSnTDL!3ifsV_qC_r-MJ-y45yDcwemkgTGY_jTr_OObHRktC-M[/url]
- The product name is now "Nexus 6" instead of the default "AOSP on Shamu". The modified device tree is available [URL="https://github.com/zhaofengli/device_moto_shamu"]here[/URL].
- The navigation bar editor is now accessible in System UI tuner. This is done by reverting [URL="https://android.googlesource.com/platform/frameworks/base/+/72195a011128d1c516149763c4c156539a470ed5"]this commit[/URL].
- I found out that I checked out the master branch for a handful of repositories when playing around. This is now fixed.
- This build was compiled with external/icu at [URL="https://android.googlesource.com/platform/external/icu/+/683055d9b50491dedbadea4e8ffb484e99e4f52b"]683055d[/URL] (the current master). This is to get RIL working.
- Developers: See [URL="http://forum.xda-developers.com/showpost.php?p=68556855&postcount=10"]this post[/URL] for a full explanation of the solution to get RIL working on 7.0.0_r1.
V1 - Initial build
Note: On a closer look, this is actually not a proper 7.0.0_r1 build. You should download V2 instead for a smoother experience.
Flashable ZIP: [url]https://mega.nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY[/url]
Mods: Please move this thread to the appropriate section if required.
Where did you get blobs from?
Kernel source?
Well done on being the first XD
neobuddy89 said:
Where did you get blobs from?
Kernel source?
Click to expand...
Click to collapse
Blobs are from https://developers.google.com/android/nexus/blobs-preview
And as said, I haven't changed the source in any way. Kernel source is available at https://android.googlesource.com/device/moto/shamu-kernel/+/android-7.0.0_r1
Edit: Wow, didn't look too closely. That's the prebuilt kernel, and the corresponding source hasn't been uploaded yet.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
The mega link don't work.
serch826 said:
The mega link don't work.
Click to expand...
Click to collapse
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Twiggy000b said:
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
I removed the <dot> but it doesn't work.
serch826 said:
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
looks like mega is having server issues... i got it though
---------- Post added at 06:28 AM ---------- Previous post was at 06:25 AM ----------
Zhaofeng Li said:
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Click to expand...
Click to collapse
the log shown was simulating actions and then went to success. let me try again
Twiggy000b said:
looks like mega is having server issues... i got it though
Click to expand...
Click to collapse
Thanx mate!
cerico76 said:
I removed the <dot> but it doesn't work.
Click to expand...
Click to collapse
i retract my last response lol, you also gotta put a "." between mega and nz lol mega is alive!
Thanks, will download and try asap!
EDIT: i guess it will encrypt the device?
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Q9Nap said:
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Click to expand...
Click to collapse
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Noob Question:
Where can I get the GApps file for this build?
Thanks!
edwaine said:
Noob Question:
Where can I get the GApps file for this build?
Thanks!
Click to expand...
Click to collapse
Use open gapps
Sent from my Nexus 6 using Tapatalk
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
In twrp I wiped everything except internal storage. flasked. still have my files. So, no it does not force encrypt. Your welcome.
Zhaofeng Li said:
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Click to expand...
Click to collapse
So.. this probably force encrypts device, right?
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
harpin14789 said:
So.. this probably force encrypts device, right?
Click to expand...
Click to collapse
Flash this after flashing the rom zip and you don't have to worry about it:
http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
VV READ THIS BEFORE DOING ANYTHING ELSE VV
By using this ROM you agree to these conditions:
1. I am not responsible for anything that you do or that happens to you that is related to the ROM in anyway.
2. You have an advance knowledge of how this stuff works before trying it yourself.
3. You have backups and know how to recover your data if something was to happen.
I am not connected in any way, shape or form to AOSPA. I just respect them and like what they do.:good:
I did not make this ROM. All I've done is compiled it from the source on GitHub, anyone could do that. ----> https://github.com/AOSPA/android_kernel_oneplus_msm8974
Okay I believe that covers me, so lets get down to the specifics.
It takes me approximately 35m to compile a new build, I'll do this either weekly or sub-weekly if there's a bad bug that's been fixed.
I have not had any problems thus far with it.
To flash this I strongly recommend you
1. Use the latest TWRP.
2. Have a backup in case you mess something up.
3. Wipe only these partitions: system, data and both caches. DO NOT EVER WIPE THE INTERNAL STORAGE OR THE OTG DRIVE
4. Flash the ROM.
5. Flash the most recent Open GApps [ARM] [7.1] the variant is up to you but I recommend [PICO]
6. Reboot and enjoy!:good:
Bugs:
I don't know, you tell me. I haven't had anything go wrong.
Here you go:
https://goo.gl/Ph7SmW pa_bacon-7.3.0-DEV-20171009.zip
https://goo.gl/VE5rdx pa_bacon-7.3.0-DEV-20171009.zip.md5sum
https://youtu.be/PH3pG8xU5QQ
This shows exactly what I'm doing. Enjoy!
joefso said:
can you build paranoid android with OOS blobs V3?
It uses 2.x right now, right?
Click to expand...
Click to collapse
Possibly. Tell me where I get the blobs from. And I'll work from there.
Techie Android said:
Possibly. Tell me where I get the blobs from. And I'll work from there.
Click to expand...
Click to collapse
it is from this thread and the Bacon (OOS 3.x blobs) can be found here
joefso said:
it is from this thread and the Bacon (OOS 3.x blobs) can be found here
Click to expand...
Click to collapse
Okay thanks I'll update you on my results.:good:
Techie Android said:
Okay thanks I'll update you on my results.:good:
Click to expand...
Click to collapse
This might be of use to you... HalogenOS ( they dropped bacon, maintainer had no time) used OOS 3.1.3., their github can be found here
Same as PA ?
OP,please add "unofficial" to the title.I know you've kind of mentioned that in OP but still.. It wouldn't hurt.
Also, "It takes me approximately 35m to compile a new build". What kind of internet you have?!
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
Piypoo said:
Same as PA ?
Click to expand...
Click to collapse
Yeah,only difference is that it is unofficial as of now.
Mr.Ak said:
Yeah,only difference is that it is unofficial as of now.
Click to expand...
Click to collapse
Alrighty. Thankyou.
Mr.Ak said:
OP,please add "unofficial" to the title.I know you've kind of mentioned that in OP but still.. It wouldn't hurt.
Also, "It takes me approximately 35m to compile a new build". What kind of internet you have?!
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
Yeah,only difference is that it is unofficial as of now.
Click to expand...
Click to collapse
What do you mean? My internet is 100mbps (12MB/s). I have moderate specs for a PC, i5-6402p, 8GB RAM and SATA lll 3TB HDD 64MB cache, Kubuntu 17.10 with modifications and bleeding edge software updates (I'm moving to Gentoo soon).
What do you mean "unofficial as of now"? I don't see a need to add it if it's not a requirement.
Techie Android said:
What do you mean? My internet is 100mbps (12MB/s). I have moderate specs for a PC, i5-6402p, 8GB RAM and SATA lll 3TB HDD 64MB cache, Kubuntu 17.10 with modifications and bleeding edge software updates (I'm moving to Gentoo soon).
What do you mean "unofficial as of now"? I don't see a need to add it if it's not a requirement.
Click to expand...
Click to collapse
Nvm,it's your own choice anyways,it just makes thread more sophisticated.BTW,your internet is amazing,I'd only wish an internet like this.
Techie Android said:
[reserved]
Click to expand...
Click to collapse
Don't forget to post sources (kernel is required)..
Having installed magisk, opengapps, default apps I always use on each rom i lose 12% battery over night. Temporary switched back to another ROM... need stability.
Will try soon again
Any changes made versus the latest official AOSPA build? NFC? Camera?
joefso said:
Having installed magisk, opengapps, default apps I always use on each rom i lose 12% battery over night. Temporary switched back to another ROM... need stability.
Will try soon again
Click to expand...
Click to collapse
Use greenify.
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
eiwarmer said:
Any changes made versus the latest official AOSPA build? NFC? Camera?
Click to expand...
Click to collapse
I don't think there's any change to NFC.I'll have to try out this ROM to compare camera against official PA,which I'll do soon.
Setting.Out said:
Don't forget to post sources (kernel is required)..
Click to expand...
Click to collapse
I did post where the sources are from. GitHub.
Techie Android said:
All I've done is compiled it from the source on GitHub, anyone could do that.
Click to expand...
Click to collapse
joefso said:
Having installed magisk, opengapps, default apps I always use on each rom i lose 12% battery over night. Temporary switched back to another ROM... need stability.
Will try soon again
Click to expand...
Click to collapse
eiwarmer said:
Any changes made versus the latest official AOSPA build? NFC? Camera?
Click to expand...
Click to collapse
Not having any stability problems myself but I'll look into it. I did not change anything from the master on GitHub, no modifications, pure AOSPA.
Techie Android said:
I did not change anything from the master on GitHub, no modifications, pure AOSPA.
Click to expand...
Click to collapse
Sooooo you're just compiling moments before the PA team does without any changes? This means I could just wait for the PA-team to compile their build and I'll get exactly the same, right? Or am I missing something here
eiwarmer said:
Sooooo you're just compiling moments before the PA team does without any changes? This means I could just wait for the PA-team to compile their build and I'll get exactly the same, right? Or am I missing something here
Click to expand...
Click to collapse
I don't know what you mean by moments before they do. But yeah what I compile is exactly the same as if they were to release an update. But they haven't all they have on their website is AOSPA 7.2.1. That's the whole point of why I'm doing it, I liked the ROM but wanted updates, so when they make improvements on the master I pull the changes and compile a new build.
Mr.Ak said:
Use greenify.
Click to expand...
Click to collapse
you failed to comprhend my point. Also not asking for advise.
joefso said:
you failed to comprhend my point. Also not asking for advise.
Click to expand...
Click to collapse
Calm down. There's no need to get worked up over it.
Hi guys,
as LineageOS 15.1 is just around the corner and I had a few spare CPU cycles, here's the current build which I did as a 'code of honor'-member. Just flash with TWRP as usual, add gapps (stock are too big) and optionally root.
Watch out as the whole rom might still lack a few features.
Sources are on https://github.com/LineageOS
Credits to anyone who worked on them including intel for their buggy CPUs enabling me to build.
Build date: 2018-03-02
Download: https://go.stargazer.at/bacon
FAQs.:
Q: What patches did you include?
A: None. Pure LineageOS as it would come from the build server
Q: So this IS the official LineageOS rom?
A: In theory it's the same thing, but I am NOT a linageos developer
Q: What Gapps package did you use?
A: Nano. Stock is too big as it wouldn't fit on /system
Q: Support?
A: None officially. But ask - maybe someone has an idea.
Q: What works?
A: Phone rings, I'm able to answer and do calls, BT works, Wifi... annoying texts already arriving. I assume it's working.
Q: Bugs?
A: You tell.
Q: Is it complete?
A: I doubt it. Some translations are still missing. Keep in mind it's an early version of lineageOS
Q: Why did you build it?
A: Because I did not want to wait for the official release and live on the edge.
Q: Why does a girl build roms?
A: Short answer: because I can.
is the camera working? apparently that is the reason why the official build have been delayed
borzowsky said:
is the camera working? apparently that is the reason why the official build have been delayed
Click to expand...
Click to collapse
Honestly, I did not check yet as camera is not one of my basic needs. Will do so as soon as I get home.
If it does not work yet, I do not intend to fix too much stuff as I want to stay on the official sources. If there's a patch to cherrypick from gerrit, it's something we may talk about.
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Long live bacon
cb5264 said:
Camera does not work yet...
Click to expand...
Click to collapse
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
I've been keeping tabs on this every day and no one has touched it for weeks [emoji24] hopefully they just have code they're working on offline and just have to upload it and merge. Waiting is killing me though. Good to know it's getting close but probably will still wait since I'll probably do a full wipe once it's ready and don't want to do it twice.
Sent from my Nexus 7 using Tapatalk
remedya said:
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
Click to expand...
Click to collapse
I doubt that it's SELinux. Looking at the logcat the problem root seems to be the HAL and that we should use the CAF stack. Besides that some clocks seem to be out of sync (mainly front camera). If it would be SELinux, logcat/dmesg would show.
Download doesnt work
I will fix it as I compile the next version.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
Some changes on 19 March.
Download link fixed btw
remedya said:
Some changes on 19 March.
Click to expand...
Click to collapse
Are these the changes needed to fulfill the LineageOS Device Support Requirement/camera recorder?
cb5264 said:
Download link fixed btw
Click to expand...
Click to collapse
Error 7
---------- Post added at 08:37 PM ---------- Previous post was at 08:19 PM ----------
Lol and now the download link is gone. Just stop. Wait for the official there is clearly a reason why its not been officially released yet.
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
The_Voice_70 said:
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
Click to expand...
Click to collapse
You had no problems flashing?
It's happening!
Sent from my A0001 using Tapatalk
TbagBaggins said:
You had no problems flashing?
Click to expand...
Click to collapse
Nope. No Problems.
The_Voice_70 said:
Nope. No Problems.
Click to expand...
Click to collapse
Im getting error 7. No other rom gives me error 7. Download link works on and off have tried installing twice same error.
Use latest official TWRP 3.2.1.0. No Problems with it. Error 7 seams to be old Recovery.