Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.
Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app
Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?
Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat
Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.
tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app
For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing
Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).
I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.
Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store
Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip
New google keyboard is available: link
DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.
tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!
Related
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.
Unofficial CM 10.2 builds for Nexus 4
Hi all,
I decided to post my unofficial builds of CM10.2 for Nexus 4 after being asked by a few people in the CM10.1 Q&A and development threads, in order to consolidate questions and keep clutter down in those threads I decided it was best to make a thread specifically for these builds.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
How to install:
First time installing or coming from another 4.3 based ROM:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Wipe data/Factory reset
Flash the ROM
Flash Gapps
Reboot
Coming from a previous CM10.2 nightly:
Download the ROM
Reboot into recovery
Flash the ROM
Reboot
Coming from a previous CM10.1 nightly:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Flash the ROM
Flash Gapps
Reboot
Builds:
Built from official CM sources only, no cherry-picks, no changes, no additions. I will not be changing the official sources in any way so don't bother asking.
http://goo.im/devs/thracemerin/cm_builds/mako
Note: These builds are produced by my buildbot at 4am US Eastern time (build + upload takes approximately 90 minutes), the repo will be synced during the build process to ensure that the latest sources are used. The completed file size should be approximately 196MB, so if the latest download isn't it's not fully uploaded yet
Note 2: If the build fails for some reason, I will try to build one later in the day, but if I can't you may have to wait until the following day.
How to get root:
In order to get root access, you need to do the following:
Activate the Developer Settings by going to Settings->About Phone ant tap on the Build Number 7 times.
Go to Settings->Developer Options and change the Root Access to 'Apps and ADB'
You may also need to activate USB Debugging in Developer Options (some people say you do, others say you don't)
Note: If you have flashed a kernel that comes with it's own boot.img package it may not have the correct instructions to start the internal su daemon as a result root will stop working, at the moment the best way to fix this is to not use that kernel. If you absolutely have to use a custom kernel you may need to flash SuperSU for the moment or ask your kernel dev to support this feature.
Known Issues
None that I'm aware of, but keep in mind that these are pre-nightly builds and could contain bugs and/or non-working features at any time.
Thanks
Google
CyanogenMod
F.A.Q
Q: When will official builds start?
A: Soon
CyanogenMod Blog said:
“Who cares about the old, gimme 10.2!”
We have one last internal item on our checklist before we open the floodgates on CM 10.2 nightlies. We fell into an old habit in 10.1 and the settings menu became more cluttered than we would like, and at times confusing both in presentation and in code. We are working to resolve this before 10.2 nightlies begin, so the transition is less jarring than it would down the line. Expect the new layout to be in effect with the first nightlies. If all goes well, we are talking days, not weeks.
In the meantime, the majority of our 10.1 roster have transitioned to being 10.2 capable. This means for you at-home builders, things should be in a fairly good spot for your own personal builds. If you want to checkout all the stuff we’ve merged, click through the pages.
Click to expand...
Click to collapse
Q: What is SELinux?
A:
CyanogenMod Blog said:
What is SELinux?
The project’s official description reads “SELinux is a security enhancement to Linux which allows users and administrators more control over access control.”
SELinux is a set of Open sourced and peer reviewed changes to the core Android Software stack to help prevent apps from performing malicious activities. This is done by establishing a set of policies that act as mandatory access controls (MAC). Depending on the policy, it can do things such as prevent apps from running or accessing specific data, to preventing root access altogether.
SELinux has wide-scale adoption throughout the linux landscape, with Fedora, Red Hat and others incorporating policies to better the system security. The default policies are usually written per distribution, by their maintainers – we have begun this process for CyanogenMod.
We will be working on this policy creation in parallel to Google’s own policies for Android, which we believe will be released with the Android 4.3 source; effectively getting us ahead of the eventual 4.3 source release. As this process is open source, policy creation and suggestions will be handled via our gerrit instance.
What it’s not?
SELinux is not a backdoor for government agencies to spy on you. It is not PRISM, PROMIS, CARNIVORE, The Great Firewall or any other ominous Big Brother-like initiative.
Access Control Modes
By default, we will be shipping with SELinux capabilities enabled in the kernel, but in a Permissive mode. What this means is that your phone will behave exactly as it currently does, with no noticeable change to the user.
There are 3 modes in total, Enforcing, Permissive and Disabled. While in Enforcing mode, SELinux policies are enforced, preventing whatever causes a violation (ie su). Permissive mode logs policy violations, but does not prevent the activity that caused it. Disabled turns SELinux off.
We are using Permissive mode as our default so we can come up with sensible policies. If you submit a log for us to analyze (via JIRA) for SELinux policy improvements, the logged exceptions will be of high value.
This will be an ongoing process as we work to incorporate sensible policies for each device repo. As always our source is available on Github and patches will be peer reviewed via gerrit. For those more attuned to personal data security, you are welcome to watch and audit our efforts. For the rest of you, sit back and relax – no need for pitchforks.
Click to expand...
Click to collapse
Third
amazing mate, keep it up the good work!
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Feedback
Nice man, thanks for this work, btw, the front cam is upside down.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
BaNkS only includes the essential Google Apps that are needed for the Google experience -- working sync services, the Play Store itself, and so on. He provides other Google Apps in the form of an add-on, a separate zip, for the keyboard/camera/etc. Basically, most of the Google Apps are now available to download from the store itself (Keep, Earth, Maps, Voice Search, Search and so on). That wasn't always the case, but still some are releasing a full Google Apps package with everything.
The minimalistic approach is obvious - only install what is necessary, manually get anything else yourself. That is why the banks package is small because it is not forcing other apps that people may or may not use since they could simply download it themselves if they wanted to. I assume the 200mb or more package is simply every single Google APK that comes with the official factory images.
lwkkazz said:
Nice man, thanks for this work, btw, the front cam is upside down.
Click to expand...
Click to collapse
Weird, doesn't seem to be for me.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
markd0wn basically covered it, but it also depends on what you want in your /system directory, most of the apps that used to come in Gapps packages are now available in the Play Store as stand alone packages so you can still get them if you want them and they get installed as user apps instead of system apps, not that it makes a tremendous difference, but for the most part they don't need to be in /system.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
lwkkazz said:
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
Click to expand...
Click to collapse
Android reserves around 4GB of the total space on the device. Yes, it is quite normal.
Glad I picked up the 16GB model.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
l.m.prowse said:
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hmm....it's early for focal still, probably just an oddity.
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
markd0wn said:
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
Click to expand...
Click to collapse
I heard about it, but I always use Apex Launcher so it doesn't happen to me. I'm not sure they want you to put things for 10.2 on JIRA or not (probably not) but its a fairly serious thing, so you could try logging it, worst case they ignore it.
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
Thanks to DJLamontagneIII for this:
Titanium backup Users
1. In tb go to menu>preferences>backup folder location
2. Navigate to storage/emulated/legacy
3. Select your Backup folder and Select "Use the current folder"
4. Then it will ask you to move backup to that folder.... Select that
5. Restart app and restore.
jpreichart said:
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Beat me to it
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
markd0wn said:
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
Click to expand...
Click to collapse
They're doing a fairly significant reworking of the entire settings apk and all of the CyanogenMod settings, it's possible something got added/removed that broke this temporarily. I would expect that certain settings menus, etc... may be broken over the next little while before the official nightlies begin.
I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07
Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)
Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!
Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages
I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.
So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.
Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.
Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.
More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.
Good version,thanks. But it often wifi reconnect , can it fix?
wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time
Android system cost battery drain more than screen, is it normal?
wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks
monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.
wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!
Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436
syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.
TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs
I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.
ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from
syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?
saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs
Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.
You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".
I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk
Yeah, can't get it to stick on a stock 932.
You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.