Search results

anyone having quick battery drain using this rom?

is there a apn option in this rom?

v4a supported for r32?

samething + saving snaps isnt working...

cant seem to get this to save snaps at all

has anyone tried v33 with android N?

has data been fixed? cant get data working on 1/26 nightly.. baseband 1.23

Uhn_dre

Uploaded one of my photography pics to the flickr group but dont see the tags for it coming up in the app

Tmobile LTE GPE Wifi is fine

ota link fails to flash ...twrp 2.8.7

Welp the latest nightly is terrible. Lost data connectivity and it hasn't returned since. Sent from my m8 using Tapatalk

GPS working?

i dont deal with roms anymore

yeap i disabled it so no one can pm me

cool just dont complain when things stop working

you do under these are unofficial dev builds and are not meant to be daily driver software? They are built for bug testing and bug reporting but not for stable day to day use.....

use root explorer

http://forum.xda-developers.com/showpost.php?p=63702456&postcount=3088

too bad i use linux and not windows EDIT: I got it to boot. Flashed your RUU zip to covert to GPE then reflashed TWRP 2.8.7 lastly flashed: https://www.androidfilehost.com/?fid=24269982086989725 and after 5 mins it booted up

i am having same issues as you man

The its Apache licensed not GPL. They don't have to share code. Android is accessible to anyone so no violation if anyone can access code and build on it. So if they decide to make proprietary code then they can without sharing it to the public...just accept this fact Sent from my Nexus 5...

it wont be, oxygen os and other manufacturer roms fingerprint scanner features are proprietary and under legal disclosure. So after market roms wont have the features until android M

hmm built using your resource ontop of PA Grarak ,testers saying they having sim issues. Had that trouble when you brought up device?

nope

will never be included in rom....use a third party app

dont bother doing unofficial releases, people need to wait per week like everyone else

I don't appreciate unofficial builds when I still haven't fixed bringing up the Rom. Ask permission before just building without knowing the ramifications of what you're building and releasing to people. Its in a new github organization for a reason.... Please remove links or I'll contact a mod...

you obviously don't realize supporting devices we don't own is a sh!t idea

thanks for feedback, next time post logs via pastebin

not in op, lvm builds are linked in PA community

Multirom needs to be updated to 2.8.4.1 for PA to work on it

boom

thanks however, even with making selinux permissive and adding seliux permissions. Still can not get device to boot wondering if my implementation is wrong somehow last_kmesg: [ 8.008765] SELinux: Could not set context for /cache: Read-only file system [ 8.009439] SELinux: Could not...

tried to do it based off your commits, device wont boot: https://github.com/AOSPA-legacy/android_device_oppo_find7-common/commit/428454011c895f3474f5e6d00a654a30026ea8d7 https://github.com/AOSPA-legacy/android_device_oppo_find7-common/commit/bedfa5db2e4810193333aad970c1dddf6b9cd75c

they use caf, thats the difference

any plan on updating this? doesnt work on lollipop even disabling block

thought that was implied....

find7s and find7 next nightlies from jenkins should fix bricking issues as they come with firmware additions

i highly doubt video issues will be fixed anytime soon

not fun when users want a working device they spent $700 on

kind of a pos job for that to happen

i still think its a hardware thing but ok

pretty sure its not blobs, ive redone them 5 times. Building on cm base with each redone blobs resulted in video playback still working fine however on aosp base its broken....

find 7

pfft wish i had the money for one

hmm no source

next idea would be hardware repos especially. media... All roms with working playback use Caf hardware repos + pathmap implement from cm

AFAIK i havent seen a github source for that rom, which is ashame and against XDA rules

device must not have the battery included or it wont see it as qualcomm driver