Develop Bugs

[Q] "Unfortunately, Mobile data has stopped" Error. How to fix it?

Hi all,
I have the mentioned error on Nexus 7 LTE version, Stock android(AOSP), rooted. The error pops up every 2 seconds. Here is what I have done so far:
- Clear Contacts
- Clear Contacts storage
- Clear Mobile Data
- Clear Google contacts Sync
- Disable Mobile data from the settings menu
- Rebooted the device several times
Because I was getting the error every 2 secs, it was a bit annoying to do all the above commands in 2 secs intervals. Anyway, non of them solve the issue and finally I rebooted the device with no SIM card and obviously the error is gone.
Could you please help me to fix the error while the SimCard is in the SIM slot? I need to have the Mobile data ability.
Best regards,
Shobeir

Update: I kept getting the error right after rebooting the device after some time (more than 3 days) and I installed a couple of apps in the meanwhile. But there wasn't any error until the device was rebooted.
Sent from my Nexus 7 using XDA Premium HD app

Are you using any startup managers that might have disabled a module from starting automatically?
If you haven't, with you having done all the other things, I'd suggest your next step is to reflash the stock ROM (first wipe cache, system and userdata to be sure). Test things out without installing any apps.

Pandae said:
Are you using any startup managers that might have disabled a module from starting automatically?
If you haven't, with you having done all the other things, I'd suggest your next step is to reflash the stock ROM (first wipe cache, system and userdata to be sure). Test things out without installing any apps.
Click to expand...
Click to collapse
I haven't use any startup manager. Recently I installed the Android device manager and Battery Doctor. I uninstalled them based on your suggestion as they may be associated with the mobile data. I am getting same error..
Do you have any idea why this error is being generated?

shobeira said:
I haven't use any startup manager. Recently I installed the Android device manager and Battery Doctor. I uninstalled them based on your suggestion as they may be associated with the mobile data. I am getting same error..
Do you have any idea why this error is being generated?
Click to expand...
Click to collapse
No idea. It's hard to say if Battery Doctor hibernated something and left things mucked up, even if you uninstalled it. At this point I'd look to making backups and reflashing your ROM. You'll save more time than investigating what might have happened.

Pandae said:
No idea. It's hard to say if Battery Doctor hibernated something and left things mucked up, even if you uninstalled it. At this point I'd look to making backups and reflashing your ROM. You'll save more time than investigating what might have happened.
Click to expand...
Click to collapse
Thank you for the reply.
Here is what I have done (It may help others):
1. Using Titanuim backup to backup my device and generated an update.zip so I was able to flash the update.zip from CWMR to restore the apps faster that ever
2. Using ADB to transfer ROM files to N7 in order to install it in sideload mode
3. Install the ROM (CM11)
4. Restore apps. It was awesome restoring!
But I wasn't able to install (flash) the image factory from Google. The file comes in ".tgz" format and inside the compressed file, there is ".zip" file, but the ".zip" will be aborted in the installation process!! I have downloaded the ".tgz" file twice to make sure it wasn't because of a broken download file.
Any idea how to install RAZORG KOT49H on Nesux 7 with CWMR?
Cheers,
Shobeir

shobeira said:
Thank you for the reply.
Here is what I have done (It may help others):
1. Using Titanuim backup to backup my device and generated an update.zip so I was able to flash the update.zip from CWMR to restore the apps faster that ever
2. Using ADB to transfer ROM files to N7 in order to install it in sideload mode
3. Install the ROM (CM11)
4. Restore apps. It was awesome restoring!
But I wasn't able to install (flash) the image factory from Google. The file comes in ".tgz" format and inside the compressed file, there is ".zip" file, but the ".zip" will be aborted in the installation process!! I have downloaded the ".tgz" file twice to make sure it wasn't because of a broken download file.
Any idea how to install RAZORG KOT49H on Nesux 7 with CWMR?
Cheers,
Shobeir
Click to expand...
Click to collapse
Update: I have found this post useful and it is the solution I was looking for.

