Related
NOTE: This ROM is not mine, I only share you the KK Evervolv ROM to download it and install. If Moderators or Evervolv Team has to delete this post, I will not complain about it.
Hi.
As you see, in Evervolv web page, the KK updates of our N1 are gone. (Don't ask me, I don't know either.)
I have the last update that Texasice made on his OP. On Google Drive.
If you want to download it, this is the link, Gapps now available (The minimal, because in my case, the standard doesn't work)
http://mae.cr/O5xV
The ROM is named "ev_passion-nightly-2014.05.21-squished.zip".
The OP is this one:
http://forum.xda-developers.com/showthread.php?t=2540366
UPDATE:
06/05 I didn't know that the link was private, now is public
06/06 Gapps now available (5-16-pt2_GApps_Minimal_4.4.2_signed.zip)
I uploaded the newest ROM, and the 4.4.3 minnimal GApps for them
[Q&A] [ROM][4.4.4] Beanstalk 4.4.4065 (Unofficial)[9-21-14] *Now with CM11 theme eng
Q&A for [ROM][4.4.4] Beanstalk 4.4.4065 (Unofficial)[9-21-14] *Now with CM11 theme engine!*
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] Beanstalk 4.4.4065 (Unofficial)[9-21-14] *Now with CM11 theme engine!*. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
group mms not working
I have installed almost every aosp/cm based rom on my htc m7ul but have not been able to make group MMS work. for me to be able to receive or send group MMS I have to manually turn on mobile data which means if someone sends me a group MMS, I wont know until I turn on mobile data. I have also installed sense based venom rom on my phone and group mms works fine on that. anyone has any solutions.
I tried to change the APN settings but it didnt help either.
thanks
Good Rom!!
Merry Christmas Guys!!
Google Search has stopped.
just finished flashing Beanstalk 5.0001 20141211
so far working very fine. more stable beta version then other betas. flashed Gapps 5.0 beta 5.
two problems found;
1. I couldn't able to find out the option to enable battery percentage.
2. error "Google search has stopped" is popping repeatedly
otherwise, very good working indeed. thanks for your hard work
"Google play services has stopped"
This annoying message "unfortunately, Google play services has stopped" can anyone help me out.
ROM: beanstalk 5.0.1 dated 20141223
HTC one M7.
just finished installing latest build
just finished installing latest build. will let you know if there is any issues.
HTC One Int. version,
good work. heads up . well done, just waiting for final office build. very smooth, just one time rebooted while closing flashlight. battery timing is also great.
Happy new year to you too
Happy new year to you too. And I'm anxiously waiting foe your latest buid. However, build dated 30 was working very smoothly. Thanks.
titanium backup
I can not get titanium backup to restore system apps without freezing up. I'm using the latest titanium backup and beta supersu. I've tried the stable supersu. I've tried changing app processing mode. I've also tried the Mount namespace thing.
What is the trick?
Reboots almost anytime flash is used.
Force close on omniperformance memory tab always.
Besides those two issues, this rom is solid!
Keep it coming!
When can we expect updates?
sati71 said:
When can we expect updates?
Click to expand...
Click to collapse
No offense mate, but are you going to bump each threads of this forum to ask for ETA's ?
Same answer, read the OP: http://forum.xda-developers.com/showpost.php?p=51390648&postcount=2
I think the text in red and pink mean everything...
In general, developers doesn't appreciate to be under pressure and will not provide ETA's, especially if its mentioned in the OP.
http://forum.xda-developers.com/showpost.php?p=58329339&postcount=28
http://forum.xda-developers.com/showpost.php?p=58329154&postcount=11
http://forum.xda-developers.com/showpost.php?p=58328752&postcount=19
http://forum.xda-developers.com/showpost.php?p=58328977&postcount=3081
http://forum.xda-developers.com/showpost.php?p=58327405&postcount=43168
http://forum.xda-developers.com/showpost.php?p=58310125&postcount=21
installed
Had a clean dirty falsh than clean flash. working very great. when will you add " signal bar on left" feature on it. I m looking forward to it
No problem at all
I haven't have any problems with Google play store. If someone has, should try flashing latest pa_gapps.
however, 31st jan build is running great. there were couple of surprised reboots during night while phone was on standby.
working great
working great thank you.
Downloading new build.
Is there any change log?
Q&A for [ROM][OFFICIAL][Lollipop 5.1][TENDERLOIN] PAC-ROM LP-MR1 Beta-1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][OFFICIAL][Lollipop 5.1][TENDERLOIN] PAC-ROM LP-MR1 Beta-1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Re [Q&A] [ROM][OFFICIAL][Lollipop 5.1][TENDERLOIN] PAC-ROM LP-MR1 Beta-1
ROM: pac_tenderloin_LP-MR2.Beta-1.Unofficial_20150608-111712.zip
Purpose: Feedback
Installed from Touchpad Toolbox V42.
Complete Data Wipe.
HP Touchpad 32GB.
Just about when Google begins to download Apps and Settings during the prompted welcome setup the Touchpad rebooted. The ROM came back up with the WiFi disabled and message about Camera stopped. Re-enabling Wifi locked the tablet hard. Reset and reboot to try Wifi again. The Wifi settings were lost. Re-added the settings and all is well.
Not sure why the panic attack but I figured you might want to know. It's been running solid since.
pac man LP 5.1 boot order
I upgrade from to PAC Man LP 5.1 using twrp and now whenever it reboots default is twrp and not LP in moboot. How can I change the sequence to default to select booting in LP. Many thanks
luvmyi said:
I upgrade from to PAC Man LP 5.1 using twrp and now whenever it reboots default is twrp and not LP in moboot. How can I change the sequence to default to select booting in LP. Many thanks
Click to expand...
Click to collapse
Find the file moboot.default in /boot. Using a root file editor, change the contents from TWRP to:
(note capitalization):
Code:
CyanogenMod
Editing files in /boot is tricky. It may not save it, in which case you'll need to save your file under a different name, delete the original moboot.default file, then rename your saved file as moboot.default.
luvmyi said:
I upgrade from to PAC Man LP 5.1 using twrp and now whenever it reboots default is twrp and not LP in moboot. How can I change the sequence to default to select booting in LP. Many thanks
Click to expand...
Click to collapse
Thanks for quick reply. I tried to change permission using Android Browser and ESplorer with no luck. It won't let me delete boot.default or modify the file. Do I need to delete the file connecting to my PC or using toolbox to delete the boot.default. I was trying to install your version of LP 5.1 with tool box but it didnt like the zero gapp file from op. So I install with TWRP. Now the boot.default read what is left from previous build of LP "everVolv".
luvmyi said:
Thanks for quick reply. I tried to change permission using Android Browser and ESplorer with no luck. It won't let me delete boot.default or modify the file. Do I need to delete the file connecting to my PC or using toolbox to delete the boot.default. I was trying to install your version of LP 5.1 with tool box but it didnt like the zero gapp file from op. So I install with TWRP. Now the boot.default read what is left from previous build of LP "everVolv".
Click to expand...
Click to collapse
I don't know if it's still the case, but in the past you often needed to wipe going between AOSP builds and not. That it says EverVolv seems to indicate it's not been cleaned. In any case, make sure you have root. Hit the build number in "about" 5 times to get developer options and turn on root in the developer options. The root apps should let you modify after that.
Ashenn said:
I don't know if it's still the case, but in the past you often needed to wipe going between AOSP builds and not. That it says EverVolv seems to indicate it's not been cleaned. In any case, make sure you have root. Hit the build number in "about" 5 times to get developer options and turn on root in the developer options. The root apps should let you modify after that.
Click to expand...
Click to collapse
I was not able to install PacMan LPGA 5.1 with toolbox. It said something wrong with the gapps file. How did you install it? With toolbox? I tried with several different gapps in the Op but fail to install with toolbox. So I download the Rom and move to external card intt folder that was created with tool box from evervolv then use twrp wipe system data delvik and cache then install. Will that consist of clean install or do I need to install with toolbox?
Anyway I got the problem fixed using your advise to to turn on root access to App in developer option and install SuperSu then with root browser to change permission and delete old moboot.default and past a new one that I previously copied to a different folder.
Thanks for all the help. Still can not figure out how to install PacMan LPGA 5.1 WITH toolbox?
---------- Post added at 12:16 AM ---------- Previous post was at 12:10 AM ----------
In the about section this rom build said LP-MR1 Beta2. One of your post said it should be LP-MR2 Beta1. I downloaded the 6_08 build after you erase the 06_09 build.
latest 06_15 update
Hi I just update to the 6_15 update and can not log in to Google play? Is there a fix around it or do I have to down grade back to 6_08 version. Thanks
luvmyi said:
Hi I just update to the 6_15 update and can not log in to Google play? Is there a fix around it or do I have to down grade back to 6_08 version. Thanks
Click to expand...
Click to collapse
Downgrade. Read in the development thread.
Just did a clean install with jcs's TPToolbox, installed cleanly and seems to work great! The only thing that's bugging me right now are the volume buttons, since I tend to use my Touchpad in portrait orientation, which makes things a bit confusing XD
jkmartindale said:
Just did a clean install with jcs's TPToolbox, installed cleanly and seems to work great! The only thing that's bugging me right now are the volume buttons, since I tend to use my Touchpad in portrait orientation, which makes things a bit confusing XD
Click to expand...
Click to collapse
You can change them in Settings->PAC Settings
What is a bluetooth WIP? Camera? Cache?
Hi, I upgraded from CM11 to CM12 unofficial tenderloin on Rolands thread to the Pac Rom and it is wayyyy better and wanted to give my praise and thanks.
Don't know what is meant by Bluetooth WIP?
I am unable to pair or find my Bluetooth speakers... Maybe the bluetooth isn't functioning...
I have another soundbar I can try to pair to later this week.
I upgraded to Pac Rom today and registered to the forums.
I am new to the forum world and just wanted to say thanks.
Last weekend I was running CM 11 on Kit kat and now I am up to date with the latest Pac Rom
- cm11-20140705-unofficial-3.4 kernel-tenderloin with gapps kk-20140105
To:
Rolands cm12-20150331-UNOFFICIAL-tenderloin and gapps-lp-20150222-signed.zip
(this crashed all the time for me) I was going to roll back to kit-kat
To:
pac_tenderloin_LP-MR1.Beta-2.Unofficial_20150620-171712.zip
Slim_mini_gapps.BETA.5.1.build.0.x-20150629.zip
Is there anyone working on the camera? OR any idea when that will be working like CM 11 was.
Lastly, I don't believe I removed the cache files after flash? How do I go about doing that with TPTB?
Unless a part of the flash cleared the cache for me? but not sure..
Thanks,
:good:
Trey
Treybone said:
Hi, I upgraded from CM11 to CM12 unofficial tenderloin on Rolands thread to the Pac Rom and it is wayyyy better and wanted to give my praise and thanks.
Don't know what is meant by Bluetooth WIP?
I am unable to pair or find my Bluetooth speakers... Maybe the bluetooth isn't functioning...
I have another soundbar I can try to pair to later this week.
I upgraded to Pac Rom today and registered to the forums.
I am new to the forum world and just wanted to say thanks.
Last weekend I was running CM 11 on Kit kat and now I am up to date with the latest Pac Rom
- cm11-20140705-unofficial-3.4 kernel-tenderloin with gapps kk-20140105
To:
Rolands cm12-20150331-UNOFFICIAL-tenderloin and gapps-lp-20150222-signed.zip
(this crashed all the time for me) I was going to roll back to kit-kat
To:
pac_tenderloin_LP-MR1.Beta-2.Unofficial_20150620-171712.zip
Slim_mini_gapps.BETA.5.1.build.0.x-20150629.zip
Is there anyone working on the camera? OR any idea when that will be working like CM 11 was.
Lastly, I don't believe I removed the cache files after flash? How do I go about doing that with TPTB?
Unless a part of the flash cleared the cache for me? but not sure..
Thanks,
:good:
Trey
Click to expand...
Click to collapse
No active work on the camera. Bluetooth is problematic (WIP-Work In Progress). You clear the caches in recovery before or after you flash, but before you reboot.
Hello, as I understand it, there are no vpn libraries? vpn software not working.
I have been using the 11 July 3.4 ROM on f2fs for the last week and it is the best 5.1 ROM so far. Very snappy. The only downside is the battery drain and the rare doubletap. Thanks for the great work!
Sent from my TouchPad using XDA Free mobile app
Re [Q&A] [ROM][OFFICIAL][Lollipop 5.1][TENDERLOIN] PAC-ROM LP-MR1 Beta-2
ROM: pac_tenderloin_LP-MR1.Beta-2.Unofficial_20150717-190334-3.0.zip
GAPPS: Slim_mini_gapps.BETA.5.1.build.0.x-20150717.zip
Purpose: Feedback
Installed from Touchpad Toolbox V42.
Complete Wipe.
HP Touchpad 32GB.
Touchpad locks solid after about 3 minutes of use after boot. After forced reboot the ROM optimizes all the apps fairly quickly. Wifi settings are lost and have to be re-added. Restore starts download apps. After about 1 or 2 apps the HP Touchpad locks. The cycle repeats. Previously used build pac_tenderloin_LP-MR1.Beta-2.Unofficial_20150620-171712 with Slim_mini_gapps.BETA.5.1.build.0.x-20150620 had worked ok.
---------- Post added at 06:10 PM ---------- Previous post was at 05:13 PM ----------
Re [Q&A] [ROM][OFFICIAL][Lollipop 5.1][TENDERLOIN] PAC-ROM LP-MR1 Beta-2
ROM: pac_tenderloin_LP-MR1.Beta-2.Unofficial_20150719-081052-3.4
GAPPS: Slim_mini_gapps.BETA.5.1.build.0.x-20150717.zip
Purpose: Feedback
Installed from Touchpad Toolbox V42.
Complete Wipe.
HP Touchpad 32GB.
Unlike kernel 3.0 post above, no major problems to report.
Anyone unable to achieve cpu clock speeds of 1728MHz and 1782MHz?
I can only seem to get my cpu speed as high as 1620MHz and it won't go any further.
HighAllegiant said:
Anyone unable to achieve cpu clock speeds of 1728MHz and 1782MHz?
I can only seem to get my cpu speed as high as 1620MHz and it won't go any further.
Click to expand...
Click to collapse
on 3.0 kernel, I can run to 1914MHz, on 3.4, 1782MHz without issue.
shumash said:
on 3.0 kernel, I can run to 1914MHz, on 3.4, 1782MHz without issue.
Click to expand...
Click to collapse
Im using the 3.4 kernel.
Is this using the built in kernel adiutor or are you using a third party program?
HighAllegiant said:
Im using the 3.4 kernel.
Is this using the built in kernel adiutor or are you using a third party program?
Click to expand...
Click to collapse
built-in, but it shouldn't make any difference.
Omni 9.0 has gone official.
See https://forum.xda-developers.com/xperia-xz/development/rom-omnirom-t3912113
This thread is now closed.
---
These builds are UNOFFICIAL! They do not meet the quality standards of the OmniROM project.
Flash at your own risk! You have been warned.
OmniROM 9.0 builds based on kernel 4.9. The internals are mostly the same as my regular AOSP nightly builds.
SELinux: Enforcing (but lax policies right now)
Priv-app permisisons: Enforcing
Dm-verity: Disabled
Latest downloads: sx.ix5.org
Latest semi-stable will be called "-SEMISTABLE".
Install guide: sx.ix5.org (it should be the same as for AOSP).
Changelogs: TBD
Known bugs: See sx.ix5.org
Read the install guide and post #2 before reporting bugs or asking for help!
DO NOT POST HERE FOR FLASHING HELP OR YOU WILL BE REPORTED. Read everything before posting.
Don't make me ask you for logs every time!
Sources:
https://git.ix5.org/felix/omni-repo-update
https://git.ix5.org/felix/local-manifests-omni-kagura
https://github.com/omnirom/android_kernel_sony_msm
https://github.com/omnirom/android_device_sony_common
https://github.com/omnirom/android_device_sony_tone-common
https://github.com/omnirom/android_device_sony_kagura
XDA:DevDB Information
OmniROM for XZ (unofficial), ROM for the Sony Xperia XZ
Contributors
local__hero, oshmoun, humberos
Source Code: https://git.ix5.org/felix/local-manifests-omni-kagura
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 or .192 firmware
Based On: OmniROM
Version Information
Status: Nightly
Created 2018-11-30
Last Updated 2018-11-30
Reserved
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
Reserved
OH MY GOD... Thanks for the great news.. android 9 omnirom for XZ !! Keep up the great work.. in my country there are alot of ppl using xz and following for this !!!!
rezerved
F8331 cihazımdan Tapatalk kullanılarak gönderildi
Just a question, what version of the OEM I should I use? I know that some of them have a few bugs in then, what would you recommend? Latest OEM or a previous one?
DarkPrinciple said:
Just a question, what version of the OEM I should I use? I know that some of them have a few bugs in then, what would you recommend? Latest OEM or a previous one?
Click to expand...
Click to collapse
I'm using the one from AOSP 9.0 thread and it works fine.
Can't play m4a audio files
I'm using omni_kagura-2018-12-06-UNOFFICIAL_NIGHTLY
successfully flashed it with gapps, magisk 18 etc
it seems that with any audio player i can't play my m4a audio files.
+ is this rom the same as your other aosp 9.0?
Please, please do not abandon development
Omni 9 will have update in the future?
robby.pgn said:
Omni 9 will have update in the future?
Click to expand...
Click to collapse
We can only hope and pray.
Update
New build up, 2019-01-23. This is a "user" build, and as usual, runs enforcing SELinux. Getting very close to an official build.
This release is only compatible with the v5 binaries.
In case you need better battery life over fast screen wake-up, you can turn on Deep Sleep in Settings -> System -> Advanced -> Extended Settings and toggle "Disable Deep Sleep".
Please test thoroughly and report the bugs as described in post #2.
Hi guys
Tranks for your work, Is there a list of known errors in this construction?
Thanks.
Need to get home so I can test this. Been on Omni Oreo for awhile. Been waiting for a good pie rom, especially if it's a omnirom
fallingandroid said:
Need to get home so I can test this. Been on Omni Oreo for awhile. Been waiting for a good pie rom, especially if it's a omnirom
Click to expand...
Click to collapse
Hi bro
The last compilation work fluid, but the camera be continue a bad experince, the rest without problem.
Stronger1101 said:
Hi bro
The last compilation work fluid, but the camera be continue a bad experince, the rest without problem.
Click to expand...
Click to collapse
I'm sure there's other cameras besides stock that can be used. Let's hope lol
fallingandroid said:
I'm sure there's other cameras besides stock that can be used. Let's hope lol
Click to expand...
Click to collapse
I tried use Open camera, a better camera, google camera, and the result dont has been so much diferent.
?
I keep getting the error, failed to mount /oem. WHat am I doing wrong, I follow the instructions right and flash the right binaries. I can't figure this out
fallingandroid said:
I keep getting the error, failed to mount /oem. WHat am I doing wrong, I follow the instructions right and flash the right binaries. I can't figure this out
Click to expand...
Click to collapse
Can seem ridiculus my question, but It happened to me...
You intent flash with flashtool open? This can been the reason of error when youre try flash adb mode.
Stronger1101 said:
Can seem ridiculus my question, but It happened to me...
You intent flash with flashtool open? This can been the reason of error when youre try flash adb mode.
Click to expand...
Click to collapse
I flash with flashtool. Flash the recovery, flash the OEM that's listed for the install. But when I boot into recovery, it says it can't mount /OEM. I don't understand what's happening when I followed the directions step by step.
fallingandroid said:
I flash with flashtool. Flash the recovery, flash the OEM that's listed for the install. But when I boot into recovery, it says it can't mount /OEM. I don't understand what's happening when I followed the directions step by step.
Click to expand...
Click to collapse
Please, you can copy the links files specific you used? To try to see, where is the problem.
Changelog:
2019-10-26: First build.
cm-11-20191026-NIGHTLY-n8013.zip
2019-11-29: Build upgraded to LineageOS 14.1
lineage-14.1-20191129-UNOFFICIAL-n8013.zip
XDA:DevDB Information
[ROM][4.4.4][N8013][EMMC][UNOFFICIAL] CyanogenMod 11, ROM for the Samsung Galaxy Note 10.1
Contributors
secretwolf98, CyanogenMod
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: cm-11-20191026-NIGHTLY.zip
Stable Release Date: 2019-10-26
Created 2019-10-26
Last Updated 2019-10-26
Can i use it for N8000
mohameddeela said:
Can i use it for N8000
Click to expand...
Click to collapse
No, there would have to be a different build to get the phone features. But if you don't care about the phone features, you can edit the updater script so that it will flash successfully on n8000.
New builds are up!
https://forum.xda-developers.com/devdb/project/?id=35159#downloads
Code:
Changelog:
---LineageOS---
Security patch bump up to 2019-12-05
Bug fixes in frameworks/base
Bug fixes in external/ImageMagic
---Device changes---
Fix device specific code for n8010
https://github.com/secretwolf98/android_device_samsung_n8010
N8000
Download for n8000 link not working.
musicofwar said:
Download for n8000 link not working.
Click to expand...
Click to collapse
Under advanced, you'll see proceed anyway.
lineage-14.1-20191207-UNOFFICIAL-n8000.zip
secretwolf98 said:
https://forum.xda-developers.com/devdb/project/?id=35159#downloads
Code:
Changelog:
---LineageOS---
Security patch bump up to 2019-12-05
Bug fixes in frameworks/base
Bug fixes in external/ImageMagic
---Device changes---
Fix device specific code for n8010
https://github.com/secretwolf98/android_device_samsung_n8010
Click to expand...
Click to collapse
Link for N8010 is not working
TutsiYama01 said:
Link for N8010 is not working
Click to expand...
Click to collapse
Like I said in my last reply. You just have to press advanced ---> proceed anyways.
Please... I am searching for a rom for this Note 10.1.
But, it is the Verizon SCH-I925. Exactly the same as the N8013, but...... freaking Verizon.
It is already rooted. I am just trying to upgrade (update) the Android from 4.1.2 to something a little more usable.
I have been searching all through the site. Was about to try the CyanogenMod 12.1 rom but I was unsure if it would work.
Can you help?
does your latest build for n8000 fix the mtp issue that Don Carnage has on his build?
thanks
Nightly uploaded today didn't have a working keyboard fyi trying lineage but flash don't work on camera
Sent from my SM-G935V using Tapatalk
jcwilliams said:
Nightly uploaded today didn't have a working keyboard fyi trying lineage but flash don't work on camera
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
There is a setting in the settings app to enable the keyboard. You'll find it under the keyboard settings.
Is the LineageOS 14.1 build on this thread related to the one at here? https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514/
I just wanted to prevent future confusion from myself and others who may be browsing the forums here for this device, since we already have at least 3 threads related to LineageOS 14.1 Nougat.
FanboyStudios said:
Is the LineageOS 14.1 build on this thread related to the one at here? https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514/
I just wanted to prevent future confusion from myself and others who may be browsing the forums here for this device, since we already have at least 3 threads related to LineageOS 14.1 Nougat.
Click to expand...
Click to collapse
This one here is not the same. I wish that I could have the last thread closed or deleted.
Does the cm flash work on 8010?
Start by reading the thread.
JJEgan said:
Start by reading the thread.
Click to expand...
Click to collapse
I have and i dont see anything about the CM rom and the 8010.
New builds are up!
https://forum.xda-developers.com/devdb/project/?id=35159#downloads
These new builds includes the 2020-01-05 security patch.
secretwolf98 said:
https://forum.xda-developers.com/devdb/project/?id=35159#downloads
These new builds includes the 2020-01-05 security patch.
Click to expand...
Click to collapse
I've installed the new build on my note 10.1 8010 and flashed it with the arm 7.1 nano Gapps which constantly pops up with the "Setup Wizard keeps stopping" error.
I've tried using the pico version and this didn't work either.
Reviewing some fixes online say that i should grant permissions to Contact and Telephone, but these have already been granted to the Setup wizard.
Another fix is to make sure you have Wifi connected, which it is.
I've cleared cache and wiped everything many times to see if it was a way i was installing Gapps, attempting to install it right after the rom was installed, installed the rom, then booted and then installed Gapps...
..tried lots of different methods but nothing seems to work.
Using TWRP.
Are you able to help, or anyone help? Been at this for days now and really out of ideas.
Thanks
Edit: correction on something: - The com.google.android.setupwizard has permissions to the Contacts and Telephone. I've found another SetupWizard which isn't asking for any permissions at all.
New builds are up!
Code:
Changelog:
~ System bug fixes ~
[LIST]Bug fixes in system/core.[/LIST]
[LIST]Bug fixes in frameworks/native.[/LIST]
[LIST]Bug fixes in system/bt.[/LIST]
[LIST]Bug fixes in frameworks/base.[/LIST]
[LIST]Bug fixes in external/libnfc-nci.[/LIST]
[LIST]Bug fixes in external/libavc.[/LIST]
~ Device specific code ~
[LIST]For the n8010, n8013, and the n8000: the build fingerprints has changed and has been put into a cleaner state.[/LIST]
[LIST]Camera bug fixes for n8010.[/LIST]
[LIST]n8020 builds are dropped until I can fix the build errors.[/LIST]
https://forum.xda-developers.com/devdb/project/?id=35159#downloads