so i had no problems going from nightly to nightly up until i did the mtd partitions..
ever since then i flash the newest nightly then the mtd boot zip then after reboot im still on nightly #7..it did the same thing with the newest froyo radio until i flashed thru flashboot..then it stuck. is this something to do with my cache mtd partition not being large enough its 1.5mb
Anybody
Sent from my T-Mobile myTouch 3G Slide using XDA App
droopypillow said:
Anybody
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I had a similar issue when I flashed the new radio. Well, not entirely similar, but yes it MAY have something to do with your cache. It shouldn't, but it might. Flashing new nightlies worked fine for me with MTD. Are you sure you're doing it in the right order? ROM, gapps/custom kernel (if any), THEN boot patcher?
When I flashed the newest radio, somehow it broke my /data partition, like it erased the file system tables or something rather, because the data was still taking up space, but no files were listed and /data/app was completely gone. I figured it must have had something to do with my 1.5 mb cache, since that's where the radio is supposed to copy to. It must've failed to write to /cache so it wrote to /data and overwrote something important, who knows. You MIGHT want to raise your cache to 20-50mb. Right now I have a 140mb /system and a 50 mb /cache.
Thanx..I actually went back and cleared the mtd partitions installed build 9 and reinstalled mtd with 10mb cache and it worked fine..
Sent from my T-Mobile myTouch 3G Slide using XDA App
droopypillow said:
Thanx..I actually went back and cleared the mtd partitions installed build 9 and reinstalled mtd with 10mb cache and it worked fine..
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Yeah, sometimes a small cache screws up stuff.
Sent from my T-Mobile myTouch 3G Slide
Related
Hello community. Once again asking a question
My phone takes about 2 minutes to load all the apps on the home-screen. It's really tiring and annoying. I seriously mean like 2 minutes, literarily.
I did apps2sd, and followed the guide, and it still takes forever.
How can I fix this??
Mytouch slide
cyanogen 6.1.0
android version 2.2.1
xologist said:
Hello community. Once again asking a question
My phone takes about 2 minutes to load all the apps on the home-screen. It's really tiring and annoying. I seriously mean like 2 minutes, literarily.
I did apps2sd, and followed the guide, and it still takes forever.
How can I fix this??
Mytouch slide
cyanogen 6.1.0
android version 2.2.1
Click to expand...
Click to collapse
Try clearing your dalvik cache in recovery? See if that works
MusicMan374 said:
Try clearing your dalvik cache in recovery? See if that works
Click to expand...
Click to collapse
How do I do that again?
Can you tell me please
Sent from my T-Mobile myTouch 3G Slide using XDA App
xologist said:
Can you tell me please
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Just get into Clockwork recovery, and there will be an option that says "Wipe Cache Partition".
Lemme know if that works :3
Sent from my T-Mobile myTouch 3G Slide using XDA App
supermario12312 said:
Just get into Clockwork recovery, and there will be an option that says "Wipe Cache Partition".
Lemme know if that works :3
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Did that just now. Still taking forever to load home icons.. like 4 minutes no lie
xologist said:
Did that just now. Still taking forever to load home icons.. like 4 minutes no lie
Click to expand...
Click to collapse
What launcher are you using?
are u using tha a2ext method from acejoker? Or the built in froyo a2sd? Because the a2xt method can really slow down boot, which is why I stopped using a2ext and instead installed all apps on main memory (main memory has custom mtd partitions for larger data partition)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
supermario12312 said:
What launcher are you using?
Click to expand...
Click to collapse
ADW Launcher
Version 1.3.3 system
agentg1001 said:
are u using tha a2ext method from acejoker? Or the built in froyo a2sd? Because the a2xt method can really slow down boot, which is why I stopped using a2ext and instead installed all apps on main memory (main memory has custom mtd partitions for larger data partition)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
Im using the one from Acejoker
this url http://forum.xda-developers.com/showthread.php?t=791795
xologist said:
ADW Launcher
Version 1.3.3 system
Im using the one from Acejoker
this url http://forum.xda-developers.com/showthread.php?t=791795
Click to expand...
Click to collapse
Yea like i said you can't really fix it the acejoker a2ext is just slow, which is why i removed it
agentg1001 said:
Yea like i said you can't really fix it the acejoker a2ext is just slow, which is why i removed it
Click to expand...
Click to collapse
You can apply s-off and repartition your phone's internal memory as well, to get more /data space, without speed issues.
MusicMan374 said:
You can apply s-off and repartition your phone's internal memory as well, to get more /data space, without speed issues.
Click to expand...
Click to collapse
That umm sounds complicated.. lol
i'd probably get the S-off installed lol, but then the repartition.. lol that'd be a different problem
idk, might just stick to 4minute start
xologist said:
That umm sounds complicated.. lol
i'd probably get the S-off installed lol, but then the repartition.. lol that'd be a different problem
idk, might just stick to 4minute start
Click to expand...
Click to collapse
The repartitioning isn't hard, there's a simple guide here, it literally is just making a text file and flashing stuff in the right order. http://forum.xda-developers.com/showthread.php?t=893706
to clear dalvick cache and not just cache do these steps
go to your recovery
then go to advanced
then clear dalvick cache.
The first boot after wiping will be a LONG time since the cache has to be recreated but that should fix any slow downs or FC's
UberMario said:
to clear dalvick cache and not just cache do these steps
go to your recovery
then go to advanced
then clear dalvick cache.
The first boot after wiping will be a LONG time since the cache has to be recreated but that should fix any slow downs or FC's
Click to expand...
Click to collapse
Thanks, I did that quite a lot. The problem persisted.
I got rid of A2EXT
::CLOSE::
Yeah, the reason apps2ext was slow for you is because you're using a slow SD card.
Sent from my T-Mobile myTouch 3G Slide using XDA App
How do I remove "a2ext" from my phone?
I wanted it for more space.. but it really slows down the phone too much, and now with CM7, It's not gonna work anyways.
How do I remove "a2ext" from my phone?
and remove the partitions I made for it
BUMPPPP BUMPP
Anyone? Come on..
Sent from my T-Mobile myTouch 3G Slide using XDA App
There is a thread in the development section about setting up a2ext so there might be some info in there. I would think it would be a similar process but no idea. If however its done and you have to format your sd card, MAKE SURE TO BACK IT UP. Formatting will delete everything on your sd card
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yea, thanks. I already got everything backed up.
I saw the thread, but I dont want to apply the wrong command and then my phone wont turn on or something.
I would like someone to tell me how to do it.
xologist said:
Yea, thanks. I already got everything backed up.
I saw the thread, but I dont want to apply the wrong command and then my phone wont turn on or something.
I would like someone to tell me how to do it.
Click to expand...
Click to collapse
Back when I had a htc hero, I asked the same question and so did others.. If I recall a dev told me to pretend I'm setting my SD card for A2SD but to put 0 for swap size and 0 for the memory reserved as well try that, that's what I did and took it off, then reformat it in the PC as well to be in the safe side if you want.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok i set them both to 0 (zero)
Now i get continuous cyanogen loop. I deleted catche, and Dalvik cache.
Should I "Wipe data/factory reset" ?
then apply cyanogen 6.1.1 again
or does the "Wipe data/factory reset" root?
xologist said:
Ok i set them both to 0 (zero)
Now i get continuous cyanogen loop. I deleted catche, and Dalvik cache.
Should I "Wipe data/factory reset" ?
then apply cyanogen 6.1.1 again
or does the "Wipe data/factory reset" root?
Click to expand...
Click to collapse
Yeah, I'd suggest you do a full wipe and flash a ROM of your choice, I'd recommend the latest CM7 nighty! It is by far flawless to me and fast! Btw always do a full wipe when flashing ROM's as it will delete any old files that can cause issues and nope it wont lose you root
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
CaliBoyPhillip said:
Yeah, I'd suggest you do a full wipe and flash a ROM of your choice, I'd recommend the latest CM7 nighty! It is by far flawless to me and fast! Btw always do a full wipe when flashing ROM's as it will delete any old files that can cause issues and nope it wont lose you root
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
Yeah, I tried CM7
That's the main reason im getting rid of this A2EXT
it sucks.. slows down your phone wayyyy tooo muuchhh
Im gonna put CM 6.1.1
do a nand
then apply CM7
then switch back with the nand if I need to.
Hey no lie, CM7 was awesomee!!
xologist said:
Yeah, I tried CM7
That's the main reason im getting rid of this A2EXT
it sucks.. slows down your phone wayyyy tooo muuchhh
Im gonna put CM 6.1.1
do a nand
then apply CM7
then switch back with the nand if I need to.
Hey no lie, CM7 was awesomee!!
Click to expand...
Click to collapse
ahh kay kay, just wondering which CM7 did you flash? was it the cyanogen nighty release? which is found here below.
http://mirror.teamdouche.net/?device=espresso
so far to me it is beast, going to OC soon so its even faster ha!
CaliBoyPhillip said:
ahh kay kay, just wondering which CM7 did you flash? was it the cyanogen nighty release? which is found here below.
http://mirror.teamdouche.net/?device=espresso
so far to me it is beast, going to OC soon so its even faster ha!
Click to expand...
Click to collapse
I flashed the one thats on Rom Manager
whichever that is lol
It was pretty nice, had wifi connection issue, but now that I started my phone fresh, it should all work out nice!
Had wayy too much garbage.
Only thing im waiting for now is the market to stop saying "starting download" forever and actually restore some of my apps lol
i was trying to flash build 9.i did the same steps as usual including the mtd boot.zip
and now im stuck in a bootloop..ive tried to restore my back ups and re flash the rom and it never gets past the cyanogen mod 7 screen...what do i need to do
Do a nandroid restore.
If that doesn't work, try doing a
"wipe/factory reset" from recovey menu.
Then
Apply cyanogen mod .zip again
Sent from my T-Mobile myTouch 3G Slide using XDA App
xologist said:
Do a nandroid restore.
If that doesn't work, try doing a
"wipe/factory reset" from recovey menu.
Then
Apply cyanogen mod .zip again
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
i did all of that prior to posting.. i ended up erasing the mtd partitions and starting from scratch with everything
Try it without the mtd boot.zip stuff?
I know that kind of defeats the purpose, but well, who knows. D:
So build 7, and 8 and all those worked, right?
Yeah everything worked up until build 9..but I ended up restoring a very old backup and it worked..then reflashed build 9 and mtd..
Sent from my T-Mobile myTouch 3G Slide using XDA App
The same thing happened to me, boot zip got me into a splash1 bootloop, no logcat. Wiped everything and reflashed and it worked. It happened after I flashed the new radio
Sent from my T-Mobile myTouch 3G Slide
I flashed a sense rom today and updated my prl. Afterwards I restored my nandroid of CM7, and now I can't get my data to work for anything.
Can updating your prl break data? I was coming from a Verizon prl if that matters.
Sent from my PC36100 using XDA App
michaelvibe said:
I flashed a sense rom today and updated my prl. Afterwards I restored my nandroid of CM7, and now I can't get my data to work for anything.
Can updating your prl break data? I was coming from a Verizon prl if that matters.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hmm, I would tend to think that updating your PRL wouldn't break your data, however I'm not familiar with the verizon prl hack, so I'm not sure if the procedures of updating PRL differ from normal. Did data work on the sense rom, after you updated the PRL, before you nand restored to CM? I'd hop back onto a sense rom, update profile and prl again, then see if data works while on that rom. Then try nand restoring back to CM again, and see what happens.
It worked on the sense rom. I just tried flashing back, updating again, and restoring my nandroid...same thing. I called sprint and had them update my services but that didn't fix it either. I thought the problem might have been with my flash so I wiped everything twice and flashed CM7 again. No go.
I'm perplexed.
Sent from my PC36100 using XDA App
Go into your Mobile Network data settings, and make sure all the roaming options are enabled, and that data is enabled.
Also, FWIW, format /system, /data, and /cache (Amon_RA 2.3 and ClockworkMod 3.x both have these options), then flash CM7 Nightly 19, followed by the 20110307 GApps. See if you get the same problem.
drmacinyasha said:
Go into your Mobile Network data settings, and make sure all the roaming options are enabled, and that data is enabled.
Also, FWIW, format /system, /data, and /cache (Amon_RA 2.3 and ClockworkMod 3.x both have these options), then flash CM7 Nightly 19, followed by the 20110307 GApps. See if you get the same problem.
Click to expand...
Click to collapse
International data was disabled.....I ignored that in the settings because it said international haha. Thanks now I feel like an idiot.
Sent from my PC36100 using XDA App
prl
well i would say to get a prl for your area and then see what happends you might have the wrong prl
Previously i was running stock froyo rooted.
Ive flashed the stock gingerbread (odexed) from here and all went well.
Ive noticed that it seems dalvik-cache is wiped and/or rebuilt during each reboot (i.e. i did not initiate the wipe of dalvik-cache).
I only realized this because i use link2sd app (which moves apps and data to sd-ext partition and creates the necessary symbolic links). I used link2sd to move some of my apps, dalvik-cache (the entry for each app) and libraries to sd-ext, but when i reboot the symbolic links that were in dalvik-cache are removed.
So....
this is not really a question about link2sd but rather i would like to know from anyone else running a gingerbread rom, if dalvik-cache is indeed getting wiped and/or rebuilt during each reboot (i.e. i did not initiate the wipe of dalvik-cache)?
Has anyone else noticed this behavior that dalvik-cache is wiped/rebuilt during each reboot (perhaps you noticed each reboot takes a long time)?
p.s. in case it has any bearing, i was previously using clockworkmod recovery 3.0.0.5. But to install the new radios, NV, Wimax, and PRI, i flashed Amon Ra v2.3. After I flashed the radios I went back to clockworkmod 3.0.0.5.
I noticed extremely abnormal reboots as well. Running clockwork and rooted 2.3.3 manual flash with updated radios. Guess that explains it. Never thought to put 2 and 2 together and get 5, even though I have wiped dalvik many times.
Sent from my PC36100 using XDA Premium App
Anyone else? Any recommendations?
We two cannot be the only ones with this issue.
The ROM is expecting the dalvik to still be on /data so it's not seeing you moved it. You'll need to add that to the init scripts and move the dalvik properly for it to work.
xHausx said:
The ROM is expecting the dalvik to still be on /data so it's not seeing you moved it. You'll need to add that to the init scripts and move the dalvik properly for it to work.
Click to expand...
Click to collapse
The only problem with that statement is I was using the stock rooted odex rom. Now I am using MikG, and still have the same issue, but that could be the rom.
Sent from my PC36100 using XDA Premium App
grolthok said:
The only problem with that statement is I was using the stock rooted odex rom. Now I am using MikG, and still have the same issue, but that could be the rom.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
MikG is completely different than the ROM the OP is talking about but I'm pretty sure it doesn't use the ext partition for the dalvik either. You have to use a ROM that was made to move the dalvik to an ext partition or it's not going to work.
xHausx said:
MikG is completely different than the ROM the OP is talking about but I'm pretty sure it doesn't use the ext partition for the dalvik either. You have to use a ROM that was made to move the dalvik to an ext partition or it's not going to work.
Click to expand...
Click to collapse
Right, but I said I had the issue originally from the stock odex rooted gingerbread rom. A few non- rooted evo friends also have this issue from the OTA.
Sent from my PC36100 using XDA Premium App
grolthok said:
Right, but I said I had the issue originally from the stock odex rooted gingerbread rom. A few non- rooted evo friends also have this issue from the OTA.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
yeah, that's definitely strange then. Odexed apk's dont use the dalvik cache so I'm not sure what would could be causing it.