Code:
/*
* Your warranty is now void.
*
* Neither me nor Resurrection Remix nor anyone else mentioned in this post is
* 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.
*
*/
This is my first ROM built with help from jdelano who used to build this ROM for these devices.
Even if this is quite new to me, issue reports are welcome and I'm trying to help as good as I can.
About Resurrection Remix
Resurrection Remix has been based on CM, slim, omni and original Remix ROM builds creating an awesome combination of performance, customization, power and the newest features while being completely open source.
Features
Statusbar customization (Centered clock, custom battery icon, battery bar,...)
Navigationbar (activate navigation bar, rearrange buttons, custom actions,...)
Hardware buttons customization
Lockscreen customization (shortcut custumization, hide emergency button,...)
Gestures
Quicksettings customization
Interface customization (custom dpi, ambient display,...)
Themes (OMS support)
and many more
Changelog
Known issues
MHL out to TV doesn't work
Mentioning issues
Before mentioning issues, please make sure you followed the instructions mentioned below and you're not using custom kernels or mods modifying system files.
Installation instructions
First install/Clean Flash
Download latest ROM zip file
Download GApps
(Download latest TWRP and install it) - T900 users need to use a special TWRP linked in Downloads section
Reboot into recovery
Make Nandroid backup (recommended)
Wipe Data, System and (Dalvik) Cache
Flash ROM and GApps
Reboot
Enjoy Resurrection Remix!
Update/Dirty Flash
Download latest ROM zip file
Reboot into recovery
Make Nandroid backup (not needed in most cases, but better to be save if something went wrong)
Flash ROM
Reboot
Enjoy the update!
Downloads
ROM
P900 (v1awifi)
T900 (v2awifi)
TWRP
P900
T900: Your TWRP is linked in this thread under Installation - step 3
Open GApps
Download latest GApps from Open GApps official website using
Platform: arm
Android: 7.1
Variant: the one you prefer (I use stock without issues but on another device I had issues with GBoard settings force closing)
Credits
RR Team
CyanogenMod/LineageOS Team
OMNI Team
SLIMROMS Team
Substratum Team
Open GApps Team
Exynos5420 Team
and of course all the contributers, supporters and donators
Sources
P900 device sources
T900 device sources
RR sources
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just updated my phone to 5.8.2 last night. It'll be interesting to run the same ROM on both of my devices. Thanks for your contribution...I look forward to trying it out this evening.
So happy that you took this on @Schrolli97 I love RR and our device deserves the best in software, it's really that good. Best of luck
New builds are up and linked in OP.
Next update should show up in OTA updates
Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).
shonkin said:
Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).
Click to expand...
Click to collapse
I had this some time ago. I moved all data to my PC. Formatted the card in my tablet and moved it all back. Now it works fine
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Anybody wants great sound on your tablet? Tested by me. Works great. I installed the whole choobang. Damn! I have bass on my speakers now!
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Schrolli97 said:
New builds are up and linked in OP.
Next update should show up in OTA updates
Click to expand...
Click to collapse
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).
Gary_O said:
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).
Click to expand...
Click to collapse
Very happy that you guys enjoy this. Hope that I can contribute to making this device even more awesome
Thanks for mentioning this fix. Just added it to the OP :highfive:
Let's see if I can get it to work that you don't need to edit build.prop anymore.
shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" uu. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.
shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
Same issue to me, it report SD card (exfat) corrupted after upgrading to 2/28 version.
Schrolli97 said:
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.
Click to expand...
Click to collapse
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.
shonkin said:
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.
Click to expand...
Click to collapse
If changing build.prop values doesn't work, I don't think there's a way to revert this from your end. I don't even know if (i.e. how easy) I can revert it. So I guess I will read about it. It may take a while, though, as I'm quite busy for the next week.
Deathly Adiutor is an altered version of kernel Adiutor that only works with devices using the processor of our tablet. I don't think the note 4 is one of those devices. Also it probably has another maintainer who's maybe just not including it in the ROM.
I guess sdcardfs is also just included by lineage maintainers whose device drivers I'm using. Though, I didn't have enough time to check, yet.
I'll keep my eyes open. Will tell you when I know more.
New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
For the next update I'll target the SD card if the problem is still present.
Schrolli97 said:
New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
Click to expand...
Click to collapse
Thanks, and thanks for incorporating the non-rotating lockscreen. :good:
I have noticed a problem with Substratum with this 20170317 version of the RR ROM. Substratum is running in Legacy mode, and not OMS mode. On the previous version 20170228 RR ROM, Substratum was running fine in OMS mode. I did a full wipe / clean install of the 0317 ROM. I have installed the same version of Substratum (604) on both 0228 and 0317 ROMs.
Per some other forum suggestons, I tried force closing Substratum, then clearing the data and cache for substratum and reopening it. Still in Legacy mode. Anyone else experiencing this?
Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices
JodyBreeze901 said:
Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices
Click to expand...
Click to collapse
I have not experienced any Bluetooth issues. Although so far only connected to my Mpow bluetooth headphones, worked first time.
Alrighty then.......looks like it's time for a clean install
Sent from my SM-N920C using Tapatalk
I dirty - flashed the 0317 update, and I wasn't going to say anything... But since someone else clean-flashed and has the same problem with substratum, I decided to post.
It is running in legacy mode, and isn't applying anything. I've cleared data on substratum, disabled/rebuilt the themes, and uninstalled all/reinstalled all. Of course, the tab has been rebooted in between many times.
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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.x (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Githubs:
Andromadus
CyanogenMod
Rukin5197
Mustaavalkosta
Changelogs:
BBQLog
CM Gerrit
CM Google+
Github (see above)
Donations:
codefi.re (use the donation button at the bottom of the page)
Mustaavalkosta
Rukin5197- (Use "Donate To Me" underneath my avatar")
Flashing Instructions
Fresh installation instructions:
Download Nightlies
Download gapps (goo.im/gapps)
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-primoc.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot into bootloader
fastboot flash boot boot.img (Grab the one from the ROM zip)
Reboot and enjoy.
Update installation instructions:
Download Nightlies
Put the file on SD card.
Reboot to recovery.
Format /cache
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-primoc.zip
No need to flash gapps as CM backuptool script should take care of them.
Reboot and enjoy.
Status
Not working (In order of importance):
- 5mp Camera/720p Video Recording (On Native camera app)
- Lockscreen glitches and random reboots upon unlock
GooManager Support
My ROMs now have GooManager OTA support, so when I release a new update, it will tell you via notification. All you need to do is go into Play Store and download the GooManager app and everything will take over from there.
Q&A:
Q: I have not read the OP, but I have this issue
A: If it is already listed in the OP as an issue, please don't add to the thread. Read first por favor
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: How about them Ravens right guys?!.
A: Leave.
rukin5197 said:
Guys don't download the latest build just yet. I'm still figuring out the kinks
Click to expand...
Click to collapse
Credits:
simonsimons34 for the kernel
beyond for getting it booted/fixing a lot of things
Lloir for helping as well
jmz for the device tree start
CyanogenMod team
sellers86 for helping me pass a very tedious error
|0xD34D| for basically mentoring me
Rohan32 for giving me all his findings
Andromadus/CodeFireX guys for giving me bases and advice
Mustaavalkosta for the local_manifest.xml
Changelog:
Code:
[B]2-10-2013-[/B] Back to the CM10.1 base, Fix native camera app, now better performance/stability
[B]2-8-2013-[/B] New Andromadus base. Fix Camera/Camcorder/PlayStore
[B]2-5-2013-[/B] New PMEM kernel,
[B]2-4-2013-[/B] First ION build, updated OP
[B]1-27-2013-[/B] WiFi Fixed
[B]1-25-2013-[/B] Initial Release
Can somebody please confirm that WiFi is broken? I need to be 100% positive
Thank you Rukin, your a beast... Backing up my SD right now. will flash in a sec. and let you know about WIFI.
Edit:
No just sits at turning WIFI on. very smooth though, i like the statusbar and transitions.
rukin5197 said:
Can somebody please confirm that WiFi is broken? I need to be 100% positive
Click to expand...
Click to collapse
confirmed.....WIFI borked....I'm gonna flash evervolve kernel just to see what happens....
WiFi is confirmed working in the latest nightly.
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
jcru53 said:
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
Click to expand...
Click to collapse
Flash the boot.img I provide in the thread please
Flashed provided boot.img and SD problem went away, but still no wifi. Attached logcat.
jcru53 said:
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
Click to expand...
Click to collapse
same here
x3reme85 said:
same here
Click to expand...
Click to collapse
LOL I'm so sorry guys, I've been holding out on your guys
I forgot to put in beyond's wifi modules. If any of you guys have beyond's builds, just take his /system/lib/modules and put them in yours. I'm going to put them into the build for the next release.
Sincere Apologies
This is a beautiful piece of work, Rukin.
I have encountered a slight annoyance and I am curious if anyone has experience with this but last night, when I went to search for the update, it was unable to find it. I originally did this through the "About Phone" section of the settings and then tried it through ROM Manager and it didn't even execute a search at all. I've searched the forums to see if this is a common problem since this is my first experience with nightly builds but did not have any luck, likely because of the quite-common key words of my search.
Anyone have some ideas or is this a corner that needs polished still in this build and it isn't special to just me?
blameitonchemo said:
This is a beautiful piece of work, Rukin.
I have encountered a slight annoyance and I am curious if anyone has experience with this but last night, when I went to search for the update, it was unable to find it. I originally did this through the "About Phone" section of the settings and then tried it through ROM Manager and it didn't even execute a search at all. I've searched the forums to see if this is a common problem since this is my first experience with nightly builds but did not have any luck, likely because of the quite-common key words of my search.
Anyone have some ideas or is this a corner that needs polished still in this build and it isn't special to just me?
Click to expand...
Click to collapse
You're going to need to download the GooManager app off the Play Store. I have not made this ROM compatible with the GooManager app though, but thanks for reminding me as I will implement it into the next update
Also for all the people wondering: I have just about fixed AOKP up to date with this ROM, so I will be releasing that today
Okay guys, try the Jan 27 build again and tell me if WiFi works
rukin5197 said:
Okay guys, try the Jan 27 build again and tell me if WiFi works
Click to expand...
Click to collapse
It does not but I am again new at this so I could be wrong. Would I need to flash the boot.img once again as well?
blameitonchemo said:
It does not but I am again new at this so I could be wrong. Would I need to flash the boot.img once again as well?
Click to expand...
Click to collapse
Yes but I would also try a full wipe if it doesn't work. It worked for me
rukin5197 said:
Yes but I would also try a full wipe if it doesn't work. It worked for me
Click to expand...
Click to collapse
Unfortunately I ended up trying a full system wipe and reinstall and it still didn't work. Thank you for your persistence in figuring this out.
I should also mention since it seems relevant at this point that is says my radio is .0521_2 so there is no problem there.
---------- Post added at 05:52 PM ---------- Previous post was at 05:36 PM ----------
blameitonchemo said:
Unfortunately I ended up trying a full system wipe and reinstall and it still didn't work. Thank you for your persistence in figuring this out.
I should also mention since it seems relevant at this point that is says my radio is .0521_2 so there is no problem there.
Click to expand...
Click to collapse
Some other things I have noticed from poking around. It does not allow me to slide the Wi-Fi button to on most of the time. It's not even active EXCEPT for when I go into Advanced and go to specify a region code. Europe is the default so I set it to United States and 60-90 seconds later, I am able to move the Wi-Fi slider to on. It never actually turns blue to indicate it is on, nor does it turn on, but I am able to slide it over. When I go back to advanced and region code, it has reverted back to Europe.
I doubt this helps at all but I know it's good to have as much information as possible.
Okay, try the next download. I'm getting tired of this
rukin5197 said:
Okay, try the next download. I'm getting tired of this
Click to expand...
Click to collapse
Please don't consider this a "needless" post. Rukin you are a well respected DEV and all around good guy here and please don't abandon your efforts due to some off the wall remarks. At that thanks for ALL your contributions thus far sorry if I clogged the thread
blameitonchemo said:
Heh, I don't think anyone blames you for getting tired of it.
---------- Post added at 06:59 PM ---------- Previous post was at 06:53 PM ----------
Is the file up now or is it going up with 1/28?
Click to expand...
Click to collapse
It's 1/27. Although I think a 1/28 build should be up soon because I'm compiling a new build right now
Temasek's UNOFFICIAL CM13.0 BUILDS
{
"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"
}
I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* 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.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
A WORKING version TWRP is required i use Official TWRP 2.8.7.2
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Ensure you’re on the latest vendor image from google - https://developers.google.com/android/nexus/images
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
probably something i havn't found as yet
@temasek
@apascual89 - Developer of nexus 9 temasek dark
@Chainfire
CM Team, CyanogenMod
@DrawnToLife
@zawata
@joshuabg
@craigacgomez
Source
Orignally forked from CyanogenMod
Kernel Source
Device Tree
Temasek Source
Rom Source
Changelogs
https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65562191&postcount=652
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/flounder
GApps - Lollipop 5.1 64 Bit GApps Package
http://opengapps.org/
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to Chainfire
http://download.chainfire.eu/supersu
and one more.
okay rom is now uploaded onto basketbuild. Please follow link in post 2.
i recommend clean flash from another rom as usual. If dirty flashing in the future there is no necessity to flash gapps again, however sometime i do notice supersu goes a bit funny so i would recommend reflashing supersu just to be safe. failing that you can just install it again from market and cause it to update via openrecovery script.
awesome !!! love this rom on my N6 . and now also on my N9 thanks !!!
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
nericollin said:
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
Click to expand...
Click to collapse
Let me know otherwise I will full wipe again and try again myself
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
I know the change log is on the device once you flash the ROM. But I would like to know the changes that have been made besides what is in CM12 already.
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Does LTE work on this ROM?
Alright. Thanks man. I'll just flash it and play around
Edit:: Flashed it. Everything running great. One thing I have been looking for in several ROMs is the ability to put the nav bar on one side while in landscape. I kinda sucks having the bar at the bottom of my screen when it would be much more convenient right by one of my hands whole holding in it landscape. Is that possible here or in any rom yet.
joshndroid said:
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Click to expand...
Click to collapse
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
joshndroid said:
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
Click to expand...
Click to collapse
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
Click to expand...
Click to collapse
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
zawata said:
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
Click to expand...
Click to collapse
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
Click to expand...
Click to collapse
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I was! I figured it must have been that because I remember changing it from F2FS to ext4 when development for the N9 was still in early stages.
The ROM runs amazingly now though! Awesome job! Will report feedback if any issues arise!
andreglud said:
Does LTE work on this ROM?
Click to expand...
Click to collapse
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
joshndroid said:
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
Click to expand...
Click to collapse
So in short, I shouldn't expect it yet?
Not necessarily. I don't have a LTE device to try it on, so I can't just flash it and let u know.
disregaurd, didnt realize there were more replys
{
"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"
}
OmniROM 5.1.1 coming to a xoom near you!
This ROM is for wingray.
Based on:
OmniROM "omnirom-5.1.1"
Kernel ElementalX-Xoom-2.1 by flar2
Download
omni-5.1.1-latest-wingray.zip (md5sum)
Download GAPPS
p75xx-gapps-L-5-6-15.zip
Download SuperSU
UPDATE-SuperSU-v2.XX.zip
Download Deprecated Versions
Browse deprecated
Install
You will need bigPart TWRP and execute the repartitioning as described in
Source
Prerequisites
TWRP 2.8.6.0 BigPart Edition Recovery
The ROM you want to flash
Instructions
Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.
Put TWRP 2.8.6.0 BigPart version and your desired rom on your microsd card.
Reboot into recovery. Flash TWRP BigPart.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
Internal Storage
and wipe them. Don't reboot just yet.
Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". You can now follow the steps below, starting with Flash omni-5.1.1-XXX-wingray.zip.
If updating from older ROM version in this thread, you don't have to wipe anything
If updating from an different ROM, wipe
Dalvik Cache
System
Cache
Data
Flash omni-5.1.1-XXX-wingray.zip
Flash p75xx-gapps-L-5-6-15.zip
Flash UPDATE-SuperSU-v2.XX.zip
Reboot
Wait a long time...
Copy SuperSu and Gapps zip to /sdcard/OpenDelta/FlashAfterUpdate so that they are automatically applied after OTA update. (Internal storage/OpenDelta/FlashAfterUpdate)
Issues
Camera not working
HW Videodecoding not working
HDMI output not working
BT audio not working
Microphone not working
...
Tips'N'Tricks
Show Developer and Performance settings
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number."
Tap it seven (7) times, and *poof*, you've got the developer settings back.
Reduces lagging
Overclock to 1.4Ghz (Performance menu)
Decrease Window/Transition animation scale and Animator duration scale to Animation off (Developer options menu)
Source
https://github.com/Schischu
Thanks
dreamcwli
DJNoXD
bubor
michie
flar2
Adler12
realjumy
rchtk
bigrushdog
Special thanks to everybody who donated, You guys rock!
Code:
/*
* Your warranty is now void.
*
* I will not accept responsibility for any adverse effects to your device,
* including, but not limited to: bricking, dead SD card, bootloops etc.
*
* You mod your device at your own risk.
*/
Please Donate
If you like my ROMs please donate by pressing the "Donate to Me" button below my name on the left side. It takes a lot of my spare time developing these ROMs for the community and every penny is greatly appreciated .
XDA:DevDB Information
[ROM][5.1.1] OmniROM - Wingray - bigPart, ROM for the Motorola Xoom
Contributors
Schischu
Source Code: https://github.com/Schischu
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 2.6.x
ROM Firmware Required: TWRP 2.8.6.0 for BigPart
Based On: OmniROM
Version Information
Status: Alpha
Created 2015-06-30
Last Updated 2015-10-25
Reserved
Changelog
20150726.203925
Fix standby.
20150704.112502
Fix minimum brightness.
Fix setting cpu clock.
20150630.183925
Initial Release
How to build
repo init -u https://github.com/Schischu/android.git -b android-5.1
repo sync
./build.sh wingray clean
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Schischu said:
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Click to expand...
Click to collapse
Awesome! Looking forward to flash. You are unbelievable![emoji12]
fantastic
got an error when trying to flash the gapps though
ApplyParsedPems: lsetfilecon of /system/addon.d/50-hosts.sh to ubject_r:system_file:s0 failed :
Operation not supported o
set_metadata_recursoce: some changes failed
E:Error executing updater binary in zip...
Error flashing zip
p.s. the error seem to be harmless
everything seems to be working including playstore
after changing the animation / transition and co like mentioned in the op i got a pink graphic
flicker -> rebooting fixed that
Wow, this is so impressive. Cannot believe the Xoom is on 5.1.1. Amazing work!
matt4321 said:
Wow, this is so impressive. Cannot believe the Xoom is on 5.1.1. Amazing work!
Click to expand...
Click to collapse
That's the awesome develpment this tablet have... Still don't know how this don't went to front page yet, is amazing what a 2011 hardware can achieve these days
Schischu said:
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Click to expand...
Click to collapse
@Schischu, you are awesome, man.
andPS2 said:
fantastic
got an error when trying to flash the gapps though
ApplyParsedPems: lsetfilecon of /system/addon.d/50-hosts.sh to ubject_r:system_file:s0 failed :
Operation not supported o
set_metadata_recursoce: some changes failed
E:Error executing updater binary in zip...
Error flashing zip
p.s. the error seem to be harmless
everything seems to be working including playstore
after changing the animation / transition and co like mentioned in the op i got a pink graphic
flicker -> rebooting fixed that
Click to expand...
Click to collapse
I just flashed the new build and got the same fail message, but the tablet booted fine and most items are working as expected.
working ok
dolphin browser only works when jetpack is turned off
doesnt go into deep sleep mode yet at least for me
does it work for you guys?
switched launcher to nova - seems to be a little bit faster
overall thanks a lot @Schischu!
Unbelievable! ! Nice job and fixes will b fix very soon I hope so.
I will update very soon till fixes not comes out. @Schischu thanks man for your hard work!
Sent from my SM-G925I using Tapatalk
Amazing work!
andPS2 said:
working ok
dolphin browser only works when jetpack is turned off
doesnt go into deep sleep mode yet at least for me
does it work for you guys?
switched launcher to nova - seems to be a little bit faster
overall thanks a lot @Schischu!
Click to expand...
Click to collapse
Oh you are right. The battery drain is huge, need to investigate.
This is awesome.
Now, I just hope that camera and video works.
The tablet is used by my parents for video calling (Skype etc.) and watching YouTube videos.
If I want to upgrade from omniROM 4.4.2 (February 2014) to 5.1.1, do I not wipe anything at all?
4.4.2 is laggy (as reported by my parents) on that tablet.
Very happy, u r d MAN !
This ROM is great.... Running so smooth
Uploaded small update:
- Fix minimum brightness.
- Fix setting cpu clock.
Great work
So glad there's still xoom love. As it's an alpha issues are expected. Just reporting that I can't seem to install any gapps package. Wiped everything first and formated data to start with a clean device before copying zip files and flashing. Keeps saying "Error executing updater binary in zip '/emmc/Download/p75xx-gapps-L-5-6-15.zip" Thanks again for the great work and I look forward to future updates.
---------- Post added at 06:05 AM ---------- Previous post was at 05:55 AM ----------
Spoke too soon. Not sure how but I managed to get it to work.
Nuny0biznes said:
So glad there's still xoom love. As it's an alpha issues are expected. Just reporting that I can't seem to install any gapps package. Wiped everything first and formated data to start with a clean device before copying zip files and flashing. Keeps saying "Error executing updater binary in zip '/emmc/Download/p75xx-gapps-L-5-6-15.zip" Thanks again for the great work and I look forward to future updates.
---------- Post added at 06:05 AM ---------- Previous post was at 05:55 AM ----------
Spoke too soon. Not sure how but I managed to get it to work.
Click to expand...
Click to collapse
Others have posted with the same gapps report. When this happened to me, I did another clean install and flashed the stock package from http://forum.xda-developers.com/android/software/tk-gapps-t3116347. It flashed perfectly and seems to be working fine.
I have a WiFi only Xoom, but I've never heard of WinGray. Is that all WiFi Xooms? I actually won this Xoom in a Twitter contest. It would be awesome if I could keep it going.
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.0 (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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Hotspot
Flash
GPS
What's not working :
Boot doesnt work all the time (just dont reboot the phone, i guess)
GSIs (Generic System Images) work fine though for some reason
DAC(?)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions :
Download the build
If you dont have a vendor partition yet, create one GUIDE
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Here
H932 Build
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-15.1-treble branch
XDA:DevDB Information
LineageOS 15.1 - Treble, ROM for the LG V30
Contributors
SGCMarkus, rashed97
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-10-03
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that, same for vendor
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/Linea..._base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 22.07.2018
- Updated blobs to H930 V20R
- fixed vibration becoming dull after a while
- all other past changes from normal LOS since last update here
- updated source
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a
- Vibration motor ready for P GSIs
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Does this work on the US998?
A. Hasn't been tested yet. Try it out and report (but make a backup first as always).
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
okaiuz said:
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
Click to expand...
Click to collapse
The reboot problems only occur with the 2 LineageOS builds, not with GSIs (or i was just really extremly lucky, but i doubt that).
On LOS i have a ~20% boot chance (did once 35 boot tries after another...), and on GSIs it boot always like 6 or 7 times after another. Suppose it works there, really unlikely i was that lucky lol
The GSI of LOS by phhuson also works btw (just no double tap 2 wake).
I would actually love to make way more ROMs.... I even had a CrDroid test build once (to check if its only LOS with that problem), but sadly im out of space now.... dont have more space than for LOS :/
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
okaiuz said:
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
Click to expand...
Click to collapse
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
SGCMarkus said:
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
Click to expand...
Click to collapse
i have to thank you again for you work!
Thursday i'll try to partition my v30+ and try your treblelized los!
i give a chance even to phh los, aosp and rr!
i 'll yo know my experience, hoping that you can fix the boot problem!
Regards!
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
donky kong 017 said:
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
Click to expand...
Click to collapse
Use Viper4Android and the predicament is solved.
Nikola Jovanovic said:
Use Viper4Android and the predicament is solved.
Click to expand...
Click to collapse
does viper use the quad DAC. AFAIK no. ATM i use the V30 Quad DAC and Ainur Sauron
As it also counts for this, i will simply refer to my post in the other LOS thread
https://forum.xda-developers.com/showpost.php?p=76536335&postcount=20
you're the best!
tnx to phh also!
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
elba96 said:
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
Click to expand...
Click to collapse
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
SGCMarkus said:
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
Click to expand...
Click to collapse
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
okaiuz said:
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Click to expand...
Click to collapse
Yes, you can still use the non treblelized version
Still working on adding features though, fixing major bugs first ^^
Doblix said:
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
Click to expand...
Click to collapse
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
elba96 said:
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
Click to expand...
Click to collapse
My testers say its ready for daily usage
Couldnt test for battery life yet myself. Didnt have the time to setup everything a new... University life is tough
SGCMarkus said:
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
Click to expand...
Click to collapse
Yes vendor is listed there and I could also format it. I am at university right now and reverted to stock to be able to use it (which can be flashed fine btw.), I will see when I find the time to flash again and post the log here then.
Hi,
{
"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"
}
DarkJoker360 AOSP 10 for Huawei P10 Lite
*** Stable Version ***
About
Code:
[CENTER]Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
This rom has been edited by DarkJoker360 with some additions such as:
* Pixel UI
* Theme picker
* Fruity pebble v2.0
* AospExtended's material icons
* Google bootanimation
[/CENTER]
Working
Code:
[CENTER]* Touchscreen
* Adb / Mtp
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Sensors
* Wifi
* RIL
* Camera
* Android 10 gestures
* NFC
* FP gestures
[/CENTER]
Not Working
Code:
[CENTER]* Offline charge (It works by switching to permissive selinux)
[/CENTER]
Installation
Code:
[CENTER]* you must also have this recovery version installed : [URL="https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890"]TWRP[/URL]
* go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 10 zip
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* flash root(optional)
NOTE: If you are coming from Android 9 flashing root is a MUST DO !
NOTE2: Flash only the Magisk zip linked in this post !
* reboot to System
* reboot to TWRP
* flash gapps (optional)
* reboot to System
* reboot to TWRP
* flash patch_r2.zip
NOTE: this zip is needed for having working NFC and overlays. DO NOT IGNORE IT !
* reboot system
* Enjoy !!![/CENTER]
Update
Code:
[CENTER]* extract the new update of AOSP
* reboot device to : TWRP
* wipe cache & dalvik cache
* reboot to bootloader
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* install gapps(optional)
* reboot to System
* reboot to TWRP
* install patch_r2.zip
* NOTE: this zip is needed for having a working NFC and overlays. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!![/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P10%20Lite/Android-10/"]DarkJoker360 AOSP 10 and patch_r2 fix[/URL]
[URL="https://opengapps.org/"]Gapps[/URL]
[URL="https://forum.xda-developers.com/attachment.php?attachmentid=4882825&d=1574332554"]Magisk Phh v19.3[/URL][/CENTER]
Credits:
@phhusson
@flex1911
@haky 86
@Dil3mm4
@Hami_Do
Please support my work, it's very important! Thanks
DONATIONS
Regards !
XDA:DevDB Information
Android Open Source Project, ROM for the Huawei P10 Lite
Contributors
DarkJoker360
Source Code: [url]http://github.com/DarkJoker360[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2019-11-24
Created 2019-11-24
Last Updated 2020-01-02
FAQ.
Gapps
The recommend package at the moment is this:OpenGapps_arm64-BETA
* Flash this after first boot(with patch zip flashed) and ignore Setup Wizard errors
* Open Play Store and Log in
If you get some errors about Play Services make sure it has full permissions.
Aosp has "ugly" ui
I am sorry for giving you AOSP, hi6250 sources aren't good for other rom actually. As soon as I am able to fix these issues with other custom roms I will provide them, otherwise I will customize it starting from next build by bringing pixel styles and new apps with recent ui look.
NOTE: while inatalling gapps you can may face error 70 insufficient space error, just resize system and if the problem persist flash pico gapps !
Thanks for developer
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Added new gapps and steps for their installation in OP and 2nd post.
NeoPreacher said:
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Click to expand...
Click to collapse
Thanks for reviewing, I forget to include GPS stuff, in next build it will be fixed !
Nfc is almost fixed, we got it enabling at the moment.
For sd card I will take a look.
Here's a working fix to get nfc option (but no tile): https://forum.xda-developers.com/showpost.php?p=81021365&postcount=26
Q looks promising for our chipsets.
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
DarkJoker360 said:
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
Click to expand...
Click to collapse
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
NeoPreacher said:
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
Click to expand...
Click to collapse
Thanks so much for beliving in me, cool stuff is coming really soon. Including a newer decent ui
Great work. .. waiting for new release.
Finally oreo vendor is getting some love and a taste of android 10... Please keep up the good work man... And thank you
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
ghassan haddad said:
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
Click to expand...
Click to collapse
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Copkiller2010 said:
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
Click to expand...
Click to collapse
Tried a factory reset from twrp?
NeoPreacher said:
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Tried a factory reset from twrp?
Click to expand...
Click to collapse
I have a question, the charge of 9watts are working?
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
FranckTheMiner said:
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
Click to expand...
Click to collapse
Same, add to that inability to sign in to Google Services. Were you able to sign in?
ghassan haddad said:
Same, add to that inability to sign in to Google Services. Were you able to sign in?
Click to expand...
Click to collapse
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
FranckTheMiner said:
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
Click to expand...
Click to collapse
The internal storage is working good !