[ROM][7.1][NOUGAT][TESTING] CyanogenMod14.1-cohaolain [UNOFFICIAL] - OnePlus 3 ROMs, Kernels, Recoveries, & Other Devel

Hey guys!
To prevent the other CM14.1 thread from getting too crowded I'll be putting my own builds up here
These builds will be based on the official source except I'll keep adding in new features and fixes before they're officially merged, and I'll be putting in some other small changes along the way if I feel they improve the experience without compromising on anything else
Currently working:
//All battery status indicators are fixed
//Pocket mode
Modifications:
//'Unofficial' tag removed from CyanogenMod version. It just made me squirm with the lack of aesthetic. Of course this is still an unofficial version!
Updated (//): 16.11.03
Download link: https://drive.google.com/open?id=0B88aOagl9VcCV3YtNFpwRzR1akk
Credit of course goes to CyanogenMod and all of its contributors for all of their work!
Disclaimer:
This software is provided by me "as is" and "with all faults." I make no representations or warranties of any kind concerning the safety, suitability, lack of viruses, inaccuracies, typographical errors, or other harmful components of this software. There are inherent dangers in the use of any software, and you are solely responsible for determining whether this software is compatible with your equipment and other software installed on your equipment. You are also solely responsible for the protection of your equipment and backup of your data, and I will not be liable for any damages you may suffer in connection with using, modifying, or distributing this software.
XDA:DevDB Information
CyanogenMod14.1-cohaolain, ROM for the OnePlus 3
Contributors
cohaolain
Source Code: https://github.com/cohaolain
ROM OS Version: 7.x Nougat
Version Information
Status: No Longer Updated
Current Beta Version: 7.1 (CM14.1)
Beta Release Date: 2016-11-04
Created 2016-10-31
Last Updated 2016-11-12

First...!!
Will definitely try it out.
Peace

Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?

Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!

silentvisitor said:
Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?
Click to expand...
Click to collapse
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that

Great! When I have time I'll definitely give it a try.
Sent from my iPod touch using Tapatalk

revive111 said:
Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!
Click to expand...
Click to collapse
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....

Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?

cohaolain said:
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....
Click to expand...
Click to collapse
OK,fine.
In cm13, I can pass it without anything, just wait cm to fix this bug.

Thanks for this! :good:

saayuj98 said:
Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?
Click to expand...
Click to collapse
As soon as I've learned how to do that, I will do that.

If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán

cohaolain said:
If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán
Click to expand...
Click to collapse
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.

which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?

Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I use pico gapps everytime(I like my system being less bloated). Nano is a good option too.
I suggest you to go with Nano.

Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I recommend pico, but nano is fine if you don't want Google Now, or Now on Tap, or Assistant and stuff.

saayuj98 said:
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.
Click to expand...
Click to collapse
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.

Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?

cohaolain said:
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.
Click to expand...
Click to collapse
Maybe init.d
---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------
cohaolain said:
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that
Click to expand...
Click to collapse
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:

ankushgautam said:
Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?
Click to expand...
Click to collapse
I've read abouyt some bugs with the Aroma installer in 14.1. I'm not even sure if this is a CM problem or a Gapps problem, but for now, stick with pico or something pre-packaged if you can
silentvisitor said:
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:
Click to expand...
Click to collapse
Thanks mate Maybe, maybe . Gotta finish school first!
init.d, hm. Mysterious to me. I've heard tell of it many times but never learned too much about it. Better start reading up

Related

Paranoid Installer Like CyanogenMod

Yesterday i saw CyanogenMod Installer app for android...
It is quite helpful for those who are flashing roms first time on their device after rooting...
This app also tells them whether a Cyanogen rom is available for their device or not...
I m currently working on paranoid if this feature is added to PA source itself then it will cause pain for other roms...
This will be a arsenal for paranoidsss...
Have a look at CM installer
https://play.google.com/store/apps/details?id=org.cyanogenmod.oneclick
I m not promoting CM but giving u all idea atleast...
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Installer will be great for newbies...
theroadrunner said:
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Click to expand...
Click to collapse
if a rom offers an installer app then it will attract new users who havent flashed custom roms yet...this what i meant..
Custom ROM Installer
I think that an Automatic Installer for the first flashers would be indeed "comforting" Because I've started to flash custom roms recently and my first one was a pain, not because of the steps....The steps for installing the recovery tool and all are pretty easy and all. But we have the feeling we are going to brick the device at the first flash! hehe Maybe an automatic installer that detects your device model would be kinda safe for unexperienced users...
But nowadays I find it nice to manually flash roms, keep backups, etc...
Oh well...not a bad idea at all in my opinion ;}
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
moneyolo said:
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
Click to expand...
Click to collapse
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
stephendt0 said:
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Click to expand...
Click to collapse
Yeah, that was my fault aswell.
Now it will help..
Entropy512 said:
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
Click to expand...
Click to collapse
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
anurag.dev1512 said:
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
Click to expand...
Click to collapse
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
wait i will check ...
Mazda said:
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
Click to expand...
Click to collapse
thnxxx for notifying me... i havent checked the source but i will check now...
nice!

