Related
Hey guys,
I love my 101it and can't wait for full root.
in the mean time I've been using z4oot like everybody else.
But since yesterday that stopped working for me.
I've been running z4root and it said that temp root has been granted.... but it hasn't.
I've tried rebooting. Enabling and disabling USB debugging,but nothing works.
I feel like I'm skipping some stupid step.
Anybody has any idea?
Thanks!
Check free memory using ATK or any other app killer. My Z4 was giving me the same issues till I fixed the free memory. My issues started when memory went below 49MB. So I uninstalled some apps and no issues so far.
Some said that you need more space for it (100MB free out of 300MB).
Some also said that it only works after they moved all their apps back to the 300MB storage after they used app2sd (and may or may not have uninstalled it before they rooted).
Some said clearing the data/cache of and reinstalling superuser/z4root worked for them.
Also, once you got it rooted, don't reboot, use hot reboot to keep your root while booting.
For me, I haven't tried the second solution, and I had to reinitialize the entire system... Thankfully appmonster backup, titanium backup, and appbrain sync makes it easy to reinstall all the apps I had.
Thank you guys.
I was able to release 78mb on my internal, cleared data and cache on both but its still not working.
I would consider formatting but since I have no root I can not backup using TB...
Ill try to clear more space later and retry.
Will post results here.
Any other ideas?
Thanks!
Consider backing up with appmonster, swiftp, usb, appbak (list of app, if app monster don't do that already), and appbrain (for quick reinstall).
I believe appmonster let you backup apks, and app list. And with appbrain, you can just copy your synched app list to the new install and tell it to install them.
I had the same problem before and as MoonPhantasm suggests... moving all apps back to the phone from internal storage let me root again. Give that a shot.
The problem is that I have way too many Alps to keep in the measly 256mb on this device...
I ended up formatting the device and now it works.
lets see how long I can go without a full reboot
Thanks all.
madhouze said:
The problem is that I have way too many Alps to keep in the measly 256mb on this device...
I ended up formatting the device and now it works.
lets see how long I can go without a full reboot
Thanks all.
Click to expand...
Click to collapse
There is over 300 MB for "Alps" on the device unless you move them to SD in which case there is nearly 8 GB. There is 256 MB of RAM which only comes into play when you swap applications to background. Formatting is like swatting a fly with a grenade launcher but then if you don't know RAM from flash...
I'm finding the tablet pretty responsive without upping the CPU limit but I would prefer a more clear and workable solution than formatting every time I reboot.
sequitur said:
There is over 300 MB for "Alps" on the device unless you move them to SD in which case there is nearly 8 GB. There is 256 MB of RAM which only comes into play when you swap applications to background. Formatting is like swatting a fly with a grenade launcher but then if you don't know RAM from flash...
I'm finding the tablet pretty responsive without upping the CPU limit but I would prefer a more clear and workable solution than formatting every time I reboot.
Click to expand...
Click to collapse
I have autocorrect to thank for the "Alps"
I agree - there are 300mb for apps, but I use a lot of apps on my device, and some are rather big (it adds up) and most of these unfortunately do not allow to move to SD Card. I can force some of them to SD using Titanium Backup, but then again once I go under a certain threshold I cannot root and therefore cannot use TB.
I would love to have more than 300mb for apps. It seems kind of stupid that out of 16GB on the device they partitioned only 300mb for apps.... Unless I am missing something... in which case please feel free to correct me.
I do appreciate the opinion though.
Ohad.
madhouze said:
I would love to have more than 300mb for apps. It seems kind of stupid that out of 16GB on the device they partitioned only 300mb for apps.... Unless I am missing something... in which case please feel free to correct me.
Click to expand...
Click to collapse
You have to remember that the folks that frequent these boards are not the typical end-user. I had read that the average user installs 8 apps. I have 64, and you are probably around the same high number. The space allocated to the system apps area is not available for content storage, so to most users even the 300MB seems like too much wasted space.
I got 90 apps installed myself, and only have about 30-40MB free right now. Was full for a bit, before I uninstalled a few things... :/
It is pretty ridiculous to only have 300MB for app, when there are 8GB total space. My first time reaching that limit shocked me quite a bit.
About average users installing 8 apps, that sounds impossibly low. Over time, even average users are going to accrue quite a lot of apps. I don't think average users are good at 'uninstalling' things that they don't use til they have to.
Had the problem too and some of it was due to app2sd. Plus, apps keep disappearing when using app2sd, so this feature, one of the most important of froyo, isn't working at all.
Read in another forum that it might be a good idea to first stop all apps by using TaskControl or a similar task manager, before trying to root.
I can't seem to get Z4 to work at all now after doing the firmware update. Tablet seems a lot more stable than it was before the update but would still like to be able to use setCPU to bypass the CPU lock.
jagpoag said:
I can't seem to get Z4 to work at all now after doing the firmware update. Tablet seems a lot more stable than it was before the update but would still like to be able to use setCPU to bypass the CPU lock.
Click to expand...
Click to collapse
In the latest patch they fixed the options that were allowing temp root. This was mentioned in other posts. Right now there is no root for this device.
Faldiin
Instructions I use to root my A70 IT 8 GB
Hello,
I've been using z4root on my A70 IT 8 GB, since I discovered the ping command requires root access on the Archos Gen 8 line. In the meantime, I found additional reasons to use root mode, such as:
1) MyBackupPro supports root mode for full application and data backup.
2) Swap to increase the memory on these 256 MB devices. While swapping to a SD Card isn't a good idea, I'm looking to do it on the 250 MB version.
3) 1 Ghz fix, which once I can go to the 2.0.71 firmware won't be necessary.
4) Run applications that use the ping command.
I'm using these instructions for running z4root on my system. They assume you already have z4root installed on your system. As for validating rooting was successful, there are a couple of ways on the Archos Gen 8 devices:
1) Run setCPU
2) Run the Terminal Emulator and try to use the su command. If it exists you're golden, if not then it failed.
Steps I use:
1) Let the boot process complete, but don't start additional commands.
2) Make sure USB Debugging is on and (if you want) see if there is at least 100 MB of storage left.
3) Start z4root
4) Select temp root
5) Confirm the notice about USB debugging. If it doesn't appear, something isn't right.
6) z4root will take you to the settings. At this point select development from the opened settings, disable and then enable USB debugging. Confirm the message about USB debugging.
7) Return to the home page.
8) Go back into settings -> Applications -> Manage Applications -> All Applications (tab). Go to the bottom of the list, find z4root and select it. Once there you need to:
8A) Do a Clear Data. This is important.
8B) If z4root is running do a Force Close.
8C) Return to the home screen.
9) Start z4root again.
10) Select temp root and in 5 seconds or so you should see a White flash and the text on the screen should change to say the application is finishing up.
Allow it to finish. See notes below should these steps fail to produce temporary root.
z4root will tell you it was successful whether it was or not. I don't know why. At least on the Gen 8 line checking is as simple as seeing if the "su" command exists on the system. If it does, you're golden and if not then something failed and you can't access root.
To validate success, I'll use one of the following methods:
TERMINAL EMULATOR: Start the Terminal Emulator application and issue the "su" command. If this fails, you don't have root. (Note: If this is the first time running terminal emulator in root, you'll get a message asking to give your permission for terminal emulator to have root access. If the message fails to appear, you don't have root. Again this is the first time only.)
setCPU: Start setCPU and if it is the first time ever using the command, run the Device Selection choosing "Autodect Speed Recommended." If you get a screen asking permission to add setCPU to the list of application, you're golden. If you don't get the prompt or setCPU says it failed to get root, you don't have root.
Subsequent times you use setCPU and adjust the maximum speed, you'll see a message flash on the screen about setCPU gaining superuser permission. This message is from the Superuser application. NOTE: You may see the message even before you adjust anything on subsequent uses of setCPU during the same session.
TROUBLE SHOOTING z4root:
Should z4root fail, you should try it a second time after doing a Clear Data and Force Close. If this fails, do a reboot and try again.
Should it fail all the above retries, I go back to square one. I'll uninstall it, download it again from XDA-Developers, and install it with reboots between each step. I have yet to have this last method ever fail on me.
Typically, though, I don't need to go beyond a second try with a reboot.
Should it again fail, my best success has been to uninstall z4root, reboot, reinstall, reboot, and then follow the instructions.
Good luck and hopefully your mileage will be as good as mine.
If you hear of a version working with firmware 2.0.71, please, let me know.
BGMArchos,
i'm not sure to understand you... you have root your 70it with which firmware ?
not the latest firmware. He said once he can go to the .71 firmware the 1GHz fix from rooting wont' be necessary.
But I find unrootable android device pretty ridiculous. I'll be trading this archos for another device at this rate.
I am sure perm root will come, it's just a matter of time.
Btw what alternative is there for the archos in its price range.
I use the 71 firmware and i am pretty happy with the archos at the moment.
When root comes it will just get better.
But for now I can live without root.
Biggest improvement in think is the way it handles the ram. I don't need to kill any tasks anymore like before. That was one of the most annoying things about the tablet.
Not like it was really much of an issue. You can always reboot every a while too as it reboot pretty fast.
So I installed the new gingerbread powerwashed rom (amazing rom by the way) and went and bought Settlers of Catan off the marketplace. It wouldn't download and the developer (of the game) says its because of a download size limit present on Samsung devices. I found the apk online and sideloaded it (which is a gheto albeit functional workaround) but this means I still cant update it since it gives me the same error. Is there a way to fix this on my phone?
Just a limit for the market you mean? I've downloaded 1.5 gb files from the browser before?
haven't heard about this before.
There is some kind of download cache for apps that you download. Apparently it is limited to around 30 megs which becomes problematic for apps like Catan which are larger (35megs in this case). This is not the same as the system memory (I still have about 1.2 gigs of system memory free and many more on the SD card free). If you download a file through the browser, it is not subject to this limit. Trying to figure out how to bypass it though.
I've been having a bit of trouble with my HD2 for some time now. Sometimes it just freezes and only a hard factory reset (VolUp+Down while rebooting, then VolUp) clears the problem. Temporarily.
I've run Win6.5 mobile for a while and tried Android aswell but due to problems with booting to Android I've stuck with Win6.5.
I've already downloaded the latest firmware for my HD2 several times and installed it several times. However, every time I try to get back in to Windows, it seems I have a little less free storage space. Eventhough I don't install anything.
At the moment, the errormsg:"Your phone is running low on free storage space. Delete old or unused items to create more space." is more on then off.
I've downloaded ClearTemp 1.3.1 Final but it couldn't clear more then about 50kbits of data, which is normal since I've done a hard reset about 2 days ago.
What strikes me as odd though is that it says my free storage space is very low. For programs I've got about 130MB left, but for main only 0.3MB out of 10MB.
If I'm not mistaken that should be way more then just 10MB but I have no clue how to fix this.
Anyone able to help me out with advice?
Please, more info:
- STOCK ROM or CUSTOM ROM (which version?)
- SPL or HSPL (also which version?)
- which radio?
I have the CM10 [skang jellybro] fascinate rom installed, and coming from a cm9 rom, all my apps didn't fit because they switched the partition around [making the app partition only 468MB, and the system partition 1.5 GB].
So anyway I had to move a lot of apps to the sdcard. So I just downloaded a newer version of my rom, and wiped cache/dalvik, nandroid backup, then I installed the new zip.
Then I rebooted, and it had to 'optimize' apps [create dalvik cache?] and after that finished...I only had about 15-20 apps show up in my app drawer. [I have probably around 40] So I clicked on Zedge, on my homescreen, and it said "App isn't installed." I then started to worry..:S I googled apps on sdcard disappearing.. and so I opened titanium backup, and under Batch operations, it said "Restore missing apps (6)," and they were 6 apps that I'd uninstalled but didn't delete the backup. so then I wasn't sure what to do next, because I did not create a fresh titanium backup prior to updating my rom [because I did a nandroid instead..] so then I went to Manage Apps, and then.. for some reason, all my apps showed up again! all the ones on my sdcard.
I tapped Zedge again on my homescreen, and it loaded up! So my question is, what happened? Why did my apps disappear, and then just show up again? was it loading titanium backup? or did the rom just scan the sdcard for apps?
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Crawshayi said:
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Click to expand...
Click to collapse
ah.. yes they are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
I guess if it is the media scan thing, that would explain it.
Fast Boot option may be the culprit
mvmacd said:
ah.. yes the [apps] are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
Click to expand...
Click to collapse
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE3D5NrpiSqCRSof-ou1mn6iyeGVg
(I am copying this original post (without edits) to other relevant threads, but will not post anything further elsewhere -- only here. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
EDIT 2012-12-26-a:
Nearly all of the 100+ apps on my HTC DINC (Droid Incredible) continue to behave normally after the "fast boot OFF" fix. (No disappearing act.) However, I did find one that appeared to be installed but really was not: ASTRO File Manager. I used Titanium Backup Pro to reinstall app+data from a backup. It only took a couple of minutes, and after that all went normally.
The only other noticeable issue right after the fix is that nearly all of my installed, functioning apps were listed as "missing" by Titanium Backup in its Batch scenario list (although they were NOT counted in the total number of apps listed with the scenario -- that number was 61, and it should have been nearly 170 based on the number of apps actually in the physical list). After about a day or so of regular usage, a re-check of the "missing apps" Batch scenario found all the functioning apps no longer listed; the 61 missing apps were valid -- they were all from earlier ROMs belonging to the original HTC setup and another phone (MOTO OG Droid). Since I have kept the MOTO as an emergency backup smartphone, I might conceivably want to revive some of these apps.
EDIT 12-26-b:
Some other potentially useful points I have gathered in my survey of this topic across XDA:
1. This problem happens most often when using the "Disk drive" option in the USB Debugger system app. It also happens after physically returning the sdcard to the phone after removing and inserting it into a PC.
2. Those who have wiped the app data cache also report serious problems.
3. Wiping the dalvic cache while in Recovery mode automatically triggers a rebuild of that cache, which may make apps behave oddly or disappear until the rebuild is complete, which reportedly "takes time"
Personally, I did only #1 myself, and the fast boot removal fix seems to work well for that one.
I cannot confirm the others, but they seem to make sense to me, and I doubt the fast boot removal fix would have any influence on them.
4. There are some signs that apps installed to internal phone storage can behave in the same way. This may mean that the fast boot OFF tweak may prove beneficial to any storage area, since they all come on-line after the OS loads from phone memory.
EXT4ALL (aka Convert2ext4) = final fix for dalvik cache related bugs (?)
Further investigation of the Dalvik cache reveals a significant connection between it and a number of odd and unpleasant behaviours, including Low Disk Space warnings and disappearing apps.
Fortunately, there are some excellent XDA forum threads about dealing with the Dalvik cache.
The best recent place to start seems to be here:
[Q] Incredible running CM7.2 "Low on space" message (launched 2012-12-14)
http://forum.xda-developers.com/showthread.php?t=2047424
It is not because of the focus on the Droid Incredible or CyanoModGen in this thread, but the attention paid to the more universal fix "EXT4 4 ALL" aka "EXT4ALL" or "Convert2Ext4". (Thanks to Senior Member cmlusco for his post #9 on the thread that got me started in the right direction!)
Files can be found at these locations:
Goo.im site http://goo.im/devs/tiny4579/mods
DINC.does-it site http://dinc.does-it.net/EXT4_Mods/
One version of this fix (Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip) moves the Dalvik cache from the default, limited 150MB internal partition to the "unlimited" (or at least maximum) 750MB internal partition.
Any phone with a kernal installed that supports ext4 can utilise this fix.
[ I personally use gingertiny 2.6.35.14-v2+ (2012-02-13), which has supported ext4 since late 2011]
My own experience has been to flash the "no data limit normal dalvik" zip file using ClockworkMod 5.x Recovery -- this was entirely painless. I just downloaded the file into my phone's downloads folder on the sdcard using a web browser, then ran CM Recovery (with a little assist from ROM Manager), selected "install a zip from sdcard" and navigated to the file. It was all done in 5 minutes. After manually rebooting a second time, everything seems to be working normally after about half a day of regular use.
For those who flash a new or updated ROM sometime in the future, you would need to flash this fix after doing so.
There is plenty of information contained on the main threads of this topic. Links aplenty can be found; just follow the ones provided in the thread I suggest here to get started.
Hopefully, this brings an end to my struggles with my phone's storage issues, and to others of you reading this post and following the links to the threads and downloads.
FYI -- My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)
So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.
SUMMARY:
1. Turning off "fast boot" in Android settings helps some, but it does not get to the heart of the issue. It will NOT make a Low Disk Storage warning go away.
2. Once you have a Low Disk Storage warning, you MUST uninstall enough apps to make it go away (keep track of what you take away, because you can reinstall them very soon!)
3. With no LDS warnings showing, flash the "Convert2ext4 no data limit normal dalvik" zip file. THIS APPEARS TO BE THE REAL SOLUTION!
4. Reinstall your recently removed apps, and you should be good to go! :fingers-crossed:
PS>>> One last unresolved issue: I am still unclear exactly WHERE the dalvik-cache ends up, since my Astro file browser cannot locate anything containing the word "cache" that does not now report "EMPTY". There are a large number of "com." folders containing software I have installed found in the /mnt/asec/ folder. The total size of the contents of this folder (362 MB) is within 100MB of the amount of internal memory reported in use. Does that 100MB represent the current size of the Dalvik cache files, or at least include them? If so, where are they located? If anyone can help me figure this bit out, I would be grateful! :fingers-crossed:
Hello...I'm running Elegancia and Nova browser right now with SuperUser installed. I went to place a "system reboot" shortcut on my homepage. When I went to use it it asked for "Superuser Priveleges" which I granted...but after that there was an error saying that the program couldn't work on an 'unresponsive shell" or something like that. I had the same issue when i tried to install a power down button through the power toggles app. Any idea why this is happening?
I have another question about a different issue, but I'll post it here to avoid making multiple threads. I go into advanced task manager and even after I kill everything it says there is only 300mb of RAM left...is this normal? Does the system/ROM/launcher consumer 700mb of RAM?
Also, BUMP to my first question
I will try to answer your first answer but I don't have the exact answer to this only a theory. The Widget shortcut is only valid for a Reboot on a Sense based ROM and since you are using Nova launcher...
As for your second question...
You don't have to worry about memory. The OS manages how applications use your phone’s RAM. It only allows applications and their component processes and services to use RAM when they need it. It will cache processes that you’ve been using recently in RAM, so they restart more rapidly when you open them again, but it will erase the cache if it needs the RAM for new applications. It's not a Windows like system where the more RAM you have the better the OS is responding. This is based on Linux core and the memory management is totally different. And way more effective. If this phone was built with 2Gb of RAM the cache would only cache more applications and their components processes since more space would be available for caching.
Lucky Thirteen said:
I will try to answer your first answer but I don't have the exact answer to this only a theory. The Widget shortcut is only valid for a Reboot on a Sense based ROM and since you are using Nova launcher...
As for your second question...
You don't have to worry about memory. The OS manages how applications use your phone’s RAM. It only allows applications and their component processes and services to use RAM when they need it. It will cache processes that you’ve been using recently in RAM, so they restart more rapidly when you open them again, but it will erase the cache if it needs the RAM for new applications. It's not a Windows like system where the more RAM you have the better the OS is responding. This is based on Linux core and the memory management is totally different. And way more effective. If this phone was built with 2Gb of RAM the cache would only cache more applications and their components processes since more space would be available for caching.
Click to expand...
Click to collapse
Good to know about the memory. Regarding my other issue...I don't know what happened, but I reflashed the ROM without wiping and the reboot shortcut started working.