Database Develop

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Buzz] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Very nice m8,
i'm using it on my CM7 Build #0, with much apps i have 156MB free..

cool man sounds orsum will have to add this to my new rom

Would you say this is better than the normal Froyo App2sd? is it any faster at loading the apps one the sd card loading from **** drive mode?

Froyo app2sd sucks, this one is heaps better as apps are stored on ext partition, so you save way more internal phone memory. And yea its fast.
Sent from my HTC Wildfire using XDA App

nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms

I have now installed this, how do i know apps are being moved to the sd card?

I would love to for those roms. I'll have to look at the roms. Unfortunately, I don't have a ZTE Blade, but I don't own most of these phones that Darktremor works on (I only have a Sprint Hero and a Sprint Evo).
The more roms, the better.
danne_jo said:
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
Click to expand...
Click to collapse

Run a2sd check. That will check the configuration and tell you if everything is setup correctly.
-Howad- said:
I have now installed this, how do i know apps are being moved to the sd card?
Click to expand...
Click to collapse

You can also just start "Titanium Backup" and check memory in the main screen

I installed Darktremor app2sd on Modaco custom rom (Froyo), and must say its excelent, I got internal memmory of 160 mb free, and now with 100 apps installed have 155 mb free. My ext3 partition is 512 mb and Dalvik cache is on ext3. With zipalign phone work well, no issues about stability, widgets work normal (its not case with Froyo a2sd).
Thanks Tkirton for this.

bump---new version available.

is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)

rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
I want to know about that too. Can we flash the new version on top of the original one? Will it harm the installed apps?

"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???

how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.

Just flash on top of it.
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse

Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
WackyWookie said:
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
Click to expand...
Click to collapse

Describe the steps that you went through in installing it, including any commands you ran after the install.
vilks said:
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Click to expand...
Click to collapse

tkirton said:
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
Click to expand...
Click to collapse
Ah good I was starting to doubt my phone's installation, good to know it's a bug...
Sent from my HTC Wildfire using XDA App

[Q] How do I get apps2sd ext 4 working on the Nexus one with the latest Cyanogen Mod?

Hey guys, I'm loving my new N1, but I keep running out of room for applications, and I wanted to know if I could implement Apps2sd ext2/3/4 or w.e to make more room. I like to use Cyanogen Mod, but I'm not sure how to implement it. If someone could help me, that'd be great! Thanks!

Ditto.
Sent from my Nexus One using XDA App

Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...

danger-rat said:
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
Click to expand...
Click to collapse
When i use darktremors, it doesn't work, but if I type in a2sd reinstall, it says location is read only

Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...

danger-rat said:
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
Click to expand...
Click to collapse
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting

Try the DT thread... xD

isikh said:
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Click to expand...
Click to collapse
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.

zero2cx said:
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
Click to expand...
Click to collapse
Thank you, I figured it out.

DT is the best choice, but S2E is simpler than DT, it's avaliable in market

[ROM][NANDROID-BACKUP] minusculeShield 1.0

minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)

This is great. Will give this a shot today or tomorrow. Thanks!

themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.

I still get notification prompts for ota.

themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such

jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.

same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can

milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way

[Q] Total noob I flashed 10.1 everything works but ..

I followed the directions for installing CM10.1 on my 32G Touchpad on the "Easy Way" thread. I used the ACMEinstaller5E. I put the 20131019 build in the cminstall folder with the gapps and the cwm6. Everything works. Apps updated (I had CM9 on for a long time) and all seems ok and working. However, I noticed that my internal storage is now at 1.5G ( I assume the 5E did that) but only 300M is free. That seems like a lot is in use. I had made a nandroid backup of CM9 before i started and went straight over 9. Is the backup sitting in internal memory, I wonder.
Does having only 300M free of 1.5 seem like something is wrong? I believe I have 52 apps.
The other thing I discovered, since I have to push buttons, is that in the recovery or moboot menu when you first turn on the machine, there is an entry for Evervolv and an entry for CM. The first time the TP rebooted after the 10.1 install all the apps updated. Well after I turned off and restarted the TP, I did not expect to see Evervolv on the menu, but I entered it any way. No Problems. Started right up. Showed the 4.1.2 build and everything worked. Decided to see what happens when I chose the CM entry instead of the Evervolv. Took forever to boot and all the apps updated again. Again, it was the same 4.1.2 build and everything appeared the same either way I started; through Evervolv or CM.
So.. where is all that memory being used? And is it unusual to see both the Evervolv and CM choices in the boot menu?
Thanks for any insight you could give me.

I have about 40 or so apps installed and looking in settings/apps shows I have 1gb of storage space used on a 4gb /data partition. I'm guessing it would depend on the app as to how much space on /data it would take up
Using terminal emulator and typing df will display sizes of partitions and how much space is being used.
Your boot options as displayed by moboot depend on what is in /boot. You could use a rooted file explorer such as es file manager to delete any entries you don't want, but be careful what you do delete! If you're running cyanogen mod then its safe to delete the evervolv entry - this gets left behind if evervolv is installed then cm installed at a later date.
Hope this helps...
Peace

Cyanogenmod 13??????

Will cyanogenmod 13 come to the kindle fire hd 7 (Tate)?

Yep, @BuQQzz and I (mostly him, haha) are working on porting CM13 to this device, as well as the 8.9" (jem). I'm not exactly sure when a usable build will be uploaded, but it should be in the not-so-distant future.

I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.

Jaybone073 said:
I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.
Click to expand...
Click to collapse
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.

monster1612 said:
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.
Click to expand...
Click to collapse
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.

Jaybone073 said:
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.
Click to expand...
Click to collapse
If you go into the CM Downloader app settings, you should be able to add in the zips (maximum of 6) you want flashed after a ROM update. Once that's complete, all you need to do is download an update and initialize the install process from within the app, and it'll handle flashing the zips. From personal experience on CM nightlies for jem (the 8.9" version), I tend to see stability break down after about 24 hours of device uptime without a reboot, so reboots do help significantly.

Any progress so far?

Pix12 said:
Any progress so far?
Click to expand...
Click to collapse
Currently, the generated zips take longer than cm12.1 to flash (but they still flash successfully). As for a functional ROM, that hasn't happened yet - it refuses to boot after about 5 seconds. last_kmsg says it's an SELinux issue.