Which is the proper way to downgrade from cm11 to cm10.2? - Galaxy Tab Q&A, Help & Troubleshooting

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

Related

rom question

On the goomanager app when I browse compatible roms there are quite a few besides nightly. I know what nightly is, but what are the others? Like teamdouche,aokp, eyeballer, teambroccoli, etc.
I've never heard of teamdouche or eyeballer. I've also never used goomanager so I dont know if it displays ROMs only for the TouchPad or all ROMs in general. But the difference between CM9 and any other ROM is each ROM has their own set of features. Most arent that different. Some have more tweaks than others. All you can do is try them out and see what you like better.
EDIT: Just did a search and I guess teamdouche and eyballer are the devs of the their own ROMs. Again, they probably just have their own features.
jsgraphicart said:
I've never heard of teamdouche or eyeballer. I've also never used goomanager so I dont know if it displays ROMs only for the TouchPad or all ROMs in general. But the difference between CM9 and any other ROM is each ROM has their own set of features. Most arent that different. Some have more tweaks than others. All you can do is try them out and see what you like better.
EDIT: Just did a search and I guess teamdouche and eyballer are the devs of the their own ROMs. Again, they probably just have their own features.
Click to expand...
Click to collapse
yes. you can also go here to see more about different dev roms
http://forum.xda-developers.com/forumdisplay.php?f=1248
also in goo manager app i would advise against installing open recovery script from the menu options. It doesn't play well with touchpad. just use your regular recovery like cwm.
In answer to the OP's question about which is which:
Nightly is the official CM9 nightlies
AOKP is for the Android Open Kang Project (based on the CM9 tree)
Eyeballer is the one who was doing the unofficial nightlies until the official ones got up and running.
Philicibine is host to the CherryKang project (also based on the CM9 tree)
TeamBroccoli hosted a separate mod of AoKP called AOKPCB (again, based on CM9 tree)
TeamDouche is where the official Alpha's were hosted (alpha0, 0.5, 0.6, and Alpha2)
TravP624 created his own cang version of it called BlackICE (not sure about this one).
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
And I must disagree with your last statement there, haxin. The OpenRecovery Script installed TWRM, which allows me to start the flash, wipe cache and Dalvik, right from the app itself on the next reboot, then when it's done, it reboots back into CM9. So instead of me having to go in, manually wipe Cache and Dalvik, then flash the ROM, then reboot, it does it all for me with a couple of quick touches. Plus it's a touch-readable recovery - meaning you don't have to use the Vol-Up and Vol-Down buttons, just touch the screen. I DEFINITELY recommend it, as it is a simplification tool that makes our lives easier. However, it is completely up to you which recovery you use.
ve6ay said:
In answer to the OP's question about which is which:
Nightly is the official CM9 nightlies
AOKP is for the Android Open Kang Project (based on the CM9 tree)
Eyeballer is the one who was doing the unofficial nightlies until the official ones got up and running.
Philicibine is host to the CherryKang project (also based on the CM9 tree)
TeamBroccoli hosted a separate mod of AoKP called AOKPCB (again, based on CM9 tree)
TeamDouche is where the official Alpha's were hosted (alpha0, 0.5, 0.6, and Alpha2)
TravP624 created his own cang version of it called BlackICE (not sure about this one).
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
And I must disagree with your last statement there, haxin. The OpenRecovery Script installed TWRM, which allows me to start the flash, wipe cache and Dalvik, right from the app itself on the next reboot, then when it's done, it reboots back into CM9. So instead of me having to go in, manually wipe Cache and Dalvik, then flash the ROM, then reboot, it does it all for me with a couple of quick touches. Plus it's a touch-readable recovery - meaning you don't have to use the Vol-Up and Vol-Down buttons, just touch the screen. I DEFINITELY recommend it, as it is a simplification tool that makes our lives easier. However, it is completely up to you which recovery you use.
Click to expand...
Click to collapse
I guess I just got used to managing all the recovery flash options through rom toolbox pro, it is one of my MUST have apps for sure. I always liked using the non touch recoveries because its only a matter of time before you acidentally tap an option you didnt mean to and mess something up. I went back to the regular cwm recovery after this happened 3 or 4 times to me. maybe i'm just not very coordinated. I do however love goomanager it is a must have app.
The nice thing with TWRM is that you have to confirm everything each and every time by a long swipe - not even just a "Tap here for OK", it's a swipe toggle, like the slider unlock from CM7 or CM6 phones. Makes it a LOT easier to not screw up. Because I agree, if it was just a tap-tap-done, it would be bad. A swipe, that's a little harder to screw up (Don't get me wrong, it can be done, but it's harder).
ve6ay said:
The nice thing with TWRM is that you have to confirm everything each and every time by a long swipe - not even just a "Tap here for OK", it's a swipe toggle, like the slider unlock from CM7 or CM6 phones. Makes it a LOT easier to not screw up. Because I agree, if it was just a tap-tap-done, it would be bad. A swipe, that's a little harder to screw up (Don't get me wrong, it can be done, but it's harder).
Click to expand...
Click to collapse
ok well that is alot better than some of the cwm touch recoveries that I tried a while back.
Yeah, I really like it. The other huge bonus is again that it scripts to run all your updates through the recovery from GooManager. So this way, you can tell it to flash a series of two zips (For example, your rom, then gapps), as well as clear your cache / Dalvik, and even do a full data wipe, all from GooManager, then it reboots, does it, and restarts into Android for you. I can't say that I've come across anything that allows me to do that in CWM.
ve6ay said:
--SNIP--
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
--SNIP--
Click to expand...
Click to collapse
Lately, TWRP shows the TP as a hercules. I've checked build.prop and build information in Settings, and they all indicate tenderloin. Any idea why TWRP would think it's a hercules?
shumash said:
Lately, TWRP shows the TP as a hercules. I've checked build.prop and build information in Settings, and they all indicate tenderloin. Any idea why TWRP would think it's a hercules?
Click to expand...
Click to collapse
Hercules is the code name for a T-mobile Samsung galaxy SII (T989) as used by rohan32 in his supreme mods for compatibility with gameloft games, if you flash his mod that's what goo manager will find
Sent from my CyanogenMod9 TouchPad using TapaTalk 2

