Related
THIS IS FOR A2SD ONLY!
THIS METHOD HAS BEEN VERIFIED 6 TIMES!
We all have been there at one time or another. We just finished upgrading our G1's or MT3G's to the next awesome version of CYANOGEN rom or we have wiped and installed a fresh CYANOGEN rom and then when the phone boots all of these FC's come up. Normally the next steps are to go in the market and unistall and reinstall the problem apks. Well those days are over, I don't know if anyone here has discovered this method but you will no longer have to install each Protected APK one by one.
Procedure:
Step 1: Make sure you have the latest version of RA-dream-v1.2.3 installed on your device. Now assuming you have just finished flashing the latest update to your phone then follow the next step.
Step 2: Reboot into recovery by holding down the HOME key
Step 3: Select the option in the list for "Wipe Dalvik-Cache on SD", select this option and then hit the HOME key to confirm.
Step 4: Once that completes reboot the phone (it may take 5 or 6 minutes as it is re-Odexing) until it loads as normal, open up your Terminal Emulator. Type in "su" and enter. Then type in "fix_permissions" (depending on how many apps you have this may take a couple of minutes, so do something to stay occupied..) Once this completes proceed to step 5
Step 5: Now while in Terminal Emulator type in "reboot recovery" and hit enter. This will force the phone into recovery without holding the HOME key.
Step 6: Once recovery has loaded, chose the option for "fix mismatched apk uids" and hit HOME key to confirm. Let this run for a little bit, its usually quicker than fix_permissions while the phone is on completely.
Step 7: Once complete reboot your device.
Final Step: Assuming all steps were followed, attempt to open a protected app such as Power Manager or watch it load. If you have any issues please let me know here or PM me.
-flak0
Reserved
Reserved for future SPACE... Just in case
Reserved
Reserved again..... really just in case... Screenshots possibly..
What script? This should be common knowledge by everyone who flashes a rom. This will help with questions and it should be linked whenever someone asks about the flashing procedure.
~~Tito~~ said:
What script? This should be common knowledge by everyone who flashes a rom. This will help with questions and it should be linked whenever someone asks about the flashing procedure.
Click to expand...
Click to collapse
Hmm I was hoping theres some new magical method that he created, instead its just a how-to tutorial on what most people usually do (well almost..why run fix permissions twice?)
You might as well suggest a WIPE to never have a single FC issue!
My procedure before flashing any rom is:
Repartition *manually, meaning removing the ext partition and the linux-swap partition, then recreating them
Wipe
Repair ext
Wipe
Never get a issue, or FC, and once you get the procedure down it takes about a 1 minute and a half. Then I flash and I only get the issues that are issues with the rom I flashed(If there's any) and not an issue on my end. Everyone should do that and no one will have problems
*using Gparted in console of course
Oh and when I flash a theme for cyanogen I usually boot into the fresh flash then I reboot into recovery and nandroid back up then flash the theme, then I only get the problems that occur with a theme(If there's any).
THANKS for this bit of info. What people fail to realize is that EVERYONE is NOT a root specialist like some of us so things that are "easy" to us are difficult and frustrating to others with less skills. That's like me and my IT friends expecting a new graduate to know all the tricks and trade of fixing and maintaining servers across the world. Common knowledge is knowing HOW to root, HOW to find roms/themes and how to wipe and flash new roms. Everything else may get a little sticky for the "common" android users. Afters hours of helping people with tasks who seriously have no clue, i can tell you...its TRUE lol
can anyone please update RA-dream-v1.2.3 link in the first post or post here this is my last hope trying out
phone2175 said:
can anyone please update RA-dream-v1.2.3 link in the first post or post here this is my last hope trying out
Click to expand...
Click to collapse
Here ya go, just had to remove the double "http://"
Ra-dream-v1.2.3
~~Tito~~ said:
My procedure before flashing any rom is:
Repartition *manually, meaning removing the ext partition and the linux-swap partition, then recreating them
Wipe
Repair ext
Wipe
Never get a issue, or FC, and once you get the procedure down it takes about a 1 minute and a half. Then I flash and I only get the issues that are issues with the rom I flashed(If there's any) and not an issue on my end. Everyone should do that and no one will have problems
*using Gparted in console of course
Oh and when I flash a theme for cyanogen I usually boot into the fresh flash then I reboot into recovery and nandroid back up then flash the theme, then I only get the problems that occur with a theme(If there's any).
Click to expand...
Click to collapse
So you like going through and having to install everything again and setting up all your settings again? or do you use some type of back up?
I think he came out with this "guide" to help reduce FCs for those that don't want to wipe every time, because really, it's unnecessary and quite a hassle.
This is brilliant. I just tried it going from a themed cyan 4.2.3.1 to plain 4.2.4 and I had just one force close (which is a protected app that I had a widget for on my home screen so I suspect that is why) instead of at least 8 apps that normally need to be reinstalled taking time and losing settings.
Awesome work sir!
Ummmm doesn't the option of "fixing mismatched uid" mean fix_permissions
don kiedic said:
Ummmm doesn't the option of "fixing mismatched uid" mean fix_permissions
Click to expand...
Click to collapse
Seems you are correct there:
http://forum.xda-developers.com/showpost.php?p=4727115&postcount=377
So I guess we can skip either the fix_permissions step or running 'fix uid mismatches' then? Does it make a difference running in the booted system as opposed to from recovery?
Hmm, this isn't working for me anymore. Do themes have some affect on this?
I've been getting a lot of messages asking, 'How do you create ROM's?' Well, I got so many I decided to make this. This process is called cooking a ROM.
The first thing you have to do is get a ROM that's already been created and signed that you'd like to change around. Make sure it's a signed update.zip. Then, you unzip the rom, and you should see directories, like data/ and system/. If you want to add/remove applications in the ROM, you would goto data/app/. In there you will find the apk's of files that will be pre-installed on the ROM. You can add or remove the apk's there. Another place for the apk's is in /system/app. You really shouldn't put new apk's in here, but you can remove the system apk's. So, if you wanted to remove Sprint TV, delete Sprint_tv.apk. Also, the apk's can be treated as zip's; you can unzip them and look inside, and if you wanted to, change around the icon's and stuff like that. After you are done changing around the ROM, you might want to edit the build.prop (This part is optional!) You would find it in system/build.prop. Look for a line that says 'ro.build.description='. You can edit that with the name of your ROM. When your all done, you would zip it all back up, and sign the update.zip. On windows, this is pretty easy. Download flipz pre-kitchen, and use a setting in tools called something like sign apk/update.zip. Navigate to where you put your rom, and sign it. Then, your rom should be ready to flash.
This is also a good post to read:
http://forum.xda-developers.com/showthread.php?t=551711
Notes:
*DO NOT* TRY TO FLASH A GSM ROM TO A CDMA HERO!
If you edited a apk, make sure to sign it before zipping it and signing the update.zip.
If you have any problems, I created a IRC channel for this, so I can give live support:
server: irc.bikcmp.info port 6667 (port 6670 for SSL)
channel #hero-cdma
If you don't have a IRC client, use mibbit:
http://widget.mibbit.com/?server=irc.bikcmp.info&channel=%23hero-cdma
Told ya! But, seriously -- thanks a whole hell of a lot, this is very much needed!!
pseudoremora said:
Told ya! But, seriously -- thanks a whole hell of a lot, this is very much needed!!
Click to expand...
Click to collapse
You're welcome! If you have any problems, get me on IRC.
This should be a Sticky!!! Was thinking about doing it but not best speller.......
Thanks for the guide, what I really like is the irc, I think we should have had one of these up for awhile now, it would help keep the clutter in the forums down.
theoottesen said:
Thanks for the guide, what I really like is the irc, I think we should have had one of these up for awhile now, it would help keep the clutter in the forums down.
Click to expand...
Click to collapse
What's even better is it's being DDoSed. . Anyone got a spare server? LOL.
But seriously, DDoS'es ARE NOT COOL.
Alright, I've got my ROM made and everything -- signed it as well. I put it on my SD Card, and its flashes successfully -- but now I'm stuck at the HTC Screen?
I took the battery out; went back into recovery and Wiped and formatted my SD Card, and flashed again (successful), but still stuck on HTC screen?
Any ideas?
bikcmp said:
What's even better is it's being DDoSed. . Anyone got a spare server? LOL.
But seriously, DDoS'es ARE NOT COOL.
Click to expand...
Click to collapse
I think this is crazy awesome to give a small how to on 'cooking' ROMS....I've always been interested! However what are DDoS'es....if it's all good to ask?
I don't have linux on my windows laptop...but do I need to get a dual boot/OS on my laptop to get this running. Last I knew, Linux and Windows were not friends...?
pseudoremora said:
Alright, I've got my ROM made and everything -- signed it as well. I put it on my SD Card, and its flashes successfully -- but now I'm stuck at the HTC Screen?
I took the battery out; went back into recovery and Wiped and formatted my SD Card, and flashed again (successful), but still stuck on HTC screen?
Any ideas?
Click to expand...
Click to collapse
What ROM did you start with...? Did you do all kinds of crazy stuff to it? I found a ROM, downloaded it and opened it....saw a bunch of stuff in there that the OP described. Not quite sure what is game to pull and what is cool to add...?
Konikub said:
What ROM did you start with...? Did you do all kinds of crazy stuff to it? I found a ROM, downloaded it and opened it....saw a bunch of stuff in there that the OP described. Not quite sure what is game to pull and what is cool to add...?
Click to expand...
Click to collapse
Alright -- this is what I did.
1. I made a new folder called Penguin
2. Took Gumbo1.5c and unzipped it
3. Moved all the stuff from Gumbo to Penguin
4. Began removing apps I didn't want in /system/app
5. Added some apps in /data/app
6. Added a white taskbar to its respective dir
7. Added Espresso -- again to its respective dir
8. Added the 2.1 Icons
9. SIGNED the new zipped folder (Penguin) successfully
10. Copied to SD Card
11. Flashed successfully
12. When I reboot, I stuck at the HTC Screen (I waited about 2 and half minutes)
Steps I've taken to solve:
1. Removed battery
2. Wiped
3. Formatted card
4. Flashed again
5. Stuck again at HTC (again 2 minutes or so, until removing battery again)
5. Stuck again
Konikub said:
I think this is crazy awesome to give a small how to on 'cooking' ROMS....I've always been interested! However what are DDoS'es....if it's all good to ask?
I don't have linux on my windows laptop...but do I need to get a dual boot/OS on my laptop to get this running. Last I knew, Linux and Windows were not friends...?
Click to expand...
Click to collapse
DDoS is a denial of service attack. They are attacking my server and also my home network. I've got a lot of it cleared out, but still a lot of IP's doing it. Also, try Wubi for that Linux and windows issue.
Should you have waited longer than 2 and a half mins? I flashed Godzson Dialer and rebooted and it took 5 or 6 mins to boot, and when it did...I was happy.
Not sure if you took too much out or added something you shouldn't have, or just perhaps didn't wait long enough for it to boot.
...OH Wait, you mean that HTC symbol at the very begining..........gotcha now! I at least was on the nexus bootscreen when I waited.
Hope you get an awnser soon, I am looking forward to playing around and perhaps cooking up something good of my own
Konikub said:
Should you have waited longer than 2 and a half mins? I flashed Godzson Dialer and rebooted and it took 5 or 6 mins to boot, and when it did...I was happy.
Not sure if you took too much out or added something you shouldn't have, or just perhaps didn't wait long enough for it to boot.
...OH Wait, you mean that HTC symbol at the very begining..........gotcha now! I at least was on the nexus bootscreen when I waited.
Hope you get an awnser soon, I am looking forward to playing around and perhaps cooking up something good of my own
Click to expand...
Click to collapse
Exactly what I was saying, 2 minutes isn't enough for the first boot. It takes 5 or maybe even 10!
bikcmp said:
Exactly what I was saying, 2 minutes isn't enough for the first boot. It takes 5 or maybe even 10!
Click to expand...
Click to collapse
Well -- I've reflashed and am now playing the waiting game -- going to wait 15 minutes. Started at 2:17 (central)... we'll see in a little bit.
Here is a good list of Apps/Apks I found to help out some who don't know what to remove without causing a slew of FC's......if anyone knows of anymore that are safe, please keep this "How To" going strong!
APPS that are SAFE to remove
Question....where would the respective 'dir' be for throwing 2.1 icons into a ROM while cooking...? data/apps?
I'm honestly trying to google all my questions as well as search this forums threads....but sometimes I don't get the answer I need
Konikub said:
Here is a good list of Apps/Apks I found to help out some who don't know what to remove without causing a slew of FC's......if anyone knows of anymore that are safe, please keep this "How To" going strong!
APPS that are SAFE to remove
Question....where would the respective 'dir' be for throwing 2.1 icons into a ROM while cooking...? data/apps?
I'm honestly trying to google all my questions as well as search this forums threads....but sometimes I don't get the answer I need
Click to expand...
Click to collapse
The directory that the 2.1 icons should go in is /system/app/
Lets say I want to change the Browser.apk icon. I would pull it, open it as a zip file, look for ic_laucher.png (or something of this sort) -- and replace this file with the newly created icon (has to be the SAME name as the original file), you'll copy this new "icon" into the original dir, overwriting the changes -- and that's it.
If you need some help:
This will help you changing icons:
http://forum.androidcentral.com/htc-hero-roms-hacks/6070-changing-hero-application-icons.html
ROM FAQ/Building
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
I waited 15 minutes and still nothing -- so I just did a nandroid. I'll work on it some more tomorrow.
pseudoremora said:
The directory that the 2.1 icons should go in is /system/app/
Lets say I want to change the Browser.apk icon. I would pull it, open it as a zip file, look for ic_laucher.png (or something of this sort) -- and replace this file with the newly created icon (has to be the SAME name as the original file), you'll copy this new "icon" into the original dir, overwriting the changes -- and that's it.
If you need some help:
This will help you changing icons:
http://forum.androidcentral.com/htc-hero-roms-hacks/6070-changing-hero-application-icons.html
ROM FAQ/Building
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
I waited 15 minutes and still nothing -- so I just did a nandroid. I'll work on it some more tomorrow.
Click to expand...
Click to collapse
Any luck...? Anyone out there having success in trying to get this to work?
pseudoremora said:
The directory that the 2.1 icons should go in is /system/app/
Lets say I want to change the Browser.apk icon. I would pull it, open it as a zip file, look for ic_laucher.png (or something of this sort) -- and replace this file with the newly created icon (has to be the SAME name as the original file), you'll copy this new "icon" into the original dir, overwriting the changes -- and that's it.
If you need some help:
This will help you changing icons:
http://forum.androidcentral.com/htc-hero-roms-hacks/6070-changing-hero-application-icons.html
ROM FAQ/Building
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
I waited 15 minutes and still nothing -- so I just did a nandroid. I'll work on it some more tomorrow.
Click to expand...
Click to collapse
Have you tried just opening the zip,editing the name and files inside the zip,then resign it an flash. I ran into problems when I tried to take the files out and make my own.
[email protected] said:
Have you tried just opening the zip,editing the name and files inside the zip,then resign it an flash. I ran into problems when I tried to take the files out and make my own.
Click to expand...
Click to collapse
What files exactly are you saying I should edit? I'm up for any ideas -- I'm definitely going to get this to work, I want to contribute damn it!!
I just downloaded a ROM and took some apks that were on the "SAFE" list to remove from the link in the above post. Replaced some apk files with the 2.1 icons....using the same name as the ones I replaces (so I'm not 'adding' anything new)
Renaming my ROM and then zipping it up to flash. (doing it now, and if that works....then I will play with it a little more and see how far I can get until it does not boot)
HOPEFULLY this boot with what I've just done....lol. I should, I've done nothing really...
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD. POSSIBLY, it will be available for the Sensation in the near future. One user has used it and has had great success.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
crypted said:
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
Click to expand...
Click to collapse
I'll take a stab at it. I have a custom one running as well from another thread where I get 8 sats locking on eventually.
Sounds good. Got the two devices I can easily support/test doing quite well. I'd just like to share this with as many as I can, but without a device it's hard to know who would benefit.
Initial flash made my phone bork lol. It wouldn't boot up. Did a adb reboot and a system error window showed up.
Tried the 2nd time and booted up fine. Weird. I guess next time I'll just push the gps.conf. .
Ok I'll report back on the locks tomorrow. I'll test out the gps locks tonight before bed.
kpjimmy said:
Initial flash made my phone bork lol. It wouldn't boot up. Did a adb reboot and a system error window showed up.
Tried the 2nd time and booted up fine. Weird. I guess next time I'll just push the gps.conf. .
Ok I'll report back on the locks tomorrow. I'll test out the gps locks tonight before bed.
Click to expand...
Click to collapse
That is extremely weird. How did you flash it?
crypted said:
That is extremely weird. How did you flash it?
Click to expand...
Click to collapse
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
crypted said:
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
Click to expand...
Click to collapse
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
kpjimmy said:
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
Click to expand...
Click to collapse
The boot issue is from the nohz kernel. I've had it happen quite a few times and so have others.
Sdobron said:
The boot issue is from the nohz kernel. I've had it happen quite a few times and so have others.
Click to expand...
Click to collapse
soma900 said:
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
Click to expand...
Click to collapse
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
kpjimmy said:
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
Click to expand...
Click to collapse
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
crypted said:
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
Click to expand...
Click to collapse
I want to say soma is correct with regards to the kernel. Prior to pushing your file over, my gps was fast, but wasn't as fast as yours. Meaning its a matter of seconds really. Whereas I run gps fix and now I got a fix before the map loads up, which never happened in the past.
As for trying it with a different kernel, I'll do that later maybe after work if my 3 yr old stops "helping" me on my netbook lol.
As for a faster and more reliable way of installing your gps.conf, IMO is to just simply push the file to the /system/etc folder. But I know a lot of people are wary of adb commands and much rather flash and forget it, but I think trying out adb commands are worth the practice and with this it's easy peasy to push it over via adb. As for a simple flash, well I guess if they are on a stock kernel they can try to flash it once you mount your system under recovery. Or when flashing a new rom or update, they can revert and flash a stock kernel first, flash your zip file and reboot, but seems like a bit more work than just pushing the gps.conf file.
With either extracting your gps.conf or mine stripped down with your info, here's a basic adb/shell command thread to help people on their way if they choose to.
http://forum.xda-developers.com/showthread.php?t=517874
Back to topic: as stated before, locking onto my gps now is a breeze. Thanks!
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
soma900 said:
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
Click to expand...
Click to collapse
Make a backup of your current gps.conf from your phone under /system/etc so you can revert back to that file if this one doesn't work for you.
As for installation, just push that file over or even use root explorer.
EDIT 2. From work (office window with view of sky), I tried to get a lock but it did not lock even though gps test saw the sats. Ever since flashing roms, I think wifi has a conflicting issue when trying to get a gps lock. I then turned off wifi, let the phone sit for a minute to let it get the 4g up and going and then tried the gps test again. I then got 8 sats and then opened up gps fix to see how fast I could get a fix and like before, the gps locked my location before it fully loaded up. Pretty cool IMO. LOL
And after the lock, I can go ahead and turn wifi on again and it no longer conflicts with the gps lock issue. Weird work around, but that's how I have been able to get gps locking to work.
kpjimmy said:
I want to say soma is correct with regards to the kernel. Prior to pushing your file over, my gps was fast, but wasn't as fast as yours. Meaning its a matter of seconds really. Whereas I run gps fix and now I got a fix before the map loads up, which never happened in the past.
As for trying it with a different kernel, I'll do that later maybe after work if my 3 yr old stops "helping" me on my netbook lol.
As for a faster and more reliable way of installing your gps.conf, IMO is to just simply push the file to the /system/etc folder. But I know a lot of people are wary of adb commands and much rather flash and forget it, but I think trying out adb commands are worth the practice and with this it's easy peasy to push it over via adb. As for a simple flash, well I guess if they are on a stock kernel they can try to flash it once you mount your system under recovery. Or when flashing a new rom or update, they can revert and flash a stock kernel first, flash your zip file and reboot, but seems like a bit more work than just pushing the gps.conf file.
With either extracting your gps.conf or mine stripped down with your info, here's a basic adb/shell command thread to help people on their way if they choose to.
http://forum.xda-developers.com/showthread.php?t=517874
Back to topic: as stated before, locking onto my gps now is a breeze. Thanks!
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
Make a backup of your current gps.conf from your phone under /system/etc so you can revert back to that file if this one doesn't work for you.
As for installation, just push that file over or even use root explorer.
EDIT 2. From work (office window with view of sky), I tried to get a lock but it did not lock even though gps test saw the sats. Ever since flashing roms, I think wifi has a conflicting issue when trying to get a gps lock. I then turned off wifi, let the phone sit for a minute to let it get the 4g up and going and then tried the gps test again. I then got 8 sats and then opened up gps fix to see how fast I could get a fix and like before, the gps locked my location before it fully loaded up. Pretty cool IMO. LOL
And after the lock, I can go ahead and turn wifi on again and it no longer conflicts with the gps lock issue. Weird work around, but that's how I have been able to get gps locking to work.
Click to expand...
Click to collapse
I think I know how to resolve that wifi issue. I can give you the test version of 1.3.
If v1.3 works fine AND if you can help me draft instructions on specifically installing on your device, I can post the full-support thread.
Are you up for this? If so, please draft and message me instructions. And, I'll send you the test version of 1.3 for your flashing pleasure.
Well ..didn't seem to do any good for me ... stock rom .. rooted.
There has to be a way to allow it to position based on less satellites .... damn it.
steve841 said:
Well ..didn't seem to do any good for me ... stock rom .. rooted.
There has to be a way to allow it to position based on less satellites .... damn it.
Click to expand...
Click to collapse
All: try these two patches individually instead: http://derekgordon.com/gps-files/worldwide1.2-t.zip and http://derekgordon.com/gps-files/worldwide1.2-tn.zip
If one doesn't work well, try the other. This solved a problem with some Tunisia users. It has to do with GPS and Wifi conflicts when the phone has an older GPS unit built in.
crypted said:
I think I know how to resolve that wifi issue. I can give you the test version of 1.3.
If v1.3 works fine AND if you can help me draft instructions on specifically installing on your device, I can post the full-support thread.
Are you up for this? If so, please draft and message me instructions. And, I'll send you the test version of 1.3 for your flashing pleasure.
Click to expand...
Click to collapse
What do you want me to draft up? I'd help if I can of course. OH nvm I think I got it lol....sending you a pm.
kpjimmy said:
What do you want me to draft up? I'd help if I can of course. OH nvm I think I got it lol....sending you a pm.
Click to expand...
Click to collapse
Thanks.
All: let me know how those test builds (posted above) and the one in private message (kpjimmy) work out on your Sensations. I feel confident that we can make this release happen next week when v1.3 comes out.
crypted said:
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
Click to expand...
Click to collapse
Dear crypted,
Your configure script works on HTC sensation. Thanks! Great work! Got a lock in 10 seconds. before it is really difficult and take ages to get a lock.
Did not flash it just change the file property "readonly" with RE. Copy and overwrite.
I am sorry I do not understand what is an NOHZ kernel. I am a noob.
By the way I am using a modded ROM of LeeDroid 3.1.0. S-OFF, Revolution recovery 5.0.2.0. Thus ROOTED. Now every program use GPS-sat get a quick lock within 10 seconds. You shall promote your script to every ROM-devs. I highly recommand your script!
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
soma900 said:
Dear crypted,
Your configure script works on HTC sensation. Thanks! Great work! Got a lock in 10 seconds. before it is really difficult and take ages to get a lock.
Did not flash it just change the file property "readonly" with RE. Copy and overwrite.
I am sorry I do not understand what is an NOHZ kernel. I am a noob.
By the way I am using a modded ROM of LeeDroid 3.1.0. S-OFF, Revolution recovery 5.0.2.0. Thus ROOTED. Now every program use GPS-sat get a quick lock within 10 seconds. You shall promote your script to every ROM-devs. I highly recommand your script!
Click to expand...
Click to collapse
steve841 said:
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
Click to expand...
Click to collapse
Okay. If y'all could private message instructions on how to copy the GPS configuration over to the /system/etc folder, I would appreciate it.
I have one set of instructions sent to me thus far. I'd just want to make sure we have all of the various methods ready to post when I release the Sensation version.
Faux kernel no go for me so I am trying another. The bricked 0.5ver. Flashing now and will report back.
EDIT:Back in the office. Flashed the bricked 0.5 v kernel and then flashed the test 1.3 gps script.
Got about 5 sats in use and in view using GPS test and locked it with 10 seconds. Not as fast as 1.2 but still quick. Maybe because it's looking at the worldwide servers before seeing where I am? I was using 1.2 US gps script.
---------- Post added at 01:55 PM ---------- Previous post was at 01:38 PM ----------
steve841 said:
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
Click to expand...
Click to collapse
Just download whichever file you want to use and extract the zip under system/etc and then push the gps.conf over via adb or root explorer.
I'm surprised at there being a decrease in v1.3. Possibly a placebo effect. Hmmm.
Sent from my Inspire 4G using XDA App
I've recently started having problems after changing ROMs a couple of times.
I tried installing a new Rom (CM12.1) but it is still happening and I've installed a new GAPPS each time too so I guess the problem runs deeper than that.
The ROM runs fine for a bit but then all of a sudden I get a force close which constantly keeps coming up no matter how many times I press 'Ok'.
I've had a few different processes stop but the last two that spring to mind are 'process.android.phone', 'Swiftkey' and 'Google Play'.
I have to reboot but then end up stuck at the splash screen at boot. I then have to Power+Vol Down to go into recovery and then reboot system from there. It then runs through the App optimisation screen brfore restarting.
I've never touched kernels since I've been changing ROMs so whether thats the issue.
Any help with this would be great as otherwise this is the best Rom Ive used.
Thanks in advance
A logcat showing traces of these force closes would help
Aquous said:
A logcat showing traces of these force closes would help
Click to expand...
Click to collapse
I didnt do one on account of me not having a clue what the hell one was
Luckily my friend Google does know what the hell one was.
I've attached a couple of log files created around the time of the unpleasantries which hopefully might shed some light.
This one attached might be better, this was taken after I sorted out my Root Access again so might have more info.
Regards
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Aquous said:
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Click to expand...
Click to collapse
Hi, thanks for your reply. I havent been near any other custom themes. I've had this problem over a couple of Roms too.
I've tried to generate a catlog to get some error messages around the time its happening but I keep getting constant force close boxes which stop me doing anything (for a couple of different processes). The only way to stop them is to reboot but then the logs stop and reset when it boots so I cant get the info.
I've had to reboot about three times today and each time it has had to optimize the apps for some reason.
I've tried to get a catlog through ADB but I cant run the Android SDK as I need to install the JDK which keeps giving me 'Error 1500' on the install (even though I am most definately not already trying to install it).
Thanks for your help so far though and taking the time to read through the previous log.
Every solution I try just seems to create more problems
I've managed to attach a text file of all the error files its had since it started up (they are all in the space of about 10mins)
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Aquous said:
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Click to expand...
Click to collapse
Well I'm assuming their force closes. I get a white box popping up that says 'unfortunately XXXXX has closed' and when I click 'ok' the box goes away but either comes straight back or another similar one pops up. Its Trebuchet quite a lot.
I can't do anything then, if I try to get to LogCat that closes too and I can't really do anything until I reboot.
Its happened over 3 different Roms so dont think theres much the Rom compiler (is that what they're called, lol) can do.
I'm am probably going to have to see if I can get a Log through ADB, if I can remember how to use it, when I have time.
Cheers
I've managed to connect the tablet through ADB and managed to get some errors taken at the time I started getting all the 'Unfortunately XXXXX has closed [ok]' boxes kept coming up.
All the error messages attached came up in the space of a few seconds.
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Aquous said:
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Click to expand...
Click to collapse
Hi,
Thanks for looking through them errors.
To be honest I haven't heard of fsck. Is it something I can pick up fairly simply or am I more likely to do more damage? I've done a few searches and it looks a bit difficult and couldn't really find any threads that sounded similar to what I might need.
Thanks again
Update : I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs is it a case of running a command through terminal command in recovery from this directory?
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Aquous said:
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Click to expand...
Click to collapse
Hi,
No worries mate, I wasn't sure if what I said didn't make sense thats why there were no replies
The problem seems to be a lot better now but I've still had it a couple of times over the last two days.
I've tried to run the command above but with no joy. I'm still only learning the basics of ADB so still having some trouble.
I wasn't sure exactly where to run the commands from through the SDK so just went to the Terminal Command in Recovery and after navigating to the system/bin folder tried that command but it came up with the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS is in use
esfsck: cannot continue, aborting
I apologise if some of what I am doing seems nonsense but I am trying to pick up what I can by myself from various sketchy threads to avoid being a 'tell me what to do cos I can't be bothered looking myself' person. I dont know if this is doing more harm then good
Thanks again in advance for your help.
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Aquous said:
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Click to expand...
Click to collapse
For some reason I cannot get my PC to pickup the tablet in a command window when in TWRP so I was unable to run through ADB. 'ADB Devices just did not show anything.
In the end I did it all on my tablet in TWRP through the 'Command Terminal'. I navigated to the necessary folder (the one with fsck.exfat and fsck.f2fs in - /system/bin) through the Command Terminal and after typing the command in I got the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS clean, 9086/791520 files, 694414/3160055 blocks
Is that good?
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Aquous said:
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Click to expand...
Click to collapse
Hi, yea sure. I could use a bit of guidance with exactly how to do that though. I take it that is something I would have to run through ADB from my PC before I reset my tablet? Step by step instructions would be appreciated a lot (as has your extensive help already, creep creep ).
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Aquous said:
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Click to expand...
Click to collapse
Right, first thing this morning I had some errors, so I've managed to paste the results of a dmesg into the log file attached.
Cheers!
Hmmmm, now this is interesting. It looks like random services are failing to load - they are immediately exiting after being restarted. This is basically the same problem as with your apps force closing - something at the lower layers is causing everything to crash immediately upon launch.
Yet you're able to run basic programs (e.g. adb, dmesg) just fine, meaning that it's not likely to be a hardware issue.
What happens if in adb shell you run su and then 'stop' followed by 'start'? What should happen: when you run 'stop', the whole system freezes, and when you run 'start', you see your boot logo and android starts booting up again. Is this indeed what happens in this case, or do you get a bootloop? If so, post another logcat when you're stuck in the loop; you can get out of it by simply entering 'reboot' in your still-open adb shell.
I just got a s5 prime from eBay and was in the process of debloating via tibackup but kept getting stuck at boot screen showing warranty kernel bit. Required a restore of system and data each time to get it going again. Through arduous process of elimination I was able to narrow the culprit down to the aforementioned seemingly innocuous apk. When it's removed the phone dies.
What's even stranger is that this page seems to indicate that it's fine to remove:
http://forum.xda-developers.com/gala...oater-t3319854
I'm just curious as to why!
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
KamilKiri said:
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
Click to expand...
Click to collapse
I remove it from all my ROM builds with NO PROBLEM...
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
KamilKiri said:
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
Click to expand...
Click to collapse
endless boot is from some files in the /lib I believe if you look for these from a rom that worked and replace them in the rom your installing this would work in this case as well...
This link originated here >>>> https://www.tech1xpert.com/guide-to-port-roms-android/
Fixing a Bootloop
Your Port should take less than 5-8 minutes to boot. When the screen dims during boot logo, your Rom has successfully boot.But If your waiting for like 15 minutes, and boot logo is still going, YOU HAVE A BOOTLOOP. Luckily, the fix is easy!
STEP1:
Navigate to “PORT” folder. A ROM THAT BOOTS AND WORKS for you device
STEP2:
Go to lib folder inside System folder of Base Rom.= ROM That you want to install
STEP3:
Inside lib folder of PORT search for these libs:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Once you find each, copy them to the lib folder of Base Rom.= The ROM you want to install -- Right-click lib folder of Base Rom, select paste, and click the box in the lower left corner. Now “Click Move and Replace”
STEP4:
All done! Now add to a zip and flash!
This HAS WORKED in my attempts on PORTS that BOOTLOOP KUDOS
The same problem happened on my device. I took it to the mechanic before I tried to get into the recovery screen. We thought there was a power problem. The mechanic probably damaged my robust device because they didn't open it properly and handed it back to me in a broken state.
By taking a second N910C device and risking it, I repeated the same process step by step and found that the problem was caused by uninstalling the program "DictDiotek.apk". I restored my backup with Recovery. And my device turned on normally. DictDiotek is not a problem if frozen. Only uninstalling the phone does not turn on.
My phone is N910C. Custom ROM 6.0.1: Ditto ROM DN6