I gather you extracted twice, using something like 7-Zip or WinRAR? Inside there's image-razor-kot49h.zip, and another file flash-all.bat to flash it.
If you prefer, you could extract the zip into its individual .img files, then do things like "fastboot flash system system.img" to restore each one. It's much easier to use flash-all.bat, though.
---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------
Ah good, glad you got it. :good:

20140606 KK Gapps-slim and custom for CM11

gapps-slim1.6_CM11_kk4.4.4.zip (your link to simplicity) change-log coming to post #7.
Recent changes:
Google Play 5.0.31
Google Play services 6.1.74
new Link2SD script added to avoid remounting script and reboot after gapps flash; thanks to Fiouz @ XDA for original script
edited 70-gapps.sh to set default media tones; no guarantees, seemed to work the one-time I tried it. Test it; adjust to preference.
Removed Google Calendar and corrected script to allow CM Calendar to update with nightlies, when applicable.
more script changes to hopefully make the important steps 2-4 below less important (let me know)
more suggestions at post 6
Important! (prior to flash):
1) BACKUP; if you want to skip steps 2-4 or if your encounter problems, goto recovery and wipe data, manually format system, flash CM ROM, flash gapps, restore user apps only (not any Google Apps unless they are missing; ie, Google Search. Missing apps found in Google Play store)
2) goto Manage apps/Downloaded and uninstall updates to Google Play and Google Play Services (this update places Google Play 4.9.13 and Google Play Services 6.1.09 in /system
3) launch a root browser and goto /system/addon.d and delete 70-gapps.sh and 91-cm.sh
4) it's helpful to uninstall keyboards other than the Google L development keyboard used in this gapps (use Titanium Backup or Link2SD to uninstall it); the integrated scripts will remove CM-AOSP KB (Have a preference for a different keyboard? -see post 5)
Note: Your CM Nightly updates can be downloaded and installed by the integrated CMUpdater without overfilling system. Also, gapps will be restored as flashed until 70-gapps.sh is removed or the system is manually formatted prior to ROM flash. Relax; it's auto-magically done without returning to recovery each update. More bloat is being removed -see change-log post 5
Suggested use: Flash prior to next CM11 nightly update to:
1) automatically remove CM wallpapers and AOSP keyboard with each CM11 update. Still supported but epicmtd is now a mini ROM build
2) automatically backup and restore /system gapps with each CM11 update (includes: Google Play version 5.0.31, Google Play Services 6.1.11 and Google L developer edition keyboard (with three themes in advanced settings).
(suggestions and disclaimers)
*Recommend flashing initially as clean install; scripts have been modified to flash prior to nightly but dirty flash at own risk. Subsequent updates of CM 11 nightlies can be done retaining userdata, if preferred, but do so at own risk.
**If not using with clean install on initial flash, may require manual removing of original keyboard in /data partition.
***A recommended trial of these gapps could be done prior to flashing another CM nightly. Backup first. If flashing this shows problems, the userdata may need wiping or manual cleaning prior to flashing nightly and gapps. Once in place and functioning, the /system/addons.d scripts will restore minimal gapps and Google L keyboard as well as remove the bloat each update. Therefore, you can simply use the integrated CM Updater in System settings/About phone/CyanogenMod updates to download and update without manually flashing in recovery.
****Any missing Google apps should be available in Google Play.
FYI: deleting the /system/addon.d scripts manually or manually formatting system partition will defeat the auto backup and restore of this custom gapps with bloat melt.
Advantage? Free up available system and data space occupied by infrequently used gapps or outdated ones. No manual bloat melt or modifying ro partitions required. Automatically repeats manual steps... advanced users can modify to automate most manual steps repeated in CM nightly updates. (One step I still repeat manually after each boot is to cycle location toggle.)
(hints and suggestions for advanced users)
You can add your own preferred user apps at /data/app location of .zip archive using your computer but only recommend that for clean installs. If so, use this once for dirty flashing over existing userdata, your updated custom version once for each clean install. (more after disclaimer)
*disclaimer: nightlies sometimes require clean installs due to changes; dirty flash and customize this at own risk. Always backup prior to flash in case of problems.
Within reason, I can attempt to help with in-demand changes to this. To edit for more /system app removal, look into META-INF\com\google\android\updater-script and follow the method in original to make changes take each gapps flash for clean install. You'll also need to edit /system/addon.d/91-cm.sh following that method to make same changes permanent. To add user apps for clean installs, simply download to computer, open the archive and copy your preferred user apps to /data/app folder (updater-script is already modified for permissions).
Note: for those of you that like to manually format /system prior to flashing nightlies, I've looked at the CM11 updater-script and normal format does indeed take place after backing up per addon.d scipts. For example, the CM50 script actually backs up your /system/etc/hosts and rewrites to same location after its normal system partition format. This is useful for those that use apps that modify hosts to block ads. But, formatting prior to flashing could be useful if you happen to suspect a /system/addon.d backed up script was causing you problems.
Note2: I had given up on using addon.d scripts to restore scripts like Link2SD or Xposed framework but now seem to have some scripts that work for CM Updater updates over userdata; they simply eliminate a couple of manual steps within the applications and the reboot that would follow those steps. This is a safer mod, minimizing risks using the existing user scripts rather than flashing an individual's personal script. Post 3 may contain a future update for advanced users with additional scripts for backing up and restoring Link2SD sdext2 partition remount script backup and restore during CM update as well as Xposed framework /system/bin/app_process and app_process.orig backup and restore as needed. WIP; update coming soon.
Note3:There is potential to gain more system partition space available but preferences vary. Keep in mind that scripts will only impact /system partition. A customized version would be required if advanced users wish to add user apps to /data/app like user tools and apps that load quicker in a flash rather than download or side-load apps.
Note4: I've read other CM forums and latest gapps are recommended. Looking through the changes, I agree. I will try to keep this updated, if needed.

added CM Updater support!
Thanks to CMNein and blowtorch in this thread:
[Tutorial] CM9/CM10/CM10.1 back up script along with one other source that I lost in tapatalk, got this CM Updater support working for CM11 Nightlies for both backup and restore gapps as well as melting the bloat. If anyone knows the other source, please let me know so I can thank and give credit but the script is almost identical to the one linked.
Same apps; different scripts. Flash this one to make the backup and restore proper and continual (follow the asterisk comments for conditions)
change log:
1) added appropriate support to 70-gapps.sh to backup the right gapps and keyboard when flashing new nightly without requiring flash of gapps each time(*)
2) added new 91-cm.sh script to melt the bloat each time OTA CM Nightly is flashed.
3) consequently, changes 1 & 2 now make it possible to update CM Nightlies without having to flash gapps each time(**). I came to this realization a bit late
(*)provided that system is not manually formatted (Allow the CM scripts to backup, format system and restore gapps.)
Note: to use different gapps, format system manually or delete /system/addon.d/70-gapps.sh prior to flashing new gapps)
(**)System settings/About phone/CyanogenMod updates/update types: All versions (press the nightly version for changelog; icon gives option to download, install or indicates current version installed) Limit visits to recovery:good:
In summary: you can flash this once and forget about flashing gapps again on nightlies. Works with the integrated CM Updater also (manually formatting system or deleting /system/addon.d/70-gapps.sh and 91-cm.sh will keep these changes from automatically restoring. Editing those scripts can save you time and pose less risk editing ro partition prior to boot.)
version 1.1

