Related
Voxive GApps for 4.4.x [DISCONTINUED]
Formerly "Famigo AROMA GApps"
Long time no see, huh? Well, contrary to the Post title, I am back but it's different now! Why?
THESE GApps ARE NOW APART OF Open GApps!
I wanted to cover a few things about this package real quick though!
First, the source code has been moved and updated (the old actually was missing the newer releases!) onto GitLab. One note though is that the APKs themselves are managed using Git-Annex, so you will need that to "complete" your repo. Find the source code here: http://gitlab.com/TeamVoxive/vox_gapps/
Second, Open GApps includes a AROMA version too that will be easy for you guys to migrate over to!
Third, my other project, Vox Remover is on hiatus as it is semi-replaced by Open GApps as not only it includes more removals than the original PA/TK Gapps these were based on but it also includes the ability to remove ANY app (have to configure in config file).
Lastly, I want to mention my "other" project that I am still working on. Vox Variety is a 24-hour variety station playing a lot unique stuff!
You can find Open GApps at http://opengapps.org with daily, auto-generated builds for 4.4x to 5.1x on arm(64) and x86(_64) with a ton of variants!
XDA:DevDB Information
Voxive GApps, Tool/Utility for the Android General
Contributors
dotmaniac, 3DSammy, amarullz, AOSPA, TKruzze
Source Code: http://gitlab.com/TeamVoxive/vox_gapps/
Version Information
Status: No Longer Updated
Current Stable Version: v12
Stable Release Date: 2014-04-11
Created 2013-12-06
Last Updated 2015-06-27
Create your own Remover Script
QUICK HOW-TO
We will cut everything after a pound sign/hashtag/"#" from the script. That is, all the tutorials, app descriptions, and apps you want to keep; thus, only leaving the script with the files you want to remove
Edit the list below as you see fit, examples:
AdobeReader.apk > Removed (because there is no "#")
#AdobeReader.apk > NOT Removed (because of "#")
AdobeReader.apk #PDF Reader > Removed (but extra text ignored)
CUSTOMIZING
By making a file named junk.txt in the /sdcard/Famigo/remover folder you can add files from anywhere and use wildcards to cut similar items.
Files and folders deleted ARE case-sensitive, examples:
/path/to/file/file.txt > Deletes file.txt
/path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"
/system/app/Apollo.apk > Deletes the system app Apollo ... REMEMBER to scan Everywhere during install when including FULL PATH
/data/app/Facebook.apk > Deletes the user app Facebook (if that's what it's called) ... REMEMBER to scan Everywhere during install when including FULL PATH
Apollo.apk > Deletes the app Apollo ... REMEMBER to Scan /system and/or /data depending on place
Apollo > Deletes apps named Apollo ... REMEMBER to Scan /system and/or /data depending on place
Apo* > Deletes all files starting with "Apo" ... Be CAREFUL with wildcards.
WHAT TO SCAN
During the install, it will ask you which folders to scan. By default, we will only Scan /system/(priv-)app which is where system apps and PARTICULARLY junk apps are. However, you may want to erase user apps that are in /data/app or other system files located elsewhere. Unless you are specifically trying to remove user installed apps - do not check Scan /data/app and unless you are trying to cut a specific file or folder (ringtones, wallpapers, etc) - do not check Scan Everywhere
Reserved
Reserved
Where's the download link?
Sent from my Droid Razr Maxx HD (GSM)
XBlackChaosX said:
Where's the download link?
Sent from my Droid Razr Maxx HD (GSM)
Click to expand...
Click to collapse
I am still waiting for it to upload to devdb!
Sorry for the really long wait but DevDB never wanted to upload...
So I decided to tweak a few things and upload to DevHost!
Download Now!
Does it only delete the apk,s or all xml,s and lib,s too?
GREEEEETZ!!!
-CALIBAN666- said:
Does it only delete the apk,s or all xml,s and lib,s too?
GREEEEETZ!!!
Click to expand...
Click to collapse
It deletes anything that I am aware of.
So if for example, you was going to delete the stock Email app; it would also erase Exchange Services.
Sent from my Nexus 7 using Tapatalk
The new version now available with updated 4.4.1 libs, apps, and more removable bloat!
Changelog
v3
App Improvements:
Updated Core Apps and libs to 4.4.1 Variants
Code Improvements:
Moved Info Screen to Menu
More removable apps
can you please add the google dialer
MaddScientist said:
can you please add the google dialer
Click to expand...
Click to collapse
Sorry, their is a whole bunch of issues trying to add it. Also I don't have a phone to test it with.
Sent from my Nexus 7 using Tapatalk
Is this Gapps package still compatible with a 4.4 ROM? I did not read anywhere if the update to 4.4.1 changed the ROM version requirement.
Thanks for this contribution as I've been looking for a selectable 4.4+ gapps package for a while.
3DSammy said:
Is this Gapps package still compatible with a 4.4 ROM? I did not read anywhere if the update to 4.4.1 changed the ROM version requirement.
Thanks for this contribution as I've been looking for a selectable 4.4+ gapps package for a while.
Click to expand...
Click to collapse
Yes, it is still compatible with 4.4.
Sent from my Nexus 7 using Tapatalk
Continuity
I found this Gapps this morning and installed it on my 4.4.1 Tab2. It is absolutely great!! Having the option of only installing what I really need is fantastic. My only question is if this is a one shot deal or do you intend to update it on a regular basis?
motisu said:
I found this Gapps this morning and installed it on my 4.4.1 Tab2. It is absolutely great!! Having the option of only installing what I really need is fantastic. My only question is if this is a one shot deal or do you intend to update it on a regular basis?
Click to expand...
Click to collapse
I intend to update it every time AOSPA updates theirs.
Sent from my Nexus 7 using Tapatalk
dotmaniac said:
I intend to update it every time AOSPA updates theirs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That's great to hear. One suggestion: I don't know if it is possible, but since most of the latest ROMs require you to reinstall the Gapps after flashing the ROM, and since this Gapp requires you to pick and choose which apps you want and don't, it would be very useful to have a way of saving the choices so that you wouldn't have to go through the whole selection process every time you reflash a ROM. Maybe it could be done in a "preprocess" step on the PC or on the SD card as a small saved file?
motisu said:
That's great to hear. One suggestion: I don't know if it is possible, but since most of the latest ROMs require you to reinstall the Gapps after flashing the ROM, and since this Gapp requires you to pick and choose which apps you want and don't, it would be very useful to have a way of saving the choices so that you wouldn't have to go through the whole selection process every time you reflash a ROM. Maybe it could be done in a "preprocess" step on the PC or on the SD card as a small saved file?
Click to expand...
Click to collapse
During the gapps flash process the Aroma UI selections are all saved in two files:
/tmp/aroma/gapps.prop
/tmp/aroma/remover.prop
Just in case you do not know "/tmp" disappears after the flash file completes.
Those would be the files to save. Access to user internal storage is possible assuming if has not been wiped prior to ROM flashing. Of course saving to SD/OTG storage would even get around that situation. All this assumes the two prop files could be retreived from where they are stored before Aroma starts executing. I have been looking at this over the last hour just to see if it is possible.
3DSammy said:
During the gapps flash process the Aroma UI selections are all saved in two files:
/tmp/aroma/gapps.prop
/tmp/aroma/remover.prop
Just in case you do not know "/tmp" disappears after the flash file completes.
Those would be the files to save. Access to user internal storage is possible assuming if has not been wiped prior to ROM flashing. Of course saving to SD/OTG storage would even get around that situation. All this assumes the two prop files could be retreived from where they are stored before Aroma starts executing. I have been looking at this over the last hour just to see if it is possible.
Click to expand...
Click to collapse
motisu said:
That's great to hear. One suggestion: I don't know if it is possible, but since most of the latest ROMs require you to reinstall the Gapps after flashing the ROM, and since this Gapp requires you to pick and choose which apps you want and don't, it would be very useful to have a way of saving the choices so that you wouldn't have to go through the whole selection process every time you reflash a ROM. Maybe it could be done in a "preprocess" step on the PC or on the SD card as a small saved file?
Click to expand...
Click to collapse
I will look into it!
Sent from my Nexus 7 using Tapatalk
dotmaniac said:
I intend to update it every time AOSPA updates theirs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
great stuff think this will be my go to package
---------- Post added at 07:56 PM ---------- Previous post was at 07:47 PM ----------
can you please add mirrors?
dotmaniac said:
I will look into it!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I couldn't figure out how to get it to work... Sorry guys!
MaddScientist said:
great stuff think this will be my go to package
---------- Post added at 07:56 PM ---------- Previous post was at 07:47 PM ----------
can you please add mirrors?
Click to expand...
Click to collapse
I will add some mirrors as soon as possible!
Sent from my Nexus 7 using Tapatalk
Let's keep all cm12 preview discussion in here please.
Cm12 preview builds.
http://downloads.codefi.re/jrior001/cm/evita
Warning!! These are still in early development and any build could be highly unusable!! If you dare continue, have a backup ready and Good luck.
Thanks for the build jrior!
I've been running 11/27 for a day now, very smooth and fast - too soon to say about battery life.
Just a heads up for anyone flashing - 11/28 and 11/29 the SD card doesn't work. On 11/27, you can't answer incoming calls and can't music over Bluetooth.
EDIT: No SD on 11/30 either.
Glad to see android lollipop on beautiful evita, thanks jrior001 ?
Would you like us to report what's working and what's not ?
Working Dialer and SD
This information is for those who are having dialer force close issues with 27/11.
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Also, the latest Google Camera works great on this ROM, and fixes the 'squashed' preview when taking 16:9 photos.
http://www.apkmirror.com/apk/google-inc/camera/camera-2-4-024-1564481-30-apk/
00Scott00 said:
Hi all,
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Click to expand...
Click to collapse
So you're in 27/11 and everything is working?
I just flashed 1st 29/11 and later 27/11 and I just get everything working.
Working.
Mexickano said:
So you're in 27/11 and everything is working?
I just flashed 1st 29/11 and later 27/11 and I just get everything working.
Click to expand...
Click to collapse
I also flashed 27/11 and all seems good so far. Been up for almost 5 hours. No glitch to report so far.:good:
Hey dudes, any feedback on latest build 12/01 please?
azirgi said:
Hey dudes, any feedback on latest build 12/01 please?
Click to expand...
Click to collapse
Remember that is only an Alpha release, dont expect that everyone here try the new releases for you, you always can do a backup of your actual ROM and install this one if something goes wrong you always can comeback.
I will test the 12/01 version I used the 11/27 version and only notice one bug when receiving whatsapp on my lock screen went crazy shaking and disappearing background if I try to view the notification if I just went home and open the application this problem didn't occur.
12/01 Sdcard still broke, testing a pending fix from cm crew shortly
tested 12/01 version external storage is not mounted
00Scott00 said:
Hi all,
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Click to expand...
Click to collapse
My dialer appears to be working on 11/27, what issues did you come across that you needed the 11/30 dialer?
buradd said:
My dialer appears to be working on 11/27, what issues did you come across that you needed the 11/30 dialer?
Click to expand...
Click to collapse
I had FC every time i recieved a call. Did you make and receive calls?
00Scott00 said:
I had FC every time i recieved a call. Did you make and receive calls?
Click to expand...
Click to collapse
Ive been on the 11/27 build last couple of days and have been able to receive and make calls without any issues.
OK, then ignore my post
frozenreality44 said:
tested 12/01 version external storage is not mounted
Click to expand...
Click to collapse
This:
jrior001 said:
12/01 Sdcard still broke, testing a pending fix from cm crew shortly
Click to expand...
Click to collapse
Hboot ver problem :|
hi dear developers :
i have a htc ONE XL (UTL) With CIDNUM: HTC_J15 and ModelID : PJ8350000
for CM 12 I need to upgrade my hboot to at least 2.14 version
for Evita UTL i cant find Newer HBOOT With This CID And Modelid
Please Help What can i do quickly ???
Is there any changelogs for these builds?
Q&A for CyanogenMod 12.0 for Photon Q
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 CyanogenMod 12.0 for Photon Q. 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!
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0
I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!
Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!
CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...
CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).
I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.
hi,
well, as you know there is problem with CyanogenMod(and some other aosp roms) wifi in some countries and the problem is due to wifi_country_code value inside global database.
so after reading HTCZ715E amazing guide i made this flashable zip for those who still have problem with wifi in ivanich's CyanogenMod.
Installation
flash it via recovery(no need to wipe)
Credits:
@ivanich for his awesome rom
@HTCZ715E for WiFi Country Problem Solving guide
Thank you
I'm going to experience
@jinxul if it's only related to the record in the global table of settings storage database, I thought, wouldn't it be easier to use an init.d script with an addon.d script?
For example:
Code:
#!/system/bin/sh
# Set wifi country code
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value=nz where name='wifi_country_code';"
hinxnz said:
@jinxul if it's only related to the record in the global table of settings storage database, I thought, wouldn't it be easier to use an init.d script with an addon.d script?
For example:
Code:
#!/system/bin/sh
# Set wifi country code
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value=nz where name='wifi_country_code';"
Click to expand...
Click to collapse
the main problem is in the telephony-common.jar. every time that wifi turns on framework will rewrite the record on its own... so framework has to be patched(and all that will do is to stop rewriting wifi_country_code on every time wifi turns on).
i also put an script in the zip(similar to this) to change the value back to null but that's just for those who don't want to wipe their data(cause its wont work if there is already a value for wifi_country_code)
so init.d wont do anything as long as framework isnt patched.
jinxul said:
the main problem is in the telephony-common.jar. every time that wifi turns on framework will rewrite the record on its own... so framework has to be patched(and all that will do is to stop rewriting wifi_country_code on every time wifi turns on).
i also put an script in the zip(similar to this) to change the value back to null but that's just for those who don't want to wipe their data(cause its wont work if there is already a value for wifi_country_code)
so init.d wont do anything as long as framework isnt patched.
Click to expand...
Click to collapse
I thought that but when I changed mine to 'us' and toggled wifi on and off a few times and connected to network it didn't revert back for me. I tried 'uk' too but couldn't find any networks when turning wifi on.
hinxnz said:
I thought that but when I changed mine to 'us' and toggled wifi on and off a few times and connected to network it didn't revert back for me. I tried 'uk' too but couldn't find any networks when turning wifi on.
Click to expand...
Click to collapse
reboot is required when you change it manually.. system wont just read it like that unless you tell it to do so, and you cant do that with sqlite3. you need an app/service with WRITE_SETTINGS permission (android.permission.WRITE_SETTINGS).
Let me chime in:
Similar Wi-Fi issues have been persistent across my previous two devices running Android 5+. Setting the Wireless channel of your network to 11 or below (U.S. standard) fixed it. If you don't live in a too dense area - eg. have free uninterfered channels in that scale - then I suggest using those. EU channels (12,13) break far too often due to this specific issue which seems either upstream or hardware-specific. To your information, the three (with this) tested devices all have BCM4329 Wireless modems.
If anyone tries this instead, let me know if it worked here as well.
I would really appreciate if you release Wifi Fix for ivanich's CyanogenMod CM11
this4you said:
I would really appreciate if you release Wifi Fix for ivanich's CyanogenMod CM11
Click to expand...
Click to collapse
as i said in OP i dont have cm11 so i need telephony-common.jar for it. find it (system/framework/telephony-common.jar) and give it to me.
CARBON-KK-UNOFFICIAL-KERNEL-3.4-20141123-1107-pyramid
and again Hi
here you go telephony-common.jar taken from Carbon KK ROM
jinxul said:
as i said in OP i dont have cm11 so i need telephony-common.jar for it. find it (system/framework/telephony-common.jar) and give it to me.
Click to expand...
Click to collapse
there I found it as you directed me and Just Uploaded or should I say posted here for you to get it patched
However it is to say that once I tried the Guide to patch the file but it did not work at all and I faced FC at phone state
actually I could not find the line mentioned in the guide to edit that ...
by the way I`M proud of you
this4you said:
and again Hi
here you go telephony-common.jar taken from Carbon KK ROM
Click to expand...
Click to collapse
try this and let me know the result.
jinxul said:
try this and let me know the result.
Click to expand...
Click to collapse
Thank you ill try it now
in a minute ...
---------- Post added at 08:22 AM ---------- Previous post was at 08:05 AM ----------
jinxul said:
try this and let me know the result.
Click to expand...
Click to collapse
Thank yooooooooooooooooooou It worked !!:good:
I wounder is it possible to put the patched telephony-common.jar inside the Zipped ROM and replaced the old one ?
it may sound rude but as the last request can I upload the vanich's CyanogenMod`s telephony-common.jar ?
this4you said:
Thank you ill try it now
in a minute ...
---------- Post added at 08:22 AM ---------- Previous post was at 08:05 AM ----------
Thank yooooooooooooooooooou It worked !!:good:
I wounder is it possible to put the patched telephony-common.jar inside the Zipped ROM and replaced the old one ?
it may sound rude but as the last request can I upload the vanich's CyanogenMod`s telephony-common.jar ?
Click to expand...
Click to collapse
unzip the rom, replaced it then zip it. it should do the job.
sure.. which one is it?(cm11 or 12)
jinxul said:
unzip the rom, replaced it then zip it. it should do the job.
sure.. which one is it?(cm11 or 12)
Click to expand...
Click to collapse
up to here I was to use viper`s ROM cause of KK`S wifi issues but here you wiped out the nightmare , and I must give you a big thanks...:good:
and again cm-11-20150607-UNOFFICIAL-pyramid ...
but i have to download it first and then upload it here
this4you said:
up to here I was to use viper`s ROM cause of KK`S wifi issues but here you wiped out the nightmare , and I must give you a big thanks...:good:
and again cm-11-20150607-UNOFFICIAL-pyramid ...
but i have to download it first and then upload it here
Click to expand...
Click to collapse
here you go the telephony-common.jar of cm-11-20150607-UNOFFICIAL-pyramid
this4you said:
here you go the telephony-common.jar of cm-11-20150607-UNOFFICIAL-pyramid
Click to expand...
Click to collapse
OP updated to include cm11 patched file.
jinxul said:
OP updated to include cm11 patched file.
Click to expand...
Click to collapse
thank you very much
Great work
After months of searching for a solution
Wi-Fi now works nicely
Without any problems
Thanks
Hi
Please for cm12.1 (06/29) ivanich
Thanks
LineageOS 13 for Life One X2
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know if you find anything else)
Camera
Flash (works but reversed front to back)
Fingerprint
Downloads:
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhVnppRTdHbjZyZEk?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhRGhuQVNsWUFsa0k/view?usp=sharing
Kernel: https://github.com/meganukebmp/android_kernel_blu_life-one-x2
Gapps: http://opengapps.org
Special thanks to Ieatgravity and Tydraco for all their support.
Screenshots:
(screenshots taken with the PitchBlack | DarkRed CM13/12 theme)
Theme: https://apkpure.com/pitchblack-darkred-cm13-12/com.resurrectionremix.pitchblack
Changelog
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2:
fixed gapps (fixed "there was a problem communicating with google servers" error)
Lineage-13.0-09042017-2137-UNOFFICIAL-Life_One_X2:
Fixed theme manager crashing
Cleaned up some of my code
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
Reserved
Great work! I look forward to testing this.
I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?
Daisuke1988 said:
I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?
Click to expand...
Click to collapse
Go into TWRP and format Data. That fixed it for me.
srgrusso said:
Go into TWRP and format Data. That fixed it for me.
Click to expand...
Click to collapse
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?
Daisuke1988 said:
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?
Click to expand...
Click to collapse
Sorry unfortunately I haven't been able to get them working either. I've been getting "there was a problem communicating with google servers" error. I'm currently trying to fix this. I think it is related to this error from dmesg:
Code:
[ 1398.055688] type=1400 audit(1503798238.823:50): avc: denied { search } for pid=7470 comm="IntentService[P" name="com.google.android.gsf" dev="mmcblk0p46" ino=803248 scontext=u:r:untrusted_app:s0:c522,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=1
I have been using other apk resources for now. I'll add opengapps to the list.
Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.
The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough
srgrusso said:
Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.
Click to expand...
Click to collapse
man youre awesome!
kiomet said:
The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough
Click to expand...
Click to collapse
im assuming once the finger print sensor is working we can use it as gesture navigations right?
Daisuke1988 said:
im assuming once the finger print sensor is working we can use it as gesture navigations right?
Click to expand...
Click to collapse
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.
New build uploaded with gapps fixed.
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2.zip
srgrusso said:
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.
Click to expand...
Click to collapse
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )
ieatgravity said:
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )
Click to expand...
Click to collapse
on the stock rom it has the option to use it as a agivation option under the finger print settings
Daisuke1988 said:
on the stock rom it has the option to use it as a agivation option under the finger print settings
Click to expand...
Click to collapse
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.
ieatgravity said:
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.
Click to expand...
Click to collapse
well it will come. over all, the rom is working great.