Google Apps Basic Packages for cm-11.0 - Samsung Galaxy 5 I5500

GOOGLE APPS PACKAGE FOR CM11 BUILDS
System version
These versions of gapps will be installed on your system partition (/system) just like official gapps packages.
Link to the latest package:-
gapps-kk444-20140724-v2.2.zip (7.9 MB only)
Requirements:-
Need a cm11 build from Jenkins' project: cm-ota which is built after 22/06/2014 (users of older builds are recommended to use gapps-v1.0).
Need a minimium of 12 MB free space in system partiton (Tip for galaxy5 users: 20 MBs of free space is there by default on cm11 builds after 22/07/2014).
Need CWM recovery 6.0.5.2+ by psyke83/Jenkins-cm-recovery (gapps-v1.0 can be installed using any recovery).
How to install? (With a cm11 clean install?)
Reboot to recovery. (Use CWM 6.0.5.2+ by psyke83/Jenkins)
Wipe Data/ Factory Reset.
Go to 'Install zip from sdcard' and select the ROM file (only cm11) you want to install from your sdcard. Let the process complete.
Then, Choose the above given gapps package (only use v2.0 or later for cm11 builds after 22/07/2014) for cm11 in 'install zip from sdcard'.
Then just reboot and you're done!
How to install? (Already installed the cm11 and just want to install gapps now?)
Reboot to recovery (CWM 6.0.5.2+ by psyke83/Jenkins).
Choose the gapps package (only use v2.0 or later for cm11 builds after 22/07/2014) in 'install zip from sdcard' option.
Then just reboot and you're done!
Changelog:-
v2.2
Play-Store updated to latest version: 4.9.13 (released on 23/07/2014).
Fixed updater script to install on all other devices.
v2.0 (Removed link because this version worked only on Galaxy 5)
Updated updater-script to make installation compatible with new CWM 6.0.5.2+ (with swapped partitions).
Updated Play Store to latest version (v4.8.20).
Continued using JB (cm10.1) Google Framework and Login Services as latest KK (cm11) Google Framework and Login Services exceed the free size of system partition even if slimmed to it's end.
v1.1
Fixed: Now it can be flashed using cwm 6.0.4.6 by psyke83
v1.0
Can be installed using CWM 6.0.1.2 (Trying to make it capable of flash via CWM 6.0.4.5+)
Play store, Google account and everything working.
Removed big apps like talk, youtube, etc.
Updated Play Store to latest version.
NOTE: These gapps are the minimalistic gapps possible.
SD-EXT version
This version will be installed on your sd-ext partition. (So these packages won t occupy space in system partition. This will help devices with tiny system partition.)
Link to the latest package:-
gapps-kk442-20140225-sdext-v2.0.zip (20.5 MB only)
Patch for Mountscript :-
gapps-kk442-sdext-patch.zip (128 KB only)
This patch creates a mount script for your sd-ext partition. And if your using any app2sd apps like link2sd then also please INSTALL this patch. It won't conflict with link2sd (or other app2sd apps), Don't worry.
Patch for Dalvik-cache Duplication:-
dalvik-cache-patch.zip(128 KB only)
This patch is optional and will save you 5 MBs in data partition because it removes (symlinks infact) duplicated dalvik-cache files.
Requirements:-
Need a cm11 build from Jenkins' project: cm-ota which is built after 22/06/2014.
An sd-ext partition of any size having atleast 31 MB free space for v2.0 and 11 MB free space for v1.0.
Any working recovery (Recommended: CWM recovery 6.0.5.2+ by psyke83/Jenkins-cm-recovery).
How to install?
Download gapps package, mountscript patch and dalvik-cache patch from above link.
Install mountscript patch & dalvik-cache patch.
Then install gapps package. (Install simply without any wipes). IF you are using my v1.0 sdext gapps, for upgrading to v2.0 do a full data wipe and again flash cm11.
Reboot to system and you're done!
Changelog:-
v2.0
Made from fresh official cm-11.0 gapps.
Added GmsCore.apk because without it, new cm11 gapps don't allow you to add a Google Account.
GoogleContactSyncAdapter and GoogleCalendarSyncAdapter are now moved to /system/app because they must be there (not needed to put in priv-app).
Added few necessary permission files (to /system/etc/permissions) to run Google Maps and few other things.
Added framework jars for maps, drm and media-effects.
Added system/addon.d/70-gapps.sh
Added GoogleOneTimeInitializer.apk (not OneTimeInitializer.apk)
Added ConfigUpdater.apk
v1.0 (only 6.5 MB)
Can be flashed on sd-ext partition.
NOTE: These gapps (all versions) are incompatible with ART.
Credits:-
psyke83 : for his cm10.1 gapps package and for help with mountscript and dalvik-cache patch's script.
Feby : for help of mountscript.
Me : for maintaining these gapps packages.

