{
"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"
}
* By flashing this, you automatically void your warranty!
* If your phone breaks, blows up or runs away from you, do not cry to us!
* Do not ask for ETAs!!
* Download the ROM and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the ROM and then GApps
* Reboot your phone
* Enjoy
* PAC-ROM Download
* Open GApps Nano 5.1
* PAC-ROM Sharing Policy
* PAC-ROM Site
* PAC-ROM Forum
* PAC-ROM Gerrit
* PAC-ROM Changelog
* PAC-ROM JENKINS
* PAC-ROM Bug Reports/Feature Requests
* PAC-ROM Github
* PAC-ROM Stats
* PAC-ROM Google+
* PAC-ROM Facebook
* PAC-ROM Twitter
* Want to become a device Maintainer for PAC-ROM?
* PAC-ROM Central - Questions and Features broken down and seen by all PAC Devs on XDA
* PAC-ROM Team
* Cyanogen Team
* AOKP Team
* Paranoid Android
* SlimRoms
* RootBox
* Carbon ROM
* Vanir
* ChameleonOS
* Omnirom
* Paranoid SaberDroid
* Special thanks to all our Build Bot Providers (see Contributors list for all names)
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names)
* And of course, thank you for your love and support!
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
Status: Unofficial Release
NOTE: THIS IS ONE AND THE LAST ONE 5.1.1 (LMY49J) BUILD.
AFTER INSTALLATION:
GO TO SETTINGS - PAC SETTINGS - MISCELLANEOUS - PAC STATS
AND UNCHECK THIS BOX <ENABLE REPORTING>
OPTIONAL:open build.prop file (requires root) and change string "ro.build.display.id=cm_tate-userdebug 5.1.1 LMY49J..." to "ro.build.display.id=pac_tate-userdebug 5.1.1 LMY49J..." (watch screenshot #1)
Personal Modifications:
- Bootanimation is replaced with MM bootanimation
- Old fashioned Calendar replaced with Google Calendar
- Added missing OmniSwitch
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.
alexander_32 said:
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.
Click to expand...
Click to collapse
I have the same issues when building for jem. If you don't mind PMing your build errors (preferably the whole build output if you have it), I can try to patch file_contexts until transi fixes the file to resolve the build errors. Also, you may later get an issue with make_recovery_patch; if you do, let me know and I'll tell you how to fix it. transi's been quite helpful when I started building my custom CM ROM for jem; I tried contacting him about the latest issue with file_contexts, but he hasn't responded yet.
Sent from my Amazon Jem using XDA Labs
Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.
xWolf13 said:
Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.
Click to expand...
Click to collapse
Yep, I guess that Git is not up to date.
Thank you xWolf13.
alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:
vasolini said:
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:
Click to expand...
Click to collapse
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.
alexander_32 said:
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.
Click to expand...
Click to collapse
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'm gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.
alexander_32 said:
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'll gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.
Click to expand...
Click to collapse
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Alright, we'll see what happens.
Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.
mikeataol said:
Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.
Click to expand...
Click to collapse
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.
alexander_32 said:
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.
Click to expand...
Click to collapse
Fixed it as you expected it would, Thanks!
mikeataol said:
Fixed it as you expected it would, Thanks!
Click to expand...
Click to collapse
No problem
That is the last one Lollipop release (LMY49J), by the way. Forgot to add it before.
Related
These are UNOFFICIAL CM10.1 JellyBean Nightlies / Releases brought to you by Mustaavalkosta and TeamCodefire as a continuum to CM10 nightlies.
{
"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
General:
Builds are generated automatically each day week (except "releases" which will be done once a month and after SR1 when required) with latest changes from CM, Andromadus and myself. Builds use some required Andromadus' repos for msm7x30 that can be found from github (link below) and local device repo for ace. Kernel is based on synergye's KangBang kernel with some changes to fulfill some dependencies on this rom. Local manifest used for the builds can be found here. If the builds stop coming at some point, it most likely means there are changes in upstream that broke the build. I'll attend to solving such situations when I have time. Latest 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 (for msm7x30 repos)
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
Juansheng
KangBangKreations (shipped kernel is based on this)
paulb_nl
thachtunganh (s2w)
PipelinerArd (for initial spark for this project)
synergye
TeamCodefire (for build server and hosting, priceless)
a user (for provided tweaks)
Flow-Wolf (for the video review, see Q&A)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
Andromadus
CyanogenMod
Mustaavalkosta
Changelogs:
BBQLog
CM Gerrit
CM Google+
Github (see above)
Fresh installation instructions:
20130313 and newer nightlies are not compatible with KangBang 3.x or older!
Download Nightlies / Releases [BasketBuild mirror]
Download gapps (goo.im/gapps)
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot and enjoy.
Update installation instructions:
20130313 and newer nightlies are not compatible with KangBang 3.x or older!
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them.
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
codefi.re (use the donation button at the bottom of the page)
Mustaavalkosta
(codefi.re donations are used to cover the server costs, my donations will be used to increase my beard growth in a way or another)
Q&A:
Q: What's "M-Series"?
A:
CyanogenMod said:
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
Click to expand...
Click to collapse
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: HTC Dev unlock is pretty much useless when flashing roms from recovery. Until HTC One, it doesn't allow flashing boot partition from recovery which pretty much kills or cripples any custom rom if boot.img has been modified. You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: What does the ROM look like?
A: Video review by Flow-Wolf.
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM10.1 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm10
cd cm10/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
wget https://github.com/Mustaavalkosta/android/raw/cm-10.1/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: My device rebooted itself all the way to the white HTC bootsplash. What should I do?
A:
synergye said:
Regarding the reboots, it would be incredibly helpful if someone could get a last_kmsg after an unexpected reboot. To do so, go directly to recovery after the reboot (without booting into android) via the volume key and power button, then run adb pull /proc/last_kmsg on your computer and upload. I thought the issue was stemming from out of pmem errors like on vision which is why I increased pmem allocation again. Without any evidence, it's just guesswork though.
Click to expand...
Click to collapse
Flashable zip to copy /proc/last_ksmg to your sdcard, no adb needed: http://downloads.codefi.re/mustaavalkosta/last_kmsg.zip
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 10.1 Nightlies / Releases [SR3], ROM for the HTC Desire HD
Contributors
Mustaavalkosta
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: SR3
Stable Release Date: 2013-11-25
Created 2014-10-09
Last Updated 2014-10-09
First:good:
MMS - 1a perfekt
GPS- 1a perfekt (need 16sek. for 16 Sat.)
Baterry- 360 min. from 100% to 89% (GPS;Whatsapp,3 call/ 15 min.,and more....
I use HOLO L. and Juice Def. PERFEKT COMBI!!!!
THX for this ROM man!
Second :crying:
But tested! and wow.. great rom! Thank you Mustaavalkosta ! :good:
here comes another one!
Wow, owners of other devices are sure gonna be jealous. Such an old device getting so many stable 4.2 ROM! Respect to all developers.
Sent from my Desire HD using xda app-developers app
I love that so much developers release new, stable ROM for DHD. keep it up devs. Very cool.
Sent It From Outer Space.
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
ps: do you want to marry me
yener90 said:
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
Click to expand...
Click to collapse
Nope, as close to AOKP as you can get currently (feature-wise) is by using codefireX (afaik).
ps: do you want to marry me
Click to expand...
Click to collapse
Depends if you like beards?
yener90 said:
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
ps: do you want to marry me
Click to expand...
Click to collapse
blindndumb has paranoid android, cm10 and AOKP mixture ROM, commonly known as PACman ROM. It is based on RB's R30
Sent from my Desire HD using xda app-developers app
Mustaavalkosta said:
Nope, as close to AOKP as you can get currently (feature-wise) is by using codefireX (afaik).
Click to expand...
Click to collapse
Yes i know, but it has so much patches, that i get trouble with it.
SR1:
- clock issue -> i came really late to university, after this i use more often my wristwatch xD
- opera issue -> only browser i can use on android
had more troubles didnt remember
SR2 i realised same problems. not the clock issue but the other.
Now i am using CM10.1. really love the rom
AOKP has more features -> only reason i want to have this rom
Mustaavalkosta said:
Depends if you like beards?
Click to expand...
Click to collapse
hmm i got self one i didnt expected that yu would agree :laugh:
NiCk.JaY said:
blindndumb has paranoid android, cm10 and AOKP mixture ROM, commonly known as PACman ROM. It is based on RB's R30
Click to expand...
Click to collapse
i already tried it.
Its slow. i dont like lags. i need a phone which is fast. codefireX & CM10.1 are the fastest roms i ever had.
Sorry being offtopic.
Here goes the 4.2 again , hooraay ..
Sent from my iPhone powered iOS 6.0.1 by Apple™
Hey anyone can show me screenshots of this ROM plz............
sagar4all007 said:
Hey anyone can show me screenshots of this ROM plz............
Click to expand...
Click to collapse
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
KalZakath said:
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Maybe i'm wrong, but it's not true. - I don't know any other pure AOSP+CM rom 4.2 for Ace
The other builds i've tested have extra settings
KalZakath said:
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
True but it is hard to show diffrience by screenies. If someone want to see how does it looks should install it because 1st impession is - standard 4.2.
Sent from my Desire HD using xda app-developers app
thanks to all the developers that make me use this phone
Mustaavalkosta said:
These are UNOFFICIAL CM10.1 JellyBean Nightlies brought to you by Mustaavalkosta and TeamCodefire as continuum to CM10 nightlies.
General:
Builds are generated automatically each night with latest changes from CM, Andromadus, KangBang stable kernel and myself. Builds use some required Andromadus' device specific repositories (for Desire S) that can be found from github (link below) and local device repository for ace. Local manifest used for the builds can be found here. If the builds stop coming at some point, it most likely means there are changes in upstream that broke the build. I'll attend to solving such situations when I have time. Latest 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 (for device specific repos)
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
Juansheng
KangBangKreations
PipelinerArd (for initial spark for this project)
synergye
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:
Andromadus
CyanogenMod
KangBangKreations (kb-stable)
Mustaavalkosta
Changelogs:
BBQLog
CM Google+
CM Gerrit
Github (see above)
Installation instructions:
Download ROM
Download gapps (goo.im/gapps)
Put them on SD card.
Reboot to recovery.
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot and enjoy.
Donations:
codefi.re (preferred, use the donation button at the bottom of the page)
Mustaavalkosta
(codefi.re donations are used to cover the server costs)
Q&A:
Q: What's the difference between these builds and PipelinerArd's builds?
A: These builds are as close to CM source as possible without breaking either build or hardware support. PipelinerArd uses a big chunk of codefireX's repositories for various things. This doesn't mean his builds are bad, they are just not very close to CM source anymore. You can compare the manifests yourself and decide which one better suits your needs. My local manifest / PipelinerArd's manifest. And again, I'm not here to invalidate his work and I've no quarrel with him. I'm just mentioning this as someone is bound to ask about it.
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: I'm not here to fix any device specific bugs or problems. I only compiled the build manifest using repositories already available to everyone. I can only rearrange build manifest to fix feature X. If it still doesn't work, too bad. Hope that Desire S is having the same problem and Andromadus is going to fix it. Help yourself and help others.
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Something about something something something.
A: Ask the guy/gal next to you.
Click to expand...
Click to collapse
If you're gonna compare your rom to mine you could at least get the repo right git://github.com/PipelinerArd/android.fit -b cm-10.1
I've just flashed and configured this rom as my daily one.
Anyway it seems to works fine as the other 4.2.1 roms, but anyway i've found a not "green" camera on this one on the preview of the shot.
PipelinerArd said:
If you're gonna compare your rom to mine you could at least get the repo right git://github.com/PipelinerArd/android.fit -b cm-10.1
Click to expand...
Click to collapse
Ah, my bad. The new github layout is confusing. I only saw the popular repositories when I was looking for your manifest. I spend my time mostly with bitbucket these days. You didn't have a direct link to manifest (nor any repo links) anywhere in your ROM's first post (or at least I didn't and still can't see anything). :|
I'm sorry for any hard feelings caused by unintentionally stepping on toes. I fixed the incorrect Q&A section. At least flashmaniacs should be happy for daily doses. Hurray.
can anyone confirm it possible to auto focus by hold shutter icon and capture by releasing it?
{
"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"
}
What is OmniROM?
OmniROM Gerrit Review
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/
Important Information
Root access has not been incorporated into the ROM source yet, so you will need to flash SuperSU in recovery SuperSU
For all you Do-It-Yourself-ers, simply follow this guide to initialize a build environment and get your own builds started - OmniROM - Setting Up A Compile Environment
Got a bug report? Want to request a feature?
jira.omnirom.org
Click to expand...
Click to collapse
Installation Instructions
FROM ANOTHER ROMS
Factory Reset/Wipe Data
Format System
Format Dalvik Cache
Install ROM
Install Gapps
Reboot
Profit
UPDATE FROM OMNIROM TO NEWER RELEASE
Settings -> System Updates -> Check for update
You will NOT need to wipe anything with the delta updates :good:
Click to expand...
Click to collapse
Downloads
ROM:
jflte
http://dl.omnirom.org/jflte/
Gapps:
PA 0-Day Gapps
Click to expand...
Click to collapse
Contributors/Credit
The OmniROM Team - Great devs that have taught me just about everything I know about this stuff in such a short amount of time
CyanogenMod
ParanoidAndroid for the GApps package
@jumoog for working with me on the jf family of devices (MOAR Galaxay S4's to be supported soon!)
@SferaDev for ALL the work on adding Samsung RIL support
@CNexus for his awesome boot.img tools and helping me out
@Evisceration for his insane kernel pwnage
Testers
@CPA Poke
@LamboDroid19
@RockMan195
@crzygrmn
@uberstupd
@Pump Ac7i0n
And anyone else I apologize I forgot on this list but thank you
Source
OmniROM Source
XDA:DevDB Information
OmniROM, a ROM for the AT&T Samsung Galaxy S 4
Contributors
jakew02
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Rooted, Custom Recovery
Based On: AOSP
Version Information
Status: Alpha
Current Stable Version: -
Current Beta Version: -
Created 2013-10-28
Last Updated 2014-04-08
Changelog
Changelog
OmniLog - jflteatt
OmniLog - jfltecan
Q&A
Frequently Asked Questions
Q: Why don't I have root access after installing OmniROM?
A: OmniROM does not have an official, prebuilt root method yet, so you'll just need to flash SuperSU in recovery and you'll have 100% working root access. SuperSU can be found here: SuperSU
Q: Where is <insert feature here>, like CM/AOKP/PA/etc have??
A: Omni is still very early in development, but moving at an incredibly fast rate. New feature, bug fixes, and device support are added just about daily. Check it out here: OmniROM Gerrit Review for the latest and greatest
Q: How do I start/stop screen recording?
A: Volume UP + Power will start screen recording. Simply drag the notification bar down and click the button to stop.
Q: HALP NFC doesn't work!!
A: We know.
Nice to see a new release, thanks for sharing with us
Awesome
Interesting ...
Nice work Jake!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
anyone try it out yet?? i've been running it all day. everything's working great! :highfive:
I just wiped everything and installed it. I haven't found any issues yet, but I haven't even made any phone calls yet.
Thanks a ton for pulling this all together and sharing with the rest of us. I've been itching to try Omni.
EDIT: I made a phone call now! I haven't run across anything that doesn't work. Calls, texts, camera all work fine.
jakew02 said:
anyone try it out yet?? i've been running it all day. everything's working great! :highfive:
Click to expand...
Click to collapse
I did load it up seems to run just fine, missing alot of features I like to use such as hardware keys (custom settings) which is the main thing and the general interface options so I'll wait for some future tweaks.
I'd love to try this but again what are the tweaks in this rom? What do they differ from others and what are the same?
Sent from my SGH-I337 using XDA Premium 4 mobile app
PapaMag said:
I did load it up seems to run just fine, missing alot of features I like to use such as hardware keys (custom settings) which is the main thing and the general interface options so I'll wait for some future tweaks.
Click to expand...
Click to collapse
Custom hardware keys options are comnig very soon
lauterm said:
I just wiped everything and installed it. I haven't found any issues yet, but I haven't even made any phone calls yet.
Thanks a ton for pulling this all together and sharing with the rest of us. I've been itching to try Omni.
EDIT: I made a phone call now! I haven't run across anything that doesn't work. Calls, texts, camera all work fine.
Click to expand...
Click to collapse
toxicpaulution said:
I'd love to try this but again what are the tweaks in this rom? What do they differ from others and what are the same?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right now there are less than CyanogenMod, it is very close to stock AOSP at this point, but Gerrit review is overloaded with tons and tons of new features, theres at least one or so new features being merged in daily. Read the articles I posted in the OP for more information on that from the OmniROM team themselves, their philosophy, and future plans
It might be missing some extras, but this is a very solid ROM.
I've only found two minor issues that are probably upstream issues. The capacitive buttons never light up. I'm pretty sure that's a known Omni-wide issue. Secondly, I got root to work, but OpenVPN Installer still says it can't remount /system as rw. I even tried remounting it rw first in root explorer, but it just won't install the OpenVPN binary. I'm guessing that's related to root not being built in.
Battery life seems good given how much I've had the screen on (50% battery with over 2.5 hours of screen on).
Overall, great job, Jake!
Sent from my SGH-I337 using xda app-developers app
Will there be a jfltecan build down the road?
SGH-I337M jfltecan
Gordietm said:
Will there be a jfltecan build down the road?
SGH-I337M jfltecan
Click to expand...
Click to collapse
definitely. i didn't want to push out builds for a device that i couldn't test on.
If someone wants to test for me, I'll definitely do it. :highfive:
Gordietm said:
Will there be a jfltecan build down the road?
SGH-I337M jfltecan
Click to expand...
Click to collapse
I would gladly test it.
SGH-I337M jfltecan
Gordietm said:
I would gladly test it.
SGH-I337M jfltecan
Click to expand...
Click to collapse
I'll send you a PM once i get it built. working on having it compile TWRP over CWM right now , after class i'll start working on jfltecan :good:
Jakew02, I'm going to try to compile a build using your repos. Hopefully I can start trying to contribute a bit. I'm a total noob though.
Sent from my SGH-I337 using Tapatalk
jakew02 said:
I'll send you a PM once i get it built. working on having it compile TWRP over CWM right now , after class i'll start working on jfltecan :good:
Click to expand...
Click to collapse
Huh? Recovery is NOT built into the kernel for this device. Its in a different partition of its own. There is no compiling TWRP over CMW for this device. Recovery needs to be compiled separately if you're trying to compile your own. Just look in the device repos.
jakew02 said:
I'll send you a PM once i get it built. working on having it compile TWRP over CWM right now , after class i'll start working on jfltecan :good:
Click to expand...
Click to collapse
I'm on Canadian i337m and I would test it too.
Right now I'm just using t mobile or ge roms. To chicken to flash any thing att only.
Sent from my SGH-M919 using xda app-developers app
task650 said:
Huh? Recovery is NOT built into the kernel for this device. Its in a different partition of its own. There is no compiling TWRP over CMW for this device. Recovery needs to be compiled separately if you're trying to compile your own. Just look in the device repos.
Click to expand...
Click to collapse
Well, add TWRP configuration to the device tree then and confirm it still builds
Sent from my SGH-I337 using Tapatalk
#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.
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet 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 our public Gerrit to submit patches of any type.
Slim6 is the project name for SlimRoms based on Android 6.0.1 Marshmallow and offers the following original features:
Slim6 is still in its early stages of development so if your favourite feature is not back yet, don’t worry more will be added with later releases.
SlimLauncher
An Open source, feature filled launcher! -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to 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.
*/
POST LIST:
2nd post: Screenshots
3rd post: Known Bugs and workarounds (if any)
4th post: Downloads and recommended GApps
5th post: Changelog and Thanks
6th post: Updates, aka announcements.
Sources:
Local Manifest
You can actually determine everything from there, I did not cherry-pick or kang any extra features.
Feature list can somehow or another be found here or here
XDA:DevDB Information
Slim6, ROM for the Samsung Galaxy S III I9300
Contributors
limjh16, Trafalgar Square, SlimRom Team
Source Code: https://github.com/SlimRoms
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: SlimRom
Version Information
Status: Alpha
Created 2016-01-25
Last Updated 2016-07-17
Screenshots
{
"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"
}
Bugs, Workarounds, etc.
WORKING:
RIL
Data (3G tested only, LTE can't test)
Camera
Xposed
Layers 4.0 except Frameworks and SystemUI overlays
NOT TESTED
Bluetooth
GPS
NOT WORKING:
Layers Frameworks and SystemUI Overlay
You tell me?
THE DRILL: FOLLOW OR DON'T POST
Downloads (ROM, SU and GApps)
ROM mirror links:
AFH
Google Drive
LP:
Look here for updated
Google Drive
XDA Download
Mega
Android File Host
Working GApps:
OpenGApps
Reccomended:
SuperSU
GravityBox for Customisation
Credits
Credits roll...
1. Thanks to whoever who helped in making SlimRoms Source possible, aka slim team and whoever they kanged from
2. @Yank555 @Trafalgar Square @rodman01 @p.a.n @aaz03 @Gokulbalram Yay MM for Slim is finally here
3. All you great people testing the ROM
Changelog to be uploaded #soon
Personal Updates
[17th Jul] MM out. Old LP stuff here:
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.
*/
Credits roll...
Big thanks to @Trafalgar Square, @spezi77, and many others who helped me in the "Source to End" forum namely:
@nitin.chobhe
@KeTuRr74
More big thanks to @Trafalgar-Square for inspiring me
Big thanks to xda university creators and @jackeagle for his guide
Big thanks to SlimRoms team (of course) for providing the source code. I merely took the source code and followed some guides, all credit goes to their team.
Big thanks to NamelessRom for providing the hardware and Kernel and bla bla sources.
Big thanks to CrazyWeasel for providing vendor trees
Big thanks to winxuser for providing device trees.
And lastly thank you in advance for all those who test this ROM.
POST LIST:
2nd post: Screenshots
3rd post: Known Bugs and workarounds (if any)
4th post: Downloads and recommended GApps
5th post: Legit changelog between release versions
6th post: Updates, aka announcements.
In the future it is going to be stripped, I am going to follow these stuff: 1. and 2.
Sources:
Local Manifest
You can actually determine everything from there, I did not cherry-pick or kang any extra features.
Feature list can somehow or another be found here or here
[27th Jan] Future planned stuff:
uber kernel/TC and -o flag optimisation
[26th Jan] Mega and XDA Download links updated!
[26th Jan] @aaz03 since I feel this ROM is essentially stable, can I ask that you advice me on how to optimize it?
[25th Jan]
I will soon be moving this OP to changelog and include a legit OP here since I uploaded to G Drive already. Seems like I do not need to ask for permission, but I need to credit people? Please correct me if I'm wrong, but I'll be going ahead and crediting people while uploading my ROM.
----EDIT ABOVE----
So I didn't need to fix my graphics driver i used terminal lol but anyways I'm uploading my ROM to google drive, theres 2 zips ill upload both idk which works. Everyone please still help on who to look for permission to post ROM, I don't want to post ROM w/o permission. I also need testers.
----EDIT ABOVE----
SlimRom LP5.1.1 HELP NEEDED
So, I finished compiling the ROM (Proof in 2nd post or whatever) but as this is my first ROM I need some help.
1. Who do I contact for permission on posting the ROM?
2. As you can see the terminal looks wierd, that's because XServer and/or MDM died, I'll fix that myself since problem is due to VM config but for now I can't post the ROM since I can't access my files from terminal and move it to my native OS since I suck. (ANYONE CAN HELP WITH TERMINAL COMMANDS???)
3. What do I do for testing? I need my phone for daily driver, and I have no other backup/fallback phone. If I get stuck in bootloop I know how to recover but I do not know how to recover from bricks easily.
4. If there are any bugs at all I will not know how to solve it so I beg all devs looking at this page to like bookmark it or smth and help me, especially @aaz03 since you built slim for our phone before.
For the users who are waiting to test this ROM pls dont post lol, I am also very anxious to test.
I am sorry for this wierd ROM DevDB post but I assure you guys I won't stop attempting to make this work until I get pumped with too much schoolwork/MM is stable.
Thanks for your time in reading this post!
I see you managed certain things on your own. But anyway, I'd like to help as much as possible. If you want an "OK" to post the build I recommend to ask o their official g+ community https://plus.google.com/communities/104509876514579429216 or you take some inspiration from the SlimRom Builders collection http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778.
Just make sure that you give credit to people who have helped you and/or you borrowed stuff from. If you cherrypicked or "kanged" certain things ask for permission to use it and give credit as well.
As long as you can boot into download mode chances for bricking the device are small. I'm just talking about software bricks of course. Keep a stock ROM on your hard drive in case something is messed up and you cannot get your phone booting. If you're using adb make sure it works correctly first.
If you need anything I'm sure other peeps will help you of course. As for testing purposes share the link first in private with a handful of people who know what they are doing before you release it in public. The key features should definitely work (or as far as possible), adding features is something for the future when the ROM has less or no bugs. Adding features can break some things within the ROM.
maultasche said:
I see you managed certain things on your own. But anyway, I'd like to help as much as possible. If you want an "OK" to post the build I recommend to ask o their official g+ community https://plus.google.com/communities/104509876514579429216 or you take some inspiration from the SlimRom Builders collection http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778.
Just make sure that you give credit to people who have helped you and/or you borrowed stuff from. If you cherrypicked or "kanged" certain things ask for permission to use it and give credit as well.
As long as you can boot into download mode chances for bricking the device are small. I'm just talking about software bricks of course. Keep a stock ROM on your hard drive in case something is messed up and you cannot get your phone booting. If you're using adb make sure it works correctly first.
If you need anything I'm sure other peeps will help you of course. As for testing purposes share the link first in private with a handful of people who know what they are doing before you release it in public. The key features should definitely work (or as far as possible), adding features is something for the future when the ROM has less or no bugs. Adding features can break some things within the ROM.
Click to expand...
Click to collapse
Alright, thank you for that advice. I do not have time today at all, but I'll put like a warning saying do not test if u do not know what u r doing in red. Meanwhile I'll credit ppl.
limjh16 said:
slim_i9305-ota-8806e3adf9.zip
Click to expand...
Click to collapse
No need for this. Don't know for what this is.
It boots, will attack screenshots later after I find out which gapps works (tk gaapps doesn't work)
limjh16 said:
It boots, will attack screenshots later after I find out which gapps works (tk gaapps doesn't work)
Click to expand...
Click to collapse
Slim GApps
Update: Most major features are working, I think this ROM should be categorized as stable...? I'll leave it as beta first.
good job...this was my favorite until it stopped at beta 0.9.
Installed and working very good.
is RRO Layers Theme supported?
Yes it's supported.
So, can anyone give an opinion on how the battery life? Random reboot or FC?
And by the way, is it okay to flash agni kernel?
Mrxyzl said:
So, can anyone give an opinion on how the battery life? Random reboot or FC?
And by the way, is it okay to flash agni kernel?
Click to expand...
Click to collapse
No random reboot or FC, As for agni kernel try yourself should be okay.
Battery life? Well, its normal as with any other ROM. Please don't complain of bad battery on first day, because its like that for every ROM.
Still testing...i have problems with Layers , the themes seem to have wrong colors....and i have tried many.
Can you please look into it.
Agni kernel 5.9.7 smdk work fine.
The rom is very fast ad battery life is ok.No FC or random reboots.
hexisg said:
Still testing...i have problems with Layers , the themes seem to have wrong colors....and i have tried many.
Can you please look into it.
Agni kernel 5.9.7 smdk work fine.
The rom is very fast ad battery life is ok.No FC or random reboots.
Click to expand...
Click to collapse
thanks but next time can you post in bug report section? I want to keep this clean. Anyways I haven't tested layers because I don't use it and idk how to test, could you provide a logcat and I ask maybe @Trafalgar Square to look into it?
TWRP restarts when i try to flash this ... any help plz?
twrp 2.8.7.0
Aminewolf said:
TWRP restarts when i try to flash this ... any help plz?
twrp 2.8.7.0
Click to expand...
Click to collapse
Where did you install from? The ones from twrp.me are buggy or smth. Try sdt barbarossa homebuild here
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
This ROM compatible with L version in both S7580 & S7582
DO NOT SUBMIT BUG REPORT.
Press Thanks If you like my work
This (28thNov build) is the last update of this ROM. This ROM will no longer been maintained.
{
"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"
}
About Us:Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days -- it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and gained contributors in the process. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew further with experience and learned a lot more along the way.
It has been an awesome learning experience and it's still not over! We are still learning, striving to grow each day, and continuing to move forward. Lastly, weDO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc. We will never ask for a dime. All that we do ask is that you have patience, search for answers prior to posting, read, and try to enjoy the process with us!!
Note: This ROM is based on AOSP not CyanogenMod,in CyanogenMod optimizing apps happens at first boot shows up after bootanimation but in aosp ROM or some AOSp based ROMs it's hidden, that means apps will optimize during boot(animation),so if booting takes time don't pull out battery thinking phone is stucked at boot. Wait for 20mins or average time ,takes for optimizing apps(with gapps)
29th Nov:-
-------------------------------------------------
S7580:
Download ROM: Click Here
-------------------------------------------------
S7582:
Download ROM: Click Here
OLD builds:-
More? : Search on my AFH
S7582:
18th June : Click Here
16th June: Click Here
17th June:
Click Here
S7580:
18th June: Click Here
-Installation guide:
*Download ROM
*Wipe System, Data,Cache, Dalvik Cache
*Install ROM
*Install G-Apps
*Reboot
FAQs:-
-----Read before Installing ROM-----
Q1. Do i need to install G-Apps?
Ans:- Use A-GApps
Q.2 Can i install XXX GApps?
Ans:- Yes, use A-GApps
Q3. How much ROM installation take?
Ans :- Around 15-20mins. So don't be panic and be patience.
Working things & Fixed bugs:
- Everything except listed in Bugs
- AV(video &audio playback)
- Screen Record
- Preferred network setting
Issues & Bugs:-
- None, same as of CM-13.0
Report if you find any.
Changelog:-
Code:
29th Nov:
- Fix blank screenshot
28th Nov:
- Random Reboots? Permanently fixed
- F2FS supported
- Upstreamed to R74
- And many more platform changes from DU Team.
20th June:
-Fixed 3G only selection bug
-Fixed Hotspot not starting
18th June:
-Added 3G/2G Preferred Option
17th June:
-Added 2G/3G only option
16th June:
-Initial Release
CLEAN FLASH:
-Before install ROM package if you're currently use STOCK ROM/CM11, make sure to wipe data/factory reset; if possible then do a internal sd format first, else you'll get error.
+ HOW?
- When entering TWRP Recovery, it will ask you if you want to keep system partition Read only, check the box "Never show this screen during boot again"and swipe the lock bar, else you can't modify system partition in TWRP like install ROM, root...
Credit and Thanks: (ROM DEVELOPMENT TEAM)
-JMZ Software
-Baby Jesus
-Code Aurora Forum
-Omni ROM
-Android Open Kang Project (AOKP)
-Android Ice Cold Project (AICP)
-XDA-Developers
-SlimROMs
-Preludedrew
-Max Weninger
-Team Black Out
-CyanogenMod
-Pure Nexus Project
(Team for bringing to Kyleproxx)
-Sandpox
-zim555
-pawitp
-no_name( for porting ROM)
For developer:
Device Tree (GT-S7580): Click Here
Device Tree (GT-S7582): Click Here
Kernel Source: Click Here
Vendor Blobs: Click Here
Compatibility Patches:Click Here
XDA: DevDB Information
Dirty Unicorns(DU) by no_name(a.k.a Ishant Vivek), ROM for the Samsung Galaxy S Duos 2/Trend Duos
Contributors
sandpox,ishantvivek,zim555,pawitp
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information:
Status: STABLE
Current Stable Version:10.7
Stable Release Date: 29.11.2016
Screenshots:
Planned features to be added in next build:
*MotoDoze
Daily Builds:
*Not started now
i flashed the rom successully with opengapps6.0_pico..
the problem is "unfortunately aosp keyboard stop"
TWRP Recovery v3.0.0 for Samsung GT-S7582
http://www.mediafire.com/download/938c3d5o1brp6pz/TWRP_v3.0.0_GT-S7582.tar.md5
Dirty Unicorns ROM review on GT-S7580:
The ROM is OK
GT-S7580-specific bugs:
* I can't connect to a network operator
General bugs:
* Random reboots (more frequent than on CM 13) (@no_name, could you try using the ROM actively with GApps?)
Sent from my GT-S7580 using Tapatalk
kimmoth26 said:
i flashed the rom successully with opengapps6.0_pico..
the problem is "unfortunately aosp keyboard stop"
Click to expand...
Click to collapse
Don't flash open gapps, as it changes keyboard lib causing fc. Use A-Gapps
DodoGTA said:
Dirty Unicorns ROM review on GT-S7580:
The ROM is OK
GT-S7580-specific bugs:
* I can't connect to a network operator
General bugs:
* Random reboots (more frequent than on CM 13)
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
Bug 1 is because you flashed 7582 on 7580, or maybe something else, whatever... No issue such like that on 7582 ,will release for 7580 soon.
Ignore bug 2 , firstly wait for a 7580 build, second "more frequent"? Nah during one full day of test i don't even have one random reboot,so it's just you @present.
@all new build released , added option for 3g only and 2g only
Can you add FM Radio in this build next up date please ? ?
And , Trying Rom now ..
Taxilion said:
Can you add FM Radio in this build next up date please ? ��
And , Trying Rom now ..
Click to expand...
Click to collapse
Common FM-Radio app isn't working,so no.
BTW wait,i just being reported messaging app is missing so wait ,new build is coming with messaging app.
Edit: Links updated of new build,with messaging app included
Hotspot Not Working
I have to report a bug that hotspot is not working in my gt s7582....Is anyone having the same issue please let me know
---------- Post added at 03:20 PM ---------- Previous post was at 03:10 PM ----------
G-Apps without keyboard FC ....I have tested it
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
Mms apk
If someone is not having messaging app after rom installation... Like me you can use this apk
a very good rom indeed, lighter and faster and better than cm13
will flashing that audio_hal zip solve the sound libs issue in this build too?
amit kattal said:
a very good rom indeed, lighter and faster and better than cm13
will flashing that audio_hal zip solve the sound libs issue in this build too?
Click to expand...
Click to collapse
Yes
Sent from my GT-S7580 using Tapatalk
amit kattal said:
a very good rom indeed, lighter and faster and better than cm13
will flashing that audio_hal zip solve the sound libs issue in this build too?
Click to expand...
Click to collapse
It should work. Because this zip has binaries from ace 3's stock rom and they can't be edited. And this rom has binaries from ace style's stock. They haven't edited.
@no_name ROM is fast and smooth.. but i have frequent reboot..
can you please add "3G and 2G preferred" in network selection
DodoGTA said:
Dirty Unicorns ROM review on GT-S7580:
* Random reboots (more frequent than on CM 13) (@no_name, could you try using the ROM actively with GApps?)
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
yes,i used A-Gapps, don't have idea of other,but opengapps will create some issues, and BTW provide log(logcat+kmsg) just at the time of reboot,so that i could encounter what's making the ROM to reboot, though i haven't faced any reboot.
amit kattal said:
a very good rom indeed, lighter and faster and better than cm13
will flashing that audio_hal zip solve the sound libs issue in this build too?
Click to expand...
Click to collapse
I guess yes you can,but sound libs comes with kernel (boot.img) ,so if you are going to flash that, which has boot.img of cm13(maybe), may cause unknown issues,because of different ramdisk(modified ramdisk). Rest is yours choice.
kimmoth26 said:
@no_name ROM is fast and smooth.. but i have frequent reboot..
can you please add "3G and 2G preferred" in network selection
Click to expand...
Click to collapse
I won't say anything about random reboots, as till now, no idea what's creating this issue. But if you modify things over this ROM like flashed old audio hal package or something else,i won't take guarantee of it. Reason is already explained ^^ .
I am working on 3g and 2g preferred options. Maybe added in next build.
no_name said:
Don't flash open gapps, as it changes keyboard lib causing fc. Use A-Gapps
Bug 1 is because you flashed 7582 on 7580, or maybe something else, whatever... No issue such like that on 7582 ,will release for 7580 soon.
Ignore bug 2 , firstly wait for a 7580 build, second "more frequent"? Nah during one full day of test i don't even have one random reboot,so it's just you @present.
@all new build released , added option for 3g only and 2g only
Click to expand...
Click to collapse
UPDATE: I solved "I can't connect to a network operator" bug myself ???
Sent from my GT-S7580 using Tapatalk
ss plz?
dude no hotspot. btw the rom is really awesome better than cm13 in many ways. please fix hotspot i rely too much on it. thank you and no_name u rock.
no_name said:
yes,i used A-Gapps, don't have idea of other,but opengapps will create some issues, and BTW provide log(logcat+kmsg) just at the time of reboot,so that i could encounter what's making the ROM to reboot, though i haven't faced any reboot.
I guess yes you can,but sound libs comes with kernel (boot.img) ,so if you are going to flash that, which has boot.img of cm13(maybe), may cause unknown issues,because of different ramdisk(modified ramdisk). Rest is yours choice.
I won't say anything about random reboots, as till now, no idea what's creating this issue. But if you modify things over this ROM like flashed old audio hal package or something else,i won't take guarantee of it. Reason is already explained ^^ .
I am working on 3g and 2g preferred options. Maybe added in next build.
Click to expand...
Click to collapse
Here's the logcat and kmsg:
http://cloud.tapatalk.com/s/57650ecda883d/dujun17reboots.txt
http://cloud.tapatalk.com/s/57650ef534a9c/dujun17kmsg.txt
(This patch should fix issue that's mentioned in the logcat: https://github.com/pawitp/android_d...osp-6.0/PATCHES/frameworks_native.patch#L1179)
Sent from my GT-S7580 using Tapatalk