{
"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
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"
}
Evervolv is a free, community built distribution of Android 4.1 (Jellybean) which greatly extends the capabilities of your phone.
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.
*/
im on freenode #onev-dev a lot so if you want join me there.
Rom Installation:
Wipe Data, Cache, and system (optional but recommended, this will be the first question if you have FCs or random reboots)
Flash the ROM
Extract boot.img from zip file and run command "fastboot flash boot boot.img"
Flash GApps
Reboot into the system (first boot will take several minutes)
Download
GApps
Discussion Thread
Screenshots
Changelog:
Code:
For an updated changelog look here http://review.evervolv.com/#/q/status:merged,n,z
2012-11-3
Original upload
Working:
-Camera
-Sound
-Phone calling
-Data
-SMS
-MMS
-Wifi
-Charging LED
-Bluetooth - Thanks Maxwen
-Camcorder - Thanks Maxwen
Broken: (In order of importance)
Headphones
Donations: Ok, so im not the type thats going to say "if you donate you will get special access." (yes i got asked this already, which is the point of this writing) Sorry, just not my style. Not trying to make money. But donations are welcome. Maybe I will get to work more on it if I can take the wifey out for dinner . You will get your name in the 2nd post under donated. Also, if you do donate please pm me here with transaction id. That will make it where i can confirm your donation and add you to the list on donators. Thanks for all you guys support. Link in signature
Thanks:
Evervolv team. Obviously
preludedrew - For helping a lot
Lloir - For listening to me ***** and helping
Maxwen - For the Bluetooth and Video Camera fixes
simonsimons34 - For maintaining while I was away and A LOT of kernel help
Placeholder
jmztaylor said:
Click to expand...
Click to collapse
Do I download the nightlies or stables? I'm confused. And which exact file?
brandon1212 said:
Do I download the nightlies or stables? I'm confused. And which exact file?
Click to expand...
Click to collapse
Basically its up to you. But generally if you want a known working ROM use stable. If you are willing to take a chance something may be broken but be more up to date then choose nightlies
Sent from my PK7630000 using xda premium
MMS is not working. Tried using wifi and data, just keeps saying "sending"
Finally JB with working camcorder! You are my hero, man! Do you want bug posts in this thread, or do you have a dedicated topic elsewhere?
dafzuka said:
Finally JB with working camcorder! You are my hero, man! Do you want bug posts in this thread, or do you have a dedicated topic elsewhere?
Click to expand...
Click to collapse
Maxwen fixed it, I was just the first one to post a rom with it working. Its coming to all others too on next release.
Be sure to rape his thanks button for that
What more does the nightlies offer than the stable? I can deal with things being broken.
brandon1212 said:
What more does the nightlies offer than the stable? I can deal with things being broken.
Click to expand...
Click to collapse
Evervolv is still being actively dev'd on. But its a lot more tame than CM. New features are added constantly.
But there is always a chance that a system change could effect this device. So thats why i gave the caution with nightlies.
Headphones is all. Gave this ago the second it was uploaded. *Stalker Status*
Awesome job.
I wiped everything, flashed stable and gapps, booted in to bootloader, flashed the boot.img that was in the zip, and I flashed your OneV Kernel. Its not booting
edit: I fixed it. I flashed jellyboot.5 and it booted in 1 minute.
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
when unlocking after swiping, it shows a red box outline on all sides of the screen. any ideas what that could be?
brandon1212 said:
I wiped everything, flashed stable and gapps, booted in to bootloader, flashed the boot.img that was in the zip, and I flashed your OneV Kernel. Its not booting
edit: I fixed it. I flashed jellyboot.5 and it booted in 1 minute.
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
when unlocking after swiping, it shows a red box outline on all sides of the screen. any ideas what that could be?
Click to expand...
Click to collapse
The boot.img in the zip has been confirmed to work by multiple people. So im not sure why you had and issue with it.
The red box is something that just arrived. I will look into it
MMS not working for me. Says "sending" and "downloading" but it doesn't work or send for any of them.
served24 said:
MMS not working for me. Says "sending" and "downloading" but it doesn't work or send for any of them.
Click to expand...
Click to collapse
are you on 3G or wifi? If on wifi disconnect
I came from cna and it was okay, a few graphical glitches. But this is smoother, the only thing is the red box. Other than that, thanks for a great ROM (;
jmztaylor said:
are you on 3G or wifi? If on wifi disconnect
Click to expand...
Click to collapse
i'm on data and i'm trying to send one and its not sending. keeps saying "sending"
served24 said:
i'm on data and i'm trying to send one and its not sending. keeps saying "sending"
Click to expand...
Click to collapse
well one, get off wifi for mms. it doesn't work over wifi. secondly the wrong apn is in there so it doesn't work even on 3g right now
jmztaylor said:
well one, get off wifi for mms. it doesn't work over wifi. secondly the wrong apn is in there so it doesn't work even on 3g right now
Click to expand...
Click to collapse
that probably explains it. I'm using 3G. Is there anything i can do right now?
served24 said:
that probably explains it. I'm using 3G. Is there anything i can do right now?
Click to expand...
Click to collapse
https://dl.dropbox.com/u/28491940/apns-conf.xml
you can download and push it to /system/etc/ or use root explorer. that should fix it. if not browse to /data/data/com.android.providers.telephony/databases and delete the two telephony files. reboot and should be good to go. Or just wait till tonights nightly and it will work then
jmztaylor said:
https://dl.dropbox.com/u/28491940/apns-conf.xml
you can download and push it to /system/etc/ or use root explorer. that should fix it. if not browse to /data/data/com.android.providers.telephony/databases and delete the two telephony files. reboot and should be good to go. Or just wait till tonights nightly and it will work then
Click to expand...
Click to collapse
how do i download it?
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
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.
{
"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"
}
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.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We 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) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device 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.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Credits:
Huge thanks to everyone below, without whom this would have not been possible.
* rcstar6696 (and everyone else who helped with the shinano bring up - these guys are the best)
* SpiritCroc
* Myself5
* The entire CarbonROM team
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z1
Contributors
drakonizer
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP + CAF
Version Information
Status: Alpha
Created 2017-12-25
Last Updated 2018-05-22
CHANGELOGS:
All changes can be tracked here:
https://blog.carbonrom.org/changelog
You can find the changelog prior to official builds below.
Official Build:
* Fixed Video Recording
* Improved RIL for C6903 devices
14/04/2018:
* Fixed Camera
* Fixed RIL and mobile data (on C6902 at least)
* Enforcing SELinux + user build
* Fixed Bluetooth
23/01/2018:
* Fixed audio
* Fixed thermanager
24/12/2017:
Initial Release
BUGS:
* Connecting to data for C6902 devices is buggy (read FAQ).
* NFC may or may not be broken (I cannot test it as my device does not have the NFC plate).
FAQs (Please read before posting questions):
Q: Does the ROM support OMS and theming with Substratum?
A: Yes it does! Simply enable "Allow untrusted overlays" from Settings -> CarbonFibers -> Privacy and Security and follow the instructions that follow.
Q: Does the ROM work on C6902 as well?
A: Yes, but you will face a few issues while trying to connect to mobile data. Apparently the way to make it work is by going to *#*#4636#*#* -> Phone Info, change the network mode to WCDMA only, and turn on and turn off airplane mode.
Q: Is the ROM rooted by default?
A: No, please flash your favorite root solution after installing the ROM.
Q: Do I need to make a factory reset before installing this ROM?
A: If you're moving from cr-5.1 official builds to cr-6.1 builds, then a factory reset is recommended. Some have been able to dirty flash their way from cr-5.1 to cr-6.1, but before trying that, make sure you have a backup, in case you're caught in a bootloop. Clean install is ALWAYS recommended. If you face any issues after dirty flashing, clean flash first and see if it's persistent and only then report the bug.
Q: SafetyNet?
A: Sure, if you use Magisk and enable Magisk hide.
Reserved
Nice!
Merry Christmas :victory:
Thanks for sharing carbon rom oreo, I will download and let you know whether audio and nfc work
---------- Post added at 03:41 PM ---------- Previous post was at 03:23 PM ----------
Unable to flash on latest TWRP, any ideas how to fix?
Coming from CarbonROM nougat, i already done wipe /data /system /dalvik-cache /cache
https://drive.google.com/open?id=1fVGP6Be2u5j7T8lpPkeuF_mXmQXxIw6_
miXXed404 said:
Thanks for sharing carbon rom oreo, I will download and let you know whether audio and nfc work
---------- Post added at 03:41 PM ---------- Previous post was at 03:23 PM ----------
Unable to flash on latest TWRP, any ideas how to fix?
Coming from CarbonROM nougat, i already done wipe /data /system /dalvik-cache /cache
https://drive.google.com/open?id=1fVGP6Be2u5j7T8lpPkeuF_mXmQXxIw6_
Click to expand...
Click to collapse
Try to install advanced kernel img via fastboot. Then reboot. In the kernel is twrp 3.1 included. Then you're able to boot into that recovery. Wipe all and try again to flash
MIcHiJK said:
Try to install advanced kernel img via fastboot. Then reboot. In the kernel is twrp 3.1 included. Then you're able to boot into that recovery. Wipe all and try again to flash
Click to expand...
Click to collapse
same issue
miXXed404 said:
same issue
Click to expand...
Click to collapse
Okay strange. When nothing helps try to start from the bottom and go back to stock. I will also test this rom later to check, if it's working on my third party screen.
Reflashing stock, flashing twrp again doesn't help, still same issue, something is wrong with carbon rom oreo zip
@miXXed404 update your recovery in this version https://androidfilehost.com/?fid=745425885120742869
https://forum.xda-developers.com/showthread.php?t=2522762
in any case follow the XDA link to resolve the error!
Merry Christmas!
Hansars said:
@miXXed404 update your recovery in this version https://androidfilehost.com/?fid=745425885120742869
https://forum.xda-developers.com/showthread.php?t=2522762
in any case follow the XDA link to resolve the error!
Merry Christmas!
Click to expand...
Click to collapse
Flashing recovery that you provided does not help, still same issue persist, also there is no lines in updater-script thats checking for specific device
thankyou so much....
Nevermind,somehow i managed to flash it,first impressions.. working better than nougat, at first boot up it heated up a lot, i can't enable NFC in settings, so i can't even test it, battery is draining pretty quick, gapps is working, audio is not working , i'm gonna use it for few days, maybe i will find more bugs.. and please fix thermal in this rom, 81c cpu 44 battery and still all cores is enabled on max frequency 2150mhz
miXXed404 said:
Nevermind,somehow i managed to flash it,first impressions.. working better than nougat, at first boot up it heated up a lot, i can't enable NFC in settings, so i can't even test it, battery is draining pretty quick, gapps is working, audio is not working , i'm gonna use it for few days, maybe i will find more bugs.. and please fix thermal in this rom, 81c cpu 44 battery and still all cores is enabled on max frequency 2150mhz
Click to expand...
Click to collapse
I have no issues of battery draining on my end. Nor did I face heating issues. My phone went to deep sleep and drained less than 1% an hour. Maybe you should just let it settle down for a few days and see if it helps.
If not, maybe it's me not using a SIM card or gapps giving me a better experience.
drakonizer said:
I have no issues of battery draining on my end. Nor did I face heating issues. My phone went to deep sleep and drained less than 1% an hour. Maybe you should just let it settle down for a few days and see if it helps.
If not, maybe it's me not using a SIM card or gapps giving me a better experience.
Click to expand...
Click to collapse
Really? no heating issues? try use 100% of cpu and it should throttle down frequency when it heats up, but it doesn't doing that
i'm only connected to wi-fi and charging, brightness set to 0% no apps in background.... no problems with heating? look at this
https://drive.google.com/open?id=1PMnMLuNsunStZV_Wd-AKXj8uR3FrOGCV
ΤΗΑΝΚ YOU! Merry Christmas!
miXXed404 said:
Flashing recovery that you provided does not help, still same issue persist, also there is no lines in updater-script thats checking for specific device
Click to expand...
Click to collapse
good morning, I saw that you have solved, I still do not flash because of too many bugs and the bug that is present in addition to the other bugs! thanks to the developer for the work done! @drakonizer
o be an alpha, the rom is stable.
some things do not work:
- without audio in calls and player
- root can not be activated
- the phone gets very hot
- the wifi is disconnected every time
- the sim card sometimes detects it and other times it does not
- the gapp can not be installed gives error 20 the twpr
for now just notice those problems .... thanks
rayzo_1986 said:
o be an alpha, the rom is stable.
some things do not work:
- without audio in calls and player
- root can not be activated
- the phone gets very hot
- the wifi is disconnected every time
- the sim card sometimes detects it and other times it does not
- the gapp can not be installed gives error 20 the twpr
for now just notice those problems .... thanks
Click to expand...
Click to collapse
Gapps.. use this, it will work-- https://drive.google.com/drive/folders/16D1ev3XgcjoewlPuafvlheUaqFA15cly
Root.. flash magisk it worked for me
Wi-Fi also works for me
No sim card problems
i agree that phone gets very hot, this rom is not safe to use because of overheating
miXXed404 said:
Gapps.. use this, it will work-- https://drive.google.com/drive/folders/16D1ev3XgcjoewlPuafvlheUaqFA15cly
Root.. flash magisk it worked for me
Wi-Fi also works for me
No sim card problems
i agree that phone gets very hot, this rom is not safe to use because of overheating
Click to expand...
Click to collapse
thanks
gapps work
but I do not get root with magisk 15 and 14 gives me error 1 in twrp
a question the audio works for you?
temperature in 40 degrees and more
{
"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"
}
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.
*/
CherishOS is an AOSP based rom focusing on a Unique UI with many customizations.
Known bugs
- Loudspeaker is loud and creates some echo in calls
- Wifi is known to have lower signal than stock through all custom roms for NB1
- you tell me
Please ensure T-virus-2.0 is installed before attempting to flash this rom! follow this guide here: https://forum.xda-developers.com/t/nokia-8-nb1-full-rom-installation-guide.4349525/
Selinux status: Enforcing
Download
ROM
https://github.com/megafire91/NB1-CherishOS_Releases/releases/
Recovery
TWRP:
https://github.com/log1cs/android_device_nokia_msm8998-twrp/releases/tag/3.7.0_12.0
Flashing instructions
Clean Flash:
1. Take a full backup of both your data and internal storage as it may be wiped.
2. Download the ROM from above link and flash the recovery zip (optional)
3. Download the recovery zip of your choosing and flash it if not already on latest twrp.
4. flash the rom zip and recovery zip again right after the rom zip before rebooting , it will reboot you to recovery automatically in other slot. (optional) cherish recovery included.
5. Flash any mods you may want
6. run factory reset from recovery, or wipe /data and /dalvik if you don't want internal wiped.
7. reboot to system and enjoy!
Installing an OTA (Dirty flash):
1. Download the ROM from above link
2. flash the rom zip and twrp zip (optional) and let it reboot into recovery.
3. wipe Dalvik cache only
4. flash any mods you had previously flashed.
5. reboot to system and enjoy!
Device support:
https://t.me/HMD_Nokia_8
Credits
Me for building the rom
@emufan4568 for the NB1 device and vendor tree, atomix kernel and TWRP.
@Log1cs for his device trees and latest TWRP
@NobodyDbg for always assisting me with build issues & fixes
@CherishOS team for the amazing ROM
@THMSP for T-virus
all users in our telegram groups that helped us contribute and find bugs as well as sent us logs.
if i missed anyone in credits please let me know and ill add you to this list.
coffee:
Pay Marcel Dos Santos using PayPal.Me
Go to paypal.me/marceldossantos91 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
paypal.me
if you do decide to donate, thank you, appreciate it more than you know.
Sources:
CherishOS: https://github.com/CherishOS
Device trees: https://github.com/megafire91
https://github.com/GPUCode
https://github.com/log1cs
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Kasi1906 said:
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Click to expand...
Click to collapse
hey, thank you i am glad you are happy with it, always nice to see things like this, appreciated.
4.2 build is up, happy flashing, changelog in git page
marceldossantos91 said:
4.2 build is up, happy flashing, changelog in git page
Click to expand...
Click to collapse
Thank you for the timely security update! My gratitude is still very high. The ROM works perfectly. So far I have not had any problems.
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
satanvade said:
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
Click to expand...
Click to collapse
Hi, you can follow the guide in the Q & A section linked above or in our telegram support group, but the basic idea is:
Unlock bootloader + critical
Flash Tvirus 2.0, which includes twrp 3.6 already (there is however a 3.7 update available, which supports decryption in A12/13, but 3.6 can flash fine)
Flash the rom
Wipe data
Reboot to system
If you need further support, we are more responsive in our support group
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
guorium said:
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
Click to expand...
Click to collapse
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
marceldossantos91 said:
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
Click to expand...
Click to collapse
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
guorium said:
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
Click to expand...
Click to collapse
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
marceldossantos91 said:
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
Click to expand...
Click to collapse
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
guorium said:
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
Click to expand...
Click to collapse
thanks
marceldossantos91 said:
thanks
Click to expand...
Click to collapse
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
guorium said:
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
Click to expand...
Click to collapse
thank you for the log i will look into it and see if i can resolve it in updated builds
marceldossantos91 said:
thank you for the log i will look into it and see if i can resolve it in updated builds
Click to expand...
Click to collapse
No problema. PE A12 has the same problema. Must be easy to miss.
4.4 build is up, happy flashing
marceldossantos91 said:
4.4 build is up, happy flashing
Click to expand...
Click to collapse
Thank you!
Enjoy
Kasi1906 said:
Thank you!
Enjoy
Click to expand...
Click to collapse
tysm appreciate it
4.6 build is up, happy flashing!