Problem while installing these gapps
Hi,
I'm having a big problem about getting these gapps to work. Indeed, even if they are installed perfecly through the recovery (CWM/ PhilZ Touch), when my callisto reboots there no google apps (e.g Play Sore) installed. I tried to add my google account through the settings but didn't helped, still nothing. I'm using CM11 made by psyke83 : http://forum.xda-developers.com/showthread.php?t=2453085
Any idea to get play store working ?

mehdoux said:
Hi,
I'm having a big problem about getting these gapps to work. Indeed, even if they are installed perfecly through the recovery (CWM/ PhilZ Touch), when my callisto reboots there no google apps (e.g Play Sore) installed. I tried to add my google account through the settings but didn't helped, still nothing. I'm using CM11 made by psyke83 : http://forum.xda-developers.com/showthread.php?t=2453085
Any idea to get play store working ?
Click to expand...
Click to collapse
Please read instructions. Free up enough space in system partition first. And if you're using sd-ext gapps, make sure it has free space and even it exist and you flashed mountscript patch.
READ INSTRUCTION CAREFULLY AND GET THE JOB DONE.

Bhargav97 said:
Please read instructions. Free up enough space in system partition first. And if you're using sd-ext gapps, make sure it has free space and even it exist and you flashed mountscript patch.
READ INSTRUCTION CAREFULLY AND GET THE JOB DONE.
Click to expand...
Click to collapse
Hi,
THIS IS EXACTLY WHAT I DID. I deleted all the files you mentionned (some files won't get deleted though).The recovery wasn't giving any error. Anyway, I deleted some others system apps (which I will replace with some third-party apps, it was the only solution because i didn't want to use sd-ext gapps) and finally get the play store installed. Thank you for your help and keep up the good work.

one question: what this gapps-kk442-sdext-patch script is better link2sd?

iSanechek said:
one question: what this gapps-kk442-sdext-patch script is better link2sd?
Click to expand...
Click to collapse
If you have that then you can't use link2sd because the gapps will be installed on the sd-ext partition. So, if you install link2sd it will override the gapps.
Sent from my GT-I5500 using Tapatalk

Vagelis1608 said:
If you have that then you can't use link2sd because the gapps will be installed on the sd-ext partition. So, if you install link2sd it will override the gapps.
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
Don't give wrong advice please. He can use Link2SD without any problems even if he's using that patch and gapps, already written on first post. gapps will just occupy a little space on sd-ext partition and that's it.
iSanechek said:
one question: what this gapps-kk442-sdext-patch script is better link2sd?
Click to expand...
Click to collapse
I'm not sure what you are asking. I've already written on first post that installing this patch and gapps won't create any problems with Link2SD. And, if you have link2sd then also you must install that patch because of a different (non-standard) mount-point creation by Link2SD.

Bhargav97 said:
I'm not sure what you are asking. I've already written on first post that installing this patch and gapps won't create any problems with Link2SD. And, if you have link2sd then also you must install that patch because of a different (non-standard) mount-point creation by Link2SD.
Click to expand...
Click to collapse
I asked what the plus of this script? if I use link2sd. thanks for reply and help. I understood everything.

Help Google now not working!!
HI
Thanks for providing the SD ext version of gapps but i have a major problem as Google now doesn't work. The app will be installed and start normally but when i tap the mic to start speaking it say "Unfortunately Google Search has stopped working" .
Thanks in advanced (a lot).
DETAILS:
Galaxy 5 running on cm11 20140531 NIGHTLY
SDEXT:- 512 mb
Swap:- 64mb
processor oc to 768Mhz
SDEXT gapps (provided by you):laugh:

abhijeet98 said:
HI
Thanks for providing the SD ext version of gapps but i have a major problem as Google now doesn't work. The app will be installed and start normally but when i tap the mic to start speaking it say "Unfortunately Google Search has stopped working" .
Thanks in advanced (a lot).
DETAILS:
Galaxy 5 running on cm11 20140531 NIGHTLY
SDEXT:- 512 mb
Swap:- 64mb
processor oc to 768Mhz
SDEXT gapps (provided by you):laugh:
Click to expand...
Click to collapse
The Google Now's Voice Search is not compatible with armv6 devices (like: galaxy5). Because the libs needed for them are compiled for armv7. So it's not fault of my gapps, it's where the limitation of your device arrives.
However, there's a workaround for that (it's not too pretty but it works):
http://forum.xda-developers.com/showthread.php?t=2709285

Not related to gapps but only one Question!
I wanted to ask that whether I can install cm11 Nightlies to SDEXT like "psyke" sir developed the rom for my device(GT15503) that can be installed
in the SDEXT ? As the further development has stopped of that Rom so i thought it would be great if Jenkins build could be installed on SDEXT :laugh:.If possible please give me a solution.

Thnx man this works perfectly with The CM11 for Galaxy 551 and had no problem with it whatsoever. I have to applaud you
and say good work on this.

thanks :good:

MADjohny24 said:
thanks :good:
Click to expand...
Click to collapse
Seems like you are new to XDA.
If somebody helped you, don't make a post to say "Thanks". Just click on the "Thanks" button found on the left of every post. It's the only purpose of the Thanks button which helps to keep the thread clean of common posts which are just made to say: 'Thank you', 'It helped a lot, Thanks' and such others.

Thanks mate. I managed to install it on CM11 for Galaxy Mini/Pop Plus/Next Turbo GT-S5570I (I know. Different names for different countries). The version 1.1, though. I think you updated the post just the day after I downloaded it.
Just for reference other Gapps were crashing the AOSP keyboard. With this it works just fine!
EDIT: Just installed v2.2. No issues either. The catlog is clean and AOSP works!

Mounscript link doesn't work...

aamm95 said:
Mounscript link doesn't work...
Click to expand...
Click to collapse
Checked here. Link is all fine.

I'm sorry, i was going out to the internet thru a sonicwall firewall...I've download the script.

zlock2sonyexperia
hello
bhargav97
i like your hard work for our small but good enough smarphone galaxy 5. today i was reading an article in they ported sony experia lock to their phone and that is pretty good so my question is that can we put this lock on our set bcoz i have tried and failed to put this lock on my g 5.so can you tell us whether we can use it or not, if yes than it will be great g 5 user.
thanks in advance
rztg1618:

@Bhargav97,
Can you do me a favour?
1. Your information in post #1 re: the mountscript is inaccurate - it breaks simple2ext_mod. If someone has S2E installed, they don't need this patch, as /sd-ext will be mounted by simple2ext's script.
2. The dalvik cache patch won't work with with S2E due to the order of script execution. There are two possible solutions:
a) Rename the script to "/system/etc/init.d/91linkduplicates". This will ensure that the script is executed after all userinit.d scripts (including S2E's mount script) have finished.
b) Move the script to /data/local/userinit.d.
Option B has the advantage of surviving full OTA updates... however, you will need to choose a different name for the script to make sure it is executed after /data/local/userinit.d/simple2ext. The first letter of the filename would need to start with the letters t-z (so that it's executed after simple2ext). Ideally simple2ext's script should start with a number, but since I forgot to make that change in my initial mod, it's a bit of a pain to change it now (as the app will create duplicate mount scripts)
It would probably have been a better idea to implement a userinit.d script to symlink *all* gapps files on /system (as well as the dalvik duplicates), instead of doing any symlinking in the updater-script. That would make the whole gapps sd-ext package compatible with full OTA updates (as the userinit script survives /system reformatting), and avoid the need to provide a separate dalvik cache patch. Let me know if you want me to write the script.

Related

[MOD] D2P - free some space on /data, for most ICS ROMs

This is an init.d script inspired by bodhisattva99's work that can be found here:
http://forum.xda-developers.com/showthread.php?t=1526827
Props to him for the idea.
This script does the same as his, but my zip does not flash a new zImage (the partition can be mounted anywhere with one single command, thanks, Chainfire!).
I do not own an SGS2, so this is untested by me personally, but it was tested by AColwill on A LOT of ROMs and he noticed seemingly better boot times than with the original script. However, he discovered that this also doesn't work on GB and earlier ICS builds. If you do happen to flash it on an unsupported build, the script should simply print out that your ROM isn't supported to /data/d2p.log, exit, and let the boot process continue.
What does it do?
Basically, what it does is it puts Dalvik cache on /preload (which is about 500 MB in size and otherwise totally unused), freeing up space on /data for even more apps.
It will not wipe any of your data, it will just put Dalvik cache on /preload. First boot will take a while since Dalvik cache needs to rebuild, afterwards, it should work like a charm, leaving you with a few hundreds of megabytes more on /data.
Requirements:
- A recovery image
- A rooted ROM
CWM update.zip:
Download link
Huge thanks to:
AColwill - testing, testing, testing and some more testing
Ante0 - providing proper hosting for the zip
brabo, GShellz admin - the bash wizard
Chainfire - providing me with the preload parition ID
mattgirv (from #villainrom, Freenode) - compiling bash for me, help with cross-compiling
sircrazy, GShellz admin - help with cross-compiling
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.
Got some fail:
Code:
I/run-parts( 1667): /system/etc/init.d/99dalvik2preload: line 13: syntax error: unexpected word (expecting ")")
I/run-parts( 1667): run-parts: /system/etc/init.d/99dalvik2preload exited with code 2
I/logwrapper( 1667): /system/xbin/run-parts terminated by exit(1)
Sorry about that, should be fixed now. Try it now, should work like a charm!
This is great! A few questions though, a small FAQ could be useful in the first post.
1. Is this reversible?
2. Will it wipe any data?
3. Will the Wipe Dalvik command work in CWM?
4. What happens when the Dalvik becomes full?
Thanks for the mod and for replies in advance!
And the link is where??? i only see download link [fixed] but cant press it
blizzari said:
And the link is where??? i only see download link [fixed] but cant press it
Click to expand...
Click to collapse
well the link he credits (http://forum.xda-developers.com/showthread.php?t=1526827) at the end of page2 does have a valid link to his script (called dalvik2preload_proz0rmod-signed.zip) now I'm not sure the OP link is down because it is borken or because the script is being worked on and he'll make the link active again once work is completed.
---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------
Phat7 said:
This is great! A few questions though, a small FAQ could be useful in the first post.
1. Is this reversible?
2. Will it wipe any data?
3. Will the Wipe Dalvik command work in CWM?
4. What happens when the Dalvik becomes full?
Thanks for the mod and for replies in advance!
Click to expand...
Click to collapse
just have a quick read at the link the OP credits ( http://forum.xda-developers.com/showthread.php?t=1526827 ) and all your questions will be answered.
Due to an issue with ASH and some retarded builds of busybox from some devs, Davor (Proz0r) has had to pull the release as it wasn't doing what it was supposed to do.
Currently, the 1.19.4 busybox which is included with the CM9 firmwares AND the one downloaded by jrummy's busybox installer (same build) is missing some core functionality required to get the script working :|
I'll be working with Davor over the next few days (hopefully) to get this fixed and released.
Exactly, thanks AColwill for the explanation as I was too busy with school at that time. I will get on it soon and deal with the Busybox issues.
Script works like a charm now, no need for Busybox. All tools required for the script to run are included, all you need is a rooted SGS2 with a recovery image and you're all set!
Just flash it or we need to wipe something too?
Getting a 404 error when I click on the link
Sent from my GT-I9100
soyef said:
Getting a 404 error when I click on the link
Sent from my GT-I9100
Click to expand...
Click to collapse
Me too. Can somebody post a link that works?
need new download link
Thanks
Whoops, fixed. AColwill also tested this with a whole bunch of ROMs to find out that it should work on KPA and newer ROMs, but no pre-KPA ones. I've also added a failsafe which will just print out that your ROM isn't supported to /data/d2p.log instead of causing a bootloop if you happen to flash it to an unsupported ROM.
As always when flashing stuff. NANDROID FIRST.
Even though I have done extensive testing with multiple SGS2's, I am not infallible (even though it appears that way).
Proz0r said:
Whoops, fixed. AColwill also tested this with a whole bunch of ROMs to find out that it should work on KPA and newer ROMs, but no pre-KPA ones. I've also added a failsafe which will just print out that your ROM isn't supported to /data/d2p.log instead of causing a bootloop if you happen to flash it to an unsupported ROM.
Click to expand...
Click to collapse
Not getting any errors on KL1 - My phone now boots in less than 10sec. Great mod. Thanx.
Awesome, thanks for the feedback!
Just flashed it... I'm on Spike's 7.1 SE
1.
Booted into CWM, wiped dalvik-cache & flashed d2p-mod.
Phone does not boot... gets stuck in bootanimation...
2. Restored phone.
Booted into CWM, this time I did NOT wipe dalvik & flashed d2p-mod.
Result: Phone stuck in infinite boot loop on the Samsung Galaxy SII screen...
It is sad there seems to be not updates at this time...
Flashed it on Westcrip's 1.0 Pro, and checked the /preload was empty....
We probably need a zImage-empty file, to install our custom rom's kernel
Ty for any update!

[ROM][PORT] PAC ROM UNOFFICIAL for Redmi Note 4G Single Sim

Hi guys, this is my first port, i am not a developer, i have just followed a rom porting guide.
created by @rishabh.raj37
This Rom is based on lastest CM11 build by jkaz.
Working :
Everything..(Including Headphones)
Not Working :
None
Procedure :
1. Download the Rom and gapps and copy both files in to sd card or ext-sd.
2. Reboot into recovery
3. wipe cache, dalvik cache, data...
4. Install both rom and gapps.
5. Reboot phone...
I am not responsible for bricked devices.
Credits:
Xda
Cyanogenmode team
Pac-man developers
Mokee developers,
@LiquidPlacidity
JKaz
@Jamil69
@umangleekha (For Headphone fix patch)
I take credit only for porting this rom to our device, but i don't take credit any other way...
ROM Download
Gapps
For root access flash zip file from the link
SuperSu
Note:
1. - Just edit the build.prop, find the line: ro.sf.lcd_density = 270 change the value to 320 save it and reboot.
2. - Download system app remover from playstore
- Open it and grant root permission
- select and uninstall nfc service and pac console.
- reboot.
- this removes nfc wake and pac console force close.
Great News.. Thanks Bro, finally another cusrom for Dior.
asrupesh said:
Hi guys, this is my first port, i am not a developer, i have just followed a rom porting guide.
created by @rishabh.raj37
This Rom is based on lastest CM11 build by jkaz.
Working :
Everything..(Including Headphones)
Not Working :
None
Procedure :
1. Download the Rom and gapps and copy both files in to sd card or ext-sd.
2. Reboot into recovery
3. wipe cache, dalvik cache, data...
4. Install both rom and gapps.
5. Reboot phone...
I am not responsible for bricked devices.
Credits:
Xda
Cyanogenmode team
Pac-man developers
Mokee developers,
@LiquidPlacidity
JKaz
@Jamil69
@umangleekha (For Headphone fix patch)
I take credit only for porting this rom to our device, but i don't take credit any other way...
ROM Download
Gapps
For root access flash zip file from the link
SuperSu
Click to expand...
Click to collapse
Thanks for this cusrom bro, i will try it.
There's a nfc wakelock and Systemupdateservice wakelock. Other than that the rom is functional.
Thanks bro, this runs better than mokee and doesn't have shady apps.
screenshot plz...
So far everything works fine.
Bugs:
1) Everytime Wi-Fi is turned on, PAC Console forced close.
2) The resoulution is kinda small & look like tablet.
Maybe I can tweak the build.prop about the resolution.
I can confirm what zahinasaur wrote:
1) PAC Console force closes, but for me, on each boot, but after I disabled it in Manage Apps, it's OK.
2) Resolution looks strange, but it's also OK.
3) New thing: isn't App2SD functionality enabled on this ROM? Can you please package a new version with this functionality enabled?
Besides these, it's works much better than Mokee ROM at least for me, so thank you for your work!
Resolution fix
Just edit the build.prop, find the line:
ro.sf.lcd_density
Change the value & reboot.
Mine works best at value 320. You can try different value.
Thank you, this works. I'm more happy with the 296 setting, but you wrote the correct solution for this problem.
2 problems left.
By the way, not installing SuperSU gives you the default (CM?) SU implementation which works better at least for me, for e.g. BusyBox installation.
1st post updated...
headphone fix
asrupesh said:
1st post updated...
Click to expand...
Click to collapse
Is the headphone fix included in the rom or I have to flash something for it?
and what about system update service bug? - for this I have a solution
download my android tools from play store
in service tab -> system -> google play services -> at the end of the list there is system update service, just disabling it worked for my old phone, which had similar bug...
Hope this helps..
whats new??
Guys, do you see the external SD card?

