[ROM][OFFICIAL][Lollipop 5.0.2][LS970-GEESPR] PAC-ROM LP Beta-1 - Sprint LG Optimus G

{
"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"
}
PAC-ROM is built with our own tweaks and options, including picks and features from the best ROMs out there!
Why choose among ROMs, when you have All-in-One !!
* 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 *​
* Download the latest version *
* Reboot to recovery *
* Flash the ROM *
* Wipe both dalvik cache and cache *
* Reboot your phone *
* Enjoy the latest version of PAC-ROM *​
* Submit a bug report *
* Submit a patch *​
* None for now *​
* PAC-ROM Downloads *
* GApps *​
* PAC-ROM Team *
* Cyanogen Team *
* AOKP Team *
* DirtyUnicorns *
* SlimRoms *
* Vanir *
* Omnirom *
* 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! *​
Support us with these banners:
Help with server costs
​

PAC-man ROM for the LG Optimus G - Devices and threads:
Sprint ls970/geespr: Here
Canadian e973/geeb: [ROM][OFFICIAL][KitKat 4.4.4][E973-GEEB] PAC-man 4.4.4.RC-2
International e975/gee: [ROM][OFFICIAL][KitKat 4.4.4][E975-GEE] PAC-man 4.4.4.RC-2

Thanks a bunch!
I'm a bit confused.
The download link you provided takes me to PacMan files basketball files>LS970
I do not see this particular build (PAC-man 4.4.4.RC-1) in any of this folders.
However I do see a similar build label in the p970 folder (release).
Help me sort this out.

mesacarvin said:
Thanks a bunch!
I'm a bit confused.
The download link you provided takes me to PacMan files basketball files>LS970
I do not see this particular build (PAC-man 4.4.4.RC-1) in any of this folders.
However I do see a similar build label in the p970 folder (release).
Help me sort this out.
Click to expand...
Click to collapse
Yeah, sorry about that. I'm still in the process of taking over as this device's maintainer. Once I'm done, the ls970 will be added back as a supported device and you should expect to see fresh nightlies rolling out soon.

I'm happy to say that I'll be your new maintainer. The ls970 is once more a supported device and as such, will be getting nightlies rolled out soon. I'll be around for you guys if you need help or have questions. Looking forward to getting this stale August 24th build off my device, and I know you guys are too.

Welcome and thanks for taking this awesome ROM to maintain it. :good:
As you are the maintainer now, I'll suppose that is fine tho post feedback about the ROM to you...
I've been running that last old build (08/24) since a few weeks. only two things to report:
1- having delay waking up the device when it self goes off due the ''screen off time'' but not if I lock it through the button.
2- bsod sometimes, with the built in kernel and with different custom kernels too, that's why I'm guessing is ROM related.

FcoEnrique said:
I've been running that last old build (08/24) since a few weeks. only two things to report:
1- having delay waking up the device when it self goes off due the ''screen off time'' but not if I lock it through the button.
2- bsod sometimes, with the built in kernel and with different custom kernels too, that's why I'm guessing is ROM related.
Click to expand...
Click to collapse
1) I can confirm this problem. It cropped up in the last couple builds. It may be temporary, so let's wait and see if it occurs in the latest nightlies once they roll out.
2) BSOD as in a blue screen saying something like "subsystem crash"? I've gotten those a few times too. They're just the weirdest things to see on an Android system. And they occur for me at the oddest times, like when the phone's just sitting there doing nothing. I haven't gotten any lately though. This is another case of waiting and seeing if the problem has been fixed in the latest nightlies.
As for the nightlies, you can see here that I've added the ls970 back into nightly.xml, so our Jenkins build bots will be getting around to making a build for the device soon. By the way, if you'd like to volunteer one or more of your machines as a build bot and help speed up our nightly build process, by all means view this thread. Thanks.

rectec said:
1) I can confirm this problem. It cropped up in the last couple builds. It may be temporary, so let's wait and see if it occurs in the latest nightlies once they roll out.
2) BSOD as in a blue screen saying something like "subsystem crash"? I've gotten those a few times too. They're just the weirdest things to see on an Android system. And they occur for me at the oddest times, like when the phone's just sitting there doing nothing. I haven't gotten any lately though. This is another case of waiting and seeing if the problem has been fixed in the latest nightlies.
As for the nightlies, you can see here that I've added the ls970 back into nightly.xml, so our Jenkins build bots will be getting around to making a build for the device soon. By the way, if you'd like to volunteer one or more of your machines as a build bot and help speed up our nightly build process, by all means view this thread. Thanks.
Click to expand...
Click to collapse
Happy to know that our device is back in business.
By bosd or "black screen of death", I mean that when I try to unlock/wake up the device it doesn't, keys lights up but the screen stays off.
I'll would love to help with the building process, I even would love tho be able to build some ROMs but my machine doesn't have the requirements :/

FcoEnrique said:
Happy to know that our device is back in business.
Click to expand...
Click to collapse
You and me both
FcoEnrique said:
By bosd or "black screen of death", I mean that when I try to unlock/wake up the device it doesn't, keys lights up but the screen stays off.
Click to expand...
Click to collapse
Oh. Yeah I've had that problem too. It's a pain in the ass but at least you can hold the power button down for a little bit to hard restart the phone. But we'll have to see if we have this problem with the latest nightlies as well, because it may have already been fixed.
FcoEnrique said:
I'll would love to help with the building process, I even would love tho be able to build some ROMs but my machine doesn't have the requirements :/
Click to expand...
Click to collapse
No problem. They're pretty demanding requirements and rightfully so; building a single nightly can take hours. That was just a general solicitation in case anyone who can meet the requirements happens to stumble upon my post. But if you want to contribute a build bot, next time you're in the market for PC hardware, I'd recommend getting one of those cheap AMD 8 core CPUs, since building is a heavily multi-threaded process. Thanks for your interest

Some goodies in the last build like stop and resume downloads, good to have new builds again. :good:
so far the only bug in my end is still present, having that delay when unlocking after it self turn off the screen.
Edit: I think that I've found another one,something wrong with YouTube.

FcoEnrique said:
Some goodies in the last build like stop and resume downloads, good to have new builds again. :good:
so far the only bug in my end is still present, having that delay when unlocking after it self turn off the screen.
Edit: I think that I've found another one,something wrong with YouTube.
Click to expand...
Click to collapse
Yeah I still have the delay too, even though I started with a fresh install and just restored my apps with Titanium. I'm going to test these bugs on a true fresh install, and if they're there I'll ask around about it.
Edit: Yep. Just as I thought, the (or at least a) cause of the screen on delay is from disabling the lockscreen from quick settings. As soon as I re-enable the lockscreen, the delay goes away for me. Can you confirm that this happens with your phone too? I've attached a couple images of my quick settings to illustrate what I mean.
As for the YouTube problem, before I've noticed occasional artifacting/video corruption all over videos, which goes away when I fiddle with the seekbar. With the latest gapps' YouTube I just see a small band of artifacting at the bottom of the screen that won't go away. When I update to the latest YouTube through the Play Store, I see the same all-over artifacting that I saw before (https://puu.sh/bHxBq/a65975f799.png), only it doesn't go away. I don't see anyone complaining about it on the Play Store entry, so I'll assume it's specific to us.
I'll ask around about these problems. For now I'll note them in the "Other info" section of the OP. I'll keep you guys informed.