[Q&A] [ROMS][SGH-T679]Mass CM Thread

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.

What is the best ROM for Z1

Hello, i have the c6903 and a modded but official 5.01 ROM along with Twin Recovery and Exposed.
The phone works ok until it starts to seriously lag, with icons taking ages to appear on screen (like the HOME screen or APPs screen). Also at points, it fails to recognize any WIFI signals. It is as if there are no signals at all.
The biggest issue is the reboot. In order to restart OS i have to enter recovery and wipe Cache which leads to an approximatelly ~13minutes boot up time.
Now i browsed the ROM section and i've nerver seen so many ROMs available before. It makes it hard to choose which on to install.
I need a rom with Dual Recovery and root. Which is the best offer at the moment with SONY camera software working? I dont care for experimental ROMs but i need something stable, fast and well, fast.
Thanx for reading this.
Hi, installing Xposed Framework will it lead me to bootloops? Was that the cause of my bootloops with the .254(i think) version?
Hi,
First, there is no such thing as "Best ROM", the best to do is search the Development Thread, read some threads, some comments and go for the ROM that interests you. I am running Stock Rooted + Xposed and it has been quite nice to me.
About your question, Xposed is still in alpha version, so maybe it indeed caused bootloops, but latest version has been running fine on my device. I'm running .270 firmware by the way.
All the best,
~Lord
BLiapis said:
Hello, i have the c6903 and a modded but official 5.01 ROM along with Twin Recovery and Exposed.
The phone works ok until it starts to seriously lag, with icons taking ages to appear on screen (like the HOME screen or APPs screen). Also at points, it fails to recognize any WIFI signals. It is as if there are no signals at all.
The biggest issue is the reboot. In order to restart OS i have to enter recovery and wipe Cache which leads to an approximatelly ~13minutes boot up time.
Now i browsed the ROM section and i've nerver seen so many ROMs available before. It makes it hard to choose which on to install.
I need a rom with Dual Recovery and root. Which is the best offer at the moment with SONY camera software working? I dont care for experimental ROMs but i need something stable, fast and well, fast.
Thanx for reading this.
Click to expand...
Click to collapse
I had the same issues as you and I finally found a ROM that is really smooth! However it does not have Sony camera software as it is based on cm12, the ROM is crdroid
Thamx for the reply guys

Help and Advice for First Time Attempt at Rooting

