Related
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Follow me on twitter and github for updates, and what's going on right as it happens.
I think i already mentioned this once, but please, follow the instructions below when flashing this rom, for your phone's sake!
Here is my build from 03-15-12
And a mirror
MD5 checksum: 3ca7871541bf1fb5ecba70fd9661baef
Google Apps: HERE
Kernel: FC14
Recovery: Stock
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD... unless you unmount the internal storage
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Once again, follow the instructions below, for flashing this ROM!!!
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data or cache wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Here's a README in my github, that has thanks and whatever comes with a README
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.
EDIT4: Hey, i updated the OP with the build from yesterday, that i built. wasn't really planning on giving it out, but it appears that everyone is already using it, so might as well post the link in the OP. Please, don't ask what's changed, because not much has really changed: for this i wasn't planning on posting it... but oh well, it's out . Enjoy
Unacceptable
There seems to be a significant amount of animosity that permeates throughout the Android related forums. I'm not certain as to why this is, nor do I want to hear any reason for justification; what I do know is that it is unacceptable.
As moderators, we spend more time cleaning up flame & troll posts than working on our own community contributions. Unfounded accusations such as KANG'ing serve to drive away those valued members who try to contribute to XDA ... further lowering the quality of threads and posts on this forum.
XDA is about bringing together folks who have similar passions about mobile technology. I would have expected more maturity and professionalism. Instead, I find a thread full of inflammatory posts ... it is not constructive and serves no purpose.
While the Forum Moderator(s) take time from their busy schedule to effect cleanup and "damage control"; further detracting of this thread once it is re-opened will result in permanent holidays for those involved, rest assured that appeals will be non-negotiable. I would encourage members who have posted in this thread to reacquaint themselves with the forum rules - the best moderation is self-moderation.
Forum rules, please read!
To make sure this is clear from the beginning, and since I had to close the previous thread due to trolling and abuse, there is no kanging go on.
sbrissen and darchstar are and have been collaborating for awhile on this, helping each other out in the true spirit of the community. This thread will remain closed until darchstar is ready to have it opened.
http://twitter.com/#!/sbrissen23/status/178160581851889664
https://twitter.com/#!/darchstar/status/178170605747716096
If you look at the github and commit log you'll see the collaboration going on between the two. darchstar is publishing the builds per an agreement between the two. This is open source and community involvement at it's finest.
Any trolling will not be tolerated.
Just took the plunge and flashed.... No problems with the flash and loving the rom.
Sent from my SPH-D710 using xda premium
Great.
Just want to say thanks Darch loving all the builds
Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming
A HUGE thanks to the XDA community, darchstar, Sbrissen, and Team Rogue for putting out an excellent product on my E4GT!
Sent from my SPH-D710 using Tapatalk
Steady Hawkin said:
Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming
Click to expand...
Click to collapse
+100000000000
coming from a new resident of brix city trying to upgrade from the 309 version to the 311 version blod, forgot I had changed the kernel to the fc07 rouge before nandroiding, stupid me, 35 dollars later and a refurb im back in business
@darchstar, are you wanting us to post bugs/issues here in the thread?
drdrewdown said:
@darchstar, are you wanting us to post bugs/issues here in the thread?
Click to expand...
Click to collapse
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here
darchstar said:
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here
Click to expand...
Click to collapse
cool, did you happen to see my post/everyone else commenting about the volume issue of playing music & receiving a notification of sorts (sms etc) where the volume gets really low until you toggle the levels
it's so easy to duplicate & i've tried looking through logcats but can't find anything particular. should i still pastebin something for you?
edit: i'm grabbing a cable now to capture some logs
&& it appears to only do it via the headphone jack
Anybody know of a vnc viewer that will work with this?
Sent from my SPH-D710 using xda premium
Good job Team, so far so good.. gonna test this out so more..
Thanks so much, been running great, and I could not be happier having darch, sbrissen, steady, and all the other greats on our team working together! Thanks again guys.
I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.
cidica said:
I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.
Click to expand...
Click to collapse
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium
JohnCorleone said:
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
meh that's lame. Oh well guess it's time for a bug report to xda for the app then
everything for me is working decently well using it as daily so i love it
only issue that irks me is the very weak signal
Love it! Better than any Sammy ics leak, and prefer it over anything official even!? Everything looks great and is smooth. Unable to install sprint NBA mobile though as unable to install on any storage seems like. Also, mms is funky sometimes. Have to toggle 4g to fix.
Anybody notice super heavy battery drain between 14%-4%?
Sent from my SPH-D710 using XDA
Fyi to all, the feedback thread was moved to general and I updated the OP with tips made by others.
Here is the link:
[FEEDBACK]Darchstar CM9 ROM *Help,Tips, and Tricks*
http://forum.xda-developers.com/showthread.php?t=1543349
Sent from my SPH-D710 using Tapatalk
Vanir is an AOSP based ROM built to exacting standards with the goal being a high end user experience, over needless features.
Join the Google+ Community for updates, bug reporting, and general conversation
https://plus.google.com/communities/111378032131473754160
Requests for features should be submitted to Gerrit
http://gerrit.vanir.co:8080
Bug reports should be submitted to the vanir community, with the following.
!. Device (using code name - D851, for T-mobile LG G3 - for example)
2. Brief description of how you caused the bug to trigger, and steps to replicate
3. Whether you clean flashed your current build, or dirty flashed (If dirty, over what build)
4. If you are on a different kernel, than what is packaged with the ROM
5. A Logcat, copied to www.pastebin.com
(Tutorial on capturing a logcat http://www.vanir.co/word/diy/capturing-a-logcat/ )
Flashing instructions
Reboot to recovery
create backup of current build
wipe cache and dalvik for dirty. If clean flash (mandatory, if coming from a different rom) wipe system, data, cache, and dalvik
install ROM
install GAPPS
reboot
Downloads
ROM
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/
GAPPS (DHO is recommended, but not mandatory)
http://www.emccann.net/dho/5-Gapps/
Changelogs are on the Nightlies page
You can view the gerrit (linked in the feature submission section) for a more in depth look.
Credits
Lead Developers:
DHO
NuclearMistake
Prime Directive
Images credit to Yanowman
Thanks!!
Awsome thanks
purrbody sonic rukia purrs
Wohoo vanir! :d
Excited to see Vanir here in G3 world, Woohoo is right!
Wish I didn't have to wait till after work to flash...
Thanks Txwolf1980!
Clean install...get Google service error on bootup...black screen. I'll try it again
reserved
seems like alotttt of people having problems on google+ with this ROM
I dont think this ROM is for most people... no density change, no nav bar height, no network traffic, no clock mods,
A.K.A The things we've grown accustom to with 5.0 ROMS already
Im not having any problems, but its too vanilla for me !
Thanks for bringing it to XDA ! The more ROMS the merrier !
Here are some sccreenshots
Post looks good with me. Big thanks for posting!
Just to reinforce, we support about 100 devices so the dev team can usually be tracked in the G+ community if your question cannot be answered by your peers in this xda community.
aaronuser said:
Clean install...get Google service error on bootup...black screen. I'll try it again
Click to expand...
Click to collapse
Google service may be your Gapps package. Did you clean install? And are you still having issues?
yanowman said:
seems like alotttt of people having problems on google+ with this ROM
I dont think this ROM is for most people... no density change, no nav bar height, no network traffic, no clock mods,
A.K.A The things we've grown accustom to with 5.0 ROMS already
Im not having any problems, but its too vanilla for me !
Thanks for bringing it to XDA ! The more ROMS the merrier !
Here are some sccreenshots
Click to expand...
Click to collapse
I'll give you a couple of points, and argue a couple
1. If you're talking about this device, specifically, I've not had any issues, and a single other poster has. That's not much of a sample to work with. In more general terms, most of the issues I've seen have been on older devices (I.E. outdated drivers and modules for kernels, etc)
2. You're right. There aren't a ton of options, even compared to other ROMs. But, that's never what Vanir has been about. It's always been about trying to achieve stabilitly. Function over form, if you will. That could go to your third point, as well (about it being too vanilla). Would I like more features? Sure. We all would. But I want them to be useful, not just checkboxes that spawn forcecloses.
3. Agreed. The beauty of android is something for everyone. And 'the more the merrier' is the rule of thumb.
And thank you for the screenshots. I'll add them to the OP and give you credit. I missed that one.
VanirAOSP and Commotio Android MM 6.0.1 for the SPH-L710
Credits go to Team Vanir and DHO for the development of these roms.
Disclaimer : Use these ROM's at your own risk and please don't blame me if you brick your device . If you are new and don't know what your doing please don't flash these ROMS until you've done your research , read through the thread, and made yourself aware of previous known issues. THIS THREAD IS FOR DEVELOPMENT AND BUG REPORTING ONLY EVERYTHING ELSE WILL BE IGNORED. Use the Q&A thread for questions and other issues.
Note for mods: I am taking over for MonstaDriva, if this thread presents an issue or there is a better way to do this let me know.
This thread will be updated as I remember to add things.
I do not have this device, therefore I can not test any builds. I am also not known in the Vanir/Commotio community yet. This is my first time maintaining a device, I will probably screw up, a lot, until I get practiced at it. Because I do not have this device, I am extremely reliant on bug reports by the community, therefore if you are not reporting a bug all other questions or issues go in the Q&A thread. I REPEAT THIS THREAD IS FOR DEVELOPMENT AND BUG REPORTING ONLY EVERYTHING ELSE WILL BE IGNORED. This is to keep this thread clean so I can keep track of what needs to be fixed.
The following is required if reporting a bug, everything else will not receive a response and the bug may or may not be ignored.
Reporting a bug:
Read through the whole thread. See if bug is already reported
Read through again.
If bug is already reported, provide link to original report, add your logs, and any extra information that expands upon what is missing.
List rom. EG. Vanir or Commotio
List build date
List official or unofficial
Describe issue in detail. All know facts
Steps to reproduce issue
Logs. Any and every log imaginable. Eg. Logcat, kmesg, dmesg, etc.
Read through the whole thread again
Anything else that will help diagnose the issue
If you can satisfy all the above requirements then you may report a bug.
Downloads:
Unofficial: Coming soon
Official Vanir: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/d2spr/
Official Commotio: http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/
GAPPS:
DHO: http://www.emccann.net/dho/5-Gapps/
OpenGapps: http://opengapps.org/
Installation:
Backup
Wipe -- Note: If coming from stock you must wipe the internal storage.
Flash
Gapps -- Note: do not reboot before flashing gapps. This is an issue with how gapps are flashed on android 6. Source
Sources:
Rom: https://github.com/VanirAOSP
Device: https://github.com/VanirAOSP/device_samsung_d2spr
Kernel: https://github.com/CyanogenMod/android_kernel_samsung_d2
Gerrit: http://gerrit.vanir.co:7070
Community: https://plus.google.com/communities/111378032131473754160
XDA:DevDB Information
[ROM][6.0.1][Official]Vanir/Commotio for D2SPR Samsung Galaxy S3 Sprint, ROM for the Sprint Samsung Galaxy S III
Contributors
Lrs121
Source Code: https://github.com/VanirAOSP
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP, CAF Mixed
Version Information
Status: Nightly
Created 2016-05-11
Last Updated 2016-08-28
Reserved
Lsr121 is the new official rom/thread maintainer .
Thank you Lsr121 for doing this . Thread looks great and I appreciate you taking over the official Vanir/Commotio !! Users will appreciate ya too man .:good: I will be asking the mods to close my old thread soon .
MonstaDriva said:
Thank you Lsr121 for doing this . Thread looks great and I appreciate you taking over the official Vanir/Commotio !! Users will appreciate ya too man .:good: I will be asking the mods to close my old thread soon .
Click to expand...
Click to collapse
Good luck with everything!
Looks good. Lrs121, for not having this device, you have definitely done a lot for it. Thanks bro.
I was honestly expecting this thread to explode with comments. Well I've gotten a new wireless card and can begin attempting to push patches if anyone thinks they may be necessary.
Lrs121 said:
I was honestly expecting this thread to explode with comments. Well I've gotten a new wireless card and can begin attempting to push patches if anyone thinks they may be necessary.
Click to expand...
Click to collapse
Vanir run's so good usually that there's seldom any issue even when other devices are having them . You are sort of like the infamous Maytag Repairman Bored for wanting to patch . Sent you a pm .
Anyone install this yet?? Screenshots would be cool...
I JUST reverted back to Wicked X 4.4 because the new 6.0 Roms i've tried (OctOS, AICP) have the exact same issues with phone calls, audio, and especially BT. They're usable, but barely. Takes too long for calls to answer, and it's buggy....after answering, they'll still appear to be receiving a call haha. They're heavily based on CM13. Dunno how much AOSP. If someone had a screenshot of their InCallUI with this ROM that'd be awesome.... if it's different I'd go ahead and wipe 4.4 again to try it.
EDIT
If there's a Q&A thread, I couldn't find it....Im sorry to be so noob but, should I just make a new thread? Again, such noob but, would it make sense to make a thread in QA titled the same as this thread, and link to THAT thread in this thread's OP?
akira6968 said:
Anyone install this yet?? Screenshots would be cool...
I JUST reverted back to Wicked X 4.4 because the new 6.0 Roms i've tried (OctOS, AICP) have the exact same issues with phone calls, audio, and especially BT. They're usable, but barely. Takes too long for calls to answer, and it's buggy....after answering, they'll still appear to be receiving a call haha. They're heavily based on CM13. Dunno how much AOSP. If someone had a screenshot of their InCallUI with this ROM that'd be awesome.... if it's different I'd go ahead and wipe 4.4 again to try it.
EDIT
If there's a Q&A thread, I couldn't find it....Im sorry to be so noob but, should I just make a new thread? Again, such noob but, would it make sense to make a thread in QA titled the same as this thread, and link to THAT thread in this thread's OP?
Click to expand...
Click to collapse
The qa thread is meant to be made but it seems it hasn't auto generated. I plan to make one as soon as I get back to my desktop.
Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
Nice!
Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.
Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.
device boots up? display?
thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress
Maybe change the title with correct spelling of " Unofficial "
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments
@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.
krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app
@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse
Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?
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.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pre-Disclaimer:
THIS IS AN UNOFFICIAL BUILD. The intent is to showcase what is coming up soon. I have been working hard on getting Walleye on a level I consider DD ready, especially from a security side of things.
Please keep any problems with those builds in this thread, I don't accept any bug reports for any other builds other than my HomeBrews.
Disclaimer:
While I make every effort to test these builds as much as possible, I am not responsible for anything that may happen to your device. I ask that you do your part to know your device and know how to recover from problems before you flash or post that you broke your phone!
Support:
I spend an astonishing amount of time developing this device. I can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Ask a question in this forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
Notice:
This build includes GApps for now. We're still working on ways to not prebundle it.
Before you flash, make sure you're on the latest 8.1 stock builds (and bootloader), then flash the ROM in TWRP.
Instructions :
Boot to TWRP
Format Data (If you didn't type YES, you did it wrong!)
adb sideload homebrews.zip
reboot system
(to gain root you must first boot homebrewsROM. Then reboot and to TWRP and install Magisk 1 6.0)
See below
Reporting Bugs:
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
What is your--
Build Date:
Did you--
wipe:
all data?
install gapps when you weren't suppose to?
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!
If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).
### RELEASES ###
https://drive.google.com/drive/folders/1NY1j-eH9demisz5Y05jeIPGXipENo5yK?usp=sharing
XDAevDB Information
LineageOS, ROM for the Google Pixel 2
CarbonROM, ROM for the Google Pixel 2
DirtyUnicorns, ROM for the Google Pixel 2
Contributors
Source Code: http://github.com/LineageOS
Source Code: http://github.com/CarbonROM
Source Code: http://github.com/DirtyUnicorns
Source Code: http://github.com/TresReinosDeLeche
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
### DONATE ###
paypal.me/JacobStermer
Created 2018-02-2
Last Updated 2018-03-Today
reserved
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
I for one am happy to see it.
iluvamk said:
I for one am happy to see it.
Click to expand...
Click to collapse
Me to ? do we need to flash twrp after the ROM like on pixel 1?
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
Archangel said:
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
Click to expand...
Click to collapse
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Let us know how it goes brother.
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
right now i am getting FC on Camera APP, X Google, Ok Google, and T Google something. My computer just crashed building the potential fix.
Ryche666 said:
boot to twrp.
wipe all data
adb push lineageos
reboot to bootloader
boot to twrp
adb push magisk
reboot to system.
right now i am getting FC on Camera APP, X Google, Ok Google, and T mobile something. My computer just crashed building the potential fix.
Click to expand...
Click to collapse
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
jasonsamms666 said:
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
Click to expand...
Click to collapse
Sorry, i got super anxious myself when i finally got playstore, phone, and text messaging working.
Thus the piss poor thread that i copy and pasted from taimen's lineage.
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Ryche666 said:
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Click to expand...
Click to collapse
FWIW this is what's been done with the Essential Phone.
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
I was the same way. A **** ton of reading and a lot of PMing. It is pretty simple when you get the hang of it. This early in the game you get to see the codes that attract you to certain roms or kernels.
Right now i just need to make sure it is stable before i work on the kernel or choose what rom i am gonna stick with.
NadavCE said:
FWIW this is what's been done with the Essential Phone.
Click to expand...
Click to collapse
That's what i heard. If i knew that last weekend we would have had that much sooner.
Awesome, glad to see some work
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Chronzy said:
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Click to expand...
Click to collapse
Can you share the complete steps and details on how you flashed it? Thank you!
infamousvincci said:
Can you share the complete steps and details on how you flashed it? Thank you!
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.