advanced user scripts for Link2SD and Xposed framework
gapps-SlimAdv1.2_kk-20140606-signed.zip
(Outdated; merged scripts into one release. See post #4)
refer to edited OP for advanced user discussion (spoiler or hidden text)
same gapps but added a couple of new scripts to support backup and restore of Link2SD and Xposed framework when updating CM with integrated updater while retaining userdata
changelog:
1) added 89link2sd.sh script to backup and restore user's mount script at /system/etc/init.d when updating CM
2) added 90-exposed.sh script to backup and restore /system/bin/app_process if using Xposed framework. Thanks to rovo89; script pulled from link in his OP
Note: if not using either of the above applications, just use version 1.1 referenced in previous posts.
Note2: if one of these scripts do not apply, you can open archive of zip and delete the script not needed without breaking the zip for flashing.
Disclaimer: Use at own risk; currently testing on CM Nightly 20140809.

If you've encountered CM theme or theme update install errors with Google Play since the 4.9.13 update, this gapps update may help; install and use the workaround below the changelog... if not having issues, stay with what works until a CM 4.4.4 Gapps is released.
changelog:
1) updated Google Play to 4.9.13; installs to system partition
2) removed backup/restore of /system/priv-app/GmsCore.apk in /system/addon.d/70-gapps.sh (no longer needed for CM updates)
(after next CM update, you should see a little more system partition available space)
Note: this update includes the advanced scripts 90-xposed.sh and 89link2sd.sh; open zip archive and delete from /system/addon.d if not needed (optional but not necessary; the scripts are there if ever needed for Link2SD or Xposed framework mods).
Note2: this update is only intended for those encountering update or install error in the new Google Play version 4.9.13 (don't update if not having issues; follow the workaround, if needed).
Install instructions:
If you have Google Play version 4.9.13, it's most likely on the data partition. Wipe its data in System settings/apps/Downloaded/Google Play Store and Uninstall the update.
Flash the updated Gapps. If having problems, go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot.
Workaround:
for Google Play Store install errors -24, -110: go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot.
If you encounter Google Play install install error -401 or -400, consider your CM theme may be causing this and revert back to original CM holo (Default) theme in System settings/Themes, freeze Link2SD and Link2SD Plus, go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot. After successfully installing or updating the problematic application, select desired CM theme and unfreeze Link2SD. The 400 hundred series install errors may be rare but I've notified the application developers of the issue.
Notes for Link2SD users:
1) after a CM update, launch the Link2SD application, wait for it to load and "clean up the 2nd partition" in the "more"/left tab slide-out. Don't click OK but read the details and note that you most likely need to "Link dalvik-cache" files in the "more"/left tab slide-out after each update. I've found it's important to wait until the application fully loads to check; otherwise, you may be causing more steps to get your linked files restored and keep the redundant files out of the internal memory.
2) if you have Google Play services update 5.0.89 in Downloaded tab of System settings/Apps, you no longer need the dalvik-cache file [email protected]@[email protected] (you can safely delete it when running the "clean up the 2nd partition" in the "more"/left tab slide-out (if deleting, reboot once more) . You should not see it again after updating CM with the CM updater.
gapps-Slimv1.3-_kk-20140606-updated.zip

change-log for gapps-slim1.4_CM11_kk4.4.4.zip update
Still don't see an official CM gapps for Android 4.4.4; this is an OTA update pulled from apk's pushed to my phone by Google
gapps-slim1.4_CM11_kk4.4.4.zip
Important: see OP (post 1) for update instructions; the old scripts need to be flushed and replaced. The gapps flash/updater-script should take care of that but to be sure, follow the manual steps.
Themes: some themes or theme updates pulled from Google Play WILL (if you have Link2SD installed and sdext2 partition is visible) give you an update error -401 If this happens to you, the workaround in post # 4 above still applies.
change-log:
removed cm-91.sh bloat remover script and integrated into a new 70-gapps.sh
removed more bloat; necessary for larger Google Play and Google Play Services moving to /system
want custom ring tones? look into /system/addon.d/70-gapps.sh for ideas (for those that can edit scripts)
Warning: many media tones were removed as bloat. Check your tones for correctness; if needed, I can add these back in.
Note:
there is a limited space left in system if you choose to risk adding some back in. During testing, the old method was actually maximizing system capacity before the bloat was removed. Therefore, a change to delete the bloat prior to writing/restoring the larger apps from gapps was necessary. If you've ever experienced lag after installing or restoring gapps during CM updates, these scripts are necessary to avoid that mishap. The scripts and updates also keep the updates from landing in /data partition, using more of your internal storage space while the system space is not utilized to its fullest capacity (until next Google update pushed OTA). If you've tried this update before, please try it again and make sure no redundant updates are in /data partition.
Tones retained:
ringtones: Orion, Themos, Kuma
alarms: Argon
notifications: Argon, Altair, Proxima
Extra bloat removed:
Apollo.apk
Galaxy4.apk
NoiseField.apk
HoloSpiralWallpaper.apk
LiveWallpapers.apk
LiveWallpaperspicker.apk
MagicSmokeWallpapers.apk
VideoEditor.apk
VisualizationWallpapers.apk
PhaseBeam.apk
PhotoTable.apk
PhotoPhase.apk
MediaUploader.apk

New Google Play, Services and more scripts
gapps-slim1.5_CM11_kk4.4.4.zip
What's new:
Google Play 5.0.31
Google Play services 6.1.11
new 88-link2sd.sh script added to avoid remounting script and reboot after gapps flash; thanks to Fiouz @ XDA for original script
more script changes to hopefully make the important steps 2-4 from OP less important (let me know)
What's important?
see OP, post 1. You can try the easy way of flashing prior to next nightly or unofficial nightly; the scripts should restore gapps and keep the ROM build "mini"
Check your tones; pull from another nightly ROM or customize as this is done in /system/addon.d/70-gapps.sh script
Xposed framework support was removed; if you need the script, pull from an older gapps version or from here; the bottom script. Hit the thanks button while you're there (the script inspired the latest 88-link2SD.sh used in this gapps release)

gapps-slim1.6_CM11_kk4.4.4.zip (Update)
gapps-slim1.6_CM11_kk4.4.4.zip
Changes:
Removed Google Calendar and corrected script to allow CM Calendar to actually update, when CM applies applicable update
updated Google Play Services to 6.1.74
attempted to set default media tones within the 70-gapps.sh; no guarantees. Thought it worked the one time I tried it but without data wipe so IDK.
FYI: can't test the flashes against the Epic any longer; mine got traded-in for the Note 4 ($200 BB gift card), Friday Oct. 17, 2014. Retired. Farewell Epic forum. Peace.

[LP][5.X][XPERIA] Debloating Script For Performance , battery Life and more memory

Hey guys, I sharing debloating script for those interested in a higly DEBLOATED LP installation, very slimmed down, battery friendly, faster, with less RAM comsuption etc
It will remove everything that is not important so before proceding be sure to backup full system
RESULT
As said at the top, you'll get a very slimmed down LP FW, battery friendly, very fast, with less RAM comsuption etc
Of course, everything is working great here, I mean all the features I need/use!
you are going to delete more than 160 packages in total with all relevant libs/stuff plus all applications automatically installed by Sony
HOW TO RESTORE SOMETHING
PS. of course I also removed from my FW all the stuff that can be easily downloaded from the Play Store (Gmail, etc)
below you will find the restoring instructions you need to follow to restore any package you may want back
According to what you want to restore, you have to follow two different procedures:
- all the APKs that are inside /system/__Backup/various/etc_custom_apps and /system/__Backup/various/etc_prod_apps are regular APKs that are going to be installed in /data, so you can just run them and then select "install" like a normal APK, easy. You will then see them in Settings > applications > downloaded
- instead, all the things in /system/__Backup/system_app and /system/
__Backup/system_priv-app folders can't be normally installed, but must be restored in the correct /system folders with correct permissions. To do this, see the step-by-step instructions below (in the following example, I am going to restore Chrome app in /system/app and Velvet (Google Search) in /system/priv-app, but of course you can restore how many things as you want at the same time)
Click to expand...
Click to collapse
- with a root file manager like ES, go to /system/__Backup/system_app and MOVE the whole "Chrome" folder to /system/app
- with a root file manager like ES, go to /system/__Backup/system_priv-app and MOVE the whole "Velvet" folder to /system/priv-app
- reboot
- done
Click to expand...
Click to collapse
PS. don't copy but MOVE things back, or permissions will get messed up and you are likely to end up in a bootloop!
Requirements:
- working recovery
- be on LP already, 5.0.2 or 5.1.1, doesn't matter
DISCLAIMER
If you apply my script again please take care I did a pretty massive debloat as I don't use a lot of stuff (social apps, small apps, many of the sony "addons"/special settings etc!!) and this is a working config for me, but for others some functionalities will be probably missing, so mind what you do before apply them! (but again you can restore anything anytime, if interested just go for it)
Click to expand...
Click to collapse
Installation:
1. full nandroid backup to eventually go back to previous any time
2. wipe data, cache and dalvik ***
3. flash debloating script
4. that's all! reboot/enjoy and hit thanks
View attachment Bloatware_Removal_LP.zip
Credits
Many THANKS @ondrejvaroscak and @Puffin617 for some very good advices, @mj084 for some packages descriptions and @moly82 for sharing this

Hi,
In stock debloated ROM whether screen mirroring will work or not, please let me know. Now I am using Decepticon ROM. Which one is better.
Before putting debloating script keeping a backup of all system apps using Titanium Backup is enough or not. Please clear my doubts.

bootloop on latest 5.1.1 d5322

SH1M4BD3 said:
bootloop on latest 5.1.1 d5322
Click to expand...
Click to collapse
Clear delvik catch and restart no such issues same device I have

Fantastic - thank you. Did the job perfectly!

hi i have this phone last month, hand-me-down. does this procedure require root? and what recovery do i have to use?

[ROM][Unofficial][ResurrectionRemix-P-v7.0.0][manta] -> 20190208 (DISCONTINUED)

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289294
Thanks for understanding ..
Resurrection Remix for manta ..
RR-P-v7.0.0-20190208-manta-Unofficial.zip
Known issues:
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- NavBar is not visible - same hwc issues like above !
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
RR-O-v6.2.1-20181209-manta-Unofficial.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
4. install Opengapps or other Gapps package
5. install Magisk.zip
6. Reboot into system ..
- Please install Magisk.zip (17.x) yourself.
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/manta-rros-lineage-15.1
Download:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Enjoy Resurrection Remix on your Nexus 10 ..

Finally it's own thread ..
August 2018
RR-O-v6.1.0-20180814-manta-Unofficial.zip
Changes:
- Google August 2018 Security updates
- Adjust DRM blobs
- ro.opa.eligible_device=true -> Google Assistant
- Latest LineageOS and RR changes
Enjoy

Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro

amitroutray said:
Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro
Click to expand...
Click to collapse
No .. RR is it's own ROM .. Even it's based on Lineage you don't need to install it first.
Just corrected the typo ..
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
Cheers

followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.

Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip

yeoldeusrename said:
followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.
Click to expand...
Click to collapse
Yes .. it's actually 2 things .. gapps pico packages has been grown ... From ~105mb (may) to ~125mb (today)
As well RR made some additional changes (not part of lineage code) to optimize the compression of aapt. (.apk sizes)
I have taken out the changes now.
For next release camera will be taken out from build.
You may take gapps config file using "smallbuffer" parameter to use 2mb right away.
Or change buffer inside installer to another value.
Similar problems will happen for los-15.1 if the pico gapps size is still growing.

someguyatx said:
Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip
Click to expand...
Click to collapse
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !

@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro

followmsi said:
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !
Click to expand...
Click to collapse
Thanks I will give it a try tonight. Nothing important enough to backup this is just my entertainment tablet.

amitroutray said:
@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro
Click to expand...
Click to collapse
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.

followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10

amitroutray said:
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10
Click to expand...
Click to collapse
For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.
It's a space problem !
Will check if I can reduce system space usage a bit more ..as well reducing buffer for gapps down to 2MB.
Cheers

followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?

someguyatx said:
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?
Click to expand...
Click to collapse
Audio jack kernel is part of this ROM ..
Depending on the gapps package size you may have to delete camera2.apk - to increase free space for gapps installation.

September 2018
RR-O-v6.2.0-20180909-manta-Unofficial.zip
Changes:
- Google Security updates -> September 2018
- moved shim libs to vendor
- Latest LineageOS and RR changes (update to version 6.2.0)
Enjoy

Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?

Don Moahskarton said:
Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?
Click to expand...
Click to collapse
- install latest TWRP (3.2.3)
- Wipe systen first.
- Install current ROM
- Install just one Gapps package (manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip - buffer has been reduced to fit into manta system partition)
- Wipe cache / dalvik
- Reboot system
If SetupWizard is crashing we will need logs for further troubleshooting.

Somehow it immediately worked by following closely your instructions. I must have done something wrong before then.
Thanks a lot still, and very kudos for this ROM : )