Hello XDA community, I am a 100% new noob who is interested in getting started with rooting. I am going to get right to the point with what I am working with, what I have done, and what I need some help with. May my journey with lovely pictures be a helpful guide for all those who follow me (I find it is easier to understand things with lots of images).
Used this thread to begin my journey on rooting an old Nook HD tablet.
Started with a factory reset but it automatically updated according to my settings page, so one of my question is; does it matter what software version my device is running before I root it?
Followed instructions in PeteInSequim guide and created an 8 GB Micro SD Card with all the files.
Green = CM-12.1_Installation_20150925 Instructions PDF
Light Blue = Files from NookHD-bootable-CWM-6046-for-emmc-BOOTFILES-rev0-(07.13.14)
Red = CyanogenMod 12.1 (No official release on their website)
Orange = ClockworkMod_Recovery (Couldn't find website for other versions)
Yellow = TWRP Recovery (They may have a newer version)
Purple = TK-GAPPS (Which I downloaded the STOCK package, and am not sure if that is compatible)
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake. Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
Thanks for the help,
Buckaroo9
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions any time you wish, but you must do the wipes first. This means you will have to go through the set-up procedure all over again, which takes a lot longer than a dirty install.
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
Click to expand...
Click to collapse
PeteInSequim
Could you please explain this concept slightly more to me? How much would I be able to change and what would the consequences be? If I make changes would I always have to do a clean wipe, would that mean I would have to not make changes and constantly wait for updates? This uncertainty is kind of pushing me away from rooting...
Buckaroo9 said:
...
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake.
Click to expand...
Click to collapse
The files you got look right, although I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
...
Click to expand...
Click to collapse
CM12.1 for the HD/HD+ is not officially supported and, more importantly, is no longer enhanced/maintained (its original developer has recently moved onto CM13). I've been using CM12.1 for about a month now: the apps' performance can be noticeably more snappy but not consistently so, on the downside couple of apps/features that used to work on CM11 no longer work.
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
digixmax said:
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Click to expand...
Click to collapse
Is there any reason TWRP can't flash itself?
digixmax said:
I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Click to expand...
Click to collapse
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
digixmax said:
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
Click to expand...
Click to collapse
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)? Someone made a good point that, the most advanced, newest, and coolest software will always be unstable. You have to trade off the cutting edge for reliability and support.
As a new member to rooting, I think I may start with more stable things, and then work my way up.
Buckaroo9 said:
Is there any reason TWRP can't flash itself?
Click to expand...
Click to collapse
The TWRP flashable zip file you have contains a TWRP image that is compiled for internal EMMC. Once installed, it can be used to flash CM, GApps, or another version of CWM or TWRP to replace itself.
To flash from SD you need to find and use a TWRP recovery image that is compiled for SD.
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
Click to expand...
Click to collapse
You can use a Zip archive program like 7-zip to open up and browse the content of these GApps zip packages to see and compare their particular mixes of apps.
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)?
Click to expand...
Click to collapse
This depends on your particular use and choice of apps for the tablet, but as examples, the Hulu app and USB Host feature which work on CM11 don't work on CM12.1.

Is there any OS that works ?

