{
"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"
}
[ROM][AOKP 7.1/Nougat][HLTE]OFFICIAL AOKP for Galaxy Note 3 (Unified) Nightlies
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Introduction
AOKP is a ROM developed by TeamKang, based on AOSP with magical unicorn bytes (awesome features) baked right in!
These builds have only been tested on SM-N9005! @Buslova confirmed working on SM-N900P for Sprint
Features
Full OMS/Substratum support - Theming built right in
ROM Control app - A central place to manage all almost all the cool features Magical Unicorn Bytes!
Gesture Anywhere/App Circle Bar/App Sidebar - Use gestures/side bars to launch frequently used apps/activities
PIE - Quickly access common actions by swiping up above home key
LED Control - Control color and pattern for notification LED
Tons of other tuneables - So many aspects can be changed, from the LockScreen to the hardware button mapping, and much more!
Click to expand...
Click to collapse
Installation instructions
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS (OpenGapps or similar; ARM platform; Android 7.1)
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
Official AOKP Download Page:
AOKP for Samsung Galaxy Note 3 (hlte)
Source:
AOKP Source
Click to expand...
Click to collapse
Changelog
Code:
Changelog is available at the download link above
Thanks To/Credits
*TeamKang
*tdm
*LineageOS
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Android Open Kang Project for Samsung Galaxy Note 3 (HLTE), ROM for the Samsung Galaxy Note 3
Contributors
shane87
Source Code: [url]http://aokp.co/source[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest TWRP or CWM Recovery
Based On: AOKP
Version Information
Status: Nightly
Created 2017-11-26
Last Updated 2017-11-26
Reserved
Finally! An official AOKP! I was just wondering if a custom kernel would work here? synergy kernel perhaps
I can't guarantee that it would, but this rom uses the exact same kernel as lineage, so any kernel that works with lineage should work here. If you try it out, let me know
wow thanks
Can't wait I be flashing this after work tomorrow
shane87 said:
I can't guarantee that it would, but this rom uses the exact same kernel as lineage, so any kernel that works with lineage should work here. If you try it out, let me know
Click to expand...
Click to collapse
Currently there are no custom kernels that do work with LineageOS, because of changes in RIL libs location on 5.11, so any build after that date will only work with stock kernel.
please add the rom screenshots and tell us the features of rom,
this rom have spen?
Arquiteto said:
Currently there are no custom kernels that do work with LineageOS, because of changes in RIL libs location on 5.11, so any build after that date will only work with stock kernel.
Click to expand...
Click to collapse
Ah ok. I haven't looked into any custom kernels on the hlte. I use my wife's phone for testing, so not a lot of chance to test stuff like that.
[Clarification]
Another point that I just thought of (it's very early lol); If you DO find a kernel that works with Lineage/AOKP, I don't accept bug reports from people running custom kernels. Too many variables to account for in debugging.
persiansoftware said:
please add the rom screenshots and tell us the features of rom,
this rom have spen?
Click to expand...
Click to collapse
There are a few screenshots, if you click on the screenshots tab at the top. I will add more later. As far as features, it's AOKP. AOKP's website can give you a decent overview of the features. I may add a feature list later. If I have time. As far as s-pen support goes, not yet. S-pen currently only works on stock to the best of my knowledge.
[Update]
It appears that Lineage has added at least partial s-pen/stylus gestures support. I'm looking into pulling that support over to AOKP. NO ETAS!
[Update 2]
I added a short feature list. And more screenshots. For further info, refer to the AOKP site posted above.
Arquiteto said:
Currently there are no custom kernels that do work with LineageOS, because of changes in RIL libs location on 5.11, so any build after that date will only work with stock kernel.
Click to expand...
Click to collapse
Would you have any idea on which changes exactly we're looking at?
I'm on RRN 5.8.5 CHN version but with "no sim" issues since the last 2 releases even on stock kernel, just wondering if AOPK has the same issue. Note that my device is a China model SM-N9008V Qualcomm CPU
Thanks for the feedback
Chinaboy5216 said:
Would you have any idea on which changes exactly we're looking at?
I'm on RRN 5.8.5 CHN version but with "no sim" issues since the last 2 releases even on stock kernel, just wondering if AOPK has the same issue. Note that my device is a China model SM-N9008V Qualcomm CPU
Thanks for the feedback
Click to expand...
Click to collapse
I gave up on hlte for a long time before I began working on AOKP for hlte. I use my wife's phone as a guinea pig (I own an AT&T LG G4), and I was compiling LOS for her. Around May or June, all of the LOS builds started giving me "no sim" grief. I pored through LOS kernel and device tree changes, and couldn't come up with anything. Then, about a month ago, I started digging again. The "no sim" issue, at least in my case, was caused by LOS upgrading the firmware that they build in to their ROM. The new firmware requires a modem update. Flashed the latest modem, and problem solved. I can't guarantee that your "no sim" issue is the same, but it is a good place to start. Also, please note that I have NOT tested these builds on anything but an SM-N9005 International unlocked GSM variant, as that is all I have access to.
shane87 said:
I gave up on hlte for a long time before I began working on AOKP for hlte. I use my wife's phone as a guinea pig (I own an AT&T LG G4), and I was compiling LOS for her. Around May or June, all of the LOS builds started giving me "no sim" grief. I pored through LOS kernel and device tree changes, and couldn't come up with anything. Then, about a month ago, I started digging again. The "no sim" issue, at least in my case, was caused by LOS upgrading the firmware that they build in to their ROM. The new firmware requires a modem update. Flashed the latest modem, and problem solved. I can't guarantee that your "no sim" issue is the same, but it is a good place to start. Also, please note that I have NOT tested these builds on anything but an SM-N9005 International unlocked GSM variant, as that is all I have access to.
Click to expand...
Click to collapse
Thanks for the feedback, problem is i'm already on the latest modem (China ... :crying: not the most updating country around). Anyway i keep hoping and checking also with Lineage OS devs, so with a bit of luck We need to stay optimist here. If i doesn't get solved then maybe i turn to a non lineage based rom if they are still around.
Thanks a lot!! Good luck with AOPK :good::good:
sm-n900p (SPRINT) user here. I've run AOKP on my galaxy nexus before my note 3. I always enjoyed the built in options and smoothness of AOKP. And once again AOKP knocked it out tha park on first nougat build for us! It even works on my picky n900p without needing to set any APN or network settings. Full LTE, SMS, MMS access upon first boot after flashing ROM + nano gapps! That's a rarity these days! I can't say thanks enough. I seriously have been thinking about getting a new phone since all other ROMS I have saved or even "new" ones were all starting to have little quirks or data was near impossible to get to work (mainly those ports) even after flashing apn setting .zips in recovery (I have a few mvno zips and one I made just for sprint).
However, after the magical pink unicorn boot animation closed and the system began running, I instantly had LTE service. Thanks so much! I haven't upgraded because honestly I don't think a better over-all device has been made since the note 3. Features keep disappearing with only marginal increases in performance that for a while (gotten a lil better lately) was negated by bloated ui overlays.
I can't believe I finally have official AOKP on my n900p and it ran flawless on 1st try. =)
Awesome! Glad to hear man. I'll update the op to reflect a confirmation for n900p
Considering how hard I've been both working followed by partying hard (i work retail....everyday that I survive is a miracle), I'm sure I'm just overlooking these features. I apologize if I just overlooked these. If they're not there, is there a way to request it/them to be added to AOKP chain?
1. Is there a way to turn on battery bar on home screen especially since my battery % icon I've been using occasionally disappears (weird one, never witnessed that before). Not a big deal but I always preferred a thin battery bar at the top. 1 less thing in my status bar.
2. Am I just missing it or is there a way to set a specific app launch to long press of left capactive button or better yet for consistency reasons, ability to choose specific apps for long press on any of the 3 buttons on the bottom? I only see options for pre-set android actions, not an option to choose an app to launch.
3. Is there or ever will be a theme engine or maybe substratum support?
I'm gonna rock this ROM regardless, just 3 of my top fav features that I haven't found yet. Figured I'd ask since knowing me, I just missed the option somewhere.
For the first two, I'm honestly not sure. I know that they are not implemented. As far as getting them added, I'm just getting my feet wet on maintaining a device, and I know that TeamKang is working on Oreo bring up, so I wouldn't hold my breath on them getting in any time soon. Maybe once Oreo work settles down a bit it can be looked at.
OMS/Substratum support is already built in. Just download the Substratum app from the play store, and any themes you want as well. My wife is running J-Ice Substratum theme on her SM-N9005 right now.
shane87 said:
For the first two, I'm honestly not sure. I know that they are not implemented. As far as getting them added, I'm just getting my feet wet on maintaining a device, and I know that TeamKang is working on Oreo bring up, so I wouldn't hold my breath on them getting in any time soon. Maybe once Oreo work settles down a bit it can be looked at.
OMS/Substratum support is already built in. Just download the Substratum app from the play store, and any themes you want as well. My wife is running J-Ice Substratum theme on her SM-N9005 right now.
Click to expand...
Click to collapse
Thanks man. Ya, I ain't holding my breath that this device will get Oreo builds but I'm happy since this is the most stable/feature packed nougat ROM that I've been able to run on my n900p without jumping through hoops.
Thanks again for everything. Wasn't trying to add requests to your plate. I also didn't even think about the fact Oreo is here so of course all the larger teams have moved their focus to that build. I just thought maybe I missed the first 2 items I mentioned since almost any aosp/cm/lineage/sammy based rom have those features nowadays. No biggie. I can survive without.
Can't say thanx enough man which is why i maxxed out my "thanks" button on you today. =)
Well, again, no promises or ETAs, but I am going to work on getting Oreo for hlte. I already let TeamKang know I would work on the Oreo bring up when they made me device maintainer. But I have a few other things I'm trying to get pulled in first (s-pen), and I'm waiting a bit to see how Oreo bring up on lineage works out for hlte. Anyway, thanks for the support! Its nice to be able to share my work (what little I do, lol) with someone besides family and friends.
Nice rom :laugh:
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
[ROM][UNOFFICIAL][4.4.4][WEEKLIES] SlimKat [m4], ROM for the HTC One Mini
Contributors
pandasa123
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2014-08-13
Last Updated 2014-08-12
Downloads
ROM - Full ROMs every week
SlimGapps - Download Google App package and other addons. Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Slim 7.0 Stable
Start of project
For full list: Click here
Click to expand...
Click to collapse
List all Questions and Off-Topic discussions in Q/A Thread
Remember, flash at own will! Don't message me and threaten me with a lawsuit because I may or may not have broken your device!
Issues
Waiting for this to fill
Thanks to:
SlimROMs for ROM
CyanogenMod for kernel
Click to expand...
Click to collapse
Installation Instructions
You must unlock your bootloader or be S-OFF.
You must have a custom recovery installed that allows SELinux.
Download the HTC One Mini build .
Locate Slim 4.4 Gapps here.
Fully wipe your device from Recovery if you are not coming from SlimKat already.
Reboot into recovery and install.
Hi bud. Just to confirm Rom boots fine and installs flawlessly! So far not noticed any issues. Unfortunately I'm a loyal candyRom user so will be bouncing back to that but good work and thanks for bringing this to the m4..cheers
Good luck on getting it official
Anyone found any bugs? I want to get rid of them for you guys by next build
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
dipje said:
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
Click to expand...
Click to collapse
Well that's up to the user if he wants a none sense ROM. I seen all the fuss about the issues etc even seen the Sense Fanboys loving that people are being scared off AOSP too. Tbh I don't see any problems with it my Rom been tested for awhile and is build from slim not CM with no issues at all... if people don't wanna try aosp then that's their loss....
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
dipje said:
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
Click to expand...
Click to collapse
Well I don't own this device anymore but the guy who tests builds doesn't have any issues with my ROM. This isn't my thread and I didn't build this ROM so you would have to take it up with the thread owner...
"On multiple aosp version" ???
Had no problems with any aosp rom on this device and I haven't ran sense for about a year now. No issues with pac,or slim and definitely none with candy which is my daily rom. Tbh I did have one issue with cm in the early days which I managed to recover from... But I put that down to my error... Flashing different kernels, installing performance mods/scripts etc and using different xposed modules.
Apologies for hijacking thread
Don't worry about the thread hijack lol...i wasn't paying attention..
I'm back from the hospital and i'm ready to build. t6vzw is brunching right now, and once it's done t6spr will start. after that, the m4 will get going and then my evita...so m4 users, expect your build to be ready by the end of tonight or so
slim m4 should be coming out today or tomorrow...the new server had a lot of build errors so i just fixed it for the evita
going to build for t6vzw, then t6spr, and then m4...
NEW BUILD! 7.6! Wait for around 15 min after this post is done and you'll see it. Check on the slim website for changelog...
http://downloads.codefi.re/ethanj99/pandasa123/Slim
Ok everyone, i'm building right now and this is the last time (i hope) that i move hosts
be a bit patient with me and i'll try and get it uploaded as soon as I finish homework
http://downloads.codefi.re/pandasa123
EDIT: UPDATED! Enjoy
New build guys - 7.9 Weekly (FINALLY )
Changelog:
Settings: Slimrecents card/text color
Add ADB over network tile
frameworks/av updates aosp caf
frameworks/base updates aosp caf
audio-caf updates
updated apns
frameworks/native-caf updates
more translations
Click to expand...
Click to collapse
enjoy
pandasa123 said:
New build guys - 7.9 Weekly (FINALLY )
enjoy
Click to expand...
Click to collapse
Sorry, but I can't find 7.9, only 7.8.
Thanks for building slim for m4!
Hey guys, Slim 8.0 Stable is out! Enjoy
pandasa123 said:
Hey guys, Slim 8.0 Stable is out! Enjoy
Click to expand...
Click to collapse
Ok. but where to download ?
http://downloads.codefi.re/pandasa123/Slim
No root after installing this ROM. Kernel installed is TWRP. No other kernel seems to work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* 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:
1. First time flashing CyanogenMod 13.0 your device, or coming from another ROM?
2. Download the zip(s).
3. Install a compatible Recovery
4. Perform a NANDroid backup of your current ROM (Optional)
5. Wipe data & cache partitions of your device
6. Flash CyanogenMod.
7. Optional: Install the Google Apps addon package.
Firmware Update:
If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.
4.3.0 (M)
4.2.0 (M)
3.1.1 (L)
Official Downloads:
get.cm
GAPPS
Bugreport: Report in this thread. It was likely my fault.
Known Problems:
Touch doesn't work in Retroarch (ingame, main menu works fine) and some others games.
Source Code:
https://github.com/CyanogenMod/android_device_nvidia_shieldtablet (branch cm-13.0)
https://github.com/CyanogenMod/android_device_nvidia_shield-common (branch cm-13.0)
https://github.com/CyanogenMod/android_kernel_nvidia_shield (branch cm-13.0)
XDA:DevDB Information
CM13.0 Shieldtablet, ROM for the Nvidia Shield Tablet
Contributors
Steel01, Unjustified Dev
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-03-15
Last Updated 2016-09-06
Notes
Disclaimer
These notes are old and do not apply to recent builds.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Side Notes:
I initially made these builds to test some work I am doing with the proprietary apps on the Portable. But since no one else has released cm builds for the tablet, I figured I might as well. Unjustified Dev did the vast majority of the work on the kernel and device tree. I only did a bit of work to enable the modem. Attached are the two patches I made to the framework to allow controller pairing to work. Also attached is a flashable zip of the proprietary apps. Do note that these do not work as intended and should not be used with great expectations. The controller will pair and seems to work indefinitely (unlike on the Portable), but audio is always forwarded to the headphone jack on the controller regardless of something being plugged in. The Shield Hub can be installed, but the Grid section is not even available as a selection (again, unlike the Portable, which gets into the grid stuff but segfaults mediaserver). If anyone has reverse engineering or research skills, help would be much appreciated in smoothing out the problems here.
The North American LTE build is reported to work as expected on the Rest of World LTE model. I have not finished research on what all the stock build differences are. But it should be safe to use the build on either model.
Installing now, I'll let you know. I appreciate the build, I really think this tablet would benefit Cyanogenmod. But they all have locked up the touchscreen for me. Only comes back after reboot.
Really appreciate you putting this together. Can't wait to get CM on my Shield!
pjim said:
Installing now, I'll let you know. I appreciate the build, I really think this tablet would benefit Cyanogenmod. But they all have locked up the touchscreen for me. Only comes back after reboot.
Click to expand...
Click to collapse
Let it boot up and just basic set up, very smooth and fluid, just like CM should be. I let it go to sleep a half dozen times and it woke right up, touchscreen and all. So far so good.
I'm still getting touch fail, but it's getting better. It took almost a day before it started. But after turning the screen off and on a few times it comes back. Haven't had to reboot yet.
Sent from my SHIELD Tablet using XDA Free mobile app
danjull said:
I'm still getting touch fail, but it's getting better. It took almost a day before it started. But after turning the screen off and on a few times it comes back. Haven't had to reboot yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
But...but the ROM's only been up for 2 hours. It "took almost a day" isn't even possible. Unless I'm missing something, which must be the case haha.
ROM works just fine on the WiFi model, except for obvious (and obnoxious) data indicator in status bar, and mobile network options in settings, any way to just chop those out, maybe in a WiFi build? As like I said it works fine otherwise.
I posted a link of a prior build to some of the other tablet devs yesterday, that's where he got it from.
Yes, this is a build for the North American LTE tablet since that is what I have. I can run off a build for wifi-only, but it will be tomorrow before I get to that. I eventually want to get a unified build of this that will enable the data stuff for the LTE model and hide it all on the wifi model. Shouldn't be terribly difficult, but that's further down the road.
Steel01 said:
I posted a link of a prior build to some of the other tablet devs yesterday, that's where he got it from.
Yes, this is a build for the North American LTE tablet since that is what I have. I can run off a build for wifi-only, but it will be tomorrow before I get to that. I eventually want to get a unified build of this that will enable the data stuff for the LTE model and hide it all on the wifi model. Shouldn't be terribly difficult, but that's further down the road.
Click to expand...
Click to collapse
Awesome to hear
The gps works, took a while for the first lock, but locks in seconds after that. Compass is 180° off, pointing north, indicates south
Alright, here is the wifi only build. I have not tested flashing it since I don't have time right now. But the only difference between this and the lte build is marking it as wifi only and not including the modem libs. Also disregard the day difference in the filename between this and the lte build, it's the same code base. I'll link this in the first post if I get a couple positive comments on it working.
Steel01 said:
Alright, here is the wifi only build. I have not tested flashing it since I don't have time right now. But the only difference between this and the lte build is marking it as wifi only and not including the modem libs. Also disregard the day difference in the filename between this and the lte build, it's the same code base. I'll link this in the first post if I get a couple positive comments on it working.
Click to expand...
Click to collapse
Just got it up and working an tested (doesn't work on MultiROM but I figured as much because Pac doesn't either) and everything seems to work 100% fine.
I've tried to get touch to break after deep sleep with no avail. So for now, for me, it's great! Touch responsiveness is great, and its performance seems to be on par if not better than stock, not that I could get stock to even studder at anything.
Does this ROM support HDMI out, Shield controller and the stylus?
matlear said:
Does this ROM support HDMI out, Shield controller and the stylus?
Click to expand...
Click to collapse
The stylus and HDMI out I can confirm working. The controller I never bought because I owned a Moga PRO before buying the tablet, so you'll have to try that out yourself.
It should work with multirom as long as you have the latest twrp and multirom. Bogdacutu posted those toward the end of his multirom thread. The official releases won't work.
The stylus works and seems accurate, but none of the specific apps are included and I don't know if the pressure sensitive part works. I haven't tried HDMI, but the report above says it works. Once other show stopping problems like the grid and controller stuff is worked out, I'll look into reimplementing console mode. Should be pretty easy. As mentioned in my second post, the controller pairs, but isn't completely working. Like it won't remember the pairing and you'll have to repair on every reconnect.
Steel01 said:
It should work with multirom as long as you have the latest twrp and multirom. Bogdacutu posted those toward the end of his multirom thread. The official releases won't work.
The stylus works and seems accurate, but none of the specific apps are included and I don't know if the pressure sensitive part works. I haven't tried HDMI, but the report above says it works. Once other show stopping problems like the grid and controller stuff is worked out, I'll look into reimplementing console mode. Should be pretty easy. As mentioned in my second post, the controller pairs, but isn't completely working. Like it won't remember the pairing and you'll have to repair on every reconnect.
Click to expand...
Click to collapse
Yes, I was using the latest MultiROM with the latest TWRP.
Also WiFi often disconnects, and stays on "saved" until I reconnect it.
Great news!
Firs of all, thank you for sharing and the team work.
I'm newbie with Android roms but in the past I've compiled and tunned linux kernels (since Linux was 0.9...) I've been playing with cm12 and nvidia sources without success... I've too much to learn...
I ask if this rom is suitable for wx_un_do model (RoW LTE). Anyway, I'm dowloading sources for playing (perhaps to adapt to wx_un_do if necessary and I'm able to...). I would like to help....
One more question... Is it necessary to add vendor directory from nvidia sources... ? How are proprietary (licensed) files managed in the source ?
Thnx a lot again for this work.
PS: Very interesting if we can count with nvidia apps in cm12... it would be the "perfect" scenario :good:
---------- Post added at 06:42 PM ---------- Previous post was at 06:34 PM ----------
BitOBSessiOn said:
Great news!
Firs of all, thank you for sharing and the team work.
I'm newbie with Android roms but in the past I've compiled and tunned linux kernels (since Linux was 0.9...) I've been playing with cm12 and nvidia sources without success... I've too much to learn...
I ask if this rom is suitable for wx_un_do model (RoW LTE). Anyway, I'm dowloading sources for playing (perhaps to adapt to wx_un_do if necessary and I'm able to...). I would like to help....
One more question... Is it necessary to add vendor directory from nvidia sources... ? How are proprietary (licensed) files managed in the source ?
Thnx a lot again for this work.
PS: Very interesting if we can count with nvidia apps in cm12... it would be the "perfect" scenario :good:
Click to expand...
Click to collapse
I think answer to myself about proprietary files...
github.com/ShieldTabDev/proprietary_vendor_nvidia
Is this ok?
Thnx.
Flashed the LTE rom on my Wifi unit. I have been using it since last night and so far so good, no touchscreen issues yet!
Only issue is auto connecting WiFi. I am very happy to finally be rid of the stock ROM lag ☺
nice... ..using SuperPichu's Custom Lollipop Kernel, Kernel for the Nvidia Shield Tablet with this rom no issues so far.!
Gilbot said:
Flashed the LTE rom on my Wifi unit. I have been using it since last night and so far so good, no touchscreen issues yet!
Only issue is auto connecting WiFi. I am very happy to finally be rid of the stock ROM lag ☺
Click to expand...
Click to collapse
Check the thread out, there is a build for WiFi model and it works great, Steel said he'll put it on the OP if he gets enough positive feedback!
{
"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 again, gain contributors. 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 even more and learned a whole lot more.
It has been an awesome learning experience and is still not over! We are still learning every day and continue to move forward. Lastly, we DO NOT accept, nor ask, for donations. We don't believe in that. Everything that is necessary to keep this project going is out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc. We will never ask for a dime. All we do ask, is that you have patience, search, read and try to enjoy the process with us!!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_nvidia_shieldtablet
Flashing Instructions:
- Verify that you're using the latest version of TWRP
- Perform a FULL WIPE as described below if coming from another ROM or a different version of Android
(A full wipe is when you wipe system/data/cache)
- Flash the latest version of this ROM
- Flash recommended GAPPS linked below
- Reboot and ENJOY!!
**If you fail to follow these instructions, please don't bother reporting any bugs**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
Change Log:
Code:
[B]Version 10.0 [/B]
- Initial Release of M
For a detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z[/URL]
Credit and Thanks:
We would like to give thanks to everyone that contributes to the Android community, big or small because every bit counts. Although we can't list each and every contributor within the Android community, we would like to highlight some of the teams and individuals that have made it possible NOT only with just this version of DU but throughout the years because we don't ever want to forget where we came from nor those that have helped us!
That said, on behalf of the DU team we say THANKS to....
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
**If we have left someone or some team out, we apologize and please PM us**
Download Links:
Version 10.0 - http://download.dirtyunicorns.com/f...tablet_6.0.1_20160304-2345.v10.0-OFFICIAL.zip
GAPPS - http://download.dirtyunicorns.com/files/gapps/
WEEKLIES - http://download.dirtyunicorns.com/files/
Frequently asked questions:
The download link is slow, can you provide a mirror?
From time to time, we perform maintenance on our website but we do not authorize any mirrors. Please have patience!
I'm on a TEST BUILD and have this bug, can you help?
Please keep any discussion about test builds in the G+ community!
How can I get Viper4Android working?
Check this thread out https://plus.google.com/+JasonPasch5/posts/6JDRjdL2mKM
Are you coming from a ROM with Layers?
Make sure you remove your 'overlay' folders and perform a FULL WIPE
My battery stats are all messed and reporting the wrong percentage, what can I do?
Stop using another kernel. Do a FULL WIPE and flash the ROM again
Is this ROM CM based or AOSP based?
This ROM is based off AOSP
Does this ROM have layers or the CMTE?
This ROM uses the CM theme engine
Pulse doesn't work with [insert music app]
Check this thread out https://plus.google.com/101146731143183859725/posts/TcSzc61xuVx
I'm getting a FC from the theme chooser, what gives?
This is due to restoring data/apps from Google. Go ahead and clear data and cache for theme chooser and theme provider then reboot you should be good moving forward.
I changed my LCD density and now the navbar looks weird, what gives?
This is currenly an issue that we are aware of and addressing. For now after you changed density reset navbar layout or stay on the stock density.
Other Links:
G+ community - https://plus.google.com/u/0/communities/109738128866939227235
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
Jira (Bug Report / Feature Request) - http://jira.dirtyunicorns.com/
XDA:DevDB Information
[ROM] [SHIELDTABLET] [6.0.1] Dirty Unicorns - Shield Tablet WiFi & LTE, ROM for the Nvidia Shield Tablet
Contributors
danjull
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-11-25
Last Updated 2016-03-05
Reserved
any bugs?
Very good work! Firmware establish good! I really liked the minimalism! Many settings - will study unsubscribe later!
Big question,
to choose from this ROM or before going back to official Shield ROM, does touchscreen works or has a fix on KODI?
Regards
chapas said:
Big question,
to choose from this ROM or before going back to official Shield ROM, does touchscreen works or has a fix on KODI?
Regards
Click to expand...
Click to collapse
I had the firmware TeamEOS. Wipes are made in TWRP and flashed Dirty Unicorns.
Everything works well!
Touchscreen does not work on kodi, like all other non stock ROMs. Other than that touchscreen works fine. Not aware of any other bugs. Working on getting marshmallow proper. Boots up, but sound is a little unstable and video doesn't work.
Hi.. I have problem with my shield tab
Im from Malaysia and i bought the Shield Tab from local online seller but the sim locked with AT&T.
ive tried everything, even contacted AT&T but still nothing...Anyone here can help me..?? Obviously custom rom didnt fix it..
Is there anyway to get it works with my local data/sim..
Everything works flawless, but how to get the controller connecting and working with the tablet? Tried the .zip file from another thread and i still cant connect my controller
pr0jesse said:
Everything works flawless, but how to get the controller connecting and working with the tablet? Tried the .zip file from another thread and i still cant connect my controller
Click to expand...
Click to collapse
Haven't pulled in those functions yet.
Flashed DU with no issues, but Banks Dynamic GAPPS will not flash.
Hands down the best rom for this tablet. Runs smooth as butter, great battery life, and none of the audio issues that plagued all the other roms ive tried. This should be the definitive custom rom for the shield tablet.
nbollinger said:
Hands down the best rom for this tablet. Runs smooth as butter, great battery life, and none of the audio issues that plagued all the other roms ive tried. This should be the definitive custom rom for the shield tablet.
Click to expand...
Click to collapse
would you recommend this rom over the latest BlissPop rom?
supertory said:
would you recommend this rom over the latest BlissPop rom?
Click to expand...
Click to collapse
I havent tried the latest r29 build so I can't comment on it but I gave up on blisspop with r28. I switched to TeamEOS ROM which i liked but development was stopped and then transitioned to Dirty Unicorn.
I fully recommend this ROM. The only issue I have run across is the battery saver option won't allow you to change the color from the default . The color change option doesn't work and apparently the shield cqontroller doesnt work with Kodi. I dont have the shield controller so I can't comment on that either.
I'm using slim zero gapps and not the ones recommended with the rom.
I really hope this ROM takes off.
thanks for the quick reply , going to try this tomorrow
What limitation does this rom have over the official stock rom in terms off functionality and user experience ?
Sent from my SHIELD Tablet K1 using XDA Free mobile app
abati said:
What limitation does this rom have over the official stock rom in terms off functionality and user experience ?
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't seen any limitations at the moment other than the Kodi bug with the shield controller not working with the app. As far as user experience goes, it's been hands down the best I've seen for custom roms on this tablet.
I don't think the NVIDIA functions work at all on this rom, which is what is stopping me from giving it a test drive.
Hopefully the nvidia apps will be integrated into a usable state soon.
as for KODI, does it work with the touch screen? or is it just the controller that doesn't work?
I'm having some issues. I did everything as mentioned. I came from a rooted stock L and after installing DU and the Du TBO Gapps, not 64 bit version, I boot to the home screen and nothing pops up without an error. So format and reinstall again but I can't move forward because I can't access the store to do updates that it says it needs because I can't connect to my wifi. Here is the MAIN problem. When I go to settings to connect to wifi my keyboard won't work. "Unfortunately, Android Keyboard (AOSP) has stopped." How do I fix this?
JohnK71 said:
I'm having some issues. I did everything as mentioned. I came from a rooted stock L and after installing DU and the Du TBO Gapps, not 64 bit version, I boot to the home screen and nothing pops up without an error. So format and reinstall again but I can't move forward because I can't access the store to do updates that it says it needs because I can't connect to my wifi. Here is the MAIN problem. When I go to settings to connect to wifi my keyboard won't work. "Unfortunately, Android Keyboard (AOSP) has stopped." How do I fix this?
Click to expand...
Click to collapse
Flash other gapps than TBO. Slim zero worked for me, but I am sure other ones work too.
Enviado desde mi ALE-L21 mediante Tapatalk
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/d2vzw/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_d2vzw
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod/
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightlies
Created 2015-12-12
Last Updated 2015-12-12
Clean flashed earlier today and seems to be running great. Haven't found anything that doesn't work yet, camera, video, phone calls, GPS all seem to be working fine. Might be the best first nightly for any CM release on this device.
Sent from my SCH-I535 using Tapatalk
So installed Stock Gapps and the 1st nightly. So far so good, though I didn't get any of the stock CM software like messaging and the browser.
The default google camera gave me the typical "camera has failed" error that I got non stop on 12.1. My solution was always going with Open Camera. Never had issues but in a blue moon.
Any clue why?
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Shakes The AssClown said:
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Click to expand...
Click to collapse
I remember CyanogenMod said a dirty flash from 12.1 is possible, but just not tried it yet
Do we need any special version of TWRP to flash this for 6.0?
Samsung.Galaxy.S3 said:
Do we need any special version of TWRP to flash this for 6.0?
Click to expand...
Click to collapse
Nope, flashed it with the latest twrp image from their site on my old s3 and it booted up just fine
Sent from my SCH-I545 using Tapatalk
So what exactly is working right and what still needs tweaking? Is this a daily driver at this point?
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
All Hail to @invisiblek!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pogeymanz said:
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
Click to expand...
Click to collapse
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Master Cylinder said:
All Hail to @invisiblek!
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Click to expand...
Click to collapse
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
pogeymanz said:
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
Click to expand...
Click to collapse
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Master Cylinder said:
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Click to expand...
Click to collapse
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
pogeymanz said:
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
Click to expand...
Click to collapse
I used 11/25 which didn't need the zip and have just kept going.
Here's the new changelogs for CM13 builds: http://www.cmxlog.com/13/d2vzw/
Thanks to invisiblek and CM Team for keeping us current!
Great work!
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invisiblek back in the d2 saddle. Thanks!
The d2vzw must have 9 lives because this is gonna make it last quite awhile longer!!
Let's give it up for @invisiblek once more!
Darn! Gif animation doesn't work on the XDA phone app.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invsiblek back in the d2 saddle. Thanks!
Click to expand...
Click to collapse
Mine seems to do better in battery saving mode than the other 2 - puts my address across the street but the dot is next door.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps?
Click to expand...
Click to collapse
I haven't tried it while driving, but I've used it while walking, biking, and hiking. I have no idea what the difference is, but GPS is flawless on MM whereas I couldn't get a lock since KK. I usually get GPS fix in ~30-40s to ~5m accuracy. [[EDIT: That's actually in GPS only mode.]] My experience is that Mapquest is better for handling navigation purposes than Maps. Idk. Personal preference.
I follow in the footsteps of those before me, and hail the mighty invisiblek!
does anyone have a list of what currently doesn't work? I accidently flashed this when doing the weekly updates..
From what i noticed when just quickly messing with it..
Video Camera did not work (said couldn't access camera)
Front Facing camera froze (took picture but then would not let me click anything)
{
"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"
}
Disclaimer
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.
Extra Information
Builds are released for both H830 and H850 variants
To gain all of Tesla ROM's functionality please flash SuperSU
What's Not Working
NFC
Portable Hotspot
Ambient Display
Video Recording (HAL3 Issue affecting quite a few devices on Nougat)
Always Listening for "OK Google"
BLE (Bluetooth Low Energy)
DT2W
Downloads
H850:
Google Drive
H830:
Google Drive
Device Sources
Common Tree
Kernel Tree
H850 Tree
H830 Tree
Ground Zero ROMs Google+ Community
Google+
ROM Permissions
I got sole permission to build Tesla for the LG G5 from Martin (GZR Team)
Who is ConquestDevTeam?
ConquestDevTeam consists of three developers, myself (King_lilrowrow), Rashed97 and Drsn0w.
Together we work on bringing customs ROM's to the LG G5!
After a few hours thinking it over, i've decided to call it quits and end support from ConquestDev for this ROM. The commitment and time it takes to maintain two ROM's simultaneously is crazy and I simply don't have the time anymore (I didn't really to begin with but thought i'd try) but college, work and family/friends take up most of my time and the spare time I do have I work on the G5 CyanogenMod tree's and building cm-14.1 for the other thread. Builds from 20161217 will be left active.
My focus is fully on CyanogenMod 14.1 for the LG G5 now, why not check that ROM out?
XDA:DevDB Information
Tesla v3.4 (7.1.1), ROM for the LG G5
Contributors
King_lilrowrow, Conquest Development Team
Source Code: http://github.com/teslarom-n
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader / TWRP 3.0.2-1
Based On: AOSP, Slim
Version Information
Status: Abandoned
Created 2016-12-15
Last Updated 2016-12-20
Code:
RRO Layers & OMS (Theme engine with substratum)
Custimizable QS Tiles
Advanced Power Menu
Status bar, Nav bar and Hardware keys configuration
Animation Control
Dark Mode Theme
Omniswitch
Kernel Auditor
AdAway Built In
Lockscreen Weather
Screenrecorder settings
Plus lots more
The initial bugs I had (RIL not working) I have now fixed.
Clean fresh builds are running now and will be uploaded once they have completed.
Can you flash this over a current cm build?
nima0003 said:
Can you flash this over a current cm build?
Click to expand...
Click to collapse
I wouldn't
nima0003 said:
Can you flash this over a current cm build?
Click to expand...
Click to collapse
A clean flash will be needed if your coming from any ROM other than Tesla.
King_lilrowrow said:
The initial bugs I had (RIL not working) I have now fixed.
Clean fresh builds are running now and will be uploaded once they have completed.
Click to expand...
Click to collapse
What happened to Tipsy?
Tazlo73 said:
What happened to Tipsy?
Click to expand...
Click to collapse
I'd call it a difference of opinion. Out of respect I abandoned that project and will speak no more about it on this thread.
Enjoy Tesla though!
King_lilrowrow said:
I'd call it a difference of opinion. Out of respect I abandoned that project and will speak no more about it on this thread.
Enjoy Tesla though!
Click to expand...
Click to collapse
OK, understandable. Tesla it is.
Initial H850 build is ready to download!
Tesla 20161216 build for H850 is ready to be downloaded!
Change Log:
- Initial Build
H830 build to follow shortly!
Is Tesla based more on Slim than AOSP, compared to that other Rom you were working on recently?
lordodin912 said:
Is Tesla based more on Slim than AOSP, compared to that other Rom you were working on recently?
Click to expand...
Click to collapse
Tesla is based on AOSP, Slim.
Initial H830 build is ready to download!
Tesla 20161216 build for H830 is ready to be downloaded!
Change Log:
- Initial Build
Enjoy!
Going to flash this right now.? Thanks
Sent from my LG-H830 using XDA-Developers mobile app
King_lilrowrow said:
Tesla 20161216 build for H830 is ready to be downloaded!
Change Log:
- Initial Build
Enjoy!
Click to expand...
Click to collapse
Thanks! Downloading now and I will let you know how much I enjoy it.
Edit: using proper English lol. Damn kb
Hmmm ... I flashed it, set it up ... just to find it wouldn't charge any more. Tried with 3 different cables that all work in RR, nada.
Rebooted to TWRP and it charges just fine there. So now I'm making a nandroid of it and then restoring my backup of RR.
Hey, at least I tried ... I still don't like OMS, but Tesla looks promising
King, your talent and enthusiasm for the G5 is something I hope we never lose.
Nimueh said:
Hmmm ... I flashed it, set it up ... just to find it wouldn't charge any more. Tried with 3 different cables that all work in RR, nada.
Rebooted to TWRP and it charges just fine there. So now I'm making a nandroid of it and then restoring my backup of RR.
Hey, at least I tried ... I still don't like OMS, but Tesla looks promising
Click to expand...
Click to collapse
Hmm, H830 or H850? I have not ran into this issue myself on 850. I'm typing this as my phone is charging correctly right now.
Tesla kinda depends on having either phh superuser or SuperSU (whichever you prefer) to unlock some of its features, have you flashed either of these? (shouldn't affect charging but its worth checking before looking into it)
Coachmark2 said:
King, your talent and enthusiasm for the G5 is something I hope we never lose.
Click to expand...
Click to collapse
I won't
King_lilrowrow said:
Hmm, H830 or H850? I have not ran into this issue myself on 850. I'm typing this as my phone is charging correctly right now.
Tesla kinda depends on having either phh superuser or SuperSU (whichever you prefer) to unlock some of its features, have you flashed either of these? (shouldn't affect charging but its worth checking before looking into it)
Click to expand...
Click to collapse
H850 and yes, SuperSU flashed together with rom + gapps. Everything else seemed fine, SuperSU prompted for apps like it's supposed to, I even installed Substratum and 2 themes
But neither the wallcharger (quickcharge) nor the USB docking station or another USB cable got it to charge at all. I was down to 60% (from full when I started), so I didn't want to take any more chances. Rebooted to TWRP and it charged fine there. So I restored my nandroid and the phone is fully charged again now. No idea if it was kernel issue or something else
I'm sure it will get sorted, but I've decided I'm staying on M anyway ... at least until N has CMTE. It was fun looking at a new rom for a few hours, but I just miss my "proper" themes too much :angel:
You do a great job no matter which rom you cook - thank you
Nimueh said:
H850 and yes, SuperSU flashed together with rom + gapps. Everything else seemed fine, SuperSU prompted for apps like it's supposed to, I even installed Substratum and 2 themes
But neither the wallcharger (quickcharge) nor the USB docking station or another USB cable got it to charge at all. I was down to 60% (from full when I started), so I didn't want to take any more chances. Rebooted to TWRP and it charged fine there. So I restored my nandroid and the phone is fully charged again now. No idea if it was kernel issue or something else
I'm sure it will get sorted, but I've decided I'm staying on M anyway ... at least until N has CMTE. It was fun looking at a new rom for a few hours, but I just miss my "proper" themes too much :angel:
You do a great job no matter which rom you cook - thank you
Click to expand...
Click to collapse
Glad you liked it minus the issue you ran into, I've noticed with CyanogenMod/Tesla/RR that having two ROMs one active one nandroid you stumble into issues. As when you format in TWRP then flash Tesla for instance you more likely to have a cleaner and more stable experience, of course not everyone wants to start from fresh again.
If you decide to come back to Tesla try what I said above and I can guarantee you that you won't have that charging issue.