#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM13.0 Marshmallow Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM10, 10.1, 11.0, 12.0 and 12.1 builds. Builds are generated automatically on daily basis. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
kylon
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Make sure you have properly converted your device to use aceopt partition layout.
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-aceopt.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-aceopt.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
InspireMod
codefi.re
Kernel
Source: github
Compiler: stock AOSP gcc-4.9
Branch: cm-13.0
Kernel Version: 3.0.101
defconfig: ace_defconfig
Contact:
My Google+ (I don't accept Hangouts invitations though, use IRC if you need something that requires direct chat.)
My twitter
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 13.0 Nightlies [EOL], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl, kylon, Phantom Shadow
Source Code: https://github.com/OpenDesireProject
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 2.8.7.0
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2015-11-26
Last Updated 2018-10-05
Screenshot
OMG! It's finally here.
The never ending thread begins. :laugh:
If you are still doubting. here is the proof.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this dream is becoming a reality for our device.
Please take a minute and say thank you to @Mustaavalkosta
Wow!!!!! interesting......Long Live Our DHD
xdagee said:
OMG! It's finally here.
The never ending thread begins. :laugh:
Screenshots, First impressions and review coming up soon.
Thank you @Mustaavalkosta
Click to expand...
Click to collapse
Initial screen shot as posted by Mustaavalkosta in his CM12.1 thread : http://i.imgur.com/mdpQJKO.png
Adoptable Storage
Continuing on the adoptable storage discussion from cm 12.1 thread:
Now that I really thought about it, this is not a solution for us. Our biggest issue is the small system partition which won't benefit in any way from adoptable storage thus I will stick to maintaining only aceopt device tree and regular ace tree is frozen on cm-12.1.
gjc said:
Initial screen shot as posted by Mustaavalkosta in his CM12.1 thread : http://i.imgur.com/mdpQJKO.png
Click to expand...
Click to collapse
yeah got that, thanks. But still waiting to post screenshots from my own device. (you know what I mean)
Mobile data fixed with PhantomShadow's patch for 12.0. Now it's mainly just hanging on the camera libs.
Fantastic news, thanks you for all
So impressive this phone is still kicking thanks to Mustaavalkosta, It's still sitting on my desk as my first android phone. Can't wait to try cm13 on it.
SubNoizey said:
So impressive this phone is still kicking thanks to Mustaavalkosta, It's still sitting on my desk as my first android phone. Can't wait to try cm13 on it.
Click to expand...
Click to collapse
Desire HD was my first Android phone too. But don't have the phone anymore
really great
thanks very much.
Waitting for the final great news.
Oh my gosh the hype is real :d ... Man you are fantastic!
HTTPS, first build, etc.
HTTPS / SSL
SSL certificates are now renewed across the ODP domains just in case someone faced HSTS block earlier with expired certificates. Let me know if something isn't working with SSL. Let's Encrypt service only just entered open beta after all.
Nightlies
I started nightlies to check that everything is in order in automation side of things. Camera is still broken and since I caught cold last night again and this time it seems to be quite furious cold I'm not sure when I can/will continue to poke the camera with shim library. You can poke around in 6.0 now though and get mad when all the things are broken.
Only opt variant build is available. Regular ace builds are dead for 13.0 as far as I'm concerned. You can read how to convert your stuff to support opt version's changed partition layout here. I'll update FAQs and so forth as soon as I can.
First Nightly Quick Impressions
Didn't expect much on flashing the first nightly, but it's running smoothly.
so far, so good. . Expect for screen flicker glitches which happens randomly on using the phone.
xdagee said:
Didn't expect much on flashing the first nightly, but it's running smoothly.
so far, so good. . Expect for screen flicker glitches which happens randomly on using the phone.
Click to expand...
Click to collapse
And the flicker will likely get a bit worse when camera libs start working again. They trigger crazy blue flickering during bootup etc. and there's no fix in sight. I have already spent countless hours with 12.1 based builds and this LCD underflow issue. But hey, 6.0 is booting up and is generally running ok apart from the ever-increasing annoyances. I guess that's something even though not a perfect score.
Mustaavalkosta said:
And the flicker will likely get a bit worse when camera libs start working again. They trigger crazy blue flickering during bootup etc. and there's no fix in sight. I have already spent countless hours with 12.1 based builds and this LCD underflow issue. But hey, 6.0 is booting up and is generally running ok apart from the ever-increasing annoyances. I guess that's something even though not a perfect score.
Click to expand...
Click to collapse
Does this means it is using the new adreno blobs (what about saga, same thing too)? Do gapps/playstore work now? Someone installed games? Does it improve performance? I'll stay on 12.1 for now (it's my daily phone) but will definitely be following the CM13 thread
i23098 said:
Does this means it is using the new adreno blobs (what about saga, same thing too)? Do gapps/playstore work now? Someone installed games? Does it improve performance? I'll stay on 12.1 for now (it's my daily phone) but will definitely be following the CM13 thread
Click to expand...
Click to collapse
Yeah, I wouldn't have even released anything for 13.0 without the new adreno blobs because the old ones are already killing WebView on 12.1 and because that issue seems to come from the actual blobs themselves it's pretty much impossible to fix without changing blobs. Going backwards is not really my "thing" so new blobs or gtfo.
And the builds are the same for both devices. This would have been very difficult to manage with different stuff for each device.
I was initially planning to quit this hobby (or probably already a habit at this point) after 12.1 but since it turned out to be possible to utilise the sdcard and work around quite fatal insufficient storage issue here we still are. This has made my goals for the 13.0 a bit fuzzy but I suppose we'll see how much is doable and how much isn't. Problems have gradually got worse and worse as the upstream makes more or less huge changes while we are, for example, still using gingerbread camera blobs and this trend is continuing so let's try to keep out expectations low.
@i23098
With gapps first bootup takes hours and after boot I got error Unfortunately, Android Keyboard (AOSP) has stopped. Default browser is not crashing
marek287 said:
@i23098
With gapps first bootup takes hours and after boot I got error Unfortunately, Android Keyboard (AOSP) has stopped. Default browser is not crashing
Click to expand...
Click to collapse
I am also getting an Adroid Keyboard (AOSP) stopped working notice and an Encryption unsuccessful error warning. Pressing Reset phone reboots it into TWRP, which tries to wipe cache and Data and restart, leading to the same error warnings. (20151205 nightly and 20151201 gapps)
Today's build wasn't favorable, it has FCs throughout. quick - Is either you restore back to previous build or old back up.
Related
CyanogenMod 11 Rom for Sony Xperia Z2 Tablet Wifi (SGP 511/512)
Development stopped because Castor_windy gets official cm Support!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the Castor_windy Cm Device tree available at https://github.com/CyanogenMod/android_device_Sony_castor_windy
Kernel source: https://github.com/CyanogenMod/android_kernel_sony_msm8974pro
Big thanks to fxp Team and Bin4ry
Downloads
First Version:
https://mega.co.nz/#!6NZB1SiC!Ec2HIIzks7_FKLpjZ5rT-ZIIq64_sBtsH7mkuY56LmM
Second Version: (Fixed Touchscreen Problems)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Requirement
An unlocked Bootloader
Recovery
Not Working
-NFC
-Video recording
-ART (don't test it it cause a bootloop)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM. If you are already on CM11, just make Wipe Cache & Wipe Dalvick-Cache for a upgrade.
Install the ROM with the Recovery and than Flash gapps
Use Official CM Gapps or Latest Paranoid Gapps for 4.4.4
CyanogenMod Changelog
http://changelog.bbqdroid.org/
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
I will discontinue develope this Rom if Castor_windy get Official Support from CM
Reserved!!!!
Success.
The boot.img stuck right away.
Installed latest PA Gapps plus supersu.zip 2.01.
A few minor issues so far-
The CM11 setup was looking for a SIM Card during initial install-
but the castor_windy version doesn't support LTE or WWAN.
Mobile network setup is visible from the settings screen.
(windy_pollux does not show these menus but pollux LTE does)
My play store apps are restoring as I type- so far so good.
xbill9 said:
Success.
The boot.img stuck right away.
Installed latest PA Gapps plus supersu.zip 2.01.
A few minor issues so far-
The CM11 setup was looking for a SIM Card during initial install-
but the castor_windy version doesn't support LTE or WWAN.
Mobile network setup is visible from the settings screen.
(windy_pollux does not show these menus but pollux LTE does)
My play store apps are restoring as I type- so far so good.
Click to expand...
Click to collapse
I will look on it but i use the same lines as in pollux_windy tree
Tomorow i Release a New version and i will look on it before the release
Installation went great here too. I have the same SIM-issue as the previous poster.
Other than that, it seems to be working perfectly (aside from the known issues). Currently pulling everything in from Play!
Thanks man!
I'm seeing some crazy bettery usage - Android OS eating up 60% of the battery. The charger can't even keep up!
I'm guessing this is related to the SIM card stuff, as the power graph shows "Mobile network signal" in bright red at the top -which is odd, considering this is the wifi model .
thomholwerda said:
I'm seeing some crazy bettery usage - Android OS eating up 60% of the battery. The charger can't even keep up!
I'm guessing this is related to the SIM card stuff, as the power graph shows "Mobile network signal" in bright red at the top -which is odd, considering this is the wifi model .
Click to expand...
Click to collapse
Yes i saw the battery usage is crazy and the cpu load is to high but both can related to the sim card stuff
After Work i will looking on it but i can 't guarantee that i can fix it
rcstar6696 said:
Yes i saw the battery usage is crazy and the cpu load is to high but both can related to the sim card stuff
After Work i will looking on it but i can 't guarantee that i can fix it
Click to expand...
Click to collapse
That's what testing is for! Take your time - I'd rather things are done well but take time, than done quickly but crappy .
A couple more things working with the ROM-
-weird screen flickering when I connect with a USB cable to a PC
after booting the tablet standalone (it happens with ADB USB debugging on and off)
-I can confirm the battery drain too - same results
-I managed to turn ART runtime on- it rebooted 3-4 times but it did come back eventually
-screen touch bug (maybe after the tablet sleeps?) I set the screen lock to None and still see the bug
xbill9 said:
-I managed to turn ART runtime on- it rebooted 3-4 times but it did come back eventually
Click to expand...
Click to collapse
Are you sure? Mine rebooted a couple of times, like yours. However, they were soft reboots (not near a computer, so no logs I'm afraid). It eventually did a hard reboot at "Starting apps" and then reset to Dalvik (notice the much faster " Optimizing apps" phase). Check back in settings, but I'm guessing yours set itself back to Dalvik too.
Sorry- I stand corrected.
The ART settings did not stick.
I know it is experimental - but I have been running ART for quite a while
on other Sony devices (amami, pollux, and pollux_windy) with no problems.
The final reboot on castor_windy seems to reset Dalvik after several failed boots.
Castor _windy runs very well other than the touch interface bug. Thanks for working on this ROM and take your time. We look forward to the fix.
Sent from my Nexus 5 Unchained using XDA Premium 4 mobile app
New Build is up!!
A New Build is online
Touchscreen Problems should be fixed
And newest cm source are used!! (CyanogenMod 11 M8)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Enjoy it!!
Rcstar6696
rcstar6696 said:
A New Build is online
Touchscreen Problems should be fixed
And newest cm source are used!! (CyanogenMod 11 M8)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Enjoy it!!
Rcstar6696
Click to expand...
Click to collapse
Thanks! Flashing NOW!
rcstar6696 said:
A New Build is online
Touchscreen Problems should be fixed
And newest cm source are used!! (CyanogenMod 11 M8)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Enjoy it!!
Rcstar6696
Click to expand...
Click to collapse
Installation of the new build went perfectly. Does it fix the battery drain?
And, of course, thanks!
rcstar6696 said:
A New Build is online
Touchscreen Problems should be fixed
And newest cm source are used!! (CyanogenMod 11 M8)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Enjoy it!!
Rcstar6696
Click to expand...
Click to collapse
Installed, Touchscreen is working flawlessly. No bugs apparent so far. I will let you know if I see anything...
THANKS AGAIN RCSTAR6696!
Thanks RCSTAR6696 working good so far..
rcstar6696 said:
A New Build is online
Touchscreen Problems should be fixed
And newest cm source are used!! (CyanogenMod 11 M8)
https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
Enjoy it!!
Rcstar6696
Click to expand...
Click to collapse
Any chance for LTE version, please?
Sent from my SGP521 using Tapatalk
da900 said:
Any chance for LTE version, please?
Sent from my SGP521 using Tapatalk
Click to expand...
Click to collapse
I think i will do it at the weekend!! But i need a Tester because i dont have the lte Tablet
Would you do that??
thomholwerda said:
Installation of the new build went perfectly. Does it fix the battery drain?
And, of course, thanks!
Click to expand...
Click to collapse
I think its a little Bit better but not fixed in this version
Go in airplan mod then 3g things are disabled i think battery live wil be better but not the same as in stock:crying:
Touch is definitely better than official rom...
Camera doesn't seem to work for me...
and have managed to freeze it in chrome with the cnn website when you click on the video to play, not shaw what it is maybe flash or something...http://edition.cnn.com/2014/07/10/justice/prostitute-yacht-killing/index.html?hpt=hp_c2
does work ok in UC browserHD tho
other than that it's awsome, thankyou, understand it's work in progress.
Keep up the good work..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
[ROM][UNOFFICIAL][4.4.4][WEEKLIES] SlimKat [m4], ROM for the HTC One Mini
Contributors
pandasa123
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2014-08-13
Last Updated 2014-08-12
Downloads
ROM - Full ROMs every week
SlimGapps - Download Google App package and other addons. Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Slim 7.0 Stable
Start of project
For full list: Click here
Click to expand...
Click to collapse
List all Questions and Off-Topic discussions in Q/A Thread
Remember, flash at own will! Don't message me and threaten me with a lawsuit because I may or may not have broken your device!
Issues
Waiting for this to fill
Thanks to:
SlimROMs for ROM
CyanogenMod for kernel
Click to expand...
Click to collapse
Installation Instructions
You must unlock your bootloader or be S-OFF.
You must have a custom recovery installed that allows SELinux.
Download the HTC One Mini build .
Locate Slim 4.4 Gapps here.
Fully wipe your device from Recovery if you are not coming from SlimKat already.
Reboot into recovery and install.
Hi bud. Just to confirm Rom boots fine and installs flawlessly! So far not noticed any issues. Unfortunately I'm a loyal candyRom user so will be bouncing back to that but good work and thanks for bringing this to the m4..cheers
Good luck on getting it official
Anyone found any bugs? I want to get rid of them for you guys by next build
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
dipje said:
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
Click to expand...
Click to collapse
Well that's up to the user if he wants a none sense ROM. I seen all the fuss about the issues etc even seen the Sense Fanboys loving that people are being scared off AOSP too. Tbh I don't see any problems with it my Rom been tested for awhile and is build from slim not CM with no issues at all... if people don't wanna try aosp then that's their loss....
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
dipje said:
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
Click to expand...
Click to collapse
Well I don't own this device anymore but the guy who tests builds doesn't have any issues with my ROM. This isn't my thread and I didn't build this ROM so you would have to take it up with the thread owner...
"On multiple aosp version" ???
Had no problems with any aosp rom on this device and I haven't ran sense for about a year now. No issues with pac,or slim and definitely none with candy which is my daily rom. Tbh I did have one issue with cm in the early days which I managed to recover from... But I put that down to my error... Flashing different kernels, installing performance mods/scripts etc and using different xposed modules.
Apologies for hijacking thread
Don't worry about the thread hijack lol...i wasn't paying attention..
I'm back from the hospital and i'm ready to build. t6vzw is brunching right now, and once it's done t6spr will start. after that, the m4 will get going and then my evita...so m4 users, expect your build to be ready by the end of tonight or so
slim m4 should be coming out today or tomorrow...the new server had a lot of build errors so i just fixed it for the evita
going to build for t6vzw, then t6spr, and then m4...
NEW BUILD! 7.6! Wait for around 15 min after this post is done and you'll see it. Check on the slim website for changelog...
http://downloads.codefi.re/ethanj99/pandasa123/Slim
Ok everyone, i'm building right now and this is the last time (i hope) that i move hosts
be a bit patient with me and i'll try and get it uploaded as soon as I finish homework
http://downloads.codefi.re/pandasa123
EDIT: UPDATED! Enjoy
New build guys - 7.9 Weekly (FINALLY )
Changelog:
Settings: Slimrecents card/text color
Add ADB over network tile
frameworks/av updates aosp caf
frameworks/base updates aosp caf
audio-caf updates
updated apns
frameworks/native-caf updates
more translations
Click to expand...
Click to collapse
enjoy
pandasa123 said:
New build guys - 7.9 Weekly (FINALLY )
enjoy
Click to expand...
Click to collapse
Sorry, but I can't find 7.9, only 7.8.
Thanks for building slim for m4!
Hey guys, Slim 8.0 Stable is out! Enjoy
pandasa123 said:
Hey guys, Slim 8.0 Stable is out! Enjoy
Click to expand...
Click to collapse
Ok. but where to download ?
http://downloads.codefi.re/pandasa123/Slim
No root after installing this ROM. Kernel installed is TWRP. No other kernel seems to work
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/d2vzw/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_d2vzw
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod/
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightlies
Created 2015-12-12
Last Updated 2015-12-12
Clean flashed earlier today and seems to be running great. Haven't found anything that doesn't work yet, camera, video, phone calls, GPS all seem to be working fine. Might be the best first nightly for any CM release on this device.
Sent from my SCH-I535 using Tapatalk
So installed Stock Gapps and the 1st nightly. So far so good, though I didn't get any of the stock CM software like messaging and the browser.
The default google camera gave me the typical "camera has failed" error that I got non stop on 12.1. My solution was always going with Open Camera. Never had issues but in a blue moon.
Any clue why?
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Shakes The AssClown said:
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Click to expand...
Click to collapse
I remember CyanogenMod said a dirty flash from 12.1 is possible, but just not tried it yet
Do we need any special version of TWRP to flash this for 6.0?
Samsung.Galaxy.S3 said:
Do we need any special version of TWRP to flash this for 6.0?
Click to expand...
Click to collapse
Nope, flashed it with the latest twrp image from their site on my old s3 and it booted up just fine
Sent from my SCH-I545 using Tapatalk
So what exactly is working right and what still needs tweaking? Is this a daily driver at this point?
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
All Hail to @invisiblek!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pogeymanz said:
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
Click to expand...
Click to collapse
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Master Cylinder said:
All Hail to @invisiblek!
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Click to expand...
Click to collapse
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
pogeymanz said:
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
Click to expand...
Click to collapse
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Master Cylinder said:
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Click to expand...
Click to collapse
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
pogeymanz said:
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
Click to expand...
Click to collapse
I used 11/25 which didn't need the zip and have just kept going.
Here's the new changelogs for CM13 builds: http://www.cmxlog.com/13/d2vzw/
Thanks to invisiblek and CM Team for keeping us current!
Great work!
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invisiblek back in the d2 saddle. Thanks!
The d2vzw must have 9 lives because this is gonna make it last quite awhile longer!!
Let's give it up for @invisiblek once more!
Darn! Gif animation doesn't work on the XDA phone app.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invsiblek back in the d2 saddle. Thanks!
Click to expand...
Click to collapse
Mine seems to do better in battery saving mode than the other 2 - puts my address across the street but the dot is next door.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps?
Click to expand...
Click to collapse
I haven't tried it while driving, but I've used it while walking, biking, and hiking. I have no idea what the difference is, but GPS is flawless on MM whereas I couldn't get a lock since KK. I usually get GPS fix in ~30-40s to ~5m accuracy. [[EDIT: That's actually in GPS only mode.]] My experience is that Mapquest is better for handling navigation purposes than Maps. Idk. Personal preference.
I follow in the footsteps of those before me, and hail the mighty invisiblek!
does anyone have a list of what currently doesn't work? I accidently flashed this when doing the weekly updates..
From what i noticed when just quickly messing with it..
Video Camera did not work (said couldn't access camera)
Front Facing camera froze (took picture but then would not let me click anything)
AOSPA 6.0.1 for the Xperia Z3 Compact!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Instructions
If installing fresh and/or coming from another ROM (including previous PA versions)
Reboot into Recovery (Please use the latest TWRP) and MAKE A BACKUP!
Wipe System, Data, Cache, and Dalvik Cache
Flash Latest OFFICIAL STOCK ROM - This will ensure a clean system and all bootloader etc updated to latest.
Wipe System, Data, Cache, and Dalvik Cache
Flash the ROM
Flash GApps
Flash SuperSU (if you want to have root, that is)
Wipe Caches and Reboot
Profit!
Download Links
ROM: http://get.aospa.co/official/aries
AOSPA Links
Google+: https://plus.google.com/communities/112514149478109338346
Gerrit: http://gerrit.aospa.co/
GitHub: https://github.com/AOSPA
#StayParanoid
XDA:DevDB Information
Paranoid Android 6.0.x, ROM for the Sony Xperia Z3 Compact
Contributors
tomgus1, sonyxperiadev, PA Team
Source Code: https://github.com/AOSPA/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSPA
Version Information
Status: Stable
Created 2016-08-08
Last Updated 2016-08-11
Reserved
Except for the camera bugs, seems to be stable. I've read somewhere about Sony releasing new sources for camera. Are these new sources used in this ROM?
juliopw said:
Except for the camera bugs, seems to be stable. I've read somewhere about Sony releasing new sources for camera. Are these new sources used in this ROM?
Click to expand...
Click to collapse
You are correct in that Sony will be releasing new binaries for camera and this is indeed what we are using for PA on Sony. However this work will take time, but we will in the end have Nexus like support for Sony devices.
tomgus1 said:
You are correct in that Sony will be releasing new binaries for camera and this is indeed what we are using for PA on Sony. However this work will take time, but we will in the end have Nexus like support for Sony devices.
Click to expand...
Click to collapse
That's what we are waiting for, Nexus like support :highfive:
However due to that nasty reversed fish-eye people just gave up, since Sony didn't release proper binaries and blobs. Lets see if that gets fixed with those releases.
Yeah. Making the camera work properly seems to be the biggest difficulty in developing for the Z3C. I will test every build and give feedback. Thanks!
@tomgus1 thanks for the rom !!
@juliopw source about new camera blobs ? Thanks !
@snaky90 Can't remember where I saw it. Only found this old post. Sorry. I will look into it again.
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
@TomGus 1 hi I can't find your sources on the official PA repository. Are you using the sony open devices repos for device tree etc?
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
Click to expand...
Click to collapse
mcgi5sr2 said:
@TomGus 1 hi I can't find your sources on the official PA repository. Are you using the sony open devices repos for device tree etc?
Click to expand...
Click to collapse
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
tomgus1 said:
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
Click to expand...
Click to collapse
Thanks for the reply, that is an almighty dependency list
mcgi5sr2 said:
Thanks for the reply, that is an almighty dependency list
Click to expand...
Click to collapse
More than I'd like but Sony has some cross-overs with Nexus which causes incompatibility.
As reported on G+ here a short sum-up after a week of usage PA on z3c.
Installation broken
Installation expects the getprop("ro.product.device") to be "aries", but mine was z3c, therefore failing. Had to edit the META-INF/com/google/android/updater-script to get it working (exchange "aries" with "z3c").
Tim: Fixed for next release.
Voice Calling volume not changable (very loud)
https://plus.google.com/u/0/+GeorgGrabler/posts/FY9xZZuHMde
Tim: No fix yet.
Voice calling crashes most of the time (beeping or no sound at all), rebooting / locking up the phone (huge issue, makes the ROM unusable for me now)
https://plus.google.com/u/0/+GeorgGrabler/posts/GF2Eac9xtcn
Tim: Fixed next release.
NFC broken
https://plus.google.com/u/0/+GeorgGrabler/posts/iejmnYxSDkh
Tim: Can't reproduce.
=> Got a log of me because he can't reproduce it. Maybe that will help (does not happen if you have a USB attached).
Log at: http://pastebin.com/brZiHsky
Fast Charge not working
https://plus.google.com/+GeorgGrabler/posts/7kKjXJDKQB7
Tim: Will never work, not part of Sony AOSP.
=> Sad, but ok .
Camera issues
Well known, we'll have to see how the open drivers get along over time. They got better in the past, but still there are issues.
I sometimes even get "could not connect to camera" after making a picture.
Can't use the rom for production until the calling issue is solved.
tomgus1 said:
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
Click to expand...
Click to collapse
bad news: My recovery was deleted by aospa
recovery isn't touched by aospa. You can't use the standard adb commands to get to recovery though, you have to use the "hardware method".
If your recovery is really gone, just re-flash it, that's not a big issue.
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Just wanted to add: AOSPA team and Tim - great work there. It looks like we could get a really usable rom some time soon (though, the volume highness will still be an annoyance if it can't be fixed ).
---------- Post added at 01:19 AM ---------- Previous post was at 12:42 AM ----------
Last but not least, thanks PA team for all the work and effort. I may not be able to use the ROM yet, even though, I'd love to. You have been and are doing great work, and I hope you'll manage to bring us a good AOSP(A) image some day (rather sooner than later if you ask me ).
Don't take my reports and disappointment as a grain of salt but constructive feedback.
STiAT said:
As reported on G+ here a short sum-up after a week of usage PA on z3c.
Voice Calling volume not changable (very loud)
https://plus.google.com/u/0/+GeorgGr...ts/FY9xZZuHMde
Tim: No fix yet.
Can't use the rom for production until the calling issue is solved.
Click to expand...
Click to collapse
@tomgus1 : Calling volume sound had already been a problem in CM12.1 sometime in 2015. Was solved then. Maybe you can find some useful infos over CM JIRA:
https://jira.cyanogenmod.org/browse/NIGHTLIES-930?jql=status = Closed AND text ~ "z3"
regards, phil
Boils down to this two commits.
https://github.com/CyanogenMod/andr...mmit/fe714b9501b58a63daef424d90cae62dc9743517
https://github.com/CyanogenMod/andr...mmit/899b01eea912bae4d31ae9d0181018de41990f61
the new version 6.0.3 is already working with the camera?
I found a little time on the site and the AOSP rom has a new version 6.0.3, someone already tested the camera is working?
http://get.aospa.co/official/aries
Camera is working, but still the same bad quality. We have to wait for the opensource drivers to get better. Sony is working on this, but it's still a long road ahead as it seems.
Lock-Ups have been fixed, the voice issue (speakers / loud uncontrollable voice level during calls) isn't (yet).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device..
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
Downloads
ROM: https://www.androidfilehost.com/?w=files&flid=134255
Recovery: https://dl.twrp.me/z3c/
Gapps: http://opengapps.org
What works?
Wi-Fi
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Video (playback)
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
Systemsounds are too loud (the soundlevel of systemsounds couldn’t be influenced by any of the loudnesssliders) - device related
Music can't be adjusted by EQ - device related
Vibration intensity can't be adjusted - device related
Touch focus doesn't work properly (until we get new blobs) - device related
Focus via Sony’s hardware (Cam) - Button doesn’t work - device related
Video recording- device related
Show weather on the status bar doesn’t work - CM related
NFC - device related
Random reboots while charging - device related
No Swipe (keyboard) - CM related
On Lockscreen there is only the actual weather displayed without location name and without icons - CM related
FLAC files could not be played - CM related
Problems with Bluetooth - device related
Theme engine is missing - CM related
Installation Instructions
Make a backup!
Unlock bootloader
Install the latest TWRP Recovery
Download the ROM and GApps
Reboot to recovery
Wipe data/factory reset if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Flash the ROM and then GApps
Reboot your phone
Enjoy!
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again. (However, if you are experiencing strange issues, you may want to try a wipe.)
OTA Updates:
Recommended recovery: TWRP
Changelog
Code:
20161206:
- Initial release
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
CyanogenMod14.1, ROM for the Sony Xperia Z3 Compact
Contributors
doriandiaconu
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2016-12-27
Created 2016-12-08
Last Updated 2017-01-06
First!
Nice one @doriandiaconu Will get testing today!
In call volume is fixed and other user experiences echo
video recording isn't functional but preview works
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Thanks!
It seems I misplaced the thread. I'll ask one of the admins to move it.
am i correct in assuming that you will get the fisheye effect on the camera with this?
downloading right now - will give it a try and report...
@doriandiaconu OK here is my first impression:
The ROM starts without probs - i even don't have to adjust the updater script :good:
Cam starts without forceclosing - but this could be not valid for the whole time - but for now it works - the foto i have taken has still little problems with autofocus - but for now not bad
* Equalizer for Music seems not to work - there is no difference in sound while applying different presets.
* Though weather for statusbar could be selected there is no weather to be seen - the same could be said for weather on the lockscreen simply not there - i installed Yahoo CM weather Provider - but the service couldn't even accept a given location ???
* System sounds could not be adjusted - they are very loud for now - but maybe there is a hidden feature to adjust...
* NFC could not be activated - the field is insensitiv
THX for this build
Update:
Weather seems to work now - maybe some time was needed for an update - on Lockscreen Weather could be seen, but Music on lockscreen has to be deactivated
veti said:
am i correct in assuming that you will get the fisheye effect on the camera with this?
Click to expand...
Click to collapse
You are absolutely right. That's something that won't be fixed that easily (if ever)
[emoji7] [emoji7] [emoji7]
Downloading now...
Hmmm, my new home...
mcgi5sr2 said:
First!
Nice one @doriandiaconu Will get testing today!
In call volume is fixed and other user experiences echo
video recording isn't functional but preview works
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Click to expand...
Click to collapse
You lucky bastard!!
I wanted to be first [emoji23]
A.R.I.S.E Z3C DiSCONTiNUEdSLiMM EliteKernel Phh.superuser Magisk Substratum
mcgi5sr2 said:
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Click to expand...
Click to collapse
My bad & thanks for the info.
Maybe it is now time for the common github creation to keep all of this clean. Will see if I can do this today.
Here is z3 not working list.
Bluetooth is fixed, then break again, etc... Other meaning: Under development
Another point are deep_sleep, we are working on it but will take time.
CC: @doriandiaconu
P.S. I came from z3 and don't own z3c so only can help on basics.
Thank you for the intervention @nailyk
Will edit OP when I get home and hopefully will fix some stuff in the next days.
EDIT: can someone make a list with what it's not working? It seems some of the things took some time to settle @Rhonin86 @mcgi5sr2
Never mind .....
i think tomorrow afternoon / evening i will find some time to proceed further tests and create a list - any wishes concerning the format of the list ?
Google Doc / Excel sheet / a simple post ...
Your wish is my demand
Cheers
Rhonin
doriandiaconu said:
You are absolutely right. That's something that won't be fixed that easily (if ever)
Click to expand...
Click to collapse
It's so bad that we will not get a proper working aosp or cm rom. I'm so pissed on sony about this, probably will not buy any sony device just because of this reason.
Delete
Truth is we could get a good working camera but this implies a lot of knowledge that i don't have and a lot of time.
Sony aren't at fault for this. Look at Samsung. Because of the Exynos CPU and the knox partition they don't even hope for a CM/AOSP project, either on the S7 or the S6.
@Rhonin86 I don't mind it either way
doriandiaconu said:
Truth is we could get a good working camera but this implies a lot of knowledge that i don't have and a lot of time.
Sony aren't at fault for this. Look at Samsung. Because of the Exynos CPU and the knox partition they don't even hope for a CM/AOSP project, either on the S7 or the S6.
@Rhonin86 I don't mind it either way
Click to expand...
Click to collapse
People know there will be no custom aosp/cm rom working on exynos chipset before buying samsung phones. I bought this phone with high expectations, but regretted.
Barua said:
People know there will be no custom aosp/cm rom working on exynos chipset before buying samsung phones. I bought this phone with high expectations, but regretted.
Click to expand...
Click to collapse
On a long term, there will be development for the shinano devices. Now it's just the beginning and we are few that are working. But there's still hope. CM12.1 was good, CM13 was hardly workable because of the 3.4 kernel. Devs didn't like that and left. Now they have switched to the 3.10 kernel again and CM14.1 is less buggy than CM13.
I think I managed to fix the NFC issue. Camera will get better once the new blobs will be released. Things will get OK. But only in due time and with a lot of work.
why is fish eye so present in this device? I got that in every rom (stock even when in 4k without steadyshot)... I came to this device from xperiaZ thinking camera will rock, and now I can't even use cm/aosp cause camera is so important to me
Edit: sorry for partially off-topic :3
I am getting error 7 when installing in recovery, please help
I also got error 7 flashing this in twrp 3+ but flashed this version last week successfully. Might have to change script can't remember if i had to or not. Good luck. I'm going to keep trying this. Cant post link new user but bing "sony aries cm14.1" choose androidbiits how to install nougat 7.1 on sony z3c. The link is good.
Take out underscores and link is to rom.
ps://androidfilehost. ______-com./?______fid=385035244224400853
For people with error 7 you can just remove the first line of the install script in the zip.
For comments on the camera, to be honest no one cares what you think here. If you want to vent go to the official sony forum, the people on XDA are working with what we have. This is a development thread for CM-14.1 if you don't have anything to add about the ROM ie logcats dmesg etc or bug reports then please don't post.
https://github.com/mcgi5sr2/device_sony_aries is the device tree i used for some early builds. It was forked from latest 7.1 branch of the sonyxperiadev repos.
hey, thanks for ur work. is great. i want to ask if is possible to apply any theme. theme engine is not yet implemented, so exist another alternative?