Related
Hi guys,
I've done a fair share of searching but it seems nobody is having the same issues
Basically, I thought i'd try out these new tweaks I found, the V6 Supercharger and the 3G Turbocharger from zeppelinrox - The V6 installed fine and was running smoothly but when i installed the faster version of the 3G turbocharger sent my phone into a bootloop (it eventually came back on to my relief). My HTC Wildfire is now thrown into a bootloop every time i enable mobile data. WIFI works fine.
I have reflashed my ROM, wiped data and dalvik cache, but when i flash the G_apps, the phone goes into the boot loop - and thats after a full wipe and reboot (i have now restored a backup - but the issue is still apparant)
Another thing worth mentioning is my local.prop file is empty and i'm not sure if this should contain any script.
Any help appreciated. Phone Spec below.
Thanks
Phone Model: HTC Wildfire Buzz
Android Version : 2.3.7
Rom: Cyangoen Mod-7.1.0.1-Buzz
Kernal: 2.6.35.14-nFinity [email protected] #1
Radio: 3.35.15.31
Baseband: 13.45.55.24U_3.35.15.31
Hboot: 6.01.1002
S-OFF
V6 Supercharger - Unsupercharged
3G Turbo Charger - Uncharged
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Fix for bootloop after 3g turbocharger script install
FIX:
Ran an RUU for wildfire.
- Downloaded (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24_ 3.35.15.19_release_141106_signed) from android forums.
- Connected phone to PC and ran RUU
- This downgraded phone OS to eclair (android 2.1)
- Let it do the bizniss
- Had to re-root with unrevoked 3
- Re-Flashed CM7 and gApps
All ok
I'll say one thing, CM7 doesnt need a v6 or a 3G super/turbocharger. It works fine without them. The minfree values are set at an ok level and I always have HSDPA signal. Its not worth the effort.
Yeah after carefully tweaking this and that - all one change after the other and testing a lot before going on - I've been pretty much satisfied with my old buzz. Until I decided to give that 3G Supercharger a try (because of 3G didn't ever work really good - the only thing I was not completely satisfied with)...
It turned out that there hasn't been any improvement from my perspective so I just reverted the settings and went on.
It took me 2 weeks to find out where the bootloops suddenly came from (1 day to narrow down the prob had to do with switching on data and at least 10 days for the 2g/3g part).
Is there anybody who can explain more specific a) what causes this behaviour and b) what would be necessary to eliminate the cause (and probably avoid it in the future)
I won't get misunderstood but just "do an RUU update" sounds a bit like the standard no.1 suggestion "format and re-install" in all those amateur winsucks forums...
3xeno said:
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Click to expand...
Click to collapse
Thanks for the hint but even after reading all the related posts several times I don't feel enlighted somehow (besides the information that I don't need any super charge scripts with CM - which I'm half the way to be convinced of )
noone? I just want to find out what exactly is the problem (to avoid it in the future) and I'm really curious why a complete wipe doesn't help. The Supercharger scripts just tweak values in config files (correct me if I'm wrong) - so if the problem is caused by the script(s): why can't it be solved by simply revert those changes (or replace the files by the default ones)?
Fix for bootloop after 3g turbocharger script install
eventcom
Did you find anything more about this problem?
I have the boot loop after using 3g/4g optimizer from the market, but I can get partial network use if I enable only 2g and not 3g. Better than nothing while I see if it can be fixed without a RUU.
Just wondering if a RADIO flash may solve the problem.
Regards.
Phone Model: HTC Wildfire Buzz
Android Version : 2.2.1
Rom: Stock
Kernel: [email protected] #1
Radio: 3.35.20.10
Baseband: 13.55.55.24U_3.35.20.10
Hboot: 6.01.1002
S-OFF
st3v3droid said:
Did you find anything more about this problem?
Click to expand...
Click to collapse
nope unfortunately not, but it seems, that the problem still occurs - see in this thread or here in that one - I've given it another try to flash radio again - with no help. The information about changed values in build.prop isn't new to me (as I did expect something like that) - what I don't know is which values exactly and how to overwrite them (if too many) when flashing a new rom...
So I went a bit deeper into the build.prop and made a simple diff against the build.prop of October 2011 (has been an earlier nightly and that problem definitely didn't occur at that time).
The only differences were those:
This looks like a simple addition for identification
Code:
+++ ro.cm.device=buzz
Perhaps that's a better guess (looks like this had been added sort of randomly anyway? - qualifies):
Code:
+++ # For PDP overlap problem
+++ ro.ril.avoid.pdp.overlap=1
That shouldn't harm anything:
Code:
+++ # update the acoustic table for Buzz NEL lab testing
+++ ro.ril.update.acoustic.table=1
My own changes which didn't cause any trouble before:
Code:
--- dalvik.vm.heapsize=24m
+++ dalvik.vm.heapsize=32m
+++ ro.compcache.default=0
That shouldn't have to do with the problem, too:
Code:
+++ persist.sys.rotationanimation=false
+++ persist.sys.scrollingcache=2
but that one probably?:
Code:
+++ # Lock dirty_ratio to 20 when USB is mounted for improved transfer speed
+++ ro.vold.umsdirtyratio=20
So I simply commented out the stuff I guessed to be responsible (no. 2 and 6) and restarted - no success. Reboots again when turning on 3G
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Doddster said:
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Click to expand...
Click to collapse
that sounds exactly like LucidSomnia's report in the thread I've used to continue with my experiences. I can't tell if my solution (if it was any and not by accident) will help you but it shouldn't hurt to give it a try...
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
P.S The camera works occasionally, I get viewfinder but no way of taking picture and if I install the 3rd party app Line camera I can take pictures with no viewfinder.
Doddster said:
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
Click to expand...
Click to collapse
As you can see in my posts (in three threads) I've done a lot of stuff, too, what did the trick in the end (if it was not just by accident) was
Total/full/mega wipe (except SD card)
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (older one in my case)
Boot
after that just the same procedure
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (newest in my case)
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
If that's the case with you I'd give my method a try and if that doesn't work I'd do an RUU (the safe flash variant first of course).
eventcom said:
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
Click to expand...
Click to collapse
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Steps followed:
(In recovery)
Wipe Cache,
Factory Reset.
Flashed CM7
Flashed Radio (3.35.19.25) using CMrecovery 2.5.0.7
Thanks eventcom
**Dunno if I'm gonna have the balls to install CM9 again after all this
Doddster said:
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Click to expand...
Click to collapse
glad to hear that it helped
**Dunno if I'm gonna have the balls to install CM9 again after all this
Click to expand...
Click to collapse
I'm not really sure about what exactly caused the problem (at my side at least) - but even if CM9 on the Wildfire is highly experimental this particular problem doesn't look to me that it has to do with the ROM. I slightly remember a few people having this problem after flashing a different ROM but in most cases this could be solved by a simple restore. Did you also use some tweaks - like a different kernel, RAM scripts or something similar?
nope, nothing different from what was included on the CM7 and CM9 builds. :/
It's frustrating as ICS actually runs ok on the wildfire, it's only till it hits the radio or camera hurdles it lets itself down lol
I'm getting another phone soon so I will be using my Wildfire for development and I'll put all my effort into helping us wildfire'ers run ICS with no hassle.
Im gonna stick my neck out here, all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Could be coincidence or could be the reason!
Forum fishing.... Who's biting!
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Doddster said:
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Click to expand...
Click to collapse
Have you ever had the problem with the radio outside of cm9?
Ive never tried cm9 nor had issue with any of my radios but have had bootloops when i tried the v6 scripts back in my early days.
Forum fishing.... Who's biting!
slymobi said:
all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Click to expand...
Click to collapse
Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
]Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
Click to expand...
Click to collapse
I try to follow all threads here in wildfire as well as a handful outside and like i said the main 3 factors mentioned above are nearly always present or come to be eventually
I dont think it will ever be pinpointed or whittled down to just one reason due to there being so many possible causes/possible triggers. I can however say from my own experiences that ive not had a single bootlooping issue since the day i removed and never again used any v6/juuwes enhancing scripts. I keep my processor at 633 max,264 min ondemand/smartass, my readahead sd speed never over 1024(516 is my preference, to limit sd errors) set on any rom i use.
I always unzip the rom and study within to edit, mod, remove certain elements i desire/dont need or want prior to flashing it.
This way i have the setup i want and need for my own personal liking.
Regards slym.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
Hi guys,
I own a Motorola Defy currently running on Froyo 2.2.
I've been reading the guide threads on installing a custom ROM and I am interested in trying it out.
I am currently focused on CM7.
However, I just want to confirm that going through this process is going be advantageous. My current stock Froyo installation is stable but can sometimes be a bit slow. Would CM7 (running Gingerbread) be a smoother ROM overall? Also would I be able to get better battery life, or overclock my CPU to a higher clock speed? Are there other advantages?
Apologies if this question has been asked before. I tried searching but could not find any direct information on why I should change from stock.
If u just want a faster and a bit smoother rom just install 2nd init to overclock yr cpu. If you are looking for speed and performance then CM7 and lastly Miui for beauty and customization. U can have a different theme for your stausbar, sms etc. And if you don't like the iphone style launcher of miui then u can always install a different launcher In terms of battery life it depends but custom roms usually have less battery life from what i have seen. Hope this helps
Shahmatt said:
Apologies if this question has been asked before. I tried searching but could not find any direct information on why I should change from stock.
Click to expand...
Click to collapse
i dont think anyone can give you any reason why YOU should change your ROM, but they can give you reasons why they changed theirs... its all a matter of preference, if you want a stable and reliable phone with everything working fine then you can stick with stock rom (or is it really reliable?? debatable hehe)
or you can go for ROMS that have beautiful interfaces, good battery life, lots of functions, fast and smooth... there are lots of options, its best you try it out yourself, i personally prefer CM7.1 while a friend of mine loves CMIUI...
I think just rooting the phone by itself will give you quite a few advantages, personally I didn't see much difference in at first battery life by using CM7, 7.1, 7.2....but those give a good bit more freedom, and if you want to you can turn your phone into a speed demon (the stock defy....is....not...) or a battery sipper that lasts for a while.
It's mostly just the freedom.
I root and use custom ROMs because I like to tinker it's the same reason I use Linux more than windows. I like to be able to change things and yes sometimes I break things but then I get to learn how to fix them.
Sent from my SCH-I500 using Tapatalk
Thanks for the responses.
Would the CM7 jump from Froyo to Gingerbread show a significant improvement?
Shahmatt said:
Thanks for the responses.
Would the CM7 jump from Froyo to Gingerbread show a significant improvement?
Click to expand...
Click to collapse
Yes.
I use MIUI. Exactly WajkUI.
Faster and all ways better than stock ROM.
CM 7 is good also but I think it has an old and boring user interface.
If you're installing a Custom ROM it is not only that you get Gingerbread (this is actually the smaller thing), you get a different user experience, a fresh design (no Motoblur anymore), more customizations and tweaks.
My favorite in terms of stability, smoothness and speed was Galnet MIUI (before I switched to CM9 but that's not really final...), imho MIUI looks better, has nice built in apps and an awesome theme support (you can customize everything like the status bar, boot animation, font, lockscreen...). CM7 was a tiny bit less stable for me, it looks more like plain stock Gingerbread and you have some additional advanced settings.
Shahmatt said:
Thanks for the responses.
Would the CM7 jump from Froyo to Gingerbread show a significant improvement?
Click to expand...
Click to collapse
Yes of course
I tried it myself and CM 7.1 is more stable
Thanks all for your help.
I think I will indeed go ahead and try a custom ROM.
I notice MIUI also seems to have a following. Can anyone point me to the relevant ROM forum link? I can't seem to find it in the Android Development Forum. :-/
I intend to use the instructions shown in the following link in order to flash a new ROM:
http://forum.xda-developers.com/showthread.php?t=1054447
Am I right in assuming that steps 1 to 9 must be universal to all Defy's and that step 10 is where you flash the ROM of your choice?
There are indeed a few different miui variations that often different mods and add-ons. U can try the official english builds with no tweaks and mods just translated to english at miuiandroid.com or other english variation at miui.us or one with awesome mods and tweaks that i recommend will be wajkiui ics or ics miui dsj from the forums or galnetmiui from galnetmiui.co.uk.
Yes the steps are universal but a bit outdated.
U can't download 2ndinit from market anymore just get latest apk from here http://forum.xda-developers.com/showthread.php?t=1032212
Make sure you're on froyo if not you won't be able to downgrade or use any custom roms as they use froyo as base.
Also have your files ready on your sd card before you start this.
Steps
1. Backup your apps using titanium backup root or mybackup root additional you can backup your contacts and messages by selecting data in mybackup root
2.Download superoneclick from here http://forum.xda-developers.com/showthread.php?t=803682. Use the 2.11 version easiest and quickest to root froyo
3.Connect your phone to PC. Right click superoneclick -> open as admin
4.Wait till it says waiting for device then go to your phone in settings->Applications->Development check usb debugging is on
5.After your phone is rooted. Uncheck usb debugging and restart your mobile.
5.Now switch your phone on again and check usb debugging is on then download 2nd init from here http://forum.xda-developers.com/showthread.php?t=1032212 and install the 2nd init recovery. It will ask the superuser permission Accept it. If the led light is green then 2ndinit was successfully installed.
6. Now Uncheck the USB debugging from Settings->Applications->Development and restart the phone now.
7.It will go in to bootmenu select 2nd init as default boot. Using the volume rocker to navigate and power button to select
8.Go back and click recovery -> Custom recovery ->* Wipe data/factory and Wipe cache and also go to advance and clear dalvik cache -> Install zip file from sd card(select the cm7 zip, repeat with the gapps zip) If it's miui no need to flash gapps
12. Reboot. Go to app drawer and start up the defy baseband switcher. select the appropriate baseband to achieve optimal reception.
Thanks to stewi21 for the original guide. If u need more help pm me or ask on the forums.
Happy Modding
If you are a us tmobile user, you almost certainly need wifi calling as the service stinks in closed spaces. So using a custom rom based on other than us froyo will eliminate that option...come on guys get it fixed please!
Thanks Kayant for the modified instructions. Many thanks also to others for the help.
So I went ahead and installed CM7. I figured I'll try the rest after having done a basic install to begin with.
It's pretty much the default Gingerbread experience I see. Quite smooth. A little disappointed that standard google apps like Gmail and Maps were not included but I soon settled this through the market.
Funny thing but Titanium Backup has seemingly not backed up some software like a paid version of Quick Office and Math Workout. Strange to me.
Battery life seems not much changed from the previous stock Froyo however I probably should give it a few days to stabilize.
Shahmatt said:
Thanks Kayant for the modified instructions. Many thanks also to others for the help.
Funny thing but Titanium Backup has seemingly not backed up some software like a paid version of Quick Office and Math Workout. Strange to me.
Battery life seems not much changed from the previous stock Froyo however I probably should give it a few days to stabilize.
Click to expand...
Click to collapse
Sure that you have selected the paid apps when you backupped them with Titanium? I never had such issues.
Battery life: Have you already recalibrated the battery after installing CM7.1? Af not, after installing a new ROM simply use the app "battery calibration" from the market to improve battery life.
Ok so I'm not experiencing good battery life.
I tried recalibrating but the improvements seem negligible if any.
I'm getting about 10 hours on a full charge with moderate use.
I tried changing the CPU governor in the boot menu. I switched from on-demand to smartass, and now to powersave. Oddly enough powersave seems to be worse than smartass. With smartass it seemed the battery drain was slower, but still not significantly so.
I would like the phone to comfortably last at least 12 hours wth moderate use. Moderate being about 8 mins of calls per hour on average.
I guess it I ought to downclock the CPU from the default 1000MHz to the original 800MHz. But I don't understand the settings properly. I see numbers 300, 600, and 1000, but what do these mean? Can I just simply change 1000 to 800 to reduce the upperbound frequency, or is there more that I should do?
The main thing I see as an advantage is speed. My phone is 3x faster now that I have CM7
I just installed miui and im stuck... where is the app drawer???? Am i blind??
Sent from my Nexus S using XDA App
There's no appdrawer. Miui's look a like IPhone.
Sent from my MB526 using xda premium
Ok, well im still stuck i cant get my network connection...im with telus on hspa
I see that for cm7 i can select a baseband with a well done app. It works very well so i am happy to see that i am still able to get a network connection somehow but i would prefer to use miui and it does not seem to find anything like if i did not get antenna conections with the rom. I tried miui on; miuiandroid.com 1.12.30 and an optimized version from a user on xda on another tread, after that i tried miui.us on version 1.12.23 and 1.12.30 and it always gives me the same exact result where i dont get any connection.
Since i was not able to get my connections i tried cm7 and i am facing another problem, i cant instal google. i went on filecrop and searched gogleapps and found 2 results, one apk that does not work and one zip file. I try installing googleapps.zip right after installing cm7.zip (the version from the cm defy link on the official site) and it just loops between the android skating and the start sceen for selecting wich language or a choice of start wizard and another one that i dont remember. Even if i reboot i get the same problem and if i try installing the rom without googleapps.zip all works great but i cant get google apps of course so i am shure it is when i instal the google.zip. So now what can i do?? Is there a super version of the rom with google apps already installed???
update; ok, ive got cm7 up and working, now to get that network connection on miui!!!!
Sent from my Nexus S using XDA App
baseband switcher is built into CM7/9...
it can be installed on MIUI to allow regular reception ^^
I wub MIUI...
PS - Why install custom ROM? So, your not stock! <<= never look back
Hello fellow Gio owners!
I have this problem with my phone, it's running CyanogenMod 7.1 RC3.0. It takes FOREVER to fix my GPS position! Like 20-25minutes or so...
The thing is, I use this great app CardioTrainer when I go out running, but I only get a GPS fix when I'm done!
I don't think it has anything to do with the current ROM since even with stock ROM it was pretty much the same. I also installed this FasterFix app, that didn't help either...
Do you guys have the same problem? Any advice or solutions?
Thanks in advance.
fikhl said:
Hello fellow Gio owners!
I have this problem with my phone, it's running CyanogenMod 7.1 RC3.0. It takes FOREVER to fix my GPS position! Like 20-25minutes or so...
The thing is, I use this great app CardioTrainer when I go out running, but I only get a GPS fix when I'm done!
I don't think it has anything to do with the current ROM since even with stock ROM it was pretty much the same. I also installed this FasterFix app, that didn't help either...
Do you guys have the same problem? Any advice or solutions?
Thanks in advance.
Click to expand...
Click to collapse
try to make sure you can see the sky so it gets a better fix also have you tried turning gps on and off or maybe even a factory reset
if i helped please click the "Thanks" Button
If there is a case or cover try to take it off and try again.
ارسال شده از GT-S5660 با استفاده از تپاتالک 2
GPS very slow and inaccurate on Samsung Gio
I am using the stock rom (Andriod 2.3.6) and I also have problems with my GPS.
I've been searching these forums for a while now but most people talk about either Sygic navigation or about a non-stock rom.
I hope someone can help me out here.
At first I could not find a fix at all.
After starting up Google Maps I did find a fix quite fast (4 - 5 minutes while being indoors).
After that, other apps (Endomondo and Runkeeper) also where able to find a fix (only outdoors, not indoors).
And now suddenly the time to find a fix outdoors has been degrading from almost instantly to more then 10 minutes. Also the fix is highly inaccurate.
The effect of this: when I go out for run, the app Runkeeper is not able to track my route and speed/distance. Which is exactly why I use the GPS function of my Gio. I hope this problem is fixable or at least to make the GPS function better.
I tried:
- Starting Google Maps again - no effect
- Resetting phone - no effect
- Wipe cache partition - no effect
- Banging my head against the wall - sore forehead
- Crying while running - wet face
So.... I am out of ideas... anyone with experience and knowledge about this problem on these forums that could help me out or point me in the right direction?
I am willing to root my phone and to use a custom rom if necessary. But I have no idea which rom is completely functional and works best with GPS. Also I have never rooted a phone before.
Perphide said:
I am using the stock rom (Andriod 2.3.6) and I also have problems with my GPS.
I've been searching these forums for a while now but most people talk about either Sygic navigation or about a non-stock rom.
I hope someone can help me out here.
At first I could not find a fix at all.
After starting up Google Maps I did find a fix quite fast (4 - 5 minutes while being indoors).
After that, other apps (Endomondo and Runkeeper) also where able to find a fix (only outdoors, not indoors).
And now suddenly the time to find a fix outdoors has been degrading from almost instantly to more then 10 minutes. Also the fix is highly inaccurate.
The effect of this: when I go out for run, the app Runkeeper is not able to track my route and speed/distance. Which is exactly why I use the GPS function of my Gio. I hope this problem is fixable or at least to make the GPS function better.
I tried:
- Starting Google Maps again - no effect
- Resetting phone - no effect
- Wipe cache partition - no effect
- Banging my head against the wall - sore forehead
- Crying while running - wet face
So.... I am out of ideas... anyone with experience and knowledge about this problem on these forums that could help me out or point me in the right direction?
I am willing to root my phone and to use a custom rom if necessary. But I have no idea which rom is completely functional and works best with GPS. Also I have never rooted a phone before.
Click to expand...
Click to collapse
The best rom for gps is CM7 from Phiexz. The latest update is from July 2012 so a little bit outdated but the gps fix is really good! You also can try CM7 from MMB team it's up to date and see if gps fix is the same as Phiexz rom. And I also change the gps.conf to my country. If you have CM7 let me know and I sent you mine gps.conf (with your language settings). Root your Gio is easy just flash an update.zip file in recovery. Then you need a custom recovery like cwm. Custom recovery is in ext4 format so you have to flash ext4 formatter before you flash the rom... it's also from Phiexz but when you choose CM7 from Phiexz you don't need ext4 formatter cause it's build in his CM7.
This is what I use:
- px-recovery or cwm (custom recovery)
- cm7.2 from Phiexz (custom rom)
- adrenaline engine (tweaks script)
- change gps.conf
- cronmod int2ext+ (so now I have 600 mb intern memory) (script)
- modded hosts file (no ad anymore)
Edit: it's a long time ago when I went from stock to custom rom so I don't remember anymore I only know I did it with Odin on pc.
Edit 2: I think you can do it without Odin now. This is the installation guide from CM7 MMB team thread:
Installation: You need to be on (at least) a Stock Gingerbread ROM 2.3.* otherwise your device won't boot:
[*]Root your device and install ClockworkMod Recovery.
[*] Reboot into Recovery (power+home key)
[*] Do a Nandroid backup!
[*] WIPE (wipe data/factory reset + wipe cache partition)
[*] Install the ROM (go in recovery and choose install from zip)
[*] Optionally install the gapps (play store, ...) But if you use cm7 from phiexz you flash the rom in recovery and a menu appears where you can choose wich settings and apps you want to install. Really easy.
Nice link:
http://www.androidauthority.com/galaxy-gio-s5660-root-68206/
The first thing you can try is to root your current stock rom and install an app that edit your gps.conf:
Root tweaker (change gps.conf + change host file)
https://play.google.com/store/apps/details?id=com.broodplank.roottweaker
FasterGPS (change ntp to your country + modded gps.conf)
https://play.google.com/store/apps/details?id=org.fastergps
Verstuurd van mijn GT-S5660
I Flashed AOKP's JB rom , this one to be precise ' http://forum.xda-developers.com/showthread.php?t=1985437 ' and it works smoothly.
Now the problem is, after i mount any script , int2ext / d2ext+ , it works well for the 1st time, but once i restart the phone, it goes back to having just 150mb free again and my ext partition doesn't seem to have been connected,i end up reflashing the whole thing again.My phone shows S-ON when i reboot in recovery, does that have something to do ? because when i flashed WIldChild 3, the scripts were working fine. i'm a newbie here, so can someone help!!
Xenux92 said:
I Flashed AOKP's JB rom , this one to be precise ' http://forum.xda-developers.com/showthread.php?t=1985437 ' and it works smoothly.
Now the problem is, after i mount any script , int2ext / d2ext+ , it works well for the 1st time, but once i restart the phone, it goes back to having just 150mb free again and my ext partition doesn't seem to have been connected,i end up reflashing the whole thing again.My phone shows S-ON when i reboot in recovery, does that have something to do ? because when i flashed WIldChild 3, the scripts were working fine. i'm a newbie here, so can someone help!!
Click to expand...
Click to collapse
WildChild (also my first ROM ) is based on the Stock Sense 2.1, so not much has been changed, well not technical stuff anyway, just visual with a few minor tweaks. JellyBean though is still in Alpha, meaning the features are minimal, also meaning that there are a lot of things that don't work, and will never work. I have used it, battery life was dreadful and it didn't do much so it's just to do with that ROM. Try this (Android 4.0.4) ROM: http://forum.xda-developers.com/showthread.php?t=1633198
I've used it and it's great, the only problem is that it doesn't read contacts from the SIM Card or Sync them from G-Mail, so if that's a problem (was annoying for me) don't use it. It would however get rid of all the problems you're having if you did use it..
99Aaron99 said:
WildChild (also my first ROM ) is based on the Stock Sense 2.1, so not much has been changed, well not technical stuff anyway, just visual with a few minor tweaks. JellyBean though is still in Alpha, meaning the features are minimal, also meaning that there are a lot of things that don't work, and will never work. I have used it, battery life was dreadful and it didn't do much so it's just to do with that ROM. Try this (Android 4.0.4) ROM: http://forum.xda-developers.com/showthread.php?t=1633198
I've used it and it's great, the only problem is that it doesn't read contacts from the SIM Card or Sync them from G-Mail, so if that's a problem (was annoying for me) don't use it. It would however get rid of all the problems you're having if you did use it..
Click to expand...
Click to collapse
I'll flashed the speed droid yesterday, and even though it says that the scripts are working fine (In the description) , my phone goes into boot loops when i flash it. Will flash the one you suggested! thanks ! :good:
CyanogenMod 11 KitKat for Optimus S/V
This is a basic CyanogenMod 11 rom for the Optimus S/V. It has NOT been tested extensively and I take NO responsibility for any bricked phones, data loss or damages that occur as a result of flashing any version of this rom. It requires ClockWorkMod 6.0.4.5 or later, or TWRP 2.6.3 or later, in order to flash.
What works:
Phone calling (ZVH and ZVJ radios require a patch)
Wifi
Mobile data (thanks to thekraven)
USB tethering
Camera
USB mass storage, MTP
What's broken:
Bluetooth
Wifi tethering
SELinux
You tell me
CWM 6.0.4.6 can be found in the rom directory. Flash Skinny_4.4_Gapps.zip after flashing the rom to get Play Store and Google Sync. Other Gapps will probably be too big to fit on /system.
https://www.mediafire.com/folder/nfgfef6qpril7/CM11
Contributors:
skinbark
bigsupersquid
thekraven
Special thanks to the CyanogenMod and androidarmv6 teams, also gu5t3r for GOptimize.
CM11 KitKat os2sd Version:
cm-11-20140116-thunderc-skinbark-sd.zip is a version of CM11 which is designed to run off your sd card.
To use this version:
1) create and format 3 ext4 partitions following the fat32 partition on your sd card (use gparted not a windows partitioning tool)
/data - at least 256 mb (512 mb or more recommended)
/system - at least 256 mb
/cache - at least 256 mb
2) format /boot in cwm
3) install cm-11-20140104-thunderc-sd.zip
4) install Skinny_4.4_Gapps-sd.zip and reboot
Known Issues (in addition to those in post #1):
formatting/backup/restore issues
possible reduced performance (older/slower sd cards)
reduced battery life (?)
Add wipe zips to a folder on your sd card and flash them from recovery to clear external /data, /system, /cache, or all three.
CWM_6.0.4.6-thunderc-sd.zip is a special version of CWM for os2sd that should only be used if you understand how it works.This version of CWM is not necessary to flash the os2sd rom. See this post for more info about recovery issues with this rom.
A Class 10 microSD card is recommended for best performance.
Power off or reboot to recovery before removing sd card.
os2sd mod courtesy of bigsupersquid
https://www.mediafire.com/folder/dj2d4vpp0hzvb/CM11sd
Warning: This is a highly experimental setup and a work-in-progress. You should have adb installed and know how to use it, along with the flash_image command, before attempting this install. If you have trouble installing this and are unsure how to resolve the problem ask for help on this thread. I take no responsibility for bricked devices, data loss or any other damages resulting from the use of this software. USE AT YOUR RISK.
New build with rild fix for ZVD/ZV5. You'll want to upgrade to this for stability and battery life even if you're not activated.
cm-11-20131225-thunderc-skinbark.zip
Link in OP.
Merry Christmas guys!
Sweet! Will flash once o find my ov...
Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
captaincrook said:
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
Click to expand...
Click to collapse
Well the biggie right now is getting data going which is sort of difficult for me since my phone's not activated (next week I hope). I'm assuming you're not activated? I guess just general stability and performance, battery life, see what you can run on on it, put it through the wringer. All info is welcome since I really haven't had much feedback yet. It seems to be pretty stable. Let me know if you have any problems, thanks.
really works well...nice job. No chance to test 3g data yet, but everything else works very well...I had to install a keyboard manually, and the battery stats are wrong (fully charged, and stayed fully charged all day) but it is def a daily driver for me.
I uploaded a new 'OS2SD' rom with special recovery, gapps and virgin fix:
cm-11-20140101-thunderc-sd.zip
CWM_6.0.4.6-thunderc-sd.zip
Skinny_4.4_Gapps-sd.zip
Virgin-fix-CM11-sd.zip
Link in post #2. Happy New Year!
Got the order of the partitions wrong in post #2, sorry. Fixed now. 3G fix coming soon!
I uploaded new standard and os2sd builds with data fix.
cm-11-20140104-thunderc-skinbark.zip
Link in post #1
cm-11-20140104-thunderc-sd.zip
Link in post #2
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
captaincrook said:
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
Click to expand...
Click to collapse
long press home and press the three-bar onscreen button to close running apps.
also fast reboot off market is very handy to manually clear ram. heard about that one from andyopie150, like it.
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
For now I can just suggest the usual speed-up stuff - turn off animations, ksm, cpu/governor etc. There may be some build.prop tweaks you could use, and I'm expectiing zram support to be enabled soon. Crossbreeder might be something else to try. If we could get ART going it might help some but I don't know if that's likely. I probably won't try to tweak the stock keyboard, there's plenty of alternatives available.
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Trozzul said:
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Click to expand...
Click to collapse
regular rom or os2sd?
skinbark said:
regular rom or os2sd?
Click to expand...
Click to collapse
regular i tried a different CWM 6+ and that one gave me the error*
Trozzul said:
regular i tried a different CWM 6+ and that one gave me the error*
Click to expand...
Click to collapse
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
Any information is a good thing, positive or negative. Harmonia with the Xionia kernel fairly flies speed-wise, but everything since that seems to choke my phone somewhat. And Mirage is the best Gingerbread available... but I enjoy the extra features more than the speed, which is what keeps me trying for the bleeding edge.
(example: the double-tap-hold-and-slide to zoom is built in all over 4.4, in 4.2 I only saw that in Maps.)
ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
CrossBreeder seems to work.