So, I'm obviously not remotely an expert when it comes to Android mods, but I'm finally fed up with being stuck on Android 4.1 - since it doesn't appear we'll ever get any upgraded qwerty phones ever again, I figured I'd try diy'ing it.
I have successfully flashed TWRP, rooted the phone, and installed what I believe(?) to have been the most recent version of CM11 (I figured it'd be cleanest to keep the phone closer to what it was designed for - I've seen tons of apps require 4.4 at minimum, not too many that require 5+): cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip. Was the most recent version I could find, anyway?
I booted it up and for the most part, everything seemed to be working. Everything except Chrome, which crashes reliably and immediately. I tried clearing all the caches (the app's cache + data, and the phone's, from recovery), uninstalling and reinstalling Chrome, I tried the beta version (crashes), I tried a fork, Brave (crashes). Other browsers are working fine, but I like Chrome.
One weird thing I did notice: I was thinking it might be a gapps issue, but weirdly, the Play store, gmail, maps, everything else just installed and seem to work out of the box before I did anything with gapps? I did also try flashing the most recent base 4.4.4 gapps zip from what I could tell (gapps-444-base-20170209-1-signed.zip), but I'm not sure how to tell if it actually did anything? It said it flashed successfully, but (other than having to wait for all my apps to recalculate because I cleared all the caches), nothing noticeably seemed to change on the front-end as a result, and yes, Chrome still crashes. Should I be using a different gapps install than that for the Photon Q? Or anything else I should check/try? Thanks!
Yay! Answered my own question, with sufficient digging!
Answer seems to be basically: the newest version of Chrome (v55) exposed some sort of weird incompatibility with CM, so the easy fix is just not to use it, at least for now. I sideloaded Chrome v54, and it stopped crashing, yay! Source: https://forum.xda-developers.com/showpost.php?p=70762641&postcount=198
Just FYI, the latest version available for this device is CM13.
They are working on Lineage.
Edit - seems you found the CM13 thread already
Yep - I'm glad to see people other than (and smarter than) myself recognize the Photon Q's unique place as being the final and, sadly, best qwerty slider available for our use, and that it therefore needs to be actively maintained even if Motorola won't... I just figured it'd be better to use an OS closer to the one the device was intended to be used with. Once I'm done testing CM11 out on my old half-working phone (re-purposed to a test phone) and push it to my new fully-functional one, I will probably at some point upgrade that first phone to the latest to try it out (probably once a Lineage build comes out, so I can be on a build that's actively being maintained). For right now, though, I figured I'd stick with CM11. Any case, looks like CM13 exposed the same Chrome issue, anyway.
Related
I am currently running tnt lite 4.2.3. I updated to that directly from stock. The performance I'm getting is less than many people on here say they are getting (i'm getting a quad score of 1730). Everything is working (marketplace, maps, etc) and i'm relatively pleased, but it still seems quite slow. I should also mentiong angry birds won't install for some reason. I'm not sure if i did something wrong or skipped something (i never did anything with partitioning my memory). I was thinking about starting all over again, but i noticed there are several "starting points" for tnt. Can someone recommend which version I should revert to and direct me to the best way to do it please? Thanks in advance.
Hmm weird, Ive been getting nothing less than 2050 on all scores for every rom Ive used and I think the going rate for the tntlite is 2400! You might want to try to reflash it maybe
nmac99,
Since your tablet is working fine (though I agree it sound a little slow), you have lots of options. TNT Lite 4.2.3 is the older 1.0.1-1.1 generation of software, so you can
change simply by re-flashing using stock recovery.
I have a suggestion. I just completely wiped and rebuilt my 3991 version machine and
I install roebeet's 4.3.0 and then 4.3.1. It worked smoothly and really looks nice since
it has some of the latest stuff in it.
Since you are at 4.2.3, all you would have to do is download 4.3.0 and 4.3.1 and
install them. Load recover folder and update.zip into /sdcard. Shut down. Reboot
into recovery by holding power and volume + down until you get the black recovery
message.
Go to roebeet's thread in Developers and read up and see what you think.
If you decide you're not interest in that, then I would recommend recoverying the same way to Version 3588. It is solid and you could go any direction from there. And
again, all you would have to do is flash it with stock recovery process. You might
need to reset the factory data (Settings menu, Security Option on G-Tablet). If so,
you would have to put your date, time, other settings, passwords, etc. back in.
Hope this helps!
Rev
P. S. -- I think 2100-2200 is realistic for Quadrant. Less you're behind and more you're ahead!
EDIT: Just found the Tnt Lite 4.3.2 is out. Happy modding!
I'm actually adding a new recommended pre-req to my TNT Lite and gADAM posts, today -- basically, I'm going to request that users try to start with 3588 stock as a baseline.
The reason why is because I think users who are modding back and forth all the time have started moving too far off the beaten track. When I test a new mod, I almost always do it with either 2967 (from my nvflash) or 3588 stock. And a do a data wipe. That way, it minimizes all the weird issues that might crop up if I was many steps away from stock.
Thanks for the quick replies. This board is awesome.
ive installed tnt 4.3 with no problems except i cant get the market to work. I tried the same fix i did on 4.2.3 and it doesn't work. i can initially get it open, but then it force closes after about 5 seconds and i get the process com.android.vending error. is there something else i should try with 4.3? or is it best just to reflash? by the way, i really like the look of 4.3 compared to 4.2.3. i haven't been able to run the quad score either, but it feels faster.
nmac99 said:
ive installed tnt 4.3 with no problems except i cant get the market to work. I tried the same fix i did on 4.2.3 and it doesn't work. i can initially get it open, but then it force closes after about 5 seconds and i get the process com.android.vending error. is there something else i should try with 4.3? or is it best just to reflash? by the way, i really like the look of 4.3 compared to 4.2.3. i haven't been able to run the quad score either, but it feels faster.
Click to expand...
Click to collapse
It is a tad faster, as the system.img is based off their 3991 UAT - allegedly their next released stock firmware will look and feel very similiar.
I have not had an issue with the Market and 4.3.x, but again I always wipe my data when I test my mods.
Suggestion: if you didn't wipe data and want to avoid doing that, make sure that the Market app is REMOVED from your downloaded applications. It's possible that the app there is the same (or older) than the one in 4.3.2. Just taking a complete guess, here.
It worked with the data wipe. thanks for all your help.
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
toejam316 said:
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
Click to expand...
Click to collapse
Might be an issue with OpenSensation (as you're using nightlies). Back up what you have, format everything but SD card, and I'd recommend trying a completely different non-nightly ROM, try AOKP m6. This way you can see if the SMS issue is related to OpenSensation or not. backup m6 THEN try the newest OpenSensation nightly to see if the issue is fixed. This way you'll likely be left with at least one ROM you can restore with working SMS functionality.
I might yet have to do that, although I would prefer to stay as close to vanilla as possible, that's why OpenSensation interested me - I think I'll try regressing to the CM9 RC2 on the official Cyanogen mod website first, then try other projects after that if that doesn't work. Does seem strange that no one else is complaining of this issues though, and I really can't see myself being the only one running the latest versions.
Oh yeah, the newest nightly and Tamcore kernel didn't work - the only thing that's changed is now I know I can't regress directly to my ARHD backup, yay!
This one's a bit of a thinker.
Well, I did a full wipe, installed the latest HyperSensation CM9 build and reinstalled the TamCore Kernel. Everything seems to be working now.
Thanks for the input, thread can be closed.
Hi
I can't post in real thread so it is here , I'm on big part from beginning (Everest XOOM) and at first everything works great but in last two weeks problem start both on Chrome and Chrome Beta.
I try dalvik wipe , cash wipe, try to use ART , try to reinstall both applications , to remove flash player and finally switch from OMNI to CM11 but there is still same problem
so if anybody have any suggestion it would be great
Many thanks in advance
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
gtrhr said:
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
Click to expand...
Click to collapse
I also had serious problems with Chrome constantly freezing and crashing on my Xoom wifi upgraded to Kitkat Omnirom 4.4.2. I've installed version 33 as advised in another thread (a developer one that doesn't allow me to post there), using an apk file linked on that thread.
I haven't tested this yet but, assuming it works ok, how do I stop it from updating automatically? Any idea on how we'll know when an update appears that is safe to install, and will work?
Chrome Beta
I had the same problem too. Chrome on Omni and TeamEOS kept freezing. Only to kill the running app was helpful till it freezes again.
Then I've installed Chrome Beta (v37.0.2062.55) and since then everything seems ok. Until now no more freezes.
Maybe anybody else to prove that?
Simple fact of the matter is, KK is just slow on the Xoom. I'm amazed that we even saw 4.4, seeing as how mine (wingray) is over 4 years old.
I ran CM11 there for a while, but the constant freezing of Chrome and the slow clunkiness of the interface was enough to drive me back to CM10.1
I decided to try out simplifying my phone and reduce issues that I've come across when using various custom ROMs, modified stock ROMs, etc... and used the Restore-To-Stock tool found in these forums. I then updated the phone via Settings, About, System Updates... then once that was done (Several times...) I was fully updated and ready to go. I flashed the latest TWRP & then installed the latest SuperSU for MM via TWRP... went into the file system and removed the APPs I did not want or need on my phone, wiped the caches and rebooted... I did this a few days ago and am insanely impressed by it. I forgot what stable and issue-free felt like... There's no fancy custom edits, no oddball quirks randomly from whatever was modified from various ROMs and after I installed xPosed, a few basic modules, setup Nova Launcher and all my APPs (Did a full fresh no restore of anything run through of it all)... I am the happiest I've ever been with my Moto X Pure (XT1575).
Once N pops in, I'll go through the whole process again, of course... but I think I might start sticking out simplified setups from here on out. I wanted to get the next Google "Nexus" phones released this year, but after seeing the Pixels and the prices... no thank you, I'm staying with my Pure for a while. I'm VERY happy with it... Dual front facing speakers are pretty much a necessity now for me. Internal Storage and Removable Batteries (prior to my Pure) are no longer my requirement. I've adjusted to pretty much using Google Drive and Google Play Music for all of my Files & Music with T-Mobile's no-data-cost of Google Play Music Streaming, I download my favorites (All I ever need would fit on a 32GB phone easily)... and Google Photos auto-backup has prevented me needing tons of storage options anymore... Battery you say though? No... I've YET to have a phone I wasn't able to charge on-the-go or even have a battery go bad.
Rambling here, this post was probably more for me than anyone who might read it, lol... I wanted the Moto Z so bad... but if I can't get an unlocked one that has the shatterproof display to use on T-Mobile... I don't see myself getting one at all. I want my next phone to have a fancy AMOLED hopefully shatterproof display with dual-front facing or at least a mod for sound / speakers like the Z and perhaps smaller top / bottom bezels. Not sure if I care about a fingerprint sensor yet or not. Anyway, have a great day everyone!!!
Have you compared debloated stock to tru pure x?
I've been thinking about doing something similar for the last few days. I've been running the latest TruPure since it came out several months ago. It might be the longest I've ever had an Android device without doing a clean flash of something, and things are degenerating.
I've always been a huge fan of TruPureXMM but have run into a few minor quirks here and then over time and definitely feel this is proving to be a much more stable experience. I removed (debloated) pretty much everything TruPureX did when it comes to APPs, but I believe TruPureX had a lot more going on than just that, which is what prompted me to go this route.
Since we're all sort of waiting for the official N, and we all know it won't be here amazingly fast... I've opted for this route to stay with the official run of things until N is stable and available through the official channel. I'll go through the full official update process and then TWRP and Root after... I'll be able to stay away from xPosed at first simply because the only things I'm using now are making MM more like N and I won't need to do that with N. I'm hoping once I can TWRP, Root and debloat by deleting the many APPs I don't like... things will be great!
CJ-Wylde said:
I've always been a huge fan of TruPureXMM but have run into a few minor quirks here and then over time and definitely feel this is proving to be a much more stable experience. I removed (debloated) pretty much everything TruPureX did when it comes to APPs, but I believe TruPureX had a lot more going on than just that, which is what prompted me to go this route.
Since we're all sort of waiting for the official N, and we all know it won't be here amazingly fast... I've opted for this route to stay with the official run of things until N is stable and available through the official channel. I'll go through the full official update process and then TWRP and Root after... I'll be able to stay away from xPosed at first simply because the only things I'm using now are making MM more like N and I won't need to do that with N. I'm hoping once I can TWRP, Root and debloat by deleting the many APPs I don't like... things will be great!
Click to expand...
Click to collapse
You've made me interested in trying this out as well. Is titanium backup the best way to remove system apps or is there a better alternative?
HaggisIV said:
You've made me interested in trying this out as well. Is titanium backup the best way to remove system apps or is there a better alternative?
Click to expand...
Click to collapse
What I've always done is go into TWRP and remove them myself. Going full fresh no restore means no real need for Titanium. Return-To-Stock first, then OTA your way up to current... THEN TWRP and SuperSU... then boot in, make sure everything is working and jot down on a piece of paper or Google Keep from your computer a list of the APPs you don't want.
Then power off, get into TWRP and mount /System, go into Advanced, File Manager and within /system/APPs and /system/PrivAPPs (Or something like that, memory just blanked) and find what was on your personal list... enter the folder for it, hit button bottom right, choose delete, done, go back and do the others... then wipe Cache / Dalvik and power off / boot up for the absolute freshest experience you can have with a stock ROM.
The trick is to NOT restore ANYTHING... install all your preferred Google APPs first, do the whole Google Phone install if you removed the stock Phone app, etc... (I remove it and the messenger, and a bunch of other stuff like the gallery, mail, etc... because I solely use Google services now).
I removed my case cover and have been carrying the phone around bare.
It's like I bought a whole new phone.
Have you guys tried a quality AOSP based ROM like Dirty Unicorn or BrokenOS?
Super stability. Nothing at all like running a CM ROM.
Testing cm14 now. Hashbang is doing a great job getting it daily worthy.
nobreak1970 said:
Testing cm14 now. Hashbang is doing a great job getting it daily worthy.
Click to expand...
Click to collapse
cant get it to recognize my sim
unitz0mbie said:
cant get it to recognize my sim
Click to expand...
Click to collapse
10/11 build will I bet. :highfive:
What apps/services did you remove? I'm running stock rooted myself and honestly I only see a couple of things I'd get rid of, nothing that would have any real impact on battery/storage though. This phone's stock ROM really is close to AOSP.
same too what apps did you remove tnx.. im not rooted .. tried uninstalling apps and guess what it got temp bootloop.. did hard reset using stock recovery and got fix again started tru welcome menu.... may i know guys what apps not to unistall tnx
Did a side by side comparison of apps in TruePure and stock. I counted 39 apps deleted from TruePure.
Android Live Wallpaper, Basic Daydreams
Bubbles, Calculator
Cloud Print, Com.Android.wallpaper.holospiral
Com.Motorola.audiomonitor.helper
Com.Motorola.bug2go
Com.Motorola.motgeofencesvc
Com.qualcomm.atfwd
Config Updater, CQATest
Demo mode, Device help
DiagMdlog Settings , Entitlement
Google Indic Keyboard , Japanese Input
Google Launcher Config , Korean Input
Pinyin Input , Play Movies
Play Music , Hangouts
Input Devices , Messaging
Moto Care , Moto Care int
Motorola Boot Services , Motorola Checkin
Motorola Notifications , Motorola One Time Init
Motorola Update Services
Native Drop Box Agent , Phase Beam
Rescue Add-on: Motorola
Sheets , Slides , Talk Back
I only deleted the extra Keyboards, Play Movies, Music, Hangouts, Sheets, Slides and Talk Back to be sure I had enough space for Xposed.
Are there any ROMs that work well/ respond to touch quickly?
I recently pulled out my old tf201 to try to start using it again. I was able to get the last version of HairyBean working.. But it is really really slow. Like I'll click a button and maybe 30 seconds later it will respond (or tell me the app isn't responding). I mostly use it for my kids to watch shows. Once the show starts it works great, but just navigating the menus and apps to get to the shows can be excruciating. Also, I know thisdevice has WiFi issues just due to the all metal construction, but I feel like the WiFi is even slower than what it used to be when I actually used this 5 years ago or so.
I flashed a couple of other ROMs and either had a lot of bugs, or couldn't get root, or something. Does anyone have any recommendation for a ROM that works well and is actually usable? Thanks!
Anyone??!! I recently put kashmellow (tduros android M). Gapps no longer works so I didn't install that. Many people say its fast w/no gapps. But mine is barely usable. So slow. What the heck happened to these devices? Thing used to be a beast! Believe it came with ICS
I use KatKiss timduru site and xda thread, it is Android 4.4.4 ROM and it is quite fast an somewhat usable. I also have old Google Play Services 10.5.42 that mostly do not crash so even Play store works. However many new apps either cannot be installed or crash because of missing NEON support, sometimes older apk versions work. Basically I keep it for lot of old stuff that still works but don't update anything (or keep Titanium backup of apk+data and often restore back to old version when newer one crashes or needs newer play services).