(Mod) DUAL BOOT N910w8 (Stock and Cm)

Hello I have made a very detailed video showing how to get Stock Samsung Lollipop (5.0.1) and CyanogenMod 12.1 (5.1.1) on the same phone [n910w8] dual booting.
THIS IS DONE AT YOUR OWN DESCRETION and I am not responsible if something goes wrong or you do something wrong. I have repeated the process at least 10 times to see how it works. Even did it on a Samsung Galaxy S4 with no issues.
This video is demonstrating the installation process for the Galaxy Note 4 n910w8 (Canadian snapdragon version used in video)
PLEASE TAKE YOUR TIME even watch the video a few times before you give it a try. In the end you can always flash stock Samsung Rom and do a factory reset.
I really enjoy using this feature and having the choice between two different roms on the same phone.
You can share apps from your stock Samsung Rom to your Cyanogenmod Rom without having to reinstall most of your apps. Saving lots of space.
I hope you enjoy.
Like.
Subscribe.
Click an add or two.
Thanks and a wonderful day.
Happy dual booting.
VIDEO LINK:
Samsung Galaxy Note 4 Dual Boot/multi Rom support:
https://youtu.be/CpegzNc4ZH0
Download Link Dual Boot Patcher:
https://snapshots.noobdev.io/
Download Link CM 12.1 (trltetmo) WORKING ON N910w8:
https://download.cyanogenmod.org/?device=trltetmo
Download Link Cyanogenmod Google Apps:
http://wiki.cyanogenmod.org/w/Google_Apps
Thanks:
chenxiaolong
Working on getting support brought to the Samsung Galaxy Tab S 8.4 also. Awaiting conformation, working with the developer. No garinties but fingers crossed that another top device gets dual boot compatibility.
Does anyone have a link to this build????
cm-12-20150413-NIGHTLY-trltetmo.zip
i keep trying on cyanogenmod website but the link is down.
If anyone could help it would be greatly appreciated.
It would really help with Google cardboar/vr testing. Native sbs is reported working on the rom I am looking for and it would be worth a try.
Nice mate
So by using FolderMount I am able to save so far 3gb of space on my data folder. I transfer app data to external SD card. Link the app data on external SD card with FolderMount which tricks the app into thinking it is installed on internal data.
Then I created a backup in FolderMount. Switch roms load FolderMount. Restore backup for FolderMount. Restore link app data locations because cm and touchwiz see external SD card different and FolderMount corrects this thankfully.
Click the green linking tab a few times and FolderMount will recognize the data.
As I said I have saved 3gb of room on my internal data having app data on external SD card.
If something like this was built into our dualboot patcher it would make things easier. Maybe if we spoke to the developer of FolderMount. If not using both FolderMount and Dual boot patcher I now have 3 roms on my Note 4 and almost 4gb free space on internal data between all 3 roms. Look at the pics of before in my previous comment and this one to see.
Just finding ways of maybe booting 4 roms on one phone.
Will report back.
Think I am on to something, let me know what you think. Give it a try possibly. I will be making a youtube video to help better demonstrate.
Before and after of data saved
My current Tri Boot state on my Note 4
Currently running Touchwiz stock lollipop 5.0.1 (primary partition), cm12.1(secondary partition) and cm12(data partition) all on the same phone.
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
samurai_vara said:
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
Click to expand...
Click to collapse
Try reinstalling cm12 and sharing again once you boot up.
Leonidas87 said:
Try reinstalling cm12 and sharing again once you boot up.
Click to expand...
Click to collapse
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
samurai_vara said:
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
Click to expand...
Click to collapse
Once you do those 3 steps all apps should share between both the primary and secondary Rom once you do a quick reboot after enabling the app sharing. Whenever you install a new app on one or the other Rom and then boot in to one of the roms you will usually see android upgrading or upgrading apps something like that during boot up. But yea you only need to enable app sharing in the second Rom not primary. Everything from the secondary Rom seems to share with the primary Rom. Overall it is a great system. Complicated in thought but it works. Once you get a feel for it you will be impressed.
Nice. I will try this when I get home. Been wanting to run CM but gear vr has me stuck on touch jizz. Will report how it works.
Sent from my SM-N910T using Tapatalk
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
chrisa887 said:
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
Click to expand...
Click to collapse
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Leonidas87 said:
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Click to expand...
Click to collapse
I see, I want the cm12 as my secondary rom so I patch it first then install it then I patch the gapps then install them then I can reboot to secondary rom and set everything up right?
Sent from my SM-N910T using Tapatalk
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Leonidas87 said:
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Click to expand...
Click to collapse
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Great job, thank you dev.
I have question about App Sharing. Should I install Gapps on both roms or only on Primary and share them?
chrisa887 said:
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yes patch then install. No need to reinstall Google apps all that will still be there.