[MOD]Hey Snapdragon! Mod - 4/14/15

Disclaimer
I'm not responsible for anything that may happen to your device. I've tested this mod to the best of my abilities, but I can't guarantee anything. Make a complete backup before applying any of these changes. If you brick your device, boot loop, lose data, or etc...again, I'm not responsible.
CM12 - Working
- CM12S YNG1TAS0YL with stock kernel
- CM12 nightly with stock kernel
CM11 - Working
- CM11S XNPH30O, XNPH33R, XNPH38R, XNPH44S, and XNPH05Q with stock kernel
- CM11, PAC-man, crDroid with most recent kernels
- franco r35 kernel
CM12.1 - Not Working
- CM12.1 nightly (bootloop)
CM11 - Not Working
- LiquidSmooth ROM (mediaserver seg faults immediately)
- OmniROM
Also, I found a commit in the CM source that adds Voice Wakeup options to the Settings app. If the ROM doesn't have this code compiled into their Settings, the mod will probably not work. You'll still be able to go through the training process, however, I don't believe Google Now will launch because the intent action is never being set.
Instructions
1.) Backup any important data on your phone (files, pictures, etc.)
2.) Boot into recovery. I use and have only tested with TWRP
3.) Make a nandroid backup
4.) Flash the mod
5.) Reboot
Recovery
If you encounter any issues (e.g. bootloop) or just want to remove the mod, go into recovery and restore just the System partition from the backup you made earlier (this will preserve your Data partition).
After Installation
After installing, you'll get a notification to enable Voice Wakeup and to train your voice. You can do this now or skip it. It can always be setup later by going to:
CM11: Settings --> Voice Wakeup --> Retrain your voice
CM12: Settings --> Language & Input --> Voice Wakeup --> Retrain your voice
Also...
1.) Go into the Google Now settings and disable "OK Google" detection settings.
2.) Disable your lockscreen if on CM11S or CM12S...other CM11/CM12 based ROMs should work fine since the apk is signed correctly. Some users have reported being able to use a 3rd party lockscreen (e.g AcDisplay) as a work around for CM11S.
If something is not working for you, I need the following or I can't help...
- The ROM you're using (date/version too)
- The kernel you're using (date/version too)
- A description of the problem
- A logcat of the problem in action
Changelog
Code:
[I]4-14-2015[/I]
- New test version for CM12 based ROMs. I believe this should work with most kernels.
[I]Version 2.0[/I]
- CM11 based ROMs only
- Updated mixer_paths.xml with more recent version from CM11
- Deodexed, signed, and zip aligned VoiceWakeup.apk. The app can now bypass the lockscreen on CM11 based ROMs
Disabling the lockscreen is still necessary for CM11S ROMs because those keys aren't public
- Added a "loud" version. It increases the microphone volume levels to make it more sensitive
[I]Version 1.0[/I]
- Initial Release
Woow. It seems working flawlessly
me wanty. Hopefully you can post a how to in the near future
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jojo_whit3 said:
I bought the OnePlus One in August because I was interested in the always on listening feature that they showed off back in the Spring. So when I actually received the phone, I was pretty disappointed to learn that they took the feature out before shipping. Over the past couple weeks, I've been working on a way to get this feature back in the phone and I think I finally got it working pretty well. I've only tested it on the 25R and 33R builds, but it should work on most ROMs for this phone. The mod uses the always on low power core, so there's no significant drop in battery life. I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here. But in the meantime, here's a demo of it working...
Click to expand...
Click to collapse
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
share it pls!
Overdose1986 said:
share it pls!
Click to expand...
Click to collapse
Did you read the OP?
I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here.
Click to expand...
Click to collapse
Transmitted via Bacon
looks cool, do keep us updated if you are able to share this "legally" or can you pm me the "not so legal" way? LOL
I didn't know I wanted this until now
That looks awesome
I've been trying to contact someone from the Cyanogen team to get some more information about posting this. If anyone has any contact info, either send me a PM or send them over to this thread.
To give a little more information about this mod, its essentially a port of the VoiceWakeup.apk I found here. If you use apktool to disassemble this file, it's easy to tell it came directly from Qualcomm. However, if the Cyanogen team intended to release this apk with the phone initially, then I'm assuming they already have some agreement in place with Qualcomm. So hopefully that also means it'll be ok for me to post this mod in the near future.
26.2man said:
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You would still be able to download the OTA updates, but you wouldn't be able to apply them since there would be changes to your file system. If you make a nandroid backup in recovery, then anything is easily reversible.
Thanks. Hope you can release this soon.
Sent from my A0001 using Tapatalk
Looks great, wonder if the cm team is working to make it work by choosing you own wake up command. Had it on my find 7a and saying snapdragon was strange
If it's already freely available then it's unlikely to cause any more issues, depends on what did you do to"port" it I guess.
All the cm11s apps have been made available, so if it came from an existing rom I can't really see much of an issue. But I'm not a lawyer
Alternative is to post a walkthrough of your changes to the original.
Sent from my A0001 using Tapatalk
Awesome work, hopefully you're and to post it up for us eventually.
Hi Everyone...I did a little thread cleaning. Please, lets not harass the OP about when this will be released. Like everything else on xda, it will be released when the developer is ready. Just as a reminder to everyone,
yes this is a hackers site, but certain things are not allowed. If the OP wants to make sure that he isn't violating CMs or Qualcomm's Intellectual Property then we should let him do this to his own satisfaction. Nobody
wants to see a modification removed because CM or Qualcomm complained.
Thanks!
This looks really good! Would love to have this feature, keep it up man
If you're worried about posting the modded APK and the IP issues, can you at least let us know what you modded so we can do it on our own?
had a quick play with it earlier,
Cm 11 nightly contains the background libs (except liblisten.so) but there's some java calls missing. Curious that cm have left most of the libs in place.

