I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
try a task manager and see what is running in the background
try ending programs that may be chewing up memory
set up a swap
What do you mean by set up a swap? My SD card already has a main partition, an ext3 partition and a linux swap partition.
you made no mention of your sd partitions
something is most likely hanging up your memory which is why i said check with a task manager
you can always try flashing the adp again and then cyan
when i first went to cy's i had to do that
I'll try the task manager. Based on how slow it is, it may take me a few hours to get it installed.
i got a quick idea, try shutting off your phone, pull out your sd and try rebooting without it and see what happens without apps2sd going
update to ext3 if you are not already
delete your dalvik-cache if you are upgrading from a previous rom and didn't wipe
huh, did you not read his posts, he has ext3 and he has wiped
Don't know if it would make any difference, but maybe try to install HTC and 4.1.99 and then just flash .999 over the top of that.
hey knowfear, you are not too far from preme, right? do you guys know each other
gridlock32404 said:
hey knowfear, you are not too far from preme, right? do you guys know each other
Click to expand...
Click to collapse
Not personally but I have talked to him in PMs. He lives not too far away from me.
sweet, you might see me driving through your day in about 2, 3 weeks after preme gets me drunker than all hell
so just aplogizing before hand
The fact of the matter is that it simply is DEAD SLOW.
His development process is taken from the MS-developers-handbook.... just keep on shovelling on the bloat, and every once in a while release a new version and CLAIM that it is faster than the last, even when it is slower.
Then you get all the little kiddies, who update with every new version, each of which makes no appreciable difference, BUT because the release notes SAY it is faster, and the fact that they can't really tell, the placebo effect tells them that it IS faster. They keep doing this... several times, so the cumulative placebo effect tells them that it *must be WAY faster*, except that with every new version it actually becomes slightly SLOWER, so after MANY MANY "upgrades", what you turn out to have is something FAR FAR slower than the original.
Just to get a feeling for the differences, try out a stock cupcake build, then try FOUR CM cupcake builds that are evenly spaced out (in order), then again try the stock cupcake build. Then try the stock donut build.
If you want a fast donut that supports apps2sd, etc., and doesn't have the insane bloat, take a look at this one: http://forum.xda-developers.com/showthread.php?t=538456
This ROM is a simple rooted ADP1 donut base, with an "expansion pack" -- from which you can pick and choose the extra features you need/want so as to end up with a system that is optimized to YOUR needs, rather than just packing in everything including the kitchen sink and claiming it is the best thing ever.
zinite said:
I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
Click to expand...
Click to collapse
I had the same horrible lag when I went from 10.1 to .999, so I repartitioned my sd and tried again fresh and it worked perfectly...purrs like a kitten now...
kittens purring is a good thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed it.
I wiped, deleted dalvik cache in console (I can't find the command I used though), reinstalled, fixed permissions in console.
Thanks guys
Related
How to install Froyo 2.2 that works with out a computer & w/ out bricking your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I took the time to write this up because i know how frustrating it can be to brick your phone it has happened to me before trying to update it but I've learned how to flash my phone & done it successfully more then 5 times so far so read this careful before trying it out.
you can install this update with Rom Manager worked perfect for me I've installed 3 of Eugene's Froyo updates with this method just make sure you are rooted first & running kernel 2.6.32.9
or use this kernel here below
Vibrant Kernel Back Support for new Builds
http://forum.xda-developers.com/showthread.php?t=796425
Download Eugene's Froyo 2.2 Macnut update from here
http://forum.xda-developers.com/showthread.php?t=820414
here's a step by step on how i did it
1. make sure to back up all your applications first! I used App Saver FREE application from the market. Open App Saver run it & save your applications this app will save them to the internal SD card so look for the folder called app saver copy & paste it to your External SD card using Astro File Manager FREE application on the market.
2. download macnutR5 update to your phone
3. remove external sd card once you back up your applications
4. install paid version of rom manager
5. open rom manager click on the first option flash clockworkMod Recovery choose Galaxy S Vibrant hit allow on super permissions then click ok.
6. click on install ROM from SD card
7. go to your download folder & point it to the MacnutR4 zip folder hit install
8. optional choose back up current Rom & clear date & cache but no necessary
then let it do its thing it might take 3-5 minutes to finish the update i noticed the update went faster when i plugged the phone to a power outlet.
note 1: this update will delete your apps and you will have to start from scratch but if you back up your apps with App Saver you will be fine read step 1.
note 2: once your done make sure to go into settings mobile networks then network mode and choose WCDMA ONLY! if not you will have 3G problems.
enjoy FROYO!
I'm loving froyo running flash 10.1 watching my NFL games from my phone!
is jit working on the newer froyo roms?
If you click on the link to the ROM you would have read:
~ Working jit ( 14 MFLOPS is about all we get.. 16 ish if overclocked to 1.2Ghz)
GPS still not working in Froyo ROMs for vibrant.
Sent from my SGH-T959 using XDA App
I've NEVER removed a memory card to flash, any real reason for adding that step in your guide?
GPS issues should be stated, agreed ^
You should remove your SD card because some ROMs have bugs and have the tendency of wiping it clean.
So what's the purpose of the Kernal? You didn't mention what to do with it.
MrDragomir said:
You should remove your SD card because some ROMs have bugs and have the tendency of wiping it clean.
Click to expand...
Click to collapse
In near 3 years I have never heard a developer say to take out your sd card, and I've never heard anyone lose the data on their sd card....
s15274n said:
In near 3 years I have never heard a developer say to take out your sd card, and I've never heard anyone lose the data on their sd card....
Click to expand...
Click to collapse
I've had my SD card wiped before. But it wipes the internal card, not the external so removing that wouldn't do much good.
I'm more intrigued at how you are watching NFL games on your phone!? Link?
^ froyo = flash - sites like atdhe.net work... the nfl app is pretty sweet too.
^^ right, that was my whole point... removing the external sd card seems pointless, hence why I spoke up.
In installed dexter mod 1.3 but the firmware update for feb 4th did not update. do I need to install the 1.2 first then the 1.3 are am I doing something wrong. I followed all the instrustions.
No, you should not have to install any of the prior mods since the current mod will include all previous data. But you do need to do a wipe/ reset before applying the update. If not, it won't work properly. See the instructions for installing the mod on this page http://forum.xda-developers.com/showthread.php?t=890042&page=63 and make sure you follow each step. Hope this helps! Btw - refer to Dex's thread for future issues. Most likely, someone else will have the same problem you're having.
Dexter install
Once I put the sd card in and it starts it says something about bad and it can't open the file what do I do then I tried 3 times what am I doing wrong I wiped clean I clean the cache so I don't get get it
Trying to install 1.3 mod need help.
I instaled 1.2 dex mod no problems and now with 1.3 I tried three times with two seperate sd cards and three different downloads and each time the tablet could not find anything on the sd card. I forrmatted the card in fat32 and put the mod only and did the wipe and reset before attempting the update and each time it could not find it. I am going to rename it update only as update.zip or Update.zip are not recognized. After the wipe still shows I am using Dex 1.2.
Anyy thoughts?
Really liked the 1.2 mod and would like to try the new one.
Rob
robbbzilla said:
I instaled 1.2 dex mod no problems and now with 1.3 I tried three times with two seperate sd cards and three different downloads and each time the tablet could not find anything on the sd card. I forrmatted the card in fat32 and put the mod only and did the wipe and reset before attempting the update and each time it could not find it. I am going to rename it update only as update.zip or Update.zip are not recognized. After the wipe still shows I am using Dex 1.2.
Anyy thoughts?
Really liked the 1.2 mod and would like to try the new one.
Rob
Click to expand...
Click to collapse
1.3 still shows as 1.2 in the About screen, Dexter didn't update the build.prop ... This has been covered, dug up, and covered again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
robbbzilla said:
I instaled 1.2 dex mod no problems and now with 1.3 I tried three times with two seperate sd cards and three different downloads and each time the tablet could not find anything on the sd card. I forrmatted the card in fat32 and put the mod only and did the wipe and reset before attempting the update and each time it could not find it. I am going to rename it update only as update.zip or Update.zip are not recognized. After the wipe still shows I am using Dex 1.2.
Anyy thoughts?
Really liked the 1.2 mod and would like to try the new one.
Rob
Click to expand...
Click to collapse
What size file is your download?
I had an issue where my download was only a 63K file (and update would fail), it should be closer to 100MB. I had to start to download 1.2 first, calcel after is started then download the 1.3. I would cork correctly and downloaf the complete file size after that.
Double check and make sure your not having the same issues as I.
Goog luck.
What To Know When Getting a Bigger SD Card I found out the hard way after getting a 16GB PNY Class 10 card for my x10. I had my backups and all that. I copied from the old card to the new one. Then things began acting odd. process.android.media error was really bothering me on startup. So I looked around and found a few suggestions, like clear data drom download manager and media storage. These didnt help at all. I got to looking around under the app management, because I noticed a few app shortcuts were gone. So it was a step in the right direction. I clicked the on SD card tab, started scrolling and said well the last app I moved was this... so I clicked it and went to move it back to the internal memory. It errored out and said something to the effect it was not installed. I went on a witch hunt from that point forward. Apparently Gingerbread will let you know something is amiss. It will have a generic icon and or a checkmark next to the app. I figured thus far the ones with a checkmark could be moved, the ones with a generic icon, were missing and therefore I had to click on each one and uninstall. After doing this all was well. As I really didnt want to move every app back to the internal storage, besides I would have ran out of room too.
The first mistake I realized I made was that, I should have busted out the sd card reader. I was doing this at my mothers and said well its easier. No... Because of the swapping and therefore powercycling the x10. The os scanned or tried to load some apps. There is where it all started going downhill. I thought well I am staying on the same rom, whats the harm.
Important steps / tips I learned.
1. Use a card reader, to transfer all files from old to new card. This also helps with making sure you have a backup too.
2. Consider uninstalling all apps from sdcard, or move them. Depending on situation. I use Titanium Backup & My BackUp Root, so I opt for uninstalling them.
3. Restore your uninstalled apps, or move them back afterwards.
4. Find an app or script to verify all apps are installed correctly? (Dont know if it exists) Otherwise launch each one or verify there are no missing icons or checkmarks present.
Now on to the new adventure of partitioning. I have came across some tips here and there. None really all that dramatic. I am still looking for a guide/line for setting up more than 2 partitions. This is how I have my desktop, but android is a little different. So far I have learned that if you use a Mac, you should bootcamp, dualboot, VM, or boot a linux cd for partitioning. I have not found the right app or terminal commands to make it easier to do. Perhaps I need a better rom. I am fairly happy with zmodv3 hotfix 3. I also think the unlocked bootloader is a blessing and a curse (kernel hell). I still like the CM based ROMS, but am thoroughly turned off by all this MIUI stuff. I may own a Mac, but think iphones are shaat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Suggestions and links are welcome. Please no flaming or bashing about what I have wrote. We all know about opinions.... Besides I have to sart posting sooner or later.
After some more tinkering 11/11/11- I have discovered that there is an issue with xrec 0.3gb ready, on zmod hotfix3. If you use xrec to make a full backup after reboot there is that error again. This can be resolved by clearing market and storage data. It works fine via CWM 4or5 recovery.
Thanks from this, I'm about to order a newer card off eBay.
Sent from my x10 running TEAM.
I just got myself a new card yesterday and I just backed up using titanium, then copied everything to the new card, then do a fresh install of my rom (CM nightly).
This Info was very helpful. Thanks
Can I use a 32GB sd-card partitioned as 2x16GB?
Thanks you, this information help me alot.
krecha-one said:
Can I use a 32GB sd-card partitioned as 2x16GB?
Click to expand...
Click to collapse
There are a few guides on that. Use windows or a linux based boot cd. Make 2 partitions and they must be primary fat32 (safest). It depends on the phone really. Have not used a 32GB, allot say it works fine and some out there say no. If you need exact walkthru just google it.
aR_ChRiS said:
I just got myself a new card yesterday and I just backed up using titanium, then copied everything to the new card, then do a fresh install of my rom (CM nightly).
Click to expand...
Click to collapse
I am not very happy with my rom right now, will be changing. But that is a good Idea to reinstall the rom. I just didnt want to wipe everything for a rom Im not real happy with. I had to get a bigger card to make a backup with. The shuffling from x10 to desktop was really bothersome.
can the
can the x10 go upto 32gb?
This CWM script will reodex any custom ROM.
With BOOTCLASSPATH edit in dexo.sh it can work on any ROM and phone.
Reodexing gives some people perceivable speed up. And it frees data partition from system dalvik cache. So dalvik-cache rebuild is also accelerated.
I ran it with stock kernel (root injected). And had problems with running it on any custom kernel.
http://galaxytree.net/bravomail/universalOdex.zip
Also a good example of output from shell script into CWM console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great to see new tweaks. For me, flashing this mod went well, but it put me in an endless boot loop. I'm using a Cappy with a Jelly Bean custom rom. I know it's supposed to be "universal", but maybe some ROMs are not compatible. Any suggestions? Hope I can get it to work.
Using the android sdk you will want to try DDMS.bat and see what spew you get while the phone boot loops.
Sounds similar to what I used for all my roms.
Here are some tips I've picked up along my dev experience:
1. Make sure you have at least 50+ mb space free in /system. Else it may not complete and your /system/app and /system/framework folders may not work properly, thus causing many android core processes to force close and rendering your device unusable. If this happens, wipe, reinstall the rom, and delete more things using Root Explorer from /system. Such as unnecessary ringtones/notification sounds in /system/media and unnecessary system apps like *WallpaperChoosers.apk, stock launchers if you aren't using them, and other stuff you don't need. If you aren't sure what it is, don't delete it because it might be important for the use of your phone.
2. Also, it doesn't work on some roms, I'm not exactly sure why. But make sure you read the script's logs to ensure there are no errors. If you are getting mounting errors, make sure your phones /system partition is mounted as r/w (root explorer can do this). If it still doesn't work, try rebooting into recovery and mounting /system in mounts and storage and then try running the script.
3. Just because your phone is now odexed doesn't mean its gonna be a ton faster. In my experience, I found it to be a slight improvement from the original. In most cases it was unnoticable, so don't expect too much.
Cheers!
Sent from my SGH-I897 using xda app-developers app
Holy cow amigo. You started a bunch of threads. A little credit to original author would have been nice if you took the work and revamped it. All credit cause you didn't.
Sharing is caring. But I suggest you put where you got the script, etc, as well as the original author.
edit. upon further review, i see that you did change some things, mainly removing the original header (which is absolutely lame) and made it work with CWM. Also, you set a static BOOTCLASSPATH - which defeats the purpose of this script!!
Let me check my pms and emails. Someone contacted me a long time ago asking me review to their changes. Maybe it was you lol.
Sent from my EVO using Tapatalk 2
When installing apps the storage manager is not registering the correct size to start off with. For instance a 1.5gb app is showing as total size of maybe 59mb. Under data for the apps it shows maybe 200kb.
Now the worse part is when uninstslling apps it does not race the data for the app. In order to remove the data and get my space back I have to boot into recovery and wipe cache.
Tried removing external SD card and trying it again and it's th deer same issue.
Also when attempting to move data to SD card it doesn't seem to really move anything but takes at least 30 seconds to do it and still requires the SD in the 0hone to run the app
Does anybody know what's up here and willing to tell me?
Thanks maybe.
Yes I'm about to smash this **** ING thing.
Nickvanexel said:
Yes I'm about to smash this **** ING thing.
Click to expand...
Click to collapse
Try Odining the stock tar from www.sammobile.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Nickvanexel said:
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Click to expand...
Click to collapse
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
bilgerryan said:
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
Click to expand...
Click to collapse
So that means at this point you wouldn't really need to wipe before installing wicked rom anymore?
Also decided against any over clocking now, changed to performance governors and things are working great now, especially games. No hitching, we're I was getting 10fps or less I cod strike team it's now 30.. so if I install a rom it will be wicked, especially the function on it "fix external SD write" fixes my storage management issues than that alone would be great and the debloat and performance tweaks would be a great bonus.
Thanks.