rectec said:
Yeah I still have the delay too, even though I started with a fresh install and just restored my apps with Titanium. I'm going to test these bugs on a true fresh install, and if they're there I'll ask around about it.
Edit: Yep. Just as I thought, the (or at least a) cause of the screen on delay is from disabling the lockscreen from quick settings. As soon as I re-enable the lockscreen, the delay goes away for me. Can you confirm that this happens with your phone too? I've attached a couple images of my quick settings to illustrate what I mean.
As for the YouTube problem, before I've noticed occasional artifacting/video corruption all over videos, which goes away when I fiddle with the seekbar. With the latest gapps' YouTube I just see a small band of artifacting at the bottom of the screen that won't go away. When I update to the latest YouTube through the Play Store, I see the same all-over artifacting that I saw before (https://puu.sh/bHxBq/a65975f799.png), only it doesn't go away. I don't see anyone complaining about it on the Play Store entry, so I'll assume it's specific to us.
I'll ask around about these problems. For now I'll note them in the "Other info" section of the OP. I'll keep you guys informed.
Click to expand...
Click to collapse
Yes that's exactly what is going on with youtube.
about enabling/disabling lockscreen in quick settings, I'll check that, as I dont have that toogle added to my QS screen.
I'll let you know if that solves it.
EDIT:
Nope that's not the problem, I have it enabled.

Hey guys. Anyone else having issues with NFC? I'm running on the 9/20 nightly and I can't get it to come one. I check the NFC box and it just fades but it won't come on.
Sent from my LG-LS970 using XDA Free mobile app

ibleo02 said:
Hey guys. Anyone else having issues with NFC? I'm running on the 9/20 nightly and I can't get it to come one. I check the NFC box and it just fades but it won't come on.
View attachment 2946904
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
yup, happened to me, but after a reboot it works.
the annoying bug that is still present for me is the delay when waking up the device...
i think I'll try another ROM to see if it's only PAC.

Sorry for the delay. XDA decided to not email me about thread replies.
So I've been told the delay is normal behavior when you've disabled the lockscreen through quick settings, since it's bypassing the lockscreen. I wish I could give you a better explanation. It's not bug, just an unintended side effect. Hopefully we'll implement a better method in the future that doesn't have a delay.
Since you still have the delay even when the lockscreen isn't disabled, I'd do a nandroid backup, wipe, then do a fresh install of the ROM. Then see if the issue appears. If it doesn't, then it could be something wrong your current install. If it does still appear, then I don't know what to tell you lol. All I can say is that I only have a screen on delay when I have the lockscreen disabled - both in a fresh install and a non-fresh install - and that it's apparently normal behavior.
As for the YouTube corruption, I'm not having that problem on my current install. I'd like to see if more people have this problem before we go on a full on investigation.

rectec said:
Sorry for the delay. XDA decided to not email me about thread replies.
So I've been told the delay is normal behavior when you've disabled the lockscreen through quick settings, since it's bypassing the lockscreen. I wish I could give you a better explanation. It's not bug, just an unintended side effect. Hopefully we'll implement a better method in the future that doesn't have a delay.
Since you still have the delay even when the lockscreen isn't disabled, I'd do a nandroid backup, wipe, then do a fresh install of the ROM. Then see if the issue appears. If it doesn't, then it could be something wrong your current install. If it does still appear, then I don't know what to tell you lol. All I can say is that I only have a screen on delay when I have the lockscreen disabled - both in a fresh install and a non-fresh install - and that it's apparently normal behavior.
As for the YouTube corruption, I'm not having that problem on my current install. I'd like to see if more people have this problem before we go on a full on investigation.
Click to expand...
Click to collapse
Ups I forgot to try youtube in the last build...
as for the delay, well, I don't know what it could be, I wiped my phone completely even sd card (for accident ) and the delay persist

FcoEnrique said:
Ups I forgot to try youtube in the last build...
as for the delay, well, I don't know what it could be, I wiped my phone completely even sd card (for accident ) and the delay persist
Click to expand...
Click to collapse
I'm guessing it doesn't occur in other ROMs?

rectec said:
I'm guessing it doesn't occur in other ROMs?
Click to expand...
Click to collapse
Nope, I'm in AOKP right now and it doesn't happens, neither in Carbon before PAC.

FcoEnrique said:
Nope, I'm in AOKP right now and it doesn't happens, neither in Carbon before PAC.
Click to expand...
Click to collapse
Out of curiosity, do you guys happen to be using see-through on the lockscreen. I know that creates major delays for me when turning the screen on

goldflame09 said:
Out of curiosity, do you guys happen to be using see-through on the lockscreen. I know that creates major delays for me when turning the screen on
Click to expand...
Click to collapse
Nope... even after a clean flash.
it happens to me right away :/

Related

[ROM][GT-N8000][4.1.1] CyanogenMod 10 Nightlies

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
PREVIEW DISCLAIMER:
This is a PREVIEW : CyanogenMod 10 is nowhere near ready to be used as a daily driver (lots of features still have to be merged), and same is the device support. CHECK THE KNOWN ISSUES LIST BEFORE THINKING ABOUT POSTING.
IF YOU ARE *****ING WITH "When this will be fixed!!!!?????" THEN I'LL JUST CLOSE THE THREAD AND YOU'LL HAVE TO WAIT EVEN MORE.
DISCUSSION THREAD: http://forum.xda-developers.com/showthread.php?p=30744835
IF YOU WANT TO SAY THANKS, HELLO, ASK ABOUT YOUR KERNEL, ISSUES WITHOUT LOG, OR HAVE SEX, THAT'S THE THREAD TO USE!
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. You can also view the Changelog for a full list of changes & features.
KNOWN ISSUES
Click to expand...
Click to collapse
- FMradio, heh!
- Camera is unstable, though taking pics should work
- Wi-Fi tethering is semi-broken
- Some audio issues #blamecodeworkx
TIPS & TRICKS
Click to expand...
Click to collapse
- Camera is now part of Gallery, that's why you might have two (because of Gapps)
- If you have no Camera icon in app drawer, remember you have a lockscreen
- If one camera app doesn't work, try the other one (if you have two)
- If it worked once then didn't work anymore, reboot
HOW TO INSTALL
Click to expand...
Click to collapse
- Download the zip
- Download Gapps
- Install the update zip from recovery
- Install gapps from recovery
- Wipe/Factory reset
- Reboot
SCREENSHOTS
Click to expand...
Click to collapse
{
"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"
}
SUPPORT
Click to expand...
Click to collapse
If you're encountering a bug that isn't listed above, make sure to attach a logcat with your report. If you don't know how to do it, then refrain from posting. Once again, if this thread is becoming a hassle for me, then I'll close it right away. And remember that CM10 IS A WORK IN PROGRESS. No complaints for missing features either.
You can check out #teamhacksung-support on Freenode for live support - but we won't hesitate to ban you if you're *****ing.
Also, a donation on the www.teamhacksung.org webpage is really appreciated. Thanks!
reserved for entropy's house of n8013
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
mitchellvii said:
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
It is working, yes
mitchellvii said:
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Entropy512 said:
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Click to expand...
Click to collapse
Thank you so much for your hard work! Looking forward to a stable release for my 8013 .
Entropy512 said:
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Click to expand...
Click to collapse
Does this mean the built in s-pen apps won't work under cm10? Of course that would also mean no split screen I guess. Sorry if these questions seem dense but its all bit confusing.
Sent from my GT-N8013 using Tapatalk 2
Thanks, will give it a try.
espenfjo said:
PREVIEW DISCLAIMER:
This is a PREVIEW : CyanogenMod 10 is nowhere near ready to be used as a daily driver (lots of features still have to be merged), and same is the device support. CHECK THE KNOWN ISSUES LIST BEFORE THINKING ABOUT POSTING.
IF YOU ARE *****ING WITH "When this will be fixed!!!!?????" THEN I'LL JUST CLOSE THE THREAD AND YOU'LL HAVE TO WAIT EVEN MORE.
DISCUSSION THREAD: http://forum.xda-developers.com/showthread.php?p=30744835
IF YOU WANT TO SAY THANKS, HELLO, ASK ABOUT YOUR KERNEL, ISSUES WITHOUT LOG, OR HAVE SEX, THAT'S THE THREAD TO USE!
If you're encountering a bug that isn't listed above, make sure to attach a logcat with your report. If you don't know how to do it, then refrain from posting. Once again, if this thread is becoming a hassle for me, then I'll close it right away. And remember that CM10 IS A WORK IN PROGRESS. No complaints for missing features either.
You can check out #teamhacksung-support on Freenode for live support - but we won't hesitate to ban you if you're *****ing.
Also, a donation on the www.teamhacksung.org webpage is really appreciated. Thanks!
Click to expand...
Click to collapse
Just wanted to point out that most of the replies so far should go in the discussion thread, not this one (this post is off topic too). This thread should be reserved for bug reports with proper logs and other information.
But just to clarify for those new to custom ROMs, CyanogenMod is a ROM that is based off of google's Android Open Source Project. Furthermore, Samsung's stock ROMs include a lot of proprietary parts for which source is not available. Any customizations from Samsung's stock ROMs that aren't in AOSP will never be found in AOSP ROMs (for the most part - I think at one point a talented smali hacker got the Touchwiz camera to work on AOSP ROMs on the Galaxy S).
Thus, specifically for the Galaxy Note 10.1, you will not have the split screen multitasking, floating apps on the navbar, S Note, or any of the other Samsung apps. Most of them have third party equivalents you can find on the market anyway. Split screen multitasking is not something you can really recreate in an app, but there was at one point a project (Onskreen Cornerstone) to build something similar for Android, and Cyanogen at the time expressed interest in including something like it in CyanogenMod. However, that was March of last year and nothing is there yet so who knows if it's still on the table (maybe our friendly neighborhood maintainers can tell us more).
You also won't be able to use any apps that specifically use the S Pen SDK, but apps that use the built in ICS Pen APIs will work (and I don't know why anyone would use the S Pen SDK on ICS, even if there aren't any other active digitizer ICS devices now, there surely will be in the future and limiting yourself to Samsung devices for little benefit seems pointless to me).
Hi @All,
Phonecalls and Textmessage positive too?
ill it run on the 80013?
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Go here
DISCUSSION THREAD: http://forum.xda-developers.com/show...php?p=30744835
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Have you got it running? the thread link doesnt work. I get a status 7 error
Read the OP !!!
Discussion thread link: http://forum.xda-developers.com/showthread.php?t=1854841
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Works for me. It just has a little empty cell signal thing by the clock, but it doesn't seem to have any problems
Sent from my DROID4 using Tapatalk 2
now we have Official Nighties for the 8013 !!! http://get.cm/?device=n8013
I understood that this is the thread to post bugs with logcats in. So here goes.
There is this one network to which I can not connect. It tries and fails. The trying and failing goes on indefinitely. There are other networks to which it connects just fine, but this one keeps failing.
Device: N8010
CM Version: cm-10-20120930-EXPERIMENTAL-n8013-ENTROPY (The first nightly)
Logcat: http://pastebin.com/WaAhji6k
Most notable error from logcat:
E/WifiHW ( 2467): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": No such file or directory
Click to expand...
Click to collapse
It might be a certain security method that is missing, or that the connection socket is somehow closed before it's supposed to.
Router data:
Brand: ZyXEL
model: P-2602HW-D1A
SSID: Smient24Wifi
Security: WPA2-Personal
Encryption: AES
Notes:
- The network used to work fine on stock rom
- it was also broken on build cm-10-20120924-UNOFFICIAL-n8013
- I turned on the logcat, turned on wifi, let it try about 7 times, turned wifi off, turned logcat off.
- The logcat will probably report a poor signal strength. The signal strength is low when it's trying to connect, and jumps to the real value in between connections. This behavior remains exactly the same when I hold my tablet right next to the antenna of the router. I don't know how much this is related to the reported bug.
- Until this bug is fixed, I can work around the issue with connectify, so I won't be whining about when the bug is fixed
Thanks!
This morning's nightly for n8013 bombed, no clue why. If it bombs again I'll look into it further, assuming it was a fluke for now.
Entropy512 said:
This morning's nightly for n8013 bombed, no clue why. If it bombs again I'll look into it further, assuming it was a fluke for now.
Click to expand...
Click to collapse
how did it bomb? as in its not safe to install? or has some issue?
jmwils3 said:
how did it bomb? as in its not safe to install? or has some issue?
Click to expand...
Click to collapse
More a question for the other thread.. but wth.. It didnt build, so the one that "bombed" doesnt exist
Newest nightly from get.cm is safe and ready.

[ROM] Task650 AOKP (Jellybean 4.3)(10.25.2013) (TMO)

I wanted to bring you guys some AOKP releases with other mods and code changes to the T-Mobile SGS IV.​
{
"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"
}
​
A Big Thanks Goes to the AOKP Team & CyanogenMod Team. Without their source this wouldn't be possible. Go thank them, tweet them, and donate to them. Also a HUGE thanks to mrgoat for the hosting!!!​If you decide that you are not going to read all of the information provided in this OP or the FAQ, then GTFO. There is a lot of useful information in either of the two that will really help you and this thread out.​
PLEASE STICK TO DEVELOPMENT HERE!!! TAKE ALL QUESTIONS YOU MAY HAVE TO THE Q & A THREAD!!!​
READ THE Q & A
READ THE FAQ HERE
​
RULES​1.) You must read the FAQ & Installation Instructions before installing this ROM or posting in this thread. It has so much useful information that I can guarantee if you actually read though it, you won't have many unrelated questions to post in this thread.
2.) If you don't like how I run this thread. Leave. You do not have to be here and you are not forced to read it. You are doing so on your own free will.
3.) If you don't like something that someone has to say. DO NOT RESPOND!!! It's that simple. Your personal opinions DO NOT BELONG HERE! Please leave them out of this thread. I will do the responding and so will the Moderators.
4.)This is not a "captain save a hoe" thread. It's not your job to stand up or fight for what you believe in here. This is a development thread! Leave it at that!
5.) Search before posting here. You are most likely not the only one to have the question/issue.
6.) Have fun in this thread. I don't mind if we have some fun, joke around, or whatever. As long as it's fun.
7.) If you're going to post here, keep it to this ROM and this ROM only (unless its fun as mentioned above). It is useless to compare to Stock ROMs, CM10 ROMS, ect...
Code:
[B][U][I]AOKP 4.3 Jellybean 10.25.2013[/I][/U][/B]
[B]Updated Kernel
Updated to Android 4.3.1 (JLS36I)
Added Multi-Window (Open up recents with Home button and longpress apps to add to split-window) [B][COLOR="Red"]This is a WIP!!! No bug reports on this!!![/COLOR][/B]
Added Random Color Tile option (ROM Control/Toggles)
Moved Dark UI switch to ROM Control (ROM Control/General UI)
Added "Low Battery" Options (ROM Control/Battery/Low Battery Warning)
Updated Active Display
Add hardware keys rebinding (ROM Control/Hardware Keys)
Switched to a different Mms app. It has more options.
Added Custom Vibrations for Contacts
Added Minimum Vibration Duration (ROM Control/Sound)
Updates to Camera (Too many to list)
Added AppOps Section (Settings/App ops)
Updated and added Blacklist Settings (Phone/Settings/Blacklist)
Added Lockscreen Lock Icon Color (ROM Control/Lockscreen/Lockscreen Lock Color)
Turn Kill All and Google Now into normal buttons
Frameworks: Enhance face detection
Added "Pause" while recording video
Option to control cursor in text fields using volume keys (Settings/Language & Input)
Moved Active Display to ROMControl (ROMControl/Active Display)
Added Hide Low Priority Option to Active Display
Allow exporting of AOKPChangelog
GC triggering performance optimizations
dalvik/vm: Dalvik startup with a low memory footprint
Build minivold for recovery
Added 4G/LTE icon toggle (ROMControl/Signal)
Fix LTE Fully Connected
Updated mGerrit
Updated SuperUser
TRDS new 4.3 png's (DarkUI)
Squashed commit of installd changes
Option to hide Camera widget from lockscreen (ROMControl/Lockscreen)
RC: Fix capitalization
Add setfattr
LengthFilter on Carrier Label
Mms: Fix "done" action
Settings: Bypass Alert Improvement (Quiet Hours)
ROMControl: Fix Notification Landscape
ROMControl: Fix isSW600DPScreen
Include mGerrit as prebuilt apk
I'm sure there's more that I'm missing. Too busy at work here...[/B]
[B][U][I]AOKP 4.3 Jellybean 9.29.2013[/I][/U][/B]
SystemUI: Recents window visual updates
[B]Added Option to add Google Now to recents (ROMControl/General UI)
Updated Animation Controls
Added Network Speed Indicator (ROMControl/General UI)
Added Active Display Notifications (Settings/Display) ([B][URL="http://www.youtube.com/watch?feature=player_embedded&v=3TMycL9mzpg"]VIDEO[/URL][/B])
Added more battery icon options
Added increasing ringtone option (ROMControl/Sound)
Updated mgerrit activities
Browser: Fix NPE on First Launch
Dialer: Increased suggestions from 3 to 6
Fixed 2G toggle not being set on boot if selected
Fixed sshd_config and ssh-start
Fixed QuietHours Setting
Fix fstab memory leak
Updated Lockscreen Wallpaper option
Build BluetoothExt
Improved swagpaper error handling
AwesomePlayer: silence useless log and fix C derp[/B]
[B][U][I]AOKP 4.3 Jellybean 9.21.2013[/I][/U][/B]
[B]Merged android_4.3_r3.1 (JLS36G)
Allow Quick Settings tiles/toggles to be blacked out with Dark AOKP
Added Swipe to switch as a Toggle (ROMControl/Toggles)
Updated Listview Animations
vold: don't crash when formatting card with no filesystem
make_ext4fs: fix static utility executable, this time for SELinux
ext4_utils: fix utility build (SELinux)
Fixed turn off Camera Sound
Mms: Fix Multi-thread "read" button/intent
MMS: Fix Wrong QuickReply Counter
Offload database handling to seperate thread
Bluetooth: Handle BT search while rotate screen
Bluetooth: Handle pairing Cancel intent.
Bluetooth: Not allow Blank BT device name.
Bluetooth: Set isPreferred to true for PanProfile Connections.
libstagefright: Add support for custom LPA buffer size
Fixed left/right ribbon height
There's more. Back to work I go...[/B]
[B][U][I]AOKP 4.3 Jellybean 9.17.2013[/I][/U][/B]
[B]Initial release
Android 4.3 (JLS36C)[/B]
MAKE A NANDROID
Boot into recovery
Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system (if using CWM). To format system w/TWRP, select Wipe then System!!!(If already on AOKP 4.2.2 you should be able to just wipe cache & dalvik. If you have ANY ISSUES, FULLY WIPE BEFORE POSTING IN THIS THREAD!!!)
Flash ROM
Flash Gapps (Use the gapps package that I provide in this thread!)
Reboot
You have to flash Gapps every time you flash an update!
Jellybean
NEW!!!
AOKP 4.3 Jellybean Build 10.25.2013
Download HERE
Mirror
Download HERE
---------------------------------------------------------------------------------------------------------------
GAPPS
NEW!Gapps for Jellybean (4.3) 10.7.2013
Download HERE
Mirror
Download HERE
---------------------------------------------------------------------------------------------------------------
Kernels
Underwear Kernel (4.3) 10.25.2013 (Included in ROM)(Kernel Source)
DOWNLOAD HERE
----------------------------------------------------------------------------------------------------------------
Old Releases LOOK ON GOO.IM FOR OLDER BUILDS!!!
AOKP 4.3 Jellybean Build 9.29.2013
Download HERE
AOKP 4.3 Jellybean Build 9.21.2013
Download HERE
AOKP 4.3 Jellybean Build 9.17.2013
Download HERE
----------------------------------------------------------------------------------------------------------------
If you want to donate to me just click the "Donate to me button" under my avatar or click the PayPal Button ---->
These guys spend countless of hours doing this for next to nothing. Posts, views, and donations encourage them, and everyone else who helps out.
You guys can go HERE and donate team the AOKP Team. Throw some money at them, tweet them, love them.
Every donation is cherished and loved.
Check out the ROM source ( https://github.com/AOKP ) on github. Open source, in the spirit of community kangage.
This is a development thread where development takes place. Please respect that and treat it as so. I dont mind the thank yous and things like that. But i dont want this thread to stray too far from its purpose. With this being a development community, it is part of the plan to have you as the users involved to assist in providing information that can help with the troubleshooting process here. I don't have t-mobile service so anything related to their services will be on you tel help me acquire the information to help fix issues with them. I've provided a very useful q & a and faq section that is linked in the op of this very thread. Please read it!!! Thanks to everyone who is willing to help further the development of this rom.
I'm going to give this another shot guys. I received an overwhelming request response via messaging and I've decided to bring this back. Please be helpful in this thread. Please read the Q & A and FAQ and use it for any non development related questions you may have. There is a ton of useful information there for you guys. Thanks.
Yes!
Thanks so much for bringing it back Task! Have a cup on me. 6AP56290HU506182
shadowronemus said:
Thanks so much for bringing it back Task! Have a cup on me. 6AP56290HU506182
Click to expand...
Click to collapse
Thanks dude. I appreciate it. :highfive:
Thanks!!
task650 said:
I'm going to give this another shot guys. I received an overwhelming request response via messaging and I've decided to bring this back. Please be helpful in this thread. Please read the Q & A and FAQ and use it for any non development related questions you may have. There is a ton of useful information there for you guys. Thanks.
Click to expand...
Click to collapse
confirmation #5CR98190W1350083C Another small donation to show my respect for your work, and i would STRONGLY encourage other people who love his work to show it!! hoping this gets the thread started right!!
Manufactured consent said:
confirmation #5CR98190W1350083C Another small donation to show my respect for your work, and i would STRONGLY encourage other people who love his work to show it!! hoping this gets the thread started right!!
Click to expand...
Click to collapse
Thanks man. :highfive:
Just keep in mind that donations are not necessary. They are always very appreciated though. Anything i get here just goes to my little girl anyways. She deserves it more than me.
Subbed
Wayne Tech Nexus
zelendel said:
Subbed
Wayne Tech Nexus
Click to expand...
Click to collapse
I love having you everywhere on the internet. :highfive: :victory: :highfive:
Thank you for stopping by again ^.^
fantastic.
Just flashed an hour ago with full wipe of course, no issues whatsoever so far. BT, GPS everthing working perfectly.You are the man with the plan Task. Thanks again.
WOW! Task, you're really in the TMO thread?
lol Thats awesome bro! Less trash in the ATT thread. Your roms have always been amazing! :good: :highfive:
random reboots
Just a few logs from random reboots I've had, hope they help with future development.
Crash 1
Crash 2
Crash 3
Crash 4
Crash 5
Crash 6
Crash 7
Crash 8
Crash 9
Crash 10
Crash 11
These are just the ones I managed/remembered to grab. Sometimes it crashed before I was able to even get a log. These are the last_kmsg logs from random reboots. I noticed that the latest version of dolphin browser caused a few of them, I included only logs from after I uninstalled it. If you need more logs, or more details let me know. I'm happy to provide anything needed to make this better. Thanks for bringing this back, your hard work is greatly appreciated.
dragon-son said:
Just a few logs from random reboots I've had, hope they help with future development.
Crash 1
Crash 2
Crash 3
Crash 4
Crash 5
Crash 6
Crash 7
Crash 8
Crash 9
Crash 10
Crash 11
These are just the ones I managed/remembered to grab. Sometimes it crashed before I was able to even get a log. These are the last_kmsg logs from random reboots. I noticed that the latest version of dolphin browser caused a few of them, I included only logs from after I uninstalled it. If you need more logs, or more details let me know. I'm happy to provide anything needed to make this better. Thanks for bringing this back, your hard work is greatly appreciated.
Click to expand...
Click to collapse
I have been on this since it original release on the 18 and having changed anything and I have not had 1 random reboot....did you change kenel
dragon-son said:
Just a few logs from random reboots I've had, hope they help with future development.
Crash 1
Crash 2
Crash 3
Crash 4
Crash 5
Crash 6
Crash 7
Crash 8
Crash 9
Crash 10
Crash 11
These are just the ones I managed/remembered to grab. Sometimes it crashed before I was able to even get a log. These are the last_kmsg logs from random reboots. I noticed that the latest version of dolphin browser caused a few of them, I included only logs from after I uninstalled it. If you need more logs, or more details let me know. I'm happy to provide anything needed to make this better. Thanks for bringing this back, your hard work is greatly appreciated.
Click to expand...
Click to collapse
I would think about using another ROM considering you seem to he the only one to be having this issue. I have 8 testers and not one of them or anyone has reported anything like this since I started building for this device. You probably have a device that just won't work with the ROM. All devices are not created equally and it seems as though you might have a weak one.
cwalker0906 said:
I have been on this since it original release on the 18 and having changed anything and I have not had 1 random reboot....did you change kenel
Click to expand...
Click to collapse
Neither have any of my testers since first release. Its most likely just his device.
task650 said:
I would think about using another ROM considering you seem to he the only one to be having this issue. I have 8 testers and not one of them or anyone has reported anything like this since I started building for this device. You probably have a device that just won't work with the ROM. All devices are not created equally and it seems as though you might have a weak one.
Click to expand...
Click to collapse
Seriously... well you're the dev I'll take your word for it, I'm good at getting logs but not reading them. I'll try again on next build. Build from 6/18 was getting less reboots than 6/12 so I'm sure it can only get better. Hope the logs were useful, even if only to say my phone sucks.
dragon-son said:
Seriously... well you're the dev I'll take your word for it, I'm good at getting logs but not reading them. I'll try again on next build. Build from 6/18 was getting less reboots than 6/12 so I'm sure it can only get better. Hope the logs were useful, even if only to say my phone sucks.
Click to expand...
Click to collapse
Differences between devices, quality control, ect.. has been well known since the release of the s3. Hundreds of users were having to RMA their devices just to be able to run certain kernels/roms. So it seems this doesn't look like anything different than that. With you being the only one to have this issue I will be honest and say that I won't go around changing things to get it to work on one single device. That just wouldn't make any sense when things work just as they should for everyone else. So those logs really don't apply here considering those facts. Sorry dude.
Unable to Update
For some reason I'm unable to update the ROM, I receive multiple notifications every two days or so reminding me to update, but once I attempt and click the motif, I receive a:
Error occurred: Protocol not found:
Not too sure what to do now...
mr.g said:
For some reason I'm unable to update the ROM, I receive multiple notifications every two days or so reminding me to update, but once I attempt and click the motif, I receive a:
Error occurred: Protocol not found:
Not too sure what to do now...
Click to expand...
Click to collapse
Clear your caches and manually update your rom this time. Which version are you on?

[ROM][4.3][Unofficial] CyanogenMod 10.2 Beta Builds

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 10.2 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Useful Links
BBQLog changelog
Odin CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR UNOFFICIAL BUILDS!
Other Issues?
Use this for obtaining logs.
These are unofficial beta builds so bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Download Links
CyanogenMod:
Builds: http://goo.im/devs/mithun46/CM4.3
Google apps addon:
Download: 4.3 Google Apps
Root access:
Go to Developer options --> Root Access
And change to "Apps and ADB" to fix root
Screenshots: 1, 2 & 3
Thanks to:
CyanogenMod: Thanks a lot! You guys are awesome!!
@jug6ernaut : For being a awesome friend! Thanks man!
Reserved
Sweet! Downloading now!
If I'm on stock rom, Do I just follow the OP instruction?
motoxxxx said:
If I'm on stock rom, Do I just follow the OP instruction?
Click to expand...
Click to collapse
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
havanahjoe said:
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
Click to expand...
Click to collapse
Thank! now I need to unlocked my bootloader.
How is the rom?
motoxxxx said:
Thank! now I need to unlocked my bootloader.
How is the rom?
Click to expand...
Click to collapse
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Titanium Backup > Menu > Preferences > Backup Folder Location > DETECT > Whole Device > Select /storage/emulated/legacy/titaniumbackup and click yes when prompted to move backup files.
Click to expand...
Click to collapse
Looks like it works without doing that last step.
And in case you are trying to get into recovery, reboot and when you see the LED flash orange, hold the volume down button. Thanks mithun for the help
havanahjoe said:
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Click to expand...
Click to collapse
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
jug6ernaut said:
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
Click to expand...
Click to collapse
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Enable developer options. (go to about phone, scroll to the bottom, find the “build number” field, click on it seven times and it will turn on developer options.)
go back one level to the main settings screen and you’ll see developer options now. Open that, Enable advanced reboot options by clicking on the relevant checkbox
Click to expand...
Click to collapse
havanahjoe said:
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Click to expand...
Click to collapse
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
jug6ernaut said:
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
Click to expand...
Click to collapse
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
havanahjoe said:
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
Click to expand...
Click to collapse
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
jug6ernaut said:
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
Click to expand...
Click to collapse
Ah yes. I had noticed that in my status page before, but didn't know it broke the Group MMS option. I'll use the Sim Number Changer.
I asked in the Z thread to see if they are having issues with SMS too.
EDIT: Sim Number Changer FCs on me
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
{
"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"
}
havanahjoe said:
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
Click to expand...
Click to collapse
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
A little off topic, do you have the new Nexus 7?
havanahjoe said:
A little off topic, do you have the new Nexus 7?
Click to expand...
Click to collapse
I do .
jug6ernaut said:
I do .
Click to expand...
Click to collapse
The million dollar question is... Is it worth the upgrade from the original 7?
havanahjoe said:
The million dollar question is... Is it worth the upgrade from the original 7?
Click to expand...
Click to collapse
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick review. I really don't have a lot of use for a tablet myself, I have my laptop with me almost all the time and I don't mind carrying it (even though it's a 17" MBP), but I have been considering using a Nexus 7 as Nav/Media in the car. I've seen several people with a Subaru Legacy do it on theirs and it seems to fit very well. In that case the screen wouldn't really matter that much and doing a quick search on craigslist I found a 16 GB for $100. With what you said, it seems like a no brainer to get the first gen.
Apologies for the off topic discussion. To bring it back to CM, I am currently building a copy myself. Thanks to mithun I got my Ubuntu VM ready for compiling and it's CCing away.

[ROM][4.4.4][M7VZW][OFFICIAL] OmniROM

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.
*/
{
"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"
}
Introduction
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognize how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Click to expand...
Click to collapse
Sources
OmniROM's GitHub
OmniROM's m7vzw device tree
OmniROM's stock m7 kernel
Click to expand...
Click to collapse
Installation instructions
-- Requires S-OFF
* -- Download ROM and GApps (optional)
* -- Coming from some other ROM? WIPE ALL TEH THINGS (system and factory reset; don't have to wipe storage/internal)
* -- Flash ROM
* -- Flash GApps (optional)
Click to expand...
Click to collapse
Download
OmniROM-m7vzw
[GAPPS][4.4.x] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's)
Click to expand...
Click to collapse
Changelog
Code:
[note] Always review [URL="https://gerrit.omnirom.org/#/q/status:merged,n,z"]OmniROM's merged gerrit[/URL].
[B]Upcoming changelog -- XXXXXXXX[/B]
[B]Current changelog 20140628[/B]
Updated: Android 4.4.4
[URL="https://gerrit.omnirom.org/#/c/2944/"]Fixed kernel compile (broke build bot)[/URL]
Older changelogs:
Code:
[B]20140102[/B]
[fixed] -- [URL="https://github.com/PonsAsinorem/android_device_htc_m7vzw/commit/bac0f981e11fb4890b308a38fca21bf3e224d1e6"]m7vzw: fix Goo OTA support[/URL]
[B]20131229[/B]
[new] -- [URL="https://github.com/PonsAsinorem/android_device_htc_m7vzw/commit/676fbacde7799f0680163d1d52392a063ff5413f"]Goo Manager OTA support[/URL]
[B]20131220[/B]
[fixed] -- [URL="https://github.com/PonsAsinorem/android_device_htc_m7vzw/commit/0d2e8344daeaeb11c5156f6f818e94eba469b8d2"]Access VZW apps in the Play Store[/URL]
[changed] -- [URL="https://github.com/PonsAsinorem/android_device_htc_m7vzw/commit/4d3ca74981ea1ef46a973057852508178ee9537c"]Updated 4.3 fingerprint[/URL]
[fixed] -- [URL="https
://github.com/PonsAsinorem/android_device_htc_m7vzw/commit/d87e0ec50aafb5ee8c160e339b718ac4c83d4eff"]No longer shows Roaming on Verizon[/URL]
[B]20131218[/B]
[new] -- Initial UNOFFICIAL release
Click to expand...
Click to collapse
FAQ
-- [Q] I have a question...
-- [A] Please post it in the Q&A/T thread: [Q&A/T][M7VZW][UNOFFICIAL] OmniROM
-- [Q] I have found a bug that needs squashed. How do I report it?
-- [A] If it's m7vzw specific, please post in the Bug tracker section of this devdb. Also be sure to include a logcat.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* [URL="http://omnirom.org/"]The OmniROM Project[/URL]
* [URL="http://www.cyanogenmod.org/"]The CyanogenMod Project[/URL]
* [URL="http://source.android.com/"]The Android Open Source Project[/URL]
XDA:DevDB Information
[ROM][4.4.4][M7VZW][OFFICIAL] OmniROM, ROM for the Verizon HTC One
Contributors
PonsAsinorem
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.10.605.3
Version Information
Status: Nightly
Created 2013-12-18
Last Updated 2014-08-07
Reserved
Bear in mind, that this ROM is in "Testing" phase, and Unofficial from Omni (pretty sure it's the first that I could find for the m7vzw). All I did was boot up, sign in to my Google account, signed into my WiFi, called and texted someone as a test. That's it, and that's all I've tested.
And Q&A/T thread has been added. Please use that for...uhh..Q&A. And basic troubleshooting. This thread is purely for development.
PonsAsinorem said:
And Q&A/T thread has been added. Please use that for...uhh..Q&A. And basic troubleshooting. This thread is purely for development.
Click to expand...
Click to collapse
Hi PonsAsinorem, could you post a link to your Q&A/T thread in the OP or second post.
Many thanks and best of luck with this:good:
Robbie P said:
Hi PonsAsinorem, could you post a link to your Q&A/T thread in the OP or second post.
Many thanks and best of luck with this:good:
Click to expand...
Click to collapse
Done.
So I've been running it since last night....about 6-7 hours of actual usage. Everything is working properly except Bluetooth. Bluetooth can find devices it just cannot communicate with them. I receive an error "cannot communicate with device" in my car, with my jawbone and also with a $10 BT headset from RadioShack. I will provide a logcat later tonight or tomorrow when I have some free time. Just throwing it out there for now to see if anyone else can confirm. Also, I haven't found a way to use multiwindow. Other than that it has been great and battery life is very good. Thanks man. Have a great day.
Sent from my HTC One M7 using XDA Premium 4
Moved some posts to the Q&A thread.
Please don't post questions here, only dev talk :good:
Good to see you're back at building roms. Flashing now. ^_^
-will update this post when i have more info.-
Oh man I was hoping we were going to get Omni
Sent from my HTC6500LVW using Tapatalk
I'm bumping it up because I don't think a lot of people know a second build is out. It has less than ⅓ the amount of downloads as Build 1....Build 2 is working great BTW
Sent from my HTC One M7 using XDA Premium 4
JamesPumaEnjoi said:
I'm bumping it up because I don't think a lot of people know a second build is out. It has less than ⅓ the amount of downloads as Build 1....Build 2 is working great BTW
Sent from my HTC One M7 using XDA Premium 4
Click to expand...
Click to collapse
Any additional features added?
Sent from my One using Tapatalk
whirl08 said:
Any additional features added?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
No real major additional features (a minor changes from Omni), but does fix the Roaming indicator being always on, despite not roaming.
New Christmas Eve build up, complete with holiday themed image in the OP. Thanks, Alex.
I haven't added Goo Manager update support yet, because I was hoping to get the m7vzw official status.
Does this have the split view support that's available on the international build of Omni?
XPEric said:
Does this have the split view support that's available on the international build of Omni?
Click to expand...
Click to collapse
It should. I didn't deviate too far from Omni's device trees to ease a merge.
XPEric said:
Does this have the split view support that's available on the international build of Omni?
Click to expand...
Click to collapse
PonsAsinorem said:
It should. I didn't deviate too far from Omni's device trees to ease a merge.
Click to expand...
Click to collapse
It doesn't. I actually asked 3-4 times but never got an answer as to where it should be to enable it. So I looked online to see how to enable it (open recents and long press an app) but it doesn't have that feature. Maybe build 3 will have it but 1 and 2 definitely didn't. Merry Christmas guys
Sent from my HTC One M7 using XDA Premium 4
JamesPumaEnjoi said:
It doesn't. I actually asked 3-4 times but never got an answer as to where it should be to enable it. So I looked online to see how to enable it (open recents and long press an app) but it doesn't have that feature. Maybe build 3 will have it but 1 and 2 definitely didn't. Merry Christmas guys
Sent from my HTC One M7 using XDA Premium 4
Click to expand...
Click to collapse
If the m7ul has it, then this *should.* If it doesn't, then I didn't carry over something. I'll have to take a look at this after the holidays. And Merry Christmas to all of you as well.
PonsAsinorem said:
If the m7ul has it, then this *should.* If it doesn't, then I didn't carry over something. I'll have to take a look at this after the holidays. And Merry Christmas to all of you as well.
Click to expand...
Click to collapse
Yeah its no worries man. I haven't been able to try it on any AOSP ROM yet and was hoping to try it on here so I looked up how to use it on YouTube but it doesn't look like its included on here. I tried to look through all settings and advanced settings to see if I had to enable it or if I was missing something but I couldn't find anything so I'm guessing it just isn't present. Anyway its no big deal and no rush whatsoever because everything else works properly and its super smooth. Have a great week happy holidays.
Sent from my HTC One M7 using XDA Premium 4
JamesPumaEnjoi said:
Yeah its no worries man. I haven't been able to try it on any AOSP ROM yet and was hoping to try it on here so I looked up how to use it on YouTube but it doesn't look like its included on here. I tried to look through all settings and advanced settings to see if I had to enable it or if I was missing something but I couldn't find anything so I'm guessing it just isn't present. Anyway its no big deal and no rush whatsoever because everything else works properly and its super smooth. Have a great week happy holidays.
Sent from my HTC One M7 using XDA Premium 4
Click to expand...
Click to collapse
And you're sure the m7ul and/or m7att has it? I'll check it out in a bit (a bit being relative).
PonsAsinorem said:
And you're sure the m7ul and/or m7att has it? I'll check it out in a bit (a bit being relative).
Click to expand...
Click to collapse
I think that feature is on 4.3 not 4.4.
PonsAsinorem said:
And you're sure the m7ul and/or m7att has it? I'll check it out in a bit (a bit being relative).
Click to expand...
Click to collapse
Androcles said:
I think that feature is on 4.3 not 4.4.
Click to expand...
Click to collapse
No clue... @XPEric was the one who mentioned international version...but Androcles very well could be right that it isn't in 4.4
EDIT...It looks like only some homemade builds of 4.4.2 have multi window included...on m7ul's page it lists official builds and homemade builds and the differences each one has...one of them being multiwindow
http://forum.xda-developers.com/showthread.php?t=2488216
Sent from my HTC One M7 using XDA Premium 4

{ROM} Dirty Unicorns_4.4.4_GEE {v-8.2}_11/4/14

{
"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"
}
Dirty Unicorns is a custom ROM built with stability in mind and optional customization. The idea to start this ROM began out of pure boredom around 4.1.2 on the EVO 3D and later turned into a form of an addiction (a good one) to see where we could go from there. We have since expanded to more devices to include the HTC One, Nexus 5, SGS4 and many more. We quickly realize that users loved what we were doing as well as other developers because it was done the right way. We've always had fun doing it and take pride in knowing that we've done it without having to bug the end user for donations to pay for server costs and/or any of those sob stories you hear. This ROM is 100 percent free and will remain that way.​
Those wanting to use our ROM as a base are more the welcomed to do so but please maintained the credits/thanks below, do not ask for donations as it wouldn't be fair to do so considering and let us know as we often like to contribute to other projects.
As stated above, we love to maintain authorship but we also like to publicly praise those that have helped us along the way with our wonderful project. With that said, this wouldn't be possible without the work and help of those listed below THANK YOU ALL!!
| OmniROM | AOKP | CM | ChaOS | Paranoid Android | Slim ROMs | Preludedrew | Team Black Out | Official Testers / Translators |
Please check our gerrit/github for full credits/thanks of individual contributors​Believe it or not, we are human and we do forget things. If we have left someone out of the credit/thanks list, just PM us and we'll gladly add on to the list.
Code:
-- Built-in ad blocker (able to update hosts on the fly)
-- Ability to disable FC notifications
-- Enable pointer/user microphone options (screen record)
-- Download Center (Gapps, Xposed, etc)
-- Ability to force Expanded Notifications
-- Over 100 cloud based wallpapers
-- Facebook Sync Hack
-- Immersive mode
-- Hot Reboot In Power Menu
-- Appbar (app sidebar)
-- Customizable Quick Settings
-- Customizable power menu
-- Customizable lockscreen shortcuts
-- App Ops access in Settings
-- TRDS (built in theme in settings)
-- Statusbar Clock options
-- NavBar Options
-- Halo (multi-tasking tool)
-- Halo size/color changer
-- Hardware key remap mod (only for HW button devices)
-- Battery Bar / Circle batteries
-- Network speed indicators in statusbar
-- SuperSU (chainfire)
-- Build.prop mods
-- Init.d Tweaks
-- Active Display (Moto X notifications)
-- ListView Animations
-- Custom System Animations
-- Toast Animations
-- Custom BusyDialog
-- Advanced Low Battery Indicator options
-- ScreenShot QuickTrash
-- Color Changing PhaseBeam
-- Gesture Anywhere
-- Button Light Notification
-- Statusbar Color options
-- OmniSwitch (multi-tasking tool)
-- Driving Mode
-- Lockscreen theme options
-- Lockscreen notifications / options
-- System App Remover
-- Identicons
-- Suspend Actions
-- Wakelock Actions
-- SlimROM based recents
-- Contextual notification panel headers
-- SlimROMs privacy guard
-- Blacklist calls/sms
And much much more, just take a peek into Dirty Tweaks and ENJOY!!!
HERE
- Make sure you have TWRP or compatible recovery for kitkat
- Wipe everything but your external/internal storage
- Move the ROM zip to your device
- Flash it and reboot
- Once the ROM boots, reboot back into recovery
- Flash the recommend GAPPS and ENJOY!!
Code:
[B]8.2 - 11/4/14[/B]
-Navbar:Custom Glow Time
-SystemUI:Fix crash during notification/theme change
-Bring back color changer for MIUI-like carrier label
-Fix carrier label not sticking after a reboot
-Fixed clear-all button Bug
-Fix auto rotation/battery tile long press
-Double tap to sleep on navigation bar
-Add Voice Dialer back
-Support full size application screenshots
-Fix bootanimation cut off on HDPI devices
-NavRing:Last App
-Fix longpress app circlebar QS tile
For a more detailed changelog, feel free to check out our Gerrit or Github.
ROM
GAPPS
Google+ community - https://plus.google.com/u/0/communities/109738128866939227235
Please keep in mind that in our Google+ community, we like to post test builds to fix bugs and/or gauge what the user would like to see in this ROM.
With this said, if you would like to test out an experimental build (might not be stable) please check out our G+ community.
Github source (4.4.4) - https://github.com/DirtyUnicorns-KitKat
Gerrit review - http://gerrit.dirtyunicorns.com/
If you would like to submit a patch to our ROM, please use our gerrit as pull requests often go unnoticed.
All patches are welcomed and reviewed in a timely matter
For more screenshots, please visit this imgur gallery - http://imgur.com/a/KRhfq#0
PLEASE DO NOT MIRROR ANY VERSION OF THIS ROM!
- IF THERE'S AN ISSUE WITH THE LINKS, JUST LET ME KNOW!
XDA:DevDB Information
Dirty Unicorns , ROM for the Sprint LG Optimus G
Contributors
k5t4j5, Team D.I.R.T
Version Information
Status: Stable
Reserved
Reserved
*INFO: You'll notice, in Dirty Tweaks there is an option in misc. tweaks to turn off force close notices, for anyone that sticks with stock kernel or has issues until there resolved.
Sent from my Optimus G using XDA Premium 4 mobile app
First? Lol. I'm dling right now. Can't wait to test a new ROM. Thank you.
Edit: great job on the ROM. It's super smooth and snappy. I had a few FC's with the baked in kernel and decided to switch to matr1x. All smooth so far. The only thing I'm seeing is as I type this it seems that the keyboard is not all the way at the bottom of the screen, it doesn't want to put a space every time I touch the spacebar, default keyboard. I see you suggest using an alternate, what's the reason?
Thanks again. Great so far.
Downloaded. Will test this later
thanks.
Sent from my Nexus 7 using Tapatalk
dopy25 said:
First? Lol. I'm dling right now. Can't wait to test a new ROM. Thank you.
Edit: great job on the ROM. It's super smooth and snappy. I had a few FC's with the baked in kernel and decided to switch to matr1x. All smooth so far. The only thing I'm seeing is as I type this it seems that the keyboard is not all the way at the bottom of the screen, it doesn't want to put a space every time I touch the spacebar, default keyboard. I see you suggest using an alternate, what's the reason?
Thanks again. Great so far.
Click to expand...
Click to collapse
Reason I suggest alternate keyboard, when I first booted up I started typing a message, hit the voice to text button, and phone rebooted. Tested this 3 times and all three resulted in reboot so there's some properties missing in this area. I use SwiftKey anyway. The prediction texting on stock is horrible compared to other keyboards you can get in the market. Example: I wrote this reply in seconds. I see what you mean with it not all the way at the bottom. That's odd, will look into it.
Sent from my Optimus G using XDA Premium 4 mobile app
k5t4j5 said:
Reason I suggest alternate keyboard, when I first booted up I started typing a message, hit the voice to text button, and phone rebooted. Tested this 3 times and all three resulted in reboot so there's some properties missing in this area.
Click to expand...
Click to collapse
oh that's weird because I'm using it right now to say this into my reply. but maybe it's a kernel issue. Do you remember if that was the baked in or matr1x? Also, how can I enable trace with this keyboard? I live by that lol.
There's a few other things I've noticed. When you go to about phone and click about du or du statistics I get unfortunately settings has stopped every time.
And under "dirty tweaks/lock screen/misc tweaks/lockscreen notifications/privacy" the word being is spelled incorrectly as beeing. I don't know if that's intentional or upstream, or if nobody cares but I thought I'd bring it up.
Any idea why it would never provision? It told me 3 times that it's unable to complete.
dopy25 said:
oh that's weird because I'm using it right now to say this into my reply. but maybe it's a kernel issue. Do you remember if that was the baked in or matr1x? Also, how can I enable trace with this keyboard? I live by that lol.
There's a few other things I've noticed. When you go to about phone and click about du or du statistics I get unfortunately settings has stopped every time.
And under "dirty tweaks/lock screen/misc tweaks/lockscreen notifications/privacy" the word being is spelled incorrectly as beeing. I don't know if that's intentional or upstream, or if nobody cares but I thought I'd bring it up.
Any idea why it would never provision? It told me 3 times that it's unable to complete.
Click to expand...
Click to collapse
What where your steps/actions leading up to provision problem ? Many of the little bugs will be fixed in the coming build. Building this one with the B kernel and also some different variables I used resulted in the issues. I wanted to get it posted up for all to test out and give me a checklist to fix. Thanks for the info.
k5t4j5 said:
What where your steps/actions leading up to provision problem ?
Click to expand...
Click to collapse
As soon as the phone boots for the first time and you start to enter information it wanted to activate the device. It dialed a *phone number I think it was *28something. But either way it was a recording that states the process could not be completed. I retried it a couple times and got the same message. The funny thing is that I have data and can make calls and get texts.
Oh yeah, some roms do that, you can let it call and press 1,it'll say it couldn't activate, then you can just hit the skip button. You can also hit skip when it first pops up on and move on to adding Google account or boot up. Either way your activated.
Sent from my Optimus G using XDA Premium 4 mobile app
If all goes well I'll be pushing a big update this afternoon/evening for everyone, few additional features, and hopefully lots of fixes.
Wow good job. Downloading now, I've been dying to try the latest DU. Glad someone picked this up.
Sent from my Optimus G using xda app-developers app
Installed and setting up now. I did get a flash failed message. I had to install super su and reboot to recovery and flash that way.
Also I flashed mirage. Any drawbacks to that since this is built with matrix?
One more question. Remapping of the capacitive keys? Its not under buttons and I can't find it. I like changing my menu to a recents button.
Thanks for your work on this!!
Sent from my Optimus G using xda app-developers app
likwidkool said:
Installed and setting up now. I did get a flash failed message. I had to install super su and reboot to recovery and flash that way.
Also I flashed mirage. Any drawbacks to that since this is built with matrix?
It's built with b55 kernel, I suggest the matr1x kernel but you can try Mirage I haven't tried it with that one. Let me know how it goes though! A couple options didn't take in initial build but I think I have the problem solved and new update is building right now.
Click to expand...
Click to collapse
k5t4j5 said:
likwidkool said:
Installed and setting up now. I did get a flash failed message. I had to install super su and reboot to recovery and flash that way.
Also I flashed mirage. Any drawbacks to that since this is built with matrix?
Click to expand...
Click to collapse
It's built with b55 kernel, I suggest the matr1x kernel but you can try Mirage I haven't tried it with that one. Let me know how it goes though! A couple options didn't take in initial build but I think I have the problem solved and new update is building right now. Update will have matr1x built in.
Click to expand...
Click to collapse
sharkboy0901 said:
Wow good job. Downloading now, I've been dying to try the latest DU. Glad someone picked this up.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Pleasures all mine man, I'd been wanting to build this for a while since we didn't have an updated version, and the new stuff is awesome, just gotta get some kinks smoothed out.
k5t4j5 said:
k5t4j5 said:
It's built with b55 kernel, I suggest the matr1x kernel but you can try Mirage I haven't tried it with that one. Let me know how it goes though! A couple options didn't take in initial build but I think I have the problem solved and new update is building right now. Update will have matr1x built in.
Click to expand...
Click to collapse
So far so good!! Enjoying all the options!!
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
Has anyone else noticed problems with messages? Data works fine but I can't send/receive any MMS.
dopy25 said:
Has anyone else noticed problems with messages? Data works fine but I can't send/receive any MMS.
Click to expand...
Click to collapse
You might look in mobile network's on make sure data is checked on. I was showing full data service but somehow it wasn't checked, maybe a reboot will fix also. New update halfway finished

Categories

Resources