Related
i am wondering why my app market is not working and how i would fix that. It keeps saying "the requested app cannot be found". Yet when i search i find them as soon as i click them i get that error. I am running the latest kingxrom. On his thread it says to use this script but were do put this script i tried entering it in the terminal but it just forceclosed and then i tried the console and after the reboot i got just a blackscreen so i had to reflash so im wondering were im suppose to put this script or what another way to fix my market thanks.
# mount -o rw /dev/block/mmcblk0p2 /system/sd
(enter)
# rm -rf /system/sd/*
(enter)
# rm -rf /system/data/*
(enter)
# reboot recovery
I myself also have been experiencing this issue, really annoying and don't know whats the cause.
ya i have flashed a couple other roms and im getting the same problem when i had mlign rom i didnt have this problem so i think im going to flash back to the mlign and see if it works. I searched google for 3 days and didnt come up with anything that worked man im so stumped on this problem.
I am also getting the errors. I have tried other ROMs and still get the errors.
mpfuzz2 said:
I am also getting the errors. I have tried other ROMs and still get the errors.
Click to expand...
Click to collapse
seriously dang that sucks man now i know im screwed i dont know what to do i guess im going to have to buy a new phone because i lost all my apps to plus my navi that i need lol
if anyone finds a fix please let me know
still no fix
i been having the same problem also... with mlign... tried two different hero roms and the same thing happened, put cm 4.2.2 on it an now it works... so seems to me that google has somehow blocked 1.5 versions of the market??? only thing i can think of... im gonna try a couple other different hero roms and maybe trying cm 4.0.4 and see if it still works...
crackahunky said:
i been having the same problem also... with mlign... tried two different hero roms and the same thing happened, put cm 4.2.2 on it an now it works... so seems to me that google has somehow blocked 1.5 versions of the market??? only thing i can think of... im gonna try a couple other different hero roms and maybe trying cm 4.0.4 and see if it still works...
Click to expand...
Click to collapse
ok well i have tried kings new rom sense v1.3 and the market still doesnt work so i guess ill be trying cm's 4.2.2 by the way is that rom faster then the hero's i find the hero's to be pretty dang fast
I switched to CM 4.1.11.1 and the is market working. It is the 1.6 version of course. Don't know what the 1.5 version market's issue is, and I really like the Hero ROM's.
mpfuzz2 said:
I switched to CM 4.1.11.1 and the is market working. It is the 1.6 version of course. Don't know what the 1.5 version market's issue is, and I really like the Hero ROM's.
Click to expand...
Click to collapse
ya me to man i like the hero roms a lot but i need the market so guess ill be trying out the cm rom now is it faster then hero
why arent you guys flashing 4.2.1 - it is Very fast and better than the other CMs in my opinion.
i might just try that one
Strange, but I decided to try and go back to Hero ROM again and it works fine (the market). Like nothing ever happened.
associated with login
I had this problem. I tried several different roms, completely wiped everything, reformatted sd... I even wiped and went back to stock Donut. It didn't work, until I created a new Google account. Now it works fine on any rom. I wonder if google has put a limit on how many times you can log in to the market, to stop sharing of paid apps.
carnegie0107 said:
I had this problem. I tried several different roms, completely wiped everything, reformatted sd... I even wiped and went back to stock Donut. It didn't work, until I created a new Google account. Now it works fine on any rom. I wonder if google has put a limit on how many times you can log in to the market, to stop sharing of paid apps.
Click to expand...
Click to collapse
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes
Wipe
Wipe again
Drop to terminal and rm -r
system/sd/app
system/sd/app-private
system/sd/dalvik-cache
data/app
data/app-private
data/dalvik-cache
data/data (I think)
run e2fsk on your system/sd
wipe again
And only then you should install Hero rom following all recommendations from the creator of the rom.
Also, I wouldn't wipe right after installing a rom: sometimes devs sneak a thing or two into /data which you could delete if you wipe.
Good luck.
borodin1 said:
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes.....
...Good luck.
Click to expand...
Click to collapse
Yes, I definitely completely cleaned out my phone. I completely wiped EVERYTHING, everything in data, in cache, in system... I even completely formatted my sd back to fat32, then reformatted again with ext4 and swap partitions. Then I wiped again, twice, then flashed cyan's stable. I also did the same thing (minus the total reformat of sd, just a simple delete of data) with a couple other ROMs, including kingklick. Market still didn't work. I did one wipe, flashed kingklick's latest sapphire sense port, and logged in with a NEW google account, and it worked perfectly. I'm going to try wiping and logging in with my old account, to see if it gives me the same error.
edit: Confirmed. Wiped, flashed, logged in with old account --> Market broken. Wiped again, flashed again, logged in with new account again --> Market works. I'm trying to contact Google to see what can be done.
borodin1 said:
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes
Wipe
Wipe again
Drop to terminal and rm -r
system/sd/app
system/sd/app-private
system/sd/dalvik-cache
data/app
data/app-private
data/dalvik-cache
data/data (I think)
run e2fsk on your system/sd
wipe again
And only then you should install Hero rom following all recommendations from the creator of the rom.
Also, I wouldn't wipe right after installing a rom: sometimes devs sneak a thing or two into /data which you could delete if you wipe.
Good luck.
Click to expand...
Click to collapse
i tried this over and over and over again and nothing im gonna try creating a new google account and see if that works
I ended up wiping, repartitioning my sdcard card and wiping and reinstalling my ROM and it all works (I did backup ONLY using backup for root users.) and it all works fine for me know, going on 1 1/2 days. I use the same google account.
i had apps backed up on my sd card but if repartioning the sd card worked for you then i might to do that dont want to make a new google account lol.
ok so pretty much nothing worked for me besides changing my gmail account anyway i can change my gmail account sign in back to my old one without reflashing
Hi all,
I've been trying to change the font on my Captivate with no luck tonight. I sideloaded some Vibrant FlipFont apk's from this thread
They show up fine on the font menu, I can see the font preview, but when I select the font and restart my phone as suggested, the fonts are still the default.
I'm running the stock firmware, and I'm rooted, sideload enabled, and one-click lag fixed (ext2). Any ideas on what might be holding me back?
Thanks
I had the same problem, its the lagfix(ext2) specifically that ext2 fix, Remove the lagfix and the font will change, I dont know if they've fixed that problem yet, but they are aware of it.
Thanks, Nammyczc! Removing the ext2 lagfix did fix the problem. Is there a lagfix that you've found that allows for font changes?
It seems, (from reading other ppls experience) the ext3-4 lagfixes dont have this problem. I personally haven't tried those two but from what I read ppl dont have problems changing fonts with those.
Using the Tautama ext 4 lagfix right now. Fonts work fine. Plus the ext 4 is supposed to be better somehow based on the comments in the lagfix post.
Sent from my Samsung Captivate via XDA app
I was just wanted to make sure i did this the right way to change from ext4 to rfs file formate is just disable voodo lagfix and then flash cwm and thats it.Anybody please correct me if I'm wrong .
Yep, by disabling voodoo u'll go back to rfs but imo the cwm flash after that was unnecessary.
Thanks alot i thought that was right i wanted to make sure before I flashed a new rom I need to be on rfs for the rom I'm gonna flash.
Sent from my SAMSUNG-SGH-I897 using xda premium
I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.
OwenW71 said:
I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.
Click to expand...
Click to collapse
Did you reboot?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, then checked mount in terminal. The Cognition kernel did not use Voodoo, so the 'disable-lagfix' is not going to get the job done, I think.
That is a beta kernel, from what I remember it had trouble converting back to rfs from ext4. You'll have to flash back to a "stock" firmware with either a 1 click or using a .pit along with the firmware .tar with Odin/heimdall to repartition your file system.
Yikes. Since I'm stuck on EXT4, will my TiBu data backups be any good once I'm up and running on RFS?
Doesn't matter, your backup is fine.
1. Another easy way is to download the "voodoo control app" from the market. It will let you toggle rfs / ext4 from there and reports on current file system.
If I am not mistaken, this portion of the app is free..........but it is worth buying if you do a lot of ext4 stuff.
If you are on a GB ROM from KH3 on, ext4 is kind of unecessary, since rfs makes no difference in "laggy-ness"
Cognition 5 isn't voodoo. I don't remember if you can change it on CWM. Check in CWM if there is an option to switch to rfs or disable lag fix, if not you need to use ODIN back to "stock". Doesn't matter wich leaked firmware you use.
+1
FOR COGNITION:
prbassplayer is correct
See here http://forum.xda-developers.com/showpost.php?p=16664289&postcount=2818
You have to go back to stock.
Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.
prbassplayer said:
Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.
Click to expand...
Click to collapse
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.
chappatti said:
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.
Click to expand...
Click to collapse
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...
studacris said:
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...
Click to expand...
Click to collapse
Well, I am lazy..... And first timers can be comfortable !
Also its in CWM anyways. I have paid for sound, so I have control over conversions on it. But as Studa said it isn't needed.
So I've been having a problem with my phone that I've never had before. My cache is almost always filled and I'm having issues downloading updates from Market. The file size range can be anything from 100k to 23MB and it refuses to update. Sometimes booting in CWM and clearing cache works, sometimes it doesn't. I looked around and found a cache size changing script from the I9K forums, but that also doesn't work. So my questions are:
1) Does anyone else have this issue, and if so, what did you do to fix it?
2) Are there way to actually change the cache size? Either via CWM or I think I remember something about a pit file.
3) If I can't find a solution, does anyone know if any other the custom roms have changed the size of the cache to anything larger then 25mb which is the stock Samsung limit
And if there's already a thread with the answer, please point me to it. I searched prior and everything was about dalvik cache, which is not my issue.
Here is a post by Kyuta Syuko which includes all links for the captivate cache info.
I use the init.d script and it works great (also works for others too). Did you set the permessions on the script? Look over here for an init.d cwm script package that includes the cache scrpit. Disregard the other two scripts (S98screenstate_scaling and S98system_tweak) in the zip if ur not interested in them, simply delete them from the zip before flashing. Follow the steps to be taken after flash in the link. Cheers
I actually have the init.d script but it doesn't work for me. And I'm certain Cog4 has init.d support as there are already other scripts in there that I did not put there myself.
Don't know about cog4 (froyo rom if I'm correct), but the script works great on talon/darkcore + i9k based gb roms (tested on jvq/s/t).
fuloplori said:
Don't know about cog4 (froyo rom if I'm correct), but the script works great on talon/darkcore + i9k based gb roms (tested on jvq/s/t).
Click to expand...
Click to collapse
Yes it is Froyo. And after some more tinkering with adb, I got the script to work. Had to comment out a line. I finally have a cache thats USABLE. Thanks guys.
Cool, glad u figured it out
Is anyone else having this issue? More importantly, has anyone else solved this problem? I've searched (as effectively as I can via mobile) and found a thread or two discussing it, but no one seems to have a solution.
Regardless of the ROM, it seems that a lot of apps immediately FC when I open them after restoring their data. Installing the app by itself works fine, but the moment I attempt to restore the data I get the FCs.
It's quite infuriating really, as it's preventing me from trying any MIUI ROMs because I can't get them to boot without doing a data wipe (no, I won't run a ROM without my apps' data, sorry)
Checking and unchecking the "follow all symbolic links" option hasn't worked either.
Basically, HALP!
Herp derp Captivate Tapatalk 2
So... I'm the only one with this problem?
Herp derp Captivate Tapatalk 2
I only had this problem because I was using a datafix script and didn't have the symbolic links option checked. I lost all my data because of this. Now would be a good time to check if my new backups even work...
EDIT: They work fine... Maybe try deleting all of yours and doing it again, and have symbolic links checked.
korockinout13 said:
I only had this problem because I was using a datafix script and didn't have the symbolic links option checked. I lost all my data because of this. Now would be a good time to check if my new backups even work...
EDIT: They work fine... Maybe try deleting all of yours and doing it again, and have symbolic links checked.
Click to expand...
Click to collapse
Sorry I never replied, I had a response typed out and never posted it =/
My problem seems to have disappeared after coming back to SimplyAOKP from my nandroid. I don't actually use a datafix script.
Here's what prompted me to post this:
I wanted to try out the port of Andy's MIUI v4, so I wiped all of my backups and made new ones (didn't check the symbolic links option before backup) as well as a nandroid. After flashing MIUI, I'd say about half of my apps worked fine. The rest FC'd immediately. Now that I'm back on SimplyAOKP, the backups work fine =/
After thinking about it, I realized that I usually move my larger apps to the SD, and never did that on MIUI. So in the end, the FCs mightve come from my datadata partition being full (I never checked, just figured it was the same old backup problem and nandroided back) . If the problem resurfaces, I'll post back here and hope for the best.
Herp derp Captivate Tapatalk 2