Related
Could someone with a Jelly Bean ROM, or more specifically Slim Bean on their Vibrant tell me if their voice search works as it should.
Mine listens to what I have to say, loads up the browser, but doesn't actually initiate the search?
FWIW, all other voice actions work, eg: "Send text to xyz" or "Call xyz Home" etc...
Stoked with this ROM (2.9) now that I've sorted out a lot of intricacies, but still finding a few bugs...
Thanks in advance. :cyclops:
Try installing the JB4.2 gapps instead: http://d-h.st/sPL (this patch makes gps stop working on SlimBean rom)
You can also do this manually:
Delete the /system/lib/Velvet.apk and the /system/lib/libgoogle_recognizer_jni.so.
Reboot, then install Google Search from the Play Store.
Sent from my Galaxy Nexus
eksasol said:
Try installing the JB4.2 gapps instead: http://d-h.st/sPL
You can also do this manually:
Delete the /system/lib/Velvet.apk and the /system/lib/libgoogle_recognizer_jni.so.
Reboot, then install Google Search from the Play Store.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Flashed the file and it fully broke search and also broke the clock LOL. Had to Nandroid back.
I'll try the manual method...
EDIT - I actually don't have either of those two files in /system/lib ??
Just flashed the newly released Slim Bean 3.0 and all is fixed. This makes me very happy :laugh:
The Velvet.apk is the actual Google Search app, usually in /system/app if its installed permanently in the system. The lib file is in the /system/lib folder, without it Google Search will not work. When you install Google Search app from the PlayStore, it extract the lib folder to an appropriate folder.
But anyway good that you solved the issue.
eksasol said:
But anyway good that you solved the issue.
Click to expand...
Click to collapse
Thanks!
Yep, Slim 3.0 fixed this issue, but broke my GPS which has been solid on every ROM this phone has run up to this point. Not sure what happened there?
I was thinking of trying out Paranoid, no reason not to now! :laugh:
Install this GPS patch and you're good to go. This and performing the hardware fix made my Vibrant have better signal than my Galaxy Nexus and the XPeria Play which also has GLONASS: http://forum.xda-developers.com/showpost.php?p=33844820
Sent from my Galaxy Nexus
Thanks man. I already have that patch flashed. It does make some difference, without it I now don;t even get the GPS icon come up in the notification bar. With the patch the icon comes up (with the dot flashing) but zero sats in sight/in use
I'm kind of stuck now, this ROM is perfect apart from GPS, I can Nandroid back to 2.9, it had solid GPS but a few other problems, I've also tried flashing Paranoid and CM10 and both come unglued with a status 7 error I can.t get past
I don't have any problem with it on my Vibrant and Galaxy Nexus. Can you try wiping data and cache, then format /system partition, then reflash everything.
To flash other roms you need them to have the compatible version of CWM. So flash the rom once and you will get Status 7, don't reboot but flash it again immediately and it should reboot the phone into a boot loop. Then pull battery and boot back into CWM, you will be in a new version of CWM. Flash the rom the third time and it should work.
Sent from my Galaxy Nexus
Thanks...
I can never get to the bootloop stage, just the status 7 over and over. It's a bit odd.
I've managed to get pretty much this same conversation going in 2 places now, what a spammer
wendleburger said:
Thanks...
I can never get to the bootloop stage, just the status 7 over and over. It's a bit odd.
I've managed to get pretty much this same conversation going in 2 places now, what a spammer
Click to expand...
Click to collapse
If you must, Odin back to stock, update it to CM7, then to ICS Passion rom, then to a JB rom.
Or you can just flash a kernel first, reboot recovery and flash the ROM. I would try semaphore 2.5.0v
???
Good point, that should work.
Sent from my Galaxy Nexus
eksasol said:
Good point, that should work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks guys, I'll try that when I get a chance. Later today hopefully.
samsgun357 said:
Or you can just flash a kernel first, reboot recovery and flash the ROM. I would try semaphore 2.5.0v
???
Click to expand...
Click to collapse
That did it. Kernel flashed straight in and then the ROM just punched its way straight in :cyclops:
I don't quite understand why flashing the bare kernel first should make a difference but it certainly does.
And hello GPS! Went from dead in the water to locking within 10 seconds indoors?
Safe to say I'll be sticking with this ROM unless I find something really broken in it.
Thanks Guys.
The error was because of recovery mismatch. Some people don't get the error from it, it will just flash a d bootloop. Flashing the kernel first, gives you the proper recovery version.
???
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
rosser725 said:
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
Click to expand...
Click to collapse
Just flash the Terrasilent Kernel with Odin to get CWM. That's the recommended starting point for installing CM10 anyway.
Remember to do all your backups (including and -----> **ESPECIALLY** <------ your EFS.rfs) first because when you flash the new ROM you'll want to clear your Dalvik cache and reset to factory settings, which would wipe all of the data on the device.
Once you've installed Terrasilent, press the power button and volume up at the same time to get into CWM.
I don't have my EFS.. I can't figure out how to get it back. I don't have a lock screen or a power menu.
rosser725 said:
I don't have my EFS.. I can't figure out how to get it back. I don't have a lock screen or a power menu.
Click to expand...
Click to collapse
Well, in any case, flash Terrasilent for CWM and then use that to upgrade to Jellybean.
In the future though, remember to backup your EFS before you flash a new ROM. You can't get it back once you've lost it, and faking one doesn't always work right.
F22Rapture said:
Remember to do all your backups (including and -----> **ESPECIALLY** <------ your EFS.rfs) first[...]
Click to expand...
Click to collapse
This, so much.
http://forum.xda-developers.com/showthread.php?t=1632376
It takes all of five minutes(if you have ADB set up) and I cannot recommend it highly enough.
Guys we don't even know if he has his efs so why bother flashing terrasilent? Hmm do you have a efs backup laying somewhere on your /sdcard like efs.tar? Maybe you can get your efs if you have this.
Sent from my Nexus 7 using Tapatalk HD
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
rosser725 said:
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
Click to expand...
Click to collapse
Well, if you're absolutely sure there isn't one, go ahead with Terrasilent I suppose.
Zac, since you're here I had some questions for you:
1. I noticed that in the CM9 thread you said the gapps package needs to check for the EFS folder, but the CM10 gapps post didn't mention it. Is it still necessary?
2. Do I need to clear the user data when switching between builds of the same ROM, or only between major versions (ie. CM9->CM10)?
3. I noticed that "Cell Standby" is sucking up quite a bit of battery life (latest CM10 build). Is this something we can fix (or workaround), or is the problem "upstream?"
Thanks for all the work you and bbelos (and others) have put in over the past few months. It's really great to see it all paying off so well.
rosser725 said:
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
Click to expand...
Click to collapse
Hmm you could ask for somebody to make a dummy efs with the necessary information to get CM9/CM10 flashed into your device
F22Rapture said:
Well, if you're absolutely sure there isn't one, go ahead with Terrasilent I suppose.
Zac, since you're here I had some questions for you:
1. I noticed that in the CM9 thread you said the gapps package needs to check for the EFS folder, but the CM10 gapps post didn't mention it. Is it still necessary?
2. Do I need to clear the user data when switching between builds of the same ROM, or only between major versions (ie. CM9->CM10)?
3. I noticed that "Cell Standby" is sucking up quite a bit of battery life (latest CM10 build). Is this something we can fix (or workaround), or is the problem "upstream?"
Thanks for all the work you and bbelos (and others) have put in over the past few months. It's really great to see it all paying off so well.
Click to expand...
Click to collapse
1. It's not the gapps that checks the efs folder, it's the zip installer script
2. It's not mandatory but if you experience problems, it's recommended to do so
3. As I've already said in the FAQ, it wont change anything because the device don't have any antenna or anything cell related. The battery won't even be touched.
Would anybody here be able to do that for me?
Sent from my YP-G1 using xda app-developers app
Bump
rosser725 said:
Would anybody here be able to do that for me?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
do you have a us or intl device
rosser725 said:
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
Click to expand...
Click to collapse
If you have the INTL version, you have to download Kernel r14 (Odin):
http://forum.xda-developers.com/showthread.php?t=1414565
Now, the Odin program:
http://forum.xda-developers.com/showthread.php?t=2189539
1->Shut down your mobile.
2->Start Odin 3 (for example).
3->Connect the galaxy player with USB while pressing the volume down button.
4->Now, Odin will have to say that it's connected to your mobile. Then press on PDA and charge the YP-G70-Kernel-r14.tar
5->Tick ONLY Auto Reboot and F. Reset Time.
6->Pres Start and it will flash your Kernel.
7->Start your galaxy player while pressing volume up and home button. That's all! You will be in CWM recovery!
For US galaxy player, it's pretty the same, but the kernel is here: http://forum.xda-developers.com/showthread.php?t=1445840 (Download the .tar version! If not you'll be nothing with Odin )
Ooww... If it's a YP-G1 I don't know... Sure is the same but you've to find the adient kernel...
txordi said:
Ooww... If it's a YP-G1 I don't know... Sure is the same but you've to find the adient kernel...
Click to expand...
Click to collapse
the problem isnt that he cant find the kernel. i kernel s included in the rom that you have downloaded and only needs to be extracted,
his problem now is that he lost his efs and doesnt have it anymore. you need your efs in order to flash CM10 because the updater script checks for certain files
US Model
Sent from my YP-G1 using xda app-developers app
Hi everyone. This is my first post...anyways, been playing around with a gt-i9100 and have flashed many ROMs successfully. The latest (and best) being slim saber. I THOUGHT it was soooo easy! Haha! Wrong! Recently flashed the experimental cm11. Did the customary cwm backup, wiped cacheband partition, formatted, and wiped dalvik. Installed and Booted up fine. From reading that thread I'm experiencing the same common problems. The two worst are the battery level is out of whack and cwm can't read the SD card or micro SD. Smaller problems include can't adjust screen brightness and any apps on SD get deleted after reboot. Other smaller issues also. The overall speed is great and battery life is better than 4.3 ROMs.
Now, the real problem...because cwm can't read SD, I can't go reinstall my backup, which was my plan. Unable to flash new because downloads also go to sd, which is unreadable. Performed a backup of the current rom and its going to the phone memory. Is there anyway to move my nanadroid backup or new ROM there so cwm can see it and I can flash or any other suggestions? Any help would be greatly appreciated!!!
hawaiisteve said:
Hi everyone. This is my first post...anyways, been playing around with a gt-i9100 and have flashed many ROMs successfully. The latest (and best) being slim saber. I THOUGHT it was soooo easy! Haha! Wrong! Recently flashed the experimental cm11. Did the customary cwm backup, wiped cacheband partition, formatted, and wiped dalvik. Installed and Booted up fine. From reading that thread I'm experiencing the same common problems. The two worst are the battery level is out of whack and cwm can't read the SD card or micro SD. Smaller problems include can't adjust screen brightness and any apps on SD get deleted after reboot. Other smaller issues also. The overall speed is great and battery life is better than 4.3 ROMs.
Now, the real problem...because cwm can't read SD, I can't go reinstall my backup, which was my plan. Unable to flash new because downloads also go to sd, which is unreadable. Performed a backup of the current rom and its going to the phone memory. Is there anyway to move my nanadroid backup or new ROM there so cwm can see it and I can flash or any other suggestions? Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Flash apolo 6.1 tar from Odin, then you get cwm back.
full wipe n flash stock rom to aviod ny further problems n then install your backup after rooting again
Jimsilver73 said:
Flash apolo 6.1 tar from Odin, then you get cwm back.
Click to expand...
Click to collapse
thanks, Jim! can you direct me to a link to download apolo? been searching high and low...cant seem to find it...
hawaiisteve said:
thanks, Jim! can you direct me to a link to download apolo? been searching high and low...cant seem to find it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2291756&page=314
First post ?
Not sure why you couldn't find it though, comes up straight away when I search for it?? Do you type in the search box for all forums xda?
Jimsilver73 said:
http://forum.xda-developers.com/showthread.php?t=2291756&page=314
First post ?
Not sure why you couldn't find it though, comes up straight away when I search for it?? Do you type in the search box for all forums xda?
Click to expand...
Click to collapse
Thanks again! Found it after all...I was using an ooolllllddd pc with really bad connection...everytime I clicked that link nothing happened. Went home and tried on mine and presto! It opened!
hawaiisteve said:
Thanks again! Found it after all...I was using an ooolllllddd pc with really bad connection...everytime I clicked that link nothing happened. Went home and tried on mine and presto! It opened!
Click to expand...
Click to collapse
OK, glad your sorted now. Have fun playing with new kk, think I'm gonna wait a couple of weeks till the devs iron out the teething problems ?
Jimsilver73 said:
OK, glad your sorted now. Have fun playing with new kk, think I'm gonna wait a couple of weeks till the devs iron out the teething problems ?
Click to expand...
Click to collapse
Man Jim, u gonna hate me lol. Unfortunately apolo 6.1 is a zip file, and as far as my research has gone, no way to convert it to tar for odin flash. any other suggestions? I think the only way might be to revert to stock and root again like bhavstech recommended. I'm not desperate, as it is still usable and I have another phone so I'll wait a while and hope someone can enlighten me...thanks!
hawaiisteve said:
Man Jim, u gonna hate me lol. Unfortunately apolo 6.1 is a zip file, and as far as my research has gone, no way to convert it to tar for odin flash. any other suggestions? I think the only way might be to revert to stock and root again like bhavstech recommended. I'm not desperate, as it is still usable and I have another phone so I'll wait a while and hope someone can enlighten me...thanks!
Click to expand...
Click to collapse
LOL - I forgot!! I think there is a tar file for 4.1 - use that, or use latest dori (either 8.43 or 9.43) it doesn't matter which because you will be re installing your back up which will have its own recovery img.
Hope this helps :cyclops:
Jimsilver73 said:
LOL - I forgot!! I think there is a tar file for 4.1 - use that, or use latest dori (either 8.43 or 9.43) it doesn't matter which because you will be re installing your back up which will have its own recovery img.
Hope this helps :cyclops:
Click to expand...
Click to collapse
Hey Jim I got it fixed using dori! Funny because the latest 4.4 addressed both of my major issues...stubborn me decided to try it out and I gotta say its pretty good! Stable but just a few broken apps and small issues. Gonna five it a try as a daily driver...thanks again!!!!
use odin to flash tar and then install and older rom which is functional with the sdcard. and then flash back your backups.
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
Well, you are supposed to post stuff like this in the Q&A forum, that's why you have to post 10 times. To learn the structure.
You could try to clear data for play services and the play store app and see if that works. If not, I suggest that you try to flash some other gapps package.
Maybe one of these:
http://forum.xda-developers.com/google-nexus-5/themes-apps/gapps-t2012857
Gnarfsan said:
Well, you are supposed to post stuff like this in the Q&A forum, that's why you have to post 10 times. To learn the structure.
You could try to clear data for play services and the play store app and see if that works. If not, I suggest that you try to flash some other gapps package.
Maybe one of these:
http://forum.xda-developers.com/google-nexus-5/themes-apps/gapps-t2012857
Click to expand...
Click to collapse
Opss...
Well I wasn't taking about apps update. I was talking about cm updates.
Harellevy said:
Opss...
Well I wasn't taking about apps update. I was talking about cm updates.
Click to expand...
Click to collapse
Ah, sorry. I don't know about that.
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
Welcome to the family.. Just go and find 10 other things that you are curious about and reply to those.
Kinda hard. Nothing make sense here so many advanced stuff.
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
same here, have to download the nightly through browser
the cmupdater has not been working since i started with 403. download through pc or browser
try cyandelta
Just go through the browser. What I did and no problem.
So just download the new nightly and reflash?
Do I need to wipe cache or something?
What if I want to go from nightly to stable or M, then I need to wipe?
Thanks for the help
Harellevy said:
So just download the new nightly and reflash?
Do I need to wipe cache or something?
What if I want to go from nightly to stable or M, then I need to wipe?
Thanks for the help
Click to expand...
Click to collapse
I've always wiped when updating, after a backup of course!
NIke619 said:
I've always wiped when updating, after a backup of course!
Click to expand...
Click to collapse
But then you need to download all the apps all over again no?
Harellevy said:
But then you need to download all the apps all over again no?
Click to expand...
Click to collapse
No, just flash the update zip. (That's called a dirty flash in case you didn't know)
If you use custom kernels, flashed mods or custom system apps, they might have to be reinstalled. You also need to reinstall Xposed Framework from the app if you use that.
But remember to back up your phone in recovery before you update!
Okay thanks. 3 last questions (I hope).
I got cm-11-20140410-NIGHTLY
And yesterday released cm-11-20140411-NIGHTLY
Is this an update? Or a completely new nightly? sorry for all the ignorance, I'm totally new to this and android
2. Should I use old M builds or new nightlys? Which one Is more stable
3. If I want to flash M build and I'm currently using nightly, there is a different way or something special I need to do?
If you're going from an m build to a nightly, or any other variation (stable to m, etc) then wipe data and cache. Every nightly can be flashed on top of itself. There are more specific things to be said but I'll leave it at that so you don't get yourself bootlooped.
Make sure you make a nandroid before you do anything (I.e. a backup in custom recovery) and it would be a good idea to put that on your pc. Also a good idea to have the files and setup ready to flash your phone back to factory with kdz or tot--that way if you do something boneheaded you won't be in as much of a panic. It definitely wouldn't hurt to have some experience with adb ahead of time--just in case.
If none of that makes sense I'd wait a bit before flashing (though you could go for it and probably make out fine).
VS980 - CM11 nightly
marleyinoc said:
If you're going from an m build to a nightly, or any other variation (stable to m, etc) then wipe data and cache. Every nightly can be flashed on top of itself. There are more specific things to be said but I'll leave it at that so you don't get yourself bootlooped.
Make sure you make a nandroid before you do anything (I.e. a backup in custom recovery) and it would be a good idea to put that on your pc. Also a good idea to have the files and setup ready to flash your phone back to factory with kdz or tot--that way if you do something boneheaded you won't be in as much of a panic. It definitely wouldn't hurt to have some experience with adb ahead of time--just in case.
If none of that makes sense I'd wait a bit before flashing (though you could go for it and probably make out fine).
VS980 - CM11 nightly
Click to expand...
Click to collapse
- nandroid BackUP - Check. i learned how importent and how lucky to do a nandroid backup when i flashed yesterday the cm. bricked my phone 2 times, thanks to nandroid backup didnt need to flash stock.
- stock KDZ - Check. including flashing tool and all that.
what do you prefer, nightly or M? the nightly can go rough just like that in the middle of everything?
Hi all! I just finished porting Paranoid Android Beta 5 (Oct 22, 2014) to our beloved Vibrant. My only problem is my Vibrant is my daily driver. Can any kind soul whose Vibrant is not your daily driver (or if you just like to live on the bleeding edge) please test this out for me?
ROM *EDIT: Wi-Fi not working yet. Wi-Fi working now, but took down link to wait for original dev's permission. I have permission now, but I keep getting "No SD card" error
PA Gapps
Official PA5 xda link of the Rom I ported (i9000/galaxysmtd)
Permission from the official Rom maintainer is still pending, hopefully I'll get it soon.
Thank you so much!
Edit: I suppose I should include these steps (copied from xda thread above):
Installation Instructions
Coming other ROM
1. You must be rooted!
2. You must have a custom recovery installed.
3. Wipe your device if you are not coming from PA 4.+ already.
4. Flash the ROM zip, it could appear a warning (all data will be wiped due different partition table)
5. Reflash the ROM zip, it will continue now.
6. Flash the GAPPS.
7. Reboot. (It can take up to 5 min.)
8. Enjoy
Coming from AOSPA 4.0+
NOTE: I'm not responsible of crashes due kernel changes.
1. Flash the ROM zip.
2. Reboot.
3. Wait the upgrading android dialog.
4. Enjoy!
Click to expand...
Click to collapse
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
raddatt said:
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
Click to expand...
Click to collapse
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
dzee206 said:
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
Click to expand...
Click to collapse
Omg, that worked beautifully! Thank you so much, kind sir! I've also taken down the Rom download link and will put it back up again once I have full permission. Thanks for prompting me to do it. This is my first time at porting a Rom, so I'm not fully caught up on the etiquette yet. I've asked him for permission, and thought I could put it up only for testing purposes in the meantime, and then post it fully in our development forum once I have his full permission. He has been pretty great so far with granting a few people permission on that thread, so hopefully I can become one of them soon Thanks again so much!
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card". When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
raddatt said:
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card. When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
Click to expand...
Click to collapse
Try flashing one of the custom kernels we have and see if that works, if it doesn't help solve the issues it may just be kernel related. If all else fails give this a shot http://forum.xda-developers.com/showpost.php?p=51293597&postcount=151<br /> and if that doesn't help try porting a previous version of PA and see if the SD will mount properly.
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
raddatt said:
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
Click to expand...
Click to collapse
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
dzee206 said:
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
Click to expand...
Click to collapse
Ah, yes, from the kernel, that makes sense. Yeah, I'm glad more people are switching to Twrp because I like the touchscreen too instead of hurting the physical buttons. There's also a kernel (Semaphore?) that uses touchscreen scrolling in Cwm, which is cool too. Thank you, I'd really appreciate that!
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Btw, I just tried pulling the kernel resources of the kernel used by SlimKat into PA5 rom, but I still get the No SD card error
Our SlimKat rom uses the "samsung kernel aries", which is also used by the i9000 PA rom, so I thought it would work this time, but nope.
@dzee206 - Sorry for the spamming, man, but I just wanted to clarify the SD card problem I'm having, because I'm a bit confused as to what exactly it is. So when I try to download an .apk off of an xda thread using Browser, I get the error:
"No SD Card
An SD card is required to download ...apk"
But I am able to successfully download an app from the Play Store and use it well.
When I open Gallery, I get this error:
"No Storage
No external storage available"
Sorry I'm a big noob, but is the phone saying I don't have an external card or an internal card? I've never had these problems on this phone before, and I've never used an external SD on it. Thanks.
raddatt said:
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Click to expand...
Click to collapse
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man, I really appreciate your advice and efforts. Will try a couple more things and report back.
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
raddatt said:
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
Click to expand...
Click to collapse
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
raddatt said:
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
Click to expand...
Click to collapse
It's some what true about using the same type of based ROMs when it comes to porting but pickings are slim. Myself and a bunch of other porters have been using cm as base and haven't had any issues porting different type ROMs.
Sent from my SGH-I717 using XDA Premium 4 mobile app