Related
Hi everyone !
http://project-voodoo.org/
I tweet about progress on the project.
Last but not least, the wonderful community-build page for the Voodoo 5 Froyo preview (not yet up to date)
Voodoo 5.x releases with Voodoo sound, build from sources, recommended:
Checkout the Sound bounty thread:
I propose also versions only the lagfix only, called stock+Voodoo because they are build around the kernel compiled by Samsung
stock+Voodoo-latest XYJS8:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS8.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS8-unsigned-update.zip
stock+Voodoo-latest XYJS5:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS5.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS5-unsigned-update.zip
stock+Voodoo-latest XYJS3:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS3.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS3-unsigned-update.zip
stock+Voodoo-latest XXJPY:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XXJPY.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XXJPY-unsigned-update.zip
stock+Voodoo-latest XXJPX:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XXJPY.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XXJPY-unsigned-update.zip
JPX, JPY, JS3 versions are based on Samsung pre-compiled kernels. This is why those are feature limited (no Voodoo sound, no BLN, no sharpness adjustment).
This project is 100% opensource and i'm proud of it
You can build everything from sources using https://github.com/project-voodoo
Important note, I don't recommend installing this relase with Odin if you don't have a direct access to the Download mode with the 3 buttons combination.
Odin is known to give a % of flash fails. This has no consequences for most because if you retry it works, but for people unable to go to the download mode this is a serious problem (and a Samsung official bug, they distribute a hardware part internally to force the download mode access)
5.1 changes:
Updated lagfix
Voodoo sound support (Download Voodoo App from the market)
5.0.3 changes:
added cool shell with tab completion
Final changes:
So many it will be hard to describe everything here:
converts /data /dbdata /cache /system to optimized Ext4 for each partition
more reliable and faster
beefed up conversion process, with conversion time estimation
memory management optimizations
VFS (disk write behavior) optimisations
BLN notification built-in
ClockWorkMod recovery built-in (optional) with total Rom Manager compatibility
Standard bootanimation support
linux standard /etc/init.d/ boot scripts support with integrated run-parts (additional busybox not necessary)
Click to expand...
Click to collapse
Short FAQ:
Does it includes Voodoo sound and color ?
- Voodoo color: sharpness adjustment and color rendering in videos only.
- Voodoo sound: YES
Also in stock+Voodoo builds ?
Nope, thos contains only the lagfix option (and su)
I want root !
Who doesn't
The technical setup is made automatically. If you want root, install Superuser App from market, that's all.
Hey, curio, do you have an eta for bêta 2? I mean first public release at least.
Will this kernel work on soon-to-come official froyo and less officiel Cm6?
Sent from my GT-I9000 using XDA App
I heard about a possible heavier battery draining using Voodoo lagfix comparing with a stock FW.
Anyone has an extensive feedback about that? (Maybe a direct comparison with/without?)
@Supercurio
Is heavier battery draining "kernelly" possible with your lagfix?
Hi,any way to get rid of clockword mod incompatibility issue?
Any other way to uninstall the fix,besides disable-lagfix file and flash of other firmware (it seems that some settings remain modified,i.e. wifi sleep time)?
Yes i can confirm the battery draining ...
I'm on M6 and after flashing the voodoo kernel the phone is really fast and smoooth...no lag anymore....really really fast. But too much battery draining...i fully charged till 11am ....at 23 pm the phone was completely exhaust with normal use of data connection and a bit of wifi...
So i removed the lagfix with the disable_lagfix file with no extension in the sd card and another little problem comes out. The wifi doesent turn off in idle with screen off..
Ryanza found a solution about this:
http://forum.xda-developers.com/showpost.php?p=7998188&postcount=458
Now my only trouble is about the battery draining...I just removed and fully charged my galaxy s and i'm wondering if the battery efficency is back as before the lagfix or i need to reflash my JM6.....or is there other solution like flashing only a kernel....
i dont know..
if someone know something about this let me know : >
(sorry for my bad english)
ivan
Narcissus85 said:
Yes i can confirm the battery draining ...
I'm on M6 and after flashing the voodoo kernel the phone is really fast and smoooth...no lag anymore....really really fast. But too much battery draining...i fully charged till 11am ....at 23 pm the phone was completely exhaust with normal use of data connection and a bit of wifi...
So i removed the lagfix with the disable_lagfix file with no extension in the sd card and another little problem comes out. The wifi doesent turn off in idle with screen off..
Ryanza found a solution about this:
http://forum.xda-developers.com/showpost.php?p=7998188&postcount=458
Now my only trouble is about the battery draining...I just removed and fully charged my galaxy s and i'm wondering if the battery efficency is back as before the lagfix or i need to reflash my JM6.....or is there other solution like flashing only a kernel....
i dont know..
if someone know something about this let me know : >
(sorry for my bad english)
ivan
Click to expand...
Click to collapse
well i unplugged it by 9am yesteday and I still have 74% battery left so I think the fix improved my battery life...
To every people experiencing Wifi sleep issue.
- Does it persist after flashing another kernel (OC kernel, Stock kernel) ?
- Does it persist after flashing another firmware ?
Thanks for your answers.
supercurio said:
To every people experiencing Wifi sleep issue.
- Does it persist after flashing another kernel (OC kernel, Stock kernel) ?
- Does it persist after flashing another firmware ?
Thanks for your answers.
Click to expand...
Click to collapse
Hello.After applying your fix the wiffi will turn off after 15 minutes on my jm7 firmware and to be honest i can live with that.I dont know about other firmware.Thank you for your work waiting for the full fix to be available
About battery draining i think its the same as before i didnt notice any raise on the draining.
Wifi sleeps after 15 minutes on JM7 after the lagfix was removed. I then replaced the kernel with stock and no change.
After that I restored a nandroid backup of JM5 and still no change.
I honestly couldn't tell if this was different after I installed JPC and then went back to JM5. I also had the NEW version of JM1 on there not too long ago. Mabe JM1 or JPC made changes or removed a setting. I would have thought that a wipe would clear /dbdata anyway.
Using RyanZa's database edit the wifi now sleeps again ;-) I needed to put the setting into both tables btw.
I think the 15 minutes to turn wifi off after display is off hasnothing to do with this kernel, i think (not sure 100%) it has already been with jm3 and jm7 without supercurios kernel.
First I wish to thank supercurio for the fix. It's perhaps one of the best I had tested so far. Been using it ever since and never had been happier.
Anyway are there anyway to reverse the lagfix ? I had did a few flashing between JPC and JM7 and it seems like the ext4 partition was never wiped off. The prior apps that were there before the wipe had persisted.
Thanks.
I have not noticed a difference in battery drain actually.
Hmmm.....so those on beta1 might have trouble upgrading to beta 2?
Well, my wifi takes 15 minutes to get disabled. I have never tried the Voodoo Lagfix, so that can't be the source of the issue. I was previously on JPC and currently on XXJM1. I don't remember if it used to take just 30 seconds for Wifi to turn off on my stock firmware - sorry.
No noticeably difference in battery drain here.
80 hours since last reboot of the phone on voodoo and not a hint of lag or slowdown. This one seems like the real fix for sure. (And no, that's not 80 hours without a charge, just no reboots.)
The lack of clockwork or some other whole-rom backup facility is slightly concerning, but I've only needed it once, and a fresh install plus appbrain/titanium backup are still available.
I did not notice any extra battery drain either.
As for the wifi. Has it ever been different? Anyone who has a different time in there?
Sent from my GT-I9000 using XDA App
WiFi sleep settings
Settings->Wireless and network->Wi-Fi settings->menu button->Advanced->Wi-Fi sleep policy set to never
You can change it to turn off WiFi when screen turns off, or keep it on if your phone is on charger.
..
kgk888 said:
Official instructions are to create a blank file with no extension in /sdcard with the name "disable-lagfix"
If you don't know how to do this from the desktop environment (extensions are disabled by default in Windows7), just use Root Explorer on your phone, navigate to the sdcard directory, hit the menu button, go to More, and create new file with that name. It will have no extension by default.
Then reboot.
What I did personally after the normal instructions was an SD card format, and a factoryreset/cache wipe just to be sure afterwards.
Then I flashed to a diff firmware. It wiped the EXT4 partition for me.
Click to expand...
Click to collapse
How's that video coming?
Sorry to be a noob, but how do I download beta 1? Do I have to sign up for the beta or something?
hi,,
i just flashed Android revolution 6.1 ROM on my DHD
everything is working fine but i cant get a gps fix ?? it picks up satellites but cannot provide me a fix ?
i have tried the efs wipe , faster fix etc method, but to no avail
any help ?
---------------------
andrd revolution 6.1.2
3.06.405.1 BUILD
2.6.35.14-rcmix-arhd-5.0--gd85ad63-dirty [email protected] KERNEL
Have you tried doing the method below? It tends to make GPS lock on faster as well as fixing the problem of no satellite lock.
http://forum.xda-developers.com/showthread.php?t=1252011
If the problem continues after this, I'd say try doing a wipe (optional I suppose, but I would) and flashing 6.1.3
Sent from my HTC Desire HD using xda premium
Hashed said:
Have you tried doing the method below? It tends to make GPS lock on faster as well as fixing the problem of no satellite lock.
http://forum.xda-developers.com/showthread.php?t=1252011
If the problem continues after this, I'd say try doing a wipe (optional I suppose, but I would) and flashing 6.1.3
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
i tired, http://forum.xda-developers.com/show....php?t=1252011 ,but when i do try this, im not even getting any satellites to even get a lock, but when i install rcmix3d gps patch it works better and locks but after like 2 minutes, and dont worry my antenna has contacts with the motherboard gps, i made sure of it, if you know the steps of what to do exactly using those patch in the thread i just posted i would really appreciate it, which one do i install? i try GPS CONF first one and alternate one tried the world patch still nothing, my phone is DHD btw, RCMIX3d 3.0 rom
thanks a lot HASHED ,,,
gps now works like a charm!!!
moh8021 said:
i tired, http://forum.xda-developers.com/show....php?t=1252011 ,but when i do try this, im not even getting any satellites to even get a lock, but when i install rcmix3d gps patch it works better and locks but after like 2 minutes, and dont worry my antenna has contacts with the motherboard gps, i made sure of it, if you know the steps of what to do exactly using those patch in the thread i just posted i would really appreciate it, which one do i install? i try GPS CONF first one and alternate one tried the world patch still nothing, my phone is DHD btw, RCMIX3d 3.0 rom
Click to expand...
Click to collapse
To be honest it is just what build you would like to use, but I personally prefer the Google specific build. You should only use the world file if your Rom doesn't support the updated version.
The easiest method (in my opinion) is flashing it via clockwork recovery. The steps are:
1. Download a GPS file (I chose the Google specific) and put it somewhere easily accessible on your sd card
2. Reboot into CWR
3. Mount /system/ (go to "Mounts and storage" option, then "mount /system")
4. Flash the GPS file from your sd card
5. Reboot your device
That should be it after rebooting its generally a good idea to get an app called GPS Status and leave it running for 5-15 minutes as the phone needs to get all the GPS data again, which happens the first time you use it. Hopefully it works for you this time
P.s. I'm currently using ARHD 6.1.2 and I haven't had any issues with it yet
Sent from my HTC Desire HD using xda premium
Hashed said:
To be honest it is just what build you would like to use, but I personally prefer the Google specific build. You should only use the world file if your Rom doesn't support the updated version.
The easiest method (in my opinion) is flashing it via clockwork recovery. The steps are:
1. Download a GPS file (I chose the Google specific) and put it somewhere easily accessible on your sd card
2. Reboot into CWR
3. Mount /system/ (go to "Mounts and storage" option, then "mount /system")
4. Flash the GPS file from your sd card
5. Reboot your device
That should be it after rebooting its generally a good idea to get an app called GPS Status and leave it running for 5-15 minutes as the phone needs to get all the GPS data again, which happens the first time you use it. Hopefully it works for you this time
P.s. I'm currently using ARHD 6.1.2 and I haven't had any issues with it yet
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
i dont have cwr but i have ext4 recovery, im guessing same type of procedure,i tried the google specific one but i never got any sattelite, so your saying i should run GPS status for 5-15 min? ive never left it for that long
moh8021 said:
i dont have cwr but i have ext4 recovery, im guessing same type of procedure,i tried the google specific one but i never got any sattelite, so your saying i should run GPS status for 5-15 min? ive never left it for that long
Click to expand...
Click to collapse
try using the latest CWR, it worked perfectly for me. and yeah, 5-15 mins just locked onto some satellites so you don't have to wait long when you really need to use it. It essentially just gets the data for the satellites, as previous data gets removed when you flash the GPS file. It isn't necessary but it is better to do it earlier
Sent from my HTC Desire HD using xda premium
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
Hey XDA,
I installed Codename Android on my phone about 2 weeks ago. There are two real issues with this ROM:
1. Lack of CWM Recovery - can't flash anything.
2. My GPS NEVER locks. EVER.
I don't care so much about #1, because I like the look, feel, and performance of this ROM. However, #2 is devastating. I use my GPS all the time. I can still get some function out of it (it gets my location within several hundred feet) by using the turn by turn directions and trying to follow them, but it's not the same as seeing EXACTLY where I am and EXACTLY where and when I need to turn.
What I'm trying to say is that I've gotten lost twice already!!
I've heard of a few solutions -
1. All of the "GPS Status" tricks. This hasn't worked for me.
2. Using a program to set my GPS region (North America) and then another program to get a GPS Fix on my signal. After 15 minutes of waiting, no fix was gained and I uninstalled both.
3. Go back to a GB ROM, turn on GPS, get a GPS lock, then leave on GPS and re-install ICS ROM. I can't do this because as I mentioned earlier, this Codename Android ROM does not have a CWM recovery mode and I can't make a nandroid backup.
Does anyone know of a real solution to this problem?
Can't you just Odin or mobile Odin back to a gb rom, then use option 3 in your OP? If you're concerned that you have no Nandroid backup option for your app data this way, I think you can still use TB for everything, since your backup and eventual restoral with both be done while running ICS at the beginning and end of the process.
Well I guess I'd be willing to try it, though I have yet to do a TB with ICS so can't confirm it works 100%.
I'd be much more comfortable doing it if someone else has done the same. Anyone out there?
I've never been able to get a GPS lock with any rom other than stock. I've tried all sorts of tricks using scripts and whatever you can think of and never get a lock. The best I ever get is like a 2100 meter radius.
webbiam said:
Hey XDA,
I installed Codename Android on my phone about 2 weeks ago. There are two real issues with this ROM:
1. Lack of CWM Recovery - can't flash anything.
2. My GPS NEVER locks. EVER.
I don't care so much about #1, because I like the look, feel, and performance of this ROM. However, #2 is devastating. I use my GPS all the time. I can still get some function out of it (it gets my location within several hundred feet) by using the turn by turn directions and trying to follow them, but it's not the same as seeing EXACTLY where I am and EXACTLY where and when I need to turn.
What I'm trying to say is that I've gotten lost twice already!!
I've heard of a few solutions -
1. All of the "GPS Status" tricks. This hasn't worked for me.
2. Using a program to set my GPS region (North America) and then another program to get a GPS Fix on my signal. After 15 minutes of waiting, no fix was gained and I uninstalled both.
3. Go back to a GB ROM, turn on GPS, get a GPS lock, then leave on GPS and re-install ICS ROM. I can't do this because as I mentioned earlier, this Codename Android ROM does not have a CWM recovery mode and I can't make a nandroid backup.
Does anyone know of a real solution to this problem?
Click to expand...
Click to collapse
this is actually pretty easy to fix now seeing as code name comes with cwm now... this is what I've done many times... get Mobile odin and flash an old el26 kernel with cwm on it. When rebooting starts hold volume up and power button then in cwm make a backup of your current rom real quick. After that wipe all data and everything so you're clean and flash ANY gb rom and get a GPS lock that is very accurate! Once you have that lock leave GPS on and boot into recovery again... now restore your codename rom and reboot ( even though it still has the el26 kernel). Once it starts rebooting hold the buttons for recovery once again until it appears. Now wipe everything except data (calkulins modified wipe all (no data)). Flash your codename rom again over your last recovery and that wlll give you the new codename kernel (which does have cwm now). Now reboot and you will be back at the same rom u were except your GPS WILL WORK perfectly! Hope you try this buddy!! Goodluck!!!
Sent from my SPH-D710 using xda premium
clipsedrag said:
this is actually pretty easy to fix now seeing as code name comes with cwm now... this is what I've done many times... get Mobile odin and flash an old el26 kernel with cwm on it. When rebooting starts hold volume up and power button then in cwm make a backup of your current rom real quick. After that wipe all data and everything so you're clean and flash ANY gb rom and get a GPS lock that is very accurate! Once you have that lock leave GPS on and boot into recovery again... now restore your codename rom and reboot ( even though it still has the el26 kernel). Once it starts rebooting hold the buttons for recovery once again until it appears. Now wipe everything except data (calkulins modified wipe all (no data)). Flash your codename rom again over your last recovery and that wlll give you the new codename kernel (which does have cwm now). Now reboot and you will be back at the same rom u were except your GPS WILL WORK perfectly! Hope you try this buddy!! Goodluck!!!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
what codename rom did you flash??
i just flashed the latest one and it does not have cwm on it...
Cmon... use Odin or Mobile Odin to flash a stock CWM recovery. Boot to recovery. Nandroid. Flash GB ROM. Get GPS lock. Reboot to recovery immediately, flash stock CWM recovery, wipe and restore backup.
It takes 10-15 minutes.
This sounds like a quick fix...I'll try it when I have the time.
I'm also curious about clipsedrag's comment. Where did you get a Codename ROM with a recovery baked in? I'd love to upgrade.
Hello!
I've tried installing App2SD script just after applying MIUIv4 firmware and it works - but - the speed/access time is slow to speak the least. The phone is completely useless - Android Tools measured the time needed to boot up for system only: 110 min. After that I could use Dialler, Contacts with no "slowdowns" whatsoever, but again - when I just wanna to install a new application the nightmare starts again - everything is laggy, downloading an app takes forever - installing ever more.
I think, that the best solution for that could be S2E, which works just fine for me on CM7. But I have no luck with that either (App does not recognize EXT partition).
Does anybody know how to make these two things work together?
stalowynalesnikzaglady said:
Hello!
I've tried installing App2SD script just after applying MIUIv4 firmware and it works.../QUOTE]
Hey, how did you manage to get it to work? I've been trying for quite a while with no luck.
Click to expand...
Click to collapse
If you're using (and hopefully you do, because the new version is a lot better) 2.8.3 you could use a CronMod-INT2EXT4+ script provided within croniccorey's thread. The new MIUI and this INT2EXT4+ script doesn't affect phone performance like it was with the older MIUI port.
But, be careful - the 2.8.3 have some strange battery issues. In my case, the phone didn't last for more than 8-10 hours. Now I'm trying to reproduce that and see what makes that strange issues. Also, some users wrote, that their phone's batteries aren't affected more after installing the MIUI port... You should see it for yourself.