Related
i am currently building a rom for the samsung captivate built off 2.3.5.
The base im using is stock - deodexed/ ziped / minorly changed
this base flashes and works just fine!
what i am doing to it:
remove bloat.
- at&t apps,
- protips.apk
- remove broken swype
- remove stock email (not gmail)
- removed stock launcher
change to hacked camera.apk
remove bootsound
remove shutdown sound
change bootanimation
added user apps in data/apps
added widget picker in system/app
changed default wallpaper in framework_res.apk
changed install script
changed CSC
custom twwallpaperchooser
everything works fine through the install.
but durring the "setup" on first boot " phone setup wizard " will force close right at the step where you setup your google sign in.
BUT THATS NOT THE PROBLEM, (just the first sign of it)
the real problem is any apps installed after flashing do not show up in data/apps
any apps installed through the flash are there, but any installed after ARENT.
and no they arent on the SD card.
the apps will slowly disappear after installing one by one.
when i reboot THEY ALL DISAPPEAR!!!
it seems that the apps install to cache or memory.
as the memory gets cleared or you reboot, they get wiped away!
i have tried various things to fix this
i have rebuilt my rom MANY times.
with and without my framework res changed file
with and without my custom install script
with and without removing stock launcher
with and without changed CSC files.
with and without twwallpaperchooser
if i flash the base i was working from again, all is good.
this only seems to be an issue when i flash data/apps from the zip file. however i have used a script from a rom that successfully flashed data/apps before without this issue, so i do not think it is a permission problem....
im stuck and lost.
more specific, rewritten description i emailed to a few friends
holy hell i bet youve been busy...
me too, i finally have my rom built. for KH2 KJ1 and KJ2 !!
have it down to an easy process now. install script working!
but im having one final issue and cant find any useful info on it anywhere and its very specific
**I know KJ1 and KJ2 install any app to the SD if possible by default. any app on SD will not be affected by this issue ***until it is moved to phone
if I build my rom to install apps to data/app (through cwm flash )- any app that gets installed after (through market or sideload) will slowly disappear after some use or immediately after reboot. they also will not show up in data/app or system/app when installed ** once again not including apps on SD. and if apps on SD are moved to data/app they do not end up there. they disappear.
this leads me to beleive that they are installing to cache or memory, as the memory gets cleared or the phone reboots. they are gone!
if i build my rom without user /data/apps (and without that part of the script).
everything is fine. any app installed after shows up in data/app and is still there after reboot.
i have also used unmodified scripts with and without the package_extract ("data", "/data")
that have been known to work with the original rom they were taken from. without the issue i am seeing.
so i do not think it is a script / permission issue not allowing the system to write new data to that location. but i could be wrong.
my rom is ready for release once i can get this last part figured out. otherwise ill have to release with no user apps... any input would be greatly appreciated.
thanks again!
Click to expand...
Click to collapse
one search i came across mentioned something about possibly not being converted to rfs, but I have flashed to stock with re-partitioning ( rfs for sure ) and the rom and kernel i am building does not support it so that shouldn't be an issue.
from what other rom builders have told me this is an issue with gingerbread roms.
have apps copied to SD card and ask users to install manually.
Dude just found this post....sorry i was busy with KJ2
glad you got a tempory fix
ya you gave me the fix in the PM! LOL
TRusselo said:
ya you gave me the fix in the PM! LOL
Click to expand...
Click to collapse
you just got spanked!!
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.
Hi,
This is a unique kinda problem (not very unique actually but only faced by couple of people) on any cm10 based rom I have tried till now.
The issue is that after I properly flash the rom (yes, I have double checked and flashed roms exactly following OP's instructions in all cases), I find that pre-existing media files (pictures,music and videos) are not getting scanned at all and added to the stock gallery/music app. if I take any picture or upload any media using MTP with the rom, its added properly.
So, I have tried all suggestions (fixing permission, full wipe, delete .nomedia etc) and still no solutions. I am sure that the issue is with mediascanner and I have monitored it and found that eventhough I manually stop and start it using "Rescan Media ROOT", after runnnig for like 20-30 secs, it just says restarting again and again.
Additionally I have also found that when connecting via MTP, eventhough the SD Card and internal memory has alot of stuffs, they are not shown. So I think issue can be with the this also.
I've grown very frustated over last few days due to this and I cannot use any of the amazing cm10 roms that we have and have to go back to my old ics rom.
PLEAZZZ HELP !!!
I also encourage all others who are facing similar issue to post here which would definately help in understanding and fixing the issue.
Thanks !!!
really man? CM10 is not even beta yet. its got bugs. deal with them or use ICS. Im on ICS still due to them.
Complaining about bugs in a build that is so far from being stable, that'll cause trouble.
MotoMudder77 said:
really man? CM10 is not even beta yet. its got bugs. deal with them or use ICS. Im on ICS still due to them.
Complaining about bugs in a build that is so far from being stable, that'll cause trouble.
Click to expand...
Click to collapse
If it would be a bug in the build only, then it should have affected all who are using it, why only few are getting affected.
And yes, I know its not right to complain about still in beta cm10 releases and thats why I'm not bothering any Devs for it. I have started this thread in Q&A so that guys who are facing the issue can match the different conditions/scenarios it is happening as I know its not a coincidence that its happening on some devices and not on others.
dev997 said:
If it would be a bug in the build only, then it should have affected all who are using it, why only few are getting affected.
And yes, I know its not right to complain about still in beta cm10 releases and thats why I'm not bothering any Devs for it. I have started this thread in Q&A so that guys who are facing the issue can match the different conditions/scenarios it is happening as I know its not a coincidence that its happening on some devices and not on others.
Click to expand...
Click to collapse
Its either s/w or h/w man.
And from what I can tell its s/w. so its on them. get logs, and send them in.
Entropy has said to set screen to stay awake while charging in dev options. Then plug your phone into charger and reboot then give it about 15 min. to scan. This is to keep media scanner from eating battery, but you could try it and see if has any effect on your issue.
adfurgerson said:
Entropy has said to set screen to stay awake while charging in dev options. Then plug your phone into charger and reboot then give it about 15 min. to scan. This is to keep media scanner from eating battery, but you could try it and see if has any effect on your issue.
Click to expand...
Click to collapse
That is not at all what he asked...
122ninjas said:
That is not at all what he asked...
Click to expand...
Click to collapse
I assume that this allows for a complete scan which would help. If it doesn't help then what was lost?
http://forum.xda-developers.com/showpost.php?p=30017461&postcount=2348
MotoMudder77 said:
Its either s/w or h/w man.
And from what I can tell its s/w. so its on them. get logs, and send them in.
Click to expand...
Click to collapse
Yes, I do have commonsense and have already posted the issue in CM forum along with logcat, but no replies yet.
122ninjas said:
That is not at all what he asked...
Click to expand...
Click to collapse
Yeah , my issue is completely opposite of what most guys were facing (which is supposedly been solved in latest builds). In my case, mediascanner is not running at all to scan all media.
adfurgerson said:
I assume that this allows for a complete scan which would help. If it doesn't help then what was lost?
http://forum.xda-developers.com/showpost.php?p=30017461&postcount=2348
Click to expand...
Click to collapse
Same thing , this solution is for those whose battery is getiing hit by wakelock and cpu overload due to mediascanner.
dev997 said:
Yes, I do have commonsense and have already posted the issue in CM forum along with logcat, but no replies yet.
Yeah , my issue is completely opposite of what most guys were facing (which is supposedly been solved in latest builds). In my case, mediascanner is not running at all to scan all media.
Same thing , this solution is for those whose battery is getiing hit by wakelock and cpu overload due to mediascanner.
Click to expand...
Click to collapse
I would do a clean install of cm10, and NOT use the root media scanner app, and then follow what entropy said (keep display on while it scans).
Also, go to manage apps and clear data on DRM, Galley, and Media storage. Reboot and then play some music through your favorite file explorer. The Media Scanner will rebuild data in about 10 minutes to half an hour (try to keep screen on if you can)
(Semi quoted from 1weener)
Sent from my SGH-I777 using xda app-developers app
diabolicalangle said:
I would do a clean install of cm10, and NOT use the root media scanner app, and then follow what entropy said (keep display on while it scans).
Also, go to manage apps and clear data on DRM, Galley, and Media storage. Reboot and then play some music through your favorite file explorer. The Media Scanner will rebuild data in about 10 minutes to half an hour (try to keep screen on if you can)
(Semi quoted from 1weener)
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Just tried this as I'm having the same problem, no luck. My music player was working fine yesterday then it decided to forget where all the songs were.
Same problem here with Task's AOKP latest(04/9)
I didnt have any problem with the previous release... BUT:
What i already did:
1- Full wipe to flash the new aokp release.
Tibe restore the rescanMedia Root... didnt touch it.
Media not working
2- Flash again without full wipe. Media not working
searched for .nomedia files. No results.
3- Flash again with another full wipe plus system format.
Checked with no Apps installed, media scan not working.
Installed RescanMediaRoot... didnt work.
After that i quit and decided to sleep. All my work on it was with the phone pluged. I dont know why but after unpluged a few musics show up. Only 40 of 2000. No pics.
4-Full wipe + chache format + System format + flash the previous AOKP release. MEDIA NOT WORKING.
was working yesterday...
5- Nandroid restore to number 3.
Thats where i am now. Stuck with the problem with aparently any JB release.
PS. Any new pic shows on gallery...
RatusNatus said:
Same problem here with Task's AOKP latest(04/9)
I didnt have any problem with the previous release... BUT:
What i already did:
1- Full wipe to flash the new aokp release.
Tibe restore the rescanMedia Root... didnt touch it.
Media not working
2- Flash again without full wipe. Media not working
searched for .nomedia files. No results.
3- Flash again with another full wipe plus system format.
Checked with no Apps installed, media scan not working.
Installed RescanMediaRoot... didnt work.
After that i quit and decided to sleep. All my work on it was with the phone pluged. I dont know why but after unpluged a few musics show up. Only 40 of 2000. No pics.
4-Full wipe + chache format + System format + flash the previous AOKP release. MEDIA NOT WORKING.
was working yesterday...
5- Nandroid restore to number 3.
Thats where i am now. Stuck with the problem with aparently any JB release.
Click to expand...
Click to collapse
I'm still facing the issue with apparently any JB build till now .. right from the first one entropy released as cm10 previes build and trust me , I tried all (well almost)
Now , from your problem it seems that once with some particular way of flashing roms, we do something that causes media scan to get corrupt..
Tell me this .. before when it was working.. have u ever tried going to gallery and then settings ?? I never got that menu on any JB release...
After making too much efforts in vain to get it right , I have resorted to the alternatives :
1. Quickpic as replacement to Gallery app.. Keep the default gallery app running for camera..
2. Poweramp full version as replacement to Music.. It has a folder rescan option under setting and searches all ur music..
3. MX video player for video playback.. However I still find few codecs doesn't support audio till now.. but it is issue with all roms for all people afaik..
Let me know if you find a solution and get it working again...
I'm on AOKP for months. Never used any other rom. Never even installed to see what happens.
So, recently Task release his JB AOKP. It is 1 week older and he released 3 or 4 builds.
The first release i did not installed, The second one was released on same day and i did a full wipe to install it from AOKP ICS.
So far everything was working good.
Then came another release, the 30/08. Installed without a full wipe, just dalvik and cache, and everything was working fine.
From the build 30/08 to the build 04/09 i did bought Tibu Pro.
So i did a full wipe to install the 04/09 and the bug show up as you can see on my previous post.
The weirdest thing is full wiping + format System + format cache + install an old AOKP(30/08) and the bug are still there.
Could be that app RescanMediaRoot? Do you have it?
what do this app do to disable the scan? If we disable and uninstall what happens?
I do have setting options on gallery but when i click it nothing happens. No setting there.
Edited:
I just checked BetterBatteryStats and it looks weird. No kernel wakelocks... not even 1.
The most interesting was the Partial wakelocks:
MediaScannerService is the number one with 12min. Its running but nothing changes.
I dont like poweramp cuz the AwesomeBeats wont work with it.
RatusNatus said:
I'm on AOKP for months. Never used any other rom. Never even installed to see what happens.
So, recently Task release his JB AOKP. It is 1 week older and he released 3 or 4 builds.
The first release i did not installed, The second one was released on same day and i did a full wipe to install it from AOKP ICS.
So far everything was working good.
Then came another release, the 30/08. Installed without a full wipe, just dalvik and cache, and everything was working fine.
From the build 30/08 to the build 04/09 i did bought Tibu Pro.
So i did a full wipe to install the 04/09 and the bug show up as you can see on my previous post.
The weirdest thing is full wiping + format System + format cache + install an old AOKP(30/08) and the bug are still there.
Could be that app RescanMediaRoot? Do you have it?
what do this app do to disable the scan? If we disable and uninstall what happens?
I do have setting options on gallery but when i click it nothing happens. No setting there.
Edited:
I just checked BetterBatteryStats and it looks weird. No kernel wakelocks... not even 1.
The most interesting was the Partial wakelocks:
MediaScannerService is the number one with 12min. Its running but nothing changes.
I dont like poweramp cuz the AwesomeBeats wont work with it.
Click to expand...
Click to collapse
I don't think "rescan Media root' app has anything to do with it .. actually
in my case , I never had this working since the start and at that time I didn't even knew about this app.
I have also noticed the partial wakelocks and if you go to running apps , you will see media storage running when u start a music/gallery app , but nothing happens..
I did tried alot to figure the problem out and seek help from all dev's that I can from this one and i9100 forum , but no results.. So finally I made peace with the workaround I mentioned...
One thing you can try in ur case is full wipe + format system/cache/data and then install a ICS rom.. after reboot.. try any JB rom again....
Good luck !! :good:
dev997 said:
I don't think "rescan Media root' app has anything to do with it .. actually
in my case , I never had this working since the start and at that time I didn't even knew about this app.
I have also noticed the partial wakelocks and if you go to running apps , you will see media storage running when u start a music/gallery app , but nothing happens..
I did tried alot to figure the problem out and seek help from all dev's that I can from this one and i9100 forum , but no results.. So finally I made peace with the workaround I mentioned...
One thing you can try in ur case is full wipe + format system/cache/data and then install a ICS rom.. after reboot.. try any JB rom again....
Good luck !! :good:
Click to expand...
Click to collapse
I'l try that and repport back.
The problem with media on the external SD card I believe is directly due to the change made in the location of the external SD card card within the directory. Many apps were built for ICS and GB and so when the scan is performed, the app isn't picking up the external SD card which used to be found within the internal SD. Now if media scanner isn't finding media within the internal SD card, that is a whole different story. I have media on my internal SD card and it has worked flawlessly. If you have music on the extsd and are using poweramp you can go into setting and check the box for the extsd outside the internal SD storage and it imports fine. Oh, and I'm running the latest AOKP with the Fluxxi kernel.
beaverslayer said:
The problem with media on the external SD card I believe is directly due to the change made in the location of the external SD card card within the directory. Many apps were built for ICS and GB and so when the scan is performed, the app isn't picking up the external SD card which used to be found within the internal SD. Now if media scanner isn't finding media within the internal SD card, that is a whole different story. I have media on my internal SD card and it has worked flawlessly. If you have music on the extsd and are using poweramp you can go into setting and check the box for the extsd outside the internal SD storage and it imports fine. Oh, and I'm running the latest AOKP with the Fluxxi kernel.
Click to expand...
Click to collapse
I do have pics on the Camera360 folder(internal SD) and it wont show on gallery.
I'll wipe everything and flash JB without the external. But i just find out something strange.
Im on recovery right now and using the file explorer of MrRobinson aroma to test it.
looks like the external its NOT on MNT folder. There are not and MNT folder on root. The external is called Sdcard and there is an emmc folder that looks empty.
Is it right? I really dont know nothing about the folder structure.
Edited:
Second time on Aromas file manager the emmc show all files now.
I belive all this means nothing.
Not all file explorers are equal. You need a root explorer to see the folders. Your music if on the internal, should be in the Music folder following the path home/sdcard/Audio/Music. Pictures on internal should be under home/sdcard/DCIM/Camera. When the external sd card is inserted it should show up in three places. At the root of the directory,you will find it as home/extSdCard, then under home/mnt/extSdCard and finally under home/storage/sdcard1. sdcard is the internal memory. I just moved photos to my extSdCard and rebooted the phone and media scanner didn't find them and setting don't exist on the gallery so you can't direct it to the new path of the extSdCard. So, I just replicated what you have been experiencing. If you move your photos to the Camera folder following the path I listed they should show up. The only reason my music works on Poweramp is because I can go to settings and check the sdcard1 folder under storage. Man I hope you don't mind all this rambling I'm doing and I hope I'm not insulting your intelligence.
No you are not. All this is new to me.
Thanks for all the info. It helped me.
Problem is gonne here.
What I did was:
1- clear cache and dalvik
2- data/factory reset
3- format system
4- format cache
5- format data
6- format internal SD
7- installed latest AOKP+ Gapps. Task's gapps don't come with Gmusic so I installed from Justin's Aroma with 1 or 2 inverted and Apex as a system app. But I did installed the normal gapps before try the Aroma.
First boot fine. I did config WiFi and gaccount slowly.
I didn't let the screen turn off.
When I first open the Gmusic everything was there.
Then I installed Titanium backup pro and did my full restore.
Tested another player , Mixzing, and was all there.
I forgot to save any pic on external since I do have Dropbox and it send it to my PC asap. So I didn't worry about pics.
Everything is working!!!!:beer:
Thank you for all your help.
Sent from my SGH-I777 using xda app-developers app
Hi guys,
First of all, thanks for the great community, good to be here
I've just got my mediapad at a bargain as 2nd hand and installed 'CleanICE 1.5 Rom (ICS 4.0.3). It has a really great response and installed with such little effort on my part so cheers h25p. I considered a couple other ROMS too, particularly the one posted by 'after_silence', http://forum.xda-developers.com/showthread.php?t=1856571 CM10 but it is said to have issues with HDMI out (which is an important feature to me) so I haven't tried that one yet.
What I'm trying to do now is boot in to Recovery (so I can install GoogleNow as per this thread http://forum.xda-developers.com/showthread.php?t=1843457) but can't seem to figure it out for this ROM.
Has anyone had success doing so with ICS? Or better yet, anyone with experience of the 'glitchy HDMI' on the CM10 Jellybean ROM (is it really bad or is it workable most of the time)?
Cheers guys!
[edit]
used auto recovery installer and got CWM on the device now (after_silence provides link to it here : http://forum.xda-developers.com/showthread.php?t=1856571)
i thought installing that would wipe everything else so to other newbies, don't be concerned. it's just installing the recovery manager and nothing else is affected
after that i went and installed the 'GoogleNowforICSInstaller_v1.1.zip' (http://forum.xda-developers.com/showthread.php?t=1843457) from sd card in CWM but sadly when it boots up there is still no google now. any ideas on where to proceed from here?
Maybe our recoveries doesn't support aroma installer. Try to flash twrp instead of cwm or put manually lib and apk/apks from zip to your system folder (same as it is located in zip), set perrmisions to apk and reboot.
Corn Flake said:
Maybe our recoveries doesn't support aroma installer. Try to flash twrp instead of cwm or put manually lib and apk/apks from zip to your system folder (same as it is located in zip), set perrmisions to apk and reboot.
Click to expand...
Click to collapse
thank you for your suggestion, it has got me one step closer (well I suppose anyway). perhaps from here it is just something to do with the gnow port just not being compatible with my rom? after I install it manually and recheck all the permissions via my file manager, whenever i go to google search it simply says "unfortunately, google search has stopped."
Try to find another moded version. I tried it on stock fw (ICS) few mounths ago and it worked.
Corn Flake said:
Try to find another moded version. I tried it on stock fw (ICS) few mounths ago and it worked.
Click to expand...
Click to collapse
Thanks, also posted a logcat dump for one of the Gnow developers and they said there was a lot of location / graphics card errors and also suggested to try another ROM. Ended up flashing JB 4.1.1 AOKP for mediapad 30.1 Final (http://forum.xda-developers.com/showthread.php?t=1876676) and enjoying GoogleNow which comes built in with it.
So far I'm really surprised at how much better it is - initially thought my battery was failing ( purchased my device 2nd hand) but the drain is really low now with this ROM. Seems a bit faster over all too. Didn't test out the HDMI function yet but hope that's not as bad as it sounds. Keeping my eyes open on the development of the 4.2.2 nightlys thread and will probably head over to that once HDMI and bluetooth is working a bit better there
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.