[ROM][I9295(jactivelte)][5.0.2] SlimLP [UN-OFFICIAL]

SlimLP Android 5.0
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimLP is currently in alpha / beta stage, some custom features are already in place, but much much more is planned for the future.
Download:
First build , Date : 1/29/2015
https://s.basketbuild.com/filedl/devs?dev=mythi&dl=mythi/slim/Slim-jactivelte-5.0.2.alpha.0.91-UNOFFICIAL-20150129-1852.zip
Second build , Date : 2/3/2015
https://s.basketbuild.com/filedl/devs?dev=mythi&dl=mythi/slim/Slim-jactivelte-5.0.2.alpha.0.91-UNOFFICIAL-20150203-1046.zip
Third build , Date : 2/11/2015
https://s.basketbuild.com/filedl/devs?dev=mythi&dl=mythi/slim/Slim-jactivelte-5.0.2.alpha.0.91-UNOFFICIAL-20150211-1836.zip
Google Apps / How to
Our resident Gapps guru, @dankoman, is still working on our custom Gapps. For now please use those provided here.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
Slim FAQ
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
Kernel Source
https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.0
Device Trees used :
for jactivelte
https://github.com/hashem78/android_device_samsung_jactivelte/tree/slimlp
-----
for jf-common
https://github.com/hashem78/android_device_samsung_jf-common/tree/slimlp
Thanks to :
SlimRoms
Cm
@AntaresOne
@spegelius
@rebelos
@olarf
me :victory:
Why do you put TARGET_DEVICE=jfltespr in slim.mk?
https://github.com/hashem78/android_device_samsung_jactivelte/tree/slimlp
...
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=jactivelte TARGET_DEVICE=jactivelte \
TARGET_DEVICE=jfltespr \
BUILD_FINGERPRINT="sams....
That's Samsung Galaxy S4 (Sprint) while you claim this slim build is for Samsung Galaxy S4 (Intl ) Active i9295.
@O-T using words like "claim" will easy trigger a defensive stance on many persons. Are you not happy to have the second 5.02 rom for your device? Or you just can't do better.
Its almost like next thing a army of lawyers will jump on the mod… learn to chose words dude…. No one ows you nothing
O-T said:
Why do you put TARGET_DEVICE=jfltespr in slim.mk?
https://github.com/hashem78/android_device_samsung_jactivelte/tree/slimlp
...
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=jactivelte TARGET_DEVICE=jactivelte \
TARGET_DEVICE=jfltespr \
BUILD_FINGERPRINT="sams....
That's Samsung Galaxy S4 (Sprint) while you claim this slim build is for Samsung Galaxy S4 (Intl ) Active i9295.
Click to expand...
Click to collapse
@O-T words I am not claiming anything , check your facts and come back
https://github.com/spegelius/android_device_samsung_jactivelte/blob/cm-12.0/cm.mk this is how I found it in @spegelius and cm does it ., BTW the value isn't important because it adds a check in updater script to determine whether this is a gs4 for sprint or gs4 active .
Oh damn, i wondered why adb shell shows jfltespr, need to fix this. Copypasta error.
And nce work mythi :good:
spegelius said:
Oh damn, i wondered why adb shell shows jfltespr, need to fix this. Copypasta error.
And nce work mythi :good:
Click to expand...
Click to collapse
lol yeah i was about to remove the flaag in the next build was debugging some apps and noticed jfltespr in log lol ,
thanks for your thanking me
mauk said:
@O-T using words like "claim" will easy trigger a defensive stance on many persons. Are you not happy to have the second 5.02 rom for your device? Or you just can't do better.
Its almost like next thing a army of lawyers will jump on the mod… learn to chose words dude…. No one ows you nothing
Click to expand...
Click to collapse
Despite English is not my native language I usually spell and construct grammatically as best I can to avoid misunderstanding. Sorry if that single word offended you.
Also sorry for not including fancy words like dude, bro, man, guys, lol, rofl or more of this kind.
In respect of the person who is addressed I will not fall to the level of calling anyone dude, bro, man or guys when male/female is unknown.
Status
Dear OP, I would like to know the latest status of this ROM though it has only been posted a few days ago. Do you have any plan on releasing new updates for this ROM in the nearest time? Thanks.
amruhaidy said:
Dear OP, I would like to know the latest status of this ROM though it has only been posted a few days ago. Do you have any plan on releasing new updates for this ROM in the nearest time? Thanks.
Click to expand...
Click to collapse
yes , i will , but i dont see slim adding much features in daily so weeklies will do it until slim adds all their features
O-T said:
Despite English is not my native language I usually spell and construct grammatically as best I can to avoid misunderstanding. Sorry if that single word offended you.
Also sorry for not including fancy words like dude, bro, man, guys, lol, rofl or more of this kind.
In respect of the person who is addressed I will not fall to the level of calling anyone dude, bro, man or guys when male/female is unknown.
Click to expand...
Click to collapse
Sorry of i offended you.. Not my intention… I just hope you got my point… if not, well...others will put it in worst words then I did when it will be the case ..cheers and I am omw with the install.
Thanks for this ROM. It works like a charm for an early build and I'm expecting the next updates will be better. Good job to OP and everyone that worked together. Just to report that NFC isn't working but I hardly see it as a problem since I never use it anyway.
EDIT - Enabled ROOT from the Developers Option but how do I get SuperSU works here? Or do I even need one? Thanks
amruhaidy said:
Thanks for this ROM. It works like a charm for an early build and I'm expecting the next updates will be better. Good job to OP and everyone that worked together. Just to report that NFC isn't working but I hardly see it as a problem since I never use it anyway.
EDIT - Enabled ROOT from the Developers Option but how do I get SuperSU works here? Or do I even need one? Thanks
Click to expand...
Click to collapse
I never used nfc personally too , but I will work on it the next build , if you want SuperSu from chainfire simply the supersu zip from recovery(make sure you have enable root from developer options)
Tested first alpha version.
* MP3 ring tones not working, (same issue for 1101, 2501, 2701, 3001 and now 3101 official, Unofficial )
Really strange :-/
Another issue that I just found is the Camera sometimes unresponsive and Unable to connect the camera message popped up. Thanks
Sent from my GT-I9295 using XDA Free mobile app
camera not working
This fix works for the camera.
http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973
@ mauk - I've had a run in with @O-T before - It seems to be a serial offender when it comes to flaming people - There are only so many times that you can use the excuse of something not being your native language. @ O-T The sensible way would be to ask someone who has english as a first language to read you posts first.... that way any unpleasantness can be avoided - If you want to PM me your posts I'll check them over. As for being called dude - as far as I'm aware it can be non gender specific term - so no offence caused there!
Thanks for the sharing! But I'm gonna wait for the OP to fix this issue in the future build.
Sent from my GT-I9295 using XDA Free mobile app
SuperSU for root on Lollipop - tested working
@amruhaidy
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
nasaprinsloo said:
@amruhaidy
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks dude. That matter had been resolved but it's good that you share, someone might need it. Thanks!
Sent from my GT-I9295 using XDA Free mobile app
injenue said:
This fix works for the camera.
http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973
Click to expand...
Click to collapse
Are you sure thats for gs3 bro