Hello .... I'm finding whatever OS I'm trying becoming unstable to use . So, I'm asking if there is any OS that is actually stable enough to use . I don't care whether it's an old version or what . I'm not using the tablet for games, just something I can browser the internet with . TIA
The one that has given me the fewest issues is https://forum.xda-developers.com/showthread.php?t=2712680 [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [06/12/15]
everything works extremely well except the DSP manager when adjusting audio settings for the built in speakers where changes beyond the defaults do not have any effect on the audio.
Sadly many of the links are dead for things like gapps.
The ROM I use is cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
The gapps I use is: gapps-444-base-20160802-1-signed.zip
If needed, I can upload the gapps that I use though I am unsure if the forum has any rules surrounding it if I were to upload them to something like dropbox.
I try the others from time to time (easier for me since I really only use BSplayer and chrome in order to watch videos in a hover window while surfing the web (occasionally using my Bluetooth speakers or headphones).
Anyway, the main reason why I keep coming back to it, is the memory management. For many newer ROMs, you have issues such as the google calendar widget not working,or chrome not working properly, or when it is working, frequeny memory issues, especially if you want to upload an image to a site where it switches to the gallery app. by the time you select an image, it would fail to attach it because it will complain that the previous action could not be completed due to low memory.
With android 4.4, I do not have that issue. I don't know why it keeps happening for me since there are times when there will be over 100MB of free RAM, and chrome will still fail to do things with that error message.
Beyond that, the home screen under android 7.1.1 does not hold as many icons or widgets, even if you set the screen size to small, or adjust the dpi to 120. the home screen holds fewer icons and fewer widgets.
Overall, while it si great that newer versions of android are being supported, I feel that from a hardware standpoint then tablet has reached its limit with android 4.4
While there is also an evervolve version of android 4.4, for some reason it does not perform as well, even with more kernel features such as being able to overclock past 1.78GHz. it takes longer to boot, and some widgets do not work, along with issues with chrome.
https://forum.xda-developers.com/showpost.php?p=71176374&postcount=937
Check out the Nougat Evervolv thread. I've been using it, and it's fantastic.
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Dude905 said:
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Click to expand...
Click to collapse
Yes it has, but you need to download the nightly from their website. The XDA thread has an older version.
http://evervolv.com/devices/tenderloin
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Dude905 said:
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Click to expand...
Click to collapse
I'm not sure about the Youtube instructions, and I followed the written instructions on the forums.
Also, IIRC, if you're using a 7.1.1 ROM, you can't use a 5.1.1 Gapps. I would recommend downloading the newest 7.1.1 Gapps.
Here are the instructions I followed:
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the 9/6/16 TWRP 3.0.2.0 or the smaller 9/11/16 TWRP 3.0.2.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the ROM from the OP along with some OpenGapps
10. Worship @jcsullins and @flintman, as they are your gods.
Click to expand...
Click to collapse
Here are the changes/differences I made/noticed:
crazyates said:
Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.
Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.
Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).
Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.
Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.
Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.
Click to expand...
Click to collapse
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
bobcote said:
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
Click to expand...
Click to collapse
I am running the 7.1.1 nightlies. I haven't had any problems, and it's running very smooth. I'll randomly update it to the newest nightly, and haven't noticed any issues.
I do remember the time I first installed Evervolv 6.0 nightly last year. I installed it, and the touchscreen didn't work. At all. Looked into it, and it was a problem with that specific nightly build, so I went and reflashed everything with the one from the day before, and it worked great.
Anyways, all that to say it's working great, but it's still a nightly, so sometimes things go wonky.
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
wprpalmeida said:
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
Click to expand...
Click to collapse
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
crazyates said:
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
Click to expand...
Click to collapse
yeah, this is what I want to figure out. The developments in the Android codebase were quite extensive between these two releases, and the huge influx of budget phones in some markets (like mine for example) lead me to believe memory management would have been a key point in developing versions after 4.4.4. I'll give 7.1.1 a whirl and see how it goes.
Here are the instructions I followed:
...
Here are the changes/differences I made/noticed:
Click to expand...
Click to collapse
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
I used the latest nightly (ev_tenderloin-7.1.1-nightly-2017.03.08.zip) and tried both open_gapps-arm-7.1-pico-20170312.zip and open_gapps-arm-7.1-pico-20170312, also I tried some of the TWRP-Versions you linked. I'm using TPToolbox v42 2015-01-08). So I wonder how you can figure out which versions fit together, I can remember this nagged me last time until I found a combination that worked...
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
Click to expand...
Click to collapse
Flexmaen said:
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
Click to expand...
Click to collapse
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
7.x is very slow some times.
Flexmaen said:
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
Click to expand...
Click to collapse
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
giolc90 said:
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
Click to expand...
Click to collapse
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Flexmaen said:
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Click to expand...
Click to collapse
Perhaps using F2FS could help, if not currently using it?
crazyates said:
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Click to expand...
Click to collapse
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
DoubleStuff said:
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
Click to expand...
Click to collapse
It doesn't work for me ... I'm having issues . First off I like to ask why he didn't use the latest Rom ? And the part with go to the PC Mounted Touchpad internal drive for the TWRP ? When I open the TWRP folder I don't see twrps file, why not ? There nothing in this folder, its empty . What I done was just placed those zip files in the TWRP folder . Afterwards once I do the final reboot to Evervolv it will just show those Evervolv lights flashing like its trying to load up but it doesn't, it just keeps continuously trying to load but it never does

Categories

Resources