For those of you that want to try this and got the error about front facing camera try this link for fix. I am running CM7 nightly 204 and can confirm it works lovely.
Enjoy and leave feedback to help out those that are going to ask did this work on blah blah blah....lol
Edit:here is the info from the page.... THANKS FernandoMiguel
FernandoMiguel said:
all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
Click to expand...
Click to collapse
Doesn't work =/
I tried to push the file via root explorer and I did. I then rebooted and had no luck. It just shows the hangout post and no link or message about not having a camera. I also ran fix permissions in ROM Manager and rebooted and still nothing. I am running the latest CM7 Mod and running it on the Droid 1. Any help would be great!
Ive tried the method above, still same message about FFC.
Running Decks 1.3b
Works a treat, on HTC desire using mild wild 2.6
Brilliant
Works like a charm.
However, when running fix_permissions, my MIUI install is running for 1 min and 20 seconds, updating a lots of permissions, usually adding rwx-rights to group or something. I guess that's alright.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
Any progress?
H0wdy said:
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
Click to expand...
Click to collapse
My wife's EVO 4g is also at CM7.2 rc1. Any progress on getting this to work? Is it possible to move back to an earlier version of cm7 to get it going? As it stands now, I have to take it all the way back to cm6 for it to work.
Got it working with this:
http://forum.xda-developers.com/showthread.php?p=22668916
After tweaking some of the settings in camera, like force enable video calling.
Thanks!
H0wdy said:
Got it working with this:
http://forum.xda-developers.com/showthread.php?p=22668916
After tweaking some of the settings in camera, like force enable video calling.
Click to expand...
Click to collapse
Thanks, H0wdy! That worked for me. I had to also check on "Avoid setFPS" to get Skype video to work.
Related
Anyone havng issues with the Kindle App. I am running the latest Eris Lightining Mod. Apps2SD active. The ap loads but when I sync to download my books it sayd - "The books could not be opened. Please remove the book from your device and download again."
Wel I have done that a million times...no luck. Anyone else have this issue?
carpsworld said:
Anyone havng issues with the Kindle App. I am running the latest Eris Lightining Mod. Apps2SD active. The ap loads but when I sync to download my books it sayd - "The books could not be opened. Please remove the book from your device and download again."
Wel I have done that a million times...no luck. Anyone else have this issue?
Click to expand...
Click to collapse
Could it be JIT related ? I know JIT is enabled by default on CELB ..... maybe disable JIT and see if it works anybetter ? ...not sure as I haven't used Kindle yet...though I am planning on it
How do I disable JIT?
carpsworld said:
How do I disable JIT?
Click to expand...
Click to collapse
Assuming you have the SDK installed type the following commands from you PC's command prompt:
adb remount
adb shell "busybox sed -i 's/dalvik.vm.execution-mode=int:jit/dalvik.vm.execution-mode=int:fast/' /system/build.prop"
adb reboot recovery
Then from the recovery menu:
Wipe -> Dalvik-cache
Reboot the phone
Disabled JIT and no luck....can I get instructions for enabling it again. I am at a loss why it wont work...
carpsworld said:
Disabled JIT and no luck....can I get instructions for enabling it again. I am at a loss why it wont work...
Click to expand...
Click to collapse
adb remount
adb shell "busybox sed -i 's/dalvik.vm.execution-mode=int:fast/dalvik.vm.execution-mode=int:jit/' /system/build.prop"
adb reboot recovery
Then from the recovery menu:
Wipe -> Dalvik-cache
Reboot the phone
ETFix: JIT not JI
This was brought up in the 2.7 Cyanogen Eris Lightning Bolt thread:
paulbonner said:
I had previously noticed garbled text problems with RoboDefense with this ROM, and today saw the same problem in the Kindle App. According to this thread hxxp://code.google.com/p/cyanogenmod/issues/detail?id=1663#c35 , the garbled text issue is specific to Cyanogen 5.08. The thread contains links to three patches for the issue -- one for the Dream/Sapphire, one of the Nexus, and one for the Droid. Has anyone tested any of these with the Eris and found one that works?
Click to expand...
Click to collapse
If you go to that thread they mention the patches they have done but when asked about the Hero/Eris they replied that those phones are not supported by Cyanogen Mod so they didn't bother with it. It's up to a developer to study the patch and get it into an Eris rom I guess.
EDIT: I'm an idiot and can't read I guess - I can download books fine, the only problem I've been having is garbled text.
I get garbled text as well on free books. My purchased books will not download.
Since there are patches out, I suspect it will be fixed on the next release of cyanogen, do he fix should make its way to eris eventually.
Sent from my Eris using XDA App
my experience with kindle was that i was using the stock web browser and it said that my device wasn't supported/recognized or something. couldn't buy even the free ones.
this was fixed by using dolphin browser.
Worked fine last night.
Still works on incredible.
It says I need new version
but it's not in market?
I have HTC Vision in build.prop
anyone know how to fix it?
Sent from my ADR6300 using XDA Premium App
I also used the htc vision fix.
I had the exact same problem last night. I opened netflix & couldn't use it, just got a message saying there was an update for the netflix app and I could not use the app till I downloaded the update. Clicking on the Ok button took me immediately to the update on the market, the screen where you can click to download the app.
Then the updated version of the app wouldn't work. Just an error message saying something like there is a problem with my netflix account, or my device has been deactivated at netflix.com.
I got it working again but had to try lots of things. I deleted the updated app, and tried restoring the older version from titanium backup, but got the same message about needing to install the update,& updated app gave same error message. Cruising around netflix.com website wasn't useful, my device (nc) hadn't been ' deactivated' as far as I could tell.
Side loading the netflix app didn't work. After I reloaded the old app ( titanium) a few times, & updated & rebooted a few times, i started getting stuff to play sound, but no picture. Then I discovered it will work perfectly after a reboot, but only for the very first thing you pick! After that it's just sound again, & i have to reboot again to watch something else!
Anybody else having a netflix issue?
[Solved] Netflix weirdness
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Interesting.....
I had the modified .apk which didn't need a prop.build change.
Of course, it died last night like the above threads state.
Wouldn't let me update it either as everytime I tried to install, it would error out...
But, I went an uninstalled the program (first deleteing cache) then found the program in the market and it installed with no problem....
It runs fine... no chipmunks.... nada....
Lucky I guess.... Running CM7 off the emmc on an overclock of 1200.
Lego
Legobricke said:
Interesting.....
I had the modified .apk which didn't need a prop.build change.
Of course, it died last night like the above threads state.
Wouldn't let me update it either as everytime I tried to install, it would error out...
But, I went an uninstalled the program (first deleteing cache) then found the program in the market and it installed with no problem....
It runs fine... no chipmunks.... nada....
Lucky I guess.... Running CM7 off the emmc on an overclock of 1200.
Lego
Click to expand...
Click to collapse
Woops, hit the thanks by accident I was trying to quote your post. So you didn't modify your build.prop and the updated client works without chipmunk voices? I'm running .32 CM7 after a restore to stock (was having issue with a later nightly) and when I downloaded the updated Netflix app it still gave me chipmunk voices until I edited build.prop again.
Are you running 7.0.x stable or one of the newer (.32) nightlies?
I am using CM7.0.3 - encore stable.
I also am using the ext4-CM7-dalingrin-OC-emmc-042411 overclock set to 1200.
These are running from the internal. Not an SD card.
I have had zero issues with netflix.
The stable (and the .29 kernel nightlies) have no problems running Netflix now that device check has been disabled.
It's only the .32 installs (later nightlies and beta1) that have the chipmunk voice regardless of what Netflix client is used (and thus needs the build.prop mod)
Just to add to the conversation. The Netflix Market Update worked perfectly fine for me.
Nook 1.2.1, rooted.
fuzzynco said:
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Click to expand...
Click to collapse
Also running SD card Nookie Froyo 0.6.8, but I'm still getting the chipmunk effect with this APK :/
Worked for me on 2 versions of NF.
I did have to do the build.prop fix though.
I used HTC Vision.
This worked perfectly... Thanks so much!!!
fuzzynco said:
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Click to expand...
Click to collapse
Thanks that worked for me.
I just updated to CM7 Nightly #93 via ROM Manager yesterday.
The only thing I had to do was update build.prop with the HTC Vision information to get it working again.
Rocking...
Edit: Just updated to #94 via ROM Manager, updated build.prop again, rebooted, and still working.
NOTE: I updated to most current version of CWM using ROM manager prior to CM7 update as well...
running rooted 1.2 with dalingrin's OC kernel --> was able to install and run netflix from market but had the chipmunk / fast forward feature... changed my build.prop with the HTC/Vision mod and all works great.
FYI, I was able to copy the latest apk from my Nexus One to the Nook Color, and Netflix is working again.
Can't get Netflix to work after update
I am at a total loss what to do. I updated my netflix app like it asked me to but now it lets me put my login info in (all red screen) and then I hang where it is a white screen with Netflix in a red bar at the top of my nook color. It never goes any farther than that and it used to work for me great before the update and I am doing the Vision HTC build prop thing and I have tried clearing data. Any thoughts. Thanks
bhaycraft said:
I am at a total loss what to do. I updated my netflix app like it asked me to but now it lets me put my login info in (all red screen) and then I hang where it is a white screen with Netflix in a red bar at the top of my nook color. It never goes any farther than that and it used to work for me great before the update and I am doing the Vision HTC build prop thing and I have tried clearing data. Any thoughts. Thanks
Click to expand...
Click to collapse
Exact same thing just happened to me. But I actually got it to work after the update. Then today it suddenly started giving me the white screen with Netflix at the top. Arggg.
Ditto for me on my ManualRooted Nook; however, Netflix still works from my SD-based CM7. What are you guys running on?
What I am running
I am running on Manual nootered latest 4.5.25 and I am running the OC kernel from Dalingrin.
I have exactly the same problem. Running the same combo.
So far I've uninstalled, and re-installed, cleared dalvik cache, but nothing has made a difference.
Working one day, then broken.
I know this was posted elsewhere but thought we needed a dedicated thread...
Patch is from this Asus Transformer thread:
http://forum.xda-developers.com/showthread.php?t=1178773
I'll confirm it seemed to work for me. I bought my Iconia yesterday and updated it to the lastest OS version. Then rooted. I downloaded the new Netflix 1.3 app last night, but got the same error everyone else is reporting. This morning, I downloaded the zip file mentioned above, unzipped the file on my PC, copied just the .so file to a microSD card, put the card in my Iconia, then transferred the file to /System/lib using Root Explorer (backed up a copy of the original file, of course). Then I loaded Netflix and video seemed to work just fine. I wasn't able to test it much since i am at work..the video quality looked good after a few seconds. Didn't verify that the sound and video were in sync. Will do that when I get home tonight.
I wonder if the Hulu hack for the Transformer would work, too? I think its just an older version of the Flash apk (or something like that).
i flashed it as well, video and audio is synced on mine enjoying it right now.
1.3 APK here:
http://www.multiupload.com/3A8C4GWL8R
jm77 said:
1.3 APK here:
http://www.multiupload.com/3A8C4GWL8R
Click to expand...
Click to collapse
THANK YOU!!
Installed the patch with the old app from the market (before it was taken down) and I had no luck. I didn't even get the 12001 error anymore, this time I just straight up got "Device not compatible"
Installed 1.3 app and boom, good to go. Netflix on Iconia Comfirmed :]
*Also* Like other's have said, yeah it starts off in a crappy quality but about a 30 secs to a min into your movie it scales up
I can also confirm it worked on mine. Virtuous Picasso 1.10. You have to install the app from the download link provided. I just flashed the zip for the patch via CW and thats it. Audio sync is perfect.
confirmed working, sync'd audio!
Excellent work!
Confirmed on stock ROM yet?
Looked through the post and didn't see it.
Virtuous Xoom users - Netflix will work, but your Camera apps will FC.
-- This is probably due to libnvomx.so being pulled from HC3.1 Xoom. We'll need to track down a copy of libnvomx.so from HC3.2 Xoom to confirm.
entropyiv said:
Confirmed on stock ROM yet?
Looked through the post and didn't see it.
Click to expand...
Click to collapse
Confirmed... just make sure to clear data and cache from the app after you flash the patch
whoweee now my work will hate me lMore
Thank you guys awesome
acorsino said:
Confirmed... just make sure to clear data and cache from the app after you flash the patch
Click to expand...
Click to collapse
+1 to that.
Also confirm works on stock 3.1. Only thing I had to do was reboot the tab. Audio synced fine on the first movie I tried.
Do you have to be rooted for this to work?
Do you have to be rooted for this to work?
I posted this elsewhere too... After being successful with this patch and loving the Netflix... I cannot use Music... anyone else having this problem?
Camera crash.
Im running the latest version of picasso and after the patch netflix works great but if i do anything with the camera it force closes. Any thoughts?
cubanorafter said:
Also confirm works on stock 3.1. Only thing I had to do was reboot the tab. Audio synced fine on the first movie I tried.
Click to expand...
Click to collapse
Same here. I'm not sure how everyone else installed the patched file, but since I have not installed Clockwork Mod, I did the following:
Extracted the ZIP and dumped the file on my device at /sdcard/
Logged in a local console using Connectbot (in the market)
Ran "su" (requires root)
Remounted the /system partition as RW: mount -o rw,remount /dev/block/mmcblk0p3 /system
Renamed the old library: mv /system/lib/libnvomx.so /system/lib/libnvomx.so.bak
Copied the new file from my SDCARD: cp /sdcard/libnvomx.so /system/lib/
Reboot
i have it working without a patch, i just installed it by sending the apk from my thunderbolt, and its the netflix right out of the market. no camera fc's here i think the new update made all tablets work
EDIT: im running virtuous xoom 1.1.2 just to clarify
krickatthedisco said:
i have it working without a patch, i just installed it by sending the apk from my thunderbolt, and its the netflix right out of the market. no camera fc's here i think the new update made all tablets work
EDIT: im running virtuous xoom 1.1.2 just to clarify
Click to expand...
Click to collapse
So you aren't running a factory ROM. And no, the Netflix update didn't make it work with all tablets out of the box.
From the press release I gather that Lenovo worked some deal with Netflix to ensure theirs were the only tablets it worked with. It wouldn't surprise me if Netflix was specifically looking for certain file versions to ensure it works, and intentionally breaking it if not. From the Lenovo press release:
As the first Android-Honeycomb tablets certified for Netflix, Lenovo tablets can help turn every night into
"movie night."
Click to expand...
Click to collapse
And I have no FC's from my camera after the patch install, so unsure what hungsohlo's issue is.
Confirmed working on Acer_A500_4.010.01_COM_GEN2.
Thanks!!!!!
*NEW INSTRUCTIONS*
Today I figured out how to get Amazon Video On Demand app on my phone and watch videos
I did this with a rooted phone, I am not sure if you phone needs to be rooted to accomplish this task. I have attached the required files to accomplish this task. These steps are assuming you have a rooted phone.
REQUIREMENTS:
Download attached APKs
Wireless connectivity
VooDoo OTA for rooted phones (https://market.android.com/details?id=org.projectvoodoo.otarootkeeper)
INSTRUCTIONS:
1. Copy downloaded APKs to your phone
2. Install each APK and make sure to click DONE after each installs
3. Enable phones Wireless and connect via WiFi
4. Go to your phone SETTINGS>ACCOUNT AND SYNC
5. Press ADD ACCOUNT
6. Press AMAZON and enter your Amazon Prime credentials
7. Start the VooDoo OTA app
8. Press TEMP.UN-ROOT and allow the program to temporarily unroot your phone
9. Reboot your phone
10. When the phone comes up, still be attached via wireless and try your app
I hope this works for everyone who tries, please report your findings
Currently this app only works on wireless it will not work with your cell signal. I am looking to see if I can figure out how to enable the app to use the cell signal, I'm not a developer but I do have an idea to try!
ill try this on my Amaze 4G when i get home
I did all of these on my CM7 mod and "Watch Now" is still grayed out for me.
MoToKrusheR said:
I did all of these on my CM7 mod and "Watch Now" is still grayed out for me.
Click to expand...
Click to collapse
The only think I can say is that make sure the device is un-rooted and reboot after using the VooDoo OTA
You're just about there!
do you guys think this would work with the bionic?
elephant007 said:
The only think I can say is that make sure the device is un-rooted and reboot after using the VooDoo OTA
You're just about there!
Click to expand...
Click to collapse
I've done the reset 3 times, still a no go. Going to keep looking into it though.
MoToKrusheR said:
I've done the reset 3 times, still a no go. Going to keep looking into it though.
Click to expand...
Click to collapse
Are you doing this on a phone or on your Fire?
I wonder if you can remove root from some alternative method and see if you can run VOD, perhaps remove BurritoRoot if that's what you have installed.
There is something about CM7 that amazon does not like. I have never gotten it to work on CM7, even after temp unrooting. But if I did the same thing on a none cm7 rom, it worked fine. Go figure.
elephant007 said:
Are you doing this on a phone or on your Fire?
I wonder if you can remove root from some alternative method and see if you can run VOD, perhaps remove BurritoRoot if that's what you have installed.
Click to expand...
Click to collapse
It's on a fire. Before I flashed CM7 over, I was running just a rooted fire, and voodo ran just fine allowing amazon video to work when needed. Would be a shame if I couldn't get it to run on CM7.. not a huge loss, just would like to see if it could work on this variant..
That's too bad that it doesn't work on CM7
Maybe I should try it and see what I can find out
will try and post quick feed back
for those of you having problems running this one CW7, according to this link here http://forum.xda-developers.com/showthread.php?t=1390773 I'm guessing it's the MAC Address issue
Just a guess
elephant007 said:
for those of you having problems running this one CW7, according to this link here http://forum.xda-developers.com/showthread.php?t=1390773 I'm guessing it's the MAC Address issue
Just a guess
Click to expand...
Click to collapse
Wonder if an update.zip could be made for the CM7 variant in this thread?
MoToKrusheR said:
Wonder if an update.zip could be made for the CM7 variant in this thread?
Click to expand...
Click to collapse
EDIT - I flashed the updated/MAC address fix - No wipe ROM, but still a no go... Might have to do a full wipe/install?
This is the ROM: http://www.mediafire.com/?hmdc0lmgvnlbg97
Located in this thread - http://forum.xda-developers.com/showthread.php?t=1390773&highlight=mac
"If you're upgrading from an EXISTING CM7 install then use this ROM instead. This one will NOT wipe the cache and data partitions which should mean that you can upgrade from one version of CM7 to another without losing any of your existing date (or that's at least the idea)"
I tried this on my CM7 Kindle Didn't Work
I copied the apk's and ran the installs. It won't let me login to Amazon even. I just grabbed the apk's from the Kindle Fire .bin file though. I'll try the ones you have for download in your post and see if they work differently.
Hmm, MAC wasn't the problem
I'm on ICS and when I try to add an Amazon account I get a failure. I've checked my MAC and it's the same as under stock, but what does concern me is my serial number is all 0's.
Has anyone got this to work under ICS? Is everyone's serial number all 0's? Any other hints on how to get VOD working?
its working fine on my amaze 4g!
thedarksavant said:
I'm on ICS and when I try to add an Amazon account I get a failure. I've checked my MAC and it's the same as under stock, but what does concern me is my serial number is all 0's.
Has anyone got this to work under ICS? Is everyone's serial number all 0's? Any other hints on how to get VOD working?
Click to expand...
Click to collapse
Did you try logging into Amazon via WiFi?
"Parse error. There is a problem parsing the package" when install MyAccount-unsigned.apk. Any ideas?
Emerald214 said:
"Parse error. There is a problem parsing the package" when install MyAccount-unsigned.apk. Any ideas?
Click to expand...
Click to collapse
Redownload and try again, sounds like maybe it didn't download or get copied to your phone correctly
It looks like Hashbang is working on bringing Nougat to the OtterX
https://www.androidfilehost.com/?w=files&flid=110844 :good:
Yep, it's booting and pretty much everything is functional now.
Hi
I tried the cm-14.0-20161003-UNOFFICIAL-otterx after a full wipe, and am getting constant com.android.phone has stopped messages.
I tried clearing
rm -fr /data/data/com.android.providers.telephony/
rm -fr /data/data/com.android.phone/
which seems to have worked in other cases , but not here.
trying the cm-14.0-20160920-UNOFFICIAL-otterx now
Any advice?
-----------
edit: loaded the 0920 and pico gapps, no issues at all with the com.android.phone, seems very good. Thanks!
Thanks for your providing these
Hashbang173 said:
Yep, it's booting and pretty much everything is functional now.
Click to expand...
Click to collapse
Bravo! Late to see but you made OtterX immortal. Too bad mine doesn't work anymore
@a.cid we need a blog post.
It's mainly the work of hashcode. I mainly fixed a couple of things and picked some commits to add compatibility with otterx (I've pushed these commits to CM gerrit and they were merged a while ago, so no more commits need to be picked when building otterx).
mikeataol said:
Hi
I tried the cm-14.0-20161003-UNOFFICIAL-otterx after a full wipe, and am getting constant com.android.phone has stopped messages.
-----------
edit: loaded the 0920 and pico gapps, no issues at all with the com.android.phone, seems very good. Thanks!
Thanks for your providing these
Click to expand...
Click to collapse
I have cm-14.0-20161003-UNOFFICIAL-otterx.zip installed with pico gapps but I'm getting constant com.android.phone has stopped messages.
I will try 0920 and report back.
OK no stopped messages on 0920 but this ROM has lots of lag.
Any way to speed it up?
luisenriquereyes said:
I have cm-14.0-20161003-UNOFFICIAL-otterx.zip installed with pico gapps but I'm getting constant com.android.phone has stopped messages.
I will try 0920 and report back.
OK no stopped messages on 0920 but this ROM has lots of lag.
Any way to speed it up?
Click to expand...
Click to collapse
To possibly fix the com.android.phone fc messages, try to freeze or uninstall the phone package as this device isn't a phone so it likely won't make a difference (although I could be mistaken). To speed it up, download kernel adiutor and then put low memory killer on "Very Aggressive". Next enable developer options in settings by tapping on the build number a bunch (if you are able to flash a ROM I assume you know the process). Go to developer options and turn animations down to 0 for everything. Next, try to stop any apps running in the background on boot etc...
rjmxtech said:
Uninstall or freeze the phone package?
Click to expand...
Click to collapse
re: com.android.phone....
I'd love to disable it but there doesn't appear to be a discrete app called com.android.phone in /app or /priv-app.
I recall in the Éclair era there was, but I haven't located it in this 14.1 environment....
mikeataol said:
re: com.android.phone....
I'd love to disable it but there doesn't appear to be a discrete app called com.android.phone in /app or /priv-app.
I recall in the �clair era there was, but I haven't located it in this 14.1 environment....
Click to expand...
Click to collapse
My age must be showing lel. All jokes aside let me check and I will get back to you.
On that build, does it allow you to even boot up and use apps? I see a few packages that are part of system containing "phone" in Titanium Backup so it must be there somewhere.
rjmxtech said:
My age must be showing lel. All jokes aside let me check and I will get back to you.
On that build, does it allow you to even boot up? I see a few packages that are part of system containing "phone" in Titanium Backup so it must be there somewhere.
Click to expand...
Click to collapse
well, I Think there's a newer release anyway that doesn't have the issue.
https://www.androidfilehost.com/?w=files&flid=110844
I fired up my Kindle OtterX, and its using a later build (cm-14.1-20161105-UNOFFICIAL-otterx.zip) that I don't remember having any issues installing, but
I must have installed and put the Kindle to the side.
mikeataol said:
well, I Think there's a newer release anyway that doesn't have the issue.
https://www.androidfilehost.com/?w=files&flid=110844
I fired up my Kindle OtterX, and its using a later build (cm-14.1-20161105-UNOFFICIAL-otterx.zip) that I don't remember having any issues installing, but
I must have installed and put the Kindle to the side.
Click to expand...
Click to collapse
@mikeataol I found the package
To remove it delete "TeleService.apk" in /system/priv-app/TeleService/
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
mikeataol said:
well, I Think there's a newer release anyway that doesn't have the issue.
https://www.androidfilehost.com/?w=files&flid=110844
I fired up my Kindle OtterX, and its using a later build (cm-14.1-20161105-UNOFFICIAL-otterx.zip) that I don't remember having any issues installing, but
I must have installed and put the Kindle to the side.
Click to expand...
Click to collapse
Going to test the latest build in a bit, I am basing this knowledge off of a Marshmallow ROM on my nexus 6, but I think it should be somewhat similar anyway. I will see if the com.android.phone package is the same (or there at all) when I get the Kindle all fired up with the newer build.
mikeataol said:
well, I Think there's a newer release anyway that doesn't have the issue.
https://www.androidfilehost.com/?w=files&flid=110844
I fired up my Kindle OtterX, and its using a later build (cm-14.1-20161105-UNOFFICIAL-otterx.zip) that I don't remember having any issues installing, but
I must have installed and put the Kindle to the side.
Click to expand...
Click to collapse
So I could be going crazy, but after installing the latest build (1105) even without gapps, every time I try to select the language for cyanogenmod it says the settings app has force closed on me and I cannot get past that screen. Any ideas?
rjmxtech said:
So I could be going crazy, but after installing the latest build (1105) even without gapps, every time I try to select the language for cyanogenmod it says the settings app has force closed on me and I cannot get past that screen. Any ideas?
Click to expand...
Click to collapse
Oh, y...
in TWRP, mount /system
advanced / file manager
remove CyanogenSetupWizard from system/priv-app
mikeataol said:
Oh, y...
in TWRP, mount /system
advanced / file manager
remove CyanogenSetupWizard from system/priv-app
Click to expand...
Click to collapse
Lol thanks
So.... is everything functional?
WiFi, Bluetooth, Location, Good battery life, Google Play store?
Can I ask what recovery everyone is using to install these cm-14 roms
Sent from my Pixel using Tapatalk
So excited to see 7.1 on here. I had issues with installing as well (TWRP 3.0.0), so I changed the install script directories to match those in CM13 and it seemed to install fine.
The problem I'm running into is low memory. Once it boots I have about 3MB free, which leads to crashes to the desktop and soon a reboot. Is the RAM supposed to be compressed or is there still more optimization that needs to be done?
Keyboard issues
My keyboard won't show up on any of the builds. Any suggestions?
Hi there!
It's been a while since i was using this tablet but here we are. I want to use it without PlayStore, just for reading so i want it to ask if this CM14 Build is working well or recommend me a solid Otterx ROM.
I don't know if this is legit... https://www.androidfilehost.com/?fid=312968873555011561
But according to that link, there is a CM14.1 build from 11/05. is it safe to flash ? What Gapps ?
Thanks in advance.
GIL0802 said:
Hi there!
It's been a while since i was using this tablet but here we are. I want to use it without PlayStore, just for reading so i want it to ask if this CM14 Build is working well or recommend me a solid Otterx ROM.
I don't know if this is legit... https://www.androidfilehost.com/?fid=312968873555011561
But according to that link, there is a CM14.1 build from 11/05. is it safe to flash ? What Gapps ?
Thanks in advance.
Click to expand...
Click to collapse
yes the build is fine. If you don't need PlayStore than you don't need any gapps...
see the posts above about removing the CM setup program while in recovery before launching the rom on first boot.