Our Device doesn't work with Android keystore?

I tried running the "bitwarden" app without success on omnirom, AICP and paranoid. I was able to get it to work once on AICP but then never able to recreate the scenario or know what was different. When I provided logcats to the developers they came back asking why our device doesn't work with the android keystore. Specifically:
01-23 23:01:06.816 11841 11841 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid ---> SimpleInjector.ActivationException: Key not yet valid ---> Java.Security.InvalidKeyException: Key not yet valid
Namely
Java.Security.InvalidKeyException: Key not yet valid
This is the error. For some reason that device doesn't work with the Android Keystore. Any idea why?
I was going to say something about Chinese phones and not having good encryption due to the Chinese government's need to snoop on literally everything, but I don't think that's the case. Have you tried it on other ROMs, namely, stock/official LeEco ROMs? Or eUI? If bitwarden still doesn't work, you ought to contact a veteran dev like codeworkx.
sk8223 said:
I was going to say something about Chinese phones and not having good encryption due to the Chinese government's need to snoop on literally everything, but I don't think that's the case. Have you tried it on other ROMs, namely, stock/official LeEco ROMs? Or eUI? If bitwarden still doesn't work, you ought to contact a veteran dev like codeworkx.
Click to expand...
Click to collapse
In the bug report I opened at bitwarden a second user has reported the same issue with AICP 13.1. I personally tried AICP 12.1, Paranoid Android 7.3.1 and Omnirom 7.x. Oddly I did manage to get it working on AICP 12.1 one time but then was unable to identify what was different or recreate the situation. I did leave a PM for codeworkx identifying the issue since it appears to be a problem on both nougat and oreo. If it's an issue with any app that tries to use encryption in ANY form it could be a big problem. I don't see how that could be the case though since they have android pay working on some roms and it certainly uses encryption in it's processes (or at least I'd think it would).
Bitwarden bug report: https://github.com/bitwarden/mobile/issues/264
That app seems to be working for me, what exactly i should do to reproduce the crash?
voron00 said:
That app seems to be working for me, what exactly i should do to reproduce the crash?
Click to expand...
Click to collapse
Which ROM? Which version of Android? At least provide that information too...
sk8223 said:
Which ROM? Which version of Android? At least provide that information too...
Click to expand...
Click to collapse
Personal build of paranoid, 7.1.2. I don't think i've changed anything related to fscrypt/keystore.
voron00 said:
That app seems to be working for me, what exactly i should do to reproduce the crash?
Click to expand...
Click to collapse
I personally tested the app on Omnirom 7.x, AICP 7.x, and Paranoid Android 7.x.
A 2nd user in the bitwarden bug report stated it crashed for them as well under AICP 13.1 (Android 8.x).
https://github.com/bitwarden/mobile/issues/264
So if you have it working please state Rom, and kernel used .
*update*
Are you using the "stock" kernel in your personal build or one of the available ones like darkobas's or blackscreen?
famewolf said:
I personally tested the app on Omnirom 7.x, AICP 7.x, and Paranoid Android 7.x.
A 2nd user in the bitwarden bug report stated it crashed for them as well under AICP 13.1 (Android 8.x).
https://github.com/bitwarden/mobile/issues/264
So if you have it working please state Rom, and kernel used .
*update*
Are you using the "stock" kernel in your personal build or one of the available ones like darkobas's or blackscreen?
Click to expand...
Click to collapse
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797
voron00 said:
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797
Click to expand...
Click to collapse
I'll give it a try. For me and others the bitwarden app crashes immediately when you try to open it...you never get to actually use it for anything.
I'm currently on the "official" paranoid android 7.3.1 with it crashing like that so will try yours. Hopefully just a drop in replacement.
voron00 said:
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797
Click to expand...
Click to collapse
I just flashed your rom, open gapps 20180123 mini and finally magisk 15.3...booted up and had it start restoring apps from backup...installed bitwarden as one of my first apps and tried to open it...it promptly closed....so tell me what you are doing different please.
famewolf said:
I just flashed your rom, open gapps 20180123 mini and finally magisk 15.3...booted up and had it start restoring apps from backup...installed bitwarden as one of my first apps and tried to open it...it promptly closed....so tell me what you are doing different please.
Click to expand...
Click to collapse
Magisk could be your problem or backups, maybe try without them first. I did nothing unusual really, just downloaded that app from play store and it works, but i don't have root.
voron00 said:
Magisk could be your problem or backups, maybe try without them first. I did nothing unusual really, just downloaded that app from play store and it works, but i don't have root.
Click to expand...
Click to collapse
Are you using open gapps as well? Are you using mini or another version? I'll try it without magisk and without any type of restore.
famewolf said:
Are you using open gapps as well? Are you using mini or another version? I'll try it without magisk and without any type of restore.
Click to expand...
Click to collapse
Im using opengapps stock but i dont think gapps is an issue, most likely root.
voron00 said:
Im using opengapps stock but i dont think gapps is an issue, most likely root.
Click to expand...
Click to collapse
I tried your rom and open gapps..no magisk...no data....did the bare minimum to get to the desktop and installed bitwarden via playstore. It crashed the same as always.
Will download opengapps stock and give it a try.
*deleted*
famewolf said:
I tried your rom and open gapps..no magisk...no data....did the bare minimum to get to the desktop and installed bitwarden via playstore. It crashed the same as always.
Will download opengapps stock and give it a try.
Click to expand...
Click to collapse
@voron00
Tried the unofficial version of paranoid + opengapps stock...nothing else.......connected to my google account...installed bitwarden via play store...it crashes.
Until I can find a 2nd person that says it works for them I have to consider you the lucky one
@voron00
After alot of testing it looks like a clean install of AICP 12.1 is the ONLY rom I personally could use that will let bitwarden work. Titanium Backup can be used to restore user apps and the data for those apps but that's it. Thanks for the information that it was possible to get it to work although I'm still unsure how you got it working on Paranoid Android unless perhaps you restored data from AICP 12.1 that had whatever bitwarden is looking for. Here's hoping android pay works on AICP 12.1. The low volume in calls on AICP is very bad or I'm going deaf..will work on that next.
I got works on AOKP 7.2.1 everything works on this great ROM.
Sent from my LEX727 using xda premium
mchlbenner said:
I got works on AOKP 7.2.1 everything works on this great ROM.
Click to expand...
Click to collapse
How is in call volume and speakerphone? So far the only ones that I found with good in call sound were pixel experience and omnirom.
famewolf said:
How is in call volume and speakerphone? So far the only ones that I found with good in call sound were pixel experience and omnirom.
Click to expand...
Click to collapse
In call is good.
Sent from my LEX727 using xda premium

