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.
???
Related
This is only for Telus Fascinate not Verizon Fascniate!!
I'm not good at speaking English just you know (or can somebody rewrite this for me??)
As you know, Telus Fascinate is pretty simillar to Galaxy I9000
The differences between those two are FF Camera, buttons, and some others
Okay Ill shut up and let you know how to flash MIUI/CM7 rom
Flash it at your own risk!!! I'm not responsible for anythings that you just did!! This is only for people who know how to fix your 700$ toy. Read Carefully.!! There might be alot of bugs when you are using this methoud.
Things that you need
1. speedmod-kernel-k13c-500hz.tar
2. Newest Version of MIUI Rom or Newest Version of CM7 Rom
3. cm7-galaxys-initial-kernel.tar
4. galaxy-efsbackup.zip
5. [CM7/MIUI]Telus Fascinate Platypus Kernel
Here is How! (How to flash it, when you are using stock Froyo Rom)
1. Get those files download
2. Copy all these files into your Phone (except speedmod-kernel-k13c-500hz.tar & cm7-galaxys-initial-kernel.tar files)
3. Get into download mode and than flash speedmod-kernel-k13c-500hz.tar with using odin (do not check mark on the repartition!)
4. Get into recovery mode and than install galaxys-efsbackup.zip
5. Turn off your device and than get into download mode again
6. Install cm7-galaxys-initial-kernel.tar with using odin again (do not check mark on the repartition and auto reboot!!!)
7. Unplug your USB and than get into recovery mode again
8. Choose "mounts & storage" and format system, data, and cache
9. Flash MIUI Rom or CM7 Rom
10. Reboot your device and you will see MIUI rom booting and make sure you are in service and 3g working fine. If you dont get any of that you might have to go back to stock Froyo rom and do this steps again.
11. If you have service and 3g data working, go to recovery mode again!!
14. After done flashing it install [CM7/MIUI]Telus Fascinate Platypus Kernel kernel from recovery
15. Reboot your device and you will be running MIUI Rom or CM7 Rom
Starting from Telus Fascinate Platypus Kernle Quorra-r8, there is no need of changing home key and back key
16. There is a problem between home key and back key. They are reversed. so Donload Root Explorer app
17. Run Root Explorer and than go look for /system/usr/keylayout/cypress-touchkey.kl longpress of cypress-touchkey.kl file and you will see Open in Text Editor Press it
18. you will see in your text
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 SEARCH VIRTUAL
19. Change this in to
key 139 MENU VIRTUAL
key 158 HOME VIRTUAL
key 102 BACK VIRTUAL
key 217 SEARCH VIRTUAL
20. and save it and reboot your device!!!!!
Please read this guide carefully and flash it at your own risk!!!!!
Sorry for my Bad English !!!!!
Thanks to (please dontae them!!)
The MIUI9000 team :MAMBO04, jblanc and Kenia
CyanogenMod team
zacharias.maladroit for the Kernel Build (Big thanks to you!!)
I know that you guys will understand my guide
I would be happy to test this on my device. Glad to see more roms/tutorials for the telus facinate.
Sent from my GT-I9000 using XDA App
Tested, with my modded way to install CM7 (Cant access recovery with hard key got me hard time ( I am not sharing this way to install as it's really dangerous)). Confirming that everyting is working very well on my phone. + I love this ^^. thx man.
chadouming said:
( I am not sharing this way to install as it's really dangerous)).
Click to expand...
Click to collapse
can you pm me about this part?? i want to test it too.
Which CM 7 files do you recommend using: Galaxy S or Vibrant?
What about flashing back the Telus modem?
daoom said:
Which CM 7 files do you recommend using: Galaxy S or Vibrant?
What about flashing back the Telus modem?
Click to expand...
Click to collapse
I recommend to use GALAXYS and you dont need to worry about flashing back the Telus modem cause it is fine to use jvk modem.
If you want it, i can make one for you.
harimgs said:
I recommend to use GALAXYS and you dont need to worry about flashing back the Telus modem cause it is fine to use jvk modem.
If you want it, i can make one for you.
Click to expand...
Click to collapse
I'm sure it's somewhere already, but it would be nice of you to add it
daoom said:
I'm sure it's somewhere already, but it would be nice of you to add it
Click to expand...
Click to collapse
Can you submit a telus modem file for me??
Magnetic detector isn't working. Has some issues getting to HSPA (Stays on 3g) but everything else works.
I'll rewrite this bad boy for you if you wish.
nvm, I was wrong lol
Doc_rockulus said:
Magnetic detector isn't working. Has some issues getting to HSPA (Stays on 3g) but everything else works.
I'll rewrite this bad boy for you if you wish.
Click to expand...
Click to collapse
you mean g-sensor(gravity sensor) right?
just reboot your device few times 2~3 times, its just a normal problem that everyone has
danboard said:
nvm, I was wrong lol
Click to expand...
Click to collapse
you was wrong about what?
harimgs said:
you mean g-sensor(gravity sensor) right?
just reboot your device few times 2~3 times, its just a normal problem that everyone has
Click to expand...
Click to collapse
No, I'm refering to the built in geo-magnetic sensor. Essentially the built in compass.
Edit: But the accelerometer doesn't work either, I don't particularly care about that.
Also, occasionally after being plugged in, the software seems to ignore the fact that it's charging until reboot. That one sucks because it stops charging while I'm sleeping.
Camera app occasionally won't display a preview until the phone is locked/unlocked with the app open. Widgets disappear puriodically, and sometimes it won't let me fruit ninja
Hey harimgs,
is it normal to constantly bootloop on miui? My phone will bootloop 3 or 4 times then finally boot on the 5th.
danboard said:
Hey harimgs,
is it normal to constantly bootloop on miui? My phone will bootloop 3 or 4 times then finally boot on the 5th.
Click to expand...
Click to collapse
The first few times it takes a while, I think the boot animation is too long/too short. I changed it to a different one (Through the theme manager) and it boots a lot quicker now.
Do I have to flash the CM7_TELUS-FASCINATE_platypus-kernel_20110418_16_core.zip and then the WiFi fix? Or can I just flash the Wifi fix?
Doc_rockulus said:
Do I have to flash the CM7_TELUS-FASCINATE_platypus-kernel_20110418_16_core.zip and then the WiFi fix? Or can I just flash the Wifi fix?
Click to expand...
Click to collapse
You gotta flash CM7_TELUS-FASCINATE_platypus-kernel_20110418_16_core.zip and than if your wifi works and everythung else works fine, you dont have to flash wifi fix kernel. If dont flash it
Sent from my GT-I9000 using XDA Premium App
So, say I wanted to overclock the phone, afaik there is no kernel allowing to do that, right? Supercurio's didn't allow it when I used it on my 959D to load Darky's and SimplyHoney and I just flashed CM7 using the instructions in this thread (so I'm now running Platypus kernel).
Also, is there a lagfix included with CM7?
Hey! I was using 2.3.3 miui rom with Platypus everything worked fine, I upgraded myself to the new miui rom which uses 2.3.4 and problem is when I flash the kernel if wont go past the cm7 boot logo. I have flashed it several times and reinstalled the rom still same issue.
I have already posted in the thread for it but getting no help there. I have flashed the zip through recovery launched from rom manager and it's not working, can anyone tell me why? I could really do with some signal now, it's been days!
accxnts said:
I have already posted in the thread for it but getting no help there. I have flashed the zip through recovery launched from rom manager and it's not working, can anyone tell me why? I could really do with some signal now, it's been days!
Click to expand...
Click to collapse
Just a try:
Do not use ROM Manager.
Start your phone into recovery mode (shut down and hold Volume UP + Home + Power as long as you can see the recovery menu).
Then try to flash the zip file from sd card again.
Good luck !
Just tried that and no luck there, still no signal.
****, I even tried going back to 1.11.11 or whatever, and still no signal, WHAT
I'd really like to try MIUI but when i flashed i also got no signal, which is obviously needed on a phone. I flashed back to stock rooted for now until this issue is fixed, if i were you i'd flash another Rom till it's fixed
Sorry if it's not the answer you wanted but at least you'll be able to use your phone for now
Sent from my GT-I9100 using XDA App
accxnts said:
****, I even tried going back to 1.11.11 or whatever, and still no signal, WHAT
Click to expand...
Click to collapse
Try to back to official rom.
If this doesn't work, if think that you f****d your /efs
Before do anything, backup your /efs folder.
If you lose your /efs folder, your S2 could be banned from carrier network.
what/where the hell is /efs folder?
MIUI have a new update so I'm hoping the ROMs will be out when I wake up tomorrow, if not, gonna go back to stock ROM because this is ridiculous.
accxnts said:
what/where the hell is /efs folder?
MIUI have a new update so I'm hoping the ROMs will be out when I wake up tomorrow, if not, gonna go back to stock ROM because this is ridiculous.
Click to expand...
Click to collapse
Try GingerMod in the android Original development thread. or CM7. MIUI hasnt bothered fixing that bug for the GS2 for ages.
do the following->
1. Flash a Stock gingerbread ROM.
2. Root it.
3. Install Nitrality from market.
4. open nitality->tools-> backup efs
5. Flash MIUI.
6. Install nitrality again. (Use wifi)
7. Open nirtality->tools->restore efs
8. Open Dialer and type *#06#
9. If an IMEI number is shown then Mission successful.
this worked for me when i first experienced this problem
It's okay now, after updating to 1.11.25 my signal is back
I'm having the same issue and I've posted on their forum and elsewhere.... bmarko didn't work, the nitrality efs fix didn't work because wifi wouldn't turn on, and upgrading didn't fix anything. I really have no idea what to do, I just want miui!
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
I noticed about a week ago that my GPS was not locking my location. I‛m on RootBox 4.0, and I've read that others had this issue with the ROM. I tried all the solutions listed in the thread, but nothing solved the problem. My phone shows no satellites in view or in use, even if I leave it for 20mins. Occasionally I get 1 satellite in view but my phone doesn't use it.
I would appreciate any help.
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Click to expand...
Click to collapse
I reboot every time I apply a GPS 'fix'. I'll try again though.
Tried again, still no joy.
vSTATERv said:
Tried again, still no joy.
Click to expand...
Click to collapse
Alright, so the obvious which may not be so obvious. It took me a while to figure out what was going on but now each flash I can get GPS lock after a few minutes fiddling and 10 seconds waiting for a lock. So we're on the same page, this is what you're doing:
Download and extract attachment. Using Root explorer, backup the gps.exynos.so in system/lib/hw to sdcard, then remove it from the system/lib/hw folder. Also using Root explorer, copy the gps.exynos4.so that you extracted or whatever its called to system/lib/hw. Fix permissions to rw-r--r--. Reboot. Open Google maps, grant it the permission to access location. Wait for GPS fix.
Using those steps I get GPS working first go every time on RootBox 4.0. If I miss anything, or do anything different, it won't work. Are those the exact steps you're using?
Hopper8 said:
Fix permissions to rw-r--r--.
Click to expand...
Click to collapse
What do you mean by this? The read write execute permissions? Or something else?
vSTATERv said:
What do you mean by this? The read write execute permissions? Or something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1857648
Yes, the file permissions. Stickied at the top of the GSII 'General' Section.
Permissions set properly - still not working.
vSTATERv said:
Permissions set properly - still not working.
Click to expand...
Click to collapse
Another captain obvious comment, you are searching for GPS while you're outside? I would assume so. Have you tried re-downloading the file for the fix from the RB thread? If you haven't, try that. If you have, reflash the ROM after a factory reset, cache & dalvik wipe. Try to fix the GPS before restoring all your data etc.
---------- Post added at 10:25 PM ---------- Previous post was at 10:11 PM ----------
FD1999 said:
Sorry but what attachment?
Gesendet von meinem LG-P880 mit Tapatalk 4
Click to expand...
Click to collapse
The one from the third post of this thread: http://forum.xda-developers.com/showthread.php?t=2117444. In the 3rd post, the third option for the GPS fix.
Does this mean anything? One satellite keeps popping up in the centre of the radar.
vSTATERv said:
Does this mean anything? One satellite keeps popping up in the centre of the radar.
Click to expand...
Click to collapse
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
I did a full wipe, still persists. I might try and flash another rom.
vSTATERv said:
I did a full wipe, still persists. I might try and flash another rom.
Click to expand...
Click to collapse
Omega AOKP has written in the OP 'instantaneous GPS lock'. I've used it and had no issues with GPS at all, give it a shot.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
I've restored an old backup of resurrection remix, and I still have the problem.
Is it possible that some system files regarding the GPS were corrupted?
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Click to expand...
Click to collapse
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
vSTATERv said:
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
Click to expand...
Click to collapse
Two words: Flash Stock.
Flashed stock - problem still persists.
UPDATE - finally got it working. Flashed latest stock firmware; it didn't work at first, however after persistent testing I finally get a lock after 26 seconds or so.
Thanks very much for all the help.
Hardware problem. Service centre (Unless you want to try all the usual fixes you'd try if you were still running a custom rom, which I very much recommend you do first).
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