Related
I upgraded my p1000 from cm10.2 to cm11 few weeks ago but the latest cm11 seems to be a bit laggish on my device and I'd like to go back to cm10.2, first of all... is it possible? If so, which is the proper way to do it?
mrfree2ita said:
I upgraded my p1000 from cm10.2 to cm11 few weeks ago but the latest cm11 seems to be a bit laggish on my device and I'd like to go back to cm10.2, first of all... is it possible? If so, which is the proper way to do it?
Click to expand...
Click to collapse
I'd recommend you try OmniROM Its what I'm using on my "P1" and although it has its share of problems. Wired Headsets don't seem to be working. Its no more worse then CM10 was, and on that note why CM10.2 which like CM10.1 was broken beyond use? The only decent CM10 was CM10 from 2013 - 02 - 03. Which AFAIK was the last fully working CM10 Mod for the P1000. As the 10.1 and .2 had the Camera Bugs.
In any case Omni is pretty well supported with near nightly, or at the lest every other night updates. As long as you don't get crazy with it with Live Wallpapers, like my Old man was trying to run on it. (He too has a P1000), its pretty damned responsive. But. Again you ONLY have 512MB of RAM on the P1000. In some rear cases even less then this!
In my Fathers case the same sh-- that was causing his CM11 to lag like heck, was the same crap that was making the fresh install of his CM10 (version as dated above!), lag just as bad. So you might want to first clean up such resource hungry Apps as you have first.
But, on the Latest OmniROM for the P1 (Int't GSM version), as of 06.08.14 (Which is still the the most current at the time I wrote this), just running the Google Now Launcher, and a few widgets. The Tablet doesn't feel any considerably slower then it did back in CM10, and the Google Now Launcher is a KEEPER! I can't imagine wanting to roll back to CM10.
P.s. Did you remember to reset your Firmware + wiping the Cache Partition, and Dalvik Cache? This could also partially explain your problems. If you, had not done this.
P.p.s. Download your ROM, and appropriate GAPPs Package, then reboot your P1000 by pressing both the Volume Up, and Power Button till you see the Galaxy Tab / Samsung Bootloader Screen. Then release the Power Button, while continuint to hold the Volume Up till you fully enter the Recovery Mode.
Once in the Recovery Mode do the following Factory Reset, then Wipe Cache Partition and the Dalvik Cache (Advanced Settings). Then install your CM10.x ROM from where you stored it i.e. the /Download Folder? And when thats though. Your GAPPs Package as well. After which you then boot into your new ROM. Which might take a few moments longer, on the first boot as the Database(s)? have to built from scratch again.
Mmmhh I think I'll follow your suggestion and I'll try OmniROM. Have you used the CWM recovery or the TWRP suggested on their official wiki to flash the omnirom?
mrfree2ita said:
Mmmhh I think I'll follow your suggestion and I'll try OmniROM. Have you used the CWM recovery or the TWRP suggested on their official wiki to flash the omnirom?
Click to expand...
Click to collapse
The way I described it before was for CWM. OmniROM uses TWRP. The ideas the same, in fact its a bit simpler on TWRP, in as far as it simplifies the wipe progress. Just One TIP download and install SuperSU, and run it. Once your rooted, go into your System Settings and click on the SuperSu Setting, (near the bottom), and it should ask you if you want to use a backup script, to keep root! You should run this if you want to... Need to keep Root for say AdAway. As OmniRom does NOT ship out with Root... WHY?! I can't say.
Other then that the only other annoying things I dislike about this ROM is that I have to keep uninstalling the Apollo Player. as well as reinstalling the Xposed Installer reset the "ro.config.low_ram" from true, to false, to re-enable transparencies, as well as other Lock Screen Widgets. After each update. Which again averages about every other day. I use something called ROM Toolbox Lite to do this, as trying to do this manually I always seem to gimp my install to a point of bootlooping.
But, other then these little niggles I actually like this ROM! for the most part.
And we should discourage question thread in development forum.
Sent from my GT-N7100 using XDA Free mobile app
Q&A for [ROMS][SGH-T679]Mass CM Thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
fajrero said:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
Click to expand...
Click to collapse
Roms come with a kernel the kernel linked is just special some have overclock under volt etc etc.
Explains the kernel options.
If you do flash them do it after rom.
Gapps you dont technicly have to but yes. (for a standard setup flash gapps)And there should be a gapps linked at the start of rom. If not there will be soon.
Can't import contacts from SIM
Thanks! That clears up a lot.
I installed CM, and it looks very cool and smooth. But when I tried to import contacts from my SIM card, it said "No contacts". I thought maybe it was because I hadn't installed GApps, so I downloaded the "small" GApps package linked from the CM wiki and installed it from CWM. Still no contacts on the SIM card. Next, I thought that maybe my contacts actually weren't on my SIM for some reason. So, I booted back into CWM recovery and restored my previous system. Then, from the phone app, I went to Import/Export > Manage SIM card contacts. Sure enough, all of my contacts were there.
It seems like CM isn't reading my SIM. Any idea what's causing this?
Edit: Never mind. I found out that newer versions of Android don't allow you to store contacts locally. Somehow, the contacts got silently added without me having to import them, though. That's odd, because I don't remember allowing Google to store them in the cloud, and the SIM card appears blank... Oh, well, I installed MyLocalAccount, so I'll see if I can store the contacts locally that way.
@cars1189 running 10/18 build with 10/19(PAgapps micro) and 9/9k^k UV vhm kernel and have had no issues! Thanks for the great work, this runs solid and smooth!
I recently installed 10.2 and am loving it so far. One thing I ran into though was that the cLock widget was showing lots of wakelocks, so I disabled it and battery life has been great. Haven't run into any other issues (other than the screen staying on when off and charging), so this one is a keeper for me.
Didn't see this problem with 10.1, so curious if this is a known issue or not with the cLock widget? Also, are there any other planned updates coming for 10.2?
Thanks.
@RobbyG2112 I noticed it too when I was on 10.2 how ever I only ran it for a week maybe b4 going to cm11 I will say not sure if cars will update 10.2 but if you haven't tried cm11 its super stable and gets updated monthly!!
Thanks for confirming canodroid15, I wasn't sure what the lock screen would show when I disabled the widget but it put the default digital clock and date in it's place so it works out ok. I had disabled the weather and alarm widgets also so wasn't sure why having only the clock widget would cause wakelocks.
I'll probably get around to installing CM11 next, I'm a little slow on upgrading. I had been using CM10 for a long time and finally got tired of seeing the green preview pictures every time I used the camera so decided to go to CM10.1/10.2 recently.
Sure man, about the wakelocks you can try to catch it in a log. Enjoy 10.2 bro!!
kernel for cm11 (SGH-T679)
I recently installed @cars1189's CM11 10-4-14 build for the SGH-T679, with kernel 3.4.104-cyanogenmod-gda4bf58. It took a few tries, but it finally succeeded.
However, there's a slight issue in that I can't access my SIM card contacts. When I try to import from the dialer, it says "no contacts." I've searched around these threads and on the internet, and it seems that it is an issue with the kernel. Would it be possible for someone to recommend or point me to a compatible kernel that would fix that issue for me? Thank you so much for your help!
@valmeras I really don't think it has anything to do with the stock cm kernel but if your on 10/4/14 you can flash 9/9k^k kernels safely on that build about sim contacts idk I use my Google account to sync my contacts hope this helps good luck!
Edit: look for the rom & kernel dates/links in OP.
@canodroid15 - thanks for the response and suggestion. I'll give that kernel a try in the next few days. Not sure this is the solution, but hopefully that works. I've also seen some reference to SIM Tool Kit (STK), but I wasn't able to figure out if it that was the issue.
I would definitely use Google for syncing the contacts once I get this fixed, but for now, that's not possible because my phone is not able to read the SIM properly. I've tried saving a contact to the SIM, but I get an error like "unable to write, SIM is full" but I know for sure that's not the case. Alternatively, I might try to revive my old dumb phone and try to retrieve the contacts that way, then hopefully export that in some way.
@valmeras no prob man, if you have contacts on your sim and u put the sim in the dumb phone and export to storage u could then send a vcard via Bluetooth to the exhibit go into contacts and import from storage then Google sync good luck let me kno if u get it
So I flashed the kernel, but that didn't fix my issue. I do have some more free RAM now though
My old phone doesn't support exporting multiple contacts/vcards via bluetooth, but fortunately, Motorola has a contact exporter utility that exported everything into a CSV file to my laptop via USB. I had to install the drivers for the old phone to be recognised first. I was skeptical it would work given it was a new all-in-one driver thingie and my Motorola was quite old, but somehow it did! The whole process took several hours, but my contacts are now synced!
Sensors/rotation problem
Thanks for posting these ROMs! I just upgraded from Peach Sunrise and I'm really impressed with how well CM11 runs on this phone.
I want to report a problem I had and my solution for the next guy's benefit. With the latest 12-9-14 CM11 ROM, my sensors and compass didn't work correctly. The biggest symptom was auto-rotation did not work at all. Downgrading to the 9-9-14 ROM fixed everything. I didn't try any other ROMs, so they might work too.
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
masteff said:
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Hey man! I hope you got it figured out! The only Gapps I use are PA Gapps! There are others but PA is the most complete package & has many options "IMO". You need to use a package that will fit your phone I use the micro package, or the nano. You need to use a package that matches your ROMs version, if your on 4.4.x then use 4.4.x Gapps. If on 4.3 use 4.3 Gapps. PA Gapps has a 4.3 package but its hard to find if you don't know where to look. 4.3 package can be found in the devs (Tkruzze) files on android file host, same place as the 4.4.x Gapps! Sorry if you didn't get answered b4 this I haven't been on this thread for weeks it seems! Hope this helps
So I've been trying out the CM11 OS2SD ROM (the last one in December), but I need to switch back as the bugs are just too much. I need my phone to work and stay charged, which is not happening on this ROM. And since it looks like CM12 is being worked on now that it's not likely the bugs in CM11 OS2SD will get fixed any time soon.
So first the problem. My USB socket on the phone is a little iffy, so I know that is where most of the problem is coming in. However, on the CM11 OS2SD ROM I'm using right now (the one dated 12/25) it frequently says it is plugged in, but is not charging. I've actually seen times where the battery monitor I'm using shows it has discharged the battery as much as 20% before I caught it, yet the status bar battery icon shows it as full and plugged in. On the older ROMs it didn't do this, so something isn't right with how the ROM handles the charging circuits in the phone. Plus, I've had frequent periods of "cpu hogging" (massive CPU load that doesn't seem to come from any one source and that doesn't seem to show up in OS Monitor) that can end up in a crash-reboot of the phone.
So as a result, I want to switch back to an older version of the CM11 ROM. I was using one of the November builds for quite a while, only having to put up with an occasional crash-reboot (the current ROM seems to do this at least every other day, the older one could go a whole week and maybe have it happen only once). What is the process to undo what was done to the phone for the OS2SD build to be loaded?
can't install
I have a problem after installing it via cwm and rebooting, the ensender shows me a screen where I order a factory reset but when I was I do not ensiende the phone
CM 12 Android is upgrading every boot
Ever since I flashed Cyanogenmod 12 every time I reboot it says "android is upgrading optimizing app 1 of 1" and it takes about 8 minutes. There are no odex files in data/app so that cant be the problem. Someone please help. The first time I flashed CM 12 I wiped data and factory reseted but since i seen this happen I flashed Cm 12 again but this time I formatted System, Data, Boot, and SDcard 0 but it still seems to happen. Also, recently my phone has been shutting off by itself every time I turn off the screen. And I know this isn't a hardware problem because the phone never turns off while music is playing with the screen off. It didn't start happening with CM 12. It was already happening with CM11 but it only started happening about a week ago. Im really thankful for cars1189 working on the rom and anyone else who worked on it. You guys are great. Hopefully you can help me out.
New member; just registered today. I'm really pleased to be here.
I've been learning how to install CyanogenMod CM-12.1 with help from many xda threads, but especially these two:
http://forum.xda-developers.com/nook-hd/development/unofficial-cm12-1-nook-hd-hd-2015-04-08-t3078260
http://forum.xda-developers.com/showpost.php?p=42406126
Many thanks leapinlar, e.mote, Hashcode, verygreen, and amaces.
I successfully installed amaces's CM-12.1 20150628 build on my three Nook HD+, and then successfully moved on to 20150706 build for each of them. Some details are mentioned below.
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I wondered if I was being punished for declining, but I did the same with the HD+ tablets without consequence.
I eventually shut down and restored to the stock HD OS, which appears to be working fine.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
I guess I'll have to learn how to use ADB to find and fix this problem, but if anyone has a suggestion to try before that I'm very anxious to hear it.
Thank you for reading my first post.
Some details:
My installation method, successful only for the HD+, is adapted from leapinlar's Installing CM11 for Dummies (Updated 7-13-14). I used the provided .rar file contents to build the external bootable microSD card with the CM-12.1 zips from amaces. But instead of flashing the provided CWM resident recovery zip I substituted a TWRP zip that I fabricated around amaces's TWRP 2.8.7 images. I was obsessively careful to use the model-specific images and zips in each case.
With build 20150628 on the HD+ I saw the Netflix green screen problem, and a serious screen instability when trying to manually enter a URL in a browser (keyboard and auto-suggest overlays). Disable HW overlays stopped this of course.
I then moved on to 20150706 build on each HD+. The only issues I now see are slight screen instability with overlays and restart about 15 seconds after power-down, which happens almost every time.
P. S. I really like the Nook HD and HD+ tablets. They are perfect for my use as annunciator panel displays for my horticultural controls (hobby), and so plentiful on eBay.
PeteInSequim said:
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
Click to expand...
Click to collapse
A Factory Reset solved the CWM problem and I was able to get a good install of CM-12.1 UNOFFICIAL build 20150706. I exercised a few things including the Android browser, and entered a URL manually from the overlay keyboard with no screen instability. Really looked good.
Sadly though, after shutdown it won't complete a restart. Just hangs with the cyanoboot universal bootloader banner in view.
Can anyone suggest what might be wrong?
FIRST EDIT: I should add that I am able to restart and boot into the resident TWRP recovery utility that I flashed during the installation. Just can't boot into CM-12.1.
SECOND EDIT: Rebooting from TWRP seems to have blazed the trail for a normal boot from power-up, which has worked 4 times out of 4 tries. Maybe its fixed now.
Still have the unexpected reboot after shutdown, though it doesn't happen every time. It seems to shut down and stay there if I've exercised it a bit with some apps. I did install Netflix and watched a few minutes of something, then shut down and it stayed off.
Things are definitely improving.
Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.
ieatabiscuit said:
Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.
Click to expand...
Click to collapse
Thanks for the reply. The only builds I've been able to find are the UNOFFICIALS from amaces, for which I am most grateful. CM-12.1 nightly download pages for ovation and hummingbird always come up blank. Where should I look for those beta releases you mentioned?
But yes, I've moved on to amaces's build 20150716, which when installed by CWM 6.0.4.6 from a booted microSD card to a wiped target has shown no problems, except of course for the reboot after shutdown.
But when installed with resident TWRP over an earlier build the "Unfortunately Google Play services has stopped" problem appeared. I got it fixed on one of the Ovations but not on a second one.
I noticed build 20150717 this morning which I might try on an additional Nook (I have 7 of them scattered around here).
I wonder what's counting out the approximately 10 seconds between shutdown and reboot?
It sounds like you might want to try a different gapps file then. The unofficial amaces builds are the ones I meant, the latest ones are great. For gapps try googling "tk gapps pico" its a bare minimal gapps that let's you install the rest that you use from play store. It works for me, so maybe it will help you. Also, a full gapps file runs the ovation and hummingbird pretty hard on RAM, that could possibly cause an out-of-memory error and make the kernel panicked, which leads directly to a reboot. That pico gapps can help by freeing up ram for more useful things than having everything Google has to offer running all at once.
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.