After upgrade from Android 4.2: Stuck with Android 5.1 and GApps for 4.2, unusable

I have painted myself into a corner with a Samsung Galaxy S 2. It is my
girlfriend's phone and she wanted to play Pokemon Go. The Android
version there was 4.2 (CyanogenMod) with appropriate Google Apps. It has been
working reasonably well.
Pokemon Go needs to have at least Android 4.4, so an update was due. There was
a CyanogenMod snapshot of 12.1 (Android 5.1) which was installable from within
the old CyanogenMod. I hoped that this would go through well and we did the
upgrade. After the upgrade it indeed had Android 5.1. However, the Google Apps
directly crash, especially the Trebuchet launcher. This means that one cannot
start any apps or use any Google services. Especially the Google Play Store
does not work, it shows the error message [RH-01].
I first thought that we had upgraded to Android 4.4, therefore I installed the
Open GApps nano for 4.4:
(Due to forums policy I am not allowed to hotlink or link to the images.
So this is the best I can do now.)
http ://i.imgur.com/DRHqxNx.jpg
This then (unsurprisingly) failed:
http ://i.imgur.com/qjzrDKw.jpg
At least the error message was really helpful! So then I downloaded Open
GApps nano for 5.1. This then also failed because the GApps that I
have installed together with CyanogenMod years ago were not Open GApps but some
other package:
http ://i.imgur.com/0tI6eEn.jpg
At this point I got uneasy. Her phone turned into a paperweight with a
lockscreen. Since I could not seem to move the GApps forward without flashing
the ROM again, I tried to to so without wiping the data. For this I selected
the update mechanism in Cyanogen Recovery and flashed the Android 5.1
ROM onto the device. After this I tried to install the GApps again. However,
those still fail to install. Here I would guess that the CyanogenMod 12.1
“installer” does not wipe the system partition and leaving remnants of the old
GApps package there.
Since it got late I tried to at least get back to the old state and downloaded
the CyanogenMod with Android 4.2. Trying to flash this failed as the device
type was not picked up correctly:
http ://i.imgur.com/yZ9ilM1.jpg
I do not understand this error. This (or a very similar) version of CyanogenMod
has been present on the device up til yesterday. Why doesn't that work any
more.
A friend of mine suggested to replace the Cyanogen Recovery with the
TWRP. For this I have downloaded the appropriate IMG file from Team Win.
Then using heimdall-frontend on Linux I pulled out the PIT file and put the PIT
file back with the twrp.img file onto the recovery partition. Although the
heimdall-frontend told me that I had a success, there was still the Cyanogen
Recovery.
My current guess is that this phone has hardware which does not allow for a
separate recovery partition unless there is an IsoRec kernel installed. The
CyanogenMod 12.1 should have that, but the recovery is probably the one from
the CyanogenMod 10.1 as the option to update the recovery partition was not
checked when performing the OTA upgrade.
I'm stuck and I have no idea how to get the phone into a working condition. Do
you perhaps have an idea what I could do now?
Hi,
CM12.1 Snapshot unfortunately doesn't have isorec, hence you can not install the twrp .img file.
You can flash this and it will give you isorec kernel:
https://www.androidfilehost.com/?fid=24407100847293132
You will then be able to flash TWRP here:
http://forum.xda-developers.com/devdb/project/dl/?id=17876
Once that's install, reboot back into the recovery and you should have TWRP.
Wipe /system, /cache and /dalvik cache.
Flash ROM then flash gapps, then flash isorec kernel again (because once you flash ROM, you will have overwritten the kernel).
If you can't install gapps and it says you have insufficient space, use opengapps 5.1 pico instead.
gsstudios
I managed to install the IsoRec kernel. Then flashing TWRP worked and I was able to use it. The installation of Android 5.1 has worked, but I still had issues after cleaning up /system. Installing Android 4.2 or 4.4 did not help, it kept crashing either way. 4.2 even had an infinite boot loop.
Then I ended up wiping /data and installed 5.1 and the GApps Pico package. Then everything worked, even Pokémon Go.
Thank you for your help, you saved a phone from being unusable .
I have a smiliar issue. I updated to CM 13.0 as well to newest TWRP. I wanted now to install Open Gapps Pico package but can't flash because of insufficient system space.
Do you have an idea what to do now ?
Achi92131 said:
... but can't flash because of insufficient system space.
Click to expand...
Click to collapse
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Python Guy said:
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Click to expand...
Click to collapse
Thanks Phyton Guy, I will do that.
Tired of failed installed GAPPS ? Different reasons and many many lost time ...
Here is alternative :
1. Install UC Browser
2. Inside , you will find : 9Apps ( the same app as PlayStore )
3. Install 9Apps
- same app as PlayStore
- every app related to Google : working fine.
*** BONUS - install Video Downloader for UC Browser - search Google for this as APK file .
you can download on your phone any video on youtube , inside UC Browser .
That's it ! It's so simple and ...No more Google domination on your Phone !

[ROM][Android 7.1.1]Unofficial Okeys Builds[LineageOS 14.1][OMS7]

Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.

Categories

Resources