Gapps Have To Be Included In Custom Roms?

I've been looking at buying the phone since there's a sale going on Amazon for $249USD, but after reading a bit through the forum, seems like custom roms will have gapps preinstalled?
This would be a real deal breaker for me, as I'd like to go microG, Xposed FakeGapps, FakeStore, Fdroid route, Google Free, as much as possible...
But if gapps have to be presinstalled, anyone used Terminal Debloater and uninstalled gapps with it?
Hmm
I dunno about using the rom without gapps, but CarbonRom doesn't come with gapps.
I use it with gapps and its pretty smooth, so I'm assuming it should be the same without it.
CarbonRom also has signature spoofing included.
foueddyf said:
I dunno about using the rom without gapps, but CarbonRom doesn't come with gapps.
I use it with gapps and its pretty smooth, so I'm assuming it should be the same without it.
CarbonRom also has signature spoofing included.
Click to expand...
Click to collapse
I was reading something on XDA over this, not sure now, sounded like because of some issues custom roms had to come with Gapps preinstalled for Essential.
But now you mentioning Carbon without, well, guess that throws that out the window, I hope... LOL
Every custom rom I've installed didn't have any Gapps installed, expect for just a few of the the basics, phone, messenger, calendar...
I never install Gapps, I use microG, Xposed, F-Droid here on my phones, I like to be as Google Free as possible.
Thanks
A lot of the essential (mata) roms have gapps included because it's actually a pain to install it post-install because of the 2 partitions.
So many users get confused and end up flooding the Rom threads with the same questions on how to install gapps.
I thought if they want the Gapps, then people would just pick and choose between the various OpenGapps and flash one in twrp?
hmm
DoR3M3 said:
I thought if they want the Gapps, then people would just pick and choose between the various OpenGapps and flash one in twrp?
hmm
Click to expand...
Click to collapse
Typically, you would do that, but for whatever reason Essential Phone is a lot harder to install gapps on; apparently it's not as easy as flashing in TWRP, I'm not daring enough to mess up the rom install by installing it on my own
My guess is, the partitions really throw a wrench into the equation.
Thanks!
beard805 said:
Typically, you would do that, but for whatever reason Essential Phone is a lot harder to install gapps on; apparently it's not as easy as flashing in TWRP, I'm not daring enough to mess up the rom install by installing it on my own
My guess is, the partitions really throw a wrench into the equation.
Thanks!
Click to expand...
Click to collapse
Is the A/B partitions, that have just come out, pretty much the same on all Android devices?
Because I see on some phones with A/B it seems to all be working easier then then Essential... hmm
Anyone?
DoR3M3 said:
I use an Mi A1 which has A/B partitions, I wonder what is so different about the Essential then?
Anyone?
Click to expand...
Click to collapse
Flash carbon then..it doesn't include them
Can't we all just get along? Lol, @DoR3M3 did you get your phone yet?
I just got one and installed resurrection remix no pre installed gaps
ipatrick123 said:
I just got one and installed resurrection remix no pre installed gaps
Click to expand...
Click to collapse
Nice to hear, carbonrom was mentioned with no gapps...
Are you going to try microG and Xposed on it, if so, let us know how that works out...
DoR3M3 said:
Nice to hear, carbonrom was mentioned with no gapps...
Are you going to try microG and Xposed on it, if so, let us know how that works out...
Click to expand...
Click to collapse
Actually just made a post about a huge issue I am having with Xposed that caused me to need to Uninstall it, but I really need to have it installed so I was asking for suggestions on what to do. As far as microG probably sometime soon I've been customizing the hell out of this phone.
https://forum.xda-developers.com/essential-phone/help/essential-phone-fingerprint-scanner-t3820388
I've had a cleanup in here and I don't want to be returning for more of the same!
If you've got nothing constructive to add to the thread, do not even bother posting here.
If you see that one or more of your posts have been deleted, I'm referring to you!

Categories

Resources