root access
Fyi it did not like addonsu 15.1 for what ever reason, it was flashed via TWRP and turned on in dev mode but never gave access .. However Magisk flashed fine from TWRP and gave root access so no problem. had to have my Adaway from XDA.

PSA: NFC banking and Netflix working with EdXposed!

Just wanted to share my experience with NFC banking and FullHD working Netflix. Managed to delete everything google and installed Microg only (to get Gcam to work), my banking app, Netflix app, Canary EdXposed and it works flawlessly! Could never get FullHD and NFC banking to work previously with Xposed. Of note was the fact I am running Xprivacy, too. Just make sure you blacklist the apps in EdXposed and also hide them in Magisk and it all works
Hope this helps others as it really made my NoGapps/Rooted stock phone experiences significantly better.

Hi, did you follow a guide to de Google your phone or did you do it yourself?

I didn't follow any guides, per se. Deleting gapps is risky but I always do full nandroid backup beforehand, in case something goes wrong. Make sure you know what you're doing. Make sure LGUp is working properly before starting this! Anyway, here's what did:
1) Make sure you have followed WTF instructions to unlock the phone on Oreo rom. Don't update to Pie without unlocking bootloader in Oreo first. This is to ensure you can have root in Pie.
2) Fresh install stock Pie with LGUp. Ensure there us no SIM card and no wifi access to the phone. Make sure you remove google account from phone before installing Pie kdz!! Otherwise it won't work.
2) Install TWRP. Follow WTF instruction for Pie to install Magisk, etc. Factory reset. Wipe /cache /data /dalvik. Reboot into TWRP/recovery. Format data. Reboot into TWRP/recovery again. Make a full backup. Mount /system partition and using the file explorer in TWRP, I deleted all the google apps folders (except googlepackageinstaller, googleExt, and any other google apps you might use) from /system/apps and /system/priv apps. Remember to have a full nandroid backup on and sdcard in case you get bootloop.
3) Delete cache and dalvik and reboot into system now.
4) After first boot, if everything goes well, boot into recovery and install EdXposed (riru core 19.5 then latest canary build Yahfa version EdXposed). Wipe cache and dalvik. Reboot.
5) Install F-droid, search for gapps. You should find an app called /dgapps/ or something. Install it. Delete Amazon and GMS (gapps) and hit 'clear and reboot' in the bottom.
6) Once ypu have entered phone again, install microg gmscore app only. Now, using titanium or whatever you used to backup your apps reinstall them without their data. Once your phone is back to normal with all your apps, follow my guide above to blacklist netflix and banking apps in EdXposed app and Magisk app.
7) Reboot and everything should be working.
P.s. Word of warning: deleting gapps can cause bootloop so ensure you make full backups in TWRP. Make sure you know how to use LGUp to flash kdz if things go wrong.
P.s.s. Deleting gapps means GPS will have fewer sats connecting and will take longer to connect, as well. It's a tradeoff for privacy.