Related
Been using vegan 5.1 for a month now and its been great. Now the browser and market just closes at random. Not FC but just closes. Reboot doesn't help but turn of then wait a min then on does. I reinstalled and with supplement and without several times. Same thing.
sometimes it can go hours and sometimes its min when it starts.
Please help me or I wont have much hair left!
Thanks guys
It seems to happen more after using market. not sure though
clear cache in cwm first
thebadfrog said:
clear cache in cwm first
Click to expand...
Click to collapse
Dalvik cache? If so I just did and I will report back
Did it start happening after the supplement 5.1.1? A few users rebooted reboot issues especially after using Flash in the browser. I haven't been able to replicate it, but I also wipe user data as a rule between mods and updates.
roebeet said:
Did it start happening after the supplement 5.1.1? A few users rebooted reboot issues especially after using Flash in the browser. I haven't been able to replicate it, but I also wipe user data as a rule between mods and updates.
Click to expand...
Click to collapse
before I tried the supplement. I have min stuff on the tab and use it for web browsing. but I did install a few apps that I could share folders off my pc.
it seems to be doing it after I use market at some point. i done the cache clear as above and it worked fine for 2 hours, then I opened up market and looked around. with in 2 min the screen went blank and i was to the lock screen. other times it goes to the home screen.
I done a shut down, restart and havent been on market and its been up for a hour.
I'm running the supplement at this time. only thing downloaded was quadrant and kindle.
first time I done the quadrant test also, it was 2152 or close. not sure what it should be if that matters.
thanks for your help.
this still happens in all roms I use. i can figure out whats up.
Jack Daddy said:
this still happens in all roms I use. i can figure out whats up.
Click to expand...
Click to collapse
Doesn't make sense it would only happen with the same 2 apps & on different roms.
Have you tried browsers other than the stock browser & does it happen with those? What version of Market is currently installed, an older version or the nesest (3.0.27)?
aabbondanza said:
Doesn't make sense it would only happen with the same 2 apps & on different roms.
Have you tried browsers other than the stock browser & does it happen with those? What version of Market is currently installed, an older version or the nesest (3.0.27)?
Click to expand...
Click to collapse
happens with all of the browsers and ever verson of market tried. it does happen less if I never open up market.
I'm using cm7 right now and lately it has been random rebooting on its self. not everyday but it does it.
Jack Daddy said:
happens with all of the browsers and ever verson of market tried. it does happen less if I never open up market.
I'm using cm7 right now and lately it has been random rebooting on its self. not everyday but it does it.
Click to expand...
Click to collapse
After switching roms you are doing data/factory reset, wipe cache & wipe dalvik aren't you?. Have you tried doing Fix permissions?
aabbondanza said:
After switching roms you are doing data/factory reset, wipe cache & wipe dalvik aren't you?. Have you tried doing Fix permissions?
Click to expand...
Click to collapse
yes, but have not tried doing fix permissions. i will try that, thanks
what should be mounted and unmounted? checking everything
thanks
Jack Daddy said:
what should be mounted and unmounted? checking everything
thanks
Click to expand...
Click to collapse
Are you talking in CWM, Mounts & Storage?
Shouldn't have to do anything there. All that should be automatically mounted. you wiud know if one of those wasn't. ..system would come up.../data is where installed apps are, /sdcard is where you store stuff, /system is where your rom is, /cache is by the system
If you use cpumaster,setcpu or similar, try removing.I found setcpu to be responsible for crashing some apps and sleep of death on my tab and was only overclocked to 1.2Ghz.I now overclock by editing script included in rom and no more problems.
Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
duble08 said:
Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
Click to expand...
Click to collapse
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
k2buckley said:
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
Click to expand...
Click to collapse
no problem! this community has helped me TONS in the past, even though i haven't said anything about it (due to not being able to post in developer threads yet). I reflashed and wiped my phone about 4-5 times before realizing that the cache had to be cleaned AFTER the install and first boot of the new rom, and all the dev's kept stating it was from not wiping prior to flashing, which i did every time. Hopefully this will save some people time and headaches and i'm sure the dev's will soon find a fix to this, as they seem to work very fast at finding bugs and cleaning em up.
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Welcome to xda.
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
newkidd said:
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
Click to expand...
Click to collapse
that would make a lot of sense as well - if that's the case, maybe people should let google market crash the cache before they clear it out again? that's what i did when i got it working... it was one of those things where i just watched and wondered, "is it going to do it all this time?", and of course when it didn't, that's when i discovered re-clearing the cache again in recovery fixes it. I noticed that by clearing the application cache (settings/applications/manage programs/market/clear cache) the problem still persists, and the only way to get google apps to install again is by clearing cache in recovery, which made me think it was an installation/boot thing. but i'm still learning, like many of us here
thanks for the input!
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
this is an issue i noticed as well - i had to re-add my apps manually after it only added 24 of the 120 i had going. but hey, beggers can't be choosers, and i'm just mostly happy that i got a new rom going with everything functioning properly within 2 weeks of the phones release!
If anyone knows how to re-start the app sync succesfully without space errors, that might be good info to include in this post
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
-viperboy- said:
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
Click to expand...
Click to collapse
Recovery. Downloading another app doesn't rebuild the cache either. Now it's gotten to the point where no ROM will restore any of my apps at all, it basically thinks I've never downloaded anything. So now I've gotta try and remember the 130 or so apps I had installed.
Not complaining, just an observation. One of the caveats of rooting a new device
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
empiire said:
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
Click to expand...
Click to collapse
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
You can also go into terminal emulator and delete the Download.apk files in the cache.
You'd think Google would be a little smarter at this. All the market would need to do is download fewer apps at a time, as the files are cleared once the installation is complete.
Sent from my PG86100 using XDA App
I feel a s0be market fix coming on. Although I have not seen the issue, you could pwn the cache and symlink it out of /data and into /system. A genious linux guy, seriously, genious, made this hack back on the hero, fixed market download errors EVERY time.
See this post:http://forum.xda-developers.com/showpost.php?p=11055157&postcount=4650
If you like it, go find s0be and thank him
duble08 said:
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
Click to expand...
Click to collapse
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That won't make any difference if there is no room to actually store the downloads. Downloads from the Market go into /cache while downloading and then move to /data/app or /system/app, depending on the app. Hence why clearing cache fixes it.
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
duble08 said:
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
Click to expand...
Click to collapse
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
laie1472 said:
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
Click to expand...
Click to collapse
I tried something similar, but not exactly like you said earlier. I set my accounts to sync, but immediately went into the market while it was syncing, and cancelled everything. This would've still left the user picking each app to re-download one by one, because I believe there's no way to restart the app sync. I ended up buying titanium, and used that to put all my apps back on - its much less of a headache.
This is a more detailed edited version of how to install the Resurrection ROM by westcrip...
as have seen too many users that seem to be skipping parts or confused of the installation.
This is also for users like myself, who just started on this site and can't post on Development side to find their answers.
BACKUP your apps of course...but DO NOT backup system data.Repeat!! DO NOT BACKUP SYSTEM DATA. Restoring system data can give you some problems because if you don't know what you're doing, can accidentally replace something from the fixes that screws things up!
-----------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------
PART-1
Rom Installation (you MUST follow these steps! )
**Go to recovery mode( Vol UP + Power+ Home and hold until the Samsung Galaxy screen comes on)
1- Wipe data / Factory reset then (can Wipe cache partition or go straight to)
Install ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip
*if you did not Wipe cache, can go straight to install from cache...
but if you Wiped cache then you go to install from external SD card and install 1.0_CWM.zip (this will be touch version)...
then choose - install zip from sdcard. - choose zip from sdcard. Scroll down to Download folder and select ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip.
Please wait a moment.
2-Install gapps_for_remix_v1.1.zip
3-Install gapps_fixer.zip then go back and go to Advanced.
4-Wipe dalvik cache (required)
and Fix permissions and go back to
5-Reboot system
(at this stage it may take a while for first bootup, because we have wiped cache. It needs to rebuild it, so don`t panic.
It may take a while *average around 3-5min before getting to Installing applications screen)
At this stage, boot to system and configure the phone (change language settings, etc).
When finished, again reboot into recovery and follow PART-2
PART-2 (required)
This part it's mandatory here are contained the language, theme, AOSP apps and the T9 dialer if you want it...
or use default. ONLY install one of these:
*note: you're in regular CWM using up and down volue + power button to enter.
If you want the touch - reinstall it like before.
1.- Install the SMSfixupdate-afterboot+T9 Dialler.zip
or
SMSfixupdate-afterboot+default remix dialler.zip
go back
2.- Reboot into system
After finishing the boot it's highly probably that you receive a force close from android phone.
It's normal and it's the only FC that you should get.
Enjoy!
**There is a RAM Manager Fix (When you open the Task Manager app, there's a section called RAM and a button to Clear Memory.
The fix enables that button again... for those not working).
Here is a mirror link for this and other files: RAM Manager Fix and others
PART-3 (optional)
*This can apply to many other files you want to flash.
If you want to install Siyah kernel:
Place Siyah-v3.0rc4-CWM.zip (or whichever version you're using) in the root of internal SDcard memory ("download" folder) and go to recovery mode (Vol Up + Power + Home).
Go to Install zip from SDCard... and select it.
Yes and install... Fix permissions... Reboot.
**battery issues with Siyah?
go to recovery
wipe dalvik
go to "kernel specific options" to reset them or other performance tweaks.
reset kernal
fix permission
reboot
**No more video player?
Get the VideoPlayer.apk file (*have to do a search for it now until I find another working link to it)
and copy it to system/app using something like Root Explorer
Reboot
Hope this helps. I'll edit this when I have time (usually busy with other projects).
*Version 1.2 is out now Check it here.
Good job
Tho make sure you spend a bit of time regularly checking the thread (depending on how much action the thread gets, obviously). Once you make threads like these people invariably ask questions & it's best if the person who detailed the method answers most of them.
Thank you sir.
I will give as much time as I can on this, when questions come up... and I'll be sure to keep up with bugs going on on original thread... though they will be updating this ROM soon to 4.0.4.
When that happens, guess will have to update this lol.
(oh no, what have I gotten myself into )
Language problem
Hello!
Thanks for the thread, really useful for noobs needing help to fix some problems.
I am a noob... and I have a problem.
Everything is working fine, battery is ok, no fc... but language seems to be messed up, I get my language (spanish) in almost all settings and menus, but dialer is invariably in english. Some contacts dialogs show this behaviour too.
Thank you very much in advance!
Thanx a lot, really useful...cant wait for 1.2
SMSafter-reboot is the only fix i needed to fix my dialer fcs issue, after a dalvik cache clean and permission fixing. That was the only way, if some1 has same issue.
Sent from my GT-I9100 using XDA
Hi Miguel. The ROM is mostly for English and some language settings are off here and there. Mine too shows Chinese characters in some parts. I think this has to do with where the phone is originally from.
Version 1.2 will be out soon (based on 4.0.4) and should have more bugs fixed. I will see if there's anything can be done to help you with Spanish settings.
*glad it's helpful for you guys.
Thanks for a good simple guide.... it is getting pretty difficult to find answers with so many posts in the main thread.
Will you be making a similar step by step guide for ver 1.2 that should be out soon?
If it is needed I will. Will have to wait for it to come out and see if instructions changed. The process will be easier (after what westcrip said), not needing to add gapps fix, etc now I think.
Anyways, if I think needs more detail for newer users, I'll add a new thread for it and post a link here to it too.
Which dialler
I'm a true noob and I'm rooted with CWM installed and I'm giving serious consideration to this rom. My only question at this point is what are the differences btw the 2 diallers and do most folks prefer one over the other?
Hi tlmacson. It's a very good fast and smooth rom with good support. 1 dialer gives you T9 abilities... which means when you start dialing some number, it shows you contact(s) that much those numbers.
But there are some bugs in it not working for some, so recommended to install the default one and add some other app that does the same, or install T9 on after the default.
PS
If you want to give this ROM a try... the new 1.2 version will be out any moment which should have easier installation with hopefully less bugs ^^
I have been using it for a few weeks now. It has run really smooth, the only bugs are very small and do not effect the use of it daily.
I had a few problems with the dialler, so I installed exDialler. I actually prefer it, it has t9 searching and can be skinned to look like ics dialler.
I will definatly give ver 1.2 of the rom a try too.
Yes, that's the 3rd party app people like for T9 use: exDialer
It also allows you to give it black theme.
HELP!
Cyber i'm wondering if you did test the 1.2 PRO resurrection I want to upgrade to it but i don't know if it is a FULL WIPE or not because westscript didn't mention it also there are no GAPPS and FIXER within the thread can you please confirm for me this?
I think that I may just do that since I'm not having any real issues with the leaked "stock" XXLPQ. I appreciate your advice and dialer explanation.
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Test
Thank you cyberboob.
I will try 1.2 and see how it goes, anyway I will install exDialer to fix my languages "problems" (it is not a dealbreaker but is disturbing seeing some dalogues in other language).
According to 1.2 changelog this version is promising.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
thank you. i'll try without the wipes
Sorry.. a full wipe is needed again (or more bugs will be present).
Follow these steps:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*Also westcrip will post a new fix update for some new bugs reported by some users.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
I know I'm showing my "noobness" but I thought that the kernel was part of the ROM; so how do I install the kernel after the ROM?
Same way you installed the main ROM.. go into recovery mode and select the folder you placed it in (usually internal sd card "download" folder) and flash it "yes". Fix permissions if want and reboot. Same with anything else you need to flash/CWM after/before.
[Resolved] Play Store & Mobile Network force closing, can't send/receive texts/calls
Hi there!
I installed the Resurrection Remix ICS AOKP ROM v.1.8.1 on my unlocked Galaxy S II i9100 a couple of days ago after factory resetting it, wiping the SD card, cache, etc.; completely getting rid of everything from the previous Resurrection Remix ICS ROM I had on there before.
Spent a lot of time customizing it over the past couple of days and not had any problems. I have a UK GiffGaff SIM which runs on the 02 network. There is a GiffGaff app on the Play Store that copies the correct information into your clipboard so that you can go through the steps of creating an APN easy as pie. However, whenever I go to Settings/More/Mobile networks a dialog box immediately pops up stating "Unfortunately, Settings has stopped." and puts me back to my app drawer. I spent a while trying to fix it, then loaded up the Play Store to look for APN apps, but whenever I try to download an app it comes up with the same message above with "Settings" replaced with "Google Play Store".
I've literally spent hours and hours getting extremely frustrated and would be very appreciative of some help as I currently cannot send or receive texts or calls, cannot use the internet without Wi-Fi and cannot download any apps.
Things on the top of my head that I've tried are deleting the vending.apk (Play Store) in the system/app directory and copying another version of the store over, clearing caches of numerous apps, clearing Dalvik cache, wiping cache partition in CWM, restored some apps and settings from my Titanium Backup backup (which replaced some of my customization that I worked hours on ) and searched for ages for the APKs of some APN apps. I even wiped data/factory reset the phone a few minutes ago, but I still can't access Mobile networks to input the APN and now Google Play Store isn't even in my damn app list anymore!!
Can someone help please?
Edit: Managed to get the Play Store back, downloaded an APN app successfully, opened it and it force closes!
RESOLVED: If anyone else has similar problems, just download the ROM that's installed onto your phone, install it again, boot into CWM, wipe cache, wipe Dalvik cache, fix permissions and reboot! Thanks JJEgan and Sun90
Clean re flash its the rom at fault .
jje
JJEgan said:
Clean re flash its the rom at fault .
jje
Click to expand...
Click to collapse
Thanks for the reply! Do you mean downloading the ROM onto the phone, wiping all data and installing the ROM again?
MC0NRAD8 said:
Thanks for the reply! Do you mean downloading the ROM onto the phone, wiping all data and installing the ROM again?
Click to expand...
Click to collapse
simply reflash the rom over the exsisting one then wipe cache and dalvik do fix permissions and reboot everything will wrk fine afterwards
PS: do not wipe any data
Sun90 said:
simply reflash the rom over the exsisting one then wipe cache and dalvik do fix permissions and reboot everything will wrk fine afterwards
PS: do not wipe any data
Click to expand...
Click to collapse
Ohhhh myyyyyyyyy goddddddddd. I love you. Haha, downloaded and installed the ROM, now everything works completely fine!! Thank you so much I'll remember that tip for the future
By the way, are some of the textures and backgrounds in this ROM supposed to be.. messed up? Like, some menus such as Settings have completely dark checkered backgrounds which look ugly o_o And when I pull down the notification bar, there are a lot of blue diagonal textures which again, look ugly.
Is this just me or is it the ROM? If it's the ROM, are these textures being worked on?
Thanks again
MC0NRAD8 said:
Ohhhh myyyyyyyyy goddddddddd. I love you. Haha, downloaded and installed the ROM, now everything works completely fine!! Thank you so much I'll remember that tip for the future
By the way, are some of the textures and backgrounds in this ROM supposed to be.. messed up? Like, some menus such as Settings have completely dark checkered backgrounds which look ugly o_o And when I pull down the notification bar, there are a lot of blue diagonal textures which again, look ugly.
Is this just me or is it the ROM? If it's the ROM, are these textures being worked on?
Thanks again
Click to expand...
Click to collapse
u can check the link below for some good cwm flashable mods for system background as well as phone dialer background choose the one u like dwnld the same and flash it from recovery and enjoy
http://forum.xda-developers.com/showpost.php?p=25666954&postcount=28585
PS:- please do not try the tablet mode ui in the above link since it has got issues still
---------- Post added at 05:48 PM ---------- Previous post was at 05:03 PM ----------
hey if all ur issues r resolved please edit ur orginal post by putting issues resolved and close the thread this is as per XDA rules
Sun90 said:
u can check the link below for some good cwm flashable mods for system background as well as phone dialer background choose the one u like dwnld the same and flash it from recovery and enjoy
http://forum.xda-developers.com/showpost.php?p=25666954&postcount=28585
PS:- please do not try the tablet mode ui in the above link since it has got issues still
Click to expand...
Click to collapse
Wow, I had no idea we could do this! Thanks a lot, haha, it all looks awesome now! One last thing if that's okay How can I customize what I see after pulling the notification bar down? I done a little Googling just now but kept finding apps that just customize the actual bar and not the bad textures after pulling it down.
Are there mods for that too?
Edit: Ah, will do! Thanks for informing me
2nd Edit: How do I close the thread?
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre