Related
maxdamage2122 has set up a buildbot and will be making nightlies. I haven't had the time to read the sticky for cm7 nightlies for a few days, and am glad I did. My builds will be discontinued so that we don't have a plethora of threads with different builds.
Here is the page with maxdamage2122's statement: http://forum.xda-developers.com/showthread.php?t=1064775&page=30
Mods, please close this thread so that the real rom dev threads get bumped up.
changelog
NOTE: Flash Gapps afterward for market,gmail,etc.
Known bug(s):
--dsp manager fc erratically
----FIX: settings->applications->manage applications->all->dsp manager->clear data will stop the fc (thanks dodo99x!)
Release 6-21-11
-repo sync @~7:10 P.M Pacififc
-should include all changes up to: Add vivo (HTC Incredible S) support (android_vendor_cyanogen) (Not for our device, just stating last item in changelog)
-Download Link: http://www.multiupload.com/8PL7BUOEII
Release 6-20-11:
Should include all changes up to:
Workaround for blackscreen after unlock with electron beam. (android_frameworks_base)
from http://cm-nightlies.appspot.com/?device=harmony
Link: http://www.multiupload.com/GHIXTGU1D8
Release 6-19-11:
Should include all changes up to:
libaudio: Add missing GB function (android_hardware_msm7k)
from http://cm-nightlies.appspot.com/?device=harmony
Just flashed....thanks
Sent from my GTablet using XDA Premium App
Whats the difference between nightly and stable?
TheMuffStuff said:
Whats the difference between nightly and stable?
Click to expand...
Click to collapse
Generally, when a release has been tested thoroughly and shows no signs of having any major bugs(e.g. camera not working, no touchscreen interaction) it is considered stable and usable as a daily driver for most people. The nightly builds of CM7 are considered unstable, because as new features are added on a daily basis, there is a possibility that those features/corrections may break some functionality in the device. This is not always the case, but it can happen.
This build seems pretty stable to me at least. Have at it and tell me/everyone what you think.
Issues?
Anyone test this out yet? Are there still issues with camera res, etc? How about Netflix playback?
thanks.
will you keep building?
tjsooley said:
thanks.
will you keep building?
Click to expand...
Click to collapse
I'd like to. I'm going on vacation in a few days, so after Wednesday I may not do a build for a week. Until then I'm planning on doing a release every night, contrary to what I stated in the OP. I'm not one for thorough testing/debugging/fixing though, so I will not attempt to patch/add anything to these releases other than what a nightly repo sync adds.
ubufugu said:
Release 6-20-11:
Should include all changes up to:
Workaround for blackscreen after unlock with electron beam. (android_frameworks_base)
from http://cm-nightlies.appspot.com/?device=harmony
Link: http://www.multiupload.com/GHIXTGU1D8
-Severe Bug: DSP manager force closes at erratic inervals. Not sure if it's just me or this build.
--FIX: uninstall with titanium backup, take dsp manager from previous nightly and place it in /system/app with proper permissions and reboot.
Release 6-19-11:
Should include all changes up to:
libaudio: Add missing GB function (android_hardware_msm7k)
from http://cm-nightlies.appspot.com/?device=harmony
NOTE: Flash Gapps afterward for market,gmail,etc.
Click to expand...
Click to collapse
The nightly list for Harmony is huge; however they do not seem to be packaging up for release like the other devices... anyone know why or when the harmony nightly will be packaged up and released (it has been almost a month since the last nightly was released!) ?
GTablet said:
The nightly list for Harmony is huge; however they do not seem to be packaging up for release like the other devices... anyone know why or when the harmony nightly will be packaged up and released (it has been almost a month since the last nightly was released!) ?
Click to expand...
Click to collapse
Start reading about 3/4 down: http://forum.cyanogenmod.com/topic/20070-cm7-discussion-of-nightlies/page__st__60
essentially(at least as far as I understand) The Gtablet build was renamed from harmony to smb_a1002 under the malata name/platform. This broke the buildbot for us for the nightlies, which has not been fixed yet. I have not yet seen an eta on when nightlies for us will be up again.
ubufugu said:
Start reading about 3/4 down: http://forum.cyanogenmod.com/topic/20070-cm7-discussion-of-nightlies/page__st__60
essentially(at least as far as I understand) The Gtablet build was renamed from harmony to smb_a1002 under the malata name/platform. This broke the buildbot for us for the nightlies, which has not been fixed yet. I have not yet seen an eta on when nightlies for us will be up again.
Click to expand...
Click to collapse
ubufugu,
Thank you for the reply and link; both were VERY helpful !!!
Rick
GTablet said:
ubufugu,
Thank you for the reply and link; both were VERY helpful !!!
Rick
Click to expand...
Click to collapse
Damn it, they need to get the quote and thanks button away from each other. I guess you got a free thanks there GTablet.
Well, was quoting to say same from me, I was going through nightly withdrawals.
i am releasing this to all from a a very special friend of mine. so enjoy folks, as many others have before you as well !!!
Build #7 is live. Changes to ramdisk.
Kernel 2.6.35.14-08042011 is live.
Keep checking for updates via twitter @ProTekkFZS.
If you are a DInc user that followed my thread, you will be plenty familiar here.
KERNELS
2.6.35.14 08/04/2011 http://fzservers.com/cm/mecha/2.6.35.14-08042011.zip
MD5SUM: 40104693b6cc222668fb9ec9f111ac3f
UPDATE
Build #1 07/31/2011: http://www.multiupload.com/6CL0QGXO80
MD5SUM: 276a0b360e1a480166812b0540e34d28
Build #2 08/02/2011 http://romshare.deployfu.com/downloads/613/587/update-cm-7.1.0-ProTekk-Build-2-signed.zip
MD5SUM dd0f1b6f223958a9ebe6841df053b521
Build #3 08/02/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-3-signed.zip
MD5SUM: 4ea9f41649ad6a840c64dda84e377b9b
Build #4 08/03/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-4-signed.zip
MD5SUM: ff5c25114d38e483f42974147ed5f3cf
Buld #5 08/05/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-5-signed.zip
MD5SUM: 48c99a0aed89ccf619f4728cb337864b
Build #6 08/06/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-6-signed.zip
MD5SUM: afeeece65d680aac1147a19a3c0518db
Build #7 08/06/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-7-signed.zip
MD5SUM: fc4bcacb6631d90df02b28d1c1aae265
You can grab these builds via ROM Manager as well.
Q: What is this?
A: This is something I have started doing since the buildbot has been on hiatus and I needed to feed my addiction to flashing the most recent build of CyanogenMod 7 I could get my hands on. I started doing this for myself and saw that there was a pretty big demand for the newest updates possible so I said why not share it with everyone. Nothing in my builds have been altered so don't worry. It is not a ROM I have customized. All I am simply doing is pulling the source every morning and compiling it.
Q: Wait, so this is the same as the CyanogenMod 7 nightly builds? Why rename it and make it?
A: Great question. Think about it this way. The CyanogenMod team builds nightly right? Well, lately it hasn't been nightly but more random. The advantage of building daily, for me and the people on the east coast, it is much better to have a new build readily available in the morning versus waiting all night for a release or no release at all and wasting time. I am not taking credit for the CyanogenMod team's work and I refuse to as I am simply pulling the source and compiling it. The renaming of my builds is to defer the confusion between the CyanogenMod nightly builds as my builds have nothing to do with how CyanogenMod builds and releases.
Q: Ok, so if I am having issue X,Y,Z who do I report it to?
A: As of yet, there is no official CyanogenMod 7 thread so please feel free to post here!
Q: Uh, if there are nightlies then why would I want to use your builds? Doesn't it make sense to use one of the nightlies?
A: Sure, you are more than free to use one of the official CyanogenMod nightlies! The reason why some use my builds is simply the fact that they want to have the newest updates and merges on their device! The buildbot does not always pump out a new nightly where as I always will be building and compiling every day. Also, the nightlies don't always include the newest merges because of the fact that merges can be push at any time.
Q: If you are building these daily what happens if updates are merged after you build?
A: Haha, I know this is sad but I don't have much of a life but I do have one! I keep on top of all the merges almost like clockwork! I normally check about every hour to see if there are any major updates and fixes. If a major fix is merged I will be pushing out another build as soon as I see that it has been merged! So no need to worry about having the newest build besides downloading it and installing it.
Q: Ok, so nightly #X is released, wouldn't it be the same as your build #Y?
A: This is a little harder to answer but I will make it simple. As I said before and as many have noticed, the buildbot doesn't always push a new build and I compile AFTER all the merges are done for the day. I will be working on a log that tracks the differences between the nightlies and my builds shortly.
Q: I can't get CWM 3.x.x.x to update on my phone. I don't know what I'm doing wrong. Every time I go to recovery, it says i'm running 3.y.y.y
A: ROM Manager > Menu > Settings > Erase Recovery > Back > All ClockworkMod Recoveries > select desired version
Any other questions? Please let me know and I will include them in this post!
------------------------------------------------------------------------------------------
I personally test out each build as I release them and if there is one posing serious issues I will pull it!
All my builds will be online and ready to download no later than 10 AM eastern time! I try to get them out as quick as possible for you guys!
As a sidenote and fore more clarification, I am NOT taking credit for the fabulous work that the CyanogenMod team is doing! This is NOT a custom ROM I have edited or made! This is always going to be straight from the CyanogenMod team's source!
Please enjoy it and happy crackflashing to all!
Perhaps one of these builds will clear up my "can't establish a secure connection" problem when trying to log into my google account on the slayhers build.
Thanks for uploading.
Random battery drain/heat?
I personally think this is the best ROM. However, not sure if it's just me, the phone would often heat up as if I am running something intensive. Obviously, when that happens, the battery would drain fast. Is this just me? Also, will there be anymore updates to this awesome rom? Thanks
icedmayhem said:
i am releasing this to all from a a very special friend of mine. so enjoy folks, as many others have before you as well !!!
Build #7 is live. Changes to ramdisk.
Kernel 2.6.35.14-08042011 is live.
Keep checking for updates via twitter @ProTekkFZS.
If you are a DInc user that followed my thread, you will be plenty familiar here.
KERNELS
2.6.35.14 08/04/2011 http://fzservers.com/cm/mecha/2.6.35.14-08042011.zip
MD5SUM: 40104693b6cc222668fb9ec9f111ac3f
UPDATE
Build #1 07/31/2011: http://www.multiupload.com/6CL0QGXO80
MD5SUM: 276a0b360e1a480166812b0540e34d28
Build #2 08/02/2011 http://romshare.deployfu.com/downloads/613/587/update-cm-7.1.0-ProTekk-Build-2-signed.zip
MD5SUM dd0f1b6f223958a9ebe6841df053b521
Build #3 08/02/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-3-signed.zip
MD5SUM: 4ea9f41649ad6a840c64dda84e377b9b
Build #4 08/03/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-4-signed.zip
MD5SUM: ff5c25114d38e483f42974147ed5f3cf
Buld #5 08/05/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-5-signed.zip
MD5SUM: 48c99a0aed89ccf619f4728cb337864b
Build #6 08/06/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-6-signed.zip
MD5SUM: afeeece65d680aac1147a19a3c0518db
Build #7 08/06/2011http://fzservers.com/cm/mecha/update-cm-7.1.0-ProTekk-Build-7-signed.zip
MD5SUM: fc4bcacb6631d90df02b28d1c1aae265
You can grab these builds via ROM Manager as well.
Click to expand...
Click to collapse
why would protekk want this posted here? He hates xda. Rootzwiki not giving him enough exposure?
nrfitchett4 said:
why would protekk want this posted here? He hates xda. Rootzwiki not giving him enough exposure?
Click to expand...
Click to collapse
It doesn't really matter does it? That's not a development related question and sort of thread jacking. It's posted and still up after a week, so that's good enough imho.
yareally said:
It doesn't really matter does it? That's not a development related question and sort of thread jacking. It's posted and still up after a week, so that's good enough imho.
Click to expand...
Click to collapse
I think its a valid question related to the developer of this ROM. Seems like a back door way to get your ROM on xda after being banned. Hell, could be a secondary account of Protekk.
In either case development has slowed down on both sites.
Sent from my ADR6400L using Tapatalk
Hello friends.
As all of us see, LG released their KitKat sources long time ago. Our great developers like @dr87 @Savoca @houstonn and others made it with Their hard work to merge them so we have two stable / nearly stable roms: Mahdi and PA. But what with other roms? Most of the roms are based on CM, so they still have bugs.. During months, CM doesn't seem to have done ANYTHING.
So my question is, how about to send a message (or spam, in any way u name it) by all of us to CM, to the maintainer? We have official support, but in fact it's "support without support" in my opinion. Maybe after these messages they would finally start to do something, because it's like they forgot about G2...
Regards.
EDIT: so we have a way to contact => https://jira.cyanogenmod.org/secure/Dashboard.jspa
now we should make a well, polite message so everyone would copy it and drop there.
Another way it would be to ask the maintainer directly https://plus.google.com/+RicardoCerqueira
EDIT2: I gave a comment to Ricardo on Google+ here https://plus.google.com/+RicardoCerqueira/posts/4dc8kVBYuTq feel free to do it as well
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Inviato dal mio LG-D802 utilizzando Tapatalk
Airidas said:
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
Click to expand...
Click to collapse
could u give a link please? so we could prepare a message and then everyone would leave it there
vittogn said:
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Click to expand...
Click to collapse
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
reas0n said:
could u give a link please? so we could prepare a message and then everyone would leave it there
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
Click to expand...
Click to collapse
Here: jira.cyanogenmod.org
Thanks, so anyone is, i would say, good in kind speaking to prepare a message?
Oh and we could also use Google+ and ask the maintainer directly https://plus.google.com/+RicardoCerqueira
Replyed 2 times to posts in his google + account with message " When LG G2 is going to have updated KK sources? A lot of people are waiting for bug-free CM and CM-based 4.4 ROMs ". I hope that all you guys do the same.Cheers
Sent from my LG-D802 using XDA Premium 4 mobile app
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
apparently theres a bit of confusion, there was some one nightly where the rotation wasnt working with the jb baseband, (im gussing on that nightly he used the kk source ) because flashing the kk baseband on that build fixed the rotation issue, but im not quiet aware of what the situation is ince im back on stock. anyways ill be swinging it on the latest nightly just to clarify my doubts. and im pretty sure they just want the maintainer to switch to kk source , btw nice to see you here hope your cooking something great for us
dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
reas0n said:
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
Click to expand...
Click to collapse
Did you get a response from Ricardo?
LenAsh said:
Did you get a response from Ricardo?
Click to expand...
Click to collapse
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
reas0n said:
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
Click to expand...
Click to collapse
Oh
Discussion and information about official cm14 nightlies.
Download latest nightly: get.cm/?device=bacon
Installation:
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Optional: Install the Google Apps addon package
Reboot
Useful links
Latest twrp recovery: Download from here
Install twrp recovery: Official instructions
Gapps: Open Gapps
Jenkins: Build history of jenkins
(Check the build process)
Cyanogenmod code review: Gerrit review
Simple changelog: cmxlog
Device tree: Bacon cm14.1
Kernel tree: oneplus msm8974
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
vickeye said:
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
Click to expand...
Click to collapse
The test builds out there seem fairly good. So I think odds are with us
vickeye said:
The odds are v might never get official cm14 .. but things might just change.,, All we gotta do is wait
Click to expand...
Click to collapse
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
the_rooter said:
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
Click to expand...
Click to collapse
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
vickeye said:
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
Click to expand...
Click to collapse
That was related to not getting official COS i.e. Stock ROM won't get Nougat. CM nightlies will be available just have to be patient they don't need to go through CTS
the_rooter said:
Odds that we won't get a official? Why you claim this? There are phones older than Bacon that will be getting bacon.
Click to expand...
Click to collapse
Bacon in bacon? OPO inception.
I'm sure CM14 will come to OPO in an officially branched CM capacity, but probably not a stock OnePlus commissioned capacity. Does that make sense? I'm still thinking about bacon in bacon...
https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
cm14 branch for bacon? someone post it in official cm13 nightly thread.
varben said:
Can we discuss about cm14? What is achieved until now? How are the early unofficial ROMs? Will we have an official cm14?
Seems like cm14 branch is up: https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
Click to expand...
Click to collapse
lets see.. i hope so
varben said:
Can we discuss about cm14? What is achieved until now? How are the early unofficial ROMs? Will we have an official cm14?
Seems like cm14 branch is up: https://github.com/CyanogenMod/android_device_oneplus_bacon/tree/cm-14.0
Click to expand...
Click to collapse
So its a green light for bacon users waiting for official cm14 right?
Sent from my A0001 using XDA-Developers mobile app
vickeye said:
May be I was wrong .. but if you look at the so called "801 and noughat drama " and there isn't a official branch for cm14 yet .. again I may be wrong .
Click to expand...
Click to collapse
The oneplus x with the same chipset as baocn has had a cm14 branch for a while now so I doubt they'll leave us behind
gursimar said:
So its a green light for bacon users waiting for official cm14 right?
Click to expand...
Click to collapse
Personally I can't say. But is a small step towards a possible official cm14 (imho)
Maybe this thread wakes up soon, there is bacon cm14 commits
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
giaur said:
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
Click to expand...
Click to collapse
It is just the processor support missing, from what I read. Other commits will follow more easily.
And finally bacon commits on gerrit...
http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_oneplus_bacon
giaur said:
Well, let's analyze it a bit. Official 6.0 release: 05.10.2015. First official cm13 nightly build: 24.11.2015. So, cm release just 1.5 month after official Marshmallow release.
Nougat release date: 22.08.2016. Most likely, we won't get anything usable after 1.5 months. Now we have nothing (nothing official, even official cm14 sources are unusable currently).
I see no reasons to be optimistic. Progress is much slower this time.
Click to expand...
Click to collapse
Agreed. It will probably be slower this time around since Cyanogen has let go of 20% of their workforce since CM13 was released.
Sent from my A0001 using Tapatalk
Elius2676 said:
Agreed. It will probably be slower this time around since Cyanogen has let go of 20% of their workforce since CM13 was released.
Click to expand...
Click to collapse
I don't see the connection here with cm14 and Cyanogen work force.
Cm doesn't depend on paid workforce.
varben said:
I don't see the connection here with cm14 and Cyanogen work force.
Cm doesn't depend on paid workforce.
Click to expand...
Click to collapse
I suggest you start doing your homework before speaking. Hint: go through the gerrit commits and look for people with "@cyngn.com" emails. maybe starting from Steve Kondik himself.
fmc000 said:
I suggest you start doing your homework before speaking. Hint: go through the gerrit commits and look for people with "@cyngn.com" emails. maybe starting from Steve Kondik himself.
Click to expand...
Click to collapse
Well, I think I did mine. CyanogenMod and CyanogenOs (from where the workforce was "fired") is not the same. So, please Carry on! This discussion is not useful really. It is discussed to death already.
Hi guys,
I want to notice you that a new build of Paranoid Android is available on the official site
http://get.aospa.co/official/onyx
The AOSPA 7.3.0 comes with various bug fixes and performance improvements.
I'm testing to discover if major bugs were be resolved.
For now, overnight freeze was not occurred.
magisk - work
substratum theme - work
gestures - works
unlock phone with face - work
viper fx - doesnt work
Thanks for the information. Nice to see the development for our onyx but still goes. Is this the official thread here? Or is it only on Google Plus?
What kind of GAPPS do I need to install PA ?
@kratosboss are you new maintainer for onyx?
--
Sim slot 2 bugs still persist since the first build of PA.
Any workaround for this?
---------- Post added at 03:25 AM ---------- Previous post was at 03:23 AM ----------
kareem19 said:
What kind of GAPPS do I need to install PA ?
Click to expand...
Click to collapse
Opengapps, pico or nano, I prefer nano..
Again new thread in wrong section...!!
AOSPA thread is already there you should share it there rather than creating new thread.if the rom does not belongs to you don't post in original development section.
Fap4k said:
Again new thread in wrong section...!!
AOSPA thread is already there you should share it there rather than creating new thread.if the rom does not belongs to you don't post in original development section.
Click to expand...
Click to collapse
Sorry man,
I was writing from my phone and I made mistake.
I'm not the mantainer of this ROM. I only found the post on xda (not the forum) with Onyx specifically bug fixes.
Although OVERNIGHT FREEZE still occurred!
I'm switching to AOSCP 'cause in AOSP 8.0 the equalizer don't work (even with Magisk and modules) and the battery drain in higher than normal!
With the PA from the firt release to the last 7.3.0 every morning the opx is dead and the alarm don't ring. I have to press power button to force the restart. How can I resolve? Thanks
7.2.0, 7.2.1, 7.2.3, 7.3.0, 7.5.0, 8.0, 10.0....... no different.
Q: why bother to flash? A: because im dumb enough
Q: who is the official maintainer for onyx anyway? A: NONE, a ghost, i dont really care
Q: Do you like the new PA's added features XYZ? A: NO. its a gimmick for me.
Q: So its useless? A: MAYBE. but its unusable.
Q: will he (maintainer) abandoned us again with broken build or unfixed old issues (just like the former maintainer) A: i hope not. but its crossed in my mind
End of chat: good luck then.. | you too..
Part.0 said:
7.2.0, 7.2.1, 7.2.3, 7.3.0, 7.5.0, 8.0, 10.0....... no different.
Q: why bother to flash? A: because im dumb enough
Q: who is the official maintainer for onyx anyway? A: NONE, a ghost, i dont really care
Q: Do you like the new PA's added features XYZ? A: NO. its a gimmick for me.
Q: So its useless? A: MAYBE. but its unusable.
Q: will he (maintainer) abandoned us again with broken build or unfixed old issues (just like the former maintainer) A: i hope not. but its crossed in my mind
End of chat: good luck then.. | you too..
Click to expand...
Click to collapse
Yep thats what I want to say...why people so curious about this ROM if they doesn't even know who is maintainer for this ROM..People here creating threads to share issues but don't know who is going to solve.
The ROM seems fine and functional but it doesn't seem to use OOS camera blobs so you can't get manual mode in any camera. Why are we hell bent on having crappy camera software?
Can anyone confirm working of sdcard in exfat in 7.3.0
This is not the official thread.
Please do not post on this thread.
Use the official thread which is located here: https://forum.xda-developers.com/on...ranoid-android-6-0-1-aospa-oneplus-x-t3400781
Forritan49 said:
Please do not post on this thread.
Use the official thread which is located here: https://forum.xda-developers.com/on...ranoid-android-6-0-1-aospa-oneplus-x-t3400781
Click to expand...
Click to collapse
This is a thread for PA marshmallow. Not Nougat.
The original thread for PA Nougat is closed because the dev had to quit.
There were no communication from PA team to OPX users which is quite sad (because that means that we won't have "full support". NB : I'm not criticizing the team).
Kéno40 said:
This is a thread for PA marshmallow. Not Nougat.
The original thread for PA Nougat is closed because the dev had to quit.
There were no communication from PA team to OPX users which is quite sad (because that means that we won't have "full support". NB : I'm not criticizing the team).
Click to expand...
Click to collapse
But the discussion is taking place over there...
10 posts (last on 24 Sept) isn't a discussion
Sent from my ONE E1003 using Tapatalk
gurgao said:
10 posts (last on 24 Sept) isn't a discussion
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Correct ! Burt it not anly the number of post, it's the fact that the dev there doesn't post anymore or update the topic.
The official PA 7 thread is closed.
Incrovantilist said:
Can anyone confirm working of sdcard in exfat in 7.3.0
Click to expand...
Click to collapse
When I tried the 7.3.1 before coming back do LOS 14.1, it didn't work (I had to backup and re-format to FAT32).
Paranoid Android bug for OPX
I have a really serious problem here. I flashed my OPX the rom with nano g-apps as mentioned in the thread. Initial set up was fine. I configured personal settings. Now the device sometimes hangs during the usage. It just hangs while I'm using. Not a particular app or particular thing but it suddenly stops working and gets stuck. I then have to press power button for like 30 seconds to reboot it. I thought this is because first time but then this kept repeating and I'll be battery less if it continues.
Any help? If you wanna see some kind of bug report for my device, please tell me where I would find it to upload here.
PA is not updated anymore by a dedicated dev to OPX. So specific bugs won't be solved.
I'd advise to try an other rom...
Except that , you can try a custom kernel on it if it's possible (at one moment, RJ blocked kernel installation... Don't know if still the same.)